Ansicht
Dokumentation

CRMC_ORGMAN_PRF - Maintain Organizational Data Profile

General Data in Customer Master   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.

Automatic creation of organizational data in business transactions is controlled using the organizational data profile. This means that the system determines the responsible organizational unit from the data in the business transaction, and enters the values for attributes in the document.

A determination rule is defined in the organizational data profile for this purpose. This specifies how the system determines organizational data. It also allows you to specify which organizational data is required for a transaction type or item category.

Organizational data profiles are scenario-specific. A profile is valid either for the sales scenario, the service scenario, or for both. If a profile is valid for both scenarios, the system tries to determine organizational data for both scenarios (sales and service) in the business transaction.

The organizational data profile is assigned to a transaction type or to an item category. The determination rule applies to this transaction type or item category.

You must have defined a determination rule. SAP delivers typical determination rules. You can find further information under Maintain Determination Rules.

You can use one of the wizards for creating your own determination rules. These can be found under Wizards for Organizational Data Determination.

To determine organizational data with the rule type Organizational Model, you must have defined attributes in the model for the organizational plan.

The following organizational data profiles are available in the standard system for the Sales and Service scenarios:

• for the transaction header: 000000000001

Sales: organizational model determination rule: 10000177, determination based on country/region

• for item: 000000000002

Does not contain determination rule. Organizational data is copied from the header to the item.

The following organizational data profiles have been created in the standard system for the Enterprise Buyer (EBP) scenario:

• Profile 000000000003

This profile is required for the purchasing contract. The purchasing organization is mandatory.

• Profile 000000000004

This profile is used for the purchase scheduling agreement. The purchasing organization and purchasing group are mandatory.

The following organizational data profile is created in the standard system for the Sales scenario (not service).

• for transaction header: Profile 000000000005

Determination rule organizational model: 10000144 with function module CRM_ORGMAN_ORGOBJECTS_FIND_4, determination based on sales areas maintained in the business partner master.

The following organizational data profile is maintained in the standard system for the Service scenario.

• for transaction header: Profile 000000000008

Determination rule organizational model 10000276,

Determination of service organization based on the postal code

You should not change the delivered organizational data profile. If you need to, you can create it again.

To create a new organizational data profile, you can use the wizard for organizational data profiles. This can be found under Wizard for Organizational Data Determination. The organizational data profiles created with this wizard can be processed further in this activity.

To create a new organizational data profile in this activity, proceed as follows:

1. Choose a profile from the organizational data profiles that best suits your requirements and copy it or create a new profile using New entries.
2. In the Description field, enter a new description for the profile.
3. Choose Detail.
4. Enter a key for the profile and select a scenario.

If you want to use the profile for both Sales and Service, you must create it separately for each scenario. In the Profilefield for both scenarios, enter the same key and select the relevant scenario.

1. Assign one of the available determination rules (standard roles) to the organizational data profile.

If you define a determination rule (standard role) in the field Organizational Model Determ. Rule (Organizational Model Determination Rule), the system determines the org data set by evaluating the org data attributes. In this case, you must have assigned attributes to the organizational units in the organizational data model and defined values in them.

If you define a determination rule (standard role) in the field Responsibilities Determ. Rule (Responsibilities Determination Rule), the system determines using the role type responsibility, this means it establishes in the standard role the values in a specific attribute for which an organizational unit is responsible.

If you define a determination rule in both fields, the system displays the overlap from the resulting quantities, determined from the fields Organizational Model Determ. Rule and Responsibilities Determ. Rule. This option is particularly good if the resulting quantity from one determination rule would be too big.

If, however, the system determines several possible organizational units, a message is displayed in the document. You can then select the required organizational unit.

1. If required, determine which organizational data must occur in the corresponding transaction type. If organizational data that is mandatory in this area has not been determined or has been entered manually, an error message is issued.

Finally, assign the organizational data profile to a business transaction type or a business transaction item category.

CPI1466 during Backup   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.

Length: 6819 Date: 20240523 Time: 155539     sap01-206 ( 105 ms )