Debug PAYEXT Outoing Idoc

Hi Everyone,
I have an issue to look into. There is an Outgoing Idoc (Msg type PAYEXT and Basic Type PEXR2002). Some of the segments are missing some data and I have to find out why. In the event module configurations we have defined a Z function module which is responsible for changing data in this Idoc. I have to debug this Idoc now to find out why some segments are not populated properly.
I would be grateful to all of you if you can let me know how to stop at break point.
Thanks a lot!!
SA

Hi,
1) put an explicity break point in your function module "break <userid>".
2) Go to transaction with generates the IDOC
3) Before saving the transaction activate debugging using '/h' in command.
4) Save the transaction
5) When the system is in debug mode, Select the menu option "Settings -> Update debugging".
     In the message bar the message "Update debugging switched on" will appear.  Press F8 to continue
     execution.  Processing will stop at the function module where you have created the explicity
     break point.
Regards
Vinod

Similar Messages

  • Where to put break point when debugging the inbound IDOC processing

    Hi, Dear Experts,
    If IDOC has error and want to debug, which program or function module  to put break point when debugging the inbound IDOC processing
    Thank you so much!
    Helen

    It depends on if you have the custom FM or standard FM...Is it MM invoice or FI invoice? ... You can find out your FM by going to partner profile (WE20) for your sender partner and partner function.. Drill down to your partner and the message type and find the inbound process code.. Double clicking on the process code will help you find the FM...
    If you don't have access to WE20, You can also put BP into any of the IDOC_INPUT_INVOIC* FM and see if it is getting triggered (assuming your IDOC is standard FM)...

  • How to Debug the Outbound IDOC

    Dear SDN Members,
    How to debug the outbound idoc please.
    Thanks in advance
    Yerukala Setty

    Hi,
       IDocs are processed by a function module, which are mapped against in table EDIFCT. When you process an IDoc in transaction BD87 you can put a breakpoint in the function module and it will stop there.For outbound processing it depends on which program is sending the IDoc. For transactional data like purchase orders, the IDoc is created via RSNAST00 which in turn calls a function module assigned to the processing code (BD41).
    Thanks,
    Asit Purbey.

  • Reg :How can we debug in ale/idoc

    in ale/idoc  where can we put the break points , and how can we know is it received correctly with out we05.

    Hi,
                  WE19 tcode is the Test tool for IDOC. You can put a break-point in the correspond inboound or outbound function module for that IDOC and debug it.
    Regards,
    Vishnu Priya

  • How to generate PAYEXT (PEXR2002) IDOC with many invoices for same vendor

    Hello,
    We are implementing the IDOC payment processing through transaction F110.  The first test we ran using multiple items for the same vendor created an IDOC with multiple E1IDPU1 segments for each invoice.  We then configured a second bank and ran the test again.  This time the multiple invoices for the same vendor generated a seperate IDOC.
    Does anyone know where I should start looking to figure out what I did wrong?  We are hoping to generate 1 IDOC for all invoices for the same vendor.
    Thanks,
    Brian

    Hello,
    May I know how or what are the steps you did to create multiple invoices and generate multiple idocs for the same vendor? I have a requirement to generate multiple payext idoc for a single vendor.
    Please advise. Thank you very much!

  • PAYEXT - PEXR2002 Idoc

    I am generating the Idoc through F110.
    Few of the mandatory segments from the bank prospective are not populated.
    These are : E2IDT02 / E2EDKA1003 (Ordering Party)  and
    EXTPAYM field of segment E2IDKU3002
    Any idea what data should be maintained and where?
    At the Bank Level or Invoce Level or the Vendor Level or anything else?
    Help would be appretiated.

    Hello,
    May I know how or what are the steps you did to create multiple invoices and generate multiple idocs for the same vendor? I have a requirement to generate multiple payext idoc for a single vendor.
    Please advise. Thank you very much!

  • Debug billing document IDOC

    Hi,
    I need to change the IDOC data for the segment E1EDK01 for the billing document putput generated via transaction VF02.
    However after I make the changes in the include ZXEDFU02,I'm unable to debug my code.
    Can soemone please let me know how to debug this code in include ZXEDFU02?

    How did you set the breakpoint? If the IDOC is processed by another user, you have to use external breakpoints. If your user is processing it, you may also enter debugging mode and set a breakpoint at the include using the menu.

  • To seperate PAYEXT outbound IDoc according to message type

    Gurus
    This is business scenario. We are using four different flavours of payment methods. when exectuing F110 for each payment method,Program RFFOEDI1 generates IDOC. This IDOC are send to EDI team who then sends that as EDI820 to bank.
    The payment method used are populated in Detail record field of IDOC . But EDI team wants that to be in Control record of IDOC .
    We are using PEXR2002 and message type is PAYEXT . this is an outbound IDOC .
    I want to know whether Message code given for PAYEXT and how to link that with Payment Method?
    Is it possible to add segement in control record  and to map that to each payment method?
    Your reply would highly help me to slove out the problem
    Thanks
    Auroar

    Hi Auro,
    You use use EDI_DC-SNDSAD field, currently this field is used no where.
    If you not sure where to see double control record and click address info tab
    you can use either field receiver or sender.
    For testing use WE19 transaction and pass your paymethod to following field
    and then inform to EDI Mapper that your sending paymethod in this field.
    For them this field is very easy to grab.
    Let me know if you any concern.
    Thanks,
    Narayan

  • Debug the Outbound IDoc

    Hi,
    I have a outbound IDoc.
    I would like to reprocess the same and test the FM.
    I am going through the Tcode :WE19.
    put the IDOC : XXX in the exisiting IDoc field. Execute.
    I get to see the IDoc structure and the data.Then i click on the "standard outbound processing".
    I would like to get into the FM and debug it.
    But once i press "standard outbound processing".
    It is giving a pop up which says "start outbound processing of file immediately"
    No of IDoc's to be generated.
    Receiver port
    Port type
    output file
    etc.
    But i would like to get into the debug mode.
    Pls advise.

    Set ur Break point at your code
    now come to VA02 Transaction and use order number.
    click on enter
    GOTO->HEADER->OUTPUT
    Give the output type and print medium should be 6(EDI) or A( ALE)
    Click on Further data and select->select send with periodically scheduled job and save it.
    Now Come to SE38 and use RSNAST00
    Output Application : V1
    Object key - order Number ( 10 digit)
    Output type - BA00( SAP Standard)
    Transmission medium = 6(EDI) ,A(ALE)
    Now it will stop at your code.
    Reward Points if it is helpful
    Thanks
    Seshu
    Message was edited by:
            Seshu Maramreddy
    Message was edited by:
            Seshu Maramreddy

  • Best Way to Debug an Inbound IDoc

    Hi
    As previous posts suggest I am having trouble with IDoc PORDCR101 message type pordcr   bapi_po_create
    i input
    comp code 3000
    doctype      NB
    vender        58121
    purchorg     3000
    purchgrp     000
    doc date     01112007
    item           0010
    material     scw1212
    qty            0001000.000
    currency    USD
    scheduleitem  0010
    deldate           01/18/2007
    qty                 0001000
    i put this exact info in se37 with bapi_po_create
    I can successfully create a new po
    now i try to do the same thing in we19 standard inbound
    using idoc pordcr101
    each time i try i get status 51 enter purchasing org
    what is the best way to debug this thing so that i can see what is going on
    i am entering the purchasing org and for some reason it does not see it
    what can i do in the way of debugging?????
    HELP!!!!!!

    Janice,
    conversion-exit routines are used when the contents of a screen field(SAP GUI) are converted from display format to SAP-internal format and vice versa.
    --Archana

  • Debugging of otbound IDoc with we19

    Hi Experts,
    i am using we19 tcode to test outbound idoc
    How to debug outbound iDoc using we19.
    Thanks.

    HI,
    Below are the steps to be followed for debugging outbound IDOC.
    1) Put the breakpoint in the FM
    2) Goto the application document repeat the output and save.
    3)Goto program RSNAST00 give the document number and execute.
    Regards,
    Sharath

  • Debugging EDI output (IDOC creation) for purchase order...

    Hi,
    We have a EDI output type defined for Purchase order. When I go to Messages tab in ME22N transaction and repeat the EDI output and save it, it creates a IDOC which I can see using transaction WE02.
    Now the problem is there is a user exit which I know gets triggered, when the IDOC is created for this PO. When we do some changes in this user exit, I see those changes are reflected when new IDOC is created. But if I put breakpoint, and do repeat output -> save, the debugger does not stop there.
    Is there is some technique I can see the breakpoint stoppage in user exit for IDOC creation during EDI output for Purchase order ?
    Regards,
    Rajesh

    Hi
    Youc can set the output Peridoically (After Giving the output type, set the furthere data as periodic).
    Save.
    Set the break point in your user exit.
    Go to se 38 -> Run RSNAST00,
    Give the object id (Your PO #)
    Give the output type  and execute, the control will stop at break point.
    Regards,
    Baburaj

  • Payment requests created from In-House Cash - error with PAYEXT IDOC

    Hello -
    I am getting getting a '51' error with my inboud PAYEXT IDOC and the payment request cannot be created and the IDOC error is : Error creating the payment requests - no valid payment method available.  
    I have checked the Route process config in IHC and it looks good (or I think so).  I then checked the IHC config: Set Up of payment request for inbound IDOC in FI and am wondering about the Processing Parameters set up.  In this config, I see 2 payment methods field (Payment Method for This Payment) and (List of the Payment Methods to be Considered).   Can somebody tell me what's the difference between these two fields and since my payment method is not in the List of PM to be considered, could that be causing my erorr?
    Any guidance would greatly be appreciated.
    Thanks
    Becky

    Hi Odaiah
    I am in ECC 5.0 and when I view IMG activity IHC_VC_INB_CUST, there's a field called:
    Payment Method for This Payment(Payment method used to settle open items)
    and another field called List of the Payment Methods to be Considered.
    The invoice was paid via payment method 'W' and in our system, we are using IHC to make payments on behalf.  So after running F110 for payment method 'W', the IDOC gets created and sent to IHC to process.  IHC will then create the payment request (IDOC PAYEXT) which will then get process by F111.  Since the IDOC is failing, the payment request is not getting created.   You mentioned to get an ABAPer to throw in debug, I would love to but does not know the program that this process is running through. I tried putting it in debug from WE02 (IDOC processing) but with no success.
    Becky

  • OUTBOUND IDOC DEBUGGING

    I have Output type  defined for the application V3
    i.e meant for Billing.and the output type is custom development with name ZD00 for invoice-Bill to.
    This output type is defined for edi processing.
    Now the problem is when invoice is created and this
    outputtype is selected the quantity field in idoc and invoice differs.just get double in idoc.but if the same output is fired again data in idoc gets corrected.now i want to debug the idoc outbound processing.what i did i run the transaction we41 and find the process code  and find the function module that is running in the background for collection of data of invoice and
    filling the idoc.but but but the problem is i put break point in the function module to check the value at run time but this is not triggered . iam confused tell me how to debug the outbound idoc.
    Help me out i will be waiting for the response.

    Hi,
    You can use the Update Debugging. If you know the prognam name/function module of your source code, upon saving your document, a new screen will pop up if the Update Debugging mode is on. From this, you can then hit F8 to stop on your break-point.
    Let me know if you need further help.
    Thanks,
    Eric

  • How to debug outbound Idoc function module for invoice

    I have to debug the outbound IDOC function module and UserExit for invoice message type INVOIC, process code SD09, function module is IDOC_OUTPUT_INVOIC and user exit for the function module LVEDF001.
    I tried putting the break point in function module IDOC_OUTPUT_INVOIC and recreate the IDOC using WE19 but it creates the idoc but does not stop at the break point. I have also tried generation of idoc through VF02. It again creates the idoc but does not stop at the function module.
    Please let me know if I am missing any thing and not doing it right.
    Appreciate your help.
    Rohit

    Hi Ali,
        I faced the same problem. Thing is the break point is not getting triggered when i ran tha IDOC through WE19.
    What i have done is i created a project for my exit in CMOD and kept some junk code in the exit and executed it through BD21. Then the Break point got triggered. See if it works.
    Regards,
    Uday S.

Maybe you are looking for