error KI 280(create cost element for GL account) while converting PR in PO

[Former Member]

Hi Experts ,

When we create a sales order with an item of item category (TAS)(Third part sales) a purchase requisition is automatically created and these requisitions pick a G/L account which is defined for third party sales

We have been using this G/L account for third party sales and never defined this account as cost element.

We do not want to post the charges in to controlling , is this possible for us to correct the error without changing message control?

Now when we convert such purchase requisitions in to a purchase order system gives an error "define G/L account 60100071 as cost element".

Earlier we have been creating PO's from PR's with same GL account.

I am new to this module and will appreciate if can get some documentation on account determination and posting of charges at my personal email <deleted by moderator>.

Any help in this regard will be appreciated,

Thansk & Regards

Anand Tripathi

[former_member1145826]

Hi

You getting Controlling Area xyz Does Not Have a Standard Hierarchy – Error Message No. KS055---

then you go to T code OKKP----click on positions---give your own controlling area---enter---double click on your document--check your standard hierarchy if not assigned then you entered manually H1 and Save it. then you goto create new cost center

[Former Member]

Nothing much helpful has been received from forum.

[Former Member]

Hi Anand

do not change the message to be able to temporarily correct this error - cos this will lead to further problems later

the reason u get this error is cos this is a scenario where the setting tells the system it is made inhouse, so it wants to cost it -

this setting is maintained on the Material master, MRP 1 view - material group field - if u have a PTO there, usually the system things that the item is going to be produced in- house, therefore this error

if u take this off, it should be fine

hope this helps

Rukshana

[Former Member]

HI,

One of the reasons why SAP is giving you this error message is because in case of TAS, the sales order itself becomes the CO object. You can't avoid making a posting to CO in this scenario.

Regards

[Former Member]

Hi Akhilesh,

Thanks for your reply.

what exactly determines whether it should post to a CO or not, like when it should search for CO object and when it should not.

In our case earlier we used tocreate TAS with same G/L account and it never asked for a CO object, problem started after a hot pack was implemented.

We ahve checked SAp note 356094 but we never defined message KI280 as error message in OBA5.