KX3-003 Exam Dumps : Certified RapidResponse Author Level 3 Exam

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.

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.

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.