Account should not hit for a condition type

[Former Member]

Dear All,

I have a requirement, Accounts should not hit for a condition type if Sold to Party and Other Partner function( in my case it is AGENT)  is different, and if both are same then it should allow to post the value to accounts.

please suggest me What could be the best approach to achieve this.

Thanks,

Chandra

[anita_patil3 · Accepted solution]

Hi;

I would suggest to create a routine in KOFI -  account determination access sequence and assign against the access in which the customer field is used. In this you need to code to check and compare the partner functions sold to party and agent  are same or not. If yes system should allow to post with that access else  not. System automatically will select the deferent account with next access.

Hope this will help you.

Regards;

Avinash

[jobis · Accepted solution]

Hi Avinash,

I dont think the requirement is to have a different account for accruing the value. The value should not be posted to any account if the partners are different.

Only option is to make the condition behave as "statistical" during such cases.Even if you do not give an account for posting (ie, the account determination fails,) then the system will give an error for the entire invoice and posting of entire invoice will not take place.

I dont think routines in account determination will help. look for options to make the condition behave as "statistical' during this particular scenario alone.

Jobi

[Former Member · Accepted solution]

Dear Jobi,

Let me check this option with ABAPer (Skipping "Statistical" check).

Regards,

Chandra

[jobis · Accepted solution]

Chandra,

Dummy GL is a good idea. But you have to consult the business as well as the FI guys for accessing its feasibility.

[Former Member · Accepted solution]

Jobi,

If I get idea that where can i assign that Dummy G/L. then I can talk to business team and FI core team.

Regards,

Chandra

[jobis · Accepted solution]

CHandra,

Dummy GL is not a standard functionality in SAP. its like normal account assignment and determination. It has lot of implecations in FI side. So its the call of FI guys

[Former Member · Accepted solution]

Thanks Jobi for your help.

Regards,

Chandra

[former_member182378]

Chandra,

In line with Jobi and Ravi's posts, when you make an amount statistical, then it will not impact the net value in the billing document. Is that ok with business / client?

If yes, then you could implement this solution. First, you need to understand that is ok for the client.

TW

[Former Member]

TW,

Yes Its been resolved, the value should not add to net value  and It should not post to GL accounts. We made it Statistical by checking partner functions.   Thank you all for your support.

Regards,

Chandra

[Former Member]

TW,

One more observation is, when you check "Accrual" in V/06 for a condition type, the value of the condition type will not be added to Net value even if  "Statistical" is not checked in V/08,  correct me if i am wrong.

Regards,

Chandra

[jobis]

Dear Chandra,

Thanks for the update.

Your observation is correct, in your last post above.

Please close this question as your requirement is met.  

Regards

Jobi

[jobis]

Hi Chandra,

Has your requirement met?  Keep us posted.

Regards

Jobi

[Former Member]

Deal All,

I am working on Creating a new routine for assigning in Access Sequence. I will let you know the result.

Thanks,

Chandra

[jobis]

Hi Chandra,

What really is your requirement..?  Do you want a value to be determined/entered against the condition type and if the partners are different , then it should become " statistical" in pricing, so that its not posted to accounting..?

Or, you dont want a value determined/entered against a condition in your sales order/invoice pricing if the partners are different?

If its the second case, then solution is in above posts.

If its the first case, then avoiding the determination of revenue acct may not be a good solution as it will give error while positing the invoice, posting will not happen for the entire invoice. Best is to have a solution to make that condition " statistical " at that point. KOMV_KSTAT, should get checked.

Regards

Jobi

[Former Member]

Dear Jobi,

the requirement is,

I have a manual condition type which NOT 'statistical' and the condition value should go to Accrual Key if SP and Commission agent(other partner) is same, other wise the value should not go to Accrual Account. Please note that there is NO Account Key is assigned for this condition type.

Thanks,

Chandra

[former_member220617]

Dear Chandra ,

Create price in VK11 with the combination of sold to party and agent combination , so that price will flow in the sales order if this combination comes, if other combination comes price will not come in pricing and it will not flow to accounts .

Regards,

C.B Reddy.

[Former Member]

Dear Reddy,

This is a manual condition type. suggest me

[ravi_kumar100]

Hi,

For manual condition types it can be achieved through routines. Discuss with your ABAP ér as rightly said by TW.

Regards,

SRK

[former_member182378]

Chandra,

This is a requirement (if xyz condition is fulfilled, then go further; OR else stop).

