on 03-23-2017 2:09 PM
Is that possible to explode BOM with SC stock issue from another plant belonging to different company code? There is a solution where both plants belong to the same company code
https://archive.sap.com/discussions/thread/1616755
When I try to create the special procurment key with withdrawal from alternative plant I get the error No 61 824 "Plants X and Y are assigned to different controlling areas"
There are CO reasons behind, you can find more details in the following OSS notes
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you very much for the notes, especially 1095113 is helpfull. At least it's clear that SAP doesn't support the Intercompany postings between different controlling areas and you could possibly use it at your own risk after thorough CO testing.
When I ignored error 61 824 and created special procurement key like described in note 588396, everything works as desired without further errors or warnings. Now just CO issues should be checked precisely.
Thanks for this interesting information. I have an additional question: how can I trigger IC-Billing in this case?
Requirement's:
(1) SC-Vendor invoice should be payed by the company providing the components
(2) Goods should flow directly to the company ordering (SC-PO)
(3) Intercompany billing between Company A and B in the same controlling area
Thanks Wernher
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Moreover there is a note 120277 - Cross-controlling area stock transfer where the same error was corrected for stock transfer special procurement key. Final conclusion - is that limitation not redundent?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
OK but what is the root problem with different controlling areas, why there is such a limitation? When I create SC order manually and change the plant in components there is no problem, no warning, means the process is possible. It's no problem also to post 543 o MvT from different controlling area plant after Intercompany accounts config in OBYA.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The document in OSS note 205454 does not say the plants must be under the same company code.
The message you get (61824) is a hard coded error message and it is issued because the controlling areas of the plants are different (not because of the different company codes). Multiple company codes can be assigned to one controlling area. In such a scenario you would not get error message when trying to define the special procurement key with a plant which belongs to another company code.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
100 | |
12 | |
11 | |
6 | |
6 | |
4 | |
3 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.