Show TOC Entering content frame

Function documentation Modeling the Purchasing Organization in the Organizational Plan Locate the document in its SAP Library structure

Use

In order that worklists for processing purchase orders can be created and to enable reporting, you must have defined your purchasing organization.

Integration

Each purchasing organization and purchasing group in a company is defined as a procurement organizational unit.

Each purchasing organization or group must be a node (organizational unit).

In the case of a local purchasing organization, users (professional purchasers) are assigned to the procurement organizational units. If the purchasing organization is located in an SAP backend system, these organizational units are only used to forward the necessary values from the backend system. In such a case, no users are linked with the organizational units.

Activities

Modeling the Purchasing Organization in the Organizational Plan

You do this as described below in the Customizing for the organizational plan. (Menu path in the Implementation Guide (IMG):
Supplier Relationship Management
® SRM Server ® Cross-Application Basic Settings ®  Organizational Management ® Create/Change Organizational Plan.)

·         You define the relevant organizational units.

·         You define the purchasing organizations and purchasing groups using the Type tab.

·         In the case of local purchasing organizations and purchasing groups, you leave the additional fields for organization and group in the backend system empty. However, if a purchasing organization or group corresponds to an organization or group in the backend system, you can define this using the input help.

Note

Attributes PURCH_ORGX and PURCH_GRPX are no longer used.

·         Save your entries.

Note

It is no longer necessary to activate the function of an organizational unit.

 

Defining the Purchasing Group Responsible

You can define organizational and product responsibility on the Responsibility tab.

Note

Attributes RESP_PGRP and RESP_WGR are no longer used.

·         You define product responsibility in the upper area of the tab page. You can enter individual product categories or value ranges for product categories. You can use wildcards (*) to do this. You can select the source system from which the product category is replicated from the list.

·         Specifying product responsibility is optional. If your procurement department is organized by product category, you should assign all your product categories to purchasing groups using this attribute. If you fail to do so, all the orders relating to unassigned product categories will be assigned by the system to the same purchasing group. This only makes sense if you intend a particular purchasing group to assume the role of dispatcher.

·         In the lower area of the tab page, select organizational responsibility. You can use the input help to select the departments or groups for which the purchasing group is responsible. The organizational responsibility has to be defined for purchasing groups.

The following graphic shows an example of how product and organizational responsibility might be defined in the organizational plan. In this example, purchasing groups 1 and 2 are both responsible for purchases made by the same departments (represented as organizational units 50002974 and 50002975). While purchasing group 1 processes all shopping carts containing items from product category 00105, purchasing group 2 processes all shopping carts containing items from product category 001.

This graphic is explained in the accompanying text

 

Assigning Vendors to Purchasing Groups

Vendors can no longer be assigned to purchasing organizations in the buying company’s organization model by using transaction PPOMA_BBP. Instead, you have to use transaction PPOMV_BBP to group vendors with identical attributes in an organizational object, the so-called vendor group.
For further information, see Creating the Organizational Plan.

 

Enhancing the Organizational Plan

To make the connection between purchasing organizations and purchasing groups more flexible, you can lessen the restrictions of the organizational model.

Employees that are assigned to the line organization of the HR organizational model and work as purchasers in an SRM purchasing organization can be assigned to the new relationship type Is Purchaser of...

For more information, see the section Creating the Organizational Plan of the Business Scenario Configuration Guide Self-Service Procurement. You can find this guide in SAP Service Marketplace at service.sap.com/ibc-srm.

 

 

Leaving content frame