How to debug Po printing

Hi,
How can I debug PO printing process.
Ingen
Edited by: Autobots 21 on Sep 23, 2008 11:56 AM

Hi
you need to put a HTTP / Session break-point inside any of the BADI Implementations (in SE19 Transaction)
- BBP_ECS_PO_OUT_BADI
- BBP_CREATE_PO_BACK BADI..
Related pointers ->
Re: BAPI_PO_CREATE1
Note 539978 Automatic generation of BAPI test data directory
Re: BBP_ECS_PO_OUT_BADI
Re: Problem with BAPI_PO_CREATE1
Re: BAPI for replicate PO in Ext. Classic Scenario
Re: DATA VALIDATION INSIDE BAPI_PO_CREATE / BAPI_PO_CREATE1
Regards
- Atul

Similar Messages

SAPSCRIPT - HOW TO DEBUG

hi all ,
I need to debug the layout as well as the print program simultaneously , In tcode se71 i have activated the activate debugger , only layout is debugged not the print program ,
how to debug the print program with layout.
thanks in advance.
ravi.s

Hi,
Script:In SE71 give your form name and in Utilities-->Active debugger.
Then put a break point in your print prog where ever you want to stop it.
After that you need to go to your transaction like VF03/../..etc for Invoice you need to execute it by giving Outtype.
Then your print prog and form will debugg step by step.
Thanks.
If this helps you award points and close the thread.
Message was edited by: Deepak333 k

How To: Debug missing Drivers in MDT

