RapidResponse Author KX3-003 Updated Exam

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.

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 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.

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.