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

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

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.

SHIPMENT OUTPUT TYPE AUTOMATICALLY NOT DETERMINED

DEAR SAP Gurus,
I got one issue i.e in shipment document the output type is not determined automatically.I checked the config settings , everything is ok and condition records are already maintained. Pl resolve this ASAP . I need to close this issue in 2 days..
Thanks in Advance...
Regards,
Rafiq

hi,
You will resolve it following this:
o Start Transaction VL10CUC ("Parameter per Profile in Delivery
   Process") in the change mode.
o Goto the detail screen of profile '2000'.
o Check the status of parameter 'No OutputDet.' and correct the
   setting of the parameter:
   - If parameter 'No OutputDet.' is active, the output
      determination is not executed for the process.
   - If parameter 'No OutputDet.' is not set, the output
      determination is executed for the process.
Regards,
david

How can I determining Output Type automatically in Invoice

Hi Friends
Can any body advise How can I configure output type or its related settings so that output type should be determining Automatically when saving the invoice.
right now it comes in the invoice only manually but I want automatically.
Thanks in advance.
Regards
Neeraj Jain

Hi,
did you assign output determination procedure,output type and application to billing type? Check in VOFA t.code.
Goto NACE t.code Select the application V3 and click on output type.
Select the output type and choose details.
Activate the field Access to conditions. in general data tab.
If this field is not selected, then system will not search for condition records.
Regards,
Chandra

Automatic configuration of NEU output types for PO Vendor and its partners

Hi All,
I have requirement where I need need to send IDOC to PO Vendor and its partners at the same time when PO is created and changed. I need to get NEU output types for Vendor and Partners in messages automatically. Can any one guide me how to get this functionality. Please help me with step by step process. I am new to MM.
Thanks,
Ravi

To attach output type to purchase order :
Go to NACE , Select Application EF ( Purchase Order) and Click on Condition Records button.
In a POP UP window double click NEU and then select the right Key Combination and maintain right transmission medium and output devide details.

Automatic Output Type Determination

Dear All,
I have a situation where I want my system to determine which Output Type to be selected automatically, by which I dont have to select for the particular output type.
Can u suggest me some input pls ?
Rgds,
Indrajit

Hi Indrajit,
For Automatic Output Determination
1. Use Condition Technique
2. Create Condition Records
You need to maintain ouput condition records from below T-Codes
T.Code: VV11 - Sales Documents for Sales orders (Output type = BA00)
T.Code: VV21 - Shiiping Activities for Deliveries (Output type = LD00)
T.Code: VV31 - Billing Dcouments..for Billing   (Output type = RD00)
T.Code: VV71 - Shipment              for Transportation
T.Code: VV61 - Handling Units       for Packaging
T.Code: NACE (Group)
Just maintain them and you will get the output type automatically.
It will help you,
Regards,
MH

Blocking Output types from Triggering.

Client has a requirement that if overall credit status of delivery is 'B' ( Blocked ) then all output types Automatic or Manual associated with the delivery should be blocked.
I added following lines of code in requirements for all output types associated with deliveries
IF   KOMKBV2-CMGST CA 'B'.
    SY-SUBRC = 4.
    EXIT.
ENDIF.
But we are still able to attach output types to deliveries with credit status blocked, any pointers ?

hi Saket,
This can be the issue you are facing.
you are exiting from the current event with the 'EXIT' statment, but the validation is not applicable in the subsequent event.
in the subsequent event, may be 'END-OF-SELECTION',
insert the following statement, as the first statement:
CHECK NOT KOMKBV2-CMGST EQ 'B'.
hope this helps

Output type not proposed in Message Control when PO is created

Hi,
DETAILS
I have set up the system to send a IDOC when a PO is created. I have done the following settings in the system to send the IDOC using the message control functionality in the PO creation screen.
1). Created a new output type ZNEU which is an exact copy of NEU output type provided by the SAP system.
2). Assigned the new output type to the output determination procedure.
3). Enabled the new output type ZNEU for ALE distribution.
4). Maintained the condition records in the system for the output type ZNEU such that for the P org, endor and Docmuent type combination the output shall be proposed.
5). Maintained a partner profile( Logical System ) and assigned the output type ZNEU to this partner profile.
6). Created a Distribution model for Sender ~ Receiver for ORDERS message type.
PROBLEM
When i create a PO the new output type is not getting proposed by the system. I am not sure why it is not getting porposed in the message control.
I tried to manually enter the ZNEU output type in the system to see if the system is accepting. I am getting an error
Partner % does not exist for partner function LS
Any idea what i am missing? Am i missing any configuration or am i doing something wrong?
cheers

The output is not being proposed automatically is becuase you are missing "Condition Records" for the output type ZNEU.
Go to NACE.
Select EF - Purchase Order
Select "Condition Records"
Select ZNEU and select condition records
Now, system will bring the combinations of access sequence. Maintain appopriate record.
This will enable you to get the output type automatically in the purchase order.
Regards,
Naimesh Patel

PO output type is not reflected in PO message.

Hi,
I have created new PO output type for standard PO Document type.Which is also reflected in NACE.But while creating the PO
it couldnt reflected in PO o/p type in mesaage tab.

Hi,
If you do not want, PO output type automatically displayed during PO creation, then use path:
SPRO>MM>Purchasing>Message>Output control>Message types> Define message type for Purchase Order--> Maintain Message Types for PO,
Double click your PO output type and in General data TAB, do not select check box u201CAccess to conditionsu201D & save
Now create PO and you need to enter manually the PO output type, if you need PO print out
Regards,
Biju K

Default output type in purchase order

Dear All
i have short and easy question:
how can i set one output type(like NEU) as default in purchase order as when create P.O output type automatically comes from customizing?
best regards
R.T

Hi,
If you have done all customizing setting & maintain condition record for message type in t.code : MN04. Now Just fine tune the output (message) type in following path:
SPRO>MM>Purchasing>Message>Output control>Message tyoes> Define message type for Purchase Order-->Fine-Tuned Control: Purchase Order
Now here select the check box corresponding to your output(message) type NEU to have print output for this message type is automatically displayed & save.
Now try creating PO & u will have default message type.
Regards,
Biju K

Sale order create BAPI and output types

Hi Experts,
In our organization, we are using BAPI BAPI_SALESORDER_CREATEFROMDAT2 to create sales order.
We are having no problem creating sales orders. But one more functionality they wanted to add.
We have a screen where user enters all the data and at the same time he selects weather the order should be printed or Faxed or both.
Please let me know where i can send this information in that BAPI and how.
I hope ORDER_KEYS is the table to send the data. If that is the case, could you please explain how that works and how that makes entry in NAST table.
Thanks,
ABAPer.

To propose output type automatically, you need to maintain proper output determination for the sales.
For example, you want to have BA00 output for every order, than you need to maintain the order type for that condition in VV11 transaction. Here you can maintain customer numbers. Now, when you create a Sales order for this customer and saves it, system automatically propose an output.
So, you need to maintain on output detemination to propose output.
Regards,
Naimesh Patel

Creating/Triggering Output Type from program

Hi,
When I am creating Inbound Delivery using VL31N tcode, an Output type associated with it triggers automatically. But my problem is that I have stopped the triggering of Output type automatically while saving Inbound delivery. and want to create mannually through program.
Is there any FM or any other way to do through program.
best regards
bobby

Hi
Below link is for your reference
[create output type reference|http://www.interfax.net/en/help/sap_sd_mm_module.html]
hope it will help you.
Regards
Natasha Garg
Edited by: Natasha Garg on Feb 5, 2009 7:25 AM

Attaching output type automatically

Similar Messages

Maybe you are looking for