IDOC error for same custom IDOC extension/segment between two SAP systems (version 750->740) – Part II
Introduction: In my previous blog, I explained a scenario in which we needed to add new fields in a custom segment of the IDOC in two SAP systems while both systems are on different releases. It is mention to worth it that there were no problems before the upgrade when both SAP systems were on the same release (740).
In this article, I’ll cover how to add new segments in the same IDOC basic type and custom extensions in SAP MDG(750) and SAP ECC(740).
Background: To illustrate the issues and potential fix, I’ll use the MATMAS IDOC (Basic Type: MATMAS05) with extension (ZMATMAS05_EXTN) and a single custom segment (Y1MARAM1) that was developed identically in both the SAP systems.
So let’s get started.
While it is possible to add new segments to the ECC system (in the custom extension in the same release, let’s say 740), however, the same segments could not be added in MDG with the older extension version. According to the SAP release strategy, to add new segments to the IDOC extension from prior versions, a successor extension must be created.
SAP MDG system release – 750
IDOC Extension release – 740
It is not advisable to cancel the release which is from the previous SAP release.
In this scenario, we need to create a new successor extension ( let’s say ZMATMAS05_EXTN_750) of an existing extension(ZMATMAS05_EXTN) in the MDG system, add a new segment (Y1MARAM1_NEW ) and release the segment and the new extension.
Change ABAP code when passing CIMTYP (new extension ZMATMAS05_EXTN_750) for IDOC extension in the MDG system.
Next, we need to maintain Output types and IDOC type/extension in T-code WE82
And in WE20 for the outbound partner profile – Add extension ZMATMAS05_EXTN_750
Now we will log in to the ECC system and will create the same replica as the MDG ones. So we will create one successor extension and a new segment. We can release the segment but not the extension ZMATMAS05_EXTN_750 following the SAP basic release concept ( We can’t have two released extensions in the same release, here 740).
In T-code WE82: Add Message type, Basic type, and new extension ZMATMAS05_EXTN_750, same as MDG.
In T-code WE57: Add an entry for FM (for Inbound IDOC processing) against message type, basic type, and new extension ZMATMAS05_EXTN_750.
This completes the configuration and now IDOC is ready to be sent over from MDG to ECC and will be posted successfully in ECC.
Now next step is not required but if we want to release new extension in ECC, then we need to change it in the SAP standard table EDCIM-related to the old extension (here ZMATMAS05_EXTN) – in debug mode. We can set Application Release ( for example 617) and it will allow releasing new extension( ZMATMAS05_EXTN_750 ) too.
I sincerely hope you enjoyed reading this article. Please continue reading. I value your opinions and recommendations at any moment. And, once again, thank you for your time.