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

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.

Considering that Demand 2 has a higher priority than Demand 1 (as indicated by "High" versus "Medium"), it will be allocated available supplies before Demand 1, following the priority rules. SR1 is scheduled for Monday and will likely be allocated to Demand 1, being the first demand of the week. For Demand 2, SR2 is the nextavailable and will fulfill 200 units. Since Demand 2 requires 300 units and SR2 only supplies 200, the next available SR, which is SR3, will cover the remaining 100 units needed.

ReferencesAllocation of supplies to demands in Kinaxis RapidResponse takes into account both the chronological order of the scheduled receipts and the priority of the demands. This is consistent with Kinaxis's allocation rules as outlined in the RapidResponse documentation.

References:

• The Kinaxis RapidResponse documentation indicates that scheduled receipts are allotted based on priority and availability, with earlier dates being allocated first to meet high-priority demands12.

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 AvailableRule control table is used to define how available dates for supply and demand are calculated in Kinaxis RapidResponse. This includes the rules for when supplies are considered available for meeting demand and vice versa, such as lead times, transit times, and other considerations that might affect when a part can realistically be expected to be available.

ReferencesThe function of the AvailableRule control table and its impact on the calculation of available dates for supplies and demands is outlined in Kinaxis RapidResponse configuration settings for supply chain planning processes.

A filter based on the IndependentDemand table would improve the performance of a worksheet based on the WhereConsumedForDemand table, assuming that the demand is what drives the consumption. By filtering on IndependentDemand, you reduce the number of records the worksheet needs to process, thus improving load times and responsiveness, especially if there are a large number of records in the WhereConsumedForDemand table.

ReferencesThe Kinaxis RapidResponse documentation suggests that filtering based on driving factors such as demand can significantly enhance performance by narrowing down the data set to the most relevant records.

Turning off bucket settings can improve performance by reducing the computational load required to generate the buckets. Adding an expression to filter out records that are beyond the one-year horizon ensures that only data relevant to the desired timeframe (one year's worth of forecast records) is displayed. This streamlines the data set, potentially improving load times and making the worksheet more responsive.

ReferencesKinaxis RapidResponse documentation recommends streamlining worksheet data and using filters to improve performance, especially when dealing with large data sets or long time horizons.

References:The answer is based on general best practices for performance improvement in data systems, which suggest limiting data to the necessary scope.Specific Kinaxis RapidResponse documentation cannot be accessed or verified by me, so please refer to the official Kinaxis training materials for RapidResponse Author Level 3 for detailed guidance12.

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.

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

When setting the bucket date in an insert definition, if the requirement is to have the record due on the last workday of the week (which is Friday or Thursday if Friday is a non-workday), then the correct approach is to configure the insert definition to use the last workday in the bucket. This will ensure that the due date falls on the correct day according to the specified requirement.

ReferencesThe Kinaxis RapidResponse documentation details how to use bucket dates and adjust them according to workdays in the insert definition setup for crosstab worksheets.

The code block IV is correctly using the script execution pattern in RapidResponse. It first gets the script usingrapidResponse.scripts.get()method with the correct parameters for the name and scope, and then calls the script with.call()method, passing the necessary scenario argument. This is how you would invoke another script from within a script.

ReferencesThe use ofrapidResponse.scripts.get()andcall()methods is standard practice in Kinaxis RapidResponse for executing one script from within another, as detailed in the Kinaxis RapidResponse scripting documentation.

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.

Performance issues often stem from the complexity of calculations and the size of the data sets they are applied to. In this case, the use of a calculated field (NameAndDescription) in the hierarchy definition is the most likely cause of performance degradation. This field is calculated on the fly using a concatenation of the Name and Description, which is a more resource-intensive process compared to using static fields.

Calculated fields, especially those involving string operations like concatenation, can be significantly slower because they require runtime computation. This contrasts with static fields that are indexed and retrieved directly from the database without additional computational overhead.

References:

• Kinaxis RapidResponse documentation on hierarchy design and performance considerations.
• Kinaxis best practices for creating efficient hierarchies and using calculated fields.

Using a calculated field, especially one that concatenates strings like in option C, can significantly impact performance because it requires additional computation for each record. This is more resource-intensive than using a direct field value, which would explain the poorer performance when using the PartFamily hierarchy compared to the PartPlanner hierarchy.

References:

• Kinaxis RapidResponse Author Level 3 training materials1.
• Web search results and Kinaxis best practices2.

When defining a new table in the TRM namespace that requires a key reference to a table in another namespace (in this case, the Mfg namespace), you must add the namespace containing the referenced table as a dependency to the namespace where the new table will be created. By doing this, the new namespace acknowledges the existence of the other namespace and its tables, allowing for proper reference linking. This is why the correct action to take is to add the Mfg namespace as a dependency for the TRM namespace.

ReferencesThis information is in line with the principles of data modeling in Kinaxis RapidResponse, where namespaces serve as containers for data model components such as tables and fields, and dependencies between namespaces must be defined to create cross-references between tables located in different namespaces.

References:

• Kinaxis RapidResponse Author Level 3 training materials emphasize the importance of setting dependencies between namespaces to ensure proper reference and functionality within the data model12.
• The Kinaxis documentation on data modeling and table creation within RapidResponse provides guidelines on how to manage namespaces and their dependencies34.

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.