Overview

This Excel template is a tool you can use to create the CSV file for the Load Planning Data from Files task for Fusion Order Pr
Promising searches for supply of an item at an organization.

Preparing the Table Data

1. Prepare the data for each staging table using the corresponding worksheet in this template. See the section Excel Templa
2. Refer to the column headers for detailed instructions on preparing the data in that column, or for descriptions of the data

Loading the Data

After you finish preparing the data in the worksheets of this template, click the Generate CSV File button provided on this w
Create a zip bundle from all CSV files directly. Do not create zip of a folder with all CSV files.
Upload the zip file to the Oracle Universal Content Manager (UCM) server. A valid UCM account must be set up prior to perf
Use the Load Planning Data From Flat Files task to load data from the Oracle UCM server to the planning repository.
For more information on loading data using CSV files, see the documentation provided in the implementation guide regardin
with the Load Interface File for Import scheduled process in Oracle Enterprise Repository for Oracle Fusion Applications.

Generate CSV File

Excel Template Format

• Each staging table is represented as a separate Excel sheet. Do not change the worksheet tab names. Changing the works
• The first ten rows in each sheet contain column headers corresponding to the staging table columns. The columns are in t
Do not change the order of the columns in the Excel sheets. Changing the order of the columns will cause the load proces
You can hide columns that you do not intend to use, but you may not delete columns. Deleting columns will cause the loa
• In each worksheet, the first three rows of column A provide information regarding the respective rows they represent. Th
Oracle Fusion Supply Chain Planning products.
• Review the corresponding rows marked "Name" and "Description" for information on any field. The row marked "Technic
in the planning table. Do not use the technical name to interpret the meaning or function of any field.
• Any column that is marked as Required against a product in the list indicates that the column is mandatory for the corresp
System Code is mandatory for Planning Central.
• You must enter data that conforms to what the control file can accept and process for the associated database column. F
- Date fields must be entered in YYYY/MM/DD format.
- Amount columns must not contain a thousands separator and must use a period (.) as the decimal separator.
- Columns that must be whole numbers have data validation to allow only whole numbers
• Columns have been formatted, where applicable, to match the expected data type to eliminate data entry errors.
• The unique key columns are identified with an asterisk (*) prefixed to the names appearing in the first row of each data sh
• Data to be uploaded starts at row 11. Sample data must be deleted.
Recommendations for Loading Data
Because the details of any data conversion will vary, the scope of this document is limited to a best practices approach. If yo
consulting Oracle resources on open interfaces and the strategies for populating them.

In general, we recommend the following:

1) Build an export file in the same format as described in this template. You can build an export file in one of two ways:
a) Extract data into a spreadsheet that contains the same structure as this template.
b) Use SQL, Oracle Data Integrator, or a similar tool to extract data into a .CSV file with the same structure as the .CSV fil
section entitled Loading the Data).
2) Your spreadsheet must have the same columns, and the columns must be in the same order, as in this template.
3) After you have extracted the data into your temporary spreadsheet, cut and paste the data into the relevant sheets provi
 Oracle Fusion Applications Release 13
Supply Chain Planning Upload: ATP Rules

plate is a tool you can use to create the CSV file for the Load Planning Data from Files task for Fusion Order Promising Available to Promise
ches for supply of an item at an organization.

Table Data
data for each staging table using the corresponding worksheet in this template. See the section Excel Template Format for details about t
column headers for detailed instructions on preparing the data in that column, or for descriptions of the data and data type that the colum

preparing the data in the worksheets of this template, click the Generate CSV File button provided on this worksheet to generate one or m
ndle from all CSV files directly. Do not create zip of a folder with all CSV files.
file to the Oracle Universal Content Manager (UCM) server. A valid UCM account must be set up prior to performing this step.
anning Data From Flat Files task to load data from the Oracle UCM server to the planning repository.
mation on loading data using CSV files, see the documentation provided in the implementation guide regarding flat file upload. This proces
nterface File for Import scheduled process in Oracle Enterprise Repository for Oracle Fusion Applications.

erate CSV File

