Organization Structure Extended Classic

[Former Member]

Hi,

Can you please help me with the following Questions

The below link says that one can use local porg and Local Pgrp in Extended classic. In this case when a PO is replicated to backend, system determined the back end porg for replicated PO based on Location or plant

http://help.sap.com/saphelp_srm30/helpdata/en/0a/baf73a93ad9179e10000000a114084/content.htm

a) My question is a plant can have several Purchasing Organizations assigned to it in back end ? In this case which one of them will be determined..

b) Also, if an SRM system is connected to multiple ECC. And similar categories are procured in all the ECC systems. We will have duplicate product categories after replication pointing to their individual ecc systems.

Now if we are to do Shopping carts using catalogues and since each catalogue item can have only one product category pointing to one of the systems.; this will result in duplication of catalogue items with each item for each system even though physically the item is same.

To avoid the above, If we decide to use local product categories and some how map them to one back end product category based on company code during creation of PO, it would help us simplify the process. Would it be Possible to do?

The purpose of the above question is. We want to use extended classic with plants and company codes mapped to back ends.

Entire Purchasing structure including Purchasing Organizations and purchasing groups will made local to SRM. The product categories are alos local product categories in SRM.

When i make the Shopping cart for example which is complete,

1. There should be some way to determine back end system. We are planning to use BBP_DETERMINE_LOGSYS. In this we will determine back end system using plant

2. Then the next question is what willl be the Purchasing org in replicated PO, Your clarification to "a" above will answer this question

3. the next thing is what will be the purchasing group in the replicated PO. We are planning to use BBP_PGRP_FIND to do this

4. The next thing is what will be the Product category in replicated to back end. Your clarification to "b" willl answer the question.

c. Finally because of this design, will we have issues with contracts etc......

Edited by: kiransap25 on Aug 3, 2010 8:35 PM

[Former Member]

Hi Kiran,

Regarding your 1st question:

a) As it can happen in backend for plant associated with sevarl P orgs, but in SRM it is one to one and I think you can have a custome table in EBP for that one to one relationship through which you can decide the backend Pur Org in backend based on the plant.

b) Not very clear with the question, But the Product categories are based on the Backend and so is the catalogs which you assigned as in the users attributes which is get validated with the co code and backend system (based on the user attribute).

IS