Multiple Validity Dates in Contract Pricing Agreements

Hi
We are using Quantity contracts in ECC 5.0. Now business wants to maintain multiple validity dates in price agreement of contract.
When we try to create the agreement with multiple validity dates, i am getting following message:
The condition is being processed in the current session.
Message no. VK104
Diagnosis
A condition record with the same variable key is already being processed.
System response
The new record is not included in processing.
Procedure
Carry out the changes to the record that is currently being processed.
In this case we are unable to maintain multiple validity dates for same combination (Sales Document & Line Item).
Is this standard scenario? If no, how to address this issue.
Please awaiting your valuable feedback.
Regards,
Shankar

Question answered by SAP.
1. Use VK11/12 to maintain the multiple validity dates.
2. If 2 Logical systems are used, then need to use separate condition types for CRM & ECC.
3. Ensure new condition types are blocked from replicating to CRM.
Now, we are able to maintain separate condition for ECC & CRM and working satisfactorily.
Thanks
Shankar

Similar Messages

Rebates Conditions with Multiple Validity Dates

We have a customer that has a 1 year rebate agreement but the rate changes quarterly. Any suggestions on how to change the rate quarterly. Everything I have tried ties the Validity Period on the Condition directly to the Validity Perion on the Agreement.
Thank You
Pam

Hi pam,
Extended Rebate Processing
Use
The SAP Beverage Extended Rebate Processing component is an enhancement of the standard SAP R/3 rebate processing.
You can use Extended Rebate Processing to process business transactions that are typical for and occur frequently in the beverage industry. This includes indirect sales, which are a frequent practice in the beverage industry.
Indirect sales are sales activities in which the rebate-relevant sales do not take place directly between the rebate granter and the rebate recipient. In the terms of the SAP R/3 System, this means the system does not use customer billing documents to update sales.
In the SAP Beverage Extended Rebate Processing component, you can model and settle the rebate for each specific article. The system allocates the defined rebate levels to the individual articles and provides a wide range of analyses in SAP CO-PA.
The standard SAP R/3 System only supports a single rebate recipient for each agreement. The SAP Beverage Extended Rebate Processing component has been enhanced to support multiple rebate recipients in a rebate agreement. This applies especially to customer hierarchies.
The SAP Beverage Extended Rebate Processing component enables you to settle rebate agreements periodically. Individual periods are settled like individual agreements in this case.
Implementation Considerations
The SAP Beverage Pendulum List component is an enhancement to Extended Rebate Processing. The pendulum list enables you to process indirect sales. The SAP Beverage Pendulum List component provides tools for automatic data import. For more information, refer to the SAP Beverage Pendulum List component.
This documentation describes the special features of the extended rebate, compared to the standard SAP R/3 rebate. For more information, please refer to the standard SAP R/3 component Rebate Processing.
Integration
Extended Rebate Settlement is integrated in SAP Profitability Analysis (CO-PA). SAP Profitability Analysis supports the article-specific update of the so-called "customer rebate", for example. The system provides detailed information directly after settlement.
Features
A variable key in the rebate information structure provides more flexibility during rebate settlement.
When the rebate information structure is updated, certain data from the billing documents can be added to the variable key. The system copies this data to the billing document when it generates the credit memo. This enables you, for example, to add the articles that resulted in the rebate to the credit memo, instead of the material for settlement. The partners from the billing documents can also be copied, which makes it possible to allocate multiple rebate recipients to a single condition.
Periodic settlement of rebate agreements.
Instead being limited to periodical partial settlements that always consider the entire validity period of an agreement, you can now also perform partial settlements that only take individual periods for settlement into account. As a result, individual periods are settled like individual agreements. This applies especially to the use of scales and fixed amounts.
Processing of indirect rebate agreements.
The use of pro forma billing documents makes indirect data available for rebate processing. You can use special pricing procedures and condition formulas to use plan data for forming accruals and actual data for rebate settlement.
Credit memo requests unnecessary.
The system generates billing documents (credit memos) immediately during settlement.
Constraints
The SAP Beverage Extended Rebate Processing component is a new function in SAP Beverage. The SAP Beverage Extended Rebate Processing component replaces the following SAP Beverage rebate versions:
Rebates: Enhancement Beverages u2013 (SAP Beverage BEV02).
Rebates: Enhancement Beverages (old) u2013 (up to SAP R/3 4.5B and SAP Beverage BEV01).
The earlier rebate versions are only relevant for migration customers, and will not be described in detail below. We recommend using the SAP Beverage Extended Rebate Processing component exclusively.
To avoid inconsistencies in your datasets, you must never configure settings/values in the following SAP Easy Access folders at the same time:
Extended Rebate Processing
Rebates: Enhancement Beverages
Rebates: Enhancement Beverages (old)
Also make sure that you use either the SAP Beverage Extended Rebate Processing or the standard SAP R/3 Rebate Processing component.
thanks
karthik
To use the SAP Beverage Extended Rebate Processing component, you have to activate the new standard SAP R/3 rebate processing

