Golden Rules

Forecast and User models

• User models in DP

• User model naming

For technical user model = x. User model name

For specific GBU user model = y. GBU User Model

For process user model = z. User model name 

Datatable

> Datable should not contain more than 30 datafields.

• Datatable naming

Generic Data Table 

DataTable = User model | Datatable name

Examples : 

F1C.1 Material:ShipTo@DC | Forcing Loop (ETD)

• Master Table Update 

Data Table = Master Tables Update | Masterdata - "dimension" level

Example : 

Master Tables Update | Business Customer - Material:Forecast Customer@Spec level

• Import/Export Datable 

Import and Export Model Objects Naming

• Data Table = Import/Export | "System" - "dimension" level
• Data fields = "Data" (same name as the input at DFU L2 level)
• Calculations = Import/Export | 0x0. "Data Table Name" | 00x.  "Data" ["All GBUs/GBU", "Past/Future/(Start - End)"]

Note: calculations should be added to the model where the output has been created.

Calculation Naming

Calculations = Datatable name (of output data) |  00x. "Data"  ["All GBUs/GBU", "Past/Future/(Start - End)"]

Note: calculations should be added to the model where the output has been created.

Views Naming

When creating views in a workspace use the correct naming scheme. 

Each view name should be prefixed by GBU Code | Tab Name (in the Workspace) | Grid View Name. 

Please see example below:

Conditions Naming

Conditions Naming must be coherent in order to find them quickly on a list. Conditions might be grouped and so naming should start identically as well.

Linked to DFUs Management

• 'Active "data" | All GBUs' = for all Active DFUs L1/L2 in the data base.
• 'Active "data" | CM' = for Active DFUs L1/L2 only for GBU Composites.
• 'Planned "data" | All GBUs' = for to all Planned DFUs L2 in the data base.

Note - in order to avoid any confusion:

• if your condition is directly linked to Material:Shipto:Spec@DC or Material:ForecastCustomer@Spec Master Tables as parent, you must specify "DFUs L1" or "DFUs L2"
• if your condition is for all DFUs, you must specify "| all GBUs" whereas if your condition is for one specific GBU, you must specify the GBU code "| CM" (example for Composites).

Linked to Users Management

• 'Demand Planners - "Name"' = for Demand Planners.
• 'CM - FAM - "Country Code" / "Name"' = for Account Managers.
• 'CM - RSM - "Country Code" / "Name"' = for Regional Sales Managers.
• 'SC1/2/3-"Name"' = for PMI users.
• 'PMI Admin. - "Name"' = for PMI Admin.

Note: refer to this section Composites User Management for more details.

Linked to BAAN vs SAP processes

• 'SAP "data"' = for filtering on SAP or on non-SAP data exclusively.
• 'BAAN/PE1 "data"' = for filtering on mixte DFUs L1/L2 exclusively. 

Note: BAAN/PE1 data has been imported into DynaSys for complete S&B picture: they should not be less and less used (to none). Refer to this section Mass Cleaning Process for more details.

Linked to Composites Specific Processes

For specific processes, there is no regular rules except:

• generally, condition can follow this scheme '"Master Table Name" - "Entry"' (example of Market 1 - Engines);
• when condition is fed by a data field, the name must match (example of "No Forecasting Flag").

Sequences Naming

Sequences ran by Interfaces

Each sequence must be named based the following scheme:

• on which batch will launch it: [STATIC IMPORT] or [DYNAMIC IMPORT].
• on which frequency: [DAILY] or [WEEKLY] or [MONTHLY].
• on which scope: [AERO] or blank.
• on which related topic.

Sequences ran Manually

Each sequence must be named based on the following scheme: ["code GBU"] "Topic".

Master Table Update Model Objects Naming

• Data Table = Master Tables Update | "Data Override" - "dimension" level
• Data fields = "Data Override" from Hierarchy/Override/Final
• Calculations = "Data Override" at "dimension" level | 0x. "Output Data field"

Import and Export Model Objects Naming

• Data Table = Import/Export | "System" - "dimension" level
• Data fields = "Data" (same name as the input at DFU L2 level)
• Calculations = Import/Export | 0x0. "Data Table Name" | 00x. ["All GBUs/GBU", "Past/Future/(Start - End)"] "Data"

Note: calculations should be added to the model where the output has been created.

Continuous Cleaning

In order to prevent any regression, objects should be deactivated and then deleted. It is a two-steps process done on each Monthly Release. Deactivation and deletion should be done on a monthly basis based on promoted evolutions and analyzed processes.

• Deactivation step: right click on the object and select "Deactivate"; and/or rename the object with "zzz" at the beginning (depending on the object, both actions are mandatory or only the renaming one);
• Deletion step: right click on the object and select "Delete" (if "Delete" is grey out, it means that it can't be deleted because it is still linked to other active objects. In this case, the whole process needs to be re-analyzed).

Each Monthly Release should start by deleting all the deactivated objects from last Monthly Release. Then, while promoting evolutions, other objects might be deactivated. They will be deleted on the next Monthly Release. 

Note: beware deletion is a definitive action which should be used wisely.