Hello,

Welcome to installment #1 in my series on loading data to Oracle Planning and Budgeting Cloud Service (PBCS).

In this series I will cover the current Oracle supported methods for loading data and meta data to PBCS.

How do we load data to the cloud?

• We either input data or load a file.

Can we source from a table or view?

• At this time we either input data directly or load a file.

Let me show you the options.

Installment #1 – Smart View to load data and meta data

Installment #2 – Export Data/Meta Data and Import Data/Meta data from the web interface

Installment #3 – FDMEE data loads

Installment #4 – Automated loads

Series 1 – Smart View

Direct loads:
Depending on your application size manual maintenance may be the most efficient.

The Oracle Smart View add-in for MS Excel is an extremely powerful tool for both users and administrators.

Meta Data (Administrators only)

1. Select the dimension(s) to edit

2. Make your updates

Updates:

• Parent/Child layout
• Type or past in member names
• Active drop down menus for selecting member properties

Advantages:

• Move members just by changing the parent in the spreadsheet
• Create alternate hierarchies

Current Smart View limitations (These task can be completed through the web interface):

• Attribute assignment
• Member renaming
• Member deletion

Member Properties drop down menu.

3. Submit the updates to the relational database

4. Don’t forget to refresh the Essbase application

Data (Administrators and Users)

Data can be entered through Forms and Ad hoc connections.

1. Select your vehicle for data entry

Open a Web Form (data entry template)

• Forms may have Business Rules attached to them.  (Be sure  you know your companies business process for data entry)

Or create your own input sheet using Ad hoc analysis.

2. Enter the data

Since this is a planning connection we can enter data and non-numerical data.

3. You need to Submit

This is the end of this installment.

Coming soon:

Installment #2 – Export Data/Meta Data and Import Data/Meta data from the web interface

Installment #3 – FDMEE data loads

Installment #4 – Automated loads

Best Regards,

Scott Williams