RFQ Output Determination Schema

Hi all,
I am trying to create a new message determination schema for RFQ print out. The aim is to include plant code in the message determination schema. We have previously configurfed this for PO.
However, when we tried to create the condition table in transaction M/58, plant code is not in the field catalog.
May I know how I can add plant code in the field catalog for condition table (Output purchasing RFQ)?
Thanks!

Thanks for the quick reply.
I've added plant code WERKS into the RFQ output field catalog via maintenance of view  V_T681F via SM30.
I then created the condition table in M/58 and assigned it to the RFQ access sequence.
I've also maintained the message output for RFQ via transaction MN01.
However, the output message type is not triggered even when I create a RFQ with the specified plant code maintained in MN01.
Any idea?
Edited by: Jit Wei Tan on Aug 23, 2011 2:34 PM

Similar Messages

  • RFQ Output determination

    Hi,
    I want to know how can I configure the output determination for RFQ for mails to be sent when we save a RFQ.
    Regards,
    Sachin

    Hi ,,,
    1.Create Message Type(ex. xneu)and set the Dispatch Time
           as 4( Sent after Saving) and set the Transmission Medium.
    2.Assign this Message Type in the Message Determination
           Schema for RFQ(RMBEA1).
    3.Create Condition Records by T-Code- MN01.
    4.You can Trigger the Output if needed by T-Code - ME9A
    Hope this helps to solve your requirement....
    Thanks and Regards
    R.B.K.Kannan

  • Output Determination for Material movement

    Hi All,
    I am configuring output Determination for Material movement.
    In my case, am doing the config when the movement type is 311, we want to generate IDoc.
    i have configured everything, output type,output Determination schema..
    When i am trying to maintain the condition record for the same through MN21,
    here i am facing one problem on Partner Function.
    Here what partner functuion i'll give.
    waiting for all valuable response.
    Regards
    Indrashish

    Hello Indrashish,
    Maintain that output type as partner independent.
    This will help.
    Regards
    Arif Mansuri

  • Output determination for PR, RFQ, Contracts

    Hello,
    I want the detailed stepwise procedure for the output determination of PR, RFQ, Quotation Comparison and Contracts in SAP. I have to first check the std printout and then customize it as per clients requirement. Quick response would be very much appreciated.
    Regards,
    Prasanna.

    1.  Check to what extent you can utilize the condition tables included
        in the SAP standard system for message control.
    2.  If you want to create a new condition table, proceed as follows:
        -   Enter the name of the table you want to create. Note that you can only choose names between 501 and 999.
        -   If you are creating without referencing, enter the table category (e.g. pool table) for the condition table.      
        -   Enter a description (title) for the condition table.
        -   From the list of allowed fields, choose the desired fields for the condition table.
        -   Generate the new condition table.
        -   Define the new condition tables.
    3.  Enter the condition tables in the access sequences ( The access sequence is a search strategy by means of which the SAP
        system searches for valid message records.)
        This way, you establish the link between message condition, access sequence and message record.
    4. define a message type, you must enter the following:
    Message type
    Alphanumeric key of up to 4 characters, uniquely identifying a
    message type.
    Access sequence
    Key for the access sequence.
    Description
    Text describing the message type.
    Detail data (only the most important data is described):
    -   Transmission medium
         One-character numeric key determining the type of message processing (e.g. printout, transmission as fax or e-mail).
    -   Time-spot
         One-character numeric key defining the point in time at which message processing takes place (e.g. immediately a document is
         saved or with the next selection run).
    -   Partner role
         Partner role defining the recipient.
    -   Condition access
         Indicator allowing you to specify that the default value for the relevant message is to be determined using the condition
    The values entered in the detail data for transmission medium, time-spot, and partner role are automatically adopted as default
    values when a message record of the relevant message type is created.
    Set up fine-tuned control for each message type
    For each type of message you create, you must specify the operations for which it is to be used.
    For example: New (original) output, output of change notices, or output of urging messages (expediters).
    First choose "Perform function" and then "Purchasing document ->
    Purchase order -> Messages -> Fine-tuned control". You must do this for all purchasing documents.
    5. Define your message determination schemas and assign them to the relevant purchasing documents.
    A message determination schema contains the permissible message types for each message application (new printout, reminder, etc.). This allows the system to automatically suggest the associated messages as defaults in purchasing documents.
    Only one schema and only one message type can be assigned to each purchasing document.
    6. Specify which partner roles are allowed for the message type in connection with each individual purchasing document.

  • Purchase Order and GR document Output Determination and creating own logo o

    Can anyone let me know the process of output determination of PO and GR documents.
    Also let me know the way to incorporate my own logo on the documents

    Hi sudip
    For the logo on documents, you have to take help of ABAP ppl.
    Output of Purchase Order
    1. Condition Table
    SPRO > Material Management> Purchasing -> Message -> Output Control->Condition Tables->Define Condition Table for Purchase Order
    Select: 
    Purchasing Doc. Type,
    Purch. Organization,
    Vendor
    2. Access Sequences
    SPRO -> Material Management-> Purchasing -> Message -> Output Control->Access Sequences->Define Condition Table for Purchase Order
    3. Message Type
    SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Types->Define Message Type for Purchase Order
    *4. Message Determination Schemas*
    4.1. Message Determination Schemas
    SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Schema->Define Message Schema for Purchase Order-> Maintain Message Determination Schema
    4.2. Assign Schema to Purchase Order
    SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Schema->Define Message Schema for Purchase Order-> Assign Schema to Purchase Order
    5. Partner Roles per Message Type
    SPRO -> Material Management-> Purchasing -> Message -> Output Control-> Partner Roles per Message Type ->Define Partner Role for Purchase Order
    6. Condition Record
    Navigation Path: SAP Menu-> Logistics -> Material Management -> Purchasing-> Master data->Messages-> Purchase Order-> MN04-> Create
    Now you create PO (ME21N) and save it. Go to ME22N and print the PO by giving output type.
    Output of GR
    After setting table, access sequence and output type for GR,run MB02 transaction, enter material document number. Double click one line item and select messages. Separate screen will be opened to configure outputs. Give the required fields and save the document. 
    Now Run MB90, you can take printout. Output Type: WE03 or WE01 or WE02

  • How to re-run output determination after goods issue through idoc

    Hello,
    i've got a question about output determination. We are currently in a process to automate picking, packing and goods issue through a 3rd party software. The software creates DELVRY03-Idocs including picking, packing and goods issue-information. Picking, packing and goods issue work just find and after submitting the idoc, the delivery is updated as needed.
    The problem arises when it comes to printing the shipping document on the printer belonging to the picking station that just processed the delivery. To determine the correct printer, the external software includes the picking station number inside the idoc. A user exit in idoc_input_delivery puts the number (3 digits) into likp-traid. The customizing for using this field inside output determination is complete and seems to be working.
    The problem is: as the number of the picking station is not known before goods issue, the LD00 message must not be generated before goods issue. I used the appropriate condition insinde the message scheme, the message is not generated until goods issue is complete. After processing the DELVRY03-Idoc, the message should be found and generated, but it isn't. When i take a look at the delivery after submitting the idoc, goods issue is complete, picking and packing is done - and no sign of an header message of type LD00. First i thought about a misconfiguration inside my customizing for output determination, but when i access the delivery via vl02n (change delivery), output determination seems to be processed again and without making any changes or actions, LD00 is generated and waiting for processing. After saving the delivery, LD00 is processed and the shipping document is printed exactly where it should be.
    So, as my customizing seems to work and everything else around idoc processing doesn't make any problems either, i conclude that, after processing the idoc, R/3 just needs a little kick to re-run the output determination, find the now fitting condition for LD00, find the appropriate entry in the condition table and print the document.
    I already tried report rsnast00, but this one just seems to run already created messages.
    Any ideas how to automate this little "kick in the butt"?
    Thanks in advance!

    I'm working on a similar issue with ws_delivery_update. I'm not using the IDOC as you are, but I'm using the function in a program of mine to PGI the delivery, but the output isn't being added to the delivery. I've tried to run the function twice as you suggested, but that doesn't seem to work. Do you have any suggestions or ideas on things to try?
    Thanks,
    Eric

  • Output determination for PO

    Hi, I don't have much knowledge,waht are the steps and settings  required to maintain output determination for purchase order and material document.
    Thank you.

    Hi,
    PO Output
    Output of Purchase Order
    1. Condition Table
    SPRO > Material Management> Purchasing -> Message -> Output Control->Condition Tables->Define Condition Table for Purchase Order
    Select:
    Purchasing Doc. Type,
    Purch. Organization,
    Vendor
    2. Access Sequences
    SPRO -> Material Management-> Purchasing -> Message -> Output Control->Access Sequences->Define Condition Table for Purchase Order
    3. Message Type
    SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Types->Define Message Type for Purchase Order
    4. Message Determination Schemas
    4.1. Message Determination Schemas
    SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Schema->Define Message Schema for Purchase Order-> Maintain Message Determination Schema
    4.2. Assign Schema to Purchase Order
    SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Schema->Define Message Schema for Purchase Order-> Assign Schema to Purchase Order
    5. Partner Roles per Message Type
    SPRO -> Material Management-> Purchasing -> Message -> Output Control-> Partner Roles per Message Type ->Define Partner Role for Purchase Order
    6. Condition Record
    Navigation Path: SAP Menu-> Logistics -> Material Management -> Purchasing-> Master data->Messages-> Purchase Order-> MN04-> Create
    Now you create PO (ME21N) and save it. Go to ME22N and print the PO by giving output type.
    GR Output
    Output of GR
    After setting table, access sequence and output type for GR,run MB02 transaction, enter material document number. Double click one line item and select messages. Separate screen will be opened to configure outputs. Give the required fields and save the document. Now Run MB90, you can take printout. Output Type: WE03 or WE01 or WE02
    Regards,
    Biju K

  • Purchase order output determination thru User exit

    Hi,
    We are trying to find a way to determine the output for PO while creation (me21n) or modification (me22n).
    We do not want to maintain output condition records for each fax/print/email etc..cases.
    Can we do below thru a user exit or any other method ?
    While creating PO, an OA partner will be chosen, so instead of maintaining the output condition records,
    - user exit can access to OA's vendor master record and read Standard Comm.Method in Address section.
    - according to comm.method, the PO message should be determined..
    i.e: if comm.method is Fax, then message should be sent to OA thru Fax.
    can this be done thru an exit ?
    Thanks and Regards,
    Ocal

    Hi Stefan,
    The steps are as follows:
    Output of Purchase Order
    1. Condition Table
    SPRO > Material Management> Purchasing -> Message -> Output Control->Condition Tables->Define Condition Table for Purchase Order
    Select: 
    Purchasing Doc. Type,
    Purch. Organization,
    Vendor
    2. Access Sequences
    SPRO -> Material Management-> Purchasing -> Message -> Output Control->Access Sequences->Define Condition Table for Purchase Order
    3. Message Type
    SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Types->Define Message Type for Purchase Order
    *4. Message Determination Schemas*
    4.1. Message Determination Schemas
    SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Schema->Define Message Schema for Purchase Order-> Maintain Message Determination Schema
    4.2. Assign Schema to Purchase Order
    SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Schema->Define Message Schema for Purchase Order-> Assign Schema to Purchase Order
    5. Partner Roles per Message Type
    SPRO -> Material Management-> Purchasing -> Message -> Output Control-> Partner Roles per Message Type ->Define Partner Role for Purchase Order
    6. Condition Record
    Navigation Path: SAP Menu-> Logistics -> Material Management -> Purchasing-> Master data->Messages-> Purchase Order-> MN04-> Create
    Now you create PO (ME21N) and save it. Go to ME22N and print the PO by giving output type.
    Reward me if it helpful
    ASHOK

  • Urgent - Automatic output determination for PO doc type

    Hello all,
    I have created an output type along the lines of NEU and maintained all the necessary setting. new outpout type is ZNEU. I want this to be triggered when i save my PO with new PO order type ZS.
    However, when i save my PO type ZS no output determination takes place.
    Where exactly is the link between PO type ZS and output type ZNEU.
    Any help will be appreciated.
    regards
    s Datar

    Check all the settings as mentioned below
    PO Output
    Output of Purchase Order
    1. Condition Table
    SPRO > Material Management> Purchasing -> Message -> Output Control->Condition Tables->Define Condition Table for Purchase Order
    Select:
    Purchasing Doc. Type,
    Purch. Organization,
    Vendor
    2. Access Sequences
    SPRO -> Material Management-> Purchasing -> Message -> Output Control->Access Sequences->Define Condition Table for Purchase Order
    3. Message Type
    SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Types->Define Message Type for Purchase Order
    4. Message Determination Schemas
    4.1. Message Determination Schemas
    SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Schema->Define Message Schema for Purchase Order-> Maintain Message Determination Schema
    4.2. Assign Schema to Purchase Order
    SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Schema->Define Message Schema for Purchase Order-> Assign Schema to Purchase Order
    5. Partner Roles per Message Type
    SPRO -> Material Management-> Purchasing -> Message -> Output Control-> Partner Roles per Message Type ->Define Partner Role for Purchase Order
    6. Condition Record
    Navigation Path: SAP Menu-> Logistics -> Material Management -> Purchasing-> Master data->Messages-> Purchase Order-> MN04-> Create
    Now you create PO (ME21N) and save it. Go to ME22N and print the PO by giving output type.
    GR Output
    Output of GR
    After setting table, access sequence and output type for GR,run MB02 transaction, enter material document number. Double click one line item and select messages. Separate screen will be opened to configure outputs. Give the required fields and save the document. Now Run MB90, you can take printout. Output Type: WE03 or WE01 or WE02
    Regards,

  • OutPut as a PDF doc for Output Determination process of a PO

    Hi
    Can I get the OutPut as a PDF document for OutPut Determination process of a PO for a Vendor.
    My schema should produce a PDF file and get transmitted to that Vendor as soon i save my PO.
    Also can i get any SAP document on this.
    Pls help me. Swifty reply me.
    cheers
    MaruthiRam

    Hi,
    PO can be sent to using Outlook email or the Internal send within SAP.
    Message via E-Mail
    Use
    You can send purchasing documents to a vendor by e-mail.
    You can also send memos to an internal user from within the purchasing document, in which case the recipient can directly access the relevant document when processing the e-mail (executable mail).
    Prerequisites
    External Transmission
    Make the necessary Customizing settings
    The SAP system is configured for the transmission of external mails.
    The message determination facility has been set up in Customizing for Purchasing.
    You have defined a communication strategy in Customizing under Messages Output Control -> Message Types -> Define Message Types for <Purchasing Document> -> Maintain Message Types for <Purchasing Document> on the Default Values tab page, so that if no e-mail address can be found, for example, the system sends a fax.
    The following information is necessary:
    1.Data
    2.Value
    3.Comment
    Message type:
    Communication strategy
    E.g. NEU
    Choose a communication strategy or create a new one. Via the input help, you can branch to the maintenance function for communication strategies. Choose in the following window.
    Enter the necessary data on the Default Values tab page on the detail screen for the message type ().
    Processing routines
    Medium
    Program
    FORM routine
    5 (external transmission)
    SAPF06P (e.g. for PO)
    ENTRY_NEU
    The entries are identical to those of the print output.
    Partner roles
    E.g. external transmission/LF
    Maintain master data
    Message records must have been created through master data maintenance (Purchasing menu). (See Creating Message Records)
    Enter the necessary data u2013 for example, role LF (vendor), medium 5 (external transmission) and time spot 4 (send immediately upon saving).
    SAP recommends that you work with time spot 4, so that the e-mails generated are sent immediately.
    If you work with processing time spot 1 (send via periodically scheduled job), you must schedule the program RSNAST00 periodically for message output, so that messages are generated and e-mails sent.
    An e-mail address is stored in the vendor master record.
    An e-mail address is stored in the user master record.
    Please note that you must also maintain an e-mail address for user IDs with which batch-jobs are carried out.
    Internal Transmission
    Make the necessary Customizing settings:
    You have maintained the Customizing settings for Purchasing under Messages, Output Control -> Message Types ->Define Message Types for <Purchasing Document> -> Maintain Message Types for <Purchasing Document>.
    The following information is necessary:
    1.Data
    2.Value
    3.Comment
    Message type:
    Time-spot
    Transmission medium (output medium)
    Partner role
    E.g. MAIL
    E.g. 4 (send immediately upon saving)
    7 (SAPoffice)
    MP (mail partner)
    Enter the necessary data on the Default Values tab page on the detail screen for the message type ().
    Mail title and texts
    E.g. mail from purchase order
    Processing routines
    Medium
    Program
    FORM routine
    7 (SAPoffice)
    RSNASTSO
    SAPOFFICE_AUFRUF
    Partner roles
    E.g. SAPoffice/MP
    SAPoffice/LF
    Maintain master data
    Message records must have been created for the message type MAIL through master data maintenance (Purchasing menu). (See Creating Message Records)
    For more information on the internal and external transmission of e-mails, refer to the Basis documentation under Business Workplace (BC-SRV-GBT).
    Further information on external transmission is available in the Basis documentation under SAPconnect and in the section External Sending in the SAP System.
    Activities
    External Transmission
    If you have specified the processing time-spot 4 (send immediately upon saving), the system will immediately generate and transmit a message when you save the purchasing document.
    If you have specified the processing time-spot 1 (send via periodically scheduled job), you must initiate the output of e-mails manually.
    Result
    You see the documents generated in the SAP system under Office ->Work center -> Outbox -> Documents.
    Internal Transmission
    On the message screen of the Purchasing application (e.g. in the purchase order), enter the message type, the medium (SAPoffice) and the role (MP = mail partner).
    Choose Means of communication and enter your text on the following screen (<Purchasing document>: Send with note). Enter the useru2019s first and last names, for example, in the Recipient field.
    Executable mail
    If you wish to insert a transaction (because you want the recipient to view a purchase order, for example), choose Goto -> Execution parameters. Enter the necessary data, such as execution type (T = transaction), execution element (ME22N = Change Purchase Order), execution system, and the SET/GET parameters (BES for purchase order).
    Result
    If you have specified send immediately as the processing time-spot, the user will immediately receive a message or document when the purchase order is saved.
    The user can view the message sent to him or her via Office -> Work center -> Inbox.
    If the document in your inbox is an executable mail, you can click the right-hand mouse button and directly access the relevant purchase order, for example, via the menu thus displayed.
    Hope it works...
    Regards,
    Kiran

  • How is Output determination done for a PO ??

    Hi
    How is Output determination done for a PO ??
    I need the O/P to the vendor sent in the form of a PDF file.
    is it possible !!
    cheers
    Maruthi

    Hi,
    1. Condition Table
    SPRO > Material Management> Purchasing -> Message -> Output Control->Condition Tables->Define Condition Table for Purchase Order
    Select: 
    Purchasing Doc. Type,
    Purch. Organization,
    Vendor
    2. Access Sequences
    SPRO -> Material Management-> Purchasing -> Message -> Output Control->Access Sequences->Define Condition Table for Purchase Order
    3. Message Type
    SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Types->Define Message Type for Purchase Order
    *4. Message Determination Schemas*
    4.1. Message Determination Schemas
    SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Schema->Define Message Schema for Purchase Order-> Maintain Message Determination Schema
    4.2. Assign Schema to Purchase Order
    SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Schema->Define Message Schema for Purchase Order-> Assign Schema to Purchase Order
    5. Partner Roles per Message Type
    SPRO -> Material Management-> Purchasing -> Message -> Output Control-> Partner Roles per Message Type ->Define Partner Role for Purchase Order
    6. Condition Record
    Navigation Path: SAP Menu-> Logistics -> Material Management -> Purchasing-> Master data->Messages-> Purchase Order-> MN04-> Create
    Now you create PO (ME21N) and save it. Go to ME22N and print the PO by giving output type.
    Output of GR
    After setting table, access sequence and output type for GR,run MB02 transaction, enter material document number. Double click one line item and select messages. Separate screen will be opened to configure outputs. Give the required fields and save the document. 
    Now Run MB90, you can take printout. Output Type: WE03 or WE01 or WE02
    Thanks,

  • PO delete after output determination.

    Dear Expert,
    Is there is any option to delete PO after output determination.Release indicator 2,3 is in the release strategy.Please help me how to solve this problem?
    Regards
    Tanmoy_mm.

    Output of Purchase Order
    1. Condition Table
    > SPRO > Material Management> Purchasing ->               > Message -> Output Control->Condition Tables->Define       > Condition Table for Purchase Order
    Select:
    Purchasing Doc. Type,
    Purch. Organization,
    Vendor
    2. Access Sequences
    > SPRO -> Material Management-> Purchasing -> Message -> Output Control->Access Sequences->Define Condition       > Table for Purchase Order
    3. Message Type
    > SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Types->Define Message Type for > Purchase Order
    4. Message Determination Schemas
    4.1. Message Determination Schemas
    > SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Schema->Define Message        > Schema for Purchase Order-> Maintain Message              > Determination Schema
    4.2. Assign Schema to Purchase Order
    > SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Schema->Define Message         > Schema for Purchase Order-> Assign Schema to Purchase > Order
    5. Partner Roles per Message Type
    > SPRO -> Material Management-> Purchasing -> Message -> Output Control-> Partner Roles per Message Type ->Define > Partner Role for Purchase Order
    6. Condition Record
    > Navigation Path: SAP Menu-> Logistics -> Material           > Management -> Purchasing-> Master data->Messages->  > Purchase Order-> MN04-> Create
    Now you create PO (ME21N) and save it. Go to ME22N and print the PO by giving output type.

  • Output determination and Printer determination for  both PO and GR

    Dear all,
    Can anyone please help me in congiguring the output determination and printer determination for  both PO and GR. please give me detailed configuration including the paths as i am stuck with the configuration.
    Thanks & Warm Regards
    Somashekar Anand

    hi Somashekar
    follow he steps
    Output of Purchase Order
    1. Condition Table
    SPRO > Material Management> Purchasing -> Message -> Output Control->Condition Tables->Define Condition Table for Purchase Order
    Select:
    Purchasing Doc. Type,
    Purch. Organization,
    Vendor
    2. Access Sequences
    SPRO -> Material Management-> Purchasing -> Message -> Output Control->Access Sequences->Define Condition Table for Purchase Order
    3. Message Type
    SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Types->Define Message Type for Purchase Order
    *4. Message Determination Schemas*
    4.1. Message Determination Schemas
    SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Schema->Define Message Schema for Purchase Order-> Maintain Message Determination Schema
    4.2. Assign Schema to Purchase Order
    SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Schema->Define Message Schema for Purchase Order-> Assign Schema to Purchase Order
    5. Partner Roles per Message Type
    SPRO -> Material Management-> Purchasing -> Message -> Output Control-> Partner Roles per Message Type ->Define Partner Role for Purchase Order
    6. Condition Record
    Navigation Path: SAP Menu-> Logistics -> Material Management -> Purchasing-> Master data->Messages-> Purchase Order-> MN04-> Create
    Now you create PO (ME21N) and save it. Go to ME22N and print the PO by giving output type.
    Output of GR
    After setting table, access sequence and output type for GR,run MB02 transaction, enter material document number. Double click one line item and select messages. Separate screen will be opened to configure outputs. Give the required fields and save the document. Now Run MB90, you can take printout. Output Type: WE03 or WE01 or WE02
    Reward points if helpful
    Thanks and regards
    Ravikant Dewangan

  • Schedule Agreement Message Output Determination

    Hi Vishal
    Can you give me some more details for Configuring the Schedule Agreement Output Determination in the same manner for which you have given for a PO.
    My scenerio:
    Making a contract with a Vendor --> Maintain Source list --> Giving MRP indicator as 2 in the source list for that delivery --> Running MRP for that material --> Checking the Schedule lines are generated in the Stock/Req list --> Now the schedule lines should send message output to the vendor via EDI/Print.
    So give the answer relevant to above situation.
    points already awarded to the previous question.
    Thanks Vishal
    Regards
    Maruthi Ram

    Hi,
    PO Output Determination
    Output of Purchase Order
    1. Condition Table
    SPRO > Material Management> Purchasing -> Message -> Output Control->Condition Tables->Define Condition Table for Purchase Order
    Select:
    Purchasing Doc. Type,
    Purch. Organization,
    Vendor
    2. Access Sequences
    SPRO -> Material Management-> Purchasing -> Message -> Output Control->Access Sequences->Define Condition Table for Purchase Order
    3. Message Type
    SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Types->Define Message Type for Purchase Order
    4. Message Determination Schemas
    4.1. Message Determination Schemas
    SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Schema->Define Message Schema for Purchase Order-> Maintain Message Determination Schema
    4.2. Assign Schema to Purchase Order
    SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Schema->Define Message Schema for Purchase Order-> Assign Schema to Purchase Order
    5. Partner Roles per Message Type
    SPRO -> Material Management-> Purchasing -> Message -> Output Control-> Partner Roles per Message Type ->Define Partner Role for Purchase Order
    6. Condition Record
    Navigation Path: SAP Menu-> Logistics -> Material Management -> Purchasing-> Master data->Messages-> Purchase Order-> MN04-> Create
    Now you create PO (ME21N) and save it. Go to ME22N and print the PO by giving output type.
    GR Output Determination
    Instead of Purchase order use Scheduling agreement
    Output of GR
    After setting table, access sequence and output type for GR,run MB02 transaction, enter material document number. Double click one line item and select messages. Separate screen will be opened to configure outputs. Give the required fields and save the document. Now Run MB90, you can take printout. Output Type: WE03 or WE01 or WE02
    G.Ganesh Kumar

  • Output Determination in Invoice

    Hi,
    I created a Invoice using VF01, but I am not able to see the output. I don't see any values in Output Type.
    Rather than manually enterting the values for Output Type , Medium....is there a way to automatically populate these values once the Invoice is created , so that I can view it in VF31?

    Hi Naga,
    Normally, sequence of activities is:
    - Maintain output types:
    in which you can find the list of all messages type for billing document. For message type you want to use, select it and set "access to condition in first view"
    NOTE: If you have created a custom message, you have to verify at this point you have linked program and sapscript (or smartform) to the message type
    -Assign output types to partner functions
    Normally, for a billing type message, partner function linked is "BP" (bill to party)
    -Maintain output determination procedure
    In customizing of billing document (trans. VOFA) there's the "Output determ.pr
    " field. These schema is the same in which you have to put the message type you want to link in billing document
    -Assign output determination procedures
    To link output schema messages at billing document type
    You want to test these procedure, i can suggest you to use a standard message type, for which all these activities are normally already done.
    In all it's ok, using VV32 transaction you can insert the message type and fill condition records to link automatically message in billing documents
    Bye
    Gianpaolo