Copy contract pricing from sales contracts in billing

Hi
I Have a requirement to Copy contract pricing agreements from sales contracts during resource related billing creation.
At the time of resource related billing is performed, the agreed contract rate should be taken into account when pricing is performed in SAP. So, the agreed price needs to be copied from the contract condition record into the resource related billing transaction (sales pricing) as a condition record.
Can i get the solution for this?
If anybody knows the solution please help me out. Appropriate Points will be awarded. Thanks in advance.
Regards
Ravi

You just need to configure your pricing properly.
Suppose you have condition type with document/item keys in the condition table.
Now, if you define conditions for contract/item, to pick them up in the invoice - you just need to pass contract number/item number in the fields you use in your access sequence for this particular condition type.
You can either define new step in the access sequence passign different fields (assuming konh or konp have fields for contract number) OR use ueserexit_pricing_prepare_tkomk, userexit_pricing_prepare_tkomp to populate fields in TKOMK/TKOMP you then use in your access sequence to search for pricing condiiton record.

Mass change of pricing date in contract VA41

Mass change of pricing date in contract VA41
In VK11 - we have updated a new pricing date.
In contract the same needs to be updated. Can this be done through VA45 -( List of contracts) Edit - Mass change - new price - which price type should i give to change the pricing date. Where should i mention the new pricing date?
or is there any other way to get the latest pricing date from vk11 to contract va42.
Thanks,
Mahe

Hi,
As i understood from your question, You have changed the Validity periods in your VK11 records.
Since your contract Line Item Pricing date is already set (Line Item Sales A tab), you will not be able to pick the relevant pricing by UPDATE PRICE option in condition tab. (Because price is picked based on the pricing date in the line item)
Try this method;
Use transaction MASS, to update all Pricing Dates in contract line items to a particular date within new validity period.
Once you update your pricing date in the contract line item, system will automatically carry's the new pricing, resulting new pricing in the line item.
Hope this is useful to you !
Best regards,
Anupa

How to add Pricing Agreement in Value Contract Item level

Hi Exports,
In my requirement i need to Add Product category ID at item level in a Sales Contract. we done with this through CRM_ORDER_MAINTAIN
we are able to add this
For This Item we need to add Pricing Agreement as Below ( Added at in UI level but we need this through CRM_ORDER_MAINTAIN ) we tried through PRICE_AGREEMENTS_CRM and PRIDOC but its not working. We observers Pricing Agreement details In CRM_ORDER_READ at
PRICE_AGREEMENTS_CRM and PRIDOC. we debug the Transaction but didn't find any clue. Can any once please help me to how to Proceed.
Can we add only pricing through BOL, because we are creating sales order and item through CRM_ORDER_MAINTAIN and ORDER_SAVE, We don't want disturb this.
Thanks,
Sateesh U

What are you exactly asking for, I don't understand your question...
Transaction screen, adding a tab / customer fields
Business Object / BAPI, modifying BAPI signature, extension
NB : The quality of an answer depends significantly on the quality of the question ...
Regards,
Raymond

Trans ME31K:Defaulting item condition validity to contract validity date

Hello Experts,
I have a request from my client which is as follows :
On transaction ME31K (Create Contract), at header I can enter a start date and an end date for the validity of my contract.
Program name : SAPMM06E
FIELD-NAMES : EKKO-KDATB & EKKO-KDATE
The users want the same date range to appear at item level for the conditions :
Select a new created Item > Conditions.
Program name :SAPMV13A
FIELD NAMES : RV13A-DATAB & RV13A-DATBI
Because, the transaction is changing the program name, it is very difficult for us to replicate the dates at the item's condition level.
Can you please suggest any idea to implement this solution ?
Thanks & Regards,
Mahesh
Edited by: Maheshsingh Sharma Jhoomuck on Oct 5, 2009 4:52 PM
Edited by: Maheshsingh Sharma Jhoomuck on Oct 5, 2009 4:53 PM

