Cross purchase organization in multiback-end SRM system

[Former Member]

Hi Gurus,

I would like to make a few questions relating to my scenario.

The application map is as follows:

-To-Be SAP ECC system called "AAA" (in this system we will implement the to-be model only for 3 companies, this model will be used as template for the other roll-out)

- As-Is SAP ECC system called "BBB" (transitional system that will be migrate in “AAA” in a subsequent phase of the project - there shall be no changes to the customizing of this system)

- To-Be SAP SRM system (this system should be linked to both SAP ECC “AAA” & “BBB” – multi backend system)

In this scenario, is possible to customize a single cross purchasing organization code able to work simultaneously on different companies present in different SAP back-end?

Example: PR 10000345 from SAP “AAA” for the company 1 and 10000888 from SAP “BBB” for the company 2 both converted in different Purchase Order but with the same purchasing organization code in SAP SRM.

Also, in terms of customizing, the "Product Category", the " Purchase Group", the "Purchase Organizations" and all data in the PO must be replicated in SRM system customization? The customizing of the SRM system must be the sum of the “AAA” and “BBB” system?

Thanks in advance,

Marco

[laurent_burtaire]

Hello Marco,

see my remarks below.

Marco Cariello wrote:

(...)
- As-Is SAP ECC system called "BBB" (transitional system that will be migrate in “AAA” in a subsequent phase of the project - there shall be no changes to the customizing of this system)
(...)

Don't understand what you meen by "transitional system that will be migrate in “AAA” in a subsequent phase of the project".

Please give clarifications.

Marco Cariello wrote:

(...) 
In this scenario, is possible to customize a single cross purchasing organization code able to work simultaneously on different companies present in different SAP back-end?
(...)

No, this is not SAP SRM standard.

You will have to use BBP_PGRP_FIND BAdI to assign correct backend system to Purchasing Organization.

Marco Cariello wrote: 
(...)
Also, in terms of customizing, the "Product Category", the " Purchase Group", the "Purchase Organizations" and all data in the PO must be replicated in SRM system customization? The customizing of the SRM system must be the sum of the “AAA” and “BBB” system?
(...)

Product Categories, Vendors, Locations, etc, for all backend must exist in SRM.

Purchasing Organizations and Groups are not replicated from ECC backend.

See SRM configuration guide "Basic Settings for SAP Supplier Relationship Management".

Regards.

Laurent.

Message was edited by: Laurent Burtaire

[Former Member]

Hi Laurent,

thanks for your support.

Our client application map include two SAP ECC system, "AAA" and "BBB".

We have to implement a new process model in a third TO-BE system ("CCC" = "AAA"+"BBB")

We have different implementative waves, so in in the first one we'll have to:

- implement the new process on "CCC" system

- connect both "CCC" and "BBB" to the SRM system

The assumption is that we can't perform customizing in "BBB" system.

In the next wave "BBB" will disappear and converge into "CCC" system as well.

In our new process ("CCC" system) we need to implement one cross purchase organization code (ie. called "DDDD"), already present in "BBB" system.

So in the first wave the situation is:

- "CCC" backend system linked to SRM, with purchase organization "DDDD"

- "BBB" backend system linked to SRM, with purchase organization "DDDD" 

In the SRM organizational structure (PPOMA_BBP transaction) we will set only one purchase organization code "DDDD" looking for "CCC" target system. Is it correct? Despite the purchase organization code is the same in "BBB" system?

With this configuration, in the SRM system can I buy with purchase organization "DDDD" for the "BBB" system?

If not, can you suggest me the correct organizational structure configuration?

BR,

Marco

[laurent_burtaire]

Hello Marco,

please, read my first response.

Regards.

Laurent.

[Former Member]

Hi Laurent,

thanks for your support.

Could you please suggest me the SRM organizational structure configuration to manage a cross purchase organization for different company codes?

For example:

In the Manage Organizational Plan (PPOMA_BBP transaction)

- Create Company Code 0001 for the BE system "CCC"

- Create Purchase Organizational "DDDD" under this Company 0001

- Create Purchase Group for this company 0001

- Create Company Code 0002 for BE systems "BBB"

- Create Purchase Group for this Company  0002

- Manage the purchase throuth the "Responsability" TAB in Purchase Organizational "DDDD" line

Do you think this configuration works correctly?

Regards