iSetup – A Guide/Benefit for the Functional User!

1. iSetup – A Guide/Benefit for the Functional User! Mohan Iyer January 17th, 2008

2. iSetup – An Introduction • Migrate Setups • Extract • Transform • Load • (Upload) • Predefined Selection Sets for master setup data • Snapshot of configurations that are downloaded are stored • Data extracts are in XML (in most cases) • Snapshots are transportable • downloadable ZIP files • Then uploaded to another instance • Reporting • Generic listing reports • Comparison reports between two snap-shots

3. iSetup Variations in usage • Single instance mapping • Can be used to extract data and then upload into same instance with changes/transforms • Or download ZIP file to transport and upload in other instance • Not very functional in R11i - not much transformation capability • Very limited use if done this way • Double instance mapping • Have two instance mapping that are created within each instance and you can work on extracts from either instance • Extract and Load data from one to the other without download • Comparison reports between data in both instances possible • Central instance mapping • One instance is a central instance where all mappings are maintained • All extracts and transformation are done in this instance • All reports/comparisons are performed in this central instance • Loads are possible into any one instance from this one central instance

4. AR:Receivables Tax Codes and Rates Accounting Calendars. Bank and Bank Account Chart of Accounts Currencies Customers Daily Rates Discrete Mfg. and Distribution Setups Employees Financials Operating Unit Level Setup General Foundation HR:Organization Structure Setup Oracle Financials Setup Product Foundation Profile Options Set of Books Suppliers Release 11i functionality Many of these have limited transform capability They can be extracted and loaded into another instance You can run reports (including comparison reports) between snapshots

5. Specific, additional - selection sets (data groupings) Australian Leave Liability Payroll Elements Personalizations Profitability Manager Setups Transfer Pricing Setups Workflow Business Event System Objects Workflow Definitions XML Publisher Discontinued Selection Sets Receivables Tax Codes and Rates Customers Discrete Manufacturing & Distribution Setups R12 functionality

6. R12 functionality • Functionality available in R12 • Planned in future (presented at Oracle OpenWorld November 2007) • Selection set taxonomy – additional areas and groupings • Extensibility to create custom selections and sequencing of events/extracts • Cascade transform • Reporting changes/modifications • Layout modifications • BR100 style reports • Preferences support • Extensibility to add loader file types • Register these as external interface elements and report and compare • Cascade OU related setups to create a new snapshot • Cascade transform on specific Setup elements

7. Using iSetup

8. Using iSetup • Before you see the screen in the last slide • You need to create a mapping for the instance • The mapping creation needs the DBC file name to identify the source/target • The DBC file name is something that you will need to get from your DBA

9. Using iSetup • Selection Set • All pre-defined data elements are called Selection Sets and need to be chosen and defined (with filters if need be) before you extract • An extract is based on a selection set • A selection set is pre-defined and there are 17 such selection sets in Release 11i and R12. • Selection set filters need to be specific depending on the data elements • Choose the way to identify these as a group rather than by a specific characteristic in the name • Also, there is by default a Profile Option that does not allow specific choices to be extracted within a selection set. Set this Profile Option to ‘Yes’ to be able to do that • Profile Option Name – “AZ: Partial Selection Set Feature”

10. Selection Sets – with Profile Option set to ‘No’

11. Selection Sets – with Profile Option set to ‘Yes’

12. Using iSetup • Selection sets

13. Using iSetup • Selection sets

14. Using iSetup • Selection sets • You now have filtered data as part of this selection set • The filter is set

15. Using iSetup • Selection sets • You can update existing selection sets once they are created so that they can be re-used

16. Using iSetup • Extract • An extract process will pull data from the instance specified when creating a selection set • The extract is a concurrent program and can be scheduled to run at a later date or immediately • Once the extract is created – the concurrent program completes with the following status’ • Complete successfully • Can complete with an error • Can complete with a warning • You cannot use the extract if it does not complete successfully • The log will show cryptic information about why the process did not succeed • There will be some information about why it failed, and you can research to identify the offending data element

