Creating an Analysis Load Format
The Analyses Load Format configuration defines the structure and format of the text or XML file generated for campaign loads and analysis exports.
To create an Analysis Load Format:
-
Navigate to .
-
To create a new record, use the Form Applet.
- Open the Form Applet.Note: The List Applet doesn't allow creation of new records.
- Create a new record.
-
Provide the required field values described in following table.
Field Description Required Values or Format More Information Output Type Specifies the output format for the Analysis Load Format. Yes Select one of the following values:-
Delimiter
-
XML
The supported output type depends on the selected Purpose Type. For Campaign Load, only comma-delimited output is supported. For Analysis Export, delimiter-based output or XML is supported. Name Specifies the name of the Analysis Load Format. Yes Enter a unique name. The name must uniquely identify the Analysis Load Format. Purpose Type Specifies the purpose for which the Analysis Load Format is used. Yes Select one of the following values:-
Campaign Load
-
Analysis Export
Campaign Load supports only comma-delimited CSV output. XML format isn't supported for Campaign Load. Analysis Export supports XML and delimiter-based formats. Text Qualifier Specifies the character used to enclose text values in delimiter-based output files. No Recommended value: double quotation mark ( ")A text qualifier helps preserve commas within field values, handle special characters correctly, and support proper CSV parsing by downstream systems. Max # Records Specifies the maximum number of records written to a single output file. No Enter a numeric threshold value. Use this field to limit file size for server memory optimization, better processing performance, and easier file handling. If no value is specified, the default value is 1000.Header Field Format Defines the Integration Object mapping used by Siebel EAI during data import. Yes Use the following format:
#<Integration_Object_Name>#From the 26.6 release onward, customers must specify the Integration Object name in the header field of the Analysis Load Format. Users no longer need to create a column named -SiebelIOName-..Integration Object Mapping..File Prefix Specifies the prefix for generated files. No Enter a file prefix value. If a file prefix isn't specified, the generated file name starts with the campaign name. - Open the Form Applet.
The following table describes the fields available for configuring an Analysis Load Format
Supported Output Types by Purpose Type
| Purpose Type | Supported Output Type | Notes |
|---|---|---|
| Campaign Load | Comma Delimiter only | Supports only comma-delimited CSV output. XML format isn't supported. |
| Analysis Export | Delimiter or XML | Supports XML and any delimiter-based format. |
Header Field Format Requirements
- Location: Go to the Header field in the Analysis Load Format view.
- Required format: Specify the target Integration
Object using this format:
#<Integration_Object_Name> # - Example:
#Marketing Contact - Usage: Siebel Enterprise Application Integration uses
Integration Objects to load list data directly into transactional tables
such as
S_CAMP_CON.
Important Notes for Header Field Format Requirements
- The Integration Object name must exactly match the configured Siebel Integration Object.
- Don't add extra text, additional spaces, blank lines, or any characters after
the second
#. - Don't press Enter after the second line.
File Naming Convention
Campaign Load File Format
<Prefix>_<CampaignName>_<SegmentId>_<TreatmentId>_<Timestamp>_<FileCounter>.csv
Example:
MKT_SummerCampaign_101_501_20260520_1.csv
Analysis List Export File Format
<Prefix>_<CampaignName>_<ListDistributionId>_<Timestamp>_<FileCounter>.csv
Example:
EXP_CustomerList_2001_20260520_1.csv
XML Configuration
When the Output Type is set to XML, the Form Applet displays
additional fields for XML configuration.
For XML output, configure these properties.
| Property | Description | Default Value |
|---|---|---|
| File Prefix | Prefix added to the generated XML file. | NA |
| XML Rowset Element | Specifies the root XML element name. | rowset |
| XML Row Element Tag | Specifies the XML row element name. | row |
If values aren't provided, the default values rowset and
row are used.
Important Points for XML Analysis Export
- XML output is supported only for the Analysis Export use case.
- The Max Records option is currently not supported for XML output.
- XML file output is supported only under List Distribution.
- Campaign Load doesn't support XML output.
- You can use Siebel attributes like
CampaignId,WaveId, and similar attributes when defining filter criteria in an Analysis within Oracle Analytics Server. However, such analyses are supported only for the Analysis Export use case in List Distribution and aren't supported for other output types.