Oracle 1z0-1066-23 Oracle Planning and Collaboration Cloud 2023 Implementation Professional Exam Practice Test

If a plan is set up as private, there is no way to further limit what users see within the plan.

If a plan is set up as public, there is a way to further limit what users see within the plan.

Data access sets can be used to limit what a planner can see. based on Items, Organizations, Carriers, Suppliers, and Customers.

A plan can be set up to be public or private.

A global sourcing rule for 50% make at ABC and 50% buy from ABC

A local sourcing rule for 100% make at ABC; a global sourcing rule for 100% transfer from ABC

A local sourcing rule for 100% make at ABC; a global sourcing rule for 100% buy from ABC

A local sourcing rule for 100% buy from ABC; a global sourcing rule for 100% transfer from ABC

A global sourcing rule for 100% make at ABC; a local sourcing rule for 100% transfer from ABC

Manage Plans > Search and select supply plan > Supply tab > Organizations and Schedules tab > Remove all demand schedules

Manage Plans > Search and select demand plan > Demand tab > General tab > Select 'Do no spread forecast'

Manage Plans > Search and select demand plan > Demand tab > General tab > Check Demand Time Fence Control

Manage Plans > Search and select supply plan > Supply tab > General tab > Advanced Options > Check 'Create time fence'

Manage Plans > Search and select supply plan > Supply tab > General tab > Check Demand Time Fence Control

Manage Plans > Select each supply plan > Edit each supply plan > Manually add each exception specified by client

Configure Exceptions > Expand Supply Planning Exceptions > Highlight lines with exceptions specified by client > Click 'Add to Exception Set'

Configure Exception Sets > Create exception set > Add exceptions specified by client

Select 'Add to Supply Plan' button > Select which supply plans you want to have this group of exceptions

Manage Plans > Select each supply plan > Edit each supply plan > Add your exception set to Plan Options for each supply plan

Showing customer demand trend over a specific time period

Showing inventory values by product category

Showing a breakdown of exception in a pie chart

Showing on-hand value compared to targets

Showing inventory value across time

Upload the value using File Based Data Import (FBDI)

Enter your value in the Safety Stock Quantity column in the Items page.

Run the Safety Stock Quantity Update Process.

Enter your value in the Safety Stock Quantity Override column in the Items page.

For demand plan option, add forecast shipments as forecasting profile, enter history start date as 1/1/15, enter history end date as 12/31/15, and enter forecast start date as 1/1/17.

For demand plan option, add forecast shipments as forecasting profile, and enter historical buckets as 24.

For demand plan option, add forecast shipments as forecasting profile, enter history start date as 1/1/15, forecast start date as 1/1/17, and enter forecast end date as 12/31/17.

For demand plan option, add forecast shipments as forecasting profile, enter historical buckets as 24, and enter forecast buckets as 12.

For plan scope, select plan horizon days as 365, forecasting calendar as Gregorian, and forecasting time level as month.

For plan scope, select plan horizon as 12 months, forecasting calendar as Gregorian, and forecasting time level as month.

Manage Planning Profile Options

Manage Plans

Manage Sourcing Rules

Manage Assignment Sets

Manage Planning Source Systems

It cannot be done at this time.

Generate manually using Planning Analytics

Excel upload using File Based Data Import Process

Create based on the supplier performance for drop shipment collection

Create based on the drop shipment or booking history; the ship from will be the drop ship validation organization

For demand plan option, add forecast shipments as forecasting profile, and enter historical buckets as 24.

For demand plan option, add forecast shipments as forecasting profile, enter history start date as 1/1/21. forecast start date as 1/1/23. and enter forecast end date as 12/31/23.

For demand plan option, add forecast shipments as forecasting profile, enter history start date as 1/1/21. enter history end date as 12/31/22. and enter forecast start date as 1/1/23.

For demand plan option, add forecast shipments as forecasting profile, enter historical buckets as 24. and enter forecast buckets as 12.

For plan scope, select plan horizon as 12 months, forecasting calendar as Gregorian, and forecasting time level as month.

For plan scope, select plan horizon days as 365. forecasting calendar as Gregorian, and forecasting time level as month.

Set up Levels and Attributes

Set up Measure Catalogs

Run the Configure Dimension Catalog process

Set up Default Catalogs

Set up Dimension Catalogs

Set up Hierarchy Attributes

Planning process reduces the demand based on shrinkage factor and keeps the supply quantity as is.

Planning calculation does not support shrinkage functionality.

Planning calculates no additional demand but creates the additional required supply based on shrinkage factor.

Planning calculation creates scrap demand to compensate for loss and maintains supply.

Minimum Order Quantity

Fixed Lot Size Multiplier

Maximum Order Quantity

Fixed Order Quantity

Rounding

CSV file must be generated.

Collect Planning Data Process must be run from Planning.

Collect Legacy Data Process must be run from Planning.

Load Interface File for Import Process must be run.

Flat File must be zipped.

Work orders

On-hand inventory

Purchase requisitions

Purchase orders

Transfer orders

Planned Orders

The approve action takes the data from the two final forecast measures and copies to Approved Final Shipments Forecast and Approved Final Bookings Forecast, respectively. After a forecast is approved, the approved values remain unchanged until the forecast is approved again.

The approve action makes the Adjusted Shipments Forecast and Adjusted Bookings Forecast measures "not editable." After a forecast is approved, the Final Shipments Forecast and Final Bookings Forecast measures remain unchanged until the forecast is approved again.

