planning implementing supply chain - oracle...oracle scm cloud implementing supply chain planning...

Oracle SCM Cloud

Implementing Supply ChainPlanning

20B

Oracle SCM CloudImplementing Supply Chain Planning

20BPart Number F27665-01Copyright © 2011, 2020, Oracle and/or its aliates.

Authors: Rohit Chaubey, B. Mise, D. West

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected byintellectual property laws. Except as expressly permied in your license agreement or allowed by law, you may not use, copy, reproduce, translate,broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering,disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you nd any errors, please reportthem to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, thenthe following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed oractivated on delivered hardware, and modications of such programs) and Oracle computer documentation or other Oracle data delivered to oraccessed by U.S. Government end users are "commercial computer software" or "commercial computer software documentation" pursuant tothe applicable Federal Acquisition Regulation and agency-specic supplemental regulations. As such, the use, reproduction, duplication, release,display, disclosure, modication, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system,integrated software, any programs embedded, installed or activated on delivered hardware, and modications of such programs), ii) Oracle computerdocumentation and/or iii) other Oracle data, is subject to the rights and limitations specied in the license contained in the applicable contract. Theterms governing the U.S. Government's use of Oracle cloud services are dened by the applicable contract for such services. No other rights aregranted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for usein any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware indangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safeuse. Oracle Corporation and its aliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its aliates. Other names may be trademarks of their respective owners.

Intel and Intel Inside are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarksor registered trademarks of SPARC International, Inc. AMD, Epyc, and the AMD logo are trademarks or registered trademarks of Advanced MicroDevices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. OracleCorporation and its aliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, andservices unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its aliates will not be responsiblefor any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicableagreement between you and Oracle.


Contents

Preface i

1 Overview 1Overview of Supply Chain Planning Implementation ............................................................................................................ 1

Supply Chain Planning Conguration Tasks ........................................................................................................................... 1

2 Planning Source Systems and Prole Options 5Manage Trading Community Source Systems for Data Collections .................................................................................. 5

Manage Planning Source Systems for Data Collections ...................................................................................................... 5

How You Manage Planning Prole Options ........................................................................................................................... 7

Considerations for Enabling Organizations for Data Collections ..................................................................................... 10

Dene Flexeld Mappings .......................................................................................................................................................... 11

3 Planning Data Collection 13Overview of Data Collections for Supply Chain Planning ................................................................................................... 13

Global Entities .............................................................................................................................................................................. 14

Data Collection Types for Supply Chain Planning ............................................................................................................... 15

How the Order Orchestration and Order Promising Processes Use the Collected Planning Data ............................. 16

How You Enable Cross-References of Entities by Data Collections ................................................................................. 17

How Planning Processes Collect Dierent Work Denitions and Item Structures ........................................................ 17

Enable External Data Collection for the Oracle Fusion Source System ........................................................................... 19

Collect Planning Data from the Oracle Fusion Source System ........................................................................................ 20

Load Planning Data from Others and External Source Systems ...................................................................................... 26

Verify Collection Processes ...................................................................................................................................................... 49

Aggregate Customer Data ......................................................................................................................................................... 51

4 Planning Analytics 55Overview of Planning Analytics ............................................................................................................................................... 55

Congure Planning Analytics ................................................................................................................................................... 55

Dimensions and Dimension Catalogs .................................................................................................................................... 57

Measure Catalogs ....................................................................................................................................................................... 60

Levels and Aributes .................................................................................................................................................................. 61


Preface

i

PrefaceThis preface introduces information sources that can help you use the application.

Using Oracle Applications

HelpUse help icons to access help in the application. If you don't see any help icons on your page, click your user imageor name in the global header and select Show Help Icons. Not all pages have help icons. You can also access the OracleHelp Center to nd guides and videos.

Watch: This video tutorial shows you how to nd and use help.

You can also read about it instead.

Additional Resources

• Community: Use Oracle Cloud Customer Connect to get information from experts at Oracle, the partnercommunity, and other users.

• Training: Take courses on Oracle Cloud from Oracle University.

ConventionsThe following table explains the text conventions used in this guide.

Convention Meaning

boldface Boldface type indicates user interface elements, navigation paths, or values you enter or select.

monospace Monospace type indicates le, folder, and directory names, code examples, commands, and URLs.

> Greater than symbol separates elements in a navigation path.

https://docs.oracle.com/en/cloud/saas/applications-help/

https://docs.oracle.com/en/cloud/saas/applications-help/

https://apex.oracle.com/pls/apex/f?p=44785:265:0::::P265_CONTENT_ID:27341

https://apex.oracle.com/pls/apex/f?p=44785:265:0::::P265_CONTENT_ID:27341

http://www.oracle.com/pls/topic/lookup?ctx=cloud&id=OACPR158049

https://appsconnect.custhelp.com/

http://education.oracle.com/pls/web_prod-plq-dad/db_pages.getpage?page_id=906


Preface

ii

Documentation AccessibilityFor information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website.

Videos included in this guide are provided as a media alternative for text-based help topics also available in this guide.

Contacting Oracle

Access to Oracle SupportOracle customers that have purchased support have access to electronic support through My Oracle Support. Forinformation, visit My Oracle Support or visit Accessible Oracle Support if you are hearing impaired.

Comments and SuggestionsPlease give us feedback about Oracle Applications Help and guides! You can send an e-mail to:[email protected].

http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc

http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info

http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs

mailto:[email protected]


Chapter 1Overview

1

1 Overview

Overview of Supply Chain Planning ImplementationTo implement Oracle Supply Chain Planning Cloud, you perform the tasks specied in the Supply Chain Planningoering. The Supply Chain Planning oering is available on the Oerings page in the Setup and Maintenance work area.

The Supply Chain Planning oering includes the following task lists:

• Dene Common Applications Conguration for Supply Chain Planning

• Dene Supply Chain Planning Conguration

• Dene Extensions for Supply Chain Planning

The setup and implementation of Supply Chain Planning follows the implementation of these other applications tocollect data from the Oracle Fusion source system:

• Oracle Product Management Cloud

• Oracle Supply Chain Materials Management Cloud

• Oracle Order Management Cloud

• Oracle Purchasing Cloud

• Oracle Manufacturing Cloud

Note: If you plan to implement only the Supply Chain Planning oering and you have a completely externalsource system from where you plan to collect data, you do not have to install other applications. Implementonly the Supply Chain Planning oering and then load data from external fulllment systems using CSV les.

The tasks that comprise the Dene Common Applications Conguration and Dene Extensions task lists aredocumented in the Oracle SCM Cloud Implementing Common Features for Oracle SCM Cloud guide. When you setup Supply Chain Planning you have already performed the tasks in these task lists for the other applications. You canperform additional setup for these tasks if needed. For example, if you need to set up additional users, you can do so.

The Dene Supply Chain Planning Conguration task list is specic to the Supply Chain Planning oering. The setuptasks that comprise this task list are documented in the SCM Cloud Implementing Supply Chain Planning guide.

Supply Chain Planning Conguration TasksThe Dene Supply Chain Planning Conguration task list is part of the Supply Chain Planning oering. If you havenavigated to the Setup: Supply Chain Planning page from the Supply Chain Planning oering in the Setup andMaintenance work area, the Supply Chain Planning Conguration functional area corresponds to the Dene SupplyChain Planning Conguration task list. The task list, or functional area, contains six tasks, two of which are required toset up Planning Central, Supply Planning, Demand Management, and Sales and Operations Planning work areas. Thistopic explains the following:

• The tasks included in the task list, or functional area, and which tasks are required.

• The work areas you can use to access the tasks.


Chapter 1Overview

2

The Tasks Included in the Task ListThe following table species which tasks are included in the Dene Supply Chain Planning Conguration task list orSupply Chain Planning Conguration functional area. The table also species which tasks are required.

Task Required or Optional Comments

Manage Trading Community SourceSystems

Optional

The Oracle Fusion source system ispredened. You must create a tradingcommunity model if the source systemversion is External

Manage Planning Source Systems

Optional

The Oracle Fusion source system ispredened. You must add a source system if youplan to perform supply chain planning forexternal source systems.

Manage Planning Prole Options

Optional

You can use the predened values for allof the prole options. To use the Order Promising work area,there is one prole option you mustdene: the Order Promising SourcingAssignment Set.

Collect Planning Data

Required

Planning Central, Supply Planning,Demand Management, and Sales andOperations Planning work areas use datacollected into the planing data repository. You must collect planning data to use anyof these products.

Load Planning Data from Files

Optional

If you are not using the Oracle sourcesystem to collect data, you can load datafrom CSV les for usage by Supply ChainPlanning work areas. For example, if you are using externaldata for Order Promising work area, youmust load data from these external sourcesystems.

Congure Planning Analytics

Required A minimum set of steps must be

completed for this task for plans to runsuccessfully.

Collect calendars from the Oracle Fusionsource.


Chapter 1Overview

3

Task Required or Optional Comments

Add the following to the defaultDimension catalog:

• At least one calendar to the Timehierarchy.

• At least one product catalog to theProduct Hierarchy, if the defaultPlanning Catalog is not collected.

Default hierarchies can be used for theother dimensions.

Work Areas to Use to Access the TasksYou can access the tasks included in the Dene Supply Chain Planning Conguration task list from the following workareas:

• Setup and Maintenance: Use the Supply Chain Planning oering on the Setup and Maintenance work area. Formore details regarding using the Setup and Maintenance work area to perform setup tasks, see the Oracle SCMCloud Implementing Common Features for Oracle SCM Cloud guide.

• Other Supply Chain Planning work areas (Planning Central, Supply Planning, Demand Management, and Salesand Operations Planning): Use the Task menu to access these tasks from one of the Supply Chain Planningwork areas.


Chapter 1Overview

4


Chapter 2Planning Source Systems and Prole Options

5

2 Planning Source Systems and ProleOptions

Manage Trading Community Source Systems for DataCollectionsThe Oracle Fusion source system is predened in the Trading Community Model. For a new installation, the name of thepredened Oracle Fusion source system is OPS. If the installation is an upgrade, the existing name of the source systemis used.

If you plan to collect data from external source systems, each source system must rst be added to the Manage TradingCommunity Source Systems page in the Setup and Maintenance work area. Here, the external source system indicatesthat the source system is not connected to any other Oracle Fusion applications. For example, you may want to collectdata for Oracle Fusion Global Order Promising Cloud from an external source system.

To reference a source system in a collections process, you must select the Enable for Order Orchestration and Planningcheck box. To open the Manage Trading Community Source Systems page, navigate to the Setup and Maintenancework area, and select the Supply Chain Planning oering. On the Setup: Supply Chain Planning page, click the SupplyChain Planning Conguration functional area. On the Supply Chain Planning Conguration page, you may have toselect All Tasks from the Show drop-down list to view the Manage Trading Community Source System task.

The types of source system are explained in detail in the Managing Planning Source Systems for Data Collections:Explained topic.

Manage Planning Source Systems for Data CollectionsTo populate the planning data repository, also known as the order orchestration and planning data repository, youcollect data from the Oracle Fusion source system. On the Manage Planning Source Systems page in one of the SupplyChain Planning work areas, enable organizations for collections. Depending on your security privilege, you can alsoenable organizations from the Setup and Maintenance work area.

In the Setup and Maintenance work area, use the following:

• Oering: Supply Chain Planning

• Functional Area: Supply Chain Planning Conguration

• Task: Manage Planning Source Systems

The Oracle Fusion Source SystemThe Oracle Fusion source system is included as a source system for data collection. Supply chain planning, orderorchestration, and order promising processes use data that are stored in the planning data repository. You ensure theCollections Allowed check box is enabled and manage which organizations you enable for collections.



6

To open the Manage Trading Community Source Systems page, navigate to the Setup and Maintenance work area anduse the following:



• Task: Manage Trading Community Source System

