Logistic Integration

If enabled, ProConfiguration also supports plant revisions. For a description, see Logistic Integration in the ProConfiguration User's Guide.

The following Customizing views control the behaviour of Logistics Integration:

View	Description

View	Description
Document definition group Documents to be linked	If object linking is activated in the control parameters of a logistic object (OBJECT_LINK_HANDLING), the object types of the documents to be linked must be entered here in a document definition group and this document definition group must also be entered in the control parameter using parameter DOCUMENT_DEFINITION. Besides the object type, further restrictions are possible. Linking to the document objects is done without authorization check. I.e. even if the user has no authorization to maintain a document type, it can be linked to the corresponding logistic object.
Logistic objects Selection constraints Control parameter	Identifier of a logistics integration definition for a logistics object according to selection conditions. The basic type of the logistic object is defined by the logistic object type. For each such type, several entries with different selection conditions can be recorded by means of the sequence number. See also online documentation of the sequence number. The behavior of the logistics integration is set via the control parameters.
Fallback language	If language-dependent document objects are linked, the language is used according to the logistical object (plant language for production order, vendor language for purchasing documents). For missing languages, escape languages can be defined here.
Own / alternative handling classes	Allows the use of custom handling classes, which are defined as derivatives of the base class /PCH/CLA_PRM_LOGINT_HANDLER or one of the object-specific classes derived from it. If one of the default keys is used as the key / object type, this class is used instead of the default object-specific class, otherwise a new type is defined.