Prerequisites and assumptions

Software

Before beginning the installation of PreBilt for IM/WM/StRM, it is important to consider the following. One or more SAP transport packages will typically be provided, which must be imported into the SAP system in the specified sequence by a suitable resource. These transport packages contain all the necessary objects and content required to deliver the solution, including supporting SAP transactions and configuration options.

Once the installation is complete, additional configuration steps are required to set up the system for operational readiness. It is also worth noting that all objects delivered through these transports are developed under the namespace /TCTM/.

Required authorisations

The following authorisations are required to complete the installation and configuration of PreBilt in the development environment. These transactions will ideally be available to the TCT resource for follow up and troubleshooting, but if any access should be restricted this will need discussing with the assigned TCT resources and a segregation of duties agreed.

Transaction	Description	Systems
/TCTM/SRV_LOG_CTRL	TCT Mobility: Log & Trace Control	All
/TCTM/SRV_TRACE_RPT	TCT Mobility: Display Trace Data	All
/TCTM/WM_CFG	TCTM: WM Configuration	All
/TCTM/WM_CFG_D	TCTM: WM Configuration Data	All
/TCTM/SRV_LOCKS	TCTM: Service Object Assignments	All
/TCTM/WM_LICENSE	TCTM: WM License Manager	All
CG3Z	Add transport files to SAP directories	All (unless SAP directories are shared across systems)
STMS	Add external transports to transport queue	All
AL11	Check SAP transport directory path	All
LRFMD	Menu assignment for RF Users	All
SICF	Display and activation of services for platform connections	All
SM30	Maintain table views	All
SCPR3	Uploading of BC sets to for app pre-configuration	Dev
SCPR20	Activation of BC Sets	Dev
SE03	Adjust namespaces	Dev
SE11	ABAP dictionary display	Dev
SE24	Class builder	Dev
SE38	Needed to run some setup programs that do not have transaction codes	Dev
SE80	Object navigator	Dev
SMICM	Check port set up and run traces if required	All
STRUST	Trust manager	All

To complete functional unit testing, appropriate business roles will also be required.

Installing Neptune

If you are installing PreBilt on Neptune, the instructions below can be used to complete the installation of Netpune.

If Neptune Planet 8 is not already installed in the SAP landscape, the files needed to complete the installation will be supplied by The Config Team or the Neptune Partner. These files will be:

1. Neptune-DXP-SAP-6.0

2. Neptune-DXP-SAP-6.0-SP18

3. SAPUI5–v.1.71.36

4. Neptune-DXP-6.0.019-Hotfix-21-15919-Licenced-users[CS1]

Any additional installation guides and certificates needed for the install are included in the zip files provided. The above installation package includes 2 temporary licenses, these will be replaced with the permanent Neptune licenses, which will be provided by Neptune, when the purchase order for the licenses has been received by Neptune.

Note

Neptune installation should be completed in the normal customising client or applicable client in DEV, QA or PRD. This section needs repeating in each system as it is not transportable.

For implementing the first file, follow the instructions in ‘Neptune-DXP-SAP-6.0-Installation-Guide.pdf’ in ‘Neptune DXP-SAP-6.0’ folder, following the below notes in parallel.

Before completing the post-installation activities, do the following:

• Install the transport in ‘Neptune-DXP-SAP-6.0-SP18’ following the import process in ‘Neptune-DXP-SAP-6.0-Installation-Guide.pdf’ that was used for the first file.

• Install the transport in ‘SAPUI5–v.1.71.36’ following the import process in ‘Neptune-DXP-SAP-6.0-Installation-Guide.pdf’ that was used for the first file.

• Install the transport in ‘Neptune-DXP-6.0.019-Hotfix-21-15919-Licenced-users’ following the import process in ‘Neptune-DXP-SAP-6.0-Installation-Guide.pdf’ that was used for the first file.

On page 7, step 3 of the PDF, when activating the Neptune Service, select 'Yes' (with sub levels), so that all the levels are automatically activated.

On page 10, step 4 of the PDF, PWA apps aren’t applicable for PreBilt so this step can be skipped.

On page 10, step 5 of the PDF, rest APIs aren’t applicable for PreBilt so this step can be skipped.

On page 10, step 6 of the PDF, start the transaction /NEPTUNE/DESIGNER, to create the Neptune URL for the relevant SAP client.

On page 11, step 7 of the PDF, a standard Neptune Developer role is provided in a transport which allows Neptune Cockpit setup and in addition there are other roles defined in an additional transport if required.

On page 11, step 8 of the PDF, run the program in SE38.

On page 12, step 12 of the PDF, load the Neptune certificate.

On page 13, step 13.1 of the PDF, this will be handled separately by the TCT Functional Consultant or Neptune Partner.

Set up lock handling

Open SAP transaction SM62, select 'Goto' -> 'Background Events tab' -> 'New'.

Enter the following details:

• Event: NEPTUNE_LOCK

• Description: Neptune Lock Handler

Next, set up a background job.

• Open SAP transaction SE38, enter program /NEPTUNE/HANDLER_LOCKING and click 'Execute'.

• Enter the time in seconds between lock requests checks. The recommended default value should be set to 2.

• Enter name of background user (mandatory). Note - this user name must be the same as the user running the background job.

• Enter time in minutes to automatically release locks. Leave blank to disable automatic release of locks. The recommended default value should be set to 180.

• Click on 'Save' and create the variant with variant name ‘DEFAULT’.

• Click 'Save' again in order to save the variant.

• Open SAP transaction SM36 and enter job name NEPTUNE_LOCK_HANDLER and press Enter. The job will only have one step with the following settings:

  • User: Username that will lock/unlock resources on each request. This username will be the one that owns the locks on behalf of the requester.

  • ABAP Program Name: /NEPTUNE/HANDLER_LOCKING

  • Variant: DEFAULT

• Click on 'Save'.

• Finally, set the Start condition for the job. Click on 'Start condition'.

• Click on 'After event' and enter event NEPTUNE_LOCK. 'Periodic job' must be checked.

• Click on 'Save' and the job will be ready.

Hardware

When dealing with PreBilt on mobile devices and computers your TCT project team will need to receive the following information from you:

• Hardware Specifications Provide details for each device, including:

  • Manufacturer

  • Model number

  • Base Android version (minimum requirement)

• Mobile Device Management (MDM) Share details of any MDM software in use.

• Software Installation We will supply software packages (e.g., APK files) for both QA and Production environments. You will be responsible for installing these on your mobile devices.

• Network Access Devices must be able to connect to your SAP systems. This includes resolving URL paths mapped in ICF subnodes.

• Scanner Configuration Devices must be configured to meet scanning requirements. Typically, this includes:

  • Enabling AIM Code Symbology with the appropriate scan wedge prefix

  • Activating “Scan & Tab” functionality as a suffix

While we are not specialists in mobile hardware, we will work with your device provider and project team to help resolve connectivity or configuration issues.