External Source SystemsYou can also allow collections for external source systems if you will be loading planning data from les for OracleFusion Global Order Promising. You must rst dene the external source system on the Manage Trading CommunitySource Systems.

There are two types of external source systems: Others and External.

Version ExternalThe version External source system indicates that the source system is not connected to any other Oracle Fusionapplications. This source system is not integrated with Oracle Fusion Product Data Model, Oracle Fusion TradingCommunity Model, and Oracle Fusion Order Management Cloud. The external source system is also referred as acompletely external source system. You cannot enable any other source system seings that are related to other OracleFusion applications. You can select the Collections allowed check box now or later depending on when you want to startcollecting data. This enables the source system for data collections using the le-based import process.

Version OthersThe version Others source system indicates that the source system is connected to other Oracle Fusion applications.This source system is integrated for Oracle Fusion Product Data Model, Oracle Fusion Trading Community Model, andOracle Fusion Order Management Cloud. The following conditions are applicable when the external source is Others.

• External system data for Items, Item Structures, and Catalogs is uploaded to Oracle Product Data Model Cloud

• External system data for Customers, Customer Sites, Regions and Zones is uploaded to Oracle TradingCommunity Model Cloud

• External system data for Sales Orders is uploaded to Oracle Order Management Cloud

For more information on types of data that can be collected for each source system, see the Import Templates Used toCreate CSV Files for Supply Chain Planning topic.

Organizations Enabled for Data CollectionsThe process for enabling organizations varies depending on the version of the source system.

To enable organizations for data collections when the source system version is Oracle Fusion, perform the followingsteps:

1. Click the Manage Organization List buon for your Oracle Fusion source system.2. Click the Refresh Organization List buon to update the organizations list3. Select the Enable for Collections check box for the organizations from which you want to collect data.



7

Tip: When performing collections during your initial setup, collect order orchestration reference objectsfrom the predened Oracle Fusion source system, and consider collecting organizations. After enablingorganizations for collection, collect organizations rst. You can conrm the collection results on the SupplyNetwork Model page.

To enable organizations for data collections when the source system version is External (completely external sourcesystem), upload organizations using the le-based import process. The organizations are automatically enabled forcollections.

To enable organizations for data collections when the source system version is Others, perform the following steps:

1. Dene an organization as an item-organization in the product data model.2. Upload the organization using the le-based import process and associate the organization with Others source

system.

Related Topics

• Import Templates Used to Create CSV Files for Supply Chain Planning

How You Manage Planning Prole OptionsFor Planning Central, Supply Planning, Demand Management, and Order Promising work areas, set prole options tospecify the following:

• The prole option used by Supply Chain Planning processes

• The sourcing assignment set and lead time multiplier used by the Check Availability process

• The number of minutes that the results from the Check Availability process remain valid on the CheckAvailability page, as well as whether the check availability page displays analytics

• The number of default display days for the Review Supply Availability page, as well as the organization calendarto be used for supply buckets in the Supply Availability report

• The category set used when assignment sets are created

Use the Manage Planning Prole Options task from one of the Supply Chain Planning work areas to open the ManagePlanning Prole Options page. From this page, you can manage all of the prole options except the following:

• Order Promising Sourcing Assignment Set

• Order Promising Horizon in Days

To manage these two prole options, use the Manage Administrator Prole Values task in the Setup and Maintenancework area to open the Manage Administrator Prole Values page. On the Manage Administrator Prole Values page,search for the prole option code MSP. The search results will also include the External ATP Web Service Enabled proleoption that must remain set to No in the current release.

For more information about prole options, see the Dene Prole Options section in the Oracle SCM CloudImplementing Common Features for Oracle SCM Cloud guide.

Supply Chain Planning ProcessesThis table lists the prole options that aect Supply Chain Planning processes. If the prole option does not have adefault value, the Default Value column in the table is shown as Not applicable.



8

Prole Option Display Name Default Value Eect

Catalog for Sourcing Assignments

Not applicable

Denes the catalog to be used whendening sourcing assignment sets.

Decimal Precision for Quantity Display

3

Sets the precision to which quantities arerounded for display in planning products.

Default Bookings History Measure

Booked Item by Booked Date

Species the default bookings historymeasure to use in demand forecasting.

Default Capacity Display Calendar

Not applicable

Species the default calendar to usefor the display of supplier capacity andresource availability in supply plans.

Default Shipments History Measure

Requested Item by Shipped Date

Species the default shipments historymeasure to use in demand forecasting.

Disable Search Warning in Planning Pages

No

Denes whether to disable the displayingof a warning when users try to run asearch without including certain keycriteria used to limit the amount ofinformation returned.

Enable Data Security for Planning

No

Enables planning data security todetermine access to Item, Organization,Customer, and Supplier data.

Fixed Plan Start Date

Not applicable

Species the xed plan start date forplanning applications, and in orderpromising, for selected organizationsusing the MM/DD/YYYY date format.

Full Data Access Allowed for Entities withNo Conditions Dened

Yes

Enables full data access allowed, insteadof no data access allowed, for entities withno data access conditions dened.

Maximum Rows Displayed in PlanningSearch Pages

100000

Sets the maximum number of rows todisplay for searches that return largevolumes of data.

Plan to Display Automatically

Not applicable

Species the name of the plan to beautomatically displayed.

Share Plan Partitions

No

Species whether a customerenvironment is partitioned by each plan.When enabled, a single partition is createdfor all plans.



9

Check Availability ProcessThis table lists the prole options that aect the Check Availability process. If the prole option does not have a defaultvalue, the Default Value column in the table is shown as Not applicable.


Order Promising Sourcing Assignment Set

Not applicable

Denes which sourcing assignment setwill be used by the supply allocation andcheck availability processes

Order Promising Horizon in Days

700

Sets the number of days into the futurefor which Oracle Fusion Global OrderPromising can schedule orders. Demandswith dates after the horizon cuto are notscheduled.

Supplier Capacity Accumulation LeadTime Multiplier

1

Denes the multiplier of the approvedsupplier list lead time to be used todetermine the date when to begin theaccumulation of supplier capacity

Check Availability PageThis table lists the prole options that aect the Check Availability page.


Timeout for Check Availability Results

10

Sets the number of minutes that theresults returned by the Check Availabilityprocess will remain valid on the CheckAvailability page

Analytics for Check Availability PageEnabled

Yes

If enabled, the Check Availability page willdisplay analytics

Fulllment Line Distribution Analytic Daysfor First Date Range

2

Sets the number of days for the rstlateness range in the Fulllment LineDistribution analytic

Fulllment Line Distribution Analytic Daysfor Second Date Range

7

Sets the number of days for the secondlateness range in the Fulllment LineDistribution Analytic

Fulllment Line Distribution Analytic Daysfor Third Date Range

14

Sets the number of days for the thirdlateness range in the Fulllment LineDistribution Analytic



10


Review Supply Availability Page and Supply Availability ReportThis table lists the prole options that aect the Review Supply Availability page and the Supply Availability report. If theprole option does not have a default value, the Default Value column in the table is shown as Not applicable.


Default Display Days in Review SupplyAvailability Page

21

Sets the number of horizon days for theReview Supply Availability page if end datewas not entered on the Check Availabilitypage

Organization Calendar for Supply Bucketsin Supply Availability Report

Not applicable

Denes the organization calendar to usefor the weekly and period supply bucketsin the Supply Availability report

Assignment Set, Assignment Level SelectionThis table lists the Sourcing Rule Category Set prole option. There is no default value for the Sourcing Rule CategorySet prole option. You must dene a value for the Sourcing Rule Category Set prole option to have the assignmentlevels that include categories available as choices for assignment level when creating assignment sets.

Prole Option Display Name Eect

Sourcing Rule Category Set

Determines which category set is used when dening assignment sets

Related Topics

• Overview of Prole Options

• Hierarchy in Prole Levels

Considerations for Enabling Organizations for DataCollectionsFrom the list of organizations for each source systems, you designate which organizations will have their data collectedwhen a collections process collects data from the source system.

http://www.oracle.com/pls/topic/lookup?ctx=fa20b&id=1DA7F9962C72097FE05362C3F00A358C

http://www.oracle.com/pls/topic/lookup?ctx=fa20b&id=95FA21E236672BB3E040D30A6881061E



11

Deciding Which Organizations to Enable for CollectionsTo determine which organizations to enable for collections, analyze the sourcing strategies for your company, the typeof organization for each organization in the list, and any other business requirements that would determine whethersystem resources should be expended to collect data from that organization. If the data from that organization wouldnever be used by order promising or order orchestration, no need to collect the data.

For example, consider a scenario where the list of organizations for a source system includes 20 manufacturing plantsand 10 distribution centers. Because the business requirements specify that the movements of materials from themanufacturing plants to the distribution centers are to be controlled separately from order orchestration and orderpromising, there are no sourcing rules that include transferring from one of the manufacturing plants. For this scenario,you would only enable the 10 distribution centers for collections.

Dene Flexeld MappingsIf your source systems include usage of exelds to capture additional aributes, you can map the exelds fromthe source system to the destination system. Use the Manage Planning Source Systems task to map the descriptiveexelds.

Oracle Fusion source systems support the descriptive exeld segment values from multiple source systems. Thiscapability enables you to combine exeld aributes on the same entity from multiple sources.

Perform the following procedure to dene the exeld mappings:

1. In the Setup and Maintenance work area, select the Supply Chain Planning oering.2. On the Setup: Supply Chain Planning page, click the Supply Chain Planning Conguration functional area.3. In the Supply Chain Planning Conguration list of all tasks, click the Manage Planning Source Systems task.4. On the Manage Planning Source Systems page, select your destination system.5. In the Source Systems section, select a source system, click Actions, and then click Dene Flexeld Mapping.6. In the Dene Flexeld Mapping dialog box, map the source entities for the available source and destination

exelds.7. Click Save and Close.

Related Topics

• Overview of Flexelds

http://www.oracle.com/pls/topic/lookup?ctx=fa20b&id=96E89901A4049BF4E040D30A68811939



12


Chapter 3Planning Data Collection

13

3 Planning Data Collection

Overview of Data Collections for Supply Chain PlanningTo run plans from one of the Supply Chain Planning work areas, you must collect data into a planning data repository.Order promising and order management processes also use the planning data repository to promise and manageorders.

To collect data into the planning data repository, you can perform these tasks from one of the Supply Chain Planningwork areas:

• Collect Planning Data: Use this task when you collect data from the Oracle Fusion source system.

• Load Planning Data from Files: Use this task when you collect data from a completely external source system.

Depending on your security privileges, you may need to manually add these tasks. In the Setup and Maintenance workarea, use the following:



• Task: Collect Planning Data

The following gure illustrates the collections processes that you can use to populate the planning data repository.

Collect Planning Data

Planning Data

Repository

Staging Table Load Process

Push

Pull

CSV Files

Oracle Fusion Source System

Load Planning Data from Files



14

Collect Planning DataThere are two steps involved in the data collection process. The Collect Planning Data process rst pulls data from theOracle Fusion source system into staging tables. The process then loads data from the staging tables into the planningdata repository.

On the Collect Planning Data page, use the following tabs to select what data you want to collect:

• Reference Data

• Demand Planning Data

• Supply Planning Data

Most of the reference data are global entities. Global entities are common for all source systems. For example, Units ofMeasure (UOM) is common for all source systems. The supply planning and demand planning data are transactionaldata. Most of the transactional data are local entities. Local entities are specic to each source system. For example, On-hand Quantity is specic for each source system.

You can also select collection lters to further rene what data you want to collect. You can save your selections tocollection templates.

Load Planning Data from FilesUse this option to populate the planning data repository using CSV les:

To load the planning data from les, follow these steps:

1. Create the CSV les. To create the CSV les, you can use a predened set of Microsoft Excel les as importtemplates.

