Hi Aditya,
this window pop up if you got more than one message to process.
Make sense, because how to know what you want to see in preview.
Tried it by my own and window is still there. I suggest that there are 50% thinking "why isn't it gone" and the other are thinking "great, so I don't need to click again to see the other message".
So there might be no true or false
~Florian
Hi Aditya,
haven't check if the information is correct, because I don't have access to a system right now.
Form: LE_SHIPMENT_CMR2
Program: RVADTR00
Source: CMR - SAPscript or SMARTFORM | SCN
~Florian
Hello Team,
I am trying to print the Handling unit. We have several key combination. I have maintained the condition record through VV61.
1- But we have several user and respective printer has maintained in specific user profile through SU3.
2- So what key combination I should use without maintaining output device in condition record or if I will maintain default printer(LP01) will it be work with specific user ?
3- If I am not maintaining printer name in output device then during packing out-put type not coming automatically.
I have attached screen shot what are the key combination we use.
Appreciate if you can confirm at the earliest.
Thanks
Sits
Hi,
Use the data without space in order to rotate the string without overlapping. You can use underscore as a separator instead of space.
Thanks,
Arun
I have many invoices that went out electronically (transmission medium 5), and I want to now reprocess them with VF31, but spool them to a printer instead (transmission medium 1). Because they were not originally printed, then I can't change the transmission medium to a 1. VF31 will not find any documents.
How can I mass print invoices that have been previously processed using a different transmission medium? I do not want to go into each one and manually create the output.
Thank you for any help.
Janet Kuck
Hi Janet,
First of all, whether you have output determination for Transmission Medium 1 for the desired output type? If yes, then you should be able to do that. But, in the standard process, the system will not consider Transmission Medium 5 execution result as bases for process(re-processing) output type with Transmission Medium 1 execution in VF31.
If you still have any concerns, please do let us know.
Thanks, JP
Unless you provide additional details, like the coding, related to the requirement routine, I think it is bit hard to provide any further guidance by the forum members. So can you add those details?
Regards,
Hello Florian,
Could you please explain me....I hop this will be helpful for me.
Drisya
Hi Anurag,
VF31 is used for Mass maintenance ( such as Triggering Output types in mass, Processing, re-triggering)
in the Process of VF31, system will execute the Routines assigned to the output from the configuration.
While creating the billing document, you can enter the output manually and use a program to process that output such a PRINTING, FAXING, sending OUTPUT AS MAIL, the same is done automatically using VF31.
Hello Drisya,
When you print in tcd:VF01.You should firstly configure your output type in v/40.In the tab "default
values",pls select the option "Send immediately(When saving application)".
Also you need to use an output device which use the access method G.It will show the windows
printer selection dialog,you can select a PDF creator(For example:CutePDF writer) as the printer,so that you can get the print data to be saved as PDF file.
Regards
Jie Bai
Hello,
Anu other ideas?
Luc
Moved from SAP ERP Sales and Distribution (SAP SD) to Output Management
Hi,
what do you mean by "requirement routine" - can u add a screenshot so i can understand.
regads
Stefan Seeburger
Hi Luc,
can you access your local SAP directories using TAC AL11? Depends on your spool and printer configuration though.
Kind regards.
Hi,
you have to controll the printing in your print programm - check if the text is available in your language and use command new-page to get the new page.
handle the pages in your print programm.
as long as they dont have differnet layouts, you dont need different pages. the output controll can print 2nd page as back page and so on.
regards
Stefan Seeburger
Hi,
It needs to maintain condition to your So10...for eg.
Text element in SO10 to be check:
IF <txt_element> IS NOT INITIAL.
INCLUDE &O_CON_SAL& OBJECT TEXT ID ST LANGUAGE &NAST-SPRAS&
ENDIF.
So, if not SO10 text is available - system default takes care.
Regards,
Suren.
Hello Diana,
Yes, I have an access to AL11 in my kernel. It's SAP Directories.
What the next steps should look like?
Luc
It depends what (and how) you're trying to print.
If your print driver program is executable, it should be possible to debug the sapscript form by activating the debugger in SE71 first.
If you're trying to debug the reprint of something like a billing document, activate the debugger via SE71, then launch VF02
Goto > Header > Output
Select an entire row that's already been processed successfully (Green square icon).
Repeat Output
You should see a new entry near the top of your list with a Yellow triangle icon (Not processed).
Highlight that row and make a note of the Output Type (e.g. RD00) and the Transmission Medium (e.g. External Send).
Set the 'Dispatch time' to "Send with periodically scheduled job". Hit 'Enter' then 'Back' then 'Save'.
You should be returned to the VF02 selection screen with a status bar message telling you your document has been saved.
In the same session, navigate to the ABAP Editor via transaction [ /nSE38 ] or [ /nSE80 ].
Execute program RSNAST00.
The selection screen options in this case will be
Output Application = V3 - Billing (because the document we've just reprinted was a billing document, accessed via tcode VF02).
The application may be different in your case if you had tried reprinting a Sales or Shipping document instead.
Object Key = blank.
Output Type and Transmission Medium are the values you took note of earlier (i.e. 'RD00' and 'External Send' respectively).
Execute the program (F8), and you should now see the initial popup screen of the Sapscript Form Debugger.
Smartforms are much easier to work with IMO.
As for your original issue, I'm assuming the Dispatch Time of your output was set to 'Immediate'.
If you had changed it to 'Send with Periodically Scheduled Job', saved it, then run program RSNAST00 for Output Application V3 (with appropriate Output Type and Transmission Medium), you should have been able to debug the sapscript.
Assuming you can set your output to 'Send with periodically scheduled job' rather than 'Send Immediately', you should then be able to debug the sapscript by executing program RSNAST00 with the appropriate parameters. Assuming you've already activated the debugger via SE71.