Skip to Content

Organizational Data Determination(I took these data from SPRO Documentation)

In this section you can make the settings for automatically determining organizational units in transaction documents. The organizational data is determined in a business transaction independently of the sales organization, distribution channel, and division (sales area) attributes that are stored in the business partner master.

Note the following:

  • The organizational data for transaction documents is determined at header level.
  • If the system cannot find organizational data at header level, the fields for organizational units are left blank in the transaction document. You can then complete these manually.

There are several methods for defining rules. In CRM we recommend you use the rule categories Responsibilities and Organizational Model.

We can create two types of rules through wizard

  1. Determination Rule from Organization Model( it will check Org unit attribute values)
  2. Determination Rule from the Responsibility Type( It will check your Maintained Conditions )

Create Determination Rule from Organizational Model

ODD01.JPG

This wizard helps you to create a determination rule of the organizational modeltype.

Make sure that the organizational units and the attributes for the sales and service scenarios are created.

The determination rule is created as follows:

  1. Enter a name and an identifier for the rule.
  2. Choose a scenario. You can choose sales or service as a scenario.
  3. Select the attribute that you would like to use for the rule. The attributes from the previous scenario are proposed.
  4. Enter a detailed description for the rule you have created.

To test the determination rule, you can call up the simulation in the standard activity Define determination rule.

To transport the determination rule into other systems, you must include it in a transport request at the end of the wizard.

 

ODD02.JPG

ODD02.JPG

ODD02.JPG

ODD02.JPG

ODD02.JPG


You can find the newly create rule number on the Status bar as a information message.

ODD02.JPG

If you want to change any thing in this generated rule, go to  TCode PFAC. Or  Follow below SPRO IMG path.

IMG->Customer Relationship Management->Master Data->Organizational Management->Organizational Data Determination->Change Rules and Profiles->Maintain Determination Rules

ODD02.JPG

ODD02.JPG

ODD02.JPG

Here you can see what you maintained at the time of Rule creation wizard. And we can test this rule by simulation.

ODD02.JPG
In the above result list, every org unit has maintained region attribute region = 10.

To check this, goto Tcode PPOSA_CRM or Follow IMG Path.

IMG->Customer Relationship Management->Master Data->Organizational Management-> Organizational Model-> Change Organizational Model

ODD02.JPG

Creating a Determination Rule with Rule Category Responsibilities:

IMG->Customer Relationship Management->Master Data->Organizational Management->Organizational Data Determination->Change Rules and Profiles->Maintain Determination Rules

  1. Choose Create. You reach the screen Rule: Maintain.
  2. On the tab page Rule definition you specify your determination rule and assign an identifier.
  3. Choose the rule category Responsibilities.
  4. Choose the tab page Container.
  5. Choose Add container element. You reach the dialog box Create element.
  6. If you want to use Data Dictionary fields, choose Yes. You will reach the dialog box Create with Data Dictionary Field entries.
  7. Enter the table from which you wish to select fields and choose Continue. The table appears.
  8. Choose the fields that should appear in the container definition and confirm with Continue. In the dialog box Create the system asks you to create texts for these container elements.
  9. Create the texts and choose Continue.
  10. On the Container tab page double-click on the container element. You reach the dialog box Element <…..>. If you select the field obligatory, an error occurs in workflow if no data flow is defined for this element. If you select the field multiple-lines, you can enter several values for an individual container element. You can select both fields at the same time. Then choose Continue.
  11. Save the determination rule. The system automatically assigns a number to the rule.

Otherwise you can create rule using wizard also.

Create Determination Rule of Responsibilities Type through wizard

This wizard helps you to create a determination rule of the responsibilities type.

Make sure that the organizational units and the attributes required for the sales and service scenarios have been created.

To create a determination rule, proceed as follows:

  1. Enter a name and an identifier for the rule.
  2. Choose a scenario. You can choose Sales or Service as a scenario.
  3. Choose the attribute that you would like to use for a rule. The attributes from the previous scenario are automatically proposed.
  4. Enter a name and an identifier for the rule.
    The responsibility is the evaluated container for the determination rule.
  5. Enter values for the attribute that you previously selected.
  6. Assign the required organizational units to the responsibility.
  7. Enter a detailed description for the rule you created.

To test the determination rule, you can call up the simulation in the standard rule Define Determination Rule .

In order that the determination rule can be transported into other systems, you must include it in a transport request at the end of the wizard.

Note: Here I am not adding screen Shots, because we already discussed on this wizard.

After Rule creation we can maintain some more again determination conditions  to the same rule.

ODD02.JPG

Here No FM will be there, and one extra tab added named as Responsibilities.

ODD02.JPG

  These are conditions, witch will check before finding responsible org unit determination

.ODD02.JPG

Thanks & Regards

Vijay

To report this post you need to login first.

2 Comments

You must be Logged on to comment or reply to a post.

Leave a Reply