Rebate Condition Records Redetermination

Dear All,
When we Copy the Service Rendered Date in Billing Document into Billing Date using User Exit then Rebate Condition Records are not getting determined. If I go to the Analysis then i can see that the rebate Condition Record Exists but it does not gets set. In the analysis this is the message which shows for the Condition Record.
"Condition record exists, but has not been set"
Any Pointers as to which User Exit can be used to Redetermine the Rebate Condition Records.
Regards,
Madhukar

Hi,
Did you try to use transaction VBOF to rebill those invoices to set the rebate conditions.
Regards,
Rajesh Kumar

Similar Messages

ERROR Message while creating Rebate condition record T code VBO1

Dear Experts,
I am getting error message while creating rebate condition record T code-VBO1-Error Msg-862 system cannot read the structure for table,because of this i could not create condition record.
Please give the solution to create condition record.
Regards
siva

Hi,
You said you are trying to do this stuff in IDES right.
If you are using IDES provided by a company and where many people play on IDES, then you can get many such issues...
This is by our experience. Today you do something in IDES and tommorow that thing or config is screwed up by others.
If you have your own IDES, then check the suggestion given by the forum Guru's.
Regards,
SB

Rebate condition record T code VBO1-Error Message

Hi,
I am getting error message while creating rebate condition record T code-VBO1-Error Msg-862 system cannot read the structure for table,because of this i could not create condition record.
(This error has occured while i am testing rebate process in IDES and it happen while creating condition record for rebate agrement,After filling the initial values in T code VBO1 and when click on enter the above mentioned error message has come).
Please give the solution to create condition record.
Thanks in Advance
Regards
Praveen P C

Hi,
You said you are trying to do this stuff in IDES right.
If you are using IDES provided by a company and where many people play on IDES, then you can get many such issues...
This is by our experience. Today you do something in IDES and tommorow that thing or config is screwed up by others.
If you have your own IDES, then check the suggestion given by the forum Guru's.
Regards,
SB

Table Name for Rebates Condition Records in Rebate Agreements

Hello All,
I want to know the table name which stores the condition records for Rebate Condition Types?
fast responses are appreciated.
Regards,
Rags.

Hi,
Try KONA table.
KONM KONW
Regards,
Chandra

T-Code for Rebate Condition Record

Hi,
Can someone help me with this. I need to create a condition record for Rebate Condition type. Please give me the T-Code to create the Condition Record for Rebate condition type. Cause I am unable to create this thru VK11.
Thanks,
Sumit

Hi
First search in the forum regarding rebate agreements. The same as been answered so many times in the forum.
For this you need to create a rebate agreement for the customers
Goto T code VBO1
enter the rebate agreement type as per your requirement BO01 or BO03
there in the screen enter the rebate recepient now from the menu press "CONDITIONS" tab
there you can enter the condition records
regards

Rebate agreements / Rebate condition type

Hi Experts,
Can anyone tell me how to process Rebate agreements/Rebate condition types in pricing procedure.Please help me by giving step to step description for rebate condition type and where to maintain condition records and how they function.
Thanks in advance experts,
Kanna Palle.

