Debug PO print program

Hi friends.
I am trying to debug PO print program, even after putting an endless loop.. it's not going to debug mode. Please help
Thanks
Lakhbir

Lakhbir,
There are several ways to keep breakpoints.
1. Get the Layout name. Go in SE71, give layout/form name and enter in display mode. Use menu path Form Check --> Texts. It will display all associated driver programs. If you know your driver program name, place a breakpoint from SE38. Usually there should be a FORM ENTRY routine call.
2. Go to program RSNAST00 -search for
    PERFORM (TNAPR-RONAM) IN PROGRAM (TNAPR-PGNAM) USING RETURNCODE
                                                         US_SCREEN
                                                         IF FOUND.
PGNAM is program name, RONAM is Name of routine to be called up in the processing program.
Keep a break point. When you print from ME23N, control will come to this place in debugging mode.
Check form name, program name. Go to program and associated form and keep breakpoint.
Hope this will help you.

Similar Messages

Debugging MEDRUCK print program

Hi All,
How can I debug SAPFM06P (print program for MEDRUCK) ???
Thanks
Message was edited by:
sapsudha rao

Hi Sudheer,
I've tried what you said...but while saving PO changes or while generating print view ..... control is not stopping at break-point... do I need to make any further settings???
Thanks in advance..

Debug print program

Hi,
I have created a output type for the packing list inside vl02n i.e.
vl02n->pack->Extra->Output. Then, i also tried to debug my print program by placing a break point in it. But, the system did not stop in the breakpoint during the execution. Is there any alternative to debug it??
Regards,
Kit

Hi
Keep a Break point in the driver program and debug it.
It's similar to the debugging of a ordinary report.
Keep some break points in the program code and execute the SF output using MB02 then it will stop at the break point.
SCRIPT
There are 2 separate kinds of debugging available when you try to debug scripts.
1. Debugging the print program : This is the normal debugging we do for our report programs.
2. Debugging the script itself : You Can debug a SAP Script by activating debugger in two ways:
a .In SE71->Menu->Utilities->Activate Debugger, then debugger will be get activated and when your print program is executing Script Debugger will be in active and you can proceed with your debugging.
b. Goto se38-> RSTXDBUG ->Execute this same as going thru in se71-> Menu, now debugger will be activated.
refer to the link below
http://www.howforge.com/how-to-debugging-sapscript-form

Print program debugging

Hi all,
I've copied standard MEDRUCK (form ) & SAPFM06P (print program) to ZMEDRUCK & ZSAPFM06P and I've made changes to settings in NACE as well.
If I made any changes in ZMEDRUCK , I'm getting changed output.. everything is fine
Finally my problem is how can I debug print program.. some body (SDN forms ) suggested me to set break points in include ZM06PF02 ..but control is not at all stopping..
Could any one suggest me how can I debug print program..please!!!!!

hi
good
SCRIPT
There are 2 separate kinds of debugging available when you try to debug scripts.
1. Debugging the print program : This is the normal debugging we do for our report programs.
2. Debugging the script itself : You Can debug a SAP Script by activating debugger in two ways:
a .In SE71->Menu->Utilities->Activate Debugger, then debugger will be get activated and when your print program is executing Script Debugger will be in active and you can proceed with your debugging.
b. Goto se38-> RSTXDBUG ->Execute this same as going thru in se71-> Menu, now debugger will be activated.
refer to the link below
http://www.howforge.com/how-to-debugging-sapscript-form
reward point if helpful.
thanks
mrutyun^

Finding Program for triggering Print Program (MIGO - Goods Receipt)

