SAP Solution Sales Configuration for SAP S/4HANA

Administration Guide | CONFIDENTIAL2019-09-19

SAP Solution Sales Configuration for SAP S/4HANA: Administration Guide

© 2

021 S

AP S

E or

an

SAP affi

liate

com

pany

. All r

ight

s re

serv

ed.

THE BEST RUN

Content

1 About This Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.1 Document History. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

2 Getting Started. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62.1 Useful Links. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72.2 Overview of Relevant SAP Notes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82.3 Getting Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92.4 Glossary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

3 About SAP Solution Sales Configuration for SAP S/4HANA. . . . . . . . . . . . . . . . . . . . . . . . . . . 123.1 Software Units of SAP Solution Sales Configuration for SAP S/4HANA. . . . . . . . . . . . . . . . . . . . . . . 123.2 System Landscape for SAP Solution Sales Configuration for SAP S/4HANA. . . . . . . . . . . . . . . . . . . 133.3 Overall Implementation Sequence. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

4 Installing SAP Solution Sales Configuration for SAP S/4HANA. . . . . . . . . . . . . . . . . . . . . . . . 164.1 System Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Required Notes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184.2 Overall Installation Sequence. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

SAP S/4HANA Add-On Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Installing the SSC Engine on SAP NetWeaver AS Java (EJB IPC Installation). . . . . . . . . . . . . . . . 27Solution Modeling Environment Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Installation of User Exit Deployment Mechanism. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44

4.3 Post-Installation Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47Importing Configuration Master Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47Generating Authorization Profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Assigning Authorization Roles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49Scheduling Background Jobs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50UI Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Maintaining Destination Name to SSC Engine on SAP NW AS Java. . . . . . . . . . . . . . . . . . . . . . . 57Syncing Existing Master Data (RTVs) with EJB-IPC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Deployment of User Exits for Pricing and Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Setting Up Interval for Number Range Object. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73Required Entries in the Gateway ACL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73Adjustment of BAdI Implementations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74Maintaining Fiori Launchpad Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74Setting Up the Inbound IDoc to Communicate with SAP CPI. . . . . . . . . . . . . . . . . . . . . . . . . . . .75Update Entries For User Exit Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

4.4 Using SAP Solution Sales Configuration for SAP S/4HANA with Vehicle Management. . . . . . . . . . . . 76

2 CONFIDENTIALSAP Solution Sales Configuration for SAP S/4HANA: Administration Guide

Content

5 Upgrading SAP Solution Sales Configuration for SAP S/4HANA. . . . . . . . . . . . . . . . . . . . . . . .775.1 Pre-Upgrade Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 775.2 Overall Upgrade Sequence. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .775.3 Post-Upgrade Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Migrating IPC Switch for Materials. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .78

6 Configuring SAP Solution Sales Configuration for SAP S/4HANA. . . . . . . . . . . . . . . . . . . . . . 796.1 Business Scenarios of SAP Solution Sales Configuration for SAP S/4HANA. . . . . . . . . . . . . . . . . . . 79

Solution Configuration in SAP S/4HANA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79Solution Configuration in Non-SAP Sales Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80Solution Configuration in SAP Hybris. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

6.2 Solution-Wide Topics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82Customizing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

6.3 Configuring SAP Solution Sales Configuration, UI Composer Add-on. . . . . . . . . . . . . . . . . . . . . . . . 82UI Composer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82Solution Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83Business Scenarios. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87Operations Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

7 Security Information for SAP Solution Sales Configuration for SAP S/4HANA. . . . . . . . . . . . .887.1 Other Required Documents for Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 887.2 User Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 897.3 Role and Authorization Concept. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .897.4 Network and Communication Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Communication Destinations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90Implementing Logon/Assertion Ticket for JSP UI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

7.5 Data Protection and Privacy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110Glossary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111User Consent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113Information Retrieval. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .114Deletion of Personal Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .114Change Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

8 Operating SAP Solution Sales Configuration for SAP S/4HANA. . . . . . . . . . . . . . . . . . . . . . . 1188.1 Other Required Documents for Operations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1188.2 Monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

Monitoring Concept. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119Logging and Tracing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119Alert Monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .120Error Logs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120Workload Monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

SAP Solution Sales Configuration for SAP S/4HANA: Administration GuideContent CONFIDENTIAL 3

Interface Monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120Background Job Monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

8.3 Administration and Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120Cache Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121Solution Configuration Support - Backend Utilities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122Starting and Stopping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .123Technical Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124Backup and Restore. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124Periodic Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124Load Balancing and Scalability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .124High Availability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

8.4 Software Change Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

9 Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

10 Support Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126


Content

1 About This Guide

This guide is the central starting point for the implementation of SAP Solution Sales Configuration for SAP S/4HANA. It tells you how to install and implement SAP Solution Sales Configuration for SAP S/4HANA and also provides security and operations information.

This guide addresses the following target audience:

● System administrators● Technical consultants● Key users

1.1 Document History

Note

Date Change More Information

September 27, 2019 First release of document All

SAP Solution Sales Configuration for SAP S/4HANA: Administration GuideAbout This Guide CONFIDENTIAL 5

2 Getting Started

Ensure you read the information in this section before you get started with SAP Solution Sales Configuration for SAP S/4HANA.

This guide is the central starting point for the technical implementation of SAP Solution Sales Configuration for SAP S/4HANA, where you can get an overview of the product, its software units, and its scenarios from a technical perspective. You can also find cross-scenario implementation information as well as scenario-specific information in this guide. You can leverage this information as a planning tool that helps you to design your system landscape.

It refers you to the required detailed documentation, mainly:

● Installation and configuration guides for single software units● SAP Notes● SAP Library documentation

The administration guide consists of the following main sections:

● Installing SAP Solution Sales Configuration for SAP S/4HANA discusses the installable components and all the activities to be executed before, during, and after installation of these components.

● Upgrading SAP Solution Sales Configuration for SAP S/4HANA● Configuring SAP Solution Sales Configuration for SAP S/4HANA discusses the solution component matrix

and system landscape, and provides the overall implementation sequence.● Security Information for SAP Solution Sales Configuration for SAP S/4HANA discusses the security and

privacy-related information. Additionally, it also specifies the setup for user log in and required authorizations.

● Operating SAP Solution Sales Configuration for SAP S/4HANA

We recommend that you use the documents available here. The guides are regularly updated.

Constraints

● The business scenarios that are presented here serve as examples of how you can use SAP software in your company. The business scenarios are only intended as models and do not necessarily run the way they are described here in your own system landscape. Ensure that you check your requirements and systems to determine whether these scenarios can be used productively at your site. Furthermore, we recommend that you test these scenarios thoroughly in your test systems to ensure they are complete and free of errors before going live.

● This administration guide primarily discusses the overall technical implementation of SAP Solution Sales Configuration for SAP S/4HANA, rather than its subordinate components. This means that additional software dependencies can exist without being mentioned explicitly in this document.


Getting Started

Related Information

Installing SAP Solution Sales Configuration for SAP S/4HANA [page 16]Upgrading SAP Solution Sales Configuration for SAP S/4HANA [page 77]Configuring SAP Solution Sales Configuration for SAP S/4HANA [page 79]Security Information for SAP Solution Sales Configuration for SAP S/4HANA [page 88]Operating SAP Solution Sales Configuration for SAP S/4HANA [page 118]

2.1 Useful Links

The following resources provide access to more information about general topics, such as software downloads, customer incidents, or high availability.

Resource Where to Find It

User assistance for SAP Solution Sales Configuration for SAP S/4HANA

http://help.sap.com/sscs4

Information about creating customer incidents http://support.sap.com/incident

SAP Notes search http://support.sap.com/notes

SAP Software Download Center http://support.sap.com/swdc

Product Availability Matrix http://support.sap.com/pam

Sizing http://www.sap.com/sizing

Security http://www.sap.com/security

Performance http://www.sap.com/performance.html

Information about support package stacks, latest software versions and patch level requirements

http://support.sap.com/sp-stacks

SAP Customer Experience wiki https://wiki.hybris.com/

Release Availability Matrices for Focused Business Solutions https://support.sap.com/content/dam/support/en_us/library/ssp/release-upgrade-maintenance/maintenance-information/fbs/solution_sales_configuration.pdf

SAP Solution Sales Configuration for SAP S/4HANA: Administration GuideGetting Started CONFIDENTIAL 7

http://help.sap.com/disclaimer?site=http%3A%2F%2Fsupport.sap.com%2Fincident

http://help.sap.com/disclaimer?site=http%3A%2F%2Fsupport.sap.com%2Fnotes

http://help.sap.com/disclaimer?site=http%3A%2F%2Fsupport.sap.com%2Fswdc

http://help.sap.com/disclaimer?site=http%3A%2F%2Fsupport.sap.com%2Fpam

http://help.sap.com/disclaimer?site=http%3A%2F%2Fwww.sap.com%2Fsizing

http://help.sap.com/disclaimer?site=http%3A%2F%2Fwww.sap.com%2Fsecurity

http://help.sap.com/disclaimer?site=http%3A%2F%2Fwww.sap.com%2Fperformance.html

http://help.sap.com/disclaimer?site=http%3A%2F%2Fsupport.sap.com%2Fsp-stacks

http://help.sap.com/disclaimer?site=https%3A%2F%2Fwiki.hybris.com%2F

http://help.sap.com/disclaimer?site=https%3A%2F%2Fsupport.sap.com%2Fcontent%2Fdam%2Fsupport%2Fen_us%2Flibrary%2Fssp%2Frelease-upgrade-maintenance%2Fmaintenance-information%2Ffbs%2Fsolution_sales_configuration.pdf



2.2 Overview of Relevant SAP Notes

The following SAP Notes are essential for installing, upgrading, and operating SAP Solution Sales Configuration for SAP S/4HANA.

NoteThe SAP Notes relevant for installation and upgrade are also listed in the respective sections in this guide.

Make sure that you have the latest version of each SAP Note, which is available on SAP Support Portal at http://support.sap.com/notes .

SAP Note Number Title Description

2824688 Release Information Note for SAP Solution Sales Configuration for SAP S/4HANA 1907

See this SAP Note for information about installing SAP Solution Sales Configuration.

2251429 Support for SAP Solution Sales Config-uration

See this SAP Note if you are using SAP Solution Sales Configuration with S/4HANA/Ready To Integrate Scenario and you observe some bug or unexpected behavior in SAP Solution Sales Configuration for SAP S/4HANA that you would like SAP Support to analyze.

1876540 SAP Solution Sales Configuration for SAP S/4HANA Solution Modeling Environment FAQ

General FAQ for when you are using the Solution Modeling Environment (SME) component of the SAP Solution Sales Configuration for SAP S/4HANA.

2314556 SAP Solution Sales Configuration - Frequently Asked Questions

General SAP Solution Sales Configura-tion for SAP S/4HANA related FAQ.

2246019 SAP Solution Sales Configuration Hybris - Frequently Asked Questions

General SAP Solution Sales Configura-tion Hybris related FAQ.

1819856 Additions to IPC VC deltalist - updated version

The behavior of the configuration in the Sales Configuration Engine (SCE) is different from the ERP variant configura-tion (VC).

937044 Characteristic Value Surcharge in ERP ISA scenario

Run report /SAPCND/UE_GENERATE_ENTRIES as per this note of variant price is not working.

3008067 Launching SAP Solution Sales Configu-ration in ME51N/ME21N

Program error while trying to lunch SAP Solution Sales Configuration in ME51N/ME21N


Getting Started

http://help.sap.com/disclaimer?site=http%3A%2F%2Fsupport.sap.com%2Fnotes

http://help.sap.com/disclaimer?site=https://launchpad.support.sap.com/#/notes/2824688









3023690 Missing Authorization Object in the Solution Sales Configuration Transaction Codes

Missing authorization object in the Solution Sales Configuration dialog transactions

3020687 Solution Sales Configuration SME roles updated with RFC and pFunction user exit authorization

On triggering the process to upload, delete or read the pFunction user exits stored in the ECC, SAP S/4HANA or CRM backend while using the SAP Solution Sales Configuraton SME (Solution Modelling Environment), you get an authorization error which aborts the process.

You are facing RFC authorization errors while running the initial download of the SAP Solution Sales Configuraton dataloader.

2.3 Getting Support

If you encounter any problems with SAP Solution Sales Configuration for SAP S/4 HANA, report an incident on SAP Support Portal.

To report an incident, go to SAP Support Portal at http://support.sap.com/incident . The relevant component is LO-SLC.

2.4 Glossary

Term Definition

SSC Short for SAP Solution Sales Configuration for SAP S/4HANA

EJB IPC Synonym for SSC Engine, which is a further development of the SAP IPC with extended solution configuration capabilities (for example, KB orchestration, bottom-up configura-tion, and an extended syntax).

This SSC Engine implements the EJB standard.




http://help.sap.com/disclaimer?site=http%3A%2F%2Fsupport.sap.com%2Fincident

Term Definition

Knowledge base A structured database that contains the master data of a solution model created in the solution modeling environment of SAP Solution Sales Configuration for SAP S/4HANA.

A knowledge base contains information about the classes and materials used in a solution.

Master store definition A collection of predefined pages that UI designers can use in their regular store definitions for a specific product category. Master store definitions are created by UI administrator users.

Predefined page A predefined page layout used for content that is identical for all stores of a specific product category, such as maintenance configuration information, and contact configuration information.

Predefined pages can be reused in all regular store defini-tions.

Solution A collection of interrelated components, such as hardware components, software components, and services.

In addition to selling their own products, many businesses also sell solutions that include products, services, and parts from other manufacturers. For example, many technology companies sell solutions that include combinations of highly complex hardware, software, and services, and each of these can have options or features that the customer must specify during the ordering process.

Solution model A hierarchical decomposition of a solution. It defines the products (configurable materials and the services) that can be contained within the solution. It also defines the relationships between the various elements of the solution, including any dependencies (constraints and rules).

Store A set of pages rendered by the Product Configurator application. A store displays the selectable options and features of a solution. To prepare a quotation, sales representatives use the store to configure a solution.

Store definition A configuration of a store used in the Product Configurator application to specify options and features of a solution.

Users define the store definition in the UI Composer. To do so, they use store templates and predefined pages to create a uniform look for the stores of a product category. A store definition is based on a specific version of a knowledge base.


Getting Started

Term Definition

Store template A store template contains the basic UI layout of the store pages. For example, a store template can specify the layout of the header and footer for all pages. The store template also specifies the UI elements that can be used in the store defi-nitions.

A default store template is delivered with the UI Composer. However, you can develop your own store templates. For example, you might develop a different store template for each product line.

Workspace Screen in the UI Composer where users organize and manage their store definition versions.

Source system A backend system from which the UI Composer retrieves the knowledge base information and quote/order information. By default, the UI Composer supports SAP S/4HANA systems. The source systems are configured in the UI Composer backend system (Gateway Hub).

UI designer A user role for the UI Composer application. The UI designer creates regular store definitions and configures the store definitions by composing store pages.

UI administrator A user role for the Composer application. The UI administrator performs various administrative tasks and reviews the store definitions that the UI designers have committed.


3 About SAP Solution Sales Configuration for SAP S/4HANA

This section provides an overview of SAP Solution Sales Configuration for SAP S/4HANA, including relevant business scenarios and technical system landscape.

SAP Solution Sales Configuration for SAP S/4HANA is a system that helps customers to configure and sell solutions made of complex product combinations. In addition to selling their own products, many businesses also sell solutions that include products, services, and parts from other manufacturers. For example, technology companies sell solutions that include combinations of highly complex hardware, software, and services, and each of these can have options or features that must be specified by a customer during the ordering process.

From a modeling perspective, each individual product can be split into many different instances, and there are many possible relationships and dependencies between the product instances. SAP Solution Sales Configuration for SAP S/4HANA provides a flexible modeling environment, which in turn simplifies the ordering and configuration process for the customer.

SAP Solution Sales Configuration for SAP S/4HANA includes a configuration engine that provides the ability to perform bottom-up configuration as well as the normal top-down approach. The system also offers innovations that make it easier to maintain configuration model data. The system is designed to provide efficient configuration execution performance, flexible user interfaces, and advanced integration capabilities.

3.1 Software Units of SAP Solution Sales Configuration for SAP S/4HANA

SAP Solution Sales Configuration for SAP S/4HANA consists of the following software units:

● Solution Modeling Environment (SME)An eclipse-based tool that supports online and offline collaborative development of Solution Models

● SAP Solution Sales Configuration Configuration Run TimeThe heart of SAP Solution Sales Configuration for SAP S/4HANA, it is what makes the robust power of the Solution Sales Configurator directly available for all the applications that offer Solution Sales Configuration functionality.

● Configuration User Interface (UI Composer UI)This is the UI5 UI that you are able to adapt for each solution or product as required.

● Configuration User Interface (JSP UI)This is the Java-based UI that allows backward compatibility of your application with the previous releases.

● Integration to Back-End Order System (SAP S/4HANA system)○ Provides material and product master data to the Solution Modeling Environment○ Enables the flow of solution configuration results for downstream processing


About SAP Solution Sales Configuration for SAP S/4HANA

3.2 System Landscape for SAP Solution Sales Configuration for SAP S/4HANA

This section describes the technical system landscape and the software components involved.

The following figure provides an overview of the system landscape for SAP Solution Sales Configuration for SAP S/4HANA.

Technical Landscape

The Solution Modeling Environment is installed on the personal computers of the modelers and the build manager. Modelers can use an extract of material master data from S/4HANA as part of the solution model they build. We recommend that you use a source control system (not part of SAP Solution Sales Configuration for SAP S/4HANA), such as GIT, on a centralized server where developers can check-out and check-in their solution models. Using a job, such as Jenkins, and the SME in headless mode, you may export the consolidated model to your SAP S/4HANA system.

Finally, the sales scenario that uses a non-SAP system requires an SAP AS Java for deployment of the SAP Solution Sales Configuration for SAP S/4HANA Runtime. The Solution Modeling Environment is also recommended.

The following software components are either required or optional, as indicated below, for the technical implementation of SAP Solution Sales Configuration for SAP S/4HANA.

SAP Solution Sales Configuration for SAP S/4HANA: Administration GuideAbout SAP Solution Sales Configuration for SAP S/4HANA CONFIDENTIAL 13

Business Scenario: SAP Solution Sales Configuration for SAP S/4HANA

Software Component Required or Optional

SLCE 800 Required

SLCUI 100 Required if you use the UI Composer UI

FBS_SOLCONF_IPC 3.0 SP01 and above Required

FBS_SOLCONF_SHRAPP Required if you use the JSP UI

3.3 Overall Implementation Sequence

The following table describes the overall installation sequence for SAP Solution Sales Configuration for SAP S/4HANA. This table contains all available software units. However, to implement a specific scenario, you only need a subset of available software units. Some are only required for special processes. For information about which software is required to implement a specific scenario, see Software Component Matrix, or scenario-specific sections under Business Scenarios of SAP Solution Sales Configuration for SAP S/4HANA.

For the latest component version and patch level requirements, see http://support.sap.com/sp-stacks .

For documentation listed in the following table, see Useful Links.

Process

Step Action Remarks/Subsequent Steps

1 Complete the implementation of your S/4HANA system in accordance with your business requirements.

This step is a prerequisite to Step 4.

2 Install the required notes according to the list in the installation description.

3 Install the SAP Solution Sales Configu-ration add-on for SAP S/4HANA.

Component SLCUI should be installed on front-end server. Please check if you have either embedded deployment or hub deployment:

SAP Help Portal.

4 Install SAP Solution Sales Configuration RUNTIME on the JEE server.


About SAP Solution Sales Configuration for SAP S/4HANA

http://help.sap.com/disclaimer?site=http%3A%2F%2Fsupport.sap.com%2Fsp-stacks

https://help.sap.com

Step Action Remarks/Subsequent Steps

5 In SAP S/4HANA, complete the Customizing of SAP Solution Sales Configu-ration (discussed in the Post Installation Steps).

For more information, see Customizing for Solution Sales Configuration under

Logistics - General Solution Sales

Configuration .

