The Complete Guide to On-Premises Deployment of SAP S/4HANA 2023
New Installation of SAP S/4HANA 2023 FPS1 – Part 1 – Maintenance Planner
This procedure is Part 1 of the series which describes the very first steps to download the media. We will focus on creating Sandbox type instance with co-deployed (embedded) gateway.
As a prep you may like to empty the download basket for your S-000 user so that any files added to the download basket are meant for this task and will help to ensure that only the required files are included.
As a prep you may like to empty the download basket for your S-000 user so that any files added to the download basket are meant for this task and will help to ensure that only the required files are included.
You need to login to SAP Maintenance Planner to access system assigned to your S-user. Please ensure landscape data is uploaded to SAP support portal via LMDB of SAP Solution Manager. The diagram below shows the Maintenance planner cloud service and how it integrates with Customer system.
The source system is first defined in Maintenance planner (1) generates (2) stack.xml, used for (3) Installation and (4) Upgrade and then system
is (5) registered with Solution Manager. The system data is synchronized with Landscape Management Database (LMDB). From LMDB the data is (6) uploaded to customer profile in SAP support portal. (7) Data Fetch occurs using Solman daily job – “Landscape Fetch”.
If there is issue in replicating you may be asked to apply Note 2186164 – Problem in replicating systems to SAP Maintenance Planner
TIP: This data based on Customer Number is used by Maintenance Planner for all planning activities. Also ensure you use same Customer Number to define
system in sapnet. Use the S-user id of this Customer Number.
Login to SAP Maintenance Planner and select the SAP Fiori tile Plan for SAP S/4HANA
In the next screen,choose Install a new SAP S/4HANA system, Manual Installation. Here you can click on the link for the SAP S/4HANA on SAP Help Portal for the documentation and click on Next.
In the next screen enter SID = S4H; select Target Version = SAP S/4HANA 2023; Target Stack = 01 (02/2024) FPS
TIP: The component SAP Predictive integrator is selected by default but please note this component will not be installed by SWPM/SUM but has to be
manually installed on the database.
Click on Next.
TIP: The selection of component above will only download the files. You have to install them as per the procedure for the component.
In the next screen choose Co-deployed with Backend. Please refer SAP Fiori Deployment Options and Landscape recommendations for detailed information.
Please select checkmark Target Product Instances as applicable depending on which SAP FontEnd Applications you need among UI for SAP
S/4HANA, SAP Human Capital Management, SAP Master Data Governance and SAP Travel Management.
In the next scree click on Continue Planning
In the next screen Click on Next
In the next screen select OS/DB dependent files checkmark Linux on x86_64 bit and click on Confirm Selection.
You will get warning as below. Go through the Note and click on Continue.
In the next screen click on Next.
Click on NON-ABAP and you find that only DE and EN are selected by default. Select any other languages you require for installation.
TIP: The files are selected above for download only. Later on during installation, you have to select the languages in the SUM tool.
In the next screen click on Download Stack XML, Download Stack Text File, Download PDF and Export to Excel to download the files to your desktop. Out of
these you will have to ftp the stack.xml file to the server. It will look something like this – MP_Stack_2001518606_20240228_.xml
TIP: Before you click on Push to Download Basket on next screen, please ensure that download basket is empty so that the download contains only the files
needed for SAP S/4HANA installation.
Click on Push to Download Basket. This will load the Download Basket with files you need.
In the pdf file downloaded above, in the Planned Changes section there is a link provided that takes you directly to Service Marketplace to download the media.
Download all the media and separate the following into separate directories for convenience under /sapmedia/download. This includes files from Maintenance Planner
You need the files below for the installation, please check if these are included in the maintenance planner download: SWPM20SP17_0-80003424.SAR – Latest version of Software Provisioning Manager
SUM20SP19_1-80002456.SAR - Latest version of Software Update Manager SAP HANA DATABASE:
HANA Database and Database Client media is already provided in the Maintenance Planner download basket.
PleasereferSAPNote3421172-SAPS/4HANA2023FeaturePackageStack01:AdditionalReleaseInformation forSAPHANAdatabasereleasedetails. However, please check Note to ensure there are no problems with the SAP HANA release you select. Refer SAP Note 2655761 - SAP S/4HANA - restrictions and recommendations regarding specific revisions of SA...
IMDB_SERVER20_076_0-80002031.SAR - Latest version of SAP HANA Database as of this blog (Linux x86_64 64bit) IMDB_CLIENT20_019_21-80002082.SAR - SAP HANA Client (Linux x86_64 64bit)
If you want to install LiveCache you will require the SAP HANA database LCAPPS plugin from Software Downloads => SUPPORT PACKAGES AND PATCHES => SAP HANA PLATFORM EDIT 1.0 => HANA LCAPPS => SAP HANA LCAPPS 1.00
TIP: If the above path is not available, please search for below file in the url https://launchpad.support.sap.com/#/softwarecenter/support/index IMDB_LCAPPS_2076_0-20010426.SAR - Corresponding version of SAP HANA LCAPPS (Linux x86_64 64bit)
Download all the media and separate the DB files IMDB* into separate directories for convenience under /sapmedia
OTHER FILES:
In addition, please download file/s for best practices content activation from SAP Note 3409343 - SAP Best Practices for SAP S/4HANA 2023 Cloud, private edition FP-Stack 01 (02/20... .The file will be in this format BPS4CONT202301_0_0-80008741.ZIP
crlbag.p7s from https://tcs.mysap.com/crl/crlbag.p7s
COMPONENT FOR INCIDENTS:
You can open OSS messages using component BC-UPG-MP
OTHER REFERENCES:
Maintenance Planner - User Guide
Maintenance Planner Help Portal
Maintenance Planner – Frequently Asked Questions
New Installation of SAP S/4HANA 2023 FPS0 – Part 2 – Installation
This blog includes installation of SAP S/4HANA 2023 FPS0 and will focus on creating Sandbox type instance with co-deployed (embedded) gateway.
STEP 1: OPERATING SYSTEM
It is recommended to install SuSE Linux or RedHat Linux. Refer SAP Note 2235581 - SAP HANA: Supported Operating Systems.
SAP Note 2399995 - Hardware requirement for SAP HANA 2.0
SAP Note 2620910 - SAP S/4HANA 1511, 1610, 1709 and SAP BW/4HANA 1.0: Recommended Application Server...
SAP Note 3108303 - SAP HANA DB: Recommended OS Settings for RHEL 9
SAP Note 2684254 - SAP HANA DB: Recommended OS settings for SLES 15 / SLES for SAP Applications 15
You can check your operating system version as below:
|
sid-hdb-s4h:~ # cat /etc/os-release |
|
NAME="SLES" |
|
VERSION="15-SP3" |
|
VERSION_ID="15.3" |
STEP 2: SAP HANA DATABASE
It is recommended to install minimum SAP HANA 2.0 SP07 rev71
SAP Note 2655761 - SAP S/4HANA - restrictions and recommendations regarding specific revisions of SA...
SAP Note 3198680 - SAP HANA Platform 2.0 SPS 07 Release Note
SAP Note 3364390 - SAP HANA 2 SPS07 Revision 073.00 <= Current at S/4HANA 2022 FPS2 release
SAP Note 2423367 - Multitenant database containers will become the standard and only operation mode
SAP Note 2469025 - How-To: Upgrading to SAP HANA 2.0
We will install HANA database through SWPM. So you need to have the SAR file IMDB_SERVER20_073_0-80002031.SAR available along with SAP HANA Client IMDB_CLIENT20_018_24-80002082.SAR
After S/4HANA and HANA Database are installed please follow SAP Note 2600030 - Parameter Recommendations in SAP HANA Environments for parameter recommendations. This note contains check scripts which detect SAP HANA version, SAP product installed, etc. and give specific parameter recommendations.
|
TIP: Please change the log mode if you don’t want to be spend time on log maintenance: In HANA studio –> Configuration –> global.ini –> persistence and set the parameter log_mode to overwrite. When you change the log mode, you must restart the database system to activate the changes. |
|
It is also recommended that you perform a full data backup. You can also set the log_mode to ‘overwrite’ using the following SQL-Statement: |
ALTER SYSTEM ALTER CONFIGURATION ('global.ini', 'SYSTEM') SET ('persistence', 'log_mode') = 'overwrite' WITH RECONFIGURE;
STEP 3: SAP S/4HANA INSTALLATION USING SWPM
TIP: You don't need to extract the backup zip files S4CORE108_INST_EXPORT_*.zip. SWPM tool will extract them into /usr/sap/HDB/HDB02/backup/data/DB_HDB. Ensure sufficient space of 100GB is available in this folder.
We will use the procedure for SWPM+SUM combined installation and you don't need the SYSTEM/DDIC password from backup Database/ABAP instance. Extract the SWPM SAR file as below
|
sid-hdb:/ # cd /install |
|
sid-hdb:/install # /sapmedia/SAPCAR -xvf /sapmedia/download/SWPM20SP16_0-80003424.SAR |
You should get message at the end of this that SAPCAR: ... files(s) extracted Execute SWPM to do system copy with backup restore as below:
sid-hdb:/install#./sapinst
SAPINST_USE_HOSTNAME=vhcals4hci SAPINST_STACK_XML=/sapmedia/download/MP_Stack_1001829732_20231011_.xml
I started with command:
./sapinst SAPINST_USE_HOSTNAME=vhcals4hci SAPINST_STACK_XML=/sapmedia/download/MP_Stack_1001829732_20231011_.xml
This is ok for sandbox.
I am showing only the important screens as most are self explanatory. Select Standard System from path below:
Click on Next
At the screen Software Integrity click on Next
|
TIP1: If you select Typical at next parameter, those skipped are shown in Strikethrough. Skipping these parameters will save some time and you may be able to change them in the |
|
final Parameter Summary.If you need integrated web dispatcher please select Custom. |
TIP2: To take less time for installation I have copied the kernel files into a subdirectory of download so that it takes less time to scan & search for media. Also copy files S4CORE108_INST_EXPORT* into separate folder.
At the screen Parameter Settings select Custom and click on Next
At the screen General SAP System Parameters accept SAP System ID (SAPSID) S4H SAP Mount Directory /sapmnt
At the screen (strikethrough font means dialog is skipped if you select "Typical" option in the beginning) set FQDN for SAP system checked, DNS Domain Name for SAP System dummy.nodomain click on Next
At the screen Master Password specify Master password and confirm password Xxxxxxxn click on Next At the screen accept master password or enter password Xxxxxxxn
At the screen SAP HANA Database for SAP System enter details
Database Host vhcalhdbdb
Database ID (DBSID)HDB
Instance Number 02
Password of DBA Xxxxxxxn click on Next
At the screen SAP HANA Multitenant Database Containers enter password for HANA Database superuser Xxxxxxxn click on Next
At the screen Software Package Browser enter path for the downloaded media from Maintenance Planner. Package Path: /sapmedia/download click Next
The status will change from "still missing" to "Available". Click on Next
At the screen Prerequisites Checker Results please resolve or ignore any issues. Click on Next.
At the screen Upgrade SAP Host Agent checkmark Upgrade SAP Host Agent with provided version and click on Next , after it is shown as "Available". Click on Next
At the screen Configuration of SAP liveCache with SAP HANA accept uncheck on Install SAP liveCache for SAP System and click on Next TIP: We will be installing HANA DB through SWPM, and this option has to be uncheck to proceed further
At the screen SAP HANA Client Software Installation Path choose radio button Local Client Directory click on Next
At the screen Software Package Browser enter the Package Path /sapmedia/hana2/IMDB_CLIENT20_018_24-80002082.SAR and click on Next
At the screen Media Browser enter Package Path /sapmedia/download/exp click on Next.
TIP: SWPM takes 20 minutes to verify and check the zip files
Individual Package Location will change to
/sapmedia/download/exp/S4CORE108_INST_EXPORT_1.zip click on Next
At the screen Software Package Browser accept Individual Package Locations /sapmedia/download/exp/S4CORE108_INST_EXPORT_[2..30].zip
At the screen Software Package Browser enter location of HANA Database file /sapmedia/hana2/IMDB_SERVER20_73_0-80002031.SAR Click on Next
At the screen General SAP HANA Database Parameters accept defaults for Instance Number and SAP Mount Directory and click on Next
At the screen HANA Database Administrator accept defaults and click on Next
|
TIP: If you need to install additional software, at this point it is better to ensure the files SAPPAAPL4_2203_2-80004547.ZIP and HANAUMML12_7-70001054.ZIP are copied to the |
|
folder /sapmedia/hana2 |
At the screen SAP HANA Additional Archives select checkmark for Install HANA software for PAi Click on Next. This step will select HANA Automated Predictive Library and HANA DU for Unified Model Manager.
At the screen Database Schema accept schema DBACOCKPIT password and confirm Schema password Xxxxxxxn click on Next At the screen Database Schema accept schema SAPHANADB password and confirm Schema password Xxxxxxxn click on Next
At the screen SAP HANA Data at Rest Encryption accept the master password or checkmark on Set Root Key Backup Password to enter password and click on Next
At the screen Secure Storage for Database Connection select HANA Secure User store (hdbuserstore) click on Next At the screen s accept parameter values to keep on import and click on Next
TIP: Please note that database log mode is Overwrite by default here and you can change if needed. Configuration File=global.ini, Section=persistence, Parameter Name=log_mode, Parameter Value=overwrite
At the screen SAP liveCache with SAP HANA checkmark on Install SAP livecache for SAP System and click on Next At the screen Software Package Browser select Package Path and click on Next
At the screen Primary Application Server Instance and ABAP Central Services Instance accept values PAS Instance Number 00, PAS Instance Host vhcals4hci ASCS Instance Number 01, ASCS Instance Host Name vhcals4hci click on Next
At the screen accept values for Ports 3601 and 3901 click on Next
At the screen accept number of Dialog Work Processes (10) and Number of Batch Work Processes (6) click on Next
At the screen r accept password for webadm Xxxxxxxn and click on Next
At the screen SLD Destination for the SAP System OS Level leave default radio button at No SLD destination click on Next
At the screen leave default radio button at Do not create Message Server Access Control List click on Next
At the screen enable checkmarks at Install integrated web dispatcher and Install Gateway integrated in ASCS instance and click on Next
At the screen s leave default dispatcher parameters HTTPS Port 44301, Encryption Always, Configure HTTP Port Yes, click on Next
At the screen leave default for Add Security Profile Parameters, click on Next
At the screen Secure Storage Key Generation accept radio button – Individual Key (Recommended for Productive Systems) On the Next
At next screen Warning click OK
At the screen SAP System Users Passwords enter password for DDIC and SAP* in Client 000 click on Next
At the screen Configuring Transport Management for Single System select Run TMS config and enter password for TMSADM in Client 000 click on Next
At the screen Import SPAM/SAINT Update for Import SPAM/SAINT Update select radio button Yes SPAM/SAINT Update as /download/KD75785.SAR and click on Next
At the screen leave radio button at default No for Import ABAP Transports click on Next
At the screen checkmark on Install Additional SAP System Languages and click on Add. click on Next
At the screen Preparing for the Software Update Manager checkmark for Extract the SUM *.SAR archive and Start Sum Automatically. Click on Next
At the screen Software Package Browser accept Individual Package Location /sapmedia/download/SUM20SP18_0-80002456.SAR Click on Next
At next screen Cleanup of Operating System Users checkmark on Yes cleanup os users and click on Next
Here is the Parameter Summary Click on Next to confirm and begin the installation.
At next screen 99% Information click on OK
TIP: Please click on the url https://vhcals4hci.dummy.nodomain:1129/lmsl/sumabap/S4H/doc/slui and continue with the upgrade in another browser tab.
You can then continue in the sapinst tab to complete SWPM. Using the combined SWPM+SUM command with stack.xml many dialog screens are skipped.
On sapinst screen click on OK.
Fill in the Feedback to SAP. and Exit
STEP 4: ADDON INSTALLATION USING SUM TOOL
As we executed combined SWPM+SUM you should have filesystem /usr/sap/S4H/SUM and you should directly jump to url https://vhcals4hci:1129/lmsl/sumabap/S4H/doc/slui
If not, don’t worry, please extract it as below 2 commands:
|
as s4hadm |
|
cd /usr/sap/S4H |
|
as root |
|
ps –ef | grep –i sapup /usr/sap/S4H/SUM/abap/SUMSTART confighostagent |
|
TIP: Please check that your /windows/drivers/etc/host file contains entry with IP address mapped to hostname vhcals4hci.c:\users\mahesh>type c:\windows\system32\drivers\etc\hosts10.20.130.140 vhcals4hci vhcals4hci.dummy.nodomain vhcals4hcs vhcals4hcs.dummy.nodomain vhcalhdbdb |
|
vhcalhdbdb.dummy.nodomain |
Open Google Chrome browser (latest version recommended) Enter URL:
https://vhcals4hci:1129/lmsl/sumabap/S4H/doc/slui
In case you get screen below please click on Advanced and then “Proceed to vhcals4hci(unsafe)"
Enter s4hadm/(password you used before) in the screen below
TIP: If you get message that Page is Unresponsive just click on Wait.
GET ROADMAP
TIP: If you start with sapinst command combined with SWPM+SUM, the SUM tool may skip most of the screens to reach the final stage at 90% with SPAUINFO.
At Additional Parameters for "Update on SAP S/4HANA (Single System)" Check archive authenticity and checkmark Switch expert mode on.
EXTRACTION PHASE
No prompts here ....
TIP: If you get error manifest signature revoked download new crlbag.p7s as per SAP Note 2491577 - SUM fails at phase
PREP_EXTRACT/SCAN_DOWNLOADDIR with error message "SIGNATURE: m...
CONFIGURATION PHASE
At (10%) Current Phase: PREP_EXTENSION/BIND_PATCH
Click on Next
At (13%) Current Status of Roadmap Step "Configuration" Click on Next (may be skipped)
CHECKS PHASE
At (16%) Current Status of Roadmap Step "Checks" Click on Next (may be skipped)
PREPROCESSING PHASE
At (60%) Current Phase MAIN_DTTRANSSHD/DOWNCONF_DTTRANS_BCK accept selected radio button Backup completed click on Next (if prompted)
Click on Next (may be skipped)
EXECUTION PHASE
At (88%) Current Phase:
End of technical Downtime, click Next (may be skipped)
POSTPROCESSING PHASE
At (90%) Current Phase: MAIN_POSTPROC/SUBMOD_SPAU_INFO/SPAUINFO
Adjust the repository objects as needed, click Next (may be skipped) At (94%) Current Phase: MAIN_POSTPROC/REQ_UP_FINAL
Start of Cleanup Processing, click Next (may be skipped)
At (98%) Current Phase: MAIN_POSTCLEAN/REQ_FINISH_IMPORT
Confirmation Required for Imports, check and select checkmark for I confirm that no more imports are running, click Next SUM is completed.
Please login to the system and check the Installed product version as: Please find Installed Software Component version:
TIP: Schedule complete SGEN if it is not completed so far. This will help reduce time needed for Best Practices Content Activation. STEP 5: SAP S/4HANA RELEASE INFORMATION NOTE
Please apply the notes as per SAP Note 3351047 - SAP S/4HANA 2023 Feature Package Stack 00: Additional Release Information these notes are only for SAP S/4HANA 2023 FPS0 only
|
NOTE |
DESCRIPTION |
MANUAL |
|
3373765 |
Not able to navigate or add few items in Cross catalog search with message "Resource Not Found." |
|
|
3363570 |
Service Documents and Event-Based Revenue Recognition – Sales Orders Apps Don’t Display Data Properly |
|
COMPONENT FOR INCIDENTS:
You can open OSS messages using component: for SWPM - BC-INS-SWPM
for SUM - BC-UPG-TLS-TLA OTHER REFERENCES:
Installation Guide
Administration Guide for Implementation
Administration Guide to Implementation of SAP S/4HANA 2023 with SAP Best Practices | SAP Help Portal
Your system installation is complete. Congratulations !!!
New Installation of SAP S/4HANA 2023 FPS0 – Part 3 – Best Practices Content Activation
Please refer 3393679 - Jump Start Your SAP S/4HANA 2023 Implementation by Activating SAP Best Practices which will guide you in preparing for implementation of S/4HANA using SAP Best Practices content.
WARNING: This blog provides guidance for activating S/4HANA 2023 FPS0 Best Practices when a client is setup as Best Practice client. If you set up a merged client as per Alternative 2 - Setting up a merged client (all client 000 reference settings), follow the activation guidance as per SAP Note 3346909 - Implementation of SAP S/4HANA SAP Best Practices 2023 (Private Cloud and On-Premi... (steps shown in this color)
NOTE: for Best practices activation purpose we recommend to use latest SAPGui, In case you are using SapGui version 7.50, you need to uncheck "Accept Belize theme". Once the Best practices activation is completed, you can activate the SAP Fiori visual theme back. This is shown later under SAP SAPGUI settings.
This blog includes installation of SAP S/4HANA 2023 FPS0 and will focus on creating Sandbox type instance with co-deployed (embedded Fiori gateway).
The step by step procedure for Best Practices Content Activation on SAP S/4HANA 2023 FPS0 has only two base languages EN & DE and Country= USA. Please refer Admin Guide.
Adding further language translations later is not supported once the solution is activated, therefore, identify and install all the required languages you may need in future (if possible). You can check the following blog post for information on how to import a large number of languages efficiently.
A new Solution Builder profile has been created with ALL scope items but in case you have finalized scope items you can select only the needed scope items. Depending on how many selected scope items, activation procedure will need less time The status of system before starting this procedure is clearly defined before starting.
Tax calculation for US sales and purchases:
The US solution for SAP S/4HANA 2023 (BP_OP_ENTPR_S4HANA2023_USV10.XML) is delivered with internal tax calculation. It includes sample Jurisdiction
codes and sample rates so that you can execute the best practices test scripts out of the box. For productive purposes, you must replace the sample
jurisdiction codes and rates with the your own user defined jurisdiction codes and actual tax rates. If you prefer to use an external tax provider, you must
configure the required settings
STEP 1: SAP S/4HANA 2023 FPS0 is installed and SPAM checked as per previous blog Part 2 link
STEP 2: All Notes should be applied after complete installation of SAP S/4HANA 2023 FPS0 as per SAP Note 3351047 - SAP S/4HANA 2023 Feature Package
Stack 00: Additional Release Information Apply all the SAP Notes mentioned in the above Note.
In addition please review SAP Note 3330286 - SAP Best Practices for SAP S/4HANA 2023 Cloud, private edition FP-Stack 00 (10/20...
TIP on Note 2987015 for VCH AFL installation: In this note it is mentioned that you have to download and install VCH AFL. This is S/4HANA release specific (for example 2023) as well as database specific (for example HANA 2 rel 73. Use the link to select your release 2023 and then download the specific file for the combination of S4H and DB for example VCH202300_2073_0-70007416.SAR
After you download install and follow SAP Note 1650957 - SAP HANA Database: Starting the Script Server. Excute SQL statement with SYSTEMDB@HDB
- ALTER DATABASE HDB ADD 'scriptserver'
(If you have multiple tenant databases please use SID of db that contains S/4HANA schema) and
then on tenant db HDB - GRANT AFL__SYS_AFL_VCH_2023_EXECUTE to SAPHANADB
After you have installed VCH AFL please login to S/4HANA system and run in SA38 report VCH_HL_AFL_CHECK and it should show green status.
also review SAP Note 3330258 - SAP S/4HANA 2023 collective note for content activation and SAP Note 3346909 - Implementation of SAP S/4HANA SAP Best Practices 2023 (Private Cloud and On-Premi....
STEP 3: Using SFW5, Enterprise Business Functions are activated as per Required Enterprise Business Functions in Admin Guide except FINS_PARALLEL_ACCOUNTING_BF which is only for pilot customers.
Please note that activation of some of the business functions requires additional licenses and you have to activate the business functions as per your requirements of scope list. For the purpose of the blog we have activated all business functions and scope items.
TIP: As compared to previous releases the Business Functions activation takes long time, therefore it is required to confirm that the activation job has finished successfully before proceeding.
STEP 4: Register client in table /FTI/T_NOCLN000 (for merged client do not register client in this table) so that Client Copy is done with tables defined in whitelist table /FTI/TWHITEL01.
If you want to perform client copy using new tCode SCCLN, use profile SAP_U000 for Best Practices client copy. For Merged client copy you can use you can use the copy profiles SAP_UCUS, SAP_CUST, SAP_CUSV, or SAP_UCSV. if you get any error message please create ticket using component SV-CLD-ACT.
TIP: Use the new tCode SCCLN to perform Client copy which is 10 times faster and you can do it form Client 000 or any other client than the target client and
don't need user SAP*/pass to perform client copy. If you use the new Client copy procedure you have to define logical system for Client 000 like S4HCLNT000
also besides the logical system for client 100. Otherwise you will get error - "Dedicated logical system is not defined".
Please see the screenshot below:
Copied client to have no currency in tCode SCC4.
CLIENT COPY VALIDATION: Please check table entries using tCode SE16, table (1) T001, click on (2) Number of entries to check number of entries. If there are (3) zero entries as below it is a Best Practices client.For Merged Client you should have some records in this table.
STEP 5: You may like to add Solution Builder to your Favorites in SAP Menu.as this is the transaction you will use until the activation is complete. Also add transaction SECATT. You can remove them from favorites after activation if not needed.
Review SAP Note 3330286 - SAP Best Practices for SAP S/4HANA 2023 Cloud, private edition FP-Stack 00 (10/20... Upload zip file from URLs in the above note to server.
Add transport request to buffer EERK033517 and EERK049970 with steps below tCode STMS, Import Overview,
After the transport is in buffer, select the transport and import, In the Options tab checkmark Ignore Invalid component version
STEP 6: Create users for content activation as per admin guide with details. Ensure Logon Language and Timezone (should not be empty, any timezone is ok).
STEP 7: Change SAP Profile parameters as below and restart SAP:
abap/heap_area_dia = 6442450944 sapgui/user_scripting = TRUE rdisp/scheduler/prio_high/max_runtime = 18000
USER SETTINGS:
-
Start transaction SU01.
-
On the User Maintenance: Initial Screen, enter the activation user name and choose Change.
-
On the Maintain Users screen, choose the Parameters tab, and enter the following parameter ID and parameter values:
-
Choose Save. Note - Do not delete any other existing parameters.
-
Log off and log back in before you start the SAP Best Practices activation.
STEP 8: Import solutions from SAP Best Practices content. Enter tCode /N/SMB/BBI. Choose menu Solution -> Import -> Solution (XML) -> From reference content
Select Solution Builder Content ID BP_OP_ENTPR_S4HANA2023_USV10.XML from below After import is complete log will be displayed. Click on icon Back
STEP 9: Defining the scope of your solution. (1) Copy Solution BP_OP_ENTPR_S4HANA2023_USV10 to (2) Z_MY_SOLUTION_US
Please click OK to exit.
Click on Favorite to make the solution Z_MY_SOLUTION_US as your favorite.
From the menu, choose Solution => Import => Installation Data => From reference content. Double click on INST_FILES_US_BP_S4BL_S4HANA2023_OP.ZIP
STEP 10: If only you need to remove scope items, double Click (or click on Change Icon) on Z_MY_SOLUTION_US to unselect the scope items from the list.
Descope the Decentralized EWM scope items:4RO, 4RP, 4RQ, 4RR, 4RS and 4UA as they are required only in a decentral EWM system. Also descope the UPA (Universal Parallel Accounting) scope items 3F0, 5W2, 6DF, 6DR, 6DS, 6DT, 6DU, 6EB, 6EC, 6ED, 6EE, 6EF, 6EG and 6VQ.
STEP 11: Enter tCode /n/SMB/SCOPE, Click button (1) New Entries, (2) Customer Solution and (3) select the Country and Solution as below:
Choose Save.
Now you can see that for Z_MY_SOLUTION_US the last icon shows with mouseover shows "Fully Uploaded Central Data Unchecked".
STEP 12: enter tCode SCC4 and ensure below values - Logical System - S4HCLNT100 (needed for EWM steps as per 3.5.1.4 of Admin Guide AdminGuideS4HANAImpl_HELP_EN.pdf in link), Currency - blank, Client role - Test or Customizing depending on the client role
STEP 13(OPTIONAL): Best Practices content activation for any solution will populate the client currency as USD by default. In case you want to have a
different client currency, you should change the currency before activation starts.You should not change client currency once the first solution in the client is
activated. The procedure is as follows:
Enter tCode /N/SMB/CD_MAINT
In the All Central Data Entities section, use (1) search to find (2) DSC in the table and double-click it, Click (3) Change and change the (4) ID field.
When activating several SAP Best Practices country solutions please follow the procedure provided in 2022 OP Admin guide. STEP14:PleasedoallthestepsneededforPre-activationsettingsforEWMscopeitemsasperAdminGuideaspertheadminguideinthe link
If you have activated business functions FICAC_CI and FICAC_CORE, do the steps as per Pre-Activation Settings for Contract Accounting and Convergent Invoicing in Admin Guide.
Creating Billable Item Class
-
Creating Consumption Item Class
-
Transferring Application Form from Client 000
STEP15: Depending on scope items you have selected, you may get less errors than shown in steps below. The timings are based on Cloud based VirtualMachine with 256GB RAM x 32 Cores. In the SECATT transaction there are certain number of log entries which are sown against each stop.
REMINDER: If you are activating in merged client please perform the pre-requisite steps as provided in the note follow the activation guidance as per SAPNote 3346909 - Implementation of SAP S/4HANA SAP Best Practices 2023 (Private Cloud and On-Premi... (steps shown in this color)
STEP16: Enter tCode /n/SMB/BBI and go to Solution Builder. Select the Solution and click on Implementation Assistant and Click on button Activate.
After 3 minutes you will be prompted with screen below.
You can select Skip this screen if you don’t want this screen from popping up everytime.TIP: In case you would like to migrate data to the new system then please uncheck "With Demo Data". You can use blog - New Installation of S/4HANA
2020 FPS0 Part 5 – Direct Data Transfer using Migration Cockpit (to be created for S/4HANA 2022) for rapid data migration using direct data transfer.
If a message pops up “To activate the project, the client settings need to be changed to eCATT and CATT allowed” please choose Yes. This would come up if you didn’t follow the earlier step in SCC4.
FIRST STOP:
This is a warning to confirm that you have configured the Group Currency. Please follow the steps given in the Admin Guide if you need to change the group
currency from standard delivered USD.
From this point forward it is not possible to change it. (1) Close the dialog and (2) Click on Confirm Manual Step to continue activation.
SECOND STOP:
During the activation if a warning appears then choose OK to continue.
THIRD STOP:
You will get Notification Dialog as shown below:
No steps to be done here, just click on on OK to continue. FOURTH STOP:
Click on OK.
Click OK to continue
FIFTH STOP:
Click OK to continue SIXTH STOP:
Click OK to continue
SEVENTH STOP:
You may get error on scope item 3AS as below:
Please do not confirm the step. Click on Activate.
You may get this error a couple of more times during the activation even after next 2 stops. please activate again to process the error.
EIGHTH STOP:
Click Yes to continue NINTH STOP:
Navigate to solution builder /n/smb/bbi. On the Interruption popup, choose Yes to continue. Start the activation in Implementation Assistant again.
LAST STOP:
STEP17: COMPLETION OF ACTIVATION At the end of activation you should get message “Solution Z_MY_SOLUTION_US is
activated”. CONGRATULATIONS !!!!
Please revert the parameter for rdisp/scheduler/prio_high/max_runtime, abap/heap_area_dia and adjust SAPGUI scripting as well as remove SAP_ALL authorization from functional users if granted separately.
LANDSCAPE CONSIDERATIONS:
STEP18: POST ACTIVATION - EXECUTING MANUAL REWORK ACTIVITIES:
This step should be done in DEV to create a solution for manual rework activities to general xml file for manual rework activities. This is simply a list of steps to be performed in Q just like a word document.
Please follow procedure as described in Admin Guide section 3.6 Executing manual rework activities.
Access tCode /n/SMB/BBI, select the solution you activated and set it to favorite. In the menu bar choose Solution -> Procedure -> Start a procedure. In the
Execute a Solution Processing Procedure dialog box choose procedure Manual Rework Required and choose OK.
STEP19: SYSTEM LANDSCAPE MANAGEMENT FOR QAS AND PROD:
Recommendation is not to do Content Activation of best practices in QAS and PROD. You have to move the transports as below in graphic.
-
SAP Best Practices client is set-up with specific client copy profile
-
SAP Best Practices customizing after initial activation
-
Manual extension of business configuration using IMG
-
Additional client 000 customizing for customer adaptation (Note 2838358)
(not needed for merged client)
In The QAS system, move transports to QAS first n above sequence.
CONFIGURATION GUIDES:
Please note that as of release 1909, configuration guides will be deprecated in the SAP Best Practices for SAP S/4HANA package.
COMPONENT FOR INCIDENTS:
As per the error message in the activation.
OTHER REFERENCES:
Administration Guide for Implementation
New Installation of SAP S/4HANA 2023 FPS0 – Part 4 – Rapid Activation for Fiori
This blog is based on SAP Note 3336782 - Composite SAP note: Rapid Activation for SAP Fiori in SAP S/4HANA 2023 Please use this blog only as a reference and follow the actual note which may have been updated.
Please find the rough sketch of steps. There are 3 sets of steps that are separated by thick line. Activate Enterprise Search (A) is kicked off and while it is running, you can do steps in group (B). And after enterprise search task is completed you can do tasks in group (C).
TIP: For notes applicable to other releases, please check the SAP Note 2902673 – Rapid Activation for SAP Fiori in SAP S/4HANA – Overview In this blog the text is shown in this COLOR it is for selection and copy/paste
STEP 1: CHECK SAP FIORI UI COMPONENTS
(A) Enter tCode SPAM -> button Package Level, tab Installed Product Versions, Check the below Product versions are installed - SAP S/4HANA 2023 and SAP FIORI FRONT-END SERVER 2023 & SAP FIORI FOR S/4HANA 2023.
(B) The S/4HANA system has to be with embedded Fiori deployment as per SAP Note 3336782 - Composite SAP note: Rapid Activation for SAP Fiori in SAP S/4HANA 2023
(C) Ensure that SGEN is already completed on the system
(D) Proper ICF/ICM setup including FQDN
(E) Ensure the system is configured for SSL
icm/server_port_0 = PROT=HTTP,PORT=80$$,PROCTIMEOUT=600,TIMEOUT=600 icm/server_port_1 = PROT=HTTPS,PORT=443$$,PROCTIMEOUT=600,TIMEOUT=600 icm/server_port_2 = PROT=SMTP,PORT=25000,TIMEOUT=180
(F) Suggested memory parameters. The strategy here is to double the memory parameter until runtime errors do not occur any more. You can reset back these memory parameters after activation. You can copy and paste lines into instance profile.
abap/buffersize = 2500000 # Fiori Rapid Activation Help Doc
(G) Please ensure that web dispatcher is setup correctly and working as it will be required before users can use the applications by logging in through the web dispatcher. Follow SAP Note 2740052 - Which paths are necessary to configure Web Dispatcher for Fiori Launchpad scenari...
(H) Apply the notes below through SNOTE. (note 2686456 and note 2813396 cannot be implemented as corrections through SNOTE as of 26 May 2022 but this may change later if there are more recent updates)
SAP Note 2510134 - Fiori Setup: Updates for task lists for Gateway/Fiori configuration
(for Tasklist SAP_GW_FIORI_ERP_ONE_CLNT_SETUP)
SAP Note 2712785 - Fiori Setup: Initial Setup for Fiori Applications S/4
(for Tasklist SAP_FIORI_FOUNDATION_S4)
SAP Note 2686456 - Fiori Setup: Content Activation for SAP Business Roles
(for Tasklist SAP_FIORI_CONTENT_ACTIVATION)
SAP Note 2813396 - Fiori Setup: Content Activation for Business Roles
(for Tasklist SAP_FIORI_FCM_CONTENT_ACTIVATION)
(I) Enter tCode STZAC and ensure the Timezone is set. If this is not set you will get error at task list SAP_FIORI_FCM_CONTENT_ACTIVATION with message - Service: <CDS View>_CDS 1 failed / ICF Node: not available
STEP 2: ACTIVATE ENTERPRISE SEARCH
In Work client, enter tCode STC01 - SAP_ESH_INITIAL_SETUP_WRK_CLIENT
TIP: All tasklists in this blog are to be performed in the work client
(A) Select Models to Create Connectors" -> specify software component for search models: SAPAPPLH
(B) Leave default at SAP Use SAP HANA Primary DB Connection : DEFAULT
Execute task and select Background, the job will run for 1.5 Hours or more (New Installation on S/4HANA with approved hardware and Software Component SAPAPPLH only before data migration).
If you get error - Internal session terminated with a runtime error PXA_NO_FREE_SPACE (see ST22) please refer Note 2149849 - Runtime error
PXA_NO_FREE_SPACE on ESH software component update which refers Note 147568 - PXA_NO_FREE_SPACE
Ensure PXA value in SAP profile abap/buffersize is enhanced, e.g. to 2.500.000 kB (Documentation)
TIP: While the Activate Enterprise Search task list is in progress in background you can do the activities form STEP 3 - 8 in parallel. The Fiori Content Activation task list should be done after the enterprise search is completed.
After task completion, the screen should look like this:
STEP 3: INSTALL DEPENDENT NOTES
Please install Note 1322182 - Memory consumption of ABAP Shared Objects
1. In tCode RZ11 check profile parameter abap/shared_objects_size_MB. I have this value set to 512. Keep in mind that if you get runtime error SYSTEM_NO_SHM_MEMORY or unhandled exception of type CX_SHM_OUT_OF_MEMORY you will have to increase this parameter. Alternatively you can set the automatic memory parameter PHYS_MEMSIZE.
STEP 4: INITIALLY FILL CUSTOMER TABLES
Enter tCode SU25, Make sure Step 1 "Initially fill the Customer Tables" has been at least executed two times. If date/time entry for this step is empty, click
on the step and press execute (with default settings). Ref Note 440231 - SU25 | FAQ: Upgrade postprocessing for Profile Generator
Click on Execute
You should get application help dialog message that it will take several hours and log below. If not execute the same procedure second time and get the numbers as below.
Execute the same procedure second time and get the numbers as below. It is verified that below screen is as shown.
STEP 5: ACTIVATE SAP S/4HANA EMBEDDED ANALYTICS Ensure logical client is assigned to target client in SCC4
Execute manual steps as per SAP Note 2289865 - Configuration steps for S/4HANA Analytics as shown below in work Client 100.
Prerequisites: Check function module tCode SE16 table RSADMINA field BWMANDT in table RSADMINA isn’t filled.
If above is not set, use tCode SE37 RS_MANDT_UNIQUE_SET to set value of I_MANDT = 100
After above command is executed please check the value of BWMANDT in SE16 table RSADMINA
-
In Client 100, Execute task list STC01 SAP_BW_SETUP_INITIAL_S4HANA.
-
In the first step confirm that you have read the SAP Note 2303900 - Latest Information about BW Setup in S/4HANA Systems
-
In the step Set/Check BW Client enter the BW Client number, and in the step Install essential BW Content checkmark on Force Installation. The task list will run for less than 15 minutes.
4. Please do remaining optional steps as per the note for Hierarchies - 0YEA_QUA_MON_DAY, 0YEA_MON_DAY & 0WEEK_DAY
5. Configuration of Design Studio Template
Activate the following services
/sap/bw/ina
/sap/bw/Mime
STEP 6: ACTIVATE GATEWAY & FIORI ONE CLIENT SETUP
Check that note is applied as per STEP 1 - SAP Note 2510134 - Fiori Setup: Updates for task lists for Gateway/Fiori configuration enter tCode STC01 - SAP_GW_FIORI_ERP_ONE_CLNT_SETUP
After task completion which takes about 20 seconds, the screen should look like this
STEP 7: RUN FIORI FOUNDATION TASKLIST
Check that Note is applied as per STEP 1 - SAP Note 2712785 - Fiori Setup: Initial Setup for Fiori Applications S/4
In Work Client, enter tCode STC01 - SAP_FIORI_FOUNDATION_S4
This task list activates (1) ICF Nodes (2) ODATA Services required for WebGUI and other generic Fiori launchpad features, (3) Initializes classic UI technologies,
(4) Generates working SAP Fiori launchpad user & admin roles including composite roles.
Please run this task in Foreground so its easy to handle if error occurs in next screen.
After tasks are completed, the screen should look like below.
STEP 8: AUTOMATIC ACTIVATION - ADDITIONAL TASK LISTS
There are some additional task lists under Automatic Activation of Embedded-Deployed SAP Fiori as mentioned in the note 3132689.
Task Lists are /UIF/SCHEDULE_LREP_JOB and Task list /UI2/FLP_HEALTH_CHECKS
In case you get error below for task list /UI2/FLP_HEALTH_CHECKS please refer SAP Note 3207132 - Remove Obsolete Services from FLP Health Checks. As
per the note "You can implement this note or you can ignore this issue if the SAP Fiori launchpad and its tools are working fine"
STEP 9: VALIDATION
Add role Z_FIORI_FOUNDATION_ADMIN to a test user (This role contains role Z_FLP_ADMIN).
Test using tcode /UI2/FLP or directly via url: https://vhcals4hci.dummy.nodomain:44300/sap/bc/ui5_ui5/ui2/ushell/shells/abap/FioriLaunchpad.html
You should get screen
below:
Click on the (1) Icon on top right and select (2) App Finder, you should get screen below
Please refer to the blog below for additional checks as a verification checklist once all the above tasks are completed. This is required before we proceed further to next step.
https://blogs.sap.com/2022/04/08/sap-fiori-for-sap-s-4hana-10-health-checks-for-the-sap-fiori-launch...
STEP 10: PREPARE LIST OF BUSINESS ROLES
From Fiori app reference library identify relevant business roles for activation. We will select all roles for the sandbox but you can restrict to only the required
roles.
Select All Fiori apps for SAP S/4HANA => by Back-End Product => SAP S/4HANA
IMPORTANT TIP: In case you want to select all the Roles for certain scope items activated like BKP, 1Z3, 3QD, 1GA.... etc then click on the filter icon shown above and select the Scope Items.
(A) Select all (or alternatively you can select the roles you need), (B) Aggregate, (C) SAP S/4HANA 2021 FPS1, (D) Down Arrow, (E) Download
Click on Export list of Business Roles (419 roles for SAP S/4HANA 2023 currently) and save the list as csv file. The number of roles may be different as new roles may be added or old ones deprecated.
Split the list of roles into lists with number of roles limit around 100. Also prepare separate list for roles with presteps. So you must have at least 3-4 lists of roles that you want to use for next step considering you want to activate all roles.
TIP: In case you have selected below roles, you may find it convenient to remove the below roles and activate them separately as they need some pre-steps.
|
ROLE |
COMMENT |
|
SAP_FND_BCR_MANAGER_T SAP_HCMFAB_BCR_EMPLOYEE_T SAP_HCMFAB_BCR_MANAGER_T SAP_MDG_BCR_APPROVER_T SAP_MDG_BCR_REQUESTOR_T |
RESOLUTION: Since these roles do not follow
naming convention SAP_BR_*, as per note 3236624
activate using task |
|
SAP_BR_ADMINISTRATOR_LMD SAP_BR_BILLING_SPECIALIST_ISU SAP_BR_BUSINESS_ANALYST_IOG SAP_BR_DEFERMENT_ANALYST_IOG SAP_BR_FC_ANALYST_PROD_IOG SAP_BR_FIELD_OPERATOR_IOG SAP_BR_FORECAST_MANAGER_IOG SAP_BR_FORECAST_SPECIALIST_IOG SAP_BR_HC_ANALYST_IOG SAP_BR_MASTER_DATA_IOG SAP_BR_OPERATION_CLERK_ACM SAP_BR_PROD_DATA_SPEC_IOG SAP_BR_SETL_CLERK_LMD SAP_BR_SETTLEMENT_CLERK_ACM SAP_BR_SHIPPING_SPECIALIST_IOG SAP_BR_TERMINAL_OPERATOR_IOG SAP_BR_TRADER_ACM SAP_BR_TRANSP_SCHDLR_IOG |
Activation will be skipped with warning if Business Function/Switch is not enabled RESOLUTION: Activate Business Function as per SAP Note 3236624 - Composite SAP note: Rapid Activation for SAP Fiori in SAP S/4HANA 2022 The activation of all the business functions required for these roles take long time in the range of 16 hours |
|
SAP_BR_TRANSPRT_MNGR_LMD |
|
|
SAP_BR_BUSINESS_ANALYST_GRP |
Service: /sap/bc/ina/ina1/sap/2cccnsldtbs, /sap/bc/ina/ina1/sap/2cccnsldtcfstmt, /sap/bc/ina/ina1/sap/2cccnsldtisfoe, /sap/bc/ina/ina1/sap/2cccnsldtisnoe failed. Reason: Service not available RESOLUTION: Do not use app F6133. Ignore InA1 error in task list. |
|
SAP_BR_EMPLOYEE |
Service: UI_HCMSEARCHCOURSES 1 |
|
SAP_BR_TRANSP_MDSPEC |
Format Error. Solution pending |
TIP: In case you get typical error message like for example - Service: C_SRVCCONTRFINQUERY_2_CDS 1 failed / ICF Node: not available. For detailed analysis activate failed service manually with transaction /IWFND/MAINT_SERVICE, please follow steps as below:
Enter
tCode /n/IWFND/MAINT_SERVICE
Enter (1) Technical Service Name as C_SRVCCONTRFIN*, (2) Checkmark on Co-Deployed, (3) Click on Get Services, (4) Select the service C_SRVCCONTRFINQUERY_2_CDS and then click on (5) Add Selected Services
Click on Local Object.
TIP: You should prepare your own list of roles. I have prepared a list of roles for S/4HANA releases that is shared in the link. There are 4 files for roles that were downloaded from Fiori App Library – the second list contains roles that require presteps. All these lists are available also in a spreadsheet S4HANA2023FPS0_FioriRapidActivation_BusinessRoles.xls
The first list S4HANA2023FPS0_FioriRapidActivation_BusinessRoles_List1.txt contains 100 roles and you can activate all of them together. After you run the task list for activation, if there are errors, please rerun the same list again. If there are memory issues split the list into smaller chunks.
The second list in file has 140 roles, the third list has 149 foles that you can activate together. The fourth list has 5 roles that have to be activated using task list SAP_FIORI_FCM_CONTENT_ACTIVATION. And there are some that need Business Function/Switch to be activated. And some awaiting solution.
STEP 11: ACTIVATE FIORI CONTENT
TIP: Before scheduling Content Activation task list ensure that task list for Activate Enterprise Search from STEP 2 is completed.
Check that note is applied as per STEP 1 - SAP Note 2686456 - Fiori Setup: Content Activation for SAP Business Roles
In Work Client, enter tCode STC01 - SAP_FIORI_CONTENT_ACTIVATION
The 513 roles in SAP S4HANA 2023 FPS1 as you see below have many country specific roles like SAP_BR_AA_ACCOUNTANT_JP , etc. There are 12 roles just
with *_JP. So don't try to activate all roles as they are country specific and industry specific. We strongly recommend to customers to do a conscious decision
about the role scope to be activated.
In the first task, (A) checkmark first task, (B) Click on Parameter and paste the list into the box that pops up, click on OK (Continue) at the bottom of the Define Business Roles” dialog window, and then click on (C) execute.
After clicking OK for the first task, if there are errors as below, please remove the roles that have no SAP Business Role and move the others into list that requires presteps and handle them separately.
Please see below for triggering activation of 513 roles:
Please note that there are 5 roles which are to be activated using task list STC01 - SAP_FIORI_FCM_CONTENT_ACTIVATION
TIP NO 1: Run the task list above in background (use menu option). While the task list is running, please check dumps in ST22 in separate session.
TIP NO 2: If all ODATA/SICF are activated for the first time, each group of about 150 roles takes about one hour +. But if you get an error and then you reactivate the same list it should be done in few minutes. If some ODATA services are already activated the time required should be reduced accordingly.
TIP NO 3: TIME SAVING TECHNIQUE - Once you have the list of roles, you can split the roles into multiple lists like say if you have 200 roles, split them into 2 sets of 100 roles. You can then create 2 separate sessions and run the task list. Keeping the number of roles in these 2 sessions unequal will help to know the session, like keep 98 roles in first session and 102 helps to distinguish them. I had to increase the parameter abap/shared_objects_size_MB = 512 to 768 to run parallel session. Alternatively you can set the automatic memory parameter PHYS_MEMSIZE.
TIP NO 4: After activating a role like for example SAP_BR_AP_MANAGER, if the ODATA/SICF are already activated, the delta
role SAP_BR_AP_MANAGER_US takes much shorter time as some services are already activated. So as a result your subsequent lists will take lesser time
than earlier ones.
TIP NO 5: If you get error first time, please try with same list second time and some errors may go away. Like the below list of errors reduced to no errors for second run. One of the reasons for this is - the service activation is a generation and can finish successfully later on after the logs show error. So on retry the activation finished successfully.
TIP NO 6: For the subsequent activation run, if you get error Not enough shared memory exists, you can clear the shared memry in tCode SHMM. If you dont have access to SHMM or if there is possibility of impacting other users and processes, easiest way is to logout and login. If this does not work, double the parameter abap/shared_objects_size_MB = 512 as per Note 2766677 - Not enough shared objects memory exists, will require SAP bounce.
At the end of activation you should see result as below:
STEP 12: POST ACTIVATION
Please ensure that web dispatcher is setup correctly and working as it will be required before users can use the applications by logging in through the web dispatcher.
TIP: As a Post Activation step you can revert back Memory Parameters that were temporarily increased for activation. COMPONENT FOR INCIDENTS:
You can open OSS messages using component BC-INS-TC-CNT
Please mention the SAP Fiori UI software components. The UI software component can be found in Fiori App Library. Example
for RFM_MANAGE_PRODUCT_LISTING_SRV the component is LO-RFM-MD-LST. Please see steps below:
LANDSCAPE CONSIDERATIONS:
There is a transport capability added to the Fiori launchpad content manager task list SAP_FIORI_FCM_CONTENT_ACTIVATION
Please refer the blog for more information: SAP Fiori for SAP S/4HANA – New Rapid Content Activation on S/4HANA 1909, 1809 & 1709 – Part 4 – Cus... You can also refer the Fiori Launchpad Content Manager as per SAP Help Portal
below: https://help.sap.com/viewer/d4650bf68a9f4f67a1fda673f09926a9/latest/en-US/c2f3f66fc2e04f3ea5ede6bcd4... OTHER REFERENCES:
For a more detailed description of all tasks please refer to the excellent blogs
Fiori for S/4HANA – New Rapid Content Activation on S/4HANA 1809 & 1709 – Part 1 – Overview
Fiori for S/4HANA – New Rapid Content Activation on S/4HANA 1809 & 1709 – Part 2 – Prerequisites & F...
Fiori for S/4HANA – New Rapid Content Activation on S/4HANA 1809 & 1709 – Part 3 Scope & Execute Con...
Fiori for S/4HANA – New Rapid Content Activation on S/4HANA 1809 & 1709 – Part 4 – Customize & Trans...
SAP Fiori for SAP S/4HANA – SAP Fiori Rapid Activation: Transport from Development to Production sys...
SAP Fiori for SAP S/4HANA – Transition from Standalone to Embedded Deployment in SAP S/4HANA
UI Technology Guide
Note 2902673 - Rapid Activation for SAP Fiori in SAP S/4HANA - Overview <=Contains all release specific notes
Comments
Post a Comment