練習できるKX3-003問題には認定ガイド問題と解答とトレーニングを提供しています [Q22-Q44]

練習できるKX3-003問題には認定ガイド問題と解答とトレーニングを提供しています

無料Kinaxis KX3-003テスト練習問題試験問題集

質問 # 22
At a customer site, there are multiple TimePhasedSafety records that are duplicated in the Baseline scenario.
This is caused by the cross-scenario update from a child scenario.
What are two Kinaxis best practices for cross-scenario updates to prevent this situation? (Choose two.) Choose 2 answers

• A. List the identifying fields ahead of the other columns.
• B. Delete all records in Baseline before the update to allow the database to re-link records that have a corrupted version chain.
• C. Include all key fields and all reference fields in the update to help the database clearly identify matching records.
• D. Identify fields that should be used to match records by making them read-only.

正解：A、C

解説：
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.

質問 # 23
You are required to troubleshoot a workbook designed to spread values across a specified time horizon. The start and end bucket dates are mapped to variables used in the spreading worksheet. The bucket field is not mapped to a column in the editing worksheet.
Which two actions would solve this issue? (Choose two.)
Choose 2 answers

• A. Add a column to the spreading worksheet to map the bucket dates.
• B. Select the "Use same spreading worksheet values for all edits" check box.
• C. Remove the unmapped columns from the editing worksheet.
• D. Select the "Allow editing only if all buckets are the same size" check box.

正解：A、B

解説：
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.

質問 # 24

You are asked to create a worksheet that contains fields from four tables.
Referring to the graphic, which table should your worksheet be based on to optimize performance?

• A. Table 4
• B. Table 1
• C. Table 3
• D. Table 2

正解：B

解説：
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.

質問 # 25
var dataArray = [[line, orderNo, site, orderType, partName, site, dueDate, quantity]]; var dataSettings = {scenarios: [scenario], filter: fAllParts, siteGroup: sgSite} var wbOrderChng = rapidResponse.workbooks.get({name:'Change Orders', scope:'Private'}, dataSettings); var cmdDeleteData= wbOrderChng.commands.get('DeleteData'); var wsOrderChng = wbOrderChng.worksheets.get('ChangeOrders') Which two lines of code would potentially delete records in a table if they appeared after the code shown in the exhibit? (Choose two.) Choose 2 answers

• A. var importResult = wsOrderChng.importData(dataArray);
• B. var removeResult = wsOrderChng.remove(dataArray);
• C. var executeResult = cmdDeleteData.execute();
• D. var removeResult = wbOrderChng.remove(wsOrderChng.getData());

正解：B、C

解説：
Line A withcmdDeleteData.execute();would execute a command to delete data in RapidResponse, which, if configured correctly, would delete records. Line C withwsOrderChng.remove(dataArray);is a method that would also potentially delete records from the worksheet if the dataArray contains the correct keys for the records that need to be removed.
ReferencesThe Kinaxis RapidResponse scripting and workbook API documentation explain the methods execute()for running commands andremove()for removing data from worksheets. Both can be used to delete records when executed with the proper context and data.

質問 # 26

The graphic shows the Carrier table view in the data model dialog.
Which three statements about this table are true? (Choose three.)
Choose 3 answers

• A. Each carrier can have multiple Transit Calendars.
• B. Several carriers can share the same Default Transportation Mode.
• C. A carrier must only have one Source.
• D. Multiple Shipments can reference a carrier.
• E. Multiple Delivery Routes can reference a carrier.

正解：B、D、E

解説：
A: The DeliveryRoutes being a Set data type indicates that there can be multiple Delivery Routes referencing a carrier, allowing for one-to-many relationships between a carrier and delivery routes.
C: The Shipments being a Set data type as well indicates that multiple shipments can reference a single carrier, also suggesting a one-to-many relationship.
D: The DefaultTransportationMode being a Reference data type allows for the possibility that several carriers can share the same transportation mode, as references do not enforce uniqueness.
B is not correct because the TransitCalendar being a Reference data type indicates a one-to-one relationship; each carrier can reference only one Transit Calendar. E is also incorrect because the Sources field being a Set data type implies that a carrier can be associated with multiple sources.
References:
* Kinaxis RapidResponse documentation on data modeling and table relationships.
* Kinaxis learning resources on understanding data types and their implications on table relationships.

質問 # 27
You are building a worksheet for supplier collaboration and you want to assign a profile variable, Suppliers, so each user can see data for their own list of suppliers.
You include an expression in your sheet reporting the ScheduledReceipt table:
Order.Supplier IN ListAsSet($Suppliers)
Which string would you enter for the Suppliers profile variable for a user that should see data for suppliers A, B and C?

