The Infosys global supply chain management blog enables leaner supply chains through process and IT related interventions. Discuss the latest trends and solutions across the supply chain management landscape.

« The Pit Stop - An Agile Supply Chain | Main | Automotive manufacturers of 2009: Numbers convey their Supply Chain behavior »

...SAP SRM 7.0 is here to stay, available to Leverage your SRM footprint: “The Implementation: What's the sandwich filling? ” – Part 4

In my previous Blog, I discussed about the Roadmap and the project kick-off, in this blog I would like to elaborate on what we actually crafted, “As a Solution for Plan Driven Procurement” and also the future functionalities fitment into the procurement landscape.


The out of the box requirements were funneled into a “product backlog”, there were simply “zero” developments that were in scope, since we used BADi’s in SRM to actually work over the vanilla functionalities that needed to be customer business driven.
In the Plan Driven procurement implementation, we actually went ahead and configured the system to over-ride the base functionality of Extended Classic to make it behave like a Classic deployment.

The Plan Driven model process flow implemented is explained below in the figure.

Plan Driven model process flow

Typically, the Plan Driven process is crafted on the Extended Classic framework, so the Purchase requisition that is routed into SRM from ERP will have to be fulfilled from SRM.
This brought in 2 big challenges
1)      Make the Purchase Order Changeable in ECC, this doesn’t happen without implementing a BADI since the system pushes the PO as an ECDP SRM Purchase Order, we made this modifiable in the ECC side
“Ask me how; I’d be glad to explain”
2)      Contract Compliance : The SRM Central Contract No -> Replicated as a Backend Contract wasn’t possible out of the box since we made the Purchase Order Modifiable, we worked around this too
Finally, we crafted the process that brings benefit to the client via the Strategic Sourcing Process (RFx – Bidding) coupled with Downstream Contract Management to drive contract compliance specifically for Direct Materials that do not have a valid source of supply for a plant that needs it.
In the days to come, the MDM Catalog will replace most of the maverick procurement channels focusing to curb it through decentralization.
The future aim is model SAP E-Sourcing into the application landscape to drive the eSourcing / CLM Auctions from the SAP SRM sourcing cock-pit, since there is no standard integration of SAP E-Sourcing with SRM, this makes it more interesting and challenging.
The Sourcing team also wants to get greater control of the procurement processes to eliminate Sourcing and Procurement project management currently managed via disparate spreadsheets and emails and folders.
…we will empower them with the activation of the Category Management functionality in SAP E-Sourcing.
All in all, the entire Procurement Portfolio of the SAP SRM suite will be blessed with the Business Process cutting across each of these applications, diligently.
Lastly the process instrumentation which is the Business Application Monitoring coupled with BPM will sit on the entire process to give a greater control to the “Procurement Folks” to monitor the efficiencies.
…Soon, we will look into SRM Analytics as soon as we have enough water to wade in….
Let me know if you’ve implemented SRM PDP in a way we did, or have a more efficient experience in your approach, I’d be glad to connect.



Hi Tridip,

I am interested how you made the ECC PO changeable while using extended classic scenario.

Thanks a million

Hi Tridip,

Would you please share how you made ECC PO editable in backend ECC in extended classic?


The ECS PO can be made editable in SAP, by controlling the field EKKO-STATU in the backend PO.
This can be done by implementing BBP_PO_INBOUND_BADI, method BBP_MAP_BEFORE_BAPI in SAP. here the coding can be done in such a way that for a particular PO document type or other criteria -the field can be changed from K (Purchase Order from BBP) to 9 (Enjoy Purchase Order).

Once this is changed to '9', it can be changed in SAP backend. But the disadvantage is that these changes will not be synched back to SRM PO.

Hi Tridip,

Is there any way to make the EXTR shopping carts (i.e PDP generated shopping carts) to send for SRM Process controlled workflow. If you have a solution, please help me.

As you know we cannot use the classic scenario on SRM 7.0 in case of direct material. However, client wanna have SUS integration, what is the best practice to have procurement of both direct and indirect?? for using MM-SUS, we have to implement the simillar approach you described??

Post a comment

(If you haven't left a comment here before, you may need to be approved by the site owner before your comment will appear. Until then, it won't appear on the entry. Thanks for waiting.)

Please key in the two words you see in the box to validate your identity as an authentic user and reduce spam.

Subscribe to this blog's feed

Follow us on

Blogger Profiles

Infosys on Twitter