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 #322

Topic:

Restriction on posting changes in EWM:

from Blocked -> to Unrestricted status
from Quality -> to Unrestricted status

Description:

Business require that stock movements from stock types blocked or quality status to unrestricted status can only be performed by operators having Quality roles and not by the operators having warehouse roles. This is required so that unauthorized users are not able to perform the stock movements especially when the stocks are in quality status and or blocked status for quality reasons.

In EWM system, such movements are done at warehouse monitor level which is a single transaction. This transaction also include multiple objects and  functionalities to support warehouse operations and therefore restricting any authorization at the transaction level could jeopardise other functionalities in EWM monitor. Moreover such movements are required to be restricted only in specific directions meaning from quality to unrestricted and not the other way round. 

For this reason, there will be enhancement required to provide authorization control at the specific execution object level in the monitor so that other objects are not affected and that the enhancement will ensure that specific stock type movements are restricted based on the new authorization object.

Solution Key Considerations:

Stock type changes – SAP EWM    

• Enhancement via BADI implementation (/SCWM/EX_CORE_GM_STOCK - KBA  3157694) to control the authorization at sub object level which invoke the posting change transaction in the monitor 

• Provide custom authorization object that will be checked as a part of enhancement to validate and allow transaction to be completed to the authorized roles where the object is assigned. Such roles will be assigned to the required users from quality

• Enhancement framework / Parameterization via soft config to validate applicable sites and control the stock type movements 

Process Impact:

Posting Change / Ad-hoc stock type movements in EWM

• During execution of stock type posting changes, warehouse operator should not be able to move stocks from quality to unrestricted or blocked to unrestricted.

• Ability for quality roles to be able to perform stock type changes. 

Scope and Objectives

The scope of this enhancement :

1) Create a new custom authorization object. The new authorization object will be used for validation during execution of the posting change transaction as a part of authorization check.

2) Create custom / enhancement framework table to allow activation / deactivation of enhancement , define control parameters/variables , Inclusion/exclusion option for organizational values and stock type directions (Q*→F*). The table will need to be transportable. 

3) Implement BADI enhancement to validate if the enhancement is active and if they satisfy conditions defined in the control parameters and to execute checks for the authorization object.

Objective: To restrict stock type movements from quality or blocked  to unrestricted stock type for warehouse operative or warehouse clerk roles.

Screen shot: Transaction /SCWM/MON

Screen Shot: Transaction /SCWM/POST

Assumptions

Not Applicable

Dependencies

Not Applicable

Security, Integrity and Controls

Follow calling Programs authorization check in the Badi explained in the above sections.

The calling program / Badi implementation  to perform authorization check for the new authorization object. Only when the new authorization object is available in the roles assigned to the user, should the execution of the transaction be allowed. In the event of no authorization object available to the user via role , error message should be raised. 

Configuration Requirements

Not Applicable

Language Requirements

Error message translation to be made available to reflect the custom messages are displayed when logged on specific language

Standard languages available in KDD055:

4 Core Languages (English, French, Italian and Mandarin) and additional language support (Brazilian Portuguese, German, Spanish and Thai).

Special Requirements

Not applicable.

Design Rationale

Functional Requirements

As-Is  (Business process)

• The stock type transfer from quality to unrestricted or blocked to unrestricted is only be done by quality users
• Warehouse users are restricted to carry out such stock type movements (to unrestricted , once moved to quality or blocked stock) 

SAP standard (EWM)

• SAP EWM support movement of stock type from one to another via EWM Monitor where the stock line can be selected and the stock type can be changed 
• This is a single transaction that has many sub objects and therefore, the authorization object at transaction level cannot be used as other functionalities in the monitor will be affected 
• Authorization restriction alone  at movement type level in S4 ERP would mean potential queue failures when messages are sent from EWM to ERP.

Solution Key Considerations

Stock type changes – SAP EWM    

• Enhancement via BADI implementation (/SCWM/EX_CORE_GM_STOCK - KBA  3157694) to control the authorization at sub object level which invoke the posting change transaction in the monitor 
• Provide custom authorization object that will be checked as a part of enhancement to validate and allow transaction to be completed to the authorized roles where the object is assigned. Such roles will be assigned to the required users from quality
• Enhancement framework / Parameterization via soft config or enhancement framework configuration table to validate applicable sites and control the stock type movement directions 

Proposed Technology to Use

SAP standard BADI: /SCWM/EX_CORE_GM_STOCK

Data Source Considerations

Not Applicable 

Data Validation Considerations

Not applicable

Custom Tables

A new enhancement framework table will need to be created. This will be required to control the activation/deactivation of enhancement and to define the parameters (organizational entities and transactional objects). The table entries will be transportable and will be maintained by the functional / IT team as a part of solution deployment for the sites. This will provision the parameters for the execution of checks for the activated enhancement . The values defined for the parameters could be a wildcard in such cases all the values should be accepted as validated. 

Master Data

Not Applicable 

Configuration Table

Not Applicable    

Selection Screen Enhancement

Not Applicable

Processing Logic

Below steps will happen while restriction on posting changes in EWM are performed:

Volumetrics

Not Applicable 

Performance Considerations

Not applicable 

Error Handling

Error message should be displayed as explained in the process flow step section above.

Testing

How to Test

Test Conditions and Expected Results

Test Considerations/Dependencies

Not Applicable

Other Information

Development Details

Package

Enhancement Implementation

Other Development Objects

Not Applicable

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

Not Applicable

Change log