Organizational Units

With ProConfiguration it is also possible to create and display organizational units of the material master record. For example a production data package which must be created for each plant. The documents defined therein must also be created for each plant.

Additionally to the organizational units additional objects such as routings or BOM can be displayed. These functions require the ProConfiguration LogisticExtension, which must be licensed separately.

Below a list with important customizing settings, which should be noted in relation to the organizational units of ProConfiguration LogisticExtension.

Customizing Setting	Tip

Customizing Setting	Tip
Object relevancies (I)	May require the creation of a suitable object relevance for the display of logistic objects in the data packages. Type Others without display of relevance... can be used. However type can be selected freely.
Object relevancies (II)	In case documents are linked to organizational units, this must be considered for setting Link other org.units (only DP with structure) if necessary.
Org.Unit data handler	If objects and data of organizational units shall be handled, the relevant settings are mandatory.
Object data handler	They are set-up automatically without definition. If own data handler shall be integrated or if the standard display shall be changed, the data must be maintained.
Customer-Exits	Eventually already existing customer exits must be modified, because objects and data packages can occur more than once in different organizational units.
Status Net	If necessary own status net must be created for plant and distribution line dependent status.
Objects	New logistic objects must also be recorded as objects in customizing. The respective SAP object must be recorded correctly (suitable for the relevant object handler).
Data packages	If data packages and their objects shall be assigned to an organizational unit the data package must have the type of the organizational unit (see Org.units data handler) and the key (or ) of the organizational unit. Corresponding these settings, the currently maintained material master record and the assignment of the org. unit to the configuration type (see configuration type*), the object data will be processed.
Processing scenarios	Processing scenarios can be activated by cross-plant, plant dependent, distribution line dependent material status or data packages.
Filter	With a filter the amount of objects to be displayed or handled can be restricted. Display filter are user specific, processing filters are activated by the processing scenario.
Object dependencies	It is possible to define different object dependencies between different material status types or documents.
Configuration types	Option Assignment Org/Status Net allows following settings º Definition, which organizational units shall be handled º Assignment of status net to organizational units. º Definition of display order of organizational units in the configuration display. Assignment of processing scenarios allows a filter, which will then be used in the object selection.
Display filter	With a display filter certain data packages, including their objects can be hidden for specific users, which can be collected in user groups. The definition also allows temporary deactivation of the entire or part of the filter by the user.