| Status | Approved |
|---|---|
| Owner | |
| Stakeholders | |
| Jira Request ID | |
| Jira Development ID |
High- Level Specification
| Implementing System | |
|---|---|
| Invoked by/Invokes | |
| Business Process Reference |
Functional Overview
The OnHand table stores inventory quantities and associated attributes for a part at a specific location within a warehouse. It represents the inventory position used by Maestro for planning, allocation, and pegging activities and is synonymous with inventory.
When on-hand inventory is allocated to demands for pegging, higher-priority demands are protected. If no priority is defined, on-hand inventory for a part is consumed based on the following attributes, in order:
- Expiry date (earliest first)
- Date (earliest first)
- Unit cost (lowest cost first)
- Quantity (smallest quantity first)
- Location identifier and warehouse
Scope and Objectives
The scope of this interface is between Global Integration Suite and Maestro. This document includes details of the OnHand.tab object.
The objective is to populate the OnHand and it's referenced tables based on the file provided by Global Integration Suite.
Process Flow Diagram
draw.io
/display/ER/System+Interface+-+Reference+Specification+for+Maestro
Step | Description | Comment |
|---|---|---|
1 | The data coming from Salesforce is described in the Salesforce functional specification. It is NOT INCLUDED in this document. | Salesforce Spec Link |
2 | The data coming from S/4 is mostly transformed within S/4, to ensure the data is in the format for Maestro. Details are NOT INCLUDED in this document, but are contained in the S/4 functional specification. | Functional Spec Link |
3 | Global Integration Suite transfers transformed data from S/4, and performs some formatting, and sends the data to Maestro. | |
4 | Transferred files will be sent to Maestro’s Client SFTP server. This sits outside of the Maestro firewall and is accessible by client using a user id/ password. Files are transferred from this component to the Planning Server SFTP by a Kinaxis automatic process once the trigger file has been placed (see below) | |
5 | Files moved to this SFTP server await loading into Maestro by a scheduled script triggered from within Maestro. | |
6 | Maestro uses the configured DSM (Data Sources and Mapping) setup to load the data into the OnHand table, with the load initiated either manually or through a scheduled system task. | |
7 | The Data Tables which store information in Maestro |
Assumptions
See Assumptions section in System Interface - Reference Specification for Maestro.
Dependencies
See Dependencies section in System Interface - Reference Specification for Maestro.
OnHand specific Dependencies include:
Reference tables to support OnHand table data have to be either loaded manually before loading the OnHand table or at the same time as the OnHand table is loaded or set to be created automatically in data model or in DSM. Below tables need to be taken into account before OnHand table data load:
Table | SyWay configuration |
Batch | Set to allow automatic record creation |
Location | Set to allow automatic record creation |
Model | Not needed in SyWay. Picks Maestro default value - None |
Pool | Not needed in SyWay. Picks Maestro default value - Unpooled |
HoldType | Set to allow automatic record creation |
Security, Integrity and Controls
See Application Architecture - Maestro for security requirements for SFTP/REST based authentication and security.
Configuration Requirements
The Data Sources and Mapping for this interface should be configured once, according to the structure in the Data Structure section below.
The Data Model needs to be configured with the Syway-specific fields shown in the Data Model Custom Fields section below.
Special Requirements
None
Design Rationale
API Use
Data Structure
The following fields will be used to provide the required data structure of the interface:
| Parent | Field | Description | Mandatory (Y/N) | Data Type |
|---|---|---|---|---|
Data Model custom fields:
Calculation and Validation
| Parent | Field | Rule Type | Rule Instruction |
|---|---|---|---|
eDocument mapping
| General | Syensqo XML (Intermediate Target) | SAP eDoc Standard Mapping (Source) | Custom Mapping (Source) | |||||||
|---|---|---|---|---|---|---|---|---|---|---|
| S-NR | Flow (SD/FI/MM/ALL) | Target Field | Target Field Details | Condition | Syensqo XML Node | Syensqo XML Field | SAP eDoc Standard Node | SAP eDoc Standard Field | Fixed Value | Custom Logic |
Processing Logic
Delta or Full Load Requirements
Interface Alert & Monitoring
Language Requirements
User Interface Requirements
Sequencing
Volumetrics
Performance Consideration
Error Handling
Testing
How to Test
Test Conditions and Expected Results
| ID | Condition | Expected Results |
|---|---|---|
Test Considerations/Dependencies
Other Information
Development Details
Package
| Package Name | Parent Package |
|---|---|
Other Development Objects
| Object Type | Object Name | Purpose/High Level Logic | Design Rationale Reference |
|---|---|---|---|