Cumulative Quantities in Scheduling Agreement

Hi All
Can anyone tell me how this works with *** quantites, we have always ran from receipts. However, if we choose inbound deliveries does that mean when we send releases the YTd receipt + open Inbound deliveries will be sent as the YTD *** values to our vendor.
Our company is looking for something with intransit values as part of our cums. How does this affect our *** requirements if this is changed?
Regards,
Krisjohn

I'm new to 862 (Shipping Schedule) iDocs and I'm having a problem with the dates/quantities during the update processing. We are receiving an inbound 862 and we run the transaction BD87 to update a Scheduling Agreement. BD87 processes without any errors. When we check the Scheduling Agreement, we expect the Forecast Delivery Schedule dates/quantities to be updated, but the JIT Delivery Schedule dates/quantities are being updated instead. How do I determine which dates/quantities are to be updated with my inbound data?
Any assistance is greatly appreciated!

Similar Messages

Cumulative quantities on sched. agreement forecast in inbound IDoc DELFOR

Hello, we have a customer that send cumulative quantities on forecast line of a 830 EDI message. Do SAP inbound IDoc processing manages cumulative quantities, or I have to transform them to corresponding discrete quanities?
Example
FST1300DW20111001
FST1400DW20111008
FST1700DW20111015
Edited by: editeam on Nov 9, 2011 4:43 PM

I'm new to 862 (Shipping Schedule) iDocs and I'm having a problem with the dates/quantities during the update processing. We are receiving an inbound 862 and we run the transaction BD87 to update a Scheduling Agreement. BD87 processes without any errors. When we check the Scheduling Agreement, we expect the Forecast Delivery Schedule dates/quantities to be updated, but the JIT Delivery Schedule dates/quantities are being updated instead. How do I determine which dates/quantities are to be updated with my inbound data?
Any assistance is greatly appreciated!

Cumulative Scales in Scheduling Agreements

Hi Guys,
I need an advice how to maintain cumulative scales, i.a. as soon as we have ordered more than 10'000 pieces of a part in total we get a better price for every part over 10'000.
So we have 3 schedule lines of 3000 pieces for price A. The forth schedule line of 3000 pieces should have price A for 1000 ea. and price B for 2000. Now each new schedule line should have price B.
Is there any way to maintain this condition.
Thanks for your help.
Tobias

Sorry for the double message. In is a mistake on my side. It is my first time on this forum...

Dates and quantities copied from Scheduling Agreement to Delivery Order

Hi everybody,
we're experiencing a problem with copying control for dates/quantities between Scheduling Agreement and Delivery Order.
If we define a Forecast Delivery Schedule with more lines/dates into a Scheduling agreement, when I create a Delivery Order with reference to a specific date the system always copies the first forecast delivery schedule date, disregardful the date specified in the selection criteria for delivery creation and with the fact that this could have already been carried out.
Here's an example:
Forecast Delivery Schedule into Scheduling agreement:
(Date) 12.03.07   (Quantity) 10 TO
(Date) 13.03.07   (Quantity) 12 TO
(Date) 14.03.07   (Quantity) 15 TO
When delivery has to be created with reference to Scheduling Agreement, the system doesn't about the date specified in selection parameters (e.g. 14.03.07) and copies the quantity of the first forecast delivery schedule line (10 TO).
Does anybody knows how to maintain Copying Control for dates and quantities between Scheduling agreement to Delivery Order?
Thank you!
Luca

Dear Pattanaik,
check data transfer from copy controls.for this T-code is VTLA
here select your doc type and select details and check also item.check inside both types data trasfer wich is assigned change from this item to header.your problem may ve coming from here.
hope this will helps you
Prem

Cumulative Qty Received by Customer wrongly updated in Scheduling Agreement

Hi All,
I face a strange issue in Schedule Agreement[Forecast Delivery Schedule].
The exact scenario is as follows:
1)On 17/09/09, I saw a CmlQtyReceived of '249'.
2)On 19/09/09, this value got changed to '141'
3)On 23/09/09, this value again got changed to '249'
I was not able to identify the reason for the '141' Qty getting displayed on 19th. Even if I go to Analysis now, there is no Forecast Delivery Schedule with '141' Qty to support the display.
Do let me know the issue in this.
Needless to say points will be awarded for helpful replies.
Regards,
Raj Kumar Reddy.

