Find the values needed for Message Format Table Name for an IDoc
Follow these steps to find the exact names needed for IDoc Message Format Tables in the NCM.
NMM Error Message
An example of a parsing error from an incorrect IDoc Segment Name / Message Format Table Name looks like this in the NMM:
Error finding table information for a message: Table information is not available on this map. (Map ID = 7, Table Name = 'E2KBEDL001')
Step-by-step guide
The Message Format Table Name for IDocs needs a specific value that has to match the current incarnation of the IDoc in the SAP system. One thing that changes the value required for Message Format Table Name is new releases of an IDoc Segment in the SAP system.
If you use the IDoc Wizard, you'll have the right values for Message Format Table Names at the time you run the Wizard. If you get subsequently get parsing errors, generally after an SAP upgrade, then these table names might be different.
Message Format Table Names in the NCM
Look in the Message Format Table Name column to see the current values in the NCM. Note that these will be the "E2" names from SAP rather than the "E1" names.
NLINK v7x and earlier presented the Table Name in the Attributes pane.
Internal Segment Names in SAP
To find these names, go to transaction WE60 and put in the IDoc type. Choose the Parser button.
Then do a Find for BEGIN_SEGMENT.
This gives you a list of just the segments with their internal names. These are the values you need to put into the Message Format Table Name in NLINK.