| Status | |
|---|---|
| Owner | |
| Stakeholders | |
| Jira Request ID | |
| Jira Development ID |
High- Level Specification
| Parameter | Value |
|---|---|
| Application System | SAP S4/HANA SyWay |
| Business Process Reference | 06.10 Manage Inventory and Logistics 06.11 Manage Warehouse and Logistics |
Functional Overview
This mobile will allow a handling unit to be moved to a new storage location.
Scope and Objectives
This app will support transfers of handling units:
- between IM handling unit managed storage locations
- from an IM storage location to an EWM storage location
- from an EWM storage location to an IM storage location
Process Flow Diagram
Not applicable. The HU Storage Location Transfer will be used in the LO and EWM processes where a handling units need to be moved to another storage location.
Assumptions
None
Dependencies
None
Security, Integrity and Controls
The user must have material document create access for the selected plant. Check object M_MSEG_WMB for Activity 01 and the selected plant. If no access, show the message "No authorization for plant <9999>".
Configuration Requirements
None
Language Requirements
This app will be available in all SyWay languages.
Special Requirements
None
Design Rationale
Functional Requirements
Detail the functional requirements that are desired to be achieved by the UI
Recommended UI Technology
This app will be developed using Neptune DXP Open Edition. The app will appear on the Neptune launchpad.
Application Screen
Wireframe or Mock-Up
Please provide a Hi fidelity mock-up of the new application’s screens. Ensure Syensqo's Brand standards are adhered to. (i.e. logo, font, colors, etc.)
The developers should follow UI best practice to keep the screens user-friendly and consistent
Screen Behavior
No special behavior required.
Screen Navigation
Standard navigation.
Data Integration
| Field | Table-Field Name | Comments / Calculation / Field Manipulation / Input / Output / Validation rule / Value help |
|---|---|---|
Custom Tables
None
Master data
None
| Field | Description | Data Type/Length | Validation rule / Value help |
|---|---|---|---|
Configuration table
None
| Field | Description | Data Type/Length | Validation rule / Value help |
|---|---|---|---|
Tooltips
None
Front-End
This app can be executed on a mobile device or in desktop mode.
Mobile Services
Not applicable.
Authentication & Authorization
The user must have material document create access for the selected plant. Check object M_MSEG_WMB for Activity 01 and the selected plant. If no access, show the message "No authorization for plant <9999>".
Accessibility
Not applicable.
Volumetrics
This solution will be used at approximately 100 plants. The total users is estimated to be around 800.
Performance Consideration
Postings should be completed in 2 to 3 seconds.
Error Handling
Errors to appear in a pop up window that needs to be acknowledged by the user.
Testing
How to Test
Test Conditions and Expected Results
| ID | Condition | Expected Result |
|---|---|---|
| 1 | Transfer highest level HU in IM sloc to another IM sloc | HU transfer successful |
| 2 | Transfer lowest level HU in IM sloc to another IM sloc | User gets information message that HU will be first unpacked. HU transfer successful |
| 3 | Transfer highest level HU in IM sloc to an EWM sloc | HU transfer successful |
| 4 | Transfer lowest level HU in IM sloc to an EWM sloc | User gets information message that HU will be first unpacked. HU transfer successful |
| 5 | Transfer highest level HU in EWM sloc to IM sloc | HU transfer successful |
| 6 | Transfer lowest level HU in EWM sloc to an IM sloc | User gets information message that HU will be first unpacked. HU transfer successful |
| 7 | Scan/Enter HU that does not exist | Error issued |
| 8 | Attempt to transfer HU to sloc, when HU is already in this sloc | Error issued |
| 9 | Transfer HU in blocked stock to another IM sloc | HU transfer successful |
| 10 | Transfer HU in quality sloc to another IM sloc | HU transfer successful |
Test Considerations/Dependencies
None
Other Information
None
Development Details
Package
| Package Name | Parent Package |
|---|---|
UI Implementation
UI Type | UI Name | Fiori Catalogue | Design Rationale Reference |
|---|---|---|---|
API Implementation
| API Type | API Name | Purpose / High Level Logic | API Product | Design Rationale Reference |
|---|---|---|---|---|
Other Development Objects
| Object Type | Object Name | Purpose/High Level Logic | Design Rationale Reference |
|---|---|---|---|
Appendix
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.