High- Level Specification

Functional Overview

1. Business Requirement

To ensure robust and stable integration between Sales & Distribution (SD) and Transportation Management (TM), the business requires control over changes to the Shipping Condition once Transportation planning has commenced.

When a Freight Unit (FU) has already been planned and assigned to a Freight Order or Freight Booking, changing the Shipping Condition—specifically from Ocean to Air—creates a mismatch between the sales document and the transportation execution. This can result in automatic de-assignment of the Freight Unit, leading to disruption of downstream logistics processes, replanning efforts, and potential delivery delays.

This WRICEF introduces controlled validation logic to prevent Shipping Condition changes from Ocean to Air when the related Freight Unit is already planned, while still allowing flexibility for other mode changes where operationally valid.

The solution supports:

• Protection of TM planning integrity

• Prevention of Freight Unit de-assignment

• Consistent SD–TM integration behavior

• Controlled flexibility based on Freight Unit planning status

Scope and Objectives

This WRICEF covers a targeted enhancement applicable to:

• Sales Orders (Document Category C)

• Change processing only

The enhancement applies at sales order header level, evaluated against item-level Freight Unit planning status, and is enforced during Save. 

Applications in Scope

• SAP Fiori

• Manage Sales Orders – Version 2
• Change Sales Orders

• SAP GUI
• Change Sales Orders Va02

Why Standard SAP Is Not Sufficient

SAP standard does not include a validation mechanism to:

• Check Freight Unit planning status in TM when a Shipping Condition is changed in Sales Orders

• Prevent mode-of-transport mismatches once a Freight Unit is Planned or Partially Planned

• Distinguish between allowed and disallowed Shipping Condition changes based on TM execution status

Without such validation:

• Users can change the Shipping Condition from Ocean to Air after TM planning has occurred

• Freight Units may be automatically de-assigned due to transport mode inconsistencies

• Freight Orders or Freight Bookings can be disrupted or invalidated

• Downstream logistics processes require manual correction and replanning

Limited Control in SAP Fiori Sales Order Processing

In the Manage Sales Orders – Version 2 Fiori app:

• Shipping Condition changes are allowed without awareness of TM planning status

• No standard error handling exists to block incompatible changes at Save

• Users receive no immediate feedback on the impact of changes to TM execution

The scope of this enhancement is depicted in process step Maintain item details below. For the full Signavio, please go to 02.04.02.01. Manage Standard Sales Order

Insert the flowchart and fill in the steps

Assumptions

• Sales Orders are integrated with SAP Transportation Management (TM) and generate Freight Units (FUs) as part of standard SD–TM integration.

• Freight Unit planning status maintained in TM (/SCMTMS/D_TORROT-PLAN_STATUS_ROOT) is considered the single source of truth for determining whether Transportation planning has commenced.

• The Shipping Condition field (VBAK-VSBED) is used consistently to derive the mode of transport for TM planning.

• Shipping Condition values are standardized across the landscape, where:

  • 01 = Ocean

  • 03 = Air

• The restriction applies only when a Shipping Condition change would result in a mode-of-transport conflict (Ocean → Air) with an already Planned or Partially Planned Freight Unit.

• Shipping Condition changes from Ocean to Road or other non-Air modes are assumed to be operationally valid and remain unrestricted.

• When a Freight Unit is in Not Planned (“01”) status, the system assumes that no TM execution commitments exist and Shipping Condition changes may proceed.

• The validation logic assumes a direct and reliable link between Sales Order items and Freight Units via standard TM integration tables.

• Error handling is implemented as a hard validation (blocking error) to prevent inconsistent data from being saved.

Dependencies

Not Applicable

Security, Integrity and Controls

The enhancement will follow the SAP standard security and authorization framework.
The authorization to maintain these this field should be included in the Customer Representative Role as part of the Manage Sales Orders v2  - F3893, VA02 Change Sales order. 

Configuration Requirements

Not Applicable

Language Requirements

Not Applicable

Special Requirements

Not Applicable

Design Rationale

Functional Requirements

Shipping Condition Change Restriction

Applicability

The restriction requirements apply to sales document header changes for:

• Sales Orders (Document Category C)

The validation behavior shall be enforced in:

• SAP Fiori – Manage Sales Orders – Version 2 (F3893)

The restriction applies during change mode and is evaluated at Save.

• SAP GUI

• VA02 – Change Sales Order

1. Shipping Condition Field (VBAK-VSBED)

