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.

Similar Messages

Update was terminated error while trying to attach output type to VA22

Hi
We are getting the below message while trying to attach output type to quotation in VA22 transaction
Can you tell us what exactly the problem is?
It doesn't happen with other output types...
Update was terminated
System ID....   PEQ
Client.......   300
User.....   Swetha
Transaction..   VA21
Update key...   1CB83C9AAEF946C8A1CDE4E19BC94479
Generated....   19.05.2008, 08:22:54
Completed....   19.05.2008, 08:23:41
Error Info...   Application area: /SMB40/SSFCOMPOSER , message no.: 002, no entry found in T100
Regards
Sudha

Hi ,
Please check the message in the table - T100 using transaction se11. You might get the answer.
Thanks
vamshi

Hiii friends! how attached output type to a transaction

Hi gurus!
how to attached output type to a transaction.
for eg - i have created a outout type zexpt and i have to assigned to transaction VF01.
Regards,
Rahul

Hi
goto VF02 tcode
fro Menu
GOTO HEADER -> Output
define there
Output is a link between the Driver Program and the Sapscript,
An output type summarizes messages of the same meaning. It contains parameters that are valid for all its assigned messages, for example appropriate partner functions.
Transmission medium is a medium which the layout will be come out, this may be printout, Fax or Mail
Check this link.
http://help.sap.com/saphelp_nw2004s/helpdata/en/c8/19884743b111d1896f0000e8322d00/content.htm
ex-how to config output type.
You will assign output types using Transaction NACE.
Do the follow steps to assign output type
1)Select Application Type V2 which will have description Shipping.
2)Click on Output types button.
3)Go to change mode by pressing Ctrl+F4.
4)Select one output type which already exists
5)Do Copy As(F6)
6)Give your output type against Output Type field.
7)Under General data Tab, Give Program and Form routine and Save the data.
i think it a work of functional guy but at senior level i think it is not a big deal for abaper.
Check the following documentation
In NACE t-codewe have the application for each one. based on the application output type can be defined, based on output type script and print progrma can be defined.
If suppose data can be read from EDI then we should go for condition records.
So whenever we execute the script first composer checks the output type and then execute the program. in program whenever opn form FM will be populate then script will open first. After that again program till another FM will populate if it then script will populate........like it is cycle proces. Composer does all these things and at last it will submit that output to spool.
Go to the Transaction NACE.
choose the related sub module.. like billing or shipping
doubel click on Output Types
Choose the Output Type for which whcih you wanted your script to trigger
Then select the Output Type and double click on Processing Routine
Then go to create new entries--> Select the Medium (1- print output), then enter your Script and Print Program detls --> Save and come out
Now go to the Transaction (for which you have created the output type)... Issue output--> Select the output type --> Print....
Device Types for SAP Output Devices (Detail Information)
Definition
The device type indicates the type of printer to be addressed. When you define an output device, choose the name of the device type that was defined in the SAP System for your printer model, such as Post2 for a PostScript printer. In the case of frontend printing under Microsoft Windows, you can also use the generic (device-independent) device type SWIN.
The system uses the information in the device type to convert a document from the internal SAP character representation (spool request in OTF or in text format) to a device-specific, print-ready data stream (output request). Since a device type specifies attributes that apply to all devices of a certain model, it can be shared among device definitions. For example, all devices in the SAP spool system that are compatible with Hewlett-Packard LaserJet IIID printers would use the HPLJIIID device type.
You should not confuse the device type with the printer driver. The device type is the total of all attributes of an output device that the SAP System must know to control the output device correctly, such as control commands for font selection, page size, character set selection, and so on. These attributes also include the printer driver that SAPscript/Smart Forms (the SAP form processor) should use for this printer. The SAPscript printer driver that is to be used for devices of this type for output formatting is therefore only an attribute that the device type specifies.
How do I choose the correct device type?
In most cases, the SAP System already provides the appropriate device type for the printer type for the printer model that you want to use.
These standard device types are completely defined and need no modification or extension before you use them in device definitions.
You can also download missing device types from the sapserv server. For a current list of the supported device types, see SAP Note 8928 in the SAP Service Marketplace.
Most printers can be controlled using a generic format, such as PostScript. They can be switched to a mode that is compatible with one of the standard printers for which an SAP device type is available. In this case, a supported model is emulated.
Almost all printers are delivered with Microsoft Windows printer drivers. The system can control these printers with the generic (device-independent) device type SWIN. The Microsoft Windows spool system then performs the processing of the print data.
If the specified device types are not available, and generic device types cannot be used, you must create your own device type or edit a copy of an existing device type. We recommend that only those with specialist knowledge of the SAP Spool System and printer driver code do this. For more information, see Defining a New Device Type .
Attributes of a Device Type
A device type is distinguished by the attributes listed below. If you change an existing device type or create a new device type, you must change at least some of these attributes.
Character set: A character set specifies the codes with which characters must be represented in the print-ready output stream (output request). This code replaces the generic SAP characters set that is used internally by the SAP spool system (spool request).
Printer driver: You can specify different printer drivers for printing SAPscript documents and ABAP lists.
Print controls: Print controls represent printer operations, such as boldface or changing the font size. These print control are replaced by printer-specific commands during the creation of the output request from a spool request.
Formats: Formats specify the format supported by the SAP system. The system differentiates between SAPScript formats (DINA4 and LETTER) and ABAP list formats (X_65_132 = 65 rows/132 columns).
Page format: A page format is the interface between a format and SAPscript. It specifies the paper dimensions with which SAPScript can calculate the row and column lengths.
Actions: Actions are output device-specific commands that are required for the implementation of a format. The action printer initialization, for example, can contain a printer command with which the number of rows on a page is defined. There is a set of actions for every format supported by a device type.
Regards
Anji

