Rebate calculation

Hi,
I need a report which shows the additional purchase in value or weight and percentage, that is required in order to meet the basis value of the purchasing rebate. Pls let me know.
Also I would like to know the standard rebate reports that are available for purchase rebates.
Thank you.

Hi,
I need a report, in which we should be able to see the additional purchases that are required to meet the basis value to beco me eligible/receive rebates.
Thanks.

Similar Messages

Rebate calculation from Basic Price PR00

Hi,
This query is related to rebate conditions. At present the rebate base is calculated from the subtotal, that is Basic price - discount(The subtotal 7 is assigend to the step 300).
As per the requirement from the business, the rebate should be calculated from the 'Basic Price'. They don't want the discount value should be considered in the rebate calculation. I explained them regarding the burden which company has to bear, but the business still want to go with the changes.
My plan is to create another step in the pricicng procedure right after the basic price and assign subtotal 7 to it and delete the exting reabte subtotal step, and assign the new step number to rebate conditions, so the reabte will be calculated based on this.
My questions are:-
1. Can I edit the existing pricing procedure to make these changes?
2) Will there be any impact on the existing rebate agreements (open) and its settlements on a later date?
3) Will there be any impact on the process of billing of open sales orders/deliveries (not billed) after the change in pricing procedure?
Please guide me.
Regards,
SAM

Hi Ivano,
Thnak you very much for your suggestion.
As the note says, the best way is to copy the existing pricing procedure and create another and assign it in OVKK.
Will there be any effect for partially billed delivery items? (at the time of creation of billing document for the unbilled items in the delivery)
OR
when we create a billing document from the delivery (in the case of sales order and delivery created with old pricing procedure and the billing document is getting created after the assignment of new pricing procedure)
Your valuable suggestions will be highly appreciated.
Regards,
SAM

FICA Rebate calculation and posting

Dear All,
When a bill is raised, the respective rebate amount is calculated and respective discount percentage(SKTPZ) field is updated.
So, when a payment is taken against the consumer the respective rebate is calculated and accordingly the amount is taken considering the amount without rebate amount before the due date.
But, we have configuration of FIFO method and clearing will be done based on due date. But if a consumer pay the partially before the due date, he is ant able to get the rebate(which he should defintely get).
I am just wondering if there will be anywhere the calcualtion is made which we can check at the time of amount posting.
Thanks,
Jay

Hi Jay,
Check event 0020 which enables additional action to be initiated where a document is posted in Contract Accounts Receivable, and open items are cleared at the same time (either fully or in part)
Thanks,
Amlan

Complex Rebate calculation

Hi All
I have tough task ahead and i need your help.I have to create a rebate which is used during sales from consigment .It is supposed to work in such a way it takes the amount in the current sales order and minuses it from the amount of material still at consigment(1000 at consigment - 200 at sales order) .The differenece (800) is the base for calculation.We take 800* current price * 2%.The outcome is subtracted from the sales amout (200).The same thing should happen with normal sales but the rebate should not take into account the amount previously sold on the reference document and the discount is on the credit memo request .Does anyone have any good tips how to get started with this ?please:)

Hi Grinch,
Glad to hear that your issue had been solved by yourself. Thank you for your sharing which will help other forum members who have the similar issue.
Regards,
Charlie Liao
TechNet Community Support

Suuser exit - rebates

hi
one scenario : About rebates with free goods :
If cust purchase 10 printers in 3 months, i want to give 500/- rebate on each printer and i want to give 2 small printers to him after 3 months along with the credit note.
How to solve this.
regards
lakki

Hi Lakki,
There is no simple user exit solution for this. You need to go for some custom development for the same.
1. First you need to create a Free Goods master record in VBN1 in such a way that Min Qty 1 Max Qty 10 Free Goods 2.
2. Create a Z table for the accumulation of invoiced goods. This will get updated when invoice will be created for the customer for that sales order/delivery. Coulmns can be as follows.
- SalesOg., Sold-To/Ship-To, Material, FreeGoodsCondType, Qty Invoiced, Date Invoiced.
User Exit for Invoice is RV60AFZZ in this USEREXIT_NUMBER_RANGE.
You have to put additional logic here to check if any Free Goods are ther in this invoice. If yes then delete all the entries from 3 months till Today.
3. Create a rebate calculation routine in VOFM (Formulas -> Calc. Rule RebateKind. e.g. 901). Attache this routine in Free Goods Master Record.
Put a logic as follows.
Read Z-table for 3 months till today. Get count of Qty Invoiced. Move this Qty. Invoiced to l_frm-mglme.
l_frm-nrmenge = ( l_frm-mglme / l_frm-knrnm ).
l_frm-nrmenge = FLOOR( l_frm-nrmenge ) * l_frm-knrzm.
business rounding
nachkomma = FRAC( l_frm-nrmenge ) * 10.
IF nachkomma < maxrund.
    vorkomma = FLOOR( l_frm-nrmenge ).
