Unique system-generated identifier for the cycle plan adjustment record. This is used as the primary key.

Globally unique identifier for the adjustment entry, typically used for cross-system integrations and data reconciliation.

System-generated URL link to the full record in Veeva Vault. This is useful for navigation from external dashboards or integrations.

Descriptive name of the cycle plan adjustment entry, used for reporting and user identification.

Indicates the current status of the adjustment, such as Draft, Approved, or Archived. Drives visibility and workflow behavior.

Username or ID of the user who originally created the adjustment record in the system.

Timestamp of when the adjustment record was first created in the system. It reflects the initial creation date.

Username or ID of the user who last updated the adjustment record. This is useful for auditing and tracking changes.

Timestamp of the most recent update to the record, providing insight into last modification timing.

The actual value applied as part of the cycle plan adjustment, often representing real-world execution data or outcomes.

External identifier assigned to the adjustment record by an external system. This is used for data synchronization and reference.

Planned or expected value for the adjustment in the cycle plan. This is typically used for performance tracking against actuals.

Identifier of the user, team, or system that owns or is responsible for this adjustment record.

Reference to the identifier used in the legacy Customer Relationship Management (CRM) system prior to migration. Helps with backward compatibility and audits.