GOA contracts SRM not transfered in back-end R/3

[Former Member]

Hello experts

we are implementing contracts into SRM 3.0. All customizing seems to be ok, specially idocs (types BLOARD, COND_A ...).

We succeed in creating contract in SRM, but they aren't transferred in R/3 system.

I can't find any idocs in R/3 or SRM.

The status of the document is I1195 : "Distribution Incorrect".

And when i execute MF META_CTR_CHECK, i have 1 error message : Error "determining document type".

Any idea of that?

Thank you for your help.

Peggy.

[Former Member]

Hi,

Please try the follwoing OSS Notes ->

Note 1042111 GOA status set to Distribution Incorrect wrongly

Note 1039819 GOA Distribution of Items in Backend R/3

Note 1037623 Incorrect Error message for maintaining distribution entries

Note 945029 Distribution of Target Quantity to QW8 failed

Note 940632 Distribution incorrect-When invalid Purchasing Org entered

Note 909516 SRM40/CTR:New line itm distribution flag cannot be unchecked

Note 847398 Incorrect determination of the EKGRP back end

Note 1039819 - GOA Distribution of Items in Backend R/3

Note 942008 - SRM Distribution of GOA to R/3 System: Scales missing

Note 842181 sent Purchase orders: lineitem-texts in wrong order

note 1030548 Revision level in SRM 6.0 connected to ERP 2005

Note 1047512 Contracts: Duplicate Messages

Note 847237 SRM Global Outline Agremt: Distribution of deleted condition

Note 609222

Note 646903

Also check when you discribe the distribution already stops in SRM, correct? It means, There are no

Idocs created (via WE02 in R/3). Are the number ranges, document types,

mapping of conditions (SRM --> R/3) set? Vendor and / or Material used valid

for the Purchasing Organisation used? Could you describe which settings you done / how the GOA looks like in your

scenario?

Have you raised any Customer message with SAP on this yet ? If not, better to raise one as well for fast processing.

BR,

Disha.

<b>Pls reward points for useful answers.</b>

[Former Member]

Hello Disha,

Thank your for your response. Actually, it seems it was a problem of conditions mapping, because I tried to create again a contract without condition and now i can find Idocs in back-end system. BUT i can't find contracts in back-end system. The status of idocs created is "transmitted" but no way to find the contract (t-code me33k or in ekko table) with the number mentionned in belnr field in idoc segment.

Here the setting up we made in back-end system for partner type LS :

- Inbound processing code for purchasing contracts to message type BLAORD (Process code: BLAO)

- Inbound processing code for conditions to message type COND_A (process code COND).

- Outbound processing codeto message type BLAREL (process code BLAREL02).

In t-code OMEF (Specifying the Document Types for Backend Contracts) :

we specifyed the type PCTR assigned to the key "MKK" and the same external number range assigned in SRM system. And we specified also the type GCTR with same data.

In SRM system, we have defined a port of type RFC to back-end system.The setting up in SRM for partner type LS is :

- Inbound processing is message type BLAREL (process code BLAR)

- Outbound processing is message type BLAREL (process code BLAREL02).

One more, i have noticed that there are Outbound idocs in back-end system type BLAORD which are failed.

I really don't understand why i find inbound idocs status "transmitted" (green) in back-end system and i can't find the corresponding contract document; and why there are outbount idocs in back-end system.

Thanks a lot for your help.

Peggy.

[Former Member]

Hello

Actually, i have a message in idoc with status "51". It concerns a problem with company.

It concerns this dynpro when you create a contract :

"The purchasing org not been assigned to a coCode. Please enter a company code".

Where do i have to fill this value? I can't find this value in structure cs_header or in CT_ITEMS table in teh BAdi BBP_CTR.

Thank you for your help.

Regards,

Peggy.

[Former Member]

Hi

Which R/3 version are you using ?

The IDoc gets created when the relevant function module in this case gets triggerred, before calling this BADI - BBP_CTR in the R/3 backend system.

Please read the standard BADI - BBP_CTR documentation in this case for more details.

<u>Put a break-point in the function module BBPV_CONTRACT_TRANSFER

in the R/3 back end system.</u>

<b>The FUNCTION module bbpv_contract_transfer is intended to

create/change MM Purchasing Contracts and MM Scheduling Agreements via the IDOC BLAORD03 and the corresponding pricing information via the IDOC COND_A02</b>

<u>Please go through the related links below as well -></u>

Hope this will help.

Regards

- Atul

[Former Member]

Hi Peggy,

Seems like you have a purchasing organisation that is not assigned to a company code in the ERP system.

Please ensure that either the Purchasing Organisation in ERP is assigned to a company code or if you want a cross company purchasing Organisation in ERP, then specify a company code in the IDOC BLAORD in segment E1EDK14 by implementing the method MODIFY_IDOC_DATA_CTR of BADI BBP_CTR

in the ERP system.

Hope this resolves the issue.

Regards

Sumat