SAP Supplier Lifecycle Management sits on the SAP NetWeaver ABAP stack as the underlying technical platform. The software component, SRMSMC (the component name for Supplier Lifecycle Management), is typically installed as an add-on for the SAP NetWeaver ABAP system.

Following the successful installation of the necessary software components on the participating systems in the SAP Supplier Lifecycle Management-based SAP system landscape, it is imperative to perform specific technical activities to ensure that users can use the system productively for transaction processing. Most of the standard activities performed as part of the standard post installation tasks in SAP NetWeaver ABAP are applicable to SAP Supplier Lifecycle Management. However, there are specific settings that are peculiar to SAP Supplier Lifecycle Management that I discuss.

A typical SAP Supplier Lifecycle Management System landscape is made up of the following main systems:

• SAP Supplier Lifecycle Management – Buy Side
• SAP Supplier Lifecycle Management – Sell Side
• Back-end systems (SAP ERP, SAP Supplier Relationship Management [SRM], or SAP Master Data Governance [MDG])

Regarding deployment options, you can choose to operate SAP Supplier Lifecycle Management as a stand-alone system or as an integrated system with (SAP ERP, SAP SRM, or SAP MDG). For a stand-alone deployment, the Supplier Lifecycle Management server component is installed in isolation without any interaction with back-end systems. When the integrated deployment approach is adopted, a specific SLC plug-in software component has to be installed on the back-end systems. You need to establish a connection to the SLC server via the appropriate communication technologies (Remote Function Call [RFC], point-to-point communication via Web Services Reliable Messaging Protocol, or SAP NetWeaver Process Integration).

SAP Supplier Lifecycle Management is technically divided into the sell side and the buy side. For security reasons, SAP recommends that the sell side reside outside the firewall and that the buy side reside behind the firewall. SAP Supplier Lifecycle Management can be accessed from the front end via the SAP NetWeaver Portal or SAP NetWeaver Business Client.

I discuss the following activities that constitute important basic technical configuration settings for the SAP Supplier Lifecycle Management system:

• Compare productive client content with client 000
• Activate business function switches
• Maintain roles and generate profiles
• Set up an RFC connection for the different communication process types
• Create an RFC destination for a supervisor
• Assign RFC connections to communication process types
• Define the SAP Supplier Lifecycle Management System Landscape
• Activate HTTPS
• Activate Internet communication framework services
• Create external aliases for services
• Set up automatic SAP business workflow customization and generalization of workflow tasks

Let’s walk through these customizing activities.

Compare Productive Client Content with Client 000

Following the installation of the SLC server, you are expected to perform a client copy of client 000 as your productive client. However, some content that is needed in your productive client only resides in client 000, especially after installation of Support Packages. To ensure that the required contents are in your productive client, it is good practice to perform a comparison between client 000 and the productive client. Wherever discrepancies exist for specific software component objects, you need to adjust the entries accordingly. The following application components need to be compared:

• SLC* for various SAP Supplier Lifecycle Management customizing
• BC-SRV-NUM for number range intervals
• BC-MUS for Launchpad, OBN (object-based navigation), and POWL (personal object worklist library) customizing
• BC-SEC-AUT-PFC for PFCG role customizing

To perform this activity, execute transaction code SCU0. This action opens the screen shown in Figure 1.

Figure 1

The initial screen for the maintenance for a cross-system customizing comparison

Activate the Choose components radio button and click the Create button. In the screen that displays (Figure 2), double-click the SLC node. Click the green checkmark.

Figure 2

Highlighted SLC application component

In the screen shown in Figure 3, the system autopopulates the Comparison run ID field. Enter a description of the comparison run and RFC connection details of Client 000 and click the Total comparison button.

Figure 3

Description and RFC connection details for comparison run

The screen in Figure 4 displays. Note that all the rows in the Comp (component) column are green. The green boxes indicate that the components are consistent. If you have any red entries, then you need to adjust the content in accordance with SAP Note 1910403.

Figure 4

Result of customizing component comparison

As opposed to performing the customizing comparison for all objects of the selected application component, you can perform a comparison run for the following specific objects:

