Debugging output types

Hi,
We can debug the processing program and routine in output type by setting them to execute with periodical jobs(instead of send immediately) and using RSNAST00 to run the unprocessed output.
How do we debug the change output program that we give in the first screen of the output type configuration? Any pointers to this would be very helpful. Thanks.
Regards,
Vijay

one tip,
the program in the output type need not necessarily be a sap script print program. The output type configuration is such that, it can accomodate 10-11 transmission mediums. Print is one of those mediums. I don't want to debug the print program, and hey putting a break point in the print program will not help debugging it. there's a different way to do it. I wanted to debug the change output program, which you can input in the first screen in the output type configuration.
Regards,
Vijay

Similar Messages

Unable to debug output type for purchase order

HI all,
In purchase order (ME21N) , i have a custom output type (ZSND) that send po to the user. I try to debug the program when the output is called. I put breakpoint in the custom program for the output ZSND. However, It did not stop at the breakpoint.
Can anyone tell me how I can debug the program ?
thanks
Joyce

Hello,
Try this:
1. Put the break-point.
2. Go to the transaction me22n --> go to mesaage --> click in your output type message click on further data --> put in dispatch time 'Send with aplication own transaction'
3. Go to transaction ME9F put your document and message --> a list with the document will appears --> choose one and process it --> then it will stop in the break-point.
Hope this will solve your problem.
Best Regards

New output type Shows Red color

Hi,
I have configured the new o/p type Zxxx , the Driver Program everything is configured,
but when i try to Print the the Document the status is red color even though the document gets printed.
Not able to figure out the error.
with rgds
Ranjith Singh

Hi Ranjith,
This is how I debug output type message related issues :
i) If you get red coloured message against the output type - Put the breakpoint in FORM ENTRY of your print program and check the RETCODE variable. Also check the sy-msgid, sy-msgno variable.
ii) If you get red coloured light after pressing messages button. These Messages are updated using 'NAST_PROTOCAL_UPDATE' fm. Put a breakpoint in the function module and find out the cause.
Regards
DPM

Debugging the program that will get triggered for a particular output type

Hi all,
I have one program,which will get triggered when a Sales order of type 'VOR' is created.Whenever 'VOR' order is created it will trigger the 'ZALT' output type.And this output type 'ZALT'has been configured to my program.This output type configuration has been set up by my functional consultant.
My problem is I created Sales order of type 'VOR'.But I want to debug my program,which has to be triggered because of that 'VOR' sales order type,which in turn triggers 'ZALT' output type and in turn triggers my program.
My problem is I created Sales order of type 'VOR' by keeping debugging point in my program.But it is not going to my program and simply displaying sales order has been saved.
So is the outtype has been configured properly?.Do I need to go to my functional consultant?Could anyone explain in this regard?
Rgds,
Balaji

Hi Balaji,
If possible, try to repeat the output in the output type messages screen of VA02 and change its dipatch time to '1'(Through further data). Now put the break point in the program assigned to output tye 'ZALT'(You can see this in the TNAPR table) and run the program RSNAST00 through SE38. The program will stop at the break point.
If its not possible to repeat the output and if you want to check it the first time the output type is processed, ask the functional consultant to change the dispatch time in the condition record that is being retrieved for proposing the output type to '1'. Now run RSNAST00. The program will stop at the breakpoint.
Thanks,
Vinay

Debugging routine for output type in purchase order

HI all,
I am unable to get breakpoint to stop at a custom requirement routine for a custom output type (ZSND) for purchase order.
I created routine 901 and explicitly add 'break userid' . In ME21N, it stops at the routine. In ME22N, it did not stop at the routine.
I like to it stop during ME22N. I tried adding the custom output in ME22N in Messages details, then save. It still did not stop at the custom routine. Can anyone pls shed lights how i can make it stop ? Or could it be that no output is generated during the ME22N changes, thus it would stop at that routine in ME22N ?
thanks
Joyce

Hello Joyce
The first output ZSND creates the ORDERS IDoc (ME21N). For this output type you obviously have assigned the VOFM condition (somewhere in the NACE transaction).
Changing the purchase order (ME22N) should create a different output type (-> ORDCHG IDoc). The first output ZSND must not be repeated (or it is defined to be set automatically only once).
Thus, there are two explanations for your observation:
(1) The output ZSND is not created a second time using ME22N
(2) The new output (-> ORDCHG) has not been assigned to the VOFM condition 901.
(1) you can test quite easily by adding the ZSND output manually in transaction ME22N.
(2) you need to check the output customizing.
Regards
Uwe

How to extract error message for each output type.

Hi All,
Need your advice on the problem that I have.
Expected Solution:
1. Create an extra column for displaying header output error message from VF02 into a report program.
Steps that i have did:
1. Go to transaction VF02.
2. Enter a billing document number.
3. Hit enter. Click "Goto" > Header> Output
4. Click on the status that is red colour. Click on "processing log".
5. Press "F1" on the red colour message type. (Found out that it is a structure).
Need your advice on the question that I have:
1) How do we know that which "not successfully" process output type belong to which error message class?

