Scheduling agreement full cycle??

Hii
Can anybody explain me step by step with transaction code for Scheduling agreement.
Full cycle with account transaction and accounting documents being generated in system ,  with vendor payment transaction.
One by one transaction - full cycle .
thanks
SAP-MM

HI,
1. SAP Menu u2192 Logistics u2192 Materials Management u2192 Material Masteru2192 Material u2192 Create General u2192 Immediately
In order for you to be able to generate both forecast and JIT delivery schedules, the JIT delivery schedule indicator in the Purchasing view of the material master record must have the value 1.
2. Change vendor master record in such a way that when ascheduling agreement with release documentation is created for plant 1000 for e.g.,the release creation profile ABCD is defaulted from the vendor master record.
a) SAP Menu u2192 Logistics u2192 Materials Management u2192 Purchasing u2192Master Data u2192 Vendor u2192 Purchasing u2192 Change (Current)
You can define the release creation profile in the plant-specific purchasing data (Alternative Data). The field is located among the default values for the material.
3. The agreement begins as of today's date and is valid for two years. The agreement is valid for plant 1000. The target quantity is 100,000 pc. You have negotiated a price of 78 EUR per pc. Deliveries are received into storage location 0001. Before saving the scheduling agreement, branch to Additional Data and verify that the release creation profile ABCD and the
JIT delivery schedule indicator have been adopted from the vendor master record and material master record, respectively. In the additional data, enter the planned delivery time of two days.
a) SAP Menu u2192 Logistics u2192 Materials Management u2192 Purchasing u2192Outline Agreement u2192 Scheduling Agreement u2192 Create u2192 Vendor Known
Choose the agreement type LPA in order to be able to send FRC and JIT delivery schedules to your vendor.
Access the additional data via Item u2192 More Functions u2192 Additional Data.
4. SAP Menu u2192 Logistics u2192 Materials Management u2192 Purchasing u2192 Outline Agreement u2192 Delivery Schedule u2192 Maintain
Select the item and choose Item u2192 Delivery schedule.
give the qty and time and date.
Hope Help U !
Regards,
Pardeep malik

