Purpose
In exceptional situations, an OBP may need to temporarily prevent dispensing of product packs belonging to a specific batch.
LOCKED state is reversible and can be removed once the issue has been resolved.
Important Considerations
A batch may contain a mix of:
ACTIVE packs
SUPPLIED packs
EXPORTED packs
DESTROYED packs
Other decommissioned packs
Applying a lock to all packs without first identifying the ACTIVE population may result in alert generation for packs that have already undergone a valid decommissioning transaction.
Before performing a bulk lock operation:
Only ACTIVE product packs should be targeted.
Attempting to lock packs that have already been decommissioned (for example SUPPLIED, CHECKED-OUT, EXPORTED, DESTROYED, STOLEN, SAMPLE or FREE SAMPLE) may result in alerts or transaction failures.
EMVO strongly recommends validating the operation on a single product pack before initiating a bulk transaction.
There is no predefined time limit for the LOCKED state.
Locked packs can be identified through Pack Verification or Bulk Pack Verification transactions.
Procedure to Lock a Batch
Step 1 – Perform a Bulk Pack Verification
Execute a Bulk Pack Verification transaction for the product packs belonging to the affected batch. This allows identification of the current pack states before any state change is performed.
Step 2 – Identify Eligible Product Packs
Review the verification results and select only product packs with an effective pack state of:
ACTIVE
Exclude any packs that are already:
SUPPLIED
CHECKED-OUT
EXPORTED
DESTROYED
STOLEN
SAMPLE
FREE SAMPLE
LOCKED
Only ACTIVE product packs should be included in the bulk state change file.
Step 3 – Validate with a Single Pack State Change Transaction
Before initiating a bulk operation:
Select one ACTIVE product pack from the batch.
Submit a Pack State Change Transaction.
Set the target pack state to:
LOCKED
Confirm that:
The transaction is successful.
No error is returned.
No unexpected alert is generated.
Proceed with the bulk operation only after successful validation.
Step 4 – Execute the Bulk Pack State Change Transaction
Submit a Bulk Pack State Change Transaction for all remaining ACTIVE product packs identified in Step 2.
Target state:
LOCKED
The selected product packs will be updated from ACTIVE to LOCKED.
Step 5 – Verify the Result
Perform a follow-up Bulk Pack Verification to confirm that all intended product packs now have the pack state:
LOCKED
Retain the verification and transaction results in accordance with your internal procedures.
Procedure to Unlock a Batch
When the reason for the lock no longer exists, the affected product packs may be returned to ACTIVE status.
Step 1 – Perform a Bulk Pack Verification
Execute a Bulk Pack Verification for the affected batch.
Step 2 – Identify Locked Product Packs
Review the results and select only product packs with pack state:
LOCKED
Only LOCKED product packs should be included in the reactivation process
Step 3 – Validate Reactivation on a Single Product Pack
Select one LOCKED product pack.
Submit a Pack State Change Transaction.
Set the target state to:
ACTIVE
Confirm that:
The transaction is successful.
No error is returned.
No unexpected alert is generated.
Proceed to the bulk operation only after successful validation.
Step 4 – Execute the Bulk Pack State Change Transaction
Submit a Bulk Pack State Change Transaction for all remaining LOCKED product packs identified in Step 2.
Target state:
ACTIVE
All eligible product packs will be reactivated.
Step 5 – Verify the Result
Perform a final Bulk Pack Verification to confirm that the affected product packs now have the pack state:
ACTIVE
Recommended Operational Sequence
For both locking and unlocking activities, follow the same process:
Bulk Pack Verification
Filter the packs to the intended population:
ACTIVE packs for locking
LOCKED packs for unlocking
Execute a single Pack State Change Transaction as a validation step
Execute the Bulk Pack State Change Transaction
Perform a final Bulk Pack Verification
Following this sequence minimizes the risk of generating unnecessary alerts and helps ensure that only the intended product packs are affected.
OBP Checklist: Locking All Active Product Packs in a Batch
Pre-Execution Checks
☐ Confirm that a temporary LOCKED state is appropriate and that a regulatory Recall is not required.
☐ Identify the affected batch.
☐ Ensure you have the list of Product Packs belonging to the batch.
☐ Confirm that the operation will be executed using a Pack State Change Transaction / Bulk Pack State Change Transaction.
Phase 1: Identify Eligible Packs
Step 1 - Bulk Pack Verification
☐ Execute a Bulk Pack Verification transaction for all Product Packs in the batch.
☐ Export or review the verification results.
Step 2 - Filter Eligible Packs
☐ Identify Product Packs with pack state ACTIVE.
☐ Exclude Product Packs with any other state.
☐ Verify that only ACTIVE Product Packs remain in the target list.
⚠ Important: Including non-ACTIVE packs may result in alerts or transaction failures.
Phase 2: Validate the Lock Operation
Step 3 - Single Pack Test
☐ Select one Product Pack from the filtered ACTIVE population.
☐ Submit a Pack State Change Transaction.
☐ Set the target pack state to LOCKED.
☐ Verify that the transaction is successful.
☐ Verify that no error message is returned.
☐ Verify that no unexpected alert is generated.
☐ Confirm that the Product Pack state is LOCKED.
Go / No-Go Decision
☐ Proceed only if the single-pack test completed successfully.
Phase 3: Bulk Lock
Step 4 - Bulk Pack State Change Transaction
☐ Prepare the input file containing only ACTIVE Product Packs.
☐ Execute a Bulk Pack State Change Transaction.
☐ Set the target pack state to LOCKED.
☐ Monitor transaction results.
☐ Confirm successful processing of all submitted Product Packs.
Phase 4: Post-Execution Verification
Step 5 - Confirm Results
☐ Execute a follow-up Bulk Pack Verification.
☐ Confirm that intended Product Packs now have pack state LOCKED.
☐ Review any exceptions, errors, or alerts.
☐ Retain transaction and verification reports in accordance with company procedures.
OBP Checklist: Unlocking Product Packs in a Batch
Phase 1: Identify Locked Packs
Step 1 - Bulk Pack Verification
☐ Execute a Bulk Pack Verification transaction for the affected batch.
☐ Review verification results.
Step 2 - Filter Eligible Packs
☐ Identify Product Packs with pack state LOCKED.
☐ Exclude all Product Packs with other states.
☐ Verify that only LOCKED Product Packs remain in the target list.
Phase 2: Validate the Unlock Operation
Step 3 - Single Pack Test
☐ Select one LOCKED Product Pack.
☐ Submit a Pack State Change Transaction.
☐ Set the target pack state to ACTIVE.
☐ Verify that the transaction is successful.
☐ Verify that no error message is returned.
☐ Verify that no unexpected alert is generated.
☐ Confirm that the Product Pack state is ACTIVE.
Go / No-Go Decision
☐ Proceed only if the single-pack test completed successfully.
Phase 3: Bulk Unlock
Step 4 - Bulk Pack State Change Transaction
☐ Prepare the input file containing only LOCKED Product Packs.
☐ Execute a Bulk Pack State Change Transaction.
☐ Set the target pack state to ACTIVE.
☐ Monitor transaction results.
☐ Confirm successful processing of all submitted Product Packs.
Phase 4: Post-Execution Verification
Step 5 - Confirm Results
☐ Execute a final Bulk Pack Verification.
☐ Confirm that intended Product Packs now have pack state ACTIVE.
☐ Review any exceptions, errors, or alerts.
☐ Retain transaction and verification reports in accordance with company procedures.