Field Usage

The system shall use the standard SAP Shipping Condition field (VBAK-VSBED) to derive the Mode of Transport for downstream Transportation Management (TM) planning.

Relevant Values

Other Shipping Condition values (e.g. Road, Rail) remain unchanged and unrestricted.

2. Freight Unit Planning Status Evaluation

TM Integration Dependency

The system shall evaluate the Freight Unit (FU) planning status in SAP Transportation Management before allowing certain Shipping Condition changes.

TM Tables in Scope

• Sales Order Item ↔ Freight Unit link: /SCMTMS/D_TORITE

• Freight Unit Root: /SCMTMS/D_TORROT

• Planning Status Field: /SCMTMS/D_TORROT-PLAN_STATUS_ROOT

Relevant Planning Status Values

Shipping Condition Restriction Logic

Standard Field Usage

The system shall restrict changes to the Shipping Condition (VBAK-VSBED) based on the Freight Unit planning status in TM.

Restriction Logic

When a user attempts to change the Shipping Condition, the system shall apply the following rules:

Restricted Scenario

The system shall prevent saving the Sales Order if all of the following conditions are met:

• Existing Shipping Condition = Ocean (01)

• New Shipping Condition = Air (03)

• A Freight Unit exists for at least one Sales Order item

• Freight Unit Planning Status is:

  • Planned (“03”), or

  • Partially Planned (“02”)

Allowed Scenarios

The system shall allow the Sales Order to be saved when:

• Shipping Condition is changed from Ocean to Road or other non-Air modes

• Freight Unit Planning Status = Not Planned (“01”)

• No Freight Unit exists for the Sales Order

Restriction Lift Logic

Applicability

The restriction shall be dynamically lifted based on the Freight Unit planning state.

Restriction Lift Rules

If the Freight Unit Planning Status changes to:

• Not Planned (“01”)

Then:

• The Shipping Condition change from Ocean → Air shall be permitted

• The Sales Order may be saved successfully

Error Handling

Blocking Behavior

If the restriction conditions are met, the system shall:

• Prevent the Sales Order from being saved

Error Messaging

The system shall display a clear and meaningful error message indicating that:

• The Shipping Condition change from Ocean to Air is not permitted

• The related Freight Unit is already Planned or Partially Planned in Transportation Management

Example (illustrative):

“Shipping Condition change from Ocean to Air is not permitted. Related Freight Unit is already planned in Transportation Management.”

Proposed Technology to Use

Typically, an enhancement will be based on an existing SAP BADI / user exit. If this is the case, please provide the proposed details of the BADI / user exit.

Data Source Considerations

Data Validation Considerations

Not Required

Custom Tables

Not Required

Master Data

<Title Custom Table 1>

<Include an overview of the table and what it’s used for>

Configuration Table

Title Configuration Table 1

Include an overview of the table and what it’s used for

Selection Screen Enhancement

This section will give the details on the selection screen parameters, parameter type and whether it’s obligatory or not. This section can be used to define the Import Export parameters for Function Module or User Exit or Screens. Can be deleted if not needed.

Processing Logic

Volumetrics

Performance Considerations

Specify if there are any specific performance factors that need to be taken into consideration during development i.e. enhancement must be able to be executed by 10 users at the same time, etc.

Error Handling

Detail how errors will be handled: Notification, Restart/ Recovery and Re-Processing Procedures

Testing

How to Test

Please provide some guidance and/or test data to help the developer unit test the enhancement. Please include both positive and negative testing (to validate error situations handling). The developer will need to test repeatedly, so where appropriate provide instructions to reverse the actions performed so the test may be run again or explain how to create new input data to the test. The developer will need logons for test users representing the various roles within the approval process.

Test Conditions and Expected Results

Test Considerations/Dependencies

List any considerations essential for application test planning (e.g., test this before ABC along with DEF separate from GHI). If the development encompasses a user interface, explain how to test it. List any insights as to how this component could be tested the most efficiently.

Other Information

Development Details

Package

Enhancement Implementation

Other Development Objects

Appendix

Custom Authorization Group Naming Convention

This table is based on the Syensqo development standards document. It provides the naming conventions for authorization groups to associated with custom reports and tables to comply with security requirements.

See also

Insert links and references to other documents which are relevant when trying to understand this decision and its implications. Other decisions are often impacted, so it's good to list them here with links. Attachments are also possible but dangerous as they are static documents and not updated by their authors.

Change log