Skip to Content
author's profile photo Former Member
Former Member

Debugging FM IDOC_OUTPUT_DELVRY

Hi There.

I am using process code DELV for functional model IDOC_OUTPUT_DELVRY in partner profile for generating an output idoc (I have created new idoc type with new segments for message type delvery05.)

The problem is that while putting breakpoint in FM IDOC_OUTPUT_DELVRY and retriggering the output through VL02N the system is not stopping at breakpoint . It is not possible that this FM is not being used as if I remove the FM IDOC_OUTPUT_DELVRY from we20 it will not process the idoc.

Could you suggest me the reason why my debugging is not working in this case. FM is definitly activated.

Regards

-Manu

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

4 Answers

  • Posted on Feb 06, 2009 at 12:47 PM

    Hi Manu,

    Try debugging the idoc through we19.

    Give the idoc number which you want to debug in we19 and execute.

    In the next screen test the inbound idoc through a function module ( ie, click on the inbound function module button). Give ur FM name there and check the check box "Call in debugging mode" to debugg.

    Regards,

    Soumya.

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Feb 06, 2009 at 01:31 PM

    Hi,

    Try like this

    goto VL02N->IN THE menu select->EXtras->Delivery output->header->Now specify the output type, meduim as ALE and then in the application tool bar select Futher data and select (send with application own transaction) and save.

    before that put break point in the program RSEOUT00 and also in ur function module...I think it will stop now.

    Check and let me know..

    Regards,

    Nagaraj

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Feb 06, 2009 at 01:38 PM

    Hi,

    Just before saving the document, put /h in the command field. Now press 'Save' button. You will be in debug mode, there Goto the menu Settings -->System Debugging and press F8 . The debugger will stop at the next break point ( i.e in your function module )

    regards,

    Advait

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Dec 11, 2015 at 05:27 PM

    Hi,

    You place a break point in subroutine CALL_BADI_SAVE_DOC_PREP/USEREXIT_SAVE_DOCUMENT_PREPARE of program SAPMV50A and enter in debugging mode, if not in New Debugger Mode, switch to New Debugger from Classic Debugger, Enable Update Debugging.

    Press F8 until it starts/enters in to Update Debugger mode, here press F5 until you reach statement like PERFORM (VBFUNC) IN PROGRAM (TFDIR-PNAME) USING VBID. Press F5 again, it would enter in to function module already set for processing in update task. If the function module is not IDOC_OUTPUT_DELVRY, place a breakpoint at function module IDOC_OUTPUT_DELVRY. Once in function module IDOC_OUTPUT_DELVRY, to determine any Customer exit considering CALL CUSTOMER-FUNCTION statement.

    To Determine the customer exits / projects, use MOD* (i.e. like MODSAP, MODATTR, etc) tables.

    Best Regards,

    Yogi

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.