What I did was to delete the whole structure and create it from scratch. I had similar case as yours and you need to make sure that the rfc user is mantained in the org. plan under a company code. Please let me know if it works.
No I haven't but we do not use SUS. I am really lost as in our Test and Prod it works fine. I read also other threads and there you mention that local p. org. and p.grp. must be created but in our case it was never needed. Now in DEV the transfer doesn't work and I am not sure what is the proper config. Maybe you will be able to clarify it for me as I have no clue why we need this local structure?
The point is that I was configuring all the systems and I did not do any settings there. I checked it now and it's also empty in prod. I am thinking about deleting the whole org. structure as I think it is the reason. We changed the backed some time ago and it never worked properly since then. I would like to start from scratch with the org. plan but have no idea how I can delete current business partners(purchasing groups) and the rest of the structure to have a fresh start.
The only thing we have is channel backend node with RFCUSER but we have no local porg. or local pgrp. We only have one purch. org. referring to backend and several p.grp. referring to backend.
What is use of local things if we only use backend?
It depends on which type of reqs are moved as there are two scenarios - procurement of external requirements and plan-driven procurement. The first uses the entry channel and makes sure, that reqs with account assignment are moved. The second use the local elements and takes care of moving direct material reqs. But the first scenario also assumes that the local elements are there and therefore requires them.
As of SRM40, you don't have to use a local Porg anymore for ECS scenario. For thsi you have to implement OSS notes 944918 and read consulting note 946201.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.