on 03-08-2006 8:17 PM - last edited on 02-04-2024 12:26 AM by postmig_api_4
Hi
We are on SRM 4.0 classic scenario and backend as ECC5.0
We have a requirement where PO approval is to be done in backend R/3 system, only for POs which are created from SRM sourcing cockpit and R/3 manual POs. POs that are created from catalog based shopping carts need not undergo PO approval in backend system.
Note : All shopping carts will be approved in SRM workflow approval process before creating follow-on doc in backend system.
My questions
1. How the workflow will recognise the PO from sourcing (SRM) and manual PO created in backend R/3(not through SRM). Because we want PO workflow to be triggered only in R/3 system for these POs.
2.Is the workflow development same for SRM and R/3 system or any difference is there. I mean in R/3 also do we have n step approval BADI?
Please give me your suggestions on how to proceed on the above.
Thanks
Jagdish
Hi Jagdish,
1- You can use document type to distinguish SRM PO from R/3 PO.
Kind regards
Yann
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Jagdish
I took the hypothesis that you use extended classic scenario :
Implement BBP_ECS_PO_OUT_BADI. This BADI is active when the Extended Classic Scenario is switched on, while PO data is transferred from EBP to R3.
Since the R3 PO does not have field for catalog id, the EKKO- BEDNR (Tracking Number) field (that's an example) can be used to store this information. In this BADI all items are identified and their tracking number field is populated with your catalogue ID.
You can take this a starting point.
Hope this helps,
Kind regards,
Yann
PS : Please do not forget to reward )
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.