Issues in Delta extraction for 0MATERIAL_ATTR and 0MAT_PLANT_ATTR
Note: The content in this blog is applicable to retail systems only.
Hi All,
In my project, we faced issues in delta extraction for 0MATERIAL_ATTR and 0MAT_PLANT_ATTR. Thought of sharing the workaround for the same.
For Retail Systems, delta doesn’t work for 0MATERIAL_ATTR and 0MAT_PLANT_ATTR.
Hence, it is suggested to use 0ARTICLE_ATTR and 0ART_PLANT_ATTR instead.
Also, please note that the delta extraction for these datasources is based on the concept of change pointers. It involves different tables which are listed below:
1. Table ROOSGEN shows which message type (format: RSxxxx.) has been assigned to a datasource.
2. Table BDCPV contains the change pointers. Every time a change relevant to the datasource is performed, a change pointer with message type RSxxxx is added to table BDCPV.
3. Table TDB62 shows fields of tables that are relevant for a message type. That is, only changes of these fields will generate a change pointer (even if there are more fields in the datasource)
4. ROMDDELTA stores for each datasource, which change document object is used and which table is used for generation of the change documents. The information stored in table ‘ROMDDELTA’ are used to generate the entries in the table ‘TBD62’. The entries in ROMDDELTA are normally created when activating a DataSource in RSA5.
If it is not there, the DataSource should be re-activated (and replicated in BW to be sure of consistency).
For a datasource: In table ROMDDELTA, field TABNAME should be the same as the TABNAME field for TDB62.
Also, esnure that the ‘Object’ field in table ROMDDELTA has value ‘MAT_FULL’ for both the datasources.
For 0ART_PLANT_ATTR, if the TABNAME field in table ROMDDELTA has value ‘MARC’, you need to run a ABAP report for changing these entries to DMARC. Below is the ABAP code that can be used.
REPORT ZZ_ROMDDELTA.
UPDATE romddelta
SET tabname = ‘DMARC’
WHERE tabname = ‘MARC’ and OLTPSOURCE = ‘0ART_PLANT_ATTR’.
COMMIT WORK.
Hope this blog post helps you.
Thanks.
Regards,
Jatin
Very good doc. Thanks for sharing Jatin.
SPRO, Logictics General->Material Master->Global...->Set Change Document Items for Message Type, setup of fields for message type, which trigger change pointer generation. (TBD62 table)
BDCPV is an old view on BDCP+BDCPS. Newer basis versions (>7.01) use BDCP2.
Good summary, Thanks for that.
few additions:
1) Table ist TBD62 (not TDB62)
2) Change Pointer are stored in Table BDCP2 (BDCPV is empty - ERP 6.0 EHP 7)
3) The RSxxxx Messages Types are not found in the TA BD52, it is therefor not possible to alter the mechanism manually