Sourcing Organization Structure

[Former Member]

Hi,

We are implementing Sourcing. We are discussing to Org. structure to be configured in the system.

The client does not want to integrate ECC and Sourcing now, but have a plan for future.

When we read the Sourcing documentation, the concept of how the Organization structure created is different from the ECC structure.

Eg. Plants are optional in Sourcing and a Plant is assigned to a Company if plant is created. In ECC Plant is assigned to Company Code.

Also during integartion , Company Code aligns to Business Unit, also Plant can align to business unit.

Its very confusing.

We want to create a structure which will help us to do the integration later rather than hinder it.

Please advice as to how we should approach it.

Regards,

Pankaj

[Former Member · Accepted solution]

Pankaj,

Even if you are not planning to integrate today, I would recommend using the standard SAP ECC data extractors. You are probably on 5.1, so I would look for the ERP Integration ABAP and XI code on the download area, or if you are looking at 7.0 you might want to use the now-built-in ECC extractor (customizing data extract) that they are shipping in conjunction with SAP Sourcing 7.0

At least if you use the standard master data extractors, your upgrade and eventual integration will go more smoothly.

-Howie Wexler

Crafty Systems, Inc

www.craftysystems.com

[Former Member]

Hi

Following is the buyer org structure comparison b/w E Sourcing and ECC which can be implemented in e sourcing:

ECC Company-> ESO Enterprise

ECC Company Code-> ESO Company / Enterprise organization unit (choose ESO company if you do not want to associate ECC plant to ECC company however in standard integration package ECC Company Code is aligned to Org unit )

ECC Plant-> ESO Plant

However make sure you have a well defined business process in place to realise integration (in case you are going for custom integration) to take care of the anomalies. A few e.g. I am giving below:

1. In ESO there is each material must have a unique external ID. This would restrict you to implement a scenario wherein one material is assigned to multiple plants. So make sure you make external ID as Plant_Material combination.

2. Vendor creation process (vendor number in ECC) and replication of vendors from ESO to ECC and vice versa.

In case you are going for standard integration package, all these conditions would be taken care of.

While making a decision b/w SAP standard integration package or custom integration, evaluate the pros and cons for e.g. ECC provides tight integration could be implemented easily but would be rigid in case you have more than one ERP's to integrate while custom integration could be flexible but would require more effort on ESO side

Regards

Mudit Saini

Edited by: Mudit_UCB on Jul 21, 2011 9:09 AM

Edited by: Mudit_UCB on Jul 21, 2011 9:15 AM