Rebate Condition Type cannot be reflected in sales order?

Hi Guru:
It seemed to be a issue? I set up the rebate agreement and ran the vbof successfully regarding this condition type rebate,and the retroactive billing also can view its rebate condition type as well as the accruals,and I believe the rebate settlement had been run too,credit memo to customer will be aslo routed to accounting side for sure,but I failed to see the rebate condition type and accrual value in the sales order based upon the retroactive all billings,please advise what I should do,thanks.

Hi Klaas,
If I remember well, in the standard price determination there is a conditional formula that only shows rebate conditions in the invoice, therefore you should not see rebate conditions in the sales order.
That is standard functionality.
For a Customer I took out the formula condition in the pricing so he could actually see the rebate condition in the sales order, the reason was to had access to this information before end of month invoicing. The problem is that in case of changes in rebate agreement or in case of retrospective agreements the rebate condition is only updated in the invoice, not in the sales order.
Best Regards,
Franck

Similar Messages

Condition type is not reflecting in sales orders

hi,
i have created two condition type like jser (service tax) and other one is jste(service tax +cess) but in pricing procedure jfact it is reflecting but while making contract order these two condition type is not accessing.
please help in this connection.

Hi,
After Creating the CONDITION TYPES you need to assign the condition types in the PRICING PROCEDURE
goto the
SPRO->FINANCIALACCOUNTING>FINANCIAL ACCONTING& GLOBAL SETTINGS>TAX ON SALES /PURCHASE>BASIC SETTINGS--->CHECK CALCULATION PROCEDURE.
Here select you procedure and assign the CONDITION TYPE
regards,
santosh

Report of condition types per line item in sales order

Hi all,
Is there any report that can tell me all the price conditions that are allocated to a sales order line item? I am talking about the actual conditions relevant for a line item, not only conditions that have a condition record setup.
So I would like to key in sales order number, the line item and get a report of all conditions that are allocated to that line item in the specific sales order.
If there is no such standard report, does anyone know what tables to link?
Thanks in advance,
Lars

Hi Lars,
In my current customer they had the same requirement and after almost 1 month of analysis we decided to build a custom report to execute this.
And as an enhancement we compare prices from the sales orders and the sap price records in order to check the differences.
First we need to find all the open lines (status and reason for rejection (ABGRU)), than loop KONV and select the KSCHL (condition types) you want, material text descriptions, etc.....of course a lot more in terms of coding.....;-)
This was the form I used :
FORM FIND_SO_PRICES.
LOOP AT IT_ITEM_REPORT.
    REFRESH IT_PRICING.
    SELECT KSCHL KBETR WAERS KPEIN KMEIN KUMZA KUMNE
      INTO IT_PRICING
      FROM KONV
     WHERE KNUMV = IT_ITEM_REPORT-KNUMV
       AND KPOSN = IT_ITEM_REPORT-POSNR
       AND KINAK <> 'M'
       AND KINAK <> 'X'.
      APPEND IT_PRICING.
    ENDSELECT.
    READ TABLE IT_PRICING WITH KEY KSCHL = 'XXXX'. -> My price condition
    IF SY-SUBRC = 0.
      IT_ITEM_REPORT-ZSP1 = IT_PRICING-KBETR.
      MODIFY IT_ITEM_REPORT.
    ENDIF.
    READ TABLE IT_PRICING WITH KEY KSCHL = 'XXXX'. -> My discount condition
    IF SY-SUBRC = 0.
      IT_ITEM_REPORT-ZSD1 = IT_PRICING-KBETR / -10.
      MODIFY IT_ITEM_REPORT.
    ENDIF.
   IT_ITEM_REPORT-LIQ = IT_ITEM_REPORT-ZSP1 - ( IT_ITEM_REPORT-ZSP1 * (
                                          IT_ITEM_REPORT-ZSD1 / 100 ) ).
    MODIFY IT_ITEM_REPORT.
ENDLOOP.
ENDFORM.                    " FIND_SO_PRICES
Please tell me if this helped you,
Regards,
Alcides Fialho

