Hiding the Output types for ME22n transaction

Hi,
We have a requirement in removing the output types from the message tab of ME22n trasaction.we have defined 2 output types for the same NEU and ZFES a special function,we need to check if the PO is already assigned with ZFES then the NEU output types should not be displayed over there in messgaes tab.
Any pointers will be really helpful.
Thanks,
Jay

Use EXIT function VN000001 for output selection
write down your code as per your need .
thanks
abhishek

Similar Messages

Update LIKP table while saving the output type in VT02N transaction

Hi All,
I have a requirement where i have to update Delivery Priority(LPRIO) field in LIKP table while saving the output type in VT02N transaction. I am not able to use the BAPI "BAPI_OUTB_DELIVERY_CHANGE" or FM "WS_DELIVERY_UPDATE" because, when we save the output type the programs that are configured in NACE are triggered in update mode and hence i will get a roll back error.
Let me know other ways of updating the table at the time of saving output type for shipment transaction VT02N.

This could be a result of one of the following reasons:
1: Incorrect smart form/routine assigned in the output configuration (NACE)
2: Serial number range of the delivery expired
3: The default settings of the user (SU01) processing the delivery is missing the default printer name.
Hope this is helpful
Manish

Is there a way to change the output type for Email Remittance Program?

Hello,
We are trying to implement Separate Remittance Program.The seeded output type is PDF( I have checked the output type for send separate remittance concurrent program) however the
email which we receive looks like a regular email I mean with a normal text . Is there a way to get the output in different type like excel,attachment,pdf.
Any inputs would be highly appreciated.
Thanks,
Sushma

Currently there is a bug raised
Bug 8208646 : R12 UNABLE TO SEND SEPARATE REMITTANCE ADVICE AS EMAIL ATTACHMENT IN PDF.
If you want to customize this process you need to create data definition,new rtf template and bursting program to send pdf as attachment.

How to know the output type for particular tcode

Hi
how to know the output type for the VL10D & VAL TCODES.
Can anybody help me out.
Thanks and Regards
Krishnarao

Hi Krishna,
GO to NACE and select your application and click on output types and in the next screen select your output type and and dbl click on Processing routines.
Here you will come to know about which driver program is used for which smartform or Script.
and for Program details you can refer table: REPOSRC
Regards,
Sachin

No processing log generated from the output type for the IDOC

Dear experts,
the output type which is triggered with a transmission medium Special Function has not generated any IDOC.
The question is what is the role of a Special function and EDI transmission.
In some cases the system has generated an IDOC and some cases not. The output is pickedup automatically, but
does not always trigger an IDOC, Thats is the issue I am facing.
Therefore in cases where there was no IDOC created there is no processing log generated.
KIndly help.

The status is green, and when I try to show the IDOC it doesnt show and no processing log.
The same output is processed for a delivery and it creates a IDOC but sometimes it doesnt.

Output type for tcode : F150

Hi ,
I am working with customer dunning letter - tr. F150
I want to attach a modified zform to it .
( acopy of standard dunning into z with some layout changes )
How to configure it / what is the output type for it / what is the application type for dunning form?
Regards
Rajesh

Hi,
Assign in the IMG (SPRO) menu....
Financial Accounting
Account Receivable and Accounts payable
Business transactions
Dunning
Printout
All req configuration is done here...
Regards
Stu

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

Defining output type to a transaction

Hi friends,
1) I have a transaction VF02.
I have created two smartforms for this transaction.
While issuing output in VF02. i can find only one output type RD00.
i also want to include ZD00.
2) is it possible to create our output types for any transaction. if yes , how to do it?
thank you,
kat.

Hi,
Is the out put types already available, if yes then just use VV31 to create new condition record for billing types and sales org.
Alse you need to follow the below steps,
SPRO-Sales & Distribution-> Basic Functions-> Output Control-> Output Determination-> Output Determination Using the Condition Technique-> Maintain Output Determination for Billing Documents-> Maintain Output Types, Maintain Access Sequences, Assign Output Types To Partner Functions, Maintain Output Determination Procedure, Assign Output Determination Procedures.
Once it is done use VV31 to create condition record.
Just an example below:
Check this hope it helps, select the meduim 1 print instead of edi. hope it helps..STEP 1: Output Type Config
Create Z810 output type with access sequence key Billing Type Sales Org Customer. Z810 is based on the SAP standard RD00.
The following steps are executed in the IMG at the following path:Sales and Distribution -> Basic Functions -> Output Contrl -> Output Determination -> Output Determination Using the condition technique -> Maintain Output Determination for Billing Documents
1.       Create Condition table (Tx: V/63)
·         Table 950
·         Description Bill.type / Sales org. / Bill to
·         Selected fields Billing type, Sales organization, Bill-to party
2.       Maintain access sequence (V/54)
·         Access sequence ZEDI
·         Description Bill.type / Sales org. / Bill to
·         Access Table 950, Exclusive
·         Fields:
o        FKART, KOMKBV3, FKART
o        VKORG, KOMKBV3, VKORG
o        KUNRE, KOMKBV3, KUNRE
3.       Maintain output type (Tx: V/40)
·         Output type: Z810
·         Description: Invoice
o        General data:
§         Access sequence: ZEDI
§         Check: Access to conditions
o        Default Values:
§         Time: 1
§         Transmission medium: 6
§         Partner function: BP
·         Processing routines:
o        Medium: 6
o        Program: RSNASTED
o        Form routine: EDI_PROCESSING
·         Partner functions:
o        Medium: 6
o        Function: BP
4.       Maintain Output Determination Procedure
·         Procedure: V10000
·         Control data: Insert step 11: Condition type: Z810 after RD00. No requirement
5.       Assign output determination procedure (V/25)
·         Doc type: ZF1
·         Output procedure: V10000. Clear output type => Either RD00 or ZD00 can be used
STEP 2: Condition Record (VV32)
The table below shows the values for the condition records.
·         Part Fn: Partner function
·         Med: Transmission medium
o        6 = EDI
·         Time
o        Timing = 1 implies that a background job (running program RSNAST00) will process the output.
o        Timing = 4 implies that the output will be created immediately on document save.
Thanks & Regards,
Nagaraj Kalbavi

