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.

To identify an automation chain and its associated resources, searching for resources based on the specific table involved in the automation (in this case, "HistoricalPartKPI") will help you find the correct automation chain. This approach ensures that you identify all the resources related to that particular table, including automation chains.

ReferencesThe Kinaxis RapidResponse documentation for administrators provides guidance on how to search for and identify resources associated with specific tables or actions within the system, which includes searching for resources based on table names.

The script is performing a data import operation into a worksheet that is configured to allow importing data for the purpose of inserting records, as shown in the worksheet properties exhibit. The JSON object in the console output would reflect the result of this import operation. The object details the number of records deleted, modified, and inserted. Since the worksheet is set up only to allow insertion, and the script is importing data for insertion, the "inserted" key would have a value of 1, and"deleted" and "modified" would have a value of 0, indicating a successful insert without any deletions or modifications.

ReferencesKinaxis RapidResponse documentation for data importing and console operations would support this behavior, outlining how the importData method interacts with worksheet configurations.

Structure II shows BuyerCode connected to Department and Department connected to Manager. This setup supports multiple departments per manager while allowing for each department to be on a specific floor. Since users may want to filter on combinations of BuyerCode, Manager, Department, and Floor, this design accommodates such queries efficiently by structuring the Department as a central entity that relates to the others. In Structure II, Department is linked to BuyerCode and Manager, enabling a query to traverse from BuyerCode to Manager through Department, making it optimal for the desired filters.

ReferencesBest practices for database design suggest structuring your data model to reflect the relationships between entities in a way that supports the expected queries and filters. In Kinaxis RapidResponse, this often means creating a logical structure that minimizes join complexity and optimizes the data model for typical user operations.

The expression that calculates the difference between the future EffectiveUnitTransferCost and the cost to transfer today would take the future cost and subtract the current cost converted to today's date, considering the transfer quantity. The CONVERTONDATE function is used to convert the historical TransferCost to its value as of today, and then this value is divided by Quantity to get the unit cost as of today. This unit cost is then subtracted from the EffectiveUnitTransferCost to find the difference.

ReferencesThis uses the CONVERTONDATE function in Kinaxis RapidResponse, which is designed to adjust historical cost figures to their equivalent value on a different date, accounting for factors such as currency fluctuation, as outlined in the Kinaxis formula and functions documentation.

The DaysSupplyRule set to ByPeriod with a PeriodSupplyInterval of a Week means that the planned orders will be generated to cover demands within each supply interval (week) separately. For the first week, the total demand is 25+15+30=70, but the order quantity is rounded up to the nearest multiple of the Days of Supply number, which is 2. Therefore, the order quantity is 80. For the second week, the demand is 40+20+15=75, which matches the Days of Supply number, hence no rounding is needed, and the order quantity is 75.

ReferencesThis answer is based on the Kinaxis RapidResponse concepts for demand and supply planning where Days of Supply calculations determine the size and timing of planned orders, considering the rules set for supply intervals and calendars.

To ensure that a forecast entry is spread correctly across multiple sites, the Site column in the spreading worksheet must be mapped to the Part.Site field. This way, the system knows how to allocate the entered forecast quantity among the different sites associated with the part.

A is incorrect because changing the base table from Part to IndependentDemand would not directly address the issue of distributing the forecast across sites. B is not relevant to the error because mapping the Name to Part.Name does not affect the distribution of forecast quantities across sites. D is not correct because adding a Date column to the spreading worksheet is not related to solving the error associated with distributing forecast quantities across sites.

References:

• Kinaxis RapidResponse documentation on forecast entry and spreading across sites.
• Kinaxis support articles on troubleshooting forecast entry errors and worksheet configurations.

Line A withcmdDeleteData.execute();would execute a command to delete data in RapidResponse, which, if configured correctly, would delete records. Line C withwsOrderChng.remove(dataArray);is a method that would also potentially delete records from the worksheet if the dataArray contains the correct keys for the records that need to be removed.

ReferencesThe Kinaxis RapidResponse scripting and workbook API documentation explain the methodsexecute()for running commands andremove()for removing data from worksheets. Both can be used to delete records when executed with the proper context and data.

To provide a worksheet based on the CRPOperation table that reports the destination location and to view all valid work centers that feed a given stock location:

• Statement B:Create a reference field on the CRPOperation table to the Location table. This approach establishes a direct relationship between operations and their respective locations, enabling efficient reporting and querying capabilities for the secondary requirement of viewing work centers related to a stock location.

Creating a reference field on the CRPOperation table to the Location table (B) is the most efficient way to report destination location while allowing visibility of all valid work centers that feed a given stock location.

References:

• Kinaxis RapidResponse Author Level 3 training emphasizes the importance of efficient data modeling and reference creation for performance optimization1.
• The Kinaxis RapidResponse documentation suggests that creating direct references between tables ensures better performance than creating additional lookup tables or worksheets23.