Hi,
I think this could not be explained in one post.
We are using the same above scenario for transferring PS or PM requisition to SRM for approval only.
Lot of conditions are set.
1. Landscape
2. Process -
3. Criteria for transferring and approving PReq’s in SRM should be defined in ECC
for example - The criteria which PReq’s should be transferred to SRM should be defined in a local customizing table XXXXX with the field purchasing organisation, plan account assignment type and update date of PReq.
4. 1st approver selection criteria should be setup in the ECC
5. When creating or updating a PReq item a workflow event will be triggered to start the transfer workflow. The trigger is implemented in the PM and PS BADI workorder_update while saving the PM order or the PS network order. The same event cancels an eventually transfer workflow which just transfers a previous version of the PReq, or waits for the approval result of a previous version.
6. The Release Strategy has to be maintained in the productive systems. Only the release codes will be defined and distributed centrally. The name of the Release Strategy can be chosen locally. It’s very important that a release strategy fits to the values of the purchase requisitions that come from SRM and that go to SRM. It doesn’t matter which release strategy. If no existing release strategy fits to the values of the purchase requisitions a classification of the new release strategies is necessary. Otherwise no classification for the new release strategies is needed.
7. Also need to do MM specific customization , PI related and SRM related.
I think it would be too much to tell everything through a post.
Please ask a specific question then i would be able to help you more.
Thanks.
from RBEI
Snehal