• SLC own customizing objects => Views /SRMSMC/V_ROS, /SRMSMC/V_S3Q, /SRMSMC/V_ACTION, /SRMSMC/V_EVAL, /SRMSMC/V_EVKEY, /SRMSMC/V_SQKEY
• Number range interval customizing (objects of the BC-SRV-NUM component) => Table TNRO
• Launchpad and OBN customizing (objects of the CA-GTF-SGF component)=> Tables APB_LAUNCHPAD_V, APB_LAUNCHPADT, APB_LPD_CONTROL, APB_LPD_VERSIONS, APB_LPD_OTR_KEY
• POWL customizing (objects of the CA-GTF-SGF-POW component) => Views POWL_V_TYPE_R; POWL_V_QUERY, POWL_V_CAT, POWL_V_QUERY_R, /SRMSMC/V_PWL_AC, /SRMSMC/V_PWL_FC; Table POWL_SELCRIT
• PFCG role customizing => Tables AGR_TIMEB, SPERS_OBJ, USMD2001, USMD2003

To perform the customizing run for a specific object, execute transaction code SCU0 and follow SAP Easy Access > Tools > Customizing Cross-System Viewer. In the initial screen that displays (Figure 5), click the Manual selection option and click the Create button.

Figure 5

Manual selection for a cross-system comparison

In the pop-up screen that displays, specify an object name (e.g., TNR0) as shown in Figure 6. Click the execute icon.

Figure 6

Define an object name for a content comparison

In the new screen that displays (Figure 7) enter a description of the comparison run and RFC connection details of client 000. Click the Total comparison button.

Figure 7

Enter a description of the comparison run and RFC connection details

The next screen displays the results of the comparison run (Figure 8).

Figure 8

Result of the customizing component comparison

Activate Business Function Switches

Business functions can be defined as self-contained objects that need to be switched on to use the associated capabilities of an application component. The activation of a business function is a prerequisite for leveraging the functionalities of any business scenario supported by the SAP Supplier Lifecycle Management system. Depending on whether the system is the sell side or buy side, you need to activate business functions belonging to the SRMSMC software component in the respective system.

The following business functions need to be activated in the buy side:

• SMC_SUPPL_DATA_MGT_1: SLC, Supplier Portfolio Management (Reversible)
• SMC_ACTIVITY_MGT_1: SLC, Activity Management (Reversible)
• SMC_SUPPL_CLASS_1: SLC, Supplier Classification (Reversible)
• SMC_SUPPL_EVAL_1: SLC, Supplier Evaluation (Reversible)
• SMC_SUPPL_QUA_BFW_1: SLC, Supplier Qualification (Buy Side) (Reversible)
• SMC_SUPPL_REG_BFW_1: SLC, Supplier Registration (Buy Side) (Reversible)
• SMC_STW_INTEGRATION_1 (Integration with SAP StreamWork)

The following business functions need to be activated in the sell side:

• SMC_SUPPL_QUA_OFW_1 (Supplier Qualification)
• SMC_SUPPL_REG_OFW_1 (Supplier Registration)
• SMC_SUPPL_SMNT_OFW_1 (Supplier Data Maintenance)

You use the Switch Framework to activate business functions. To access the Switch Framework, execute transaction code SFW5 (Switch Framework: Change Business Function Status) or Program SAPLSFW_CUSTOMIZE

To activate business functions in the appropriate SAP Supplier Lifecycle Management system, execute transaction code SFW5. In the screen shown in Figure 9, click the Continue button.

Figure 9

Security information for maintenance of business functions

This action opens the screen shown in Figure 10.

Figure 10

The initial screen for the maintenance of business functions

Click the Enterprise_Business_Functions folder to expand it. Scroll down to the business functions for SAP Supplier Lifecycle Management (Figure 11). These functions can be identified by the prefix SMC.

Figure 11

Business functions related to the SAP Supplier Lifecycle Management system

Select an entry by clicking a check box in the Planned Status column (Figure 12).

Figure 12

Select business functions to activate

Click the Activate Changes button. Figure 13 appears. Click the green check mark.

Figure 13

System information about the business function activation background job

In the refreshed screen you can view the status changes for the business functions that you activated (Figure 14).

