High- Level Specification
| Parameter | Value |
|---|---|
| Application System | |
| Business Process Reference |
Functional Overview
The business requires the ability to change the stock type of a handling unit using the Logistics Neptune Mobility Solution. This transaction will allow the stock type change such as unrestricted to blocked stock for all the contents within the handling unit.
Handling units will represent pallets, boxes or rolls etc. and a barcode label on the packaging will normally have the handling unit number in a 2D GS1 Data Matrix barcode format, but other barcode symbologies will also be supported.
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 performing the stock type change at HU level (applicable to all the contents in the HU).
This app will support stock type changes of handling units in IM handling unit managed storage locations and EWM storage locations.
Process Flow Diagram
Step | Description | Comment |
|---|---|---|
| 1 | Choose required stock type | |
| 2 | Scan handling unit(s) for stock type change | |
| 3 | Post stock type change(s) to SAP |
Assumptions
None
Dependencies
None
Security, Integrity and Controls
None
Configuration Requirements
None
Language Requirements
This app will be available in all SyWay languages.
KDD055 - Multi-Language Support
Special Requirements
None
Design Rationale
The Syensqo business requires the ability to transfer the stock of handling units into different stock types. 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
Initial Screen
The first screen will prompt to enter the destination stock type and the to scan/enter the handling units to be transferred.
The stock type can be selected from a drop down list.
Handling units in the warehouse must be entered, by scanning or typing. The handling unit number may be an SSCC number or other number.
When scanning, an enter key will be added automatically to the scanned value. This allows rapid scanning of multiple handling units.
For scanning, the HU field needs to support 2D GS1 data matrix barcodes, code 128 barcodes and other agreed formats. Application identifier 00 will be present in the case of SSCC numbers. Otherwise the entire content of the scanned barcode is to be considered the HU number.
After manual input the user can press Enter or the OK button.
Each valid HU scanned will be added to a scanned list. The scanned list will show a counter of the number of HUs scanned.
The scanned list will show, the HU number, the packaging material, the material number, the batch number, the storage location (for IM HU) or the storage bin (For EWM HUs) and the cumulated quantity on the HU.
If the HU contains more than one material, the material description will show "<Mix>".
If the HU contains more than one batch, the batch number will show "<Mix>".
Determine if HU is IM or EWM and calculate the cumulated content
See ERP-1003 for this shared logic.
Handling Unit Validation (IM)
Field | Table-Field name | Comments / Calculation / Field Manipulation / Input / Output / Validation rule / Value help |
HU number | VEKP-EXIDV | The handling unit must exist otherwise display an error “Handling Unit <hu> does not exist." |
HU Plant | VEKP-WERKS | The HU must belong to the plant of the user otherwise display an error “Plant of HU <hu> is <x>”. |
HU Object Assignment | VEKP-VPOBJ | The HU must be unassigned (VEKP-VPOBJ = 12) otherwise display an error “HU <hu>has status <VEKP-BPOBJ> <VEKP-VPOBJKEY>” |
HU System Status | Status Management | If the HU system status contains “INIV” display an error “HU <hu> is active for physical inventory”. |
HUM SLoc | VEKP-HU_LGORT | The HU must be in a HU managed storage location (VEKP-HU_LGORT = X) otherwise display an error “HU <hu> in non-HU Storage Location”. |
HU Stock Type | VEPO-BESTQ | If the current stock type of the Handling Unit is the same as the destination stock type display an error “HU <hu> already has stock type <9999>” |
HU number (Already Processed) | VEKP-EXIDV | If the HU entered has already been processed with a stock type change pending on the scanner, show an error "HU <hu> already processed for transfer to sloc <x>". |
Handling Unit Validation (EWM)
Field | Table-Field name | Comments / Calculation / Field Manipulation / Input / Output / Validation rule / Value help |
HU EWM number | /SCWM/HUHDR-HUIDENT | The handling unit must exist otherwise display an error “Handling Unit <hu> does not exist." |
HU Warehouse | /SCWM/HUHDR-LGNUM | The HU must belong to the warehouse of the user otherwise display an error “Warehouse of HU <hu> is <9999>”. |
HU System Status | Status Management | If the HU system status does not include "PORT", display an error "HU <hu> is not in warehouse". |
HU Object Assignment (PID) | /SCWM/HUREF-GUID_HU | The HU must be not have a reference to a document, otherwise display and error "HU <hu> is assigned to <Doc Category short description> <Document number of reference GUID>". For document categories PDI, PDO and SPC select reference document category ERP on table /SCWM/HUREF-DOCID. For document category PMR, select the first record with reference document category RES. |
HU EWM Stock Type | <?> | If the stock type of the Handling Unit is the same as the destination storage stock type, display an error “HU <hu> already has stock type <9999>” |
HU number (Already Processed) | /SCWM/HUHDR-HUIDENT | If the HU entered has already been processed for a stock type change pending on the scanner, show an error "HU already processed for change to stock type <x>". |
Detail screen
For any HU scanned, the HU details can be displayed by selecting the HU in the list of HUs already scanned.
With this option the user will navigate to the HU display app ERP-788.
Processing data
A summary of the HUs already scanned will be listed on the HU entry screen. The most recently scanned HU will be shown at the top of the list. The list will also show the source and destination stock types. A counter will show the number of HUs already scanned.
The user can branch to the HU details screen from the summary by clicking on an item.
Provide an option for the user to delete transactions captured. E.g. The user may elect to delete a record in the case that an HU was processed by mistake.
The user will press a Save button to post the transactions in SAP.
IM HU transfer to IM Sloc
- Post the goods movement(s) in SAP using the function module HU_CREATE_GOODSMVT_RFC.
- For the purposes of the Function Module the process code depends on the stock type change being performed. e.g. 0005 to transfer from unrestricted use stock to blocked stock.
- This posting will create a material document and the stock type change of the handling unit(s) is complete.
IM HU transfer to EWM Sloc
- Perform a Posting Change for the handling units(s) for the required stock type change.
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
See example screens in Functional Requirements section.
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
A custom table will store the allowed stock type changes for the plant.
Master data
| Field | Description | Data Type/Length | Validation rule / Value help |
|---|---|---|---|
Configuration table
| 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 |
|---|---|---|
Test Considerations/Dependencies
None
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 |
|---|---|---|---|