Exploring Field Configuration Advanced Tab Overview

Objectives

After completing this lesson, you will be able to:
  • Explain the purpose of the Advanced tab
  • Explain availability of settings in the Advanced tab
  • Identify commonly used settings in the Advanced tab
  • Identify Best Practices and tips for settings in the Advanced tab

Purpose of the Advanced Tab

The Advanced tab is where additional field settings can be enabled or disabled by checking or unchecking the checkboxes.

Note, these settings are also referred to as templates in the class browser and field customization files are exportable through Intelligent Configuration Manager (ICM).

Availability of Settings in the Advanced Tab

The availability of settings in the Advanced tab is dependent on the class and field type you’re customizing. If a setting isn’t visible in the Advanced tab for a given field, it is by design. For example, if you’re customizing a field within a Sourcing Project, you won’t see Editable in full Contract Amendment in the Advanced tab because this setting is only relevant for fields in Contract Workspaces/Requests.

Default Settings in the Advanced Tab

When creating a new, Normal field, some Advanced settings are enabled by default.

Sourcing Default Settings – Normal custom fields

LabelDescription
Copy field during object copy and exportMake the field appear in the ObjectDuplicate and DumpLoad groups which are used for copying and exporting.
Sync in copied project on createMake the field in a project copy be copied from its original project when the project copy is created.
Sync with Word Documents on ChangeSynchronize this contract workspace field with the structured field property of the same name within assembled Microsoft Word documents in the workspace.
Enabled for Project Mass EditAllows the field to be edited in Project Mass Edit.
Enabled for AuditingAllows the field to be audited when the ClusterRoot implements the AuditableObject interface.

Procurement Default Settings – Normal custom fields

LabelDescription
Value Copied Over in Object DuplicationIn case a transaction (e.g. Requisition) is created as a copy of an existing one created in the past, the value is copied over to the new document. See How to prevent the value of a field getting copied to the copied PR and When I copy a document, how do I have the data on the document get copied over as well.
Enabled for AuditingAllows the field to be audited when the ClusterRoot implements the AuditableObject interface.

Enabled for Auditing should remain enabled for all fields. In most cases, the other default settings should remain enabled too. Although, the others can be disabled if the given functionality is not wanted.

Commonly Used Settings in the Advanced Tab

The tables below contain Advanced tab settings that are often requested and enabled on fields.

Syncing Field Values – Projects/Workspaces

LabelDescription

Sync in follow-on project on create

Make the field in a follow-on project be copied from its parent project when the follow-on project is created.
Sync in sub agreement on createMake the field in a subAgreement be copied from its master agreement when the subagreement is created.
Sync in subproject on createMake the field in a subproject be copied from its parent project when the subproject is created.
Sync in subproject on changeMake the field in a subproject be auto-pulled from its parent project whenever the field is updated in the parent project, including when the subproject is created.
Sync with Contract ComplianceSynchronize this field with Ariba Contract Compliance.
Sync User type field with Contract ComplianceSynchronize this field with Ariba Contract Compliance. Only for User type fields.
Continuous sync with documentSync this field continuously with the document field of the same name in the default locale. See Ability to synchronize fields between workspaces and documents for more information.

Note: In order for fields to sync, the field type and name must match.

Syncing Field Values – Documents

LabelDescription
Sync from project on createSync this field on creation from the project field of the same name in the default locale.
Continuous sync with parent workspaceSync this field continuously with the project field of the same name in the default locale. See Ability to synchronize fields between workspaces and documents for more information.
Prompt before synching the value to the projectPrompt before setting the matching project field to this field's value when the form is published or saved. This option is ignored if "Always sync the value from the savings form to the project" is set.
Always sync the value from the savings form to the projectUse this field template when you want to sync the value to Project. This value will be synced when you Save or Publish the SavingsForm.

Editability in Amendments

LabelDescription
Editable in full Contract AmendmentThis field can be edited as part of a full contract amendment.
Editable in Administrative Contract AmendmentThis field can be edited as part of an administrative contract amendment.
Editable in Contract Renewal AmendmentThis field can be edited as part of a contract renewal amendment.
Editable in Contract Termination AmendmentThis field can be edited as part of a contract termination amendment.
Editable in Price Update Contract AmendmentThis field can be edited as part of amendments of type "Price Update". The Price Update amendment type is similar to an administrative amendment but is intended to update price of a contract.

External Integration