Attaching output types to Tcode

hi everyone,
can any one please tell me the settings for attaching output type which we give in NACE that must be attached to ME21N that means when ever a PO is created that must be printed or e-mailed...... what ever it may be, according to the output type given in NACE for all PO's,instead of creating message type for every PO in ME21N.
THANKS IN ADVANCE

hi here is another example ,
1. We can send files with attachment.
However, There is some trick involved
in the binary files.
2. I have made a program (and it works fantastic)
ONLY 6 LINES FOR EMAILING
BELIEVE ME
ITS A FANTASTIC PROGRAM.
IT WILL WORK LIKE OUTLOOK EXPRESS !
3. The user is provided with
a) file name
b) email address to send mail
and it sends ANY FILE (.xls,.pdf .xyz..)
Instantaneously !
4. Make two things first :
1. Include with the name : ZAMI_INCLFOR_MAIL
2. Report with the name : ZAM_TEMP147 (any name will do)
3. Activate both and execute (2)
4. After providing filename, email adress
5. Code for Include :
10.08.2005 Amit M - Created
Include For Mail (First Req F16)
Modification Log
Data
DATA: docdata LIKE sodocchgi1,
objpack LIKE sopcklsti1 OCCURS 1 WITH HEADER LINE,
objhead LIKE solisti1 OCCURS 1 WITH HEADER LINE,
objtxt LIKE solisti1 OCCURS 10 WITH HEADER LINE,
objbin LIKE solisti1 OCCURS 10 WITH HEADER LINE,
objhex LIKE solix OCCURS 10 WITH HEADER LINE,
reclist LIKE somlreci1 OCCURS 1 WITH HEADER LINE.
DATA: tab_lines TYPE i,
doc_size TYPE i,
att_type LIKE soodk-objtp.
DATA: listobject LIKE abaplist OCCURS 1 WITH HEADER LINE.
FORM
FORM ml_customize USING objname objdesc.
Clear Variables
CLEAR docdata.
REFRESH objpack.
CLEAR objpack.
REFRESH objhead.
REFRESH objtxt.
CLEAR objtxt.
REFRESH objbin.
CLEAR objbin.
REFRESH objhex.
CLEAR objhex.
REFRESH reclist.
CLEAR reclist.
REFRESH listobject.
CLEAR listobject.
CLEAR tab_lines.
CLEAR doc_size.
CLEAR att_type.
Set Variables
docdata-obj_name = objname.
docdata-obj_descr = objdesc.
ENDFORM. "ml_customize
FORM
FORM ml_addrecp USING preceiver prec_type.
CLEAR reclist.
reclist-receiver = preceiver.
reclist-rec_type = prec_type.
APPEND reclist.
ENDFORM. "ml_customize
FORM
FORM ml_addtxt USING ptxt.
CLEAR objtxt.
objtxt = ptxt.
APPEND objtxt.
ENDFORM. "ml_customize
FORM
FORM ml_prepare USING bypassmemory whatatt_type whatname.
IF bypassmemory = ''.
Fetch List From Memory
CALL FUNCTION 'LIST_FROM_MEMORY'
TABLES
listobject = listobject
EXCEPTIONS
OTHERS = 1.
IF sy-subrc 0.
MESSAGE ID '61' TYPE 'E' NUMBER '731'
WITH 'LIST_FROM_MEMORY'.
ENDIF.
CALL FUNCTION 'TABLE_COMPRESS'
IMPORTING
COMPRESSED_SIZE =
TABLES
in = listobject
out = objbin
EXCEPTIONS
OTHERS = 1
IF sy-subrc 0.
MESSAGE ID '61' TYPE 'E' NUMBER '731'
WITH 'TABLE_COMPRESS'.
ENDIF.
ENDIF.
Header Data
Already Done Thru FM
main Text
Already Done Thru FM
Packing Info For Text Data
DESCRIBE TABLE objtxt LINES tab_lines.
READ TABLE objtxt INDEX tab_lines.
docdata-doc_size = ( tab_lines - 1 ) * 255 + STRLEN( objtxt ).
CLEAR objpack-transf_bin.
objpack-head_start = 1.
objpack-head_num = 0.
objpack-body_start = 1.
objpack-body_num = tab_lines.
objpack-doc_type = 'TXT'.
APPEND objpack.
Packing Info Attachment
att_type = whatatt_type..
DESCRIBE TABLE objbin LINES tab_lines.
READ TABLE objbin INDEX tab_lines.
objpack-doc_size = ( tab_lines - 1 ) * 255 + STRLEN( objbin ).
objpack-transf_bin = 'X'.
objpack-head_start = 1.
objpack-head_num = 0.
objpack-body_start = 1.
objpack-body_num = tab_lines.
objpack-doc_type = att_type.
objpack-obj_name = 'ATTACHMENT'.
objpack-obj_descr = whatname.
APPEND objpack.
Receiver List
Already done thru fm
ENDFORM. "ml_prepare
FORM
FORM ml_dosend.
CALL FUNCTION 'SO_NEW_DOCUMENT_ATT_SEND_API1'
EXPORTING
document_data = docdata
put_in_outbox = 'X'
commit_work = 'X' "used from rel. 6.10
IMPORTING
SENT_TO_ALL =
NEW_OBJECT_ID =
TABLES
packing_list = objpack
object_header = objhead
contents_bin = objbin
contents_txt = objtxt
CONTENTS_HEX = objhex
OBJECT_PARA =
object_parb =
receivers = reclist
EXCEPTIONS
too_many_receivers = 1
document_not_sent = 2
document_type_not_exist = 3
operation_no_authorization = 4
parameter_error = 5
x_error = 6
enqueue_error = 7
OTHERS = 8
IF sy-subrc 0.
MESSAGE ID 'SO' TYPE 'S' NUMBER '023'
WITH docdata-obj_name.
ENDIF.
ENDFORM. "ml_customize
FORM
FORM ml_spooltopdf USING whatspoolid.
DATA : pdf LIKE tline OCCURS 0 WITH HEADER LINE.
Call Function
CALL FUNCTION 'CONVERT_OTFSPOOLJOB_2_PDF'
EXPORTING
src_spoolid = whatspoolid
TABLES
pdf = pdf
EXCEPTIONS
err_no_otf_spooljob = 1
OTHERS = 12.
Convert
PERFORM doconv TABLES pdf objbin.
ENDFORM. "ml_spooltopdf
FORM
FORM doconv TABLES
mypdf STRUCTURE tline
outbin STRUCTURE solisti1.
Data
DATA : pos TYPE i.
DATA : len TYPE i.
Loop And Put Data
LOOP AT mypdf.
pos = 255 - len.
IF pos > 134. "length of pdf_table
pos = 134.
ENDIF.
outbin+len = mypdf(pos).
len = len + pos.
IF len = 255. "length of out (contents_bin)
APPEND outbin.
CLEAR: outbin, len.
IF pos < 134.
outbin = mypdf+pos.
len = 134 - pos.
ENDIF.
ENDIF.
ENDLOOP.
IF len > 0.
APPEND outbin.
ENDIF.
ENDFORM. "doconv
CODE FOR PROGRAM
5.
REPORT zam_temp147 .
INCLUDE zami_inclfor_mail.
DATA
DATA : itab LIKE tline OCCURS 0 WITH HEADER LINE.
DATA : file_name TYPE string.
data : path like PCFILE-PATH.
data : extension(5) type c.
data : name(100) type c.
SELECTION SCREEN
PARAMETERS : receiver TYPE somlreci1-receiver lower case.
PARAMETERS : p_file LIKE rlgrap-filename
OBLIGATORY.
AT SELECTION SCREEN
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_file.
CLEAR p_file.
CALL FUNCTION 'F4_FILENAME'
IMPORTING
file_name = p_file.
START-OF-SELECTION
START-OF-SELECTION.
PERFORM ml_customize USING 'Tst' 'Testing'.
PERFORM ml_addrecp USING receiver 'U'.
PERFORM upl.
PERFORM doconv TABLES itab objbin.
PERFORM ml_prepare USING 'X' extension name.
PERFORM ml_dosend.
SUBMIT rsconn01
WITH mode EQ 'INT'
AND RETURN.
FORM
FORM upl.
file_name = p_file.
CALL FUNCTION 'GUI_UPLOAD'
EXPORTING
filename = file_name
filetype = 'BIN'
TABLES
data_tab = itab
EXCEPTIONS
file_open_error = 1
file_read_error = 2
no_batch = 3
gui_refuse_filetransfer = 4
invalid_type = 5
no_authority = 6
unknown_error = 7
bad_data_format = 8
header_not_allowed = 9
separator_not_allowed = 10
header_too_long = 11
unknown_dp_error = 12
access_denied = 13
dp_out_of_memory = 14
disk_full = 15
dp_timeout = 16
OTHERS = 17.
path = file_name.
CALL FUNCTION 'PC_SPLIT_COMPLETE_FILENAME'
EXPORTING
complete_filename = path
CHECK_DOS_FORMAT =
IMPORTING
DRIVE =
EXTENSION = extension
NAME = name
NAME_WITH_EXT =
PATH =
EXCEPTIONS
INVALID_DRIVE = 1
INVALID_EXTENSION = 2
INVALID_NAME = 3
INVALID_PATH = 4
OTHERS = 5
ENDFORM. "upl