Hi Brad Bohn,
Thanks for your advice. I am so sorry about that. Thanks so much for your advice. And i have follow your advices and steps given by you. Appreciate it very much.
But for this issue about how to extract message for each output type. I have follow your steps by using SE30 to trace VF03 and I managed to found out that they are using this function module "WFMC_PROTOCOL_SHOW". Need your advice on this, how do we know each different output type with different error message is pulled from?
From my further research and in depth debugging into this function module, i manage to find this global internal table "PROTO_TAB" which stores all the text messages for each output. How does this internal table is populated?
Thanks in advance.
Regards
Shawn

VL02N Output type issue.

Hi,
When I execute the tcode VL02N for any output type (ZEU5) for print preview and external mail then it is giving error that "Output could not be issued".
I have also checked the config of NACE , it seems to be ok.
So what are the other possibilities of this error.
Thanking you in advance,
Regards,
Vikram

Configuration of NACE does not make all the difference. The only way to come to the solution is to debug from point when button is clicked for print preview or etc.
Possible reasons may be there calling program before making a call to script or smartform encountering a problem. It may be that program is not able to get the desired data correctly from the tables or some other problem(Mainly due to subrc not coming to be 0).
Apart from this even if call is made successfully to the form but inside there could be problem like using command in smartform.
Thanks,
Mark

OUTPUT TYPES FOR SALE ORDER(VA01)

Hi All,
When i create a sale order, the data can be downloaded thru output type BA00 & standard program RSNASTED into SAPScript, but i wanted to download it to internal table. Can u please tell me the changes to be made after copying the standard program into Z... Program.

Hello Rafi,
Better U debug the report. Since the data will be in the internal table, if it is downloaded to the Script. So u no need to copy and make the changes.
Vasanth

Dumps while using output types

Hi,
We are to create a PO by giving a output type ZPO2 in the sales order. For this we have configured in NACE the ZPO2 output type with medium as 8 (special function). In NACE we have given the Z program name and the form name (Perform in the Z program).
Now when we give the output type in the sales order and then while debugging we find that the Z program and the form given in NACE is called.
But however when we check the sales order again in TCode VA02 there is a popup mentioning that the update was terminated. In ST22 there are 2 dumps.
1) One with the error DYNPRO_SEND_IN_BACKGROUND and the description in the dump is
The current ABAP program "RSNAST00" had to be terminated because one of the statements could not be executed.
The termination occurred in line 910 of the source code of the (Include) program "RSNAST00"
2) The other dump mentions Too many parameters specified with PERFORM.
In a subroutine call, there were more parameters than in the routine definition.
Error in ABAP application program.
The current ABAP program "RSNAST00" had to be terminated because one of the statements could not be executed.
The termination occurred in line 910 of the source code of the (Include) program "RSNAST00"
In both the cases the termination occurs on:
NAST = TEMP_NAST
Please help me understand what is wrong and how can it be rectified.
Thanks
Mick

Hi Mick James,
About First Error..
Check out there is an Enhancement Point there in program RSNAST00
ENHANCEMENT-POINT OBJEKT_SPERREN SPOTS ES_RSNAST00 STATIC
Check the code in this Enhancement Point...
You must be executing some objects or FMs etc which can not be run in Background because it require SAP GUI
And another You must be passing more parameters in Subroutine while calling it ... Check out the defination of Subroutine and number of parameters you are passing...
Hope it will solve your problem..
Thanks & Regards
ilesh 24x7
ilesh Nandaniya

Program name if no output type for dunning smartform

Hello Experts,
I want to know if smart form is not associated with any output type then how can I know which program is calling the smartform. I checked out in TNAPR with the smartform parameter value and system did not returns any hits. It means smartform is not associated with any output message type.
I am working with a dunning smart form where I need to make some changes, Transaction F150 displays the form print preview(One can also print from the transaction), But I have no idea which program is actually calling the smartform.
Secondly I made some changes in the text element but when through F150 I again viewed the form display, some thing I deleted from the text element still appearing in the preint preview. Could anyone throw some light on this and guide me.
secondly how to put breakpoint in the smartform, Normally in abap report you just press ctrl+shift and f12 but in breakpoint it is not applied.
Thanks,
Mark

FI Forms will not save under TNAPR table
FI Form names and Program Try to use below tables :
Tables : T001F or TTXFP
There is no output types for FI Forms,
Check the below link :
http://help.sap.com/saphelp_erp2004/helpdata/en/15/8c2239c2af4a04e10000000a11405a/frameset.htm
Path for see form name and print program - Dunning
path for configuration is :
SPRO
FInancial Accounting->Contract Accounts Receivable and Payable->Business Transactions->Dunning Notices.
Just goto SMARTFORMS Transaction -> use smartform name -> execute smartform -> it will go SE37 -> click on display -> here you can set up break point.
or you can use print program to setup debugging.
Now run F150 Transaction -> here you are able to see debugging mode
Thanks
Seshu