ELSE.
    vorkomma = CEIL( l_frm-nrmenge ).
ENDIF.
l_frm-nrrund = l_frm-nrmenge - vorkomma.
l_frm-nrmenge = vorkomma.
   l_frm-nrmenge is the calculated Free Goods.
I have just consider simple scenario, but while testing you will come up with new scenarios.
Thanks,
Mandar

Rebate Issue: Qty Based Cond Type

Hi All,
I need to know only functional way (cant use update in pricing routine due to issues in business approvals) to tackle following Rebate requirement.
Background of issue:
User has created credit memo because the logistic discount was not correctly invoiced.
However in this case the Rebate Accrual got reduced
Reason:
System must have thought that total amount of cases was returned physically and thatu2019s why rebate accruals are reduced).
This is not correct because the Materials are not returned. The materials are still with the customer. Hence the rebate accruals should not be reduced in this case. The credit note is only written because of price differences and not because of returns.
Example: to understand the issue better:
Suppose we have Invoice with 100 CV and an invoice value of 100 u20AC.
Rebate 1.) Shows an amount of 100 u20AC * 4% = 4 u20AC accruals
Rebate 2.) Shows an amount of 100 CV * 0,20 u20AC = 20 u20AC
Now we came to know that the 100 u20AC net invoice was wrong because of a wrong on-invoice discount. Hence the invoice should not be 100 u20AC, but 80 u20AC. However the 100 CV still remain (NO CHANGE IN QTY).
The credit note should affect the rebates in the following way:
Rebate 1.) Should show after the credit note: 80 u20AC * 4% = 3,20 e accruals
Rebate 2.) Remains 20 u20AC accruals (100 CV * 0,20 u20AC)
Requirement:
We want that whenever credit notes are issued which that just price related (e.g. wrong logistic discount) and which do not have a material movement, the Qty-related rebate conditions should not be affected in that invoice.
This requirement must have been used/tackled in all projects where rebate functionally is used.
If anybody has still some confusion in understanding the requirement please let me know so that I can discuss it over the phone.
With Regards,
Tushar Gawande

Hello,
actually the rebate basis can be updated for the quantity scale and/or value scale based on the document category assigned to the sales document type in customizing.
I mean that except if you configured differently, actually are used the standard program for rebate calculation and settlement. Using the standard, a key field is the document category of the document type in customizing (table TVAK field VBTYP).
For the below list of standard document category:
A Inquiry
B Quotation
C Order
D Item proposal
E Scheduling agreement
F Scheduling agreement with external service
G Contract
H Returns
I Order w/o charge
K Credit memo request
L Debit memo request
W Independent reqts plan
0 Master contract
For example, document type with document category C or H update both: quantity and value rebate basis; document type with document category K or L update only value rebate basis.
If I understand properly, in your case when the user adjust the price via credit note, once posted to accounting, the reflect in the R.A. was in both direction: update of both quantity and value.
Personal feeling is that the document type used to adjust the price was not correct and that this document type (as per customizing) is configured to reduce both: quantity and value.
Did you check the customizing of the document type used to adjust the wrong discount?
Which category did you find?
Regards,

Rebate clarification

Hi all
I need some clarification on Reabte.Kindly help me.I just want to know wheather the rebate will be considered for Free goods also?that is whether the volume of the goods supplied as free of cost also considered for rebate calculation?As per my understanding that should not be considered but still i need clarification on this.Kindly help me.

Hi,
Please follow the below link that help u ::
http://help.sap.com/saphelp_46c/helpdata/en/5d/363eb7583f11d2a5b70060087d1f3b/content.htm
http://www.erpgenie.com/publications/saptips/052005.pdf
REgards,
Krishna O

Difference between "Rebate Recipient" and "Customer" in Rebate Setting

