Regarding output proposal

hi,
I am getting this message in output propsal actually everything working fine but i am not able to see my condition record in extra-> output->header
any specific reason for this ?
Message showing
"The condition record for use B can not be Display"
Thanks in advance

Check the following.
1. Whether masterdata for the outputs is created or not , and if created, are they correct.
2. Is the Access to conditions checkbox ticked for the output in the configuration of o utput or not, if not do it.
Now try it, it will be automatically proposed in create or change mode.
Reward points if this solves ur problem.
Message was edited by:
        iimnava

Similar Messages

  • Output  Proposal  not automatically proposed

    Hi Experts,
    I have created a condition record for output type Zquo .
    When I do the output determination analysis and click on condition access i see a message < b condition found /b> and System Response says "An output proposal is created".
    Even after this The output is not proposed automatically.
    what could be the problem.
    I appreciate all the help I can get with this .
    Tks in advance

    Hi,
    Assign your Out put type to the billing Type in T.Code :VV31 and then create fresh billing doc.
    Regards,
    R.Janakiraman

  • Output proposal from customer master in 4.7

    Hi
      I'm trying to find configuration nodes in spro for <b>output proposal from customer master</b> in SAP R/3 4.7. Strangely it is not where it is supposed to be i.e.
    SD>Basic Functions>Output Control
         I tried by searching but unable to find it. However I found out that you can assign output determination procedure in define account groups.
          Please help me in finding the correct node or the t-codes for maintaining output procedure for output from customer master. Kindly note that I am looking in <b>SAP R/3 4.7</b> version.
    thanks in advance
    Koustav

    Output proposal from the customer master record
    IMG&#61664;SD&#61664;Basic fncs&#61664;Output&#61664;Output determination&#61664;Output proposal from the customer master record, Define output
    In this option one creates output types, such as BA00 (order confirmation). After creating the output type, one assigns the output type to an output procedure, such as DB0001. After the assignment of the output types to the procedure, the output procedure is then assigned to the customer account group. This is a simple procedure and results in the output that is placed on the customer master record being copied into the sales document.

  • Duplicate Outputs proposed in Billing Document unexpectedly after 3 months

    We are facing a weird problem in some of our billing documents. After the billing document has been saved and the EDI output ZEDI issued, some days later (or even some months later), 2 or 3 duplicate outputs have been proposed (automatically ?) and the IDOCs also have gone out of the system. But the status of the duplicate outputs remain in "Yellow" status and their Processing Log does not contain the new IDOC #s but the original IDOC # that was sent first.
    We are at a loss to determine root of issue, Users don't remember changing the billing documents at these times but even if they did, the "Multiple Issuing" checkbox is not selected in the Output Type "ZEDI" and hence, outputs should not have been proposed.
    Has anyone faced such an issue before ?
    I have tried to paste some logs below:
    Output Screen:
                  Output     Description Medium     PF     Part#     Language     Proc Date          Proc Time     Date/Tim
    duplicate ZEDI     EDI Invoice     EDI     BP     266     EN                    00:00:00     4
    duplicate ZEDI     EDI Invoice     EDI     BP     266     EN                    00:00:00     4
    duplicate ZEDI     EDI Invoice     EDI     BP     266     EN                    00:00:00     4
    original    ZEDI     EDI Invoice     EDI     BP     266     EN     05/13/2010     00:56:37     4
    When I do a "Determination Analysis" in Output Screen for this faulty billing doc, I get the following..
    Z1EX     502     Output ignored (requirement 962 not fulfilled)
    Z1PA     502     Output ignored (requirement 962 not fulfilled)
    ZCRE     540     Output not found
    ZED2     524     Access not made (initialized field)
    ZEDI     541     Output found
    ZLDO     540     Output not found
    The NAST entries for these outputs are follows:
    Object key     Message type     Message partner     Created on     Created at     Message manually     Processing date     Processing time     Response date     User name     Processing status     Output Device     Spool request name     Suffix 1     Suffix 2     Automatic     Recipient
    92494146     ZEDI     266     5/13/2010     0:56:37          5/13/2010     0:56:37          BATCHADM     1                         X     
    92494146     ZEDI     266     9/9/2010     8:45:26     X          0:00:00          5ECND6     0     AdobePDF     84526     MPDF     20100909     X     5ECND6
    92494146     ZEDI     266     9/9/2010     8:46:09     X          0:00:00          5ECND6     0     AdobePDF     84609     MPDF     20100909     X     5ECND6
    92494146     ZEDI     266     9/9/2010     8:59:20     X          0:00:00          QZL49N     0     AdobePDF     85920     MPDF     20100909     X     QZL49N

    Hi,
    I am getting the same issue. Did you solve this issue? If yes, please share your solution.
    Best Regards,
    Mayank Malpani

  • Output proposed  from customer master

    Hello SDN!
    I could not find output info in customer master.
    Can I check with you if output can be proposed from the customer master when creating a sales order?
    Or the only way output is determined is from output determination procedure where customer code can be one of the key condition record fields?
    regards
    Ravi

    Hi,
    Please go through the below Configuration process for Outputs
    Output is a form of media from a business to one of its business partners. Ex: Printouts, Faxes, Telexes, E u2013 mails and Electronic Data Interchange (EDI). The Output determination component offers output functions for Sales, Shipping and Billing to help in manage sales transactions with our customers and within the organization.
    Output can be sent to any of the partners defined in the document.
    Outputs are usually in the form of order confirmations, delivery notes, invoices and shipping notifications.The output determination component offers output functions for sales, shipping transportation and billing to help in manage sales transactions with our customers and with in the organization.
    We can create output.We can group output.Employers can send/receive output.
    Output directly linked to the corresponding sales transaction Ex: Trough EDI.
    System automatically proposes output for a sales and distribution document.
    System uses condition technique to determine output.
    We use output type to control how the output should be transmitted.
    Ex: Via EDI, be printed.
    We can determine output for all kinds of objects in SAP u2013 SD. Ex: For sales activities sales documents delivery documents and billing documents.
    We can determine output, we can process output, and we can send output.
    SAP uses condition technique to determine output.Output types can be Inquiry, Quotation, Order confirmation, Shipping document, Billing document, etc.The output can be sent through transmission mediums.
    Ex: Local printer, Fax, Telex, E u2013 mail, SAP inbox or even to SAP.
    Output determination closely integrated with technical module as technical consultant prepares the output format in SAP script or smart forms.
    Configuration settings:
    Output determination for sales documents: Transaction code: V/57
    Path:
     IMG
     Sales and distribution
     Basic functions
     Output control
     Output determination
     Output determination using the condition technique
     Maintain output determination for sales documents
     Maintain condition tables
     Maintain output condition table for sales documents
    Save and Exit
    Maintain output types: Transaction code: V/30
    We define output types for output type records. Out put type represents different output.
    Ex: Quotation, Order confirmation, etc.
    Path:
     IMG
     Sales and distribution
     Basic functions
     Output control
     Output determination
     Output determination using the condition technique
     Maintain output determination for sales documents
     Maintain output types
     Check different output types existed or not
    Ex: AF00 = Inquiry
    AN00 = Quotation
    BA00 = Order confirmation
    LP00 = Scheduling agreement
    MAIL = Internal message
    RD03 = Cash sales invoice
     Click on change/display icon
     Choose u201CBA00u201D
     Click on copy icon (press ENTER till 28 entries copied) and rename it
     Select our output type
     Check u201CMail titleu201D and u201CTextu201D control button whether mail and texts are existed in all languages or not
     Check processing routines for all transmission mediums are existed or not
     u201CProgramu201D, u201CFORM routineu201D, u201CFormu201D are maintained and provided by technical consultants.
     Check partner functions has been assigned to transmission mediums in partner functions control button
     Save (press ENTER up to u201CSAVEu201D request disappears)
     Come back
     Go to details icon
     Assign access sequence [ ] (create access sequence in next step)
     In general data section
    Check access to conditions
     In default values section
    Maintain dispatch time as u201Csend immediatelyu201D
    Transmission medium: u201CPrint outu201D
    Partner function: SP
     In time section
    Check timing: 1
     Save and Exit
    Maintain access sequence
    Path:
     IMG
     Sales and distribution
     Basic functions
     Output control
     Output determination
     Output determination using the condition technique
     Maintain output determination
     For sales documents
     Maintain access sequences
     Go to new entries
     Define your access sequence
     Select it and click on accesses icon
     Go to new entries
     Specify access sequence No. 10
    Table No. Ex: 001
     Save and Exit
    Assign output types to partner functions
    Path:
     IMG
     Sales and distribution
     Basic functions
     Output control
     Output Determination
     Output determination using the condition technique
     Maintain output determination for sales documents
     Assign output types to partner functions
     Check whether the system has copied output types with relevant transmission mediums and partner functions
     Save and Exit
    Maintain output determination
    Path:
     IMG
     Sales and distribution
     Basic functions
     Output control
     Output determination
     Output determination using the condition technique
     Maintain output determination for sales documents
     Maintain output determination procedure
     Choose standard output determination procedure u201CV10000u201D
     Copy and rename it
     Save and select our output determination procedure
     Click on control data button and change output type u201CBA00u201D as ours Ex: SREE
     Save and Exit
    Assign output determination procedure
    Allocate Sales Document Header: Transaction code: V/43
    Path:
     IMG
     Sales and Distribution
     Basic functions
     Output control
     Output determination
     Output determination using the condition technique
     Maintain output determination for sales documents
     Assign output determination procedure
     Assign Sales Document Header
     Choose sales document type u201CORu201D from position button
     Assign out output determination procedure (ours) Ex: SREE
     Save and Exit
    Sales Document Item: Transaction code: V/69
    Path:
     IMG
     Sales and Distribution
     Basic functions
     Output control
     Output determination
     Output determination using the condition technique
     Maintain output determination for sales documents
     Assign output determination procedure
     Assign Sales Document Items
     Choose item category as u201CTANu201D form position button
     Assign our output determination procedure
     Save and Exit
    Maintain condition record: Transaction code: VV11
    Path:
     Logistics
     Sales and distribution
     Master data
     Output
     Sales document
     VV11 u2013 Create
     Specify our output type Ex: SREE
     Click on key combination
     Maintain the details like below
    Customer No. Partner
    function
    Message transmission medium
    [M]
    Dispatch date Language
    1001007 SP 1 18 u2013 02 u2013 06 EN
     Select condition line item
     Click on communication
     Specify outputs devise [LP01]
     Check print immediately
     Save and Exit
     Go to VA01 and raise the sales order
     Go to Extras  Output  Edit  Check condition record values are copied or not
     Save and Exit
     Go to VA02  Extras  Output  Header  Print preview
     Check the result
    Steps:
    1. Put the fields into the field catalog that you will need.
    2. Create the condition tables.
    3. Create the access sequence
    4. Assign the condition tables to the access sequence
    5. Create the condition types
    6. Assign the access sequence to the condition type
    7. Create the determination procedure (if necessary) and assign the condition types to it.
    8. Assign the determination procedure.
    9. Create your condition records.
    Regards,
    Siva

  • Regarding output type and idoc trigger issue

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

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

  • Regarding Output type determination

    Hi All
    I am creating Sales order ,delivery and then INVOICE.
    When I create invoice with VF01, the output ZE01 (which is for creating Invoice Idoc) should get automatically populated in Menu path <b>GoTo --> Header --->Output</b>.
    But this is not happening.
    I am able to put the ZE01 Manually in the above path to create the invoice Idoc.But I dont want to do that. (It must be automatic!!)
    Can anybody tell me what exactly is the problem.
    I have checked NACE,VV31 etc T codes but not getting any clue.
    (Just to add one more thing The "<b>Accounting Document</b>" is not getting created during Invoice creation ...Is that the problem ? Pls justify if yes..)
    Regards
    Tulip

    Hi Nilesh and Narayan
    Thanks for replying!!
    I maintained proper condition records in VV31 and looked into "<b>determine analysis</b>" I am getting message "<b>Output ignored requirement 803 not fulfilled</b>" ,I got that somthing might be wrong with my Requirement 803.
    Can you please tell me what exactly I need to do to resolve this problem.
    Reply will be surely appreciated...
    Regards
    Tulip

  • Regarding output type for billing doc

    i have one billing doc. i want to find out type for that billing doc. through that i need to find the program name and form name.
    i have lot of out put types. In that how to find the out put for my requirement

    HI pavan,
    It is not a good idea to check with the Program name or Layout set name without knowing the OUtput types because, Billing docu number can work with multiple Output types...you never know it. So in your case to check TNAPR table would be the best option...but again it is never recomended to go ahead without knowing the output type.
    And for one Output type there will be only one smart form/ script form and a Zprogram will be configured.
    It is not possible to configure multiple Smart forms for a same Output type.
    You can use single smart form in Multiple Output types but not single output type for diff Smart forms.
    Try to either know the smart form/script from name or the Zprogram so that you can search it in TNAPR table or by using Where used list icon.
    Regards,
    Kittu

  • Regarding output type

    hi.......,
    can anybody tell me application and output type for dunning notice in FICO.
    THANKS & REGARDS,
    PHANI.

    Hello,
    DO u know the dunning notice number.
    Then go to the table NAST.
    In the sel.screen give the dunning notice number in the object key filed and execute. U will get the records of the processed outputs. from there u can find the application and output type.
    Or go to Tcode NACE.
    There u find a list of application from that u can choose as per ur req.
    Hope this will be helpful for u.
    Don't forget to reward points.
    Regards,
    Vasanth

  • Scripts ( regarding output type )

    Hi All,
    we created  New ouput type from the existing one
    and we modified the script .we are not done any changes in print program copied as it is with some other name.
    problem is:
    now if we run with new ouput type  see the print preview we are not geting the output as before( that means existing output type )?
    any changes to be done for print program?
    i mean in print program i have the old ouput type shall i replace that with new output type?
    pls give me solution.
    thanks in advance

    Hi,
    Yes please wherever you have the old output type you have to change it.
    Regards,
    Ram

  • Regarding output type Information

    Hi Gurus,
    I have more than 400 output type and i want to know for which document type and who is using these output type. Please help me to solve this issue.
    thanks
    Hemant

    Hi,
    Output types will be assigned to output determination procedures.
    These procedures will be assigned to Sales Order type and Item Category.
    The path for this is:
    SPRO>Sales and Distribution>Basic Functions>Output Control>Output Determination>Output Determination Using the Condition Technique>Maintain Output Determination for Sales Documents>Assign Output Determination Procedures>Allocate sales document header/Assign sales document items.
    Similarly the output determination procedure will be assigned to Billing document type.
    The path is:
    SPRO>Sales and Distribution>Basic Functions>Output Control>Output Determination>Output Determination Using the Condition Technique>Maintain Output Determination for Billing Documents-->Assign Output Determination Procedures.
    You can check the procedures by using the path:
    SPRO>Sales and Distribution>Basic Functions>Output Control>Output Determination>Output Determination Using the Condition Technique>Maintain Output Determination for Billing Documents-->Maintain Output Determination Procedure.
    Regards,
    Krishna.

  • Regarding output statements

    Hello experts,
                            i want to know the use of the following statements.
    can anyone give a example and explain these types of output statements.
                                    Write:/P sy-uline.
              Write:/P sy-uline(L).
              Write:/P(L) sy-uline.
              Uline.
              Uline /P.
              Uline /P(L).
    thanking u all.
    regards,
    sanjay

    Hi,
    First you know the syntax of WRITE statement.
    <u><b>WRITE:</b></u>
    Displays lists.
    <u><b>Syntax:</b></u>
    WRITE [AT [/][<pos>][(<len>)]] <f> [AS CHECKBOX|SYMBOL|ICON|LINE]
                                       [QUICKINFO <g>].
                                       [<format>]
    The contents of the field <f> are formatted according to their data type and displayed in the current list. . The additions before the field allow you to specify a line break, the starting position, and the length of the field. The additions after the field allow you to display checkboxes, symbols, icons, and lines. The <format> addition can contain various other formatting options. The QUICKINFO addition allows you to assign a tool tip <g> to the field.
    REgards,
    Bhaskar

  • Regarding output and debugguing

    Hi,
    I need to output PSPEL field from AUFK table. I need to modify contents of this field. while output this field It shows 23 characters. But while debugging It shows 8 characters. what is problem, can anybody suggest.
    PSPEL, Data Element -> length NUMC 8.
    Domain -> output length 24.
    Regards,
    Zakir.

    Hi,
    you need to make use of Conversion routine to get correct value.
    CONVERSION_EXIT_ABPSP_INPUT    Conversion External > Internal WBS Element Number
    CONVERSION_EXIT_ABPSP_OUTPUT   Conversion Internal > External WBS Element Number
    Hope this helps.
    ashish

  • Account fact sheet, print version (PDF). Query regarding output blocks.

    I have looked at OSS Note 1066280 which explains exactly how to config the PDF fact sheet. However, on looking at the view or using the SPRO path I can see that there are currenty no settings in place at the moment. i.e. the view/SPRO is showing no data.
    However, when looking at the appropriate Smartform I can see blocks for:
    Opportunities
    Activities
    Interaction history
    Contact Person
    Relationship types
    Which all print out (display in PDF) okay, except there's also a Sales block in the Smartform which does not print. The logic/output conditions in the Smartform say PRINT_DATA-SALES_AREAS = 'X' and SALES_AREAS[] NE initial.  What controls whether this information prints, config-wise.
    Also, I need to add new blocks of data, which is probably going to be sourced from ERP, but config-wise can I control whether the PDF displays these newly created blocks in the same way as it does for the SAP standard?.
    Regards
    Jason
    Edited by: Jason Stratham on Apr 20, 2010 1:46 PM

    I think my question might be answered when I look at table CRMT_BSP_PRINT.
    Regards
    Jason

  • Question regarding outputing results of query to pdf file

    Is there a way in which we can output the results of the query to a PDF file in PLSQL?
    Thanks much,
    Madhu

    I have a situation where there needs to be emails sent to the customers on a daily basis.Right now there is scheduled bat file on a particular machine which calls the Form which has the logic to generate the pdf file using Oracle Reports for each of the customer,which is then mailed using Outlook(OLE in form).But now this is kind of a problem as they are constant network problems which hinder the timely sending of the reports.
    I am trying to look for a solution so that we can do everything on database end instead of relying on the newtork.
    Thank you for any suggestions you have regarding implementing this.
    Madhu

