SAP Extended Warehouse Management provides the Radio Frequency Framework for executing warehouse activities through RF scanners and mobile devices. The framework allows organisations to customise RF screens, create customer-specific menu structures, define logical transactions, control navigation and adapt screen layouts for different presentation devices

In this blog, we will configure a custom RF functionality consisting of four screens:

All four steps will be controlled through one custom logical transaction:

Logical Transaction: ZFUNC01

Business Requirement

Assume that the warehouse requires a custom RF process for HU verification.

The warehouse operator must:

• Scan a handling unit.
• Verify product, quantity and bin information.
• Enter a verification decision.
• Review the entered details and submit the transaction.

Sample Test Data

The operator scans or enters the HU number.

The PAI logic should:

• Validate whether the HU exists.
• Check whether the HU belongs to the logged-on warehouse.
• Read the product, quantity and current-bin information.
• Return an error if the HU is invalid or locked.
• Navigate to ZCUS02 after successful validation.

Screen 2: Verify HU Details

Logical Step: ZCUS02
Screen Number: 9001

Suggested display:

Most of these fields should be output-only because they are populated by the application logic.

The screen can allow the operator to verify the data before proceeding.

Screen 3: Enter Verification Decision

Logical Step: ZCUS03
Screen Number: 9002

Suggested fields:

The PAI function should:

• Validate the entered decision.
• Make the reason code mandatory for rejection.
• Store the entered values in the global RF application structure.
• Navigate to the review screen.

Screen 4: Review and Submit

Logical Step: ZCUS04
Screen Number: 9003

Suggested display:

When the operator selects Submit, the system should:

• Perform final validation.
• Update the required custom or standard EWM object.
• Save the transaction.
• Issue a success message.
• Clear the transaction data.
• Return to Screen 1 or the RF menu.

2. Understanding PBO and PAI

PBO and PAI are often confused with foreground and background processing. They are related concepts, but they are not the same.

PBO: Process Before Output

PBO runs before the screen is displayed.

Typical PBO responsibilities include:

• Setting the screen title.
• Reading and displaying values.
• Filling output fields.
• Clearing fields during initialisation.
• Enabling or disabling input fields.
• Preparing labels and screen attributes.

Example function module :Z_RF_CUS01_PBO

PAI: Process After Input

PAI runs after the user enters data or selects a function.

Typical PAI responsibilities include:

• Validating scanned values.
• Reacting to Enter or a pushbutton.
• Updating the application structure.
• Saving business data.
• Determining the next logical step.
• Raising validation or error messages.

Example function module: Z_RF_CUS01_PAI

PBO/PAI Versus Foreground/Background

These concepts should not be treated as interchangeable.

Standard function codes such as ENTER and BACKF can be reused where suitable.

Check the function-code field length available in your system before finalising the names. For example, ZSUBM may be safer than a longer name such as ZSUBMIT.

7. Define Function Code Texts

Defining a function code does not automatically create a visible button label. The text must be maintained separately.

SPRO → SAP Reference IMG → Extended Warehouse Management → Mobile Data Entry → Radio Frequency (RF) Framework → Define Steps in Logical Transactions → Define Function Code Texts

Example:

8. Define the Function Code Profile

The function code profile determines which buttons are available on each screen and where they appear.

SPRO→ SAP Reference IMG→ Extended Warehouse Management→ Mobile Data Entry→ Radio Frequency (RF) Framework→ Define Steps in Logical Transactions→ Define Function Code Profile

Example:

Each pushbutton position, function key and shortcut must be unique within the relevant logical step.

SAP’s configuration example demonstrates that the function-code profile controls values such as pushbutton position, function key and shortcut for a logical transaction and step.

10. Map Logical Steps to Custom Subscreens

The RF Screen Manager connects the logical transaction and logical step to the actual ABAP screen.

SPRO → SAP Reference IMG → Extended Warehouse Management→ Mobile Data Entry→ Radio Frequency (RF) Framework→ RF Screen Manager

Once configured , it will start reflecting on the logical transaction screen setup under – Map Logical Transaction Step to Sub-Screen