Mirror of Oracle documentation
Converted for search and offline reading. Authoritative source: Oracle. Diagrams and some complex tables are simplified — check the PDF when in doubt.
Legend BOD= Bill of Distribution Plan Cind = Planning Calendar Life Cind = Lifecycle Calendar OEM = Original Equipment Manufacturer
The following table lists the workspaces, steps, and views for the Supply Chain Network task.
Table 19-1 Supply Chain Network Workspace, Steps, and Views
| Workspace | Steps | Tab | Views |
|---|---|---|---|
| Supply Chain Network | Overview | Overview | Statistics View |
| Workspace | Scope | Location Scope View | |
| Product Scope View | |||
| Bill of Distributions | Bill of Distributions | Bill of Distributions View | |
| Valid Source Locations View | |||
| Planning Calendars | Planning Calendars | Planning Calendars View | |
| Day of Week View | |||
| Daily Exceptions View | |||
| Lifecycle Calendars | Lifecycle Calendars | Lifecycle Calendars View | |
| Lifecycle Phases View | |||
| Rules | Setup | Rule Views | |
| Conditions View | |||
| Review | Item-Location View | ||
| Item-Location-Week View | |||
| Item-Location-Phases View | |||
| Filter | Filter | Calendar Filter View | |
| Filter Parameters View |
Supply Chain Network Workspace
The Supply Chain Network workspace allows you to access all the views listed in the Supply Chain Network Workspaces, Steps, and Views. To build the Supply Chain Network workspace, perform these steps:
1. From the left sidebar menu, click Task Module to view the available tasks.
PL Valid Count ‘aa * EE All PL Count
Bill of Distributions Description
The Bill of Distributions (BOD) Description is a calculated measure used to indicate the Bill of Distributions description. The description is calculated based on the Bill of Distributions userdefined description and the Bill of Distributions set up. The pattern applied is the following:
- When no Reserved source is set up:
[BOD User Description]+ +[Primary Source]+.+[ Lead Time]
- When only Reserved source 1 is set up:
[BOD User Description]+ +[Primary Source]+.+[ Lead Time]+.R1
-
When only Reserved source 2 is set up:
- [BOD User Description]+ +[Primary Source]+.+[ Lead Time]+.R2
-
When both Reserved source are set up:
[BOD User Description]+ +[Primary Source]+.+[ Lead Time]+.R1.R2
Bill of Distributions User Description
The Bill of Distributions User Description is an editable measure to input a user-defined Bill of Distributions description. The final Bill of Distributions description takes into consideration your defined description. The entered value must not contain a colon punctuation mark (:).
Primary Source
The Primary Source is an editable measure to select, from a list, a primary source for the Bill of Distributions. The list of sources presented to you in the list are the sources that are enabled as a valid location source in the Valid Source Locations view.
Lead Time
The Lead Time is an editable measure to define the lead time, in number of days, for the Bill of Distributions.
Reserved Source 1
The Reserved Source 1 is an editable measure to select, from a list, a reserved source for the Bill of Distributions. The list of sources presented to you in the list are the sources that are enabled as valid reserved sources in the Valid Source Locations view.
Reserved Source 2
The Reserved Source 2 is an editable measure to select, from a list, an additional reserved source for the Bill of Distributions. The list of sources presented in the list are the sources that are enabled as valid reserved sources in the Valid Source Locations view.
The source inventory consumption sequence is fixed:
1. The system will first draw stock from Reserve Source 1 until it is depleted.
2. Next, it will draw from Reserve Source 2 until it is depleted.
3. Finally, it will draw from the Primary Source.
Rule Bill of Distributions Count
The Rule Bill of Distributions Count is a calculated measure to display the total number of rules that are using the Bill of Distributions.
Product Location Bill of Distributions Count
PL BOD App. Count All PL Count
Valid Source Locations View - Default Profile Measures
The Valid Source Locations View contains the following measures.
Valid Primary Source
The Valid Primary Source is an editable measure to define a location possible location to be used by the bill of distributions as the primary source.
Valid Reserved Source
The Valid Reserved Source is an editable measure to define a possible location to be used by the bill of distributions as a reserved source.
Planning Calendars Step
This step contains these views:
-
Planning Calendars View
-
Day of Week View
-
Daily Exceptions View
In IPOCS-Lifecycle Allocation and Replenishment the Planning Calendar (Plc) is used to specify the location’s ordering/receiving patterns along with the associated planning horizon that IPOCS-Lifecycle Allocation and Replenishment should plan for. IPOCS-Lifecycle Allocation and Replenishment works with two types of calendars:
-
Review Calendar : Use this calendar for point-in-time replenishments
-
Receipt Calendar : Use this calendar for time-phased replenishments
Both calendars allow for two methods to set up a Planning Calendar:
-
Day of Week : Main method to select the review or receipt dates, by selecting a day of the week, (for example, Monday) regardless of the dates
-
Exception : Method to configure exceptions by selecting specific dates (days) that are an exception to the day of week set up.
PL Pile. Count 100 _ ———_____. All PL Count
@
The Lifecycle Description is a calculated measure used to indicate the Lifecycle Calendar description. The description is calculated based on the Lifecycle Calendar user-defined description and the Lifecycle Calendar set up. The pattern applied is the following:
[Lifecycle User Description]+ + #START# + → + #END# , where:
-
#START#value is as follows-
If the measure Lifecycle Anchor is set to assortment start date then it is the text Assortment Start.
-
If the measure Lifecycle Anchor is set to Default and the anchor date exists (measure Lifecycle Default Anchor Date is not empty) then it is the date indicated in the measure Lifecycle Default Anchor Date.
-
If the measure Lifecycle Anchor is set to Default and the anchor date does not exist (measure Lifecycle Default Anchor Date is empty) then it is the text -inf (infinite).
-
-
#END#value is as follows-
If the measure Lifecycle End is set to assortment start date then it is the text Assortment End.
-
If the measure Lifecycle End is set to Default Date and the default end date exist (measure Lifecycle Default End Date is not empty) then it is the date indicated in the measure Lifecycle Default End Date.
-
If the measure Lifecycle End is set to Default Date and the default end date does not exists (measure Lifecycle Default End Date is empty) then it is the text +inf (infinite).
-
If the measure Lifecycle End is set to Default then it is the value indicated in the measure Lifecycle Default End Duration (day).
-
Lifecycle User Description
The Lifecycle User Description is an editable measure to input a user-defined Lifecycle Calendar description. The final Lifecycle Calendar description takes into consideration the user-defined description. The entered value must not contain a colon punctuation mark ( : ).
Lifecycle Anchor Method
The Lifecycle Anchor Method is an editable measure to select how IPOCS-Lifecycle Allocation and Replenishment should calculate the Lifecycle Calendar start date. Valid values are:
- Default
This option sets the Lifecycle Calendar start date to the date indicated in the measure Lifecycle Default Anchor Date. If the measure Lifecycle Default Anchor Date is empty, then the start date is assumed as -∞ (infinite).
- Assortment Start
This option sets the Lifecycle Calendar start date to the same date as the assortment start date.
Lifecycle Default Anchor Date
The Lifecycle Default Anchor Date is an editable measure to define a default start date for the Lifecycle Calendar when the Lifecycle Anchor measure is set up as default.
Lifecycle End Method
The Lifecycle End Method is an editable measure to select how IPOCS-Lifecycle Allocation and Replenishment should calculate the Lifecycle Calendar end date. Valid values are:
- Default Date
Lfe.Count 1003PL * “AILPL Count
• Copy
The option selected in the Lifecycle Calendar to be used as the source of the copy.
- Paste
The option selected in the Planning Calendar to be used as destination of the copy.
- -
The empty option selected to clear the measure.
Note
Only one Lifecycle Calendar should be selected as a source ( Copy ) but multiple lifecycle calendars can be selected as a destination ( Paste ).
Lifecycle User Filter
The Lifecycle User Filter is an editable measure to select the Lifecycle Calendar to filter the views by the selected Lifecycle Calendar. This measure is used by the Run Filter action button responsible to calculate the filters applied to the views within the Supply Chain Network workspace.
Lifecycle Phases View
The Lifecycle Phases View , under the Lifecycle Phases tab , allows you to configure each one of the phases for the total of phases specified in the Lifecycle Calendar. In this view, you can name the phases and set up the start and duration of each phase.
The lifecycle phases are considered as Product-Location Attributes in IPOCS-Lifecycle Allocation and Replenishment that can be used to set up replenishment parameter rules based on lifecycle phases.
This allows the IPOCS-Lifecycle Allocation and Replenishment to work on associating the correct replenishment parameters down to the item-location level (lowest level) based on the lifecycle phase. Using lifecycle phases simplifies the replenishment parameter management by completing it at the lifecycle phase level.
In this option the phase starts first before all other phases in the Lifecycle Calendar. Based on the previously listed options, the lifecycle phase is assigned to the item and location combination when the IPOCS-Lifecycle Allocation and Replenishment system date reaches the start date assigned to the phase.
Phase Anchor Offset (day)
The Phase Anchor Offset (day) is an editable measure to define the number of days to offset from the Lifecycle Calendar start date. This value is only used when the Phase Start is set to Offset vs Anchor. Negative values can also be used if the offset days need to be moved backward to the past.
Phase End Offset (day)
The Phase End Offset (day) is an editable measure to define the number of days to offset from the Lifecycle Calendar end date. This value is only used when the Phase Start is set to Offset versus End. Negative values can also be used if the offset days need to be moved backward to the past.
Phase Start Date
The Phase Start Date is an editable measure for you define a specific date to start the lifecycle phase. This value is only used when the Phase Start is set to Date.
Phase Minimum Sales %
The Phase Minimum Sales % is an editable measure to define the minimum sales percentage that IPOCS-Lifecycle Allocation and Replenishment uses to identify the lifecycle phase start date. This value is only used when the Phase Start is set to Seasonal Sales %.
Rules Step
This step contains these views:
-
Rules View
-
Conditions View
-
Item-Location View
-
Item-Location-Phases View
-
Item-Location-Week View
IPOCS-Lifecycle Allocation and Replenishment Rules Concept for the Supply Chain Network Task
IPOCS-Lifecycle Allocation and Replenishment provides a powerful engine that enables you to create a set of rules to apply all set up completed, within the Setup Task (Bill of Distributions, Planning Calendar, and Lifecycle Calendar), down to the item and location levels. You can define multiple rules at a higher level using product, location and product-location attributes and then allow the IPOCS-Lifecycle Allocation and Replenishment Rule Engine to calculate at the lowest level, product and location combinations, and define the correct set up to be applied.
IPOCS-Lifecycle Allocation and Replenishment rules allows you to specify the period when the rule should be applied (if applicable) and the rules’ priority. The rule priority allows IPOCSLifecycle Allocation and Replenishment to choose the correct rule to be applied if a product and location combination fits in more than one set up rule (the lower the number, the higher the priority). The rule start and end date are used by IPOCS-Lifecycle Allocation and Replenishment to determine if the rule should be considered or discarded. If the IPOCS-
• Default
This profile is used as default by the view. All the available or visible measures are listed and described in the section Measure: Default Profile.
• Bill of Distributions
This profile displays a subset of measures from the default profile. It focuses on the rule and on the Bill of Distributions measures only. The Planning Calendar and Lifecycle calendar-related measures are left out of the visible measures.
• Calendars
This profile displays a subset of measures from the default profile. It focuses on the rule and in the Planning Calendar measures only. Bill of Distributions and Lifecycle calendarrelated measures are left out of the visible measures.
• Lifecycle
This profile displays a subset of measures from the default profile. It focuses on the rule and on the Lifecycle Calendar only. The Bill of Distributions and Planning calendar-related measures are left out of the visible measures.
Rules View - Default Profile Measures
The Rules View contains the following measures.
Rule User Filter
The Rule User Filter is an editable measure to select the rule to filter the views by the selected rule. This measure is used by the Run Filter action button responsible to calculate the filters applied to the views within the Supply Chain Network workspace.
Rule Enable
The Rule Enable is an editable measure to enable or disable a rule. Each row (or list) represents a different rule.
Rule Condition
The Rule Condition is a calculated measure used to indicate the condition for which the rule is valid. The condition is the result of the set up completed in the Conditions view.
Rule Start Date
The Rule Start Date is an editable measure for you define a start date for the rule (when the rule should become active). When the rule is valid and the start date is empty, then IPOCSLifecycle Allocation and Replenishment applies it. When the rule is valid, and the start date is populated, IPOCS-Lifecycle Allocation and Replenishment starts to apply it only when the start date is reached.
Rule End Date
The Rule End Date is an editable measure for you define an end date for the rule (when the rule should become inactive). When empty IPOCS-Lifecycle Allocation and Replenishment assumes that the rule has no end date and if it is valid then IPOCS-Lifecycle Allocation and Replenishment applies it. When the rule is valid, and the end date is populated, IPOCSLifecycle Allocation and Replenishment stops applying it starting from the defined date.
Rule Priority
The Rule Priority is an editable measure for you define the rule’s priority. The higher that the number is, then the higher the priority of the rule. This rule priority is important to IPOCS-
S00 PL Ass. Count ir PE Count
PL BOD App. Count 100 “AIL PL Count
100 PL Pile. App. Count « ———————” AIT PL Count
PLLfc. App.Count 100 * ——TITPL Count
Table 19-2 Within Condition Operator Measure Available Operators
| Possible Operators | Descriptions | Example |
|---|---|---|
| == | Checks if the attribute value is equal with the Condition Value | brand == Private Label |
| != | Checks if the attribute value is different from the Condition Value | average sales != 0 |
| > | Checks if the attribute value is larger than the Condition Value | Average sales >5 |
| >= | Checks if the attribute value is larger or equal to the Condition Value | |
| < | Checks if the attribute value is less than the Condition Value | Standard deviation of sales <6 |
| ⇐ | Checks if the attribute value is less or equal to the Condition Value | |
| contain | ||
| not contain | ||
| match | ||
| not match |
Condition Value
The Condition Value measure is used when the type of the attribute is numeric. Example: average sales > 10
Condition Value String
The Condition Value String measure is used when the type of the attribute is a string. Example: brand == Private Label
Condition Value Measure
The value of the Condition Value measure is a measure name, which is populated by an expression that let’s you refine the condition value. For instance private label versus nonprivate label.
This measure is used when you want to refine the condition value.
For instance, for the coffee items, except Private Label, you want to assign items to the rule that sell more than 50 per week. For Private Label items you may want the value to be 100. You need to populate your Condition measure with a value of 100 for all Private Label items, and the rest of the coffee items with 50.
Condition Value Date
The Condition Value Date measure is used when the type of the attribute is a date. Example: today >= 02/30/2024”
Between Condition Operator
Within a rule there can be multiple conditions and also multiple condition groups. This is specified in the Condition Group measure. Conditions with the same Condition Group value belong to the same group.
For example, if a rule has 4 conditions, Conditions 1 and 2 can belong to condition group 1, and conditions 3 and 4 can belong to the condition group 2. Also, the Condition Order measure gives the ranking of the conditions inside the group.
The following table is an assumed use case:
Table 19-3 Between Condition Operator Assumed Use Case
| Condition | Between Condition Operator | Condition Order | Condition Group |
|---|---|---|---|
| Condition 1 | AND | 1 | 1 |
| Condition 2 | OR | 2 | 1 |
| Condition 3 | OR | 3 | 2 |
| Condition 4 | 4 | 2 |
The value for the Between Condition Operator can be the logical operators AND or OR.
The conditions are evaluated first inside a condition group and then between groups. In the previous case, the resulting condition is:
(Condition 1 AND Condition 2) OR (Condition 3 OR Condition 4)
Here is an example where all conditions belong to the same condition group:
Table 19-4 Example: All Conditions Belong to the Same Condition Group
| Condition | Between Condition Operator | Condition Order | Condition Group |
|---|---|---|---|
| Condition 1 | AND | 1 | 1 |
| Condition 2 | OR | 2 | 1 |
| Condition 3 | OR | 3 | 1 |
| Condition 4 | 4 | 1 |
The resulting condition for the rule is given by:
Condition 1 AND Condition 2 OR Condition 3 OR Condition 4
Note that the conditions are evaluated in the order given by the values in the Condition Order measure.
Condition Order
The Condition Order measure displays the order in which conditions are evaluated, wither independently or inside a condition group.
Condition Group
The Condition Group measure allows you to group conditions. This is useful when you want to evaluate conditions in a two-step process. First, the conditions are evaluated inside groups. In the second step, the group results are evaluated .
Validation Result
The Validation Result measure displays the condition expressions that are validated.
Invalid Flag
• Lifecycle
This profile displays a subset of measures from the default profile. It focuses on the rule and in the Lifecycle Calendar only. Bill of Distributions and Planning calendar-related measures are left out of the visible measures.
Item-Location View - Default Profile Measures
The Item-Location View contains the following measures.
Product Location User Filter
The Product and Location User Filter is an editable measure to select the product and location combinations to filter the views by the selected product and location combinations. This measure is used by the Run Filter action button responsible to calculate the filters applied to the views within the Supply Chain Network workspace.
All Product Location
The All Product and Location is a calculated measure used to indicate if a product and location combination is valid or not. A selected measure indicates the combination is valid, meaning it has a lifecycle phase value. A clear measure indicates that it is not valid.
Product Location Valid
The Product and Location Valid is a calculated measure used to indicate if a product and location combination has a valid rule from where the IPOCS-Lifecycle Allocation and Replenishment Rule Engine calculates the replenishment set up. The measure is selected when the item and location combinations have at least one valid rule that applies. A clear measure indicates that it does not have at least one valid rule that applies.
Product Location Bill of Distributions
The Product and Location Bill of Distributions is a calculated measure used to indicate that the Bill of Distributions is applied to the product and location combination. The Bill of Distributions displayed is the one calculated by the IPOCS-Lifecycle Allocation and Replenishment Rule Engine using the rules set up.
Over Bill of Distributions
The Override Bill of Distributions is an editable measure that allows you to create exceptions at the item-location level. You can select the Bill of Distributions to override the assigned Bill of Distributions (measure Product Location Bill of Distributions). This measure is a list populated with all valid BODs that were set up in the Bill of Distributions view.
Product Location Bill of Distributions Priority
The Product and Location Bill of Distributions Priority is a calculated measure used to indicate the priority of the rule from where the Bill of Distributions was calculated for the product and location combination.
Product Location Bill of Distributions End Date
The Product and Location Bill of Distributions End Date is a calculated measure used to indicate the end date of the rule from where the Bill of Distributions was calculated for the product and location combination.
Product Location Bill of Distributions Rule Count
Product and Location Bill of Distributions Rule Count is a calculated measure used to indicate the total number of Bill of Distributions that are assigned to the product and location combination based on the set up rules. Note that a product and location combination can only
have one Bill of Distributions active. The active one is the one from the rule with the highest priority or has an exception override.
Product Location Planning Calendar
The Product and Location Planning Calendar is a calculated measure used to indicate the Planning Calendar applied to the product and location combination. The Planning Calendar displayed is the one calculated by the IPOCS-Lifecycle Allocation and Replenishment Rule Engine using the rules set up.
Over Planning Calendar
The Override Planning Calendar is an editable measure that allows you to create exceptions at the item-location level. You can select the Planning Calendar to override the assigned Planning Calendar (measure Product Location Planning Calendar). This measure is a list populated with all valid planning calendars that were set up in the Planning Calendars view.
Product Location Planning Calendar Priority
The Product and Location Planning Calendar Priority is a calculated measure used to indicate the priority of the rule from where the Planning Calendar was calculated for the product and location combination.
Product Location Planning Calendar End Date
Product and Location Planning Calendar End Date is a calculated measure used to indicate the end date of the rule from where the Planning Calendar was calculated for the product and location combination.
Product Location Planning Calendar Rule Count
The Product and Location Planning Calendar Rule Count is a calculated measure used to indicate the total number of PLC that are assigned to the product and location combination based on the set up rules. Note that a product and location combination can only have one PLC active. The active one is the one from the rule with the highest priority or has an exception override.
Product Location Lifecycle
The Product and Location Lifecycle Calendar is a calculated measure used to indicate the Lifecycle Calendar applied to the product and location combination. The Lifecycle Calendar displayed is the one calculated by the IPOCS-Lifecycle Allocation and Replenishment Rule Engine using the rules set up.
Over Lifecycle
The Override Lifecycle Calendar. is an editable measure that allows you to create exceptions at the item-location level. You can select the Lifecycle Calendar to override the assigned Lifecycle Calendar (measure Product Location Lifecycle). This measure is a list populated with all valid lifecycle calendars that were set up in the Lifecycle Calendars view.
Product Location Lifecycle Priority
The Product and Location Lifecycle Calendar Priority is a calculated measure used to indicate the priority of the rule from where the Lifecycle Calendar was calculated for the product and location combination.
Product Location Lifecycle End Date
The Product and Location Lifecycle Calendar End Date is a calculated measure used to indicate the end date of the rule from where the Lifecycle Calendar was calculated for the product and location combination.
Product Location Lifecycle Rule Count
The Product and Location Lifecycle Calendar Rule Count is a calculated measure used to indicate the total number of lifecycle calendars that are assigned to the product and location combination based on the set up rules. Note that a product and location combination can only have one Lifecycle Calendar active. The active one is the one from the rule with the highest priority or has an exception override.
Primary Source @ Today
The Primary Source at Today is a calculated measure used to indicate the applied primary source for the product and location combination at the system date. The primary source is calculated from the current Bill of Distributions assigned to the product and location combination.
Lead Time @ Today Duration (day)
The Lead Time at Today Duration (day) is a calculated measure used to indicate the applied lead time, in days, for the product and location combination at the system date. The lead time is calculated from the current Bill of Distributions assigned to the product and location combination.
Reserved Source 1 @ Today
The Reserved Source 1 at Today is a calculated measure used to indicate the applied reserved source 1 for the product and location combination at the system date. The reserved source 1 is calculated from the current Bill of Distributions assigned to the product and location combination.
Reserved Source 2 @ Today
The Reserved Source 2 at Today is a calculated measure used to indicate the applied reserved source 2 for the product and location combination at the system date. The reserved source 2 is calculated from the current Bill of Distributions assigned to the product and location combination.
Low Level Code @ Today
The Low-level Code at Today is a calculated measure used to indicate the low-level code applied to the product and location combination at the system date. The low-level code is calculated from the current Bill of Distributions assigned to the product and location combination and the valid values are:
-
0 : The location is a store
-
1 : The location is a warehouse
-
2 : The location is a supplier
-
–1 : The location is invalid
Network Loop @ Today
The Network Loop at Today is a calculated measure used to indicate if there are Network Loop errors caused by the Bill of Distributions set up for the rule group at the system date. When selected, there are Network Loop errors. Otherwise, there are no errors.
Review @ Today
The Review at Today is a calculated measure used to indicate if today (current system date) is a review day for the product and location combination. The review day is calculated from the current Planning Calendar assigned to the product and location combination.
Next Review @ Today Date
The Next Review at Today Date is a calculated measure used to indicate the next review date for the product and location combination. The next review date is calculated from the current Planning Calendar assigned to the product and location combination.
Next Review @ Today Duration (day)
The Next Review at Today Duration (day) is a calculated measure used to indicate the number of days to the next review date for the product and location combination. The calculation of the number of days uses the current system date and the Next Review @ Today Date.
Average Review Time @ Today Duration (day)
The Average Review Time at Today Duration (day) is a calculated measure used to indicate the average number of days between each review period (planning period) for the product and location combination. The value is calculated using the review periods from the current Planning Calendar assigned to the product and location combination.
Assortment Product-Location
The Assorted Product and Location is a loaded measure used to indicate whether the product and location combinations are assorted or not.
Assortment Product-Location Start Date
The Assorted Product and Location Start Date is a loaded measure used to indicate the assortment start date for the assorted product and location combinations.
Assortment Product-Location End Date
The Assorted Product and Location End Date is a loaded measure used to indicate the assortment end date for the assorted product and location combinations.
Assortment Product-Location Active
Assorted Product and Location Active is a loaded measure used to indicate whether the product and location combinations are assorted and still active or not. If the assortment end date has not been reached yet then it is active. Otherwise, the product and location combination is assorted but not active.
Lifecycle Product-Location Default
The Lifecycle Calendar Product and Location Default is a loaded measure to identify whether the product and location combination has a valid lifecycle by default or not.
Lifecycle Product-Location Exception
The Lifecycle Calendar Product and Location Exception is a loaded measure used to indicate whether the lifecycle is an exception for the product and location combination. Check the measure Lifecycle Product-Location Exception in the Assortment Admin workspace for more detail on the valid values.
Lifecycle Product-Location Validity Start Date
The Lifecycle Calendar Product and Location Validity Start Date is a loaded measure used to indicate the lifecycle start date exception for the product and location combination when there is an exception.
Lifecycle Product-Location Validity End Date
The Lifecycle Calendar Product and Location Validity End Date is a loaded measure used to indicate the lifecycle end date exception for the product and location combination when there is an exception.
Lifecycle Product-Location
The Lifecycle Calendar Product and Location is a loaded measure to identify whether the product and location combination has a valid lifecycle or not.
Lifecycle Anchor Exception Date
The Lifecycle Calendar Anchor Exception Date is a loaded measure to identify the lifecycle anchor date exception for the product and location combination when there is an exception.
Lifecycle End Exception Date
The Lifecycle Calendar End Exception Date is a loaded measure to identify the lifecycle’s exception end date for the product and location combination when there is an exception.
Actual Location Sales Units
The Actual Location Sales Units is a loaded measure to display the actual sales for the product and location combination. The value displayed for the product and location combination is the aggregation of all the weeks that are in the scope of the workspace.
Total Initial Forecast Units
The Total Initial Forecast Units is a loaded measure to display the total initial forecast for the product and location combination. The value displayed for the product and location combination is the aggregation of all the weeks from the current week up to the forecast horizon.
Lifecycle Active @ Today
The Lifecycle Calendar Active at Today is a loaded measure used to indicate whether the product and location combination has a valid lifecycle or not at the system date.
Lifecycle Active @ Today
The Lifecycle Calendar Active at Today is a loaded measure used to indicate the lifecycle phase string for the product and location combination when the product and location combination has a valid lifecycle at the system date.
Item-Location-Week View
The Item-Location-Week View , under the Review tab , allows you to review and overwrite the review weeks and receipt weeks. Any overrides are on top of the review weeks and receipt weeks that the IPOCS-Lifecycle Allocation and Replenishment calculates using the Planning Calendar set up for the product and location combination.
up at the system date. The phase names are prefixed and suffixed to provide you with additional information, the logic is as follows:
- < >
When the phase name is prefixed and suffixed this way, it means that the phase is the current lifecycle phase (for example,
- ( )
When the phase name is prefixed and suffixed this way, it means that the phase is an elapsed/previous lifecycle phase (for example, (Discovery)
When the phase name has no prefix and suffix, it means the lifecycle phase has not been reached yet (for example, EOL )
Lifecycle Phase Exception Start Date
The Lifecycle Calendar Phase Exception Start Date is an editable measure that allows you to override the phase start date set up in the Lifecycle Calendar assigned to the product and location combination.
Filter Step
This step contains these views:
-
Filter Parameters View
-
Calendar Filter View
Filter Parameters View
The Filter Parameters View , under the Filter tab , allows you to set up the filter that can change the scope of the products and locations displayed in all relevant views under the Rules Step within the Supply Chain Network Workspace.
• Copy-Paste Lifecycle
Use the Copy-Paste Lifecycle Calendar action button to copy the Lifecycle Calendar information from the Lifecycle Calendar selected as the source of the copy and paste it into all the lifecycle calendars selected as the destination of the copy. This action copies all the information in the Lifecycle Calendar view and lifecycle phase view.
• Copy-Paste Rules
Use the Copy-Paste Rules action button to copy all rule information from the rule selected as the source of the copy and paste it into all rules selected as the destination of the copy. This action copies all the information in the Rules view and Conditions view.
• Rule Conditions
Use the Rule Conditions action button for the calculation of the rule’s conditions based on the set up completed in the Conditions view. The result of the calculation is written into the measure Rule Condition in the Rules view.
• Rule Engine
Use the Rule Engine action button for running the IPOCS-Lifecycle Allocation and Replenishment Rules Engine to calculate which rule’s replenishment set up would be applied to the product and location combination level. The results of the run are visible in the statistic measures of the Rules view as they are updated with the run results. To ensure that the IPOCS-Lifecycle Allocation and Replenishment Rules Engine is run with the right conditions for all the rules, this action button runs the Rule Conditions first, as part of its process.
• Rule Apply
Use the Rule Apply action button for applying the rule’s replenishment set up, from the last Rule Engine run, down to the product and location combination level. The results of the run are visible in the Item-Location view as the measures are updated with the run results.
• Rule Engine + Apply
Use the Rule Engine + Apply action button to run the Rule Engine action button followed by the run of the Rule Apply action button. As a result, the IPOCS-Lifecycle Allocation and Replenishment Rule Engine is run, and the results are applied down to the product and location combination level immediately.
• Clear Filter
Use the Clear Filter action button to remove all filters applied in the Supply Chain Network view and clear all User Filter measures within the workspace.
• Run Filter
Use the Run Filter action button to apply the filters in the Supply Chain Network views based on the filter set up completed within the workspace. For example, the calendar horizon or check the filtered measures.
• Reload Attributes
Use the Reload Attributes action button to load the product, location, and product-location attributes from the domain into the workspace. It refreshes the measures available for all the views under the Attributes Step.
• Commit Attributes
Use the Commit Attributes action button to save the domain, product, location, and product-location attributes. This functionally ensures that any user changes to the attributes within the workspace are saved and committed to the domain.