cancel
Showing results for 
Search instead for 
Did you mean: 

how the master data delta works

Former Member
0 Kudos

hi, experts

i want to know how the master data delta (ale pointer) works? what the principle is? for example, the 0asset_attr datasource has 20 fields, any of the 20 fields changes can triger the delta? if i enhance 3 fields to the asset master data, does the 3 fields change can trigger delta?

Accepted Solutions (1)

Accepted Solutions (1)

dennis_scoville4
Active Contributor

Application Link Enabling (ALE) change pointers are configured and used to be able to trigger processing of an outbound process, such as data extraction, and determine only those Master Data records that have changed. This is all done without the need for a program being required to determine deltas.

SAP delivered program, RBDMIDOC runs periodically and deterlines if change pointers have been updated for specific message types. New or modified Master Data records are automatically initiated via ALE. RBDMIDOC references the correct IDoc program for any given type via TBDME (the TBDME table also cross-references message types with the ALE change pointer table) so that the data goes where it should and is processed accordingly. Tcode BD60 is the interface in SAP for maintaining the TBDME table.

When a change is made to the standard content Master Data record, the delta will be identified. Any columns that have been enhanced to the Master Data will not be identified as a delta because enhancements are a post-extraction process and only get updated after the standard content structure has been populated.

Former Member
0 Kudos

thanks for ur rapid reply, and i still have a question. u said "only get updated after the standard content structure has been populated", i don't understand, for example, i enhance the asset with 3 fields, z1 z2 z3, and if i add the 3 fields to the asset master data table anla, then the 3 fields change can trigger delta, am i right?

dennis_scoville4
Active Contributor
0 Kudos

Changes to values that have been appended to an extraction structure and User Exit code created, will not trigger a delta, with the exception that they are on the actual source R3/ECC table.

In your scenario, you said that the columns being added to the extraction structure and populated via a User Exit are on the ANLA table. That being the case, I believe that a delta would be triggered since the 0ASSET_ATTR_TEXT, or 0ASSET_ATTR, DataSource is sourced by the ANLA and ANLZ tables.

Had these new columns not been on ANLA or ANLZ, changes to them would not have triggered a delta.

Answers (0)