Hi all,
Currently, I have developed customized print program and SMARTFORMS for Goods Receipt via MIGO, with output type ZZGR.
Typically, this is a inter-plant transfer, where Plant A will issue a Delivery Order to Plant B, and Plant B will post goods receipt via MIGO (Movement Type 101), using Delivery Order number. As soon as the Material Document is posted, the SMARTFORMS shall be triggered by customized print program, in order to print out the goods receipt document upon material doc posted.
The config for output determination (via TCODE NACE) for goods receipt is configured. I have tested post a goods receipt using Delivery Order, and Material Document is posted successfully. However, I got a message from SAP Inbox (Businees Area), saying that my Material Document having an update error, and the root cause is specifically from calling Function Module to trigger Smartforms in the print program. From tcode ST22, I realized that the error is due to empty parameter being passed to the function module (where the parameter is required field for further processing in Smartform).
In order to rectify why empty parameter is bieng passed, I will have to debug the print program, after GR posted from MIGO. Therefore, can someone shed some lights on how to perform a debugging process, or any standard sap program involved, as I understand that the print program is triggered (in background) after GR posted?
Also, can I know why the Material Document will not be committed to MKPF table after GR posted, is it due to the update error from the above mentioned?
Many thanks.
Best regards,
Patrick
P/S: I'm using SAP ECC6.

Actually, this print program is being triggered in the update processing.
Put a breakpoint in your driver program.
In MIGO, before pressing the SAVE button start debugging.
Press the SAVE button.
Start the update debugging by Settings > Update Debugging.
As soon as you continue in debugging, it would open another debugging session for the Update debugging. You can press continue and it would stop at your breakpoint.
Regards,
Naimesh Patel

Picking output not hitting breakpoint in print program

Hi Guys,
I have an o/p type ZK00, I need to debug the print program and the script for it. I have placed a breakpoint in the print program at the designated routine in TNAPR (Entry). Now when I try to save the delivery I expect it to hit the code but it isnt. It creates another line in the Extras --> Picking o/p and created a spool as well! Wonder how is it doing that when its not going through the program or the script.
Breakpoints on the form and the driver are in the same client.
Thanks for reading
Regards
Sameer

You need to activate the Update Debugging in order to stop it to your break point.
Before saving Delivery, start debugging and Settings > Update Debugging.
Regards,
Naimesh Patel

How to debug BDC , Dialog program and Script

Hi all,
Please let me know, how to debug BDC , Dialog program and Script
Thanks&Regards
Devi

SCRIPT DEBUGGING
When we want to debug the SAPSCRIPT, we need to first activate the debugger, we have 2 ways to activate the Debugger.
1) Execute the program RSTXDBUG
2) Go to SE71, from the initial screen enter the form name and press Utilities --> Activate Debugger
When we are in the Debug screen,
3.1) F5 will be debug filed by field, that means if a single line is having 5 fields, if we press the F5 this will do field by field,
3.2) F6 will be line by line, that means when we press the F6, it will debug the line and it will go to the next line. F7 also do the same way
3.3) F8 will be very useful when we have any include statement in the SCRIPT, if any include is there and we press the F5 or F6 then this will go that Include (normally SO10 or any transaction text), then if we want line by line debugging then we can press the F5 or F6, or if you want to execute that in a single shot then press the F8, then the debugger will be executed that include and come back to the Script debugging.
Some times in the script, we may right lengthy lines, if we want to debug that whole line, we have an option called Left/Right, this we will find the Debug screen of the script, there is a Push button, we can make use this button to debug.
We can put the breakpoints in the SCRIPT DEBUGGER also, just press the BREAKPOINT Pushbutton from the debugging screen or press EDIT --> Breakpoint
If we want to debug the print program from the SCRIPT DEBUGGER, just press SHIFT+F7 or EDIT --> ABAP Debugging
If we want to see the Windows which are defined in the forms, just press the Go to --> Form --> Windows .if we want to see the pages go to --> Form --> pages. Here we have an option to see the page wise window also go to --> Form --> page Windows
If we want to see the paragraphs which are defined in that script, press go to --> Styles --> paragraphs.
If we want to see the Character formats which are defined in that script, press go to --> Styles --> Character Strings.
If we want to see the Page formats which are defined in that script, press go to --> OTF --> Page.
If we want to see the Elements which are used in the Script, then press go to --> Text Elements --> Form Elements.
If we want to see the commands which are used in the script, press go to --> Commands --> List
Finally, if we want to exit from the SCRIPT DEBUGING, simply press Debugger --> Exit
DEBUG BDC
ust go into debugging mode and do the BDC step by step, when it comes to the Call Transaction line, check the mode which will be 'N'....Now, overwrite this with 'A' and execute the BDC...It will run in All Screens Mode....
As suggested above the MODE 'A' will do the trick as it takes you to all screens.
Normally MODE N will be defaulted as it will be used for background processing,
Here is a simple tip,
This will be the call transaction part of the program,
CALL TRANSACTION 'IW32' USING BDCDATA MODE 'N'
MESSAGES INTO MESSTAB.
I would suggest you to make it like this,
DATA: V_MODE TYPE C VALUE 'N'.
*<In debug mode set V_MODE = 'A' for debugging>
CALL TRANSACTION 'IW32' USING BDCDATA MODE V_MODE
MESSAGES INTO MESSTAB.
This will be very useful because you just need to change the value of the V_MODE at runtime as A for debugging besides it has N which is the default to be used. (i.e. you need not change the code again and again).
This will be very useful when you have to debug some program in QA or PRD servers.
regards,
srinivas
*reward for useful answers*

