Description

Click to add the selected field to all field groups in the object.

Field groups are filters used to create subsets of data in a Target field. Rules, requirement settings, criticality levels and other settings can then be applied to these subsets of data.

A field can be extended to all field groups assigned to the object allowing this field to have a filter applied for every field group.

NOTE: If the Target's Design Status is Design Finished, Complete or Inactive, this icon is disabled.

This icon is disabled if the selected field is a zLegacy field.

Click to activate the selected field(s) for mapping.

When adding a field manually, the field is active by default.

When importing fields via a System Type import, all fields are configured as Inactive unless they are marked for active in the System Type.

Refer to Activate or Deactivate Target Fields for Mapping for more information.

NOTE: If the Target's Design Status is Design Finished, Complete or Inactive, this icon is disabled.

Click to deactivate the selected field(s) from mapping.

If a field is a key field and has the KEY FIELD check box enabled on the Target Fields page, the field cannot be deactivated. Uncheck the KEY FIELD check box before deactivating the field.

Refer to Activate or Deactivate Target Fields for Mapping for more information.

NOTE: If the Target's Design Status is Design Finished, Complete or Inactive, this icon is disabled.

Displays the name of the field group to which the field belongs. All fields are assigned to the default field group (*). Field groups are used to organize data to be able to apply different rules, criticality levels, requirements settings against each group depending on the values of data in a related field..

Refer to Work with Field Groups for more information.

Displays the name of the metric group to which the field is assigned. Metric groups are a subset of field groups. Metric groups are delineated into logical sets of fields that relate to a screen within the Target system. For SAP-related objects, the metric groups can represent the tabs within an SAP screen or TCode (for example, Customer Basic, Sales, Company and Accounting).

Refer to Work with Metric Groups for more information.

Displays the order of the field entered on the Target Fields page.

The order is used to sort the Field Mappings page in Map. Key and required fields are given a lower number (as in, a higher priority) than optional fields.

If checked, the field is active and can be used for mapping. If unchecked, the field cannot be used in mapping, and will not be pushed to Map when the Target design is synced.

When adding a field manually, the field is active by default.

When importing fields via a System Type import, all fields are configured as Inactive unless they are marked for active in the System Type.

Displays the field name.

This field cannot be edited for zLegacy fields.

Displays a description of the field that is provided by the ERP system.

Displays how the field is used. Values are:

• Natural – The field exists in the Target system. The system adds a “z” to the front of the field name used in the Source table.
• Utility – The field does not exist in the Target system, but can be used to register rules and reports to in Transform. Fields of this type should be captured in Target Design.  The user can choose whether this field should be mapped by using the Visibility field on the Vertical view.  A utility field is added to the Target table to be used by the AutoGen process.  Utility fields will be appended to BOTH the Target and Source table as is. No “z” field will be appended.

NOTE: A visibility can be set so that Utility fields can be mapped. Refer to Set Field Visibility for Mapping  for more information.

NOTE: By default, the visibility of a Utility field is set to NONE, except for zLegacy keys. zLegacy key fields will default to Source visibility. Refer to Allow Mapping of Utility Columns for more information.

NOTE: If the field is Natural, the Verify Post Load check box is enabled by default when a user clicks the Activate icon on the Page toolbar.

Displays the name of the check table to which a field belongs. Click the link to open the Target Lookup Table page to configure check table values.

Refer to Set up Lookup Tables for more information.

NOTE: This field cannot be edited for zLegacy fields.

Displays the Criticality level, which is used for reporting purposes. The platform is delivered with the values High, Medium, and Low. These values cannot be edited or deleted.

Custom criticality levels can be added, edited, and deleted.

Refer to Add Custom Criticality Levels for more information.

Displays the Requirement setting used for reporting. The platform is delivered with the following settings that cannot be edited or deleted.

• Technical Required—the ERP System cannot run without a value.
• Business Required—the Business requires this field to have a value.
• Conditional Required—based upon other field settings this field may or may not be required.
• Optional—this view is not required by ERP system or Business users.

This value displays on the Target Fields page (Design > Targets > Fields) in the REQUIRED list box.

If checked, the field is a key field on the table. If a field is a key field, the REQUIRED field is set to Technical Required, ACTIVE check box is enabled, and the CRITICALITY is set to High.

Key fields are created during field mapping. Key(s) on the Target table are created by using the key(s) from the Target system and the zLegacy field. For example, the MATNR field identified as the key field in Target Design is used to create the key field zLegacyMATNR on the Target table.

