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

[balazsbence95]

Hi Kiran,

For double checking I suggest you to create a brand new CPI-DS task with the same dataflow logic with a target csv file instead of targeting the IBP table. This will tell you how the data really looks like leaving CPI-DS.

If the data is correct in the csv file, then there might be some problem in IBP that you may follow up with the IBP support team (support component: SCM-IBP-INT-TS-DS).

Regards,
Bence

[kirankalpathy]

Hi Bence,

I followed your tip and the data in CSV is also populated as <NULL>. This means that there is an issue either in CI-DS or the source S4 extractor from which we are picking the data.

Weird thing though, as per my understanding if the data flows through in the design time viewer of CI-DS, I expect it to be flowing during the actual interface run. In this particular case, there is data for every flow in the design time viewer but not in the final output. Is there some other way to check the root cause for this issue?

Best,
Kiran Kalpathy

[balazsbence95]

Hi Kiran,

The Design-time data view is just a simulation which is not capable of simulating everything (e.g. the outcome of certain functions). Suggest you to execute the /IBP/LOCATION_ATTR extractor directly in SAP and check the records returned.

Are there NULLs?

Thank you,
Bence

[kirankalpathy]

Hi Bence,

I am able to see the values in the extractor /IBP/LOCATION_ATTR using the RSA3 T-code but is populated as <NULL> in both the CSV file and the IBP attribute.

1. For the highlighted record there is no <NULL> in the extractor output
2. This is a custom field and has been enhanced to populate values in the source system
3. There is no mapping rule for this attribute and is a one-to-one mapping in CI-DS

Extractor Output:

Best,
Kiran Kalpathy

[gambethkar]

1. check pre-processing error log file,

2. may be data type/ length different

[kirankalpathy]

Hi Ambethkar,

Thanks for your response. I have updated the thread with the observation and marked it as an answer. It was an issue in S4 and not CI-DS or IBP 🙂

[kirankalpathy]

Hi balazsbence95,

Issue was because of some inconsistent code in S4. CI-DS and IBP work as expected. The idea of writing data into a CSV file seems to be the resolution for such issues. Thanks so much for your efforts!

Key takeaway: Design Time Viewer is NOT 100% accurate for data validation 🙂

Best,
Kiran Kalpathy