| Status | Revision under Review |
|---|---|
| Owner | VAN AARDE-ext, Tonya |
| Stakeholders | |
| Jira Request ID | ERP-156 - Getting issue details... STATUS |
| Jira Development ID | ERP-359 - Getting issue details... STATUS |
High- Level Specification
| Parameter | Value |
|---|---|
| Application System | Application System (Source)S/4Hana ROW, S/4Hana China |
| Business Process Reference | 02.04.02.01. Manage Standard Sales Order |
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 in the SAP Fiori application.
Applications in Scope
SAP Fiori
Manage Sales Orders – Version 2
Change Sales Orders
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
Step | Description | Comment |
|---|---|---|
Assumptions
Dependencies
Security, Integrity and Controls
Configuration Requirements
Language Requirements
Special Requirements
Design Rationale
Functional Requirements
Proposed Technology to Use
Data Source Considerations
| Table | Field Name | Comments/Calculation/Field Manipulation |
|---|---|---|
Data Validation Considerations
| Table | Field Name | Comments/Calculation/Field Manipulation |
|---|---|---|
Custom Tables
Master Data
| Field | Description | Data Type/Length | Validation rule/ Value Help |
|---|---|---|---|
Configuration Table
| Field | Description | Data Type/Length | Validation rule/ Value Help |
|---|---|---|---|
Selection Screen Enhancement
| Field Name | Description | Select: | Data Type/Length | Default Value/ Validation rule/ Value Help | Selection Logic |
|---|---|---|---|---|---|
Processing Logic
Volumetrics
Performance Considerations
Error Handling
Testing
How to Test
Test Conditions and Expected Results
| ID | Condition | Expected Result |
|---|---|---|
Test Considerations/Dependencies
Other Information
Development Details
Package
| Package Name | Parent Package |
|---|---|
Enhancement Implementation
| Enhancement Type | Standard Definition Name | Custom Implementation Name | Design Rationale Reference |
|---|---|---|---|
Other Development Objects
| Object Type | Object Name | Purpose/High Level Logic | Design Rationale Reference |
|---|---|---|---|
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.
ABAP | ZFI | ZMM | ZPS | ZCO | ZSD | ZBC | ZFI | ZCA |
|---|---|---|---|---|---|---|---|---|
| TABLES | ZFIT | ZMMT | ZPST | ZCOT | ZSDT | ZBCT | ZFIT | ZCAT |
