Pass the Kinaxis RapidResponse Author KX3-003 Questions and answers with ExamsMirror

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.

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.

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.

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.

Referring to the graphic, it appears that there is a target allocation ratio between Supplier 1 and Supplier 2 (not visible in the image, but this can be inferred from the allocation quantities). When a new demand for 800 units is introduced, the SourceRule.AllotmentRule set to OnGoing will distribute the demand based on the ongoing target ratio. Since Supplier 1 has a running total that far exceeds Supplier 2, and both have a 'Multiple Qty' of 250, the next allotment will attempt to balance the ongoing total closer to the target ratio. It's likely that the new demand will be allocated by filling up to the nearest multiple of 250 that does not exceed the demand. Therefore, Supplier 1 gets 250, and the remaining 550 units would go to Supplier 2. Since Supplier 2 also must supply in multiples of 250, it rounds up to 750 units.

ReferencesThis understanding is derived from the Kinaxis RapidResponse concepts for managing supply allocations and the behavior of ongoing rules as described in the Kinaxis RapidResponse documentation.

References:

The Kinaxis RapidResponse documentation on SourceRule.AllotmentRule indicates that ongoing allotment is based on the target ratios set for suppliers1.

The Certified RapidResponse Author Level 3 materials cover the configuration and implications of SourceRule.AllotmentRule settings2.

The OrderGenerationRule of 'AfterPTF' with a LeadTime of 2 days and a PlanningTimeFence (PTF) of 2 means that planned orders will be generated for demands occurring after the planning time fence period, considering the lead time for production. Table II shows negative balances past the planning time fence (06-01 and 06-02 are within the planning time fence), indicating planned orders are created after these dates to cover upcoming demands. Therefore, planned orders appear on 06-04 and 06-05, taking into account the 2-day lead time post the planning time fence.

ReferencesThis follows Kinaxis RapidResponse rules for order generation where the PlanningTimeFence and LeadTime dictate when planned orders are created in response to demand, as detailed in the Kinaxis documentation on planning strategies.

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 ensure that neither worksheet is taking advantage of cached results, which could skew performance comparisons, you should close the workbook and any library workbooks it depends on. By reopening the workbook after this, you force RapidResponse to reload the data and recalculate the worksheets from scratch, ensuring that you are capturing performance results without the influence of previously cached data.

ReferencesKinaxis RapidResponse performance tuning guidance suggests that to accurately test the performance impact of changes, all cached data should be cleared. This can be achieved by closing and reopening the workbooks, as indicated in the Kinaxis RapidResponse resources on performance management.

When you share a scheduled task with other users in Kinaxis RapidResponse and the option "When other users run this scheduled task, run as: Scheduled task owner" is selected, those users will be able to run the task using the resource access rights of the task owner. This means that even if the users do not have access to all the resources used in the task, they can still run it because the task will execute with the owner's permissions.

ReferencesThe Kinaxis RapidResponse help documentation explains how sharing and permissions work, including details on what happens when scheduled tasks are shared with users who might not have access to all the necessary resources.

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.