POI IDocs 

 

This table provides an overview of the type of data that can be transferred from R/3 to external systems for optimization and the corresponding message types.

From

R/3

To

External Optimization System

Data

Message Type

Production/Process orders

LOIPRO

Planned orders

LOIPLO

Stock/requirements lists

LOISTD

Run schedule header

LOIRSH

Materials

MATMAS

Bills of material

LOIBOM

Work centers

LOIWCS

Resource network

LOIRNH

Work center hierarchy

LOIRNH

Routings

LOIROU

Calendar

LOICAL

Object classification

CLFMAS

Number of transferred IDocs

LOINUM

Transition matrix

LOITMX

Product group

LOIPGR

Warehouse stock

LOIMSO

Production campaigns

LPIPCM

 

In this document contains tables illustrating each of the POI IDocs and their segments. Each table represents an IDoc segment and contains a list of fields, a short description of each field, and the field lengths.

The data types listed here correspond to the data types each segment has in the R/3 System.

 

In POI, data is transmitted in CHAR format. SAP offers conversion options (for example, to ISO codes) with adjustment possibilities for input fields in CHAR format. The following data types are among those that are converted:

Because of these conversion factors and depending on the data type, there are differences in the internal and external field lengths.

To convert units of measurement, in Customizing, follow Global Settings ® Check units of measurement.

In this customizing step you can enter a corresponding ISO unit for every SAP one. If you don‘t enter an ISO unit, the SAP code is transferred in the IDoc. Important: Only the unit itself is converted, not the corresponding quantities, amounts, times, etc. There must be a 1:1 relationship between the ISO and SAP codes if you enter an ISO unit.

During the POI upload the ISO unit is automatically converted. Transferring SAP units can cause error messages in the POI upload log. If you do transfer unconverted SAP units, use the prefix SAP_CODE (upper case characters) in front of your unit. For example, use SAP_CODEKG for SAP unit KG.

For further information on conversion codes, see Cross Applications ® ALE ® Consultant’s Handbook or Programming in the R/3 Library.

For specific information on the internal and external lengths of IDocs, follow the path path Tools ® Business Framework ® ALE ® Development. In the ALE development screen, follow IDoc ® IDoc basis ® Documentation ® IDoc types

 

In the documentation as well as in the R/3 dictionary, all segments have the prefix E1 (for example, E1MAPL). As soon as the segments are transmitted via ALE, the prefix changes to E2. For instance, if you send segment E1MAPL in an IDoc to an external system, it will arrive labelled E2MAPL.

The different versions of a segment are identified by the number following the segment name (for example, E1CRHOL001). New versions are created whenever fields are added to a segment.