Scheduling Agreement and Quota arrangement

Dear all,
Kindly share with me the individual steps involved in in creating Scheduling Agreement as well as Quota arrangement procurement process with T.Codes and also the relevant configurations involved.
Thanks a lot.

Hi,
Here is all about Quota arrangement :
Following are the configurations.
1) To specify number range for quota arrangement
SPRO > IMG > MM > Purchasing> Quota arrangement> Define number range (Int or Ext)
2) Set Quota arrangement usage indicator:
SPRO > IMG > MM > Purchasing> Quota arrangement> Define quota arrangement usage
On Application side following are the prerequisites
1) Create Quota arrangement
SAP Menu> Logistic> MM > Purchasing> Master Data> Quota arrangement > Maintain
2)specify procurement type : Int / Ext
3)Where appropriate specify the special procurement type For ex stock transfer
4) Enter the vendor or supplying plant
5) Specify the quota you want to assign to this source
Please understand terms as below,
Quota Rating = Quota allocated Qty +Quota Base Qty /Quota
Quota Base Qty: Quantity used for manual control of the quota Arrangement (For example new source is included)
Quota: Number that determines how requirement are apportioned among various sources .Decided by a Purchasing people based on confidence on source.
I source determination source with lowest quota arrangement will always be assigned
Example
Source Quota    allocated Qty      Quota Rating
M             1                   100                     100
N              2                   150                     75
O             3                     75                      25 *
In above case vendor O will be assigned as low Rating *
Now quota Base Qty will come into picture when new supplier is introduced. As you have seen that vendor with low quota Rating is assigned .In case of new supplier as no allocated qty earlier its Quota rating will always be low & all Qty will be allocated to him. To prevent this Base qty is added to allocated Qty so that accordingly it will determined accordingly
If Quota base Qty is 100   & quota is 2
For new vendor X rating will be
Quota rating = 100 + 0 / 2 = 50
I hope this gives you entire clarity.
Vivek