Hi raghavendra sai !
Thanks for the answer.
But actually, my client wants 'from date' of the items conditions to be defaulted to the date that he indicated on the contract's validity date at header (from date - EKKO-KDATB).
A contract can be created with a validity interval that starts from a past date.

MDM contract validity date

Hello,
We are using MDM catalog to host all contracts from suppliers. I would like to set validity date on the Catalog (Standard field in the CATALOG table). I also want that catalogs that are not valid anymore would not be displayed to my SRM users.
Has anyone has experience with setting some kind of view, according to the contract validity date?
Thanks in advance
Limor

Hi,
One of customer has implemented item delete program using MDM API and scheduled it every night.
Please go to http://help.sap.com for MDM API.
Regards,
Masa

Pricing Procedure determination for Quotation,Contract,Scheduling Agreement

Hello All,
Plz let me know,how the pricing procedure(Both Item & Header Level) can be determined for Quotation,Contract,Scheduling Agreement.
Do let me know with configuration details.
Thanks
JP

Hi Jyoti ,
There isn't any separate pricing procedure for Quotaions , Contracts , Scheduling Agreement s..
The pricing which u normally find in PO derived from Vendor Master ( Based on Vendor Schema ) , hold good for the above purchasing documents.
Regards
Ramesh Ch

Contract validity date mandatory

Dear all,
Pls suggest me that how can we do contract validity date mandatoty ? One option is incompletion procedure but except that any other process to do validity date mandatory in contract.
Thanks in advance.
Regards
Rahul

Hi Rahul,
Please note you can also make it mandatory by using SHD0 "Transaction Variant".
Try this and confirm.
Regards,
Rahul Verulkar

Info Record Validity Dates - Future Period

Hi Gurus
can you help
we have current Purchase Info Recs in place, with pricing condition records that have a validity date that will expire in the next few days
we have already loaded the next pricing for the next cotnract period with the vendor, but wish to check the accuracy of the data before that pricing condition becomes "current"
do you know how can we pull the data from the future validity period pricing condition record, so we can validiate this
i have only found ways to get the current pricing conditions, but not the one for the future period
please advise
many thanks

hi Velu
we maintain Pricing Condition Type PB00 in ME13
when i key a Pur Ord for the part, then go to Conditions tab in ME21n, then select the Analysis of the Pricing Condition, it bring up Procedure RM0000
then Gross Price PB00, then various steps under this
a number of steps not executed due to requirements not filled etc, being Contracts, outline agreements, Plant Infor Rec Order Unit, then Material Info Rec (Plant Specific) A017, then Material Info Rec table A018 with various field names
For Access Sequence step Mat Info Rec (Plant Specific) it does say No condition record was found for this condition using the document data.
any thoughts
If we cannot resolve i shall leave it for now, and review on the day it becomes current
many thanks

Rebate conditions with mulitple validity dates

Hello,
I have an urgent requirement. My customer wants to define different rebate rate by date in one agreement like normal pricing condition types.
for an example,
The validity date of the agreement is
1/1/2008 ~ 3/31/2008
Rebate conditons are as follows,
Material A $2 per 1unit, 1/1/08 ~2/28/08
Material A $3 per 1unit, 3/1/08 ~ 3/31/08
I would appreciate with your help. I will give you high point!

Hi,
Thanks for your answer.
When I tried to create a new condition record with different validity date, the system gave me a message "VK 104, the condition is being processed in current session". and then removed the record from the screen. It's because of the same condition key exists.
I think it's related to the difference on condition tables. When I checked a condition table for PR00, the attribute was "with validity period" but a rebate condition table had none in attribute.
Do you have any idea?

Controling Dates in contracts

Hi,
In general sap Mm contracts, the delivery date of release order based on contract should be withinh the validity period of contract.
Can we chanae this control to PO date, i.e. the PO date should lie within the validity period of the contract.
Prashant

