KX3-003 Certified RapidResponse Author Level 3 Exam Question and Answers

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.

The filter expression contains a path that starts from ProductFamily, going down to ProductGroup, then ProductNumber, and Part, and finally linking to Customer prices. This path represents a 'line of descent' where the query engine filters down from the highest level of hierarchy (ProductFamily) to the desired records (CustomerPartPrices), respecting the AND logic to include only those records where the ProductFamily is either 'bikes' or 'trikes' and the Customer's Country is "US" or "CA". This is the logical path of filters applied in sequence according to the hierarchy laid out in the filter expression.

ReferencesIn Kinaxis RapidResponse, filter expressions are used to specify the subset of data that you want to retrieve. The reference to 'line of descent' reflects how the RapidResponse query engine processes the filters along the hierarchy of related tables. This is consistent with the Kinaxis RapidResponse Author Level 3 documentation on advanced filtering and data retrieval strategies.

References:

• The filter expression indicates a top-down approach, starting from the product hierarchy and moving towards customer-related data1.
• Kinaxis RapidResponse documentation suggests that the query engine follows the path from the broadest category down to the specific records that match the criteria2.

To ensure that suppliers only receive reports relevant to their purchase orders, a profile variable tied to the supplier's user group is used to filter the report data. The Notify tab in the Alert properties window is used to configure the report distribution to the appropriate supplier's user group, ensuring that each supplier gets the tailored report.

References:

• Kinaxis RapidResponse documentation on creating user groups, profile variables, and configuring alerts for report distribution.
• Kinaxis training materials on workbook filter expressions and alert notification settings.

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.

To pass information from columns in a worksheet to a script, the form controls used to collect input from users need to be mapped to the script arguments. This mapping allows the script to receive the column data as arguments. Additionally, making sure the names of the script arguments match the ID of the form controls is necessary for the script to correctly identify and use the data passed from the form.

ReferencesKinaxis RapidResponse documentation and best practices for forms and scripting indicate that mapping form controls to script arguments and ensuring the argument names match the control IDs are critical for passing data to scripts.

The worksheet properties shown in the graphic indicate how to calculate the change in theAvailableDateofIndependentDemandbetween a child and its parent scenario. Configuration II shows the expression[:AvailableDate#0 - :AvailableDate#1 Workday], where#0refers to the child scenario and#1refers to the parent scenario. This expression calculates the difference in workdays between theAvailableDateof the independent demand in the child scenario and the parent scenario.

The worksheet should be set to calculate using the final results from other columns, ensuring that it takes into consideration the latest available data from the child and parent scenarios for accurate calculation of the workday difference.

References:

• Kinaxis RapidResponse documentation on worksheet expressions and scenario comparison.
• Kinaxis training materials on configuring worksheets for scenario analysis.

For the sales staff to add forecasts, they need a framework that allows them to inputdata within a specified range (hence Start Date and End Date variables). A Calendar workbook variable set to 'Month' will align the input with the monthly granularity required. A custom Insert Definition is needed to facilitate the input of new forecast data. Including only the necessary columns would streamline the process, but it does not directly contribute to enabling the forecast addition as required by the client, hence why E is not a correct choice here.

References:

• Kinaxis RapidResponse documentation on setting up worksheets for forecast entry.
• Kinaxis learning resources on workbook variables and custom insert definitions.

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.

To identify the buyer responsible for the component part, you would use the Responsibility function with the appropriate role and the component part as arguments. The resulting column should display the user name, which allows you to interact with that user directly from the worksheet, including inviting to a collaboration, messaging, and sharing scenarios. Enabling the "Display as user name" checkbox on the Column Formatting tab would provide this functionality directly in the worksheet.

ReferencesThe Kinaxis RapidResponse function library contains the Responsibility function and outlines how to display responsible parties for certain records. Additional user interface functionalities such as messaging and collaboration options are detailed in the system's user management and worksheet configuration sections.

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.

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.

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.

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.

In the WhereConsumed table, the PegPart represents the item driving the need for the component. In this case, the independent demand for AAA requires components BBB and DDD to be produced. The DriverPart is the direct parent in the Bill of Material (BOM) for DDD, which is BBB. The NeedQuantity is calculated by multiplying the demand for AAA by the quantity per of BBB (100 units * 4) and then by the quantity per of DDD (400 units * 4), resulting in a NeedQuantity of 1600 for DDD.

ReferencesThis answer follows the logic of BOM explosion and the principles of MRP (Material Requirements Planning) that can be found in the Kinaxis RapidResponse documentation, which outlines how to calculate the required quantities of each item in the BOM based on the independent demand.