WBS is neither a billing element nor an account assignment element.

[Former Member]

Dear Gurus,

From the migo transaction, Good Issue, Reservation, we're getting the following error message:

WBS is neither a billing element nor an account assignment element. Message no. KD255

Validations previously carried out:

1.The WBS element has ticket the flag: account assignment element. The WBS element is not configured as a billing element.

2. System Status: REL NTUP SETC; User Status: RLSD.

Thanks in advanced.

[Former Member · Accepted solution]

Hi Magno,

as per my opinion we cant do grn for WBS which is not set as acct assisnment. if your project is customer project then you must set that WBS as billing element also because you will do billing for same WBS.

So set the Acct Assignment and billing elements for that WBS and then do migo.

for furthue query reply me.

Regards

Lallan.

[Former Member · Accepted solution]

Thanks Lallan,

Our WBS project is not a customer project, so the billing plan is not maintained. Our WBS element is a capex project.

[Former Member]

To Post anything to any WBS, your account Assignment Indicator should be ticked. You can either do it in Project Profile (OPSA) for all the WBS or through CJ20N manually.

Check the Acct Assignment Indicator for WBSE for which you are actually doing the postings.

Arya

[Former Member]

Thanks Arya

When the Reservation is called from the migo, the WBS Project is loaded instead of the WBS Element, of course the WBS Project has not an Account Assignment Indicator ticked, that's why the system show the error message.

I verified the Reservation and the right WBS Element is loaded for all items.

Do you have any clue why the Reservation is loading the WBS Project instead the WBS Element ?

[Former Member]

The subjetc issue is appearing because the main WBS element is not an "Account assignment element" and this option had not been ticket.

In the project definition, the option "Automatic requirements grouping" was ticket erroneously, in fact, that option never should has been ticket. When the option 'Automatic requirements grouping' is ticket while creating the project definition, after you have saved the project, you cannot change it any longer. If that option is ticket, postings are only permited over the main WBS element.

The error was solved after the option "Account assignment element" was ticket and a notification was sent to the project administrators department so that they don't ticket the option

"Automatic requirements grouping" when the project WBS is created.