Debug Issue

[Former Member]

Hi,

Task: I am trying to debug BAPI/FM to see when exactly IDOC is getting triggered.

Technic: ALE Distribution model setup

when I Confirm TO its triggering IDOC(IDOC Message Type SHP_IBDLV_CONFIRM_DECENTRAL underlying BAPI is BAPI_INB_DELIVERY_CONFIRM_DEC )

Problem facing : when I do Confirm TO i am keeping break point in BAPI_INB_DELIVERY_CONFIRM_DEC and MASTER_IDOC_DISTRIBUTE both the FM/BAPI but not stopping.

Please help me to debug this.

Thanks

Sarath

[paul_bakker2]

Hi,

Have you tried setting an external breakpoint?

The icon for this is the little stop-sign next to the session breakpoint (in SE37).

This may work if MASTER_IDOC_DISTRIBUTE is being called in another session.

cheers

Paul

[Former Member]

Paul, I have already tried that, but didn't stop in neither of BAPI or FM.

[paul_bakker2]

Hi,

OK, I'm a little rusty on how IDocs are generated, but maybe it is being done under another userid.

Try running ST05 during this process, and check the log to see which userid actually creates the IDoc.

If it is, say, WF-BATCH, then set an exernal breakpoint for that user.

good luck!

Paul

[former_member214857]

Hi Sarath

Reading this seems that system is running FM in Update or Background mode, or user set for this breakpoint is not set for current user when running the process.

One aprroach is run this process in trace mode to colect what happened in SE30

Best regards

[Harsh_Bansal]

Hi Sarath,

Switch on the System and Update Debugging.

I think that will solve your problem.

Regards,

Harsh Bansal

[Former Member]

Hi,

The user id through which Idoc created must be different from your id.

To debug it through your id. Do the steps mentioned below.

Change the output mode of your message type from "Transfer Immediately" to "Collect Idocs" in WE20.

Hence when you confirm, your Idoc will get created and it will be in waiting status.

Then keep the user breakpoint in your BAPI, and process it through BD87 or RSEOUT00 program.

It will stop and check.

Cheers,

Raja.D

[Former Member]

Hi Thanks for all the suggissions but nothing worked. Again I am trying to find when exactley IDOC is getting triggered

Just to check I have deleted BAPI SHP_IBDLV_CONFIRM_DECENTRAL (underlying BAPI BAPI_INB_DELIVERY_CONFIRM_DEC) in ALE distribution Model.

Below is the Error message I got, hope you can guide me in correct path for debugging to find out when exactley IDOC is getting triggered.

____________________________________________________________________

No recipient could be determined for object BUS2015 method CONFIRMDECENTRAL

Message no. VLBAPI005

Diagnosis

The distribution model for decentralized Warehouse Management System

(decentralized WMS) is not set up correctly with reference to the

recipient determination for object BUS2015 method CONFIRMDECENTRAL. This

means that the system cannot determine a recipient for object BUS2015

method CONFIRMDECENTRAL.

System Response

The system reacts by issuing a warning message, or by terminating

processing in critical situations. If a warning message is issued,

changes are made to the object. If processing is terminated, the object

retains its original status.

Procedure

Inform your system administrator. After the distribution model has been

corrected with regards to recipient determination for object BUS2015

method CONFIRMDECENTRAL, you can save the document and then restart

distribution or repeat the workstep that was canceled.

Procedure for System Administration

The system attempts to determine a recipient for object BUS2015 method

CONFIRMDECENTRAL using the filter object types WHSE_NO. The system

cannot determine a recipient. Define a filter object type WHSE_NO with a

valid filter value for recipient determination for object BUS2015 method

CONFIRMDECENTRAL.

[Clemenss]

Hi sarath,

IDocs are processed in background task by default. But you can load the IDoc with WE19 test tool and then use DEBUG to process. Here all your breakpoints work. WE 19 will create a copy of your IDoc and process it synchronous in foreground.

So please don't get confused if you have a new IDoc number then.

Regards

Clemens

[Former Member]

Guys,

I am able to reslove this myslef by going through transaction code BDBG.

thanks for your responses.

sarath

[Former Member]

Hi Sarath,

Could you elaborate how you debugged the bapi BAPI_INB_DELIVERY_CONFIRM_DEC? I am facing the same issue. Whenever the IBDN is confirmed, the idoc is automatically generated. And it will not stop at any break point that I put in the bapi.

Thanks

Linda

[Former Member]

OK. I was able to debug by setting 'allow update debug', and it did stop at function module ALE_INB_DELIVERY_CONFIRM_DEC.

Now I have new question, I thought that user exit EXIT_SAPLV50I_002 should be triggered when outbound idoc is created. But it was not called at all. I did all the cmod stuff to activate it. But it will not stop.

Can anyone please help?