PPP Initial Installation / Import
Problem
How to install and deploy the sophisTex PPM Process Package (PPP) in an SAP environment, including options for transport import (frontend/backend separated or embedded), SAINT-based add-on installation, and deployment on SAP BTP.
Environment
PPP Installation and Import Procedure
Solution
Option 1: Import via Transport
-
Log in to the target system where you want to import:
- In case of a separated Front- and Backend System, these steps need to be done on both systems with the according file. The Transport Files for PPP are always separated into one Front- and one Backend Transport
- In case of a co-deployed (embedded) System, both Front- and Backend Transport needs to be imported on the same system
- For further notes, refer to Importing Releases: Best Practices
-
Start transaction STMS
-
On the STMS start screen, click Overview → Imports (or press F5 / click the truck icon “Imports”)
-
Double-click the system whose import queue you want to use → You now see the import queue (list of waiting transports)
-
If the transport is not already there automatically:
-
Go to menu Extras → Other requests → Add (or Request → Add request to import buffer)
-
In the popup “Add transport request to import queue”:
- Enter the transport number
- Optional: Enter target client if required
- Confirm with Enter/OK. → The transport now appears in the queue (refresh with F5 if needed)
-
-
Select (click) the transport in the list
-
Click Import
-
In the import dialog:
- Choose options (e.g. “Background” for unattended import, “Synchronous” for immediate)
- Set unconditional modes if needed
- Start the import (OK).
-
Wait until the import finishes
-
In case this was the first installation of PPP, perform the Post Installation Activities
-
Perform the Post Update Activities
Alternative Option 2: Installation via SAINT
-
Log in to client 000 (very important for SAINT)
-
Start transaction SAINT
-
Load the installation package
- Click the button or menu: Installation Package → From Application Server (recommended if the AAK package was uploaded to the server’s transport directory by basis team) OR From Frontend (if you have the .SAR or package file locally on your PC – less common for large packages)
- In the file dialog or server directory browser, locate and select the sophisTex PPM Process Package file (it has a name like /STX/SOL_PPP_
.SAR or similar – the exact name is provided by sophisTex support ) - Confirm and load it
-
Select and review the package
- The loaded package appears in the list
- Double-click or select it to view details: version, components, dependencies, target release compatibility
- Check for any warnings (e.g., required support packages, conflicts)
- If everything looks good, proceed
-
Start the installation
-
Click Continue or Install
-
Follow the installation wizard:
- Confirm settings (e.g., target client = 000 initially, but it deploys to relevant clients)
- Choose import options (usually default: synchronous or background)
- Start the process – it can take 10–60 minutes depending on system size and package complexity
-
Monitor progress in the status bar and logs
-
If errors occur (e.g., missing prerequisites), note them and resolve (e.g., import required notes via SNOTE first)
-
-
After completion
- SAINT shows “Installation finished” (green status)
- In case this was the first installation of PPP, perform the Post Installation Activities
- Perform the Post Update Activities
Optional in Addition: Deployment on SAP BTP
-
Log in to SAP Build Work Zone
- Access the service via your SAP BTP subaccount → Services → SAP Build Work Zone.
- Ensure you are using an admin user with roles for content management and site editing.
-
Set up trust between UAA and IAS
-
Prerequisite: This must be completed before users can access content.
-
In BTP Cockpit → Security → Trust Configuration:
- Establish federation/trust to your SAP Identity Authentication Service (IAS) tenant.
- Follow the SAP standard guide: Add IAS as the identity provider, configure SAML assertions, and map groups/roles.
-
Test: Verify that users can successfully log in via IAS to the Build Work Zone.
-
-
Configure BTP Destinations
-
Before deploying the application, ensure the connectivity layer is defined so the MTA can bind correctly to existing resources or reference them.
-
In BTP Cockpit → Connectivity → Destinations, create or verify the destination for the PPP backend.
-
Key Settings:
- Name: Use the exact name provided by STX
- Type: HTTP
- Proxy Type: Internet (or On-Premise via Cloud Connector)
-
Additional Properties: You must add these to ensure the Work Zone can “see” the app data:
HTML5.DynamicDestination=trueWebIDEEnabled=true
-
-
Deploy the PPP application (MTAR)
- Ensure the Cloud Foundry CLI and MultiApps plugin are installed (
cf deployavailable). - Log in and target the correct org/space using
cf loginandcf target. - Deploy the provided artifact:
cf deploy <your-file>.mtar. - Wait for a successful deployment confirmation.
- Ensure the Cloud Foundry CLI and MultiApps plugin are installed (
-
Import or Update PPP Content Package
-
In Build Work Zone, navigate to the Content Manager.
- If this is a first-time installation:
- Create a new Content Package and upload the provided
package.zip.
-
If the PPP Content Package already exists:
- Select the existing package and use the Update Content button to upload the newer
package.zip.
- Select the existing package and use the Update Content button to upload the newer
-
Note: This process automatically configures the applications, catalogs, and launchpad groups based on the internal configuration.
-
-
Finalize Role Assignments and Site Integration
-
Navigate to Site Settings:
- Access the Site Directory, select your site, and go to Site Settings → Assignments.
- Under the Content Channels tab, ensure the PPP Content Package is enabled/assigned to the site.
-
Assign Roles to Site:
- In the Roles tab of the Site Settings, assign the imported STX PPP roles to the site to authorize visibility.
-
User Authorization & IdP Mapping:
-
Access is governed by the user’s assigned roles in the Identity Provider (IAS).
-
Map your IdP Groups to the corresponding BTP Role Collections to ensure users receive roles automatically.
-
The following roles are defined within the package:
- Admin:
stx.ppp.role.admin - Dashboard:
stx.ppp.role.dashboard - Dailys:
stx.ppp.role.dailys - Resources:
stx.ppp.role.resources - Creation:
stx.ppp.role.creation
- Admin:
-
-
-
System Initialization
- If this is the initial installation of PPP, perform the Post Installation Activities.
- Perform the Post Update Activities if applicable.
-
Test access
- Publish the site and log in as a test user.
- Open the Launchpad and verify that tiles appear and launch correctly.
- Confirm functionality across desktop, tablet, and mobile devices.
See Also
- Post Installation Activities
- Post Update Activities
- Transport Files Cannot Be Imported And End With “.txt”
- Importing Releases: Best Practices
Keywords
Transport Import STMS, SAINT, BTP Deployment