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

Structure II shows BuyerCode connected to Department and Department connected to Manager. This setup supports multiple departments per manager while allowing for each department to be on a specific floor. Since users may want to filter on combinations of BuyerCode, Manager, Department, and Floor, this design accommodates such queries efficiently by structuring the Department as a central entity that relates to the others. In Structure II, Department is linked to BuyerCode and Manager, enabling a query to traverse from BuyerCode to Manager through Department, making it optimal for the desired filters.

ReferencesBest practices for database design suggest structuring your data model to reflect the relationships between entities in a way that supports the expected queries and filters. In Kinaxis RapidResponse, this often means creating a logical structure that minimizes join complexity and optimizes the data model for typical user operations.

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.

To provide a worksheet based on the CRPOperation table that reports the destination location and to view all valid work centers that feed a given stock location:

• Statement B:Create a reference field on the CRPOperation table to the Location table. This approach establishes a direct relationship between operations and their respective locations, enabling efficient reporting and querying capabilities for the secondary requirement of viewing work centers related to a stock location.

Creating a reference field on the CRPOperation table to the Location table (B) is the most efficient way to report destination location while allowing visibility of all valid work centers that feed a given stock location.

References:

• Kinaxis RapidResponse Author Level 3 training emphasizes the importance of efficient data modeling and reference creation for performance optimization1.
• The Kinaxis RapidResponse documentation suggests that creating direct references between tables ensures better performance than creating additional lookup tables or worksheets23.

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.

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.

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.

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

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

To enable customers to view only their independent demands within RapidResponse, profile variables and worksheet filters are used. The profile variable 'CustomerView' will be set to match the customer name to the user's group name. In the worksheet filter, theOrder.Customer.IDis the correct field to match against the profile variable because user IDs and customer IDs are more likely to be used as unique identifiers in system configurations, rather than customer names which could potentially have duplicates or variations.

Thus, when customers log in, the worksheet filter will apply, and they will only see the independent demands that correspond to their own customer ID, ensuring data visibility is restricted appropriately.

References:

• Kinaxis RapidResponse documentation on user group configuration and data access control.
• Kinaxis training materials on creating profile variables and configuring worksheet filters for personalized data views.

ReferencesThe information is based on the best practices for creating filters and profile variables within RapidResponse as indicated in the training materials and documentation provided by Kinaxis123.

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.

To pass information from columns in a worksheet to a script, the form controls used to collect input from users need to be mapped to the script arguments. This mapping allows the script to receive the column data as arguments. Additionally, making sure the names of the script arguments match the ID of the form controls is necessary for the script to correctly identify and use the data passed from the form.

ReferencesKinaxis RapidResponse documentation and best practices for forms and scripting indicate that mapping form controls to script arguments and ensuring the argument names match the control IDs are critical for passing data to scripts.

To track which performers are late and by how much for each activity in a process orchestration scenario, you need to access data that includes information on activity assignments, due dates, and completion status. The Assignment table within the ProcOrch (Process Orchestration) namespace contains this data. You can use this table to identify the performers assigned to each activity, check the planned completion dates against actual completion dates, and calculate the delays.

By creating a worksheet based on the Assignment table, you can include columns for activity IDs, performer IDs, due dates, completion dates, and a calculated field for the delay. The delay can be calculated by comparing the due date with the completion date or the current date if the activity is not yet completed. If there is more than one performer per activity, each performer's assignment will be a separate record in the Assignment table, allowing the worksheet to show delays for each performer.

References:

• Kinaxis RapidResponse documentation on creating worksheets based on specific tables.
• Training and knowledge resources provided by Kinaxis on how to use and configure worksheets in RapidResponse for process orchestration scenarios.

The expression that calculates the difference between the future EffectiveUnitTransferCost and the cost to transfer today would take the future cost and subtract the current cost converted to today's date, considering the transfer quantity. The CONVERTONDATE function is used to convert the historical TransferCost to its value as of today, and then this value is divided by Quantity to get the unit cost as of today. This unit cost is then subtracted from the EffectiveUnitTransferCost to find the difference.

ReferencesThis uses the CONVERTONDATE function in Kinaxis RapidResponse, which is designed to adjust historical cost figures to their equivalent value on a different date, accounting for factors such as currency fluctuation, as outlined in the Kinaxis formula and functions 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.