High- Level Specification

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 back to restricted status by QM. In this case, the system should revert delivery status from "Ready for Shipment" to "Not-Ready for Shipping" in EWM and communicate it to TM, so the packing information of restricted batches/stock is prevented of being updated in TM accordingly.

In addition the Business requires to have automatic check and prevent start loading of already picked goods, this can be done with reversal of the already set status "Ready for Shipping" for respective delivery to status . 

The following 3 scenarios are in scope:

Scenario 1) Do not set "Ready for Shipping" status - if status of any batch assigned in the delivery is restricted or any of the picked stock for respective delivery is Blocked or in Quality Inspection.

Scenario 2) Set "Ready for Shipping" status only if the batch status of the batch assigned to a delivery is unrestricted and stock status of picked stock for respective outbound delivery is unrestricted.

Scenario 3) If "Ready for Shipping" status already set for a delivery but not yet posted Goods Issue - Reverse to "Not-Ready for Shipping" status If status of any batch assigned to delivery is restricted or status of the stock for delivery is not Unrestricted.

Requirement details:

1º.- A custom program is required, set as Batch job and run for the respective variant, to select relevant deliveries to set up "Ready for Shipping" status with additional check if all assigned batches and picked stock for respective delivery is Unrestricted.

2º.- Second step of this Batch Job needs to cover additional check of the stock and batches assigned for every delivery with already set "Ready for Shipping" status but not yet posted Goods Issue, and in case of any batch moved to restricted or picked stock different then Unrestricted, to revert the status to "Not Ready for Shipping" for respective delivery.

The following scenarios are in scope for the Batch Job:

• Do not set "Ready for Shipping" status - if status of any batch assigned in the delivery is restricted or any of the picked stock for respective delivery is Blocked or in Quality Inspection.
• Set "Ready for Shipping" status only if the batch status of the batch assigned to a delivery is unrestricted and stock status of the stock picked for respective outbound delivery is unrestricted.
• If "Ready for Shipping" status already set for a delivery but not yet posted Goods Issue - Reverse to "Not-Ready for Shipping" status If status of any batch assigned to delivery is restricted or status of the stock for delivery is not Unrestricted.
• Error handling - collect the error messages for the Job run and provide the possibility to display the log, based on the execution date.

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 is finished in EWM.

The "Ready for Shipping" status must be set only if all batches and stock, picked for respective delivery are Unrestricted.

The status change step "Ready for Shipping" sends the picking/packing details to Transportation Management system 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 assigned batches or respective stock is other than Unrestricted for respective delivery.

In such way there is a need to automatically reverse back the status to "Not-Ready for Shipping" for a delivery with not yet posted Goods Issue, if any of the batches or stock was moved to other than Unrestricted status for respective delivery.

Process Flow Diagram

Scenario 1

Automatic Ready for Shipping process

Scenario 2

Automatic revert from Ready for Shipping to Not-Ready for Shipping process

Execution step, as part of SAP SIGNAVIO Outbound flow'

06.11.02.01. Manage Outbound Material Flow for EWM Storage Locations

Execution Flow

Assumptions

We can use the standard configuration option to change the status "Ready for Shipping" and enhancement is required to prevent change of the status if any of the batches are Restricted or any of the stock is not Unrestricted.

We plan to create a Batch Job for automatic change of the status of respective deliveries to "Ready for Shipping", and in case of already set status revert it to "Not-Ready for Shipping" in case of any batch or stock not Unrestricted for deliveries not Goods Issue posted.

Dependencies

N/A

Security, Integrity and Controls

Authorization check to be done via Authorization Group for Foreground process execution.

A background system user will be used to run the background job. 

Configuration Requirements

Standard configuration for triggering the change of the status for respective delivery, after picking is completed.

Language Requirements

EN, FR, CN, IT

Special Requirements

N/A

Design Rationale

Functional Requirements

The Business team requires EWM Warehouse status change to "Ready for Shipping" to be done automatically only if all assigned Batches and Stock are Unrestricted. Also revert  the status "Not-Ready for Shipping" for deliveries not yet Goods Issue posted if any of the assigned Batches or Stock are not Unrestricted.

The standard program /SCWM/R_SET_DSH_STAT_AUTOMATIC, for deliveries with Picking completed status, can be used as a base for the new custom program, and additional logic for the conditions of the batch and stock status will be added.

Proposed Technology to Use

Batch Job

Data Source Considerations

Data Validation Considerations

Custom Tables

N/A

Master Data

N/A

Configuration Table

N/A

Selection Screen Enhancement

N/A

Processing Logic

The new custom program needs to have a selection screen for creating a Variant for Batch Job execution.

Batch Job will be set, to be executed in Background, several times a day. The period of time needs to be aligned with the Business team.

The new Batch Job program needs to have the following steps:

 A. Set status Ready for Shipping for all deliveries with Picking completed status only if Batch and Stock are Unrestricted.

1. Select all deliveries with Status "Not-Ready for Shipping" and Picking status "Completed".
2. Check if all assigned batches for respective delivery are Unrestricted.
3. Check if all picked stock for respective delivery is Unrestricted.
4. If any of the 2 previous conditions (2 or 3) are not met - stop the process.
5. if all the first 3 conditions (1, 2 and 3) are met - set status "Ready for Shipping".

B. Revert status from "Ready for Shipping" to "Not-Ready for Shipping" for deliveries with batch or stock different then Unrestricted.

1. Select all deliveries with Status "Ready for Shipping" and Goods Issue status "Not Started".
2. Check if all assigned batches for respective delivery are Unrestricted.
3. Check if all picked stock for respective delivery is Unrestricted.
4. If both of the 2 previous conditions (2 or 3) are met - stop the process.
5. if any of the 2 conditions (2 or 3) are not met - revert the status from "Ready for Shipping" to "Not-Ready for Shipping".

Volumetrics

More than 20000 deliveries per month.

Performance Considerations

N/A

Error Handling

As this will be a Batch Job, the system will collect all errors in a message and log it to an error log object.

Testing

How to Test

Prerequisites:

EWM ODO created and

Delivery Picking Status - Completed

Delivery Goods Issue status - Not Started

Execution Steps

1. Execute the enhanced program.
2. Check the status of respective EWM ODO.

Positive Test 

Create 3 positive scenarios:

1. Create Positive test flow 1 - all assigned Batches and Stock are Unrestricted - the enhanced program will set the new status Ready for Shipping. 
2. Create Positive test flow 2 - some of the assigned Batches was moved to Restricted status - the enhanced program will change the EWM ODO status from Ready for Shipping to Not-Ready for Shipping.
3. Create Positive test flow 2 - some of the Stock items was moved to not Unrestricted - the enhanced program will change the EWM ODO status from Ready for Shipping to Not Ready for Shipping.

Negative Test

Create 3 Negative scenarios:

1. Delivery with any Batch moved to Restricted status - the enhanced program will not change the ODO status from Not-Ready to Ready for Shipping.
2. Delivery with any of the Stock items moved to not Unrestricted - the enhanced program will not change the ODO status from Not-Ready to Ready for Shipping..
3. Delivery with already set status Ready for Shipping and Goods Issue status Not Started with all Batches and Stock items Unrestricted - the enhanced program will not change the status. The status will remain Ready for Shipping.

Test Conditions and Expected Results

Test Conditions and Expected Results

N/A

Test Considerations/Dependencies

N/A

Other Information

N/A

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

N/A

Change log