Pass the Kinaxis RapidResponse Author KX3-003 Questions and answers with CertsForce

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.

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

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

Developing a cross scenario data change allows for controlled updates from child to parent scenarios, aligning with company policy on not adjusting lead times in shared scenarios.

To evaluate the impact of converting planned orders to scheduled receipts and then push changes to the parent scenario, while adhering to company policy that prohibits adjustments to lead times in shared scenarios:

Statement B:Develop a cross scenario data change. This will allow users to make their changes in their scenarios and then push these changes to the parent scenario. This method ensures that changes are captured and transferred correctly while adhering to the company’s policy regarding lead times.

References:

Scenario planning

Scenario planning capabilities in Kinaxis RapidResponse allow for testing changes in private scenarios before pushing them to shared ones1.

Change management

The Engineering Change Management application in RapidResponse supports evaluating the effect of changes and determining the optimal time for implementation, which can be adapted for evaluating the impact of converting planned orders2.

Kinaxis documentation suggests using scenarios to track changes and push them to parent scenarios without affecting system performance3.

Best practices in Kinaxis RapidResponse include maintaining the integrity of shared scenarios by not altering critical parameters like lead times45.

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

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.