While setting "Rebate Agreement" (TCode VBO1), for "Customer Rebate" (0003) Agreement Type, there is one "Rebate Recipient" and then when we go on to create the conditions, there is "Customer" for different rate etc.
My question- What is difference between the "Rebate Recipient" & the "Customer" (the one we enter while entering the conditions)?
Is it like "Payer" & "Sold to Party" partner function in Sales Order Processing eg for different "Sold to Party" there could be one "Payer", similarly for Rebate, for these different "Sold to Party", which would be like "Customer" in Rebate setting and the "Payer" in Sales Order will be like "Rebate Recipient" in Rebate Setting.?
Thx

Dear SR
Rebate Recipient is the payer
As you know ,in rebate configuration , the payer's master record is to be activated which is first major setting in rebates
Customer is sold to party
As you know ,the rebate process starts from sales order (your sales order pricing procedure will have rebate condition types but they are reflected in billing) and in a sales document the pricing conditions is taken from sold to party and the pricing condition records are taken from sold to party
If in case payer and sold to party are different
That means the input is taken from sold to party that is Customer (rebate calculations in pricing procedure ) and the out put is passed on to the payer that is Rebate Recipient (passing on rebate claim as credit notes)
That is two different identities which the system needs to know
Hence SAP has defined so
Even if the payer and sold to paty are same even then we need to give the same no(customer no ) in both the places
Regards
Raja

Adding rebate condition to invoice

Hi all,
I have a requirement to add a rebate to invoices exceeding a purticular limit.
I have added the rebate condition to the list of pricing conditions using the exit USEREXIT_PRICING_PREPARE_TKOMP.
The rebate calculation is working fine but the problem that i am facing is that, when i take the pricing conditions in VF01 it will show the rebate condition that i attached and the associated rebate percentage; but the rebate will not be applied to the net amount. Only when i press enter or press activate button the rebate gets calculated and applied to the net amount.
My requirement is such that the rebate should get applied during the invoice generation itself without the user having to do anything.
Can anyone help me in solving this problem.
Regards,
Roshan

Hi Mahulenka,
Thanks for your reply.
I am not sure whether it can be done that way. Here the rebate percentage alters with customer. For each customer there will be a certain minimum amount limit for applying the rebate. Once the invoice amount exceeds this limit the rebate percentage for that customer is to be applied.
Rebate percenteges along with the minimum amount limit will be stored in an Ztable. Since the rebate percentage alters with the customer, I don't think it can be done by configuring the pricing procedure.
In the userexit I am querying the Ztable to find the limit amount and rebate percentage. I am also trying to calculate the rebate amount and move it to KBETR field of the XKOMV structure; but that amount is not getting displayed in VF01.
I'm sorry that i didn't explain the scenario completly in my first post. I hope that i have now made it clear now.
Thanks & Regards
Roshan

How to exclude particular IPC from Rebates

Dear SDN Team,
Customer want to create some rebate in order to pay later on a promotional basis for the particular IPC.
But they want to apply accruals on all IPC but by excluding particular IPC from Rebates, How to exclude the particular IPC from Rebates.
Because customer want to exclude one IPC of the rebates calculation for only one rebates -
Any Idea.
For the above request i have suggested below solution - But it does not resolve their problems. But User is expecting further any other idea in order to resolve the above requirement.
First Solution:
In order to exclude the IPC for Ecopia from the rebates calculation- this can be done by setting the Material group in the Material Master - Basic Data1 view and you can exclude these IPC's while creating the condition records in the Rebate Agreement type. By doing this we can exclude the rebates for the Ecopia tyres.
Second alternative: If you have already created the Rebate condition record for the Ecopia tyres then you can set the deletion indicator flag in the rebate condition for the particular IPC.
Can you suggest any ideas in order to resolve this problem.
Looking for your feedback.
Thanks and Regards,
Jana

Dear,
even if was not clear about the type of material you were reffering to, I analysed your request and I consider that you may proceed as follow.
To achieve this result you do NOT have to modify the material master.
Assumptions taken:
A- you have to exclude only one material from the rebate calculation for only one rebate
B- all other rebates do not have to be impacted by this exceptional rebate configuration
C- material nr1 is the material to exclude
D- material nr1 has a product hierarchy 00X (Line X)
Procedure to achieve the objective:
1) create a promotional rebate (RebateA) for the full Line X and set it relevant for accrual (define a percentage for accrual)
2) create a promotional rebate (RebateB) for the single material nr1 and set it NOT relevant for accrual (no percentage for accrual)
3) set the same percentage to pay or amount to pay to the customer in both rebates (A & B)
4) set the same validity start-to for both rebates (A & B)
5) define a percentage of accrual only for the first rebate (A only)
The second rebate created (RebateB) will help in order to pay the right amount to the final customer.
In order to perform a final settlement you will have IDEALLY simply subtract the values: RebateA - RebateB.
There is no standard way to exclude single material from a single rebate without impacting the other active rebates.
Of course, modify the material master is not the solution. Any change in material master will impact also open rebates and future rebates.
For these reasons here above there is a business scenario you may apply to achieve the objective and it will not take a lot of time to maintain it.
In case of questions or doubts to not hesitate to post your answer back to this post.
Regards,

