Problem with IDOC BLAREL02 in SRM

[Former Member]

Hi, all!

Please help me.

We have SRM 5.0 (SAPKIBKT10) the extended classic scenario.

From the sourcing in SRM we create a GOA and distribute the GOA to backend system.

After distribution of the GOA backend system creates a contract. In the backend from contract we create purchase order. At the SRM we have the IDOC BLAREL02,for example:

KONNR 5600000048 Number of principal purchase agreement

KTPNR 1 Item number of principal purchase agreement

EBELN 4500285230 Purchasing Document Number

EBELP 20 Item Number of Purchasing Document

BEDAT 20080122 Purchase Order Date

MENGE 4.000 Purchase order quantity

MEINS KGM Order unit

NETWR 196 Net order value in PO currency

WAERS RUR Currency Key

WKURS 1.00000 Exchange rate

LOGSY DEVCLN520 Logical System

WEPOS X : Yes Goods Receipt Indicator

REPOS X : Yes Invoice receipt indicator

WEMNG 0.000 Quantity of Goods Received

REMNG 0.000 Invoice Receipt Quantity

BUKRS 2000 Company Code

WERKS 2000 Plant

EKORG 2051 Purchasing organization

BSTYP F : Purchase order Purchasing document category

But during the processing the BLAREL02 in the transaction BD87 I have the error: "Object Linkage for Global Outline Agreement does not exist".

Best regards,

Guzal.

[Former Member · Accepted solution]

Hi Claudia,

Thank you for reply.

In the GOA at SRM I have next status:

HEADER I1021 Created

HEADER I1038 Complete

HEADER I1141 Released

HEADER I1180 Document Completed

HEADER I1193 In Distribution

0000000001 I1143 Item is Active

I'm tested the function module B46B_IDOC_INPUT_BLAREL

with setting session breakpoint. The function BBP_API_CENTRAL_CONTR_CALL_OFF

SY-SUBRC = 1 when 1, then error № 512: ''Object linkage for Global Outline Agreement does not exist". The sy-subrc= 1 because in the table SRRELROLES not record with key 5600000059 000000000100000000000000000000 BUS2014001 TSTCLNT300. If I manually to insert this key in the table SRRELROLES it's all the same the internal table CT_LINKS is empty. As a result - error 512. We forward message to SAP Support, but problem yet not solved.

Best regards,

Guzal.

[Former Member · Accepted solution]

What happened at my company was that there are 2 entries in table SRRELROLES, 1 which is complete and 1 that just displays the contract number.

In the inbound processing of the idoc the empty one is called first (and throws an error) the 2nd one is then not processed. We found the following note: Note 656181 - Release synchronization of releases on services in which processing is changed and we no longer have the same error as you got.

We are also on SP10 with SRM 5.0 by the way.

Regards,

Robin

[Former Member · Accepted solution]

Hi Guzal,

the error comes, when the status of the GOA is not updated correctly. In that case also releases are not updated and show an error in the IDoc.

Please check the scheduling and the settings for the jobs BBP_GET_STATUS_2 and CLEAN_REQREQ_UP. They are the drivers to get the status and the object linkage created and updaten. You can also run these reports manually via trx se38. The system will then update the status of the documents and show in case of issues the real problem. After that create a new GOA and do the whole cycle. It should work then.

Cheers,

Claudia

[Former Member]

Hi Guzal,

We are facing similar porblem and with similar versions...can you plesse help us to proivde solution!!

Thanks,

[Former Member]

Hi Claudia,

Thank you for your answer,

it's very helpful to us.

Thank you very much.

Best regards,

Guzal.

[Former Member]

Hi, Robin,

Thank you for you answer,

we was already employed note 656181, but this don't help us,

and we don't use services, only materals.

Best regards,

Guzal.

[Former Member]

Hi, Claudia

I' m create GOA only with materials (we don't have services). The GOA is distributed OK to R/3 system. At the R/3 I create PO (type ECPO) with reference to that GOA. The IDOC BLAREL to leave from R/3 OK. In the SRM IDOC BLAREL come with error.

In SRM I use transaction type GCTR and ECPO. In the R/3 I create the document type value contract GCTR (copy from WK) and create document type purchasing order ECPO (copy from NBK).

