Go to transaction NACE. Choose the required application from the list and click on output types. Chose one of the Output types from the right pane and click on processing routines. Following screen appears: If an SAP Script to be attached, fill-in the driver program name, Form routine and SAP Script name in the field “Form” (shown below)”.
It is most likely that the problem is caused by an infinite loop (or some super heavy calculations, that take a while to execute) in the code you've written, and not by the standard functionality, which means we really cannot help you without knowing the code. Now to your problem. You will probably find your problem in 1 of 3 places ( using basic debugging techniques): [PDF FORM SCRIPTS] If you have any scripts written in PDF form, I suggest you use a clean (empty new form with the same interface for testing. PDF form script debugging would require its own question and I'm not getting into it here.
If you had pdf form scripts written launch the program with a clean form and see if it still gets stuck. If it doesn't - problem is in your scripts, if it does - continue to next step. [PRINTING PROGRAM] If you are using using your own (non-standard) printing program to call PDF function module, place a breakpoint on call of PDF function module call and job close function module. Launch the program and see if the function module of PDF form and job close function module ever gets called (I assume it does, because you see the Printing pop-up). Chand chupa badal mein song download songs pk7178123.
If neither is called, you have an endless loop before even getting to pdf function module. If PDF FM gets called multiple times, but not the job close one, your pdf function module is in an endless loop. If both get called the problem is not in program.
[FORM INTERFACE] If you have any logic in your interface code, place breakpoints (by writing break-point in code) at the end of the interface code. When you run the program, the breakpoint at the end should trigger. (if it does not - look for a loop / long running code in your interface. If the problem is in the interface or program, place a breakpoint at the start of it, and look at how the program executes step-by-step, to find where it get stuck. You can also use a different approach, that Sandra Rossi suggested, and start a debugger while your program is stuck. Bare in mind, this will only help you if it actually is an endless loop (it won't help to find bad selects, bad configurations, etc).
To do that, launch your program in 1 session and when it gets stuck open SM66 transaction in another session. Find your program in the list (of SM66), select it (by clicking the left-most column) and select Administration -> Program -> Debugging from menu. A debugger should open and the 'current step' of the program should be be somewhere within your endless loop (if there is one). Since you provided no code, or any data, I assume you can correct the problem on your own, once you find it.
If it is none of those things, update your answer with some details, and maybe you will get a more specific answer. 
Configuring the Adobe Forms / Smart forms / SAP Script to the output type in NACE By Nikunj Shah, YASH Technologies Go to transaction NACE. Choose the required application from the list and click on output types. Chose one of the Output types from the right pane and click on processing routines.
Following screen appears: If an SAP Script to be attached, fill-in the driver program name, Form routine and SAP Script name in the field “Form” (shown below)” If an Smart Form / Adobe Form are to be attached, enter the form name in the field “PDF/SmartForm Form” and select one of the types “PDF” or “SmartForm”. (See the screenshot below) Please send us your feedback/suggestions at • • • • • • • • © 2006-2007 SAPTechnical.COM.