| Status | MTR Approved |
|---|---|
| Owner | |
| Stakeholders | |
| Jira Request ID | ERP-327 - Getting issue details... STATUS |
| Jira Development ID |
High- Level Specification
| Parameter | Value |
|---|---|
| Application System | S/4Hana ROW, S/4Hana China, S/4Hana CUI |
| Business Process Reference | 06.11.02.01. Manage Outbound Material Flow w/wo Discrepancies for EWM |
Functional Overview
The functional design of the enhancements describes the scenario(s) where enhancements to existing SAP programs are required.
Integration Topic #287
Topic:
Prevent Ready for Shipping Status when batch or stock is restricted.
Description:
During the warehouse execution process after picking and packing is completed, it is possible that the batches or Stock are moved to Restricted status by QM. In this case the system should stop allowing the Ready for Shipment status in EWM to be sent to TM, so that the packing information of restricted batches is prevented from getting updated in TM. In addition the Business requires to have automatic check and prevent start loading of already picked Goods, this can be done with reverse of the status to Not-Ready for Shipping.
Requirement details:
Batch job will run to select deliveries relevant to set up Ready for Shipping status with check if all Batches and Stock are Unrestricted, and with additional check of the Stock and Batches for deliveries with already set Ready for Shipping status but not Goods Issue. Deliveries with already set status Ready for Shipping and any of the Batches and Stock not Unrestricted, need to be reversed to Not-Ready for Shipping status.
The following scenarious need to be covered.
Scenario 1) Block Ready for Shipping if any Batch or Stock are Restricted.
Scenario 2) Set Ready for Shipping status only if Batches and Stock are Unrestricted.
Scenario 3) If Ready for Shipping status already set for deliveries but not yet posted Goods Issue - Reverse to Not-Ready for Shipping status if any Batch or Stock is Restricted.
Scope and Objectives
Scope:
The standard program cannot be executed automatically because the action needs to be repeated in respective time frames, and the Business Process requires to be scheduled to run as a Background Job.
The program needs to be created with a special variant for Batch Job execution for every EWM Warehouse, where this process is applicable.
Objectives:
As part of the SyWay EWM Outbound execution process, there is a requirement to set Ready for Shipping status Automatically when Picking and Packing is finished in EWM.
The Ready for Shipping status must be set only if all Batches and Stock is Unrestricted. The Ready for Shipping status sends the Picking/Packing details to TM and update the respective FU/FO.
As the Ready for Shipping status is a prerequisite for Loading in TM, we need to prevent the Loading execution if any of the Batches or respective Stock is other than Unrestricted.
In such way there is a need to automatically reverse back the status to Not-Ready for Shipping for deliveries that are not yet posted Goods Issue, if any of the Btches or Stock was moved to other than Unrestricted status.
Step | Description | Comment |
|---|---|---|
| 1. | List Deliveries relevant for the changing the status to Ready For Shipping, with EWM ODO Picking and Packing status Completed. | This step will be done by the standard program /SCWM/R_SET_DSH_STAT_AUTOMATIC. |
| 2. | Loop through the list of selected EWM Outbound Delivery Orders. | |
| 2.1. | Check if all of the Batches, picked for EWM ODO are Unrestricted. | table |
| 2.2. | Check if all of the Stock, picked for EWM ODO is Unrestricted. | table /SCDL/DB_PROCI_O |
| 2.3. | Set the status Ready for Shipping for respective EWM ODO only if both previous checks are passed and Stock and Batches are Unrestricted. | |
| 2.4. | Confirm if the status Ready for Shipping is set or check the error messages. | |
| 3. | Output the messages. | |
| 4. | List Deliveries with status Ready For Shipping with not posted Goods Issue. | |
| 5. | Loop through the list of selected EWM Outbound Delivery Orders. | |
| 5.1. | Check if any of the Batches, picked for EWM ODO is not Unrestricted. | |
| 5.2. | Check if any of the Stock, picked for EWM ODO is not Unrestricted. | |
| 5.3. | Reverse the status Ready for Shipping to Not-Ready for Shipping, for respective EWM ODO, if any of the both previous checks are passed and any of the Stock or Batches are not Unrestricted. | |
| 5.4. | Confirm if the change of the status to Not-Ready for Shipping is set or check the error messages. | |
| 6. | Output the messages. |
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 |