Distribution of GOA to the backend system

[Former Member]

Dear Experts,

I am working in Extended classic scenario (SRM 5.0). We are planing to configure GOA.

Can any one give me the steps required to configure GOA and distribute the contracts to the back end system.

When I create the GOA as of now GOA is getting created but not distributed.

Regards,

B.N.Karthikeyan

[lisa_sheil · Accepted solution]

Hi,

Here are the main configuration steps needed:

1: Make sure you have done the following in customizing:

When you go to define transaction type and you

choose the entry with BUS2000113, then you click Transaction type

go to DETAIL screen of GCTR and choose Global Outline

agreement as a specification.

2: You can follow these steps.

1. Go to the transaction WEDI

2. Goto IDoc menu and select Partner Profile (or F6)

3. In Partner Profile, Goto PartnerType LS

4. Click on the client eg. ABCCLNT300

5. In "Inbound parmtrs" make an entry for BLAORD.Enter the client as

Partner number. BLAO as Process Code.

3: In the R3 backend system,

maintain BLAORD as inbound message type, and maintain

BLAREL as outbound message type

4: One of the requirements for setting up GOA is:

Mapping of the appropriate products,product categories, condition

types, document IDs, transaction types and text iDs in the BAdis:

*IN EBP > BBP_CTR_BE_CREATE

• IN the backend system: BBP_CTR

Any GOA contract in EBP has to be mapped in R/3 with the corresponding

entry for conditions i.e 01CT to synchronise the two systems.

If the conditions are not mapped, the idocs will not be created.

Hence, please map the conditions and check for the distribution.

It is also an option to try:

Please run the function module 'BBP_PD_CTR_TRANSFER', this FM posts the

IDOC in R/3 and add an entry in BBP_DOCUMENT_TAB,

afterwards call report 'CLEAN_REQREQ_UP' which updates the status.

Kindly ensure all customizing and settings are correct in both SRM and

R/3 backend in order for the GOA to pass from systems without issues.

I hope this helps,

Kind Regards,

Lisa

[lisa_sheil]

Also please dont forget the following:

In SRM:

Use an internal number range in srm for the GOAs transaction type that

is the same as the external number range in the backend for the

corresponding transaction type.

Use PPOMA_BBP to check the org data such as Purch org & Purch Group

of the backend system exists in the org structure.

In R/3 backend system :

Make sure the backend system is release 46B or higher with Plug-In

2004.1

*Set up an external number range for the document types referring to

SRM purchasing contracts and scheduling agreements.

*Implement the number range for the number range object BBP_SRV with

internal number assignment for service items.

*Set up IDOC customizing (Note 641919 BLAREL-BLAORD03, COND_A02,

BLAREL02).

PLease also review the following Note 646903, it is very helpfull.

Kind Regards,

Lisa

[Former Member]

Hi Lisa,

In ECC side I already configed Inbound IDOC message type BLAORD and Outbound message type BLAREL. In SRM side I configed outbound message type BLAREL.

What farther config need for GOA in SRM side??

We distribute GOA from SRM to ECC by Job or other method??

In another word, how we trigger the distribution of GOA? It is auto or manual?

Thanks very much!!!!

[Former Member]

Hi,

Once you release and approve the GOA, the system distributes it as a contract or a scheduling agreement to the backend systems. Within these backend documents, you can find a link to the attachments of the GOA that are maintained in the SRM system.

For more information, see SAP Solution Manager ® mySAP SRM ® Business Scenarios ® Contract Management ® Business Processes ® Processing Global Outline Agreements ® Configuration ® Distribute Contract

http://help.sap.com/saphelp_srm50/helpdata/en/43/0f23869e242a8be10000000a1553f6/frameset.htm

Hope could be helpful..

Thanks

prasad.s