Repeatable, Reliable – FNDLOAD

Susan Behn
Gerald Jones
April 15, 2008
 Agenda

• Business Need
• Migration Alternatives
• Overview of FNDLOAD
• What to Migrate Between Instances
• Data Preservation
• How to Migrate Between Instances
• Configuration Files
• Examples
• Migration Issues
• XDOLoader

2
 Business Need for Data
Migration

• Implementations
– Migrate all setups between Development, multiple test
environments and production
– Migrate application data between instances
• Suppliers
• Inventory Orgs
• Banks
• Change Management
– Migrate selected objects between instances
• New concurrent program
• New form personalizations
• Approvals Management

3
 Migration Alternatives

• Manual
– Data entry errors are a problem
– Time consuming
• 3rd Party Applications
– Expensive
– One more application to maintain
• iSetup
– E-Business suite application tool for functional users
– Recommended for implementation process
– Migrates setups as well as application data such as Suppliers, Inventory
Orgs, etc…
– Limited ability to migrate individual objects –
• Not always ideal for change management
– No data preservation for seeded or more recent data
– No language translation features
– Source and target must be at the same patch set level

4
 Overview of FNDLOAD

• Unix command line tool for developers

– Create unix scripts to streamline
• Good for on-going change management
• Standard “out of the box” Oracle Applications
Functionality
• Use configuration file (.lct) provided by Oracle
– Ensures repeatable process
– FND – Located in $FND_TOP/patch/115/import
– AME/HR – Located in $PER_TOP/patch/115/import
• Optionally create custom configuration files
– Not supported by Oracle

5
 Overview of FNDLOAD

• Text based data files (.ldt) created by

FNDLOAD
• Files transferable to any Oracle Applications
instance
• Source and Target do not have to be at the
same patch level as a general rule
– 10.7
11i would not work due to language
translation tables
• Primarily for configuration data – not
application data
• Data preservation options protect seeded
values 6
 What to Migrate with FNDLOAD

• Concurrent Programs, • Lookup Types

Executables • User Responsibilities
• Request Groups, Request • Printer Definitions
Sets • FND Dictionary
• Profile Options • Help Configuration
• Key and Descriptive • Document Sequences
Flexfields • Concurrent Manager
• Menus and Responsibilities Schedules
• Forms and Form Functions • Forms Personalizations
• Attachments • Approvals Management
Objects
• Messages • Not in iSetup yet
• Value Sets and Values

7
 Additional Objects to Migrate
with iSetup

• Discrete Mfg and • Payroll Elements

Distribution Setups • Product Foundation
• Employees • Profitability Manager
Setups
• Financials Operating
• Suppliers
Units
• Transfer Pricing
• Financials Setups Setups
• GL Daily Rates • XML Publisher
• Organization
Structure
8
 Data Preservation

• OWNER and LAST_UPDATE_DATE ensure

data preservation
– New records are always uploaded
– OWNER=SEED
• Will not overwrite OWNER=CUSTOM
– OWNER=CUSTOM
• Always overwrites OWNER=SEED
– If OWNERS are the same
• Keeps Record with most recent LAST_UPDATE_DATE

9
 How to Migrate Data

• Executable located in $FND_TOP/bin

FNDLOAD <apps/$APPS_PW> 0 Y <Mode>
<Configfile>
<target data file> <entity> <parameter>
– 0 Y = Concurrent Program Flags
– Mode = UPLOAD, UPLOAD_PARTIAL or DOWNLOAD
– Configfile = Configuration file (.lct) provided by Oracle in
$FND_TOP/patch/115/import
– Target Data File = Name of the file (.ldt) to be created by
Download or used by Upload. This file contains the definition of
the entity being migrated.
– Entity = type of object being migrated (printer style, lookup,
executable,…)
– Parameter = parameter related to the entity (Which printer style,
lookup, etc)
10
 Migrate a Single Concurrent
Program

FNDLOAD apps/apps 0 Y DOWNLOAD

$FND_TOP/patch/115/import/afcpprog.lct
mydata.ldt
CONCURRENT_PROGRAM
CONCURRENT_PROGRAM_NAME=‘GLIMP’
– Utilize attributes on the download to limit data in .ldt file
– Downloads concurrent program data for the concurrent
program short name ‘GLIMP’ using the apfcpprog.lct
configuration file into mydata.ldt file
FNDLOAD apps/apps 0 Y UPLOAD
$FND_TOP/patch/115/import/afcpprog.lct
mydata.ldt
– Uploads all the data in mydata.ldt
• In this case, only concurrent program ‘GLIMP” 11
 UPLOAD PARTIAL DATA

FNDLOAD apps/apps 0 Y DOWNLOAD

$FND_TOP/patch/115/import/afcpprog.lct mydata.ldt
APPLICATION_NAME=‘FND’
– Download all concurrent program data for the FND application
into mydata.ldt file
FNDLOAD apps/apps 0 Y UPLOAD_PARTIAL
$FND_TOP/patch/115/import/afcpprog.lct mydata.ldt
CONCURRENT_PROGRAM
CONCURRENT_PROGRAM_NAME=‘GLIMP’
– Utilize attributes on the upload to limit data uploaded from ldt
file that contains multiple records
– Uploads only the data for the concurrent program short name =
‘GLIMP’ from a text file that contains all concurrent programs

