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

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.

To optimize performance when creating a worksheet that contains fields from four tables, the worksheet should be based on:

• Table 1

Table 1 is connected to Table 3 with a one-way arrow, indicating a one-to-many relationship where Table 1 is the primary table. This setup typically allows for more efficient data retrieval and better performance.

• References

The decision is supported by the diagram showing the relationships between the tables, where “Arrow Head = 1” and “Arrow Base = Many” indicates the direction of the relationship and the primary table.

To optimize performance, the worksheet should be based on the top-level table from which you can access related data via references. This is because starting from the top level allows you to utilize indexed lookups, which are faster than traversing from many-to-one relationships. Given the data model design, Table 1 is the topmost table with one-to-many relationships to Table 3, which in turn links to Table 4, and it can also indirectly access data from Table 2 through the many-to-one relationship back to Table 1.

References:

• Kinaxis RapidResponse documentation on worksheet creation and data model traversal.
• Kinaxis guidelines on optimizing worksheets for better performance.