NOTE: This field cannot be edited for zLegacy fields.

The key field is added to the Target table when the table is created during SQL AutoGen.

If checked, the data should be verified after it is loaded into the Target system. This option is used with Natural fields only.

NOTE: The check box is automatically enabled for:

• A Natural field marked as a Key field on import
• A Natural field that is updated to have the KEY FIELD check box enabled

Click to open the Rules: Basic Rules page to add basic rules, logic conditions to apply to the data in the field. Basic rules are automatically generated and include binding criteria. Multiple basic rules can be added and are combined with AND.

This icon is disabled if the Target’s Design Status is Design Finished, Complete or Inactive.

Refer to Add a Basic Rule for more information.

If the field is a zLegacy field, Basic rules cannot be configured.

Click to open the Rules: Field Complex Rules page to add the documentation for a complex rule. Complex rules are not automatically generated.

Complex rules provide information that the Data Services developer uses when writing the rule. When an AutoGen request is processed, a placeholder where complex rules can be developed is created.

This icon is disabled if the Target’s design status is Design Finished, Complete or Inactive.

Refer to Add a Complex Rule  for more information.

NOTE: If the field is a zLegacy field, Complex rules cannot be configured.

Description

Basic

Displays the field name.

NOTE: This field cannot be edited for zLegacy fields.

Displays a brief description of the field that was either provided on import or entered manually.

Displays how the field is used. Values are:

• Natural – The field exists in the Target system. The system adds a “z” to the front of the field name used in the Source table.
• Utility – The field does not exist in the Target system, but can be used to register rules and reports to in Transform. Fields of this type should be captured in Target Design.  The user can choose whether this field should be mapped by using the Visibility field on the Vertical view.  A utility field is added to the Target table to be used by the AutoGen process.  Utility fields will be appended to BOTH the Target and Source table as is.  No “z” field will be appended.

NOTE: A visibility can be set so that Utility fields can be mapped. Refer to Set Visibility for Mapping of Target and Source Fields  for more information.

NOTE: By default, the visibility of a Utility field is set to NONE, with the exception of zLegacy keys. zLegacy key fields will default to Source visibility.  Refer to Set Visibility for Appended Utility Columns for more information.

NOTE: If the field is Natural, the Verify Post Load check box is checked by default when a user clicks the Activate icon on the Page toolbar.

Displays the Criticality level, which is used for reporting purposes. The platform is delivered with the values High, Medium, and Low. These values cannot be edited or deleted.

Custom criticality levels can be added, edited, and deleted.

Refer to Add Custom Criticality Levels for more information.

Displays the field’s requirement status.

Values are:

• Business Required—Required to meet a business rule or otherwise meet a business need.
• Technical Required—Required by the system
• Conditional—Required depending on certain conditions
• Optional—Not required.

Displays the name of the screen in the ERP system that contains the field. The value “Not Specified” indicates that the name of the application screen has not been entered.

NOTE: If using Target Design with Full Construction and the option to generate a Vertical View is selected in the Construct AutoGen Build View field on the Target Sources page’s Vertical View, this field is used to as the tab name on the Vertical View.

Refer to Use Target Design with Full Construction for more information.

Displays the label of the field as it appears on the screens in the ERP system.

Displays the name of the metric group to which the field is assigned. Metric groups are a subset of field groups. Metric groups are delineated into logical sets of fields that relate to a screen within the Target system. For SAP-related objects, the metric groups can represent the tabs within an SAP screen or TCode (for example, Customer Basic, Sales, Company and Accounting).

Refer to Work with Metric Groups for more information.

Displays the order the field displays on the screen in the ERP system.

NOTE: If using Target Design with Full Construction and the option to generate a Vertical View is selected in the Construct AutoGen Build View field on the Target Sources page’s Vertical View, this field is used to determine the order of the fields on the Vertical View.

Refer to Use Target Design with Full Construction for more information.

If checked, the field is active and can be used for mapping. If unchecked, the field cannot be used in mapping, and will not be pushed to Map when the Target design is synced.

When adding a field manually, the field is active by default.

When importing fields via a System Type import, all fields are configured as Inactive unless they are marked for active in the System Type.

If checked, the field is a key field on the table. If a field is a key field, the REQUIRED field is set to Technical Required, the ACTIVE check box is enabled, and the CRITICALITY is set to High.

Key fields are created during field mapping. Key(s) on the Target table are created by using the key(s) from the Target system and the zLegacy field. For example, the MATNR field identified as the key field in Target Design is used to create the key field zLegacyMATNR on the Target table.  

