KX3-003 Sample Questions Answers

A. The DeliveryRoutes being a Set data type indicates that there can be multiple Delivery Routes referencing a carrier, allowing for one-to-many relationships between a carrier and delivery routes.

C. The Shipments being a Set data type as well indicates that multiple shipments can reference a single carrier, also suggesting a one-to-many relationship.

D. The DefaultTransportationMode being a Reference data type allows for the possibility that several carriers can share the same transportation mode, as references do not enforce uniqueness.

B is not correct because the TransitCalendar being a Reference data type indicates a one-to-one relationship; each carrier can reference only one Transit Calendar. E is also incorrect because the Sources field being a Set data type implies that a carrier can be associated with multiple sources.

References:

• Kinaxis RapidResponse documentation on data modeling and table relationships.
• Kinaxis learning resources on understanding data types and their implications on table relationships.

To enable data caching on a worksheet, you should minimize the dynamic content that can cause the cache to become outdated quickly. Removing hierarchy columns can improve performance because hierarchies often involve complex joins and calculations that can slow down data retrieval. Disabling the "Use As Reference" checkbox on the Part column means that changes in the Part table will not cause the cache to be invalidated, which can be beneficial if the Part data does not change frequently.

References:

• Kinaxis RapidResponse documentation on worksheet performance optimization.
• Kinaxis best practices for enabling and managing data caching in worksheets.

B. By adding a column to map the bucket dates in the spreading worksheet, you ensure that the start and end dates of the spreading are properly defined and can be utilized in the algorithm.

D. Selecting "Use same spreading worksheet values for all edits" ensures that the values entered in the buckets are consistent across the worksheet, which is necessary for the spreading functionality to work correctly.

A is incorrect because removing unmapped columns does not solve the issue related to spreading values across the buckets. C is incorrect because allowing editing only if all buckets are the same size is a constraint that does not address the mapping issue.

References:

• Kinaxis RapidResponse support articles on troubleshooting and configuring spreading worksheets.
• Kinaxis community discussions on common issues and solutions related to worksheet design.

To resolve the issue with the workbook designed for spreading values, it is necessary to ensure that the bucket dates are properly mapped in the spreading worksheet. This allows the system to recognize and apply the correct time horizon for the spread. Additionally, selecting the option to use the same spreading worksheet values for all edits ensures consistency across the worksheet.

References:

• Kinaxis RapidResponse Author Level 3 certification materials1.
• Enhanced troubleshooting skills and best practices as mentioned in the Kinaxis Certification Program2.

To highlight differences between scenarios, a hidden column that calculates the difference (QuantityDelta) can be created. The actual Quantity column would show the actual value, while the QuantityDelta column would calculate the difference between the baseline scenario and the comparison scenario. Conditional formatting can then be applied to the Quantity column to highlight when the QuantityDelta is not equal to zero, indicating a difference between the scenarios.

ReferencesThe method for comparing scenario data and highlighting differences using conditional formatting is a common practice in Kinaxis RapidResponse, as outlined in the application's user guide and best practices for building worksheets.

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.

Matching the sort order and direction in both component worksheets before creating a composite worksheet can improve performance. This alignment ensures that the composite worksheet does not have to re-sort the data from each component worksheet, which can be computationally expensive, especially for large datasets.

ReferencesThe recommendation to match sort orders and directions for performance optimization in composite worksheets is in line with best practices for data management in Kinaxis RapidResponse, which can be found in the training and documentation materials.

• Create a reference field on the ScheduledReceipt table to the WorkOrderInfo table.
• Display relevant work order data in worksheets based on the ScheduledReceipt table and the referenced WorkOrderInfo table.

Very Detailed ExplanationThe best practice in this scenario, according to Kinaxis, is to create a reference from the ScheduledReceipt table to the WorkOrderInfo table. This allows for direct linking of records between these tables. The worksheets based on the ScheduledReceipt data can then leverage this reference to display related information from the WorkOrderInfo table, ensuring that the data is accurately aligned and easily accessible for reporting and analysis.

ReferencesThis recommendation aligns with Kinaxis’s guidance for structuring worksheets and data models to efficiently report and analyze data from multiple related tables without the need for redundant worksheets or complex lookup structures.

Developing a cross scenario data change allows for controlled updates from child to parent scenarios, aligning with company policy on not adjusting lead times in shared scenarios.

