| Status | Approved |
|---|---|
| Owner | |
| Stakeholders | |
| Jira Request ID | Enter the Jira request card here (Use the Jira macro to search and add) |
| Jira Development ID |
High- Level Specification
| Parameter | Value |
|---|---|
| Application System | |
| Business Process Reference |
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 blocked or quality status to unrestricted movements can only be performed by Quality roles and not by warehouse roles. Such movements are done in EWM at warehouse monitor level which is a single transaction. 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.
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
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 |