NOTE: This field cannot be edited for zLegacy fields.

The key field is added to the Target table when the table is created during SQL AutoGen.

NOTE: If using Target Design with Full Construction and the option to generate a Vertical View is selected in the Construct Auto Gen Build View field on the Target Sources page’s Vertical View, this field determines the key fields on the Vertical view.

Refer to Use Target Design with Full Construction for more information.

If checked, the data should be verified after is loaded into the Target system. This option is used with Natural fields only.

The check box is automatically enabled for:

• A Natural field marked as a Key field on import
• A Natural field that is updated to have the KEY FIELD check box enabled

If checked, the field is included in the insert rule built by SQL AutoGen that copies the field from the Source to the Target. This field is enabled by default for Utility fields added during the sync process.

If unchecked, during the sync process, this field is added to the Target and Source tables but is not included in the insert rule. For example, the zDuplicate field may need to be added to the Source or Target table, but not included in the insert rule.

NOTE: This check box displays for Utility fields only.

NOTE: It is checked by default.

NOTE: This field is for documentation purposes only.

Displays how the field is used in mapping and whether it displays on the Field Mappings page in Map.

Values are:

• Both—Mapping for Source and Target
• None—No mapping required for the field

NOTE: Natural fields cannot have a visibility set to None.

• Source—Source only mapping
• Target—Target only mapping

NOTE: If the field is Natural, the visibility is set to Both – Mapping for Source and Target by default. If the field is a key  zLegacy field, the visibility is set to Source – Source only mapping by default. If the zLegacy field is not a key field, the visibility is set to None by default.

NOTE: Visibility can only be set if the field’s Target is in a Design Status of In Design.

Details

Displays the name of the check table to which a field belongs. Click the link to open the Target Lookup Table page to configure check table values.

Refer to Set up Lookup Tables for more information.

NOTE: This field cannot be edited for zLegacy fields.

Displays the field’s data type, such as NVARCHAR or DECIMAL

NOTE: The data type of a field determines whether the Length and Decimal fields on this page are required. When the following data types are selected, the Length field is required:

• NVARCHAR
• DECIMAL
• NCHAR
• NVARCHAR

When the field’s data type is DECIMAL or DATETIME, the Decimal field is required.

Displays the field length, or the maximum allowable characters/numbers that the field can store. This field is required when the field’s data type is:

• NVARCHAR
• DECIMAL
• NCHAR
• NVARCHAR

Displays the decimal places allowed in the field.

When the DECIMAL or DATETIME data types are selected, the Decimal field is required.

Displays the format of the field used to validate the data in this field during Data Services AutoGen. Values are Date, Time and Decimal.

The Field Format works in conjunction with the Date Format, Time Format, and Decimal Format fields on the Targets page's Vertical View, where the actual format for data fields is stored.

For example, the Date Format for a Target is set at YYYYDDMM.

A user selects Date in the Field Format list box for the field Received By Date.

The data in the Received By Date field passes through the migration process with a data type of NVARCHAR. When validation rules are written for this field in Data Services AutoGen, the format of the Received By Date field is set as YYYYDDMM so that it can be loaded into the Target with no errors.  Refer to Set the Date, Time, and Decimal Formats for more information.

Description

Help and Documentation

Displays help text imported from the ERP system.

Displays a user-entered comment about the Target field.

This field is for documentation purposes only.

Displays instructions about how to use the field in mapping or other functions.

This field is for documentation purposes only.

Click Upload a file to upload documentation related to the Target field. If documentation has been uploaded, the Download a File icon is active, and the file can be downloaded. The Download a File icon is disabled if no documentation has been uploaded for the Target field.

Click to open the Rules: Basic Rules page to add basic rules, logic conditions to apply to the data in the field. Basic rules are autogenerated during Data Services AutoGen and include binding criteria, Multiple basic rules can be added and are combined with AND.

This icon is disabled if the Target’s Design Status is Design Finished, Complete or Inactive.

NOTE: If the field is a zLegacy field, Basic rules cannot be configured.

Click to open the Rules: Field Complex Rules page to add the documentation for a complex rule. Complex rules are not generated.

NOTE: Complex Rules are for documentation purposes only to describe what the Data Services developer needs to do. A placeholder will be created when an AutoGen request is processed. This is where complex rules can be developed.

This icon is disabled if the Target’s Design Status is Design Finished, Complete or Inactive.

NOTE: If the field is a zLegacy field, Complex rules cannot be configured.