6 Install the Solution Modeling Environment plug-in in Eclipse.

As a prerequisite, the Solution Modeling Environment requires Eclipse 4.7.

Related Information

Business Scenarios of SAP Solution Sales Configuration for SAP S/4HANA [page 79]Useful Links [page 7]Post-Installation Tasks [page 47]

SAP Solution Sales Configuration for SAP S/4HANA: Administration GuideAbout SAP Solution Sales Configuration for SAP S/4HANA CONFIDENTIAL 15

4 Installing SAP Solution Sales Configuration for SAP S/4HANA

This section provides information about how to prepare for installation and what to do before and after the installation of SAP Solution Sales Configuration for SAP S/4HANA.

Use

SAP Solution Sales Configuration for SAP S/4HANA has the following software components:

● SAP S/4HANA Add-On● Configuration RUNTIME and JavaServer Pages User Interface (JSP UI)● SAP UI5 UI Composer UI● Solution Modeling Environment

The software components are available for download from SAP Software Download Center at http://support.sap.com/swdc .

Integration

SAP Solution Sales Configuration for SAP S/4HANA is integrated with the following SAP systems:

● SAP S/4HANA● SAP NetWeaver Application Server Java

The Configuration RUNTIME component is based on Java 2 Enterprise Edition (J2EE) standards. It must be deployed on an SAP J2EE engine.

SAP Solution Sales Configuration for SAP S/4HANA has the following implementation scenarios:

● Solution Configuration in SAP S/4HANA● Solution Configuration in SAP Commerce (former Hybris Commerce)

Depending on your implementation scenario, you must install the required components as defined in the table below:

Implementation Scenario

Solution Configuration in SAP S/4HANA

Solution Configuration in SAP Commerce with SAP S/4HANA Backend

SAP S/4HANA Add-On (SLCE 800)) X X


Installing SAP Solution Sales Configuration for SAP S/4HANA



Implementation Scenario

UI Composer Gateway 100 (SLCUI 100)

Configuration RUNTIME (FBS_SOLCONF_IPC)

X X

For more information about this, see the SAP Commerce Installation Guide

JSP UI (FBS_SOLCONF_SHRAPP) X X

Solution Modeling Environment (FBS_SOLCONF_SME)

X

Not required if you exclusively model in the PMEVC transaction.

X

Not required if you exclusively model in the PMEVC transaction.

4.1 System RequirementsThis section lists the prerequisites that must be met before you start installation.

SAP Solution Sales Configuration for SAP S/4HANA has the following system requirements:

Solution Modeling Environment Client System Requirements

Software Version

Operating System Windows (Win32, x86, and x64)

Java Runtime Environment Oracle, Java 1.8, SAP JVM 8

Eclipse Eclipse 4.7 (Oxygen)

NoteCompatibility for older versions of Eclipse is not guaranteed and compatibility with higher versions will be updated when supported.

Database See the product availability matrix at http://support.sap.com/pam .

Java Connector (JCo) 3.0 (delivered with the Solution Modeling Environment)

NoteThe 32-bit JCo version requires Microsoft C/C++ runtime libraries version 7.1 to be installed in the system. If the runtime libraries msvcr71.dll or msvcp71.dll are missing in the {windows-dir}\system32 or {windows-dir}\SysWOW64 directory, they must be installed separately. For more information, see SAP Note 684106 (Microsoft runtime DLLs).

SAP Solution Sales Configuration for SAP S/4HANA: Administration GuideInstalling SAP Solution Sales Configuration for SAP S/4HANA CONFIDENTIAL 17




SAP NetWeaver JEE Application Server System Requirements

Software Version

NW Application Server JAVA 7.50 SPS12 and above

SAP S/4HANA System Requirements

Software Version

SAP S/4HANA 1809 FPS01 or higher

Commerce System Requirements

For more information about this, see the SAP Commerce Installation Guide.

4.1.1 Required Notes

The following SAP notes must be implemented using transaction SNOTE before you begin installing SAP Solution Sales Configuration for SAP S/4HANA.

NoteYou must ensure that you have the latest version of each SAP Note as available on the SAP Support Portal

.

SAP Note Number Title

2653942 Adding the parameter CONFIG_MODE to the method SET_KB_DATE in the BAdI ERP_CFG_ADAPT

2773810 Legacy Adapter Refactoring

978552 Poor performance when deleting/changing characteristics

2764384 Program termination after profile selection

2787761 Adding option parameter config_id to VC_UI_CONFIG_FRAME

2766021 Improving call of classic variant configuration

2795257 Enhanced Exception Handling

2772930 Removal of singleton implementation of CU_CONFIG_DELEGATION BADI

2791365 Dump in SAPLVELO07 due to missing parameter



http://help.sap.com/disclaimer?site=https%3A%2F%2Fsupport.sap.com%2Fnotes

http://help.sap.com/disclaimer?site=https%3A%2F%2Fsupport.sap.com%2Fnotes










SAP Note Number Title

2849237 Runtime error in CE_C_PROCESSING while creating a sale order

2845710 Fixes for Generation Errors in S4H 1909

2807622 (For SAPK-10302INS4CORE and below) Migrate Classic BAdI ERP_CFG_ADAPT to new badi

The following SAP notes give you release information about SAP Solution Sales Configuration for SAP S/4HANA.


2824688 Release Information Note for SAP Solution Sales Configuration for SAP S/4HANA 1907

See this SAP Note for information about installing the initial release and the latest Support Package for SAP Solution Sales Configuration for SAP S/4HANA.

2090791 Release strategy for the ABAP add-on SLCE 607 onwards

See this SAP Note for detailed information about the installed SAP Solution Sales Configuration add-on for SAP S/4HANA 1809.

4.2 Overall Installation Sequence

This section provides detailed instructions for installing SAP Solution Sales Configuration for SAP S/4HANA.

4.2.1 SAP S/4HANA Add-On Installation

Use

You use this process to install the SAP Solution Sales Configuration add-on in SAP S/4HANA, and then define the required technical settings.

Process

1. You install the SAP Solution Sales Configuration add-on on SAP S/4HANA. For details, see the chapter Installing the SAP Solution Sales Configuration Add-On.







2. You adjust the implicit enhancements, if necessary. For details, see SAP S/4HANA Implicit Enhancements.

3. You define the RFC destination for the Solution Configuration Engine on NW AS Java. For details, see Defining the RFC Destination for Solution Configuration Engine on NW AS Java in SAP ERP.

4. You configure your Customizing settings.For more information, see Customizing for SAP Solution Sales Configuration.

Related Information

Installing the SAP Solution Sales Configuration for SAP S/4HANA Add-On [page 20]SAP S/4HANA Implicit Enhancements [page 21]Defining the RFC Destination for Solution Configuration Engine SAP S/4HANA [page 26]

4.2.1.1 Installing the SAP Solution Sales Configuration for SAP S/4HANA Add-On

Prerequisites

● You have downloaded the latest Support Package from http://support.sap.com/swdc Support Packages and Patches Access downloads A - Z C SAP SOLUTION SALES CONFIG SAP SOLUTION SALES CONFIG 3.0 .Here, you can download the relevant components listed under ENTRY BY COMPONENT and their relevant dependencies from REQUIRED COMPONENTS OF OTHER PRODUCT VERSIONS.

● You have loaded the add-on package into your SAP system.● You have implemented the prerequisite SAP Notes. For more information, see Overview of Relevant SAP

Notes.

Context

You use this procedure to install the SAP Solution Sales Configuration add-on in SAP S/4HANA.

Procedure

1. Log on to your SAP system in client 000 as a user with SAP_ALL authorization.




2. Enter transaction SAINT.

3. Choose Start.4. Choose Load.5. Choose the add-on SLCE 800 and SLCUI 100. Choose Continue.

The system displays the relevant queue.6. Choose Continue to start the installation process.

Related Information

Overview of Relevant SAP Notes [page 8]

4.2.1.2 Storing XML Configuration Results

Use

Configuration results for sales document items are stored as XML in the back-end system. When you install SAP Solution Sales Configuration for SAP S/4HANA in your SAP S/4HANA environment, you can specify whether the XML results are to be stored in compressed or uncompressed format. You do so using the business function /SLCE/BF_XML_COMPRSSION.

More Information

For more information, see the SAP Help Portal for SAP Solution Sales Configuration for SAP S/4HANA and navigate to SAP Solution Sales Configuration for SAP S/4HANA Relevant version Product AssistanceBusiness Functions Compressed Storage of XML Configuration Results .

4.2.1.3 SAP S/4HANA Implicit Enhancements

The following table lists the implicit enhancements that are a part of SAP Solution Sales Configuration for SAP S/4HANA. During installation, these enhancements are added before any existing enhancements in the relevant objects in the customer landscape. This may cause the new implicit enhancements to override the existing ones. Therefore, if you have existing implicit enhancements in the same objects as the enhancements listed below, you may have to adjust your existing enhancements accordingly.



Name Location Description

/SLCE/EHI_BOM_SKIP_CHECK Beginning of method SET_PART_OF_EXTERNAL (class CL_CUX_INSTANCE_TREE_CORE)

Used to skip the determination of bill of material (BOM) positions for advanced mode.

/SLCE/EHI_CALLING_EJBIPC Beginning of function module VC_UI_CONFIG_FRAME

Used to read CONFIG_ID from the context and pass it to the CFG_UI_CONFIGURE.

/SLCE/EHI_CHECK_SUBRC End of subroutine RV45A_MABNR_ERMITTELN (Include FV45PF0R_RV45A_MABNR_ERMITTELN)

Used to assign the determined UEPOS (parent line item).

/SLCE/EHI_COMMKB_UPD Beginning of function module CURX_KB_BASIC_DATA_READ_2

Provides a new implementation for the function module. It validates data against the COMM_CFG* tables instead of the SCE tables.

/SLCE/EHI_DETERMINE_UEPOS Beginning of subroutine STRUKTUR_ANLEGEN_POSITION (Include FV45SFST_STRUKTUR_ANLEGEN_POSI)

Used to determine the parent line item (UEPOS).

/SLCE/EHI_MAP_INSTANCES End of method GET_INSTANCE_INTERNAL (class CL_CUX_INSTANCE)

Used to get the mapping of instance IDs to the internal generated instance number.

/SLCE/EHI_ORDER_CONFIG Beginning of subroutine USEREXIT_SAVE_DOCUMENT_PREPARE (Include MV45AFZZ)

Used to move instance GUIDs to table VBAP.

/SLCE/EHI_ORDER_SAVE Beginning of subroutine USEREXIT_SAVE_DOCUMENT (Include MV45AFZZ)

Used to save, change, or delete XML, IRT, and binary large object to the respective tables.

/SLCE/EHI_OVERWRITE_BOM Beginning of function module V45CU_GET_COMPONENTS

Used to overwrite BOM table with the data from the configuration container for advanced mode.

/SLCE/EHI_REFRESH Beginning of subroutine TRANSAKTION_INIT (Include MV45AF0T_TRANSAKTION_INIT)

Used to refresh the data on transaction initialization (that is, at the start of the transaction).

/SLCE/EHI_REFRESH_BLOB_ON_DEL Beginning of subroutine USEREXIT_CHECK_XVBAP_FOR_DELET (Include MV45AFZB)

Used to clear binary large object XML data when an entry is removed from the order before the document is saved.



Name Location Description

/SLCE/EHI_SAVE_PREV_ITEM Beginning of subroutine CONFIGURATION_ADD_STRUCTURE (Include FV45SFCO_CONFIGURATION_ADD_STR)

Used to save the previous item for the determination of parent line item.

/SLCE/EHI_SKIP_ERROR Beginning of method SET_PART_OF_INTERNAL (class CL_CUX_INSTANCE_TREE_CORE)

Used to skip a BOM-related exception.

/SLCE/EHI_SKIP_STREF_PLC2 Beginning of subroutine XVBAP_LOESCHEN_PRUEFEN_UPOS (Include FV45PFAP_XVBAP_LOESCHEN_PRUEF3)

Used to skip the BOM (STLNR) check for advanced mode.

/SLCE/EHI_SORT_INSTANCES End of function module V45CU_CONFIG_HAS_CHANGES

Used to sort the instances.

/SLCE/EHI_STLNR_SKIP Beginning of subroutine CONFIGURATION_LOAD_STRUCTURE (Include FV45SFCO_CONFIGURATION_LOAD_ST)

Used to skip the BOM check (STLNR) for advanced mode.

/SLCE/EI_COMM_PROFILE Beginning of method CHECK_WITH_KB_DATA (class CL_CU_PROFILE)

Used to get data from COMM_CFG* tables instead of SCE tables.

The following implicit enhancements are used in various methods of class CL_IM_CU_CONFIG_DELEGATION (the implementation class for BAdI CU_CONFIG_DELEGATION).

They are used to delegate control to methods of class /SLCE/CL_IM_CFG_IPC_ADAPTER (a copy of the standard class CL_CFG_IPC_ADAPTER).

Name Location

/SLCE/EI_CEI0_DDB_HAS_TYPE Beginning of method IF_EX_CU_CONFIG_DELEGATION~CEI0_DDB_HAS_TYPE (class CL_IM_CU_CONFIG_DELEGATION)

/SLCE/EI_CEIO_GET_CONDITIONS Beginning of method IF_EX_CU_CONFIG_DELEGATION~CEI0_GET_CONDITIONS (class CL_IM_CU_CONFIG_DELEGATION)


Name Location

/SLCE/EI_CE_C_HAS_CHANGES Beginning of method IF_EX_CU_CONFIG_DELEGATION~CE_C_HAS_CHANGES (class CL_IM_CU_CONFIG_DELEGATION)

/SLCE/EI_CE_C_HAS_MODEL Beginning of method IF_EX_CU_CONFIG_DELEGATION~CE_C_HAS_MODEL (class CL_IM_CU_CONFIG_DELEGATION)

/SLCE/EI_CE_C_PROCESSING Beginning of method IF_EX_CU_CONFIG_DELEGATION~CE_C_PROCESSING (class CL_IM_CU_CONFIG_DELEGATION)

/SLCE/EI_CE_C_SET_CBASE Beginning of method IF_EX_CU_CONFIG_DELEGATION~CE_C_SET_CBASE (class CL_IM_CU_CONFIG_DELEGATION)

/SLCE/EI_CE_I_CONFIGURE Beginning of method IF_EX_CU_CONFIG_DELEGATION~CE_I_CONFIGURE (class CL_IM_CU_CONFIG_DELEGATION)

/SLCE/EI_CE_I_GET_INFORMATION Beginning of method IF_EX_CU_CONFIG_DELEGATION~CE_I_GET_INFORMATION (class CL_IM_CU_CONFIG_DELEGATION)

/SLCE/EI_CE_I_GET_STATUS Beginning of method IF_EX_CU_CONFIG_DELEGATION~CE_I_GET_STATUS (class CL_IM_CU_CONFIG_DELEGATION)

/SLCE/EI_CE_I_GET_VCSD_UPDATE Beginning of method IF_EX_CU_CONFIG_DELEGATION~CE_I_GET_VCSD_UPDATE (class CL_IM_CU_CONFIG_DELEGATION)

/SLCE/EI_CHECK_DELEGATION Beginning of method IF_EX_CU_CONFIG_DELEGATION~CHECK_DELEGATION (class CL_IM_CU_CONFIG_DELEGATION)

/SLCE/EI_CUKO_CHECK_CONFIG Beginning of method IF_EX_CU_CONFIG_DELEGATION~CUKO_CHECK_CONFIGURATION (class CL_IM_CU_CONFIG_DELEGATION)

/SLCE/EI_CUKO_CONFIGURATION_IN Beginning of method IF_EX_CU_CONFIG_DELEGATION~CUKO_CONFIGURATION_INTIALIZER (class CL_IM_CU_CONFIG_DELEGATION)

/SLCE/EI_CUKO_CONFIG_TO_DB Beginning of method IF_EX_CU_CONFIG_DELEGATION~CUKO_CONFIGURATION_TO_DB (class CL_IM_CU_CONFIG_DELEGATION)



Name Location

/SLCE/EI_CUKO_DDB_COMPONENTS Beginning of method IF_EX_CU_CONFIG_DELEGATION~CUKO_DDB_HAS_COMPONENTS (class CL_IM_CU_CONFIG_DELEGATION)

/SLCE/EI_CU_SINGLE_CFG_CHANGED Beginning of method IF_EX_CU_CONFIG_DELEGATION~CU_SINGLE_CFG_CHANGED (class CL_IM_CU_CONFIG_DELEGATION)

/SLCE/EI_CU_SINGLE_CONFIGURE Beginning of method IF_EX_CU_CONFIG_DELEGATION~CU_SINGLE_CONFIGURE (class CL_IM_CU_CONFIG_DELEGATION)

/SLCE/EI_DDB_HAS_CHARAC Beginning of method IF_EX_CU_CONFIG_DELEGATION~CEI0_DDB_HAS_CHARACTERISTICS (class CL_IM_CU_CONFIG_DELEGATION)

/SLCE/EI_DDB_HAS_VALUES_INTERN Beginning of method IF_EX_CU_CONFIG_DELEGATION~CEI0_DDB_HAS_VALUES_INTERNAL (class CL_IM_CU_CONFIG_DELEGATION)

/SLCE/EI_DDB_SET_VALUES_INTERN Beginning of method IF_EX_CU_CONFIG_DELEGATION~CEI0_DDB_SET_VALUE_INTERNAL (class CL_IM_CU_CONFIG_DELEGATION)

/SLCE/EI_DISPLAY_CONFIGURATION Beginning of method IF_EX_CU_CONFIG_DELEGATION~VC_I_DISPLAY_CONFIGURATION (class CL_IM_CU_CONFIG_DELEGATION)

/SLCE/EI_GET_STATUS_SINGLE_LEV Beginning of method IF_EX_CU_CONFIG_DELEGATION~CE_C_GET_STATUS_SINGLE_LEV_CFG (class CL_IM_CU_CONFIG_DELEGATION)

/SLCE/EI_VC_I_GET_CONFIG Beginning of method IF_EX_CU_CONFIG_DELEGATION~VC_I_GET_CONFIGURATION (class CL_IM_CU_CONFIG_DELEGATION)


4.2.1.4 Defining the RFC Destination for Solution Configuration Engine SAP S/4HANA

Context

You use this procedure to define the RFC destination for communication of SAP S/4HANA system with the SSC engine on NW AS Java. You perform these steps in SAP S/4HANA.

Procedure

1. Enter transaction SM59.

2. Choose Create.3. Choose the Technical Settings tab page.4. Choose Registered Server Program.5. Choose Start Type of External Program as Default Gateway Value.6. Enter the required details.7. If you are using the SAP Gateway of the application server, leave the fields Gateway Host and Gateway

Service empty. If not, enter the following data:

Field Input

Gateway Host Host name (with domain name if necessary) or the IP address of the host on which the gateway is installed

Gateway Service Name of the gateway in the form sapgw <instance_number>

NoteThe connection type is T (TCP/IP Connection). The RFC destination must match the details you enter when defining the Java Resource Adapter on the Java application server.

8. Choose the Unicode tab and select the Unicode option for Communication Type with Target System.9. Save your entries.

NoteMaintain the same host name as in Creating the XCM Configuration for SSC JSP UI on NW AS Java.



Related Information

Creating the XCM Configuration for SSC JSP UI on NW AS Java [page 51]

4.2.2 Installing the SSC Engine on SAP NetWeaver AS Java (EJB IPC Installation)

Use

You use this process to deploy the components required for the EJB IPC and the JSP UI and to configure the required technical settings.

Process

1. You deploy the required application components to the Java application server.For more information about this, refer to the chapter Deploying Application Components to the Java Application Server.

2. You define a Java Resource Adapter.For more information about this, refer to the chapter Defining a Java Resource Adapter for ABAP to Java Communication.

3. You define an RFC for Java to ABAP communication.For more information about this, refer to the chapter Defining an RFC for Java to ABAP Communication.

Related Information

Deploying Application Components to the Java Application Server [page 28]Defining a Java Resource Adapter for ABAP to Java Communication [page 31]Defining an RFC Destination for Java to ABAP Communication [page 29]