• A. A\, B\, C
• B. A, B, C
• C. 'A', 'B', 'C'
• D. 'A, B, C'

正解：C

解説：
The ListAsSet function in Kinaxis RapidResponse expects a set of elements as input, typically in the format of a string with elements enclosed in single quotes and separated by commas. For a user that should see data for suppliers A, B, and C, you need to format the string to match this expected input format.
References:
* Kinaxis RapidResponse documentation on the ListAsSet function and profile variables.
* Kinaxis community discussions or support articles on configuring profile variables for user-specific views.
References: The information is based on the Kinaxis RapidResponse documentation and learning resources, which provide guidelines on how to properly format expressions and variables for worksheets.

質問 # 28

Forecasts are being received on a monthly basis and you are asked to spread these forecasts into weekly intervals. The month has four weeks, and you are using the spreading profile shown in the graphic where the first week is on the left. The monthly forecast is for a quantity of 500. The PlanningCalendars.ForecastCalendar=Month and PlanningCalendars.SecondCalendar=Week.
Referring to the graphic, what will the weekly forecast quantities be?

• A. 100, 100, 135, 165
• B. 100, 100, 140, 160
• C. 100, 100, 125, 175
• D. 125, 125, 125, 125

正解：C

解説：
When forecasts are spread into smaller time intervals using a spreading profile, the quantities are distributed according to the specified proportions in the profile. The graphic indicates that the profile points are 20, 20,
25, and 35 for each of the four weeks, respectively. To spread the monthly forecast of 500 units into weekly intervals, you multiply each proportion by the monthly forecast and divide by the sum of the profile points. So, (20/100) * 500 for the first two weeks, (25/100) * 500 for the third week, and (35/100) * 500 for the fourth week, which results in the weekly forecasts of 100, 100, 125, and 175, respectively.
ReferencesThe calculation uses basic arithmetic based on the principles of proportionally spreading a total quantity across a defined profile, as described in the Kinaxis RapidResponse demand planning documentation.

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

正解：D

解説：
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.

質問 # 30
You are asked to report data based on the ScheduledReceipt table that also displays information from a custom table, WorkOrderInfo. There will be at most one WorkOrderInfo record for any ScheduledReceipt record and WorkOrderInfo will be used often in worksheets reporting ScheduledReceipt data.
Following Kinaxis best practices, what should you do to accomplish this task?

• A. 1. Create a reference field on the ScheduledReceipt table to the WorkOrderInfo table.
  2. Display relevant work order data in worksheets based on the ScheduledReceipt table and the referenced WorkOrderInfo table.
• B. 1. Create two worksheets: one based on ScheduledReceipts and one based on WorkOrderInfo.
  2. Create a column in the ScheduledReceipts worksheet to lookup values in the WorkOrderInfo worksheet.
• C. 1. Create a reference field on the WorkOrderInfo table to the ScheduledReceipt table.
  2. Display relevant work order data in worksheets based on the WorkOrderInfo table and the referenced ScheduledReceipt table.
• D. 1. Create a composite worksheet using two component worksheets, ScheduledReceipt and WorkOrderInfo.
  2. Use left join and grouping to align the two sets of data.

正解：A

解説：
* 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.

質問 # 31

A part has several demands due in a particular week. All demands are the same priority. Available supplies are shown in the graphic. The control table settings for the OrderPriority.AllocationRule is FairShare and PlanningCalendars.AllocationCalendar is Week.
How much of the supply quantity on Thursday will be allocated to the Wednesday demand?

• A. 0
• B. 1
• C. 2
• D. 3

正解：C

解説：
Given that the control table setting for OrderPriority.AllocationRule is FairShare and all demands are the same priority, the available supply quantity will be allocated evenly among the demands. The graphic shows there are demands due on Monday, Tuesday, and Wednesday with planned orders due on each day as well. If the total supply on Thursday is not specified in the question, we assume it is enough to meet or exceed the demand. Since all demands have the same priority and the allocation rule is FairShare, the entire supply quantity for Thursday will be evenly distributed. Without the exact supply quantity, the best assumption is that the full quantity needed for the demand due on Wednesday will be allocated.
ReferencesThis explanation is based on the FairShare allocation rule which distributes available supply evenly across all demands when they have the same priority, as per the Kinaxis RapidResponse documentation on supply allocation.

質問 # 32
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:By}
• B. COUNT IndependentDemands {Order.Customer<>''}
• C. COUNT IndependentDemands {Order.Customer:Sum}
• D. SUM IndependentDemands{Order.Customer:Sum}

正解：A

解説：
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.

質問 # 33

