SRM 7 SC: wrong confirmation linkage

[Former Member]

Hi

We have upgrade from srm 3 to srm 7 and are using with classic scenario.

SC are created successfully with backend PR and PO, when we check the status of SC in related documents it shows all the documents from SC to PR to PO correctly except confirmation.Here even though we havent created any confirmation for the PO it shows an old confirmation linking to the newly created PO in history.

For eg.

Doc Doc no Backend Doc No date

Shopping cart 71 8/26/2010

PR 31 8/26/2010

PO 41 8/26/2010

Conf 13 5/19/2009

As you can see though i havent created any confirmation it automatically links an old confirmation dated back to 2009 to sc/po.

I have created both background jobs clean-req and bbp_get_status plus also have maintained SYS for both r/3 and local srm system,as we create confirmations in SRM.

Please do advice.

Thanks,

Mahesh.

[Former Member]

This note might help -

Note 1413439 - History: Wrong confirmation link after applying Note 1390087

[Former Member]

Dear Jay,

Appreciate your quick response,Thank you.

we are on SP Level SAPKIBKV07 , below notes are already

present.

I managed to debug "LBBP_PDH_HISTORYF06" and have found out below

pointers.

Below select statement fetches the confirmation linked to the backend

PO,but one thing i dont understand is why in firstplace this old

confirmation linked to the newly created backend PO.So i feel when PO

is created in backend it creates this entry in SRM which links it to

already existing confirmation.

• read lean objects linked to this backend PO

SELECT * FROM bbp_pdview_bih INTO TABLE int_objects

WHERE be_refobj_type EQ c_b_po

AND be_refobj EQ history_po-object_id

%_HINTS ORACLE 'INDEX

("&TABLE&" "BBP_PDBEI~REF" "BBP_PDBEI^REF" "BBP_PDBEI_REF" "BBP_PDBEI_REFX")'

DB2 '&SUBSTITUTE VALUES&'.

Hope you understood my query.Please do advice .Thanks a lot.

@Experts pls do chip in.

mahesh

[Former Member]

One more finding

SRM creates a record in table 'BBP_PDBEI'( which stores backend references for PO object) with a guid which exists in table crmd_orderadm_i(as its the item guid) but its parent is the CONF document in crmd_orderadm_h.

Edited by: mahesh.a on Aug 27, 2010 1:36 PM

[Former Member]

Hi Mahesh

Is it happening for every new PO?

Try to do the following: -

1. Stop BBP_GETSTATUS_2 and CLEAN_REQREQ_UP

2. Do not let the Approved PO to flow to ECC (stop it by putting some hard stop in the FMs which make a call to ECC)

3. Check Tables in SRM to see if the PO is still linked to Old Confirmation.

If that does not happen, then let activate the above reports again and let the PO get created in ECC. Monitor BBP_GETSTATUS_2 job to check what is being updated in SRM by this job.

If you still do not get any success, its time to send it to SAP as they can login to your system in your landscape.

Regards

Virender Singh