ERP Contracts as source of supply in SoCo??

[Former Member]

Hi Everyone,

We are implementing SRM 7 with ECC EhP4 in classic. We have read about the new business scenario "Service Procurement Classic (MM-SRV)",in this scenario we cannot create SRM contracts to requirements of services with hierarchical structure, only ERP contracts. Aditionally, in the documentation, we read that only ERP contracts can be used as source of supply to this kind of requirements. So, this mean if we send a PR from ECC to SRM, the purchaser can use the ECC contracts in the Sourcing Cockpit (Care out sourcing)? o How can we use the ERP contracts??

BR

Ivá

[Former Member · Accepted solution]

Hi Ivan,

if your system landscape is on ECC 6.0 Enhpk 4 and SRM7.0 , you can find only ERP contract as a source of supply in the SRM sourcing cockpit. Once you assign the ERP contract as a source of supply, the follow-on document such as PO will be created in ERP backend system.

The advantage of service procurement classic is that the PO created in the ERP system will be sent to SUS system and you can collaborate with Supplier on po confirmation, service entry sheet and invoicing.

Thanks and regards,

Ranjan

[Former Member · Accepted solution]

Hi Yeu Sheng and Ranjan,

As we understand, according yours answers, the ERP contracts can be used in both systems (MM and SRM). We can use them before the PR is sent to SRM and during the SoCo. Is it correct our understanding?

BR,

Ivá

[yeushengteo · Accepted solution]

Hi,

As long as you are running classic scenario, ERP contract can be used as SOS in both SRM or ERP.

Regards.

YS

[Former Member]

Sorry, an error was mine. had put wrong the delivery dates

[Former Member]

Thanks Yeu Sheng,

So, if we can use de ERP contracts in classic, this mean we can use both material contracts and service contracts? Can we create Contracts directly in the ERP and use them as SoS in SoCo? And also, can we use the Badi BBP_DETERMINE_LOGSYS in order tu create only ERP contracts (materials and services) and use them both in SoCo. This action with the porpuse of having only one repository of contracts?

BR

Ivá

[yeushengteo]

Hi,

ERP contract that is transfered from SRM (via BADI BBP_DETERMINE_LOGSYS) or in ERP (via ME31K) can be used as SOS in both ERP and SRM in classic mode. So to answer you, YES is the answer.

Where to have all your operational contract document residing at which system is depending on your preferences. If you have multiple ERP systems, then the SRM central contract will be a better choice in my personal opinion. If you are not missing the SRM central contract features, then definitely you can continue to use the ERP solely as the system for contract creation.

By doing classic scenario, there is direct material which will alter it since direct material will always create local SRM PO and replicate to ERP (like ECS PO). So now the 1st point arise where you have to consider. I leave you to think of others point which will affect your decision which system to house the operational contract.

Regards.

YS

[Former Member]

Hi Yeu Sheng,

In our case, we have only one ERP. In this case, It seems that we can have only ERP contrats and ERP as repository.

In the case of the direct-material PO, Is there any Badi like BBP_DETERMINE_LOGSYS for POs?

Thanks,

Ivá

[Former Member]

no . you can not enjoy the backend contract for ordering as Direct via SRM

either you have to go CCTR contract creation .this is can be achieved so it can be used .

When you order as Direct , the system behaves totally extended classic scenario.

SAP Note 495484 - Direct material: Sources of supply from

the back end

Note Language: English Version: 2 Validity: Valid Since 14.02.2002

Summary

Symptom

A product is entered in a shopping cart item. Sources of supply (contracts

or info records) are determined for this product from a back end system,

which is apparent when you select the "Sources of supply" table tab page in

the detail view of the shopping cart item.

If you choose "Procurement as direct material" for the item, the sources of

supply previously determined from the back end system disappear.

Other terms

BBPPU99, contract, info record, extended classic scenario, shopping basket

Reason and Prerequisites

The direct material scenario or the extended classic scenario is used.

Solution

The behavior described above is in accordance with the system design.

Only local sources of supply (local contracts and interlinkages) can be

used in the direct material scenario, as well as in the extended classic

scenario. The purchase order handling is mapped, as for the standalone

scenario, via local purchase orders.

In addition to the standalone scenario, the copy of the local purchase

order to the back end system facilitates full subsequent processing in the

back end system for direct material and extended classic scenario.

Also refer to Note 419424 which describes the prerequisites for local

contracts as possible sources of supply

[yeushengteo]

Hi Ivan

As above reply from Muthu, you cannot use any BADI to control the direct material. It will be defaulted as local SRM PO first and replicated into the ERP (similar to Extended classic). As such ERP contract will not works here..

To enable direct material with classic scenario, please also check this [thread|; too.

Regards.

YS

[Former Member]

Hi,

I am i SRM 7 EHP8 with classic scenario but in SOCO i can not view the ECC contracts,

any idea what I'm doing wrong?

Thanks.

[yeushengteo]

Hi,

Firstly read the service procurement classic [documentation|http://help.sap.com/saphelp_srm70/helpdata/en/bd/12bd5534c74cfeaae81d30f13d5750/frameset.htm] which SAP has provided.

As for how you can use your contract - contract can be used as SOS for ERP PR. Hence once the contract is already established, there may not be a need to send the PR into the SRM Sourcing Cockpit for assignment of supplier unless you really have to do so (e.g. for new RFx re-tendering).

One other key advantage of the service procurement is the integration of the SUS which is working for classic deployment. Hence ERP PO can seamlessly works with the supplier on SUS.

Best regards.

YS