You are creating a new script that must insert a new customer record, archive that record weekly in a new scenario, and then commit the child scenario to a parent scenario. You already have a script that commits child scenarios.
Referring to the graphic, which code will call the script that commits child scenarios in your new script?

• A. III
• B. II
• C. IV
• D. I

正解：C

解説：
The code block IV is correctly using the script execution pattern in RapidResponse. It first gets the script using rapidResponse.scripts.get()method with the correct parameters for the name and scope, and then calls the script with.call()method, passing the necessary scenario argument. This is how you would invoke another script from within a script.
ReferencesThe use ofrapidResponse.scripts.get()andcall()methods is standard practice in Kinaxis RapidResponse for executing one script from within another, as detailed in the Kinaxis RapidResponse scripting documentation.

質問 # 34

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 750
  Supplier2: quantity 250
• B. Supplier1: quantity 250
  Supplier2: quantity 750
• C. Supplier1: quantity 1000
• D. Supplier2: quantity 1000

正解：B

解説：
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.

質問 # 35
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. 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.
• B. 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.
• C. 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.
• D. 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.

正解：B

解説：
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.

質問 # 36
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. 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.
• B. 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.
• C. 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.
• D. 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.

正解：B

解説：
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.

質問 # 37
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. ( Lookup({Part.Name,Part.Site.Value, DueDate}, LKPScheduledReceipt!, "N", LKPScheduledReceipt!Exists) = "N" )
• B. NOT IsNull ( Lookup ({Part.Name, Part.Site.Value, DueDate}, LKPScheduledReceipt!, Null(Mfg::ScheduledReceipt), Exact, LKPScheduledReceipt!Self ))
• C. NOT {Part.Name, Part.Site.Value, DueDate} IN LKPScheduledReceipt!
• D. NOT {Part, DueDate} IN LKPScheduledReceipt!

正解：D

解説：
Using the NOT IN operator with the key fields from the PlannedOrder table in the LKPScheduledReceipt worksheet is the most direct and efficient way to excluderecords that already exist. This filter checks if the combination of Part and DueDate from PlannedOrder records does not exist in the LKPScheduledReceipt worksheet, ensuring that only new ScheduledReceipt records will be created.
ReferencesThe best practices for filter expressions in Kinaxis RapidResponse workbooks, as described in the documentation, recommend using simple and direct expressions that efficiently exclude existing records to improve performance.

質問 # 38

Given the following order policies:
* MultipleQty: 10
* MinimumQty: 15
* MultipleUsage: Use
* MinimumUsage: Use
Referring to the graphic, what are the sizes of the three planned orders A, B, and C?

• A. A = 30, B = 15, C = 15
• B. A = 25, B = 15, C = 15
• C. A = 30, B = 15, C = 10
• D. A = 30, B = 20, C = 20

正解：D

解説：
Given the order policies of MultipleQty: 10, MinimumQty: 15, MultipleUsage: Use, and MinimumUsage:
Use, the sizes of the planned orders are determined by rounding up to meet the minimum quantity and then to the nearest multiple of the MultipleQty. Order A needs to meet the demand of 25, so it must at least meet the MinimumQty of 15 and then round up to the nearest multiple of 10, which is 30. Order B, with a demand of
12, will also round up to the minimum quantity of 15 and then to the nearest multiple of 10, which is 20, since the MultipleUsage is "Use." The same logic applies to order C, with an initial demand of 20, it is already at a multiple of 10, so it remains 20.
ReferencesThis answer applies the principles of order quantity rounding based on multiples and minimums as commonly used in supply chain planning and as described in Kinaxis RapidResponse's order policy settings.
References:
* The Kinaxis RapidResponse documentation and training materials provide guidelines on how to apply order policies to determine the sizes of planned orders123.

質問 # 39

Which two violations of Kinaxis best practice are shown in the graphic? (Choose two.) Choose 2 answers

• A. The deployment name prefix is included in the OrderId field.
• B. The key field contains the table name.
• C. OnTimeQty should specify the data type in the field name.
• D. The Line should be a number field.

正解：A、B

解説：
The two violations shown in the graphic are:
A: The key field contains the table name: Best practices suggest that the name of a key field should not repeat the table name. It should be succinct and only include the necessary distinguishing characteristic to remain clear and avoid redundancy.
C: The deployment name prefix is included in the OrderId field: Including a deployment name prefix in the field name can create issues when moving between environments, as the deployment name typically changes between development,testing, and production. It's better to use generic field names that are not environment-specific.
ReferencesThis is based on Kinaxis best practices for data model design, which recommend avoiding redundancy in field naming and ensuring that field names are environment-agnostic to facilitate easier migration and understanding of the data model across different stages of the deployment process.

質問 # 40

