Kinaxis KX3-003 Certified RapidResponse Author Level 3 Exam Exam Practice Test

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

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

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 the order policies of MultipleQty: 10, MinimumQty: 15, MultipleUsage: Use, and MinimumUsage: Use, the sizes of the planned orders are determined by rounding up to meet the minimum quantity and then to the nearest multiple of the MultipleQty. Order A needs to meet the demand of 25, so it must at least meet the MinimumQty of 15 and then round up to the nearest multiple of 10, which is 30. Order B, with a demand of 12, will also round up to the minimum quantity of 15 and then to the nearest multiple of 10, which is 20, since the MultipleUsage is "Use." The same logic applies to order C, with an initial demand of 20, it is already at a multiple of 10, so it remains 20.

ReferencesThis answer applies the principles of order quantity rounding based on multiples and minimums as commonly used in supply chain planning and as described in Kinaxis RapidResponse's order policy settings.

References:

• The Kinaxis RapidResponse documentation and training materials provide guidelines on how to apply order policies to determine the sizes of planned orders123.

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

The DaysSupplyRule set to ByPeriod with a PeriodSupplyInterval of a Week means that the planned orders will be generated to cover demands within each supply interval (week) separately. For the first week, the total demand is 25+15+30=70, but the order quantity is rounded up to the nearest multiple of the Days of Supply number, which is 2. Therefore, the order quantity is 80. For the second week, the demand is 40+20+15=75, which matches the Days of Supply number, hence no rounding is needed, and the order quantity is 75.

ReferencesThis answer is based on the Kinaxis RapidResponse concepts for demand and supply planning where Days of Supply calculations determine the size and timing of planned orders, considering the rules set for supply intervals and calendars.

To manage the demand forecast effectively while simplifying user controls, enabling hierarchy columns would allow users to make selections across different levels of the data hierarchy in one go. For instance, if a user wanted to select a particular product for a specific customer region and distribution site, they could do so without navigating through multiple filters. Additionally, having a hierarchy available for users to select regional distribution sites will allow them to filter data based on their particular region, which aligns with the management of demand forecast by customer region and distribution site. Disabling default filters that are not relevant to the users’ needs can also simplify the user experience but is not specifically mentioned in the given options.

ReferencesThe guidance is based on Kinaxis RapidResponse workbooks best practices, which suggest using hierarchies for filtering to simplify user experience and enable efficient data navigation, as documented in the RapidResponse Author Level 3 training resources.

References:

• Kinaxis RapidResponse documentation highlights the importance of using hierarchies to simplify user controls and enhance data management within workbooks1.
• The Certified RapidResponse Author Level 3 badge details the skills required to create and edit various types of complex workbooks, which includes managing hierarchies effectively2.

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.

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.

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.

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.

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

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.

The worksheet properties shown in the graphic indicate how to calculate the change in theAvailableDateofIndependentDemandbetween a child and its parent scenario. Configuration II shows the expression[:AvailableDate#0 - :AvailableDate#1 Workday], where#0refers to the child scenario and#1refers to the parent scenario. This expression calculates the difference in workdays between theAvailableDateof the independent demand in the child scenario and the parent scenario.

The worksheet should be set to calculate using the final results from other columns, ensuring that it takes into consideration the latest available data from the child and parent scenarios for accurate calculation of the workday difference.

References:

• Kinaxis RapidResponse documentation on worksheet expressions and scenario comparison.
• Kinaxis training materials on configuring worksheets for scenario analysis.

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.

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.