Maybe you are looking for

  • List of activities in SAP requiring printer maintenance

    Dear All, Can anybody help me to gather a list of standard activities/tasks that are performed in SAP and require printer maintenance. What actually is required is a guide for IT staff to know that in this list of places in system the printer should

  • Persistent "You got a mail." dialog

    Last evening my iPhone began to exhibit very odd behavior. Every few minutes (whether awake or asleep) a dialog appears saying that "You got a mail." I've posted a screenshot here: http://i.imgur.com/USxwJ.png. (For those who don't read Japanese the

  • Why can't I close my screen while using an external monitor?

    It goes to sleep of course. How can I change this? I'm not seeing anything in the power settings. Thanks!

  • Original Airport Card Firmware Update?

    I have been trying to update the firmware on my airport original card. Even though I installed the 4.2 update via panther, I still found the firmware to be the same. Is this wrong? It says the airport card firmware is 8.7 something. I think the lates

  • Dynamic Layer 3 VPNs with Multipoint GRE Hardware Support

    Hello. Cisco feature navigator says that only ASR9000, 7500 and 7200 support this feature but in the following link http://www.cisco.com/c/en/us/support/docs/ios-nx-os-software/layer-3-vpns-l3vpn/116725-configure-mgre-00.html#anc7 Cisco refers 7600 p