2. Import the CSV les. From the navigator, click File Import and Export, and create a new import. Specify scm/planningDataLoader/Import for the account.

3. Submit the Load Planning Data from Files process. When you submit the process, the process rst pushes thedata from the CSV les into the staging tables. The process then loads the data from the staging tables into theplanning data repository.

Related Topics

• Update Existing Setup Data

Global EntitiesWithin data collections, Oracle Fusion Supply Chain Planning refers to certain business entities as global entities. Globalentities are specic for each instance and are common for all source systems. They are common without regard towhether they are collected from the Oracle Fusion source system or collected from an external source system using thele-based data import (FBDI) method.

When collecting data for a global entity, the planning data repository stores only one record for each instance of theglobal entity. The data collections process removes the source system reference from the global entity and stores thedata in the data repository. If the data collections process collects the same instance of a global entity from more thanone source system, the data repository stores the value from the last collection.

http://www.oracle.com/pls/topic/lookup?ctx=fa20b&id=13D98109B8975768E05362C3F00A8AE1



15

For example, the following scenario describes the collection method of the global entity called units of measure (UOM)from three source systems, namely source system A, B, and C respectively.

• Source system A has an instance of UOM. During the collection of UOMs from source system A, the kilogramUOM is collected. This is the rst time the kilogram UOM is collected. The data collections process creates akilogram record in the data repository.

• Source system B does not have any instances of UOM. During the collection of UOMs from source system B,the data collections process does not collect the kilogram value. Since there was no record for the kilogramUOM in source system B, the data collections process does not change the kilogram record in the datarepository. The record of the kilogram value from source system A is still valid.

• Source system C has an instance of UOM. During the collection of UOMs from source system C, the kilogramUOM is again collected. The data collections process registers the kilogram record in the data repository tomatch the values from source system C.

Note: When you use the FBDI collection method, the global entity les require a source system. Thecollections framework validates that the source system matches each record's source system. A source systemidentier marks each data record.

In Supply Chain Planning, the following entities are classied as global entities:

• Order Orchestration Reference Objects

• Units of Measure and UOM Conversions

• Demand Classes

• Currency and Currency Conversion Class

• Shipping Methods (Carrier, Mode of Transport, Service Level)

• Customer and Customer Site

• Suppliers and Supplier Sites

• Regions and Zones

• Approved Supplier List

• Supplier Capacity

• Planners

Data Collection Types for Supply Chain PlanningWhen you collect planning data, one of the parameters you specify for the Collect Planning Data task is the CollectionType parameter. You can select this task from any of your Supply Chain Planning work areas. For the Collection Typeparameter, you can select one of the following values:

• Targeted: Choose the Targeted collection type when you want to collect a signicant volume of source systemdata. Typically, you use the Targeted collection type in scenarios such as bulk upload of transaction data,instance upgrade, and change in collection lters.

• Net change: Choose the Net change collection type when you want to collect changed data and new recordssince the last successful collection cycle.

• Automatic selection: Choose the Automatic collection type when you want the planning process to decide andautomatically select an appropriate collection type for each of the entities.



16

TargetedYou use the Targeted collection type when you want to perform a complete refresh of the data in the data repository.In this mode, the planning process deletes the existing data for the selected entities from the data repository. Next, ifsubsequently collected from the source, the data for the selected entities replaces the deleted data.

Note: For the following data collection entities, you can use only the Targeted collection type: Item Costs,Resource Availability, Fiscal Calendars, and all Shipment and Booking History data.

Net changeWhen you use the Net Change collection type, you collect data incrementally. The Net Change collection type collectsonly changed or new data. Collecting data using the Net Change collection type is usually faster than using the Targetedcollection type. You typically use the Net Change collection type when you have previously performed a Targetedcollection, and now you want to keep your planning data current with your execution system data. You cannot select thedemand planning data when the collection type is Net Change.

Automatic selectionYou use the Automatic collection type when you are not sure which collection type to select and you want the planningprocess to decide the collection type for each entity. The planning process evaluates each entity on multiple factors,such as the last collected date for an entity, and decides whether to perform a Targeted or a Net Change collection forthe entity. You can manually select the entities that you want to collect or you can use one of the predened templatesto select your entities. If you select one of the predened templates, you can't make any changes in the Reference Data,Demand Planning Data, and Supply Planning Data tabs.

How the Order Orchestration and Order PromisingProcesses Use the Collected Planning DataYou perform data collections to populate the planning data repository. In addition to being used by Supply ChainPlanning processes, the collected data is used by Oracle Fusion Order Management order orchestration processes andby Oracle Fusion Global Order Promising processes.

Data CollectionsYou must perform data collections to populate the planning data repository, also called the order orchestration andplanning data repository, with data from the Oracle Fusion source system or from a completely external source system.When you load data from an external source system, use the XLSM les to organize your data in the required formatand then convert the data into CSV les. You can then upload the CSV les to the planning data repository.

Order OrchestrationOrder orchestration processes use some reference data directly from the planning data repository. You must performdata collections for the order orchestration reference entities even if you are not using the Supply Chain Planning workareas.



17

Note: Before collecting data from your Oracle Fusion source system, you must dene at least oneorganization for the source system. After you have set up at least one organization, you must updatethe organization list on the Manage Planning Source Systems page and then enable at least one of theorganizations for collections. If you have not enabled any organization, then the collections process ends withan error.

Order PromisingThe Global Order Promising processes use an in-memory copy of the data from the planning data repository. Whenorder orchestration processes send a scheduling request or a check availability request to Oracle Fusion Global OrderPromising, the order promising processes use the data stored in main memory to determine the response to send backto order orchestration. You must refresh the Global Order Promising data store after every collections so that the mainmemory always reect the current.

Related Topics

• Refresh the Global Order Promising Server

How You Enable Cross-References of Entities by DataCollectionsCross-references enable you to locate the correct source value for each cross-referenced entity. When you enableentities for cross-referencing, data collection pays aention to the cross-references that you have set up for certainvalues.

To enable cross-referencing of entities, click the Manage Planning Data Collection Processes task from your supplychain planning work area. Select the source system from the list, and then enable the available entities that you want tocross-reference during data collections.

You can view the cross-referenced data for each entity on the Cross-Reference Relationships for Collected Data page inthe Plan Inputs work area.

How Planning Processes Collect Dierent WorkDenitions and Item StructuresYou may be concerned that the work denition and item structure data in your supply chain planning work area doesnot match with what was dened in Oracle Manufacturing Cloud. You don't need to worry. The planning applicationcollects and uses data based on how the work denitions and item structures are dened and associated in themanufacturing source system.

Work Denitions and Item Structures in the Source SystemThe work denition is a primary source of data for the planning application. The planning process uses the workdenition of make order items to determine component and resource requirements. In case the work denition is not

http://www.oracle.com/pls/topic/lookup?ctx=fa20b&id=A1BFF74F47049E3EE040D30A68813ED6



18

dened, the planning process uses the dened item structure, but to plan for components only. If a work denitionis dened and no item structure is associated to it, then you can manually add ad hoc components to it. If an itemstructure is associated to it, you can still add ad hoc components to the work denition, alongside the components inthe item structure. Remember that while a work denition can be associated with only one item structure, one itemstructure can be associated with several work denitions within the parent item.

Work Denitions and Item Structures in the Planning DataRepositoryIn the manufacturing source system, the work denitions and item structures for an item can be dened and associatedin dierent ways. The following table lists the most common source system combinations and how the collections andrun plan processes proceed accordingly:

Manufacturing Cloud Denition Item Structure Name and WorkDenition Name in the Planning DataRepository

Planning Collections Processes

Only item structure is dened for an item.No work denition is dened.

Item structure name exists, no workdenition name

The planning process collects the itemstructure information but does not collectinformation for routing, operations, oritem resources. The planning process uses item structureto plan components and does not planresources.

Only work denition is dened for an item.No item structure is dened.

Work denition name exists, no itemstructure name

The planning process collects the workdenition information to populate theitem structure and routing information. The planning process populates thecomponent information and operationsequence number in the item structurebased on the ad hoc components andoperation assignment available in thework denition. The planning process uses the workdenition information to plan bothcomponents and resources.

Both item structure and work denitionare dened for the item.

Both work denition name and itemstructure name exist

The planning process uses thecomponents that are associatedwith the work denition to plan. Theplanning process does not consider anycomponents of item structure that arenot associated with the work denition.You can override the item structurecomponent usage within the workdenition. The planning process collects componentaributes (such as component eectivity)



19

Manufacturing Cloud Denition Item Structure Name and WorkDenition Name in the Planning DataRepository

Planning Collections Processes

from the item structure if the componentsare associated with the work denition. The planning process uses the workdenition to plan resources.

Both item structure and work denitionare dened for the item, but the workdenition does not refer to the itemstructure. Ad hoc components areassigned to the work denition operations.

Work denition name exists, no itemstructure name

The planning process collects thecomponents from the work denition andnot from the item structure in the OracleFusion Product Information Managementsolution. The process plans components based onwork denition operation assignmentsand plans resources based on the workdenition.

Enable External Data Collection for the Oracle FusionSource SystemEnable external data collection if you want to load transactional data from external systems. Typically, you do this ifsome of your supply chain processes are managed in external applications. You load the transactional data from theseapplications using le-based data imports (FBDI).

You can use external data sources for these functional areas: Inventory and Materials Management, Procurement,Order Management, and Manufacturing. When you enable external data collection for a functional area, be aware ofthese restrictions:

• You can't use congure-to-order, drop shipment, and back-to-back fulllment.

• The entities associated with the functional area are no longer available for Oracle Fusion source collection. Forexample, if you enable Order Management, the Sales Orders entity won't be available on the Collect PlanningData page for you to select for Oracle Fusion source collection.

This table lists the entities for each functional area.

Functional Area Entities

Inventory and Materials Management

On-hand Quantity and Transfer Orders

Procurement

Purchase Orders and Requisitions

Order Management

Sales Orders and Reservations



20

Functional Area Entities

Manufacturing

Work Order Supplies, Resource Availability, Resources, Work Denitions, and Item Structures

Enable External Data CollectionUse these steps to enable external data collection:

1. Select the Manage Planning Source Systems task in the Tasks panel from any Supply Planning work areapage. Or use this task in the Setup and Maintenance work area:

◦ Oering: Supply Chain Planning

◦ Functional Area: Supply Chain Planning Conguration

◦ Task: Manage Planning Source Systems

2. In the list of source systems, select the row that has Oracle Fusion in the Version column.3. In the Actions menu, click Select Data Sources.4. Select the Enable External Data check box, and then select the functional areas that you want to source

transactional entities for.

Note: Every time you enable or disable external data collection, you must run a targeted data collection toensure complete refresh of data in the data repository.

Collect Planning Data from the Oracle Fusion SourceSystem

How You Collect Dierent Data Types for Supply Chain PlanningWhen you collect data, you collect data from three categories: reference data, demand data, and supply data. On theCollect Planning Data page there is a tab for each of these categories.

The collected data are stored in the planning data repository.



21

The following gure illustrates the three categories of data that you collect from the Oracle Fusion source system to theplanning data repository.

Planning Data Repository

Reference Data

Supply DataDemand Data

1

32Manufacturing

Procurement

Materials Management

Order Management

Materials Management

Product Information Management

Costing

Explanation of Callouts

1. Reference data is primarily sourced from Oracle Fusion SCM Cloud2. Demand data comes from Oracle Order Management Cloud Service and Oracle Materials Management Cloud

Service3. Supply data is sourced from Oracle Inventory Management Cloud Service, Oracle Manufacturing Cloud Service,

and Oracle Purchasing Cloud Service

Reference DataThe collection process begins with reference data, which is primarily sourced from Oracle Fusion SCM Cloud. You collectthe data collection entities, such as basic item, resource, organization, customers and suppliers, and calendar data.

