Mysterious Account Determination results

[Former Member]

Dear SAPiers,

Account Determination Analysis:

***********************************************************************************************

Cond Msg Description

type

-

---

-

---

-

---

Z100 120 G/L account 0021601003 determined from Account determination type

KOFI

<b>Z100 215 G/L account in document: 0021101033</b>

Access Message Description

-

---

-

---

-

---

10 120 G/L account 0021601003 determined from Account

determination type KOFI

***********************************************************************************************

Although G/L account 0021601003 have been determined by the account determination (1st msg. above; VE 120), It has been substituted, somehow, by account 0021101033 (2nd msg. above; VE 215)

Any idea ?

Thanks!

Harel

[Former Member]

Hi Harel/Jitesh,

Account determination access sequence is a bit different in behavior than pricing access sequence because it is not having an exclusive tickbox for each condition table. An exclusive indicator tells SAP to stop searching for the value if the current table provides the value. Since account determination is not having a exclusive indicator by design, you are facing this problem.

Your first table in access sequence has value, SAP reads the value 21601003

goes to next table and the next value is read, 21101033

could not find any further value and the last accessed value becomes the final value. 21101033

What you can do?

Either you can go ahead and delete the values from the other table in VKOA so that SAP only finds a value in 1 table.

OR

you can create a requirement and tell SAP not to look further if the value is found in the previous condition table. Assign this requirement to all the condition tables except for the 1st one in your account determination access sequence KOFI00.

1st table No requirement

2nd table Requirement

3rd table Requirement

This way SAP will first read the value in table 1, it will read 21601033,

it will go to 2nd table and will read the requirement first, requirement will tell it to check whether the 1st table has value, if the value found in first table, the 2nd table will not be accessed, next table 3 will also behave the similar way and you will get only 21601033.

Your analysis on account determination will show the results log as

Z100 120 G/L account 0021601003 determined from Account determination type

KOFI

Z100 215 Determination not carried out - requirement XXX not fulfilled

Z100 XXX Determination not carried out - requiremen XXX not fulfilled

For writing the requirement using Tcode VOFM, you need to take the help of your ABAP Resource.

Thanks

Kapil Sharma

[Former Member]

hi,

this may be because the records in VKOA wud be chnaged and this doc wud be open (not released to accnting) wen the changes were made. chek in vkoa hte g/l accnt actually hit is teh one for which the records are maintained.

saurabh

[jiteshmehta]

Dear Harel

I am also getting the same kind of problem

Was your problem solved ???

We have added one more access sequence and maintained G/L Accounts for it

As it was in PRD earlier G/L Accounts are still in the system, so when account determination is happening it is giving correct G/L account , but accounting document is getting posted to wrong account (determined by earlier access maintained.)

If we remove the earlier entries in VKOA (of earlier access) then we don't know the impact of it on exisiting transacton

Would be glad if you can share your experience

Regards

Jitesh

[jiteshmehta]

Dear Harel

Have found out the cause

Please refer Note 172692 - Error in the revenue account determination

The problem occurs when fields of the billing header (for example, billing type, field VBRK-FKART) are used as criterion for the revenue account determination and are billed in collective processing.

there is correction procedure given in note

Regards

Jitesh

[Former Member]

Hi Harel,

You can see the account determination that was done in the billing document. You may be having an account determination set up at the Customer / Material account determination grp which may be valid for this document in addition to the account key level and this may be the cause for the system to determine another record for revenue account determination.

Hope this helps.

Regards,

Rohit Zalani