Output type and Routine

Hi All,
I have created one Z* output type and attached it with Z* program. and it is having routine called ENTRY_N. Now when i execute a transaction which will trigger my output type, is giving me error saying "Processing routine ENTRY_N in program Z* does not exist".
Can anyone help.
Regards,
Dharmesh

> Hi,
>
> in the Driver Program have a routine with name ENTRY.
> just paste it.
>
>
FORM ENTRY USING RETURN_CODE US_SCREEN.
>
> CLEAR RETCODE.
> XSCREEN = US_SCREEN.
> PERFORM PROCESSING.
> IF RETCODE NE 0.
> RETURN_CODE = 1.
> ELSE.
> RETURN_CODE = 0.
> ENDIF.
>
> ENDFORM.
>
> and put the aboce code in it.
>
in the above code Perform processing you need include all your open_forms and write_forms, close_form. the data you are trying to pass it to script. i hope it is clear.you need to put that logic in the form ENTRY.
regards
vijay

Similar Messages

How to assign output type and trigger printing in ABAP

hi all,
i have create invoice by using BAPI_BILLINGDOC_CREATEMULTIPLE and create header/item text with CREATE_TEXT.
please advise how to assign the output type and trigger immediate printing after this.
thanks.

Hi Reetha ,
This is a functional setting , and should be done by some functional guy. The setting can be done by NACE.
Just follow the path : NACE - > Select V3 for Billing - > Press Output type Button Just above - > Assign Output Type and
then Assign Output program and form in PROCESSING ROUTINE comes into left. Set this output type for immediate print.
Whenever You create a billing document by BAPI with this document type , the print out will be fired immediately.
Hope it will solve your problem.
Thanks.

PO Output Type / Processing Routine Problem

Hello everyone,
I cannot seem to find any reference to the problem described below.
I have encountered a problem by migrating from SAPFM06P to SAPLMEDRUCK during an ECC 5.0 upgrade, at a client where I am under contract as an ABAP Developer.
Here is some background to the situation. The client is currently migrating from version 4.6C to 5.0 and thought it was a good idea to upgrade their purchase order messaging programs from the outdated SAPFM06P, which was utilized in version 3.x, to the newer program SAPLMEDRUCK implemented for use in version 4.6.
Specifically, Message Output (ME9F) controls the output of purchase order messages in foreground, when the purchase order message is saved and the "further Data option" of the PO message contains "requested processing" equal to the value of "send with application own transaction". This way, the actual messaging can be controlled in foreground and "breakpoints" can be set to display tables and fields. Behind the scenes, the message status program RSNAST00 is executed by ME9F program RM06ENDR_ALV. During this execution, it locates the message (NAST) record from the purchase order and the (TNAPR) configuration, which links the output type to the ABAP print program and SAPscript layout set. The specific problem is: in RSNAST00, the external call perform "PERFORM (TNAPR-RONAM) in PROGRAM (TNAPR-PGNAM) USING RETURNCODE US_SCREEN IF FOUND" does not pass NAST information to the called program (TNAPR-PGNAM). I know no NAST table information is passed because I set a break-point on the perform and single step to the print program. Therefore, the purchase order is unknown by the print program (TNAPR-PGNAM) and results in an error and no purchase order print is provided. Needless to say, this was tested with a new "Z" version of SAPLMEDRUCK. So, I changed the program name (output type processing routine) in configuration to SAPLMEDRUCK, but there again the NAST information is not passed to the print program from RSNAST00. Ironically, I reverted back to the older "z" version of SAPFM06P and NAST and TNAPR information is passed to the print program thru the external call perform quoted above. I prefer to not modify the SAP original code for RSNAST00, which is used in many other applications.
One other note, I had previously performed this maneuver on one different occasion with very successful results.
Has anyone ever encountered this problem in a 5.0 environment (running Windows NT and MSSQL and SAP BASIS 6.4).
I know this is long winded, but I wanted to explain the background of the entire situation.
Any and all help would be appreciated. Thanks in advance,

