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

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.

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 prevent duplication of TimePhasedSafety records in cross-scenario updates:

Statement A:Including all key and reference fields in the update is a best practice. This ensures that the database can accurately match records across scenarios, reducing the risk of duplications.

Statement C:Listing identifying fields ahead of other columns in the update process helps in prioritizing these fields during the matching process, enhancing the accuracy of record linkage and minimizing duplication errors.

References

Kinaxis RapidResponse documentation and best practices on Automation Chains and Scheduled Tasks.

References:The search did not yield specific documentation on best practices for cross-scenario updates in Kinaxis RapidResponse. However, these answers are aligned with general best practices for database management and updates to prevent duplication and ensure data integrity.

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.

The migration of the Supplier.Id filter to the secondary filter expression box allows for enabling caching because it is a user-specific filter. Moving user-specific or session-specific expressions to the secondary filter ensures that the primary filter canbe cached independently of user sessions. This way, the overall data set can be cached, and the user-specific filtering is applied afterward, improving performance.

References:

Kinaxis RapidResponse documentation on primary and secondary worksheet filters.

Kinaxis support resources on caching strategies and performance improvements for worksheets.

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

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.

B. By adding a column to map the bucket dates in the spreading worksheet, you ensure that the start and end dates of the spreading are properly defined and can be utilized in the algorithm.

D. Selecting "Use same spreading worksheet values for all edits" ensures that the values entered in the buckets are consistent across the worksheet, which is necessary for the spreading functionality to work correctly.

A is incorrect because removing unmapped columns does not solve the issue related to spreading values across the buckets. C is incorrect because allowing editing only if all buckets are the same size is a constraint that does not address the mapping issue.

References:

Kinaxis RapidResponse support articles on troubleshooting and configuring spreading worksheets.

Kinaxis community discussions on common issues and solutions related to worksheet design.

To resolve the issue with the workbook designed for spreading values, it is necessary to ensure that the bucket dates are properly mapped in the spreading worksheet. This allows the system to recognize and apply the correct time horizon for the spread. Additionally, selecting the option to use the same spreading worksheet values for all edits ensures consistency across the worksheet.

References:

Kinaxis RapidResponse Author Level 3 certification materials1.

Enhanced troubleshooting skills and best practices as mentioned in the Kinaxis Certification Program2.

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.