Standard Fields

Sequence of the standard fields. Value increases by factor of 10 for each new entry.

Name of the standard field.

The description for this standard field.

The format of the standard field. Ex: NVARCHAR, INT, NUMERIC, DATE

The max number of characters for this standard field.

The number of decimal places for the field.

The toggle that identifies this standard field as used for Targets.

Identifies the original source of every record in the Working and Target Tables.   Defaults to the name of the Datasource without the src or tgt Prefix.

It should be carefully chosen to identify the source system using the common name for the system which can be easily recognized by the Validators. 

Ex: JDE, MAXIMO, ECCNA, ADAGE

Used in working table, target table

Segregates the Validation Reports and ENRICH data in Releases that support multiple Business Units.   Values must be pre-defined at the start of the release and are based solely on how the project intends to Validate and Cleanse the Legacy Data.   Most often this field represents Countries, Business Units, or Site Locations.

Ex: US, CAN, MEX or S10, S20, S30.  

If a Release only contains one logical deployment, it can be named like the Release for simplicity.

Used in the working table, target table

Flags the Critical Master Data as defined during the mapping sessions.  For example, top 100 Customers by sales, or top 100 Materials by Transactions, etc.

The Critical Flag is carried down to the Transactional Data based on it having a Critical Master Data item.   So a Critical PO would have a Critical Vendor or Critical Material.

The Purpose of the field is to allow the Pre and Post load validation teams to focus on the "Critical" records in order to shorten the validation time, and insure that the most important record will be converted correctly.   

Used in the working table, target table

Identifies the Datasource of the "Winning" record as duplicates can be found across multiple data sources (inter-source duplicates)

Used in the working table 

Identifies a Duplicate Record in the Working table by referencing the "Winning" record that is relevant. Record which have DUPLICATE_OF populated generally is flagged as NOT ACTIVE so they are not inserted into the Target Table.

Used in the Working Table

A concatenated list of ERROR MESSAGES from the Error Report registrations.  Used to identify all the errors in a given Record in a single field

Ex:  Invalid Postal Code, Missing Phone, PO Box on Ship To

Populated by the Validation Reports automatically.

Used in the Target Table

A concatenated list of reasons why a record was marked as Not Active (not relevant).   Often used in addition to common Relevancy Flags (zPO, zOpenPO, zNew, zInventory, etc)

Used in the Working Table

Identifies records which were Loading during the current load cycle.  Used for Post Load metrics and Delta Loads if needed.

Used in the Target Table

Data Time the record was loaded, useful for Post Load metrics and Project Planning.

Used in the Target Table

Identifies records which contain a non-critical Data Error which does not prevent the record from loading.  Populated based on the Data Readiness Error Reports.

Ex:  Missing a Phone Number.

Used in the Target Table

Identifies records which can be loaded, but should not due to missing business required field values.

Ex:  Missing a custom added field value.

Used in the Target Table

Identifies records which contain a Critical Data Error which prevents the record from loading, based on information available BEFORE the start of the data loads.  Populated based on the Stage Readiness Error Reports.

Ex: Missing Required Fields, Invalid Configuration Values, Missing Master data based on errors in upstream Staging Tables (not in wrkMM.dbo.MM_MARA_T)

Used in the Target Table

Identifies records which contain a Critical Data Error which prevents the record from loading, based on information available only AFTER the start of the data loads.  Populated based on the Target Readiness Error Reports.

Ex: Missing Master Data in the Target System (not in tgtECC.dbo.MARA)

Used in the Target Table

Integer field used in partitioning of the Export file to support Parallel Loading.  Defaults to 1.   To create 4 load files, populate each record with a 1,2, 3, or 4.   For Header/Detail targets it can be important to copy the CHUNK from the parent record (so PO Lines Items have the same chunk as the PO Header)

Used in the Target Table  

Identifies records that already exist in the target system prior to loading data.  Applies to mergers and acquisitions, or multi-release projects where loads are into an existing Production System that already contains common master data items.

Used in the Target Table

This flag shows that the row has been remediated for one or more fields to make it successful to load.   Used for Load Metrics reporting.

Populated by the Validation Reports automatically.

Used in the Target Table

Name of the Standard Field. (Required)

The description of use of the standard field.

Sequence of the Standard Fields in the table. Value increases by factor of 10 for each new entry. (Required)

The format of the standard field. Ex: NVARCHAR, INT, NUMERIC, DATE

The max number of characters for this standard field.

The XML scripting to use this standard field.

The XML format for this standard field. Ex: datatype="VARCHAR" size="MAX" nullable'"true"

The SQL format for this standard field. Ex: NVARCHAR(MAX).

Enter the value that may be defaulted for this standard field.

Toggle to mark this standard field as Active/Inactive for a Primary Key field.

Toggle to mark this standard field as Active/Inactive for use on the Source staging table.

Toggle to mark this standard field as Active/Inactive for use on the Target table.

Toggle to mark this standard field as Active/Inactive for Relevant for mapping.

Toggle for status of Standard Field as active/inactive for conversion.

Note

Defaults as Active.

Select from drop-down to mark this standard field as active or inactive for mapping.