cancel
Showing results for 
Search instead for 
Did you mean: 

Extended Classic Scenario PPOMA_Purchasing Org and Group

Former Member
0 Kudos

Hi gurus,

We are working with SRM 5.5 and we are having problems with the assignments for the Purchasing organization and Purchasing groups in the PPOMA.

In the documentation it says we should have one box for the R3 Purchasing Organization (flagged and referred to the backend POrg) and one for the Local Purchasing Organization (flagged but NOT referred to the backend POrg). The same for the Purchasing Groups, the one under R3 POrg will be flagged and referred to the PGroup in R3 and the one under the Local POrg will have the flag but it will not be referred to the backend PGroup.

Afterwards, in the attributes for the Local POrg and Local PGroup, with the attributes PURCH_ORGX and PURCH_GRPX the local and the R3 POrg and PGroup will be assigned each other.

The purchasers will be located in the Local PGroup. The R3 POrg and PGroup will never have users assigned.

The problem is that all the workflow is only working if the "Local" POrg and Group have the backend purchasing organization and purch group assigned in the Function Tab. This means that the 2 boxes for R3 are no longer necessary. In the documentation it says that this version of SRM needs both boxes for the POrgs and the 2 boxes for the PGroups. We have flagged the Extended Classic Scenario.

Any help on this? It's because of the version?

Many thanks and regards,

I will give Points!

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

Hi Muthuraman,

If we only use backend POrg and PGroup we will be using Classic Scenario instead of Extended Classic Scenario.

We know how to define the attributes. What we do not understand is why it's not working if we create 2 boxes for the POrg (local and backend) and 2 boxes for the PGroup (local and backend). The purchasers will be located under the Local Purchasing group. If we define the POrg and PGroup as it is said in the Cookbook it is not working.

Why?

Many thanks and regards,

Ana

I will give points

Former Member
0 Kudos

Hi Muthuraman,

The problem is that, if we only flag the POrg and PGroup without the reference to the backend, the completion WF does not trigger the purchasers referred to the local PGroup. They are only determined if the POrg and Pgroup have the reference to the backend.

In the last version, the attributes PURCH_ORGX and PURCH_GRPX for the local units were filled with the ID in the PPOMA for the backend units POrg and PGroup (O 50000012) to relate them.

In this version, we can only select the backend POrg and PGroup values (OCV1 and 010)

Any help on this? If we only use backend POrg and PGroup we will be using Classic Scenario instead of Extended Classic Scenario.

Many thanks and regards,

Ana

I will give points

former_member183819
Active Contributor
0 Kudos

Hi Ana

PURCH_GRP Purchasing group Number of an organizational unit that is indicated as local purchasing group in the organizational plan.

This attribute is simulated. You define an organizational unit as company on the Function tab.

PURCH_GRPX R/3 purchasing group Number of an organizational unit that is indicated as the R/3 purchasing group in the organizational plan. The value contains the ID and the associated backend system of a backend purchasing group.

This attribute is simulated. You define the ID and the associated system on the Function tab.

-

PURCH_ORG Purchasing organization Number of an organizational unit that is indicated as local purchasing organization in the organizational plan.

This attribute is simulated. You define an organizational unit as purchasing organization on the Function tab.

PURCH_ORGX R/3 purchasing organization Number of an organizational unit that is indicated as the R/3 purchasing organization in the organizational plan.

This attribute is simulated. You define the ID and the associated system on the Function tab.

can you elaborate more?

in ECS also we can map the backend purchase organisation/ purchase group for purchasing activity.

there might be a resposibilty tab for the backend purchase group might be mapped the responsible purchaser list (dept).plz check it up

regards

Muthu

regards

Muthu

former_member183819
Active Contributor
0 Kudos

Hi

- please refer this thread for more clarification

if you flag and type porg /pgruop and backend logical system.

if you just flag it is called local purchase organisation.

http://help.sap.com/saphelp_srm30/helpdata/en/b2/afe438b572b407e10000000a114084/content.htm

Attributes PURCH_ORGX and PURCH_GRPX are no longer used.

regards

Muthu