| Status | |
|---|---|
| Owner | |
| Stakeholders | |
| Jira Request ID | |
| Jira Development ID |
| Parameter | Value |
|---|---|
| Application System | SAP S4/HANA SyWay |
| Business Process Reference | 06.10 Manage Inventory and Logistics 06.11 Manage Warehouse and Logistics |
This mobile app will allow stock overview information to be displayed. This can be all stock for a storage location or limited to stock for a specific material, batch or storage bin etc. Drill down options will allow the user to see the information by stock type, batch, handling unit or storage bin level.
This app will support stock overview reporting in IM and EWM.
Step | Description | Comment |
|---|---|---|
1. | Initial screen | The field selection for the report offers fields for material, batch and storage location. For plants with EWM, the user can additionally select on storage type, storage section and storage bin. There will also be a checkbox to allow empty storage bins to be reported. The user can scan or enter the values for the selection fields. When the user presses the OK button, if a storage type of storage bin has been entered, the EWM stock screen will be shown (Step 6), otherwise the Stock Overview screen will be shown (Step 2). For plants with EWM, a button will allow the user to go directly to the EWM Stock screen (Step 6). |
2. | Stock Overview screen | Shows all stock by Material/Storage Location with the ability to search by material. Clicking on a material will branch to the Stock Type screen (Step 3) |
3. | Stock Type screen | Shows all stock for the selected material by stock type. For IM HUM storage locations, buttons will allow the user to display stock information per batch (Step 4) or per top level Handling Unit (Step 5). For EWM storage locations buttons will allow the user to display stock information per batch (Step 4) or the EWM stock details (Step 6). |
4. | Batch screen | Shows the same information as the stock overview screen, but per Material/Batch. Has a button to branch to the HU details screen for a selected batch, for IM HUM storage location or to the EWM Stock screen for EWM managed storage location. |
5. | Handling Unit screen | Shows the details of HU’s for material or material/batch in a given storage location with the ability to search the list for a given HU. Include a button to branch to the HU Display transaction. |
6. | EWM Stock screen | Shows the stock per storage bin, listing storage type, storage section, storage bin, handling unit, material, batch and EWM stock type. |
There will be no more than one EWM warehouse assigned to a plant.
None
The user must have material document display access for the selected plant. Check object M_MSEG_WMB for Activity 03 and the selected plant. If no access, show the message "No authorization for plant <9999>".
None
This app will be available in all SyWay languages.
None
Initial Screen
The first screen will prompt to enter Material, Batch and Storage Location. The values for these fields can be scanned or typed.
If the plant is using EWM there will be additional fields to enter Storage Type, Storage Section and Storage Bin. For EWM there will also be a checkbox to allow the user to report empty bins.
For scanning, the field input needs to support the 2D GS1 Data Matrix barcode format or other agreed formats. Material numbers will use application ID 240. Batch will use application ID 10. Barcodes for storage bin will have no application ID.
Any combination of values can be entered with the following exceptions:
The plant and EWM warehouse for the user have already been established at the time of logon to the handheld solution.
Initial Screen Validation
Field | Table-Field name | Comments / Calculation / Field Manipulation / Input / Output / Validation rule / Value help |
Material | MARD-MATNR | |
Batch | MCHB-CHARG | |
Storage Location | MARD-LGORT | Dropdown will only list storage locations for the plant of the user. |
Storage Type | /SCWM/AQUA-LGTYP | Dropdown will only list storage types for the EWM warehouse of the user. |
Storage Section | /SCWM/T302-LGBER | Drop down will only list storage sections for the storage type entered. |
Storage Bin | /SCWM/AQUA-LGPLA | When a storage bin is selected, clear any values entered for storage type and storage section. A valid storage bin for the warehouse must be entered, otherwise display an error “Storage bin <x> does not exist”. |
Empty Bins | /SCWM/LAGP-KZLER | Checkbox. Can only be switched on when all other selection fields are blank, or when only storage type and/or storage section are populated, otherwise display an error “Empty bins by warehouse, storage type of storage section only.” |
<Example Initial screen>
Stock Overview screen
The Stock Overview screen will display a list of material stock based on the selection. The quantity displayed will be the total quantity of the material in stock per storage location across all stock types. This is the same information reported in SAP transaction MB52, selecting by plant, batch and storage location and no zero stock lines.
<Example Stock Type screen>
The user will have the ability to filter the list based on the material or description to allow searching for a specific material.
Selecting a row in the table will take the user to the Stock Type screen.
Stock Type screen
The material details screen shows the quantity of the material by stock type, based on the selection. This is the same selection as the MMBE transaction, selecting by material, plant, storage location, also select special stocks and special stock numbers e.g. Vendor consignment stock: K, Vendor: 29899, no zero stock lines and display level for plant and storage location.
If the location is handling unit managed (T001L-XHUPF = X) and the material exists in handling units, then a “Handling Units” button is displayed allowing the same material stock information to be displayed per handling units. This is the same selection as transaction HUMO selecting by material / plant / storage location. If the location is not handling unit managed, then this button will not be displayed.
If the material is batch managed (MARC-XCHPF), and the initial report selection was not by batch, a button “Batches” will allow the same material stock information to be displayed per batch. This is the same as the previous selection on MMBE but with the batch level selection switched on.
<Example Stock Type screen>
Batch Screen
The user will be presented with a list of all batches in stock for the material, based on the selection. If the storage location is handling unit managed, then a button “>” will also be available on the batch record, to allow branching to the Handling Unit screen for the selected batch.
The fields to be displayed for the handling unit are:
<Example Batch screen>
Handling Unit Screen
The user will be presented with a list of all handling units in stock for the material, based on the selection. Only the highest-level handling units are displayed so if a box is on a pallet only the handling unit for the pallet is displayed.
The fields to be displayed for the handling unit are:
<Example Handling Units screen>
A button “>” per HU, will allow branching to the Display HU transaction, covered in FS ERP-788.
EWM Stock Screen
The user will be presented with a list of all stock for the material in the EWM warehouse, considering earlier selections by material, storage location, batch, storage type, storage section and storage bin.
For HU managed materials, only the highest-level handling units are displayed so if a box is on a pallet only the handling unit for the pallet is displayed.
The fields to be displayed for the handling unit are:
When the empty bins option is used, this screen will also be displayed but only the empty storage bin information will be displayed.
<Example EWM Stock screen>
This app will be developed using Neptune DXP Open Edition. The app will appear on the Neptune launchpad.
See example screens in Functional Requirements section.
No special behavior required.
Standard navigation.
Stock data by storage location is selected from table MARD:
| Field | Table-Field Name | Comments / Calculation / Field Manipulation / Input / Output / Validation rule / Value help |
|---|---|---|
Material | MARD-MATNR | |
Plant | MARD-WERKS | |
Storage Location | MARD-LGORT | |
Unrestricted-Use Stock | MARD-LABST | |
Quality Inspection Stock | MARD-INSME | |
Blocked Stock | MARD-SPEME | |
Restricted Stock | MARD- |
Stock Data by batch is selected from table MCHB:
| Field | Table-Field Name | Comments / Calculation / Field Manipulation / Input / Output / Validation rule / Value help |
|---|---|---|
Material | MCHB-MATNR | |
Plant | MCHB-WERKS | |
Storage Location | MCHB-LGORT | |
Batch | MCHB-CHARG | |
Unrestricted-Use Stock | MCHB-LABST | |
Quality Inspection Stock | MCHB-INSME | |
Blocked Stock | MCHB-SPEME |
All quantities in tables MARD and MCHB are in the base unit of measure (MARA-MEINS)
IM HU information is selected from tables VEKP and VEPO:
| Field | Table-Field Name | Comments / Calculation / Field Manipulation / Input / Output / Validation rule / Value help |
|---|---|---|
EWM information is selected from table \SCWM\<>:
| Field | Table-Field Name | Comments / Calculation / Field Manipulation / Input / Output / Validation rule / Value help |
|---|---|---|
None
None
This app can be executed on a mobile device or in desktop mode.
Not applicable.
The user must have material document display access for the selected plant. Check object M_MSEG_WMB for Activity 03 and the selected plant. If no access, show the message "No authorization for plant <9999>".
Not applicable.
This solution will be used at approximately 100 plants. The total users is estimated to be around 800.
Errors to appear in a pop up window that needs to be acknowledged by the user.
| ID | Condition | Expected Result |
|---|---|---|
List any considerations essential for application test planning (e.g., test this before ABC along with DEF separate from GHI). If the development encompasses a user interface, explain how to test it. List any insights as to how this component could be tested the most efficiently.
| Package Name | Parent Package |
|---|---|
UI Type | UI Name | Fiori Catalogue | Design Rationale Reference |
|---|---|---|---|
| API Type | API Name | Purpose / High Level Logic | API Product | Design Rationale Reference |
|---|---|---|---|---|
| Object Type | Object Name | Purpose/High Level Logic | Design Rationale Reference |
|---|---|---|---|
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.