Mandatory segment: NO

The document item segment E1J3P01 starts the transfer of data per item. Below the segment you find further item-related segments with detailed information for the respective item. A prerequisite for correctly processing the segment is that the external item number in field POSEX is uniquely filled. If the field remains initial, error message /AFS/IDOC 018 is displayed. In view of automatic order changes with the message type ORDCHG you must note that the external item number is uniquely transferred to the created document. After the creation of the order, it is the unique identification and reference criterion of an item.

For the processing of bills of materials in incoming orders, there are some special features. There are basically two ways of BOM processing:

• In the IDoc, only the header material of a BOM is sent.
• Both header and component materials are sent.

In both cases the BOM is exploded in the sales document, according to the settings in the IMG. Make sure when using item categories that the correct item categories are transferred for both header and component items. An automatic item category determination only takes place if neither field PSTYP nor field PSTYV are filled in segment E1J3P01. The sales document contains more items after the transfer of IDoc data than were sent in the IDoc. This has to do with the fact that during the BOM explosion in individual components, new items are generated.

If both header and item materials are sent as mentioned in the second case, the relation between the two can be created using field UEPOS in segment E1J3P01. Here, the value of the superior item always refers to the external item number (POSEX) of the header material. We strongly recommend that you send related components and their respective header material as groups in the sequence of the individual E1J3P01 segments.

It is possible to send a material as an individual item without reference to a header material, even if it belongs to a BOM as component. In this case you must not fill field UEPOS.

There can generally be one of the following situations during the processing of the item segments: A material of the following types is sent:

• Standard (= non-AFS) Material
• AFS material with dimensions
• AFS material without dimensions (without a grid)

In the first case a 1:1 ratio exists between the sent E1J3P01 segment and the created document item. Normally the item contains a delivery schedule line.

In the second case an n:1 relation exists between the sent E1J3P01 segment and the created document item. The ordered dimensions are first grouped by material numbers and combined to items with the same material number. Different dimensions of the same material (for the same recipient) are combined to one item. The individual dimension is reflected in a schedule line on the document. All the relevant data is "copied" from the item header to the schedule line for the identification of the individual purchase order items. That means that the external item number POSEX is not connected to the document item itself, but rather to the schedule line at dimension level.

In the third case (no grid material) the processing is similar to the standard material without combining at item level.

The grouping of AFS materials and their dimensions is controlled by the following sort criteria:

• Material number
• Goods recipient
• Plant
• MSO Mix key
• Requested delivery date
• Cancellation date
• Department
• Item Category

If you change one of the criteria, a new document item is created.

The values of field VPREI and NETWR are interpreted as customer-expected price or item value. The entries are assigned to the condition types EDI1/EDI2 or JED1/JED2. The assignment to the AFS-specific conditions JED1 and JED2 only takes place, if the condition type is flagged as dimension-relevant in the IMG.

When transferring the values, remember that the transferred values are checked in the sales document against the amounts determined by pricing. If there are differences, an incompletion log for the document is created according to the settings in the IMG. You can not overwrite the values that are determined by the pricing with the entries of the IDoc. The transfer of conditions both at header and item level is not supported by the inbound processing.