To evaluate the impact of converting planned orders to scheduled receipts and then push changes to the parent scenario, while adhering to company policy that prohibits adjustments to lead times in shared scenarios:

• Statement B:Develop a cross scenario data change. This will allow users to make their changes in their scenarios and then push these changes to the parent scenario. This method ensures that changes are captured and transferred correctly while adhering to the company’s policy regarding lead times.

References:

Scenario planning

• Scenario planning capabilities in Kinaxis RapidResponse allow for testing changes in private scenarios before pushing them to shared ones1.

Change management

• The Engineering Change Management application in RapidResponse supports evaluating the effect of changes and determining the optimal time for implementation, which can be adapted for evaluating the impact of converting planned orders2.

• Kinaxis documentation suggests using scenarios to track changes and push them to parent scenarios without affecting system performance3.

• Best practices in Kinaxis RapidResponse include maintaining the integrity of shared scenarios by not altering critical parameters like lead times45.

The ListAsSet function in Kinaxis RapidResponse expects a set of elements as input, typically in the format of a string with elements enclosed in single quotes and separated by commas. For a user that should see data for suppliers A, B, and C, you need to format the string to match this expected input format.

References:

• Kinaxis RapidResponse documentation on the ListAsSet function and profile variables.
• Kinaxis community discussions or support articles on configuring profile variables for user-specific views.

References: The information is based on the Kinaxis RapidResponse documentation and learning resources, which provide guidelines on how to properly format expressions and variables for worksheets.

Given that the control table setting for OrderPriority.AllocationRule is FairShare and all demands are the same priority, the available supply quantity will be allocated evenly among the demands. The graphic shows there are demands due on Monday, Tuesday, and Wednesday with planned orders due on each day as well. If the total supply on Thursday is not specified in the question, we assume it is enough to meet or exceed the demand. Since all demands have the same priority and the allocation rule is FairShare, the entire supply quantity for Thursday will be evenly distributed. Without the exact supply quantity, the best assumption is that the full quantity needed for the demand due on Wednesday will be allocated.

ReferencesThis explanation is based on the FairShare allocation rule which distributes available supply evenly across all demands when they have the same priority, as per the Kinaxis RapidResponse documentation on supply allocation.

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.

Adding a dedicated input table with a single key reference to the Customer table and a field for the MostRecentOrderDate is the most memory-efficient approach. This design avoids adding additional fields to tables that may contain a large numberof records, which would increase memory usage. Instead, the MostRecentOrderDate is stored once per customer in a separate table, minimizing the memory footprint and optimizing query performance since only the relevant data is accessed.

References:

• Kinaxis RapidResponse documentation on data modeling and performance optimization.
• Best practices in database normalization and data model efficiency provided by Kinaxis.

The expression to display the number of the calendar week from the beginning of the year takes today's date, resets it to the start of the year (the 0 Year part), and then calculates the week number from this start date, adding 1 since week numbers generally start at 1, not 0.

ReferencesThe logic for calculating week numbers from a given date is commonly described in Kinaxis RapidResponse documentation and training materials concerning date and time functions.

In the context of creating a metric worksheet for calculating the number of late orders, you want to group by DueDate to consolidate orders that are due on the same day, and then sum the Count for each of these groups to get the total number of late orders per day. Therefore, DueDate should be the grouping column, and Count should use the Sum function to add up all instances of late orders for each DueDate.

References:

• Kinaxis RapidResponse documentation on creating metric worksheets.
• Kinaxis learning resources on the use of expressions and functions for grouping and aggregation in worksheets.

A. Enabling the Bucket data by date checkbox and setting the Bucket Size to Day and the Number of Buckets to 730 would directly create a view that organizes daily historical data into daily buckets spanning the last two years (since there are 365 days in a year, multiplied by 2).

C. Creating calendar interval, start date, and end date variables using the CalendarDate table allows for the configuration of a custom time range in the worksheet. These variables can be referenced to display historical data for the desired period.

B is not correct because adjusting the Anchor date by 1 year would only provide data for the last year, not two. D is not correct because it suggests a method of filtering data by date without bucketing, which does not align with the requirement to show historical data in daily buckets.

References:

• Kinaxis RapidResponse documentation on bucketing data by date.
• Kinaxis support resources on configuring worksheets with date variables and bucketing.