Note: Oracle Fusion Sales and Operations Planning uses the Bill of Resources entity to link the make itemswith their associated components and resource requirements. For more information on collecting Bill ofResources from an external source system, see the Loading Planning Data from Files section.

You also use Oracle Supply Chain Planning Cloud to collect the following items:

• Item structures: To explode item-level demand into component demands and supplies.

• Work Denitions: To assign the component and resource requirements for make items.

• Units of measure: To align plan data and to convert plans from one set of units to another.

• Costs: To review plans in nancial terms and evaluate the nancial impact of planning decisions.



22

Demand DataYou collect demand data from two potential sources:

• Sales orders that ow from Oracle Order Management Cloud Service: You can use this as the basis of thedemand forecast, while current orders can consume the demand in near-term forecast time buckets.

• Shipment history from Oracle Materials Management Cloud Service: You can use this to generate a shipmentsforecast.

Supply DataYou collect supply data from three sources:

• Oracle Inventory Management Cloud Service: This provides data related to on hand inventory, reservations,material transfers, in-transit supplies, and receipts.

• Oracle Manufacturing Cloud Service: This provides work in process status and any manufacturing work orders.

• Oracle Purchasing Cloud Service: This provides purchase requisitions and purchase orders.

Collection Filters and Collection TemplatesYou use collection lters and collection templates when you need to collect some common set of entities repeatedly.The collection lters and collection templates are located on the Collect Planning Data page. To open the CollectPlanning Data page, click the Collect Planning Data task from one of the Supply Chain Planning work areas.

Depending on your security privileges, you can also open the Collect Planning Data page from the Setup andMaintenance work area. In the Setup and Maintenance work area, use the following:



• Task: Collect Planning Data

Collection FiltersUse collection lters to improve the performance and eciency of the collections process, and to avoid accumulation ofirrelevant data in the planning data repository. You can use several lter criteria while performing collections, such as byemploying catalogs, order types, and price lists. You can also use date-based lters for collecting shipment and bookinghistory information.

Enabling Collection FiltersTo enable collection lters, you must rst run the schedule process called Load Filter Names for Planning DataCollection from the Scheduled Processes work area. When you run the scheduled process, the lters get enabled in theCollect Planning Data page. Then, you can apply the lters from the next collection.

Collection TemplatesUse collection templates when you want to collect a set of data repeatedly over a period. You can select either one ofthe predened templates that serves your specic need, or you can create your own template and save it for future use.

When you select a predened template from the list, the Collection Type eld is defaulted to Automatic selection andyou cannot edit the eld. Also, when you select a predened template, the Select Collection Filters eld is disabled.



23

You can create a collection template on the Collect Planning Data page by selecting the data collection entities andsaving the template for future use. For example, if you frequently collect certain supply planning transactional entities,such as On Hand, Purchase Orders, and Purchase Requisitions, then save these entities as a collection template. Itreduces the overhead of selecting the same entities for subsequent collection cycles.

If the template le contains any error during the upload process, rectify the issue found in the log le and upload thetemplate le again.

Collect Data Using Targeted Collection TypeTo perform a complete refresh of the data repository used by the Supply Chain Planning products, run a targetedcollection. You can run the targeted collection immediately or you can schedule the process to run later. Demandplanning data can only be collected by using the Targeted collection type.

Note: Before collecting demand planning data, you must successfully run the Load Filter Names forPlanning Data Collection scheduled process.

Perform the following steps to collect reference data, demand planning data, and supply planning data using theTargeted collection type.

1. Access the Collect Planning Data page from a Supply Planning work area or the Setup and Maintenance workarea.

◦ If you are in one of the Supply chain Planning work areas:

i. Click the Tasks panel tab.ii. In the Tasks panel drawer, click the Collect Planning Data link.

◦ If you are in the Setup and Maintenance work area, then select the following:

• Oering: Supply Chain Planning• Functional Area: Supply Chain Planning Conguration• Task: Collect Planning Data

2. On the Collect Planning Data page, complete the following steps.

◦ On the Parameters tab:

i. Select your source system.ii. For the collection type, select Targeted.

Demand planning data can only be collected by using the Targeted collection type.iii. Click Select Collection Filters to select the collection lters.

◦ On the Reference Data subtab, move the required reference entities to the Selected Entities area.

◦ On the Demand Planning Data subtab, set options to collect the historical demand data in the planningdata repository. The planning process uses the historical demand data for statistical forecasting.

• Collection Time Frame Options: You can specify a xed or rolling date range for which to collectdata.

The Fixed Date Range option enables you to collect history data within a xed date range that youspecify.



24

The Rolling Date Range option enables you to collect the history data for the number of days thatyou specify. For example, if you forecast weekly, specify 7 in the Number of Days to Collect eldto collect the demand history data once per week. The data collections collect the demand historydata for the latest week.

Select Roll o time periods automatically to truncate the history data by the number of days thatyou specify in the Number of days to keep eld each time you run collections for the demandhistory data. For example, if you prefer to forecast each week based on the history data of 52weeks, select the Roll o time periods automatically check box and specify Number of daysto keep as 364 days. This seing ensures that as you collect data every week, you keep the mostrecent history of 52 weeks and automatically purge history data older than 52 weeks.

• History Measures and Aributes: Select your shipments history and bookings history measures.• Collection for ETO Items: Select Collect history from associated base models to collect

bookings and shipments history for Engineer to Order (ETO) items from the associated basemodels. When you don't select this option, the history is collected from the standard ETO items.

• History Data Options: To collect only specic order types, select from the Order Types to Includelist of values. By default, all order types are included.

Select Organization - Consumption Inventory Transactions to Include to collect consumptioninventory transactions at the organization level. You can collect only the transfer orders inventorytransactions or all consumption inventory transactions.

Select Subinventory - Consumption Inventory Transactions to Include to collect consumptioninventory transactions at the subinventory level. You can collect only the transfer orders inventorytransactions or all consumption inventory transactions for the organizations that you enabled forsubinventory planning.

Select the Collect amount data for history check box to collect amount data.• Additional Options: Select additional options for collections.

Collect Price Lists: Collect the price lists specied in the collections lter for price lists, or collect allprice lists if no lter is specied.

Collect Congure to Order Data: If you selected history measures and aributes, then select therelevant check boxes to collect shipment history options and booking history options.

Sales Organization Hierarchy: Select Enable sales organization hierarchy collection to collectone or more sales hierarchies.

◦ On the Supply Planning Data subtab:

i. Move the required supply entities to the Selected Entities area.ii. If you collect resource availability, then select a date range type: Fixed or Relative to collection

run date.

If you selected Fixed, then provide a start date and an end date for collecting resource availability.

If you selected Relative to collection run date, then enter a number of days in the CollectionWindow in Days eld. The number that you enter determines a collection window in days to collectresource availability based on a rolling time window. That rolling time window adjusts itself, basedon the date that you run collections. For example, if you specify 90, then resource availability iscollected for the next 90 days each time from the date of the collection run.



25

Note: You can save your date range type selection for resource availabilitycollection as a collection template to use later.

iii. You can collect the existing data for the resource availability.iv. You can also regenerate the resource availability data and then collect the data. If you select the

Regenerate data, and then collect option, the collections process runs the Update ResourceAvailability Job scheduled process rst and then collects the resource availability data.

3. (Optional) Click the Schedule tab and set collections to run as soon as possible or schedule to run at a dierenttime.

4. Click Submit to start the collections process.5. Monitor the collection status using the Scheduled Processes page.6. Review the collected data in the Plan Inputs work area.

Related Topics

• Set Up Forecast Consumption for Transfer Orders

Collect Data Using Net Change Collection TypeYou can collect data from the Oracle Fusion source system by running the net change collection or by scheduling to runthe process later. Before running a Net Change collection, you must run a Targeted collection for the selected entities.After the rst Targeted collection, you can run Net Change collections.

Perform the following procedure to collect reference data and supply planning data using the net change collectiontype:

1. If you are in one of the Supply Chain Planning work areas, then click the Tasks panel tab. In the Tasks paneldrawer, click the Collect Planning Data task. If you are in the Setup and Maintenance work area, then use thefollowing:



◦ Task: Collect Planning Data

2. Complete the following parameters for the Collect Planning Data process:

a. Select your source system.b. Select the collection type as Net change.

Note: You cannot make any changes to the lter criteria and demand planning data inthe net change collection type.

c. In the Reference Data tab, move the required reference entities to the Selected Entities area.d. In the Supplies Planning Data tab, move the required supply entities to the Selected Entities area.

3. (Optional) Click the Schedule tab and set collections to run as soon as possible or schedule to run at a dierenttime.

4. Click Submit to initiate the collections process.5. Monitor the collection status using the Scheduled Processes page.6. Review the collected data in the Plan Inputs work area.

http://www.oracle.com/pls/topic/lookup?ctx=fa20b&id=78499167FD3B5900E053A398F70A27BE



26

Related Topics• Update Existing Setup Data

Enable Organization Group Collection for the Net ChangeCollection TypeYou can use organization groups to limit the net change data collection from a source system to specic organizations.Using organization groups for collection also eliminates the chances of data overlap when multiple instances of netchange collections are run at a time. Planners can run collections for their organizations without waiting for each other.

Let's take a simple example where your organization considers only the D1 and D2 distribution centers in your sourcesystem for shipments to your customers. In such a case, you can create an organization group, assign D1 and D2 to theorganization group, and collect net change data specically for this group.

Note: Before you begin, ensure that you have your organization groups created. A supply planner creates andmanages organization groups using the Manage Organization Groups buon on the Maintain Supply NetworkModel page.

Do these to collect net change data for an organization group.

1. Access the Collect Planning Data page or Load Planning Data from Files page from a Supply Planning workarea.

2. Select the source system. Organization groups are managed within the source systems.3. Select the Net Change collection type. You can select an organization group for data collection only when the

collection type is Net Change.4. Enable the organization group collection, and then select an organization group.5. Perform the net change data collection. Refer to the Collect Data Using Net Change Collection Type topic in this

chapter for instructions.

Note: After selecting your organization group and other data collection entities, you can also save yourselections as a template. Refer to the Collection Filters and Collection Templates topic in this chapter foradditional information.

Related Topics• How You Maintain Your Supply Network Model

Load Planning Data from Others and External SourceSystems

How You Load Planning Data from FilesYou upload data using CSV les for specic business objects using the targeted or net change method.

Note: To create the CSV les, you can use a set of Microsoft Excel template les that are provided for thispurpose. You can download the templates from the File-Based Data Import for SCM Cloud guide in the OracleHelp Center.

http://www.oracle.com/pls/topic/lookup?ctx=fa20b&id=13D98109B8975768E05362C3F00A8AE1

http://www.oracle.com/pls/topic/lookup?ctx=fa20b&id=3262B9A5EB8C7207E05362C3F00A26B5



27

You use the targeted mode when you want to refresh data for selected entities in the planning data repository. You usethe net change mode to collect data incrementally. The net change collections mode collects only the changed or newdata. Data collection using the net change mode is fast compared to the targeted mode. The net change mode is usedto retain planning data to current with that of the executing system.

The following gure illustrates the process of collecting data from les.

Prepare the Data Files

Run the Load Process

Verify the Load Process

Review the Loaded Data

To load planning data from les, you perform the following steps:

1. Create CSV les using Microsoft Excel template2. Run the process to load planning data from les3. Verify the load planning data process4. Review the loaded data

Create CSV Files to Load Planning DataTo perform the Load Planning Data from Files task in one of the Supply Chain Planning work areas or Setup andMaintenance work area, you must prepare the data you want to load. You must create the necessary CSV les used tocreate les for import. This procedure explains how to create CSV les to prepare planning data for loading.

1. Locate the applicable le import templates (XLSM les) in the following guide: File Based Data Import for OracleSupply Chain Management Cloud. Extract the templates to a local space.



