| 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 such as, after picking and packing is completed, it is possible that the batches 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. Batch job will run to check deliveries feasible to set up Ready for Shipping status.
Scenario 1) Block ready for shipping if batch restricted.
Scenario 2) if Ready for Shipping status already set up, enhancement on LO side to block LE-Outbound delivery.
=====
This approach will work before standard functionality to check Ready for Shipping status in outbound delivery (ODO EWM):
Business require "ready for shipment" status for outbound deliveries to be automatic after picking and packing is completed. Currently this status is provided with manual option in SAP EWM Monitor.
The "Ready for Shipping" status was automatically set using report /SCWM/R_SET_DSH_STAT_AUTOMATIC.
Requirement is to add additional check if the Batch is Restricted to do not send the status “Ready for Shipping” to TM.
Scope and Objectives
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 |