17. Using iSetup • Extract

18. Using iSetup • Extract

19. Using iSetup • After Extract • Once you have extracted data you can do a couple of things • Download • Upload • Transform • Load • You can download the file (ZIP) file to your desktop and transport it to another instance and load it • CAVEAT – The original manual and all documentations says that these two instances have to be on the same patching level and the same version!

20. Using iSetup

21. Using iSetup • Transform

22. Using iSetup • Transform • With the transform function you can actually change some aspects of the data that you have extracted • You can extract Supplier information and change the name of the Supplier • You can download Accounting Calendar Information and change the name of the Accounting Calendar • Only some specific attributes can be changed • Some extracted are not changeable at all • Once the transform is done you can then continue with the load to a specific instance in effect making “Setup Changes”

23. Using iSetup • Transform

24. Using iSetup • Transform

25. Using iSetup • Transform

26. Using iSetup • Transform

27. Using iSetup • Load • You can load the following • Extracts from the existing instance • Extracts you have uploaded from another instance • Extracts that you have transformed • All of these files have to be a specific state before you can load • Transforms have to be frozen • Extracts concurrent programs MUST be completed successfully • Load processes loads the data into the target instance using API’s for each of the products • API’s form each of the products define if they will be transformable or not • Loads normally always replace whatever is available in the tables • So if I loaded the Currencies from one instance to the other they are over-written and a new set of records are in the table

28. Using iSetup • Load

29. Using iSetup • Load

30. Using iSetup • Report (and Comparison Reports) • You can run reports to show what you have extracted • These reports can be viewed on screen • They can also be downloadable to many formats • Comparison Reports • Comparison reports allow you to check data elements between two sources • An extract from one instance to another • These need to be on the same instance for the comparison • The comparison shows data elements that are different between instances

31. Using iSetup • Report

32. Using iSetup • Report

33. Using iSetup • Comparison Report

34. Using iSetup • Comparison Report

35. Gotchas and Like to Have’s • Gotchas • Instance mappings are individual user specific • Need to make sure that when you load you ensure that you want to replace existing records – that is the default • Before you start this exercise need to define the differentiating factor • Supplier Names cannot be the only differentiating factor • Each data element needs to be reviewed in iSetup for the selection before you decide to use this as a means to make changes • Like to see • Capability to move setups between different versions • User defined selection criteria would be a good addition • Transform capability based in user needs would be an even greater help • Capability to extend this to be able to load master data – Suppliers, Customers would be great • Anyone out there has others?????

36. Technical aspects • Patchsets • 11i.AZ.H includes 5140723 • 11I.AZ.H.DELTA.1 includes 5525463 & 5725686 • CONSOLIDATED PATCH FOR THE 5040190 & 5254830 - 5597983 • The following patches are not included in the above patchsets and are needed, use admrgptch to merge them into a single patch • 3994238, 4015970, • 4188534, 4200089, • 4305771, 4449094, • 4453830, 4477329, • 4495836, 4495891, • 4528356, 4548492, • 4557501, 4586690, • 4604050, 4604123, • 4612812, 4628347, • 4636554, 4641008, • 4926690, 5201280, • 5217874 • Patch# 6526775 • Looking for the Transformation Option for the 'Financial Setup OU Level’ • Refer Meta Link Note # 472700.1 (just released)

37. Technical aspects • Other considerations • iSetup uses the Web Server to pass data between database instances. • When you define an instance in iSetup you assign it a name and link the name to a DBC file in the $FND_SECURE directory of the Apps Tier. • Your DBA should be able to provide you with the name of the DBC for each of the instances you want to use iSetup against. You only need the name of the DBC not the actual file contents

38. Next Steps & Contact Information • Mohan Iyer • FSCP Solutions Inc. • mohan@fcpsolutions.com • 408 859 4484 • Board Member • NorCalOAUG • MNSIG