28

For additional information about creating and importing CSV les, see the following section in the Oracle SCMCloud Implementing Common Features for Oracle SCM Cloud guide: External Integration chapter, External DataIntegration Services for Oracle Cloud section.

2. Open the template le for the entity you are preparing and complete the le import template worksheet.

You must enable the macros in the template le before generating the CSV le.

Caution: For the cells that contain dates, ensure that the data is set to the correct format inthe data type. For example, date must be set to YYYY/MM/DD.

3. After you nish preparing the data in the worksheet, generate the CSV le. The Generate CSV File buon islocated in the Instructions and CSV Generation worksheet of the workbook.

4. When you save the generated CSV le, you must use the suggested name of the entity. You can addunderscore and add additional characters to the le name. For example, you can name the CSV le asShipmentHistory_abc.csv and you can name the le as LoadingCSV.zip.

5. Compress the CSV le into a zipped le format using a compression utility. You can provide any name to thezipped le.

Note: You can include multiple CSV les in a single compressed le for a source system. Theload process uploads them in a sequential order. Select the CSV les and compress themdirectly. Do not compress the parent folder that contains the les.

This completes the preparation of a le that you will upload to collect planning data.

Data Collection SequenceThis topic explores the sequence that you should follow for data collection. Data collection involves collecting entitiesin a predened sequence. The collected entities form the basis for supply planning calculations. To have accurate data,you must ensure to collect the entities in a proper sequence. You cannot collect some entities without collecting theirprecursor entities. The data collection sequence is very crucial when you collect data from an external source systemusing CSV les.

If you run targeted collections for all entities, you can ignore the sequence for collections because targeted collectionsautomate the collection sequence for all entities within a single collections request. If you collect many entities in asingle request, collections will process them according to the sequences shown in this topic. If you collect only a fewentities, then you must be aware of the collections sequence information. For example, you should not collect workorders before you collect items or resources.

To make the workow simple, the collection sequence is divided into two parts - Part A and Part B. The collectionentities in Part B are dependent on the collection entities in Part A. You must collect the entities in Part A before youcollect the entities in Part B. Also, the collection entities are grouped together for easier presentation. The data groupsin Part A are:

• Collections Sequence Part A for Item Data

• Collections Sequence Part A for Region, Location, and Customer Data

• Collections Sequence Part A for Currency, Calendar, Demand Class, and UOM Data



29

The data groups in Part B are:

• Collections Sequence Part B for Sales Order and Assignment Sets

• Collection Sequence Part B for Work Orders, Work Denition, and Item Structure

Every collection sequence in Part A starts with dening a source system where the collected data will reside. If you arecollecting data to the same source system, you dene the source system only once. Then, use the same source systemto collect all the entities.

The following gure provides an overview of the data collection sequence. The overview shows how Part A and Part B ttogether to form a complete data collection ow.

Collection Sequence Part A for Item Data

Collection Sequence Part A for Region,

Location, and Customer Data

Collection Sequence Part A for Currency, Calendar, Demand Class, and UOM

Data

Continue to Collection Sequence

Part B

Collection Sequence Part B for Sales

Order and Assignment Sets

Collection Sequence Part B for Work Orders, Work

Definition, Item Structure

Data Collection Sequence Overview

Part A

Part B

Collections Sequence Part A for Item DataThe following image shows the collections sequence to follow while collecting Item data from external source systems.This image represents only half of the entities for collecting Item data.

Note: The Organization entity is marked with an asterisk because you can collect other entities such asPlanner, Item Cost, Subinventory, Carrier, Calendar Assignment, Supplier, and Supplier Site after collectingOrganization. For more information on the collection sequence for these entities, see the CollectionsSequence Part A for Currency, Calendar, Demand Class, and UOM Data gure. Refer to the entities that arecollected after Organization. Also, ensure that you collect Location before collecting Supplier Site.



30

Define Source System Organization*

ItemsLoad Items in PIMLoad UOM

Create Organizations

Item CostsItem RelationshipCustomer Specific Item RelationshipsUOM Class

Conversions

Item Catalog

Catalog Category Association

Item Category

Safety Stock Level


Part B

Item Structure

Item Structure Component

Collection Sequence Part A for Item Data

When you collect the data described here, continue to the collection sequence Part B described in the followingsubsections.

• Collection Sequence Part B for Sales and Order and Assignment Sets




31

Collections Sequence Part A for Region, Location, and Customer DataThe following image shows the collections sequence to follow while collecting Regions, and Customers data fromexternal source systems. This image represents only half of the entities for Item data.

Define Source System

Customer Region

Load Customer Sites in TCA

Load Customers, Regions in TCA

Sourcing Rules, Sourcing

Assignments, Source Organization,

Receipt Organization

Customer Sites

Calendar Assignments

Ship Methods

Collection Sequence Part A for Region, Location, and Customers Data

Customer Specific Item Relationships


Part B

Location






32

Collections Sequence Part A for Currency, Calendar, Demand Class, and UOM DataThe following image shows the collections sequence to follow while collecting Currency, Calendar, Demand Class, andUOM data from external source systems. Also, ensure that you collect Location before collecting Supplier Site.

Note: The Calendar entity is marked with an asterisk because there are other entities that are associatedwith Calendar that you must collect in a sequence. To collect other entities associated with Calendar, see theCalendar Upload Sequence gure.

Collection Sequence Part A for Currency, Calendar, Demand Class and UOM Data

Currency Calendar*

Define Source System

Currency Conversion Type

Currency Conversion Rate UOM Conversions

UOM Class Conversions

Demand Class UOM

Organization*

Continue to the next diagram

Location



33

Planner Subinventory

Continue from the previous diagram, after Organization

Calendar Assignment

Supplier Site


Part B

Carrier Supplier

Item Cost






34

Collection Sequence for Calendar DataThe following image shows the collections sequence to follow for collecting the Calendar data. Calendar data is a partof the data collection in Part A. You collect the Calendar data in the following subsection: Collection Sequence Part A forCurrency, Calendar, Demand Class, and UOM Data.

Calendar Upload Sequence

Calendar Shifts Calendar Exceptions

Calendar

Period Start Days Week Start Dates

Calendar Workday Pattern

Generate Calendar Dates Post Collection



35

Collections Sequence Part B for Sales Order and Assignment SetsThe following image shows the collections sequence to follow while collecting Sales Order and Assignment Sets datafrom external source systems. The data entities in Part B are dependent on Part A. So, you must collect entities listed inPart A before you collect the entities in Part B.

Ship Methods

ASL, Supplier Capcity Planned Orders

Forecasts

Sourcing Rules, Sourcing Assignments, Source Organization, Receipt Organization

Reservations

On Hand

Sales Orders

Transfer Order Purchase Orders

Collections Sequence Part B for Sales Orders and Assignments Sets


Part B

Collection Sequence Part

A



36

Collection Sequence Part B for Work Orders, Work Denition, and Item StructuresThe following image shows the collections sequence to follow while collecting Work Orders, Work Denition, and ItemStructure data from external source systems. The data entities in Part B are dependent on Part A. So, you must collectentities listed in Part A before you collect the entities in Part B.

Item Structure Component Operations

Item Structure Component Substitutes

UOM Conversions

Department Resources

Reservations

Resource Availability

Resource Capacity

Work Definition

Work Orders

Work Order Material

Requirement

Work Order Resource

Requirement

Collection Sequence Part B for Work Orders, Work Definitions, and Item Structures

Collection Sequence

Part A

Bill of Resources


Part B

Import Templates Used to Create CSV Files for Supply ChainPlanningYou can use the Microsoft Excel templates (XLSM les) to prepare the data for the supported collection entities. Thetemplates are listed in the following guide: File-Based Data Import for Oracle Supply Chain Management Cloud. Extract



37

the templates to a local drive, enter appropriate data as described in the template, and generate CSV les. Compressthe CSV les to a zipped le format and upload the .zip le to the Universal Content Manager using the File Import andExport utility. The data is then loaded from the Universal Content Manger to the planning data repository.

Collect Data from the Oracle Fusion Source

The following table lists the collections entities that can be loaded into the planning data repository for the OracleFusion source. The Collection Entity column provides the name of the entities for which you can collect the data.The XLSM File Name column provides the template name that you will download for the respective collection entity.Download the XLSM template from the File-Based Data Import for Oracle Supply Chain Management Cloud guide (FBDIguide). The Link in Data Import Guide column provides the name of the topic in the FBDI guide from where you willdownload the template. For example, to collect data for the Item Costs collection entity, refer to the Item Cost Importtopic in the FBDI guide.

Collections Entity Link in Data Import Guide XLSM File Name

Item Costs

Supply Chain Planning Item Cost

ScpItemCostImportTemplate. xlsm

Customer Specic Item Relationships

Supply Chain Planning Item Substitute

ScpItemSubstituteImportTemplate. xlsm

Planners

Supply Chain Planning Planners

ScpPlannersImportTemplate. xlsm

Item Suppliers

Supply Chain Planning Approved SupplierList

ScpApprovedSupplierListImportTemplate.xlsm

Demand Classes

Supply Chain Planning Demand Classes

ScpDemandClassImportTemplate. xlsm

Allocation Assignments and AllocationRules

Supply Chain Planning Planning AllocationRules

ScpPlanningAllocationRulesImportTemplate.xlsm

ATP Assignments and ATP Rules

Supply Chain Planning Available-to-Promise Rules

ScpATPRulesImportTemplate. xlsm

Supply Update Rules

Supply Chain Planning Real Time SupplyUpdates

ScpRealTimeSupplyUpdatesImportTemplate.xlsm

Measures

Supply Chain Planning Measures

ScpMeasuresImportTemplate. xlsm

Booking History

Supply Chain Planning Bookings History

ScpBookingHistoryImportTemplate. xlsm



38


Note: This templatehas been supersededby the generic templateScpMeasuresImportTemplate. xlsmbut will continue to be supported.Future enhancements will be madeonly to the generic measurestemplate.

Option Booking History

Supply Chain Planning Option BookingsHistory

ScpOptionBookingHistoryImportTemplate.xlsm


Shipment History

Supply Chain Planning Shipments History

ScpShipmentHistoryImportTemplate. xlsm


Option Shipment History

Supply Chain Planning Option ShipmentsHistory

ScpOptionShipmentHistoryImportTemplate.xlsm


Price Lists

Supply Chain Planning Price List

ScpPriceListImportTemplate. xlsm



39


Causal Factors

Supply Chain Planning Causal Factors

ScpCausalFactorsImportTemplate. xlsm

Forecast Measures

Supply Chain Planning Forecast Measures

ScpForecastMeasureImportTemplate.xlsm


Fiscal Calendars

Supply Chain Planning Fiscal Calendars

ScpFiscalCalendarImportTemplate. xlsm

Forecasts

Supply Chain Planning External Forecasts

ScpExternalForecastImportTemplate. xlsm

Safety Stock Levels

Supply Chain Planning Safety Stock Levels

ScpSafetyStockLevelImportTemplate.xlsm

Supplier Capacity

Supply Chain Planning Approved SupplierCapacity

ScpApprovedSupplierCapacityImportTemplate.xlsm

Planned Order Supplies

Supply Chain Planning Planned OrderSupply

ScpPlannedOrderSupplyImportTemplate.xlsm

Sourcing Rule and Assignments

Supply Chain Planning Sourcing Rules

ScpSourcingImportTemplate. xlsm

Cross-Reference Mapping Information

Supply Chain Planning Cross-ReferenceData

ScpCrossReferenceDataImportTemplate.xlsm

Collect Data from External Source - Version Others