Similar Messages

  • Exit for role determination via exit for scheduling agreement and contract?

    Hi..
    I have a requirement to fetch the agents in run-time for PO,PR,SCHEDULE AGREEMENT, CONTRACT..
    For PO i am using EXIT : - M06E0005
    For PR release i am using EXIT :- M06B0001
    By using above 2 exits i am getting the agents at run-time...
    Same way i need the EXIT for SCHEDULE AGREEMENT and CONTRACT..
    if there is any EXIT for this please share with me..
    Regards,
    Imtiaz Khan

    Hi Imtiaz,
    Ideally you should have your agent determination logic in workflow itself instead of determinining them in EXIT.
    Can you tell me why you are determining agents in exit and how you are making use of it ?
    Also let us know how your workflows are getting trigger for all these documents.
    Regards,
    Ibrahim

  • Contract , scheduling agreement and service order

    Hi all,
          Can anybody tell me about the contract scheduling  agreement and when we can suggest our client to go for schedule or contract agreement ?
    Pls tell me elaborately .
    Also Pls explain me about service order and when can i go for service order . whether it is restricted to AMC ?
    Pls explain me elaborately.
    pls explain me steps for creating contract or scheduling agreement and service order..........................
    points to be rewarded.
    Regards,
    Girish.

    Hi,
    Contract is outline purchasing agreement where you have a contract with the vendor,may be a for a predetermined quantity or predefined value. So everytime you need the matl,  you need to make PO ref the contract asking for the delivery of the matl. In such instance when PO is ref with contract its called contract release orders or call off orders. So Process are ME01, ME11, ME31K with aggnrement type, ME51,ME21 & MIGO,
    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. 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.So Process are ME01, ME11, ME31K with aggnrement type, ME38 & MIGO,
    Service order or service PO is created with item Category "D" and an account assignment category as per ur requirement. U can not enter ur material here only u have to maintain short text of material. Example: You want to clean the boiler and u given contract to your Vendor. Vendor sends quotation mentioning that Rs.100/hr/Man head. Now how you will measure the cleaning activities of furnace? You can pay to contractor based on the hourly basis/ man head spent in cleaning activities. So in this case create the Purchase Order mentioning "Cleaning" in the short text in Item overview(Acc assignment ' K' or “C” or “P” and Item category 'D) and item details " Man Head" Service No , Gross price - Rs.100.00 and unit - hour ( or pick from Service master) and Quantity-number of hours spent by all man head.
    The steps to create Service PO are:
    1) Maintain Item Category as D & account assignment such as cost center “K”or slaes order”C”
    2) Keep material code field blank.
    3) Enter description of service & other fields in the PO Item Overview level. Press Enter.
    4) System will prompt you to maintain services at Item Level. Maintain your service master number / service description & other fields (quantity / rate /)
    5) Save the PO.
    For more follow the links;
    For more follow the link;
    http://esoadocu.sap.com/socoview(bD1lbiZjPTgwMCZkPW1pbg==)/render.asp?packageid=DBBB6D8AA3B382F191E0000F20F64781&id=EB65A89F1AFD4C46AB61C6161BAF
    http://www.sap-img.com/sap-sd/sap-sd-scheduling-agreement-vs-contract.htm
    http://www.copacustomhelp.state.pa.us/infopak/nav/procurement/contracting/file1499/index.htm
    http://www.sap-img.com/materials/what-is-outline-and-scheduling-agreement.htm
    Regards,
    Biju K

  • Creation Profile in Scheduling Agreement and Schedule LIne

    Dear Experts,
    Currently I'm working on Scheduling Agreement and Schedule Line.In standard SAP gives the provision of creation profile.I've gone through the SAP help documentation but I'm not clear on that.I've few doubts on creation profile.
    1. I've created a profile say XXXX for 14 days JIT and 6 months Forecast.And I maintain the same on Scheduling Agreement additional data.
    2.I'm creating delivery schedule respect ot Scheduling agrrement.
    3. I maintain the aggregation horiozon in creation profile as 10 days daily aggregation for JIT and 120 days for monthly aggregation for forecast.
    4.I run MRP for the header material and I maintain the necessary SA number in Source list.
    5. After MRP run I'm not getting the respective schedule lines for JIT and Forecast.
    6. What is the use of creation profile in Scheduling Agrrement and schedule line and is it determine ant schedule lines after MRP run.
    Please clarify me on creaion profile.
    Thanks in advance
    PKB

    Dear Experts,
    I'm not getting any response regarding Creation profile which I posted last week.
    Can anybody explain me the use of Creation profile in Schedule line?
    From Standard SAP help documentation I'm not convince.
    Best Regards
    PKB

  • SCHEDULING AGREEMENT AND SCHEDULING LINE CREATION

    Hello Guys,
    I trying creating a scheduling agreement(SA) for vendor & material combination.
    I have created a Scheduling agreement in ME31L then maintained in ME38.
    In ME38 i have also mentioned the delivery date. when i am checking EKKO for Purchasing document , its created with the delivery date specified.
    My question is how to create a schedule line ? Do we need to maintain a source list of that material, plant and vendor.
    If we have the source list maintained, then what is the next step after SA is created and maintained.
    Do we need to do MIGO? because i tested by creating one SA in ME31L and maintained in ME38. I mentioned the delivery date as today and when i checked EKKO table the Purchasing document is created.
    Do i need to create a Purchase Order?
    If no then do i need to do MIGO? If i need to do MIGO, for what reference do i need to do MIGO???
    My client never maintained a Scheduling agreement, they want the scheduled lines to be created and sent to vendor and we need to receive  the goods on specified delivery date.
    Help will be appreciated.
    Thanks.

    Hi,
    You need to make a distinction between the scheduling agreement (ME31L/ME32L) and the delivery schedule creation (ME38/ME84)
    With ME31L you create the scheduling agreement. In the scheduling agreement which is created for a vendor you maintain the parts that you will order at this vendor, the target quantity that you will order over a certain period and the price.
    In ME38 you use the scheduling agreement number that is created with ME31L to create schedule lines (manually). These schedule lines consist of a date and an quantity. This is the data that needs to be transmitted to the vendor and against which the vendor is shipping the ordered materials.
    Once the vendor ships the materials you post the goods receipt in Migo against the scheduling agreement number.
    That is the basic working of the scheduling agreement and the delivery schedule.
    Now some remarks.
    You need to set-up the required output conditions for transmitting the data to the vendor either via print, fax, email or EDI.
    You can do this manually in each scheduling agreement and each release but typically you maintain the output condition records.
    For scheduling agreement contract (ME31L) you use transaction MN07.
    For the delivery schedule (ME38/ME84) you use transaction MN10.
    In order for you to be able to post the goods receipt the delivery schedule needs to have been transmitted otherwise you will get a message that not requirement are found when trying to post goods receipt.
    Also the goods receipt can only be posted if the requirements are valid on the day that you are performing MIGO. This means if you would post GR today then the open requirements in the scheduling agreement need to be for today or already from previous dates. The system will not allow you to post GR for quantities that are only due tomorrow (if this is required a user exit needs to be set-up).
    If you want schedule lines created via MRP then you need to set-up a source list using ME01. You have to make sure that the MRP key is set to 2 in orer for the system to generate schedule lines and you also have to make sure that you have the correct MRP parameters set-up.
    You can use ME84 to transmit the delivery schedule lines generated by MRP if no changes are required. With the ME84 you can transmit multiple releases at once, however this transaction can not be used to make manual changes to the MRP proposal.
    The scheduling agreement offers lot's more possibilities but the above should get you going with the basics.
    Hope this will help you on your way.

  • Change Scheduling Agreement and Info Record using Bapi

    Hi Experts,
    Can anybody say how to change the Scheduling agreement and Info Record using Bapi.
    I use BAPI_AGREEMENT_MAINTAIN to change Scheduling Agreement .
    But it does not changing Scheduling lines.

    Hi,
    Please find the below link check the setting are correct or not
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/a02cb00a-bfb4-2c10-98aa-e33e7f64ba28?quicklink=index&overridelayout=true
    Reagrds,
    Pramod

  • Same BO is getting invoked for Pur. Order, Schedule Agreement and Contract

    Hi All,
    My Scenario is like this:
    For Purchase order, Scheduling Agreement and for Contract the Release Statergy are same. For these three scenarios i have created 3 different workflow templates.
    My Purchase order workflow is working fine.
    My problem is :
    When i create a Schedule agreement or a contract, my PO business object is getting invoked and it goes to error.
    I have a doubt:
    For all the three scenario's they are using same number range, will this may be one of reason for the above problem???
    Kindly help me to resolve the issue.
    Thanks and Regards
    Balaji E.

    Hi,
    You can check this link:-
    https://www.sdn.sap.com/irj/scn/wiki?path=/display/abap/workflow+scenario (based on PO change)
    https://www.sdn.sap.com/irj/scn/wiki?path=/display/crm/action%252bprofiles%252bin%252bsap-crm(reason for more than 1 WF trigger)
    More than 1 WF trigger, could be that there would be a triggering condition that triggers more than 1 WF. Since further the conditions are not satisfied, this could lead the WF in error state.
    Let me know if u still face any issues..!!
    Regards,
    Kanika

  • Scheduling Agreements and relevant schedule lines configuration !

    Dear Sapients,
    I request you all to help me in providing the configuration steps for Scheduling Agreements and relevant Schedule lines configuration.
    Its urgent please help me !!
    Regards,
    Sreedhar.
    kodalisreedhar----
    com

    Hi Sreedhar,
    Scheduling Agreement with Delivery Schedules
    Definition
    An outline agreement that is created for one or more materials and outlines the overall expected quantity of the material(s) to be delivered to the customer over a specific period of time.
    Use
    The scheduling agreement is used as a basis for delivering a material. The customer sends in scheduling agreement releases, referred to as delivery schedules, at regular intervals to release a quantity of the material.
    Structure
    The structure of scheduling agreements with delivery schedules resemble that of other sales documents in the R/3 System, in particular the standard scheduling agreement.
    Data that applies to the entire document appears in the header; data about materials appears at item level; and delivery dates and quantities appear in the schedule lines within the delivery schedule. Additionally, the system maintains a history that permits you to compare and contrast various generations of delivery schedules.
    Integration
    Data in scheduling agreements comes from three sources:
    The customer sends in requested quantities and dates, normally by Electronic Data Interchange (EDI)
    The component supplier enters data manually
    The system automatically copies data into the scheduling agreement from master records
    Please go through the below link for further information
    http://help.sap.com/saphelp_47x200/helpdata/en/93/7439fb546011d1a7020000e829fd11/frameset.htm.
    Please Reward If Really Helpful,
    Thanks and Regards,
    Sateesh.Kandula

  • Scheduling agreement and SUS

    Hi
    Can anybody let me know,
    What are the steps involve in creation of scheduling agreement and distributing the scheduline lines to SUS.
    Regards
    Ashish

    In R/3 go to transaction -->
    ME31L ---> Create Scheduling Agreement
    ME38   ---> Maintain Delivery Schedule
    ME84  ---> Create SA Releases
    Once this is done --> and all the configurations are in place , system will SEND
    SAR to SUS.

  • What are the config steps for contract mass change and quota arrangement?

    Hi friends
    what are the config steps for contract mass change and quota arrangement?
    Regards
    Raj Kumar

    Process Flow
    The mass change process consists of four steps. You navigate between these steps by choosing the Next and Back buttons located at the bottom right-hand corner of the screens.
           1.      Search for contracts
    You search for and select the contracts or the contract hierarchy that you want to change.
    Contracts that have the status Closed cannot be changed.
           2.      Define mass changes
    You specify the changes you want to make.
    You make changes at header data level and at item data level by choosing the relevant change methods. A green tick appears next to each change parameter so that you can see where changes are already active.
    Once you enter this step, the documents you have selected to be changed are locked so that other users cannot make changes to them until you are finished with this process.
           3.      Simulate mass changes
    Here you can perform a trial run of your mass changes. This simulation step is optional.
    We recommend that you perform this step so that you can check how the change methods you have chosen will be processed by the system.
    You receive status messages about the change methods for each contract and can quickly see whether any errors arise in connection with the proposed changes at this stage. From this step, it is easier for you to go back and correct the error than after applying the changes.
    Background processing
    The system processes the changes in the background.
    If there are a large number of contracts to be processed, this step could take some time to complete. In this case, you can leave the transaction so that you can, for example, carry out other tasks in the meantime.
    The system sends you an e-mail once the simulation step is complete. The e-mail contains a link to the relevant screen in the application so that you can return to it when it is convenient for you to do so. If you have left the SRM application, you can only return via this link.
    Here you can see the status of the changes and, if necessary, you can correct any errors by going back to the Define mass changes step.
    The messages that you receive in the simulation step are not confirmation that a change has been performed. They simulate the messages you get after you apply the changes. You must complete the final step of the mass change process and apply the changes before they take effect.
           4.      Carry out mass changes
    Here you apply the changes to the contracts.
    You cannot reverse this step, which is why we advise you to perform the simulation step beforehand.

  • Deviation from sourcelist and quota arrangement

    Hi all,
    Is there any warning message if there is any deviation from source list and quota arrangement.
    For ex:
    We have maintained 3 vendors in source list , 100,101,102
    Whereas in quota 100 and 101 is mainatained
    While making PO if we give 102 vendor which is not maintained in quota,it should throw a warning.
    Thanks & Regards

    This is the std SAP solution
    if you have proper quota indicator set in material master and you create the PO other than the vendor defined in the quota and the source list is maintained for the vendor you are using in PO then system issue the warning message as stated below
    "Quota arrangement specifies vendor XXXXXX" Message no. Message no. 06564
    detaisl of message:
    A quota arrangement exists for the material you wish to order. The quota arrangement specifies that the material is to be ordered from vendor XXXXX.
    Make sure you have quota usage indicator in material master checked for PO.

  • Tables for following scheduling agreements and PR data

    Hi All ,
    Please can you tell me table names if I want the following information
    1. Scheduling Agreement Created By, Amended By, Modified Date, Plant
    2. Req Created by, Released by, Cost center, plant
    Thanks in advance
    Vinayak

    To view the fields listed in a table go to Tcode SE11 and enter the table name and execute
    EBAN  - Purchase Requisition 
    EBKN  - Purchase Requisition Account Assignment 
    Req Created by Table:EBAN Field ERNAM
    Released by- Table:EBAN Field FRGGR
    Cost center- Table:EBAN Field FISTL (Funds Center)
    plant-Table:EBAN Field WERKS
    For Scheduling Agreements following are the tables:
    EKEH    - Scheduling Agreement Release Documentation 
    EKEK    - Header Data for Scheduling Agreement Releases 
    EKET     - Scheduling Agreement Schedule Lines 
    EKETH   - Scheduling Agreement Schedules: History Tables
    You will find the following list of fields in these tables:
    MANDT                          Client
    EBELN                          Purchasing Document Number
    EBELP                          Item Number of Purchasing Document
    ETENR                          Delivery Schedule Line Counter
    EINDT                          Item Delivery Date
    SLFDT                          Statistics-Relevant Delivery Date
    LPEIN                          Category of Delivery Date
    MENGE                          Scheduled Quantity
    AMENG                          Previous Quantity (Delivery Schedule Lines
    WEMNG                          Quantity of Goods Received
    WAMNG                          Issued Quantity
    UZEIT                          Delivery Date Time-Spot
    BANFN                          Purchase Requisition Number
    BNFPO                          Item Number of Purchase Requisition
    ESTKZ                          Creation Indicator (Purchase Requisition/S
    QUNUM                          Number of Quota Arrangement
    QUPOS                          Quota Arrangement Item
    MAHNZ                          No. of Reminders/Expediters for Schedule L
    BEDAT                          Order date of schedule line
    RSNUM                          Number of Reservation/Dependent Requiremen
    SERNR                          BOM explosion number
    FIXKZ                          Schedule Line is "Fixed"
    GLMNG                          Quantity Delivered (Stock Transfer)
    DABMG                          Quantity Reduced (MRP)
    CHARG                          Batch Number
    LICHA                          Vendor Batch Number
    CHKOM                          Components
    VERID                          Production Version
    ABART                          Scheduling agreement release type
    MNG02                          Committed Quantity
    DAT01                          Committed Date
    ALTDT                          Previous delivery date
    AULWE                          Route Schedule
    MBDAT                          Material Staging/Availability Date
    MBUHR                          Material Staging Time (Local, Relating
    LDDAT                          Loading Date
    LDUHR                          Loading Time (Local Time Relating to a
    TDDAT                          Transportation Planning Date
    TDUHR                          Transp. Planning Time (Local, Relating
    WADAT                          Goods Issue Date
    WAUHR                          Time of Goods Issue (Local, Relating to
    ELDAT                          Goods Receipt End Date
    ELUHR                          Goods Receipt End Time (Local, Relating
    ANZSN                          Number of serial numbers
    NODISP                         Ind: Reserv. not applicable to MRP;Purc
    hope this helps!

  • Reg. Scheduling agreements and contracts

    Hi Dears
    Please explain in greate details "what is schedule agreements" , "contracting", "How to use Scales in standard PO" and what is scales.
    I couln't find the proper explanation in our Forums.
    Bye
    Rajkumar

    Hi
    (1) - Schedule agreements allow you to have 2 different sets of schedule lines (VBEP-ABART).  Standard SAP you should have two sets of tabs - of schedule lines. One Forecast & the other JIT.  Forecast forwards the schedule lines to planning (seen in MD04) and JIT passes them to shipping (VL10). They can be identical or different. Typically these are used for component supplier customers (namely Automotive). The customer will provide you 4-10 weekly buckets (usually a
    Monday date) of future forecast qtys. Also send you 1-2 weeks of individual FIRM ship dates - which are entered on the JIT. It comes down to the customer not knowing exactly what they need next week, but they don't want to suprise you with a large order qty, where your lead times are 5+ days. The forecasted qtys they sent last week should account for this.
    (2) Cumulative Quantities are tracked and influence how the schedule agreement passes requirements to both forecasting and shipping. These qtys are sometimes requested by the customer on ASNs. Cumulative qtys reset at year end unless you've got a customer calendar or you've modified standard SAP user exits to not reset.
    Schedule agreements are very nice when the customer sends EDI data (830s = forecast or 862s = JITs). Outside of that they can really cause trouble regarding daily maintenance, missing requirements, *** qty corrections, year end processing, etc.
    One alternative would be to use customer independent requirements - entering the weekly, monthly forecasting qtys and entering standard sales orders (with or without multiple schedule lines) to represent the true firm qtys.
    Refer below
    http://www.sap-basis-abap.com/mm/gr-creation-for-schedule-agreement.htm
    You can fix a price in the info record for a say qty from 1-100 price RS150 & if the order qty is 101- 500- the prices is 140 . Scales cannot be used directly in PO but can be pulled into the PO from various master data like info record,  quota arrangement.
    For further details refer sdn thread below
    Contracts
    scheduling agreements
    Message was edited by:
            SHESAGIRI.G

  • About selecting Scheduling Agreement and Forecast delivery schedule

    Hi Experts,
    i want to write a Report, with 2 parameters for the selection : Sold-to-party and Period
    For this Sold-to-party/Period, I want to list all scheduling agreement + Forecast delivery schedule.
    I already found the Function SD_VBEP_READ_WITH_VBELN to read all Forecast delivery schedule lines using Sales Doc.No. , but how can I select all Scheduling Agreement for the Period ?
    Regards,
    David

    Solution:
    by selecting data from table VEPVG (Delivery Due Index) and using function SD_VBEP_READ_WITH_VBELN for each SD Document.
    Regards,
    David

  • What is the difference between scheduling agreement and delivery schedule

    Hi
    1. Can anyone explain me the difference between scheduling agreement output
        and scheduling agreement delivey schedule
        Will the both look same in T.code SP02 when seeing the output for a document.
        Can anyone send me T.codes for above ones in purchasing.
    2. when seeing the Detailed statement for rebate agreement,there is item number.
        In which table can we see the item number for rebate agreement

    Hi,
    If you have to deal with more complex situations, you can define a delivery cycle in the material master record in addition to the planning cycle. In so doing, you determine the days on whichthe vendor delivers his goods. The delivery cycle is entered in the material master record as a planning calendar in the Planning calendar field.
    You enter a delivery cycle if the delivery date (or the goods receipt date) depends on the day on which you order the goods. For example, you carry out the planning run and place your orders on Mondays and Tuesdays. If you place the order on Monday, the delivery is made on Wednesday, if you wait until Tuesday to place the order, the delivery is not made until Friday
    Where as Planning calander is Three character number (numeric or using letters) that specifically identifies a PPS-planning calendar. The difference between Planning calender and delivery cycle is If you have selected the MRP type "MRP" and have set a period lot-sizing procedure according to planning calendar, you enter here which planning calendar is to be used.
    If you selected the "time-phased planning" MRP type, the planning calendar that you specify here defines the delivery cycle. This specifies the days on which the vendor delivers the material. You can enter the planning cycle in addition to the delivery cycle

Maybe you are looking for