Error 70 - Código do status 225: Rejeição: Falha no Schema XML da Nfe.

Bom dia grupo!
Nós estamos atualmente recebendo a seguinte mensagem de erro da SEFAZ relacionado aos batches que nós enviamos: Error status 70 "Error from the authorities" and Código do status (Status Code) 225: Rejeição: Falha no Schema XML da Nfe.
Nossa configuração é 46C com muitos OSS notes aplicados (veja abaixo)
Nós estamos realmente parados neste momento e não temos nem ideia de onde começar.
Atenciosamente,
Marc de Ruijter
OSS notes for NF-e phase 2
989115      Nota Fiscal Electronica (NF-e) - Overview Note
852302      Implementation Overview ISS 2004 - Legal Change MP135/LC116
759965      New Condition Formulas for MP-135 and ISS 2004
747607      Basic Customizing for MP135 and ISS legal change Brazil
980214      DDIC changes: PIS / Cofins Tax Law and Tax Situation
981123      PIS / Cofins Tax Law and Tax Situation
981687      NFe: For Services in Muncipio Sao Paulo
934846      Syntax error: TYPE-POOL 'SXRT' is unknown
979881      Message S 000 in NF writer when mandatory fields not filled
980213      Nota Fiscal Electronica (NF-e) of SEFAZ - Phase 2
1037070      NF-e of SEFAZ - Phase 2, Enhancement 01
1014600      No output found for the Nota Fiscal
1052575      NF-e of SEFAZ - Phase 2 / DDIC changes after shipment
1043688      NF-e of SEFAZ - Phase 2, Enhancement 02
1062468      NF-e: Multiple volume structure for XML file
1062251      NF-e: Extension of BADI Interface FILL_HAEDER
1070261      NF-e of SEFAZ - Phase 2, Enhancement 03
1094041      NF-e of SEFAZ - Phase 2, Enhancement 04
1000130      Public System for Digital Bookkeeping (SPED) - Overview Note
1008306      SD: Manual changes of CFOP for services when ISS tax applies
998194      Missing ISS Tax Situation in the Nota Fiscal
1047606      SD/Brazil: Using of error log during Nota Fiscal creation
120449      SD-Brazil Exchange variance error in Nota Fiscal
92383      LSA:BR:SD: Tax laws in return nota fiscal
689157      Nota Fiscal Split and number of Packages
987882      ISS Tax Law (field J_1BTAXLW3) not copied from sales order
989965      CFOP redermination in the delivery document not working
909835      Message 8B 679 raised during the delivery process
337554      SD: No. of packages in Nota Fiscal
533046      Repair order inconsistent to object list
920330      Error when changing the tax codes in a sales order
998195      PIS/COFINS/ISS Tax Law and Tax Situation in SD
104606      EDI/IDoc: Mapping IDoc types to ANSI X12
1094041      NF-e of SEFAZ - Phase 2, Enhancement 04
1105588      J_1BLFZF: Runtime error OBJECTS_OBJREF_NOT_ASSIGNED
     OSS notes for XML ver 1.1 and NF-e phase 3
1065334      NF-e: Extension of BADI Interface FILL_ITEM with tax table
1068615      NF-e: Extension of BADI Interface with SD document flow
1079826      NF-e: BAdI Interface Enhancement for NF Messages
1069919      NF-e: Partner in Block E should always be main partner
1090279      NF-e monitor: automatic refresh upon user actions
1093252      NF-e: ICMS tax situation in XML File and DANFE
1113127      NFe: New XML Layout - Version 1.10
1114348      NF-e - xNFe integration - backend
1122294      Send/resend NF-e: fill VBFA for BAdI item method
1124075      NF-e: Serie not taken from Contingency NF-Type
1144194      NF-e: Cancellation/Skipping Reason
     Bug Fix notes for NF-e BAPI.