The following table lists the collections entities that can be loaded into the planning data repository from an externalsource, where the version is Others. The Collection Entity column provides the name of the entities for which you cancollect the data. The XLSM File Name column provides the template name that you will download for the respectivecollection entity. Download the XLSM template from the File-Based Data Import for Oracle Supply Chain ManagementCloud guide (FBDI guide). The Link in Data Import Guide column provides the name of the topic in the FBDI guide fromwhere you will download the template. For example, to collect data for the Items and Item Costs collection entities, referto the Item Cost Import topic in the FBDI guide.



40


Item Costs



Customer Specic Item Relationships



Planners



Organizations (Warehouses) andOrganization Site (Including OrganizationSite - Internal Location Mapping)

Supply Chain Planning Organizations

ScpOrganizationImportTemplate. xlsm

Subinventories

Supply Chain Planning Subinventories

ScpSubInventoryImportTemplate. xlsm

Suppliers and Supplier Sites

Supply Chain Planning Suppliers

ScpPlanningSupplierImportTemplate.xlsm

Item Suppliers



Interlocation Shipping Networks

Supply Chain Planning InterlocationShipping Methods

ScpInterLocationShipMethodsImportTemplate.xlsm

Currencies, Currency Conversion Types,and Currency Conversion Rates

Supply Chain Planning Currencies

ScpCurrencyImportTemplate. xlsm

Units of Measure, Units of MeasureConversions, and Units of Measure ClassConversions

Supply Chain Planning Units of Measure

ScpUOMImportTemplate. xlsm

Calendars, Calendar Exceptions, CalendarShifts, Week Start Dates, Period StartDates, and Calendar Shift Workday Paern

Supply Chain Planning Calendars

ScpCalendarImportTemplate. xlsm

Calendar Associations

Supply Chain Planning CalendarAssignments

ScpCalendarAssignmentsImportTemplate.xlsm

Demand Classes



Ship Mode of Transport, Ship Class ofService, and Carrier

Supply Chain Planning Carriers

ScpCarrierImportTemplate. xlsm

Allocation Assignments and AllocationRules





41


ATP Assignments and ATP Rules



Supply Update Rule



Freight Terms, FOB Points, Invoicing andAccounting Rules, Shipment Priorities,Payment Terms, Return Reason, TaxClassication Code, Tax ExemptionReason, Sales Credit Type, Activity Type,Document Categories, Payment Methods,and Receipt Methods

Supply Chain Planning OrderOrchestration

ScpOrderOrchestrationImportTemplate.xlsm

Measures



Booking History








Shipment History





42







Price Lists

Supply Chain Planning Price Lists


Causal Factors



Forecasts Measures




Fiscal Calendars



Forecasts

Supply Chain Planning External Forecast


User-Dened Hierarchies

Supply Chain Planning User-DenedHierarchies

ScpUser-DenedHierarchyImportTemplate. xlsm



43


Safety Stock Levels



Supply Reservations to Sales Orders

Supply Chain Planning Reservations

ScpReservationImportTemplate. xlsm

On Hand

Supply Chain Planning Supply On Hand

ScpOnhandImportTemplate. xlsm

Purchase Orders, Purchase Requisitions,PO in Receiving, and In Transits

Supply Chain Planning Purchase OrderRequisitions

ScpPurchaseOrderRequisitionImportTemplate.xlsm

Transfer Orders

Supply Chain Planning Transfer Orders

ScpTransferOrderImportTemplate. xlsm

Supplier Capacity



Resources and Resource Shifts

Supply Chain Planning Resources

ScpResourcesImportTemplate. xlsm


Supply Chain Planning ResourceAvailability

ScpResourceAvailabilityImportTemplate.xlsm

Work Denition (Including mappingbetween Item Structures and WorkDenitions), Work Denition Operations,and Work Denition Operation Resources

Supply Chain Planning Routings

ScpRoutingsImportTemplate. xlsm

Work Order Supply

Supply Chain Planning Work OrderSupplies

ScpWorkOrderSuppliesImportTemplate.xlsm

Work Order Material Requirements

Supply Chain Planning Work OrderComponent Demands

ScpWIPComponentDemandsImportTemplate.xlsm

Work Order Resource Requirements

Supply Chain Planning Work OrderOperation Resources

ScpWIPOperationResourceImportTemplate.xlsm







Cross Reference Mapping Information





44


Key Customer Options

Supply Chain Planning Key CustomerOptions

ScpKeyCustomerOptionsImportTemplate.xlsm

Collect Data from External Source - Version External

The following table lists the collections entities that can be loaded into the planning data repository from an externalsource, where the version is External. The Collection Entity column provides the name of the entities for which you cancollect the data. The XLSM File Name column provides the template name that you will download for the respectivecollection entity. Download the XLSM template from the File-Based Data Import for Oracle Supply Chain ManagementCloud guide. The Link in Data Import Guide column provides the name of the topic in the File-Based Data Import forOracle Supply Chain Management Cloud guide (FBDI guide) from where you will download the template. For example,to collect data for the Items and Item Costs collection entities, refer to the Item Cost Import topic in the File-BasedData Import for Oracle Supply Chain Management Cloud guide. All the planning-related entity names are prexed withSupply Chain Planning in the FBDI guide.

Collection Entities Link in FBDI Guide XLSM File Name

Items

Supply Chain Planning Items

ScpItemImportTemplate. xlsm

Item Costs



Item Relationships



Catalogs, Categories, and Item Categories

Supply Chain Planning Catalogs

ScpCatalogImportTemplate. xlsm.xlsm

Item Structures

Supply Chain Planning Item Structures

ScpBillofMaterialImportTemplate. xlsm

Bill of Resources

Supply Chain Planning Bill of Resources

ScpBillOfResourcesImportTemplate. xlsm

Planners



Customers and Customer Sites

Supply Chain Planning Customers

ScpCustomerImportTemplate. xlsm

Regions

Supply Chain Planning Regions

ScpRegionsImportTemplate. xlsm

Zones

Supply Chain Planning Zones

ScpZonesImportTemplate. xlsm

Region-Zone Mapping

Supply Chain Planning Region ZoneMappings

ScpRegionZoneMappingImportTemplate.xlsm

Locations and Region-Location Mapping Supply Chain Planning Locations ScpLocationsImportTemplate. xlsm



45


Organizations and Organization Sites

Supply Chain Planning Organizations

ScpOrganizationImportTemplate. xlsm

Subinventories

Supply Chain Planning Subinventories

ScpSubInventoryImportTemplate. xlsm

Suppliers and Supplier Sites

Supply Chain Planning Suppliers

ScpSupplierImportTemplate. xlsm

Item Suppliers (Approved Supplier List)



Interlocation Shipping Networks andTransit Times

Supply Chain Planning InterlocationShipping Methods

ScpInterLocationShipMethodsImportTemplate.xlsm

Currencies and Currency Conversions

Supply Chain Planning Currencies

ScpCurrencyImportTemplate. xlsm

Units of Measure, Units of MeasureConversions, and Units of Measure ClassConversions

Supply Chain Planning Units of Measure

ScpUOMImportTemplate. xlsm

Calendars, Calendar Exceptions, Shifts,Shift Workday Paern, Week Start Dates,and Period Start Dates

Supply Chain Planning Calendars

ScpCalendarImportTemplate. xlsm

Calendar Associations

Supply Chain Planning CalendarAssignments

ScpCalendarAssignmentsImportTemplate.xlsm

Demand Classes



Carrier, Ship Mode of Transport, and ShipClass of Service

Supply Chain Planning Carriers

ScpCarrierImportTemplate. xlsm

GOP Allocation Rules and RuleAssignments



GOP ATP Rules and Rule Assignments



GOP Supply Update Rules



Order Orchestration Reference Objects:Freight Terms, FOB Points, Invoicing andAccounting Rules, Shipment Priorities,Payment Terms, Return Reason, Tax

Supply Chain Planning OrderOrchestration

ScpOrderOrchestrationImportTemplate.xlsm



46


Classication Code, Tax ExemptionReason, Sales Credit Type, Activity Type,Document Categories, Payment Methods,and Receipt Methods

Cross Reference Mapping Information



Measures



Booking History








Shipment History









47



Price Lists

Supply Chain Planning Price Lists


Causal Factors



Forecast Measures




Fiscal Calendars



Measures, Sales and Operations PlanningBacklog, Inventory, and ProductionHistory



User-Dened Hierarchies

Supply Chain Planning User-DenedHierarchies

ScpUser-DenedHierarchyImportTemplate. xlsm

Forecasts

Supply Chain Planning External Forecasts


Sales Orders

Supply Chain Planning Sales Orders

ScpSalesOrderImportTemplate. xlsm

Safety Stock Levels



Supply Reservations to Sales Orders

Supply Chain Planning Reservations

ScpReservationImportTemplate. xlsm



48


On Hand

Supply Chain Planning Supply On Hand

ScpOnhandImportTemplate. xlsm

Purchase Orders, Purchase Requisitions,PO in Receiving, In Transits

Supply Chain Planning Purchase OrderRequisitions

ScpPurchaseOrderRequisitionImportTemplate.xlsm

Transfer Orders (including expense typetransfers)

Supply Chain Planning Transfer Orders

ScpTransferOrderImportTemplate. xlsm

Supplier Capacity



Resources, Resource Shifts

Supply Chain Planning Resources

ScpResourceImportTemplate. xlsm


Supply Chain Planning ResourceAvailability

ScpResourceAvailabilityImportTemplate.xlsm

Work Denition (including mappingbetween Item Structures and WorkDenitions), Work Denition Operations,Work Denition Operation Resources

Supply Chain Planning Routings

ScpRoutingsImportTemplate. xlsm

Work Order Supply

Supply Chain Planning Work OrderSupplies

ScpWorkOrderSuppliesImportTemplate.xlsm

Work Order Material Requirements

Supply Chain Planning Work OrderComponent Demands

ScpWIPComponentDemandsImportTemplate.xlsm

Work Order Resource Requirements

Supply Chain Planning Work OrderOperation Resources

ScpWIPOperationResourceImportTemplate.xlsm







Key Customer Options

Supply Chain Planning Key CustomerOptions

ScpKeyCustomerOptionsImportTemplate.xlsm



49

Run the Load Planning Data from Files ProcessTo load planning data from les, rst you must prepare the data you want to load. To prepare the data, download therelevant XLSM template, update the XLSM template with required data, and create the necessary CSV les for upload.This procedure explains how to load planning data from les after you have prepared the data and created CSV les.

1. From the Navigator, use the File Import and Export page to upload the previously prepared and zipped CSVles to the Universal Content Manager. Use the account scm/planningDataLoader/Import to upload the zippedle.

Note: For more information about uploading les to the Universal Content Manager server,see the following section in the Oracle SCM Cloud Implementing Common Features forOracle SCM Cloud guide: External Integration chapter, External Data Integration Services forOracle Cloud section.

2. From one of the Supply Chain Planning work areas or Setup and Maintenance work area, Supply ChainPlanning oering, select the Load Planning Data from Files task.

3. Complete the following parameters on the Load Planning Data from Files page:

a. Select the source system.b. Select Collection Type: Net change or Target.c. Select the .zip le you previously imported into the Universal Content Manager.

4. Click Submit. Make a note of the process ID. You will need this process ID to review the status of the process.

Verify Collection Processes

Verify the Load Planning Data from Files ProcessPerform the following steps to verify the process status of the uploaded le and review log le for any errors orwarnings.

1. In the Navigator, click Scheduled Processes.2. In the search area, enter the process ID you noted when you submied during the Load Planning Data from

Files process. Click Search.3. Monitor the process to verify completion.

If the process completes with warnings, select the request that shows the warning status and click the View Logbuon to review the details.

4. For the rows with errors, resolve the issues found in the log le, and then upload the CSV le again. To loadonly the revised rows, use the Net Change option.

Review Data in the Planning Data RepositoryYou can review the data collected or loaded into the planning data repository using two dierent options. The optionyou use depends on which data collection entities you want to review.



50

To review the data collected or loaded into the planning data repository, use one of the following options:

• Review data using the Plan Inputs page layout

• Review data using the Maintain Supply Network Model page

To review the following entities, use the Maintain Supply Network Model page:

• Organizations

• Customers

• Suppliers

• Carriers

• Interlocation Shipping Networks

To review data that is not part of the supply network model, use the Plan Inputs page layout. You can view the followingdata in the Plan Inputs page layout

• Supply data

• Demand data

You can view Carriers and Suppliers using either option.

Review Data Using the Plan Inputs Page LayoutPerform the following steps to review the planning data that you loaded.

1. In the Navigator, click Plan Inputs.2. From the Plans menu, right-click Plan Inputs and click Open.

Tip: You can set the preview pane to Full Pane for viewing your data in full pane. Click Change andselect Full Pane.

3. On the Plan Inputs page, click Open, and click Full Pane.4. On the Open Table, Graph, or Tile Set page, search for the table name.5. Enter the criteria for the data you want to verify and click Search.6. Review the data in the Search Results table.

Review Data Using the Maintain Supply Network Model PagePerform the following steps to review the planning data using the Maintain Supply Network Model page.

1. In the Navigator, click Plan Inputs.2. From the Tasks menu, click Maintain Supply Network Model.



51

3. Enter the criteria for the data you want to verify and click Search.4. Review the data in the Search Results table.

Aggregate Customer Data

How You Aggregate Customer DataUse the key customer data options collections template to identify key customers. The data for these customerswill be visible. For each Zone, all non-key customers' data will be aggregated to a member named All Other. Byaggregating the planning data for non-key customers, you can focus your analysis on the key customers. You use theScpKeyCustomerOptionsImportTemplate.xlsm to identify the key customers; the rest of the customers' data will beaggregated under an All Other member.

The data that are not identied in the upload template are aggregated to an all other member for each zone. You canview the key customers and the All Other member containing the aggregated non-key customer data when you analyzethe forecasts and other data.

Identifying key customers and aggregating non-key customer data helps you to do the following:

• Organize key customer data that are required for planning

• Save time by collecting only the required data from Oracle Supply Chain Management Cloud

• Build a plan specically for your key customers

How can I reset the key customer aggregated data for a plan?After you make changes to the aggregation level values in the ScpKeyCustomerOptionsImportTemplate.xlsm le, youmust upload the le and run the plan again.

To reset the key customer aggregated data for a plan, do the following:

1. Review the ScpKeyCustomerOptionsImportTemplate.xlsm le.2. Update the Aggregation Level values for all of the Level Name values (for example, Customer) and upload the

CSV le.3. From your Supply Chain Planning work area, open the plan and enable the Aggregate non-key customer data

to All Other level member check box. Run the plan again.

Considerations for Collecting Key Customer InformationUse the ScpKeyCustomerOptionsImportTemplate.xlsm le to identify the key customers for which nonaggregateddata must be made available. For non-key customers, the aggregation level that you dene in the import templatedetermines whether the data is retained or aggregated. You can dierentiate between key customers and non-keycustomers and use the aggregated key customer data to build a plan specically for your key customers.

Note: For details regarding the ScpKeyCustomerOptionsImportTemplate.xlsm le, refer to the File-BasedData Import for Oracle Supply Chain Management Cloud guide. This guide is one of the guides in the OracleHelp Center for Oracle Supply Chain Management Cloud. Use the Books link for a list of the guides bycategory, and look for the Development category.



52

In the ScpKeyCustomerOptionsImportTemplate.xlsm le template:

1. Dene your key customers on the KeyCusOptnHeader tab. Enter the name of a valid customer hierarchy in theHierarchy Name column.

2. Next, enter the level of that hierarchy in the Level Name column. All customers in this level are identied as keycustomers.

3. To have only certain customers identied as key customers, enter the specic customer names on theKeyCusOptnMembers detail tab.

4. Set the aggregation level values for both key and non-key customers. Use the seings in the template to set thedata to dierent aggregation levels, such as 1, 2, or 3.

5. Upload the template.

Ignore Aggregate by ZoneThere are two Customer hierarchies--Customer and Customer Zone--where the lowest level of each hierarchy isCustomer Site. If you don't have any key customers, leave the Hierarchy Name and Hierarchy Level columns blank onthe KeyCusOptnHeader tab. All customers not named in the template (non-key customers) are aggregated into an AllOther member for the hierarchy.

The upload also creates All Other Zone members for the non-key customers in the Customer Zone hierarchy. If youdon't want to aggregate by zone, enter #ignore_zone in the Hierarchy Name column in the KeyCusOptnHeader.csv andleave the Level Name column blank.

Aggregation LevelsThe aggregation levels are listed in the following table.

Aggregation Level Description

1

Retain all customer sites, and aggregate non-key customer sites. In addition to key customerdata being available, non-key customer data is retained for plans that require data that is notaggregated. Aggregated customer data is available for plans that require aggregated non-keycustomer data.

2

Aggregate non-key customer sites. Customers that are not identied as key customers areaggregated to an All Other site by zone. However, if the Hierarchy Name and Level Namecolumns are blank, all customers are identied as non-key customers and aggregated to an AllOther site by zone. This means that there are no key customers.

3

No aggregation of customer sites. All data is available at customer site level.

To remove the key customer designation for previously-loaded customers, use Aggregation Level 3. This enables datafor all customers to be made available at the lowest level. No customers are marked as key customers.

If you select the aggregation level 3, the following happens:

• No aggregation is done. All data is at the customer site level only.

• If option 2 or 3 was used in previous collection runs, all non-key customer by zone members and data aredeleted.

• Plans using the Key Customer feature become invalid and you have to run them again.



53

The KeyCusOptnMembers detail tab is optional. Use this tab to identify specic customers as key customers.The Hierarchy Name and Level Name column entries must be the same as the information entered on theKeyCusOptnHeader tab. Enter valid level member names in the Level Member Name column. These members are theonly customers that will be identied as key customers.

• If the KeyCusOptnMembers detail tab is empty, all child members of the hierarchy level chosen in the Headertab are agged as key customers.

• If the KeyCusOptnMembers detail tab is not empty, only the listed members are identied as key customers.

The members must be children of the hierarchy level named on the Header tab.

When you create a plan, there is an option in the Plan Options dialog box that determines what level of customeraggregation is used for the plan:

• Key customer data is available and non-key customer data is aggregated to a level member named All Other.

• No customer data is aggregated for the plan if the option is deselected.

Load Aggregated Customer Data from Oracle E-Business SuiteThis topic explains the procedure you follow to load aggregated customer data from an Oracle E-Business Suite sourcesystem into your Oracle Supply Chain Planning Cloud destination system.

The procedure is comprised of the following steps:

1. Extract data from your Oracle E-Business Suite source system.2. Prepare the Supply Chain Planning Key Customer Options le if you have dened key customers in your Oracle

E-Business Suite source system.3. Add the les to your desktop or local hard drive.4. Import data into your Oracle Supply Chain Planning Cloud destination system.

Additional details for each step are provided in this topic.

PrerequisitesTo perform the process required to extract data from your Oracle E-Business Suite source system, you must have anadministrator role (Advanced Planning Administrator or Advanced Supply Chain Planner).

Your source system must be set up as one of the Trading Community Source Systems for Oracle Supply Chain PlanningCloud.

You can perform the steps to import data into your Oracle Supply Chain Planning Cloud destination system from one ofthe Supply Chain Planning work areas. You do not need an administrator role to perform these steps.

Extract DataTo extract the data from your Oracle E-Business Suite source system, run the Extract Data for Oracle Supply ChainPlanning Cloud process.

Consider the following conditions for the MSD_DEM_CUSTOMER aribute when you run the process:

• If the MSD_DEM_CUSTOMER_ATTRIBUTE is set to null, then all sites are extracted.

• If the MSD_DEM_CUSTOMER_ATTRIBUTE is set to none, then all records are aggregated to Default CustomerSite.

• If the MSD_DEM_CUSTOMER_ATTRIBUTE is set to a valid customer aribute, then all sites are extracted.



54

The extracted data is stored in a le in the zipped le format in the middle tier of your source system.

Prepare the Key Customer Options FileIf you have dened key customers in your Oracle E-Business Suite source system, then perform these steps to preparethe Supply Chain Planning Key Customer Option le:

1. Download the template for le-based data loads for the Supply Chain Planning Key Customer Options object.2. Add your data to the le.3. Generate the CSV le.

For details on preparing les for loading planning data, refer to these help topics: Loading Planning Data from Files:Overview and Creating CSV Files Used to Load Planning Data: Procedure.

Add the Files to Your Desktop or Local Hard DriveLocate the extracted Zip le on your Oracle E-Business Suite middle tier, and download or transfer the le to yourdesktop or local hard drive.

If you have dened key customers in the Oracle E-Business Suites source system, then include the Key CustomerOptions le in the Zip le.

Import Data into Your Oracle Supply Chain Planning Cloud Destination SystemTo import the data into your Oracle Supply Chain Planning Cloud destination system, perform these steps:

1. From the Navigator, click File Import and Export.2. On the File Import and Export page, perform the upload action using these values:

◦ File: The le you created

◦ Account: scm/planning DataLoader/Import

3. From one of the Supply Chain Planning work areas, perform the Manage Planning Source Systems task tocheck if your source system is already created. If your source system is not already created, then create it withthe following values:

◦ Version: External.

◦ Code: Must be the same as the one used for your Oracle E-Business Suite source system.

4. From a Supply Chain Planning work area, perform the Load Planning Data from Files task.


Chapter 4Planning Analytics

55

4 Planning Analytics

Overview of Planning AnalyticsConguring planning dimensions and hierarchies on the Congure Planning Analytics page is a key setup to use theanalytics in Supply Chain Planning work areas. It has a unied dimensional hierarchy for various uses. Depending onyour security privilege, you can also open the Congure Planning Analytics page from the Setup and Maintenance workarea by selecting the following:



• Task: Congure Planning Analytics

To run plans successfully, you must complete the following Congure Planning Analytics tasks:

• Set Up Dimension Catalogs

• Set Up Measure Catalogs

• Set Up Levels and Aributes

You can use the default hierarchies for most of the dimensions.

If the default product catalog named Product is not collected, then you must select at least one product hierarchy. If adefault product catalog is collected, then the predened Product hierarchy is selected as a product hierarchy by default.You can optionally add or change the product hierarchy. You must include at least one product hierarchy when creatinga dimension catalog.

On the Congure Planning Analytics page, Levels and Aributes tab, you can congure your planning table and graphsto display descriptions instead of codes for the following entities: Items, Organizations, Resource, Work Center, andWork Area.

Congure Planning AnalyticsTo run plans successfully, you must set up dimensions and dimension catalogs, measure catalogs, and levels andaributes. You can open the Congure Planning Analytics task from one of the Supply Chain Planning work areas.Depending on your security privilege, you can also open the Congure Planning Analytics page from the Setup andMaintenance work area.

Note: Default Catalog is the name of the predened dimension catalog. It contains predened hierarchies.Oracle recommends that you make a copy of the Default Catalog if changes are required, instead of editingthe default catalog.



56

To congure planning analytics:

1. In the Navigator, click one of the Supply Chain Planning work areas or click the Setup and Maintenance workarea.

◦ If you clicked one of the Supply Chain Planning work areas, do the following:

i. Click the Tasks panel tab.ii. In the Tasks panel drawer, click the Congure Planning Analytics link.

◦ If you clicked the Setup and Maintenance work area, select the following:

• Oering: Supply Chain Planning• Functional Area: Supply Chain Planning Conguration• Task: Congure Planning Analytics

2. On the Congure Planning Analytics page, Dimension Catalogs tab, do the following:

a. Create a dimension catalog using the Add Row buon, or duplicate the default dimension catalog usingthe Duplicate buon.

b. Specify what hierarchies to use in the dimension catalog by moving hierarchies from the Available paneto the Selected pane.

