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

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.

Using the NOT IN operator with the key fields from the PlannedOrder table in the LKPScheduledReceipt worksheet is the most direct and efficient way to excluderecords that already exist. This filter checks if the combination of Part and DueDate from PlannedOrder records does not exist in the LKPScheduledReceipt worksheet, ensuring that only new ScheduledReceipt records will be created.

ReferencesThe best practices for filter expressions in Kinaxis RapidResponse workbooks, as described in the documentation, recommend using simple and direct expressions that efficiently exclude existing records to improve performance.

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.

This setup allows for flexible data visibility based on user permissions. By creating a profile variable that contains the allowed countries for each user, you can then apply a filter expression to the worksheet that evaluates this variable. If a user is permitted to see all countries (indicated by an asterisk '*'), the expression returns TRUE, otherwise, it checks if the demand's country is in the user's permitted list.

References:

Kinaxis RapidResponse documentation on configuring data visibility through profile variables and worksheet filters.

Kinaxis training materials on setting up user permissions and responsibility definitions.

When an automation chain step that runs in parallel with other steps is removed, it does not affect the operation of the remaining steps. The other steps that were originally set up to run in parallel will continue to run in parallel unless their configuration is changed manually.

ReferencesKinaxis RapidResponse's documentation on automation chains clarifies the behavior of parallel steps in an automation chain when one step is modified or removed. The behavior and configuration of the remaining steps persist until they are manually changed.

References:The answer is based on general knowledge of automation chains and parallel processing.For specific Kinaxis RapidResponse functionality, please refer to the official training materials and documentation123.

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.

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.

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.