Hi,
Contract is a agreement between vendor and purchaser for procurement of material with a validity period and valid price.
Your contract release order should be in between contract validity period. Delivery date can be beyond the contract validity period.
reg
Durga
*Assign points

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 Kor slaes orderC
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 of PO/Contract/Scheduling agreement with ref to PR using IDOC

Hi Experts,
Is it possible to create PO/Contract/Scheduling agreement with reference to PR using inbound IDOC ?
If yes, please let me know the segment type and field to be populated for referencing PR in the IDoc .
Thanks in Advance,
Best Regards,
Mitesh Desai

Hi Aarif,
Thanks for taking time to reply .
We are palnning to integrate SAP and non SAP systems.
The business Process is as under .
(1) PR will be generated in ERP (Manaul/MRP)
(2) PR will be coverted into RFQ (for which there is no appropriate source of supply
in ERP)
(3) Sourcing will be done in non SAP system. RFQ will be created with dummy vednro (for example say "source") to identify RFQs to be sent to another system.
These RFQs needs to be sent using IDOC alonwith reference PR numbers and line item numbers.
Multiple PRs will be combined into one RFQ as multiple line items.
(4) Non SAP system will do sourcing and generates either PO or master outline agreement and have reference PR/RFQ numbers and line item numbers.
No SAP system will send PO/outline agreement information to SAP system in XML file format to generate inbound IDOC in SAP .
(5) This inbound idoc will generate PO/outline agreement in SAP.
From SAP functionality point of view, I ca createPO/outline agreement with reference to PR but My Question is how I can generate PO/outline agreement in SAP through IDOC and using "Reference PR or RFQ numbers".
Looking forward to help ASAP.
Regards,
Mitesh Desai

SRM7 grouping items in RFx despite of multiple delivery date and locations

Hi Gurus,
I need to know for a proposal of SRM 7 implementation, WITHOUT the newest E-sourcing component, how to solve the following scenario:
We are gonna use the SRM7 classic scenario where PO is created in ERP and Shopping cart is created in SRM.
In Plan-Driven Scenario for Third Party Sales Order, TPO will be created in ERP, Shopping carts, RFx and contract in SRM, PO will be triggered in SRM and created in ERP.
1.       We have 8 main customers (Sold-To Party), 50 Items, 40 Ship-To (locations) 4 delivery dates for each item to each location.
2.       Under Each Sold-To Party, there are several Ship-To party (Locations)
3.       For each location, there could be multiple delivery dates.
4.       In the Third Party Sales order (TPO), each material could be repeated several times because of the multiple delivery dates and multiple locations;
5.       After saving TPO, the system automatically generates Purchase Requisition (PR) in background.
6.       For each delivery date in TPO, the system creates a separate line in PR. These lines will be converted into line items in shopping carts in SRM.
7.        Total # of lines in PR would be:
a.       8 (main customer) X 50 (items) X 40 (locations) X 4 (delivery dates) = 64000 lines in PRs è same number of lines will be created in SRM in Shopping carts (SC)
8.       In sourcing, we have the option to convert these SCu2019s into RFx. This means we will send 64000 lines for the vendors to give their quotes while we actually have only 50 items.
My questions:
1.       In standard SRM, is there a way to create RFx for the total quantities for item? i.e. can the system read all SCu2019s and sum all the qty for each item, regardless, of the locations, customers, delivery dates and create one line item in the RFx. i.e RFx should be send for 50 items only?   If so, which functionality or work-around should I proposed to meet the req.?
Regards
Thanks
Livio

Hi Ramki,
According what you say I assume that this specific requirements in SRM7, without E- sourcing , CANNOT be executed in a standard way, it makes sense to me. Can you firmly confirm it?
My real worry is that, eventually, in this last version of SRM7 could be already covered, somehowu2026 that why my post.
Can you give me some more details when defining the u201CAggregator txnu201D please (u mean txn or txt? And why)?
I mean, If I understand good, must be a development which finally summarize the quantities for each material and create the SC/PR and related RFx.
The PO, created from the RFx, will collect all the delivery date and location from a custom table. The custom table is a pointer between TPO, delivery date, location and RFx. Am I correct?
Thanks
Livio

Multiple Validity Dates in Contract Pricing Agreements

Similar Messages

Maybe you are looking for