In SRM I create PO (type ECPO) (it's copy replicated in the R/3) or GOA (type GCTR) (that distributed to R/3) from sourcing.

Best regards,

Guzal.

[Former Member]

Hi Guzal,

I am able to replicate the issue. The object linkage is not working, when the distribution status in SRM is not set to completed. I have a GOA in R/3, but the status is still "in distribution".

There seems to be something wrong with the indexing of the documents.

Any update from your side?

Cheers,

Claudia

[Former Member]

Hi Rafael and Claudia!

Thank you for information,

but I not change the plant in the PO,

The location (plant) especified in the contract distribution - the same as the location (plant) specified in the item of the backend purchase order.

Best regards,

Guzal.

[Former Member]

Hi Guzal,

hm - getting tricky - could you confirm, the following:

- create a new GOA, only with Materials, no Services

- Distribution of a new GOA down to SRM is OK; the document exists and the status is distributed?

- PO in R/3 can be created with Reference to that GOA?

- What type of Contract - Quantity / Value is like to the GOA?

- What document types are you using for the scenario?

Cheers,

Claudia

[Former Member]

Hi, Atul

Thank you for you reply,

but this note not appropriate.

Best regards,

Guzal.

[Former Member]

Hi Guzal,

We are implementing SRM 4.0 (SAPKIBKS09 Support Package level) with Extended Classic Scenario.

We are facing the same problem as you and discover part of the solution:

We have the error "Object link doesn´t exist..." when in the backend purchase order we create, we modify the plant (or location) of any item.

However, when the doesn´t modify the plant (location) that we input in the GOA distribution, we error disappears.

We think is a gap of the standard solution. We have a OSS note regarding this question.

Hope it will help you.

And any advance you make, please tell us!!!

Regards!

[Former Member]

Hello,

SAP has answered the question: The location (plant) especified in the contract distribution has to be the same as the location (plant) specified in the item of the backend purchase order.

---> Your requirement of "change the plant in the purchase order and process

the IDOC successfully" can not be achieved in the normal SRM process.

If you feel this functionality needs a modification, i would suggest

you to create a development request as per SAP note 429166 using

'Development Request Tool'.

Anyhow, if any of you discover any solution, please tell us.

Regards.

[Former Member]

let me add to Rafael's information:

A GOA is meant to be used for the materials and releated conditions. When the plant is changed, and it is not reflected in the GOA by a combination of plant and material (price), then it makes sense to error out.

Add the combination needed to the condititions (plant specific pricing) and it should work for you.

Cheers,

Claudia

[Former Member]

Hi, Robin

Thank your for you reply.

We can't implement the note 1092012, because we have R/3 4.6 C

Best regards,

Guzal.

[Former Member]

Hi, Claudia

R/3:

Partn.number SRQCLNT900

Partn.type LS Logical system

Message type BLAREL Release order documentation f

Receiver port A000000019 Transactional RFC система SRQ мандант 900

PacketSize 1

Basic type BLAREL02 Contract release order s

SRM:

Partner No. DEVCLN520

Partn.Type LS Logical system

Message type BLAREL Release order documentation

Process code BLAR BLAREL Rel. Documentation

At R/3 in we02 IDoc in outbound processing status: Data passed to port OK, IDoc sent to R/3 System or external program. AT R/3 not error, all OK. I don't think that problem in We20 because IDOC to leave from R/3 and come to SRM. Something is wrong here with data in SRM.

Best regards,

Guzal

[Former Member]

If I recall correctly I had the same problem. What happened is that the status of the GOA is set to the wrong value, although the GOA itself is correctly replicated.

I assume you have an ECC backend, if so, apply the following note in ECC:

1092012 ERP 2005-SRM 5.0: GOA status set to Distribution Incorrect

If you don't have this note applied, some relationships in SRM will not be made and that is what causes the error.

Regards,

Robin

[Former Member]

Hi, Atul,

Thank you for your answers.

I don't have problem with distribution GOA from SRM to backend system.

I have problem with the IDOC in inbound processing in SRM with type BLAREL02.

I compare the IDOC in inbound processing in SRM with type BLAREL02 segment E1RDOCU

with structure E1RDOCU: Main seg. release order documentation for distributed contracts. They

identical. But this IDOC to get in SRM with error: Object Linkage for Global Outline Agreement does not exist.

Best regards,

Guzal.

[Former Member]

Hi

Additionally refer to the SAP OSS Notes below ->

Note 953376 - BLAREL: Incorrect values in service segment

Note 953269 - ALE contract distribution: Service statistics are incorrect

Note 948008 - ALE contract distribution: Service statistics incorrect

Note 671764 - Service segment release documentation assigned incorrectly

Note 932227 BLAREL: Net value incorrect for subsequent IDoc

Note 643823 - BLAREL: Incorrect values in service segment

Note 641919 - BLAREL: values in service segment E1RDSV1

Note 614048 Incorrect release documentation with held purchase orders

Note 671764 Service segment release documentation assigned incorrectly

Note 197050 ORDRSP, DESADV: IDoc segment number in the case of an error

Note 88968 Conversion of order currency to ISO code in IDoc

Hope this will help.

Incase this does not help, please create a Customer OSS message with SAP.

Do keep me posted.

Regards

- Atul

Edited by: Atul on Jan 24, 2008 11:23 PM

[Former Member]

Hi, Claudia.

Thank you for your reply.

I have:

In R/3 (DEVCL520) in trx We20 at partner type LS- SRQCLNT900 (SRM): outbound parametr - BLAREL, receiver port RFC destination SRQCLNT900

In SRM (SRQCLNT900) in trx We20 at partner type LS- DEVCLN520 (R/3): inbound parametr - BLAREL.

I have IDOC in inbound processing in SRM with type BLAREL02, with structure E1RDOCU : Main seg. release order documentation for distributed contracts. But this IDOC with error: Object Linkage for Global Outline Agreement does not exist.

Best regards,

Guzal.

[Former Member]

Hi Guzal,

I am pretty sure, that somewhere is a mix up. The Idocs are standard and working fine. R/3 does not find the right GOA in SRM to which it is connected. Althought is sounds nuts, have a look again or to it together with someone.

R/3:

Message Type: BLAREL

RFC Port: something like A0000000 pointing to SRM

--> there are usually more ports, make sure you take the right one

IDoc Type: BLAREL02

SRM:

Message Type: BLAREL

Process Code: BLAR --> existing? Select from list

What is the whole error in the outbound queue of R/3 SMQ2 and WE02?

What content is the GOA about - Material or Services?

Cheers,

Claudia

[Former Member]

Hi Guzal,

I assume the distribution down is working fine. Is the entry LOGSY DEVCLN520 Logical System pointing to the right system?

Check the distribution model for getting the release orders up. System does not know, where to post to.

It happens, that the destinations are getting mixed up and the entry is put in the wrong system as well connect to the wrong client:

- In SRM trx WE20 you need to locate your Backend Client System and enter the Idoc BLAREL as an inbound parameter with the details

- In R/3 trx WE20 you need to locate your SRM Client System and enter the Idoc BLAREL as an outbound parameter with the details; Make sure, you are using the right receiver port for SRM.

Cheers,

Claudia

[Former Member]

Hi

Please go through the related SAP OSS Notes as well ->

Note 953376 BLAREL: Incorrect values in service segment

Note 953269 ALE contract distribution: Service statistics are incorrect

Note 932227 BLAREL: Net value incorrect for subsequent IDoc

Note 646903 Global outline agreement: Tips and tricks

Note 641919 BLAREL: values in service segment E1RDSV1

Note 776013 Global master agreement, incorrect update of release history

Note 671764 Service segment release documentation assigned incorrectly

Note 643823 BLAREL: Incorrect values in service segment

Do let me know.

Regards

- Atul

[Former Member]

Hi

The SRM system uses the IDoc BLAREL02 for receiving update data of contract release orders (accumulated data of contract release orders in the backend system. In order to see the Release information per Contract in SRM, the Inbound Queue for the Release Order data is maintained in the SRM Partner Profile)

Please go through the pointers ->

http://help.sap.com/saphelp_srm50/helpdata/en/58/2a8442a07b0e53e10000000a155106/frameset.htm

You can also use note 646903 for more GOA tips & sample codes.

http://help.sap.com/saphelp_srm50/helpdata/en/00/f5c93f4d903b1ce10000000a114084/content.htm

https://websmp104.sap-ag.de/~sapidb/011000358700002529571998/blarel02_d.htm

Hope this will help.

Regards

- Atul