Similar Messages

  • External Kanban (full to empty) - Scheduling Agreement Schedule Lines

    Hello Sir/Madam,
    Our control cycle is using external replenishment procedure with "0002" (i.e. working with Scheduling Agreements ).
    Indicator u201CSeparate GR posting when changing status to fullu201D is not set.
    Symptom:
    When the Kanban container is empty, I perform a PKBC to sign the status from "Full to Empty" and I save it. The system generates a delivery schedule and an email is sent to the vendor.  This can be proved by MD04.
    The problem is that the system generates another delivery schedule after few minutes and also another email is sent to the vendor. So, the delivery schedule and the email are incorrectly done twice.
    I am wondering how the system setup is able to generate automatically a new delivery schedule which is not correct.
    Please could you suggest me some solution.
    Regards
    Luca

    I think in this case, that if no user exits were activated in your system, you should create an OSS message for SAP.

  • Purchase full cycle process with T-Codes and screen shots

    HI GURUS,
    will anyone mail PO Full Cycle with screen shots? And t-codes
    1. PURCHASING REQUISITION
    2. REQUEST FOR QUOTATION
    3. QUOTATION
    4. PURCHASE ORDER
    5. GOOD'S RECEIPT
    6. INVOICE VERIFICATION
    7. PAYMENT

    The typical procurement cycle for a service or material consists of the following phases:
    1. Determination of Requirements (MD02 / ME51N): - Materials requirements are identified either in the user departments or via materials planning and control. (This can cover both MRP proper and the demand-based approach to inventory control. The regular checking of stock levels of materials defined by master records, use of the order-point method, and forecasting on the basis of past usage are important aspects of the latter.) You can enter purchase requisitions yourself, or they can be generated automatically by the materials planning and control system.
    2. Source Determination: - The Purchasing component helps you identify potential sources of supply based on past orders and existing longer-term purchase agreements. This speeds the process of creating requests for quotation (RFQs), which can be sent to vendors electronically via SAP EDI, if desired.
    3. Vendor Selection and Comparison of Quotations (ME41 / ME47 / ME49): - The system is capable of simulating pricing scenarios, allowing you to compare a number of different quotations. Rejection letters can be sent automatically.
    4. Purchase Order Processing (ME21N): - The Purchasing system adopts information from the requisition and the quotation to help you create a purchase order. As with purchase requisitions, you can generate Pos yourself or have the system generate them automatically. Vendor scheduling agreements and contracts (in the SAP System, types of longer-term purchase agreement) are also supported.
    5. Purchase Order Follow-Up: - The system checks the reminder periods you have specified and - if necessary - automatically prints reminders or expediters at the predefined intervals. It also provides you with an up-to-date status of all purchase requisitions, quotations, and purchase orders.
    6. Goods Receiving and Inventory Management (MIGO): - Goods Receiving personnel can confirm the receipt of goods simply by entering the Po number. By specifying permissible tolerances, buyers can limit over- and under deliveries of ordered goods.
    7. Invoice Verification (MIRO): - The system supports the checking and matching of invoices. The accounts payable clerk is notified of quantity and price variances because the system has access to PO and goods receipt data. This speeds the process of auditing and clearing invoices for payment.
    Rebate Process:
    1. XK02 - Changing a Vendor Master Record (Activate "Subsequent Settlement" and "Sebseq. sett. index" in Purchasing view)
    2. MEB1 - Creating a Rebate Arrangement
    3. ME21N - Creating a Purchase Order
    4. MIGO - Processing the Goods Receipt for the Purchase Order
    5. MIRO - Processing the Incoming Invoice on the Basis of a Purchase Order
    6. MEB4 - Creating an Interim Settlement
    7. MEU2 - Creating a Business Volume Comparison
    8. MEB2 - Creating a Final Settlement
    A centrally agreed contract is involved if:
    A single purchasing organization procures for an entire corporate group, or
    A reference purchasing organization makes a contract available to other associated purchasing organizations, enabling the latter to issue release orders against this contract
    Centrally Agreed Contracts are created in same transaction ME31K, but here is some difference in maintaining the pricing conditions and partner functions.
    Maintaining Plant Conditions
    1. When maintaining the centrally agreed contract, choose Edit > Plant conditions > Overview.
    2. On the overview screen that then appears, enter the desired plant and choose "Overview" icon Plant prices.
    3. An item overview screen appears, starting from which you can maintain conditions.
    Choose Item > Conditions to access the condition maintenance screen.
    4. Return to the overview and repeat the process for all plants for which you wish to store plant-specific conditions.
    5. Save your input.
    Maintaining Partners
    You can maintain the different partners either in the vendor master record or individually in the contract. If the partners have been maintained in the vendor master, they are suggested in the contract.
    Maintaining partners in a contract
    1. In the contract, choose Header > Partners.
    2. The Data Retention Level: Partners screen appears. Enter the plant and/or vendor sub-range, and choose ENTER. The Maintain Partners screen appears.
    Note
    To see which partners have already been maintained, select the desired item and choose "Display" button Level.
    3. Enter the desired partner and return to the item overview for the contract.
    4. Save your input.
    Maintaining partners in the vendor master
    1. Choose Extras > Different data on the Partner Roles (partner functions) screen in the vendor master record.
    2. On the Create Different Data screen, enter the plant or vendor sub-range and select Partner Roles.
    3. Click "Enter" button. The Change Vendor: Partner Roles screen appears.
    4. Enter the desired partners and click "SAVE" button to save your input.
    Then create Release orders (in ME21N) w.r.t. Centrally Agreed Contrat

  • Error in scheduling agreement

    Dear Expert
    We are creating Scheduling agreement through ME31L system create the SA but when i check it through ME32L system is giving error SA is not created i have check in the table EKET in that also entry is not there but at the time of creation system generate SA with number , however i got this message
       *Express document "Update was terminated" received from author "XYZ" where xyz is the user id  when i use ME32L, please help me to resolve this issue
    Regards
    Edited by: usmfarhan on May 13, 2009 5:17 PM

    Dear Farhan,
    I think your problem is related data base level,i faced same problem some days ago.
    so when your data base is full the data update or table storage place is not availble system update is terminated message is come.
    so you concern your basiss people empty some data files or re arrange data base.otherwiese basis people take care how to handle this problem.
    ok,i hope this may helps you
    Prem.

  • Difference between Scheduling agreement delivery schedule and PO delivery s

    Dear All,
    Please tell the difference between the Scheduling agreement delivey schedule and PO delivery schdule.
    In PO itself, we can give the delivery schedule.
    Then what is the purpose of making scheduling agreement and maintain schedule in ME38?
    Regards

    Hi,
    Difference between Scheduling agreement and PO is while PO is a legal document whatever the delivery schedules you mention in PO, you are liable to pay for the entire qty in case of cancellation
    In case of scheduling agreement, we have Firm Zone and Tradeoff Zone to provide some cushion against paying for the entire qty you have ordered
    Firm zone: (go-ahead for production)
    If the date of a schedule line lies within the firm zone, the vendor has the go-ahead to produce the relevant quantity with the assurance that the orderer will bear any and all material and production costs associated with the scheduled quantity in the event of subsequent cancellation by the latter.
    Trade-off zone: (go-ahead for procurement of input materials)
    If the date of a schedule line lies within the trade-off zone, the vendor has the go-ahead to purchase any input materials necessary to produce the scheduled quantity. The orderer will recompense him in full for such outlay (but not for any other production costs) in the event that he should subsequently cancel the scheduled quantity.
    Schedule lines that lie beyond the firm and trade-off zones fall within the planning zone (forecast zone) and are for rough guidance only, being without any commitment on the part of the orderer.
    In case of PO if you want to cancel the order, you are liable to pay for the entire quantity, while in case of Scheduling agreement if you want to cancel the schedule and if the days fall in Firm zone or trade off zone or planning zone you have to pay only for raw materials or assembled products according to the above description
    Regards
    Venkat

  • 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

  • MRP Run with Scheduling Agreement

    Hi All,
                Can anyone explain the the Scheduling Agreements, we are running the MRP with schedule lines generated.I want to know the complete cycle with the T-codes in sequence they are executed.My requirement is business people need a demo of the Scheduling Agreement,type LP,LPA how they work and difference between LP and LPA.They run the MRP everyday.
    Thanks,
    Kris
    Edited by: Csaba Szommer on Sep 19, 2011 12:52 PM

    Hi,
    The basic difference between LP and LPA  is the way that the schedules are communicated to the vendor.
    for more clarity please refer the blow links.
    LP and LPA in scheduling agreement?????
    Difference between LP and LPA scheduling agreements
    http://it.toolbox.com/wiki/index.php/Scheduling_Agreement
    Thanks.

  • MRP Reschedules PO ahead of Scheduling Agreement

    Hi,
    We have a situation where one company code (Company A) buys product from a second (Company B) via an inter-company Scheduling Agreement. The schedule lines are generated automatically from MRP.
    Company A now has a need to purchase a one-off quantity of the same product from an external company and so have subsequently raised a Purchase Order with delivery dates in the future (after the next requirement from company B is due).
    The result of the MRP run has been to prompt rescheduling of the Purchase Order in to meet immediate requirements and only generate schedule lines from Company B after the full Purchase Order quantity has been used. This is not as required, as the dates on the PO are those that are achievable by the external supplier.
    I can't find any settings that relate to a prioritising of MRP elements which would imply that a PO has precedence over a Schedule Line, and I would rather not fix the schedule lines of the Scheduling Agreement.
    Has anyone seen this before, or knows what I'm missing.
    Thanks

    Hi suresh
    The requirement goes this way.the sales person creates a scheduling agreement instead of a sale order.The next process is running MRP for the scheduling agreement .
    Just he wants to know through a report what are the sceduling agreements peding for MRP run.
    Shankar

  • How to set delivery complete in scheduling agreement automatically

    Hi. I would like to request for help on how to flag delivery complete in an scheduling agreement?
    When creating a goods receipt against a scheduling agreement, do we need a user-exit  or how is it configured in order to check the quantity receivedthe quantity in the goods receipt and compare it with the quantity in the scheduling agreement (/- de tolerance) and, in case the full ordered quantity has been received, set the flag Delivery completed in the scheduling agreement.
    Thanks.

    Hi,
    We regret that the functionality  setting of "delivery completed"       
    indicator automatically for a scheduling agreement is not included in   
    the SAP standard system.                                                
    For scheduling agreements, you must maintain the final delivery              
    indicator only in the scheduling agreement item.                             
    A maintenance from the goods receipt is useless for scheduling               
    agreements since the current schedule line situation is generally not        
    final. Even if all schedule lines are supplied, this does not mean that      
    no new schedule line might be added. Therefore, for scheduling               
    agreements,maintenance of final delivery indicator is planned only from      
    the document item.                                                                               
    Regards,
    Edit

  • Scheduling Agreement with LPA

    Hi,
    I am trying to generate schedule lines and release them to delivery schedules with doc type LPA.
    I have done the settings in MRP2 view and done the settings in source list, info record and scheduling agreement.
    I have created and Plnd Independent requirements in MD61 and executed the planning run in MD02 but unable to create schedule lines.
    Could you please advise me if i am missing any settings or config's.
    I wan to know how the zones work with LPA and how the whole cycle and the functions available with LPA.
    Responses will be highly appreciated.
    Regards,
    Mittu G

    hi
    These are the Prerequisites befor you go on to SA with release
    Scheduling agreement releases (FRC and JIT schedules) can only be generated for scheduling agreements with release documentation (in the standard system, document type LPA).
    (In the standard system, the Release docu. indicator is selected for document type LPA in Customizing for Purchasing under
    Scheduling Agreement -> Define Document Types.)·
    If you wish to work with JIT delivery schedules, the JIT schedule indicator must be set in the material master record (Purchasing or MRP 2 view) and the Additional data of the scheduling agreement item.
    You create SA releases by means of the Purchasing menu via
    Scheduling agreement -> Create release
    Choose release type ->FRC and JIT delivery schedulesSelect scheduling agreements - Specification of plant
    Scope of selection- Changed or next date
    Creation- According to strategy in profile, Tolerance check active
    On the days on which the next FRC date (1st. Monday in the month) or the next JIT date (Monday each week) is reached, scheduling agreements with the above profile settings are selected and SA releases (delivery schedules to be issued to the vendor) created (because the next creation date has been reached).
    Reward points if useful
    Thanks & Regards
    Kishore

  • How in scheduling agreement GR and payment is done

    how in scheduling agreement the GR and payment is done or on what basis payment is done?

    Hi Rajkiran,
    Delivery dates and quantities are part of the purchase order terms.
    As soon as GR is made, vendor account is credited.
    In MIRO (LIV), vendor is paid depending upon, delivery date, price matched and quality approves the item.
    Cycle in case of scheduling agreement is the same as standard purchase order.
    Best Regards,
    Subha
    Pls grant me points if found the above info useful

  • Correct usage of Scheduling Agreements?

    Hi Experts!
    One of my groups is using scheduling agreements, however I do not think they are using it the way SAP had intended. 
    Example:  They use Scheduling agreements, similar to a blanket order.  However, the blanket order quantity is fluid and the order can remain open even when the initial quantity has been fulfilled.  These Scheduling Agreements will contain many items, sometimes around 30-40 line items.
    The staff basically conducts two activities for these customers:  enter new scheduling agreements with updated validity dates and expedite releases with a less than two week time frame.  These expedites are communicated by the customer via email. 
    The customers submit a 16 week forecast via EDI as well as a firm 2 week JIT.  Most scheduling agreement activity occurs systematically, although there are daily expedites for each customer for a few parts.
    Initially, when entering a scheduling agreement, the staff does not indicate the JIT schedule.  However, they do enter into the Forecast delivery schedule, basically just to activate and allow communication from customer.
    My concern is should scheduling agreements contain that many items?
    Also, the staff makes many changes in the scheduling agreements and when it reaches the time when the period for the scheduling agreement, what ever material they did not get to ship, they ship it to the customer in one bulk.  Are you suppose to do that with scheduling agreements?
    In addition, sometimes the staff allocates some of the materials promised to the customer on the scheduling agreements to another customer, then just re-allocates it back at a later time...should this be done or is it bad business practice?
    What are good business practices for usage of Scheduling Agreements?  Any information will be greatly appreciated.  Thank you for your time in advance!
    WC

    My concern is should scheduling agreements contain that many items?
    Also, the staff makes many changes in the scheduling agreements and when it reaches the time when the period for the scheduling agreement, what ever material they did not get to ship, they ship it to the customer in one bulk. Are you suppose to do that with scheduling agreements?
    <b>you should not do that the reason is SA is use full for the JIT and promise to deliver things</b>
    In addition, sometimes the staff allocates some of the materials promised to the customer on the scheduling agreements to another customer, then just re-allocates it back at a later time...should this be done or is it bad business practice?
    <b>It's depent on the company bussiness policy - not rgiht process but if bussiness want to do then what else you can do?</b>
    What are good business practices for usage of Scheduling Agreements? Any information will be greatly appreciated. Thank you for your time in advance!
    <b>A customer scheduling agreement is an outline agreement with the customer containing delivery quantities and dates. These are then entered as schedule lines in a delivery schedule. You can either create schedule lines when you create the scheduling agreement or you can create them later.
    You fulfill a scheduling agreement by creating the deliveries in the schedule as they become due. You process deliveries for a scheduling agreement in exactly the same way as you process a normal delivery. After you have carried out the delivery, the system updates the Delivered quantity field in the scheduling agreement item with the delivery quantity. The following graphic shows the document flow for scheduling agreements.
    The same functions are at your disposal for processing scheduling agreements as there are for the sales order, including pricing and availability checks.
    In addition to the standard scheduling agreements you can also manage scheduling agreements for the component supplier industry, with their special features that include:
    Working with scheduling agreements with EDI output
    Entering scheduling agreements in a forecast or just-in-time (JIT) delivery schedule
    Using different types of cumulative quantities
    Taking into account the automatic fiscal year change used by the component supplier
    Managing engineering change statuses
    Storing packing proposals
    Creating correction deliveries for the scheduling agreement
    Working with external service agents</b>

  • Redetermined the past due schedul lines in Scheduling agreement

    Hi All,
    We have an issue with past due schedule lines in scheduling agreement, the details are below.
    Delivery date: 3rd Jan 2011 - Order qty is 100 no confirmtion. The system has proposed new date that is 19.01.2010 (System date) with full confirmation. The Scheduling agreement is not relevant for ATP check also. When we check with other plant scheduling agreement, it is not determining any new date, it is confirming on same date.
    Different Document types used in two cases, but the config is same in both cases. Not sure why the system is determining to current date with full confirmation. Is there any config relevant to this.
    Regards,
    Lakshmikanth

    hi
    schedule lines in scheduling agreements = correct & confirmed dates.
    that means if you enter the date manually here system confirms that date as schedule line date.
    compare those two plants and let me know if any difference is there in between.
    check MMR RLT's MRP views
    check Lead time in days - document types
    check & confirm.
    balajia

  • Scheduling agreement GR

    I tried to carry out procurement using Scheduling agreement , I  made the same using  ME31l. I gave the schedule lines using ME38. I ensure that this scheduling agreement is not subjected to any release stratergy. When I tried to go for MIGO using this Scheduling Agreement and type its number against PO . System displays error message there are no selectable items in the scheduling agreement. I want to know what can be the reason for the same.
    Also Would like to have stepwise procedure and subsequent checks to carry out complete procurement cycle using Scheduling Agreement.

    HI
           Please maintain schedule lines for todays date and do <b>MIGO on the same day</b> by giving the scheduling agreement number in the purchase order coloumn.I think it may work.
    Reward if useful
    Thanx and Regards
    SHYAM.R

  • SAP BW Purchasing - Scheduling Agreement delta processing

    Hi,
    I have a question about Scheduling Agreements coming from ECC to BW with delta processing.
    When a goods receipt happens for a Scheduling Agreement item, it registers process key 2.
    However, it seems that when a second goods receipt happens for that same scheduling agreement item, the old goods receipts updates with a process key 4, and the new receipt takes the process key 2 when we aggregate at an InfoCube level. In the first level write optimized DSO, the process keys are in tact for every line item & schedule line (all goods receipts process key 2 are there).
    Can somebody confirm this logic?
    We are having issues because we need all of that goods receipt history stored in our InfoCubes, and we do not know how to resolve. Please help! Points will be assigned...
    Thanks very much,
    Courtney

    are you saying that Process Key is 2 for both the good reciepts in write optimized DSO but in cube, first good reciept is having a process key 4 when second good reciept is also there?
    If yes, it seems that problem is with the info object for process key - is it a Key Figure or characteristic?
    It should be a characteristic so that the value is not added but overwritten.
    you are doing a full or delta from Data Source to DSO and DSO to Cbue?
    Regards,
    Gaurav

Maybe you are looking for