Output Type Print Issue

Hi Experts ,
I have a output type ZDDC that is triggered from Shipment document and printed automatically at the end user . Now they dont want the print out automatically for only Belgium. Means ZZDC will be triggered but no auto print out for Belgium . What configuration modification is required for ZDDC so that it wont be printed at the user end automatically only for Belgium.Do I need to modify all the condition records maintained for ZDDC for Belgium . If so what Medium shall I choose or should I keep ..

If the users dont maintain condition record for Belgium, then your requirement would be addressed. On the other hand, if you want to prevent users maintaining condition record for this country, then the logic can be added in the existing smart form being used currently.
G. Lakshmipathi

Similar Messages

Creating output type for issuing print

hello friends
can anybody tell me the process or steps to create output type to issue print

HI.
Goto NACE transaction.
Select the application for whch you want to create the output type. For ex. select v3 for invoice.
Click on 'Output Types' button on application toolbar.
Click on 'New Entries'.
Click on Processing Routines on the left-side to enter the driver program and SAPscript/Smartform name.
Regards.
Jay

Output type print

Dear All
I select particular output type DC print . In that particular output type printing slowly 1 hr what is the reason
Thanks and Regards
Suresh

hi,
in the messages->further data under dispatch time give it as send immediately.
\[removed by moderator\]
siri
Edited by: Jan Stallkamp on Jul 24, 2008 12:43 PM

Output Type - Print Preview issue

Dear Friends,
I have an Output Type which when seen in the output preview / printing of billing doc shows the PO No. along with the other data.
The Output Type picks up the Sales Order no. from the table VBFA based on the billing doc no. and collects the preceding doc no. This preceding doc i.e. the Sales Order doc no. is then passed in the VBKD table along with the line item no. of the billing doc. and then the PO No. maintained at the item level is picked up from the field BSTKD by matching it with the line item no. of the Sales Order Doc No.
Now, I am facing a problem where when the PO No at the header level and the PO No of all the Item levels are same at the Sales Order doc, the output preview does not display the PO No. in the Output preview / print. This happens with only those sales order doc where the header level PO No. and Item level PO No. are the same. For rest other docs, things are running smooth.
Kindly suggest me with some solution.
Regards
Vineet Jain

When business data is the same on header and items, VBKD does not contain any lines for the items - it only contains a single line for the header where the item number is initial. This fails your logic of looking up VBKD by line numbers.
Edited by: Keerthi Hiremath on May 29, 2008 9:00 AM

Output type - LD03 issues

Hi friends,
I am having an issue with output type determination LD03 -packing slip. We are having three access sequences and condition tables. The condition records are also maintained.
Shipping point/ Route --- Printer A is assigned
Shipping Point/Delivery type---- Printer B is assigned
Shiiping point --- Printer C is assigned
When the shipping and route is 5000 and 0089 respectibely, the printer should be A. However the printer "C" is getting picked and printing there. What should be changed so that when the shipping point and route are 5000 and 0089 respectively. I have maintained a condition record with printed C. Why is the access sequence falling all the way to just shipping point???
Please advise

Dear Sanjay,
Please check the delivery or sales order route is getting determined or not.
If the route is not gettting determine then the system will pick the condition record based on shipping point only.
I hope this will help you,
Regards,
Murali.

Output type message issue

Hi experts,
I got an issue regarding po's output message related one
here is issue : In my production system some messages(NEU) type are deleted manually (in me22n).
next day to the same PO's NEU type message is sent to vendor with out physical trigger and with out any changes made to that PO's.
PO message settings : output type : purchase order(VN) , medium EDI ,date/dispatch time 4 ,send with periodically scheduled job
program : RSNAST00 job name : RSNAST00 ( i found it from tbtcp table)
here i want to track out why it was happening. I am abap developer.
where would be the problem is happening.my functional was saying that it was due to the job process which triggers program"RSNAST00 " in background.he was asking to check the current settings of that job process.
Even i tried to debug the RSNAST00 program. still i didn't found any solution for that .
here one more problem is : it was triggering output next day itself.my functional is asking to find out that from where it was extracting date and time to send output.
why it was sending output next day .why not it on that day itself.
thanks
konidala