Figure 14

Status change for activated business functions

Dependencies might exist for specific business functions. Therefore, you need to activate specific business functions before others can be activated. For example, the SMC_SUPPL_DATA_MGT_1 (Supplier Portfolio Management) business function is a prerequisite for activating all sell-side business functions. If you do not adhere to the dependent requirements, you receive an error similar to the one shown in Figure 15 when you try to activate the business functions.

Figure 15

Error generated because of violation of dependencies for business function activation

Maintain Roles and Generate Profiles

The SAP Supplier Lifecycle Management system has standard roles that can be adapted to suit the security (authorization) and business needs of your operating environment. Suffice it to say that the standard roles can be copied to your namespace and authorization data maintained accordingly via transaction code PFCG. The standard roles are specific to the individual SAP Supplier Lifecycle Management server (i.e., the buy side or the sell side) even though all standard roles are visible irrespective of the SLC server role. The standard roles relevant to this application have the prefix /SRMSMC. Authorization for roles needs to be generated to ensure that all profiles have the necessary authorizations provisioned for them. To mass generate profiles for roles, use transaction code SUPC. Figure 16 shows what a typical generated profile master data for roles looks like for SLC-specific roles.

Figure 16

Confirmation of profile generation for roles

Following the generation of the profiles for roles, the appropriate roles need to be assigned to technical and functional users. For example, the creation (maintenance) of RFC users in the participating systems in the SAP Supplier Lifecycle Management is required to allow for cross-systems communication when RFC technology is used for system communication. The technical user accounts need to be created in the SAP Supplier Lifecycle Management Systems (sell side and buy side). These users must be defined via transaction code SU01 for different business process types and assigned the corresponding roles. 

Set Up an RFC Connection for the Different Communication Process Types

The RFC connection between the SAP Supplier Lifecycle Management system (sell side) and the SAP Supplier Lifecycle Management system (buy side) facilitates the following processes:

• Distribution of supplier data (or changes to supplier data) to the SAP Supplier Lifecycle Management system (sell side)
• Transfer changes made to the supplier master data by the supplier to the buy side
• Transfer supplier qualification request data to the sell side
• Transfer supplier qualification response data to the buy side
• Transfer supplier registration request data to the buy side

To create an RFC destination for the different communication process types, execute transaction code SM59 or follow menu path SAP Customizing Implementation Guide > SAP Supplier Lifecycle Management > Basic Settings for SAP Supplier Lifecycle Management (Buy Side) > Cross System Communication > Create RFC Connections. In the screen shown in Figure 17 select the ABAP Connections RFC Connection type and click the create icon.

Figure 17

Types of RFC connections

In the next screen, enter a description in the Description section. Click the Technical Settings tab and enter the required details as shown in Figure 18.

Figure 18

Define an RFC destination name and technical settings

Click the Logon & Security tab and enter logon information for the RFC users created for the corresponding communication process type as shown in Figure 19. 

Figure 19

Define logon information for the RFC destination

Click the Special Options tab. Figure 20 displays with a dialog box.

Figure 20

Remote logon support message

Click the green checkmark, and then in the Transfer Protocol field, select Classic with background RFC (bgRFC) as the transfer protocol as shown in Figure 21. 

Figure 21

Notification for change of transfer protocol

In the dialog box that displays, click the Yes button. Figure 22 displays with a status message. 

Figure 22

Status message for successful definition of RFC

Create an RFC Destination for a Supervisor  

The background RFC Supervisor destination is designed to support the processing of bgRFCs in the SAP Supplier Lifecycle Management system. The system uses the RFC supervisor destination to ascertain the configuration settings for the bgRFC scheduler as defined on each application server, thereby guiding the start and stop operation of the scheduler. The background supervisor destination needs to be assigned to a technical user (with the role SAP_BC_BGRFC_SUPERVISOR) of system type.

To set up background RFC supervisor destinations, execute transaction code SBGRFCCONF. Figure 23 displays. Click the Define Supervisor Dest. tab.

Figure 23

The initial screen to define a background RFC supervisor destination

Figure 24 appears. Click the Create button.

Figure 24

The initial screen to create a supervisor destination

