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 <u>in total</u> we get a better price for every part <u>over</u> 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...

Similar Messages

Scales in Scheduling agreement MM - ME31L

Hi,
I tested the scales with a condition in the scheduling agreement and the system always take the target quantity in the scheduling agreement to define the amount to use in the scale.
Did anyone already had a requirement to configure the scales based on the schedule line received and not on the entire scheduling target qty ?
Thanks !
José

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

Scales in Scheduling agreement.

Hi,
This query i am posting again, as there is a need from my client for this regularly.
I need your expertise for meeting out this functionality.
Hi,
Pl findherwith the following sceario.
I had created a Scheduling agreement for 5000 units with the following quanity discounts
1000 - Rs. 10
2000 - Rs. 08
5000 - Rs. 05
The quantity discount is maintained through Scales.
After that i had maintained delivery schedules like this Say
1 st day 1000 units
2 nd day 1000 units
3 rd day 2000 units.
My requirement is , when i am trying to do MIRO for the first line item,
I should get the value as 1000 units * Rs. 10 = Rs.10000
For 2 nd line item
Value = Rs. 1000 units * Rs. 08 = Rs. 8000
( since the quantity of line item had exceeded 1000 units and sum of line item 1 & 2 is equal to 2000 for which the rate is Rs. 08)
So i should be able to post the invoice at Rs. 8000 instead of Rs. 10000.
Pl suggest with your valuable solutions.
Regards,
R. Dillibabu.

Pl try this with an ABAPer.
In Condition Types configuration, maintain a condition type by copying the discount condition type. In this new condition, Activate 'Group Condition' indicator. Maintain Group condition routine as required (Need to code with your logic).
Note: I have never tried this. But, I know that SD consultants use such conditions frequently.

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!

BAPI for Scheduling Agreement Scales

Hello,
I want to add Scales to my Scheduling Agreement.
Tried using BAPI_SAG_CREATE, I was able to successfully create a Scheduling Agreement but it says that "No scales exist". According to the FM documentation, scales are not supported during the creation of outline agreements.
Tried using BAPI_SAG_CHANGE using the Scheduling Agreement created but I always get a dump and points me to a standard code.
Runtime Errors         GETWA_NOT_ASSIGNED
ABAP Program         SAPLMEOUT
Include                      LMEOUTP14
Row                          1,454
Module type              (METHOD)
Module Name           POST
If these BAPI will not work, my last option would be BDC.
Thanks in advance.

first see the documentations.
Regards
Peram

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

Scales definition in Scheduling agreement

Hi,
In a scheduling agreement, you can maintain condition with scales.
When you do so, at goods receipt time, the system does not look at how many you just received to define the scale to use but look at the target quantity on your scheduling agreement item and choose the scale appropriate for that qty.
Does anyone already had a requirement to calculate the quantity received since the beginning of the scheduling agreement and define the appropriate scale according to that ?
Thanks in advance.

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

Scale maintained in info records but not picking up in scheduling agreement

Hi,
We have maintained scales for PB00 in info record (subcontracting), this scale is picked up in Subcontracting Purchase Order.
But when we are trying to create Subcontracting scheduling agreement, this scale is not picked up by the system.
Why the system is picking up scales for PO but not for scheduling agrmment?
Regards,

Hey there,
Please check your InfoUpdate Indicator on the scheduling agreement.
The indicator determines which prices and conditions are suggested in future PO items.
Prices and conditions can apply to an entire purchasing organization or to a single plant within a purchasing organization.
For example, if you create a purchase order for a plant for which an info record has been defined at plant level, the purchase order is based on the conditions in the plant info record and not on the conditions that apply to the purchasing organization.
probably your info record is at the Porg level and not at the plant level and hence it's not picking it up.
Hope this helps,
Cheers,
Dhaval

Scheduling Agreement with Scale

Dear Friends,
Pl advise how to go for scale price in GR for Scheduling agreements:
GR Qty from 1 is rs.15/-
GR Qty from 1000 is rs.12/-
GR Qty 2000 is rs.10/-
How to go about it. What will be the configuration settings. What will be the accounting entries in GR and IV.
Pl let me advise the full procedure.
Note: I already refereed SAP NOTE- 401941,But it was 2003 version.So is their any standard settings are available in ECC6 to address this above issue ??
Regards
AKS

Hi,
Note is also valid for 600 release. see note in details
Valid releases
Software Component                        Release
                                          from            to
SAP_APPL
     SAP Application
                                          600          - 600
                                          500          - 500
                                          470          - 470
                                          46C          - 46C
                                          46B          - 46B
                                          45B          - 45B
                                          40B          - 40B