Hi
If output is sent through periodically scheduled job.Then output is sent as per the schedule.
For eg,
You have scheduled a job RSNAST00 for evey monday 9 am.
Then it will process the output every monday 9am irrespective of time and date of output in PO.
To send out put immediatley make date/dispatch time 1(Send immediatley).
Hence check the job for time,day or date scheduled make necessary changes if required.
Use SM36 tcode or you can find it is tbtcp table also.

Output type - Print preview Commodity code

Hi All,
I have created an F8 billing document and I can see the commodity code in the foreign trade tab.
Is there standard output type which I can use to view the invoice and see if the commodity code is getting printed?
Any ideas?
Regards,
Meghna

When business data is the same on header and items, VBKD does not contain any lines for the items - it only contains a single line for the header where the item number is initial. This fails your logic of looking up VBKD by line numbers.
Edited by: Keerthi Hiremath on May 29, 2008 9:00 AM

WE03 Output type with print version '3' (Collective Slip)

I am using output type WE03 with combination of print version 3 (Collective Slip) to print GR slips.
My requirement is to print all the line items on single page (unless there is no room) .
However with this output type one line item is printed per page.
Does anyone manage to print items continously on the page without page break?
Is there any other output type/print version for that?
Well, the last option will be to change the print program and sapscript, but I am trying to avoid that...

Created new print program and replaced sapscript with smartform

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

Configuring output type

Dear experts,
We have attached using NACE smartform for deliveryNote.
I select the output type which is ZD00.
Form preview opens as i have defined preview option only in my code.User goes to Text->Print.
Print is fired .But i get message "output cannot be issued."
Further no entry goes in nast and output type ZD00 comes
yellow triangle.I have used function module for NAST updation.
But it is not working here.I want to define output type ZD00
from my code itself so that i get Output issued succesfully.
and could see green triangle on print out.Simultaneously
nast entry should be populated.
st_control_parameters-preview = 'X'.
st_control_parameters-device = 'PRINTER'.
st_control_parameters-no_dialog = 'X'.
st_output_options-tddest     = 'ZERP'.
st_output_options-tdimmed   = 'X'.
CALL FUNCTION FM_NAME
EXPORTING
ARCHIVE_INDEX              =
ARCHIVE_INDEX_TAB          =
ARCHIVE_PARAMETERS         =
    CONTROL_PARAMETERS         = st_control_parameters
MAIL_APPL_OBJ              =
MAIL_RECIPIENT             =
MAIL_SENDER                =
    OUTPUT_OPTIONS             = st_output_options
    USER_SETTINGS              = ' '
IMPORTING
DOCUMENT_OUTPUT_INFO       =
JOB_OUTPUT_INFO            =
JOB_OUTPUT_OPTIONS         =
TABLES
    i_header                   = i_heading1
    i_detail                   = i_lipsvbap
EXCEPTIONS
   FORMATTING_ERROR           = 1
   INTERNAL_ERROR             = 2
   SEND_ERROR                 = 3
   USER_CANCELED              = 4
   OTHERS                     = 5
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
CALL FUNCTION 'NAST_PROTOCOL_UPDATE'
EXPORTING
    msg_arbgb                    = SYST-MSGID
    msg_nr                       = SYST-MSGNO
    msg_ty                       = SYST-MSGTY
    MSG_V1                       = SYST-MSGV1
    MSG_V2                       = SYST-MSGV2
    MSG_V3                       = SYST-MSGV3
    MSG_V4                       = SYST-MSGV4
EXCEPTIONS
    MESSAGE_TYPE_NOT_VALID       = 1
    NO_SY_MESSAGE                = 2
    OTHERS                       = 3
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.

When a Output type in an apllication doc is configured with a Medium, Partner, Lang and other communication paramters an entry is created in NAST table
so to trigger the output an entry in NAST is compulsory
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?
u2022 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.
u2022 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.
u2022 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.
u2022 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.
u2022 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.
u2022 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).
u2022 Printer driver: You can specify different printer drivers for printing SAPscript documents and ABAP lists.
u2022 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.
u2022 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).
u2022 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.
u2022 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.
Nace

Two output type

Hi Gurus,
I've a typical issue here.
I've two output types for sales order .Maintain condition record ,access sequence,VOFM routines individually perfectly for both output types.
1st output type - no multiple issue..(maintained in NACE)
2nd output type - multiple issue.(maintained in NACE properly)
While creating order both outputs are issued(fine).
But while changing order, 2nd output type has to be issued but its not.
When I debugged , its looping the entries already present in NAST table.(checking the first output type for multiple issue)
its not and then its completely coming out of the program without checking the second output type for multiple issue.
Is there any extra settings I've to do or its SAP bug.
Regards,
Ponraj.s.

