KX3-003 Practice Exam Questions with Answers Certified RapidResponse Author Level 3 Exam Certification

To identify an automation chain and its associated resources, searching for resources based on the specific table involved in the automation (in this case, "HistoricalPartKPI") will help you find the correct automation chain. This approach ensures that you identify all the resources related to that particular table, including automation chains.

ReferencesThe Kinaxis RapidResponse documentation for administrators provides guidance on how to search for and identify resources associated with specific tables or actions within the system, which includes searching for resources based on table names.

To highlight differences between scenarios, a hidden column that calculates the difference (QuantityDelta) can be created. The actual Quantity column would show the actual value, while the QuantityDelta column would calculate the difference between the baseline scenario and the comparison scenario. Conditional formatting can then be applied to the Quantity column to highlight when the QuantityDelta is not equal to zero, indicating a difference between the scenarios.

ReferencesThe method for comparing scenario data and highlighting differences using conditional formatting is a common practice in Kinaxis RapidResponse, as outlined in the application's user guide and best practices for building worksheets.

To determine the total number of unique customers that have orders for each part, the COUNT function with a By qualifier is used. This counts the number of unique instances of a field within a set, which in this case is the Customer field within the IndependentDemands.

ReferencesThe COUNT function with a By qualifier is detailed in the Kinaxis RapidResponse documentation regarding aggregation functions, which specifies how to count unique occurrences of a field within a data set.

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 create a modify command that updates the DueDate field with the New Due Date, it’s essential to simplify the worksheet. Making the Order column a reference and removing unnecessary columns like Order Site, Order Type, Control Set, and Line ensures that the modify command focuses on the relevant data for the update.

References:The search did not yield specific documentation on creating modify commands in Kinaxis RapidResponse.However, the answer aligns with general best practices for simplifying data management tasks123.

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.

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.

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

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

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.

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.

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.

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.

The SalesForecast for the TV family is for 1000 units, as shown in the graphic. The MPSConfig planning BOM will generate a planned order equal to the SalesForecast quantity because there is no available supply. OptionRatio and QuantityPer indicatethe proportion of the forecast to be planned for each product type (LCD and Plasma), not the total quantity to be planned. Therefore, the planned order quantity will match the total forecasted demand, which is 1000 units.

ReferencesThis conclusion is drawn from the Master Production Schedule (MPS) and Bill of Materials (BOM) configuration rules within Kinaxis RapidResponse. When there is no supply to meet demand and forecasts are being translated into planned production, the full amount of the forecast typically becomes the planned order quantity.