ALE/IDOC on ABAP Trial Version: 53 but no actual update ???????

Question

After installing ABAP Trial Version NW7 on my laptop, I copied ref client 000 to two clients (100 and 200), and set up a person business partner on each client with parnter number 1.
I then delegated BUS1006 on system 100  so that I had a YBUS1008 object with the same methods as BUS1006.
I then went thru the usual rhythm (SALE, WE20, SM59 to get the ALE stuff set up, and then used BDBG to generate my BAPI-ALE interface.
Everything went perfectly: I used SE37 on the sending system to execute the outbound function module with some changed data, and then used SALE to dispatch the IDOC that was created.  Then on the input side, I used BD87 to process the IDOC.
The result of all this was a final IDOC status of "53" indicating successful posting of an application document.
But when I go into BUP2, the data for the business partner isn't actually changed.
If the IDOC posts with a "53", shouldn't I see the actual changed data in the business partner on the receiving system?
I'm sure I'm missing something simple here, but I'm not sure what it is.
Thanks for any help anyone can provide.
djh

Answer 1

Hi Atish -
Thanks for taking the time to reply.
Yes, the status 53 is on the receiving system, and I've used WE19 to test my inbound function module ZIDOC_INPUT_YBUS1006 (this is the one that BDBG generated.)   In debugging mode in WE19, I see the function calls returning sy-subrc 0 for at least two levels down.  In particular, ZIDOC_INPUT_YBUS100 calls BAPI_BUPA_ADDRESS_CHANGE and BAPI_BUPA_ADDRESS_CHANGE calls BUPA_ADDRESS_CHANGE, and both these calls return sy-subrc = 0.
But I haven't gone all the way down to the actual database update modules - maybe I have to dig deeper.  I stopped when I saw that this line
MOVE-CORRESPONDING is_address TO lt_bapiad2vl.
was moving the data from the IDOC in BUPA_ADDRESS_CHANGE.
Also, one other thing that's puzzling me - when I call the inbound function module in WE19 in debugging mode, and then switch to "update debugging", I don't see code executing.  It just goes to completion and comes back with a message saying the IDOC was saved and processed successfully by the function module.
If the system is really doing an update, shouldn't I see some code executing if I turn on "update debugging" once I'm in the debugger on the function module in WE19 ????
Also, I'm assuming that if the IDOC gets a status 53 with a message saying "application document posted", then the IDOC data must be correct and the inbound function module must have processed the IDOC correctly.  Isn't this what a 53 means?
Anyway, thanks again for taking the time ... I'll post back if I see anything odd as I debug deeper.
Regards
djh