Contract GOA to Purchasing Contract for future use.

[former_member183819]

Hi

Can we abandone GOA and start use the Purchase contract for future purpose?

REVISE THE GOA AND ETC.

Has any one tried the same?

Muthu

[Former Member · Accepted solution]

Hi Muthu,

I havn't tried however I know there is functionality available for migrating GOA's -> PCTR/CCTR. The goal in SRM 7 looks to be CCTR/purchasing contracts.

You can start using a new contract type ofcourse but this i think you already knew for certain: Set-up purch. contract transaction type + nr ranges -> link activate via ppoma_bbp attributes (in short).

Kind regards,

Tim

[former_member183819 · Accepted solution]

Thanks Tim. we are in SR 550

[Former Member · Accepted solution]

Hi Muthu,

If you want to use the purchase contracts as SOS in R/3, I believe it is possible. In SRM, there is an RFC FM available to provide the list of contracts (SOSFIND*). Need to lookup the FM name though. The call-offs will be updated to the purchase contract (like it gets updated to GOAs). Some custom development may be necessary.

In case, you want to abandon the GOA after it is created and use only the local contracts directly in R/3 then it is not advisable as it does not go along with the purpose of creating a GOA.

Does this address your question?

Regards

Saravanan.

[former_member183819 · Accepted solution]

Thanks Saravanan.

for example

i created GOA 500 ..and distributed to backend 500 purchasing contract.

now I want to end of GOA creation process from SRM.

from 501 contract, i want to create a contract from me31k rather than process GOA.

can i revise the 1-500 GOA in ECC for future business purpose .

1-500 Purchasing contract must be revised for business too

501,502.. i want to keep creating contract from me31k ...

i dont bother about calloff to SRM since i dont want any more SRM release info since i too have release info in me33k.

Muthu

[Former Member · Accepted solution]

Hi Muthu,

Assuming that 500 is a GOA and 500 is the corresponding contract created in ECC.

You can as well create new contracts 501, 502 etc in ECC directly. They are in no way linked to the GOA and will have no bearing on the usage of the GOA. So, in future you can use 501, 502 and at the same time revise the GOA 500 in SRM (which will automatically revise the contract 500 in ECC).

The difference is 501, 502 are created in one ECC system and they are available only there. However, 500 may have been distributed to multiple ECC systems.

If you want to revise contract 500 directly in ECC by disregarding the GOA 500 then it is not advisable, as any change to GOA 500 at a later point will overwrite contract 500 changes in ECC. The GOA should be treated as the leading document.

Regards

Saravanan.

[Former Member · Accepted solution]

Muthu,

Here are some things you may have to do to achieve this.

1. Change number range in ECC to internal from external as the Contracts were being created from GOA and now it is local.

2. To disallow calloffs, you could take out the partner profile configuration that sends BLAREL IDOcs to SRM.

Those two steps should fix what you are looking for.

SG

[former_member183819 · Accepted solution]

Thanks every one..

[Former Member]

Do you mean stop using an already created GOA and maintain the follow-on local contracts directly? I didnt get the context of your question.