BW/4 HANA中ADSO的各种类型运用

BW/4HANA 版本，ADSO的一篇详细官方文档，写的还是很详细的，有和传统版的比较和介绍！看完这个希望对各位理解ADSO有一点帮助！
如有不对的地方或者需要改进的地方 欢迎在评论区留言或者私信予以指正,谢谢！
考虑到本人也是英语菜鸟，所以我就在下面弄了翻译！哈哈哈…见笑见笑!

Purpose
The purpose of this post is to show you the different types ADSOs in BW/4 HANA. The way to check them in the front end modeling tools (General tab on the ADSO -> Modeling Properties) and in back end ABAP (Transaction RSMNG -> ADSO name -> Manage tab-> Show settings).

本文的目的是向您展示BW/4 HANA中不同类型的ADSO。在前端建模工具（ADSO上的常规选项卡->建模属性）和后端ABAP（事务RSMNG->ADSO名称->管理选项卡->显示设置）中检查它们的方法。

Standard DataStore Object
Write Change Log:
If you choose this option, the delta (new, deleted, and changed records) is saved in the change log. The change log is used to extract the delta. Requests can only be rolled back from the DataStore object if the DataStore object has a change log; that is, the status before the activation of the request can be restored. Compared to the past (standard DSO classic), it is a new option to not use a change log. This can save resources if you do not require any delta extraction from this source object.

如果选择此选项，增量（新记录、已删除记录和已更改记录）将保存在更改日志中。更改日志用于提取增量。如果数据存储对象具有更改日志，则只能从数据存储对象回滚请求；即，可以恢复请求激活之前的状态。与过去（标准DSO经典）相比，不使用更改日志是一个新选项。如果不需要从此源对象提取任何增量，则可以节省资源。

Without Change Log:

● Snapshot Support:
If your DataSource only delivers the current dataset as a “FULL”, by setting this indicator, deleted data records can be identified and updated. Upon activation, the system recognizes records that are in the table of active data but not in the load request. These are written to the change log as reverse images

如果DataSource只将当前数据集作为“FULL”交付，通过设置此指标，可以识别和更新已删除的数据记录。激活时，系统识别活动数据表中但不在加载请求中的记录。它们作为反向映像写入更改日志

OBS: It is not possible to have Snapshot support without writing to the change log.

如果不写入更改日志，则不可能拥有快照支持。

● Unique Data Records:
If you only load unique data records (data records with non- recurring key combinations) into the DataStore object, you can select this property. If the indicator is selected, during activation, the system checks whether unique records exist. If a record already exists, the activation is canceled with an error.

如果仅将唯一的数据记录(具有非重复组合键的数据记录)加载到DataStore对象中，则可以选择此属性。如果选中该指标，激活时系统会检查该指标是否存在唯一性记录。如果已有记录，则取消激活并报错。

With Change Log:

Without Change Log:

Staging DataStore Object
Inbound Queue Only: No data is saved in the change log. The extraction process always reads the data in the inbound table again—for delta extraction or full extraction. This object is not suitable for reporting and analysis.

Inbound Queue Only: 修改日志中没有数据保存。提取过程总是再次读取入站表中的数据—用于增量提取或完全提取。此对象不适合报告和分析。

Compress Data:
In general, the data is always written to the inbound table. If you choose Compress Data, the data is written to the table for active data (during the compression process) once it arrives in the inbound table. During activation, the data is aggregated in accordance with the semantic key and is written to the active data table. In the query, you will then only see the data that has been activated. To save memory space, the change log is not filled. Therefore, you cannot perform request-based deletion of data from the DataStore object. You can only delete data selectively.

通常，数据总是被写入入站表。如果选择Compress Data，当数据到达入站表时(在压缩过程中)，该数据将被写入表中用于活动数据。在激活期间，数据根据语义键聚合，并写入活动数据表。在查询中，您将只看到已激活的数据。为了节省内存空间，不填写更改日志。因此，不能从DataStore对象执行基于请求的数据删除。只能有选择地删除数据。

OBS: The setting in the backend is the same as for a Standard ADSO.

Reporting-Enabled:
Data is written to the active data table, but is also kept in the inbound table. Since the data is stored redundantly in the inbound table, the data can be deleted from the active table and rebuilt from the inbound table. The data is only extracted from the inbound table. When a query is executed, the active table is accessed

数据被写入活动数据表，但也保存在入站表中。由于数据冗余地存储在入站表中，因此可以从活动表中删除数据，并从入站表中重新构建数据。数据仅从入站表中提取。当执行查询时，将访问活动表

OBS: In BW/4 HANA 1.0 in the front end the setting it is as the back end showing as “Keep Inbound Data and Extract from Inbound Table”

勾选这个的话就是从入站表提取数据

Data Mart DataStore Object
The Data Mart DataStore object is optimized for reporting and analysis (similar to InfoCubes of the past)

Inventory-Enabled (Non-Cummulative)

Planning-Enabled

OBS: In BW/4 HANA 1.0 the Data Mart DataStore Object is represented by: “All Characteristics are Key, Reporting on Union of Inbound and Active Table” The settings are the same in the back end.

Direct Update DataStore Object

In the DataStore object for direct update, you can load data directly to the table of active data, including standard consistency checks (for example, SID processing, consistency of time characteristics, areas locked by cold store, or NLS).

在用于直接更新的DataStore对象中，可以直接将数据加载到活动数据表中，包括标准一致性检查(例如，SID处理、时间特征的一致性、冷存储锁定的区域或NLS)。

DataStore Object with Write Interface

The data in this DataStore object can be moved to the inbound table using SAP integration solutions by PUSH. Based on this property, it is the successor for the obsolete BW source system types SAP Data Services and Web Service.

这个DataStore对象中的数据可以通过PUSH使用SAP集成解决方案移动到入站表。基于此属性，它是过时的BW源系统类型SAP Data Services和Web Service的继承者。

Standard ADSO with Write Change Log

Inbound Queue Only

OBS: In the backend these settings are the same as per each type mentioned above. It is not possible in RSMNG to determine from there if the Write Interface-Enabled flag is used or not.

在后端，这些设置与上面提到的每种类型相同。在RSMNG中不可能从那里确定是否使用了Write Interface-Enabled标志。