4.2.2.1 Deploying Application Components to the Java Application Server

Prerequisites

The following prerequisites must be met before deploying the application components to the server:

● You have generated stack for SSC 3.0 SP02 using the Maintenance Planner .● You have downloaded the required SCAs into a directory in /usr/sap/<sid>.

Context

You use this procedure to deploy the required Software Component Archives (SCAs) to the Java application server using the Software Update Manager (SUM) tool on a SAP NetWeaver system.

The following SCAs are required:

● FBS_SOLCONF_IPC (contains the EJB IPC)● FBS_SOLCONF_SHRAPP (contains slcipc config UI, slcb2b, and slcb2c E Commerce)● SAP-CRMDIC (contains data dictionary for XCM configuration and E Commerce shop data)

Procedure

1. Download the SUM tool and the latest version of its documentation from https://support.sap.com/en/tools/software-logistics-tools.html System Maintenance Software Update/Upgrade using SUM for detailed information on how to update/deploy components in SAP systems using SUM.

2. Extract the archive to a folder on the primary application server of your SAP system.3. Update and configure the SAP Host Agent to the latest patch level.4. Connect from your local PC via your browser.5. Configure the SUM tool, especially point to the stack.xml as result of the Maintenance Planner.6. Execute the maintenance on your system.

NoteFor more information about the supported maintenance procedures and update paths, see the SAP Note 2742706 (Central Note - Software Update Manager 2.0 SP06) and its attachments.

For detailed information about the Software Update Manager, see the blog Software Update Manager (SUM): introducing the tool for software maintenance on the SAP Community Network.



http://help.sap.com/disclaimer?site=https%3A%2F%2Fapps.support.sap.com%2Fsap%28bD1lbiZjPTAwMQ%3D%3D%29%2Fsupport%2Fmp%2Findex.html

http://help.sap.com/disclaimer?site=https%3A%2F%2Fsupport.sap.com%2Fen%2Ftools%2Fsoftware-logistics-tools.html

http://help.sap.com/disclaimer?site=https%3A%2F%2Fsupport.sap.com%2Fen%2Ftools%2Fsoftware-logistics-tools.html


http://help.sap.com/disclaimer?site=https%3A%2F%2Fblogs.sap.com%2F2012%2F11%2F07%2Fsoftware-update-manager-sum-introducing-the-tool-for-software-maintenance%2F

http://help.sap.com/disclaimer?site=https%3A%2F%2Fblogs.sap.com%2F2012%2F11%2F07%2Fsoftware-update-manager-sum-introducing-the-tool-for-software-maintenance%2F

Results

If the SUM procedure completes successfully, login to your JAVA system and access the NetWeaver Administrator(NWA) System Information (Components Info) where you should be able to find the installed software components.

4.2.2.2 Defining an RFC Destination for Java to ABAP Communication

Prerequisites

The technical (system) user created for communication between the SSC Engine on SAP NW AS Java and the ABAP back-end has the authorization role /SLCE/LO_SLC.

Context

You use this procedure to configure an RFC destination for Java to ABAP communication. You perform these steps in the SAP NetWeaver Administrator.

Procedure

1. On the Configuration tab page in the SAP NetWeaver Administrator service, choose Destinations.2. In the Destination Wizard, enter the following details:

Field Value

Hosting System <System ID of the local NW AS Java>

Destination Name SPACE (do not change the destination name; SPACE is mandatory)

Destination Type RFC

3. Choose Next.4. In the Connection and Transport dialog, enter the following details for the back-end system (for example,

ABAP system):


Field Value

Load Balancing No

Target Host <Target host>

System Number <System number>

System ID <System ID>

Gateway Host <Gateway host>

Gateway Service <Gateway service>

SNC Inactive

5. If you are using the SAP Gateway of the application server, leave the fields Gateway Host and Gateway Service empty. If not, enter the relevant data.

6. Choose Next.7. In the Logon Data dialog, enter the following details for the back-end system (for example, ABAP system):

Field Value

Authentication Technical User

Language <Language>

Client <Client>

User Name <User name>

Password <Password>

8. Choose Next.9. In the Specific Data dialog, enter the following details:

Field Value

Pooled Connection Mode Yes

Max Connections 10

Pool Size 5

Max. Wait Time in ms 10,000

CPIC Trace Level -1: Global CPIC Trace Level



4.2.2.3 Defining a Java Resource Adapter for ABAP to Java Communication

Context

You use this procedure to configure the Java Resource Adapter for the back-end system (SAP S/4HANA). You perform these steps in the SAP NetWeaver Administrator.

NoteThe program ID used in this procedure must be identical to the one you specify when defining the RFC destination in transaction SM59 in the back-end system (SAP S/4HANA). For more information, see Defining the RFC Destination for the Solution Configuration Engine in SAP S/4 HANA.

Procedure

1. On the Configuration tab page in SAP NetWeaver Administrator, choose Infrastructure.2. Choose Application Resources.

3. Choose Create New Resource New Resource Adapter .4. On the Names tab page, enter the following details:

Field Value

Template SAPJRA Template

Application ClonedRA FBS_SLC_JRA

5. On the Settings tab page, enter the following details:

Field Value

JNDI Name FBS_SLC_JRA

Class Name com.sap.mw.jco.jra.JRA$ResourceAdapterImpl

Work Manager Max Thread Count -1

Work Manager Start Thread Count -1

6. On the Properties tab page, enter the following details:


Name Type Value Description

ProgramID Class.java.lang.String <Program ID defined in SM59>

The program ID of the RFC connection created during the ABAP add-on installation can be used here only.

MaxReaderThreadCount Class.java.lang.Integer 10 Maximum count of listening servers

GatewayServer Class.java.lang.String <Gateway server> Gateway host as configured in SM59

GatewayService Class.java.lang.String <Gateway service> Gateway service

DestinationName Class.java.lang.String SPACE Destination name as config-ured in destination service

7. If you are using the SAP Gateway of the application server, leave the fields Gateway Host and Gateway Service empty. If not, enter the data on the Dependent JCA Connection Factories tab page and choose JCA Connection Factory Details.

8. On the Configuration Properties tab page, enter the following details:

Name Type Value

DestinationName Class.java.lang.String SPACE

9. Save your entries.

Related Information

Defining the RFC Destination for Solution Configuration Engine SAP S/4HANA [page 26]

4.2.3 Solution Modeling Environment Installation

Use

You use this process to install the solution modeling environment (SME) in Eclipse and configure the required system connections.



System Requirements

The Solution Modeling Environment has the following client system requirements:

Software Version

Operating System Microsoft Windows operating system that supports Java 1.8

Java Runtime Environment Java 1.8

Eclipse Eclipse 4.7 (Oxygen)

We have updated the latest supported version of Eclipse to Eclipse OXYGEN since release 2.5 patch 17 and release 2.0 patch 7. This is the main Eclipse version where new patches are tested. Compatibility with older versions of Eclipse are not guaranteed.

Database For more information, see the Product Availability Matrix

Java Connector (JCo) 3.0 (delivered with the SME)

The SAP NetWeaver JEE aplication server has the following system requirements:

Software Version

NW Application Serer JAVA 7.4 SP0

Java Connector (JCo) 3.0

Process

1. You install the solution modeling environment as a plug-in in Eclipse.For more details about this, refer to the chapter Installing the Solution Modeling Environment.

2. You configure a connection to a database system that is used to store your local solution models (knowledge bases).For more details about this, refer to the chapter Configuring the Connection to the Local Database.

3. You configure a connection to the target master data system.For more details about this, refer to the chapter Configuring the Connection to the Master Data System.

4. You create the tables in the local solution modeling environment database.For more details about this, refer to the chapter Creating Tables in the Solution Modeling Environment Database.

5. You configure the Solution Modeling Environment and SAP S/4HANA for knowledge base download.For more details about this, refer to the chapters Configuring the SAP S/4HANA for Knowledge Base Download and Configuring the Solution Modeling Environment for Knowledge Base Download.


http://help.sap.com/disclaimer?site=https%3A%2F%2Fsupport.sap.com%2Fpam

Related Information

Installing the Solution Modeling Environment [page 34]Configuring the Connection to the Local Database [page 36]Configuring the Connection to the Master Data System [page 39]Creating Tables in the Solution Modeling Environment Database [page 40]Configuring SAP S/4HANA for Knowledge Base Download [page 40]Configuring the Solution Modeling Environment for KB Download [page 42]

4.2.3.1 Prerequisites for SME Installation

Prerequisites for Microsoft SQLServer

● You have downloaded the Database MS SQL Server with management toolsUse the version appropriate for your version of Microsoft Windows (32-bit version or 64-bit version).

● You have configured the TCP/IP port in the SQL Server Configuration Manager as follows:1. Go to SQL Server Configuration Manager2. Change the IP address under SQL Server Network Configuration, for the protocols of the named

instance, for example, SQLSERVER013. Under IPA11, maintain the TCP port as 1433 and click onApply4. Restart the server to reflect the changes.

NoteYou must configure the database using a case-sensitive names such as “SQL_Latin1_General_CP1_CS_AS”. Collations with “CI” are case-insensitive and must be avoided.

CautionThe SME requires an SQL user to connect to the database system; Windows authentication is not supported. The user established during MS SQL Server installation (defaults to sa) can be used. You must know the password for this account later when you use this connection to connect to the database.

4.2.3.2 Installing the Solution Modeling Environment

Use

You use this procedure to install the Eclipse plug-in for the solution modeling environment and the data loader.



Prerequisites

● You have installed Eclipse version 4.7 (for supported versions, see ).● You have downloaded the zip file for the solution modeling environment plug-in. The file is available from

SAP Software Download Center under Support Packages and Patches By Alphabetical Index (A-Z)C SAP SOLUTION SALES CONFIG SAP SOLUTION SALES CONFIG 3.0 ENTRY BY COMPONENTCPQ SOL MODELING ENV FBS_SOLCONF_SME 3.0 .Ensure that you download the patch for the latest support package.

● You have an internet connectionIf you are unable to connect to the internet, contact your network administrator.

● During SME installation, the system on which Eclipse is running must have internet connectivity. Eclipse uses the default internet connectivity configured by proxy settings on OS level (for example, in Windows

Internet Options Connections LAN Settings or any other OS connectivity settings). If no internet connectivity is configured, you must configure the proxy settings in Eclipse under WindowsPreferences General Network Connection , as part of the standard Eclipse set up procedure.

Procedure

1. In Eclipse, choose Help Install New Software...2. Choose Add...3. Enter a name and the location of the zip file for the plug-in and then choose OK.4. Choose Select All.5. Choose Next.

The system calculates the requirements and dependencies and then prompts you to review and confirm the installation details.

6. Choose Next.The system prompts you to review and accept the license agreement.

7. Select I accept the terms of the license agreement and then choose Finish.Eclipse displays a progress bar while the plug-ins are being installed. When the installation is complete, the system prompts you to restart Eclipse.

If you encounter errors caused by missing components, see Appendix I: Guidance for SME Installation Prerequisites.

Related Information

Prerequisites for SME Installation [page 34]


http://help.sap.com/disclaimer?site=https%3A%2F%2Flaunchpad.support.sap.com%2F%23%2Fsoftwarecenter

4.2.3.3 Adjusting Eclipse Memory Parameters

To ensure that the SME operates in a stable manner, we recommend that you increase the memory parameters of Eclipse, for example, the heap size.

Maintain vmargs parameters Xms and Xmx in the eclipse.ini file. Parameter XX:MaxPermSize is required only up to Java 7 (Java 8 does not have a separate permanent generation space anymore). For example:

● -Xms128m● -Xmx2g● -XX:MaxPermSize=128M● -Xss1m

If you experience a StackOverflowError when using the SME, increase the stack size further, for example, -Xss2m.

4.2.3.4 Configuring the Connection to the Local Database

Use

You use this procedure to configure a connection between Eclipse and a database system that is used to store your local solution models (knowledge bases). You perform these steps in Eclipse.

Prerequisites

● You have installed EclipseFor information on supported versions, see System Requirements.

● You have installed the solution modeling environment plug-in in Eclipse.● You have installed a database system such as Microsoft SQL Server

For information about supported database systems, see the product availability matrix at http://support.sap.com/pam

● You have created a database on the database systemFor more information, see Appendix I: Guidance for SME Installation Prerequisites

NoteYou must configure the database using a case-sensitive names such as “SQL_Latin1_General_CP1_CS_AS”. Collations with “CI” are case-insensitive and must be avoided.





Procedure

Downloading a Database JDBC Driver:

Download the JDBC driver that is specific to the database system that you use.

Example Using Microsoft SQL Server

The SME supports two JDBC drivers for Microsoft SQL Server: Microsoft SQL Server JDBC and jTDS JDBC driver. One of these drivers must be downloaded:

● Microsoft SQL Server driver 3.0: http://www.microsoft.com/en-us/download/details.aspx?id=19847● Microsoft SQL Server driver 4.0: http://www.microsoft.com/en-us/download/details.aspx?id=11774● jTDS 1.3.1: http://sourceforge.net/projects/jtds/files/jtds/1.3.1/

The jTDS driver works for all supported MS SQL Server versions. If you choose the Microsoft driver, you should use either version 3.0 or 4.0. The version of the driver you use depends on the version of the SQL Server to which you want to connect. For information about the supported SQL Server versions, see the Microsoft download pages in the chapter System Requirements. In general, you require version 3.0 if you are running on SQL Server 2003 or lower; all later SQL Servers require version 4.0.

Registering a JDBC Driver:

Register the downloaded JDBC driver in the SME as follows:

1. Choose Window Preferences .

2. Choose SAP CPQ for Solution Sales Configuration Drivers .3. Choose Add... and select the driver that you downloaded in the previous section.4. Choose OK.

Defining a Database Connection:


2. Choose SAP CPQ for Solution Sales Configuration Connections .3. Choose Add...4. Enter a name for your connection and select the connection type SQL Server.5. Enter localhost as the server name.6. Enter the relevant port.

By default, this is port 1433.7. Enter client 000.8. Enter your login name for the SQL user.9. Confirm your entries with OK.

Defining a HANA Database Tenant Connection

The Solution Modeling Environment allows HANA database tenant connection setup. For more details regarding the setup and port assignment in tenant connection, refer to Connections for Tenant Databases from the SAP Help Portal SAP HANA Platform Administration SAP HANA Tenant DatabasesConnections for Tenant Databases .


http://help.sap.com/disclaimer?site=http%3A%2F%2Fwww.microsoft.com%2Fen-us%2Fdownload%2Fdetails.aspx%3Fid%3D19847

http://help.sap.com/disclaimer?site=http%3A%2F%2Fwww.microsoft.com%2Fen-us%2Fdownload%2Fdetails.aspx%3Fid%3D11774

http://help.sap.com/disclaimer?site=http%3A%2F%2Fsourceforge.net%2Fprojects%2Fjtds%2Ffiles%2Fjtds%2F1.3.1%2F


Recommended Database Drivers for SME

You can use the database support matrix to check which databases are supported for use with SME. For more information about these data bases, refer to SAP Note 1876540 .

Database JDBC Driver Comments

Microsoft SQL Server jTDS 1.3.1 jTDS 1.3.1 version of Microsoft SQL Server driver is recommended

Microsoft SQL Server 2 sqljdbc_4.0.2206.100 sqljdbc_4.0.2206.100 version of Microsoft SQL Server 2 driver is recommended

MySQL mysql-connector-java-5.1.23.jar

mysql-connector-java-5.1.23.jar version of MySQL driver is recommended

Oracle ojdbc6-11.2.0.2.0.jar ojdbc6-11.2.0.2.0.jar version of Oracle driver is recommended

MaxDB sapdbc.jar sapdbc.jar version of MaxDB driver is recommended

HANA DB ngdbc-2.0.5.jar ngdbc-2.0.5.jar version of HANA DB driver is recommended

More Information

For more information about setting up connections to the local database, refer to the SAP Help Portal and navigate to SAP Solution Sales Configuration for SAP S/4HANA Relevant version Product AssistanceSolution Modeling Environment Setup of Solution Modeling Environment SAP Modeling PerspectiveExporting a Project Setup of Local Database Connection .

Related Information

Prerequisites for SME Installation [page 34]





4.2.3.5 Configuring the Connection to the Master Data System

Use

You use this procedure to configure a connection between Eclipse and the master data system (for example, SAP S/4HANA). You perform these steps in Eclipse.

Prerequisites

● You have installed the solution modeling environment plug-in.● You have installed a database system.● You have created a database in the database system.

Procedure


2. Choose SAP CPQ for Solution Sales Configuration Connections .3. Choose Add...4. Select the connection type S/4HANA for your master data system.5. Enter the required details and choose OK.

NoteThe S/4HANA back-end user that is defined in the connection S/4HANA must have authorization role /SLCE/SME assigned. For more information about these roles, see SAP Note 1685392 (Backend Authorizations for Solution Modeling Environment). We recommend that you use a dialog user for this connection so that you have meaningful information in the Created By and Changed By fields in the knowledge bases.

More Information

For more information about setting up connections to the master data system, refer to the SAP Help Portal and navigate to SAP Solution Sales Configuration for SAP S/4HANA Relevant version Application Help Solution Modeling Environment Setup of Solution Modeling Environment SAP Modeling PerspectiveExporting a Project Setup of SAP S/4HANA Connection .




4.2.3.6 Creating Tables in the Solution Modeling Environment Database

Prerequisites

● You have installed the solution modeling environment plug-in.● You have installed a database system.● You have created a database in the database system.● You have configured the connection to the database.

Context

You use this procedure to create the required tables in the solution modeling environment database. You perform these steps in Eclipse.

Procedure

1. In Eclipse, ensure that the SAP Modeling perspective is opened.

2. Choose SAP Modeling Create Tables .3. Choose the target database.4. Choose Finish.

4.2.3.7 Configuring SAP S/4HANA for Knowledge Base Download

Use

You use this procedure to define the RFC destination required for pulling knowledge bases from SAP S/4HANA to the database system you connected to the SME. You perform these steps in SAP S/4HANA.



Prerequisites

To define the RFC destination required for pulling knowledge bases from SAP S/4HANA, the following requirements must be fulfilled:

● You must fetch knowledge bases from SAP S/4HANA for use in the solution modeling environment.● You must have configured the connection from the SME to S/4HANA.● The user defined in the connection must have authorization role /SLCE/SME.● You must be authorized to create RFC destinations in SAP S/4HANA.

Procedure

1. Call transaction SM59.2. Choose Create.3. Enter the following data:

○ Name of the new RFC destination (for example, IPC_DL)○ Description (for example, IPC Data Loader)○ Connection Type T (TCP/IP Connection).

4. Save your entries.5. Choose the Technical Settings tab page and select Registered Server Program.6. Enter a program ID (for example, IPC_DL).7. Under Gateway Options, enter the name of your gateway host and gateway service.

To find possible entries, create a new session by choosing System Create Session . Then choose Tools Administration Monitor System Monitoring Gateway Monitor (transaction SMGW); in the

menu, select Goto Parameters Display and check the entries under Gateway Hostname and Gateway Service.

8. Choose the Unicode tab page and ensure that the radio button Unicode is selected.9. Save your entries.

CautionYou cannot test your connection (using the Test Connection pushbutton) at this point. This is possible only while the data loader is running and registered at the gateway of the S/4HANA system.


4.2.3.8 Configuring the Solution Modeling Environment for KB Download

Prerequisites

● You have installed EclipseFor more information on supported versions, see the chapter System Requirements.

● You have installed the solution modeling environment plug-in.● You have installed a database system.● You have created a database in the database system.● You have configured a connection to the local database.● You have configured a connection to an SAP S/4HANA system.● You have set up an RFC destination in SAP S/4HANA.

For more information about this, see Configuring the SAP S/4HANA for Knowledge Base Download.

Context

You use this procedure to set up a connection between Eclipse and your SAP S/4HANA system. You can then download the knowledge bases (KBs) to the database system connected to the SME. You perform these steps in Eclipse.

