External Requirement with contract in backend

[sap_2605]

Dear SAP experts,

We're implementing SRM 7 with backend ECC 6.0. We are using external requirement scenario and central contract. As our backend is not ECC 4.0 we have read that SAP offers a solution using IDOC. Assuming that we can have this scenario then we will be able to replicate the contract in SRM to be used as source of supply in ECC.

In our backend we are using PS module, in which when we input the component we can manually assign the contract number. We plan to assign the central contract passed from SRM in here. Afterward when we release the network the PR will then be created having the contract assigned to it, and then we will push the PR to SRM

This lead us to the question, the PR in question is a PR having central contract assigned to it, is it possible that the PR pushed to SRM having the contract still assigned into it? We have scenario where every requirement which having contract assigned to it SHOULD be created as PO, so in this scenario we expect the PR from PS will become PO in SRM (no need to go to sourcing anymore as the source has been assigned in ECC).

Is this possible?

John

[sap_2605]

Solved. We use IDOC and it works. As for the contract selection, it turns out SRM doesnt bring the contract selected in ECC to SRM. So we use BADI source check to re-select the contract that we have chosen earlier in ECC.

[sap_2605]

Hi rajesh,

As far as i know the standard process for central contract as follow:

1. Say i make central contract in srm with target value 5000 without plants

2. Then i distribute this to ecc

3. Note that central contract can be used as source both inecc and srm, lets say someone consume 500 in srm then the release value now is 500

4. Then using my scenario, external requirement go to srm and become po with value of 700, wouldnt it update the release value in srm to be 1200?

5. As we are in extended classic then it will be replicated to ecc, once it is in ecc wouldnt it trigger the idoc to update the release value in srm.? In this case to be 1900.

That's whatimafraid of.....

For the standard scenario, this willnot happen as the pr will be sourced in ecc only and po will onlybe in ecc

John

[Former Member]

Hi John,

Release values will be updated in SRM once follow on documents (in this case PO) created in ECC.

So, obviously as per your example :

1st step - Sorucing in SRM - Release value 500 (For this also, PO will be created in ECC, is it right ?) since you are ECS.

2nd step - Sourcing through ECC - Release value 700 (total so far 1200) after creation of PO in ECC.

Hence, no duplicate entries and final release value will be 1200

If you have doubt, please do it once in development. I believe this may be useful to you.

Thanks

[sap_2605]

Hi Rajesh,

Thanks for your replies. I cannot replicate this in system because the system not there yet, we're in the middle of preparing the design. And I cannot find reference anywhere whether this will work or not. Will update you once I can set it up in the system

Best regards,

John

[sap_2605]

Hi Rajesh,

Thanks for your reply. However I have doubt.

In SAP library in http://help.sap.com/erp2005_ehp_04/helpdata/EN/17/8b6dda618e4208b3a71782b25badb1/content.htm it is mentioned that we should use different no range for SRM and ECC if we want to use the central contract feature.

Also from the standard process of central contract, the sourcing is done in ERP and then the release value is sent to SRM to update the release value for contract in SRM.

If using my scenario where the PR in ERP will get the contract and will be pushed to SRM. In SRM then it will take the same contract no and become a PO, it will update the release value in SRM contract right? As we're using extended classic, the PO then will be copied back to ERP, will it take the contract in ERP as well? If yes, once it become PO in ERP as well wouldn't it update back to SRM and I will end up having double release value for one PO?

Appreciate your help on this

John

[Former Member]

Hi,

The information what SAP has provided is not a mandatory. Still you can keep same numbers by using BADI_MMBSI_SELECT_CTR_ID. Also, in the same link SAP has mentioned that SRM contract can be kept as soruce of supply in ECC. Kindly check.

I don't think so double entries occured in SRM side.

Please note that SRM contract is a central contract which means you are not going to create on Plant level. It should be on Purchasing organisation level. If it is centralised purchasing then it will be in company code level and no need to assign the purchasing organisation level. Also, in ERP release values are going to update on contract level but on plant level.

I hope the above is in clear.

Thanks

Raejsh K

[sap_2605]

Thanks for the reply,

If we're using central contract are we getting the same contract number as in ECC and in SRM. For example we create contract 123 in SRM and distribute to ECC will we get contract number 123 in ECC?

If not, how can SRM recognize the contract in the PR when the PR from ECC is pushed to SRM?

John

[Former Member]

HI,

To get a same contract number in ECC of SRM, please maintain the number range as External in ECC.

Yes, you would get the 123 as contract number in ECC. Please maintain all the settings as per EC scenario towards number ranges.

i believe there is no issue while pushing the PR from ECC to SRM since contract number is available in SRM whatever presented in PR of ECC.

Thanks

Rajesh K

[Former Member]

Hi,

Since source of supply is already filled in ECC (Central contract created in SRM), PO will be created in SRM. However, while running the program in ECC of external requirement, you will get the Shopping cart first (w/o approval) and then PO will be generated.

Thanks

Rajesh K