Object Data Handler

The Object Data Handlers perform the following tasks for the respective objects of ProConfiguration:

Determining the relevant objects for a configuration.
Reading and preparing the data for display in the configuration (but not the display itself).
Preparing and executing object-related functions in the context menu in the old ProConfiguration Workbench.
Double-click navigation of objects.
Handling of objects to be linked (multiple uses).
Data handling (create, change, version, ...)

For a corresponding object to be visible in the configuration, a corresponding object must always be created and assigned to a data package. It should be noted that objects for data handlers, which require a specific organizational unit, can also only ever be used in corresponding data packages.

See also the online documentation of the Parameter field when assigning objects to a data package, which controls the selection of objects to be displayed.

Object type	Description	Tip

Object type	Description	Tip
DRAW	Document info record	Document info records can be used in all data packages, i.e. with or without organizational units.
MARC	Material plant view	Can only be used in data packages that are assigned to an organizational unit type with SAP object MARC.
MVKE	Material distribution view	Can only be used in data packages that are assigned to an organizational unit type with SAP object MVKE.
MKAL	Production version	Can only be used in data packages that are assigned to an organizational unit type with SAP object MARC. All production versions valid in the corresponding validity area are displayed for the corresponding MRP view. If plans (PLKO) and/or material BOMs (MAST) are also assigned to the data package and these are linked accordingly in the production version, this data is displayed subordinate to the MKAL record.
PLKO	Rotings	Can only be used in data packages that are assigned to an organizational unit type with SAP object MARC. If production versions (MKAL) are also displayed in the data package and a plan is assigned to one of these, it is always displayed below the corresponding production version.
MAST	Bill of Material	Can be done with or without reference to organizational unit plant. Cross-plant material BOMs are always output only for data packages without an organizational unit. For plant-dependent ones, the following rule is applied: If any data package with reference to plants is defined in the configuration, then plant-dependent BOMs are also only output in data packages for the corresponding plant. If no data package with reference to a plant is defined, then plant-dependent BOMs are also output in data packages without an organizational unit. Without further restrictions, all plant BOMs are output, see below. If production versions (MKAL) are also displayed in the data package and if a material BOM is assigned to one of these, it is always displayed below the corresponding production version.
QINF	Quality info record	Can only be used in data packages that are assigned to an organizational unit type with SAP object MARC. Any documents linked to the quality info record are also displayed. The display is according to the following rules: Quality info record without revision Display in all revisions according to validity from quality info record (Valid from and Valid to) Quality info record with revision If the quality info record creation date is further in the past than the valid-from date of the corresponding material revision, the valid-from date is taken from the material revision. If the quality info record creation date is further in the future than the valid-from date from the material revision, then the creation date from the quality info record is taken as the valid-from date. Note: Valid-from date of the quality info record = creation date.
CRHD	Work place	Represents the task lists below planned operations. Can only be used in data packages that are assigned to an organizational unit type with SAP object MARC and in which planned items are displayed. Note: Valid-from date of the work center = date of the last change.
EORD_HEAD	Order bookhead	Can only be used in data packages that are assigned to an organizational unit type with SAP object MARC. Represents a header entry for the source list for the plant. Is only displayed if data is maintained in the time area in the purchase order book for the plant. Note: Valid-from date of the source list header = smallest valid-from date. Date of an entry in the purchase order book in the corresponding time period.
LFM1	Supplier (purchasing view)	Can only be used in data packages that are assigned to an organizational unit type with SAP object MARC. Any documents linked to the supplier are also shown. The supplier can be displayed in two places in the structure: Below the purchase order book header record, if entry exists for the vendor in the source list. Directly below the data package, if a purchasing info record or a purchasing contract item exists for the material that is not referenced in the purchase order book.
EKPO	Purchasing contract position	Can only be used in data packages that are assigned to an organizational unit type with SAP object MARC. Any documents linked to the purchasing contract item are also shown. The purchase contract item can be displayed in two places in the structure: Below the vendor underneath the purchase order book header record, provided the purchase contract item is maintained in the corresponding purchase order book in the corresponding time period. Below the supplier, directly below the data package, if the purchase contract item is not maintained in the corresponding purchase order book in the corresponding period. Note: Valid-from date of the purchase contract item = Valid-from of the contract, if greater, the Valid-from of the corresponding entry in the purchase order book.
EINE	Purchasing info record (purchasing view)	Can only be used in data packages that are assigned to an organizational unit type with SAP object MARC. The purchasing info record can be displayed in two places in the structure: Below the vendor below purchase order book header record, provided the vendor is maintained without a purchase contract item in the corresponding purchase order book in the corresponding time period. Below the vendor directly below the data package, if the vendor is not maintained in the corresponding purchase order book in the corresponding period or if the vendor is maintained in the purchase order book with direct reference to a purchase contract item. Note: Valid-from date of the purchasing info record = creation date.