Error in releasing billing to accounting
Dear Friends,
I am facing an error while releasing the billing document to accounting.....error is "only output tax is allowed for acount 175000 9999, 01 is not allowed"......what wud b the reason?.....thanks in advance....
Hi
Go to FS00 and give you company code and G/L account 175000 and check in the control tab wheather the Tax tab is properly maintained or not
Secondly , check for tax condition record you maintained ( say MWST) in VK12 and in VK12 check what tax code you have assigned , If you have assigned tax code 01 then check wheather it is a input tax or output tax .If it is a input tax then change it to output tax by assigning a output tax code
Finally also check in SPRO->Financial accounting->Basic settings->Procedures wheather the tax code is properly maintained or not .I think 01 is a taxcode which is input tax code just check in the
Regards
Srinath
Similar Messages
-
Error- while releasing billing to accounting
Hi Friends,
Trust you are all fine.
As mentioned above on subject ....I am getting an error on biling doc while trying to release it to accounting. Problem is I am unabel to see any LOG notes as system is not generating any log error.
I was going through few related answers in forum .........buit couldnt find any on this particular issue. So, In this situation how should I and where should I look to find out error to resolve.
Many thanks in advance and kindly let me know accordingly.
Regards,Hi
1.Go to VF02 and enter the billing document no after that go to environment -Acct det analysis->revenue accounts
by doing above u will able to find the error analysis in revenue account determination
2.Check the account assignment group in the billing document header header tab and item-item detail
3.Go to VF02 and enter the billing document no and click on release flag then system will show you the error if any or it will realeased to accounts
Regards
Damu -
Error when releasing billing to accounting document
Why we tried to release the billing to accounting document. There is the below error.
Could someone please kindly help?
Message Identification: F5
System Message Number: 358
Output type: E
The Diagnosis is 'This document refers to a document which contains an invoice reference.
The Procedure is 'Enter a different document as the invoice reference'.
Thanks,You might be creating the billing document for a flow where there might be original invoice and/or credit memo also.
So check that the original invoice and/or credit memo has an invoice reference to itself (i.e. the invoice reference = the accounting document number) than there is an incorrect referencing.
Remove this reference via FB02 in the original invoice and/or credit memo and it should work
Regards,
Gaurav -
Error when releasing billing to Accounting
Hi All,
I get the following error when releasing the billing to accounting in T-code VFX3....
Tax code in procedure TAXSL is invalid
Message no. FICORE704
Diagnosis
The tax code entered is not defined in the country for this company code.
System Response
Procedure
Check and, if necessary, correct the entry.
Procedure for System Administration
If it is not an input error, check and possibly change the system settings.
To do this, choose Maintain entries (F5).
1. Check whether the required tax determination procedure is assigned to the relevant country. the Procedure field is in the detail screen.
2. Create a new tax code if required
Pls note that in the error message it does not mention a particular tax code which is invalid, it jus shows tax code in procedure TAXSL is invalid.
I have done the following customization both in FI and SD.
I have maintained condition record MWST both in FI and SD. Maintained all necessary tax codes in FTXP.
Note that in the billing, we enter the condition type MWST in the Header Level and enter the relevant percentage manually. According to my understanding since the condition is maintained at header level there is no need of maintaining condition records through T-Code VK11.Therefore the tax code is not picked from the condition record as its not maintained in the item level.
Pls advice me on how to overcome this error ASAP since its critical.
Thanks in Advance,
MaleeqHi,
Yes I have maintained tax codes in FTXP. but the error message shows that "tax code __ is missing in tax procedure TAXSL". To my knowledge it is not possible to create a tax code "blank"!!!!
I have not maintained condition records in VK11 as we maintain the MWST condition in the Header level. Condition records are picked only from ITEM level and NOT from HEADER level.
Maleeq -
Error while releasing Billing: Assign HD00 (Frieght) Condition type in COPA
Hi,
I am getting the below error while releasing billing document.
Assign condition HD00 type in COPA
HD00 condition type is frieght condition type
Is it good thing if we assign this condition type to COPA value field in KE4I? or we should not assign Frieght condition to COPA?
Please advise
Thanks
KishoreHI Kishore,
To which GL account are you posting this freight condition value? Is that GL created as a revenue element (of category '11'/'12')?
If yes (has to be 'yes', since you are getting the error message), then you don't have a choice but assigning a CO-PA value field in KE4I. The idea here is, if you have created the GL as revenue element, then you intend to take it to Controlling module for further analysis. Thus, making your FI/CO reconciliation easy.
If you do want to carry this value to CO-PA for analytical reporting then don't create that particular GL (assuming you are posting freight to a separate GL) as a revenue element. That said, it does make sense to carry this value to CO-PA and in your present case, you don't have a choice as the message which you got is an error message, which you can't circumvent.
Hope this helps. -
Error while releasing Billing doc to Accounting
Hi all
I am gettin the following error while releasing a Billing doc to FI-
Reconciliation account 240001 or short key 00 is not permitted
The Billing doc pertains to Export sales and the billing Doc type is Export Invoice. However the Customer Recon A/c is defined as 240000 which is for Domestic Sales. A/c 240001 stands for Export Sales. I am wondering why it is asking for the Export Sales Recon a/c. Does this has something to do with Alternative Recon A/c? Should I set an Alternative Recon A/c and check this? If yes, then should it be defined in SD or FI?
If any1 has come across this prob, plzz help me.
RegardsIt is all Fi related, and should be defined by the Fi Consultant.
But by changing the sort key I think your error can be solved. But I don't exactly know your config settings to recommend any solution.
Regards
AK
Please reward if helpful -
Cost Center Error while releasing Billing document to Accounting
Hi SAP Gurus,
Our user raised an issue that when he had released billing document to accounting, the system threw error message
"Cost center xxxx (CO area)/xxxx(Cost center) does not exist on date 11/16/2011". Message No. KI 222.
But the cost center xxxx does not exist in the system at all. The user does not want to create the cost center eirther. Cost center was not entered in Sales order, Delivery and Billing. I have checked 'Default account assignement' (OKB9) settings, Default account assignment in cost element master record and assignment of cost center to sales organization (OVF3). But cost center xxxx was not configured in the above settings. I have checked validations/substitutions, user exits and BAPIs, there is nothing specific to the cost center. This is not a cross-company code scenario. I have made field status to optional for cost center. But still the problem persists. Accounting document did not get generated because of the above mentioned error message. User applied SAP notes 315350. But it did not resolve the issue.
Would anyone let me know 'why the system showed the cost center xxxx that does not exist, while releasing the billing document to accounting'?
Thanks in advance.
Best Regards,
K.S.KHi Friend,
I think this link help for you
Cost center XXXX does not exist on 15.09.2010.
or check the OVF3 -
VF02 error in Release Billing document to Accounting document
Hello SAP Folks,
A sales order (VA01) and corresponding billing document has been posted (in VF01). When I try to release the billing document to Accounting, an error "Incorrect document no. XXXXXXXX. Select the document number between yyyyyyyyy and zzzzzzzzzzzzzz " shows up. When I tried to find error through VFX3, it says, Release incomplete due to "FI/CO interface" Can anyone suggest the missing configuration.
PS: I checked the doc. type RV (Billing doc. transfer) and Billing type F2. They are in different number ranges. and RV is marked external. The number range settings are similar as that of another Company code (where we are able to release billing document to accounting document).
Thanks in advance,
NarayananHi,
Thanks for your suggestions. The issue is resolved by changing the number range for RV document type (though it is still external). I guess this is made external since the Billing document number is passed to FI document number when it is released to Accounting documet.
After the release, both Invoice and Accounting document have the same no. -
Error while releasing billing documents to accounting
i am facing the following problem while releasing billing documents to accounting i.e, taxcode in procedure TAXD is invalid... pls solve it...
Hi,
That means the tax code which you are using is not linked to your tax procedure.
For this Goto T.Code :FTXP
Give Country for which this tax procedure is used.
Next you have to give the Tax Code which you are using, if it is not created in that then it will create that tax code for that country, in that screen you will see all the tax condition types, give your tax percentage to the condition type which you want to use (Say MWST)
Now release the billing document for accounting.
You want face the issue.
Hope this is clear.
Reward if helpful.
Thanks
Praveen -
Getting Error while posting billing into accounting.
Hi All,
Could any one help on this error,i am getting this while posting billing into accounting.
Tax statement item missing for tax code O0
Message no. FF805
Diagnosis
No tax item exists for tax code O0 in a G/L account item. A possible cause is an incorrect transfer of parameters by the application to the Accounting interface.
Procedure
Enter an OSS message.Hi Raja,
We have many FF805 errors reported by customers and the same solution
has resolved the problem. Please note that the SD-FI interface changed
from earlier releases.
In the vast majority of cases, error FF805 occurs because of an error
in your pricing procedure. The previously attached note 112609 explains
in detail how tax codes are transfered to conditions.
The note 400766 explains the checks performed by the system on the Tax
codes:
1. system checks whether there is a revenue line for each tax line.
2. in the reverse case, for each revenue line containing a certain
tax indicator there must be a tax line with this indicator.
If the tax condition has condition value zero and condition base
value zero, then it is not transferred to FI.
If you have revenue lines containing a tax indicator XX, but no
tax line with tax indicator XX, then the error FF805 issues, and
it is justified. => Please check these informations. I have attached
notes for further information.
-> EXAMPLE
If tax condition MWST has base amount zero and value zero; for this
reason it is not passed to accounting. But, according to the
criteria reported by note 112609, its tax indicator EG: A7
has been assigned to the condition EG: ZBR1.
So in accounting there would be a revenue line with tax indicator A7,
but there isn't any tax line with indicator A7 (because MWST doesn't
pass to FI). The note 400766 states situation is unallowed, and error
FF805 is justified.
Thanks and best regards,
Smile -
Release Billing No accounting doc.
Hi All,
I am getting a error when I Release billing .
Error:
No valuation exists for material AA X1
Message no. MLCCS030
this plant is no valuation.
what I need to do to have Accounting document for billing ?Hi tina
Go to MMR-> accounting tab 1, check wheather valuation class is coming or not. If it is not coming assign manually and save the material and then do billing
Secondly go to OBYC and assign the plant to the valuation class
As you did not maintained Accounting 1 tab in for that material , go to MM01 again and give the material name and select the Accounting 1 tab and enter and extend the material
If that view , Accounting 1 is not there for that material type , go to OMS2 and select the Accounting view and save it and then extend the material by selecting the accounting view .
Regards
Srinath -
Error while releasing Billing Document in VF02
Hi,
I am getting the below error while releasing the billing document in VF02. What could be the reason for this?
Characteristic value US does not exist for characteristic WWCST (Country Ship-to)
Message no. KE0C133
Diagnosis
The characteristic "WWCST" ("Country Ship-to") should be posted to Profitability Analysis (CO-PA). When the system checked the entries, it was established that the transferred characteristic value (" US") is not valid in CO-PA.
System Response
The data is not consistent and therefore cannot be transferred to CO-PA.
Procedure
With the function Maintain Characteristic Values, you can add characteristic values to those that are valid.
Thanks
Babu SanHey,
Nicolas' reply is correct.
And in case you could not maintain the relevant table and want to undo the
check against the check table for some chars you have to remove the check
table from table TKEF and afterwards regenerate the check routine RK2FGPKE.
I will explain this more in detail on the basis of an example: imagine you want
to get rid of the check table for char WW123. You must then proceed as follows:
1.) Remove the entries for fields CHTAB and CHFIE from the TKEF record
for WW123 (that means FIENM = WW123) so that these fields are after-
wards initial in table TKEF for the WW123 record.
2.) Execute function module RKD_SHORT_TEXT_GENERATE for APPLCLASS = KE
so that program RK2FGPKE is regenerated.
But please be careful about this workaround and test it throughly in your DEV or QAS
system before apply in PRD system.
Best Regards
Young -
Release billing to accounting incomplete
we run release billing documents for accounting for F2 billing (delivery related billing), it shows incomplete due to fi/co interface, may I know how to resolve, thanks
Hi Jolin
The Usual cases will be as rightly said Jho Posting Period issues or Issues related to GL Master data.
if it possible please attach the screen shot so that we can analyse furthur.
Mahesh -
Error while release Billing document into Accounting -Help me
Hi,
While releasing SD billing document into Accounting,i am getting the blow error.Please advice me
Valuation with material cost estimate: error with product "000AA696"
Message no. KE350
Diagnosis
In Profitability Analysis (CO-PA), the system tried to valuate a line item using the current standard cost estimate.
In order to determine the current plan period, the system needs to read the valuation segment of the material master.
The system has found that the current plan period is not filled forproduct "000AA696" in plant "OB01".
Display material (View: Costing)
The system looked for the material cost estimate using costing key "YG3", as defined in the Customizing settings for CO-PA.
System Response
The document cannot be processed.
Procedure
Contact your system administrator.
Thanks
SunithaHi Sunitha,
Please check your settings in KEPC. Check which costing key you have assigned to your plant. Also check which rule you have set for the costing key. For example if you have assigned "current standard cost estimate acc. to entry in mat. master" then check here is no current standard cost estimate for material.
Regards,
Abhisek -
Error F5742 - While Releasing Billing for accounting
Hi,
We are getting an error F5742- Break down of hold back/retainage pay is allowed for only subledger accounts while releasing a billing document for accounting.
We are using installment payment terms for the billing.
we are not sure why system is trying to split the billing amount other than reconciliation accounts. One observation is that, we have duplicate line items in the billing.Not sure if this is causing the issue?
Please share your thoughts.
Thanks,
Mano.HI,
I have identified the reason for the error,
These billing documents are created with a billing type FCR - NF Consignment fill up and in this case the invoice not getting charged to a customer account instead it is charged to GL account.
Since an installment payment terms YL33 has been used on these orders, system is trying to allocate the installment payment to the GL account and it is giving an error since it is not a sub ledger account.
we are changing peyment term on the sales order to a non-installement one.
Thanks,
Mano.
Maybe you are looking for
-
What cable do I need to hook up a mac pro to a composite tv?
I have a newer version of the Mac Pro that has the Thunderbolt connection. I want to connect my laptop to an older tv that contains composite inputs. What type of cable do I need? I already have the thunderbolt-->VGA adapter, however, the TV does NOT
-
Palm Zire M150 and Windows 7 64-bit
This worked fine with Windows 7 32-bit, but not on Win 7 64-bit. Then I found this thread: http://forums.hpwebos.com/t5/Windows-HotSync/64-Bit-Palm-Desktop-Drivers-are-HERE/m-p/337516/message... I followed the instructions exactly, including the bi
-
Database Control in Oracle 10g
hello eveybody i have got oracle10g installed on windows 2003 machine.i have two instances of oracle and two databases.now from the Database Control i am able to login to the default instance i.e ORCL. now i want to login to the other instance that i
-
How to select usr_login and him resource, it resource, login in this resource OIM
Hello im need help in how to select in database sql usr_login and him resource, it resource, login in this resource OIM&
-
Add MATNR to 0FI_GL_4
Hi Experts, We are trying to modify the 0FI_GL_4 extractor to pull in Material Number information. We understand that in this case MATNR field should be appended through CI_BSIS after reading some of the posts. We tried following approach, 1. Create