Error when exexuting a smart form from print program

Hi,
I have created a Print Program & Layout Set [Smart Form].
Now when i executed Print program it is throwing following error.
As internal table that we are passing to F.M is not having any data i have appended some data in debug mode.
After htting Print Immediaely Button Following EXIT Error is coming.
No table is currently processed, switching lines is not possible.
Message no. SSFCOMPOSER 183
Diagnosis
You tried to switch to the next table line, but currently no table is open for output.
System Response
The system issues an error message.
Procedure
This is probably an internal error. Please contact the SAP hotline and report the problem.
Can anybody solve this issue!
Thanks in advance.
Thanks,
Deep.

Make sure that you have proper definations of internal table in program and smartform.
Regards,
Amey

Problems with Print Program of Production Order (CO03) !!

Hi all,
I have a question about Print program of Production Order. I created a new Order in CO01. Then, in CO03, I call Print Program ( menu Functions >> Print). At the first time, it printed a so-called original version. Later, when i printed it again, it informed me that just was a copy. Now, that's ok.
I made some modification of Print Program by copying and changing the code (let's call it Z_PSFCOBJL) and SAPScript form. However, When I call Print function in CO03 for that Order, it didn't show any changes which I made. What's wrong? I checked in the code by debug mode, the variable that I transfered to the form was correct with its value.
I think that because SAP just make a print copy so that it will not reflect any changes that I made to the program, right? Is there any way to overcome this because I don't want to create new Orders just for testing every modification?
Thank you in advance.

Hi MURUGESAN THANGATHURAI ,
Yes, I did assign the new program and new form for this before printing. But I wanna know if there is any way that allows me to view those changes I made?
When I change the code in Print Program, print-out includes this update (although it still informs me that is a copy version). But when I make changes in the SAPScript form (for example, adding a variable for display), it will not update this?
What's problem?
Thank you guys.

Passing data to SAP script from print program-VF03

Hi All,
I have a stand alone print program which ahs the invoice number in its selection screen which when entered displays the layout of invoice by using a sap script.
Now since I have to get this layout displayed from VF03, I have added the program, sap script name and a subroutine which contains the code which was initially there under the start-of-selection event in the stand alone program, in NACE. I have replaced the selection screen parameter for invoice number in my program with nast-objky which contains the invoice entered in vf03.
But when I am entering the invoice in vf03 and selecting print preview, the data is getting captured in the internal table defined in my program but the same is not getting reflected in the layout displayed. So I am always getting the blank values in the output though I did not modify the original sap script at all. Pls help.

Keep a breakpoint in your print program and see if your program is being triggered indeed. Do not forget to start Update debugging, otherwise it will not stop in your print program.
Regards,
Ravi

Transaction code(s)- that trigger 'Cheque' SAPscript & print program

Hi,
I have to do some modifications in the cheque (CANADA) SAPscript form and the corresponding print program as per the user requirements.
Form Output and Debugging:
Can you please let me know which transaction code(s)
trigger(s) the cheque SAPscript form and its corresponding print program.
Version: SAP 4.6c
Thanks in advance.
With Best Regards,
Vidya

F110

Update terminate error in va02 Z print program

Hi All,
I have an update terminate error in va02 Z print program when it encounters information message statement while printing the sales order.
I have changed it to status message then no error
This is happening only in precessing status 4(send immediately) in edit message in va02
Regards,
Venkat

Hi venkat,
Go to SM13 . there it gives the line no. where the termination has occured. You can debug the program from there and make relavent changes.
Amar

Office 2007 attachments getting corrupted in PO Print Program

HI SRM Experts,
We are having SRM 5.0 Classic Scenario and EHP 4.0 ECC 6.0, we have a customized PO Print Program which after PO approval send notification to vendor & requestor of cart with the attachments.
We are facing problem that when requester attaches MS 2007 attachments(having 4 characters as extension) it is converting these into default 3 character extension and thus they get corrupted. I have already made settings in DMS (DC30).
Can anyone please help here to know if any SAP note is there for the same as I feel that we cannot change the ABAP program/code mentioned in standard Function module. Here is my finding after the debugging:
The Function module 'CV120_KPRO_MASTER_DATA_GET' is responsible for returning the document type.
It is returning the extension in field dappl of table ptx_data which is of type CHAR3.
So it is not accepting the extension of CHAR4.
Regards,
Varun

Hi
Analyse the Dump in ST22 transaction
difficult to say , as what was changed in the program is not known exactly
from the dump you have to know
Regards
Anji

How can i find the printing program?

hi
i have sap script how can i find the printing program ?
ami

ami bardogo wrote:
hi
what is the different between the commands 'break' and 'break-point'
thanks,
ami
h2 Breakpoints h2
Apart from being able to execute an ABAP program in the Debugger, you can also start the Debugger call by the choosing a breakpoint. This is achieved by setting one or more of these breakpoints in the program. A breakpoint is a signal at a particular point in the program that tells the ABAP runtime processor to interrupt processing and start the Debugger. The Debugger is activated when the program reaches this point.
There is also a special kind of breakpoint called a watchpoint. When you use watchpoints, the Debugger is not activated until the contents of a particular field change. For more information, refer to the chapter Watchpoints.
Breakpoint Variants
The Debugger contains different breakpoint variants:
Static
A user-specific breakpoint is inserted in the source code as an ABAP statement using the keyword BREAK-POINT. A non user-specific breakpoint is set in the ABAP Editor using the BREAK user name statement.
Directly set
dynamic breakpoints
Can be set in the ABAP Editor or the Debugger by double-clicking a line, for example. Dynamic breakpoints are always user-specific, and are deleted when you log off from the R/3 System.
Breakpoints
at statements
The Debugger stops the program immediately before the specified statement is executed.
Breakpoints
at subroutines
The Debugger stops the program immediately before the specified subroutine is called.
Breakpoints at function modules
The Debugger stops the program immediately before the specified function module is called.
Breakpoints at methods
The Debugger stops the program immediately before the specified method is called.
Breakpoints at exceptions and system exceptions
The Debugger stops the program immediately after a system exception, that is, after a runtime error has been intercepted.
Static Breakpoints
Static breakpoints are always user-independent if there is no specification of a user name. Once a user has inserted the statement BREAK-POINT or BREAK name in an ABAP program, the system always interrupts the program at that point for that user or only for the user name. This procedure is only useful in the development phase of an application when program execution is always to be interrupted at the same place. For more information, refer to the chapter Static Breakpoints.
In HTTP sessions, a static breakpoint is skipped if you did not set additional dynamic HTTP breakpoints in the editor of a BSP page. Instead, a corresponding system log entry is written, which can be checked using transaction SM21.
Dynamic Breakpoints
Dynamic breakpoints are user-specific. Therefore, you should use them if you only want the program to be interrupted when you run it yourself, not when it is being executed by other users. All dynamic breakpoints are deleted when you log off from the R/3 System.
Dynamic breakpoints are more flexible than static breakpoints because you can deactivate or delete them at runtime. They have the following advantages:
·        You do not have to change the program code.
·        You can set them even when the program is locked by another programmer.
·        You can define a counter that only activates the breakpoint after it has been reached.
Special dynamic breakpoints are useful when you want to interrupt a program directly before a particular ABAP statement, a subroutine, or an event, but do not know exactly where to find it in the source code. Event here is used to refer to the occurrence of a particular statement, for example, or calling up a method. Special dynamic breakpoints are user-specific. You can only set them in the Debugger. For more information, refer to the chapter Dynamic Breakpoints.
In HTTP sessions, the system stops both at static and dynamic breakpoints if a dynamic breakpoint was set in the editor of a BSP page before program execution.
Lifetime and Transfer of Breakpoints
A static breakpoint remains intact as long as the BREAK-POINT or BREAK-POINT name statement is not removed from the source code. Without saving, dynamic breakpoints only remain intact in the relevant internal session. However, they remain in effect during the entire user session if they are saved by choosing the menu path Breakpoints ® Save in the ABAP Debugger. For more details on the subject of user sessions and modes, refer to Modularization Techniques in the ABAP keyword documentation.
If you call an HTTP session during a user session, only the HTTP breakpoints are loaded when the HTTP session is started. You activate HTTP debugging in the ABAP Editor by choosing Utilities ® Settings ® HTTP Debugging. Depending on the setting, the system then displays either the HTTP or standard breakpoints in the Editor.
If you call an update session during a user session, breakpoints that were defined beforehand in the calling processing unit are copied to the new update session, where they can be displayed under Breakpoints. If, in the ABAP Debugger, you check Update Debugging under Settings and then, for example, call the update module func using CALL FUNCTION func IN UPDATE TASK, a new window is opened in which you can debug this function module in the update session. All the breakpoints that were set in the calling processing unit can also be processed here.
For further information on special breakpoints, refer to:
Breakpoints at Statements
Breakpoints at Subroutines
Breakpoints at Function Module Calls
Breakpoints at Methods
Breakpoints at System Exceptions
h2 page break h2
WINDOW TYPES
When defining a layout set window, you must select a window type for the window. You can choose between three types:
Constant windows (CONST)
Variable windows (VAR)
Main windows (MAIN)
CONSTANT WINDOW
A window of type CONST has the same contents and size on all layout set pages, on which a corresponding page window is defined. This allows the processing of the window contents to be optimized internally.
Page windows whose allocated window is of type CONST must have the same size throughout the layout set. If a window of type CONST is full, all remaining text the application program wants to output in this window, is lost. Constant windows do not trigger a page break. In other words: all text exceeding the window size is simply truncated.
VARIABLE WINDOW
The contents of variable windows is processed again for each page, on which the window appears. The system outputs only as much text as fits into the window. Text exceeding the window size is truncated; the system does not trigger a page break. Unlike constant windows, the page windows declared as variable windows may have different sizes on different layout set pages.
As far as the processing of the window contents is concerned, the system currently treats constant and variable windows alike. The only difference is that constant windows have the same size throughout the layout set.
MAIN WINDOW
Each layout set must have one window of type MAIN. Such a window is called the main window of the layout set. For SAPscript layout sets, the main window has a central meaning:
It controls the page break.
It contains the text body that may cover several pages.
It allows to fix text elements at the upper and lower margins of the allocated page window (for example, for column headings).
As soon as a window of type MAIN is full, SAPscript automatically triggers a page break and continues to output the remaining text in the main window of the subsequent page. Page windows of type MAIN have the same width throughout the layout set. The SAPscript composer thus avoids reformatting of the text after each page break.
If a page does not have a main window, the system implicitly processes all other windows of the page and continues with the subsequent page. This page must not call itself as subsequent page (recursive call), since this would produce an endless loop. In such a case, SAPscript terminates the output after three subsequent pages.
HOW THE COMPOSER WORKS
The composer or layout set processor is the central formatting module for the print output. It prepares the texts for the different output devices by using the allocated styles or layout sets.
Processing a layout set happens in a certain order. You must know some facts concerning the different window types, the setting of subsequent pages, or the dynamic control from within the print program.
Page control in layout sets
Define subsequent page statically
Define subsequent page dynamically
Format a layout set page
PAGE CONTROL IN LAYOUT SETS
SAPscript automatically triggers a page break as soon as the main window of one page is full. To be able to execute the page break, the system must know on which subsequent page to continue outputting the text. You can specify the subsequent page either statically when defining the layout set, or you can set the subsequent page dynamically during layout set output.
If the subsequent page is not specified, SAPscript automatically terminates printing, thereby ignoring any other output statements of the application program.
DEFINE SUBSEQUENT PAGE STATICALLY
You define the subsequent page statically with the layout set maintenance transaction. First, specify the start page in the layout set header. The system automatically calls this page whenever the layout set is started. With this page, or, more correctly, with the page window of this page, the text output starts. For each page, specify the subsequent page in the page definition. After a page break, the system continues text output on the subsequent page defined for the last page. By specifying start page and subsequent pages, you can define a page sequence.
DEFINE SUBSEQUENT PAGE DYNAMICALLY
The page sequence set in the layout set definition can be changed by the application program dynamically at runtime. If you want the layout set to start with a page other than the one defined in the layout set header, specify the desired start page using the parameter STARTPAGE when you call the function module START_FORM. However, this new start page is valid only for the current call of the function module.
If you want to break to a subsequent page other than the one specified in the page definition, use the control statement NEW-PAGE to set the name of the new page.
NEW-PAGE .
NEW-PAGE ends the output on the current page. The new subsequent page is only valid for the current call of the control statement. You can either include the control statement explicitly into the text of a text element or pass it to the layout set output using the function module CONTROL_FORM.
FORMAT LAYOUT SET PAGE
The process of formatting the output is controlled by the text contents in the BODY area of the main window. If the main window is completely filled, or if the control statement NEW-PAGE appears in the main window, the system executes a page break. Only at this point in time the system formats the contents of the windows of the other types and replaces the variables with the current values.
For each other window, the system first outputs the default text element, if it exists. Then it processes and formats the list of the active text elements of this window, which you set using the function module WRITE_FORM with the parameter FUNCTION (SET, APPEND, DELETE). Any text that does not fit into the page window is truncated.
As a consequence to this processing order of the composer, the reservation of space for the TOP and BOTTOM areas must be made beforehand. If the BODY area of the main window already contains text, a new text output to the TOP area does not appear on the current page but on the subsequent page in the TOP area. The same applies for the BOTTOM area. If the BODY area is filled to such an extend that the new BOTTOM text no longer fits into the current main window, this text appears on the subsequent page in the BOTTOM area.
A frequent error in application programs is that for the subsequent page (for example, NEXT) of a layout set no main window is defined. If the formatted text of the previous page did not fit into the corresponding main window , the composer searches the subsequent pages for a main window to output the text remainder. However, if the subsequent page of NEXT is NEXT again, the composer encounters an endless loop.
To be able to create correct page breaks in longer text, you should define a main window on each layout set page.
LAYOUT SET CONTROL
To output SAPscript layout sets, in the print program you must always start the output with OPEN_FORM and end it with CLOSE_FORM. The function module OPEN_FORM initializes the SAPscript composer and opens the specified layout set for subsequent output. The system combines all output for this layout set up to the CLOSE_FORM to one print request. If CLOSE_FORM is missing, nothing will be printed.
To output data in a layout set, you must use the SAPscript function modules WRITE_FORM, WRITE_FORM_LINES, and CONTROL_FORM. You can use these function modules any number of times in any order between opening and closing a layout set.
You cannot use the ABAP/4 statement WRITE to write output to a SAPscript layout set.
Several print requests
Start a layout set again
Switch layout sets
Find layout sets
SEVERAL PRINT REQUESTS
Within one transaction, you can open and close several layout sets using OPEN_FORM and CLOSE_FORM, however not simultaneously. You can use parameters in the OPEN_FORM to control whether the output is stored in the same print request. But also the SAP spool decides, depending on several plausibility checks, whether new output is appended to an existing print request or whether to create a new print request anyway.
CALL FUNCTION 'OPEN_FORM'
CALL FUNCTION 'CLOSE_FORM'
CALL FUNCTION 'OPEN_FORM'
CALL FUNCTION 'CLOSE_FORM'
You cannot combine ABAP/4 list output and SAPscript output in one print request.
START A LAYOUT SET AGAIN
Usually a print program does not print only one urging letter or one account statement, but several layout sets for different customers. To have the output for each customer begin with the start page of the layout set, you must start the current layout set again and again.
To start a layout set again, you must first end the current layout set and then open the layout set again. Within one print request, first call the function module END_FORM. It executes the final processing for the current layout set. Then start the layout set again using START_FORM. Output then begins again on the start page of the desired layout set.
CALL FUNCTION 'OPEN_FORM'
CALL FUNCTION 'START_FORM'
CALL FUNCTION 'END_FORM'
CALL FUNCTION 'START_FORM'
CALL FUNCTION 'END_FORM'
CALL FUNCTION CLOSE_FORM
If you use START_FORM and END_FORM, you must not specify a layout set for OPEN_FORM. However, in this case you can use the SAPscript output functions only after opening a layout set with START_FORM.

Creation of new Print Program & Variant for new Correspondence Type created

Dear Friends,
I have created 2 new Correspondence Types in SAP as SAP61 (Vendor Debit Note) & SAP62 (Vendor Credit Note) by copying SAP09 (Internal Document) properties like itu2019s Name of the print program - RFKORD30 & Name of variant - SAP09.
We are facing problem when we execute print program in F.64 for SAP09 it is coming same like SAP61 or SAP62. Actual script & print values of SAP09 are replaced by SAP61 or SAP62.
Please suggest us how we can differentiate both SAP09 & SAP61/62. Because we use these correspondences for different purposes like SAP09 gives the information for the Line items in the Document whereas SAP61/62 gives the information of vendor line item weather it is debit or credit entry.
Your kind co-operation in this matter is highly appreciated.
Thanks & Regards,
Naveen Kumar.P

"Assigned the from to the company code - progam in V_001F_B"
Check 'Form ID' field in this IMG transaction against the program and form that you have created.
I am assuming there are 2 lines with same entries but different form IDs.
Or there are 2 lines with the same entries but different CoCodes (seem to remember that the CoCode is not taken into account as a key in certain programs - not logical i know but remembered a previous issue I had many moons ago - could be to do with the blank entry for CoCode field if there is one being picked up by the program before the entry that has your CoCode).
Now check the variant attached and Form ID in step 'Created new program variants in SA38'
Ensure the correct program and variant are attached in step OB78.
My assumption is Form ID is the key.
Hope this helps

Debug PO print program

Similar Messages

Maybe you are looking for