1049946      NF-e: Adaption of Nota Fiscal Bapis
1147934      NFe: Random number should not be generated for incoming NFes
1150733      NFe: Randon number and check digit not cleared
1154995      NF-e: NF BAPI - enhancement for NF-e processing
1158622      NF-e: NF BAPI - no input of random number possible
     Bug Fix notes for Contingency process
1158612      NF-e: Wrong partner in Block-E for Entrada
1240212      NF-e: One time Vendor data not transferred to XML file
1255450      NF-e: Jurisdiction code for one time vendor / customer
1257030      NF-e: Country Name for one time vendor / customer
1069018      Cancellation of incoming NFe shows error J1B_NFE 003
1070077      NF-e: Protocol number and document status for Denied NF-e
1145148      NFe: Cancellation for Contingency NFes
1152263      NF-e monitor: wrong action status '7' for C-NF-e
1146914      NFe: Synchronous call to messaging system from backend
1149356      NFe: Dump when NFe is cancelled with MIGO
1152081      NFe: Dump when NFe is cancelled with VL09
1153533      NFe: Dump when NFe in contingency is cancelled with VL09
1156116      NF-e: Contingency by stock transfers
1160107      NF-e: Cancellation of contingency NF-e with DOCSTA = 1 or 2
1161347      NF-e: Cancellation of Contingency NF-e - correction
1238648      NF-e monitor: req. action '3' (send) wrong for swtch. NF-e
1165953      NF-e: Numbering Gaps
1244326      NF-e: Numbering gaps - Status update in table J_1BNFENUMGAP
1245425      NF-e monitor: required process step - contingency
1252567      NF-e: Resend of NF-e - rejected or with validation error
1266344      NF-e: Action Indicator for NF-e with validation error
1254565      NF-e: Synchronization of RFC call between ERP and xNFe
1053626      MIRO: wrong document reference in nota fiscal
1073259      NF-e: Transfers - Outgoing NF-e No. not taken by Incoming
1153874      NF-e: GR for future delivery takes wrong NF-e number
1174946      NF-e: Serie not considered for duplicate NF-e number in MIRO
     Miscellaneous bug fix notes
1175538      NF-e: Reference between NF and NF-e
1244881      NF-e: Mixed scenario in MIRO shows error 8B219
1257422      MIRO: Error 8B 219 by posting of reference invoices
1150843      NFe: Text for cancel reason not transferred to XML file
     Bug Fix Notes Group 2