In standard, scale prices have been defined for a scheduling agreement
item. When a goods receipt is posted, the scale price applicable to
the target quantity of the scheduling agreement item is applied for
valuation purposes.
For schedule agreements the SAP standard is to use the target quantity
for price determination.
User exit EXIT_SAPLEINR_003 exists using which you can influence the
quantity and the date of the price determination at the time of the
goods receipt for the scheduling agreement. However, you need to bear in
mind that when you call up the user exit, the quantity of goods received
actually to be posted does not yet exist. The schedule lines are
available in internal table CETT which can be used.
In the standard system, the EXIT_SAPLEINR_003 is run when a goods
receipt is posted for the scheduling agreement or purchase order when
item has the pricing date (price category) = "5" (goods receipt date).
For scheduling agreement document type, pricing category is always 5 if
time dependent conditions are used for that document type.
BR
Nadia Orlandi

Schedule Agreement scale price is maintained, Pulling wrong price in GR

Hi Experts,
When good receipts of different quantities are entered, they all pick up the lowest price/highest volume regardless of the quantity.
Case 1: Delivery schedule for 2 different quantity with same delivery date like eg. qty 5 & 6 and del. date 03/03/2011
Case 2: Delivery schedule for 2 different quantity with different delivery date like eg. qty 6 & 7 and del date is 03/03/2011 & 03/04/2011
In case 1 when doing GR first for qty 5 it is not pulling the correct price from the scale quantity 5 of scheduling agreement.
In case 2 when doing GR for qty 6 it is pulling the lowest price not pulling the price from scale quantity 6
Scale:    qty   Price                   please suggest me a solution for this issue
                 1    $20/pc
                 2    $18/pc
                 3    $15/pc
                 4    $12/pc
                 5    $10/pc
                 6    $8/pc
                 7    $7/pc
                 8    $6/pc                    Thank you in advance for your help                                                       Ismail
Edited by: iismsyed on Mar 9, 2011 3:50 PM Is anybody their to help me out in this issue or who face this issue before.

Hi Marco Antonio,
For schedule agreements the SAP standard is to use the target quantity for price determination.
User exit EXIT_SAPLEINR_003 exists using which you can influence the quantity and the date of the price determination at the time of the goods receipt for the scheduling agreement. However, you need to bear in mind that when you call up the user exit, the quantity of goods received actually to be posted does not yet exist. The schedule lines are available in internal table CETT which can be used.
Hope this can help
Regards,
Mauro

Wrong Schedule Agreement Scale price in GR posting

Hi!!
We have defined the scale price as follow:
Scale type         Scale Qty      Unit         Amount   Curr     Unit    UoM
From                           1           PC          199.96     USD     100    PC
                                300                         190.50
The problem we have is that when the GR was posted by Qty 100... the proce taken was 190.50
why is taking the range of >= 300 qty ?? and not the <=299 of 199.96?

Hi Marco Antonio,
For schedule agreements the SAP standard is to use the target quantity for price determination.
User exit EXIT_SAPLEINR_003 exists using which you can influence the quantity and the date of the price determination at the time of the goods receipt for the scheduling agreement. However, you need to bear in mind that when you call up the user exit, the quantity of goods received actually to be posted does not yet exist. The schedule lines are available in internal table CETT which can be used.
Hope this can help
Regards,
Mauro

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

Scheduling agreement in MRP

I have created a scheduling agreement for a material for 50000. There are dependent requirements on this material which creates scheduling lines. When the cumulative quantity of scheduling lines is greater than 50000 I want MRP to create purchase requisitions instead of scheduling lines based on dependent requirements. Is this possible thru configuration. Currently it creates scheduling lines even after the cumulative quantity is greater than the scheduling agreement quantity of 50000.
thanks a lot

Hi,
I think that you can achieve this by using Quota Arrangement definition.
Regards,
Mario

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

Approval process (Release strategy of scheduling agreement)

Hi,
Recently we are trying to implement the approval process of scheduling agreements.
Client requirement is when ever there is a change in price irrespective of the following
1. Retrospective price change in any line item
2. Current price change in any line item
3. Future price updation in SA in any line item
4. New addition of line item
the system should trigger the release process (i.e. Approval process).
Our idea is to design the approval process based on document type and net value of SA. Based on which trigger should happened. But when we test it we find the following issues.
1. Trigger is not happening for future date price change or price for new period as the net value of SA is based on validity time.
Becuase the net value change will happen only on that onwards..
Also we are not using any cumulative pallned values in agreements.
Any can suggest the best solution to over come this..or Any user exit is avaliable to handle this issue.
regards,
K.Sundaresan.

Below are the (changed) item fields :
Purchasing Document Item Change Date AEDAT
Item Delivery Date EINDT
Schedule Line is "Fixed "FIXKZ
Below are the (changed) header fields :
Release Indicator: Purchasing Document FRGKE
Release status FRGZU
Purchasing document processing state PROCSTAT
Item and header changes have same "Change document number " and transaction code "ME38" , this happened only in some cases,Rel Strategy is on document type level ,I am also confused on this .
Please assist on this

Cumulative Scales in Scheduling Agreements

Similar Messages

Maybe you are looking for