Header condition type value not displayed in sales order output

Hi gurus,
I have observed a strange issue regarding a header condition in a sales order.
we have a set up like following:
1. If the Header condition XXXX is used in sales Order then this value should be printed on sales order output.
2. If the Header condition mentioned in above point is not maintained in sales order it should print the total price of all line items.
Though i have maintained the header condition value in Sales Order Header its not displayed in SO output.
That is , I have a sales order and it has one HEADER condition type entered with 3500 USD.
In fact this value is used for some business purpose and is being printed on the sales order output for a specific output type.
But where as in a sales order this header condition value is not getting printed on the output though I am using same data as of the sales order which is having the header condition value printed on its output.
According to business,we must have the header condition value printed on sales Order output.
Please suggest how to proceed.
Thanks in advance.

Not sure if you are using costom smartform to print invoice, if yes then ask developer to debug and find the root cause and fix it.
You might need to give him condition when it shuld be printed and when not.
You can take reference of another output type for which it is printing

Condition type in Billing not in Sales Order

Dear Friends,
I have the following scenario in our project. Please clarify.
We have a condition type. That should be appeared only in Billing, it should not appear in Sales Order.
Please answer ASAP.
Regards,
Rajesh L

Hello,
To fullfil you requirement go to V/08 select your pricing procedure and relevant condtion type. Then select requirement column and assign the Routing 24 click save.
regards
rc gopi

Manual Condition Type should be visible in Sales order by default

Hi
How to maintain manual condition types in Sales orders by default. They will be maintaining the value based on the discussion they had with the customer(Negotiated price). The condition type should be visible in the procedure and they will only enter the value.(The method of keying condition type manually is not accepted by the client).
Thanks in advance.
Regards
Vamsi Javaji.

Hi,
In the PRICING PROCEDURE V/08 maintain the CONDITION TYPE as Mandatory
In the CONDITION TYPE V/06 maintain the field MANUAL ENTRIES as C which is Manual entry has a priority.
And check the box VALUE
Now maintain the condition records for the condition type in VK11 with 0 value
Now while processing the sales order the CONDITION TYPE will trigger from the CONDITION RECORDS with 0 value and this can be in EDITABLE mode ( and maintain the value)because of the check box VALUE you flagged in V/06.
Please try this and revert back if you need further details
thanks,
santosh

Enter condition type several times in a sales order

Hello Gurus,
I have a Pricing Procedures with net price minus some discounts and sales price. This is standard. One of the discount condition types you can enter manually in a sales order. Now my problem. This discount condition type you can enter several times in a sales order. How I can solve this for one time enter.
Regards
Artur

Yes, it is a standard behaviour only, you can only control with User exit only. Include MV45AFZZ , co ordinate with your ABAPer for the same.
Regards,
Ramesh

Condition type value not update in sales order

Hello Guru's
As per the sales order in VA01 the condition type value i.e surcharge value is not updating in sales order.
But I have maintain the condition record(Surcharge)also and in Condition technique I have checked every thing is correct .
please find below I have attached the Screen short .
Please give me solution Asap.

Hi Sukdev,
Have you checked the respective pricing procedure for From and To reference step maintained against the condition type ZSUR?
Regards,
T.R.S.Praveen

Condition type JEXP not picking in sales order

hi
i was working with all configuration of TAXINN
i am facing with a problem
when i am running mine sales order i am not able to see condition type JEXP(BED) , JEAP (AED)
can i now where i am gng wrong
whereas i can see all the other condition in sales order
but when i enter it manually JEXP it is taking but in again in billing it is not showing
can u plz help me
Regards
Vini

Dear Vini,
Please Check the configuration settings through IMG path
SPRO>IMG>Logistics general-->Tax on Goods movements >India>Basic settings-->Determination of Excise Duty -->Maintain Excise defaults here you check JEXP condition type is maintaining for A/R BED or not if not maintain then try.
Also check the condition record maintanance for the JEXP condition type through VK12 transaction.
I hope this will help you,
Regards,
Murali.
Edited by: Murali Mohan.Tallapaneni on Oct 1, 2008 6:51 AM