1059699      NF-e: Reference between NF and NF-e
1139062      NF-e incoming: Posted via J1B1N -> Wrong Document Status
1144199      NF-e: SD Billing and Contingency
1145089      NF-e: Cancellation despite rejected cancel request
1149787      NF-e: Wrong status-code text in NF-e history
1151112      NF-e: cancellation-reason text gets lost (pre req of 1150172)
1150172      NF-e monitor: selection leads to dump
1068379      Creation of Billing document issues an error 8B 145 (pre req of 1145089)
1152842      NF-e: cancellation reason does not work
1154700      NF-e: Random number & check digit not stored in active table
1073145      PIS / COFINS Tax Laws for Transfers (pre req for 1155231)
1082527      Missing PIS / COFINS Tax Laws for Transfers (pre req for 1155231)
997868      VL02N: CFOP, tax laws not copied from delivery (error 8B148) u2013 (pre req of 1155231)
1155231      PIS/COFINS tax law in NF/NF-e by split valuated material
1155424      NF-e monitor: Menu -> "Check MS Connection" does not work
1159177      NF-e: FUNC J_1B_NFE_SET_STATUS_IN_BACKEND set as Rem.Enabl
1161951      NF-e monitor: "Resend" functionality.
1162232      NF-e: switch to contingency not possible after MSS Update
1162512      NF-e: cancellation reason not initial at first-time call.
1162629      NF-e: creation date gets deleted from NF-e data-base table
1164283      NF-e: SCS '5' - upon authr.to cancel system does not cancel
1165155      NF-e Monitor: BACK (F3) leads to cancellation
1165360      NF-e Monitor: new selection parameter - creation user
1168394      NF-e: Reference document not taken from Nota Fiscal header
1168798      NF-e: User decision for used NF-Type for Material Movements
1171383      NF Writer: Copy NF-e that was switched to contingency.
799445      Nota Fiscal creation: Consideration of local dates (pre req of 1171383)
1104003      NF-Writer: Serie not taken from Reference NF (pre req of 1171383)
1156037      NF-e: NF-Writer allow reference with different NF-types (pre req of 1171383)
1175759      NF-e: central contingency per business place - correction
1239598      NF-e: Random number and check digits are lost in NF writer.
1163888      NF-e: Random Number includes spaces (pre req of 1239598)
1245425      NF-e monitor: required process step u2013 contingency. u2013 applied in bug fix notes no need to apply.
1246700      NF-e: Wrong reference for NF entradas.
1257688      NF-e: Update termination with error J1B_NFE 021
1258021      NF-e: Dump by creation of NF header text for XML file
1258974      NF-e: Monitor report aborts with DBIF_RSQL_INVALID_RSQL
1265172      NF-e - Decouple RFC from DB Update
1285851      NF-e: Cancellation of none authorized documents
1288925      NF-e: References between NF-e and non NF-e
1272677      NF-e: Cancellation for Material Document with serial number (pre req for 1288925)
1247602      NF-e: Cancellation of material documents with serial numbers
1163104      NF-e: Cancel Material documents with initial cancel reason
1293944      NF-e: Cancellation of material documents with batch classes.
1267128      NF-e: Cancellation goods movement with MVT 844 not possible (pre req for 1293944)
1300000      NF-e: Decouple - Contingency
1314856      NF-e: Decouple - Contingency in J1BNFE and VF01 & VF04
1321837      F-e: Cancel of material documents not possible
1092028      NF-e: Protocol number in NF-header overwritten (pre req for 1265172)
1114283      NF-e: cancellation - document status cleared in J_1BNFDOC (pre req for 1265172)
1234053      Local time / local date in NF header and NF-e XML (pre req for 1265172)
1288994      NF-e: Decupling note 1265172 causes error for incoming NF-e (pre req for 1300000)
1297042      NF-e: NF-e number missed in access key after decoupling (pre req for 1300000)
1087535      RFFOBR_A,U:Doc.no should be filled with 9 digits in DME file Applied OSS note 1087535 to the object Z_RFFORIY1 which was copied from RFFORIY1
1097455      NFE: Bank files should accommodate Doc. Numbers with 9 digits
304961      Wrong boleto check digit with carteira data (pre req of 1097455) - Not relevant
336117      Include due date factor in Boleto barcode for A/R (pre req of 1097455) - Not relevant
705726       ITAU: Boleto has negative interest value (pre req of 1097455) - Not relevant
846297      Func Mod - BOLETO_DATA not printing correct nosso numero (pre req of 1097455) - Not relevant
852782       BOLETO_DATA - Corrections of note 846297 for Bredesco only (pre req of 1097455) - Not relevant
1227478      Dump in payment run (F110) when XBLNR is empty
1138278      NFe: Field PREDBC not filled in XML interface structure (pre req of 1149585)
1149585       NFe: CST field required in XML file for taxes not in NFe
1053855      VL02N raises error 8B 053 "Branch not foundu201D
1165696      RFEBBU00: Error in batch input due to changes in Nota Fiscal
1180402      NF-e: BADI methods FILL_HEADER and FILL_ITEM
1180672      NF-e: Gap numbering check doesnu2019t consider the series
1225338      RFEBBU00: Additional changes to the note 1165696
1241922      NF-e: Report J_1BNFECHECKNUMBERRANGES xNFe adaption
1244326      NF-e: Numbering gaps - Status update in table J_1BNFENUMGAP (Applied using other Kintana)
1270813      NF-e: Year not included in the XML file
1247264      NF-e: Error in RFC to /XNFE/NFE_CREATE after note 1241922 (pre req for 1274200)
1274200      NF-e: Numbering gaps report sends SERIE with spaces
1276185      NF-e: Numbering gaps report sends SERIE with spaces
1294917      NF-e: Gap numbering check - several corrections
1324538      Missing address for OT Customer in J_1B_NFE_CREATE_TXT_FILE
1331432      NF-e: Numbering gaps report detects gaps for initial series
1332167      NF-e: Rep. J_1BNFECHECKNUMBERRANGES aborts with error DC 006
1092341      RFFOBR_A,RFFOBR_D: Performance problem while rebate calcula
1237089      RFEBBU10:While uploading ITAU Bank returnfile- Error(F5 170)
1051314      Check Digit missing from Boleto number (pre req for 1306966)
1306966      J_1BBR30:XREF3 is not updated correctly with Boletofrom bank
1005924      RFFOBR_A-The DME file does not include Rebate for ITAU (pre req for 1287633)
1287633      RFFOBR_A: Discount amount not calculated correctly
1234054      NF-e: function J_1B_NFE_MS_REQUESTS_DATA is not RFC enabled
1297534      NFe cancellation problems in GRC
1243964      NF-e: Adaption of xNFe interface of function NFE/NFE_SKIP
1165746      NF-e: Cancel - Error log not updated
1327465      The program /xnfe/update_erp_status is not updating R/3
1326691      BAdI for controlling the RFC call of external systems
1333136      Prevent simultaneous click on buttons in NF-e monitor
1333742      NF-e got the status 218
1354192      Validation rules: correction for fields TPLACA and T_UF1
1373175      Lock object for /XNFE/NFE_CREATE to prevent double transm
1376500      BAPIRET2 to provide the detailed information to ERP
1267455      Not possible to create different DOCREF per item using BAPI (pre req for 1373321)
1373321      BAPI_J_1B_NF_CREATEFROMDATA: DOCREF from Header go to item
1328583      NF-Writer posting of NF/NFe when mandatory fields not filled
1338166      NF-e: Random number and check digit lost after note 1328583
1259918      NF-e: RFC calls for request for cancellation or skip
1152140      NF-e: backend allows inconsistent new SCS (pre-req for 1298283)
1162852      NF-e: Inbound errors missed in error log of Monitor Report (pre-req for 1298283)
1163056      NF-e: Problems with printing via BADI method CALL_RSNAST00 (pre-req for 1298283)
1276438      NF-e: Parallel Phase not identified in messaging system (pre-req for 1298283)
1296515      NF-e: J1BNFE reset rejected NF-e after skipping request (pre-req for 1298283)
1297823      NF-e: Cancelled NF-e shows wrong action indicator (pre-req for 1298283)
1298283      NF-e: Skip for NF-e with validation error
1362969      NF-e: check cancellation for billing documents
1368159      NF-e: cancellation of invoices via original application only
1370933      NF-e: Accept Rejection to Cancel - wrong status in monitor
1376324      NF-e: Skip for NF-e with validation error
1140579      NFe: Field length conflicts from backend interface to XML
1357713      NF-e: Cancel of incoming NF-es does not update active table.
1173018      NF-e: Field control for Random Number and Check Digit (pre-req for 1366320)
1321517      NF-e: MIRO Credit Memos for NF-e shows error 8B 020 (pre-req for 1366320)
1366320      NF-e MIRO:Save is allowed without mandatory fields filled for NFe
1375066      NF-e: J_1BNFECHECKNUMBERRANGES ends too early, wrong subrc
1375894      NF-e: J1BNFE authority check for company code
1377879      NF-e: Report J_BNFECALLRFC aborts with message A098
1379062      NF-e: posting GR after cancellation leads to wrong NF-e
1357777      Cancel billing document without Nota Fiscal cancellation
1380861      NF-e Resend(proc.stat.07) with Signature error impossible
1362025      Error while sending Bacen Code EX with 0 on begining
1249819      NF-e: Field MODFRETE filled incorrectly

