SRM organization plan...

[Former Member]

Hi All ,

can anyone give me the SRM org. plan documents ? ( i.e. how to create hole org plan including managers and users)

Thanks in advance,

Vidyadhar.

[former_member195032 · Accepted solution]

Hi Vidyadhar,

Please find details below

SRM Organizational Model (Changed)

Use

SAP SRM 5.0 now uses the functionally enhanced ERP-ORG organizational model (both in ERP and in mySAP SRM). This is another step toward harmonizing master data in an integrated ERP scenario. It also builds on existing integration with HR prior to SRM 5.0. The main difference is that internal business partners (that is, employees who up until now have only been generated by means of ALE inbound processing) are now also generated when the HR-ORG, which is in the same client, is created or changed. Another change is that external business partners are no longer entered in separate organizational units in the organizational model. (Prior to SAP SRM 5.0, every vendor and bidder in the organizational model was assigned to a separate organizational unit or position.) It should be noted, though, that master data has not yet been completely harmonized. The data models merely been harmonized to the extent that identical organizational units (O), positions (S), and users (US) are used. The central person (CP) that is used in HR is a one-to-one equivalent of the business partner (BP) in SRM, which represents an employee. You still have to maintain duplicate entries for thepurchasing organization and purchasing group from MM and for the FI-specific employee <-> cost center assignment. The FIcompany code is still represented as a company in SRM.

In 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. In other words, these vendors/bidders cannot be represented by an organizational unit in the organizational model. Following on from this, their employees cannot therefore staff any positions belonging to the former organizational units of their vendors. To ensure that existing data is migrated, you have to execute report BBP_XPRA_ORGEH_TO_VENDOR_GROUP manually. 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). VGs 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. Positions are deleted. After you upgrade to SRM 5.0 (and after all XPRAs and manually executed conversion programs have run), you have to run report BBP_XPRA_ORGEH_TO_VENDOR_GROUP in every client for every central organizational unit for vendors ("root organizational unit"). This applies both to SAP Enterprise Buyer (EBP) and toSAP Supplier Self-Services (SUS) systems.

Note:

Report BBP_XPRA_ORGEH_TO_VENDOR_GROUP copies only the standard attributes shipped by SAP for external business partners: BUK, CAT, CUR, EXT_ITS, ITS_DEST, TOG, VENDOR_ACS, and VENDOR_SYS If you use other attributes for external busin ess partners, you have to register them before you execute the report in view T77OMATTOT (table maintenance: transaction SM30) for the B2B Procurement scenario and the object type. Otherwise, these attributes will be ignored by the conversion report, and will be lost.

Affected transactions:

• SRM Organizational Model (Internal): PPOMA_BBP (Changed)

• The CP (corresponds to the CP in HR) has a one-to-one relationship with the business partner (employee).

• S and CP can have different names.

• Representation/Display

In SRM 5.0, and as was previously the case, a position (S) always comes after an organizational unit (O) in the structure. Now, however, the relevant business partner (BP), followed by the user (US), is no longer displayed beneath this in the structure. The business partner and user ID are displayed in the table row beside the central person (CP), which (in SRM) comes after every S in the structure (unlike in ERP, where a [natural] person always follows an S).

Large Detailed View: If you are in the structure view, you can now choose Goto to navigate to the Large Detailed Viewwhere, among other things, you can display an overview of all of the attributes the belong to an element in the structure. You can also choose Select Attributes to select individual attributes directly.

• An S can be distributed among several CPs, and vice versa (since CPs represent [natural] persons [P] in HR). This means that an S can be divided among several CPs, and a CP can be distributed among several S (multiple assignment) and vice versa. In this case, (default) attribute inheritance starts out from the organizational unit that has the higher percentage assignment. You can use the context menu to change the percentage assignments.

• SRM Organizational Model (Vendors): PPOMV_BBP (New)

• You no longer use PPOMA_BBP to enter external vendor organizational units and vendors. Instead they are represented in PPOMV_BBP , where vendor groups (VGs) are entered as organizational objects (including the vendors that belong to the groups).

• Manage User Data: BBPUM01 (New, previously BBPUSERMAINT)

• Representation/Display

New search function with search field Department: Allows you to draw up a list of all employees in a department.

