1

Global Integration Suite transfers transformed Composites / Rest of World 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 PartCustomer table, with the load initiated either manually or through a scheduled system task.

6 

The Data Tables which store information in Maestro

0

ControlSet

DemandType.ControlSet.Value

String

N

Fixed

No

The control set associated with this demand type record

0

DemandType

DemandType.Value

String

N

Fixed

No

The demand type values from source system

0

Active

Active

Boolean

N

Fixed

No

Flag for Partcustomer based on hitory and forecast criteria. Default value Y will be shown in DP workbooks

1

Customer

Customer.Id

String

Y

Extract

No

The customer associated with the historical demand series and/or forecast.

2

PartSite

Part.Site.Value

String

Y

Extract

No

The site associated with this part. 

3

Part

Part.Name

String

Y

Extract

No

The part associated with the historical demand series and/or forecast.

4

EndUse

EndUse.Id

String

N

Extract

No

EndUse

5

ProcessingRule

ProcessingRule.Id

String

N

Extract

Yes

Processing rule associated with the part-customer

6

GBUSegment

GBUSegment.Id

String

N

Extract

Yes

GBUSegment

7

OriginalShipToKA

OriginalShipToKA.Id

String

N

Extract

No

Original Ship To KA from interface

7

ShipToKA

ShipToKA.Id

String

N

Extract

No

ShipToKA

8

IncoTerm

IncoTerm.Id

String

N

Extract

Yes

Incoterm of the part-customer

9

IncoTermDelivery

IncoTermDelivery.Id

String

N

Extract

No

Information for demand planners in determining the supply offset ETA-ETD, or for finance teams in calculating the revenue recognition date.

10

IsConsignment

IsConsignment.Id

Boolean

N

Extract

No

Flag  to identify Consignment Part-Customers

11

FinalConsignee Id

FinalConsignee.FinalConsigneeid

String

N

Extract

Yes

FinalConsigneeId

12

FinalConsignee Name

FinalConsignee.FinalConsigneeName

String

N

Extract

No

FinalConsigneeName

Field name

Description

Data type

Key

Account18DID

 Attribute used for hierarchies

String

N

Active

Flag for Partcustomer based on hitory and forecast criteria. Y will be shown in DP workbooks and N will not be shown in DP workbook

Boolean

N

BlockOffset

Used in the ETA ETD translation

Quantity

N

CreationDate

Internally used to record the date the record is created in Maestro

Date

N

DeleteNotes

Internally used as a flag for the user to mark to delete the notes

Boolean

N

IncoTermDelivery

Information for demand planners in determining the supply offset ETA-ETD, or for finance teams in calculating the revenue recognition date.

String

N

IsCondignment

Flag set to Y for Consignment Part-Customers

Boolean

N

MarketGrowthProgram

Attribute used for hierarchies

String

N

Notes

User notes in Maestro

Note

N

OverrideFinancialOffset

Populated by users in Maestro to override the financial offset

Quantity

N

OverridenDate

Stores the latest date where sales forecast and demand planner forecast category has been overriden in the previous demand planning cycle.

Date

N

OverrideTransitTime

Populated by users in Maestro to override the transit time

Quantity

N

PredecessorSelection

Used internally to create predecessor relationship- NPI / EoL 

Boolean

N

SavedActive

Internal use to identify transitional active flags and to identify where the user has changed the flag to run an automation. Where you activate a PartCustomer to be used for Forecasting (Demand Plan). Field used to compare previous and current active flags. 

Boolean

N

SavedDisaggregationEndDate

Internal use to identify when a user changes the date and an automation will runRelating to activating the PartCustomer. DisaggregationEndDate = End of life. This field is the old date to compare, to detect when changes have been made.

Date

N

SuccessorSelection

Used internally to create successor relationship

Boolean

N

UserId

internally used to record the user that created that record

String

N

WetRation

Ratio to convert the units to wet ratio. Convert forecast from dry/wet ratio for MTP

Quantity

N

BusinessLine

Attribute used for hierarchies. Used for composites, set by user, maintained in Maestro

Reference

N

EndUse

EndUse

Reference

N

FinalConsignee

FinalConsignee

Reference

N

FinalCustomerParent

Attribute used for hierarchies

Reference

N

GBUSegment

GBUSegment

Reference

N

IncoTerm

Incoterm of the part-customer

Reference

N

MainShipToCountry

Attribute used for hierarchies

Reference

N

MfgPlant

Attribute used for hierarchies

Reference

N

OriginalShipToKA

Original Ship To KA from interface

Reference

N

OverrideAccountManager

Internal use to override the account manager Changes made in Maestro for “now”, then later synced

Reference

N

OverrideForecastCustomer

Internal use to override the forecast customer. From ERP it comes into customerShipTo - this is an override.

Reference

N

ProcessingRule

Processing rule associated with the part-customer

Reference

N

Segmentation

Attribute used for hierarchies. Planners assign PartCustomers to segment

Reference

N

Data Load Successful

Data File contains 0 records

The Data Update should fail with a status of Pending. 

Data File contains invalid references (or other error)

The Data Update should Fail, the invalid references should be visible in the error log and the records with the error are not loaded into Maestro, and an alert is sent to the Admin team <Or whatever action is needed>

Fields for OnHand.tab which should be checked for invalid references are shown in the Data Structure table above as "Ref String" and are: 

Data file contains duplicates

The PartCustomer.tab file must be checked further for data uniqueness with respect to the key fields, in case data is available in file but not in Maestro