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

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.

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.

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

The migration of the Supplier.Id filter to the secondary filter expression box allows for enabling caching because it is a user-specific filter. Moving user-specific or session-specific expressions to the secondary filter ensures that the primary filter can be cached independently of user sessions. This way, the overall data set can be cached, and the user-specific filtering is applied afterward, improving performance.

References:

Kinaxis RapidResponse documentation on primary and secondary worksheet filters.

Kinaxis support resources on caching strategies and performance improvements for worksheets.

The script is performing a data import operation into a worksheet that is configured to allow importing data for the purpose of inserting records, as shown in the worksheet properties exhibit. The JSON object in the console output would reflect the result of this import operation. The object details the number of records deleted, modified, and inserted. Since the worksheet is set up only to allow insertion, and the script is importing data for insertion, the "inserted" key would have a value of 1, and "deleted" and "modified" would have a value of 0, indicating a successful insert without any deletions or modifications.

References Kinaxis RapidResponse documentation for data importing and console operations would support this behavior, outlining how the importData method interacts with worksheet configurations.

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.

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

References In 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 data 1 .

Kinaxis RapidResponse documentation suggests that the query engine follows the path from the broadest category down to the specific records that match the criteria 2 .

If each order is associated with a single salesperson and the goal is to filter records by the salesperson's name, the most straightforward solution is to add a field directly to the DemandOrder table where orders are recorded. This avoids unnecessary joins to another table and simplifies the data model. According to database normalization principles, if the field is non-repetitive and directly related to the entity (in this case, the order), it should be placed on the same table.

References The addition of a single attribute that is not multi-valued, non-repeating, and directly related to the primary key in the table aligns with the first normal form (1NF) in database normalization. This approach is also supported by Kinaxis best practices for efficient data retrieval.

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

References Allocation 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 demands 1 2 .

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

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

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.

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

References This 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 model 1 2 .

The Kinaxis documentation on data modeling and table creation within RapidResponse provides guidelines on how to manage namespaces and their dependencies 3 4 .

A. In the ItemDetail table, making Name plus Site a compound reference to the Item table aligns with relational database principles where a foreign key references a primary key in another table.

C. In the TransactionDetail table, making ID, Owner, and Type a reference to the TransactionHeader table follows the foreign key to primary key relationship as well, where TransactionDetail refers to its header record.

E. In the TransactionDetail table, making ItemName plus ItemSite a reference to the Item table ensures that each transaction detail record is linked to an existing item record, enforcing referential integrity.

B is incorrect because the TransactionHeader table should not reference the TransactionDetail table; it should be the other way around. D is incorrect because the Item table should not reference the ItemDetail table; this too should be the other way around.

References:

Kinaxis RapidResponse documentation on data modeling and relationships between tables.

Standard SQL database design principles as they apply within the RapidResponse environment.

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 report the date used to convert the calculated field EffectiveUnitPrice, the CONVERTONDATE function is the appropriate one to use. This function converts a measure's value from one date to the value it would have on another date. The $ConversionDate variable (or similar) would typically be used within the worksheet to reference the date to which the conversion is applied.

References The Kinaxis RapidResponse documentation on calculated fields and conversion functions explains how the CONVERTONDATE function is used to adjust financial measures based on changes over time, which would apply to fields such as EffectiveUnitPrice.

B. By adding a column to map the bucket dates in the spreading worksheet, you ensure that the start and end dates of the spreading are properly defined and can be utilized in the algorithm.

D. Selecting "Use same spreading worksheet values for all edits" ensures that the values entered in the buckets are consistent across the worksheet, which is necessary for the spreading functionality to work correctly.

A is incorrect because removing unmapped columns does not solve the issue related to spreading values across the buckets. C is incorrect because allowing editing only if all buckets are the same size is a constraint that does not address the mapping issue.

References:

Kinaxis RapidResponse support articles on troubleshooting and configuring spreading worksheets.

Kinaxis community discussions on common issues and solutions related to worksheet design.

To resolve the issue with the workbook designed for spreading values, it is necessary to ensure that the bucket dates are properly mapped in the spreading worksheet. This allows the system to recognize and apply the correct time horizon for the spread. Additionally, selecting the option to use the same spreading worksheet values for all edits ensures consistency across the worksheet.

References:

Kinaxis RapidResponse Author Level 3 certification materials 1 .

Enhanced troubleshooting skills and best practices as mentioned in the Kinaxis Certification Program 2 .