Hello;
I researched about this issue and I would like to recommend you to check the FAQ note about the most critical problems with Scheduling Agreements, note 923104.
As stated in question 2 (or also 3), you can check and correct the cumulative quantityes using Report SDLIPL01. Regarding this report, please refer to note 923105.
In addition, I kindly ask you to please check notes 922638 and 922639 about more details regarding the cumulative quantities.
Also, read the follow notes related to fiscal year changes:
      336670    Avoid the fiscal year change (introduction)
      332971    Avoid the fiscal year change (coding)
Well, I hope those documentation can help you a lot.
Regards
Ruy Castro

Delivery from sales scheduling agreement with one item per schedule line

Hi all,
I have a sales scheduling agreement where the same part number has 3 different JIT schedule lines and I need to create a delivery with 3 item lines: every item line of the delivery has to be referred to one schedule line of the scheduling agreement.
When I create the delivery with transaction VL10E it has only one item line and its quantity is the sum of the 3 schedule lines of the sales scheduling agreement.
I've tried to change the customizing of the User Role, choosing the Split Schedule Line = 2 ("One item per schedule line") but the delivery is created again with only one item line.
How can I solve this issue?
Thanks in advance for reply

Dear Alex
The SAP standard behaviour is that all schedule items with delivery date in the past have to be rescheduled anyway to one date and are combined therefore.
Partially this behaviour can be influenced in VL10* by 2 parameters in
the user role : Split per sched.line and Rule (delivery qty).
Please find below informations about these different parameters
"Split per sched.line propose you 3 Rule for creating one delivery item
per schedule line. In a delivery list in item view with multiple
schedule lines, you can decide for the same document item whether you
want to generate one delivery item per schedule line or whether you want
to deliver the cumulated quantity of the last schedule lines selected.
About rule for delivery quantity, the following rules are currently
implemented:
1. No cumulation
The open schedule line quantity to be delivered is the quantity at which
the list line is delivered.
2. Sum of all open schedule line quantities to be delivered that fall
before the chronologically latest date in the to field (following the
Deliv. creation date field) of the selection criteria.
3. Sum of all open schedule line quantities to be delivered whose
delivery creation date falls within the selection time frame (between
the dates in the Deliv. creation date and to fields, respectively),
making the calculation of the quantity to be delivered consistent with
selection criteria. However, calculationof the quantities delivered with
the order's schedule line quantities is not affected."
Hope this helps.
Regards
Tonia

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?
you should not do that the reason is SA is use full for the JIT and promise to deliver things
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?
It's depent on the company bussiness policy - not rgiht process but if bussiness want to do then what else you can do?
What are good business practices for usage of Scheduling Agreements? Any information will be greatly appreciated. Thank you for your time in advance!
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

Data migration approach for Scheduling Agreements

Gurus,
Can anyone provide guidance on the data migration approach for Scheduling Agreements? How can we migrate the open delivery schedules and the respective cumulative quantities? The document type being used is "LZ".
Can correction deliveries (Doc type - LFKO) be used update the initial cumulative quantities?
Any help in this regard is higly appreciated.
Regards,
Gajendra

Hi Zenith
You might find useful information here: IS-U data export (extraction) for EMIGALL.
I've done numerous IS-U migrations in the last 10+ years, but never one from IS-U to IS-U.
One main questions to start with: Are the two systems on the same release level?
If they are not and it would be too much effort to get them onto the same release level I would think creating your own extract programs and using the Migration workbench (EMIGALL) is the way to go.
If they are on the same level, there might possible other ways to do it, dependent on the differences between the two systems (mainly around customising). Assuming there are significant differences - otherwise why would you bother migrating? - there's the high probability that using EMIGALL is the way to go as well.
Yep
Jürgen

Process for Scheduling Agreement

Please tell me the process for Scheduling Agreement?
I have created Scheduling Agreement thru ME31L and delivery schedule thru ME38. what is the further process?

Scheduling agreements provide for the creation of delivery schedules specifying purchase quantities, delivery dates, and possibly also precise times of delivery over a predefined period.
Create scheduling agreement
ME31L
Create stock transport scheduling agreement
ME37
Change scheduling agreement
ME32L
Maintain scheduling agreement supplement
ME34L
Recalculate scheduling agreement prices
ME3R
Re-number schedule lines
ME85
Aggregate schedule lines
ME86
Aggregate PO history
ME87
Reset agreed cumulative quantity and reconciliation date
ME88

