High- Level Specification

Functional Overview

A Customer is a consumer of an independent demand item and may be a consumer, a distributor, service center, or a plant identifier for inter-plant orders.

Scope and Objectives

The scope of this interface is between Global Integration Suite and Maestro. This document includes details of the Customer.tab object. 

The objective is to populate the Customer and it's referenced tables based on the file provided by Global Integration Suite.

Process Flow Diagram

Assumptions

See OnHand.tab System Interface document for assumptions.

Dependencies

See OnHand.tab System Interface document for dependencies.

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

The base of this design has been taken from the existing Maestro implementation, as designed during the Advanced Planning System (APS) Project. 

A fit-gap analysis was undertaken within Syway, and changes were identified which have been incorporated into the Syway spec as shown.

API Use

The data object provided by either Integration Suite will be consumed by Maestro.

For more information see the Data Integration Document.

Data Structure

 The following Maestro fields will be populated by the file provided by Integration Suite:

File Formats 

See File Formats - SFTP section in the Data Integration Document.

Data Model Customer table settings:

Data Model Customer custom fields:

Processing Logic

See Processing Logic - SFTP section in the Data Integration Document.

Delta or Full Load Requirements

This file will be a Full Load, sent 3 times a day, so the file has been loaded at the beginning of day for each global region. If Customer is omitted from any of these loads, the Customer data within Maestro will be unchanged.

For more information on the difference between Full and Delta loads, see the  Full Loads and Delta Loads - SFTP section in the Data Integration Document.

Interface Alert & Monitoring

See the Interface Alert & Monitoring - SFTP section in the Data Integration Document,

Language Requirements

None

User Interface Requirements

Not required.
 

Sequencing

Reference tables to support Customer table data have to be either loaded manually before loading the Customer table or at the same time as the Customer table is loaded or set to be created automatically in data model or in DSM.

Below tables need to be taken into account before Customer table data load:

Volumetrics

Current APS Volume of Customer records is 32,978. Because APS makes up approximately 60% of Syway projected records, an expected estimate for Syway is therefore 52,765

This value is expected to grow by 1-2% per year. 

Performance Consideration

N/A

Error Handling

See Interface Alert & Monitoring section. 

Testing

How to Test

See OnHand.tab System Interface document for information on how to test.

There are no Customer-specific testing requirements.

Test Conditions and Expected Results

See OnHand.tab System Interface document for information on test conditions and expected results.

There are no Customer-specific test conditions.

Test Considerations/Dependencies

Dependent files should already be loaded into Maestro for these tests to complete. See Sequencing section above. 

Other Information

Development Details

Package

Other Development Objects

Appendix

See also

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.

Change log