Bom dia Marc de Ruijter,
Não dá para ler sua thread, mas imagino que seu validador esteja desligado.
No GRC vá em SPRO --> SAP GRC Nota Fiscal Electronica --> Configure System Response for Each Tax Number (CNPJ)
Para ligar/desligar o Validador basta clicar no check box na coluna Validation.
Observação: Para correto funcionamento do GRC deve-se sempre utilizar o validador ligado.
Após isto refaça seu teste, é provável que você receba um erro de validação para a NF-e. Veja em GRC Web monitor -> NFe Detailed View -> Validation History.
Atenciosamente,
Fernando Da Ró

Rebate Condition Type based on Calculation

I am trying to create a rebate condition that is based on the calculation of Average Invoice Price of group of products. However, I am not able to select the Calculation type based on Formula. Please let me know if someone has come across the same issue.

For example, Rebate of $2/unit of Product A is given to a customer only if
Averrage Invoice Price of Product A, Product B and Product C is greater than $135

Settling Rebate through free goods in R/3

Client is producing halogen and CFL lights for home and office use. Client is making sales through dealers and distributors in market.
Sales regions are: North, South, East, and West.
Sales Sub regions: Delhi, UP, Maharashtra, Karnataka, West Bengal and so on.
Promotional Schemes:
1)     Monthly:
a.      Quantity targets are given for month on achieving free goods are given
b.     No Credit Memo
c.     For example, on sale of 1000 pcs of 20W CFL in one month, 50 pcs of 15W CFL free.
d.     Mostly product based schemes as to promote particular line item
e.     Different schemes for distributor and dealers (divided on basis of customer group)
2)     Quarterly:
a.     Similar to Monthly with difference in time frame which is of quarter
3)     Secondary (On basis of points)
a.     For each qualifying product, points are awarded. On accumulation of points free gifts or goods are provided for different level of points
4)     Annual:
a.     Annual discount on basis sales amount irrespective of which products sold.
Key Points:
1)     All calculations are done on excel sheet using sales report from SAP i.e. to find the qualifying customer.
2)     Later scheme is settled by creating free of charge sales order in SAP of zero prices.
3)     Same product can be part of two schemes one on distributor level and other on regional or national level.
4)     No credit memo is issued to settle schemes.
Question: Can we map this process through rebates or any way sales such that the schemes can be created and list of qualifying customer is calculated in system itself? Later, it can be settled through free goods rather then credit memo?