Procedure

1. In your Eclipse Environment, choose Window Preferences .

2. Choose SAP CPQ for Solution Sales Configuration Data Loader .3. Choose Add...4. Select a source S/4HANA system: Choose a S/4HANA system from which knowledge bases are to be

pulled.

For more information on setting up this connection, refer to the chapter Configuring the Connection to the Master Data System.

5. Choose a client.6. Enter the name of the RFC destination that was created in Configuring the SAP S/4HANA for Knowledge

Base Download.7. Select a target database system.8. Choose an available connection.9. Choose a client.



Related Information

Configuring the Connection to the Master Data System [page 39]Configuring SAP S/4HANA for Knowledge Base Download [page 40]

4.2.3.9 Installing a Patch for the Solution Modeling Environment

You use this procedure to install a patch of the Eclipse plug-in for the solution modeling environment and the data loader.

Prerequisites

You have downloaded the zip file for the solution modeling environment plug-in patch.

Procedure

You can update the existing SME plug-in, or uninstall and reinstall it completely.

To Update the Existing SME Plug-In

Perform the procedure described in Installing the Solution Modeling Environment.

CautionTo update to a new version of the Solution Modeling Environment, do not use the Check for update feature. Instead, install the new version using Install New Software. If you are updating the SME to a new version, uncheck Contact all update sites during install to find required software. However, if you are installing the SME on a fresh Eclipse installation, you should always select this checkbox.

To Uninstall and Reinstall the SME Plug-In

1. In Eclipse, choose Help About Eclipse... Installation Details .2. Highlight the currently installed SME features and choose Uninstall.3. Choose OK to close the screen.

The program restarts.4. Perform the procedure described in Installing the Solution Modeling Environment.


Related Information

Installing the Solution Modeling Environment [page 34]

4.2.4 Installation of User Exit Deployment Mechanism

Use

You use this process to set up the user exit deployment mechanism that is used to manage (upload and delete) user-defined functions (declarative functions and pfunctions in the configuration engine and pricing formulas in the pricing engine) on Application Server JAVA.

Process

1. You define the storage location of user-defined functions in the application properties of AS JAVA.2. You assign authorization roles to users on AS JAVA.3. You install the user exit deployment Maven plug-in.

4.2.4.1 Define Storage Location of User-Defined Functions on AS JAVA

Use

You use this procedure to define the storage location of user-defined functions.

Prerequisites

You have installed the EJB IPC on AS JAVA (For more information about this, see Installing the SSC Engine on SAP NetWeaver AS Java (EJB IPC Installation)).

Procedure

Configure the following properties:

● fbs.slc.ipc.exit.isLoadExitsFromDbEnabled



● fbs.slc.ipc.exit.useAbapBackEnd● fbs.slc.ipc.exit.rfcDestinationName

The following table explains the purpose of each of these properties:

Property Name Description

fbs.slc.ipc.exit.isLoadExitsFromDbEnabled Set this to true or false.

NoteThe default value is false.

If set to false, user-defined functions will be read from the .jar files located on AS JAVA in folder <path to AS JAVA instance>/j2ee/cluster/apps/sap.com/cdev~fbs_slc_java/app_libraries_container.

If set to true, user-defined functions are read from a database. Ensure that jar files fbs_slc_exit_pvFunctions.jar and fbs_slc_exit_pricing.jar, which are located on AS JAVA in folder <path to AS JAVA instance>/j2ee/cluster/apps/sap.com/cdev~fbs_slc_java/app_libraries_container, are empty in this case.

fbs.slc.ipc.exit.useAbapBackEnd Set this to true or false.

NoteThe default value is false.

This setting is only relevant if fbs.slc.ipc.exit.isLoadExitsFromDbEnabled is set to true.

If set to false, user-defined functions will be stored and read using the default database connection of AS JAVA.

If set to true, user-defined functions will be stored and read to/from an AS ABAP database as specified in property fbs.slc.ipc.exit.rfcDestinationName.

fbs.slc.ipc.exit.rfcDestinationName Set this to an existing destination name. This setting is only relevant if fbs.slc.ipc.exit.isLoadExitsFromDbEnabled and fbs.slc.ipc.exit.useAbapBackEnd are set to true.

By default, the destination name is set to SPACE, which is also used by the SSC engine to read knowledge-base master data.


Related Information

Installing the SSC Engine on SAP NetWeaver AS Java (EJB IPC Installation) [page 27]

4.2.4.2 Assign Authorization Roles on AS JAVA

Use

You use this procedure to assign proper authorization to users on AS JAVA that are to manage (upload and delete) user-defined functions.

Prerequisites

You have installed the EJB IPC on AS JAVA (see Installation on SAP NetWeaver AS Java (EJB IPC Installation) [page 27]).

Procedure

Assign authorization role SSC_USER_EXIT_WRITE to AS JAVA users that are to be allowed to execute the management operations.

NoteIf user-defined functions are configured to be stored on AS ABAP (see Define Storage Location of User-Defined Functions on AS JAVA [page 44]), additional authorizations are needed on AS ABAP. The necessary authorizations will be assigned when you execute the post-installation step in Assigning Authorization Roles [page 49].

4.2.4.3 Installing the User Exit Maven Plug-in

Use

You use this process to install the user exit deployment Maven plug-in to manage user-defined functions (declarative functions and pfunctions in the configuration engine and pricing formulas in the pricing engine) on Application Server JAVA.



Prerequisites

● You have installed EclipseFor more information on supported versions, refer to the chapter System Requirements.

● You have installed the solution modeling environment plug-in.

Procedure

