You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Status

  Revision under Review

OwnerVAN 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

ParameterValue
Application SystemApplication System (Source)S/4Hana ROW, S/4Hana China
Business Process Reference02.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


Process Flow Diagram

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

TableField NameComments/Calculation/Field Manipulation











Data Validation Considerations

TableField NameComments/Calculation/Field Manipulation













Custom Tables

Master Data

FieldDescriptionData Type/LengthValidation rule/ Value Help









Configuration Table

FieldDescriptionData Type/LengthValidation rule/ Value Help








Selection Screen Enhancement

Field NameDescription

Select:

Data Type/LengthDefault Value/ Validation rule/ Value HelpSelection Logic













Processing Logic



Volumetrics


Performance Considerations



Error Handling


Testing

How to Test

Test Conditions and Expected Results

IDConditionExpected Result










Test Considerations/Dependencies


Other Information


Development Details

Package

Package NameParent Package




Enhancement Implementation

Enhancement TypeStandard Definition NameCustom Implementation NameDesign Rationale Reference









Other Development Objects

Object TypeObject NamePurpose/High Level LogicDesign 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

ZFIZMMZPSZCOZSDZBCZFIZCA
TABLESZFITZMMTZPSTZCOTZSDTZBCTZFITZCAT

See also


No files shared here yet.

Change log

Version Published Changed By Comment
CURRENT (v. 2) May 08, 2026 17:06 VAN AARDE-ext, Tonya
v. 17 May 08, 2026 17:04 VAN AARDE-ext, Tonya
v. 16 Apr 29, 2026 13:18 VAN AARDE-ext, Tonya
v. 15 Apr 29, 2026 12:54 VAN AARDE-ext, Tonya
v. 14 Mar 10, 2026 09:29 VAN AARDE-ext, Tonya
v. 13 Mar 10, 2026 09:02 VAN AARDE-ext, Tonya
v. 12 Mar 02, 2026 12:22 VAN AARDE-ext, Tonya
v. 11 Mar 02, 2026 12:14 WEINERT-ext, Patrick
v. 10 Mar 02, 2026 12:03 VAN AARDE-ext, Tonya
v. 9 Feb 17, 2026 15:52 VAN AARDE-ext, Tonya

Go to Page History

  • No labels