You want to enter a forecast for 6000 units of part 89-Prod0966 in the June 8 bucket. You expect that three records will be inserted into the IndependentDemand table (equal quantities of 2000 at each of the three sites); however, you get an error.
Which action would solve the error?

• A. Add a Date column to the spreading worksheet.
• B. Change the table that the spreading worksheet is based on, from Part to IndependentDemand.
• C. Map the column id Name to Part.Name in the Forecast worksheet.
• D. Map the column id Site to Part.Site in the Forecast worksheet.

正解：D

解説：
To ensure that a forecast entry is spread correctly across multiple sites, the Site column in the spreading worksheet must be mapped to the Part.Site field. This way, the system knows how to allocate the entered forecast quantity among the different sites associated with the part.
A is incorrect because changing the base table from Part to IndependentDemand would not directly address the issue of distributing the forecast across sites. B is not relevant to the error because mapping the Name to Part.Name does not affect the distribution of forecast quantities across sites. D is not correct because adding a Date column to the spreading worksheet is not related to solving the error associated with distributing forecast quantities across sites.
References:
* Kinaxis RapidResponse documentation on forecast entry and spreading across sites.
* Kinaxis support articles on troubleshooting forecast entry errors and worksheet configurations.

質問 # 41
You are creating an insert definition to insert records using a crosstab worksheet, which contains weekly buckets that begin on Monday. You want the inserted records to be due on Friday of that week but if Friday is a non-workday, you want the inserted record to be due on Thursday.
In this situation, how would you set the bucket date in the insert definition?

• A. Use the MRPDate.
• B. Use the first date in the bucket.
• C. Use the last workday in the bucket.
• D. Use the first date in the bucket adjusted by three workdays.

正解：C

解説：
When setting the bucket date in an insert definition, if the requirement is to have the record due on the last workday of the week (which is Friday or Thursday if Friday is a non-workday), then the correct approach is to configure the insert definition to use the last workday in the bucket. This will ensure that the due date falls on the correct day according to the specified requirement.
ReferencesThe Kinaxis RapidResponse documentation details how to use bucket dates and adjust them according to workdays in the insert definition setup for crosstab worksheets.

質問 # 42

You want to enter a forecast for 6000 units of part 89-Prod0966 in the June 8 bucket. You expect that three records will be inserted into the IndependentDemand table (equal quantities of 2000 at each of the three sites); however, you get an error.
Which action would solve the error?

• A. Add a Date column to the spreading worksheet.
• B. Change the table that the spreading worksheet is based on, from Part to IndependentDemand.
• C. Map the column id Name to Part.Name in the Forecast worksheet.
• D. Map the column id Site to Part.Site in the Forecast worksheet.

正解：D

解説：
To ensure that a forecast entry is spread correctly across multiple sites, the Site column in the spreading worksheet must be mapped to the Part.Site field. This way, the system knows how to allocate the entered forecast quantity among the different sites associated with the part.
A is incorrect because changing the base table from Part to IndependentDemand would not directly address the issue of distributing the forecast across sites. B is not relevant to the error because mapping the Name to Part.Name does not affect the distribution of forecast quantities across sites. D is not correct because adding a Date column to the spreading worksheet is not related to solving the error associated with distributing forecast quantities across sites.
References:
* Kinaxis RapidResponse documentation on forecast entry and spreading across sites.
* Kinaxis support articles on troubleshooting forecast entry errors and worksheet configurations.

質問 # 43
Your suppliers need to receive a report listing their outstanding purchase orders. Each supplier should receive the report in the same format but it should only display the purchase orders associated with their supplier ID.
Based on this situation, which two actions will be required to support this requirement? (Choose two.) Choose 2 answers

• A. Add the supplier's user group in the Notify tab of the Alert properties window.
• B. Assign a master Supplier group in the Advanced properties of the Alert properties window.
• C. Define a profile variable to assign the supplier ID to the supplier's user group. Add the profile variable to the filter expression in the workbook.
• D. Define a list workbook variable to provide a selector for the supplier list. Add the workbook variable to the filter expression in the workbook.

正解：A、C

解説：
To ensure that suppliers only receive reports relevant to their purchase orders, a profile variable tied to the supplier's user group is used to filter the report data. The Notify tab in the Alert properties window is used to configure the report distribution to the appropriate supplier's user group, ensuring that each supplier gets the tailored report.
References:
* Kinaxis RapidResponse documentation on creating user groups, profile variables, and configuring alerts for report distribution.
* Kinaxis training materials on workbook filter expressions and alert notification settings.

質問 # 44
......

試験準備には欠かさない！トップクラスのKinaxis KX3-003試験アプリ学習ガイドで練習問題最新版：https://jp.fast2test.com/KX3-003-premium-file.html