c. Assign the dimension catalog to a plan that will use the set of hierarchies for analysis during the plancreation from Manage Plans.

3. Each Supply Chain Planning work area has a default measure catalog. Create a new measure catalog to add orremove measures.

a. Use the Add Row buon to create a new catalog or use the Duplicate buon to duplicate an existingcatalog.

b. Specify the measures for the catalog by moving the measures from the Available pane to the Selectedpane.

c. Assign the measure catalog to a plan that will use the set of measures during the plan creation fromManage Plans.

After you create and dene a measure catalog, you can select the measure catalog for a plan from the Edit PlanOptions page.

4. Click the Levels and Aributes tab and select the desired dimension and hierarchy.

a. In the Dimension list, select a dimension.b. Optionally, in the Hierarchy list, select a hierarchy.c. Click the Search icon buon.d. To change how the level name appears in pivot tables and graphs, select the row and enter the level

name in the Level Name to Display eld.

Note: You can't edit the Level Name to Display eld for the lowest level of thehierarchy.

e. To display a particular member identier in your tables and graphs, select a dimension (Product,Organization, or Resource) and level, and then select a value in the Member Identier to Displaycolumn:



57

Dimension Level Member Identier to DisplayOptions

Product

Item

Item Name, Item Description, ItemName and Description, or ItemDescription and Name

Organization

Organization

Organization Name or OrganizationCode

Resource

Resource

Resource Code, Resource Name, orResource Description

Resource

Work Center

Work Center Code, Work Center Name,or Work Center Description

Resource

Work Area

Work Area Code, Work Area Name, orWork Area Description

Resource

Organization

Organization Name or OrganizationCode

Tip: The organization level in the Organization dimension and the organization level inthe Resource dimension are separate seings. Oracle recommends that you set them touse the same identier.

f. To add an aribute for the lowest level of the hierarchy, click the Edit Page buon in the Aributescolumn.

i. In the Manage Aribute List dialog box, click the Add Row buon.ii. In the Aribute list, select an aribute.

iii. In the Aribute Label text box, enter a label name and click OK.5. On the Congure Analytics page, click the Save and Close buon.

Dimensions and Dimension Catalogs

How You Use Dimensions and Dimension Catalogs in SupplyChain PlanningOracle Fusion Supply Chain Planning has hierarchy levels by which you can view, compare, and analyze demands andsupplies of your products over various dimensions, such as geography and organizations. Supply Chain Planning uses asingle set of dimensions and hierarchies to drive aggregation context for demand planning, supply planning, embeddedanalytics, and management analytics.



58

Supply Chain Planning provides predened planning dimensions. Each of those dimensions has a predened hierarchy.When you implement the Supply Chain Planning oering, you must decide which dimensions and hierarchies to use fordemand and supply analysis.

Each dimension catalog has a collection of hierarchies in dierent dimensions that is enabled for use in the planoptions. By default, all predened hierarchies are available in Planning Analytics. You can disable certain dimensionsthat are not relevant for your plans. For example:

• If you are only using demand plans, then supplier, resource, and order type dimensions may not be relevant

• If you are using sales and operations plans, then the order type dimension is not relevant

The following hierarchies are predened in Supply Chain Planning:

• Customer

• Demand Class

• Exception Type

• Order Type

• Organization

• Plan

• Product

• Resource

• Supplier

• Source

• Time

Access the Congure Planning Analytics page from a Supply Chain Planning work area. Depending on your securityprivilege, you can also open the Congure Planning Analytics page from the Setup and Maintenance work area.

• To access the Congure Planning Analytics page from a Supply Chain Planning work area:

a. Click the Tasks panel tab.b. In the Tasks panel drawer, click the Congure Planning Analytics link

• To access the Congure Planning Analytics page from the Setup and Maintenance work area, select thefollowing:



◦ Task: Congure Planning Analytics

In the Dimension Catalogs tab, several hierarchies are available in various dimensions. You can specify which hierarchyto use in a particular dimension catalog. For example, you can select an organization type hierarchy, a product typehierarchy, or a customer hierarchy to use in plans for analysis. After you dene a dimension catalog, you can assign it toa plan that will use the set of hierarchies for analysis.

You can select one of your dimension catalogs to be used as the default dimension catalog in plans. If you do not selecta default catalog, the predened catalog named Default Catalog is used.

Related Topics• Why You Disable or Enable Dimensions for Supply Plan Measures

http://www.oracle.com/pls/topic/lookup?ctx=fa20b&id=758E1AADE7685557E053A398F70A6829



59

Considerations for Seing Up Dimension CatalogsSupply Chain Planning provides predened planning dimensions and each of those dimensions have predenedhierarchies. The predened hierarchies are included in the default dimension catalog and are available in all plans.

Hierarchy Selections for the Product DimensionA predened Product hierarchy is included in the default dimension. The default Product hierarchy has three xedlevels: Item, Category 1, and Category 2. Other Product hierarchies (other item catalogs in Oracle Fusion Product Modelthat are collected into Supply Chain Planning work areas) can be optionally enabled as user-dened product hierarchies.

For Oracle Fusion Sales and Operations Planning, the Lifecycle Phase aribute is also included in the default dimension.

By default, Oracle Fusion Product Model's planning functional area catalog is collected into the Product hierarchy.For the collection to run successfully, you must create the planning functional area catalog in Product Model with thefollowing aributes:

• Controlled at = Master-Level (not Org-Level)

• Allow hierarchy of categories = No

• Default category must be selected

• Allow multiple item category assignments = Not selected

• Catalog Content = Items at Leaf Level

If this catalog is not set up with these aributes, the planning functional area catalog is not collected and the Producthierarchy will not be populated. This will result in the forecasting engine not being able to use the product aggregationand some of the predened tables and graphs will not work correctly.

Hierarchy Selections for the Organization DimensionEnterprise is the default organization hierarchy and has three xed levels: Organization, Business Unit, and Legal Entity.This default organization is dened in Oracle Fusion HCM and you can only modify it there. Optionally, you can enableother Organization hierarchies (based on regions, one per country).

Hierarchy Selections for the Customer DimensionThe default Customer hierarchy has three xed levels: Customer site, Customer, and Customer Class. This defaultcustomer hierarchy is dened in the trading community model and you can only modify it there.

Hierarchy Selections for the Resource DimensionThe default Resource hierarchy has four xed levels: Resource, Work Center, Work Area, and Organization. This defaultresource hierarchy is dened in Oracle Fusion Manufacturing and you cannot modify it.

Hierarchy Selections for the Supplier dimensionThe default Supplier hierarchy has two xed levels: Supplier Site and Supplier.

Hierarchy Selections for the Exception Type, Order Type, and Source DimensionsPredened Exception Type, Order Type, and Source dimensions are included in the Default dimension catalog. Each hasonly a single hierarchy with a single level.



60

Hierarchy Selections for the Time DimensionIn the Time dimension, Gregorian calendar is the only predened hierarchy. All other hierarchies can be optionallyincluded as user-dened hierarchies. These include workday calendars of inventory organizations collected from OracleFusion Supply Chain Management and scal calendars from Oracle Fusion Financials.

Related Topics

• Why You Disable or Enable Dimensions for Supply Plan Measures

What's a dimension in Supply Chain Planning?A dimension is a structure that organizes data. It categorizes data to enable you to answer business questions.Commonly used dimensions are customers, products, and time.

How can I use dimensions in Supply Chain Planning?Supply Chain Planning applications come with predened hierarchies in the Product dimension. These predenedhierarchies are part of the Dimension catalog structure in Oracle Fusion Product Model. Integrations with Oracle E-Business Suite and third-party systems where the product dimensions can still be maintained and uploaded for use bythe Oracle Supply Chain Planning Cloud applications is supported.

What's a dimension catalog in Supply Chain Planning?In Supply Chain Planning, a dimension catalog is a selected list of dimensions enabled for use in plans. In Supply ChainPlanning, a dimension catalog is a selected list of hierarchies in dierent dimensions that is enabled for use in plans.The Default dimension catalog appears by default, but can be changed to another dimension catalog that has beendened.

Can I modify the default dimension catalog?Yes, you can modify the Supply Chain Planning default dimension catalog. However, if you want to make any changes,Oracle recommends that you create a duplicate of the default dimension catalog.

Measure Catalogs

How You Use Measure Catalogs in Supply Chain PlanningThe measure catalog is similar to the dimension catalog. Each measure catalog has a collection of measures that youcan enable for use in plans in one of the Supply Chain Planning work areas. While Oracle provides predened measures,you can also create measures in some work areas and add them to a measure catalog.

http://www.oracle.com/pls/topic/lookup?ctx=fa20b&id=758E1AADE7685557E053A398F70A6829



61

On the Congure Planning Analytics page, Measure Catalogs tab, you can create a measure catalog and add or removemeasures from a measure catalog.

The predened measure catalog is the default. When you create a new plan, the measure catalog that is used is basedon the catalog check box located on the Measure Catalogs tab. For example, the catalog check box in the:

• Planning Central work area is Planning Central Catalog

• Sales and Operations Planning work area is Sales and Operations Planning Catalog

• Demand Management work area is Demand Management Catalog

• Supply Planning work area is Supply Planning Catalog

If you change the default catalog later, the plan continues to use the same measure catalog that it was created with.

Can I modify the default measure catalog?No. Although you cannot modify the default measure catalog, you can create a measure catalog, modify the list ofmeasures, and assign it to plans on the Plan Options page.

Levels and Aributes

How You Use Levels and Aributes in Supply Chain PlanningOn the Levels and Aributes tab, you can enable certain item and organization aributes (standard elds or exelds) tobe available in Planning Analytics as lters. For example, you can enable PLANNER_CODE to use in an analysis to groupmetrics and measures by that particular aribute.

You can create a display name to use in the various pivot tables and graph congurations. For example, if thepredened level name is Product Category 2, you can enter a display name of Laptops. You can also congure whichidentier to display in tables and graphs for selected hierarchies. For example, you can choose to display item name oritem description in your tables and graphs.

Displaying Descriptions in Tables and GraphsYou can analyze planning data in planning tables and graphs by using the description elds of entities in hierarchies,such as items and organizations. You can use the description elds when their primary identier is a dicult tounderstand alphanumeric code. You can toggle between the code and description, or display both, in planning tablesand graphs for the following entities:

• Items

• Organizations

• Resources

• Work Centers

• Work Areas

Tip: The organization level in the Organization dimension and the organization level in the Resourcedimension are separate seings. Oracle recommends that you set them to use the same identier.



62

Changing a member identier can impact the advanced criteria in tables and graphs. If you use an advanced ltercriteria in a table or graph, then the criteria will be compared to the new member identier, which can aect the searchresults. The change to the member identier can result in dierent or no members meeting the lter criteria. Forexample, many names might start with AB, but no descriptions start with AB. After you make this change, you shouldverify that any advanced lter criteria used are still valid.

Note: In the Selector Tool, the member values displayed are based on what is congured in the MemberIdentier to Display column on the Congure Planning Analytics page, Levels and Aributes tab. For example,for item, you can congure your tables and graphs to show item description instead of item name, which iswhat also appears when you are in the Selector Tool.


Glossary

63

Glossarydimension

A data category used to organize business data for retrieval and preservation of values. Dimensions usually containhierarchies of related members grouped within them. A dimension categorizes and describes measure data. Forexample, a measure named Price might be categorized by Product and Time, so that the price of items can be trackedover time.

measure

Contains data that is organized by the measure's dimensions. For example, measures named Price and Forecast withthe dimensions Product and Time would contain price data and forecast data for each product and time period.

planning data repository

The set of data collected from source systems and stored for use by order management, order promising, and supplychain planning processes.


Glossary

64

planning implementing supply chain - oracle...oracle scm cloud implementing supply chain planning...

Documents