You are asked to transform PlannedOrder data into new ScheduledReceipt records, assuming just one PartSource per part and no maximum quantity. You need to filter the PlannedOrder records to ensure you do not try to create any ScheduledReceipt records which already exist. The workbook includes a worksheet, LKPScheduledReceipt, on existing converted ScheduledReceipts and follows Kinaxis best practices.
In this situation, which filter expression will follow KInaixs best practices and provide the best performance to include PlannedOrder records that do not match existing ScheduledReceipt records?

• A. NOT {Part.Name, Part.Site.Value, DueDate} IN LKPScheduledReceipt!
• B. NOT {Part, DueDate} IN LKPScheduledReceipt!
• C. NOT IsNull ( Lookup ({Part.Name, Part.Site.Value, DueDate}, LKPScheduledReceipt!, Null(Mfg::ScheduledReceipt), Exact, LKPScheduledReceipt!Self ))
• D. ( Lookup({Part.Name,Part.Site.Value, DueDate}, LKPScheduledReceipt!, "N", LKPScheduledReceipt!Exists) = "N" )

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 DemandOrder table.
• B. Create a new Salesperson table referenced by the Customer table.
• C. Add a Salesperson string field on the DemandOrder table.
• D. Create a new Salesperson table referenced by the IndependentDemand table.

You have a worksheet based on the IndependentDemand table that includes columns for key fields plus multi-scenario columns for Quantity and EffectiveDemand. You want to highlight the Quantity fields where the value in the comparison scenario is different from the corresponding value in the workbook's baseline scenario. You want your worksheet to be able to highlight differences in several scenarios.
How would you achieve this highlighting?

• A. Define the Quantity column to show Actual value; add a hidden multi-scenario column, QuantityDelta, to show Difference; then define conditional formatting for the Quantity column when their QuantityDelta field is not 0.
• B. Add a hidden multi-scenario column, RecordID, as show Differences; then define conditional formatting for the Quantity column where RecordID is not equal to 0.
• C. Define the Quantity column to show Actual value, and define an additional hidden column, Quantity0, as !Quantity#0 using "Calculate using grouped results in the previous row or other results"; then define conditional formatting where the Quantity column is not equal to Quantity0.
• D. Define the Quantity column to show Difference, select the scenario comparison filtering option to show Only records with different comparison values, then define conditional formatting for the Quantity column when the respective value is not equal to 0.

You remove an automation chain step that runs in parallel with two other steps.
What is the result of this action?

• A. The other steps will continue to run in parallel.
• B. A notification is sent to the owner for action.
• C. The automation chain will no longer run.
• D. The other steps are switched to run in series.

You want to track the date of the most recent order placed by each Customer. You also want to make the most efficient use of memory, and query and algorithm performance.
Considering Kinaxis best practices, which data model design would you use?

• A. Add an input field, MostRecentOrderDate, to the PartCustomer table.
• B. Add an input field, MostRecentOrderDate, to the Customer table.
• C. Add an input field, DateOrdered, to IndependentDemand and use a set operation from Customer to Order to IndependentDemand to find the maximum DateOrdered.
• D. Add an input table with a single key reference to Customer, containing a MostRecentOrderDate.