Dave,
Your entry points (like form ENTRY_NEU) should remain in your current version of SAPFM06P. Change that form to reflect the function calls in the new SAPLMEDRUCK form (ENTRY_NEU) (calls to ME_READ_PO_FOR_PRINTING and ME_PO_PRINT.
Look at the example below:
Here is the form in your old (Z) version of SAPFM06P:
FORM ENTRY_NEU USING ENT_RETCO ENT_SCREEN.
XSCREEN = ENT_SCREEN.
IF NAST-AENDE EQ SPACE.
   XDRUVO = '1'.
ELSE.
   XDRUVO = '2'.
ENDIF.
CLEAR: XFZ, XOFFEN, XLMAHN, XLPET.
*- Anstoß Verarbeitung -
CLEAR ENT_RETCO.
PERFORM LESEN USING NAST.
MOVE RETCO TO ENT_RETCO.
ENDFORM.
Here is form entry_neu in your new (Z) version of SAPFM06P:
INCLUDE FM06PE02                                                   *
form entry_neu using ent_retco ent_screen.
data: l_druvo like t166k-druvo,
        l_nast like nast,
        l_from_memory,
        l_doc   type meein_purchase_doc_print.
clear ent_retco.
if nast-aende eq space.
    l_druvo = '1'.
else.
    l_druvo = '2'.
endif.
call function 'ME_READ_PO_FOR_PRINTING'
       exporting
            ix_nast        = nast
            ix_screen      = ent_screen
       importing
            ex_retco       = ent_retco
            ex_nast        = l_nast
            doc            = l_doc
       changing
            cx_druvo       = l_druvo
            cx_from_memory = l_from_memory.
check ent_retco eq 0.
call function 'ME_PRINT_PO'
       exporting
            ix_nast        = l_nast
            ix_druvo       = l_druvo
            doc            = l_doc
            ix_screen      = ent_screen
            ix_from_memory = l_from_memory
            ix_toa_dara    = toa_dara
            ix_arc_params = arc_params
            ix_fonam       = tnapr-fonam          "HW 214570
       importing
            ex_retco       = ent_retco.
endform.
Remember, the form should be in the Z version of SAPFM06P - not the Z version of SAPLMEDRUCK. Make sure the configuration (TNAPR) has the SAPFM06P program name and entry point.
It should work. Let me know how it goes.
Rick

Finding output type and form for the transaction

hi all,
 i have a problem finding output type and form for the transaction j1iv .actually i need to find the standard output type and form name for the transaction j1iv. how can we do it.

Hi Abinash,
 Go through the following steps.
 1 . Go to the transaction NACE.
 2. You will be able to see the Application and description tab over
 there. Select the Application for which you need the output type.
 3. After selecting the Application..on the top you can see the tab--
 output types...click in that..here you will be able to see all the output
 types for that application.
 4. Now select a output type ..and on the left side u will be able to see
 the tab for processing routines...double click on it...
 5. Here you will be able to see the standard SAP program...the form
 routine...the form..attached to it..
 Please Reward..if helpful..
Regards,
Himanshu.

Output Types Processing Routines

Hi experts,
I need help regarding the Output Types Processing Routines.
In SAP, there are several Processing Routines, how does the processing routines work if you put a Program and Forms to Processing 1 and Processing 2?
Points will be rewarded.
Thanks....

Hi Salem,
When you execute a program through a transaction, then the first program and the first form are executed..
These entries are maintained in NAST table.. Now, the first o/p is displayed... When you press the BACK button on the o/p of first form screen, It goes back to the SAP code and check for the second entry if any, if it exists, it calls the second progarm and the second form.. and so on..
Thanks and Best Regards,
Vikas Bittera.
**Reward if useful**

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 Types and output determination procedure

Hi All,
What is the output type and output determination procedure for the following:
1) Credit Memo Request
2) Credit Memo
3) Debit Memo Request
4) Debit Memo
Regards
Ashis

Hi Ashis,
As per the standard
1) Credit Memo Request-
Procedure-V10000
Output type-BA00
2) Credit Memo
Procedure-V10000
Output type-RD00
3) Debit Memo Request
Procedure-V10000
Output type-RD00
4) Debit Memo
Procedure-V10000
Output type-BA00
I hope it will help you,
Regards,
Murali.

Output type and application for order cancellation

What is the output type and application for the cancellation of a sales order