Want to change output type for 10000 sales orders through MASS

Hi Friends,
I would like to change the Output type in the sales order for 10000 sales orders.
Can I do with MASS transaction. If so, Plz let me know how ?
Is there any other process to change the output type for 10000 sales orders, as its difficult to manually in each and every sales order.
Its very urgent issue, Plz let me know at the earliest.
Thanks & Regards,
Praveen Kumar. A

This may be little tough for 10000 sales orders.
1. You have to remove the output record for the irrelevant output record using tcode VV12 for the relevant document type. So now for the document type, the old output wont be triggered.
2. Now, create output records for hte correct output type in VV11 tcode(for the output type BA03) for the document type. Now this output will be triggered for all the document types you are creating from now onwards.
3. To trigger the output type BA03, in all the old orders, you just have to open these sales orders in change mode (VA02), and just save it. When u open it the output type BA03 will be automatically triggered as the master data is maintained in VV11. But because just opening all the 10000 sales orders in VA02 one by one be a mechanical task, you have to think of some tool for this.
May be a CATT procedure can do the trick. Else, you can just create a small program, where you can upload these sales orders and the program will just open these orders in change mode and just saves it (without making any changes). Then the output will be retriggered.
Here again, if you are printing the output directly, it is advisable to trigger the output in batch mode(Date/Time field is 1 in VV11), and then you can again trigger the printing again using the program RSNAST00 after office hours for these 10k orders.
I hope I answered ur query.
Pls lemme know if you need some more info. (You can reward me too...)

Configuration output type for VL02N - creating output type

Dear Sapguru,
I want to configure output type for VL02N transaction for IDOC creation,Here scenario is to connect SAP to third party system in IS retail.
VL02N- Output type configuration In only return delivery case.
Can anybody guide step by step cycle configuration for output type.Looking forward for your quick reply.
Note: Output type required for IDOC,to communicate with third party system,not for print function.
Thanks.

Dear Anup,
If my understanding is correct,
This seems to be a outbound Idoc scenario where Idoc will be sent by SAP to third party for a return delivery notification.
Output type configuration steps are as follows :
1) Identify the standard output type (Application - V2, Transmission Medium - 6 ) for e.g. LAVA which is very close to your requirement.
2) Use this output type as a reference & create a copy output type of your own.
3) Use a suitable access sequence or create your own access sequence as per your requirement.
4) Assign access sequence to the output type.
5) Maintain output determination procedure (connect your output type to a suitable procedure )
6) Assign output determination procedure. (to your delivery document type)
7) Maintain required output condition records through T Code - VV21 against your newly created output type.
8) Set up the partner profiles as per your requirement (T code - WE20)
9) Check the reflection/ effects of your new output setup at the delivery document level (VL02N).
You may quickly access these settings through T codes - NACE.
Tables - TNAPR, NAST
Hope it will help you in the set up.
BR,
Anubhav

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

What are the output type and Tcodes?+

What are the output type and Tcodes?

hi,
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
siva

Output type for production order

Hi, when we save the production order, we wants to transfer the prod order header details in legacy system thru idocs. Trying to define output type for production orders in NACE t-code, could not find production order option there. Pls advise in this case how to define the output type for production order so that the header data will be taken by idoc and transfered to legacy. Pls advise.

Hi,
production orders don't have output types like SD orders.
But they have status control and events. Look into the object type BUS2005 in transaction SWO1. There you find the events which are fired by SAP, eg. ProductionOrder.Released.
Which Idoc type do you want to use?
I think you have to programm your own method for the Idoc creation. Put it into a workflow task and assign it to the event.
Regards
Michael

Output type for goods receipt

Hi guys,
Can any one lemme know what is the output type we can use for goods receipt- for generating a goods receipt smartform output?
and can u also lemme know the standard print program also.
if u have written any zprint program plz send it ASAP.
thanks n regards,
Bhargava.

u can see the output types for Goods Receipt in Transaction NACE. Application M1
Output type        Name
CHKL     Count List ( Program RTCHECKL, form RT_CHECK_LIST)
GRPL     Pallet Sticker ( Pro RTCHECKL, form RT_PALLET_LABEL)
The Form names mentioned are SAPSCRIPTS not smartforms.
Also Bhargava, chk out with ur Consultant wat output type suits ur requirement coz there r multiple options as u can see for urself in NACE under Applications M1/ME.
Hope it helps.
Regards,
Bikash
Message was edited by: Bikash Agarwal
Message was edited by: Bikash Agarwal

Output type for transfer order (LT31)

Hi Friends,
could you please give me a hand with this. I would like to know what is the output type for transfer order (T code LT31). Wher can i find this? I looked for in "NACE" but i did't find.
Thank you for help.
Kasia.

Hi Kasia, For TO :
- driver program 'RVADOR01'
- application 'V1'
- output type 'KO00'
check Re: Transfer order print LT31 for details

Hiding the Output types for ME22n transaction

Similar Messages

Maybe you are looking for