Revision Effectivity
Revision Effectivity is the defined applicability of a particular item or structure revision to identified parent revisions, dates, orders, lots or units.

On this page · 11 sections
- 1What revision effectivity decides—and what it does not
- 2Parent-revision applicability is different from date-based selection
- 3Choose the governing input before authorizing manufacturing
- 4RF-260: map each parent revision to its connector
- 5RF-260: test the timestamp boundary and late entries
- 6Serial, lot and job boundaries are alternative rules
- 7Split open work without rewriting its original selection
- 8Record the rule, selection, assessment and authorized disposition
- 9Keep regulatory context specific to product and jurisdiction
- 10Exchange selection decisions without creating competing truths
- 11Review the boundary before putting the rule into use
How does Revision Effectivity apply to your shop floor?
Pick your industry and scale — Ask V5 rewrites the definition in your context, gives a worked example, and shows what V5 does on day one.
01What revision effectivity decides—and what it does not
Revision Effectivity is the defined applicability of a particular item or structure revision to identified parent revisions, dates, orders or units. A revision identifier names a version; an effectivity rule determines whether that version applies to a particular manufacturing context. The distinction is between identifying a revision and selecting it for planned work.
Displaying the latest revision does not establish which revision applies to a planned job or unit. A usable selection needs an identified scope, a declared rule and the relevant input values. Without those, latest is merely a display choice. A newer revision can exist while an earlier revision remains applicable to work covered by a different boundary or an explicitly authorized continuation decision.
| Concept | Decision it owns | Resulting record |
|---|---|---|
| Revision Effectivity | Applicable planned revision | Selection and cutover decision |
| Document Control | Approval and version availability | Controlled document status |
| As-Built Configuration | Actual incorporated state | Execution evidence |
| Recipe Effective Dating | Applicable process formulation or instructions | Recipe applicability |
| Design Transfer | Manufacturing handoff | Transfer evidence |
These records answer different questions. Document approval establishes status, not applicability to every order. A job traveler can carry the selected revision into execution; as-built configuration records what was actually incorporated. Neither the planned selection nor the actual build should be inferred solely from the other.
For formulation changes, recipe versioning addresses the neighbouring recipe subject rather than making it synonymous with item-structure applicability. Design transfer concerns the manufacturing handoff, not each subsequent selection. Medical-device kitting is downstream: it follows an explicit applicability business rule when choosing components, rather than owning the selector or deciding the cutover. Keeping those responsibilities separate makes a disputed selection easier to investigate.
02Parent-revision applicability is different from date-based selection
Revision effectivity separates two manufacturing questions: which parent revision applies to the planned job, and which component associations belong to that selected parent. A date can answer the first question without making every component revision independently date-selected. Keeping those questions separate avoids constructing a combination merely because its individual revisions are the newest available.
- Select the parent revision using the site's chosen applicability rule and the relevant job inputs.
- Resolve component associations for that selected parent, rather than substituting the latest component revision simply because it exists.
This is a practical analytical model, not a claim that every manufacturing system stores a separate structure for each revision. A configuration specification can describe the intended combination; the applicability decision identifies which combination governs the planned work. The distinction matters when reviewing a screen that lists revision identities but does not explain why one was selected.
Oracle Fusion Cloud SCM 26C Item Revisions explicitly describes item structures as not revision specific. It then describes a condition under which they act as revision-effective structures: the structure components' start and end dates match the item revision's start and end dates. In that documented arrangement, date alignment establishes the revision-effective behaviour. It would therefore be misleading to describe every Fusion item revision as inherently owning a separate structure.
Oracle PeopleSoft manufacturing: Defining and Maintaining Revisions describes production selection using the production start or due date to determine which revision is in effect and which components are in effect for that revision. The same documentation describes building to an older or future revision by selecting a particular revision for the item. This provides a concrete vendor example of why selecting the applicable revision is not synonymous with displaying the latest revision.
Both documents are primary vendor guidance about their respective products, not legislation or an industry-wide specification. Their terminology does not establish V5 support for these selectors. When reviewing a supplier implementation, ask which event is evaluated, how overlapping associations are reported and whether the evaluated structure can be retrieved later. A demonstration using one uncomplicated order cannot answer those boundary questions. Test the chosen input against a known expected association, including an excluded candidate and a missing association; record each result rather than relying on the display label.
03Choose the governing input before authorizing manufacturing
A practical applicability rule starts with the affected item and manufacturing site, not a search for the newest revision. Treat the following sequence as a recommended operating design for discrete manufacturing, with responsibilities assigned through the site's controlled process.
- Identify the affected item and site. Engineering defines intended parent–component associations in the configuration specification.
- Declare the selector and input basis. Choose date, serial, lot or job applicability explicitly; identify where the governing input comes from.
- Define applicable ranges or membership. Assign each range or listed identifier to its intended revision, using consistent identifiers under master data governance.
- Assess affected work. Manufacturing identifies physical work state; the designated decision owner evaluates continuation, change or hold.
- Authorize the cutover decision. Record the selected disposition and its scope before directing affected execution.
- Use the recorded selection. Execution personnel follow the authorized result for the identified work rather than substituting the latest revision.
- Reconcile exceptions. Route missing inputs, unmatched work and conflicting matches for review; preserve the decision trail when correcting or reassessing a selection.
Selector type and input basis answer different questions. Date is a selector type; manufacturing authorization, planned start and actual start are possible governing events. A date rule remains incomplete until the site names that event. Serial, lot and job selectors are alternatives, not additional filters silently applied to every date decision.
The review branches do not imply automatic software resolution. Deliberately combined rules need their own documented interpretation and conflict handling; neither intersection nor precedence is assumed. The worked cases below keep selectors separate. These responsibilities are illustrative assignments, not universal statutory job titles.
- Identify scopeIdentify the item, site and planned job or unit.
- Read ruleRead selector_type and rule_version, not the latest displayed revision.
- Read inputUse the declared event time, serial, lot or job identifier.
- Evaluate applicabilityResolve one candidate; missing or conflicting matches need assessment.
- Resolve structureFollow the selected parent revision to its component associations.
- Assess affected workApply the authorized continuation, change or hold decision.
- Preserve selectionRetain inputs, selected structure and the decision reference.
- Authorize actionPeople authorize execution; retain actual incorporation evidence separately.
04RF-260: map each parent revision to its connector
RF-260 is a fictional discrete-assembly case. C and D are revisions of the parent assembly; A and B are revisions of connector item P10. The illustrative structure associates parent assembly revision C with P10 revision A, and parent assembly revision D with P10 revision B.
| Parent assembly revision | P10 rev A | P10 rev B | Selection result |
|---|---|---|---|
| C | Specified | Not specified | P10 rev A |
| D | Not specified | Specified | P10 rev B |
Not specified means that the association is absent from this hypothetical structure. It does not establish physical incompatibility, approved substitution or interchangeability. The matrix answers which connector revision the selected parent structure specifies—not whether another connector could perform acceptably.
- Identify the applicable parent revision for the planned job or unit using the chosen manufacturing applicability rule.
- Resolve the P10 association from that parent’s row: C selects A; D selects B.
- Carry that resolved association into the material-selection instruction rather than independently choosing the latest P10 revision.
Suppose a component display shows P10 revision B as latest while the planned job selects parent revision C. That display does not rewrite the C association: the matrix still selects P10 revision A. In a medical-device kitting workflow, an explicit business rule could use this resolved parent-component association to guide kit selection.
A proposed use of B in C is a separate assessed configuration decision. Compatibility and substitution assessment sit outside this selector’s scope; neither authorization nor technical suitability follows from revision lettering. Keep the proposal distinct from the existing C-to-A association until that decision is made.
05RF-260: test the timestamp boundary and late entries
For fictional RF-260, the site chooses the recorded manufacturing-authorization event as the governing input for selecting a parent revision for new work. The cutover is 2026-11-24T08:00:00+00:00. This event basis is an illustrative business rule, not an Oracle or FDA requirement. It answers which revision applies when manufacturing is authorized—not which revision happens to be displayed when someone later opens the job.
Use half-open intervals: C applies before the cutover timestamp; D applies at or after it. The end of C’s interval is exclusive, and the beginning of D’s interval is inclusive. The boundary therefore belongs to D, with neither a gap nor an overlap.
| Scenario | Governing event | Entry timing | Selection or action |
|---|---|---|---|
| New authorization immediately before cutover | 2026-11-24T07:59:59+00:00 | Recorded when authorized | Select C. |
| New authorization exactly at cutover | 2026-11-24T08:00:00+00:00 | Recorded when authorized | Select D. |
| Late entry reporting earlier authorization | Reported event: 2026-11-24T07:59:59+00:00 | Entered after cutover; retain actual entry timestamp | Assess evidence of pre-cutover authorization; select C only if supported. |
For the late entry, preserve both the reported authorization-event time and the actual entry time. Review evidence that authorization genuinely occurred before the boundary, including who authorized the work and the contemporaneous record supporting that event. A supported late record can describe a genuine pre-cutover authorization under this event-time rule; it cannot retrospectively create an authorization that never occurred. Route unresolved timing or authorization evidence to human assessment rather than accepting convenient backdating. Use attributable recording to keep the recorder’s identity distinct from the reported authorizer.
For a job already started to C, retain the original selection and record an explicitly authorized continuation or hold decision. Crossing the timestamp does not silently replace its selected structure with D. Resolve the connector association through the preceding parent-revision matrix; the timestamp selects the parent revision rather than independently selecting its components.
The explicit +00:00 offset anchors the cutover to an unambiguous instant instead of leaving readers to infer local time. Compare authorization times on the same time basis, preserving their recorded offsets. A date-only publication notice cannot substitute for this rule: it identifies neither the precise transition instant nor the manufacturing-authorization event that governs selection. Publication and authorization remain different events even when they occur on the same calendar day.
06Serial, lot and job boundaries are alternative rules
A site can choose serial, lot or job applicability instead of RF-260’s timestamp rule. These are separate site-practice examples: identifiers appearing on a manufacturing record do not activate additional selectors. Declare the governing rule in the configuration specification, including how unresolved identities are handled.
Serial alternative: declare named start and end serials for each revision’s range. For this example, include the start and exclude the end; compare numeric suffixes within a fixed prefix, rather than sorting the complete identifiers alphabetically. Define separate treatment for other prefixes. A missing serial leaves selection unresolved until identity is established. An unallocated serial inside the range has a prospective assignment, not evidence that a unit exists or was built. Record any later allocation against the declared rule.
Lot alternative: assign revisions through explicit membership in identified manufacturing lots. Lot identity is not manufacture date; do not infer applicability from a date embedded in a lot code. Relotting or splitting raises a fresh applicability question: record whether successor populations retain the original selection or receive an assessed change, with their membership traceable to the original population.
Job alternative: list the orders governed by each revision, or declare an order boundary with an ordering method and endpoint treatment. A job identifier establishes chronology only if the site deliberately defines that meaning; identifier sorting alone is insufficient.
Serial and lot rules also need exclusions. A scrapped serial can remain within a numeric range without being eligible for work. A supplier lot may span several receiving events, whereas an internal manufacturing lot can represent a different population. Record which identifier namespace the rule evaluates, and resolve aliases before evaluating membership. A range comparison using the wrong namespace is a different defect from a gap in an otherwise correct range.
07Split open work without rewriting its original selection
Assume the fictional RF-260 order contains 120 assembly units, all initially selected against parent revision C. At assessment, 70 units are already assembled to C, 30 are kitted but not assembled, and 20 are not kitted. The population reconciles: 70 + 30 + 20 = 120 units. These are physical work-state cohorts, not automatic dispositions. Neither revision publication nor the calendar boundary alone decides whether they continue or change.
For this hypothetical case, the responsible human assessors authorize the following outcomes after reviewing the affected work:
| Cohort | Original selection | Assessed disposition | Replacement selection | Evidence retained |
|---|---|---|---|---|
| 70 assembled units | C | Authorized to continue on C | None; C continues | Original C snapshot, continuation decision and assembly evidence |
| 30 kitted units | C | Hold while evaluating transition to D | None authorized | Original C snapshot, kit contents, hold decision and assessment findings |
| 20 not-kitted units | C | Authorized for a new D selection after cutover | D | Original C snapshot linked to authorized D snapshot and decision |
For the assembled cohort, assess whether any later operation changes the applicability question. A unit assembled to C might still await labeling, functional testing or packaging. Identify which operations the continuation decision covers and which remain subject to assessment. A restricted permission to finish one operation is not an unrestricted permission to complete or ship the entire device. Record remaining work by unit group so a reviewer can test the decision against the actual stage reached.
For the kitted cohort, assess de-kitting, material reconciliation and the complete D structure before authorizing any transition. Exchanging connector P10 alone does not establish that the remaining kit, instructions and planned operations fit D. Use in-process reconciliation to account for issued, returned and retained materials during that assessment. The held units have no authorized replacement selection in this example; their eventual disposition remains undecided.
For the not-kitted cohort, retain the original C snapshot and link the newly authorized D snapshot rather than replacing the order's earlier selection. The batch execution history can then distinguish the initial plan from the subsequent authorized change.
One order can therefore contain separately identified populations with different dispositions. In this example, the decision record identifies every unit belonging to each cohort, its assessed state and the applicable authorization or hold. An order-level revision label alone would conceal that split.
08Record the rule, selection, assessment and authorized disposition
Keep the applicability rule separate from the selection snapshot. The rule describes how selection works; the snapshot records which rule version and input values produced the selected revision for identified work. Retaining both lets a reviewer reconstruct a decision even after the governing rule changes.
For the rule, record item and site scope, selector type, governing input basis, and boundary or membership criteria. For each snapshot, record the work identity, rule version, evaluated inputs, selected parent revision and component-mapping reference. Keep governing event time distinct from record-entry time: the earlier late-entry example illustrates why these timestamps answer different questions.
Link the affected-work assessment to the original selection, physical work state, quantity and rationale. Each continuation, transition or hold decision should identify its affected population and the person authorizing it; attributable recording supports that responsibility. Avoid a single disposition label covering populations with different assessed outcomes.
For a changed selection, provide the predecessor reference needed for audit trail review. The record model below uses separate objects so an assessor can inspect one decision without retrieving every document in the order. Record unavailable attachments and unresolved assessments explicitly. An attachment identifier should distinguish the retained evidence version from a live link whose contents may change. These are practical record-design choices, not a legally prescribed form or universal signature arrangement.
Cutover decision record
Applicability rule
Defines the chosen selector and boundary.
- rule_id
- rule_version
- item_id
- site_id
- selector_type
- input_basis
- boundary_definition
Selection snapshot
Preserves inputs and the selected structure.
- selection_id
- rule_id
- rule_version
- job_id
- selector_value
- event_time
- recorded_at
- parent_revision
- component_mapping_id
- supersedes_selection_id
Affected-work assessment
Identifies the population and assessed condition.
- assessment_id
- selection_id
- unit_scope
- work_state
- quantity
- quantity_unit
- assessment_rationale
Authorized disposition
Records continuation, transition or hold.
- decision_id
- assessment_id
- disposition
- authorized_by
- authorized_at
- replacement_selection_id
Execution evidence reference
Links actual incorporation without redefining applicability.
- evidence_id
- decision_id
- unit_id
- lot_id
- as_built_record_ref
09Keep regulatory context specific to product and jurisdiction
For US medical-device manufacturing, check the current text of 21 CFR Part 820 for QMSR scope; keep historical provisions out of current-requirement comparisons. The FDA QMSR overview provides context for that review.
For US medical-device manufacturing, the FDA Quality Management System Regulation final rule is regulatory context, not a specification for a named Revision Effectivity form, mandatory selector or universal field set. Keep QMSR and ISO 13485 distinct from the proposed operational examples. Do not infer detailed clause requirements or selector permissions from the name of the standard.
For drug, supplement, food, chemical and other discrete manufacturers, the applicability model is an operational design example. Regulatory implementation depends on products, activities and markets; do not transfer the US device context to those sectors. Assess the proposed selection rule against the requirements governing the particular operation, rather than treating a shared manufacturing concept as a shared legal obligation.
10Exchange selection decisions without creating competing truths
One possible architecture assigns engineering or PLM responsibility for parent-to-component associations, ERP for job and site identity, manufacturing execution for applying authorized selections to work instructions, and quality systems for exception assessment and disposition. Designate one owner for the applicability rule; distributing its decisions should not create independent selectors. This is an implementation-neutral architecture example, not a product integration claim. MES–ERP integration addresses the surrounding exchange.
For each selection, exchange stable item and site identifiers, rule version, selector input, event time with offset, selected parent revision, component-mapping reference and selection identifier. Include the relationship to any earlier decision being corrected or replaced. A revision label alone loses why that revision applies: the receiver cannot reliably distinguish a new selection from a replay, correction or replacement. Treat message receipt as acknowledgement of delivery, not manufacturing authorization.
Suppose a receiver evaluates a job using a stale rule while a newer rule is awaiting processing. Identify the affected selection and prevent its conflicting instructions from being treated as authorized. Reconcile the selector input and rule version against the designated rule owner. If correction is appropriate, obtain human disposition and issue a linked corrected decision. If the older message subsequently arrives out of order, recognize its relationship to the corrected selection rather than replacing the current decision merely because it arrived last.
Keep unresolved exceptions visible with an assigned human decision owner through the manufacturing–quality handoff. Apply the earlier late-entry and preserved-snapshot approach to recovery. Successful synchronization establishes neither the correct cutover nor permission to continue affected work.
11Review the boundary before putting the rule into use
Use these site-practice checks before authorizing selection. For RF-260’s date rule, test immediately before and exactly at the cutover timestamp, retaining its offset. Test declared serial endpoints or lot membership only when that alternative selector is chosen; do not combine selectors implicitly.
| Failure | Review test | Decision owner |
|---|---|---|
| Missing governing event | Identify which event supplies the selection input, not merely when someone entered it. | Manufacturing rule owner |
| Applicability gap | Establish whether the population is intentionally excluded or the rule is incomplete. | Rule owner |
| Overlapping candidates | Resolve conflicting candidates or explicitly define intended rule semantics before authorizing selection. | Engineering and manufacturing |
| Incorrect parent-component association | Check each selected parent against RF-260’s connector matrix. | Engineering |
| Unresolved affected-work population | Reconcile assembled, kitted and unprepared work with assessed dispositions. | Production and quality |
| Stale receiving-system rule | Compare the receiving rule version and boundary results with the authorized rule. | System owner and rule owner |
Reconstruct a recorded selection from its retained rule version and inputs. For a changed selection, check that its predecessor and authorized disposition remain traceable. An audit-trail review workflow can structure that history check; it does not decide applicability.
The following FAQs address individual selection decisions. Treat the rule as ready when responsible people can identify which rule applies, explain its boundary, account for affected work and recover an exception without replacing history.
Frequently asked questions
Q.If revision D is approved, can a new job still be assigned revision C?+
Yes, if the authorized rule selects C for that job and no separate restriction prohibits its use. For example, engineering might approve D for a future customer variant while C remains the approved configuration for another variant. Include the variant in the rule scope, identify which permitted operations the assignment covers and check any withdrawal instruction separately. A bill of materials helps identify the intended structure, but the variant scope and withdrawal decision need their own recorded basis.
Q.Which date governs selection when the order date, planned start and actual start differ?+
Use the event explicitly named in the site's applicability rule; do not choose whichever date produces the preferred revision. The rule should distinguish an initial planning selection from the point at which that selection becomes fixed. If planned start governs, specify whether rescheduling triggers reassessment. If actual start governs, distinguish the recorded start event from its later entry time. Coordinate that policy with backward scheduling, without allowing a schedule recalculation to silently replace an established assignment.
Q.What evidence distinguishes a legitimate late entry from an attempt to backdate applicability?+
A defensible late entry preserves both the claimed event time and the actual entry time, identifies the author, and explains the delay. Independent execution evidence can support when work actually began; a typed earlier timestamp alone is weak support. Compare that evidence with the rule version governing the event and the job's original assignment. Contemporaneous recording helps establish this distinction. Corrections should remain traceable rather than making a later selection appear to have existed earlier.
Q.Does specifying P10 revision B in parent D authorize its use in parent C?+
No. The RF-260 association is not a substitution assessment. The proposed alternative needs an assessment of the interfaces and acceptance criteria it changes, plus identification of the units that would receive it. Ask whether the assembly instructions, downstream tests or labeling depend on the original connector. A technically acceptable substitution can still need different instructions or verification. An electronic work instruction should reflect the authorized operation, rather than letting a stores substitution silently alter the build.
Q.Can an older lot remain assigned to C after a date rule begins selecting D?+
Possibly, but the lot's age is not itself an exception to a date rule. An authorized continuation decision can preserve C for identified work when the site's policy permits it. Alternatively, a site can explicitly adopt lot applicability instead of date applicability; that is a different selector, not an implied override. Record which rule governs and its scope. Lot genealogy identifies the affected material relationships but does not independently authorize continued manufacture to C.
Q.What should happen when a serial falls in no applicability range or in overlapping ranges?+
Treat the result as an unresolved selection, not permission to default to the latest revision. Identify the affected serials and pause revision-dependent execution while the responsible owner assesses the gap or overlap. A predefined precedence rule can resolve an intentional overlap; otherwise, document the corrected boundary and disposition of affected assignments. Use an electronic hold tag where appropriate. Test the neighboring serials and both boundary endpoints before resuming work under the corrected rule.
Q.Can one open order contain units continuing to C and units transitioning to D?+
Yes, provided membership and authorized work remain distinguishable. For RF-260, identify assembled, kitted and unkitted groups using retained unit or sublot references. Check that an operation-level instruction cannot accidentally reach the held group. If units move between containers, preserve that membership relationship or pause work until it can be resolved. A traceability data model can organize those relationships; a single order header cannot express different permissions for different unit populations.
Q.How should manufacturing proceed when engineering and production systems show different rule versions?+
First establish whether the two versions differ in content or only in transfer status. Compare item/site scope, selector basis, boundary and exclusions, then identify which jobs were actually evaluated under each version. Obtain an authorized interim instruction for any affected work instead of allowing receipt order to choose the winner. A host system interface should carry the decision relationship and acknowledgement needed to distinguish replay, correction and genuinely new selection. Reconcile affected assignments before closing the transfer exception.
Primary sources
Want to see how Revision Effectivity could fit into your own records and workflows? Explore the related V5 pages or talk to our team about what applies to your operation.
