High- Level Specification

Functional Overview

Business Requirement

For sales order items that are Spec-based assigned to the Composite Sales Organization, specifications must remain fixed once production has started.
After the related Process Order is released, no changes to the specification fields in the sales order may be permitted.

This ensures:

• Full alignment between Sales and Production

• Prevention of mismatches between planned vs. produced specifications

• Protection of product quality and compliance once manufacturing begins

The business requires a system-controlled restriction that prevents users from modifying specification fields at the sales order item level after the process order reaches Released (REL) status.

Scope and Objectives

Scope and Objectives

This WRICEF covers a system validation enhancement in Fiori App: Manage Sales Orders – Version 2 (F3893) executed during sales order change mode.

The objective is to:

• Detect when a sales order line item is linked to a Process Order

• Confirm whether the Process Order has system status REL

• Prevent any modification to specification fields once REL status is reached

• Display an error message and block the save action

• Apply this rule only to:

  • Sales orders under the Composite Sales Organization

• Ensure no impact to:

  • Other Sales Organizations

The Process Order link is determined via the Z-table maintained by the PCCD tool (“new IPA”).

WHY STANDARD IS NOT SUFFICIENT

SAP standard does not provide functionality to restrict updates to sales order specification fields based on the status of a linked Process Order.

Key limitations include:

• SAP does not cater for specification fields at sales order item level; these fields are custom (Z-fields). Therefore, standard SAP cannot control, validate, or freeze them based on production status.

• Standard SAP allows editing of sales order data even after the associated production order is released.

• No standard integration exists between specification data and the Process Order system status (REL).

• Standard logic cannot prevent late specification changes that would desynchronize Sales and Production.

• High operational risk remains that outdated or incorrect specifications could be used once production has already started.

The scope of this enhancement is depicted in process step Other Sales Order Changes below. For the full Signavio, please go to 02.04.02.09. Manage Sales Order Execution Exceptions

Assumptions

1. Process Order Linkage Is Available and Accurate

   • The link between Sales Order Item → Process Order is derived from the Z-table maintained by the PCCD RICEF tool (“new IPA”).

   • It is assumed that this table is correctly and consistently updated before the sales order change is attempted.

2. Process Order Must Be in “REL” Status to Trigger the Restriction

   • The enhancement assumes that Process Order system status REL (Released) is the correct and only status that should freeze specification fields.

   • Any earlier status (e.g., CRTD, PREL) will not restrict changes.

3. Only Specification Fields Are Blocked

• • The enhancement will block changes only to the designated specification Z-fields.
  • Other sales order fields remain editable, provided no other business rules prevent their modification.

1. Fiori App “Manage Sales Orders – Version 2 (F3893)” Is the Primary UI

• • It is assumed that users manage sales order changes exclusively through Fiori app F3893.

  • Changes via GUI (VA02) or other interfaces may require additional enablement if deemed in scope.

Error Message Will Prevent Saving

• It is assumed that raising an error is the correct system response (not warning or hard-stop popup).

• Users must not be able to bypass the freeze once conditions are met.

1. Applicable Only to Open Sales Orders

• The assumption is that the enhancement applies to orders still within the allowable change window, excluding orders already fully delivered or closed.

Dependencies

Security, Integrity and Controls

Configuration Requirements

Language Requirements

Special Requirements

Design Rationale

Functional Requirements

Proposed Technology to Use

Data Source Considerations

Data Validation Considerations

Custom Tables

Master Data

Configuration Table

Selection Screen Enhancement

Processing Logic

Volumetrics

Performance Considerations

Error Handling

Testing

How to Test

Test Conditions and Expected Results

Test Considerations/Dependencies

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

Change log