Figure 25

Create an RFC destination for a supervisor

In the screen shown in Figure 26, click the save icon.

Figure 26

Save the entry for RFC destination for supervisor data

Figure 27 displays a status message.

Figue 27

Status message for successful bgRFC configuration

Now click the Define Inbound Dest. Tab and click the create icon (Figure 28).

Figure 28

The initial screen for the maintenance of inbound destination

This action opens the screen shown in Figure 29. Enter a name for the inbound destination in the Inb. Dest. Name field and click the Save button.

Figure 29

Define attributes for inbound destination

Figure 30 displays a status message.

Figure 30

Status message for inbound destination definition

Assign RFC Connections to Communication Process Types

After you maintain logical systems and RFC connections, you need to associate RFC connections to the different communication process types. This customizing activity requires you to define a corresponding logical system, a communication process type, and RFC destination appropriately in the buy side and sell side.

The logical system defined here should be the destination system of your RFC connection. Figure 31 shows a typical assignment of RFC destinations to communication process types. The configuration activity can be accessed by following menu path SAP Customizing Implementation Guide > SAP Supplier Lifecycle Management > Basic Settings for SAP Supplier Lifecycle Management (Buy Side) > Cross System Communication > Assign RFC Connections to Communication Process Types. 

Figure 31

RFC connections assignment to communication process types

Define the SAP Supplier Lifecycle Management System Landscape 

Different systems participate in the business scenarios processing in the SAP Supplier Lifecycle Management System landscape. You need to explicitly define the role of the individual systems in the landscape in customizing. The following system types can be maintained in this customizing activity:

•    Buy-Side SLC System (Standalone)
•    SRM System (Buy-Side SLC or back end)
•    ERP System
•    ERP with CVI
•    Sell Side SLC System (Standalone)
•    Sell Side SLC System on SUS (Supplier Self-Service) MDG Hub Supplier Master Data System
•    SAP ERP Central Supplier Master Data System

Figure 32 shows a typical configuration screen for this customizing activity. To access this screen, execute transaction code SPRO and follow menu SAP Reference IMG > SAP Customizing Implementation Guide > SAP Supplier Lifecycle Management > Basic Settings for SAP Supplier Lifecycle Management (Buy Side) > Cross-System Communication > Define System Landscape. 

Figure 32

Typical system landscape for SAP Supplier Lifecycle Management

Activation of HTTPS

Following the installation of the SAP ABAP system, you need to set up secured communication via secured HTTP to enforce security in the security landscape. This requires the maintenance of a few settings, including the installation of SAP Cryptographic Library, maintenance of profile parameters, and configuration of personal security environment (PSE).

The following are some of the profile parameters that need to be maintained accordingly:
•    ssl/ssl_lib
•    sec/libsapsecu
•    ssf/ssfapi_lib
•    ssf/name
•    icm/server_port_<xx>
•    icm/HTTPS/verify_client

To maintain profile parameters, execute transaction code RZ10. Figure 33 shows a typical definition for these profile parameters. 

Figure 33

Profile parameter settings for HTTPS activation

To verify that HTTPS is properly configured and activated, review the entries. To do this, execute transaction code SMICM (ICM Monitor) and follow menu path Goto > Services. Figure 34 shows examples of activated HTTPS services displayed in the ICM Monitor.

Figure 34

HTTPS service activated in the ICM Monitor

Activate Internet Communication Framework Services

Internet Communication Framework (ICF) services are HTTP services that are used for executing HTTP request handlers. You need to activate specific services to use the SAP Supplier Lifecycle Management System. From a security perspective, it is a best practice to activate only the ICF services that an application needs to run properly. Below is a list of the main ICF services that need to be activated in the SAP Supplier Lifecycle Management system (buy side):
 