Already solved. Item Catgory settings and Downloading R/3 customizing to CRM

What is the use of Alternative Calculation Type =2 and 4

Dear Friends
In pricing procedure in gross value, Net value for Item and Net value has Alternative calucation type is 2.
What is the use of it?
Without using it these value line are also fetching net value then what is the work of it. Please give me detail information with its effects in pricing condition tab page in sales document.
Thanking You
Arun

Arun biswal,
Correct Biswal. We have at varoius stages within Pricing procedure the "net value" which is calculated. Not only the alternative calculation type "2" is used if you notice carefully they are stored as subtotals at various levels.
For Ex Gross Value --> Subtotal =1 --> Calc type = 2
similarly for Net value for Item --> Subtotal =2 --> Calc type = 2
Net value 2 --> Subtotal =3 --> Calc type = 2
See, these are used to calculate the net value at various levels in pricing. The calculation Type has got a set of routines that will facilitate us in pricing. SAP has provided certain clauclated formulas or routines to facilitate us during calculation within pricing . Here the "2" is used for calculation without tax and store it as subtotal and display it or use it for further calculations.
We can use this "netvalue" amount for further calculations. It is used for clarity purpose when you issue a statement to customer. (like Confirmation order) at various levels like discount amt involved, Freight involved, Rebate amount invloved.....
Even without this Calc type or using sub total u can proceed....
Finally we have TOTAL --> Subtotal =A --> Calc type = 4
In the above line we have Calc type as 4, which means when you use TAX this calc type is used .
Routines are used to facilitate your process....
Regards
Sathya

Condition Type for Rebate

Hello All
I am in the process of configuring the rebate processing in our system...this is my first experience...we are on ECC7.0...I am follwing the Rebate Processing configuration guide but I have a few questions...
My requirement is the following
Order volume fully paid.... the following will apply
<$500,000 credit percentage is 3%
>500,000 and < credit percentage is 3.75
etc....
In the condition type configuration under control data I am confused of the calculation type to use and the condition category as well...I am using condition type Material Rebate, but have also added all the condition types related to Rebate...just in case.
There will be no manual payments or partial settlements. The rebate is due at end of year of all fully paid items.
If there is shipments that are due but will not be during the annual term and it exceeds the lets say 1,000,000 since he credit percentage would be 6% in this case....after the review of the rebate agreement then the discount for the following year will be set at the appropriate percentage and will begin at $1.
For example if the total sales during this term are 1.2 million the the credit percentage for the following year would be 6% for all the sales the following year beginning at $1...sales for the annual term of 1.2 million would equate to a rebate of 72,000 (6%).
Also, all material that is bought the customer receives a 3% discount on top of the above.
Will I need to also include condtion type groups???
Your help is GREATLY appreciated!!!

Hi Eric and thanks for your reply ....
If the Rebate is for a certain customer and they are having multiple materials for the rebate and can have channel partners that will also be a ship to party and rebate applies....I am thinking I need to use the 0002 condition type? Please confirm.
That is the one I have chosen so far....I do not see the rebate condtion type being being pulled through the sales order on the condition tab...it wants to keep pulling in the pricing condtion table for that rebate material....any advice as to what I may have missed....I did follow the config guide...as stated before this is my first experience wit hrebates...
I can understand the invoice showing the accruals but how would I do the scale to know if the customer reaches a certain amount their rebate percentages would be different based on the paid invoice sales...
up to 500,000 paid would be A 3 percent discount
Over 500,000 would be a 3.75 percent discount
This is also on top of the standard 3 percent discount they are given on the material as a customer discount.
Please advise....your assistance is appreciated

Rebate calculation

Similar Messages

Maybe you are looking for