| Status | Approved |
|---|---|
| Owner | |
| Stakeholders | |
| Jira Request ID | |
| Jira Development ID |
High- Level Specification
| Parameter | Value |
|---|---|
| Application System | |
| Business Process Reference |
Functional Overview
Business require ability to change the stock types at handling unit level using Neptune mobility solution. This transaction will allow the stock type change such as e.g unrestricted to blocked stock for all the contents within the handling unit.
Scope and Objectives
The scope of this document is limited to the development of the Neptune mobility transaction to allow stock type status changes at handling unit level. The Neptune mobile transaction will facilitate to perform stock type change at HU level (applicable to all the contents in the HU)
Process Flow Diagram
Step | Description | Comment |
|---|---|---|
Assumptions
None
Dependencies
None
Security, Integrity and Controls
None
Configuration Requirements
None
Language Requirements
KDD055 - Multi-Language Support
Special Requirements
None
Design Rationale
Syensqo business will require ability to transfer the stock into different stock type at handling unit level. This is identified as a business requirement within the scope of Neptune mobile transactions. This transaction will be new screen to be developed in Neptune mobile app that will support the user interface to execute the transaction and the background processing of the data to transfer the stocks into required stock type using posting change.
Functional Requirements
The Neptune mobile transaction will have the user menu option on the screen as a part of the main or sub menu of the process. This option will display the stock type change sub menu for the user interface. Once clicked on the sub menu option, the user should be prompted to scan the handling unit for which the stock type change has to be requested. Upon scanning the HU , system will show the screen with HU details such as the current stock type
Recommended UI Technology
Application Screen
Wireframe or Mock-Up
Screen Behavior
Screen Navigation
Data Integration
| Field | Table-Field Name | Comments / Calculation / Field Manipulation / Input / Output / Validation rule / Value help |
|---|---|---|
Custom Tables
Master data
| Field | Description | Data Type/Length | Validation rule / Value help |
|---|---|---|---|
Configuration table
| Field | Description | Data Type/Length | Validation rule / Value help |
|---|---|---|---|
Tooltips
Front-End
Mobile Services
Authentication & Authorization
Accessibility
Volumetrics
Performance Consideration
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 |
|---|---|
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 |
|---|---|---|---|