LabelDescription
External Integration FieldExport this field in the reports/data file that are used for integration with an external system.
ERP Integration FieldThis field contains ERP data from external ERP system.
Transaction Push FieldA transaction field that can be exported to ERP. Not recommended for complex objects (master data drop-downs) or FMD fields.
External FieldA field that is received and sent to supplier via SAP Business Network. Note that adding this template should be consulted with Ariba representative (Technical Lead, Buyer Integrator). Template is neither recommended for FMD fields or for complex objects.
Allow field to be exported to SAP S/4HANAApplicable to 2NV or 3EN deployments. Select this option to send the associated field to SAP S/4HANA.

Only following normal-field types are supported:

  • Money
  • Boolean
  • Date
  • String
  • Big Decimal
  • Integer
See Error "null" when submitting the Requisition to S/4HANA for more details.
Include field for external tax calculationSelect this option to include the field in the external tax calculation request (if in scope).
Replace newlines with spaces on exportCauses this field to be exported without any newlines.
Include in Payment ExportsField becomes part of Payment Request (OK2Pay) export

Note

Including the field for Validation and Enrichment (see Documentation) is not currently available in Customization Manager.

Search Results

LabelDescription
Show this field as a column in document search resultsAllows the field belonging to document's parent workspace to be shown in search results.

How to Test:

  1. Go to SearchAny Document or SearchEvent
  2. Set Type filter (Sourcing Project, Contract Workspace (Procurement), etc.)
  3. Run your search and select the Table Options MenuShow / Hid ColumnsMore.
  4. Select the field OK.
Show as filter choice in View HierarchyMake this field available as a filter display option on the View Hierarchy screen (Tree View).

How to Test:

  1. Go toSearchContract Workspace(Procurement/Internal/Sales) and run your search.
  2. Select Tree View from the Table Options Menu.
  3. If the field isn’t appearing in the Results, select it in Table Options MenuShow / Hid Columns.

Miscellaneous

LabelDescription
Refresh screen on value changeRefresh the screen whenever this field changes.
Require value before PublishRequire value when publishing.
Use relationship chooserA field that uses the generic relation entry nametable
Enable for template Field SetterAllow field to be set by the Task Completion FieldSetter field, and also to be set by answering project template questions.
Show in Contract Term AttributesThis field is part of the Contract Term definition. Makes the field appear in the Contract Term Attributes section instead of the Contract Attributes section.
Allow label to wrap in formsAllow label to wrap in forms.
Hide LabelThe field label is hidden in the UI.
Hide this fieldThis field is hidden in the UI. In Procurement it is recommended not to use this template.
Include field in approval email notificationsSelect this option to include the associated field in approval emails.
View in shipping detailsSelect this option to display the associated field in the Shipping Details section.
Procurement Operations Desk fieldSelect this option to indicate that the field is associated with Procurement Operations Desk queue configuration or SLA configuration. For complex fields it’s recommended to use text field (representing ID) instead.
Chooser FieldUse this field as a column in drop-down choosers. This template is applied on the complex-field classes.
Has Custom Chooser GroupWhen enabled, in the field drop-down details you can see only fields with applied Chooser Field template in the "Advanced" Tab of the Class Browser/Editor. Note that in some environments (e.g. Guided Buying) this settings might be ignored.
Synchronize field value with tax, charge, and discount line fieldsSelect this option to ensure that the tax, charge, and discount line fields are updated based on the corresponding field in the parent (material or service) line.
Allow field to define Catalog item level constraints.Select this option to enable the associated field to be used to define constraints for filtering items from catalog search.
Add To User ImportField to be added to UserConsolidated.csv structure

Best Practices and Tips in the Advanced Tab

  • Using Hide this field template in the Procurement area is not recommended. Instead, the field should be hidden via Visibility condition)
  • Templates External Field and Transaction Push Field should not be used for complex fields (Master Data, FMDs). Instead, the value should be exported via a custom derived field.
  • When using any integration-related templates, it is recommended to accept all changes in Data Definition to reflect the changes in the file structure. If you are not familiar with how to accept Data Definition changes, see How do I review and accept changes to the data definition?.
  • Using External Field template should be consulted with a SAP Ariba representative (Technical Lead, Buyer Integrator) to avoid compatibility issues, as it requires a specific field name to be sent as an Extrinsic.
  • Take caution if enabling Sync in subproject on change. This setting will overwrite values in the subproject whenever the field is updated in the parent project.
  • Do not use the Allow edit after the project completion and/or Show in the project Template editorsettings unless the customer absolutely requires these functionalities for special custom fields. These settings are generally not needed or wanted.
  • Enable Refresh screen on value change if the field controls the visibility of another field.
  • Enable Allow label to wrap in forms if the field label length is long.

Log in to track your progress & complete quizzes