BICC | BI Cloud Connector | Types of BICC Extract | Roles and Provisions required to access BICC console and UCM | Create your first BICC Extract FULL | Run for Incremental Extracts | Secure your BICC Extracts

BICC is a built in tool to extract data and store the sams data to different storages in the form of CSV file. This extracted data can be transformed and loaded to different warehouse tools for data analysis. The extracted data can be stored in 3 ways as depicted in the diagram.

Types of BICC extracts:

• FULL extract : first to to load full extract
• Incremental extract : daily extract

Roles and Provisions required to access BICC console and UCM:

A. Provisioning a User for BICC console access:

Role code: BIACM_ADMIN

Role Name: BIACM_ADMIN

Role type: BI - Abstract Roles

Roles Hierarchy:

1. ESS Administrator Role(ESSAdmin)

2. Application Implementation Administrator (ORA_ASM_APPLICATION_IMPLEMENTATION_ADMIN_ABSTRACT)

B. provision a user to access BICC content in UCM:

Role code: BICC_UCM_CONTENT_ADMIN

Role name: BICC_UCM_CONTENT_ADMIN

Role Type; BI - Abstract Roles

Roles Hierarchy: 

1. Upload and download data from on-premise system to cloud system(OBIA_EXTRACTTRANSFORMLOAD_RWD)

URLS:

https://<pod>/biacm

https://<pod>/cs

Detailed steps with screenshots:

Or

Create your first BICC Full Extract:

Highlevel steps:

• Create an offering and associate the PVOs to be extracted.
• Create a job and enabled for extract. You can also customize the PVO columns which are required and use filter.
• Create a job schedule to extract the data.

Public View Objects:

1.FscmTopModelAM.FinApInvTransactionsAM.InvoiceHeaderPVO

2.FscmTopModelAM.FinApInvTransactionsAM.InvoiceLinePVO

Detailed steps with screenshots:

Run for Incremental Extracts:

Prune time : In minutes default BICC incremental job will add a look back timeframe as defined in prune time setting. Since the extraction is done on live app db and not on a snapshot, look back or prune time is best practicr to ensure dependency synchronization across objects, Default works best for extracts with daily ot higher reoccurance. Prune time should be adjusted when extracts are scheduled more frequently or if downstream system can handle objects extracted in any order.

Secure BICC extract:

We can create a pgp public and private key and import the public key in the configure External storage UCM data encryption import option that will allow to extract secure gpg key encrypted data which later on we can decrypt with the private / secrect key.

ERP - Lookups in Fusion - Use in ESS Jobs Parameter

Usecase: Here  we will create a lookup and use it as list of values in one paramter of the ESS job.

Highlevel steps:

• Create a lookup XXSOURCE_LOOKUP with lookup codes (search Manage Common Lookup% under setup and maintenance)
• Create a List of values Source COMMON LOOKUP under Manage lisy of values sources (search Manage%Enterprise%Job under setup and maintenance)
• Application name: Application Toolkit
• User List of Values Source Name: Common Lookup
• List of Values Source Def name: oracle.apps.fnd.applcore.lookups.model.publicView.CommonLookupPVO
• Edit the previously created ESS job XXDEMO_JOB and edit paramter Invoice Source as Choice list and select source name as "Common Lookup" with attribute lookup codes.
• Select Invoice Source paramter >> Manage dependencies >>select ByLookupType >> default value : 'XXSOURCE_LOOKUP'
• Test this ess job from scheduled processes.

Detailed steps with screenshots:

Create first ESS job on BI Report | ERP Cloud

Usecase: We will create our first ESS job on BIP report and shedule the ESS job from scheduled processes and track the details from ess_request_history and ess_request_property tables.

Steps with detailed screenshots:

ERP - Secure BI Report

We can provide permissions to specific user to use the report to make it more secure.

Report >> More >> permissions >> add user >> no access to BI admin, BI author and cosumer if needed

Detailed steps with screenshots: