SRM - Unicode and Non-unicode - are you still in gutenberg era

SRM - Unicode and Non-unicode  - Are you still in gutenberg era.

A few of SRM customers might be in non-Unicode environment, during update they would face a challenge of porting to Unicode. Porting to Unicode is always beneficial and advised for the better environment integration.

 

SRM in ecosystem- Hardware/Cloud/HANA

Many organisations are passing through the phase where they are plethora of options with variety of the issues! The ecosystem is multi layered and the focus is shifting to non-disruption of the service rather than radical change (I often hear - thank you for not changing us when we were changing ourselves).

Well SRM upgrade and peripheral changes are part of this and give a thought in this change process!

New SRM

Will be SAP releasing EHP 4 of SRM, or a big shift to SRM 8 with fresh start.
What's in next year 2015.

SAP SRM 7 upgrade switching to Industry solution

If you the last minute upgrade customer and looking for to switch to the SRM PPS (Public Sector) solution, please mind below-
1. Adopt new functions
2. Retiring some processes 

3. System landscape –you may need ERP (ECC or so) changes

4 . A consultant/s for the makeover

The public sector usually has focus on document trail and financial management. Also specific functions are delivered for Public sector.

SAP SRM and SAP NetWeaver 7.41 role placement in landscape

SAP SRM and SAP NetWeaver 7.41 role placement in landscape-achieve next level of technical suite

SRM 7 - EHP 3 Best fitting the innovations

SRM 7 -EHP 3 have come up with good bunch of innovations. Please be ready with next level of procurement. Well you need your landscape in sync to reap all benefits.

SAP SRM 7 roles and authorisations

The SRM ABAP roles plays the important role in the the user activity. For the upgrade and implementation the authorisation should be given for the initial task.

The customised set of roles may need to be refreshed along with new authorisations.

SRM 7 and backend integration

The major plus point SRM provides is the multiple backend connectivity. The tight integration can be done with SAP ECC. The document can be exchanged via multiple adapter channels. As the SRM does not have the financial setup, the financial/accounting postings are done in the ERP system.

The complex setup would include the optical archiving solution, content server for attachments/ document exchange, supplier registration (Supplier Life Cycle management tool), PLM software integration, credit card / payment gateway integration.

SRM 7 and backend integration

The major plus point SRM provides is the multiple backend connectivity. The direct integration can be done with SAP ECC. The document can be exchanged via multiple adapter channels. As the SRM does not have the financial setup, the financial/accounting postings are done in the ERP system.
Also non-SAP FI system can be integrated using integration middleware. For example, PeopleSoft, Oracle Apps, JD Edwards,

The complex setup would include the optical archiving solution, content server for attachments/ document exchange, supplier registration (Supplier Life Cycle management tool), PLM software integration, credit card / payment gateway integration.

# SAP SRM and SAP NetWeaver Business Client (NWBC)

SAP has been offering new GUI platform as NetWeaver Business Client (NWBC) for quite a while. Also this been modified and updated since then. Customer having non-central place for the user navigation and completely fresh implementation can consider for the NWBC as the user interface platform.


NWBC is non internet browser based GUI, which keeps the enterprise free from the dependency on the internet browser and related requirements. User has a interface similar to SAP GUI.

Also SAP ECC (depending on NW and EHP levels) provides comprehensive out of box NWBC roles, POWL lists and management tools.

SAP SRM 7 and securing your external facing world

Recently enterprise security came to alert due to the malicious content spreading across.
Ensure you stay safe and secured.

# SAP SRM - Looking back at the history

SAP = Systems, Applications and Products in Data Processing
B2B = Business to Business Procurement (internet/web era)
EBP= Enterprise Buyer Professional
SRM = Supplier Relationship Management

I could remember the days when the Purchase order was typed and manually stamped/signed and mailed to a supplier. Then the orders were punch carded to a supplier (earlier EDI days). The communications evolved. The mass production and increased supply demand invented many of the innovations.

In the internet era of early 1999 SAP introduced the very first SRM application. SAP called it as SAP B2B 1.0. Then the re-branding and the SAP suite offering followed.

Note-
For a few releases SAP followed year nomenclature which was a trend for while in IT industry and went back to numeric one.
**SRM 2005 = SRM 5.0
SRM 2007 = SRM 6.0 (limited)


It has been the interesting journey so far!

# SAP SRM 7 EHP upgrade

Some notes for the customers going for Enhancement Pack (EHP) upgrade for SAP SRM 7.

A considerable percentage of customers have SAP SRM 7.0 in their landscape and would be looking forward for the latest EHPs.

At present SAP SRM have flavours of SAP SRM 7.02 (EHP 2) and SRM 7.13 (HANA EHP).

Please consider below points-

-Please evaluate the new functionalities you would be looking for and benefits of these
-Are you on the old workflow, it would good idea to upgrade to new workflow (BRF based, please see my earlier post on BRF)
-Any technical foundation upgrades in the Portal (Netweaver 7 to latest release), BI reporting, Interface (PI or third party)
-Upgrades in the SAP ECC EHP
for example SAP ECC 6 EHP 2 (SAP ECC 6.02) to SAP ECC 6 EHP 7 (SAP ECC 6.07)
- Are you the Industry specific customer - SAP SRM PPS

There are a couple of project methodology to achieve this (of course by the SRM functional consultant/Architect)-
1. Sandbox upgrade - Upgrade the Sandbox (or a separate system than Developement), access the functionality required
2. Workshops approach- Conduct the workshops, then upgrade in the development system.

Some customer may find some or other approach suitable based on their environments. Nevertheless, enhancement packs brings the technical and functional enhancements so should be treated as a separate project.

# SRM - Message output

SRM and the smartform for the message control for the Purchase orders- Extended Classic Scenario.

SRM offers multiple new mediums to connect/send the messages to the supplier.
The messages can be printed, email, fax, XML, EDI (other formats).


The other documents such as - Bid, RFX can be also printed based on the requirement.

The interesting is the SRM offers the printing of the shopping cart for the internal purpose. This could be treated like offline viewing of the cart. A few business scenariosmay call for a printing of the shopping cart.

# SAP SRM 7 and Internet browser - some thoughts

SAP SRM is totally browser based application (for end user). Attention must be paid to for the browser policy and add-ons fitments.

SAP has lately started supporting the open-source and zero-footprint browsers. However ensure that your organisation gets best support and the functionality before you go for any non-standard browsers.

Although the paradigm is shifting to the mobile platform, the shopping functionality is massively used in main browser.

Internet browsers - Internet Explorer (Microsoft IE), Mozilla Firefox, Google Chrome, Apple Safari

SAP SRM 7 - What goes in next Year's IT budget!

What CIO and IT heads would be looking in next year's IT budget

A few drivers-

- More business drivers that help them directly/indirectly to keep the customers happy
-Consistent and well-managed IT landscape
-More compliant business and accurately reported
-Help to grow business and increase sustainability
- Increase skill of organisation using IT as backbone

How SAP SRM 7 would help
- Get vision of the spend
- Manage procurement
- Be auditable and compliance based
- Leverage on the technology, help on sustainability

# SAP SRM 7 - Your organisations' catalog strategy

SAP SRM's main capability is of catalog functionality. Its your organisations strategy which catalog solution should be approached.

The catalog application's capabilities, export/import functions,  user-friendly navigation, scalability, support/maintenance, local requirements should be weighed along with cost/package.

In premise application has its own benefits and cloud based/hosted has its own benefits.

Consider below points as decision making
-Long term plan and business usage for the catalog
-Complexity and must versus wish
-User base happiness
-Vendor / market adaptable