Show TOC Entering content frame

Function documentation Creating the Organizational Plan Locate the document in its SAP Library structure

Use

The system administrator must create the organizational plan (and organizational model) so that

·        The self-service scenario for creating user master records can be used in Supplier Relationship Management (SRM)

·        SAP Business Workflow can determine which users are responsible for approving documents

·        The purchasing organizations and purchasing groups responsible for the relevant documents can be determined

The following graphic shows an example of an organizational plan:

This graphic is explained in the accompanying text

Caution

From SRM 5.0, external business partners (vendors/bidders and their employees) are no longer depicted in the organizational model of the company that runs SRM. They can no longer be represented by an organizational unit in the organizational model.
To ensure that inventory data migration is carried out correctly, you have to run the report BBP_XPRA_ORGEH_TO_VENDOR_GROUP (see Structure linkReports) manually in each client for each central organizational unit for vendors/bidders).
This report deletes all organizational units and positions of the vendor/bidder and - on the basis of their attributes - groups these together into new organizational objects called vendor groups (VGs).
Vendor groups (VG) are used for grouping; it is no longer obligatory to have one VG per vendor, as was previously the case for organizational units. If several vendors (who previously were assigned to an organizational unit) have identical attributes, they are now assigned directly to a common VG.

 

Integration

When an employee requests a user master record (US) for SRM, the system creates a position in the organizational unit that the employee’s manager belongs to. It assigns the user master record to that position (S).

If you use the approval procedure for user master records, the user who is assigned as the manager of this organizational unit must give his or her approval. The same applies to approving shopping carts. If there is more than one manager assigned to an organizational unit, both managers receive a work item. The first manager to process the work item will automatically delete the second manager's work item.

In the procurement organizational unit, the departments and the product categories for which the organizational unit is responsible are defined. On the basis of this information, the procurement organizational units are automatically assigned a shopping cart. This applies both to shopping carts processed locally and those transferred to a backend system for processing. See Modeling the Purchasing Organization in the Organizational Plan.

 

Prerequisites

Before the first user for SRM is created, manager approval must have been temporarily deactivated.

Menu path in the Implementation Guide (IMG): Supplier Relationship Management ® SRM Server ® Master Data ® Create Users ® Set Approval Indicator

 

Activities

The system administrator must do the following:

·        Create a root organizational unit. This is the starting point for the organizational plan. The following information about the root organizational unit is entered here:

¡        Name and validity period

¡        Address data

We recommend that the system administrator also:

·        Defines the basic organizational structure of the company preferably at departmental level.

Note

If two levels of approval are required, at least two levels of the organizational structure must have been defined.

·        Defines the values for the most important user attributes (see Maintaining User Attributes)

If the system administrator defines the purchasing department in the organizational plan, the organizational attributes purchasing organization and purchasing group should be defined.

Caution

If you want to display the organizational plan, always use transaction PPOSA_BBP. This will prevent any locking problems occurring.

Creating the Root Node of the Organizational Plan

Menu path in the Implementation Guide (IMG): Supplier Relationship Management ® SRM Server ® Cross-Application Basic Settings ® Organizational Management ® Create Organizational Plan (or transaction PPOCA_BBP)

Changing the Organizational Plan

Menu path in the Implementation Guide (IMG): Supplier Relationship Management ® SRM Server ® Cross-Application Basic Settings ® Organizational Management ® Change Organizational Plan (or transaction PPOMA_BBP)

Note

The system administrator starts to create the organizational plan using the Customizing activity Create Organizational Plan. After leaving this activity, the administrator should make any changes to the organizational plan using the activity Change Organizational Plan.

·        Creates a first user for the root organizational unit using the Web transaction Manage Users. Create this user as a manager, that is a user with the role SAP_EC_BBP_MANAGER.

For more information, see Structure linkManaging Internal Users.

 

See also:

·        For more information about how to create and maintain the organizational plan, see Organizational Management in the CRM System in the CRM documentation.

·        For information about performance issues relating to the organizational plan, see SAP Notes 110909 and 354787.

Leaving content frame