cancel
Showing results for 
Search instead for 
Did you mean: 

it possible to post to different g/l accounts one condition type( same amount ) withe the help of account keys

Former Member
0 Kudos

Dear sd gurus

    one condition type amount is 400 ,is it possible to post to different g/l accounts ( same amount ) withe the help of account keys

plz explain how to do setting

Accepted Solutions (0)

Answers (6)

Answers (6)

Former Member
0 Kudos

Hello,

     we have the same requirement when returns take place. G/L account depends on years of sale and return documents: the same year -- 1, different -- 2. We made it by means of

account determination, but with adding a new field to an account determination table

(type of returns).

Thanks,

     Evgenii.

former_member182378
Active Contributor
0 Kudos

Evgennii,

Could you please clarify, are you saying that for different criterion (i.e. same year, different year), the same value (of one condition type) is posted to different G/ L accounts?

But the OP is asking ("every time") a value of a condition type should be posted to two different G/L accounts.

Is your explanation / suggestion in line with the OPs business requirement?

Thank you, in advance!

Former Member
0 Kudos

T W,

     you are right.  i understood the question incorrectly.

My apologies.

greg_ashe
Discoverer
0 Kudos

Hi Venu,

You can post to multiple GL accounts but not using a single condition type, what controls the posting is the pricing procedure.

This works by posting all the revenue to the GL account and then the accruals remove the portion of the revenue from the GL account and post it to the accruals account.

To configure

If you look at the control data for your pricing procedure you'll notice a column on the far right called Accruals, this is what you need to harness.

1. Define a condition type to use for the accruals.

2. Define an account key to use for accruals (under revenue account determination)

3. Place the accruals condition type in the pricing procedure with the accruals account key in the accruals column

Next Step

In your account determination configuration you'll note that your define a determination to a GL account, there is also a provision account beside this.

4. VKOA - Define a determination using your accruals key, ensure you maintain the GL account and the provision account.

5. Ensure you create a condition record for the accruals condition type, this will be based on whatever accrual calculation you determine - % of sale, fixed price etc

Hope this helps

former_member182378
Active Contributor
0 Kudos

Venu,

Like Jyoti, I too request you to explain the "thought" or business requirement behind this requirement / development.

In order to understand & discuss the "logic and correctness" of this requirement, please comment on below scenario:

In billing document, Price is 100USD, this shall be posted to a G/L account.

Meaning customer has to pay 100USD.

If you post 100USD in two different G/L accounts, would that mean that customer would have to pay 200USD (in place of 100USD)?

The billing is of 100USD, asking the customer to pay double is incorrect.

Why would you want to do that?

jignesh_mehta3
Active Contributor
0 Kudos

Hello Venu,

As you already know in SAP Standard GL Account is determined based on Chart of Accounts + Sales Orgn + Customer Group + Material Group + Account Key.

Now hope you also know that this GL Account Determination is based on Consition Technique (just like Pricing). Thus you can create your own GL Account Determination criteria.

At some client-sites I have seen Sales Document Type being used a one of the GL Account Determination creteria. Thus you can define you own Condition Table & Access Sequence & maintain seperate GL Account as long as one of the selection creteria is different.

Thanks,

former_member182378
Active Contributor
0 Kudos

Jignesh,

Your post does not address the OP's question.

Venu is asking the "method" to post a value of a condition type to two different G/L accounts.

(e.g.Price = 100USD, in the billing document, to be posted to G/L accounts 1 and 2)

Your post describes how Account determination works.

jpfriends079
Active Contributor
0 Kudos

Venu

Can you elaborate the purpose of posting one amount to different GL accounts? Or for which scenario you are facing this?

Regards, JP

moazzam_ali
Active Contributor
0 Kudos

Dear

I don't think so this is possible in standard because you can assign only one account key to one condition.  You can do this by creating separate condition type and account key or with some customization. ABAPER can put some BAPI on posting of amount to some specific G/L.

Thanks

former_member182378
Active Contributor
0 Kudos

Moazzam,

I agree that "copying the value of a condition type" in to another condition type, with the help of field "From" in the pricing procedure; then posting the value of the first condition type to G/L account 1 and posting the value of the second condition type (having the same value as of the first condition type) to another G/L account 2 could satisfy the requirement.

ABAPER can put some BAPI on posting of amount to some specific G/L.

Could you please explain why ABAPer....BAPI would be required?

Using / configuring with (standard) condition technique w.r.t. Account Determination can satisfy posting in some specific G/L account.

moazzam_ali
Active Contributor
0 Kudos

Dear Sir

You have explained the whole process how to copy and post in two G/Ls. This is the standard way. We consultants prefer always to follow standards and not to go for some ABAP customization. But sometime the client or operation team don't agree for out suggested standard solution and we have to go for ABAP in worst condition. In short I have shared that in worst condition ABAPER will be required for this. But preferably we should do it in standard.

Thanks

former_member182378
Active Contributor
0 Kudos

Moazzam,

I agree with your comment:

But sometime the client or operation team don't agree for out suggested standard solution and we have to go for ABAP in worst condition.

Ultimately it is the decision of the business / client!

And some times they want to go the "coding" route.

Thank you for your reply!