SAP SRM and NetWeaver technology

SAP uses the numeric based naming convention nowadays and moved away year based conventions (for example NW 2004s). SAP NetWeaver is the foundation for the SAP products and recently evolved too. Many customers would be having quite complex landscape where SAP Business Suite applications – ERP, CRM, SRM, SCM, PLM and industry specific products would be installed. SAP provides the rules based approach to check the dependency for the SAP SRM upgrades. Please visit the SAP marketplace for details.

SRM and enterprise portal

New SRM uses the enterprise portal with webdynpro (WD) technology. New WD makes easy for tailoring the look and feel of the enterprises portal in more simple way.

SRM and industry specific solution

SAP offers the two flavours of the SRM - normal and industry specific - SRM PPS (Public Sector Procurement). SRM PPS is targeted for the public sector companies and government agencies as these enterprises have very specific requirement.

Why SRM ? and well why SRM 7 ?

Well, I am core SCM chap and believes money saved in purchasing is as good as increasing the sales!
Nowadays the organizations are supply chained in complex network and needs its strategic buyer to concentrate on strategic purchasing and increasing supplier stability (on-time delivery, quantity and quality deliverables and other factors). Many regulatory compliance must be adhered (particularly for public sector companies). Approvals and Payments should have auditable trails.
New emerging markets and technologies help purchaser to get better in market.
SAP offered SRM (EBP - Enterprise Buyer) which enables employee (internal customer!) to put the purchasing requirement in special channel. As solution grew, the offerings of SRM and integration with other modules became strong.
New SRM version 7 is based on SAP's EHP (Enhancement Package) technology and offers well integrated solution (if its SAP ERP then its one of the best possible integration). There are many features which organization can explore.

# SRM receiving

As the SRM majorly supports the indirect procurement (cost object assigned) for consumption. It very crucial to identify the receipts is delivered to requestor. Hence, the address should to be updated in these electronic requirements.
If you are using the central goods receipt point then special attention should be given to receiving person!

# Redistribution of the workload

Sourcing cockpit allows purchasing manager to re-distribute the workload- where they can manually re-assign to another purchasing or BADI can be used to (BBP_PGRP_ASSIGN_BADI) automate the re-distribution.

# Sourcing !

Till the recent release of Supplier Relationship Management (SRM) Sourcing has got more options under it cap. The sourcing as been more buyer centric now. Until release of SRM 5, buyer was able to change the cart in sourcing application however in SRM 7.0 buyer can assign the source of supply and update the price in the cart. This seems to be more of compliance to the regulations.

New enhacements in SRM 7 latest EHP offers the sourcing related activities related trigger event if workflow needed to be started.

# SRM organization Structure & SAP HR integration

Organization structure (internal) is crucial master data of SRM; as all of attributes, approval hierarchy, and lot, more is maintained here.
If SAP HR is in place for the organization units for which SRM is under implementation, then as best practice SAP HR can be used to leverage the SAP SRM organization structure.

SAP HR Infotype 1001 (along with 1000, 1002) provides the major of the user data.
Synchronization report (RHALEINI) is used to integrate the both systems, please note SAP HR will be the leading system.
Updates are carried out using the IDoc (HRMD_ABA), for the specified change pointers (report RBDMIDOC).
Transaction BBP_BP_OM_INTEGRATE can be used to fix if something missing.
Obvious but to remember - purchasing specific data (P. Org, P Grp..) needs to be maintained in the SRM.

The changes done in the SRM Organisation structure can be tracked with the maintenance of customisation in table T77CDOC_CUST. The changes can be with report RHCDOC_DISPLAY.
As change logging can deteriorates system performance only important and audit critical infotypes should be used. For exaple- approval limit, spend limit.

Note- SAP tells to limit the number of users in organisation unit maximum two hundred to avoid performance problem. As the attributes search, partner search is performed it takes longer time.

# SAP SRM 7 blog

Its all about you wanted to know about SAP SRM 7 and further releases!