Concept of just in time in Scheduling Agreements

hi ,
can any one pl help out the concept of "JUST IN TIME "(JIT) , in Scheduling Agreements .

hi,
Schedule agreements allow you to have 2 different sets of schedule lines (VBEP-ABART).
In Standard SAP you can have two sets of schedule lines. One Forecast & the other JIT(just in time)
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 userexits to not reset.
pls reward points if the answer is helpful
REgards
Murali

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

How are deliveries automatically created from scheduling agreement?

How are deliveries automatically created from the schedule line of the scheduling agreement? Can anybody explain this step by step? Can we use the code VL10BATCH for this purpose? If we can, how is this code used?
Thanks in advance.

hi
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 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.
Document Types
To configure document types for scheduling agreements, choose Sales -> Sales Documents -> Sales Document Header -> Define sales document types in Customizing for Sales and Distribution.
The R/3 System contains the following document types for component suppliers:
LZ - Scheduling agreement with delivery schedules (no external agents)
LZM - Scheduling agreement with delivery orders
LK - Scheduling agreement with delivery schedules (external agents)
ED - Delivery by external agent (consignment issue)
EDKO - External agent correction
RZ - Scheduling agreement returns (no external agents)
KAZU - Consignment pick-up for external agents
KRZU - Consignment returns for external agents
Item Categories
To configure item categories for scheduling agreements, choose Sales -> Sales Documents -> Sales Document Item -> Define item categories in Customizing for Sales and Distribution.
The system determines the following item categories for the related document types in
documents containing materials with item category group NORM:
Item category LZN for scheduling agreement type LZ
Item category LZMA for scheduling agreement type LZM
Item category LKN for scheduling agreement type LK
Item category KEN for document type ED
Item category EDK for positive corrections (or the manual alternative EDK1 for
negative corrections) for document type EDKO
Item category REN for document type RZ
Item category KAN for document type KAZU
Item category KRN for document type KRZU
Schedule Line Categories
To configure schedule line categories for scheduling agreements, choose Sales -> Sales Documents -> Schedule lines -> Define or Assign schedule line categories in Customizing for Sales and Distribution.
The R/3 System contains the following schedule line categories for component suppliers:
L1, BN, L2, and CN for item category LZN
E4, E0, E5, and BN for item category LKN
L2 for item category LZMA (standard for delivery order processing)
Schedule Line Types
To configure schedule line types for scheduling agreements, choose Sales -> Sales Documents -> Scheduling Agreements with Delivery Schedules -> Define schedule line types in Customizing for Sales and Distribution.
Creating Scheduling Agreements
To create a scheduling agreement with delivery schedules:
1. In the Sales menu http://Ext. choose Scheduling agreement ->Create.
2. Enter scheduling agreement type LK (standard) or LZ (external agents) and the
relevantorganizational data.
3. Choose ENTER.
4. Enter the following data:
Sold-to or ship-to party number
Purchase order or closing number
Material or customer material number
You can use the Description field to identify the scheduling agreement. For
example,
you could enter the model year for a particular production series.
The system allows up to 35 digits for a customer material number.
Rounding quantity
Usage
Choose Goto -> Header -> Sales to enter the usage at header level, or Goto ->
Item-> Sales A to enter it at item level. The system proposes usage S, for series, as default in both cases.
Planning indicator
Choose Goto -> Header ->Sales.
Target quantity
Mark an item and choose Goto -> Item -> Sales A
Partners
For scheduling agreements with external agents , choose Goto -> Header
->Partners to enter the external agent as forwarding agent and special stock partner
on the partner function screen.
5. Create a delivery schedule
Mark an item in the scheduling agreement and choose Goto -> Item -> <Delivery
schedule>. Enter:
A delivery schedule number and date
The cumulative quantity received by the customer
The last delivery confirmed by the customer
A schedule line with date, time, and quantity
To enter additional data in the delivery schedule, choose DlvSch.Hdr (delivery schedule header).
configuration:
img->SD->Sales->sales document->scheduling agreements with delivery schedules->
step1: define schedule line types
schedule line types are not schedule line categories. Schedule line types are used for information purpose only.
stds are 1. fixed date 2. backlog 3. immediate requirement
4. estimate
step2: maintain planning delivery sched. instruct/splitting rules
The planning delivery schedule is an internal delivery schedule used to plan requirement s more efficiently. It is sub divided into 3 parts
2.1 delivery schedule splitting rules
2.2 dly schedule instrusctions
2.3 assign dly schedule splitting rules
step3: define sales documents type
step4 : define item categories
step5: define schedule line categories
step6: maintain copy control
PROCESS
step1: create scheduling agreement
VA31
enter SP,SH valid from, valid to,
goto ITEM OVERVIEW tab
enter material, rouding qty
select ITEM click on FORECAST DLSCH
enter different dly dates and qties
save it.
step2: create sales order with reference to above
step3: create delivery
step4: create billing
regards
krishna

