SAP ABAP IMG Activity OLIS_WE30 (Maintain as IDoc)
Hierarchy
☛ SAP_APPL (Software Component) Logistics and Accounting
   ⤷ LO-LIS (Application Component) Logistics Information System (LIS)
     ⤷ MC0C (Package) Customizing Logistics Information System
IMG Activity
ID OLIS_WE30 Maintain as IDoc  
Transaction Code S_ALR_87000939   IMG Activity: OLIS_WE30 
Created on 19981222    
Customizing Attributes OLIS_WE30   Maintain as IDoc 
Customizing Activity OLIS_WE30   Maintain as IDoc 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name OLIS_WE30    

If you wish to transfer your data via the IDoc interface to LIS, you must first create a communication structure/> as a DDIC structure.
In this IMG activity, you create your IDoc type as an enhancement to the SAP Basis IDoc type "LIS_EXTR", which contains your data for the IDoc interface.

Enhancement. The enhancement is where you create your enhancement segment with the data to be transferred.

Note

Please observe the name ranges:

  • SAP segment types begin with "E1"; customer-specific segment types begin with "Z1".
  • Customer-specific IDoc types begin with "Y" or "Z".

Activities

If you wish to create an IDoc, proceed as follows:

  1. Create your extension type.

    You create an extension as follows:

    1. Enter any name for the object in the Object name field.
    2. Mark the development object as "extension".
    3. Select the function Create development object.
    4. Select create and enter the related basis type "LIS_EXTR".
    5. Enter a short description for the object.
    6. Confirm by pressing Enter.
    7. Go to the initial screen "Segment Development"
      via Environment -> Segment maintenance
    8. Enter a name for your enhancement segment in the field Segment type
      9. Note the Name space.
    9. Use the function Create segment with reference.
    10. Use the DDIC structure you created as the communication structure for the IDoc interface as the reference.
    11. Enter a short description of the segment type.
    12. In the segment definition, the fields in the communication structure are automatically proposed according to the reference. The export length required for the correct conversion of the various data types in CHAR fileds is also automatically determined in the segment definition. The export length can therefore be longer than the length used for the same field in the communication structure. The field names in the segment definition and the communication structure must be identical, as the segment releases the data to the communication structure by means of MOVE CORRESPONDING.
    13. Save your segment definition.
    14. Return to the initial screen "Segment Development"
    15. Leave this screen to create the enhancement.
    16. Position your cursor on the LIS basis segment "E1LISBA" and choose the function Edit -> Create segment. Your enhancement segment type is added as a subsegment type of "E1LISBA".
      17. You now branch into maintenance of the segment attributes.
    17. In the field Segment type, enter the name of the enhancement segment just created from h) to m).
    18. Set the indicator for mandatory segment.
    19. Specify the minimum number of segments in sequence, in other words, the minimum number of external data records that are to be transferred (at least 1).
    20. Specify the maximum number of segments in sequence, in other words, the maximum number of external data records that are to be transferred at any one time. SAP recommends that you enter the number 1000 here.
    21. Save your enhancement.
    22. Return to the initial screen "Development of IDoc Types".
    23. When your development is completed, you should release the segment definition in the initial screen "Segment Development" (n) via Edit -> Set release and release the enhancement in the initial screen "Development IDoc Types" (v) via Edit -> Set release. You can also test using objects that have not yet been released.

Further Notes

If you use the IDoc interface, you need to make the following specifications when transferring your IDoc type to the IDoc interface:

  • IDoc type:     Name of your IDoc
  • Message type:    LIS000 (fixed value)
  • Partner:     the logical system that you have chosen (only in the case of ALE) from which the function module is to be called up

    ALE/RFC:     IDOC_INBOUND_ASYNCHRONOUS (Before release 4.0: INBOUND_IDOC_PROCESS)

    File:     EDI_DATA_INCOMING (You need to specify the file name and path)

Business Attributes
ASAP Roadmap ID 255   Create Interfaces 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 1   Critical 
Country-Dependency A   Valid for all countries 
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG OLIS_WE30 0 HLA0006426 Data Collection 
SIMG OLIS_WE30 1 O HLA0009766  
SIMG OLIS_WE30 2 O HLA0001547  
SIMG OLIS_WE30 3 O HLA0001552  
SIMG OLIS_WE30 4 O HLA0001841  
SIMG OLIS_WE30 5 O HLA0006666  
SIMG OLIS_WE30 6 O HLA0009760  
SIMG OLIS_WE30 7 O ALR0006032  
Maintenance Objects
Maintenance object type C   Customizing Object 
Assigned objects
Customizing Object Object Type Transaction Code Sub-object Do not Summarize Skip Subset Dialog Box Description for multiple selections
DWBDUMMY D - Dummy object WE30 LIS_IDOC LIS: Maintain IDoc 
History
Last changed by/on SAP  19981222 
SAP Release Created in