Hi,
Try This
cancellation of sales order:
go to va02 enter the sales order and click enter
then sales document->delete
Reward if usefull

Regarding output type and idoc trigger issue

Hi
i need to copy pgi quantity into sales order quantity for that i write a code into user exit MV50AFZ1. code is working fine but
output type and idoc is not trigger due to this. In this exit to update sales order quantity i used bapi *BAPI_SALESORDER_CHANGE . can anyone tell me why o/p type and idoc not trigger ,what is the reason and what is the solution for this?
Thanks
Dinesh

Hi Dinesh,
Did you activate the enhancement for user exit ?
Did you check if the output type is configured correctly ?
Put a debugging point and see if control is coming there.
Regards,
Nisha Vengal.

Need Billing doc. number based on header Output type and also billing docum

Hi
I have header Output type and also billing document type.
will you please help me to get the billing document no. based on above combination, any SAP table, i was aware about the same. but i forgot the table name.
Thanks
Vanraj

Hi,
Check the Table NAST for the Billing documents associated with the OUTPUT type.
regards,
santosh

Table relation between Output Type and Spool

Hi all,
Is there a way to determine the table's relation between an Output Type and a Spool table for a printout.
Thanks
William Wilstoth

Hi,
See the Table TSP01 to store spool requests.
Regards,
Ballack.
Reward Points if helpful.

Link between output type and the email id in me22n ?

Hi,
Can anyone plz explain the link between the output type and the email id maintained in the address data in ME22n ?
The output type is configured fo rsending Email .Whenever i maintain the email id in the address data the outptu type gets triggered automatically but if I leave it as plank the output type does not get triggered.
Can any one explain this dependency?
thanks in advance
regards,
Ashwin

Hi,
It depends on the output record that you have used, what is the key?
It is no different that printed POs where the Printer Id is not specified in the communications tab of the output record. If the systen can't find where to send the output to it will not generate the record.
If it did generate the record without the email address, what would you expect to happen? Where could it send it?
It is far better to get the warning message "unable to determine ......" that to simply save the PO without the email addrerss.
So I would simply see the warning message as an indication that the email address is missing and fill it in before saving.
Steve B

Wrong output type and procedure

I have a problem when i choose the output type for my billing document it does not allow me to choose RD00 . Instead it give me a list of different output types which are listed in a different procedure under V3 application . I have defined my own procedure for RD00. How can i make sure that it chooses my procedure and output type and not someone else procedure and output type .
THANK YOU,
Alisha

Hi Alisha,
I think you have not assigned your o/p type to your O/Pprocedure.
Please check :
Use T/Code :NACE> Application V3-> Procedure-->Select your procedure --> choose "control" ---> Add your O/P here.
Hope this will work for you.
Lanka

Define Output type and Local destination per user

Hi Gurus,
Nowadays us have defined Output type by Sales Organiztion/Order Type (S_TCODE = VV11).
Is possible define Output type and Local destination per user?. How to do?.
thanks and best regards,
Wilson

Hi Wilson
As per my understanding of requirement: you want output type and Local destination for each SAP End user (i.e. who is processing sales order) not the customer. If this is the requirement, we have two solution for it:
1) If for a particular region/sales district customer are contacting to one particular destination, then create access sequence with output type/order type/sales district. Means for one sales district one Local destination. If sales district is big area and you have many local destination with in that, then you can divide it into regions.
2) Ask your ABAPer to create a Z table and maintain Local destination for all Users. And amend the print program such that before saving the output entry into NAST table, based on SY-UNAME(user's id), fetch the printer (local destination) from Z table and update the NAST table accordingly.
As per my observations, option 2 is simpler and more effective.
try and revert.

Difference between "output type" and "output medium" in interface

Can comebody kindly tell me the difference between "output type" and "output medium" with respect to interface?
Thanks,
Max

Hi,
Output medium means , how you wants to see the output like
Printout, Fax, Mail, or EDI output etc
Output type/Condition Type means for every Application document an Output type is create for the Output Message determination, this is linked with the Condition records, Medium, Program and the Output Script or smartform.
reward points if useful
regards,
ANJI

Output type and Routine

Similar Messages

Maybe you are looking for