12
 Configuration File Layout

• Comments Section
• Define Block
– Specifies structure
DEFINE <entity> KEY <key_attribute_name> <datatype> ...
(BASE|TRANS|CTX) <attribute_name> <datatype> ...
[DEFINE <child_entity> ...]
END <entity>
• Download Block
– SQL Statement containing bind variables to select rows to
download
– Look here for available parameters
• Upload Block
– SQL statement or anonymous PL/SQL block to accept file data
and load it into the database

13
 Configuration File List - FND

• $FND_TOP/patch/115/import
 Configuration File List - FND

• $PER_TOP/patch/115/import
 Configuration File Layout

• Comments Section

16
 Configuration File Layout

• Define Section

17
 Configuration File Layout

• Download Section

18
 Configuration File Layout

• Upload Section
– Typically a pl/sql block

19
 Example – Concurrent
Programs

• Concurrent Programs – afcpprog.lct

• Parameters
– EXECUTABLE_NAME
– APPLICATION_SHORT_NAME
• Entities
– Program
– Incompatibilities
– Executable
– Value Sets, DFFs, KFFs, Security Rules,
etc…referenced by concurrent program

20
 Example – Request Groups

• Request Groups – afcpreqg.lct

• Parameters
– REQUEST_GROUP_NAME
– APPLICATION_SHORT_NAME
• Entities
– Request Group
– Request Group Unit

21
 Example – Profile Options

• Profile Options – afscprof.lct

• Parameters
– PROFILE_NAME
– APPLICATION_SHORT_NAME
– LEV (Site, Responsibility, Application, User)
– LEV_NAME (value of LEV)
• Entities
– Profile
– Profile Option Value
– Profile Category Options and Values
22
 Example – AME

• Transaction Types – amescvar.lct

– Parameters
• APPLICATION_SHORT_NAME
• TRANSACTION_TYPE_ID

• Approver Types – amesapty.lct

– Parameter – ORIG_SYSTEM
• Item Classes – amesicls.lct
– Parameter – ITEM_CLASS_NAME

23
 Example – AME

• Attributes – amesmatt.lct
• Attribute Usages – amesmatr.lct
• Conditions – amesconk.lct
– Parameters for attributes, attributes
usages and conditions
• APPLICATION_SHORT_NAME
• TRANSACTION_TYPE_ID
• ATTRIBUTE_NAME

24
 Example – AME – Approver
Groups

• Approver Group Structure – amesaagc.lct

– Parameters
• APPLICATION_SHORT_NAME
• APPROVAL_GROUP_NAME
• Approver Groups – amesappg.lct
– PARAMETER: APPROVAL_GROUP_NAME
– Dynamic approver groups only; Does not work for static approver
groups.
– Approver group names must not contain spaces.
• Use the % wildcard symbol in between each word of the approver
group if spaces exist
– Parameter for approver group name is required
• Must supply the name of an approver group or some matching
pattern
• Use a common prefix when naming the approver group to make it
easier to download all approver groups
25
 Example – AME – Rules

• Rule Actions – amesactu.lct

– Parameters
• APPLICATION_SHORT_NAME
• TRANSACTION_TYPE_ID
• RULE_KEY
• Rules – amesrulk.lct
– Parameters
• APPLICATION_SHORT_NAME
• TRANSACTION_TYPE_ID
• RULE_KEY
– Includes rules, conditions and rule type
– Use of wildcard symbols such as % are not allowed

26
 Common Issues

• Inconsistent deletion of rows

– FNDLOAD does not always delete rows
• Depends on configuration file
• Request Sets
– FNDLOAD will not delete stages or programs
from request sets when run in UPLOAD mode
• Concurrent Programs
– FNDLOAD will delete parameters when using
force mode

27
 XDOLoader

• Java-based utility to load template files for

XML Publisher
– RTF
– PDF
– XSL-FO
– XML
– XSD
• Includes download and upload utility
• See MetaLink Doc Id: 469585.1

28
 References

• MetaLink Note 274667.1 – Contains

FNDLOAD command syntax
• MetaLink Doc Id: 472248.1 – Contains
details for FNDLOAD options for Approvals
Management
• Oracle Applications System Administrator’s
Guide - Configuration
• Oracle iSetup User Guide

29
 Available at
Got Oracle?
www.solutionbeacon.com Get the Books!
Order or Reserve
Your Copy Today!

Installing, Upgrading and

Maintaining Oracle E- The Release 12 Primer –
Business Suite Applications Shining a Light on the
11.5.10.2+ Release 12 World

The ABCs of Workflow for

Oracle E-Business Suite Release
11i and Release 12
 Oracle Applications Users
Group (OAUG)
• THE world’s largest knowledgebase for Oracle
Applications users

• Networking opportunities with over 118,000

members worldwide

• Access to over 50,000 white papers in the online

OAUG Conference Paper Database

• FREE online training every Tuesday, Wednesday and

Thursday for OAUG members

31
 Questions and Answers

Thank You!
Susan Behn
[email protected]
Gerald Jones
[email protected]

www.solutionbeacon.com
Real Solutions for the Real World ®

Copyright 2008 Solution Beacon, LLC All Rights Reserved Any other commercial
product names herein are trademark, registered trademarks or service marks of 32
their respective owners.