1. Download, install, and configure Apache Maven ( http://maven.apache.org ) with minimum version 3.1.1.2. Install the user-exit deployment Maven plug-ins to your local Maven repository.

The plug-ins are packaged with the SME. After the SME has been installed successfully, your Eclipse installation directory contains the batch script ssc-mvn-install.cmd. Execute it to install the plug-ins.

NoteAs an alternative to manually installing the Maven plug-ins to your local Maven repository, you can also choose to deploy the plug-ins to your company's Maven artifact repository. For this purpose, the Eclipse installation directory contains the batch script ssc-mvn-deploy.cmd that performs this step. Before executing this script, ensure that you set the properties REPOSITORY_URL and REPOSITORY_ID within this script to appropriate values.

4.3 Post-Installation Tasks

This section describes tasks that should be completed after you've finished installing SAP Solution Sales Configuration for SAP S/4HANA.

4.3.1 Importing Configuration Master Data

Prerequisites

● You have installed the solution modeling environment plug-in in Eclipse.● You have configured the connection to the source SAP S/4HANA system and added the connection to the

data loader configuration settings.


http://help.sap.com/disclaimer?site=http%3A%2F%2Fmaven.apache.org

Context

Once you have installed the solution modeling environment and have configured the required connections, you can import configuration master data from the SAP S/4HANA system to the solution modeling environment database.

You perform these steps in the Eclipse-based solution modeling environment.

Procedure

1. Choose File Import...

The system displays a dialog prompting you to choose an import source.

2. Choose SAP Solution Configuration Data Loader .3. Choose Next.

The system displays a dialog box prompting you to choose a data loader configuration from a list of the configured connections.

4. Choose the configuration for the SAP S/4HANA system and then choose Edit.5. Ensure that the correct RFC destination is entered.6. Choose OK.7. Choose the configuration for the SAP S/4HANA system and then choose Next.8. Enter the required passwords and choose Finish.

4.3.2 Generating Authorization Profiles

Generating Authorization Profiles in SAP S/4HANA

In transaction PFCG, generate authorization profiles for the following authorization roles:

● /SLCE/ADMIN● /SLCE/SME● /SLCE/DIALOG_USER● /SLCE/LO_SLC● /SLCE/UI_DESIGNER● /SLCE/UI_ADMINISTRATOR● /SLCE/PRODUCT_CONFIGURATOR



Generating Authorization Profiles in the Front-End Server

Authorization Role User

/SLCUI/UI_ADMINISTRATOR UI composer administrator

/SLCUI/UI_DESIGNER UIC designer

/SLCUI/PRODUCT_CONFIGURATOR UIC runtime

NoteIf you want to establish trusted relationships between the front end and back end server, you must add the authorization object S_RFCACL to the user roles.

4.3.3 Assigning Authorization Roles

You must ensure that your system administrator has assigned the following authorization roles to the system user created for communication between the EJB-IPC and the ABAP back-end (user for destination SPACE) in the SAP systems, and the dialog user that performs the interactive configuration.


/SLCE/LO_SLC Technical user specified for SPACE destination

/SLCE/ADMIN Admin user for SAP Solution Sales Configuration for SAP S/4HANA

/SLCE/SME Modeling user to import/ export knowledge base from SME

/SLCE/DIALOG_USER SAP Solution Sales Configuration for SAP S/4HANA authorizations for dialog user

For UI Composer UI, assign these roles:


/SLCE/PRODUCT_CONFIGURATOR Role to launch configuration for any product in an order.

/SLCE/UI_ADMINISTRATOR Role to manage stores created by you in UI Composer.

/SLCE/UI_DESIGNER Role to manage stores created by you in UI Composer.

/SLCUI/PRODUCT_CONFIGURATOR Role to launch configuration for any product in an order - to be maintained in front-end server.



/SLCUI/UI_ADMINISTRATOR Role to manage stores created by you in UI Composer - to be maintained in front-end server.

/SLCUI/UI_DESIGNER Role to manage stores created by user in UI Composer - To be maintained in front-end server.

NoteThe role for SAP Solution Sales Configuration for SAP S/4HANA is in addition to the other roles that the dialog user requires for his business operations.

Additionally, there is now a new authorization object /SLCE/DUSR which enables you to authorize the executing of dialog transactions of the SAP Solution Sales Configuration. This can be done by adding this authorization object into the custom dialog user's role directly.

You view this new authorization object by implementing the Note 3023690 -Missing authorization object in the solution sales configuration transaction codes.

4.3.4 Scheduling Background Jobs

A background job for replicating knowledge base updates to EJB-IBP (for example, exported from SME to SAP S/4HANA, or created from a classic-mode VC model) needs to be created and scheduled after installation. This job must be run periodically with a short interval to avoid delayed availability of updated KBs. We recommend a job frequency of one or two minutes.

Procedure

Schedule the following job to run periodically:

SAP S/4HANA /SLCE/UPDATE_EJB_CACHE

4.3.5 UI Configuration

Use

Here, you define the UI to be used with SAP Solution Sales Configuration for SAP S/4HANA. You can define the transactions for which you would like to use a specific UI and you can set up an identifier (Setup ID) for this




combination. You can use this Setup ID to associate with and identify a configurable material. This allows you, for example, to create quotations and sales orders with the SAP Solution Sales Configuration for SAP S/4HANA while using the standard LO-VC or AVC for downstream processes, like production planning. More information can be found in UI Composer Runtime User Interface

4.3.5.1 Using the JSP UI

4.3.5.1.1 Creating the XCM Configuration for SSC JSP UI on NW AS Java

Context

Here, you define a set of customizing parameters for standard configuration of the user interface in the Extended Configuration Management (XCM). Once defined, you can save them and allot a relevant name. This name must be registered in the backend system to signify the set of customizing parameters to use for the UI display.

You may define different parameter sets for different users and their respective scenarios, using the following procedure:

Procedure

1. Open the XCM Settings page using the following URL: http:// <host>: <port>/slcipc/admin/xcm/init.do.

2. On the left-hand side navigation pane, choose Application Configuration SAP .3. Create the XCM Configuration for the systems by selecting:

○ erp for your SAP S/4HANA system

4. To enable the input fields, choose Edit.5. Enter the name of the XCM Configuration (for example, XCMCONFIG_SAL for a sales document scenario or

XCMCONFIG_SIM for a simulation) and choose Create.

6. To create the JCO Connection, choose jco.7. Enter the JCO name and choose Create.8. Select the base configuration as Server_connect and enter the details of the SAP system for which the JCo

connection needs to be created. The SAP system details can be found on the SAP Logon pad.9. To save the configuration, choose Save Configuration.

If the JCo connection is successfully created (indicated by a green light), choose Run Test.10. Choose Back to Application Configuration and select the JCo name now visible in the jcodata dropdown list.


https://help.sap.com/viewer/d048886b27c9483987c0455c2aa4adee/1907%20001/en-US/99e1a835510f413c991579592b718816.html

11. Choose Default Configuration for the XCM Settings.12. Choose Display.13. Save the configuration.

The new XCM setting appears on the Customer tab page of the Application Configuration (left-hand side navigation pane) panel.

14. Restart the IPC services in NWA.

4.3.5.1.2 Registering the XCM Configuration on SAP S/4HANA

1. Maintain the destination URL of the SSC configuration UI application on SAP S/4HANA:1. In transaction SM59, specify RFC destination type G (HTTP Connection to External Server) with the

name IPC_CONFIGURATION_UI.2. As the target host, enter the fully qualified host name of the NW Java server without the leading

https.3. As the service number, enter the HTTPS port of the Web AS J2EE Engine that is used for secured SSL

communication (5NN01, where NN = instance number).4. Enter the path prefix /slcipc/ipc/command.do.5. Under Logon & Security, enable the Secure Protocol SSL with Anonymous SSL Client Certificate.

2. Maintain the XCM application configuration name - “XCM scenario”:

1. In Customizing, choose Logistics - General Variant Configuration Maintain Reference to Configuration User Interfaces (or maintain table TCUUISCEN).

2. In the XCM Scenario field, enter the name of the XCM scenario created above for the following keys:

Application Using IPC UI Sub Application XCM Scenario

ERP DEFAULT XCMCONFIG_SAL

ERP SALES XCMCONFIG_SAL

ERP SIMULATION XCMCONFIG_SIM

You can use the same XCM scenario for sales document configuration and simulation, or you can define specific ones. If you define specific ones, you only have to maintain the entry with the DEFAULT sub application.



4.3.5.2 Using the UI Composer UI

4.3.5.2.1 Establish a Connection from Back-End System to Front-End Server

Each back-end system connected to the launchpad needs to know the location of the SAP Fiori front-end server on which the launchpad runs.

Steps

Perform the following steps on the relevant back-end systems:

1. Create an RFC destination of connection type 3 (ABAP connection).This connection type is used by Role Maintenance (transaction PFCG) to determine which authorizations are required to run the back-end applications referenced by the launchpad. See, Assign Tile Catalogs to Roles.1. Select the ABAP Connections node and choose Create.2. In the RFC Destination field, enter a name following the naming convention <Logical System

Alias>_RFC (for example FESCLNT700_RFC).3. Enter a description.4. On the Technical Settings tab, select the load balancing status and provide the required information:

○ Yes: Specify target system, message server, and group.○ No: Specify target host and instance number.

5. On the Logon & Security tab, enter the client of the front-end server system to which you want to connect and mark the Current User checkbox.

2. Create an RFC destination of connection type H (HTTP(S) connection).This connection type is used to call the SAP Fiori launchpad from a back-end application.1. In Customizing, choose SAP NetWeaver Gateway OData Channel Connection Settings SAP NetWeaver

Gateway to SAP System and launch the IMG activity Manage RFC Destinations or directly launch transaction SM59.

2. Select the HTTP Connections to ABAP System node and choose Create.3. In the RFC Destination field, enter a name following the naming convention <Logical System

Alias>_HTTPS (for example FESCLNT700_HTTPS).4. Enter a description.5. On the Technical Settings tab, enter the following:

○ Host field: Enter the HTTPS host.○ Port field: Enter the HTTPS port.○ Path Prefix field: Enter the default ICF path to SAP Fiori launchpad (for example /sap/bc/ui2/

flp). See, Launching the Launchpad.6. On the Logon & Security tab, mark the Trusted Relationshipcheckbox and provide the following:

○ Client field: Enter the client of the front-end server system to which you want to connect.○ Mark the Current User checkbox.○ Under Security Options, set SSL to Active and SSL Certificate to Default SSL Client.


https://help.sap.com/viewer/a7b390faab1140c087b8926571e942b7/7.52.0/en-US/1fb206d06c074c068edf1418cf301899.html

https://help.sap.com/viewer/a7b390faab1140c087b8926571e942b7/7.52.0/en-US/1fb206d06c074c068edf1418cf301899.html

https://help.sap.com/viewer/a7b390faab1140c087b8926571e942b7/7.52.0/en-US/e08c9cfe07b8431b884048700067aa1a.html

4.3.5.2.2 Creating an SAP System Alias

Describes where the SAP system alias should point to for the applications.

You need to specify where the SAP system alias should point to for the applications. Set up the system alias according to your SAP Gateway content scenario and your system landscape. The system alias is the result of the routing for an inbound request on SAP Gateway and it can be a remote or a local system. If the system alias is flagged as a Local SAP GW instance, it means that the system that is responsible for processing (managing and storing) the data of an inbound request is the local SAP Gateway instance itself.

1. In transaction SPRO open the SAP Reference IMG and navigate to: SAP NetWeaver SAP GatewayOData Channel Configuration Connection Settings SAP Gateway to SAP System Manage SAP System Aliases and click on the Activity icon.

2. Choose New Entries.3. Enter the following details for the SAP system alias:

Field Description

SAP System Alias Name of the system alias.

Description Descriptive text for the system alias

Local SAP GW Unselected

For Local App The system alias is to be used by the backend. For more information, see the F1 help in the system and section Development in SAP Gateway Hub System.

RFC Destination Specify the RFC destination defined for your SAP system.

Software Version This setting is specified by the content scenario you are using. Typically it is DEFAULT.

System ID Name of the SAP target system.

NoteWhen specifying SAP system aliases, we recommend always to enter the system ID. The SAP target system, together with the target client, determines the system alias for a remote call to a backend system.

Client Target client

WS Provider System Name of the Web service provider business system. Here you only need to enter a setting if you use content scenarios which are configured via Web services.

4. Save your settings.



4.3.5.2.3 Activate SAP Gateway Services

Prerequisites

In addition to XCM settings described under topic Using the JSP UI, following customizing is required to enable UI Composer in SAP S/4HANA system.

Procedure

1. Maintain gateway services.

In the SAP Gateway frontend system, go to transaction /IWFND/MAINT_SERVICES and add a new service.

Provide system alias, choose Get Services to get all the available services in the system.

Add the following services: /SLCE/SSC_UI_DM_SRV and /SLCE/SSC_PC_DM_SRV

If you are providing some custom technical service name while adding these services, don’t forget to update authorization roles with following information:

Authorization role Authorization Parameters

/SLCUI/UI_ADMINISTRATOR S_SERVICE TADIR service

Prog. Id: R3TR

Object type: IWSG

Object name: Custom technical service name

/SLCUI/UI_DESIGNER

/SLCUI/PRODUCT_CONFIGURATOR

2. Activate servicesActivate the following SICF services:

○ SAP BC BSP SLCUI

○ SAP BC UI5_UI5 SLCUI

○ SAP OPU ODATA SLCE3. Customizing for gateway identification

○ Create an RFC destination (ABAP connection) pointing to gateway front-end server○ Update this information in table /SLCE/GW_RFCDEST

4. Customizing for knowledge base source system identification.

Update table /SLCE/PCFG_SYST with following information (update via maintenance view /SLCE/V_PCFG_SY):


○ Client: Client number of system where knowledge base is maintained○ Source system: System ID○ System type: E

RFC destination: RFC destination (ABAP connection) pointing to knowledge base source system. It is required even for embedded deployment

Default system: Set this flag

4.3.5.2.4 Launchpad Configuration for SAP GUI Tcodes

Steps:

1. In the SAP Backend system, go to transaction /UI2/SEMOBJ_SAP and add a new semantic object. Following semantic objects are delivered for SSC:

Semantic Object Semantic Object Name Application ComponentSemantic Object Description

SSCConfigureMaterial SSC Configure Material (Assign Products to UI Setup)

LO-SLC Update configurator for any product

SSCDPPSupport SSC DPP Support LO-SLC SSC DPP Support

SSCEJBIPCMaintain SSC Enterprise JavaBean Internet Pricing and Config-urator

LO-SLC In this Customizing activity, you maintain important client-dependent parameters that are required for using the Enterprise JavaBean Internet Pricing and Configu-rator (EJB-IPC).

SSCEditClassMaterialTexts SSC Edit Class Material Texts

LO-SLC Edit the texts that have been exported from your knowledge base in the Solution Modeling Environment (SME). You can also add texts in a language other than those that have been exported.

SSCGlobalConfiguration-Value

SSC Global Configuration Value

LO-SLC

SSCSqlSyntax SSC Sql Syntax LO-SLC In this Customizing activity, you maintain the SQL syntax for the various SQL statements. This table can then be read by other applications (for example, knowledge base



Semantic Object Semantic Object Name Application ComponentSemantic Object Description

SSCSupport SSC Support LO-SLC Utility for Solution Sales Configuration. Provides options to download XML,KnowledgeBase preload, display SLG logs and DPP

SSCUIComposer SSC UI Composer LO-SLC Launched UI composer designer view if user is authorized

SSCUIComposerSupport SSC UI Composer Support LO-SLC Utility to perform tasks specific to UI composer design time UI

SSCUploadDownloadTexts SSC Upload Download Texts LO-SLC Utility to upload/ download external texts

SSCViewConfigSetup SSC View Config Setup LO-SLC In this Customizing activity, you maintain the required UI type for the Display/Edit of the Solution Sales Configu-ration (SSC).

SSCVirtualBOMSeperator SSC Virtual BOM Seperator LO-SLC

2. Open the mass maintainer descriptor tool and create catalog for SAP GUI Tcodes.3. In the frontend system, add system alias entry in VIEW /UI2/V_ALIASCAT .4. In frontend system, run report /UI2/GET_APP_DESCR_REMOTE_DEV and extract the backend catalog.5. Use these catalogs to create reference catalogs.6. Use the reference catalogs within roles.7. If there is an blocklist error, maintain an entry in the allowlist table (HTTP_WHITELIST).

4.3.6 Maintaining Destination Name to SSC Engine on SAP NW AS Java

Use

You can maintain the destination name using the procedure below.

Procedure

SAP S/4HANA

1. Maintain EJB-IPC Parameters for S/4HANA.For more information, see Customizing for Logistics - General Solution Sales Configuration Maintain Destination Name to SSC Engine .


2. Set the name of the RFC destination and save your settings.

4.3.7 Syncing Existing Master Data (RTVs) with EJB-IPC

To sync your master data (RTVs) with EJB-IPC, execute the following report manually:

● In SAP S/4HANA – /SLCE/STRG_MIG

NoteFor the RTVs to sync successfully with EJB-IPC, the user needs the relevant JMS authorization.

For more information about this, refer to 2496808 (Issues after SP update of NW (e.g. missing KB update) due to JMS Provider Service auth. check).

4.3.8 Deployment of User Exits for Pricing and Configuration

For more information about SAP Solution Sales Configuration Runtime variant functions and user exits for pricing and configuration, see SAP Notes 870201 (Implementing variant functions in Java) and 809820(Userexit concept for pricing).

4.3.8.1 Registration of User Exits for Pricing

Every pricing user exit (including standard SAP exits) must be known to the runtime. Each implementation is loaded during runtime and controlled by configuration available through transaction /SAPCND/UEASS. The work is split into two parts: First, the implementation (class) must be registered and a name must be assigned to it. Then, the defined user exit name is assigned to a formula number that can be used in the other configuration parts (for example, pricing procedure).

Registering an Implementation

When you call transaction /SAPCND/UEASS and enter the correct usage (such as PR for Pricing), a screen appears that lists the different exit types that are available for the usage. A short description is provided for each line, which you can access by clicking the information icon.

The details screen for each user exit type shows the scope and the user exit interface. The scope is “number-dependent” (like the requirements), “one unique implementation” (like the document init formulas), or “multiple implementations” (like pricing init). The user exit interface entry describes the adapter class that a user exit must inherit.

The view level for the implementations shows the different available implementations for a user exit. Customer classes must be registered here.






You register a new implementation (cross-client Customizing) by creating a new entry. Enter the following data:

● User exit name that is a symbolic or short description of the functionality. The customer namespace starts with Y or Z.

● Name of the implementing class (for example, your.company.pricing.userexits.SpecialBaseFormula). There is no restriction on the name but it should be different from com.sap*.

● An additional long description

If a user exit depends on attributes that are passed by the calling application, the internal attribute names (used in the implementation) must be entered on the sub screen attributes along with a description.

Assigning Implementations to a Formula

After you have registered a java user exit implementation, the symbolic name of the user exit must be mapped to the “old” formula numbers used, for example, in a pricing procedure or access type.

On the formula screen, the formula number is assigned to a user exit name. The range reserved for customer formula numbers can be viewed in transaction /SAPCND/UERNG and depends on the application and usage (for example, V and PR - Pricing). On the sub screen, all the required internal attributes (those used in the user exit implementation) must be mapped with field names of the communication structure.

After registration and assignment, the user exit formula must be uploaded before it can be assigned to any pricing procedure or other configuration. As the configuration is buffered for one day (default setting), the changes become active only when the VMC or the application server is restarted.

4.3.8.2 Available User Exits and APIs

This section describes all of the available pricing-related user-exit types. Standard features are explained first and then all of the different types of user exits. The parameters that form the interface between pricing and user exits are also briefly described.

4.3.8.2.1 Logging Capabilities

For customer pricing user exits, there is an easy way to include fast logging. The com.sap.spe.base.logging.UserexitLogger class implements two methods for logging debug messages or error messages. Logging is fast and done only if the appropriate log level is reached, which you can define at runtime.

ZSpecialRoundingValueFormula (shorten)

package your.company.pricing.userexits;


import com.sap.spe.base.logging.UserexitLogger; [..] public class ZSpecialRoundingValueFormula extends ValueFormulaAdapter { private static UserexitLogger userexitlogger = new UserexitLogger(ZSpecialRoundingValueFormula.class); public BigDecimal overwriteConditionValue(IPricingItemUserExit item, IPricingConditionUserExit condition) { [..] userexitlogger.writeLogDebug("old cond value: " + val.getValueAsString()); [..] } }

Line No. Description

8 Create a static instance of the UserexitLogger class. As constructor parameter, pass the actual class.

13 Use writeLogDebug(String s) or writeLogError(String s) to log the string s in the log.

4.3.8.2.2 Condition Base Formula

The condition base formula can be used to overturn the automatically calculated base value of a condition. This type of user exit must be assigned in Customizing to the user exits type BAS (condition base formula).

This user exit is called after the condition base value has been calculated for each pricing condition. The user exit class must be inherited from BaseFormulaAdapter and implement method overwriteConditionBase. The overwriteConditionBase method has the parameters pricingItem and pricingCondition, which represents the item and the actual condition.

If this method returns a null object reference, pricing will keep the base value that is called automatically.

ZSpecialBaseFormula

package your.company.pricing.userexits; import java.math.BigDecimal; import com.sap.spe.base.logging.UserexitLogger; import com.sap.spe.conversion.IDimensionalValue; import com.sap.spe.pricing.transactiondata.userexit.IPricingConditionUserExit; import com.sap.spe.pricing.transactiondata.userexit.IPricingItemUserExit; import com.sap.spe.pricing.transactiondata.userexit.BaseFormulaAdapter; public class ZSpecialBaseFormula extends BaseFormulaAdapter { private static UserexitLogger userexitlogger =



new UserexitLogger(ZSpecialBaseFormula.class); public BigDecimal overwriteConditionBase(IPricingItemUserExit pricingItem, IPricingConditionUserExit pricingCondition) { BigDecimal result; userexitlogger.writeLogDebug("old cond base: " + pricingCondition.getConditionBase().getValueAsString()); // double the base value result = pricingCondition.getConditionBase().getValue(). multiply(new BigDecimal("2")); userexitlogger.writeLogDebug("new cond base: " + result); return result; } }


11 Extend/subclass the API BaseFormulaAdapter.

16 Overwrite the implementation of the overwriteConditionBase method.

25 Change the value of the automatically determined condition base.

30 Return the changed condition base value.

4.3.8.2.3 Item Calculation Begin Formula

This seldom-used user exit is available to change the document and item if necessary before item pricing takes place. This type of user exit must be assigned in Customizing to user exit type CAB (Item Calculation Begin Formula).

The user exit class must be inherited from PricingItemCalculateBeginFormulaAdapter. It passes a reference to the pricing document ( prDocument) and the item ( prItem).

ZSpecialCalculationBeginFormula

package your.company.pricing.userexits; import com.sap.spe.pricing.transactiondata.userexit.IPricingDocumentUserExit; import com.sap.spe.pricing.transactiondata.userexit.IPricingItemUserExit; import com.sap.spe.pricing.transactiondata.userexit.PricingItemCalculateBeginFormulaAdapter; public class ZSpecialCalculationBeginFormula extends PricingItemCalculateBeginFormulaAdapter {


{ private int stepNumber, counter; public void calculationBegin(IPricingDocumentUserExit prDocument, IPricingItemUserExit prItem) { stepNumber = 10; counter = 1; prDocument.setZeroPriceActive(true); } }


7 Extend the API PricingItemCalculateBeginFormulaAdapter

12 Overwrite the implementation of the calculationBegin method

18 Set the document to accept zero prices as valid prices

4.3.8.2.4 Item Calculation End Formula

This seldom-used user exit is available to change the document and item if necessary after item pricing has taken place. This type of user exit must be assigned in Customizing to user exit type CAE (Item Calculation End Formula).

The user exit class must be inherited from PricingItemCalculateEndFormulaAdapter. It passes a reference to the pricing document ( prDocument) and the item ( prItem).

ZSpecialCalculationBeginFormula

package your.company.pricing.userexits; import com.sap.spe.pricing.transactiondata.userexit.IPricingDocumentUserExit; import com.sap.spe.pricing.transactiondata.userexit.IPricingItemUserExit; import com.sap.spe.pricing.transactiondata.userexit.PricingItemCalculateEndFormulaAdapter; public class ZSpecialCalculationEndFormula extends PricingItemCalculateEndFormulaAdapter { private int stepNumber, counter; public void calculationEnd(IPricingDocumentUserExit prDocument, IPricingItemUserExit prItem) { stepNumber = 10;



counter = 1; prItem.findPricingCondition(stepNumber, counter).setConditionControl('A'); } }


7 Extend the API PricingItemCalculateEndFormulaAdapter

11 Overwrite the implementation of the calculationEnd method

16 Set the condition control of the pricing condition at stepNumber 10 to Automatic A

4.3.8.2.5 Configuration Formula

This seldom-used user exit is called when the product configuration process creates subitems. This type of user exit must be assigned in Customizing to user exit type CFG (Configuration Formula), which is called for subitems created by SCE.

The user exit class must be inherited from SPCSubItemCreatedByConfigurationFormulaAdapter. For each subitem, method isRelevantForPricing is called and a reference to the new subitem and the configuration instance is passed.

ZSpecialConfigurationFormula

package your.company.pricing.userexits; import com.sap.spc.document.userexit.ISPCItemUserExitAccess; import com.sap.sce.front.base.Instance; import com.sap.spc.document.userexit.SPCSubItemCreatedByConfigurationFormulaAdapter; public class ZSpecialConfigurationFormula extends SPCSubItemCreatedByConfigurationFormulaAdapter { public boolean isRelevantForPricing(ISPCItemUserExitAccess subItem, Instance instance) { return subItem.isRelevantForPricing(); } }



8 Extend the API SPCSubItemCreatedByConfigurationFormulaAdapter

10 Implement the isRelevantForPricing method

13 Set the configuration subitem to pricing-relevant or not

4.3.8.2.6 Condition Init Formula

After a pricing condition has been initialized, it can be changed with this user exit, which is called whenever an internal condition (a transactional object or business entity) is created. This type of user exit must be assigned in Customizing to user exit type CNI (Condition Init Formula).

The user exit class must be inherited from PricingConditionInitFormulaAdapter and must overwrite the method init. It allows the new condition to be changed (parameter prCondition).

ZSpecialConditionInitFormula

package your.company.pricing.userexits; import java.math.BigDecimal; import com.sap.spe.pricing.transactiondata.userexit.IPricingConditionUserExit; import com.sap.spe.pricing.transactiondata.userexit.IPricingDocumentUserExit; import com.sap.spe.pricing.transactiondata.userexit.IPricingItemUserExit; import com.sap.spe.pricing.transactiondata.userexit.PricingConditionInitFormulaAdapter; public class ZSpecialConditionInitFormula extends PricingConditionInitFormulaAdapter { public void init(IPricingDocumentUserExit prDocument, IPricingItemUserExit prItem, IPricingConditionUserExit prCondition) { if (prCondition.getConditionTypeName() != "0PR0" && prCondition.getChangeOfRateAllowed()) prCondition.setConditionRateValue(new BigDecimal("2")); } }


10 Extend the API PricingConditionInitFormulaAdapter

12 Implement the init method




17 Set the condition rate to 2

4.3.8.2.7 Copy Formula

While a document is being copied, the pricing condition can be fixed or other changes can take place if required. This type of user exit must be assigned in Customizing to user exit type CPY (Copy Formula).

This user exit is called during the copying process. The user exit class must be inherited from class PricingCopyFormulaAdapter and implement method pricingCopy. Parameters pricingDocument, pricingItem, and pricingCondition are references to the target document, item, and condition. The pricing type describes what should happen to the pricing result when new pricing takes place. The parameter copyType is a reference to the Customizing used for the copy process; sourceSalesQuantity contains the old quantity of the source item.

ZSpecialCopyFormula

package your.company.pricing.userexits; import com.sap.spe.conversion.IQuantityValue; import com.sap.spe.pricing.customizing.ICopyType; import com.sap.spe.pricing.customizing.IPricingType; import com.sap.spe.pricing.transactiondata.userexit.IPricingConditionUserExit; import com.sap.spe.pricing.transactiondata.userexit.IPricingDocumentUserExit; import com.sap.spe.pricing.transactiondata.userexit.IPricingItemUserExit; import com.sap.spe.pricing.transactiondata.userexit.PricingCopyFormulaAdapter; public class ZSpecialCopyFormula extends PricingCopyFormulaAdapter { public void pricingCopy(IPricingDocumentUserExit pricingDocument, IPricingItemUserExit pricingItem, IPricingConditionUserExit pricingCondition, IPricingType pricingType, ICopyType copyType, IQuantityValue sourceSalesQuantity) { // fix condition value and base pricingCondition.setConditionControl('E'); } }


11 Extend the API PricingCopyFormulaAdapter

13 Overwrite the implementation of the pricingCopy method



19 Fix the conditions value and base by setting the conditionControl to E

4.3.8.2.8 Document Init Formula

After a pricing document has been initialized, it can be changed with this user exit, which is called when a new pricing document is created. This type of user exit must be assigned in Customizing to user exits type DOI (Document Init Formula).

The user exit class must be inherited from class PricingDocumentInitFormulaAdapter and implement method init. A reference to the new document is passed.

ZSpecialDocumentInitFormula

package your.company.pricing.userexits; import com.sap.spe.pricing.transactiondata.userexit.IPricingDocumentUserExit; import com.sap.spe.pricing.transactiondata.userexit.PricingDocumentInitFormulaAdapter; public class ZSpecialDocumentInitFormula extends PricingDocumentInitFormulaAdapter { public void init(IPricingDocumentUserExit prDocument) { if (!prDocument.isAlwaysPerformingGroupConditionProcessing()) prDocument.setAlwaysPerformingGroupConditionProcessing(true); } }


6 Extend the API DocumentInitFormula

8 Overwrite the implementation of the init method

10 Set group condition processing to active

4.3.8.2.9 Group Key Formula

This seldomly used user exit influences group conditions (conditions that are processed together over more than one item). This type of user exit must be assigned in Customizing to user exit type GRP (Group Key Formula).



This user exit is called after the key of a group condition is determined .The user exit class must be inherited from class GroupKeyFormulaAdapter and implement method setGroupKey. The method determines a string from the different passed object reference, which is used for the grouping rule of group conditions. Different string values for two conditions mean that the two will never form one group.

ZSpecialGroupKeyFormula

package your.company.pricing.userexits; import com.sap.spe.pricing.transactiondata.userexit.GroupKeyFormulaAdapter; import com.sap.spe.pricing.transactiondata.userexit.IGroupConditionUserExit; import com.sap.spe.pricing.transactiondata.userexit.IPricingConditionUserExit; import com.sap.spe.pricing.transactiondata.userexit.IPricingDocumentUserExit; import com.sap.spe.pricing.transactiondata.userexit.IPricingItemUserExit; public class ZSpecialGroupKeyFormula extends GroupKeyFormulaAdapter { public String setGroupKey(IPricingDocumentUserExit document, IPricingItemUserExit item, IPricingConditionUserExit condition, IGroupConditionUserExit groupCondition) { return "002"; } }


6 Extend the API GroupKeyFormulaAdapter

11 Overwrite the implementation of the setGroupKey method

13 Set the conditions group key to the group key “002”

4.3.8.2.10 Item Init Formula

After the pricing item has been initialized, it can be changed with this user exit, which is called when a new pricing item is created. This type of user exit must be assigned in Customizing to user exit type ITI (Item Init Formula).

The user exit class must be inherited from class PricingItemInitFormulaAdapter and implement method init. A reference to the document and to the new item is passed.

ZSpecialItemInitFomula

package your.company.pricing.userexits; import com.sap.spe.pricing.transactiondata.userexit.IPricingDocumentUserExit;


import com.sap.spe.pricing.transactiondata.userexit.IPricingItemUserExit; import com.sap.spe.pricing.transactiondata.userexit.PricingItemInitFormulaAdapter; public class ZSpecialItemInitFomula extends PricingItemInitFormulaAdapter { public void init(IPricingDocumentUserExit prDocument, IPricingItemUserExit prItem) { if (prItem.isStatistical()) prItem.setExclusionFlag('$'); } }


7 Extend the API ZSpecialItemInitFomula

9 Overwrite the implementation of the init method

11 Set the item exclusion flag

4.3.8.2.11 Pricing Init

In previous releases, this user exit was called CRMDocumentStandardExit where it was used mainly to pass header attributes to be used in method initializeDocument. As of Release 5.0, these attributes can be customized. Pricing Init user exits can now be used only to set the unit of rounding to the smallest unit of a currency. This type of user exit must be assigned in Customizing to the user exit type PRI (Pricing Init).

This user exit is called when a new pricing document is created. The user exit class must be inherited from class PricingInitFormulaAdapter and must implement method initializeDocument. This method has parameter documentUserExitAccess, which represents the pricing document.

ZPricingInit

package your.company.pricing.userexits; import com.sap.spe.document.userexit.IDocumentUserExitAccess; import com.sap.spe.document.userexit.PricingInitFormulaAdapter; public class ZPricingInit extends PricingInitFormulaAdapter { public void initializeDocument(IDocumentUserExitAccess documentUserExitAccess) { documentUserExitAccess.setUnitToBeRoundedTo(20); } }




6 Extend the API PricingInitFormulaAdapter

8 Overwrite the implementation of the initializeDocument method

10 Set the rounding unit to 20

4.3.8.2.12 Pricing Prepare

In previous releases, this user exit was called CRMItemStandardExit. Pricing Prepare user exits can be used to add header and/or item attributes to be used during the pricing process. These attributes can now be customized. This type of user exit must be assigned in Customizing to the user exit type PRP (Pricing Prepare).

The Pricing Prepare user exit is called when creating a new pricing item and when new pricing takes place. The user exit class must be inherited from class PricingPrepareFormulaAdapter and must implement method addAttributeBindings. This method has parameter itemUserExitAccess, which represents the pricing item.

ZPricingPrepare

package your.company.pricing.userexits; import com.sap.spe.document.userexit.IItemUserExitAccess; import com.sap.spe.document.userexit.PricingPrepareFormulaAdapter; public class ZPricingPrepare extends PricingPrepareFormulaAdapter { public void addAttributeBindings(IItemUserExitAccess itemUserExitAccess) { itemUserExitAccess.addAttributeBinding("ZLAND", "DE"); } }


6 Extend the API PricingPrepareFormulaAdapter

8 Overwrite the implementation of the addAttributeBindings method

10 Set the attribute ZLAND to the value “DE”.


4.3.8.2.13 Requirement

This user exit is used during condition determination at pricing procedure step/counter level and at condition access step level. This type of user exit must be assigned in Customizing to the user exit type REQ (Requirement).

The user exit class must be inherited from RequirementAdapter and implement method checkRequirement. If this method returns false, the actual access is not made.

ZSpecialRequirement

package your.company.pricing.userexits; import com.sap.spe.base.logging.UserexitLogger; import com.sap.spe.condmgnt.customizing.IAccess; import com.sap.spe.condmgnt.customizing.IStep; import com.sap.spe.condmgnt.finding.userexit.IConditionFindingManagerUserExit; import com.sap.spe.condmgnt.finding.userexit.RequirementAdapter; public class ZSpecialRequirement extends RequirementAdapter { private static UserexitLogger userexitlogger = new UserexitLogger(ZSpecialRequirement.class); public boolean checkRequirement(IConditionFindingManagerUserExit item, IStep step, IAccess access) { String zland = item.getAttributeValue("ZLAND"); if (zland == null || zland.equals("")) { userexitlogger.writeLogError("ZLAND attribute missing"); return false; } else { return zland.equals("US"); } } }


9 Extend the API RequirementAdapter

14 Overwrite the implementation of the checkRequirement method

17 Retrieve an attribute value to be used for the check

22 Return the check result: “true” to make the access, “false” not to make the access



4.3.8.2.14 Scale Base Formula

This user exit can be used to replace the automatically determined scale base. This type of user exit must be assigned in Customizing to the user exit type SCL (Scale Base Formula).

This user exit is called after the condition-scale base value has been calculated for a pricing condition. The user exit class must be inherited from class ScaleBaseFormulaAdapter and implement at least overwriteScaleBase. If group condition processing is enabled for the condition type, method overwriteGroupScaleBase can also be implemented. Both methods can return null to indicate that the original value is to be taken.

ZSpecialScaleBaseFormula

package your.company.pricing.userexits; import java.math.BigDecimal; import com.sap.spe.base.logging.UserexitLogger; import com.sap.spe.pricing.transactiondata.userexit.IGroupConditionUserExit; import com.sap.spe.pricing.transactiondata.userexit.IPricingConditionUserExit; import com.sap.spe.pricing.transactiondata.userexit.IPricingDocumentUserExit; import com.sap.spe.pricing.transactiondata.userexit.IPricingItemUserExit; import com.sap.spe.pricing.transactiondata.userexit.ScaleBaseFormulaAdapter; public class ZSpecialScaleBaseFormula extends ScaleBaseFormulaAdapter { private static UserexitLogger userexitlogger = new UserexitLogger(ZSpecialScaleBaseFormula.class); public BigDecimal overwriteScaleBase(IPricingItemUserExit item, IPricingConditionUserExit condition, IGroupConditionUserExit groupCondition) { userexitlogger.writeLogDebug("Old scale: " + groupCondition.getConditionScale().getValueAsString()); if (groupCondition.getConditionScale() != null) { return groupCondition.getConditionScale().getValue().setScale(0, BigDecimal.ROUND_FLOOR); } else { return null; } } public BigDecimal overwriteGroupScaleBase(IPricingDocumentUserExit document, IGroupConditionUserExit groupCondition) { if (groupCondition.getConditionScale() != null) { return groupCondition.getConditionScale().getValue().setScale(0, BigDecimal.ROUND_FLOOR); } else { return null; } }


}


12 Extend the API ScaleBaseFormulaAdapter

17 Overwrite the implementation of the overwriteScaleBase method

25 Return the changed scale base value

34 Overwrite the implementation of the overwriteGroupScaleBase method

38 Return the changed scale base value

4.3.8.2.15 Condition Value Formula

This user exit can be used to replace the automatically determined condition value. This type of user exit must be assigned in Customizing to user exit type VAL (Condition Value Formula).

This user exit is called after the condition value has been calculated for each pricing condition. The user exit class must be inherited from class ValueFormulaAdapter and implement at least overwriteConditionValue. If group condition processing is enabled for the condition type, the implementation of method overwriteGroupConditionValue is possible. Both methods can return null to indicate that the original value is to be taken.

ZSpecialRoundingValueFormula

package your.company.pricing.userexits; import java.math.BigDecimal; import com.sap.spe.base.logging.UserexitLogger; import com.sap.spe.conversion.ICurrencyValue; import com.sap.spe.pricing.transactiondata.userexit.IGroupConditionUserExit; import com.sap.spe.pricing.transactiondata.userexit.IPricingConditionUserExit; import com.sap.spe.pricing.transactiondata.userexit.IPricingDocumentUserExit; import com.sap.spe.pricing.transactiondata.userexit.IPricingItemUserExit; import com.sap.spe.pricing.transactiondata.userexit.ValueFormulaAdapter; public class ZSpecialRoundingValueFormula extends ValueFormulaAdapter { private static UserexitLogger userexitlogger = new UserexitLogger(ZSpecialRoundingValueFormula.class); public BigDecimal overwriteConditionValue(IPricingItemUserExit item, IPricingConditionUserExit condition) { BigDecimal result; ICurrencyValue val = condition.getConditionValue();



userexitlogger.writeLogDebug("old cond value: " + val.getValueAsString()); result = val.getValue().setScale(0, BigDecimal.ROUND_HALF_UP); BigDecimal qnt = item.getProductQuantity().getValue(); qnt = qnt.divide(new BigDecimal("100"), 2, BigDecimal.ROUND_HALF_UP); userexitlogger.writeLogDebug("new cond value: " + result.subtract(qnt)); return result.subtract(qnt); } public BigDecimal overwriteGroupConditionValue( IPricingDocumentUserExit item, IGroupConditionUserExit condition) { // do nothing return null; } }


13 Extend the API ValueFormulaAdapter

18 Overwrite the implementation of the overwriteConditionValue method

33 Change the value of the automatically determined condition value

33 Return the changed condition value

36 Overwrite the implementation of the overwriteGroupConditionValue method

39 Return null to keep the automatically calculated value

4.3.9 Setting Up Interval for Number Range Object

To start the creation of stores, you must define an interval for the number range object /SLCE/STO.

In case an interval is not defined and the user tries to create a store, the folowing message is displayed on the UI:Could not generate store number

4.3.10 Required Entries in the Gateway ACL

Depending on your Kernel Release and security settings, you may need to add the host of the EJB-IPC, the SME, or the data loader to the gateway access control list (ACL) (reginfo).

For more information, see SAP Note 1069911 (GW: Changes to the ACL list of the gateway (reginfo)).



4.3.11 Adjustment of BAdI Implementations

If you have a custom implementation in any of these Business Add-Ins (BAdIs), you need to adjust your implementation in accordance with the implementation delivered by SAP. During the installation procedure, custom implementations of single use BAdIs may be deactivated. We therefore recommend that you review this list.

S/4HANA

Business Add-InSAP Solution Sales Configuration for SAP S/4HANA Implementation Multiple Use

CASL_CU51_DARK /SLCE/EHI_OBO_SAVE No

BADI_COM_CFG_IMPORT2 /SLCE/GENERATE_KB_WATCHDOG Yes

EXTRACT_DATA /SLCE/EXTRACT_DATA No

4.3.12 Maintaining Fiori Launchpad Settings

With the SAP S/4HANA integration, SSC provides tiles and catalogs on the Fiori Launchpad for the Customizing activities. The following catalogs are available and should be assigned to the respective user roles using the transaction PFCG:

Catalog ID Catalog Name Catalog Purpose

/SLCE/TC_SSC_UIC_CONF Solution Sales Configuration Administration

This catalog should be assigned to the admin role only.

/SLCE/TC_SSC_UIC_CONF_MODEL Solution Sales Configuration Model This catalog is specific to modeling and should be assigned to the modeler role.

This catalog must also be assigned to the admin role.

/SLCE/TC_SSC_UIC_CONF_DESIGNER

Solution Sales Configuration Design This catalog must be assigned to the UI Designer role.

This catalog must also be assigned to the admin role.

For more information about the tiles in each catalog, see the SAP Help Portal and refer to the application help.




4.3.13 Setting Up the Inbound IDoc to Communicate with SAP CPI

To setup the inbound IDoc for communicating with SAP Cloud Platform Integration, refer to the topic on SAP Cloud Platform Integration Setup in the SAP SSC for Commerce Cloud documentation on the SAP Help Portal.

For setting up the ABAP backend, in order to complement the CPI setup, follow the steps provided in the SAP Note 2985718 (Solution Sales Configuration: Post process for ABAP backend setup of IDoc).

4.3.14 Update Entries For User Exit Database

Use

With the introduction of the new column VERSION in the database table for the pFunction user exit maintained in the back-end ECC (or CRM) system, it becomes important that the entries for this new column are maintained for the records that existed in the SP02 (or earlier) release.

By following the steps below the entries will be updated as follows tables in backend environment as:

Database Table Environment

/SLCE/USER_EXIT ECC

/SLCC/USER_EXIT CRM

Prerequisites

Proceed to follow the tasks below if you have recently upgraded to the service pack SP03 (or higher than SP03) of the component SLCE 630 (or SLCC 730).

Steps

1. If you have upgraded to - SP03 of the component SLCE 630 (or SLCC 730), then please download and implement the solution note 3027526 . If you have upgraded to an SP higher than SP03 of the component SLCE 630 (or SLCC 730), then proceed to next steps

2. If you are on a CRM installation:1. Execute the transaction code SE38.2. Execute the report /SLCC/CORRECT_USER_EXIT_RECS.


https://help.sap.com/viewer/288c62ae365b453eae46105fee01d106/1905%20CCV2/en-US/42ce1250912f48f69cdb29b66a0c8517.html

https://help.sap.com/viewer/288c62ae365b453eae46105fee01d106/1905%20CCV2/en-US/42ce1250912f48f69cdb29b66a0c8517.html

https://help.sap.com/viewer/product/SAP_SOL_SALES_CONFIG_OD/1905%2520CCV2/en-US



3. Provide the default version and click Execute.All the empty records for the field VERSION in the database table /SLCC/USER_EXIT will be updated by this default version now and all the timestamps stored in the field LAST_UPDATEON with incorrect formats will be converted to the current timestamp in correct format.

3. If you are on an ECC installation:1. Execute the transaction code SE38.2. Execute the report /SLCE/CORRECT_USER_EXIT_RECS.3. Provide the default version and click Execute.

All the empty records for the field VERSION in the database table /SLCE/USER_EXIT will be updated by this default ersion now and all the timestamps stored in the field LAST_UPDATEON with incorrect formats will be converted to the current timestamp in correct format.

NoteYou only to need execute this report once to correct your entries.

4.4 Using SAP Solution Sales Configuration for SAP S/4HANA with Vehicle Management

You can use SAP Solution Sales Configuration for SAP S/4HANA with Vehicle Management using the transaction VELO.

You must follow this process for this integration:

1. Do not set the user parameter VELO_CU50_ACTIVE.2. To use pricing or transfer data from VELO to SSC, to influence the configuration (reference characteristics),

you must implement the BAdI VLC_SCE_PARAMETERS.3. With the user parameter VELO_SCE_FULLSCREEN, you can control if the SSC UI is shown in full-screen

mode or simply as part of the action screen.4. Create a new RFC destination using the following information:

1. RFC Name: IPC_CONFIGURATION_UI2. Connection Type: G (HTTP Connection to External Server)3. Description 1: Web AS Java (VM08) for SSC Configuration UI4. Description 2: This destination is required for VMS as it is still using the hard-coded

Host, Port, Path Prefix: Same as RFC destination for SSC engine



5 Upgrading SAP Solution Sales Configuration for SAP S/4HANA

This section tells you how to upgrade to a newer release of SAP Solution Sales Configuration for SAP S/4HANA.

5.1 Pre-Upgrade Tasks

This section describes tasks that must be completed before you upgrade SAP Solution Sales Configuration for SAP S/4HANA.

5.2 Overall Upgrade Sequence

This section provides an overview of the overall sequence of steps necessary when upgrading SAP Solution Sales Configuration for SAP S/4HANA.

The following table contains all available software units. However, to run a specific scenario, you only need a subset of available software units. Some are only required for special processes. For information about which software is required to run a specific scenario, see <reference to software component matrix or scenario-specific sections>.

For the latest component version and patch level requirements, see <reference to SAP Note, Support Package Stack Guide, or quick link /sp-stacks on SAP Support Portal>.

Step Task More Information

1 <for example, upgrade of software unit>

<Link to task topic> or reference to other required documents, such as SAP Notes or guides>

2

SAP Solution Sales Configuration for SAP S/4HANA: Administration GuideUpgrading SAP Solution Sales Configuration for SAP S/4HANA CONFIDENTIAL 77

5.3 Post-Upgrade Tasks

This section describes tasks that should be completed after you have finished the upgrade of SAP Solution Sales Configuration for SAP S/4HANA.

5.3.1 Migrating IPC Switch for Materials

The IPC Integration and the SSC Integration (SLCE 800) use entries in table CUCFGSW to define materials to be used either with the IPC or SAP Solution Sales Configuration for SAP S/4HANA. The current release for SAP Solution Sales Configuration for SAP S/4HANA has its own set of tables to define this relation.

You can use either the report /SLCE/REP_MIGRATE_SSC_CONFIG or transaction /SLCE/IPC_MIGR to migrate content of the table CUCFGSW to the new set of tables. This will delete the migrated content of CUCFGSW as it is not relevant for SAP S/4HANA.


Upgrading SAP Solution Sales Configuration for SAP S/4HANA

6 Configuring SAP Solution Sales Configuration for SAP S/4HANA

This section describes how to configure SAP Solution Sales Configuration for SAP S/4HANA.

6.1 Business Scenarios of SAP Solution Sales Configuration for SAP S/4HANA

SAP Solution Sales Configuration for SAP S/4HANA supports the sale of configurable products and solutions in the following sales scenarios:

● Solution Configuration in SAP S/4HANA● Solution Configuration in Non-SAP Sales Application● Solution Configuration in SAP Hybris

6.1.1 Solution Configuration in SAP S/4HANA

You use this business scenario to monitor the SAP Solution Sales Configuration for SAP S/4HANA business processes in the SAP S/4HANA system.

This business scenario comprises the following business processes:

1. Modeling the SAP Solution Sales Configuration for SAP S/4HANA2. Configure-to-Order in S/4HANA Quotation and Order Management

Technical System Landscape

For details, see System Landscape for SAP Solution Sales Configuration for SAP S/4HANA.

Software Units

For details, see Software Component Matrix.

SAP Solution Sales Configuration for SAP S/4HANA: Administration GuideConfiguring SAP Solution Sales Configuration for SAP S/4HANA CONFIDENTIAL 79

Implementation Sequence

For details, see Overall Implementation Sequence.

Related Information

System Landscape for SAP Solution Sales Configuration for SAP S/4HANA [page 13]Overall Implementation Sequence [page 14]

6.1.2 Solution Configuration in Non-SAP Sales Application

You use this business scenario to monitor the SAP Solution Sales Configuration for SAP S/4HANA business processes in a non-SAP sales application.

This business scenario comprises the following business processes:

1. Modeling the Solution Configuration2. Configure-to-Order in Non-SAP Sales Application


For details, see .

Software Units

For details, see .

Implementation Sequence

For details, see Overall Implementation Sequence [page 14].


Configuring SAP Solution Sales Configuration for SAP S/4HANA

More Information

For more information about solution configuration in a non-SAP sales application, see the business scenarios description on the SAP Help Portal and navigate to SAP Solution Sales Configuration for SAP S/4HANA Relevant version Configuration SAP SSC: Business Scenarios Description .

6.1.3 Solution Configuration in SAP Hybris

SAP Solution Sales Configuration for SAP S/4HANA offers a powerful sales configuration solution that enables sales teams, customers, and channel partners to configure, price, and order products accurately and efficiently. Leveraging the SAP Hybris platform, sales and marketing departments can manage the content for rich and proper display of options and values, with highly flexible UI customization and extensions.


The system landscape for Hybris can vary depending on the entire sales scenario that is implemented. The following diagram illustrates the minimal landscape required for the sales solution configuration in Hybris.

Landscape Required for Sales Using SAP Hybris



An SAP S/4HANA system is connected to SAP Hybris. The Solution Modeling Environment is installed on the personal computers of the modelers and the build manager. Modelers can use an extract of material master data including LO-VC product models from SAP S/4HANA as part of the solution model they build. We recommend that you use a source control system, like Git, (not part of SAP Solution Sales Configuration or Hybris) on a centralized server where developers can check-out and check-in their solution models. A build management tool like Jenkins can access the source control system on that server to build the run time knowledge base from the models, and then export them into the S/4HANA test systems.

Installation

SAP Solution Sales Configuration for SAP S/4HANA provides an extension for each SAP Hybris version. A separate installation guide for this extension on each SAP Hybris version can be found on the product page for SAP Solution Sales Configuration for SAP S/4HANA on the SAP Help Portal.

6.2 Solution-Wide Topics

6.2.1 Customizing

The entry point into the Customizing for SAP Solution Sales Configuration is at Logistics - General Solution Sales Configuration (transaction SPRO).

6.3 Configuring SAP Solution Sales Configuration, UI Composer Add-on

6.3.1 UI Composer

The SAP UI Composer for SAP Solution Sales Configuration for SAP S/4HANA provides UI designers with a WYSIWYG editor to compose the user interfaces of the product configurator.

The solution contains the following main software component versions (add-ons):

● SLCUISoftware component version SLCUI 100 is installed on the SAP Gateway and represents the main part of the UI Composer. It includes BSP applications for UI5. OData services are created and implemented in S/4HANA or CRM system.

● SLCESoftware component version SLCE 800 is installed on the SAP S/4HANA system. It includes the APIs which provide services to interact with knowledge base information, the definition of the UI Composer database tables, OData service implementation for UI composer, SSC configuration sessions, and sales transaction operations.




6.3.2 Solution Overview

6.3.2.1 SAP SSC UI Composer - Runtime UI

The UIC runtime UI is built as SAP UI5 application and its screens are generated dynamically based on the store definitions composed in the UI Composer. In case no store is composed, a dynamic UI is launched, which is similar to the configuration launched in the JSPUI. This is further integrated in quotations, sales orders, purchase orders, the Vehicle Management System (VMS), and purchase requisitions.

Users may choose the default JSPUI or UIC runtime UI based on Customizing.

The following figure depicts the high level architecture diagram of the UIC runtime UI.


Product Configurator - High Level Architecture



6.3.2.2 SAP SSC UI Composer - Design Time UI

Use

One of the main goals of the solution is to harmonize and standardize the user interfaces of the product configurator across product families. In order to achieve this goal, the store definitions are created using store templates and libraries of predefined pages. The store definition data is saved in SAP back-end database tables (SAP Gateway UI Composer). The knowledge bases of the solution models created in the solution modeling environment are designed to promote reusability and provide the maximum benefit of store templates and predefined pages.

The OData services are designed to leverage the available SAP S/4HANA APIs and the SAP Solution Sales Configuration APIs.

The UI Composer requires two user roles: the UI administrator and UI designer. UI5 developers have the same role object as the UI administrator. These roles are defined in the SAP Gateway UI Composer system using the standard transactions for the UME (User Management Engine).

High-Level Architecture

The UI Composer is integrated with the SAP S/4HANA system as depicted in the figure below. Here, the software components of the solution are represented in green and the required software releases in blue.


UI Composer - High Level Architecture



6.3.3 Business Scenarios

Composing Store Definitions

For more information about this scenario, refer to UI Composer.

Configuring Products

For more information about this scenario, refer to SAP SSC UI Composer - Runtime UI.

Extending the UI Composer

PurposeThe purpose of the UI Composer extension mechanism is to provide developers with a means to add the following elements to the UI Composer:

● Custom Components● Custom Templates● Custom Widgets● Custom metadata files● Custom CSS

Related Information

SAP SSC UI Composer - Runtime UI [page 83]

6.3.4 Operations Information

Error Logs

To display the application log, open transaction SLG1 in the backend system. Use the objects /SLCE/ and the sub-objects /SLCE/UICOMP, /SLCE/PRD_CONFIG and /SLCE/UIRUNTIME.


7 Security Information for SAP Solution Sales Configuration for SAP S/4HANA

This section deals with security topics relevant for SAP Solution Sales Configuration for SAP S/4HANA.

When you create systems that store and retrieve data, it is important to protect the data from unauthorized use, disclosure, modification, or destruction. Ensuring that users have proper authority to view, load, or update existing data is an important aspect of application development. Do all users need the same level of access to the data and to the functions provided by your applications? Are there subsets of users that need access to privileged functions? Are some documents restricted to certain classes of users? The answers to questions like these help provide the basis for the security requirements for your application.

The NW application server includes a powerful and flexible role-based security model to protect your data per your application security requirements. There is always a trade-off between security and usability. A system with no security may be vulnerable to malicious or unauthorized access. A system too tightly secured, may become too complex for end users. The following sections will introduce the NW application server security model.

For more information about using the functions and features provided by SAP Solution Sales Configuration for SAP S/4HANA, see the SAP Help Portal.

7.1 Other Required Documents for Security

This section provides an overview of other security-related documents.

SAP Solution Sales Configuration for SAP S/4HANA is based on SAP S/4HANA, SAP NetWeaver. This means that the corresponding security guides also apply.

Resource Where to Find ItMost Relevant Sections or Specific Restrictions

SAP NetWeaver Security Guide Refer to the SAP Help Portal. Navigate

to SAP Netweaver Platform SAP

Netweaver 7.5 Security SAP Netweaver Security Guide.

This guide does not replace the administration or operation guides that are available for productive operations.

SAP S/4HANA Security Guide Refer to the SAP Help Portal. Navigate

to Product Documentation

Security Guide .

This document is not included as part of the Installation Guides, Configuration Guides, Technical Operation Manuals, or Migration Guides. Such guides are only relevant for a certain phase of the software life cycle, whereas the Security Guides provide information that is relevant for all life cycle phases.


Security Information for SAP Solution Sales Configuration for SAP S/4HANA

https://help.sap.com/

https://help.sap.com/viewer/product/SAP_NETWEAVER/ALL/en-US

https://help.sap.com/viewer/product/SAP_S4HANA_ON-PREMISE/1809.001/en-US

7.2 User Management

This section provides an overview of how you manage and authenticate users in SAP Solution Sales Configuration for SAP S/4HANA.

SAP Solution Sales Configuration for SAP S/4HANA uses the user management and authentication mechanisms provided for underlying standard products, such as SAP S/4HANA and SAP NetWeaver. The security recommendations and guidelines for user administration and authentication as described in the security guides for the underlying products also apply to SAP Solution Sales Configuration for SAP S/4HANA.

The user management of SAP Solution Sales Configuration for SAP S/4HANA is discussed in Post-Installation Tasks.

Related Information

Post-Installation Tasks [page 47]Other Required Documents for Security [page 88]

7.3 Role and Authorization Concept

This section describes the roles and authorizations available in SAP Solution Sales Configuration for SAP S/4HANA.

SAP Solution Sales Configuration for SAP S/4HANA uses the authorization concept provided by the SAP NetWeaver AS ABAP or AS Java. Therefore, the recommendations and guidelines for authorizations as described in the SAP NetWeaver AS Security Guide ABAP <and/or> SAP NetWeaver AS Security Guide Java also apply to SAP Solution Sales Configuration for SAP S/4HANA.

The SAP NetWeaver authorization concept is based on assigning authorizations to users based on roles. For role maintenance, use the profile generator (transaction PFCG) on the AS ABAP and the User Management Engine’s user administration console on the AS Java.

NoteFor more information about how to create roles, see the role administration information in the SAP NetWeaver Security Guide.

SAP Solution Sales Configuration for SAP S/4HANA: Administration GuideSecurity Information for SAP Solution Sales Configuration for SAP S/4HANA CONFIDENTIAL 89

https://help.sap.com/viewer/621bb4e3951b4a8ca633ca7ed1c0aba2/7.5.16/en-US

https://help.sap.com/viewer/621bb4e3951b4a8ca633ca7ed1c0aba2/7.5.16/en-US

7.4 Network and Communication Security

This section provides an overview of the network topology and communication protocols used by SAP Solution Sales Configuration for SAP S/4HANA.

The network topology for SAP Solution Sales Configuration for SAP S/4HANA is based on the topology used by the SAP NetWeaver platform / SAP HANA. The security guidelines and recommendations described in the security guide for SAP NetWeaver / SAP HANA also apply for SAP Solution Sales Configuration for SAP S/4HANA.

7.4.1 Communication Destinations

This section shows an overview of the communication destinations used by SAP Solution Sales Configuration for SAP S/4HANA.

Destination Delivered Type User, Authorizations Description

SPACE No RFC System user with authorization role LO-SLC

This destination is used by the configura-tion engine on SAP NW Java to read customizing and master data from the S/4HANA backend. It is also referred by the Java Resource Adapter to contact the SAP Gateway and to register at the Gateway.



Destination Delivered Type User, Authorizations Description

<free name> No RFC Dialog user with authorization role LO-SLC

This destination is used by the S/4HANA backend to communicate with the Solution Configuration Engine. The ABAP add-on coding in software component SLCE uses the name of this destination for RFC calls. The Solution Configuration Engine uses the program ID of this destination to register at the SAP Gateway and receive calls from the S/4HANA backend.

7.4.1.1 Securing Communication from ABAP to EJB

The SAP J2EE engine supports the use of transport layer security for network communications. Depending on the protocol used for the connection, it supports SSL or Secure Network Communications (SNC).

SAP Solution Sales Configuration uses the destination services API to secure the communication between ABAP and EJB.

For more information about this, refer to the SAP Help Portal and navigate to SAP NetWeaver 7.0 EHP3Network and Transport Layer Security Transport Layer Security on the SAP J2EE Engine Destination Service .

7.4.1.1.1 Creating an RFC Destination in an ABAP System

This is the procedure for creating an RFC destination on a SAP S/4HANA system.

Prerequisites

You have created an RFC destination in the J2EE engine before creating it in the BW system.


https://help.sap.com/

Context

Maintaining an RFC destination, using display and maintenance of RFC destinations (transaction SM59), is necessary for integration between the ABAP and EJB systems.

This setting is required for all integration scenarios.

2. Choose Create.

3. Maintain the RFC destination

Procedure

1. Start the display and maintenance of RFC destinations (T-Code SM59) transaction

2. Choose Create3. Maintain the following information in the RFC destination:

○ RFC destination: <RFC_DESTINATION>○ Connection type: T for TCP/IP connection○ Description: <Description>○ Technical settings:

○ Activation type: Registered server program○ Program ID: <PORTAL_HOSTNAME>_PORTAL_<SID>○ Gateway host: <GATEWAY_HOST>○ Gateway service: sapgw<SYSTEM_NUMBER>

○ Logon/security (Optional): Do Not Send Logon Ticket can serve the purpose as wellSend SAP logon ticket: Activate

4. Save your entries.

Related Information

Settings for the RFC Destination [page 94]



7.4.1.1.2 Creating an RFC Destination in the J2EE Engine

Context

The RFC destination in the J2EE engine is an RFC server that is called by the BW system as an RFC client. The connection is necessary to display portal content in SAP BW. The RFC destination is then used when creating the RFC Destination for SAP EP.

You can use this procedure to create an RFC destination in the J2EE engine:

Procedure

1. Start the SAP J2EE engine administrator using <PORTAL_DIRECTORY>\nwa

2. Search for Destinations by navigating to Configuration Infrastructure Destinations .3. Maintain the following details for the RFC destination:

○ Hosting System: <LOCAL_JAVA_SYSTEM_HOSTING_W73>○ Destination Name: SPACE○ Destination Type: RFC○ Load Balancing: No○ Target Host: <BW> system○ System Number: <SYSTEM_NUMBER>○ Client: <BW_CLIENT>○ Language: EN○ User: <USER> (user in the BW system)○ Password: <PASSWORD>○ Gateway host: <GATEWAY_HOST>

For more information about this, see Creating an RFC Destination for SAP EP 6.0 in the Gateway Options section.

○ Gateway service: sapgw<SYSTEM_NUMBER>

4. Save the connection.5. Ping the destination to validate the connection details configured above.


7.4.1.1.3 Settings for the RFC Destination

The following sections define the parameters to be filled in while creating an RFC destination:

Name of RFC Destination

The name of the RFC destination for an enterprise portal is stored in the Information Broadcasting settings. This is important as it helps in identifying the connected Enterprise Portal for integration with Knowledge Management.

NoteThe broadcast settings can be transported between BW systems. For this reason, the name of the RFC destination should be identical in the source and target systems.

The name recommended by SAP for the RFC destination, to the connected portal, is SAP_EP.

Connection Type

Select connection type T for a TCP/IP connection.

Description of RFC Destination

You can maintain a description of the RFC destination in multiple languages. The language-dependent description is used when publishing iViews from the BEx Web Application Designer and BEx Query Designer, if multiple portals are connected to the BW system.

Activation Type

Select Registered Server Program as the activation type.

Registered Server Program

The server program is set up under the program ID on the J2EE engine. The recommended naming convention is <PORTAL_HOSTNAME>_PORTAL.

For more information about this, you can refer to Creating an RFC Destination in the J2EE Engine.



Gateway Options

Here, you can enter the details for the gateway host and the gateway service that the J2EE engine uses to communicate with the BW system. The gateway host, an application server for the BW system, and the gateway service comprise of the sapgw<SYSTEM_NUMBER>. You can determine the parameters for the gateway using the Gateway Monitor transaction (transaction code SMGW) and navigating to Goto ParameterDisplay .

Send SAP Logon Ticket

This option is available in SAP BW 3.5 SP 11 with SAP NetWeaver 04 SP Stack 11. This helps you avoid the use of the portal user BW_SERVICE. For more information about this, see Structure Link Information Broadcasting as Background Processing.

Check

If the RFC destination is also set up on the page for the J2EE engine, you can check the connection by clicking on the Connection button.

For more information about this, see Creating RFC Destinations in the J2EE Engine.

Related Information

Creating an RFC Destination in the J2EE Engine [page 93]

7.4.1.2 Enabling Secure HTTPS Communication between HMTL Browser and UI Application

Context

The JSP UI allows you to switch to a secure connection before you log in to the application. This is controlled through the SSLEnabled parameter in the application specific section of the Extended Configuration Management (XCM). This setting causes a redirection to HTTPS when the login function is called with http.


Procedure

1. Start XCM from the URL https://<host>:<port>/slcipc/admin/xcm/init.do.

2. Navigate to Start XCM Settings .3. Switch to the Edit mode.

4. For SAP Solution Sales Configuration for SAP S/4HANA, navigate to General Application SettingsCustomer slcipc slcipconfig and toggle to SSLEnabled in Component Configuration details to enable/disable HTTPS.

5. Save your changes.6. Toggle back to display mode.7. Restart the cdev~fbs~slc~ipc application in NWA to apply the changes.

7.4.2 Implementing Logon/Assertion Ticket for JSP UI

SAP logon tickets represent user credentials in SAP systems. When enabled, users can access multiple SAP applications and services through SAPGUI and web browsers, without needing to enter logon credentials repeatedly. These can further be used to enable SSO to authenticate access to 3rd party applications, such as Microsoft-based web applications, etc.

Prerequisites

The following need to be setup before implementation of the logon/assertion ticket for JSP UI:

● SSL protocol● HTTPS protocol● SSO on SAP S/4HANA systems

Related Information

Setting up SSL Protocol [page 97]Setting up HTTPS Protocol [page 97]SSO Setup on SAP S/4HANA Systems [page 98]



7.4.2.1 Setting up SSL Protocol

To enable the use of the https protocol for communication between the web browser and the UI application running on the SAP Netweaver Application Server Java (AS Java), the AS Java Server needs to be prepared for SSL communication and SSL needs to be enabled through XCM settings.

The use of https and SSL is the default configuration for NW 7.50 and onwards.

Enabling SSL Protocol

7.4.2.2 Setting up HTTPS Protocol

The system has a customizing setting that indicate the URL for the JSP UI. This setting uses the HTTPS protocol that can be specified using the transaction SM30 in the table COMM_IPC_URL.

Enabling HTTPS Protocol


7.4.2.3 SSO Setup on SAP S/4HANA Systems

Context

NoteYou can execute the configuration process discussed below only if you have the required authorizations. That is, you would need either the specific administrator roles and privileges in that ABAP system as well as the NW Java Application Server.

The following procedure is an example on how to setup the SSO protocol for a SAP S/4HANA system.

Procedure

1. Execute T-Code RZ10 to update parameters for login/accept_sso2_ticket and login/create_sso2_ticket.

Login Parameters

2. Select the instance profile



Selecting Instance Profile

3. Select Extended Maintenance and click on Change

Updating Profiles

4. If the parameters are unavailable, click on Parameter to create one


Creating a Parameter

5. Enter the parameter details and click on Copy

The parameter details can be entered as below:○ Name: login/accept_sso2_ticket○ Val: 1



Updating Parameter Details

6. Enter the parameter details and click on Copy

The parameter details can be entered as below:○ Name: login/create_sso2_ticket○ Val: 2


Updating Parameter Details

7. Confirm the parameter values

Confirming Parameter Values

8. Save the profile



Saving the Profile

9. Maintain the following (additional) parameters:○ icm/host_name_full = <fully qualified domain name> (SAPFQDN)○ SAPFQDN = <domain name> (Set this parameter in the default profile)

10. Restart the system to apply all changes


Restarting the System

11. In the NWAS Java portal, go to http://<server>:<port>/sso2

Click on Add Trusted System



Selecting Trusted System

12. Select ABAP as System Type and enter system details on the next screen

Accepting Trusted System

13. It is recommended that you use SNC Protection of the communication between the NetWeaver Application Server Java but it can be disabled as above.


NetWeaver Application in Java Server

Click Finish.

The system is now visible as a trusted system.14. Go to the NWAS Java portal from http://<server>:<port>/nwa and follow the procedure:

a. Navigate to Configuration - Authentication and Single Sign-Onb. Select Authentication - Components and select the Policy Configuration Name ticketc. Under the authentication stack, select the EvaluateTicketLoginModule template

The system will be automatically populated.d. Click on Edit

Select the module CreateTicketLoginModule and set the flag value as SUFFICIENTe. For the CreateTicketLoginModule module, add the following properties under the Options:

Property Value

Trusteddn1 CN=<SID>

Trustedss1 CN=<SID>

Trustedsys1 <SID>,<Client>



Property Value

Ume.configuration.active true

NWA in AS Java

f. Save your changes

15. Go to the NWAS from http://<server>:<port>/nwa and follow the procedure:a. Go to Configuration - Certificate and Keysb. Select TicketKeystore for the key storage viewsc. Confirm the availability of your ABAP systemd. Delete SAPLogonTicketKeypair and SAPLogonTicketKeypair-cert under the Details of the

TicketKeystore viewe. Click on Create Entry and enter the following details:

○ Entry name: SAPLogonTicketKeypair○ Algorithm: DSA○ Key length: 1024○ Select the Store Certificate option and click on Next

Enter the following details:○ SateOrProvinceName○ OrganizationName○ localityName


○ organizationalUnitName○ commonName = <SID>

○ Click on Finish and the entries for SAPLogonTicketKeypair and SAPLogonTicketKeypair-cert shall populate automatically

16. Download the AS Java certificate and upload it onto the AS ABAP system using the following procedure:a. Go to NWA from http://<server>:<port>/nwab. Go to Configuration- Certificates and Keysc. Select TicketKeystore to view key storaged. Export SAPLogonTicketKeypair-cert certificatee. Select Export Format as Base64X.509

Uploading Java Certificate to ABAP Systemf. Import this portal certificate in the AS ABAP system using the T-code strustsso2g. Add this portal certificate to Add to Certificate list and Add to ACL

While adding the certificate to the ACL list, Enter SID of the AS Java system and client as 000h. Restart the AS Java system

17. Under SM59 ABAP transaction to make TCP & HTTP connection secure, select the options discussed below for the respective connections



Securing TCP Connection

Securing HTTP Connection


18. You can verify this procedure either by accessing the security logs in which the NWA updates the process status or by launching a configuration for validation in the NWA JAVA application server logs for a secure handshake

7.5 Data Protection and Privacy

This section provides information about how SAP Solution Sales Configuration for SAP S/4HANA complies with data protection requirements.

7.5.1 Introduction

Data protection is associated with numerous legal requirements and privacy concerns. In addition to compliance with general data protection and privacy acts, it is necessary to consider compliance with industry-specific legislation in different countries. SAP provides specific features and functions to support compliance with regard to relevant legal requirements, including data protection. SAP does not give any advice on whether these features and functions are the best method to support company, industry, regional, or country-specific requirements. Furthermore, this information should not be taken as advice or a recommendation regarding additional features that would be required in specific IT environments. Decisions related to data protection must be made on a case-by-case basis, taking into consideration the given system landscape and the applicable legal requirements.

NoteSAP does not provide legal advice in any form. SAP software supports data protection compliance by providing security features and specific data protection-relevant functions, such as simplified blocking and deletion of personal data. In many cases, compliance with applicable data protection and privacy laws will not be covered by a product feature. Definitions and other terms used in this document are not taken from a particular legal source.

CautionThe extent to which data protection is supported by technical means depends on secure system operation. Network security, security note implementation, adequate logging of system changes, and appropriate usage of the system are the basic technical requirements for compliance with data privacy legislation and other legislation.

Generic Fields

You need to make sure that no personal data enters the system in an uncontrolled or non-purpose related way, for example, in free-text fields, through APIs, or customer extensions. Note that these are not subject to the read access logging (RAL) example configuration.



7.5.2 Glossary

The following terms are general to SAP products. Not all terms may be relevant for this SAP product.

Term Definition

Blocking A method of restricting access to data for which the primary business purpose has ended.

Business Purpose The legal, contractual, or in other form justified reason for the processing of personal data to complete an end-to-end business process. The personal data used to complete the process is predefined in a purpose, which is defined by the data controller. The process must be defined before the personal data required to fulfill the purpose can be determined.

Consent The action of the data subject confirming that the usage of his or her personal data shall be allowed for a given purpose. A consent functionality allows the storage of a consent record in relation to a specific purpose and shows if a data subject has granted, withdrawn, or denied consent.

Data Subject Any information relating to an identified or identifiable natural person ("data subject"). An identifiable natural person is one who can be identified, directly or indirectly, in particular by reference to an identifier such as a name, an identification number, location data, an online identifier, or to one or more factors specific to the physical, physiological, genetic, mental, economic, cultural, or social identity of that natural person.

Deletion Deletion of personal data so that the data is no longer available.

End of business Defines the end of active business and the start of residence time and retention period.

End of Purpose (EoP) The point in time when the processing of a set of personal data is no longer required for the primary business purpose, for example, when a contract is fulfilled. After the EoP has been reached, the data is blocked and can only be accessed by users with special authorizations (for example, tax auditors).

End of Purpose (EoP) check A method of identifying the point in time for a data set when the processing of personal data is no longer required for the primary business purpose. After the EoP has been reached, the data is blocked and can only be accessed by users with special authorization, for example, tax auditors.


Term Definition

Personal Data Any information relating to an identified or identifiable natural person ("data subject"). An identifiable natural person is one who can be identified, directly or indirectly, in particular by reference to an identifier such as a name, an identification number, location data, an online identifier, or to one or more factors specific to the physical, physiological, genetic, mental, economic, cultural, or social identity of that natural person.

Purpose The information that specifies the reason and the goal for the processing of a specific set of personal data. As a rule, the purpose references the relevant legal basis for the processing of personal data.

Residence Period The period of time between the end of business and the end of purpose (EoP) for a data set during which the data remains in the database and can be used in case of subsequent processes related to the original purpose. At the end of the longest configured residence period, the data is blocked or deleted. The residence period is part of the overall retention period.

Retention Period The period of time between the end of the last business activity involving a specific object (for example, a business partner) and the deletion of the corresponding data, subject to applicable laws. The retention period is a combination of the residence period and the blocking period.

Sensitive Personal Data A category of personal data that usually includes the following type of information:

● Special categories of personal data, such as data revealing racial or ethnic origin, political opinions, religious or philosophical beliefs, trade union membership, genetic data, biometric data, data concerning health or sex life or sexual orientation.

● Personal data subject to professional secrecy● Personal data relating to criminal or administrative of

fenses● Personal data concerning insurances and bank or credit

card accounts



Term Definition

Technical and Organizational Measures (TOM) Some basic requirements that support data protection and privacy are often referred to as technical and organizational measures (TOM). The following topics are related to data protection and privacy and require appropriate TOMs, for example:

● Access control Authentication features● Authorizations Authorization concept● Read access logging● Transmission control/communication security● Input control/change logging● Availability control● Separation by purpose Subject to the organizational

model implemented and must be applied as part of the authorization concept.

7.5.3 User Consent

Any personal data collected or processed must be linked to a specific, pre-defined purpose, such as the fulfilment of a contract or legal obligation. If there is no other legal basis for the lawful processing of personal data or - in some cases - if the data is to be sent to a third party, you must obtain consent from the data subject to use their personal data. SAP applications ask for consent of the data subject before collecting any personal data. In some cases, the data subject may also be the user. This SAP product provides functionality that allows data subjects to give and withdraw consent to collect and process their personal data. SAP assumes that the user, for example, an SAP customer collecting data, has consent from its data subject (a natural person such as a customer, contact, or account) to collect or transfer data to the solution.

Storage of Personal Data

SAP Solution Sales ConfigurationSAP Solution Sales Configuration for SAP S/4HANA saves only user names in its knowledge base tables and the terms and conditions for creating user accounts are covered under the respective employment contracts.

SAP Solution Sales Configuration for SAP S/4HANA processes the following data:

1. Configuration and pricing master data in the form of knowledge bases, pricing customizing, and pricing conditions

2. Configuration transaction data representing the configuration result in an XML document

When a knowledge base is created or changed via the SME and exported to an SAP S/4HANA system, the user name of the user is stored in the CREATED_BY or CHANGED_BY field of the table COMM_CFGKB.

This personal data can be retrieved, changed to a different user or deleted. For more information about this, please refer to Customer Experience Help Portal.


https://help.hybris.com/6.3.0/hcd/8c39af1286691014b2daed4f092998ca.html

SAP Solution Sales Configuration for SAP S/4HANA is not intended for storage of other personal data. In case you model personal data into the configuration model, you are responsible for the handling of those personal data in the configuration model and the configuration result.

SAP Configure, Price, and Quote for Solution Sales Configuration, UI Composer Add-on

Additionally, the UI Composer processes the following user data:

● Configuration data (in the form of knowledge bases).● Creating workspaces and storing information based on the connected user.

When a workspace or store is created, the user name is saved in the respective database tables, /slce/workspaces and /slce/store_def. This personal data can be retrieved, changed (for a different user), or deleted

7.5.4 Information Retrieval

Data subjects have the right to receive information regarding their personal data that is being processed. The information retrieval feature supports you in complying with the relevant legal requirements for data protection by allowing you to search for and retrieve all personal data for a specified data subject. The search results are displayed in a comprehensive and structured list containing all personal data of the data subject specified, organized according to the purpose for which the data was collected and processed.

The transaction /slce/dpp_support provides details of knowledge bases, stores, and workspaces created by a specific user.

7.5.5 Deletion of Personal Data

Simplified Blocking and Deletion

When considering compliance with data protection regulations, it is also necessary to consider compliance with industry-specific legislation in different countries. A typical potential scenario in certain countries is that personal data shall be deleted after the specified, explicit, and legitimate purpose for the processing of personal data has ended, but only as long as no other retention periods are defined in legislation, for example, retention periods for financial documents. Legal requirements in certain scenarios or countries also often require blocking of data in cases where the specified, explicit, and legitimate purposes for the processing of this data have ended, however, the data still has to be retained in the database due to other legally mandated retention periods. In some scenarios, personal data also includes referenced data. Therefore, the challenge for deletion and blocking is first to handle referenced data and finally other data, such as business partner data.



Deletion of Personal Data

The processing of personal data is subject to applicable laws related to the deletion of this data when the specified, explicit, and legitimate purpose for processing this personal data has expired. If there is no longer a legitimate purpose that requires the retention and use of personal data, it must be deleted. When deleting data in a data set, all referenced objects related to that data set must be deleted as well. Industry-specific legislation in different countries also needs to be taken into consideration in addition to general data protection laws. After the expiration of the longest retention period, the data must be deleted.

This SAP product might process data (personal data) that is subject to the data protection laws applicable in specific countries as described in SAP Note 1825544 .

DeletionTo enable even complex scenarios, SAP simplifies existing deletion functionalities to cover data objects that are personal data by default. For this purpose, SAP uses SAP Information Lifecycle Management (ILM) to help you set up a compliant information lifecycle management process in an efficient and flexible manner. The functions that support the simplified blocking and deletion of personal data are not delivered in one large implementation, but in several waves. Scenarios or products that are not specified in SAP Note 1825608(central Business Partner) and SAP Note 2007926 (ERP Customer and Vendor) are not yet subject to simplified blocking and deletion. Nevertheless, it is also possible to destroy personal data for these scenarios or products. In these cases, you have to use an existing archival or deletion functionality or implement individual retention management of relevant business data throughout its entire lifecycle. The ILM component supports the entire software lifecycle including storage, retention, blocking, and deletion of data.

End-of-Purpose CheckAn end of purpose (EoP) check determines whether data is still relevant for business activities based on the retention period defined for the data. The retention period is part of the overall lifecycle of personal data, which consists of the following phases:

● Business activity: The relevant data is used in ongoing business, for example contract creation, delivery or payment.

● Residence period: The relevant data remains in the database and can be used in case of subsequent processes related to the original purpose, for example reporting obligations.

● Blocking period: The relevant data needs to be retained for legal reasons. During the blocking period, business users of SAP applications are prevented from displaying and using this data. It can only be processed in case of mandatory legal provisions.

● Deletion: The data is deleted and no longer exists in the database.


http://help.sap.com/disclaimer?site=https://launchpad.support.sap.com/#/notes/SAP Note1825544



SAP Solution Sales Configuration for SAP S/4HANA

The SAP Solution Sales Configuration for SAP S/4HANA only processes data (user names) while updating configuration details in the database. It does not access any personal information of any business partners.

Deleting Knowledge Bases

The model dialog prompts the user for log on credentials that are used to delete the knowledge bases stored in the relevant connection properties.

For more information about this, refer to the SAP Help Portal and navigate to Solution Modeling EnvironmentSetup of Solution Modeling Environment SAP Modeling Perspective KB Admin Tool Support Deleting

Knowledge Bases .

Changing User Names for Knowledge Base Collections

This process is used to replace the user names in knowledge base tables with new user names:

1. Log on to the SAP backend system using the transaction: /n/slce/dpp_support2. Select the Update User Information radio button.3. Enter user information either manually or by pressing F4.4. Click F8 to replace the user names.5. Check the bottom of the screen to confirm the number of rows where the user name has been replaced.


Changing User Names in Workspaces

The transaction /n/slce/dpp_support provides a utility to change the user name in workspace and store tables, as these are the only tables modified by the UI Composer when user information is added or updated.

Checking and Updating User Names in Workspaces

You can use the transaction /n/slce/dpp_support to generate a utility for checking and updating user names in workspace and store tables.




7.5.6 Change Log

Creation and change of personal data need to be documented. Therefore, for review purposes or as a result of legal regulations, it may be necessary to track the changes made to this data. When these changes are logged, you should be able to check which employee made which change, the date and time, the previous value, and the current value, depending on the configuration. It is also possible to analyze errors in this way.

SAP Solution Sales Configuration for SAP S/4HANA

Displaying Change Logs in SAP Solution Sales Configuration for SAP S/4HANA

In the worklist of SAP Product, you can access a change log for each change request and activity.

NoteChange logs can only be displayed if the user is assigned the authorization role SAP_AUTH_MOC_ADMIN.

Under Evaluate New Audit Trail Enhancement Mode (transaction S_AUT10), you can see all changes that have been processed for the change document objects in SAP product, S_/IAM/ACT (activity) and /IAM/ISSUE (change request).


The change log is enabled for tables /slce/workspaces and /slce/store_def to track changes.

Personal data is subject to frequent changes. Therefore, for revision purposes or as a result of legal regulations, it may be necessary to be able to track the changes made to this data. If these changes are logged, you can check which employee made which change and when at any time. It is also possible to analyze errors in this way. You can change user information in knowledge base tables and these changes can be logged. You can use a report to display these changes.

Retrieving Knowledge Bases Associated with a User

This process is used to generate a report of the list of knowledge bases created/modified by the user:

1. Logon to the SAP backend system using the transaction /n/slce/dpp_support.2. Select the List all Knowledge Bases for User radio button.3. You can now enter user information either manually or by pressing F4.4. Click F8 to generate the list of knowledge bases.

See Also

For more information on change documents see the documentation at http://help.sap.com/netweaver. Choose the relevant SAP NetWeaver version and open the following documentation:

● Under Application Help, go to SAP NetWeaver Library: Function-Oriented View Application Server ABAPOther Services Services for Application Developers Change Documents .

● Open the SAP NetWeaver Security Guide and go to Security Aspects for Lifecycle ManagementAuditing and Logging .


http://help.sap.com/netweaver

8 Operating SAP Solution Sales Configuration for SAP S/4HANA

This section contains general information about how to operate SAP Solution Sales Configuration for SAP S/4HANA.

NoteThis section does not replace the operations handbook in which customers or the operations organization documents specific tasks, involved parties, and interaction procedures.

8.1 Other Required Documents for Operations

This section lists other documents that you need in order to operate SAP Solution Sales Configuration for SAP S/4HANA.

SAP Solution Sales Configuration for SAP S/4HANA is based on SAP S/4HANA On Premise 1809. The general operations information that is covered in the related operations guides also applies to SAP Solution Sales Configuration for SAP S/4HANA.

Document Where to Find It

Product assistance for SAP Solution Sales Configuration for SAP S/4HANA

See the Operations Information section.

SAP Help Portal

8.2 Monitoring

This section describes monitoring tasks for SAP Solution Sales Configuration for SAP S/4HANA.


Operating SAP Solution Sales Configuration for SAP S/4HANA

https://help.sap.com/viewer/DRAFT/d048886b27c9483987c0455c2aa4adee/1907/en-US/5c0016b99170446dafe71bf8d6215293.html

8.2.1 Monitoring Concept

Use

Wily Introscope is a third-party administrative tool from Computer Associates. It is used for application performance monitoring and diagnostics, and can be integrated with SAP Solution Sales Configuration.

More Information

For more information about Wily Introscope, see http://wiki.sdn.sap.com/wiki/display/TechOps/RCA_Home..

For information about the installation, setup, and configuration of Wily Introscope, see SAP Notes 797147(Introscope Installation for SAP Customers) and 1237887 (Introscope 7.2.3 Release Notes).

8.2.2 Logging and Tracing

You can implement logging and tracing in SAP Solution Sales Configuration using the standard logging capabilities provided in the Java Development Kit (JDK). The package java.util.logging provides logging capabilities via the class Logger.

After installing the solution modeling environment plug-in in Eclipse, you can enable logging in the eclipse.ini file.

Alternatively, you can use the general Java util logging settings. For more information, refer to the Java logging application programming interface (API) documentation.

Java Netweaver Logging

The application (session) log is important for the understanding and initial analysis of the issue as well as the technical flow of the process.

You can create an application log using the instructions in SAP Note 1090753 (Creation of logs for WebChannel/E-Commerce applications).

You can create a session-specific log using the instructions in SAP Note 921409 (Enable session tracing in mySAP/SLCE/(S/4) 5.0 java components).

SAP Solution Sales Configuration for SAP S/4HANA: Administration GuideOperating SAP Solution Sales Configuration for SAP S/4HANA CONFIDENTIAL 119

http://help.sap.com/disclaimer?site=http%3A%2F%2Fwiki.sdn.sap.com%2Fwiki%2Fdisplay%2FTechOps%2FRCA_Home

http://help.sap.com/disclaimer?site=http%3A%2F%2Fwiki.sdn.sap.com%2Fwiki%2Fdisplay%2FTechOps%2FRCA_Home





8.2.3 Alert Monitoring

This section describes available monitoring tools for SAP Solution Sales Configuration for SAP S/4HANA.

8.2.4 Error Logs

This section describes the error logs used by SAP Solution Sales Configuration for SAP S/4HANA.

8.2.5 Workload Monitoring

This section describes aspects of workload monitoring for SAP Solution Sales Configuration for SAP S/4HANA.

8.2.6 Interface Monitoring

This section describes aspects of interface monitoring relevant for SAP Solution Sales Configuration for SAP S/4HANA.

8.2.7 Background Job Monitoring

This section describes all background jobs used by SAP Solution Sales Configuration for SAP S/4HANA.

8.3 Administration and Management

This section describes administrator tasks for SAP Solution Sales Configuration for SAP S/4HANA.



8.3.1 Cache Management

Clearing SAP Solution Sales ConfigurationRuntime Engine Cache on NetWeaver Java Server

You can clear the SAP Solution Sales Configurationruntime engine cache on the NetWeaver Java server using the procedure below:

1. Log in to NW Operations Start & Stop

Logging on to NW2. Once you click on Start & Stop, go to the Java Applications tab3. Search for keyword slc and select the component cdev~fbs_slc_java

Selecting the Component4. Click on Restart to refresh to clear the cache

Refreshing the Cache


Monitoring SAP Solution Sales ConfigurationRuntime Engine Cache on SAP Management Console

You can monitor SAP Solution Sales Configuration runtime engine cache on SAP management console using the procedure below:

1. Go to Console Root SAP Systems W73 localhost0 AS Java CachesRight click and Refresh.

2. In the details window, filter the list of AS Java Caches by /AP/* to view further details of the relevant caches

Monitoring SAP Solution Sales ConfigurationRuntime Engine Cache on SAP Management Console

8.3.2 Solution Configuration Support - Backend Utilities

Use the solution configuration support to access (transaction /n/SLCE/CFG_SUPPORT in S/4HANA) SSC-specific utilities.

SAP Solution Sales Configuration for SAP S/4HANA Download XML

Here, you can download the sales data in an XML, simply by entering the relevant document and item numbers.

Knowledge Base Preload

Here, you can preload some standard data and inputs for the configuration page, to enhance performance of the tool. The knowledge bases are synced with a cache that is called when the pre-defined set of inputs are entered to generate the configuration page.

You can do this simply by entering the product name, type, its validity date, and the name of the production system.



Update Cache for External Text and Variant Tables

Here, you can update the data that is stored in the cache, post updation of the data in the external text and variant tables.

You can identify the specific table for updation and use this utility to process the change in data.

Delete Orphan Configuration XML

Here, you can clean up your system and remove the configuration XMLs that are now obsolete.

You can simply simulate the procedure.

Compare KB Runtime Version

This utility calculates size information for a given set of knowledge base runtime versions.

SME Models STORAGE Migration

For models created with version lower than SME 4.0, this utility is required to update the KnowledgeBase table for storage indicator. Models created with SME should have storage = 30 in table COMM_CFGKB.

Data Protection and Privacy

This utility provides the following functions:

● Displays all knowledge bases created/changed by a user● Replace the user name from knowledge base tables

8.3.3 Starting and Stopping

This section describes how to start and stop SAP Solution Sales Configuration for SAP S/4HANA.


8.3.4 Technical Configuration

This section describes aspects of technical configuration for SAP Solution Sales Configuration for SAP S/4HANA.

8.3.5 Backup and Restore

This section describes procedures for backing up and restoring SAP Solution Sales Configuration for SAP S/4HANA.

8.3.6 Periodic Tasks

This section describes periodic tasks that must be completed forSAP Solution Sales Configuration for SAP S/4HANA.

8.3.7 Load Balancing and Scalability

This section describes aspects of load balancing and scalability that are relevant for SAP Solution Sales Configuration for SAP S/4HANA.

.

8.3.8 High Availability

This section describes aspects of high availability that are relevant for SAP Solution Sales Configuration for SAP S/4HANA.

8.4 Software Change Management

This section provides information about how to deploy software changes for your software components.

Software change management standardizes and automates software distribution, maintenance, and testing procedures for complex software landscapes and multiple software development platforms.



9 Troubleshooting

This section describes troubleshooting topics for SAP Solution Sales Configuration for SAP S/4HANA.

Info Description Solution

ERROR registration of tp <progid> from host <host> not allowed.

This error occurs if the host that is trying to register at the gateway is not listed in the ACL of the gateway (reginfo).

See SAP Note 1069911 .

FAQ about Solution Modeling Environment

Frequently asked questions pertaining to the usage of Solution Modeling Environment


FAQ about Solution Sales Configuration Frequently asked questions pertaining to the usage of Solution Sales Configu-ration


FAQ about SAP Solution Sales Configu-ration Commerce

SAP Solution Sales Configuration Commerce - Frequently Asked Questions


- This issue occurs when you simultaneously open several sessions of IPC-UI (JSP-UI) on a client and the different sessions are not handled correctly


SAP Solution Sales Configuration for SAP S/4HANA: Administration GuideTroubleshooting CONFIDENTIAL 125






10 Support Components

To get support for SAP Solution Sales Configuration RUNTIME, S/4HANA integration, SME, and E-Commerce integration, create a ticket on component S/4HANA-SLC.

In addition to this, for issues encountered in the Solution Modeling Environment (SME), attach the log files to allow us to recreate the issue.

NotePer the data protection and privacy guidelines, please ensure that any test data shared with SAP is free from any kind of sensitive personal information. It is the responsibility of the customer to mask/erase any such data before making it available to SAP.

For more information on data protection and privacy guidelines, refer to the Data Protection and Privacy section.

For more information about creating the ticket, refer to SAP Note 2251429 (Support for Solution Sales Configuration (SSC)).

Related Information

Data Protection and Privacy [page 110]


Support Components


Important Disclaimers and Legal Information

HyperlinksSome links are classified by an icon and/or a mouseover text. These links provide additional information.About the icons:

● Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your agreements with SAP) to this:

● The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.● SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any

damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.

● Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering a SAP-hosted Web site. By using such links, you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this information.

Videos Hosted on External PlatformsSome videos may point to third-party video hosting platforms. SAP cannot guarantee the future availability of videos stored on these platforms. Furthermore, any advertisements or other content hosted on these platforms (for example, suggested videos or by navigating to other videos hosted on the same site), are not within the control or responsibility of SAP.

Beta and Other Experimental FeaturesExperimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by SAP at any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use the experimental features in a live operating environment or with data that has not been sufficiently backed up.The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your feedback (e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.

Example CodeAny software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax and phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of example code unless damages have been caused by SAP's gross negligence or willful misconduct.

Bias-Free LanguageSAP supports a culture of diversity and inclusion. Whenever possible, we use unbiased language in our documentation to refer to people of all cultures, ethnicities, genders, and abilities.

SAP Solution Sales Configuration for SAP S/4HANA: Administration GuideImportant Disclaimers and Legal Information CONFIDENTIAL 127

www.sap.com/contactsap

© 2021 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company. The information contained herein may be changed without prior notice.

Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names mentioned are the trademarks of their respective companies.

Please see https://www.sap.com/about/legal/trademark.html for additional trademark information and notices.

THE BEST RUN

https://www.sap.com/about/legal/trademark.html

Date post:	21-Jan-2023
Category:	Documents
Upload:	khangminh22
View:	0 times
Download:	0 times