PO rel procedure carried over to Outline agreements

Hi Experts,
Release procedure created for Purchase order has become active for Contracts & Scheduling agreement also. Infact system doesn't allow to process (MIGO) scheduling agreements (agreement type: LP) without being released.
Is this valid? if yes how do I avoid this carry over.
Thanks,
Rajoo

Hi,
In the classification of the release strategy, create one caracteristik as Document category.
Maintain the value "F" for PO.
It will not pickup the outline agreement
Cheers,
Satish Purandare

Similar Messages

  • Master Agreements fields carry over to child Agreement.

    Hi,
    How can I carry over the fields set in the master agreement module to a child agreement?
    I believe I need to have a script definition on the creation of child agreement. but how can I get the reference to the master agreement fields? Any sample code?
    Also if not for script definition is there any other way out?
    Edited by: patsy lobo on Sep 22, 2008 7:35 PM
    Edited by: patsy lobo on Sep 22, 2008 7:36 PM

    HI,
    Adding to what Sudipta has said, you can also use the workbook technique for accomplishing these type of changes. That way you can achieve all hover text changes in one shot across all MA tabs.
    The 2 main tabs in the wokbook to be changed are: 'Localized Resource' and 'UI overrides' tab.
    As an example, suppose you want to add the following text for Master Agreement External Category field:
    "This field is a classification hierarchy to describe the products or services of the event and/or agreement."
    So in the Localized resource tab, fill out the following:
    BUNDLE: custom
    RESOURCE_ID: xxx     
    RESOURCE_KIND: APP_TEXT     
    DEFAULT_VALUE: This field is a classification hierarchy to describe the products or services of the event and/or agreement.
    Then refer the same attributes in the UI Overrides tab:
    UI_ID: contracts.agreement.ui.buyside.default
    FIELD: EXT_CAT
    ATTRIBUTE: Description
    VALUE: Same as Resource ID used in localized resource (xxx above)
    Hope this helps,
    Vikram Shukla

  • Very imp  outline agreements.

    hi experts,
    1)in which type of outline agreement does the price updates in info record .
    2)i created a  quantity contract and created a pur order with reference to contract, now i want to see how much quantity is still left in the contract target quantity.
    please advice me
    regards

    Hi,
    Point wise answers as below:
    1) For value contact and Scheduling agreements will update the info record but it depends upon the indicator you are setting in additional data of agreement.
    2) Go to T.Code: ME33K and to item Over view and select line item> Item > Statistics > Release documentation (or Ctrl + Shift + F12)
    Here you can see u201COpen Target Quantityu201D
    Regards.
    Chinna

  • Material on Outline Agreements

    Hi all,
    Is there any tutorial available on sales outline agreements?
    Please respond.
    Best Regards,
    AI.

    Hi
    Check thse links
    http://homepages.wmich.edu/~c3chadde/project_3.html
    http://www.sapdb.info/scheduling-agreement/
    http://www.sapdb.info/wp-content/uploads/2008/12/scheduling-agreement-procedure.pdf
    regards
    Edited by: rithvika on May 21, 2009 2:19 PM

  • SPRO config field for Material Master & Outline agreement Contracts

    Dear Gurus,
    I want the Field AUTO PO should be mandatory field - for creating New materials - Can you please suggest me in SPRO configuration?
    For outline Agreement ( contracts) - i want to make the Plant field as mandatiry - Can you please suggest me in SPRO configuration?
    Please advice
    Regards
    RS

    Hi,
    Transaction MEKB is for maintaining Condition records, in you PRD server ask concerned to maintain condition record using MEKB for contract and its line item.
    Procedure is
    1. Input in the intial screen is Purchase org, Contract number and relevant line item number and execute
    2. In the following screen highlight the line item and click on create (F6) button in the tool bar (First one from left)
    3. In the following screen inside grid maintain price in amount column agains the condition type
    If you have done the above steps then AUTO should work
    Check on it as eill:-
    Re: pr mandatory for po
    Re: Auto PO in ME59N
    pherasath

  • Service entry against expired outline agreement

    Hi Everyone,
    Is it possible to raise a service entry sheet against an expired outline agreement?
    Thanks in advance for your responses.

    If you can see the validity end date is over in purchase order.
    Then you might have face the message SE242 - Runtime of entry must fall within runtime of purchase order (& - &).
    But you can continue by configuring this message as warning.
    In short, yes, you can create Service entry sheet with regards to this purchase order, which has created with regards to contract and the contract is expired..

  • Outline Agreement of FS Contarcts

    Dear experts,
    I'm struggling to try to understand how CRM Outline Agreements works.
    Basically I can see that the standard solution privides two kinds of OA:
    1. Promo Agreement: trans type DP, item categ DPI
    2. Master Agreement: trans type MA, item categ MAF.
    II succeeded in understand Promo Agreement, with which I can add third party subvention going to automatically add a Third Party Relationship on the FS contract, according to the access sequences defined in customizing.
    Regarding Master Agreement, I already noticed that the determination on contract is customized differently in of respect DP, but is not such a problem.
    I'm facing great difficulties in managing price agreements, payment structure and in reporting the results on the FS contract.
    Do anyone has a "Best practice documentation" on how to manage and customize an Outline Agreement MA?
    - Price agreements: It often gives errors (i.e.: when you try to maintain condition records pricing agreement the condition record is disappears from display during creation.).
    I currently assigned a cond function group to the item category MAF to which is assigned a condition type with an access sequence containing the following accesses:
    10     SAP00090
    20     SAP00099
    30     SAP00089
    - Payment structure: I cannot insert flow categories in the payment structure of the OA item because the system gives the following error:
    tem 1000: Payt struc.: You must enter a flow category before the first program run
    Diagnosis
    You have not entered a flow category for a step in the payment structure. You must enter a flow category before the first program run, otherwise you must change the flow category later. However, you are not then permitted to change the flow category group.
    Procedure
    Delete this row and insert a new row in the payment structure. Enter a flow category before the first program run.
    When I create an FS Contract and the OA is determined in it, I cannot see any result such as, for example, the price agreement.
    Do anyone knows how the outline agreement MA affects the FS contract?
    Do anyone knows how to insert the payment structure on the outline agreement's item?
    Thanks and regards
    Dario

    Hello,
    Item category 'W' in a contract is not meant for automatic creation of a purchase order. It does not have a net price, where do you expect the system to pick this price from? Tax code only comes in later. Your error also talks about that.
    The material group contracts can be used to keep track of orders so that they do not exceed a value limit.
    In case, you do not know the material at the time of contract/ or have many similar type of materials use item category 'M' Material instead. In this you can specify price as well as tax code and use for auto POs.
    Item Category/Account Assgt. Category in Contracts - Purchasing (MM-PUR) - SAP Library

  • Negative carry over sholud not be allowed in fast formula

    Hi,
    I have coded like this so that it will not allow negative carry over (note: no expiry for carry over )
    but this will not work since line 8 will bring just carry over from the previous year.
    To get absence i can use get_absence function.so if i get no of absence ,total carry over and total accrual pto i can calculte net entilement.
    but to get Total accrual PTO in carry over formula , I am not able to use the procedure
    PER_ACCRUAL_CALC_FUNCTIONS.Calculate_Accrual.If I use i get error as
    ORA-20001: The formula XXCHR_CR_VACATON_ACCRUAL_FORMULA could not be executed because the context ASSIGNMENT_ACTION_ID was not set. All the relevant context values must be set before a formula can be executed.
    Action: If this is custom code then please ensure that it sets all the appropriate context values. If this is not custom code then please contact your local support representative.
    ORA-06512: at "APPS.PER_FORMULA_FUNCTIONS", line 608
    ORA-06512: at "APPS.PER_ACCRUAL_CALC_FUNCTIONS", line 70
    ORA-06512
    so how do I not allow negative carry over.
    1 Years_service = floor(months_between(Effective_date, Continuous_Service_Date) / 12)
    2 IF (GET_ACCRUAL_BAND(years_service) = 0) THEN
    3 L_Max_carryover = GET_NUMBER('MAX_CARRY_OVER')
    4 ELSE
    5 L_Max_carryover = 0
    6 Max_Carryover = L_Max_carryover
    7 l_exp_Effective_Date = ADD_YEARS(Effective_Date,-3)
    8 L_tot_carryover = GET_CARRY_OVER(Effective_Date,to_date('0101'||to_char(Effective_Date,'YYYY'), 'DDMMYYYY'))
    9 IF L_tot_carryover <0 THEN
    10 (Max_Carryover = 0)
    11 Process = 'YES'     
    12 RETURN Max_Carryover, Effective_date, Expiry_Date, Process
    tnx in advance

    there are seeded Accrual formulas given out of the box, which you can edit for your purpose

  • To change the text of outline-agreement

    Hi Experts,
    Im using BAPI_CONTRACT_CHANGE function module to change outline agreement.When im executing this im getting the dump.Will you explain me how to use this fm to change the item text of outline-agreement.Will you please give the list of mandatory fields for this function-module.

    IMPORTING
    *"     VALUE(PURCHASINGDOCUMENT) TYPE  BAPIMEOUTHEADER-NUMBER
    *"     VALUE(HEADER) TYPE  BAPIMEOUTHEADER OPTIONAL
    *"     VALUE(HEADERX) TYPE  BAPIMEOUTHEADERX OPTIONAL
    *"     VALUE(VENDOR_ADDRESS) TYPE  BAPIMEOUTADDRVENDOR OPTIONAL
    *"     VALUE(TESTRUN) TYPE  BAPIFLAG-BAPIFLAG OPTIONAL
    *"     VALUE(TECHNICAL_DATA) TYPE  BAPIMEOUTTECH OPTIONAL
    *"  EXPORTING
    *"     VALUE(EXP_HEADER) TYPE  BAPIMEOUTHEADER
    *"  TABLES
    *"      ITEM STRUCTURE  BAPIMEOUTITEM OPTIONAL
    *"      ITEMX STRUCTURE  BAPIMEOUTITEMX OPTIONAL
    *"      ACCOUNT STRUCTURE  BAPIMEOUTACCOUNT OPTIONAL
    *"      ACCOUNTPROFITSEGMENT STRUCTURE  BAPIMEOUTPROFITSEGMENT OPTIONAL
    *"      ACCOUNTX STRUCTURE  BAPIMEOUTACCOUNTX OPTIONAL
    *"      DELIVERY_ADDRESS STRUCTURE  BAPIMEOUTADDRDELIVERY OPTIONAL
    *"      ITEM_COND_VALIDITY STRUCTURE  BAPIMEOUTVALIDITY OPTIONAL
    *"      ITEM_COND_VALIDITYX STRUCTURE  BAPIMEOUTVALIDITYX OPTIONAL
    *"      ITEM_CONDITION STRUCTURE  BAPIMEOUTCONDITION OPTIONAL
    *"      ITEM_CONDITIONX STRUCTURE  BAPIMEOUTCONDITIONX OPTIONAL
    *"      ITEM_COND_SCALE_VALUE STRUCTURE  BAPIMEOUTITEMSCALEVAL OPTIONAL
    *"      ITEM_COND_SCALE_QUAN STRUCTURE  BAPIMEOUTITEMSCALEQUAN OPTIONAL
    *"      ITEM_TEXT STRUCTURE  BAPIMEOUTITEMTEXT OPTIONAL
    *"      HEADER_TEXT STRUCTURE  BAPIMEOUTTEXT OPTIONAL
    *"      HEAD_COND_VALIDITY STRUCTURE  BAPIMEOUTHEADVALIDITY OPTIONAL
    *"      HEAD_COND_VALIDITYX STRUCTURE  BAPIMEOUTHEADVALIDITYX OPTIONAL
    *"      HEAD_CONDITION STRUCTURE  BAPIMEOUTHEADERCOND OPTIONAL
    *"      HEAD_CONDITIONX STRUCTURE  BAPIMEOUTHEADERCONDX OPTIONAL
    *"      HEAD_COND_SCALE_VAL STRUCTURE  BAPIMEOUTSCALEVALUE OPTIONAL
    *"      HEAD_COND_SCALE_QUAN STRUCTURE  BAPIMEOUTSCALE OPTIONAL
    *"      PARTNER STRUCTURE  BAPIMEOUTPARTNER OPTIONAL
    *"      PARTNERX STRUCTURE  BAPIMEOUTPARTNERX OPTIONAL
    *"      RELEASE_DOCU STRUCTURE  BAPIMEOUTRELEASEINFO OPTIONAL
    *"      EXTENSIONIN STRUCTURE  BAPIPAREX OPTIONAL
    *"      EXTENSIONOUT STRUCTURE  BAPIPAREX OPTIONAL
    *"      RETURN STRUCTURE  BAPIRET2 OPTIONAL
    FU BAPI_CONTRACT_CHANGE
    Short Text
    BAPI to Change a Purchase Contract
    Functionality
    BAPI for changing a purchase contract.
    Notes
    Master conditions
    When creating outline agreements, you can specify only one period per variable key. This means that just one period can be specified for the document header (i.e. condition table A019). The same applies to each item (i.e. condition table A016) and to each item/plant combination (i.e. condition table A068).
    You can use any periods. However they must not overlap for a variable key.
    When conditions are changed, new condition records are nevertheless written.
    Because volume rebate conditions are not taken into account in outline agreements, they are not processed.
    No subitems (e.g. inclusive/exclusive bonus quantities, display, etc.) are taken into account.
    The control key for quality management in procurement (EKPO-SSQSS) and the certificate category (EKPO-ZGTYP) are only taken into account to a certain extent. These two items of information are copied from the reference contract or material master, but cannot be changed; neither are any checks carried out for these two fields.
    The revision level (EKPO-REVLV) cannot be changed because various quality management routines were not implemented.
    Version management (Document Change Management) is not supported.
    External services (planned or unplanned) are not supported.
    The creation or changing of configurations is not supported.
    Further information
    When a purchase contract is changed (activity 02), the following authorization objects are checked:
    M_RAHM_BSA Document type in contract
    M_RAHM_EKG Purchasing group in contract
    M_RAHM_EKO Purchasing organization in contract
    M_RAHM_WRK Plant in contract
    Parameters
    PURCHASINGDOCUMENT
    HEADER
    HEADERX
    VENDOR_ADDRESS
    TESTRUN
    TECHNICAL_DATA
    EXP_HEADER
    ITEM
    ITEMX
    ACCOUNT
    ACCOUNTPROFITSEGMENT
    ACCOUNTX
    DELIVERY_ADDRESS
    ITEM_COND_VALIDITY
    ITEM_COND_VALIDITYX
    ITEM_CONDITION
    ITEM_CONDITIONX
    ITEM_COND_SCALE_VALUE
    ITEM_COND_SCALE_QUAN
    ITEM_TEXT
    HEADER_TEXT
    HEAD_COND_VALIDITY
    HEAD_COND_VALIDITYX
    HEAD_CONDITION
    HEAD_CONDITIONX
    HEAD_COND_SCALE_VAL
    HEAD_COND_SCALE_QUAN
    PARTNER
    PARTNERX
    RELEASE_DOCU
    EXTENSIONIN
    EXTENSIONOUT
    RETURN
    Exceptions
    Function Group
    <b>rewards point for helpful answer.</b>

  • MM Outline Agreement Screen Flow

    Our client has a requirement on contracts and scheduling agreements where they would like to see, displayed, the extended value of the line item and the total value of the outline agreement. I have located the fields needed and they seem to serve the client's requirement, but cannot determine how to get them to display on the outline agreement transactions (ME31,2,3....). The line item extended value field is found on EKPO_BRTWR; the document total is found on EKKO_RLWRT. Is there a way without doing a core mod that I can get these fields displayed on the documents on-screen?
    Thanks!

    hI,
    For any document SAP flow will be header detail and item details.the aggrement total value comes in the header like for contract of type WK Value contract will have the total contract value , and will be available in the header screen of the aggrement . and the item cost will be in the item over view screen of the contract, with its qty and value. if you want furthur details like other conditions for that item , select that item and go to the conditions tab in the menu bar , then those details also will come.
    Check the table EKKO for the header details and EKPO for the item details.
    Regards,

  • Selection of Outline Agreement

    Hi
    Outline Agreements are to be used whenever possible.
    What would help is if you can select a vendor, then a service agreement, today this is not easy as you have a know there is a contract and also which branch of the vendor the contract is made with.. If you chose the desired vendor, you won't find the contract. Emerson is all over the world, but where to find the contract?
    If you pick the right contract, you will see an error because the selected vendor does not match to the contract.
    Can you please help me out.
    Rahul

    I believe you are using multiple vendor code for the same vendor based on different vendor location and have multiple contracts created for each vendor code. In this case I would suggest to create only one contract using mail vendor (VN) and enter other vendors in same contract as parter - Order Address (OA), This would help when you create PO. You can choose desired ordering address vendor while creating PO.
    Regards,

  • Difference B/w Framework & Outline Agreement

    Hi Gurus
    I am new to SAP MM, can anyone please tell me the difference b/w framework orders and outline orders/ agreement.
    General examples of this regard will be very helpful.
    Regards
    Imran

    Dear,
    A Frame work order is :
    Purchasing document used for the procurement of materials or external services. Instead of stipulating a specific delivery date, this type of purchase order has an extended validity period. Goods or services can be supplied or performed against it over this period without the need for any further written instruction to be issued by the buying entity.
    Framework orders are defined with document type FO. They are used in accelerated procurement processes in connection with preventive maintenance (servicing) plans or invoicing plans, and for blanket purchase orders (purchase orders with specified limits).
    A framework order covers multiple procurement transactions over a longer period in cases where the administrative costs of processing discrete POs would be disproportionately high.
    An Outline agreement is :
    Outline agreement also referred as Contract in SAP.
    Outline Agreement can be of 2 types:- Contract and SA. 
    Contract is where you have a contract with the vendor,may be a for a predetermined quantity or predefined value. So everytime you need the material,  you need to make PO ref the contract asking for the delivery of the material. In such instance when PO is ref with contract its called contract release orders or call off orders. 
    Scheduling agreement is a long term purchase agreement, where you will keep issuing the delivery schedules whenever there is a change in requirement or at predetermined time intervals. The delivery schedule can be on hour/daily/weekly/monthly basis. But it will contain different zones viz. firm/tradeoff/Forecast.  Firm zone schedules are confirmed requirement and need to be taken by ordered party. Tradeoff zone requirement is to purchase the raw materails and ordering party is liable to pay raw material cost, in case of requirement cancellation. Forecast zone requirement is to help the vendor to plan his requirements.
    SA is also an agreement with the vendor for the supply of matl, may be a quanity or value. The delivery dates will be maintained in ME38 ref the SA which are called delivery schedules.So you can maintain the delivery schedule and communicate the vendor on Forecase basis or JIT basis. And when you need some more matl then will only create SA deliveries using ME38. SA could be of 2 types:- without release documentation-system will transmit the delivery info to the vendor once you save the document. 
    With release documentation- after creating the delivery schedules you need to create SA release using ME84.
    The main difference between contract and SA is volume of docs generated would be higher in contract since everytime you need to make a PO ref the contract and its time consuming, whereas SA can be integrated with MRP such that it automatically creates delivery schedules during MRP run provided if there is a requirement to the matl. 
    Regards,
    Syed Hussain.

  • Is it possible to create a new List from another List's template and NOT carry over the associated Workflow?

    Related to
    this post, in cases where it's desirable to have two different workflows for two different Lists—is it possible to NOT bring forward a hardwired workflow when creating a new List from a saved template?
    I.e. List #2 still has the workflow from List #1 hardwired in.  List #1 still needs its workflow but List #2 wants to have a separate Workflow.

    More importantly, because it's relatively easy for most folks to just start from scratch with a new Workflow—how does one disassociate a carried-over Workflow from the new List?
    Use the web-GUI. (List Settings > Workflow Settings)
    From Designer, there's a shortcut button at the top of the page in the Workflows tab: "Administration Web Page".

  • How to reflect variable price in outline agreement

    We procure many very complex tools that have options which significantly affect the price of that tool.  We would like to be able to reflect those price differences in the outline agreement by option within the following boundary conditions.
    1. Do not want to create a new material master for each option
    2. Do not want to utilize BOM
    3. We are buying the tool so sales order solutions won't work for us
    I have looked at configurable materials where I set up characteristics to reflect the options but I have not been able to figure out a way to price those individual options.  I do see how I could create multiple line items on the outline agreement for the same material and put unique combinations of the option characteristics in individual lines but that means I have to create a line item per option combination permutation which is much more painful than simply pricing individual options.  I also haven't seen any way to get SAP to select the correct line item based on these characteristics when doing source selection on the PR or PO.   I have started looking at variant pricing but that is completely new to me and I am not sure if that is going to go in the direction I want.  My fear is that this just allows me to price a combination of characteristics vs. pricing individual characteristics then combining the prices at the time of purchase (no different that having to create an OA line item per option combination permutation).  My apologies in advance for the convoluted message but it is difficult to ask about solutions when you are not sure what functionality potentially exists.
    Thanks,
    Ben

    Hi
    Try to check with variant Configuraqtion may be upto some extent helpful
    Check the link
    http://help.sap.com/saphelp_erp2004/helpdata/EN/92/58d455417011d189ec0000e81ddfac/frameset.htm

  • Header and footer of RTF template not getting carried over to Excel output

    We have Header and Footer in RTF template defined. The output of the report will be in Excel. When we run the report, the header and footer on the report are not getting carried over to excel has header and footer, instead the header and footer are printed as first line on the excel. Also, the RTF template is set to landscape but when the output is generated in excel, it is set to Portrait

    hi..
    chk this presentation...
    http://csc-studentweb.lrc.edu/swp/Berg/articles/NW2004s_what_is_new.ppt#352,3,Why NW 2004s?
    http://www.sap-hefte.de/download/dateien/1090/086_leseprobe.pdf'
    hope this helps...

Maybe you are looking for