The visibility of the "Editable in full Contract Amendment" option within the field configuration's advanced tab is context-sensitive and depends on two primary factors.

First, this setting is specific to the contract amendment lifecycle. Therefore, it will only be displayed for fields that are part of the Contract Workspace (ariba.contract.core.Contract) or Contract Request (ariba.contract.core.ContractRequest) object classes. If the field belongs to any other object (e.g., Sourcing Project), this option is irrelevant and thus not shown.

Second, SAP Ariba distinguishes between standard (system) and custom fields. Many properties of standard fields are locked to maintain system integrity and ensure core processes function as designed. The ability to change editability during a critical process like an amendment is often restricted for standard fields, making this configuration option unavailable.

A. System-level configuration in a template is independent of the status of any single, transactional contract document. The available customization options do not change based on a specific contract being in an amendment state.

B. An in-flight customization might prevent saving or publishing new changes, but it would not typically cause a specific configuration option to be hidden from the user interface.

1. SAP Ariba Contracts Administration Guide: In the sections discussing contract workspace template administration and field configuration

it is specified that amendment-related field properties are exclusive to the contract business objects. The guide states

"Certain field properties are only available for certain types of projects." This supports the conclusion that the field must be in a contract-related class. (Reference: SAP Ariba Contracts Administration Guide

Chapter on "Contract Workspace Template Administration").

2. SAP Ariba Help Portal - "About Custom and System Fields": The official documentation consistently differentiates between the flexibility of custom fields and the restrictions on system (standard) fields. It notes that for system fields

"You cannot edit most of the properties... such as its name

field type

or whether it accepts multiple values." This restriction often extends to advanced behavioral properties like state-based editability. (Reference: SAP Ariba Procurement and Invoicing Help

Section on "Managing Custom and System Fields").

3. SAP Intelligent Configuration Manager (ICM) Documentation: The ICM documentation outlines the object-oriented nature of configurations. Properties available for configuration are dependent on the selected class (e.g.

Contract Workspace). The absence of an option indicates it is not applicable to the selected field's class or that the property is non-configurable for that specific field (a common case for standard fields). (Reference: SAP Ariba Intelligent Configuration Manager Guide

Section on "Field Configuration").