You are asked to restrict a worksheet so that users can only see data for the demand of the countries that they should have permission to see. A field has been added to the IndependentDemand table, which is a reference to a custom table called Country. Each user may have permission to see the demands from one or more countries, and each country can be seen by one or more users. They should be able to see data from multiple countries in the worksheet at the same time.
In this scenario, what should you do to enable this capability?
- A . Create a $DmdCountry list workbook variable with a query generated list of values based on the Country table. Add the expression UserInGroup ($User, ‘DemandPlanners’) to the variable filter and then in the column properties conditionally hide the column using the $DmdCountry = False expression.
- B . Create a $DmdCountry text workbook variable with the expression UserInGroup ($User, ‘DemandPlanners’). Add the $DmdPlanners = TRUE expression to the worksheet.
- C . Build a Responsibility definition based on the Country table and assign the users to all of the countries that they should have permission to see. Add a responsibility column to the worksheet so users can select their country.
- D . Create a $DmdCountry profile variable and assign the country names to each user. Add the expression IF ($DmdCountry = "’*’", TRUE, User::DmdCountry IN eval($DmdCountry)) to the worksheet filter.
D
Explanation:
This setup allows for flexible data visibility based on user permissions. By creating a profile variable that contains the allowed countries for each user, you can then apply a filter expression to the worksheet that evaluates this variable. If a user is permitted to see all countries (indicated by an asterisk ‘*’), the expression returns TRUE, otherwise, it checks if the demand’s country is in the user’s permitted list.
References:
Kinaxis RapidResponse documentation on configuring data visibility through profile variables and worksheet filters.
Kinaxis training materials on setting up user permissions and responsibility definitions.
Which two violations of Kinaxis best practice are shown in the graphic? (Choose two.)
- A . The key field contains the table name.
- B . The Line should be a number field.
- C . The deployment name prefix is included in the OrderId field.
- D . OnTimeQty should specify the data type in the field name.
A C
Explanation:
The two violations shown in the graphic are:
You need to create a workbook to allow users to manage their demand forecast by product, customer region, and distribution site. You also want to simplify user controls and use hierarchies to allow each user to make several selections in the same hierarchy.
In this situation, which two actions should you take? (Choose two.)
- A . Select Part as the basis for workbook filtering.
- B . Disable the default Site filter.
- C . Enable the Include hierarchy columns option.
- D . Ensure a Hierarchy is available for users to select regional distribution sites.
C D
Explanation:
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.
You have a new demand for 800 units of a product. SourceRule.AllotmentRule for this part is set to OnGoing.
Referring to the graphic, which planned order results will be created to satisfy this demand?
- A . Supplier1: quantity 250
Supplier2: quantity 750 - B . Supplier1: quantity 750
Supplier2: quantity 250 - C . Supplier1: quantity 1000
- D . Supplier2: quantity 1000
A
Explanation:
Referring to the graphic, it appears that there is a target allocation ratio between Supplier 1 and Supplier 2 (not visible in the image, but this can be inferred from the allocation quantities). When a new demand for 800 units is introduced, the SourceRule.AllotmentRule set to OnGoing will distribute the demand based on the ongoing target ratio. Since Supplier 1 has a running total that far exceeds Supplier 2, and both have a ‘Multiple Qty’ of 250, the next allotment will attempt to balance the ongoing total closer to the target ratio. It’s likely that the new demand will be allocated by filling up to the nearest multiple of 250 that does not exceed the demand. Therefore, Supplier 1 gets 250, and the remaining 550 units would go to Supplier 2. Since Supplier 2 also must supply in multiples of 250, it rounds up to 750 units.
ReferencesThis understanding is derived from the Kinaxis RapidResponse concepts for managing supply allocations and the behavior of ongoing rules as described in the Kinaxis RapidResponse documentation.
References:
The Kinaxis RapidResponse documentation on SourceRule.AllotmentRule indicates that ongoing allotment is based on the target ratios set for suppliers1.
The Certified RapidResponse Author Level 3 materials cover the configuration and implications of SourceRule.AllotmentRule settings2.
You are creating a resource that is designed to evaluate the impact of converting planned orders to scheduled receipts. After the evaluation is complete, you want to provide users the opportunity to push their changes to the parent scenario. Users will be using their scenarios to consider changes to lead time, constraint available, and other planning parameters. The company policy stipulates that lead times cannot be adjusted in any shared scenarios.
What should you do to accomplish this task?
- A . Restrict the user to view only access to the parent scenario.
- B . Develop a cross scenario data change.
- C . Apply a perspective when creating your scenario.
- D . Export your changes to a .tab file and import to a scenario.
B
Explanation:
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.
You need to create an expression that displays the number of the calendar week from the beginning of the year, for example, 01 January 2017 to 07 January 2017 = week 1. The calendar is based on a January to December fiscal year. The Calendar table has the values shown in the graphic.
Which expression would display the number of the calendar week?
- A . (today – (today + 0 Year) Week)
- B . (today – (today + 0 Year) Week) +1
- C . (today + 0 Week)
- D . (today + 0 Week) + 1
B
Explanation:
The expression to display the number of the calendar week from the beginning of the year takes today’s date, resets it to the start of the year (the 0 Year part), and then calculates the week number from this start date, adding 1 since week numbers generally start at 1, not 0.
ReferencesThe logic for calculating week numbers from a given date is commonly described in Kinaxis RapidResponse documentation and training materials concerning date and time functions.
You want to compare the performance of two similar worksheets in a private scenario, but you need to ensure that neither worksheet takes advantage of cached results.
In this situation, before capturing the performance results, how would you accomplish this task?
- A . Close the workbook and reopen it.
- B . Close the workbook and also close any library workbooks it uses, then reopen the workbook.
- C . Edit the Description field for OnHandType.
- D . Edit the Description field for the selected parts.
B
Explanation:
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.
You have a worksheet showing work orders. You are asked to report the date used to convert the calculated field EffectiveUnitPrice.
Which expression will accomplish this task?
- A . DATEVALUE(EffectiveUnitPrice)
- B . CONVERTONDATE(EffectiveUnitPrice, $ConversionDate)
- C . DATETIMEVALUE(EffectiveUnitPrice)
- D . ASSOCIATEDDATE(EffectiveUnitPrice)
B
Explanation:
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.
You want to enable data caching on the worksheet shown in the graphic.
Which two actions will accomplish this task? (Choose two.)
- A . Remove the bucketing by DueDate.
- B . Remove the hierarchy column.
- C . Remove the currency column.
- D . Disable the Use As Reference checkbox on the Part column.
B D
Explanation:
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.
You are developing a worksheet that will be used to run a script through a form. For the script to work properly, you will need to pass information from two columns as script arguments.
Which two actions will accomplish this task? (Choose two.)
- A . Select the columns when mapping drill links to forms.
- B . Map the Form controls to Script arguments.
- C . Select the columns when setting an Open Form Command.
- D . Match the script arguments names with the Form controls ID.
B D
Explanation:
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 client wants to provide their sales staff the ability to add forecasts for the global total of demand across all SKUs by each customer by month. The client wants to use their historical demand to allocate from a monthly forecast to a weekly forecast.
Which three actions would accomplish this task? (Choose three.)
- A . Create a worksheet based on the HistoricalDemandActual table.
- B . Create workbook variables for Start Date and End Date.
- C . Create a workbook variable for Calendar with a value of Month.
- D . Define a custom Insert Definition.
- E . Include only columns for Part, Site, and Customer from the HistoricalDemandActual table.
B C D
Explanation:
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.
You want to control how available dates are calculated for your vendor managed parts’ supplies and demands.
In this situation, which control table would you need to configure?
- A . AvailableRule
- B . DemandType
- C . OrderPolicy
- D . SupplyType
A
Explanation:
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.
You are asked to create a workbook that identifies the change in IndependentDemandAvailableDate in workdays from a child scenario to its parent.
Which worksheet properties shown in the graphic identifies the correct configuration and expression?
- A . I
- B . II
- C . III
- D . IV
B
Explanation:
The worksheet properties shown in the graphic indicate how to calculate the change in theAvailableDateof IndependentDemandbetween 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.
You have defined a new namespace, TRM. You now want to define a new table that has a key reference field to the Mfg::ABCCode table. However, in the Add Input Field dialog,ABCCode does not appear.
What should you do to create the ABCCode key reference?
- A . Add the TRM namespace as a dependency for the Mfg namespace.
- B . Enable the Allow null reference checkbox.
- C . Enable the Allow automatic record creation checkbox.
- D . Add the Mfg namespace as a dependency for the TRM namespace.
D
Explanation:
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 graphic shows a path to generate a list of customer prices with record counts for each table in the path.
Given the following filter expression:
Part.ProductNumber.ProductGroup.ProductFamily In (‘bikes’,’trikes’)
AND Customer.Country IN ("US", "CA")
In this situation, what is the chosen line of descent from the query engine?
- A . Country > Country_Customers > CustomerPrices
- B . ProductFamily > ProductFamily_ProductGroups > ProductGroup_ProductNumbers > ProductNumber_Parts > CustomerPartPrices
- C . CustomerPartPrices > ProductNumber_Parts > ProductGroup_ProductNumbers > ProductFamily_ProductGroups > ProductFamily
- D . CustomerPrices > Country_Customers > Country
B
Explanation:
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.
You have a crosstab, bucketed worksheet that shows forecast records. There are forecast records on the first workday of every month for 18 months from the Planning Date. The bucket settings are set for 52 Weeks from the Planning Date. You want to improve performance for this worksheet, but still display it as a crosstab worksheet. You also want to display one year’s worth of forecast records.
How would you accomplish this task?
- A . Change the bucket settings to display 365 Everyday from the Planning Date.
- B . Turn off the bucket settings for this worksheet and add an expression to filter out records that are beyond the one year horizon.
- C . Turn off grouping settings for this worksheet and add an expression to filter out records that are beyond the one year horizon.
- D . Change the bucket settings to display 18 Months from the Planning Date and add an expression to filter out records that are beyond the one year horizon.
B
Explanation:
Turning off bucket settings can improve performance by reducing the computational load required to generate the buckets. Adding an expression to filter out records that are beyond the one-year horizon ensures that only data relevant to the desired timeframe (one year’s worth of forecast records) is displayed. This streamlines the data set, potentially improving load times and making the worksheet more responsive.
ReferencesKinaxis RapidResponse documentation recommends streamlining worksheet data and using filters to improve performance, especially when dealing with large data sets or long time horizons.
References: The answer is based on general best practices for performance improvement in data systems, which suggest limiting data to the necessary scope.Specific Kinaxis RapidResponse documentation cannot be accessed or verified by me, so please refer to the official Kinaxis training materials for RapidResponse Author Level 3 for detailed guidance12.
You are asked to create a worksheet that shows which process orchestration activity performers are late and how much they are late for each activity. There could be more than one performer per activity.
How would you accomplish this task?
- A . Create a worksheet based on the Assignment table in the ProcOrch namespace.
- B . Create a worksheet based on the Activity table in the ProcOrch namespace.
- C . Create a worksheet based on the ProcessInstance table in the Mfg namespace.
- D . Create a worksheet on the Activity table in the Mfg namespace.
A
Explanation:
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.
You have a worksheet based on the Part table. You want to know the total number of unique customers that have orders for each part.
Which expression accomplishes this task?
- A . COUNT IndependentDemands {Order.Customer:Sum}
- B . COUNT IndependentDemands {Order.Customer:By}
- C . COUNT IndependentDemands {Order.Customer<>”}
- D . SUM IndependentDemands{Order.Customer:Sum}
B
Explanation:
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.
You want to create a composite worksheet using two component worksheets. The group by columns in both worksheets are Part.Name, Part.Site, Order.ID, Order.Site, Order.Type, Order.Type.ControlSet, and Line.
How would you improve performance of the composite worksheet?
- A . Group the component worksheets by Part.Name, Part.Site and Order.ID. In the composite worksheet group by Order.Type, Order.Type.ControlSet and Line.
- B . Ensure that the sort order and sort direction used in both worksheets are the same.
- C . Instead of using Part.Name and Part.Site, use Part as a reference in both worksheets.
- D . Instead of using Order.ID, Order.Site, Order.Type, and Line replace them with a column that concatenates those values and use it as a group by column.
B
Explanation:
Matching the sort order and direction in both component worksheets before creating a composite worksheet can improve performance. This alignment ensures that the composite worksheet does not have to re-sort the data from each component worksheet, which can be computationally expensive, especially for large datasets.
ReferencesThe recommendation to match sort orders and directions for performance optimization in composite worksheets is in line with best practices for data management in Kinaxis RapidResponse, which can be found in the training and documentation materials.
You need to create a new custom field to be used for record filtering that will be populated with the salesperson’s name. Each order will have a single associated salesperson’s name.
Following database design principles and Kinaxis best practices, which action accomplishes this task?
- A . Create a new Salesperson table referenced by the Customer table.
- B . Add a Salesperson string field on the DemandOrder table.
- C . Create a new Salesperson table referenced by the IndependentDemand table.
- D . Create a new Salesperson table referenced by the DemandOrder table.
B
Explanation:
If each order is associated with a single salesperson and the goal is to filter records by the salesperson’s name, the most straightforward solution is to add a field directly to the DemandOrder table where orders are recorded. This avoids unnecessary joins to another table and simplifies the data model. According to database normalization principles, if the field is non-repetitive and directly related to the entity (in this case, the order), it should be placed on the same table.
ReferencesThe addition of a single attribute that is not multi-valued, non-repeating, and directly related to the primary key in the table aligns with the first normal form (1NF) in database normalization. This approach is also supported by Kinaxis best practices for efficient data retrieval.