Add output type in requirements for purchase order

Hi,
In a changed purchase order (ME22N), based on business condition (eg: tot po > $100,000), then it should trigger an email output which will send the PO to the user. In output procedure for EF, control RMBEF1, there is requirement 101 (reprint) as an example. It has:
Loop at xnast where kschl = komt1-kschl and objky = msg_objky and vstat eq 0.
Endloop.
Here it seems user manually add a new condition record for ZSND so the loop will work.
However, i need to create an output record for ZSND before i can resend the email on ME22N. Do you think having a new requirement here will enable me to create a new output record for ZSND ? IF the PO is more than $100,000, then i need to create an output type ZSND so it will re-send the PO. User will not manually create the PO.
Pls provide your suggestions.
thanks
joyce

It's difficult to say without seeing how you have it configured, but the breakpoint should be triggered if the requirement is triggered (update debugging not required). Go back to a fresh PO and use Goto -> Determination Analysis from the output screen to view the analysis. This should give you a clue as to what happened. If the output was already issued and you don't have it flagged for 'multiple-issuing' then it won't be triggered again in change mode. Keep in mind that requirement routines do not create outputs; they simply allow them to propose or stop them from proposing based on the criteria in the code. You can access the EKPO data in memory using a field symbol for '(SAPLMEPO)EKPO' (if applicable, check whether this works in BAPI mode - I don't remember) or you can use the message determination user exit in RVCOMFZZ to put the value in KOMKBEA for direct access.
OK, see my answer to your other post - it seems that you added the output manually - that doesn't work...
Edited by: Brad Bohn on May 13, 2010 2:48 PM

VL02N - Output type TRM

Hi,
Does any one know how to attach a WWI report (tremcard) to output type TRM ?
Thanks,
Michal.

Configuration of NACE does not make all the difference. The only way to come to the solution is to debug from point when button is clicked for print preview or etc.
Possible reasons may be there calling program before making a call to script or smartform encountering a problem. It may be that program is not able to get the desired data correctly from the tables or some other problem(Mainly due to subrc not coming to be 0).
Apart from this even if call is made successfully to the form but inside there could be problem like using command in smartform.
Thanks,
Mark

Attach output type to invoice

Hi All,
Is there any function module to attach the output type to the header of billing document no. inspite of running the BDC for that.
Waiting for your reply.
Thanks in advanced.
Regards,
Dheeraj

Check
RV_MESSAGES_MAINTENANCE
RV_MESSAGES_GET
RV_MESSAGES_MODIFY
Please debug the standard code after clicking the save button, you will get the idea.

Output type determination program or fuction module.

HI Gurus,
I'm looking for the standard program or function mudule that the SAP ERP are using for the determination of invoice output type.
I want to debug why is not accepting some fields.
Know anyone wich one is it?
Thank you in advance.
Abel

Dear Abel,
o        Program: RSNASTED
o        Form routine: EDI_PROCESSING
o        Procedure: V10000
For Complete Information, refer:
[Invoice Message Control Configuration|http://www.erpgenie.com/sap/sapedi/messagecontrol.htm]
I hope, this would be really helpful, to you.
Best Regards,
Amit

Output Type Determination

Hi experts,
I have a requirement wherein if an EDI invoice output type is selected during the creation of the billing document, then all the remaining output types below that should not be selected. Please find below the screen shot of the output procedure used. Whether a customer is relevant for EDI output or not is based on different values provided in different fields and the business do not want to follow that approach.
Please provide suggestions/pointers to achieve this requirement.
Thank you,
Som

Hi
In my opinion yes. In table NAST there will be a record ofr ZINV. Taking the VOFM 101 as a template (your EDI output is ZINV), maybe, your VOFM 901
PERFORM KOBED_062.     "call vofm 62
LOOP AT XNAST WHERE KSCHL EQ 'ZINV' AND
                                        OBJKY EQ MSG_OBJKY   AND
                                       AKTIV EQ SPACE       AND
                                       VSTAT EQ '0'.
    EXIT.
ENDLOOP.
IF sy-subrc = 0. "it was found
sy-subrc = 4.     "output not created
ELSE.
su-subrc = 0.
ENDIF.
Create your VOFM (remember the note I told you in my first answer), and change the VOFM 901 for the other output types different to EDI.
Although it's for pricing, see also SAP Note 156230 - Requirements: What is permitted, what is not?.
After, debug it and fit to your requirements. During the debugging, check how XNAST is populated.
I hope this helps you
Regards
Eduardo

Debugging output types

Similar Messages

Maybe you are looking for