Plan-driven procurement (PDP) or External procurement is one of my favorite area in SRM.
PDP leverage the sourcing capability of the SRM. The Requirements (read- Purchase Requisitions) are created across the system from different module and may not valid source of supply. The Purchase Requisitions can be channeled in SRM as Requirements (similar to Carts) and then sourcing is carried out in the SRM.
The customizing table entry (V_T160EX and V_T160PR) decide (and/or- with BBPK0001) which PR to be pushed in SRM and report BBP_EXTREQ_TRANSFER in back-end bring these in SRM.
SRM 7 offers new features and possibilities if the back-end is SAP ECC 6.0 EHP4 or above.
With EHP 4 new BADI- ME_REQ_SOURCING_CUST provides the collective processing of Requirements in PDP and helps organization to consolidates the requirement coming from different modules (read- PM,PS, CS, SD)./ back-ends in more efficient way after release/approval. The complex service scene is also possible. You can also integrate the it along with MRP - use BADI - MD_PURREQ_POST
PDP leverage the sourcing capability of the SRM. The Requirements (read- Purchase Requisitions) are created across the system from different module and may not valid source of supply. The Purchase Requisitions can be channeled in SRM as Requirements (similar to Carts) and then sourcing is carried out in the SRM.
The customizing table entry (V_T160EX and V_T160PR) decide (and/or- with BBPK0001) which PR to be pushed in SRM and report BBP_EXTREQ_TRANSFER in back-end bring these in SRM.
SRM 7 offers new features and possibilities if the back-end is SAP ECC 6.0 EHP4 or above.
With EHP 4 new BADI- ME_REQ_SOURCING_CUST provides the collective processing of Requirements in PDP and helps organization to consolidates the requirement coming from different modules (read- PM,PS, CS, SD)./ back-ends in more efficient way after release/approval. The complex service scene is also possible. You can also integrate the it along with MRP - use BADI - MD_PURREQ_POST