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

Insert the flowchart and fill in the steps

Assumptions

We can use the standard configuration option to change the status Ready for Shipping and enhance,emt 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

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

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

Include an overview of the source

Data Validation Considerations

Include an overview of the data validation requirement

Custom Tables

If any custom configuration tables are required, which will be read by the enhancement logic, then specify them here.

Master Data

<Title Custom Table 1>

<Include an overview of the table and what it’s used for>

Configuration Table

Title Configuration Table 1

Include an overview of the table and what it’s used for

Selection Screen Enhancement

This section will give the details on the selection screen parameters, parameter type and whether it’s obligatory or not. This section can be used to define the Import Export parameters for Function Module or User Exit or Screens.

Processing Logic

This section defines the detailed step-by-step logic implemented within the BAdI/User Exit to process the data received from the standard SAP program and database retrieval. It explains the operations performed on the data, the expected outcomes in different scenarios and how the system should behave in response to specific conditions.

Volumetrics

Provide volumetrics details: Initial load volumes, Number of Records, Expected Frequency, Expected Long term Growth)

Performance Considerations

Specify if there are any specific performance factors that need to be taken into consideration during development i.e. enhancement must be able to be executed by 10 users at the same time, etc.

Error Handling

Detail how errors will be handled: Notification, Restart/ Recovery and Re-Processing Procedures

Testing

How to Test

Please provide some guidance and/or test data to help the developer unit test the enhancement. Please include both positive and negative testing (to validate error situations handling). The developer will need to test repeatedly, so where appropriate provide instructions to reverse the actions performed so the test may be run again or explain how to create new input data to the test. The developer will need logons for test users representing the various roles within the approval process.

Test Conditions and Expected Results

Test Considerations/Dependencies

List any considerations essential for application test planning (e.g., test this before ABC along with DEF separate from GHI). If the development encompasses a user interface, explain how to test it. List any insights as to how this component could be tested the most efficiently.

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

Insert links and references to other documents which are relevant when trying to understand this decision and its implications. Other decisions are often impacted, so it's good to list them here with links. Attachments are also possible but dangerous as they are static documents and not updated by their authors.

Change log