Status
Owner	BROWN-ext, Kevin
Stakeholders	NARAHARI-ext, Bhargavi GARG-ext, Praful
Jira Request ID
Jira Development ID

High- Level Specification

Implementing System	Kinaxis Maestro
Invoked by/Invokes
Business Process Reference	04.04.06.01. Data provisioning ERP to Maestro

Functional Overview

The Account Manager table stores the Syensqo account manager information from SAP system and is assigned at Customer level in SAP system.

Scope and Objective

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

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

Process Flow Diagram

Step	Description
1	Global Integration Suite transfers transformed Composites / Rest of World data from S/4, and performs some formatting, and sends the data to Maestro.
2	China Integration Suite transfers transformed China data from S/4, and performs some formatting, and sends the data to Maestro.
3	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)
4	Files are moved to this SFTP server automatically, where they await loading into Maestro.
5	Maestro uses the configured DSM (Data Sources and Mapping) setup to load the data into the AccountManager table, with the load initiated either manually or through a scheduled system task.
6	The Data Tables which store information in Maestro

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:

Column Number	Field Name	Technical Field Name	Data Type	Key	Field Type	Description
1	Id	Id	String	Y	ExtractField	Account Manager ID from SAP
2	Name	Name	String	N	ExtractField	Account Manager Name from SAP
3	Email	Email	String	N	ExtractField	Email ID field for responsibility definition

File Formats

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

Data Model AccountManager table settings:

Allow Data update to:

Currency

Insert, Modify and Delete records

Insert and Modify records only

Allow automatic record creation

Determined by Maestro

Expression

-

Y

-

Data Model AccountManager custom fields:

Field name	Description	Data type	Key
Id	Account Manager ID from SAP	String	Y
Email	Email ID field for responsibility definition	String	N
Name	Account Manager Name from SAP	String	N
RRId	RapidResponse User Id	String	N
GBU	GBU Referenced table: GBU	Reference	N

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 Account manager is omitted from any of these loads, the Account manager 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 AccountManager table data have to be either loaded manually before loading theAccountManager table or at the same time as theAccountManager table is loaded or set to be created automatically in data model or in DSM.

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

Table	SyWay configuration
GBU	Set to allow automatic record creation

Volumetrics

Current APS Volume of Account manager records is 123,612. Because APS makes up approximately 60% of Syway projected records, an expected estimate for Syway is therefore 197,779

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 AccountManager-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 AccountManager-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

Package Name	Parent Package

Other Development Objects

Object Type	Object Name	Purpose/High Level Logic	Design Rationale Reference