To report the date used to convert the calculated field EffectiveUnitPrice, the CONVERTONDATE function is the appropriate one to use. This function converts a measure's value from one date to the value it would have on another date. The $ConversionDate variable (or similar) would typically be used within the worksheet to reference the date to which the conversion is applied.

ReferencesThe Kinaxis RapidResponse documentation on calculated fields and conversion functions explains how the CONVERTONDATE function is used to adjust financial measures based on changes over time, which would apply to fields such as EffectiveUnitPrice.

The migration of the Supplier.Id filter to the secondary filter expression box allows for enabling caching because it is a user-specific filter. Moving user-specific or session-specific expressions to the secondary filter ensures that the primary filter canbe cached independently of user sessions. This way, the overall data set can be cached, and the user-specific filtering is applied afterward, improving performance.

References:

• Kinaxis RapidResponse documentation on primary and secondary worksheet filters.
• Kinaxis support resources on caching strategies and performance improvements for worksheets.

To optimize performance when creating a worksheet that contains fields from four tables, the worksheet should be based on:

• Table 1

Table 1 is connected to Table 3 with a one-way arrow, indicating a one-to-many relationship where Table 1 is the primary table. This setup typically allows for more efficient data retrieval and better performance.

• References

The decision is supported by the diagram showing the relationships between the tables, where “Arrow Head = 1” and “Arrow Base = Many” indicates the direction of the relationship and the primary table.

To optimize performance, the worksheet should be based on the top-level table from which you can access related data via references. This is because starting from the top level allows you to utilize indexed lookups, which are faster than traversing from many-to-one relationships. Given the data model design, Table 1 is the topmost table with one-to-many relationships to Table 3, which in turn links to Table 4, and it can also indirectly access data from Table 2 through the many-to-one relationship back to Table 1.

References:

• Kinaxis RapidResponse documentation on worksheet creation and data model traversal.
• Kinaxis guidelines on optimizing worksheets for better performance.

Given the order policies of MultipleQty: 10, MinimumQty: 15, MultipleUsage: Use, and MinimumUsage: Use, the sizes of the planned orders are determined by rounding up to meet the minimum quantity and then to the nearest multiple of the MultipleQty. Order A needs to meet the demand of 25, so it must at least meet the MinimumQty of 15 and then round up to the nearest multiple of 10, which is 30. Order B, with a demand of 12, will also round up to the minimum quantity of 15 and then to the nearest multiple of 10, which is 20, since the MultipleUsage is "Use." The same logic applies to order C, with an initial demand of 20, it is already at a multiple of 10, so it remains 20.

ReferencesThis answer applies the principles of order quantity rounding based on multiples and minimums as commonly used in supply chain planning and as described in Kinaxis RapidResponse's order policy settings.

References:

• The Kinaxis RapidResponse documentation and training materials provide guidelines on how to apply order policies to determine the sizes of planned orders123.

To ensure unique key values while saving memory, it's best to concatenate critical fields that together provide uniqueness. The expression A combines the Part Site Value and the Effective In Date, providing a string that will be unique across all parts and their effective dates. This approach is more memory-efficient than storing additional redundant data or using less discriminative fields.

B is not specific enough, as EffectiveInDate alone does not guarantee uniqueness across parts and sources. C is potentially unique, but it may not be as memory-efficient as A if Part Names are long strings. D is not specific enough, as the Source ID alone does not ensure uniqueness across parts.

References:

• Kinaxis RapidResponse documentation on data modeling, particularly regarding key construction.
• Best practices for key management in database systems as relevant to Kinaxis RapidResponse.

To prevent duplication of TimePhasedSafety records in cross-scenario updates:

• Statement A:Including all key and reference fields in the update is a best practice. This ensures that the database can accurately match records across scenarios, reducing the risk of duplications.
• Statement C:Listing identifying fields ahead of other columns in the update process helps in prioritizing these fields during the matching process, enhancing the accuracy of record linkage and minimizing duplication errors.

References

• Kinaxis RapidResponse documentation and best practices on Automation Chains and Scheduled Tasks.

References:The search did not yield specific documentation on best practices for cross-scenario updates in Kinaxis RapidResponse. However, these answers are aligned with general best practices for database management and updates to prevent duplication and ensure data integrity.

To determine the total number of unique customers that have orders for each part, the COUNT function with a By qualifier is used. This counts the number of unique instances of a field within a set, which in this case is the Customer field within the IndependentDemands.

ReferencesThe COUNT function with a By qualifier is detailed in the Kinaxis RapidResponse documentation regarding aggregation functions, which specifies how to count unique occurrences of a field within a data set.