Scribd
Upload
84 views18 pages

Process Management Configuration

Uploaded by

Rituraj Jain
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
84 views18 pages

Process Management Configuration

Uploaded by

Rituraj Jain
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 18

Process Management Configuration in solution manage 7.

In this step, you activate SAP Gateway services (OData services) for Process
Management. You need these to enable the SAP Solution Manager Fiori Launchpad, and
the SAP Fiori apps and mobile applications for Process Management.

Under Infra preparation we can see gateway service is enabled

To work with the SAP Solution Manager Launchpad, you must activate the following SAP
Gateway services:

 Services for the Fiori Launchpad, external service names INTEROP,


PAGE_BUILDER_PERS, PAGE_BUILDER_CONF, PAGE_BUILDER_CUST, TRANSPORT
 Service for Guided Procedure Authoring Documents, external service name
GPA_ODATA_DOC_SRV

For Use Case A, you have activated these services under SAP Solution Manager >
Cross-Scenario Configuration > Mandatory Configuration > Infrastructure Preparation,
step Enable Gateway Services, in the List of Gateway Services, under Cross Scenario
Configuration.

Under infra configuration

Note - It is recommended that you manually select all activated Gateway Services and activate
them again to ensure that the newly added relevant Gateway Services are included in the Activation.
If you still receive warning status in this step, please try to go through a few rounds of manually
selecting those activated Gateway Services to ensure that no relevant Gateway Services are
accidentally left out.
Now under process Management, Enable Gateway service tab will be green
Once you click on Execute customer code Management

 Activate BW Content

Enables various data providers in the Business Intelligence (BI) client of SAP
Solution Manager.
o Activate BW Content for SAP References: activates the InfoCube for
references (0SM_CCREF). In this cube, you can store the raw data from
code-analysis results for references used in custom code objects.
o Activate BW Content for CCLM: activates the InfoCubes for CCLM
Reporting. (0SM_CCLM, 0SM_CCITY, 0SM_ICIDB, 0SM_ESRBM, 0SM_ESRG,
0SM_ESRSK). This group of InfoCubes is used for various reporting scenarios
(for example, city model KPI reporting).
o Activate BW Content for SQLM: activates the InfoCubes for SQL monitoring
(0SM_SQLM*). For systems with SQLM, the related data can be extracted to
these InfoCubes.
o Activate BW Content for ATC: activates the InfoCubes for quality ( 0SM_ATC,
0SM_ATCAG, 0SM_ATCEX). For systems where you perform code scans with
ABAP Test Cockpit (ATC), the scan results and exemptions can be stored in
these InfoCubes.
o Activate BW Content for Usage Logging: activates the Usage Logging
(UPL/SCMON) InfoCubes (0SM_UPL*), DSOs
Create user and put password Welcome@098
Create Solution

Execute T-Code SOLADM then click on Create Solution option

Just give Solution name and Technical name which you want to create

Now you can see it created two branches automatically which is Maintenance and Production
Click on Branch tab and you can see both branches

you can create a logical component group by clicking on the link Maintain Logical Component Groups
>Maintain Logical Component Groups. > Create above the logical component group table or select
Create from the context menu. The system opens the dialog Create Logical Component Group. Enter
your data in the fields Logical Component Group and Description
You can maintain technical systems in the dialog Assign Technical Systems.
Here solution is created now we will import best practice package into solution
Download SAP Best Practices Package (SAP BPP) for SAP Solman
7.2 processes

Prerequisites
 Solution is created – Yes (we have done it)
 Branch in Solution is created (ex. Import branch) Yes
 Logical Component Group in Solution is created Yes

1) Set up HTTP connections


To import SAP Best Practices Packages into solutions, the HTTP connections (OCDAPIS
and OCDSTORE) must be setup. For details on how to setup these connections, please
see SAP Note 2194123.
It is important, that…
 S-User maintained in the RFC Destinations is assigned to a valid SAP Customer
Number and valid in https://accounts.sap.com
 RFC Destinations OCDAPIS and OCDSTORE are working correct:
o The result for the OCDAPIS Connection Test is 404.
o The result for the OCDSTORE Connection Test is 200.

Created both RFC in SOA system as per mentioned SAP Note 2194123.

2) Add Package to SAP Solution Manager 7.2 Basket


SAP Best Practices packages are only available for import in Solution Administration, if
they are selected in the SAP Best Practices Explorer (https://rapid.sap.com/bp/).
It is important, that the S-User maintained in the RFC Destinations is the same S-User
used to add the package to the SAP Solution Manager 7.2 basket in SAP Best Practices
Explorer.
1. Open SAP Best Practices Explorer using the following
link: https://rapid.sap.com/bp
2. Choose With SAP Solution Manager 7.2
3. Select SAP Best Practices for SAP Solution Manager 7.2, edition 01
4. Choose Add to SAP Solution Manager 7.2 basket
https://rapid.sap.com/bp/ >> Click on SAP S/4 HANA, you will get below screen

You can view solution packages added to you solution manager 7.2 basket
Go to T- Code: SOLADM & Select tab Import >> Click on import

2456526 - "SAP customer number unknown for installation


number" while trying to import Best Practices package in
Solution Administration
Select SAP Best Practices Packages & click on check box.

click Next

select all the highlighted areas and click on Import

Note : We have created System landscape logical component group during solution creation, that the
reason its showing here

You will get above screen when Import is started.


In SM37 you can check below jobs during importing best practice.

Once import is finished you can check in the solution documentation under Import
Branch for SAP Best practice whether it is successfully imported or not.

Now you can validate in SOLDOC t-code

You might also like