Show TOC

Procedure documentationEnhancing a Basic Type Locate this document in the navigation structure

Prerequisites

You must have completed the required steps in Enhancing an IDoc Type.

Note Note

Sometimes you might want to fill table fields that already have an equivalent in the basic type but that are not supplied in the standard system. You therefore do not need to extend the basic type, but rather only the function module that supplies the application fields. In this case, skip the procedure.

End of the note.

Procedure

  1. Choose   SAP Menu   Tools   IDoc Interface/ALE   Development   IDoc   Generate ALE Interface   IDoc Type (WE30)  . The IDoc type editor is displayed.

  2. If you have not already done so, create a transport request for your development objects (extension segments, extension, function exit and so on). You can access the Workbench Organizer from the editor by selecting Requests (Organizer). From there, select   Request   Create   and follow the prompts. takes you back to the IDoc type editor.

  3. Name your extension in accordance with the customer namespace and choose Extension as the development object. Choose .

    Caution Caution

    The name of your extension should be no more than 8 characters if you wish to use the extension to communicate with partners who are using SAP Releases prior to 4.0. You can only use extension names with more than 8 characters from Release 4.0 onwards.

    End of the caution.

  4. Select one of the following options:

    • Create:

      create the extension without a reference.

    • Create as a copy,

      which you can then change as necessary

    • Create as successor:

      note that only one successor is allowed per release for each extension.

  5. Select the basic type which is to be combined with your extension. Confirm your entries.

    The basic type is displayed as a tree structure. See the color legend (  Utilities   Color legend  ).

  6. Position the cursor on the segment where you wish to append the extension segments (the reference segment). Choose . You must now assign attributes to these child segments:

    • Required segment (indicator):

      Does data have to be written to this segment in the IDoc?

    • Maximum and minimum frequency of use:

      How often may / must a segment occur in the IDoc?

  7. You can add additional children or "grandchildren" to this or any other reference segment of the basic type.

  8. When the new extension is complete, you can save your entry.

    Caution Caution

    You should keep the following factors in mind when dealing with extensions:

    • In the IDoc type, segments may not explicitly occur several times

      This also means that the extension must not have any segments that already exist in the basic type. This also means that a successor must not have any segments that already exist in the predecessor.

    • Parent segments of predecessors must remain parent segments in the case of successors.

    • Extension segments cannot be created from reference segments using the Cut and Paste functions and vice versa.

    End of the caution.

Example Example

In the example call your extension Z1ORDERS. Append child segment Z1TEST1 to reference segment E1EDP19 in basic type ORDERS01. The child segment can be used only once.

End of the example.