Skip to Content

Missing G/L account; No G/L account found in account determination type KOFK

Sep 21, 2017 at 03:55 PM


avatar image


I am creating an sales order and it is working fine. However, If I add the WBS element as an account assignment in the sales order line item, I am getting the below error,

"Missing G/L account; No G/L account found in account determination type KOFK"

We have COPA active. If I remove the WBS element from the line item it is working fine.

How to fix this issue?




10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

2 Answers

Veselina Peykova
Sep 21, 2017 at 06:25 PM

If you are a SD consultant - read the IMG help in SPRO->Sales and Distribution->Basic Functions->Account Assignment/Costing. Then discuss with the business how the postings should be maintained.

If you are a consultant, but not responsible for SD - discuss the problem with you SD colleague, show the document and mention the magic word VKOA and let him/her handle the rest.

If you are an end user - double-check whether you are following the right procedure and that your master data is correct, if yes - create an incident in your ticketing system. Before you do that, it will be a good approach to speak with someone from accounting and find out how the postings should look like when a WBS element is assigned in the order and add this information in the ticket.

Edit: if you are an end user and you are responsible for billing or pricing, I would strongly recommend that you ask your local consultant to handle a dedicated training session for your whole team and provide additional training documentation. Account determination logic is a must in any end user raining for billing and pricing experts.

10 |10000 characters needed characters left characters exceeded
Prabu Kaliappan Sep 22, 2017 at 02:16 AM

Hi Veselina,

The VKOA setting is correct. This is an MTO scenario and the WBS is the account assignment object in sales order line item.

Do we need to do anything at the WBS side to overcome this issue?

Appreciate your help.


Show 1 Share
10 |10000 characters needed characters left characters exceeded

In a standard system, when you post without a controlling object, requirement 3 is checked and the posting is performed via some entry with KOFI condition type . When you post with a CO object (WBS, internal order), requirement 2 is checked and the determination searches for KOFK condition type entries. Your tests so far have proven only that the KOFI one is maintained and working.

When you search in VKOA for KOFK and the desired combination on the level you perform determination (e.g. Cust.Grp/MaterialGrp/AcctKey) - are you able to find valid entries?

The usual problems with WBS elements that users encounter, are related to insufficient or missing budget, or that WBS was not set as a billing element, but if I remember correctly, the errors are different and more specific.

If you are able to see the right VKOA entries for KOFK (depending on the data in the billing document), but the system ignores them, I would suspect some custom logic interfering, but I honestly don't know where exactly this might occur and would have probably resorted to debugging.