cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Cost Center Upload - Error

EricAlo
Participant
0 Kudos
177

Hi,
I have attempted to upload the cost centers using the standard migration template but got this error:

EricAlo_0-1762227069215.png

What I find odd is that there was no error during the simulation but on the actual load they system allowed to upload 10 cost centers.
I can't find anything that stands out when I compare those 10 cost centers that were loaded vs those that fail.
What's even stranger is that I'm able to repeat the same behavior 3 times.  I reupload the file, simulated with no errors and the system allowed me to load the next 10 cost centers and the rest failed.

Here's a screenshot of my CC template:

EricAlo_1-1762227350183.png

Following the error message, I created another CC Hierarchy with sub-node and used it but it's the same behaviour.

EricAlo_2-1762227479715.png

EricAlo_3-1762227527720.png

Did I miss any configuration?

Thank you.



Accepted Solutions (0)

Answers (2)

Answers (2)

IreneLiu
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi @EricAlo 

One supplyment for Chuma's post. It seems that you are using the staging tables approach. Here is a document for this object.

SAP Help Portal - CO - Cost center
=>

Hierarchy Area 

Cost center groups entered in the KHINR/Hierarchy area field must be assigned to the standard hierarchy. If this is not the case, the error message KS 070 - Area <XYZ> cannot be used here. is displayed.

See also Cost Center Standard Hierarchy.

Best regards,
Irene

Chris1973
Active Contributor
0 Kudos

Good day @EricAlo 

Thank you for your question.

Have a look at these references, they provide more detailed guidance:

CO - Cost center, Cost Center Hierarchy, Cost Center Group, Controlling Area.

In public cloud, when your cost center references a hierarchy node or controlling area that is not properly linked, the system triggers that Area 1 cannot be used here error. The reason is, in public cloud, the simulation validates format and mandatory fields only. The actual migration checks controlling area, company code, and hierarchy node consistency. The 10 cost centers that succeeded likely matched the valid controlling area while others did not.

To summarise, the error is caused by inconsistent controlling area or hierarchy node assignment. Ensure that:

  • The controlling area is correctly assigned to all relevant Company Codes
  • Make sure you use the Root Standard Hierarchy Node
  • All validity dates align across hierarchy, controlling area, and cost centers.

 

Let me know if you have further questions.

 

Best regards

Chris

EricAlo
Participant
0 Kudos

Thanks for the reply Chris.
I was able to get pass the error by changing the value from 1 to 1~.
Thanks