Understand the Effective date BOM structure
The following conditions determine how Upchain calculates the BOM structure when an effective date is configured for a project.
Conditions 1 |
Result |
- End item and direct parent are Released.
- The item's creation date precedes the project's Effective date.
|
Effective date pulls the item into the eBOM structure. |
Conditions 2 |
Result |
- End item and direct parent are Released.
- The item’s creation date is after the project’s Effective date.
|
Effective date excludes the item from the eBOM structure. |
Conditions 3 |
Result |
- End item and direct parent are Released.
- Item belongs to one end item or project. New versions of the item exists elsewhere on the same tenant and all of these items have a creation date that precedes the project’s Effective date.
|
In the eBOM structure:
- The direct parent adopts the top-level, child-item's status;
- Includes any newly created items and new versions of existing items - pulled in from wherever it exists on the tenant.
|
Conditions 4 |
Result |
- End item and direct parent are in Development.
- The direct parent’s creation date precedes the project’s effective date.
|
- Effective date pulls the latest versions of edited/updated eBOMs into the eBOM, irrespective of their creation date.
- Effective date does not pull in newer versions of items if they are Obsolete or Externally_Released even if their creation date is within the project’s Effective date.
- Effective date pulls in the latest, checked-in versions of all items into the eBOM, irrespective of the items’ creation date. Newly created items that were checked in are also pulled into the eBOM.
|
Conditions 5 |
Result |
- End item is Released or in Development and direct parent is in Development.
- The direct parent’s creation date precedes the project’s effective date.
|
Effective date pulls in the latest saved versions of all items, irrespective of the items’ creation date. Any structural changes made in Upchain are part of this eBOM. |