Use condition type 'RC00' to process return sales order

first, I copy RC00 to RC10 and change its Calculat.type = B(Fixed amount).
second, I place a sales order to deliver 10 PC(RC10 = 10 USD) to customer and bill 8PC(RC10 = 8 USD) to customer.
third, I place a return sales order(only return 2 PC) reference to above billing but the RC10's amount is still 8 USD instead of 2 USD.
I think this is relative to Cond.base value and Cond.control = F(Condition value fixed (billed)) and who can tell me how to realize my purpose?
tks in advance.

Hi
Guess, If you do returns again for two more pieces, again it will determine the same value for RC10.
Please look into the areas of 'copy controls - price type' field and also the Calculation type (fixed amount) also.
Thanks,
Ravi

How to set a condition type to inactive/statistical during sales order crea

Hi
There is a manual header condition (Z0L1) in one our pricing procedure which I want to set to inactive or make it statistical during sales order (doc type Z9) creation in some scenarios.
How can I achieve?
Can I use user exit USEREXIT_PRICING_CHECK (Program MV61AFZA) and what code should I write here. Any help would be highly appreciated
Regards,
Javed

Thanks for your replies. Basically this condition type is a manual condition type which will be entered in sales order and then will be available in billing document. But when there is a return order created with reference to that billing document then I want that the manual condition is not deteremined in the return order.
I tried by assigning a requirement to the condition type in pricing procedure but seems to be pricing requirement don't work for manual header conditions. Then I tried to assign a condition value formula and tried to set the value to zero in case of return orders but that also did not work.
Then I also tried to apply the same logic in user exit USEREXIT_PRICING_CHECK in the following programs
LV69AFZZ
MV61AFZA
But still it did not work. Any help would be highly appreciated
Regards
Javed

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.

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

Multiple rebate condition types in one invoice

I had defined multiple rebate condition types as Y000, Y001 and Y002, which are montly offtake rebate, distance rebate and yearly offtake rebate.
Y000 and Y001 can be in the same validity period and also will be applicable to the same invoicee.
When i create a rebate agreement for customer for Y000 and go for the settlement of the rebate it is happening fine.
But for the same customer, i had defined Y001 as a rebate agreement type for the same period and materilal.
The sales volume is not updated in the rebate agreement. Evenif I do VBOF the sales volume is not updated.
the error that comes while doing VBOF is :
"7000158055 Document number RCFL 7000158055 2011 was already assigned
7000158053 Document number RCFL 7000158053 2011 was already assigned
7000158052 Document number RCFL 7000158052 2011 was already assigned
7000158054 Document number RCFL 7000158054 2011 was already assigned"
Please help me to solve this problem.
Mrs. Swati Pawar

Hello Swati,
the suggestion of JP is correct.
I explain it better.
- the document type of FI document created from SD depends on the customizing of billing type field TVFK-BLART. If it is blank, then by default is 'RV'.
- if the number range assigned to the account document type is External, then the FI document gets the same number of the SD invoice.
- transaction VBOF creates FI document referred to SD invoice. If it has external number range, and an FI document already exist with same number (created when SD invoice has been released to accounting), then the errof F5152 occurs.
SOLUTION:
in the selection screen of VBOF there is the field FI-Doc-type. Here you should specify the FI document type that should be created by execution of VBOF, and of course it must have number range internal.
Please try this.
Best regards,
Ivano.

Rebate Condition Type--Statistical in nature, but does it post to G/L ?

Hello All,
I've a Rebate Condition type, which is anyway statistical and relevant for accruals too.
So, once I've the rebate condition types are part of the Pricing Procedure and if I create an invoice... does it post anything to any G/L account?
Regards,
Raghu.

Dear Customer,
if a condition is statistical, then the condition have no influence to FI.
These conditions are not trasfered to FI.
These condtions are only relevant for CO or statistics.
I hope that the information is helpful.
regards
Claudia

Rebate Condition Type cannot be reflected in sales order?

Similar Messages

Maybe you are looking for