Free Kinaxis KX3-003 Practice Exam with Questions & Answers | Set: 2

• Create a reference field on the ScheduledReceipt table to the WorkOrderInfo table.
• Display relevant work order data in worksheets based on the ScheduledReceipt table and the referenced WorkOrderInfo table.

Very Detailed ExplanationThe best practice in this scenario, according to Kinaxis, is to create a reference from the ScheduledReceipt table to the WorkOrderInfo table. This allows for direct linking of records between these tables. The worksheets based on the ScheduledReceipt data can then leverage this reference to display related information from the WorkOrderInfo table, ensuring that the data is accurately aligned and easily accessible for reporting and analysis.

ReferencesThis recommendation aligns with Kinaxis’s guidance for structuring worksheets and data models to efficiently report and analyze data from multiple related tables without the need for redundant worksheets or complex lookup structures.

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.

When forecasts are spread into smaller time intervals using a spreading profile, the quantities are distributed according to the specified proportions in the profile. The graphic indicates that the profile points are 20, 20, 25, and 35 for each of the four weeks, respectively. To spread the monthly forecast of 500 units into weekly intervals, you multiply each proportion by the monthly forecast and divide by the sum of the profile points. So, (20/100) * 500 for the first two weeks, (25/100) * 500 for the third week, and (35/100) * 500 for the fourth week, which results in the weekly forecasts of 100, 100, 125, and 175, respectively.

ReferencesThe calculation uses basic arithmetic based on the principles of proportionally spreading a total quantity across a defined profile, as described in the Kinaxis RapidResponse demand planning documentation.

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.

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.

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

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.

A. Enabling the Bucket data by date checkbox and setting the Bucket Size to Day and the Number of Buckets to 730 would directly create a view that organizes daily historical data into daily buckets spanning the last two years (since there are 365 days in a year, multiplied by 2).

C. Creating calendar interval, start date, and end date variables using the CalendarDate table allows for the configuration of a custom time range in the worksheet. These variables can be referenced to display historical data for the desired period.

B is not correct because adjusting the Anchor date by 1 year would only provide data for the last year, not two. D is not correct because it suggests a method of filtering data by date without bucketing, which does not align with the requirement to show historical data in daily buckets.

References:

• Kinaxis RapidResponse documentation on bucketing data by date.
• Kinaxis support resources on configuring worksheets with date variables and bucketing.

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.