Hi,
There are two options.
First is, use the same output type for all the movement types. Iin the smartform itself you can put conditions
based on movement type to call a particular window.
Other options is in SPRO->Materials Management->Inventory Management and Physical Inventory->Print Control
->Maintain Print Indicator for Goods Receipt Documents. Maintain different indicators for 102 and 122 (For ex. 2)
Then maintain the condition record for the output types WE02 and ZA01 accordingly.
Maintain output type WE02 for Trans./Event Type - WE, Print Version - 1 or 2 or 3 and Print Item as 1.
Maintain output type ZA01 for Trans./Event Type - WE, Print Version - 1 or 2 or 3 and Print Item as 2.

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

How to define output types email or external send in the report program

Hi all,
now we are using a zprogram for output type printer and standard program RVADOR01 for output type external send. Now i want to modify my zprogram itself to support external send email as well as printer also. What modifications should I have to make in my zprogram. My form is a script.
Thank you,
Mallik

hi all,
i made the following changes in my code and it worked well.
thank you for all who tried to share my pain.
thanks one and all.
hope this code will help anybode.
thanks & regards
FORM OPEN_FORM_EMAIL.
TABLES: TNAPR,                         "Programs & Forms
        ITCPO,                         "Communicationarea for Spool
        ARC_PARAMS,                    "Archive parameters
        TOA_DARA,                      "Archive parameters
        ADDR_KEY.                      "Adressnumber for ADDRESS
TYPE-POOLS SZADR.
DATA: LVF_DEVICE LIKE ITCPP-TDDEVICE,
      LVF_DIALOG(1)     TYPE   C   VALUE ' ',
      LVS_RECIPIENT     LIKE   SWOTOBJID,
      LVS_SENDER        LIKE   SWOTOBJID,
      LVS_SNAST         TYPE   SNAST,
      LVF_PROGRAM       LIKE   SY-REPID,
      LVS_COMM_TYPE     TYPE   AD_COMM,
      LVS_COMM_VALUES   TYPE   SZADR_COMM_VALUES,
      LVS_TITLE LIKE SNAST-TDCOVTITLE.
reset return code
RETCODE = 0.
if there is a communication strategy used ...
IF NOT NAST-TCODE IS INITIAL AND NAST-NACHA EQ '5'.
... use stratagy to get communication type
    CALL FUNCTION 'ADDR_GET_NEXT_COMM_TYPE'
         EXPORTING
              STRATEGY           = NAST-TCODE
            ADDRESS_TYPE       =
             ADDRESS_NUMBER     = KNA1-ADRNR
            PERSON_NUMBER      = VBDKA-ADRNP
              PERSON_NUMBER      = ADDR_KEY-PERSNUMBER
         IMPORTING
              COMM_TYPE          = LVS_COMM_TYPE
              COMM_VALUES        = LVS_COMM_VALUES
       TABLES
            STRATEGY_TABLE     =
         EXCEPTIONS
              ADDRESS_NOT_EXIST = 1
              PERSON_NOT_EXIST   = 2
              NO_COMM_TYPE_FOUND = 3
              INTERNAL_ERROR     = 4
              PARAMETER_ERROR    = 5
              OTHERS             = 6.
    IF SY-SUBRC <> 0.
      RETCODE = SY-SUBRC.
      SYST-MSGTY = 'E'.
      PERFORM PROTOCOL_UPDATE.
    ENDIF.
ENDIF.
   LVS_COMM_TYPE = 'INT'.
CLEAR LVS_COMM_VALUES-ADSMTP-SMTP_ADDR.
CLEAR LVS_SNAST.
        LVS_COMM_VALUES-ADSMTP-SMTP_ADDR = V_CUST_EMAIL.
convert communication data
   MOVE-CORRESPONDING NAST TO LVS_SNAST.
        LVS_SNAST-ANZAL = 1.
        LVS_TITLE = 'Mail Header Title'.
MOVE LVS_TITLE TO LVS_SNAST-TDCOVTITLE.
   MOVE SY-REPID TO LVF_PROGRAM.
