Symptom

The system does not determine the organizational data for a transaction document (for example, telesales order) as expected (org data screen is partly or completely empty or the required organizational units were not found).

This can have various causes. You can use the following checklist to check the settings for determining organizational data.

In the Internet Sales scenario, the organizational data is always read from the product catalog variant. The following Customizing settings are therefore not valid for internet orders.

Check List

1. Organizational data model

Is the organizational data model maintained and are the organizational units provided with attributes?

Are the organizational units Sales organization, sales office, sales group, service organization and purchasing organization marked as such?

Make sure that the organizational units have been activated for the required scenario during maintenance of the organizational model (for example, the service organization for the Service scenario). On the Attribute tab page in the field Object is permitted for scenario, activate <INSERT GREEN BALL GLYPH>.

2. Attribution

Are the organizational model and attributes uniquely maintained?

When attributing organizational units overlapping may occur, for example, in the following cases:

If you evaluate attributes at a higher level of the organizational model (for example, the root), these attributes and the assigned values are passed on to all subordinate organizational units for the corresponding scenario, if they are not overwritten by another value. In some cases therefore several organizational units have the same value and attribution overlaps. In organizational data determination all of these organizational units are determined with the searched value.

You can avoid this type of overlapping by overwriting the subordinate organizational units that have inherited values with other values, or, by providing them with restricted values. To make restrictions, you can use the exclusion flag Excluded.

If you go over the value areas for attributes, there will be overlapping:

You assign the postal areas 1 –12000 to organizational unit 1, the areas 5000 to 25000 to organizational unit 2. Both organizational units are responsible for a sold-to party with the postal code 10 000.

If the system determines several organizational units for a document, a selection screen appears in which you can select the required organizational unit for the current document.

3. Organizational data profile

Has an organizational data profile been created and defined in these determination rules?

To check the determination rule, you can carry out a simulation in the determination rule maintenance (Simulation <INSERT SIMULATION GLYPH> symbol).

4. Organizational data profile assigned?

In order that organizational data is determined at header level for the transaction, the organizational data profile must be assigned to the corresponding business transaction type.

If the organizational data at item level should be copied from the header data, an empty organizational data profile (without determination rules) must be assigned to the corresponding item category.

If no organizational data profile is assigned, the organizational data set in the business transaction document is empty at header and/or item level and the screens for organizational data are not displayed.

It is not possible to carry out organizational data determination independently from the header data for the item level. This means that no organizational data profile can be assigned to an item category if it contains a determination rule.

5. Source data

Is the source data that is required for determining organization data available in the document?

If, for example, the determination rule states that the responsible sales organization should be determined using the postal code of the sold-to party but no address has been defined here, the system is not able to determine the sales organization.