Hi ,
find some notes on rebates.
in the billing document, the rebates are calculated as per the the accrual rates in rebates condition records. My question if the invoice is for Rs 100 and accrual rebate amt in invoice is rs 2. will the customer pay Rs 98 against this invoice of full Rs 100.
Ans --> Customer need to pay Rs 100 only , rebate amount will paied to the customer after completion of the rebate duration in between there will be partial settlement.
2) what happens during manual accruals. why a credit memo request is generated during manual accruals. what happens to accruals as per condition records.
Ans--> Manual Accruals
Use
Posting accruals manually can be useful in different situations such as:
Lump sum payments
Accruals correction
You can control at which time and for which amount the accruals should be posted.
You can build accruals for a particular condition record or reverse them in part or in full.
When you save the rebate agreement, the system will automatically create a credit memo request. The system uses this document to create a credit memo. When the credit memo is released, the accruals are posted to FI.
If you have posted accruals manually, but these have not been passed on to financial accounting, the manual accruals and manual payments in the rebate agreement are blocked.
3) what happens during partial settlement. do the accruals already poested gets reduced to the extent of amount of partial settlement. do manaul accruals have any role to play during partial settlement
Ans->Partial Settlement
Use
You can also partially settle a rebate agreement during its validity period. The amount to be paid can be limited in Customizing for Sales. Payments can be:
limited to the cumulative accruals of the condition record
limited to the amount that would be paid if final settlement were presently carried out
unlimited
You carry out partial settlement by using the manual payment screen within rebate agreement processing. On this screen you can specify the amount to be paid for each condition record.
The system will automatically create a credit memo request for the amounts specified.
It will also reverse the accruals with the credit memo if the rebate agreement type is configured accordingly. If the payment exceeds the recordu2019s accumulated accruals, the system will only reverse the accruals which are actually there.
The system gives you the opportunity to carry out additional partial settlements when previous partial settlements remain open in the form of credit memo requests or credit memos. The system always takes open documents into account when determining the maximum amount which you can pay.
When the system carries out final settlement for a rebate agreement, it takes all partial payments into account.
4) what happens during final settlement. do manual accruals have any role to play during final settlement i.e. do they get reversed and what happens to accurals posted as per rebate condition records.
Ans-->Final settlement
Use
When you carry out final settlement of a rebate agreement, the system automatically
calculates the rebate based on the sales volume statistics or the lump sum
deducts any previously paid rebates
It then creates a credit memo request, and proposes the end date of the agreement validity period as the billing date.
The system also reverses any accruals that have been posted.
Depending on Customizing, when the system creates a credit memo request, the document is automatically blocked for billing. After approving the credit memo request, the person responsible can remove the billing block. You can then create the final credit memo.
When you want to search for credit memo requests during sales order processing, you can use the match code F "Credit memo request for rebate".
You can carry out final settlement of rebate agreements
automatically
Manually
as a background task (in batch)
Settling Single Rebate Agreements
You can carry out settlement directly from within a rebate agreement.
Before you save the rebate agreement you can still carry out changes to the credit memo request:
The credit memo request is only saved when you save the rebate agreement.
Carrying out Final Settlement as a Background Task
If the volume of your sales rebate processing is high, you can collectively process rebate settlements as a background task.
The following reports are available:
RV15C001
RV15C002
Your system administrator can use these reports to generate a list of rebate agreements, based on various selection criteria, such as rebate recipient, status of the agreement, and so on.
Background processing can then be carried out later. I.e., after the regular posting periods.
After a list is generated, the rebate agreements can be analyzed or processed for payment.
For more information about settling rebates as a background task, see your system administrator.
Best regards,
venkataswamy.y

Manual rebate condition exclusion not refreshed after redetermination of it

Hi Experts.
I am working with CRM 4.0.
Lately, we realized there is an error occurring in the price deternination:
The condition exclusion for manual rebate condition is not refreshed after redetermination of the product. There is missing a price validation before saving the document with the new product.
Step-to-step description of the error:
1)     I am creating an order in trx. CIC0 or CRMD_BUS2000115 and determine the product (sector A).
2)     Now I assign a manual rebate (condition Z...) of 20 % on item level.
3)     On header level I replace the product to one of another sector (B).
4)     I check the pricing conditions of the new product on item level. The same rebate of 20 % is maintained.
This is an error, because the condition exclusion for products of sector B allows rebates only until 5 %.
Can anybody help me, please.
Best regards,
Cristina

This is not standard due to information of SAP OSS.

Table for Rebate Condition Types( Condition Records)

Hello All,
I need the table and the FM name which stores the values of the Key Combination of the Rebate Condition Type maintained in a Rebate Agreement.
If not, at least, give me the name of the FM which stores the values of the key combination maintained in condition records for pricing.
Regards,
Raghu.

I'll give an example,what am looking for..:
I've a Condition Type: ZBAX for ex. it has a key combination: Sales OrgCustomerMaterial.
I maintain condition records as:
For CU70/21100043/3456 the value of the condition record is say 100 euro.
My question is where will I get the values CU70/21100043/3456 ?
FYI..in T685 the defintion of the Condition Type is stored. in SAP, no T-table is meant to store condition record values.
KONA contains data on Rebate Agreements i.e. RA no, Rebate Recepient etc..
I know that KONP stores the accrual %, scale base, scale values etc..
but, I want to know where are the values for the key stored? Or, the FM that would fetch me these details?
I hope am clear..
Regards,
Raghu.

Condition record exist but not set in SO

Hi SDN Team,
I have a problem. Where in the sales order for the Discount condition type condition record where already exist in diffferent validity period.
EG
ZAJ1 discount condition type - with the same key combination with different valididity period
EG:
ZAJ1 - 27.01.2009 to 15.02.2009
ZAJ1 - 16-02-2009 to 15-03-2009
The reason is not set for the ZAJ1 condition in the Sales Order is due to the sales order was created before the pricing condition record validity datet. Sales order where created on 11.02.2009. But the condition record where valid from 16.02.2009 that is the reason the condition record was not set in the sales order.
Based on this explanation user agreed and the call was closed.
I have also explained Where ZAJ1 has condition record. but which is not set in the document. if pricing was carried out again it will set the condition for the item.
But now again the call was reopened stating that -
At the time of creating the sales order the ZAJ1Condition record exist in the period 27-01-2009 to 15-02-2009. now the primary rebate should be used by the system. Unfortunately it did not.
Based on the reopend call - i have further investigated the issue but i could not find the root cause.
Based on this when i checked the previous order where the ZAJ1 condition was well picked up with the validity period 27-01-2009 to 15-02-2009, what might be the reason the condition type was not picked up in the sales order?
Can you please let me know with your expertise in solving this issue.
Regards,
J