CALL FUNCTION 'CONVERT_COMM_TYPE_DATA'
       EXPORTING
            PI_COMM_TYPE              = 'INT'
            PI_COMM_VALUES            = LVS_COMM_VALUES
            PI_SCREEN                 = XSCREEN
          PI_NEWID                  =
            PI_COUNTRY                = ADRC-COUNTRY
            PI_REPID                  = SY-REPID
            PI_SNAST                  = LVS_SNAST
            PI_MAIL_SENDER            = SY-UNAME
       IMPORTING
            PE_ITCPO                  = ITCPO_LS
            PE_DEVICE                 = LVF_DEVICE
            PE_MAIL_RECIPIENT         = LVS_RECIPIENT
            PE_MAIL_SENDER            = LVS_SENDER
       EXCEPTIONS
            COMM_TYPE_NOT_SUPPORTED   = 1
            RECIPIENT_CREATION_FAILED = 2
            SENDER_CREATION_FAILED    = 3
            OTHERS                    = 4.
IF SY-SUBRC <> 0.
    RETCODE = SY-SUBRC.
    SYST-MSGTY = 'E'.
    PERFORM PROTOCOL_UPDATE.
ENDIF.
CHECK RETCODE EQ 0.
fill structure itcpo
ITCPO = ITCPO_LS.
open form
CALL FUNCTION 'OPEN_FORM'
       EXPORTING
          APPLICATION        = 'TX'
           ARCHIVE_INDEX      = TOA_DARA
           ARCHIVE_PARAMS     = ARC_PARAMS
            DEVICE             = 'MAIL'
            DIALOG             = 'X'
            FORM               = 'ZSDLS003'
            LANGUAGE           = SY-LANGU
            OPTIONS            = ITCPO_LS
            MAIL_SENDER        = LVS_SENDER
            MAIL_RECIPIENT     = LVS_RECIPIENT
          MAIL_APPL_OBJECT   = ' '
          RAW_DATA_INTERFACE = '*'
     IMPORTING
          LANGUAGE           =
          NEW_ARCHIVE_PARAMS =
          RESULT             =
       EXCEPTIONS
            CANCELED           = 1
            DEVICE             = 2
            FORM               = 3
            OPTIONS            = 4
            UNCLOSED           = 5
            MAIL_OPTIONS       = 6
            ARCHIVE_ERROR      = 7
            OTHERS             = 8.
IF SY-SUBRC NE 0.
    CASE SY-SUBRC.
      WHEN 7.
        RETCODE = SY-SUBRC.
        SYST-MSGID = 'VN'.
        SYST-MSGNO = '096'.
        SYST-MSGTY = 'E'.
        SYST-MSGV1 = NAST-KSCHL.
        SYST-MSGV2 = NAST-KAPPL.
        PERFORM PROTOCOL_UPDATE.
      WHEN OTHERS.
        RETCODE = SY-SUBRC.
        PERFORM PROTOCOL_UPDATE.
    ENDCASE.
ENDIF.
SET COUNTRY ADRC-COUNTRY.
ENDFORM.

Automatic Creation of PO's - Output Types?

Our company is thinking about creating PO's automatically and we are stuck at the output determination phase.
The way the system is designed now, when buyers create PO's, they select Message Type NEU and then they have the option of picking either Print or Fax.
For Automatic PO's is there a way we can do this by assigning some materials to Output Type Print and some to Fax?
Perhaps by Purchasing Group(I tried this but I was just able to choose different printers).
Or Info Record?
Please advice.
Thanks

Hi
Please try to maintain the condition record in MN04 as per yr requirement.
Thanks/karthik

PO output type.

Hi,
I am trying to send a PO through EDI but I get a status of yellow.
I tried to repeat output for a successfully sent PO but even that gave a status of yellow.
I went to NACE to see the config but everything seems to be alright.
Can't figure out the reason.
Please help.
Thanks,
Sandeep.

Hi,
check the following in sequence:
1. In the PO against the Output type you have to assign some Medium on the same line along with Parter fuction and Langu. What was assigned there is it ALE or something?
2. Check in the NACE transaction against that Output type, Print Program,Form what's the medium assigned.
In the above two cases also if you assigned something other than ALE medium if it is still coming as ALE then check in SPRO settings and in Condition records settings,
Some where it was fixed/assigned as ALE to take as Default.
reward if useful
regards,
Anji

Output Type Print Issue

Similar Messages

Maybe you are looking for