Loading an IDoc Structure from Lobster_data
The following screenshot shows the dialogue for importing a supplied IDoc template (in this case for a source structure).
(1) Search field.
(2) List of IDoc templates. There are three template types. IDOC_ (for SAP version 46C), V7IDOC_ (for SAP NetWeaver 7x) und V75IDOC_ (for SAP NetWeaver 75x).
(3) If this checkbox is set, the structure is refreshed. This only makes sense if the structure is not replaced, but is to be updated. For example, because the IDoc was extended with a new custom segment or new fields. Lobster_data tries to keep function chains and formats in existing destination structure if the differences to the IDoc template are minimal.
(4) Only applies to destination structure templates. See the following section.
(5) Only applies to source structure templates. If this checkbox is not set, the match codes of the source structure nodes are created with the version number of the respective segment and filled with whitespaces from the right up to 30 characters. If the checkbox is set, the version number and the whitespaces are not added.
Example with version (trailing whitespaces are represented with underscores):
|
Starts with: E2EDK01005____________________ |
Example without version:
|
Starts with: E2EDK01 |
Note: This checkbox is also effective for the direct import from the SAP system. However, only the match codes are adjusted, not the names of the nodes.
Variables for the Idoc Segment Header in the Destination Structure
If option (4) is set, the profile variables necessary for the generation of the segment headers of the IDOC (SYS_DOCNUM, SYS_MANDT, SYS_SEGNUM, SYS_SEGNUM_1, SYS_SEGNUM_2, SYS_SEGNUM_3, SYS_SEGNUM_4, SYS_SEGNUM_5, ...) are created automatically with the appropriate data type if they do not already exist.
In addition, these variables are filled in the corresponding destination structure fields with automatically placed functions, as you can see in the following screenshot.
(1) Field MANDT in control segment EDI_DC40 in the destination structure.
(2) Field (1) and variable SYS_MANDT get the value of the linked (mapped) field (3).
(3) This setting means that the value assigned to the variable is taken from the linked (mapped) field. The mapping itself has to be done by the user.