Data not integrating to IBP but visible in CI-DS Design Time Data Viewer

[kirankalpathy]

Hello Community,

Requesting your help & expertise on the following issue -

• A couple of attributes in IBP MD are being currently populated 'NULL'
• Their mapping seems to be fine in CI-DS
• We are able to see the values of the attributes in the design time data viewer of CI-DS
• When we run the interface for data integration it seems to load the right number of records - but certain attributes are not loaded properly

Screenshots of the same as follows. Any leads much appreciated 🙂

CI-DS Flow:

CI-DS Design Time Data Viewer (of final transformation):

Data Integration Log:

Additional Observations:

1. We are able to manually edit the master data work book, maintain & save values for these attributes
2. We are able to load the data using the Data Integration Tile (CSV upload) and attributes are populated as expected
3. When we hardcode the value of these attributes in CI-DS (such as 'X' for all records), the attribute is populated as expected

Best,
Kiran Kalpathy

[kirankalpathy · Accepted solution]

Issue was due to some inconsistency in S4.

I noticed that when it comes to working with extractors for IBP integration in CI-DS, it is a best practice to use the transaction /IBP/ETS_REPL_TEST with the projections (list of fields) and selections (filters for the fields) as defined in CI-DS to simulate the CI-DS extraction in S4 instead of the transaction RSA3. Reference of the same is provided in the help portal - SAP ERP or SAP S/4HANA Add-On Integration | SAP Help Portal

[somnath_manna · Accepted solution]

Hi Kiran,

We came across same issue. Do you know what was S4 inconsistency and how it was resolved?

Was it resolved by S4 ABAP team who enhanced Extractor structure or the inconsistency was resolved by SAP Support.

Thanks in advance,

Somnath

[kirankalpathy · Accepted solution]

Hi somnath.manna,

The issue was in the extractor enhancement (ABAP code) and was solved by the ABAP team. The ABAP team can use the method explained above (t-code: /IBP/ETS_REPL_TEST) for their unit testing and place debuggers on the enhanced code to look further into the issue.

Hope this solves your query.

Cheers,
Kiran Kalpathy