SRM Confirmation - All buttons are greyed out

[Former Member]

Hello experts,

I have seen posts on similar isue but could not find one which was relevant.

Here is my problem.

I see that after a confirmation is created, when I go back into "Display and Process Confirmations ", all the buttons are greyed out. The header statuses for the confirmation are as given below.

Complete

Confirmed

Created

Approved

Currently Being Transferred

I am not sure why it says "Currently Being Transferred", when its actually posted in the backend.

All clean up and update jobs are running fine. I am on SRM 5.0. I even tried the program to regenerate BBP_DOCUMENT_TAB entries.

Please help incase you have experienced this or know the solution to resolve this problem.

Thank you.

Thanks and Regards

Manish Mohan

[Former Member · Accepted solution]

Some information regarding the general behaviour of the system when creating material confirmations.

Generally whenever a material confirmation is created in the SRM system

,an IDoc is posted from the SRM to the R/3 system and an entry (with

DocType IM) is written into the table BBP_DOCUMENT_TAB.The sending of

the IDOC is then checked by the background job CLEAN_REQREQ_UP.The

report reads the BBP_DOCUMENT_TAB and makes a RFC(remote function call)

per META_GOODSMVT_UPDATECHECK to check the posting of inbound IDoc

If the IDoc is posted successfully (status 53), the SRM confirmation

receives status I1018 - "Posted in the Backend".In addition,the

entry is deleted in BBP_DOCUMENT_TAB.

However sometimes it so happens that due to some inexplicable reason the

background job CLEAN_REQREQ_UP sometimes does not clear the

BBP_DOCUMENT_TAB entry for some confirmations and these confirmations

remain in status I1017 - Currently Being Transferred. As a result these

confirmations show with the status 'Approved' in the confirmation

screen.It is very difficult to ascertain the exact reason as to what causes this system behaviour because of the numerous

possibilities.

However once the job CLEAN_REQREQ_UP is run again and the

BBP_DOCUMENT_TAB entries for these confirmations is cleared the

status is successfully updated from I1017 - Currently Being

Transferred to I1018 - Posted in the Backend.

In cases where the confirmation is stuck with status I1017 -

Currently Being Transferred (i.e Approved) and if the BBP_DOCUMENT_TAB

entry is missing by chance, which is mostly like your case, we have the option of recreating the

entry in table BBP_DOCUMENT_TAB for this confirmation using the

original report ZZRF1_1 given in note 644963. This report recreates the

BBP_DOCUMENT_TAB entry and once the job CLEAN_REQREQ_UP is run

the status of the confirmation is updated from I1017 - Currently Being

Transferred to I1018 - Posted in the Backend.

Regards

Lauren

[Former Member · Accepted solution]

Thank you Lauren, but as mentioned I did execute this report to regenerate the entries and then executed the clean up program as well. But this did not help.

Any other areas where I would need to check?

Thank you,

Manish

[Former Member · Accepted solution]

Hi Manish,

Did you manually run the update reports CLEAN_REQREQ_UP and BBP_GET_STATUS_2 without any document numbers?

So there is no entry in BBP_DOCUMENT_TAB for this document?

You mention that the document has been created successfully in the backend?

Did you check the status of the IDOC in both EBP and the backend?

Nevertheless I have an Info for you - If you debug the program

clean_reqreq_up you may find out that the corresponding IDOCs within the

backend system are never found by the FM

B46A_GOODSMVT_UPDATECHECK - this FM is called within the program

clean_reqreq_up with the parameters:

object_ident-objkey = IS_DOCUMENT_TAB-OBJKEY.

object_ident-objtype = 'IDOC'.

object_ident-logsys = sender_logsys.

where the OBJKEY is the IDOC number within EBP-System.

Because the corresponding IDOC is never found in the backend system

(the return code from backend system is always 1 - object not found)

all confirmations get the status I1019 (Transfer Error) and stay hang

in the table bbp_document_tab in the QSR-system and also alert message

is created for them.

The question is why is it not possible for this FM to found any IDOC in

the backend system even when there are posted there...

this FM is called within the program where the OBJKEY is the IDOC number

within EBP-System.

where the OBJKEY is the IDOC number within EBP-System.

Because the corresponding IDOC is never found in the backend system

(the return code from backend system is always 1 - object not found)

all confirmations get the status I1019 (Transfer Error) and stay hang

in the table bbp_document_tab in the QSR-system and also alert message

is created for them.

So if there is no entry in BBP_DOCUMENT_TAB, maybe, regenerage another one and run this in debug mode and recheck.

Hope this helps,

Kind Regards,

Matthew

[Former Member · Accepted solution]

Hi,

Use the Function module BBP_PD_CONF_TRANSFER_V2 for manually transfaring the confirmation from SRM to ECC.

take GUI ID from BBP_PD for the confirmation and execute. it will generate the idoc.

Check the idoc status using we02 in both systems analyze the error message if any, using BD87 reprocess the idoc.

Hope your problem will resolve

Thanks & Regards,

Prasad.s

[Former Member · Accepted solution]

Hello Mathew,

There is an entry in the BBP_DOCUMENT_TAB table.

CLIENT 300

REQNO 4100000646

CORE KEY

LOGSYS

DOC TYPE SU

ENTRYDATE 06-03-2010

ENTRZTIME 13:08:34

OBJKEY

GUID 00000000000000000000000000000000

ERROR ALERT

IS PD X

I have run the clean up and get status jobs manually with open selection as well.

This is happening consistently. All confirmations are going in "Currently being transferred" status. So manual push will not be of any hel.

One thing to note here is that this is being seen after implementing the note to "1287726 - Cancelling service confirmations in SRM".

This was applied to allow posting's of confirmation in any period.

I have reverted this back but still it did not solve the problem.

Any thoughts?

Thank you.

Manish

[Former Member]

Note 1287726 - Cancelling service confirmations in SRM was reapplied...

[Former Member]

Sorry, I did not mention that I was expecting the Delete and Return delivery buttons to be active.

[Former Member]

Hi

Just wait for 5 minutes then check the display process/confirmation you can able to perform return delivery

Since you are getting the message currently being transferred ..

i.e it will be transferring to the backend.

Regards

Ganesh Kumar .G