Your condition table is having fields, one of them is price condition type. For this table, set requirement (routine), in the access sequence (Revenue account determination).

To create the new routine, give the functional details to the ABAPer. Then assign that routine to the condition table, in the access sequence. And test.

TW

[Former Member]

Dear TW,

Thanks for reply, in my case, the value of a condition type should not accrue(Accrual Key: ZOC)  and there is no account key assigned for this condition type. Condition table:  Sales org./AcctAssgGr/AcctAsgnmt/Plant/Acct key,   so i will create a routine by checking Accrual key and Partner functions. suggest.

Thanks,

Chandra

[former_member182378]

Chandra,

Your requirement is if condition is satisfied (SP and other partner are same) then value should hit a G/L account.

This requirement is not related to accural. (or accrual key in pricing procedure)

Price condition can be entered manually in the sales order, this is ok and does not impact amount hitting G/L account.

Read the theory of Revenue account determination. Then this functionality will become clear.

TW

[Former Member]

Hi TW,

We have created a new routine and assigned, if both the parties are different, it is coming out of access sequence due to this the whole document value is not able to post to accounting. due to this, it is not allowing to create Accounting document. my requirement is to create accounting document but value for a condition type should not post to GL  accounts. Any suggestions?

Thanks,

Chandra

[former_member182378]

Chandra,

Yes, currently because one value (price or discount or surcharge) is not finding a G/L account, the accounting document will not get created. Every amount (which is not statistical) in the billing document, must find a G/L account, only then accounting document will be created.

If you donot want to make this amount as statistical in the bill, in case - if the partners are different, then discuss with Finance team to make a "dummy" account and post to it when partners are different. By that way, all amounts will find G/L accounts and accounting document will be created successfully.

TW

[Former Member]

Hi TW,

As you said, If I want to assign a Dummy G/L account, Where can assign this, because I have already assigned a  G/L account in which we are posting accrual values if partners are same.

Regards,

Chandra

[former_member182378]

Good question Chandra !

What are the fields of the table where you have assigned the requirement?

and what record you have maintained for this table in VKOA?

Can you try to create 2 records for the same table in VKOA, one with different and one with same partners - both records hitting different G/Ls?

The requirement is not needed.

TW

[Former Member]

Hi TW,

Access Sequence table consist the following fields:

Sales org./AcctAssgGr/AcctAsgnmt/Plant/Acct key

here there is no CUSTOMER field in the table.

Regards,

Chandra

[anita_patil3]

Hi Chandra;

I think you missed my second part of suggestion. If partner function of sold to and Agent differs the routine should not allow to get value from first access but it should not come out of that and should check next access for assigned tables . In this way system will get the GL account from second access.

Hope this would help you.

Regards;

Avinash

[Former Member]

Hi Avinash,

We have only one Table:   Sales org./AcctAssgGr/AcctAsgnmt/Plant/Acct key... at this table level we have all G/L accounts assigned.

I think, As per Mr.JOBI. We have to make condition type as "Statistical"  with program before saving the billing document when there are different Partner functions, so that system will not post the values to Accrual G/L Accounts. I have done testing with ABAP debugger, and yah it is working. and I have check the impact of the changes.

Any other implications or Impact by doing this?

Thanks,

Chandra

[anita_patil3]

Hi Chandra;

You are right the mentioned process can work if only access is there. I do not see any other impact because the logic meant only for this particular situation.

Regards;

Avinash

[jobis]

Chandra,

Dont waste your time. I have given you the proper logic and solutions from my initial posts Here.

Briefly, you have only 2 options, either to use abap program as I suggested to make condition statistical or else use dummy GL a/c. Dummy GL account assignment is possible, for that just go through Revenue acc determination process fully.

Dummy G/l acc, if used, has lot of implications in FI. Normally Business do not go for that. So it may not be an option atall atlast

Regards

Jobi

[former_member184555]

Chandra R wrote:

Hi Avinash,

We have only one Table:   Sales org./AcctAssgGr/AcctAsgnmt/Plant/Acct key... at this table level we have all G/L accounts assigned. 

I think, As per Mr.JOBI. We have to make condition type as "Statistical"  with program before saving the billing document when there are different Partner functions, so that system will not post the values to Accrual G/L Accounts. I have done testing with ABAP debugger, and yah it is working. and I have check the impact of the changes. 
Any other implications or Impact by doing this?

Thanks,
Chandra

Compare the net values in these two scenarios.