Attachment of output type to Invoice

Each type after i create a Invoice i have to go into Header and assign the output type (RD00) for printing purpose is there any other method wher i can give it commonly, so that i dont have to go and give it every time i create an Invoice. Like some mass attachment//... Please help me frnds.

Hi,
Output determination works as per follows:-
1.First you will have to create a output type.
2.Assign output program to this output type either SAP script or Smartform.
3.Assign this output type in output determination procedure along with the desired access sequence.
4.Assign this output determination procedure to your document type Order/Delivery/Billing
5.Maintain the condition record for the access sequence or you can maintain manualy in order/delivery/Billing
6.You can also add the output type manually in the order/Delivery/Billing.
Reward points if helpful.
Regards,
Amrish Purohit

Default Output type for Invoice

Hi Friends,
I need to get the defualt condition record for an output type when I create an Invoice. When I go through menu GOTO -> HEADER -> OUTPUT, I have to see the defualt output type there. Somebody please help me out in this regard.
Thanx in advace,
Ram

In the field for the output, check F4 help to check if any outputs are assigned to the Invoice.
Also, check the output determination attached to the billing document.
IMG-SD-Basis function-Output control-Output determination-Output Determination Using the Condition Technique-Maintain Output Determination for Billing Documents.
1. Check the transaction V/25 for the Output procedure attached to the Billing document.
2. In the output determination procedure, check the output types attached along with if any requirement.
3. In t-code, V/40: check the condition type details.
Regards,
Gauravjit.
Reward points if helpful

