cancel
Showing results for 
Search instead for 
Did you mean: 

Problem in Save the Billing Document

Former Member
0 Kudos

Hi,

We have a problem while saving the Billing Document i.e.

Document 83034087 saved (error in account determination)

Message no. VF051

when we saw it;s Revenue accounts, found there -

Condition type............Message.................Description

ZM05............................121.......................No G/L account found in Account determination type KOFI

Access Message Description

08 121 No G/L account found in Account determination type KOFI

10 121 No G/L account found in Account determination type KOFI

20 121 No G/L account found in Account determination type KOFI

30 121 No G/L account found in Account determination type KOFI

40 121 No G/L account found in Account determination type KOFI

50 121 No G/L account found in Account determination type KOFI

Plz guide...

Accepted Solutions (1)

Accepted Solutions (1)

Lakshmipathi
Active Contributor
0 Kudos

Go to VF02 item condition tab, block the condition type ZM05 and click on blue lens at bottom left so that system will show the tax code.

In normal circumstances, you can also see the relevant G/L Account in this screen but from your comments, it seems, the settings are missing in VKOA.

thanks

G. Lakshmipathi

Answers (2)

Answers (2)

Former Member
0 Kudos

You need to do GL determination in VKOA. For more information - pls. search forum or google with the error message.

Thanks

Former Member
0 Kudos

How can i know about GL determination means in Billing document, which GL is assigned...

Plz clear

Former Member
0 Kudos

For G/L determination do the following:

go to T.Code VKOA. Your have 5 options here. You need to know what is your business process clearly for this.

The normal G/L determination is done as follows:

Chart of accounts + Sales Org + Account Assignment Group: Customer + Assignment Assignment Group:Material + Account Key

So check with your FI guy which chart of accounts have been defined for your company. For your customers what are the account assignment groups you are using? Check this in XD02, sales view, billing tab.

Then check the Material account assignment group in MM02 in Sales Org 2 view.

Under application V and the above mentioned combinatinos check for condition types KOFI and KOFK what G/Ls are assigned.

This should resolve your issue

Former Member
0 Kudos

Hello Anil.Sap321,

Your problem has to do with ACCOUNT DETERMINATION.

Step 1: Check which account determination procedure is assigned to your billing type i.e. SPRO>SD>Basic Functions> Account Assignment/Costing>Revenue Account Determination>Define and Assign Account Determination

HINT: normally, this is KOFI00 in standard sap

Step 2: Check the Condition Types in your account determination in the control data in the same path as in step 1 for the Definition (e.g. KOFI, KOFK)

Step 3: Check your accesses e.g. for KOFI (this should correspond to your VKOA tables). Here, you can see the sequence in which your accounts are determined. Plus, at field level you can see where the data are taken from and then you can check your master data etc. during troubleshooting.

Step 4: Identify in which combination your G/L should be in and you or your FI counterpart should configure the G/L in the designated VKOA table (transaction VKOA).

TIP: To know which G/L account you need to input, you need the help of Financial guys as different companies have their different set of G/Ls or Chart of Accounts.

Step 5: When this is configured in your VKOA, you can re-test. Look at your Revenue Account determination analysis to see if your "access" in which you made your VKOA entry is successfully read during account determination.

NOTE: The G/L you or your FI contact have configured must exist in the Company Code involved in your accounting process.

Good luck and let me know if this helps you,

Eva

former_member183879
Active Contributor
0 Kudos

Hi,

It is anyway creating the invoice document. And it fails in the accounting document creation as account determination is not properly configured. In such scenario, this is the expected behaviour.

You have to coordinate with teh FI guy in your project, and assign the correct GL account in VKOA for the prblamatic combination. Once you do this, this problem will not come up again.