PROBLEM IN REBATES
HI
I HAVE CREATED A REBATE AGREEMENT AND ALSO A SUBSEQUENT ORDER DELIVERY AND INVOICE
BUT THE VALUES FOR THE CONDITION TYPE BO03 ARE NOT APPEARING IN THE INVOICE
SCALE BASIS =B VALUE SCALE
CHECK DESCENDING
SCALE TYPE = CAN BE MAINTAINED IN CONDITION RECORD
I HAVE DEINED SCALES IN REBATE AGREEMENT
FROM 10000 1%
20000 2%
50000 3%
REGARDS
Hi,
Rebate is a long term agreement between company and customer for buying certain products or for a certain volume and it is calculated on the basis or the no of billing documents say after creating four or five billing documents it is calculated
Note Rebates are not given on each billing document.We make four or five billing documents and then calulate the total rebate value and settled as credit note to the customer
If you want to set up rebate processing in a certain client, you must
u2022 Define Condition types for rebate (Tables T685, T685A, T685T)
Condition types must belong to condition class C (end-of-period rebate)
u2022 Define condition tables for rebate(Tables E*)
u2022 Define Access sequences for rebate (Table T682*)
The access sequences have to belong to category 1 (rebate-relevant accesses)
u2022 Maintain the condition types in pricing procedure.(Tables T683, T683S), rebate basis in the SubTo field (Condition subtotal) contains entry 7 (value takeover in field KOMP-BONBA).
u2022 Define pricing procedure determination.(Tables T683V )
u2022 Account Determination For Rebates will include: Define account key
Define account determination types
Assign account keys
Maintain account determination procedure
Define access sequences
Assign G/L accounts
Create accounts for the accrual if required.
Maintain the G/L account assignment and ensure that the G/L account is used in second place for accruals.
u2022 Define Rebate agreement types (Tables T6B1, T6B1T)
u2022 Define Condition type groups (Tables T6B2, T6B2T, T6B2F)
u2022 Assign Condition Types/Tables To Condition Type Groups (Table T6B2F)
u2022 Assign condition type groups to rebate agreement types (Table V_T6B1_ZU)
u2022 Number ranges for rebate agreement categories (should be maintained manually)
u2022 Order types B1 and B2 (Tables TVAK, TVAKT)x
u2022 Item categories B1N (Tables TVAP, TVAPT)
u2022 Assignment of item categories to item category groups (Table T184, B1, B2)
u2022 Billing types B1 and B2 (Tables TVFK, TVFKT)
u2022 Copy sales order to billing document (Table TVCPF, B1* and B2*)
u2022 Activate Rebate Processing at sales org , billing document and customer master data(payers view)
For more information on process please go through the below link;
http://help.sap.com/saphelp_47x200/helpdata/en/4a/ac853478616434e10000009b38f83b/frameset.htm
Hope this will help you.
Similar Messages
-
We have a problem with Rebate agreement settlement.
Generally when the finall settlement of Rebate is completed ( with status D - D means final settlement ), the liability should be zero. However, after we made final settlement, still some amount is showing as liability when we looked at the sales volume of the rebate agreement.
Please help us to fix the issue.
Thanks in advance for the help.Hello,
Please review the Note 392683.
Regards,
Raghavendra YN -
The problem is that After final rebate settlement there is still open accrual.
And in another agreement the p&l effect in SAP is much more higher than the difference of accrued and paid amounts.
I revised already the agreement conditions and I didn't find out anything....
Where can be the Problem?
Thanks in advance and regards
WilliamDear Tirumalasetti,
This may be due to there is holiday in that calendar on the date of the Rebate agreement period end date.
So please change the Rebate agreement period end date or change holiday to working day in that calendar on that date.
I this will help you,
Regards,
Murali. -
Hi All,
I am using material rebate (0002), in reabte agreement creation I am giving condition (material rebate B002), in the condition I am giving scale vaule on quantity scale basis. But during sales order processing system is not picking up rebate condition record on scale basis. only first record in scale is considered. Is there any specific settings for scales in rebate .
HimanshuHi all,
24 req just sees that the condition gets executed at the invoice level, remove it the condition gets executed at the order level with the same behaviour. I checked it earlier. And this is a problem to me also, that the rebate scale is not getting picked up. Only the first value of scale is active irrespective of the billing value.
I think its worth continuing this thread and keep it updated till the time we get an answer for this.
Thanks & Regards
Sadhu Kishore -
Problem in rebate agreement type 0005
Hi
I created a rebate agreement of type 0005 and maintained amount Rs 5000 for a customer
while creating billing document the condition type BO06 was determined in the billing doc but without anu value
the analysis shows that condition record has been found
I have checked the pricing date and all other parameters but still not able to figure out the mistake
Kindly help me in this regard
Thanks and Regards
SunilIyerHi SunilIyer
If you are working with the standard rebate agreement 0005 and condition type BO06
You will be working with a sales independant agreement and a fixed amount condition.
For a fixed amount there is no posting of accruals because it is already known what the
liability is in the agreement.
If accruals are required most customer's would post a manual accrual from the agreement
for the fixed amount of the agreement condition.
In your billing document you will see the Bo06 condition is determined and the agreement is
known but the condition value will always be 0.00 for a fixed amount.
This is correct and expected
Hope this helps explain the system behaviour
Kind regards
Brian -
Problem with Rebate Agreement Sales Volume
Hi,
I executed the rebate recalculation via SDBONT06 for a total of 93 agreements on 04.08.2014 and therefore the sales volume was updated and there was no message in VBO3 as well.
But today when i am checking the agreements all of them are showing message "Sales Volume is not Current"
I have gone through all the threads on SCN for this.
there have not been any changes in payer, sales org, agreement or agreement conditions.
I dont see any customizing also changed.
Please help asap as to what can be the reason for this message all of a sudden.
Regards,
Aayush Jain
SAP SD ConsultantHi Aayush
When you rebuild the rebate index table VBOX all agreement conditions will be set to retroactive again. I guess someone has run RV15B001 on your system in the meantime ?
The "Sales Volume is not current" message is issued when the rebate condition is flagged as retroactive (KONP-KSPAE) SDBONT06 resets that when it has completed a successful update
So just run SDBONT06 again, all of you 93 agreements are updated so the report will only reset the KONP-KSPAE field on the conditions in that case.
Hope it helps you further
Kind regards
Brian -
Hi thr,
I have a requirement in rebates or rather just want to know if this functionality is supported by SAP.
We have created a rebate for a customer who has several ship-to parties. Also, the rebate condition are created seperatly for different ship-to-praties with a combination of sold-to/ship-to/product hierarchy. We want to do manual accruals and we put 10$ on each customer for four different ship-to (same customer but different ship-to). However, when we checked in BI report it is showing the entered amount 40 $ only under one ship-to.
Could someone please let me know if we can have the functionality where in the accrued amount hits ship-to in case there are more than one.
Please clarify.Hi,
What I understand from the requirement is that, one Sold-to party has many ship to party and you want to accrue the amount for each ship- to party. But it is not showing the accrual for each ship to party separately and it is showing for only the sold-to party which is also a ship-to party.
Actually, the rebate is accrued for the payer only and not for ship-to parties. As far as I understand, in your case, all the ship-to parties are associated with one payer ( which is Sold-to party), so you are getting a accrual for single payer ( not for the ship to party).
So, if you have single payer and rebate agreement for him, then you cannot accrue the amount for each ship-to parties.
If each ship-to parties are also the payer, then you can create a rebate agreement for each one and in the sales order, in the line items, if you assign the ship-to party and payer and process it and it will be accrued for each payer ( which is also the ship to party). -
G/L account problem in rebates
Dear All,
My billing docs are not getting posted in FI. When i go for analysis it says- for rebate condition type BO02- the second G/L ACCOUNT IS MISSING.
Plz do the needful.
Regards,
Pankaj JainHi,
It seems your G/L assignment is missing in VKOA with Rebate Account key ERB with relevant G/L, else tell your FI Consultant to create G/L for Rebate Condition and assign to your account key e.g ERB with that G/L in VKOA..
Regards
Shambhu Sarkar -
Hi Experts,
I have problem with Rebate process. I have created new table with sales org and customer group as fields and assigned this table with access sq and condition type ZB01. Matained the rebate agreement and condition records also. Inserted the these new rebate condition types in my Pricing procudre and assigned requirement 24 in the requirement column as I want accural should show up in the billing document. But these rebate condition is not getting value in the billing document and pricing analysis shows that "Condition ignored (requirement 24 not filled)". We have maintained C (copy manaul elements and redermine others) as price type in copy control. But rebate condition not showing up in the billing document. Kindly advice me where could be the problem.
Sales org, customer and billing document type has been activate for rebate.
Edited by: sapsduser on Jan 31, 2011 11:36 AMHi,
If that is the case, no further help is possible from myside.
You can just get a developer and debug this routine. Then you will come to know where teh invoice is failing the routine 24. I am sure it is somewhere in pricing. But the exact point can be confirmed only by a developer. So please debug invoice creation with the help of an ABAPer. -
Rebate Agreement - No correction due to value change
Dear Friends,
I am facing a problem in Rebates. When I am opening the Rebates Agreement, the system prompts the following message "The sales volume for agreement _________ is not current." I have tried using the T-Code VBOF but the system prompts for the following error -
9202507314 (Billing Doc No) No correction due to value change
9202507363 (Billing Doc No) No correction due to value change
I have checked both the billing Document and checked for changes but there is not changes that was made to the billing Document.
Kindly suggest a solution.
Reagrds
Vineet JainDear Vineet,
I have the same problem while running VBOF few billing documents are showing as not updated with the message "No correction due to value change".
But I have found that those documents are belongs to other agreements of the same customer number.
Can you please help me, which sap note should apply to over come this error message.
Thanks in advance.
Anjan Kumar. -
Rebate Error- Sales Volume not current for agreement.
Hi
I am doing Rebates. "The error I am getting is Sales Volume for the agreement (xx) is not current". In the rebate agreement, condition - payment data - the accruals, rebates are not getting updated. It shows zeros.
I checked accounting documents: The accruals GLS are updated with the rebate amount. Other rebate GL account is not getting posted.
Any suggestions on how to fix the problem ?Dear Sunil A
You have got this error means some steps are there to be fallowed first please tell me what you have checked by the by please check this link also
Problem with Rebate Agreement Sales Volume -
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 incorrectlyBom 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 ...Problem B1
Can any on help me to find the solution for creating Final settlement in Rebate Agreement, after creating Partial settlement and manual settlement
I have situation
1 Accruals 200 -
2 Accruals Reversed 80
3 Rebate Payments 80 -
4 Max Payable amount 120 -
Here my problem is i am unable to create FINAL SETTLEMENT ( B1 )
I can do both Partial Settlement B3 and Manual settlement B4 What should be my next step Should i have to settle all the Accruals and then go for Final Settlement B1 ...Or can i can create directly for remaining 120 through B1 which i am unable to do as the system is not allowing me to execute final settlement tab in Condition record inside the agreement ....Or am i missing any setting in Rebate Agreement specially in the fields of Final Settlement and Minimum Status
Please help
PLEASE all GURUS
Edited by: arnoldsw sw on Feb 14, 2008 10:24 AMHave you passed the acrruals to Accounting. If not please do it.
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.
Then try the final settlement.
regds
Jude -
Rebate Agreement problem( VB(7 )
Hi All,
I'm having trouble in the creation of Credit Memo Request No..The problem is that, when i'm going to settle the rebate agreement no. ( VB(7 ), and i append a date in VALIDITY DATE TO, after the creation of credit memo request no., the billing date of that no. is not matched to VALIDITY DATE TO. What are the reason why it came up to this problem? Normally, the VALIDITY DATE TO will APPEAR in the billing date field after you created the credit memo request no. Please help people why this happen.
Points will be given immediately.
Thanks and regards,
MackoyHi ,
I have checked the Accky "ERU" and Accr "ERB"...there is no problem regarding that ....
Thanks .
Abhijit -
HI,
I have created rebate agreement for my own by coping the standard one 0003 customer rebate .and created my own condition type and assign it to pricing procedure .Now the problem is when i created billing document it shows the rebate condition type with proper value .But when i release the billing document to accounting then the condition type releavent for rebate vanish. But when i use the standard one it shows also after releasing it to accounting .Can you please tell what could be the problem .I have checked there is no diffrence with the standard but only Access Sequence . I also created accesss sequence with the acess category 1. Thanks in advance .
Regards,
Abhijit ...Hi ,
I have checked the Accky "ERU" and Accr "ERB"...there is no problem regarding that ....
Thanks .
Abhijit
Maybe you are looking for
-
MSI GF4 Ti 4200 Td not worked!!
Hallo I have new computer P4 2GHz, 2 x 512 DDR (266MHz), 80 GB HDD, GF4 Ti4200 128 mB DDR (MSI), MSI 845e Max2 BLR (mth..). Win 98 and Win Me not worked!!! Why????? Win XP and Win2000 running ok.
-
Skillbuilders modal page plugin query
Hi Guys, I have downloaded the Skillbuilders modal page plugin and it works very well for 99% of the scenarios that we have encountered. We have one page which needs a slight modification from the standard functionality with regards the modal plug in
-
Links in blog archive not working
Can anybody help me get more reliable performance from my iWeb archives page? http://web.mac.com/truthmaker/Site/Blog/Archive.html I am getting very frustrated with the Archives page for the blog I've created with iWeb. Often -- very, very often, the
-
How can I get rid of underlined links?
I have explored the Safari Preferences and cannot find any way to eliminate the underline that appears with all link items. On my Yahoo homepage, for instance, all of the links (and almost every line is a link) appear with an underline. I'd like to e
-
I paid USD150 for in app purchases for Infinity blade 2, had the game for nearly a year, 'backed it up' as per the instructions, i stopped playing the game for a bit, and an update comes along, wipes my accounts, and because of icloud sync, it wipes