The definitive post on missing drivers in MDT (most comprehensive list I've done so far)…
Please to NOT post questions from this thread, instead create a new thread.
How to debug Network Driver Problems
One of the earliest hurdles an MDT administrator will come across is the management of device drivers, specifically networking drivers. With most other drivers, like Audio, printer, and video drivers, a quick call to Windows Update or install over the network
will resolve the Installation. However unless the Network (and storage) Drivers are installed into Windows from the start, it will be much more difficult to install the rest of the system.
This post should help you get started if you find a machine that did not install a device driver properly, and you want to know how to find and import the correct drivers.
Installing network drivers in the
full OS
Step 1 - Try network connection again
It's possible that you might get a DHCP error from MDT, but when you try again later to connect the Deployment Share it works! This may be caused by a slow or malfunctioning DHCP server in your network. Re-check your DHCP servers, ensure that PortFast is enabled
on your routers. If all else fails get your network administrators to document the DHCP delay. A long delay in modern networks is unnecessary.
Step 2 - Verify connectivity
You may not have a driver problem but a network problem. Check the physical connection on the computer (Network installs on MDT *REQUIRE* a wired network connection, no Wi-Fi). Open a web browser. Check the IP Address (ipconfig.exe /all). Ping the Deployment
Server, manually connect to the Deployment Share. IF you can't connect to the Deployment Share, neither can MDT.
Step 3 - Find the Correct Driver Package
Before you load the driver into MDT, first verify that you have the correct driver. There are scenarios where you may *think* you have the correct driver, but the driver will never run because the package is designed for a different OS/SKU/Platform/whatever.
Install the driver package by:
  ○ Open the Device Manager (devmgmt.msc).
  ○ Find the network device in the list (ensure this is the wired device, not the wireless device)
  ○ Right click on "Properties" and click on the "Details" tab.
  ○ From the "Details" tab, select the property "Hardware Ids" select all the values, and copy to the clipboard, it would be a good idea to save for later. Should look something like:
      PCI\VEN_8086&DEV_1502&SUBSYS_21F317AA&REV_04
      PCI\VEN_8086&DEV_1502&SUBSYS_21F317AA
      PCI\VEN_8086&DEV_1502&CC_020000
      PCI\VEN_8086&DEV_1502&CC_0200
  ○ From the "Driver" tab, click on "Update Driver…", click on "Browse my computer for driver software" locate the driver package on the local machine or USB Drive, and install the package.
  ○ You should get a confirmation that the driver package was installed.
  ○ IF you do not get confirmation, MDT driver installation may not work.
Windows will install the driver starting with the *.inf install package, and will typically include a *.sys (binary) and a *.cat (digital Signature). If the driver package has been re-packaged into a *.cab, *.zip, or other compressed *.exe file, the
package must be extracted first. This is a hard requirement for any driver used by MDT and/or SCCM. All driver packages that are signed by Microsoft (WHQL) will be installed from the *.inf file, and you should only use devices that have the Microsoft WHQL
Logo as a sign of quality.
If you need a help on where to find driver packages for your devices, the 3 largest Computer OEM manufacturers supply drivers grouped by Make and Model that are easily imported into MDT and SCCM. See:
http://deploymentbunny.com/2014/07/08/back-to-basicwhere-to-find-drivers-for-servers-and-clients/
Step 4 - Load driver into MDT
If you have more than 20 driver packages, or if you anticipate you will have more than 20 drivers, you should start grouping your drivers in sub-folders for organization. One popular method is to group by Computer Make and Model. Ensure that you are using the
correct Driver Selection Profile in your task sequence. If you are unsure, disable any selection profile(s) to ensure the driver is installed correctly.
Step 5 - Run the full MDT installation
During installation MDT will perform the following:
  ○ Run the PNPEnum.exe utility and capture output to PnPEnum.xml. The VEN_Xxxx and DEV_Yyyy from the "HardwareIDs" property above must be present in this list. Otherwise we won't have a match.
  ○ Search through the %DeployRoot%\control\drivers.xml file looking for a match for the HardwareID. MDT may filter the search based on the folder search type.
  ○ MDT will copy each matching driver to the local c:\drivers directory using the xcopy.exe command. You can search (grep) for the string "xcopy" in the ZTIDrivers.log file, that will get you list of all driver packages matched by MDT.
  ○ MDT will allow the machine to boot into the NEW OS, and Driver Installation will begin in the OS. IF there are multiple drivers found and copied locally, the Windows (not MDT) will determine the best one. The c:\windows\inf\SetupAPI.*.log files
will detail which drivers copied locally were installed (or *not* installed).
Installing Network Drivers in
WinPE
Step 6 - Try the network connection again
(See above
Step 7 - Verify Connectivity from within WinPE
Verifying network connectivity will be a bit more difficult in WinPE, since we have a limited User Interface, so all investigation must be done in the debugging mode (Press F8) cmd.exe
  ○ Try connecting to the Deployment Share:
  c:\> net use * \\MDT\DeploymentShare$ /u:UserDomain\UserName *
  ○ Try pinging the Deployment Server:
  c:\> Ping.exe MDT.Corp.contoso.com
  ○ Verify that you have an IP address ( ipconfig /all ) If you have an AutoConfiguration address - Driver OK - WinPE can't reach the DHCP server. If you have "Media Disconnected" - Driver OK - Physical adapter not plugged to network. If
no devices are listed - Driver bad - Driver not installed.
  ○ Check the x:\windows\system32\WpeInit.log - This log will show the network driver (if found) being installed.
Step 8 - Verify driver packages are getting included into WinPE
Firstly, verify the correct driver package from within the full OS above. By default MDT will import *all* Storage and Networking drivers into your WinPE image. However it is possible to change the subset of files copied via "Selection Profile" or
other method. Cross check your WinPE Driver Settings.
  ○ From within the MDT console, right click on the root of your Deployment Share and select properties.
  ○ Click on the "Windows PE" tab, and the "Drivers and Patches" sub tab for both x86 and x64.
  ○ Your Network Drivers package must be in the "Selection Profile" if enabled.
Finally verify that the correct Network Driver package is being copied to WinPE. If necessary this may include setting up a debugger to watch the MDT Provider build the WinPE Image from scratch. My preference is to use the SysInternals
http://live.sysinternals.com/Dbgview.exe tool.
  ○ Open up the MDT console.
  ○ Download and run the DbgView.exe tool.
  ○ Update the deployment share in question.
  ○ The DbgView tool should show what drivers were copied to each WinPE Image.
Other
Whenever you add a driver into the MDT console, you must update the deployment share for that drivers to be added to your WinPE Image. If you are unsure, select "Completely regenerate the boot images." to ensure the drivers is imported. Additionally,
you must copy the updated LitetouchPE_x??.wim and *.iso files to the other consumers of the WinPE image like WDS/PXE and or any USB offline media.
Note that some Broadcom NetXtreme class of drivers have a multi-function driver architecture that may have difficulty loading in WinPE. Ensure that you load the "RIS" class of drivers from Broadcom in your MDT environment.
Note that by default MDT does *NOT* support the installation of Windows over Wireless network devices (Wi-Fi). The MDT installation sources must either be available through wired networking, or offline (USB Flash) media.
This post does not discuss origination of drivers within MDT ( Chaos vs. Total Control ), that is a different topic.
http://www.deploymentresearch.com/Research/tabid/62/EntryId/112/MDT-2013-Lite-Touch-Driver-Management.aspx
Further Help
If you are still having problems with drivers in via MDT, ask the experts in the MDT Technet Forum:
Include a short description of the problem. Including the Make/Mode if necessary.
Include the HardwareIDs from the Device Manager (Devmgmt.msc) into the post (from above).
Copy your known good driver package (step 3 above) to OneDrive.
Copy the following log files to a public site like OneDrive and include the link:
  ○ PnpEnum.xml (from Client)
  ○ Bdd.log (From Client) - or at least the ZTIDrivers.log file.
  ○ c:\windows\inf\SetupAPI.*.log (from client)
  ○ %DeployRoot%\control\Driver*.xml
  ○ %DeployRoot%\control\SelectionProfile*.xml
  ○ %DeployRoot%\control\settings.xml (if problems in WinPE)
  ○ x:\windows\System32\WpeInit.log (if problems in WinPE)
  ○ If the MDT server is not including your driver package in WinPE include the DBGView log.
This post is by Keith Garner - Keith was a developer on the MDT team where he developed the ZTIDrivers.wsf script, he also worked for the Windows Hardware Quality Labs as a technical PM on Driver Quality, and developed samples for the
Microsoft Device Driver Kit (DDK) specifically around the area of Device Driver installation in the OS (Windows NT 5.0, 2000 and Windows XP). (So yes, I know drivers :^).
Keith Garner - Principal Consultant [owner] -
http://DeploymentLive.com

OK. I have redone the drivers for WinPE which has reduced the image size by about 200MB. Unfortunately the problem persists.
Is there anyway to turn on some sort of boot logging so I can see what driver it is failing on?
I am also still seeing the weird behavior of it working over PXE but blue screens when booting from USB. Can anyone explain that?
JJ

How to debug zrffous_c payment advice script program?

Hi experts,
Payment advice is printing through (ZRFFOUS_C) this program. I want to debug this program .I tried in this way.
Put the break-point in the program and execute then enter the input data and execute then the following message is displayed.
"A:FO:098 29.01.2009 PNB" after this stopped the program .How to debug this program? I want to find these values (REGUP-BELNR, REGUP-XBLNR) in the program .The location where these values selecting in the program?I tried but i didn't get.
please give me the details or give me form name?
please help me in this?

Hi,
Your procedure of debugging is correct.
when you getting the error message , double click on the message on status bar and see wheather it is standard message or
custome message.
you are getting that error because of invalid data so get the valid data from respective Functional consultant
and try to debug again.
You ll not get that error after giving valid data.
Regards,
Pravin

How to debug payment advice program

Hi experts,
iI copied program from RFFOUS_C and named as ZRFFOUS_C.
payment advice is printing through ( ZRFFOUS_C) this program?
If yes how to debug this program ?.I want to konw the values printing in payment advice sheet came from which subroutine.?
I tried but i didn't get.I tried in this way, put the break point in the program and execute then fill the values and execute
then the following message is displayed "A:FO:098 29.01.2009 PNB".
I want to konw document (REGUP-BELNR) YOUR DOCYUMENT (REGUP-XBELNR) about this values came from which sub routine.
If u know anybody pls gime the answer.pls help me in this .

well at first you need to set a breakpoint somewhere in your program.
Then you need to check if your program is customized for payment slips, otherwise standard program will get triggered but not yours.
And finally you probably need to switch on "update task debugging" since output types are quite often processed in update task.

How to setup default print to landscape in Reportviewer (printmode activex)

We have an ASP.NET (2008) application and use the ReportViewer Web Control to show a Crystal Report on the client browser.
   - We set the "PrintMode" property to ActiveX in order to print to the client's local printer.
   - We set up the Landscape in Crystal Report Page setup.
   - We also put repdoc.PrintOptions.PaperOrientation = PaperOrientation.Landscape in the program.
The problem is when the user clicks the print icon, the report prints in portrait, not landscape.
Is there a solution for this or is this a software limitation?
Thanks.

How to setup default print to landscape in Reportviewer (printmode activex)
Hi David,
Yes, I tried that 1196969 solution first, but it didn't work. I saw all the discussion in the below thread and it seems a product issue mention by you on Aug 6, 2008 3:19 PM
CrystalReportViewer default PageOrientation ASP.NET VS 2008
I don't know if the fix works for CrystalReportWebFormViewer4 which is what we have on the web server. I put debug alert in the Javascript of the following file
WindowsMicrosoft.NETv2.0.50727ASP.NETClientFilesCrystalReportWebFormViewer4crystalprinthost.html
I can see the call goes to the file, but won't get to the window.dialogArguments.paperorientation condition.
When I write out: window.dialogArguments.paperorientation; it pops up "undefined".
Is there any updated solution for CrystalReportWebFormViewer4?
Thank you!!

How to debug the smart forms

Hi All,
Can any body guide me how to debug the smart forms.
Thanks & Regards,
Satish.

Hi,
The the best way to debug the form is to put a breakpoint in the function module generated by the smartform.
Procedure:
Open the smartform we want to debug.
Goto Environment -> Function module name.
Open the function module in SE37. From the menu GOTO -> main program. Open the last include.
This incude contains the entire code ie the code we have written in initalization + form routines + program lines + sap generated code.
Even we can search for the text nodes, folders, templates, tables, graphics, address nodes etc with their names.
Put a breakpoint at any point you want.
If we issue any doc which triggers this form, when the control reaches the break point it will stop.
Please note that hard-coding the break points in the code ( Program lines ) is not recommended and it can´t be done unless if it is development server.
So, always put a session break point in the related function module.
We can use SFTRACE transaction to know the sequence of the control flow.
If you want to break at each and every text that is printed on the output form put the break points in the forms.
1. %write_text to break at text element.
2. %WRITE_TEXT_MODULE to break at text module.
3. %WRITE_INCLUDE_TEXT to break at include text.
Please put a break point at the first sy-subrc check.
If the control reaches this point, you can find the name of the element in the varible NAME and the content in the text node in %TEXT.
Its easy to understand the sequence of the printing if we put a breakpoint as stated above.
Regards,
Satish.

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*

How to debug rename file??

Hi
I use a loop and renameTo() method below to move some files to other location. When I run my class, it should move 5 files (vector include 5 files names), but insteade, some time it move 4 files , some time it move 3 files. there are no error message. Most time, last file cann't be moved
for( int i=0; i<newFiles.size(); i++ ){
File temfile=new File(tempFolder+"/"+newFiles.elementAt(i).toString());
File realfile=new File(destDir+"/"+newFiles.elementAt(i).toString());
boolean successful=temfile.renameTo(realfile);
newFiles is vector to include files name string.
I print out temfile and realfile , all of them are correct. May be somewhere else inside my class, other code, affect this , but I don't how to debug?? Thanks for help
Gary

You can try to catch Exception which could be raise be the methode "renameTo"
try {
boolean successful = temfile.renameTo(realfile);
} catch (Exception e){
System.out.println(e.getMessage());
You can hava SecurityException - If a security manager exists and its SecurityManager.checkWrite(java.io.FileDescriptor) method denies write access to either the old or new pathnames
Bye

How to debug IDoc and waht about WE19

hi experts how to debug idocs waht is we19 and perpose

We19 is Testing Inbound IDOC and you can debugging from we19 Transaction
Outbound IDOC Debugging :
Example of Invoice :
Set ur Break point at your code
now come to VF02 Transaction and use invoice 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 : V3
Object key - Invoice Number ( 10 digit)
Output type - RD00( SAP Standard)
Transmission medium = 6(EDI) ,A(ALE)
Now it will stop at your code.
Reward Points if it is helpful
Thanks
Seshu

Hi, how to debug forms of script

hi
could anybody tell me how to debug script forms.
i am using /h in se71, but it is not going inside form.
pl guide me fast.
thanx
robo

Hi Rocky,
Go through the following two ways
SAP Script:
YOu Can debug a SAP Script by activating debugger in two ways 1.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.
2. Goto se38-> RSTXDBUG ->Execute this same as going thru in se71-> Menu, now debugger will be activated.
Smartform:I am afraid , we dont have any direct commands or direct procedure to debug a script. But in indirect ways we can do it.
1.Put a command line before where you want check the value of smartform and write the code "BREAK-POINT"->hardcoded debugging.
2.You can debug the function module which generates the smartform.
Regards
Sreeni

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..

How to debug smartforms

hi
could anybody suggest me how to debug smatforms
thank you
kalyan.

Please set a break point in side the smartform:
BREAK <USERNAME>.
Then at the time of print/ preview the program stops there.
Example : If you set the break point in initializationas
BREAK <USERNAME>.
Program stops at break point. After that use Serach and set more break points.
>Search the program logic/Textelement/Address via search and set the break point at that code.
1) One way to debug smartform is to debug the Function Module of that smartforms.
If you want to debug particular smartform node that the solution would be,
insert a "Program Line" just above the node you want to debug and this program line write a normal abap breakpoint.
So whenever you call the smartforms, it will stop at this breakpoint and you can debug onwards.
2) SFTRACE can be used for debugging SMARTFORMS.
1)goto tcode SFTRACE --> click "trace on"
2) Get the function module name and set break points in function module name.
There is a transaction 'SMARTFORMS_TRACE' (or was it 'SMARTFORMS_TRACE') which will give you quite helpful information.
In SAPSCRIPTS, you can 'Activate the debugger' in SE71 to start the debugging of script.
In SMARTFORMS, you can use BREAK-POINT (coded in any code window node) to initiate debugging of SF.
SFTRACE can be used for debugging SMARTFORMS.
Go in smartforms, put a breakpoint where you want in the generated FM.
Then go in you're PO, go to messages, generated you're output and make sure in further data option 1 is selected.
Then run program rsnast00 with you're form settings, that's it!
You could debug sapscript like that also,
regards,
srinivas