The approve action makes the Adjusted Shipments Forecast and Adjusted Bookings Forecast measures "not editable." But any subsequent demand plan run can change Final Shipments Forecast and Final Bookings Forecast values.

The approve action takes the data from the two final forecast measures and copies to Approved Final Shipments Forecast and Approved Final Bookings Forecast, respectively. Any subsequent demand plan run can change final shipments or bookings forecast values that will automatically update the approved forecast measures.

Based on the order value per customer weighted by the number of associated recommendations required to make the demand no longer at risk

Based on order value weighted by the number of compression days required to make the demand no longer at risk

Based on order value weighted by the number of associated recommendations required to make the demand no longer at risk

Based on the number of associated recommendations required to make the demand no longer at risk

Users with the Supply Chain Operations Manager role can access the Supply Chain Collaboration work area.

Users with the Contract Manufacturer role can access the Supplier Portal to upload their production updates.

Users with the Supplier Inventory Manager role don't need access to the Supplier Portal because they already have access to the Supply Chain Collaboration work area.

Users with the Supply Chain Operations Manager role need access to the Supplier Portal to see their updates and what's in progress.

Users with the Supplier Inventory Manager role can access the Supplier Portal.

In Manage Planning Cycles, right-click the Product Review tab. and select Delete.

It is not possible to ignore any of the 5 pre-configured review stages.

In Manage Planning Cycles, do not add any participants or tasks for the Product Review stage.

In Manage Planning Cycles, go to the Actions menu, select Configure Stages, and set Enabled for Product Review to No.

If you use a predefined template, you can't change the business objects being collected, but you can change the Collection Type.

Net Change collection does not collect Shipment and Booking history data.

During a Targeted collection for a specific business object, the existing data is first purged from the planning data repository.

If only a few business objects are selected for collection, their data dependencies are not automatically included in the data collection.

Release Only by User

Auto-Release Interval in Days

Auto-Release Planned Order Time Fence

Quick Release Time Fence

Compression Days Tolerance for Automatic Release

Configure Planning Analytics > Levels and Attributes tab

The process "Add Levels and Attributes" must be run to associate new attributes.

The process "Associate Measure Catalog Attributes" must be run to associate new attributes.

Enable planner code on Planning Analytics page.

Configure Planning Analytics > Measure Catalog

A demand schedule can be another Demand Plan, a Sales & Operations Plan, or a Production Plan.

A demand schedule's "End Item Demand" measure must be one of: Final Shipments Forecast, Final Bookings Forecast. Approved Final Shipments Forecast, or Approved Final Bookings Forecast.

An integrated demand and supply plan can have more than one demand schedule.

External forecast loaded from flat files can be a demand schedule.

Planned Order for 200. Maximum Order Quantity enabled

Planned Order for 100. with Minimum Order Quantity enabled

Planned Order for 150, with Rounding enabled

Planned Order for 200. with Fixed Lot Size Multiplier enabled

Planned Order for 149, with Fixed Order Quantity enabled

No sourcing rules have been defined for the configured item.

The sourcing rules of the base model overrode the sourcing rules of the configured item.

It is not possible to create sourcing rules for the configured item; all configured items always use the same sourcing rules as the base model.

The sourcing rules of the base model had a priority of 1, while the sourcing rules of the configured item had a priority of 2.

No planning percentages were defined at the operation level within the work definition.

It does not recognize forecast exceptions.

It reads published planning data from interface tables.

It received supplier commits.

It creates or updates an order forecast, used by Supply Chain Collaboration to publish to suppliers.

The conditions under which exceptions are generated can be modified.

You can act on an exception by selecting it and clicking 'Resolve exception'. A list of ways to resolve will be generated.

The calculation logic for exceptions can be modified.

You can drill down into Supplies and Demand from an exception line.

You can export exception tables to Excel.

You can create custom exceptions.

Change item specification values, change item lead times, create mass changes for items

Add demands, cancel demands, reschedule demands, add supply, cancel supply, reschedule supplies

Change item specification values, change item lead times, change item-organization specification values

Add demands, cancel demands, reschedule demands, add new planned orders, reschedule supplies

Change item specification values, change item lead times, create mass changes for items all at once, change item-organization specification values

Drop Ship Item Validation Org has not been set up.

Drop Ship Demand Class has not be set up.

Supplier not configured in Manage Planning Source Systems

Include drop ship demands and supplies flag has not been checked on your plan options.

Planning Profile 'Enable Planning for Drop Shipments' has not been set to 'Yes'.

For plan parameters, select forecasting calendar as Gregorian and time level as week.

For forecasting items, select hierarchy as product, level as category level 1, and laptop and desktop categories as level members.

For plan parameters, select forecasting calendar as Gregorian and time level as month.

For plan organizations, select hierarchy as enterprise, level as country, and US as level member.

For forecasting items, select hierarchy as product, level as product, and all laptop and desktop products as level members.

For plan organizations, select hierarchy as enterprise, level as business unit, and US and level member.

It is the source for organization-item attributes when creating drop ship planned orders.

It can be a Cost Organization.

It is not required in order to use drop shipments.

It cannot be an item organization.

It is a proxy for the organization during the collections of drop ship sales orders and drop ship history.

It can be an item organization.

Under data refresh options, select "Refresh with selected current data" and chose sales orders.

Under data refresh options, select "Refresh with current data."

Select sales orders as forecast profile.

Select forecast shipments as forecast profiles.

Under data refresh options, select "Refresh with demand planning data."