te Format
table is represented as a separate Excel sheet. Do not change the worksheet tab names. Changing the worksheet tab names will cause the
rows in each sheet contain column headers corresponding to the staging table columns. The columns are in the order that the control file
ge the order of the columns in the Excel sheets. Changing the order of the columns will cause the load process to fail.
columns that you do not intend to use, but you may not delete columns. Deleting columns will cause the load process to fail.
sheet, the first three rows of column A provide information regarding the respective rows they represent. The next six rows of column A li
n Supply Chain Planning products.
orresponding rows marked "Name" and "Description" for information on any field. The row marked "Technical Name" shows the correspo
ng table. Do not use the technical name to interpret the meaning or function of any field.
that is marked as Required against a product in the list indicates that the column is mandatory for the corresponding product. For example
e is mandatory for Planning Central.
ter data that conforms to what the control file can accept and process for the associated database column. For example:
must be entered in YYYY/MM/DD format.
umns must not contain a thousands separator and must use a period (.) as the decimal separator.
at must be whole numbers have data validation to allow only whole numbers
e been formatted, where applicable, to match the expected data type to eliminate data entry errors.
ey columns are identified with an asterisk (*) prefixed to the names appearing in the first row of each data sheet.
ploaded starts at row 11. Sample data must be deleted.
tions for Loading Data
tails of any data conversion will vary, the scope of this document is limited to a best practices approach. If you are new to data conversion
cle resources on open interfaces and the strategies for populating them.

recommend the following:

ort file in the same format as described in this template. You can build an export file in one of two ways:
ata into a spreadsheet that contains the same structure as this template.
Oracle Data Integrator, or a similar tool to extract data into a .CSV file with the same structure as the .CSV file generated by this template
ntitled Loading the Data).
sheet must have the same columns, and the columns must be in the same order, as in this template.
ve extracted the data into your temporary spreadsheet, cut and paste the data into the relevant sheets provided in this template.
Name *Source System Code ATP Time Fence User-Defined ATP Time Fence
Alphanumeric code used Basis used to define the Value specified by the user
to identify the source available to promise time fence. when the basis for the ATP
system. Valid values are: Time Fence is user-defined lead
NULL time.
1 - Total lead time
2 - Cumulative manufacturing
lead time
3 - Cumulative total lead time
4 - User-defined lead time

Description
Data Type Character(30) Number Number
Global Order Promising Required Conditional
Planning Central NA NA NA
S&OP
Demand Planning
Supply Planning
Reserved for Future Use
Technical Name SR_INSTANCE_CODE ATP_TIME_FENCE ATP_TIME_FENCE_UD
EXT 1
EXT 2
EXT 3
EXT 4 10
Profitable to Promise Indicator
Indicates if Global Order Promising uses
the Profitable to Promise feature,
resulting in order promising from lowest
cost sources. Valid values are Yes, No.
Character(3)
NA
PROFITABLE_TO_PROMISE_CODE
Yes
Yes
No
Supply Chain Search Indicator Make CTP Enabled Indicator
Indicates if supply chain search is Indicates if make CTP is enabled. If
enabled. If enabled, Global Order No, make CTP calculations are not
Promising looks at the availability of performed. Valid values are Yes, No.
material and resources during
promising. Valid values are Yes, No.
Only one promising mode can be
specified: Supply Chain Search
Indicator, Lead Time Indicator, or
Infinite Available Indicator. If more
than one promising mode is specified,
the record errors out.
Character(3) Character(3)
Conditional
NA NA
SUPPLY_CHAIN_SEARCH_CODE SEARCH_COMPONENTS_CODE
Yes Yes
Yes Yes
Yes Yes
Yes No
Include Planned Supply
Indicates if planned order supply
needs to be considered during
promising. Include planned supply
is applicable only when supply
chain search indicator is Yes. Valid
values are Yes, No.
Lead Time Indicator
Indicates if lead time based promising is enabled. If enabled,
Global Order Promising does not perform any availability search,
but promises an order from current date by offsetting the specified
lead time after considering various calendars. Valid values are Yes,
No.
Only one promising mode can be specified: Supply Chain Search
Indicator, Lead Time Indicator, or Infinite Available Indicator. If
more than one promising mode is specified, the record errors out.

