on 2025 Nov 12 2:28 PM
Hello everyone,
in on premise systems we could assign default cost centers and internal orders using the OKB9 transaction code.
In Public Cloud edition, there are no internal orders but we have instead only the WBS elements. In configuration activity "default account assignment" there is no option to set a WBS element as default.
Also, in manage substitutions/validations rules, there is no target field to change the WBS element.
How can we overcome this issue?
Request clarification before answering.
Hello @panagiotism
Thank you for your question.
Have you had a look at Default account assignment.
The restriction in public cloud is based on factors like Internal Orders not being supported, Default Account Assignment only supporting Cost Centers and Substitution Rules not being able to update WBS fields.
I recommend you assign WBS in the Business process. For example:
The summary is, public cloud does not support default account assignment because it would bypass the clean-core approach by auto-assigning functions. Therefore, WBS must be entered explicitly in the process because it cannot be automatically derived.
Best regards
Chris
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @panagiotism
You are right, the public cloud does not support automatic defaulting of WBS elements. However, you do not need to enter the WBS 100 times. You can assign it once and mass-copy it across items or you can use project-based procurement where WBS is inherited automatically from the project.
| User | Count |
|---|---|
| 17 | |
| 8 | |
| 7 | |
| 6 | |
| 2 | |
| 2 | |
| 2 | |
| 2 | |
| 1 | |
| 1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.