As per my knowledge, this should not have any impact. I would double check to see if there are any internal dependencies.
Original Message:
Sent: Mon February 10, 2025 01:11 PM
From: Hari Sadhu
Subject: SAP S4Hana Integration with B2Bi
Hi Navvakanth,
Thank you so much for your detailed explanation. This will help us a lot.
Also, I do have a one more question.
We are leaning towards NOT extending Material Number to 40 characters as it's drastically increasing the project scope and also extending material number to 40 is not mandatory.
So, will there be any other potential impact that should be considered with respect to S/4 HANA Migration from an IBM Sterling Integrator standpoint ?
Thank you,
Hari Sadhu
Original Message:
Sent: 2/10/2025 8:57:00 AM
From: navyakanth surugu
Subject: RE: SAP S4Hana Integration with B2Bi
Hello,
Expanding the Material Number (MATNR) length from 18 to 40 characters during the S/4HANA migration can affect IBM Sterling B2B Integrator (SI) in several ways.
First, you need to check how this change impacts EDI mappings. If Material Numbers are used in transactions like 850, 810, or 856, confirm whether the target format supports 40 characters. Standards like ANSI X12 and EDIFACT may have field length limits, so you might need to truncate or split the values.
Next, review Business Processes (BPML) to ensure scripts and rules handling Material Numbers can process 40-character values correctly. If you have JavaScript or BP rules checking the MATNR length, update them accordingly.
Also, verify that your database, logs, and mailbox files in Sterling can store the expanded values without issues. Another key factor is trading partner compatibility. Contact your partners to confirm they can process 40-character Material Numbers in inbound and outbound transactions. If they still expect 18 characters, you may need to apply truncation or transformation rules. To address this issue, update your EDI maps to support the new field length, adjusting rules as needed. Modify BPML scripts or any custom logic that processes Material Numbers. Conduct end-to-end testing in a lower environment to ensure partners can handle the change. A complete remap is usually not required updating existing maps should be enough unless there are dependencies on string manipulation or validation logic, in which case partial remapping may be needed.
Hope this helps!
------------------------------
nav
------------------------------
Original Message:
Sent: Fri February 07, 2025 06:46 PM
From: Hari Sadhu
Subject: SAP S4Hana Integration with B2Bi
Hi Trevor.
We are exactly in the same boat as yours. How about the Material length extending from 18 Characters to 40 Characters ? Did you incorporate this change in your S/4 HANA Migration. Did that impat your IBM Sterling Integrator ? Do we need to completly remap in IBM Sterling Integrator because of this change ?
Appreciate your insights.
Thanks,
Hari
------------------------------
Hari Sadhu
Original Message:
Sent: Fri September 18, 2020 07:23 AM
From: Trevor Richards
Subject: SAP S4Hana Integration with B2Bi
In our current project we're successfully using the "SAP Suite Adapter for JCo 3.x" service in IBM Sterling B2B Integrator 6.0.2.1 to integrate with SAP S4 HANA. We're using exactly the same methodology that we've used previously with SAP R/3.
Trevor Richards
Original Message:
Sent: 9/17/2020 3:29:00 AM
From: KALYAN PAVAN KISHORE CHAKRAVARTHULA
Subject: RE: SAP S4Hana Integration with B2Bi
Hi Rags,
As far as I know, SAP S4 HANA is a completely redesigned product. I see an RFE. I would suggest you to vote so, that IBM offering manager can prioritize accordingly.
https://watsonsupplychain.ideas.aha.io/ideas/B2BI-I-465
Hope this helps.
Kishore
------------------------------
KALYAN PAVAN KISHORE CHAKRAVARTHULA