Functions for deleting an employee: Delete (with Position) and Delete (Without Position): Without Positionmeans that structure element S in the organizational model is retained, and only the CP (including employees and users) is deleted. It makes sense to do this, for example, if the position in question is to be staffed by another employee at a later time. (If a position has multiple assignments, the position is also retained when you execute the Delete with Position option.)

New user interface design: Overview with Personal Data, User Account (including Role Assignment) and Position (including Department).

Position with integrated attribute maintenance (as an alternative to maintaining attributes in transaction PPOMA_BBP): If you change the default values for a position, this will affect all of the employees assigned to this position.

• Up to now, an employee, user, and position formed a unit. Now, from a technical point of view at least, these objects are regarded separately. This is because in HR, there can be several users per employee, and one employee for several positions (multiple assignment).

• If a new employee is created, a relevant position is also created (providing an existing one has not already been selected). You must also always specify a department for an employee/user.

• Employee/position changes department: If an employee moves to another department, you no longer necessarily have to use PPOMA_BBP to reassign the employee in the structure. If the assignment to the department changes, the fact that the employee changes means that the relevant position and attributes are also reassigned.

• Change Settings: BBPUM02 (New, previously BBPAT05)

• Mandatory Data tab page has been replaced by Personal Data

• Attributes can only be changed by means of Manage User Data transaction and on the Position tab page.

• Address Data tab page replaced by Position (in other words, it is the address data of the position that is changed)

• Manage User and Employee Data: USERS_GEN (Changed)

• Transaction USERS_GEN is used mainly for mass generating or deleting users (from SU01 or external files) as well as for running consistency checks, correcting errors, and making mass employee <-> user assignments.

• Changes: employee <-> user navigation

• Manage Business Partners: BBPMAININT

When you create/edit central data for external business partners, you no longer use a central org. unit for vendor, but rather a central org. object for vendor to create an assignment. This is because vendor groups (PPOMV_BBP) have been introduced.

• Invoicing Party tab page: Shows the relationship of a vendor to other vendors who can create invoices for the vendor or for whom the vendor can create invoices. Only this tab page and the Company Data and Contact Person Datatab pages are available for a vendor who is only ever an invoicing party (corresponds to a vendor in FI). See also: Different Invoicing Party (New).

For reasons of security (sending of passwords), users are not allowed to change the e-mail address for their user account themselves. By default, only the administrator has the authorization required to do this (authorization object S_USER_GRP). This applies to Manage User Data, Manager Business Partners, and Change Settings. (It is possible to change the e-mail address for a position.)

Regards,nishant

Please reward points if this helps

[Former Member · Accepted solution]

Hi Rajan,

Would you please sample of SRM Role model example any Role in your company used, and how it is created such as PFCG is used to create role, but I am reading one book for authorization for SRM, it says that application are control by object exammple

Purchasing Assistant is role in SRM, but what transaction we need to assign and what object we need to assign, what questions need to ask before create new roles in SRM.

Please send me this info as soon as possible

Thanks

Q

[Former Member]

Hi

Refer to the links as well.

<u>Create Org Plan</u>

<b>http://help.sap.com/saphelp_srm50/helpdata/en/c5/fa7d3cb7f58910e10000000a114084/frameset.htm</b>

<u>Create Links</u>

<b>http://help.sap.com/saphelp_srm50/helpdata/en/7f/0fea380bfe6161e10000000a11402f/frameset.htm</b>

<u>Consistency check for Org Plan</u>

<b>http://help.sap.com/saphelp_srm50/helpdata/en/1d/6ddd3bd7688370e10000000a114084/frameset.htm</b>

<u>Creating Users</u>

<b>http://help.sap.com/saphelp_srm50/helpdata/en/5d/55b158638111d2b408006094b92d37/frameset.htm</b>

Hope this will help.

Please reward suitable points, incase it suits your requirements.

Regards

- Atul

[Former Member]

Hi,

When you are asking docs pl. give yr mail ID or mention the same in yr Business card.

I have some good doc on org plan.

pl. send me a mail on

dinesh.powale@googlemail.com

and reward if helps

BR

Dinesh

[yann_bouillut]

Hi,

Please refer to the documentation :

http://help.sap.com/saphelp_srm50/helpdata/en/37/4b4b3c99c53c33e10000000a11405a/frameset.htm

-> Create organization plan

Kind regards,

Yann