Attaching output type automatically

Hi all,
i have developed an invoice form for my client.The output type for that form is maintained correctly and even condition records are maintained properly,but still the output type is not getting attached automatically.Can any one help.
Thanks & regards,
Anjana rao

Hi,
How about checking the printer assignment associated with the condition record.
If the printer specified is not found in the system (which may have been modified by Basis team), then it may not appeared at all.
I guess output device is not maintained in Communication strategy in condition record. Please maintain it properly.
For your [Reference|No automatic output for invoice;.
May it helps you.
DS

Changing output type in invoice

Hi All,
I need to attach the output type in alraedy processed invoices but as the invoices are in display mode in MIR4 I am not sable to do so.
Please advice how to do the same.
Thanks and Regards,
Manu
Edited by: Manu Agrawal on Sep 23, 2008 7:40 AM

Hi,
you must use something like
int32 out[50][50];
int32 j, k;
if (i==0)
for (j=0; j<50; j++)
for(k=0; k<50; k++)
out[j][k]=in1[j][k];
else
for (j=0; j<50; j++)
for(k=0; k<50; k++)
out[j][k]=in2[j][k];
I think this is because formula node must be precompiled before execution of your VI. In your case it doesn't know how to address different array elements of "in1" and "in2" because it doesn't know its sizes before you start your VI. In my example I specify the adresses of array elements by using indecies [j][k].
In any case it looks like you can't make direct assignment of arrays like "arr1=arr2". You always must assign its elements in a loop like "arr1[i]=arr2[i]".
Good luck.
Oleg Chutko.

Assignning Output type to Invoice/Po.

Ho Folks,
is there any userexit in the Invoice print/po print for assigning the exact form to an output?
I have different forms for each country right now.
I would prefer not to setup an output type (email) for every country unless I have to.
The best solution would be a userexit so that I can build a table to assign the correct form.
is there any user-exit or program so that i can assign?
Amit.

Hi Amit,
These are the User Exits available in the billing please go through this and choose one of them which will sute for you with the help of ABAPer.
User Exits For Billing
USEREXIT_NUMBER_RANGE (Module pool SAPLV60A, program RV60AFZZ)
The internal number range used in the standard system is specified in the billing type table and can be changed in this user exit. This user exit is only called when the billing documents is created.
USEREXIT_ACCOUNT_PREP_KOMKCV (Module pool SAPLV60A, program RV60AFZZ)
In this user exit additional fields for account determination that are not provided in the standard system are copied into communication structure KOMKCV (header fields).
USEREXIT_ACCOUNT_PREP_KOMPCV (Module pool SAPLV60A)
In this user exit additional fields for account determination that are not provided in the standard system are copied into communication structure KOMPCV (item fields).
USEREXIT_NUMBER_RANGE_INV_DATE (Module pool SAPLV60A, program RV60AFZC)
Depending on the number range, table TVFKD is used to set the billing date (country-specific requirments in Italy). USEREXIT_NUMBER_RANGE is automatically deactivated when this user exit is being applied.
USEREXIT_FILL_VBRK_VBRP (Module pool SAPLV60A, program RV60AFZC)
This user exit is only called when the billing document is created. It is used to provide the header and the item of the new billing document with deviating or additional data.
USEREXIT_PRINT_ITEM (Module pool SAPLV61A, program RV61AFZB)
Printing the item line of a billing document can be supplemented or changed.
USEREXIT_PRINT_HEAD (Modulpool SAPLV61A, Programm RV61AFZB)
Printing the header line of a billing document can be supplemented or changed.
User exits in program RV60AFZD
Short descriptions of the user exits are contained in the program:
USEREXIT_RELI_XVBPAK_AVBPAK
USEREXIT_NEWROLE_XVBPAK_AVBPAK
USEREXIT_NEWROLE_XVBPAP_AVBPAK
I hope it will help you,
Regards,
Murali.

Output Type for Invoice document

Hi,
The Output Message for Invoice Document was not created during MIRO in 2004. So no output generated & user cant able to take invoice printout via MR90.
Now user needs to output the message & take the printout. How to create the output type (tcode) for invoice document.
Regards,
Baskar

Hi
Follow this
Goto Tcode NACE ...select application MR ...click output types .... here create a copy of ERS and name it as say INVS
Now again in NACE slect MR and click on condition records and maintain condition record for INVS wrt co code
Now in Tcode M808 maintain INVS in the schema MR0002
Now when u create a MIRO doc then at header level do check if print is getting activated or not
Then take print out in MR90 tcode

Controlling time of EDI dispatch in output type for invoice

Hi Gurus,
I am trying to change the setting for invoice dispatch through EDI
Currently the system is set so that invoice is sent (EDI) upon saving - and the desire it to make a manual decision when to send invoice
I have looked at output types in SPRO - but could not figure out how to change the setting - it is not allowing me to change. Am I missing something?
Any tips / tircks / suggestions?
Thanks. - this is urgent as YE closing nears

Go to V/40 .
select the output type that you are using for Invoicing.
double click it.
go to Default Values tab .
Change the Dispatch time to 1. Send with periodically scheduled job. .
Now the invoices will be posted only when you run the program RSNAS00.
IF this doesn't work out, Change it at COndition record level.
Regards,
Ajai
Don't forget to reward points if useful.

Maintain Output type for invoice

Hi experts ,
I am using a bapi "BAPI_BILLINGDOC_CREATEMULTIPLE" for inter company billing and its working fine but it is not maintaining the output type for print this invoice from vf02/vf03 ...
Is there any BAPI to save the output type and device whenever invoice document is created ...
Thanks & Regards
Alok Vishnoi

Hi Alok,
Output types need to maintained in the system through transaction NACE. Your program would be triggered by a concept called message control.
For maintaining your program and the corresponding smartform you need to know the correct application area for its maintenance in NACE. For this you need to take the help of functional guys to determine the output type that your program is triggereing and the necessary maintenance that needs to be done.
In order to understand the concept of message control please go through the link below:-
http://help.sap.com/saphelp_erp2005/helpdata/en/c8/1989fe43b111d1896f0000e8322d00/frameset.htm

HOW TO TRIGGER AN OUTPUT TYPE ON INVOICE SAVING

I need to write a routine to trigger a specific ouput type on invoice saving for a particular pricing condition.I have written the code within the routine.But now what do I do to trigger the output type , I mean in which transaction do I place the routine
to make it to trigger when the invoice is saved if the given condition is satisfied

Hi Shah,
You need to assign that routine in your billing outptut determination procedure control data then specic the the condition type.
IMG path is
SPRO>Sales and Distribution>Basic functions-->Output control >Output determination>Output determination using by the condition technique >Maintain output detrminetion for the billing documents>Maintain output determination procedure-->Control data.
Before tha you make sure that you are maintaining condition record for that output type in VV31 transaction
I hope it will help you,
Regards,
Murali.

How to find out program name to the corresponding output type of invoice..

hi ALL,
I want to findout program name to my output type.
For one invoice functional peoples are configured. Here i know the outtype. But i don't know the program name .
Can any body please tell me how to find out the program name for the output type..?

Hi,
Goto NACE t-code
Select Billing (V3)
Press 'Output Types' Button
In the next screen select the corresponding output type you want.
Then press 'Processing Routines' in the left pane. You can see the program name
Cheers,
Kothand

Output type for Proforma Invoice for return delivery from delivery type RLN

Client require Output type Proforma Invoice for return delivery to vendor. As such return item category is not relevant for pricing so from delivery to proforma invoice can not have with p-ricing. I got quantity correct but pricing is coming Zero.
Client have ZPAC as packing list output type from delivery which shows quantity and pricing. So decided to use the same logic to pull pricing for proforma invoice from delivery.
Here delivery has standard output ZPAC as packing list with access sequence Z002 as Delivery Type.
I want to pop up output type for all return delivery so using access sequence with delivery type/vendor.
Vendor filed does not exist in delivery output type so brought that firld LIFNR.
It is assigned to procedure and maintained ZPRO output type for Proforma invoice. Asigned VV21 on front end.
Problem Still automatic output type ZPRO is not poping up. What type of access sequence will help me to pop up or what in configuration am I miising?
Appreciate help for solution at earliest.

Hi Padamsree,
I know Pricing & output very well. I need profomra invoice to be printed with quantity & value for return goods to the vendor. Pricing is associated with Item category RLLN for delivery type RLL which is return type delivery.
I need to have pricing in my Proforma invoice which is copied from delivery to billing document VTFL. Just check well how it is working in the system & if you know please answer so that it should be workable on the system. As theoretical answer may not be helpful. Appreciate for your time.
Thanks

Attach output type to invoice

Similar Messages

Maybe you are looking for