1)Requirement is set with 2 (itme with pricing). and calculation type is assigned with own calculation type.
2) In the pricing analysis - it shows as per below
This message tells you that the condition record exists, but has not been set in the document. If pricing was carried out again for the document item, then the condition would be set.
There are different reasons for this:
The condition was deleted manually in the item condition screen.
The condition record was created later. Please note that order processing and pricing have buffer mechanisms. This means that a newly added condition record might only be found after order processing has been left completely and then started again.
If the condition type is used for subsequent settlement (rebate), there may be subsequent updating of business volume (the agreement is is created retrospectively). The document conditions do not contain the condition record, as the condition record was not created when pricing was carried out. Updating of business volume is carried out using special functions for subsequent settlement.
When an item was added, the condition record was accessed with key fields other than change time. This could lead to different results in the requirements check at the time of adding and the change time. This can occur when modifications are made.
In billing (or when copying orders): Certain condition types were not determined in the source document (this is usually controlled by the pricing requirements). When creating the document, the document flow (TVCPF,TVCPA) is processed using a pricing type that does not redetermine these condition types, although they are supposed to be called via the requirements.
Thanks,
J

Accruals Condition Record posted late in COPA along with the Settlement

Hi Gurus,
Accruals condition record for 1 item in an Invoice is posted along with the Settlement Credit Note in COPA. While condition records of the other items from the same invoice were posted on the Billing Date itself.
For eg:
Invoice 111       Date 01.03.2011
Items     Condition   value
1              Z1            100
2              Z1             200
3              Z1             300
COPA Doc No.        Value Field        Date
     001                         200             01.03.2011
     002                         300             01.03.2011
     003                         100             30.05.2011
30.05.2011 is the date of Rebate Credit Note for the Invoice # 111
I also got that if Posting of Accrual is not done for an Item, Retroactive rebate settlement automatically posts a new document for accrual.
So the question is why the posting of accrual was not done on the Invoice date in the first place?
Edited by: Parth Kulkarni on Jul 1, 2011 4:31 PM

Hi Suraj,
i too have the same problem, the condition types for Values and quantity in COPA are assigned. The system updates the quantity for the first billing document but not for the subsequent billing documents.
Cost of goods sold and revenue gets updated.
Regards,
Prateek

Rebate Conditions issue (Pricing incorrect Order Viz Billing)

Hi Forum,
We have an issue with the rebate conditions.
User has created a credit memo request (VA01) due to change in the Price. Due to this change rebate accruals have got reduced. The rebate accruals should not be reduced in this case, since there is no material return.
There is a specific order reason while creating such credit memo requests Eg. ZXX.
As a solution to this we have created a new routine AAA and assigned to the rebate condition types in Pricing procedure.
This routine will function when there is a order reason ZXX entered in the Credit memo request (in VA01), therefore all the rebate condition types (assigned with routine AAA) will get deactivated in Conditions. This not change any accruals value. This is working correctly.
The issue is -
When the credit memo (VF01) is created, these condition types are again activated and accruals are posted.
This should not happen. Pricing from the CM request (VA01) should get copied in Credit memo (VF01) completely.
When we open the Credit memo we find all the conditions are activated and accruals posted.
Is there any one who has faced the similar issue in billing documents where pricing data is not getting copied from Order conditions.
Please help.
Thx / Sheetal

Hi Sheetal,
Suggest to make a seperate CR memo order type for cases wherein you don,t want reduction of rebate accruals.
You would have to redetermine a new pricing procedure (create one keeping all condition type as are in Billing procedure except rebate) and assgin the determination of new PP basis the sales areacustomer PPOrder PP.
Pls go through the below link.
Re: New pricing procedure in credit note created w.r.t. billing document.
Regrds
Sanjay

Condition records not copied from order to invoice

Hi,
I created an order and it has contion types for Frieght cost and packing cost...for both condition rocrds were found and triggered in order but whn cheked in invoice...records are not copied to invocie level..and when checked in analysis it says "access not made" for both the conditions...
Fields combination for these are shipping point and material frieght group for both condition types...
i checked the validity dates for both conditions and are still in validity dats.
Can anyone advice me is there some thing else i need to check and why condition records are not copied to invoice.
Thanks in advance
Balu

