Reference of Contract for an FOC document type

Dear all,
I have a scenario where i create a Contract with value, then for that contract if needed i send materials in FOC, so when you check the copy contral we can assign the contrac to FOC sales order document type.
when when i really create the FOC order with reference to Value contract it does not allows, as because the sale document is have reference mandatory option only for Quantity contract to be copied or referenced for a sales order,
so any suggestion for acheiving the same.
Thanks
Sudhir

Closing this thread, No solution yet

Similar Messages

  • To Make WBS element Mandatory for a particular Document type- Contract

    Hi ,
    I have a requiment where I have to make to Make WBS element Mandatory for a particular Document type of Contract . I don't want to use any User exits or Badis for this .
    Please let me know if there is any configuration that can be done to achieve this .
    Regards,
    Hari.

    Hi ,
    It is already made mandatory in account assignment categories  but My requirment is that it should be mandatory for only one particular document type . In the account assignment categories , there is no where we can specify the document type . It is only at account assignment category level but not at document type level .
    Regards,
    Hari.

  • PO from PR only for a particular document type

    Dear Gurus
    I want purchase orders should be raised with reference to purchase requisitions only. System should allow to make purchase orders with reference to purchase requisitions only for a particular document type only.
    I have configured in OMET and assigend this in SU3, now the system is not allowing to create PO for all document types, but I want to restrict this for a particular document type only
    Is there any configu change required?
    Regards
    Muthukumar

    Hi
    You can make it in MM - purchasing -> purchase orders -> define document types -> check the document type -> click on link purchase requisitions.
    And in define screen layout at document level - make PR mandatory for your purchase order document type (field reference).
    Thanks
    Edited by: Praveen Raghavendra on Jan 12, 2009 2:07 PM

  • Return PO box ticked for return PO document type

    HI All,
    There is a help need for Badi.  While creating a return PO in T Code ME21N, i want to get return PO field  ( EKPO-RETPO) box ticked for Return PO document type. I found one BADI for ME_COMMITMENT_RETURN. I need help to use this badi.
    Regards,
    Madhu.

    Hi
    Why don't use the BADI ME_PROCESS_PO_CUST, method PROCESS_ITEM? You have a demo. The idea is:
      data: ls_mepoitem type mepoitem,
            ls_header type ref to if_purchase_order_mm,
            ls_data_header type mepoheader.
      ls_mepoitem = im_item->get_data( ).
      ls_header = im_item->get_header( ).
      ls_data_header = ls_header->get_data( ).
      IF condition IS TRUE.    "with LS_MEPOITEM, LS_DATA_HEADER
        ls_mepoitem-retpo = 'X'.
      ENDIF.
      im_item->set_data( ls_mepoitem ).
    I hope this helps you
    Regards
    Eduardo

  • BASIS--to restrict authorization for a PO document type & 122 movement type

    Dear All,
    Plz guide me how to restrict authorization for a PO document type & for a movement type 122 i.e. for eg. if a user has authorization for PO document type IC then he should not be able to rum movement type 122 for any T-code he runs.
    Thanks in advance
    Arpit
    Basis

    Hi,
    Your request was not too clear to me.. As per my unde
    Here is some details of Authorization object related to Purchase Order:
    Document Type in Purchase Order( M_BEST_BSA )
    Purchasing Group in Purchase Order (M_BEST_EKG )
    Purchasing Organization in Purchase Order  (M_BEST_EKO)
    Plant in Purchase Order  (M_BEST_WRK )
    Document Type in Outline Agreement (M_RAHM_BSA )
    Purchasing Group in Outline Agreement (M_RAHM_EKG )
    Purchasing Organization in Outline Agreement ( M_RAHM_EKO )
    Plant in Outline Agreement ( M_RAHM_WRK )
    This can be helpfull to you to restrict authorization to PO..
    In Organization Level, it can be restricted by Purchasing group, Purchasing organization and plant..
    Regards,
    Sandip

  • Differentiating of pricing schema for each purchasing document type

    Dear colleagues,
    This topic could be discussed before but I need to clarify some points.
    We would like to differentiate pricing schema per purchasing document types (e.g. AA and ZZ). These purchasing documents are not like domestic and import types.
    There some condition(s) where purchasing document type AA should not be able to maintain whereas ZZ should be able to.
    In this case shall use one unique pricing schema for both purchasing document types if so how can I hide some conditions for document type AA or if I use separate pricing schema how can I set different pricing schemas for different purchasing document types because both document types have same purchasing organization, vendor etc. 
    Regards
    Metin

    Hi,
    Why to have two different schema groups! Is procurement process is completely different, so use to have!
    (have thought of separate condition types for each Calculation Schema)
    Based on Schema Group Of Vendor in the vendor master, the PO for vendor with respective Schema Group Of Vendor will populate the assigned condition typesu2019. Follow path:
    SPRO->MM->Purchasing->Conditions->Define Price determination process ->Define Schema Determination
    Under segment:
    Determine Calculation Schema for Standard Purchase Orders
    Here you can assign Schema Group Purchasing Organization, Schema Group of Vendor and Calculation Schema
    Under segment:
    Determine Schema for Stock Transport Orders
    Here you can assign Schema Group Purchasing Organization, PO document type and Calculation Schema
    Regards,
    Biju K

  • Make material as a mandatory field for a particular document type in PR

    Hi,
        Currently we are in SAP 4.6c version. There is a business requirement for making material as a mandatory field for a particular document type of purchase requisition as they don't want the user to raise non material purchase requisition using that document type. The field for material is currently not available in the configuration for Define Screen Layout at Document Level for purchase requisition.
    So could you kindly let me know the possible options to prevent user from raising a non material purchase requisition using that document type. If not could you kindly suggest me the user exits available at the time of saving purchase requisition which i could use so that we can write a code to check if the material number is entered or not. If not entered prevent the user from saving the purchase requisitions.
    Also it would be helpful if you could let me know how the fields for enjoy transaction (like material,document type) can be made available for selection in the configuration for Defile Screen Layout at Document Level for purchase requisition.
    All you help in the solving the above problem is highly appreciated.
    Thanks & Regards
    Ram

    Hi,
    Check below method works out for you, if you do not want to proceed with any ABAP development.
    Have a custom field selection key with Material Description field as "Mandatory" and "Display" in Basic Data, Item selection group.
    Assign this to your PR document type which need material as mandatory. With this you are making user to enter material indirectly as mandatory & user will not have an option of entering text which avoids indirect / service procurement.
    "Material Group" option won't help as User can have default settings with some value and it updates even in display mode of field.
    Regards,
    Ram
    Edited by: Ramprashanna S on Jan 11, 2012 11:51 PM

  • Purchase value for a particular document type of po

    I need Purchase value for a particular document type of po

    Hi Thanks for the reply. Sum of net order value will give right. Any selections we have to do at headr level ? Does it hold good for SA's also ? Please help

  • For a particular document type posting using FB50/F-02 should be restricted

    Hi all,
    I have a requirement that, for a particular document type posting using FB50/F-02 should be restricted.
    Any idea?
    Thanks,

    Hi,
    what Exactly i need to write in validation is...
    PREREQUISITE.
    company code eq '0001' or '0002' or '0003'.
    and doc type 'XX'.
    CHECK
    data: l_flag type c.
    check action eq 'BU'.    "only when clicked on 'post' in FB50
    Import l_flag from memory id 'YMMID'.
    if l_flag eq ''.
    endif.
    message
    'Doc cann't be posted'.
    Is it possible to write above code in validation?

  • Error while posting a sales order created with reference from contract for

    Hi,
    I am posting a sales document( Type: WA)  created with reference from contract document(  type wk2) for delivery.  The item category in the sales order of the Item is WAN. On posting this document for delivery I am getting the error as "Item category WAN is not defined".  Please help me out how to resolve this issue.
    Thanks
    Jayant

    Hi Jayant,
    I think its value contract releated error,
    You suppose to check material item category group through T.code-MM02 into sales2 tab and maintain VCIT,
    and do item category assignment through T.code- VOV4.
    plz.maintain like that,
    WK2 -          -VCIT-         -           - WAN(contract item category),
    wk2  -          -        -VCTR-          - WAN((contract item category),
    you should also maintain same against your standard Sales Document type and for Standard Item category into VOV4,
    WA(standard docu.type) -VCIT-                             -                -TAN(your standard docu.type item category),
    WA(standard docu.type) -         -VCTR(item usage)-              -TAN(your standard docu.type item category),

  • PR mandatory only for few PO document types

    Hi SAP Gurus,
    Issue being faced in a support project.
    A buyer is authorised to create 5 different PO doc types. Requirement is to make for only 2 PO document types PR is mandatory. Need immeidate inputs. Any suggestion without implementing user exists is highly appreciated.
    Regards,
    GM

    The field can not be made a required entry in ME21N. However you
    can use "Function Authorizations" (OMET) to restrict the user to only
    order with reference to a purchase requisition.
    As both the "agreement field" and "purchase requisition" fields are
    reference fields they are populated when created in reference and thus
    the system would not accept attempting to make them a mandatory field.
    Please use the OMET transaction and the PID EFB to accomplish your
    desired functionality.
    I have also attached note : 664424  'Requisition number not mandatory in
    ME21N' which contains further information regarding this functionality.
    I hope you find the note useful together with the information i have
    given you!!\
    This will make for all document types...........I guess you cannot do this for different document types

  • Two different billing document types for 1 sales document type.

    Hi Gurus,
    I have a requirement , wherein our client is having counter  sale.
    He is using one sales doc type , and while creating a order , he is manually adding payment terms.
    Requirement is , if the payment terms are cash, billing doc type created later on should be one , else during credit sales , billing document type should be different.
    As per my understanding this is not possible.
    Want to know if anyone has some different thought on this.
    Thanks in advance
    Nilesh.

    Dear Nilesh,
    There two options you can look in to
    One option is
    1.You can define different sales document types for cash and credit.
    2. You can define two different billing documents.
    3.Do the copy control settings for each combination
    Cash sales order >Delivery>Cash invoice
    Credit sales order >Delivery>Credit invoice
    Second option is
    1. You can maintain single sales document for both the processes.
    2.Define two different billing types then do the copy control settings for both billing types.
    But in this option user need to select the billing type manually based on the process while creating billing document.
    I hope this will help you,
    Regards,
    Murali.

  • SD - Two message category for an invoice document type

    Good morning all,
    I use InterCompany biling in SD with standard invoice document type 'IV' and message category  'RD04' (which enables  vendor invoice creation).
    My customer asks to be able to print a form for the intercompany bills.
    For the non intercompany bills this is actually performed by using a specific message category. 
    So my question is : is there any way to have TWO message category ('RD04' + specific message for form) automatically  attached to an intercompany bill (customizing, user-exit,...) ? 
    Best regards.
    Didier GOBLET.

    Hi Didier
    Assign the logic to the RD04 output type smartform.Then it is possible,In the smartform include the logic that it should automatically attach to the intercompany billing.
    Regards
    Srinath

  • Retriggering Release strategy for PR with Document Type, Company Code and Price Range as Characaterstics

    Hi Friends,
    I have a issue to fix. The issue is releated to PR.
    There are some PR's in the system which has wrong release strategy picked up or wrong approvers picked up due to some congif change. now that the config changes are rectified correctly, we need to find a solution to correct the PR's which got affected due this.
    I have to retrigger the release strategy for all the affected PR's.
    The characterstics which we have consider for release strategy is Document Type, Company Code and Price Range.
    Can anyone suggest how can we retrigger the PR in bulk or individual to all the affected PR's, so that it picks up correct release strategy as per new config changes.
    Regards,
    Manjunath K

    Hi,
    Refer the discussion to triggers release again on release code addition/change in release strategy.
    release code is changed on PR release strategy - old PR can´t be approved
    Regards,
    Biju K

  • Document number disrepencies for the same Document Type

    Dear All,
    I found an issue with Document number range with document type SA wherein last month document posted starts with 1431..... and in current month document posted starts with 1400..... how can this be possible?  NOTE: The same document number range is attached to another document type as well.

    Refer SAP Notes
    1828201 - Missing document numbers for accounting documents
    175047 - Causes for FI document number gaps (RF_BELEG)
    1522367 - Document number gap reason and analysing method

Maybe you are looking for

  • Transfer rented video/movies to my new iPhone 5?

    I purchased some videos/movies on my iPad 2, and here i wanna transfer them to my iPhone 5, i intended to copy them to iTunes library for sync but it didn't, is there any way help me?

  • Problem with amount displayed in local currency.

    Hi Experts, We have an invoice in XDR/PLN currency (exchange rate: 3,50). Then we are making a posting with clearing and in result we have a clearing document in EUR/PLN currency (exchange rate: 3,70). In one line item we are making a posting with an

  • Erreurs multiples à l'installation

    Bonjour à tous, Je viens vers vous pour un souci d'installation assez gênant. Je viens d'installer la version d'évaluation de la CS6 et beaucoup d'erreur de fin d'installation sont apparues. PS, ID, EN, PR ne se sont pas installés correctement. Il y

  • How to do this slider?

    [url=http://postimage.org/image/ggjhh0ws1/][img]http://s16.postimage.org/ggjhh0ws1/myproject2.jpg[/img][/url] Hello guys, for my school project, i have designed a simple website using photoshop as shown above. For the second part of the project, i ne

  • Sqlserver query using Group by and Order by

    SUM(BILL_DETAIL.x_bill_quantity) as BILL_QUANTITY, MIN(BILL_DETAIL.x_billable_to) as BILLABLE_TO, MIN(BILL_DETAIL.x_billable_yn) as BILLABLE_YN, AVG(BILL_DETAIL.x_bill_rate) as BILL_RATE, MIN(BILL_DETAIL.x_cost_rate) as COST_RATE, MIN(BILL_DETAIL.x_c