PO Confirmation from SUS is not going to R/3 throu Xi.

[Former Member]

Hi Experts!

We are having an issue in SRM implemented with SUS for vendor administration, and Xi to comunicate both.

Basically this issue appears when we create a PO in R/3, then it goes to SUS to be handled by vendors, it means they confirm this PO, so when it was confirmed it backs to R/3. This step is not working, the confirmation in SUS is generated but it is not replicated in R/3. We think there is an issue between SUS and R/3 communication when vendor press confirm. This "between" is the Xi interface. Does anybody know some tips to check here? Does exist any RFC executed here? Can you give me some horizont on this? Thanks in advance!

[khan_voyalpadusman · Accepted solution]

can you check the following things...

1) check in the transaction 'SXMB_MONI' on your SUS system , wether there are any errors in the XML message.

2) check in the transaction'SXMB_MONI' on your Xi system wether there are any errors in the XML message.

3) check the confirmation tab , on your R/3 purchase order to see wether there are any updates.

4) check the transaction ' WE05' on your R/3 system, wether there are any errors in the incoming IDOC message.

please ensure correct dates here , so that system shows the entries accordingly....

[Former Member · Accepted solution]

Thank you Khan, I am testing it, I'll check WE05 and keep you updated. My concern is, that this issue appears in isolates cases.

[Former Member · Accepted solution]

I have checked all points you mentioned, and all are ok. There is not error messages in monitor transactions, IDOCs are ok. But I realize in this instance, that the XML file/message is not being creating.

The issue focused is in SUS system, and for any reason when a vendor makes a confirmation it never goes to other systems throu XML message.

Thanks for yor help.

Edited by: Rodrigo Lopez on Oct 13, 2008 11:18 AM

[khan_voyalpadusman · Accepted solution]

please check for XML messages in SUS system wether they have gone in to error ---> if they are in to error, then xml message will not be send to XI system and so IDOC will not be created in R/3.

once you get the XML messages which have run in to error , get in to the details and find out the error message that has come up..

give me the error message and i will be able to help you further to resolve the issue..

[Former Member · Accepted solution]

Thanks Khan,

There is not XML message with or wothout error. Seems like process do not generate it.

I believe issue is before this step. All looks like confirmation was succefull, but not xml mesagge created, so confirmation is not replicated in R/3 or EBP systems.

[khan_voyalpadusman · Accepted solution]

hi,

do you see XML messages for the purchase order generated ? or not??

if the SUS system is not giving any error when you confirm the purchase order and send the response to R/3 , then xml message should always be generated...

do you see any history in the SUS purchase order (or) not??

please check once again in your system , sender interface should be --> PurchasOrderConfirmation_Out ...

for the XML message when the supplier confirms and sends the response to R/3 system..

[Former Member · Accepted solution]

HI,

I dont see XML message for this particular PO that we are having the issue.

There are XML messages for other POs those are ok.

Reading the history of the PO (BUS2230) in BBP_PD, I can see some warning regarding "delivery date is in the past" and some related tables have flaged the field DOC_INCOMPLETE. But these are warning messages so, I am not sure if it can be the issue. What do you think?

Thanks for your help!

[khan_voyalpadusman · Accepted solution]

warning messages should not be problem , they will not stop the xml message generation in the sus system..

get in to the details of the purchase order --> on the sus side UI --> and you can see place where there will be text

Requested Follow-On Documents .

what all do you see for the purchase order which you say is having problem..

and also check out the following -->

1) start transaction se37

2) type in BBP_PD_SUSPO_GETDETAIL

3) and execute the function module --> using F8

4) in the object id field > enter the sus purchase order number> and press F8

5) look for the table --> E_HEADER_REL

6) how many entries --> do you find there? --> look for second entry if there is --> specifially look for field --> OBJID_B.

7) that is the number of the purchase order response the sus system has send out...

let me know if the number is filled or not....

[Former Member · Accepted solution]

Hi Usman,

As mentioned, I do see the OBJID_B field populated when I run the FM.

But still the confirmation doesnot reach XI.

What could be the possible error or missing setup?

Thanks,

-Devi Swain

[Former Member]

Check in SM59 Tcode in XI and SRM to ensure that RFC coonnections are maintained correctly.

[Former Member]

Thank you Manu!. I ´ve already checked it. and connections are ok.