•    /default_host/sap/bc/bsp/srmsmc/qua_cmn - SLC Application for Supplier Qualification
•    /default_host/sap/bc/bsp/srmsmc/sup_delta - BSP Application to Display Supplier and Contact Deltas
•    /default_host/sap/bc/bsp/srmsmc/evaluation - SLC Application for Supplier Evaluation
•    default_host/sap/bc/bsp/srmsmc/eva_cmn - SLC Application for Supplier Evaluation by Appraisers without User ID
•    /default_host/sap/bc/bsp/sap/thtmlb_scripts - THTMLB Scripts
•    /default_host/sap/bc/bsp/sap/thtmlb_styles - CSS stylesheets and GIF for THTMLB tag library
•    /default_host/sap/bc/nwbc/smc - SMC NWBC HTML Service
•    /default_host/sap/bc/webdynpro/srmsmc/wda_bhp_ovp_main - Maintenance Application of Supplier Hierarchy
•    /default_host/sap/bc/webdynpro/srmsmc/wda_BP_CERTDETAIL - Certificate Details
•    /default_host/sap/bc/webdynpro/srmsmc/wda_crt_ovp_main - Maintenance Application for Certificate Type
•    /default_host/sap/bc/webdynpro/srmsmc/wda_crt_ovp_trns - Translation Application for Certificate Types
•    /default_host/sap/bc/webdynpro/srmsmc/wda_emp_det_bcard - Employee Business Card Standalone Application
•    /default_host/sap/bc/webdynpro/srmsmc/WDA_I_BP_SUPPLIER - Supplier Maintenance for SLC
•    /default_host/sap/bc/webdynpro/srmsmc/wda_i_bp_transfer - Supplier Distribution GAF
•    /default_host/sap/bc/webdynpro/srmsmc/WDA_I_QNR_OVP - Questionnaire: Overview
•    /default_host/sap/bc/webdynpro/srmsmc/wda_i_scs_ovp - Supplier Classification Profile OVP
•    /default_host/sap/bc/webdynpro/srmsmc/wda_i_scs_search_ovp - Search for Supplier Classification Profile OVP
•    /default_host/sap/bc/webdynpro/srmsmc/WDA_I_SEP_OVP - Supplier Evaluation Template
•    /default_host/sap/bc/webdynpro/srmsmc/WDA_I_SES - Supplier Evaluation Scorecard
•    /default_host/sap/bc/webdynpro/srmsmc/WDA_I_SEV_OVP - Supplier Evaluation Request
•    /default_host/sap/bc/webdynpro/srmsmc/WDA_I_SQP_OVP - Supplier Qualification Template
•    /default_host/sap/bc/webdynpro/srmsmc/WDA_I_Sqq_OVP - Supplier Qualification Request
•    /default_host/sap/bc/webdynpro/srmsmc/wda_puc - Purchasing Category WD Application
•    /default_host/sap/bc/webdynpro/srmsmc/wda_puc_t - Translation Application for Purchasing Categories
•    /default_host/sap/bc/webdynpro/srmsmc/WDA_QLB_OVP_MAIN - Maintenance Application of Question Library
•    /default_host/sap/bc/webdynpro/srmsmc/WDA_QLB_OVP_TRNS - Translation Application of Question Library
•    /default_host/sap/bc/webdynpro/srmsmc/wda_qnr_ovp_trns - Translation Application for External Questionnaire Names
•    /default_host/sap/bc/webdynpro/srmsmc/wda_sep_ovp_trns - Translation Application for Evaluation Template
•    /default_host/sap/bc/webdynpro/srmsmc/wda_sqp_ovp_trns - Translation Application for Qualification Template
•    /default_host/sap/bc/webdynpro/srmsmc/wda_act - Activity Management

The following is a list of the main ICF services that needs to be activated in the SAP Supplier Lifecycle Management system (sell side):

•    /default_host/sap/bc/bsp/srmsmc/qua_cmn -  SLC Application for Supplier Qualification. This service is used for qualification responses.
•    /default_host/sap/bc/bsp/srmsmc/ros_ext - Frontend Server for Supplier Registration
•    /default_host/sap/bc/bsp/srmsmc/ros_ext_2 - Supplier Registration - Part 2: Admin. Account Creation
•    /default_host/sap/bc/bsp/srmsmc/s3q_ext - BSP Application for Supplier Data Maintenance and  Qualification
•    /default_host/sap/bc/bsp/srmsmc/sup_delta - BSP Application to Display Supplier and Contact Deltas
•    /default_host/sap/bc/bsp/sap/thtmlb_scripts - THTMLB Scripts
•    /default_host/sap/bc/bsp/sap/thtmlb_styles - CSS stylesheets and GIF for THTMLB tag library
•    /default_host/sap/webcuif/uif_callback - Generic callback

