Loading

Product Lifecycle Events

A Product Lifecycle Event records something that happened to a batch or physical product instance: manufacture, inspection, receipt, shipment, transfer, service, replacement, repurposing, rebuilding, or recycling.

For example, battery 000042 was manufactured at Factory North and later received at Warehouse West. A receipt event can establish its present location without changing its manufacturing factory.

Time, acceptance, and current state

Occurred At identifies the actual event time. Reporting time records when Actualog received the report. A late report is placed in the effective history; it does not override a later location merely because it arrived last.

New events are Pending. Accepted events become Approved and participate in current location, custody, and lifecycle projections. Rejected events remain inspectable without establishing current state.

Who reports and accepts events

A Production Manager, Company Administrator, or user with accepted event-management delegation reports and accepts events in the permitted scope. Record the real performer and custodians; they can differ from the administering company and current user.

Record and accept an event

  1. Open Logistic → Production → Product Lifecycle Event, search existing reports, and choose + Create new lifecycle event.
  2. Select exactly one batch or instance, the event type, occurrence time, and performer.
  3. Add applicable from/to facilities, from/to custodian companies, quantity, and unit. Select entities by their displayed names.
  4. For an individual item's repurposing or rebuilding, select its resulting approved Configuration Release when applicable.
  5. Create the event. In Lifecycle decision, choose Accept or Reject, enter the reason, and choose Apply decision.

A partial batch event records that quantity's movement without moving the whole batch in its current-location projection. Track exact instances when individual location is required.

Corrections and maintenance

Create a new event with Corrects Event and Correction Reason to correct a distinct accepted event for the same subject. The predecessor cannot already have been corrected. Acceptance preserves the audit trail and withdraws the corrected fact from effective history.

Do not rewrite the original release or factory for later relocation or service. An accepted new configuration is additional history for the same physical item. Report promptly, resolve Pending events, and inspect history after acceptance.

Both subjects selected, unavailable sources, invalid quantities/dates, a mismatched correction, an unapproved resulting configuration, or a changed form version can block an operation. Correct the cited source or reload before retrying.

Lifecycle events are separate from authoritative warehouse availability reports. Refresh affected passport drafts when the selected profile uses the event; earlier publications remain unchanged.

Product instances · Component use · Instance observations · Warehouse stock reports · Maintaining traceability and evidence