Your S/4HANA environment – Part 3 – Best Practices Content Activation
Today we will take a closer look on S/4HANA Content Activation. It’s the third part of the guide, so I highly encourage you to read two previous posts:
If you want to follow today’s post it is very important that you have already prepared client in S/4HANA system (detailed guide described in Part 2).
Just before starting I would like to share two more links:
SAP Notes implementation
Our first activity today is to implement necessary notes referred in Release Information Note. Some of the notes may require additional manual steps which we have to execute.
To avoid errors and increase activation speed we disable Activation Links in BC Sets. Enter t-code SCPR20, go to System Settings and select Do Not Create.
Output management for S/4HANA
We need to import three XML files from note 2248229 in transaction BRF+.
Setting up S/4HANA Attachment Services
Enter t-code OAC0 and create new entry:
In SPRO go to Cross Application Components -> Document Management -> Additional Settings – Simplification -> Attachment Service – Storage Repository Activation and create new entry:
Modify record in table SDOKPHCL for PH_CLASS = SOFFPHIO by setting the flag in CAT_MAINT column.
Go to t-code SKPR08 and change the category for SOFFPHIO:
And finally maintain entries in TSOPE through SM30:
Importing the latest version of S/4HANA Content
In the past Best Practices content were delivered through SAP Portal as two ZIP files: Solution file and Data files. Nowadays it looks differently – SAP releases transport request valid for particular SPS, which has to be imported into system. Links to transport are included in S/4HANA Content Activation Note respective to release. After downloading and unpacking go to STMS and import them to your system:
Missing entries in TM160M
Due to an error in table /FTI/TWHITEL01 during client copy one of the tables was not replicated. We need to follow note 2257369 and insert missing entries. Firstly create and execute report Z160MIS and then use /FTI/CL_COPY to copy the missing entries.
Now we can check that table TM160M has data:
Create users for activation
To activate S/4HANA we need three users:
a) Two technical users: SAP_SYSTEM and SAP_LMADM with SAP_ALL profile
b) One dialog user with SAP_ALL profile. Please fill the Defaults tab according to the following screen:
Maintain profile parameters
Another activity we need to perform is to adjust profile parameters to avoid memory dumps.
Enable GUI scripting
The last step before entering Solution Builder is to enable GUI Scripting:
Finally we are ready to start S/4HANA Content Activation. Enter Solution Builder with transaction code /n/SMB/BBI
At the moment there is no Solution defined. In order to create one, we need to import Solution and Installation files:
Choose solution you would like to activate. During this guide we are going to work on US version.
Then import Installation Data – when all files are uploaded we get confirmation:
During the installation we didn’t implement any additional language. In our system only English and German are available, therefore we need to remove all activation content for languages that are not part of our system. Go to Building Block Builder and modify language key for V_TVAS_V_TVAS_BJF.TXT and SMBA0_V_TAUUM_CLI_J01_OP.TXT (IT -> I; LT -> X; DE -> D; EN -> E; FR ->F).
Run report /SMB/REMOVE_NOTINST_LANG_IMG and select your solution.
During next step we will run Implementation Assistant and execute S/4HANA Content Activation. It’s excellent moment to do a full system backup.
Go to Solution Builder and follow to Implementation Assistant.
To start activation, click SHIFT+F7.
After confirming the dialog box, activation begins!
Don’t worry if you run into errors. Some of them are expected. Bellow I will try to show issues I encountered and how did I solve them. If you can’t find solution bellow, you can also check Mahesh’s blog, where he also deals with content activation.
1) Checking VERTEX integration
We didn’t configure VERTEX integration; therefore, we need to perform manual step. Follow the guide attached to note 2247743 – Activation guidance without VERTEX integration.
2) Define Release Procedure for Purchase Orders – Set Criterias (/SMB99/CL20N_PO_O001_J01)
Restart the activation. Error won’t appear again.
3) Create Material Master – Work Scheduling View (/SMB99/MM01_ALL_VIEWS_O015_J01)
When the activation process is finished we get confirmation:
And that’s all for today. I hope you like it.
Next week we are going to finish setup of Fiori Apps and we will do some preliminary system checks.