Did you read OSS Note 167509 - Copying structure conditions? Try the solution provided in the note.
Regards,
↧
Re: Incorrect KUMU condition in partial invoice
↧
Re: Service Invoice delete
Hi Jobi, sorry for delay.
I was talking with my boss, and he told me that currently our SAP doesnt have install SARA module, so i think that archived documents wont possible. what do you think?
↧
↧
Re: Service Invoice delete
Hi Sircc red, sorry for delay.
i found this:
but for table TCDOB
would have to do? whats your oppinion?
Regards
↧
Billing plan XXXXXXX does not exist - Program error (V2040)
Hi,
I have the following error when displaying, modifying a contract or creating a sales document with reference to a contract (VA4*):
Billing plan XXXXXXX does not exist - Program error
Message ID: V2 040
The problem comes because contract bussiness data (VBKD) has a missing reference plan (field FPLNR) that does not match an entry in FPLA table.
I have checked several OSS notes like 720350, 60126, 180437, 868083, 81712, 1295258 and 1578559.
The only note that applies to our system is 1578559, but unfortunately it does not solve the problem (even debugging does not stop at corrected program).
I have searched any method to correct FPLA table for missing entries but have found nothing. Anyone had this problem??
Many thanks,
Salva.
↧
Re: Billing plan XXXXXXX does not exist - Program error (V2040)
Hi Salva,
as you already have found out correctly, the error is occurring due to the fact that a billing plan number is maintained in sales order field VBKD-FPLNR, but it does not exist in billing plan table FPLA.
This is an inconsistency, the billing plan had not been created, but its number is assigned to the sales document.
The most known root cause of such a situation is wrong custom-own coding in the user-exits of MV45AFZZ, notably USEREXIT_MOVE_FIELD_TO_VBKD.
For an investigation how exactly this could happen, you would have to create an incident on the SAP Service Marketplace and send to SAP Product Support.
The solution to allow further processing of this sales document would be to delete the content of field VBKD-FPLNR on the database. A correction report exists for this (ZZ_CORR_BILLPLAN) , which is however not included in any note, but can be send to you by SAP Product Support.
Since to avoid the error in the future, an analysis is required, to find out the root cause, I would suggest to contact SAP Support.
Best regards,
Tobias
↧
↧
Re: Billing plan XXXXXXX does not exist - Program error (V2040)
Hi Tobias,
Thanks a lot for your answer. I checked existing user-exits but found nothing related to that field (may be in another place).
I don't know the root cause but I could display contract debugging in quality system and modifications log has a red line with the text "has been deleted" and in the detail you can see that FPLA is the affected table. What I don't know is how this was done, so I will contact SAP support.
Many thanks,
Salva.
↧
Re: Incorrect KUMU condition in partial invoice
SAP standard behaviour investigated pricing behaviour with SAP Note 900089 and found
statement xkomv = rettkomv re-set condition rate to original even though pricing routine calculated condition rate as per invoice quantity.
Anyway thanks to people who look into this post and try to find solution.
↧
Re: Billing plan XXXXXXX does not exist - Program error (V2040)
Hi Salva,
yes, it is necessary to investigate on your system, SAP Support could assist you. And you can get the correction report, which I indicated.
Best regards,
Tobias
↧
Sales Tax Reporting for TAXUSJ
Hi SAP Experts,
The standard report for sales tax for the US is RFUTAX00.
The report is in ALV format. The layout used by the program only has five fields. If you run the report in the foreground, you can change the layout. However, if you need to run this in the background, there is no way to get the layout that you want.
Our sales tax on the AR side is very large and I can't run the program in the foreground or it will time out. I'd like to be able to enter the layout on the selection screen and have the program use that layout. I can enter the layout for other reports such as FBL3N, KSB1, SE16N, etc.
Has anyone had this same problem? Any suggestions?
Thanks and regards,
Judy Ortscheid
↧
↧
Re: Accounting doc only generating in VF02
I know this is an old post but i'm having the exact same issue.. I can only release to Accounting from vf02 ( no errors ).
Do you remember what the problem was?
Thank you!
↧
Release to Accounting only possible via VF02
Hello gurus!
I am having a strange issue. While doing billing via vf01, accounting doc is not created. If I release via vf02, accounting doc is created without any error.
I have searched again and again the forums but i am unable to find an answer.
I have checked VKOA, VOFA for Posting Block ( it is not checked ) and no errors appear when i release via VF02.
Could you suggest any possible solutions?
Thank you in advance!
↧
Rebate Agreement (Accounting Entries Confusion)
Dear Gurus,
Please clear my understanding regarding rebate agreement processing.
1. the system books accruals at the time of invoice. (this step is clear to me).
Lets assume system books the provision/accruals $1000 against an invoice.
2. partial settlement, system create credit memo request and than credit memo, to pay the accrual amount to the customer. (this step is clear to me).
lets say system create $1000 credit memo as its already accrued for the customer, system make the accounting entries accordingly.
3. what is the difference in the condition record column of rebate agreement column1 "Rate" and column 2 "Accrual".
But when I go for final settlement I get confuse: !!!!
a. why final settlement is there.
b. why this process reverse all the financial entries created in above scenario 2.
c. when accruals are booked and paid through credit memo tan why we use final settlement, and I confuse till we create final settlement before that
rebate agreement will remain open.
Looking for the gurus feedback in this regard.
Regards,
Imran khan
↧
Re: Rebate Agreement (Accounting Entries Confusion)
Hi Imran
I will try to answer your questions.
The rate (amount) column of the rebate condition is the amount or percentage that will actually be paid to the rebate recipient. The accruals field is the amount or percentage that your company want to reserve or accrue against the exposure. These are often the same but there are many reasons why they would not be the same. For example if scales are included in the agreement these are only ever included in the final settlement so a customer might want to accrue an average percentage somewhere in the middle of the scale, or other business reasons.
In rebate processing you have the option to generate partial payments throughout the period of the
agreement, these can be set to reverse accruals (VB(2) or not. If you do not want to reverse accruals for each partial payment you will need to do it with a final settlement. The final settlement is the mechanism to generate the final payment to the customer and it reverses any open accruals on the account and also sets the closed status on the agreement.
So in the rebate process, periodic or partial payments are optional, but the settlement is not, it is the step that completely and correctly closes the financial arrangement at the end of the period, clears the accruals completes the customer payment and closes the agreement.
Hope it helps you further
Kind regards
Brian
↧
↧
Re: Release to Accounting only possible via VF02
Hi
in function module RV_INVOICE_DOCUMENT_ADD the system check the posting block from VOFA
and if it is not set it calls function module RV_ACCOUNTING_DOCUMENT_CREATE to try to generate the FI document. If it fails to create the FI document in this step you will need to check
in RV_ACCOUNTING_DOCUMENT_CREATE why this is the case.
You can be sure that in VF01 with no block the system tries to create the FI document.
There are several user exits processed in the FI interface - Check if you have any active
exit_saplv60b_001 to exit_saplv60b_012 perhaps you have checks that cannot pas in Vf01
when the actual billing document does not yet exist in VBRK or VBRP ?
Hope it helps you further
Kind regards
Brian
↧
Fixed Value Date - Billing Document
Hi,
I have a combined billing Idoc which carries around 17 SO. But the Invoice get split in to two, once has 16 SO and another one has 1 SO. When I checked the header data of both the billing documents, I found FIXED VALUE DATE is empty in one SO and another one has value in it which is same as billing date. Please tell me the logic behind this Fixed Value date. As I am a beginner and ABAPer, please explain me why it gets empty and also if possible please let me know if there is any standard function module or program which calculates this Fixed value date for invoice.
Thanks
Hariny S
↧
Re: Rebate Agreement (Accounting Entries Confusion)
Thanks Brian for this explanation, rate and accruals scenario is now clear for me.
"But as per your 2nd paragraph "In rebate agreement you have the option to generate partial payment ................................................ close status on the agreement".
In partial settlement at the time of credit memo system generate accounting entries, and in final settlement system again create financial entries and reverse the old one.
but if you directly create final settlement system create financial entries only once.
how would you explain this, is it ok.
Appreciate if you explain with any value starting from provision/accruals books at the time of invoice.
Thanks again for this favor.
regards,
↧
Re: Rebate Agreement (Accounting Entries Confusion)
Hi Imran
When you have a rebate agreement the system will post a provision against the rebate recipient and the accruals account for every billing document posted (that falls within the validity). So you post for example $1000 against both accounts, in total across several billing documents. The individual postings and totals are held in the S136 and S060 tables for the agreement condition.
If you create and post a partial payment of $600 S136 and S060 tables are reduced accordingly.
So for your final settlement here the system would generate a payment value and an accrual reversal value of 400. There would never be any duplicate posting made in FI.
In a case where you had made partial payments totalling the $1000 actually posted in the billing documents you final settlement would be generated with a value of 0.00 on both lines. Net effect nothing is changed in FI only the rebate agreement status is set to closed. The same thing if no partial payment had been created and you delete the rebate agreement you would get a 0.00 value final settlement.
Hope it helps
Kind regards
Brian
↧
↧
Re: Fixed Value Date - Billing Document
Predominantly, this Fixed Value Date would be entered manually in Sale Order. So first check the related sale order for change log by executing VA02 where from top menu bar, click on "Environment > Changes". If you feel that system has fetched the Fixed Value Date automatically, then check the condition record in VK12 for that condition type where if you click the "Additional data", you can see this field. If any value is maintained, then from here only, system would be fetching automatically.
G. Lakshmipathi
↧
Re: Rebate Agreement (Accounting Entries Confusion)
Thanks Brian,
I will get back to you on this by checking my accounting entries.
Regards,
Imran khan
↧
Issue in transferring inactive shipment cost condition to SD billing
Hi Group
In our shipment cost pricing procedure some conditions may be set as inactive due to subsequent conditions. For the inactive conditions indicator is set as Y...i.e KINAK=Y(Inactive because of subsequent price). This works as intended.
However when conditions are transferred to SD billing, inactive conditions in shipment cost document are transferred/copied as active conditions and KINAK is not equal to Y.
This inflates the shipment cost in billing.
Any thoughts on what might be wrong here..
Many thanks
A
↧
