| Status | Approved |
|---|---|
| Owner | |
| Stakeholders | |
| Jira Request ID | |
| Jira Development ID |
High- Level Specification
| Implementing System | |
|---|---|
| Invoked by/Invokes | |
| Business Process Reference |
Functional Overview
The functional design of the system interface defines the API to be provided or consumed.
Scope and Objectives
Process Flow Diagram
Step | Description | Comment |
|---|---|---|
1 | The data coming from Salesforce is described in the Salesforce functional specification. It is NOT INCLUDED in this document. | N.A for OnHand |
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. | < Link to SAP S4 Spec> |
3 | Global Integration Suite transfers transformed data from S/4, and performs some formatting, and sends the data to Maestro. | <Link to Middleware spec> |
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. | |
Assumptions
Dependencies
Security, Integrity and Controls
Configuration Requirements
Special Requirements
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 |
|---|---|---|---|---|
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 |
|---|---|---|---|