To activate ICF services in the system, execute transaction code SICF. In the screen shown in Figure 35 click the execute icon.

Figure 35

The initial screen for ICF services maintenance

In the next screen, break up the default_host root node until you reach the desired service that you need to activate as shown in Figure 36.

Figure 36

Hierarchical structure of ICF services

Figure 37

Activate ICF services

Figure 38

Confirmation message for ICF Services activation

Figure 39

Test an ICF service

Figure 40

Output of ICF service test

Create External Aliases for Services

External aliases are linked to ICF services that are used to call services using any appropriate nontechnical name. External aliases are particularly useful in SAP Supplier Lifecycle Management for the registration of suppliers, qualification of supplier, and internal system use purposes. You need to create an external alias for the following ICF service in the buy side: Supplier Evaluation without user ID - /default_host/sap/bc/bsp/srmsmc/eva_cmn

You need to create an external alias for the following ICF services in the sell side:

•    Frontend Server for Supplier Registration - /default_host/sap/bc/bsp/srmsmc/ros_ext: This service permits anonymous logon (with no password) to the SAP Supplier Lifecycle Management System (sell side) for the purpose of supplier registration.
•    SLC Application for Supplier Qualification - /default_host/sap/bc/bsp/srmsmc/qua_com: This service permits potential supplier to take part in the supplier qualification process.
•    THTMLB Scripts - /default_host/sap/bc/bsp/sap/thtmlb_scripts:
•    CSS Stylesheets and GIF for THTMLB Tag Library - /default_host/sap/bc/bsp/sap/thtmlb_styles

I only show how to create external aliases for Frontend Server for Supplier Registration. The same procedure can be applied to the services concerned with internal system usage. Note that you do not need to define a user when creating an external alias for supplier qualification because users participating in a qualification typically have a user ID. Also, ensure that the correct corresponding ICF service is selected in the Trg Element tab.

To create external aliases for the front-end server for supplier registration service, execute transaction code SICF. Figure 41 appears. Click the execute icon.

Figure 41

The initial screen for ICF services maintenance

Figure 42

The Root node for ICF services

Figure 43

The initial screen for the maintenance of external aliases

Figure 44

Enter a name and description for the external alias

Figure 45

Define logon data for the external alias

Figure 46

Assign the ICF service to the external alias

Figure 47

Test the external alias

Figure 48

The Supplier Registration Page tested via the external alias

Set Up Automatic SAP Business Workflow Customization and Generalization of Workflow Tasks

The SAP Supplier Lifecycle Management system uses the standard ABAP workflow engine. Therefore, you need to perform a number of mandatory customizing activities that can be performed automatically.  

To perform this customizing activity, execute transaction code SPRO and follow menu path SAP IMG > SAP Supplier Lifecycle Management > Buy Side > Basic Settings for Supplier Lifecycle Management > Business Workflow > Customize SAP Business Workflow Automatically or transaction SWU3. Figure 49 shows a typical screen of what completed business workflow settings look like.

Figure 49

Automatic Workflow Customizing

Figure 50

The initial screen for generalizing a workflow task

Figure 51

Select a workflow task to generalize

Figure 52

Generalized workflow tasks

Figure 53

The initial screen for event type linkage activation

Figure 54

Details of event type linkage for an SLC object type

Figure 55

Activate event type linkage

Figure 56

Saved changes to event type linkage

Kehinde Eseyin

Kehinde Eseyin is a security architect. He holds a bachelor’s degree in computer science. He has about 12 years of IT security, governance framework, IS risk, and compliance experience gained by working in numerous global organizations. Over the years, he has demonstrated competencies in security design, information assurance, cyber security, data privacy, threat and vulnerability management, penetration testing, business architecture, project management, IT audit, IS controls framework, and identity and access management.
 

You may contact the author at eseyinok@gmail.com.

If you have comments about this article or publication, or would like to submit an article idea, please contact the editor.