Character(3) Character(3)
Conditional Conditional
NA NA

INCLUDE_PLANNED_SUPPLY LEAD_TIME_CODE
Yes No
Yes No
No No
Yes No

Lead Time Type
Indicates the lead time that needs to be
considered for lead time based promising. Valid
values are:
NULL
1 - Total lead time
2 - Cumulative manufacturing lead time
3 - Cumulative total lead time
4 - User-defined lead time
User-Defined Lead Time
Days Allocated ATP Indicator
Value specified by the user Indicates if supply allocations
when Lead Time Type is 4 are considered or not. If Yes,
(User-defined lead time) then Global Order Promising
to indicate the number of enforces promises based on
days for the lead time off supply allocations. Valid
set. values are Yes, No.

Number Number Character(3)

Conditional Conditional
NA NA NA

LEAD_TIME_TYPE LEAD_TIME_DAYS_UD ALLOCATED_ATP_CODE

Yes
Yes
Yes
Yes
*ATP Rule Name Description
Unique identifier Description for the ATP rule.
for the ATP rule.
Past Due Demand Cutoff Fence
Indicates the past due time fence specified in
days for demands. Only the past due
demands figuring in the specified number of
days before horizon start date will be
considered in Global Order Promising. Only
applicable in the supply chain search
promising mode.

Character(80) Character(240) Number

Required Conditional
NA NA NA

RULE_NAME DESCRIPTION PAST_DUE_DEMAND_CUTOFF_FENCE

ATP-RULE1 ATP Rule Type1 15
ATP-RULE2 ATP Rule Type2 12
ATP-RULE3 ATP Rule Type3 20
ATP-RULE4 ATP Rule Type4 15
Past Due Supply Cutoff Fence
Indicates the past due time fence specified
in days for supplies. Only the past due
supplies figuring in the specified number of
days before horizon start date will be
considered in Global Order Promising. Only
applicable in the supply chain search
promising mode.
Infinite Available Indicator Infinite Supply Fence Code
Indicates if infinite promising Indicates the lead time to be
mode is enabled. If enabled, considered for calculating infinite
Global Order Promising does not supply time fence. Valid values are:
perform any availability search NULL
but promises orders based on 1 - Total lead time
infinite supply availability. Valid2 - Cumulative manufacturing lead
values are Yes, No. time
3 - Cumulative total lead time
Only one promising mode can be 4 - User-defined lead time
specified: Supply Chain Search
Indicator, Lead Time Indicator, or
Infinite Available Indicator. If
more than one promising mode is
specified, the record errors out.

Number Character(3) Number

Conditional Conditional Conditional
NA NA NA

PAST_DUE_SUPPLY_CUTOFF_FENCE INFINITE_AVAILABLE_CODE INFINITE_SUPPLY_FENCE_CODE

3 No 1
5 No 2
5 No 3
2 No 4
User-Defined Infinite Supply Time Fence
Value specified by the user when Infinite
Supply Fence Code is 4 (User-defined lead
time) to indicate the number of days for
the lead time off set.
Include Sales Orders
Indicates if Global Order
Promising must consider sales
orders in demand calculations
(supply and demand netting).
Only applicable for supply
chain search promising mode.
Valid values are Yes, No.
Include Discrete WIP Demand
Indicates if discrete WIP demand will be
considered during promising. Valid values
are Yes, No.
Only applicable in the supply chain search
promising mode.

Number Character(3) Character(3)

Conditional Conditional Conditional
NA NA NA

INFINITE_SUPPLY_TIME_FENCE_UD INCLUDE_SALES_ORDERS INCLUDE_DISCRETE_WIP_DEMAND

Yes Yes
Yes No
Yes No
7 Yes Yes
Include Dependent WIP Demand Include User-Defined Demand
Indicates if dependent WIP demand will be Indicates if user-defined demand will be
considered during promising. Valid values are considered during promising. Valid values
Yes, No. are Yes, No.

Only applicable in the supply chain search Only applicable in the supply chain search
promising mode. promising mode.

