Override permissions and audit log

Override permissions control which users can bypass compliance failures at each stage of the sales fulfillment process. Every override is recorded on the Specification Profile Override Log page for full auditability.

Configure override permissions

Override capability is controlled separately through the User Setup page in addition to the permission set.

1. Select the Search icon , enter User Setup, and then choose the related link.
   The User Setup list page opens.

2. Locate the user and enable the override flag:

Field	Description
Allow Specification Override	Allows you to override specification compliance failures at sales order entry, warehouse picking, and shipment posting.

3. Users without this flag enabled receive a hard error with no option to bypass.

Grant override permissions

1. Select the Search icon , enter User Setup, and then choose the related link.
   The User Setup page opens.

2. Locate the user (or create a new line with their User ID).

3. Enable the appropriate override flag(s) based on their role.

4. Close the page. The change takes effect immediately.

Authorized user override workflow

When you have override permission and encounter a compliance failure:

1. A confirmation dialog displays the failing attribute details.

2. You enter a mandatory override reason.

3. The lot or shipment is accepted and the override is recorded on the Specification Profile Override Log page.

Revoke override permissions

Return to User Setup, locate the user, and disable the relevant flag(s).

Specification profile override log

The Specification Profile Override Log page records every instance where an authorized user bypassed a compliance failure. Use it to audit all specification deviations across the sales process.

Open the log

Select the Search icon , enter Specification Profile Override Log, and then choose the related link.
The Specification Profile Override Log page opens.

Log fields

The following table describes the fields on the Specification Profile Override Log page.

Field	Description
Entry No.	A system-generated, auto-incrementing sequence number that uniquely identifies each override log entry. This value cannot be modified.
Override DateTime	The date and time when the override was recorded in the system. Captured automatically at the moment the user confirms the override.
Override Stage	Sales (lot assignment), Picking (warehouse pick), Shipping (shipment posting), or Lot (lot-level override).
Override User ID	The user who performed the override.
Source Type	The document type (for example, sales order or warehouse pick).
Source Subtype	The subtype classification of the source document. For example, a sales order may have subtypes like Order or Return Order.
Source ID	The document number of the source record, such as the sales order number or warehouse pick number. Use this value to navigate directly to the originating document.
Source Ref. No.	The specific line number on the source document where the compliance failure occurred. Together with the Source ID, this uniquely identifies the exact transaction line that was overridden.
Customer No.	The customer number from the source document. Identifies which customer's specification profile was being enforced at the time of the override.
Item No.	The item number that was being validated against the specification profile's attribute criteria when the compliance failure occurred.
Variant Code	The item variant code, if a specific variant was involved in the compliance check. This field is blank if the item does not use variants or if the profile applies to all variants.
Lot No.	The lot number that failed the compliance check and was overridden. This is the specific lot whose attribute values did not meet the profile's criteria.
Profile No.	The profile code (profile number) of the specification profile that was active and being enforced at the time the override was recorded. Use this to trace which set of criteria the lot failed against.
Compliance Type	The specific type of compliance check that triggered the override, indicating which category of validation rule the lot failed (for example, attribute range check or text match).
Compliance Details	Attribute name, actual value, and required filter (for example, "Moisture: 5.2, required: >2 & <\4").
Override Reason	The free-text reason entered by the authorized user when performing the override. This field is mandatory during the override process and serves as the primary audit justification for accepting a non-compliant lot.
Shipment No.	The posted shipment number associated with the override, if the override occurred during shipment posting. This field is blank for overrides that occurred during sales order entry or warehouse picking.
Posting Date	The posting date from the related source document. For shipment overrides, this is the shipment posting date. For sales and picking overrides, this reflects the document's posting date at the time of the override.

Impact on subsequent validations

Override entries are checked during later compliance stages to avoid repeated prompting:

• Profile unchanged since override: The lot passes silently at the next validation stage.
• Profile changed since override: Re-validation is triggered and a new override reason is required.