Hi Sumanth,
Copy controls are fine...it is actually delivery related billing scenarios..and in delivery to billing copy contrls in header in determine export dat feild it is set to "B :Redetermine the export data" and at tiem level the pricing type is set to "C:Copy manual pricing elements and redetermine the others"
Kindly let me know if the settings are fine or the problem is woth these settings
Regards
Balaji

Debit memo Condition record exists (removed manually) MWBO Italy

Currently I am working on an Italian pricing issue.
Pricing V/08
Cond     Description            Fr. To. P Req. Calc. BasT.
LCIT     VAT license Italy      900     S 33   37
MWST     Output Tax                     S 10         904
BOLL     Bollo in Fattura       900     S       903   26
MWBO     Opt.tax Bollo in Fat   924     S 924 903   26
The requirments, calculation type and are all based on SAP notes regarding the LCIT, BOLL. eg. 715399 and 593672
The main requirement here is that 924 is only to activate the MWBO condition in the invoice.
This means that for a normal order (TAN) item the LCIT, MWST and BOLL is shown. If we create a delivery - invoice, the pricing in the invoice shows LCIT, MWST, BOLL and MWBO. This is correct. MWBO is a tax condition.
But if we create a debit memo request the behavior is different and would appreciate some insight.
Debit memo request created, LCIT, MWST and BOLL is shown (as expected). MWBO not shown due to requirement, that's correct.
But when I create a debit memo from this one, the LCIT, MWST, BOLL are shown. If I go into the pricing analysis then I see that the condition record for MWBO has been found but with message: Condition record exists (removed manually). Saving the document does not trigger it afterwards.
I have looked on OSS (example note 859876) to determine the cause of not triggering it.
We are not using the user exits for these conditons in example: user_exit_pricing_prepare_tkomp, user_exit_pricing_prepare_tkomk, mv45afzz or rv60afzz.
The standard copy control of L2N to the invoice is set to D. If I change this for example to G (copy unchanged, redetermine taxes), then it works. But not sure if this causes disturbtion of the regular behavior of the L2N.
In best case I would only do the G pricing type for the MWBO condition so I do not disturb the existing process. Any suggestions? I know there is RV61AFZA for manipulating the pricing type (in case you want to have user defined pricing type eg. Y). But this can not be handled per condition type, or is that possible?

Routine 924 is a altered routine provided by SAP to suppress the condition in the order - not in the invoice.
http://service.sap.com/sap/support/notes/715399
quote:
"In this case, the bollo should only be reported on billing documents, not on the
order. However, pricing condition '24' delivered in the standard system
only partially covers this requirement."
The issue here is that it is triggered with normal order - delivery - invoice. But not with credit memo, it gives message that condition is removed manually. The L2N item category is set to D (copy pricing elements unchanged). When changing it to G (copy pricing elements unchanged - redetermine taxes), it works. But that has an effect on all standard usage of the L2N and I only want to actually fix it for that condition type.

Update SO after creating missing condition record

Hi Gurus,
I was getting error message that missing MWST condition in Order, then I investigated and created missing condition record in VK11. Now I would like to update the Sales order and tried update tab on condition but invain.
Initially the document was created on 17.11.2008 and today condition record was created 18.11.2008.
Kindly help me in resolving this.
Thanks
Bawa

Dear Bawa,
While creating Condition Record "MWST" in VK11/ 12;
What were the Dates maintained in Fields:
1. Valid From (try with back-date maintenance)
2. Valid To (Maintain as 31.12.9999)
Once done, try to Update with "G - Copy pricing elements unchanged and redetermine taxes", in Sales Order.
Best Regards,
Amit

Rebate condition type

Dear Experts,
I have created a condition type for material rebate and the same has been assigned to condition type grp in turn condition type grp is assigned to rebatye agreement type....besides the same(cond type) is included in the pricing procedure.....the issue is even after maintaining the cond record the values are not flowing moreover when I see to the condition type details in the order level( I
deliberately made the rebate cond type to flow in sales order) few settings got changed like scale type,calculation type,..etc...how come the settings may change other than what I have maintained...I could see my own settings exist in V/06 for the rebate cond type.....what would be the reason?.....thanks in advance.......

Hi,
1st see in condition detial,maintain
Processing priority - Automatic entry has priorit or No limitation
Second,in price procedure V/08, if you maintained any requirement in requirement coloumn in front of rebate condition then remove that.
Kapil

Rebate Condition Records Redetermination

Similar Messages

Maybe you are looking for