Create Scales specific to a contract

[Former Member]

Hi All,

I have a scenario in which scales need to be maintained for each contract separately. E.g.:

Contract: 1

Customer: X1

Material: M1

Validity: 01.04.2013 to 30.04.2013

Qty From	Qty To	Price
1	100	30
101	500	29
501	5,000	28
5,001	100,000	26

Now, with same customer I may have other contract with same validity dates but with different scales:

Contract: 2

Customer: X1

Material: M1

Validity: 01.04.2013 to 30.04.2013

Qty From	Qty To	Price
1	1000	30
1,001	5,000	29
5,001	50,000	28
50,001	1,000,000	26

There is no limit on scaling levels. It may seems illogical having two contracts with same validity period, but actually that's the scenario (also business critical) which is being followed.

Here scales are not fixed. They may change with every sales contract. Is it possible to maintain scales in contract itself for that item?

Also, these contracts are not quantity or value based. Customer can order as much quantity as required. So no target quantity or target value logic applies here.

Please suggest.

Thanks & Regards,

Vishal

[former_member518143]

Hello,

For my point of view this is how your concern can be sorted out:

- Create as many access sequences (for a single condition type) as contract types you wish to set up for this business. Then as the contract type is the criteria that makes the price scales to be different you'll then need to use the document type (field VBAK-AUART) in the condition table for the price condition type.

You'll make the accesses exclusives indeed for response time reasons.

Then when calling the item from one of your contracts the system will retrieve the right scale thanks to the document type which is passed to the pricing procedure via the condition technique.

Finally, as value and qty do not have relevancy on your business scenario you could deactivate quantity positive or negative effects when subsequent document occurs (like sales order) in copying control for sales documents. Condition records with corresponding scales will then be maintained for both (or more) access sequences.

Hope this will help, do not hesitate to  Text Removed

Regards.

Message was edited by: G Lakshmipathi

Please dont ask for points which is not allowed here. 

[jpfriends079]

Hello Vishal,

You might agree that contract would be created based final agreement between seller & buyer. Where, seller Finance team would approve the same before that is created on SAP. Therefore, obviously, you would be aware of scales, each time you are creating a sales contract.

Now, you can have key combination(condition table/access) which would have contract number as field. Say, contract number/customer/material

Hope that would assist you.

Thanks, JP

Note: Sales Doc No(in your case its contract no.) is not field that is available in Standard field catalog for pricing.

[former_member518143]

Hello Vishal,

As Jyothi said using document number as a field for the access is possible. If this field is not in the field catalog you can  add it. Check the menu "System modification" in the SD application section of the SPRO IMG.

You need to add this field to the related communication structure, the fill it in with data (VBAK-VBELN = KOMK-BELNR). First check if you cannot add it into the dictionary without user exits.

Regards.