EDI for KMATs (Information on Creating Your Own) 

The following sections describe the structure of an intermediate document (IDoc) for configurable materials.

EDI (Electronic Data Interchange) enables you to electronically transfer documents, such as sales orders, quotations, purchase orders, from one R/3 System to another R/3 System.

 

For example, a purchase order is created for materials MAT_A and MAT_B in an R/3 System. You use EDI to transfer this purchase order to another R/3 System, such as the company from which the material is ordered. In the second R/3 System, the purchase order is converted to a sales order. This assumes that the master data in the source system is also maintained in the target system.

The application data is stored in an intermediate document (IDoc). Each IDoc is assigned to a specific IDoc type, which defines the structure and format of the electronically transferred data. If a document is to contain configurable objects, you must use IDoc type ORDERS02.

An IDoc comprises various segments, each of which carries specific information. For example, one segment can contain the header data of a document and another can contain the organizational units. Each segment has a segment type, which defines the type of data that a segment can contain.

For more general information on EDI processing, see the R/3 Library, under CA EDI and the IDoc Interface.

Documents with Configurable Materials:

Scope of Configuration:

  • Create order
  • Single-level/multi-level
    • Create order with reference to a quotation
  • Single-level/multi-level
    • Confirm order
  • Single-level/multi-level
    • Change order
  • Single-level/multi-level
    • Create inquiry
  • Single-level/multi-level
    • Purchase order
  • Single-Level
  • IDoc Procedure for a Configurable Material (Inbound IDoc):

    Once an IDoc is received, the data is transferred to the screen fields of the transaction in batch mode using Call Transaction calls.

    However, this procedure is not possible for the configuration data of an item, because the screen sequence for a configuration is very variable. For this reason, the configuration data is first put into memory. If it is then recognized that a document item in the sales order data is a configurable material, function modules for loading the data from memory and transferring it to the configurator are called.