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 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 scenarios 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 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 with not yet posted Goods Issue, if any of the Batches or Stock was moved to other than Unrestricted status.

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.

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 Picking 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.

Change of the status automatically to Ready for Shipping is standard process in EWM, the Job can be set directly using the standard program /SCWM/R_SET_DSH_STAT_AUTOMATIC, for deliveries with Picking completed.

The logic of the check of the Batch and Stock status will be added to the standard program, as it is not there as a standard steps.

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 enhanced standard program needs to have a selection screen for Variant execution.

The program needs to be available to be run on Foreground and also set as a Batch Job and run in Background.

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 3 steps:

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

 - Select all deliveries with Status Not-Ready for Shipping and Picking status completed.

 - Check if the assigned Batches are Unrestricted.

 - Check if the assigned Stock is Unrestricted.

 - If any of the 2 previous conditions are not met - stop the process.

 - if any of the 2 conditions are met - set status Ready for Shipping status.

  2. Revert status from Ready for Shipping to Not-Ready for Shipping for deliveries with Batch or Stock different then Unrestricted.

 - Select all deliveries with Status Ready for Shipping and Goods Issue status Not Started.

 - Check if the assigned Batches are Unrestricted.

 - Check if the assigned Stock is Unrestricted.

 - If any of the 2 previous conditions are met - stop the process.

 - if any of the 2 conditions are not met - revert the status from Ready for Shipping to Not-Ready for Shipping.

Volumetrics

N/A

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