Correction delivery in the scheduling agreement.

Coundnt able to create the correction delivery in the scheduling agreements.
Where can i see
Thanks in advance for your assistance.......
Message was edited by:
 tiru

To create a correction delivery (document type LFKO):
Choose Corr. delivery on the delivery schedule tabstrip.
The system displays a dialog box in which you enter a:
 --> Correction delivery date
 For help on deciding where you want to position the correction delivery, choose Display. The system lists delivery dates in chronological order.
 --> Correction quantity
 Enter a negative correction quantity by placing a minus sign after the quantity.
Choose Enter and save the scheduling agreement.
Result
When you save the correction delivery, the system updates the cumulative quantities in the delivery schedule.
To display correction deliveries, choose Deliveries on the delivery schedule tabstrip, or Environment --> Display document flow.
Thanks
G. Lakshmipathi

How to measure performance of supplier when using scheduling agreement ?

Hello all,
My client has an absolute need to be able to measure the performance of its suppliers based on delivery dates and delivered quantities. That is to say he needs to be able to compare what dates and quantities were asked to what has been really delivered.
Most of the procurement processes used are based on scheduling agreements : schedule lines are generated by MRP and forecast is sent to supplier while firm requirements are sent through JIT calls.
It seems that when doing GR in MIGO, it is done against the outline agreement number, and not against the call. Therefore, we have no way to compare dates and quantity with what was expected (in the JIT call).
Do you know if SAP proposes a standard solution to this, and what could be a solution to this issue ?
Thanks for your help
E. Vallez

Hi,
My client faced the same problem and we ended up developing an own analysis in LIS. Since the GR is not linked to specific schedule line (SAP does some kind of apportioning, but it doesn't have to correlate to the correct match), one needs to do assumptions. Our assumption was the closest schedule line, i.e. each GR is related to the schedule line with the closest date. Then all GR the same day are totaled together before the quantity reliability is calculated, since the very same shipment can be reported through several GR transactions in SAP (one per pallet).
If anybody has info about what SAP has to offer in this question (or is developing), please tell us!
BR
Raf

Closing of scheduling agreement with open quantity

In our scenario
When ever we receive the sales order,
we will convert it into scheduling agreement (VA31),
then converting them into planned orders through (MD02) & (MD16),
these are converted to PRu2019s and the procurement process continues and the material is taken into production through quality and after the processing of these materials to end products(FG).
These are taken into finished goods and we will create sales order (VA01) with reference to the scheduling agreement.
And with reference to the VA01 we make out bound delivery (VL01N) and
with reference to sch. Agreement we make billing document VF01 and create excise invoice for factory sale and send the goods to the customer
Now the problem is
When we receive sale order of 30,000 units and we will make sch. Agreement for 30,000 units.
But after planning, procurement and production we receive the FG of 29,500 only(as per yield 98%) into UR in stores.
Now we will supply the FG to customer through billing.
And now we will go to MD04 and check for the requirements the sale order sch. Agreement is still open and when we want to close that sch. Agreement to remove it from the requirements.
But the system is not allowing us to delete the sch. Agreement and giving a message no.V1748, which you cannot mark, deletion flag of xxxxx sch. Agreement.
We can only close it when we go back to initial sale order and change the quantity to 29,500 and coming back to sch agreement and changing the quantity to 29,500 and then only it is allowing us to mark delete.
Initially it is allowed but now it not allowing me to close without the reverse setting.
Kindly help me in this issue
mln raju

hi
In Scheduling Agreemnt you can maintain the Reason for rejection for closing the SA maintain it item level also by mentioning the reason for rejection and the quantities will not reflect in MD04
regards

Cumulative Quantities in Scheduling Agreement

Similar Messages

Maybe you are looking for