Manage Offerings and Data Stores

Manage Offerings and Data Stores-

1) Create Offering – For creating the customized offering

 FscmTopModelAM.FinApInvTransactionsAM.InvoiceHeaderHoldsPVO-
If we are dealing with invoices that are under review or hold, we would reference this PVO to
understand the reasons and status of these holds.
 FscmTopModelAM.FinExtractAM.ApBiccExtractAM.InvoiceHeaderExtractPVO-
When you are extracting invoice data via BICC for external reporting, integration, or data
warehousing purposes.
 FscmTopModelAM.PrjExtractAM.PjbBiccExtractAM.InvoiceHeaderExtractPVO-
When extracting invoice data that is tied to Oracle Projects for reporting or integration purposes
 FscmTopModelAM.FinApInvTransactionsAM.InvoiceHeaderPVO-
This is the core Invoice Header PVO containing the primary invoice header data.

1
 Offering Actions-

Offering Action > Delete Delete the currently selected offering . Available
only for user-defined offerings.

Offering Action > Edit Change the Offering Name and VO association

Offering Action > Reset to Shipped Reset to default configuration of an offering

Offering Action > Reset to Full Reset the last extract date so that a full data
Extract load is performed for the offering

Offering Action > Reset All Data Reset to default configuration of an offering
Stores To Shipped Content removing any changes made for all Data Stores

Reset to Full Extract- For Extracting the full data of particular Data Store(PVO)

Reset To Shipped Content- Reset to default configuration of an offering removing any changes made.

Export Metadata Definition- contains detailed information about the structure and configuration of the data
store (in this case, the InvoiceDistributionExtractPVO data store). Each row in the metadata export

2
corresponds to a column in the data store, providing information about its attributes, types, keys, and
descriptions.

Export Metadata Definition (CSV)- contains same detailed information about the structure and configuration
of the data store but in CSV Format

 File extension: .mdcsv

 Delimiter: ||| (three vertical pipes)

Export UI Label- Exports the UI labels associated with the data store.

Download Sample CSV File- Sample CSV

Advanced Extract Configuration- For Full Extract Only

Filter and/or Chunk By Creation Date Columns

Support chunking- select By Creation Date to chunk by to specify a number of days by which to extract date
range batches or chunks of data

Number of Days- If we selected to support chunking by creation date, specify the number of days, for
example 365, by which to chunk extracts.

Chunk By Primary Key Column

Number of Rows- Specify a number of rows to chunk extracts by.

Extract as String

3
In the Extract as String tab, you can select columns that are of numeric or CLOB data types for conversion.
Select the Cast to String checkbox to extract numeric columns with more than 15 digits and CLOB data types.
This setting trims the CLOB data to the character string limits supported by VARCHAR datatype. This isn't a
data transformation. Data transformations, including data format customizations, aren't supported by BICC.

Manage Extract Mode- extract jobs don't use the BI Server. They interact directly with data stores and the
Cloud Applications source database.

Manage DB Hints - A hint is an instruction to the optimizer.

2) Reset Last Extract Date for All Enabled Data Store- For All Data Store

3)Configure Flex Label Languages- we can specify a language for flex labels.

4
 4)Extract Preferences

Preferred Extract Language- Language Of Extraction

Prune Time- for managing the dependencies of the extracted data

Timeout in Hours- number of hours before a job times out

Timeout Force Fail- Force fully stops the job if the job run time is exceeds the Timeout

Compression type-Zip/GZip

Split file size-1 to 5 GB split the files in mentioned size

Uploaded file expiry -expiry of file where they are uploaded

Upload to multiple External Storage- Enabling the multiple External Storage

5
Connection retry Limit - Defines the number of times a connection retry will be attempted when an initial
attempt to connect to a database or a service fails.

Query retry Limit - Specifies the number of retry attempts allowed for a query execution. If a query fails due
to temporary issues, it will retry according to this limit before the process is considered failed.

DB fetch buffer size - Refers to the size of the buffer that holds data fetched from the database before it is
processed or returned. A larger buffer size can improve performance by reducing the number of round trips
to the database, but it also consumes more memory.

DB fetch row count - Specifies the number of rows fetched at a time from the database.

BI jdbc fetch row count - The BI JDBC Fetch Row Count parameter specifies the number of rows fetched per
batch from a database when executing a query via a JDBC connection in Oracle Analytics.

Global Extract Schedule Notification -To send notifications when scheduled extract events occur

It can be overridden at the schedule level

5)Refresh UCM Encryption Signing Key - need to manually reset at the all external storages

Data Store Details – these details to specify a data store for the selected offering.

6
Query Filter- Enter a filter to restrict the returned data when you run the query.

underscore ( _ )underscore ( _ ) DATASTORE underscore ( _ ) underscore ( _ )dot(.)>BI VO Column Name

__DATASTORE__.ViewApplicationId=0

Data Store Options

Silent Error: errors on a data store that occur during the extract are ignored.

Disable Effective date filter: Select this option to extract all historical records, and not use the date filter.

Extract Data Store Metadata: option generates an .mdcsv file with the data extract.

Use UNION ALL for incremental extract: Enable this if you schedule incremental

7
8