Prerequisites and assumptions

This section covers how to install PreBilt for EWM using Mendix, Movilizer, Neptune, or PreBilt Standalone Edition (PSE). It’s designed for SAP technical resources familiar with SAP Basis/development and some non-SAP basics.

What you need to do before installation

Determine if you'll be installing just the base framework or including additional TCTM services, apps, or plugins.
Ensure you know which platform you are using for installation: Neptune or PreBilt Standalone Edition (PSE).

Platform-specific requirements

There are no specific requirements for an installation on PSE.

User authorisations

You will need the following transaction access and authorisations to use PreBilt for EWM.

Transactions:

/TCTM/*

Authorisations:

/TCTM/*

Hardware requirements

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.

PreviousMinimum requirements NextBackend installation

Last updated 1 month ago

Was this helpful?

Hardware requirements

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.