Character(3) Character(3)
Conditional Conditional
NA NA

INCLUDE_DEPENDENT_WIP_DEMAND INCLUDE_USER_DEFINED_DEMAND
Yes Yes
No Yes
No Yes
No Yes
Include Purchase Orders Include Discrete WIP Receipts
Indicates if purchase orders will be Indicates if discrete WIP receipts will be
considered during promising. Valid considered during promising. Valid values
values are Yes, No. are Yes, No.

Only applicable in the supply chain Only applicable in the supply chain search
search promising mode. promising mode.

Character(4) Character(3)
Conditional Conditional
NA NA

INCLUDE_PURCHASE_ORDERS INCLUDE_DISCRETE_WIP_RECEIPTS
Yes Yes
No Yes
No No
No Yes
Include Nonstandard WIP Receipts Include Interorganization Transfers
Indicates if nonstandard WIP receipts will Indicates if interorganizations transfers
be considered during promising. Valid will be considered during promising.
values are Yes, No. Valid values are Yes, No.

Only applicable in the supply chain search Only applicable in the supply chain
promising mode. search promising mode.

Character(3) Character(3)
Conditional Conditional
NA NA

INCLUDE_NONSTD_WIP_RECEIPTS INCLUDE_INTERORG_TRANSFERS
Yes Yes
No No
No No
Yes No
Include On-Hand Available
Indicates if on-hand supply will be
considered during promising. Valid
values are Yes, No.
Only applicable in the supply chain
search promising mode.
Include User-Defined Supply Include Requisition
Indicates if user-defined supply will be Indicates if requisitions will
considered during promising. Valid be considered during
values are Yes, No. promising. Valid values are
Yes, No.
Only applicable in the supply chain
search promising mode. Only applicable in the
supply chain search
promising mode.

Character(3) Character(3) Character(3)

Conditional Conditional Conditional
NA NA NA

INCLUDE_ONHAND_AVAILABLE INCLUDE_USER_DEFINED_SUPPLY INCLUDE_REQUISITION

Yes Yes Yes
Yes Yes No
Yes Yes No
Yes Yes No
Include Internal Requisitions Delete Indicator Truncate fulfillment quantity
Indicates if internal requisitions Indicates whether Indicates to truncate order
will be considered during the row is no fulfillment quantity to nearest
promising. Valid values are Yes, longer valid. If integer.
No. Yes, then this row
is deleted from Valid values are Yes, No.
Only applicable in the supply the planning Default value is No.
chain search promising mode. table. Valid values
are Yes, No.
Default value is
No.

Character(3) Character(3) Character(3)

Conditional
NA NA NA

INCLUDE_INTERNAL_REQS DELETED_FLAG IS_INDIVISIBLE

Yes No No
No No No
No No No
No No No
Name *Source System Code *ATP Rule Name *Assignment Type
Alphanumeric code used Unique identifier for Numeric code to
to identify the source the ATP rule. identify the assignment
system. type. Valid values are:
2 - Category
3 - Item
4 - Organization
5 - Item and
organization

Description
Data Type Character(30) Character(80) Number
Global Order Promising Required Required Required
Planning Central NA NA NA
S&OP
Demand Planning
Supply Planning
Reserved for Future Use
Technical Name SR_INSTANCE_CODE ATP_RULE_NAME ASSIGNMENT_TYPE
EXT ATP-RULE1 2
EXT ATP-RULE2 3
EXT ATP-RULE3 4
EXT ATP-RULE4 5
*Category Name *Organization Code
Category to which the Short alphanumeric code to
ATP rule is being identify an organization to
assigned. which the ATP rule is
associated.
*Item Name Deleted Indicator
Item to which Indicates whether
the ATP rule is the row is no
assigned. longer valid. If
Yes, then this row
is deleted from
the planning
table. Valid values
are Yes, No.
Default value is
No.

Character(250) Character(18) Character(300) Character(3)

Conditional Conditional Conditional
NA NA NA NA

CATEGORY_NAME ORGANIZATION_CODE ITEM_NAME DELETED_FLAG

High Value No
AS10000 No
MFG01 No
MFG01 AS10000 No