Technical Articles
New Installation of S/4HANA 1909 FPS0- 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.
Please find other blogs as follows at S/4HANA SQUARE ONE
S/4HANA SQUARE ONE |
| NEW INSTALLATION | PART1 – MP | PART2 – Installation |
PART3 – BP Activation |
PART4 – Fiori Activation | PART5 – DATA MIGRATION |
| S/4HANA 1909 | fps2 fps1 fps0 | fps2 fps1 fps0 | fps2 fps1 fps0 | fps2 fps1 fps0 | fps0 |
| S/4HANA 1809 | fps2 fps1 fps0 | fps2 fps1 fps0 | fps2 fps1 fps0 | fps2 fps1 fps0 | |
| S/4HANA 1709 |
fps2 fps1 fps0 | fps2 fps1 fps0 | fps2 fps1 fps0 |
| SYSTEM CONVERSION | t2 – RC | t3 – MP | t4 – SIC |
t5 – CCM | t6 – SUM |
| S/4HANA 1909 | rc2 | link | link | link | prepare EHP6/mss |
| S/4HANA 1809 |
link | link | link | EHP7/hdb EHP6/db6 EHP5/ora EHP6/mss |
| SAP S/4HANA ON-PREM APPLIANCE | INSTALL USING MEDIA | ACTIVATE FROM CAL |
| S/4HANA 1909 | link – custom link – standard | link |
| SAP S/4HANA CERTIFICATION | |
| S/4HANA Certification Exams through SAP Certification Hub | link |
This is the Video for this blog (Voice to be added):
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 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 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.
Select the Fiori tile Plan for SAP S/4HANA
In the next screen,choose Install a new SAP S/4HANA system. Here you can click on the link for the SAP S/4HANA Installation Guide for the documentation and click on Next.
In the next screen enter SID = S4H; select Target Version = SAP S/4HANA 1909; Target Stack = Initial Shipment Stack. The componnets SAP Predictive integrator, SAP HANA Rules Framework and selected by default. 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 Human Capital Management, Master Data Governance and 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.
In the next screen click on Next.
Click on NON-ABAP and unselect the language files that are not required.
TIP: The files are only selected above for download. Later on during installation, you have to define 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_2000609102_20190130_.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 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 in download folder:
SWPM20SP04_1-80003424.SAR – Latest version of Software Provisioning Manager
SUM20SP06_1-80002456.SAR – Latest version of Software Update Manager
HANA DATABASE:
In case you need to install HANA database please download the files below from
Software Downloads => SUPPORT PACKAGES AND PATCHES => SAP HANA PLATFORM EDITION => SAP HANA DATABASE 2.0
TIP: Please do not select HANA 2.0 SPS2 rev 42. Instead select rev 44. Refer 2655761 – SAP S/4HANA – restrictions and recommendations regarding specific revisions of SAP HANA database for use in SAP S/4HANA
IMDB_SERVER20_044_0-80002031.SAR – Latst version of HANA Database (Linux x86_64 64bit)
You also need to download latest version of the HANA client from Software Downloads => SUPPORT PACKAGES AND PATCHES => SAP HANA PLATFORM EDITION => SAP HANA CLIENT 2.0
IMDB_CLIENT20_004_162-80002082.SAR – Latst version of HANA Client (Linux x86_64 64bit)
If you want to install LiveCache you will require the HANA database LCAPPS plugin from Software Downloads => SUPPORT PACKAGES AND PATCHES => SAP HANA PLATFORM EDIT 1.0 => HANA LCAPPS => SAP HANA LCAPPS 1.00
IMDB_LCAPPS_2044_0-20010426.SAR – Latest version of 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 below from SAP Note 2776548 – SAP S/4HANA 1909 – SAP S/4HANA 1909 FP-Stack 00 (09/2019) SAP Best Practices Content activation note
50151283.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
Mahesh Sardesai
Product Expert – S/4HANA
I tried to do exactly as this guide but i am running into an error.
Any help will be appreciated.
Hello Rachel,
While generating maintenance planner and choosing fiori deployment, only UI for S/4HANA works fine. If you select other component in SAP Fiori then you will get error and you won't be able to generate maintenance planner.
UI for HCM: OCS package SAPK-200AGINUIX01CA1 does not match the current software component vector
UI for MDG: OCS package SAPK-200AGINUIMDG001 does not match the current software component vector
UI for TRV: OCS package SAPK-300AGINUITRV001 does not match the current software component vector
I feel SAP should remove this option in maintenance planner (to avoid confusion and questions) if it is not compatible with SAP Fiori for S/4HANA 1909.
Kindly just select UI for S/4HANA when choosing fiori deployment and proceed further to generate xml.
Regards,
Dennis
Thank you for this tip. You have saved me some headache.
Hi Dennis,
Thanks for your comments.
I think it may still work using same options as before.The items marked (obsolete) should not be selected. I tried and it works.
There was a locking issue yesterday that has bee acknowledged and resolved. I feel same options should work, but let us see if this is a scenario that also needs a fix.
Hello Mahesh,
Thank you for checking on the issue. But I have generated my xml on 09/19/2019, at that time also I faced the same issue even after deselecting obsolete component. I have tried generating xml yesterday before commenting here, but was facing the same issue. Even today as you have mentioned that it should work, but I'm getting the same error. Below are screenshots.
Regards,
Dennis
please send your S-user ID to my email address <removed> simulate the issue. I don’t need password just the id.
Hello Mahesh,
I have sent you my S-User ID to your email address. Thank you for your effort.
Regards,
Dennis Padia.
Hi Dennis,
yes I see the error. Sorry for inconvenience. I have reported it internally.
Hi rachel,
There was an issue yesterday and I had reported it. The root cause was that a locked ACP has created attribute change package.
Please retry the same options you did before and let me know if there is still an issue.
Its not working for me... Checked today.
https://blogs.sap.com/wp-content/uploads/2019/09/5-4.jpg
Exact error coming up.
I am having the same issue. I also cleared my browser cookies and redid the steps from MP. And i am facing the same issue.
I have also checked 2 other ID. and same issue.
I have successfully installed the 1909 using @Dennis Padia suggested method.
Hi,
I have discussed internally and it seems that that TRV is still having issues. This should be resolved in a few hours.
Hi Mehesh,
With S/4HANA 1909, is FES on hub deployment no longer supported ? I was told by SAP to use co-deployed in maintenance planner instead of hub deployment they referred me to SAP Note - 2750164 - SAP S/4HANA FOUNDATION 1909: Release Information Note.
Our preference is to install central hub deployment for Fiori Front-end server, what are my options if I am installing S/4HANA 1909
Thanks
Hi Lindy,
The reason is - Fiori Front end components are tightly coupled with Backend meaning if you have Fiori Front End 6 it will work with 1909 but is not compatible with backend 1809 meaning it is not backward compatible. For this reason it is better to install embedded. Please read more info here:
SAP Fiori Deployment Options and Recommendations
This issue still occurs .
Hi
I am also facing the same issue even if I follow the suggestion above. I get the error - OCS package SAPK-700AGINUIAPFI70 does not match the current software
Please advise.
Hi Lindy,
Some have reported the issue when they select Fiori central hub deployment. The recommendation is “Co-deployed with Backend” option in the Maintenance Planner, where this issue will not come up.
Please refer guide SAP Fiori Deployment Options and Recommendations
Thanks
Hey Mahesh - We are working on a Greenfield S/4 HANA implementation, and have installed a Dev enviornment with S/4 HANA 1809. What is your recommendation should we install 1909 FPS0 now, or wait for a couple weeks for the next FPS release.
Thanks and Regards,
Samta.
Hi Samta,
Your decision would depend on how much work is already done in the discover and explore phase on 1809. You have to also take into consideration the advantages of 1909 as some new features are released like direct data migration using individual objects from ERP to S/4HANA 1909 using data migration.
Some companies like to be one release back by the time they golive so any fixes to the software are already available.
Nice document thanks for sharing..
Thank you
Hi Mahesh,
Thanks a lot for sharing this document. It indeed is very helpfull considering the fact that 1909 is released very recently and there is very less documentation available.
I am also installing the S/4HANA 1909 and facing the same issue in downloading the stack files(Maitenance Planner –> Plan for S/4HANA) . Where as in the Maintenance planner –> Plan a new system , I don’t see this error. But there I don’t get the option to select the "Frontend Server Selection". Could you please help on how shall we proceed.
We need to install 1909 mainly for EWM functionality. Therefore would you recommend to install the Frontend Fiori along with the S/4HANA server.
Also for EWM do I need to select any other Target Product Instance like Basis Appl or BI Content Extension or only SAP Predicitve Integrator and SAP HANA Rules Framework are sufficient for EWA functionality which are selected by default.
Thanks a lot once again and looking forward for your response.
—
With Regards,
Apurve
Hi Apurve,
Sorry for delayed reply. If you select the Explore systems tile and then choose system then you will not get the FrontEnd Server selection. Please choose the "Plan for S/4HANA" tile and then choose the options.
Yes it is recommended to install embedded FrontEnd Server along with S/4HANA srever for EWM functionality. Please refer SAP Note 2668150 – SAP S/4HANA 1809: Release information and restrictions for EWM in SAP S/4HANA - Getting Started Guide – Basic Settings for SAP EWM in SAP S/4HANA - BasicSettings_EWMinS4_V01.pdf.
Hello Mahesh,
Looking to add a S4 1909 container to a S4 1610 installed appliance (HANA DB 2.0.41). Understanding that HANA 2.0.44 is min req'd, prior to this point I understood that in a MDC s/w updates were across database containers (2.0.41 -> 2.0.44 for the database) then add the new container. Based on this blog, it seems that is not the case (as if I may have multiple patch levels of HDB if the h/w can sustain it?) - perhaps I misunderstand. The requirement is that the 2 versions of SAP S4 co-exist in the HDB for a short time before the cutover, removing the older S4 tenant after the rollover. Once the HDB requirements are determined, it seems to a matter of directing the application server to the proper container.
Also, I expect that in MP, the installation is built as "new" - and to use your example, would be named HDB, as opposed to HB0 (instance 00).
Apologies on the basic questions, but an abundance of caution when dealing with an active instance.
(The primary container will be in use during the installation process.)
Thank you in advance & Regards
Angela
Hi Angela,
Sorry for delayed reply. For installing 1909 you have to upgrade database to min rev 44. You cannot have multiple patch levels of HDB for different containers.
The database SID of HDB instance 02 was chosen for this installation and you can provide your own name HB0 and instance 00. But in this case you may have to change application instance with a different number if it is on same server.
-Mahesh
Hello Mahesh,
As I expected, I misunderstood what I read here. Overall, a very useful posting – good information for our migration.
Angela
Hello.
Im glad I found this forum. Currently installing S4HANA1909 + Fiori 6.0 Embenbed + HANA2.0 SP44.
I just jumped from SWPM (97%) to SUM and at 9% i get the error:
I checked the SAPK-300AGINUITRV001 Package Conditions and its ok with what I have in the new
system: ABAP 75E / Basis 754 / GWFND 754
What could be the error if everything is OK??
Log:
ETN245 The following import prerequisites of OCS Package “SAPK-300AGINUITRV001” have not been met:
3 ETN264 In the (alternatively) Requirement set “01”:
3WETN491 Required software component “SAP_ABA” rel.”740″ is not installed
3WETN491 Required software component “SAP_ABA” rel.”750″ is not installed
3WETN491 Required software component “SAP_ABA” rel.”751″ is not installed
3WETN491 Required software component “SAP_ABA” rel.”752″ is not installed
3WETN491 Required software component “SAP_ABA” rel.”75B” is not installed
3WETN491 Required software component “SAP_ABA” rel.”75C” is not installed
3WETN491 Required software component “SAP_ABA” rel.”75D” is not installed
3WETN491 Required software component “SAP_BASIS” rel.”740″ is not installed
3WETN491 Required software component “SAP_BASIS” rel.”750″ is not installed
3WETN491 Required software component “SAP_BASIS” rel.”751″ is not installed
3WETN491 Required software component “SAP_BASIS” rel.”752″ is not installed
3WETN491 Required software component “SAP_BASIS” rel.”753″ is not installed
3WETN492 Required Add-On component “SAP_GWFND” rel.”740″ is not installed
3WETN492 Required Add-On component “SAP_GWFND” rel.”750″ is not installed
3WETN492 Required Add-On component “SAP_GWFND” rel.”751″ is not installed
3WETN492 Required Add-On component “SAP_GWFND” rel.”752″ is not installed
3WETN492 Required Add-On component “SAP_GWFND” rel.”753″ is not installed
2WETN543 OCS package “SAPK-300AGINUITRV001” does not match the current software component vector
Dear Oswaldo,
It is difficult to provide a solution based on the details provided. Proper analysis require access to system from backend and to check the maintenance planner transaction and compare with the system.
Similar issue has been reported earlier as per comments. IN one case it was resolved by updating R3trans and tp to latest release. It's good to create a OSS ticket with SAP to pinpoiint the error since you are in the middle of SUM tool processing.
Hi Osvaldo,
What could be the error if everything is OK??
Most of the scenarios ACP file will cause "OCS package “SAPK-*” does not match the current software component vector" this error. So in this case you can try to add the ACP "UITRV001==300" file and retry.
Note: If you're getting this error in "EHP_INCLUSION" kindly make sure all the required SAR files are available in download directory.
Regards,
Rameshkumar Ramasamy
Dear Mahesh,
which is default user and password while first login in gui s/4hana 1909.
Hi Malik,
You should login with user SAP* or DDIC using the master password you specified when running SWPM.