FI postings with Statistical WBS and Cross company cost center is not allowing

[Sumanth9]

Our Business is currently on S/4 HANA On-Premise and is moving their subsidiary with multiple company codes to S4H Cloud Public Edition. In On-Prem for the business transactions single statistical(S) WBS element is being used across the company codes as Company Code is not mandatory for statistical WBS.

In Public Cloud as the Responsible Cost center is mandatory input for Project/Project element which in turn derives the Company code for Project/WBS element as a standard behavior and is allowing postings to the respective company code and related cost center only.Business concern is this limitation in cloud will increase the statistical projects master Data volume exponentially for multiple company codes and also involve data maintenance.

System does not allow the cross company postings with statistical WBS of Company A to Cost Center belonging to Company B and gives below error message:

KI302 : "CO account Assignment object CTR XXXXX belongs to company code XXXX, not XXXX"

Is it possible to convert the error message to a warning for final postings with configuration or development change request?

Best Regards,

Sumanth

[Jeremy_Deo]

Hello dear user,

And thank you for asking your question in the SAP Community blog.

You're absolutely right to be concerned this is a common issue when moving from S/4HANA On-Premise to Public Cloud.

In the On-Premise world, you had a lot more flexibility. For example, using a single statistical WBS element across multiple company codes worked fine because the system didn’t enforce company code checks for statistical objects.

In S/4HANA Cloud Public Edition, SAP has tightened the rules to make everything more consistent and secure across the board.

One of those rules is that all controlling objects (like cost centers and WBS elements) need to belong to the same company code. That’s why you're getting the KI302 error.

And unfortunately, in Public Cloud, you can’t just change this error to a warning like you might have done in On-Prem with message control (transaction OBA5). SAP doesn’t allow that kind of modification in the cloud, and there’s no workaround through development either. It's simply not something customers can override in this environment.

I hope this answers your question.

Best regards,

Jeremy

[Sumanth9]

Thanks Jeremy for your response.Are you aware or come across any KBA note or documentation on this subject?