Maybe you are looking for

  • HT5029 Subscription Calendars in iCal with iCloud

    I tried this (changing location of subscription calendar) with Lion, and it didn't offer me the choice to select iCloud as a location...only On My Mac

  • FRUSTRATED WITH PREMIERE PRO SUBSCRIPTION ERRORS AND ADOBE SUPPORT!!!

    First of all, Im a paying CC customer of Premiere Pro, Photoshop and Lightroom, all 3 apps from Adobe CC. Last 2 years, no issue! But since last few months, Im really tired of this. Premiere Pro CC stops completely and shows me EXPIRED screen and eve

  • Battlefield 3 on a Imac 27" possible?

    Hello everyone, I think i gonna buy an Imac 27" 1 ghz gpu 3.1 ghz i5. But is it possible to play battlefield 3 on it, with boot camp and windows 7? Greet, Henk-Jan Leusink

  • How to compile for Flash Player 11.3 in Flash CS6

    Hi, How can I compile for Flash Player 11.3 using Flash Professional CS6, the menu has only up to 11.2 what about 11.3 and the upcoming 11.4 ? I've already downloaded and added AIR sdk 3.3 for AIR skds paths

  • ACS 4.2.1.15 Patch Version 11

    Dear All, We are facing weird issue with ACS. The shared secret key is automatically changing to some random value and stops working for that particular group. It happens very frequently and working after manually changing the shared key. Patch also