PO Output Type not picked

Dear Experts ,
I have defined a new condition table for PO o/p as  Doc Type/P Org/Vendor/Plant.
I assigned this table to the access seq
& the acces seq to the output type .
Then I maintained Condition record for this acces seq
But the output tupe is not getting picked in the PO
The analysis shows the message  Access Not Made (Initialized Field)   .
Also I not that the system cannot pick the value of plant from the PO .
to solve this I ticked the "Initialize" tick box in the access field WERKS.
now the message is gone , but still the o/p type doesnt pick.
please sugges if this is possible at all ( I have doubts as the plant is an item level field in PO ) . If yes how .
Regards
Anis

Dear Anis,
If output type is triggered with txn like ME9F, then you can get data from EKPO table itself. Otherwise you can use options.
1. Export item data from some userexit or BADI (ME_PROCESS_PO_CUST) to memory id and then get that data in userexit userexit_komkbea_fill.
2. Using field symbol, you can get the data in userexit userexit_komkbea_fill from memory.
Data : W_Text(30) type C
Fields symbols : <FS> type EKPO.
w_text = '(Program name)EKPO[]'.
Assign w_text to <FS> .
Kind Regards,
Suneet

Similar Messages

  • Output type not getting defaulted in PO

    Hi.....
    I have configured output type as printout for purchase order, i have set the default value for message type NEU, even than when i create a PO system is not picking the message type NEU..
    i have also mainatined condition record in MN04 for the purc. document type..
    any other setting need to be maintained....
    Kindly suggest....
    Regards
    Sarfraz

    Hi,
    Please check the following
    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
    Copy NEU to ZNEU or YNEU
    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 ZNEU or YNEU.
    G.Ganesh Kumar

  • Output type NOT displaying

    Hi,
    I am creating a new Message type - zse1 to output the Purchase Order thru EDI.
    I have done the basic settings, of defining the Partner profile, message type, port definiton.
    But when I create Purchase Order & goto the messages tab, I am not able to see the new output type that I configured, nor can also select manually from the drop down list.
    How should I make the output type to automatically show up in my Purchase Orders?
    Any config I have missed out?  Pls help.
    regards,
    pri

    Hi Anne..
    For congiguring the Outputtype...the steps are..
    1.Define Output type ( Hope you did....)
    2.Assign this in to the output determination Schema RMBEF1
    3.Assign this schema into Purchase order in "Assign
       Schema to Purchase Order"
    4.Go to MN04
    5.Enter your message type and select the Key combination.
    6.Maintain all the entries and after that Select that line and
       click "Communication".
    7.Maintain the printer and all settings in this communication.
    Now put your PO ...and defineteluy the message type will pick up Automaticaly.....
    Award if solved.....
    Thans and Regards
    R.B.K.Kannan

  • Output type not triggered on time

    Dear All,
    I have an issue on output determination.
    We have a list of outputs on Delivery which will be determined after the loading start checked in Shipment based on activity profile assigned to the Shipment type.
    Out of all the outputs, only one output is not printed on time (But it is determined on time).
    We checked the condition record and everything, all found ok. But still we are facing this issue.
    Could anyone suggest me on this.
    Regards,
    Mullairaja

    Hi Mullairaj,
      If i understand it right, you are able to trigger output for both the cases but only one is picked by batch job and so you are only seeing one "Green" output but the other stays "Yellow". if this is right then did you check if the batch job is calling program RSNAST00 with right variants ?. Does this JOB has variant to pick both the Outputs.
    Let me know.
    Thanks!

  • Output types not defaulted automatically

    Hi experts,
    I have problems on two areas:
    1. Upon creation of Sales order, the output type was not defaulted automatically for picking list. 
    2. In Outbound delivery after PGI, it does not default output type for Delivery
    My settings are:-
    In config.  - VP01 Define print parameters in Sales (for selected output types)
    In master data - VV11, VV21 and VV31 all setup by output type and key combination Sales Organization/Order Type.
    Any clue where I have gone wrong or missed out?
    Regards
    PSK

    Hi there,
    For those output types check what are the default values --> dispach time. It should be "send immediately which saving the application". Only tehn the O/p will trigger immediately. Else you will have to rpocess RSNAST00 prog.
    Also check if the condition records are maintainted properly & printers are asigned in condition record --> communications.
    Regards,
    Sivanand

  • IDoc output type not getting configured in IDoc-File scenario

    Hello
    I am having IDoc to file scenario where I want to post Delivery Document to legacy system. For this I have configured following EDI configuration for Delivery through NACE transaction
    1] Created output type
    2] Created partner function as EDI LS for this output type
    3] Configured RSNASTED as Processing Routines for output type
    4] Included this output type in the Header output procedure
    5] Configured XI system as the partner in partner profile with appropriate Message control
    Still when I attempt to include this output type in the Delivery it gives me "Output for partner could not be configured". The detail message says "In Customizing, the 'CannotBeChanged' indicator has been set for output type".
    I checked in SPRO but could not find such flag.
    Does anyone had came across such output type configuration.
    Thanks in advance.
    I know this question might be not appropriate in XI forum as it comes under EDI but it has become necessary for XI profs -:)
    Regards
    Rajeev

    Hi,
    Please check the following
    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
    Copy NEU to ZNEU or YNEU
    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 ZNEU or YNEU.
    G.Ganesh Kumar

  • Output type not getting saved in the PO

    Hello Team
    we are facing one issue where output type is not getting saved in the PO.
    we give one output type and than save it , after going back to the PO we see that it is not there.and no output issued
    the PO is released properly and there is no issue , any idea what could be the reason for it

    Hi,
    Check in SU3 t.code, did check box selected u201CDelete After Outputu201D in Spool Control segment in Default TAB
    Also check Partner Function VN maintained in Default values TAB in NACR--- > EF Application for your output type
    Cross check partners {VN, PI, GS) are assigned to your PO output type in Partner Roles per Message Type
    Regards,
    Biju K

  • Output type not proposed in Message Control when PO is created

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

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

  • Delivery Output Type not updated automatically in change mode

    Hello,
    I am dealing with a strange problem.
    If i open delivery to change using VL02N then, output type configured for reissue is updated properly and on save ouput type is getting successfully processed also.
    Now if i open VL03N and then using change mode button on application toolbar i go to change of delivery, then output type is not getting created. The issue was figured out when i tried to open delivery from shipment and then using change button i tried to change and save delivery....
    Expectiing solution from experts.
    Thanks
    Hari

    Hi,
    May be this behaviour is due to the application in which you are opening the delivery. When you open the delivery from shipment, check the transaction code in the screen in system status. If it is VL03N, then it is correct. But if it is VT03N, then it is expected that even in change mode, the output is not triggered.  Pls check this once.
    I tried the same thing in an invoice from where i opened a SO and then went in change mode, and the otuput is getting retriggered.
    I hope teh configuration of your output is correct. Ensure that the Multiple Issuing button is ticked on, if you want yoru output type is to be triggered everytime you go in change mode.

  • Output type not created for outbound delivery while using SHMNT05 idoc type

    Hi Experts,
    Please help me to solve the below issue.
    Problem:- I want to to generate an IDOC(using type SHPMNT06) once the PGI is done for an outbound delivery.
    Already it is working fine when used DESADV.DESADV01 or DESADV.DELVRY07. But now the output type is not getting created when used SHMNT.SHPMNT06. I have created a separate output type ZPJ7 just as a mirror copy of the earlier output type(ZPJ6) used for DESADV.DELVRY07.
    Question:- Is it possible to use idoc SHPMNT06 instead for DESADV01 or DELVRY07? If yes then what are steps to be followed?
    The reason why SHPMNT06 idoc is planned:- We have a scenario to send outbound delivery to 3rd party system via XI. If the outbound delivery is for National(Not for Export) and PGI is completed then send the idoc straight forward to XI otherwise DO NOT generate the idoc, but just create the delivery. Collect all the deliveries in a transport and send it in a shipment. The shipment details can be sent using SHPMNT idoc. Now from XI perspective, if we can utlitze the same SHPMNT idoc for the National delivery(1st case) then perhaps this will require less effort. Hence shipment idoc is required to be generated when the delivery is created and PGI is done.
    Also it would be great if you can advice some better way to solve above mentioned scenario.
    Many Thanks,
    Sanjay

    There could be several reasons. Go to the document and in the extras-output check output determination analysis in the processing log.
    If the output has been created successfully then you need to see your printer determination. Ask basis to check it up. If the problem is that even the print preview is not coming. Check your communication in the output analysis and ensure LOCL is selected. Any other printer will need to be configured.
    If thats done already then check whether you have maintianed the condition record.
    If that too is done then check whether your output type has been assigned to the output procedure and that the output type is listed in the procedure.
    regds
    Jude

  • Output Type not automatically determined at invoice creation

    Hi Friends,
    I am facing a problem that while i am generating the invoice for a particular billing document type, the output type is not automatically being determined. Instead, I have to go into the invoice in change mode (VF02) Header>Output and assign the output type to it and select the local printer and save in order to print the invoice.
    I am generating the invoice for this Invoice Type/Output type for the first time.
    Please suggest the possible causes.
    Regards,
    Pankaj

    Hello Pankaj,
    Suppose you are using output type RD00 for invoice print out. You have maintained the condition record for RD00 in transaction code VV31. The most important thing here is the assignment of the printer.
    Suppose for output type RD00 you are maintaining the condition record for key combination - Sales Organization + Distribution Channel + Division.
    At the header level you will see the Sales Organization & Distribution Channel & at the item level you will see the Division.
    Sales Organization = BP01
    Distribution Channel = 01
    Division.............Name..........Funct.........Partner............Medium......Disp. Time.....Langu
         01............... Std Division..........BP............--......................1......................3................---
    Select the line item & click on Communication. Here assign the output type which you will use for the print out. Now Save the condition record.
    After doing this try running one sales cycle  - sales order - delivery - invoice. Save the invoice & now check in the change mode (transaction code VF02) the system will determine the output type RD00 automatically.
    Note:
    1. In the create mode the system will not display the output type RD00, after you have saved the invoice the output type will be determined automatically.
    2. Also check if there is any requirement assigned for the key combination in the access sequence (IMG - Sales and Distribution - Basic Functions - Output Control - Output Determination - Output Determination Using the Condition Technique - Maintain Output Determination for Billing Documents - Maintain Access Sequences)
    With best regards,
    Allabaqsh.
    (Idhasoft Ltd.)

  • Condition type not picked in Inquiry but picked up in order

    Hi Guys,
    We have a problem where a pricing condition type is picked up in order but it is not picked up in quotation/inquiry. So we have the price difference for the material. Points will be awarded.
    Can you guys please help?
    Thanks
    Venky

    Hi venky
    generally in Inquiry pricing is not at all required.
    but in quotation it may require sometimes. but when you create an order with reference to quotation , the price varies, this is because of the  pricing type .
    check the pricing type in VTAA quotation, the pricing type will be different for sales order and for quotation.
    Regards
    Srinath

  • Output type not coming automatically

    HI
    Whenever i am creating using t.code mb11 t.code i have to give output type wa03 manually,is this possible automaticaly output type generation in mb11 t.code
    Below settings also i completed
    NACE-Select ME Click on Condition records- Select WA03-Trans/Event Type-"WA" Print Version " 2" and Execute it
    In the next scren P-1, madium-1, Language EN and enter,, Now select the line and click on the communication method LP01 and save it,,
    Regards
    sam

    Hi
    Bijay and nisha thanks for reply still not come my output type automaticaly,i have completed my configuration in omj3 t.code for my plant and storage location.nacz t.code i give 173 GR/GI requirement,
    Regards
    sam

  • Output type not appearing in interco. document - Req. 905 not fulfilled

    Hi everyone. WHen i am creating my intercompany document, no output type is appearing. I have maintained VV31 condition records as well as WE20 settings. Also i have set output device to LOCL .When i click on Analysis output , it gives me
    RD00     502     Output ignored (requirement 905 not fulfilled).
    Any idea on this?

    Is it a newly develop routine.
    I'm not technical guy.
    But, in my opinion, the code need further work-on.
    There are
    - no IF statement
    - no READ statement
    - no table-field refer
    - logic for processing missing
    FORM KOBED_905.
    sy-subrc = 4.
    check komkbv3-rfbsk = 'C'.
    sy-subrc = 0.
    ENDFORM.
    FORM KOBEV_905.
    ENDFORM.
    For instance in this code, if there is no READ Statement, how
    sy-subrc = 4
    Then how system will judge 'READ' statement failed i.e., no record is found with key specified by you.
    Check/discuss with ABABer teammate for this.
    Further, try to manually put this output type in your desire billing type.
    Regards
    JP

  • Output type not appearing in VF02.

    Hi,
    I have created a z-output type for VF02 in the golden client ... now for me to test I have transported it to another client in the Dev environment thru SCC1 ... my problem is that here in VF02 > goto> header--> output... in this screen when I press F4 to select the output type I do not see the one that I have created ... though the entry exists in NAST & TNAPR table ... what should I do ... please help...
    Thank You,
    SB.

    Hi,
    Condition records is basically used to link your output type to the SAP document based on certain criteria (i.e sales org, customer, etc).
    Once you are done, you should be able to see the z-output type in VF02.
    Regards,
    Ferry Lianto

Maybe you are looking for

  • How to remove selection from a tr:selectManyListBox

    Hi, Let us suppose that a JSF page consists of a tr:selectManyListBox and a tr:commandButton. On clicking on an option in the list box that option gets highlighted. If press the commandButton then the page simply reloads with the slected option in th

  • Credit Memo Request and Credit Management

    Hi, can anyone advise the following? I noticed that sales values of the credit memo request is updated to the open delivery instead of open order in the credit master.  Why is this so?  Also, when i select a order order reason configured with fixed v

  • Best practice - classes folders from components

    Hi all, I have a question regarding which would be the best practice for the following scenario: I have a customer, multiple components have to be developed(including java custom components), how does it make sense better: to have one classes folder

  • Lov Values are not showing for Discoverer Reports in Application

    Hi, I developed some discoverer reports, those reports having parameters with LOV. Those LOV values are showing in Discoverer Desktop, but after registering those reports in Oracle applications those LOV values are not showing. Pls let me know how re

  • Messages keeps crashing.

    Hello, My friend and I both have iPhone 4S. We have noticed a few times that the Messages app keeps crashing. For example, last night, we tried to exchange photos using the shortcut in Messages. The phone returned itself to the Home Screen but the me