How to debug in SAP Netweaver Developers Studio?

Hi there,
I am trying to debug and slove my error in SAP NWDS.
I am building portal application->JSPDynPage
I am trying to debug the jsp code behind page, it doesn't realli give error message like the java beans does.
I am quite new to this and do not know how to set the function to test and debug this page can anyone provide any solution ?
I have have this prob pls refer to this link
<a href="https://www.sdn.sap.com/irj/sdn/thread?threadID=192104">https://www.sdn.sap.com/irj/sdn/thread?threadID=192104</a>
Thanks loads
Quatre

Hi Quatre ,
-Select the breakpoints in your Dynpages /beans in ur project
-To debug u have to change the prespective to debug which u can find in
window/open prespective /Debug in NWDS
-Select the Run/Debug or the Debug icon in the toolbar.
-Fill the project name ,application name in the in the wizard opnend .
- Follow the debugging using the next step over F6 ,step return F7 keys .
These link may be helpful:
http://help.sap.com/saphelp_nw2004s/helpdata/en/66/547f09281d464b951c9a3a6b06a12d/frameset.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/a8/def86ab54da5418a3575373934ca00/frameset.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/d4/31e24044b80b06e10000000a155106/frameset.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/be/cffcb407c67842b122bd1296dc810f/frameset.htm
U can always find out the way in the PDK development /how to debug/
ie in NWDS /HELP /SAP WAS AS Documentation /SAP J2ee Enterprise Java Beans/Java development User Guide /Running and Debugging
Cheers,
Swathi Rao
Do offer pts:-)

How to debug web app with weblogic?

I wrote a web app that includes jsp files and some javabeans, then I put the jsp files to directory
mydomain\applications\DefaultWebApp
then I complied javabeans and put those classes to
mydomain\applications\DefaultWebApp\WEB-INF\classes
Then I start the weblogic,it runs very well.
I modified some javabean, complie them and put classes override the old classes,
but the web app can not find the new classes.
Any one know How to debug web app(with javabeans) in weblogic?
thanks!

how to config the hot deploy?
thxSorry, for this delay in responding. I had set notify me with email option in Watch This topic; but I never did get any email notification.
I use wls6.1; I think the process may be very similar to this in wls8.x. In wls6.1 (sp5), this is done via the -
Dweblogic.ProductionModeEnabled=False or
Dweblogic.ProductionModeEnabled=True
in the startup cmd/sh script. Out of the box, wls6.1 is set to Dweblogic.ProductionModeEnabled=False which automatically enables hot deploys.

How to debug Po printing

Similar Messages

Maybe you are looking for