This chapter covers the following topics:
Use Bill Presentment Architecture (BPA) to customize the content and format of billing data that your customers view online or print.
BPA provides the architecture to retrieve billing data from multiple sources, including transaction flexfields and other data not interfaced and stored in Oracle Receivables. Because bill presentment is not limited to transaction accounting information, you can present bills that are more comprehensive and meaningful to your customers.
With BPA, you first indicate the data sources that you want to collect billing data from. BPA provides a framework for collecting billing data stored in:
Oracle Receivables
Oracle applications seeded in BPA, such as Oracle Order Management and Oracle Service Contracts
Other Oracle applications
Legacy systems and other non-Oracle applications
You then design billing templates for each transaction class, choosing the layout and content to determine how you want billing data to appear in an online or printed bill, and assign the templates to customers or customer categories. You can print bills individually or in batches from your billing templates created within BPA or uploaded from external sources.
Customizing the bills that your customers see helps them reconcile bills with purchase requests and facilitates timely bill payment.
Your customers can view summarized billing information and drill down using hyperlinks to detailed billing information and other related details necessary to understand and pay the bill.
Related Topics
Bill Presentment Architecture Process Flow
Implementing Bill Presentment Architecture
With Bill Presentment Architecture (BPA), you can customize the content and format of bills to be viewed online or printed by your customers and your internal users.
You can:
Design layout and select content for a bill
Display on bills information that is not stored in Oracle Receivables
Create hyperlinks that enable access to related billing information
Display summary and child lines
Provide online drilldown to transaction line details
Upload external templates
Incorporate attachments on online bills
Assign bill formats to specific customers or user-defined customer categories
Print transactions and bills
Preview billing templates using real-time data
You accomplish this by first configuring the BPA architecture, and then defining templates and assignment rules.
Your system administrator sets up the data sources, views, content items, and hyperlinks to be used in template design.
To enable access from an online bill to supporting information from Receivables, supplementary data source, or web page, add hyperlinks to content items in the templates that you define.
BPA collects, formats, and presents billing data online and in printed bills, according to templates that you define.
A template defines the content areas and content items of a bill. Each data attribute on a bill is a content item. You specify the content items that appear in each content area of a template. For example, you can specify that the bill-to address appears in the upper left corner of the bill. A template also determines the placement and format of the content items.
You can design new templates, use the default templates provided with BPA, upload external templates, or modify templates to suit your company or customer business needs. Using the desktop icons, you can easily create or modify templates graphically. Content areas can be split into as many areas as needed to create the desired layout. Content areas can be moved, duplicated, formatted, updated, or deleted.
When you create or customize templates, you design the layout and contents of a primary bill page and, if needed, a details page. The primary bill page has three content areas:
Header: This area includes information typically seen at the top of an invoice, such as the company's logo, transaction number, date, customer name, bill-to address, ship-to address, and terms.
Lines and Tax: This area contains the billing items, and can optionally include tax, for all transactions included in the bill. This section typically includes the item number, item description, quantities, and cost amounts.
Footer: This area includes information typically available at the bottom of an invoice, such as the total for the bill, aging, additional notes to the customer, and other messages.
You can create a details page for a template if your supplementary data source has a registered details page view. The details page contains supporting billing information from your supplementary data source such as Oracle Service Contracts. See: Details Page Design.
Note: After creating your billing template, you can preview and print it using actual customer data.
See: Template Management.
BPA assigns completed billing templates to customers based on the assignment rules that you define. Each rule uses predefined criteria with user-defined conditional values to match templates with customers.
When a user selects a bill to view or print, BPA applies the online or printed rules, in the order you specify, to determine which template to use.
For example, you can define a rule to use a template to display bills that are more than $10,000. Then, define a second rule to use a different template to display bills that are $10,000 or less.
You can assign different templates to be used for online bills and printed bills. You can also specify different rule order for online and printed bills.
See: Assigning Templates.
Related Topics
Working with Bill Presentment Architecture
Implementing Bill Presentment Architecture
Before you begin working with Bill Presentment Architecture (BPA), gather the requirements for your templates and determine if you need to set up any additional data sources.
How many templates do you require to satisfy your customers' needs?
Do you need different templates for online bills and printed bills?
Do you need different templates for each transaction class you use?
Can you modify seeded templates to meet your requirements, or will you need to design new templates?
Do you want to upload external templates to format printed bills?
What content items do you need for each template? Organize the layout for the primary page, and details page if used, and determine the content items for each of the following content areas: Header, Lines and Tax, Footer, and Details.
Will any bill information come from an application other than Oracle Receivables and the seeded applications in BPA? If yes, then you must register the applications as data sources, synchronize flexfield content items, register data source views, and enable these new data sources.
Do you need to set up hyperlinks?
Will you allow online access to attachments? Do you want to enable your customers to update attachments? Will you allow printing of attachments?
What assignment rules do you need to filter and match a template with appropriate customers or transactions?
After you respond to these questions, you can begin implementing BPA. Refer to the steps in the table below to help guide your implementation.
| Step | Performed by | Task | Required? |
|---|---|---|---|
| Step 1 | System Administrator | Create internal and external users and assign BPA responsibilities. See: Oracle Applications System Administrator's Guide. | Yes |
| Step 2 | System Administrator | Add BPA Transaction Print Program to Oracle Receivables responsibilities. See: Bill Presentment All Request Group. | Required if printing BPA transactions from Oracle Receivables |
| Step 3 | Application Developer | Register Attachment Categories. | Optional. Default is Miscellaneous. |
| Step 4 | System Administrator | Set HZ: Enable DQM Party Search profile option. See: Oracle Bill Presentment Architecture Profile Options. | Optional. Only if you want to do DQM search using customer name. |
| Step 5 | System Administrator | Set AR: BPA Detail Access Enabled profile option to Yes to enable access to details page of an online bill. See: Oracle Bill Presentment Architecture Profile Options. | Optional. Default is Yes. |
| Step 6 | System Administrator | Set AR: BPA Attachment Update Enabled profile option to enable users to update attachments on an online bill. See: Oracle Bill Presentment Architecture Profile Options. | Optional. Default is No. |
| Step 7 | System Administrator | Set AR: BPA Print Attachment Category profile option to print PDF attachments while printing bills. See: Oracle Bill Presentment Architecture Profile Options. | Optional. BPA will not print attachments unless you set this profile option. |
| Step 8 | System Administrator | Set grouping attribute in Receivables. | Required if you want to use default BPA contract template to view OKS invoices. |
| Step 9 | System Administrator | Run Generate Stylesheet for BPA Templates concurrent program. See: Generating Stylesheets. | Required |
| Step 10 | System Administrator | Register data sources. | Required for all nonseeded data sources. |
| Step 11 | System Administrator | Synchronize flexfield content items. | Required if you use transaction flexfields. |
| Step 12 | System Administrator | Enable Assignment Attributes. | Required if you want to designate content items as template assignment attributes. |
| Step 13 | System Administrator | Create database views. | Optional |
| Step 14 | System Administrator | Register data source views. | Optional |
| Step 15 | System Administrator | Enable data sources. | Required if you use supplementary data sources. |
| Step 16 | System Administrator | Configure hyperlinks. | Optional |
| Step 17 | Billing or accounting staff | Create custom content items. | Optional |
Related Topics
Working with Bill Presentment Architecture
Bill Presentment Architecture Process Flow
Use attachment categories to organize attachments. The default category is Miscellaneous. Register additional document categories that are specific to Bill Presentment Architecture (BPA).
To add additional categories for attachments, log in using the Application Developer responsibility and navigate to Attachment Functions.
Query:
Function Name: ARBPA_TM_REAL_PREVIEW
User Name: Bill Management: Real Preview
Click Category and search and select a category.
Note: For information about working with categories, see: Overview of Attachments, Oracle Applications Developer's Guide.
You can set up BPA profile options using the System Administrator responsibility in Oracle Receivables.
Setting the BPA profile options is discussed in detail under Oracle Bill Presentment Architecture Profile Options.
If you use Oracle Service Contracts (OKS) as a supplementary data source and want to display grouped transaction lines that originate in that application, then you must set the INTERFACE_LINE_ATTRIBUTE1 column as AutoInvoice optional grouping attribute in Oracle Receivables.
OKS passes the contract number to Receivables using this attribute. See: Using Grouping Rules to Create Transactions, Oracle Receivables User Guide.
Related Topics
Working with Bill Presentment Architecture
Implementing Bill Presentment Architecture
When you install Bill Presentment Architecture (BPA), you must run the Generate Stylesheet for BPA Templates concurrent program in order to be able to print transactions and bills. This program generates an XSL stylesheet (.xsl-fo file format) for all seeded templates. XML Publisher uses the stylesheet to format templates for printing.
When you create a new template and set the status to Complete, BPA automatically runs this program for you, to create the required stylesheets. Implementation is the only time you must run the program manually. See Bill Presentment All Request Group.
Note: If you want to use the new swan interface for an old template, you need to Incomplete and Complete your templates again.
Related Topics
Working with Bill Presentment Architecture
Implementing Bill Presentment Architecture
To make content items and hyperlinks available for your template designers to include in a template, you must register and enable the supplementary data source where the content items reside.
Oracle Receivables and Oracle Receivables Balance Forward are already registered as primary data sources in Bill Presentment Architecture (BPA) and enabled for use. Oracle Receivables primary data source provides transactional billing data. Use the Oracle Receivables Balance Forward primary data source to provide consolidated billing information for a template. All other data sources are supplementary data sources. Currently, BPA only supports registering supplementary data source for Oracle Receivables. Other Oracle applications, such as Oracle Order Management and Oracle Service Contracts, are registered in BPA, but you must first enable them for use.
If you want to use an application or other source that is not seeded in BPA as a source of content items, then you must register and enable the source as a data source. You can register any application that interfaces billing transactions to Receivables. Applications that can be registered include Oracle applications, third party applications, and legacy systems.
If you want a template to include a details page, then you must register a supplementary data source and register a details page view to provide content items. For more information on registering data source view see: Registering Data Source Views. Only supplementary data sources associated with Oracle Receivables templates can be registered in BPA.
Note: Templates for balance forward bills cannot have a supplementary data source. For more information on entering details for consolidated bills, see: Balance Forward Billing Templates.
When you register a data source, you provide the following:
Data Source Name
Data Source Description
Data Source Level
Interface Context
Prerequisite
Define context field values for line transaction flexfield segments. You specify an interface context for transaction flexfield segments using the Application Developer responsibility. See: Oracle E-Business Suite Developer's Guide.
When you register a data source, you select the interface context for the data source that you want to register.
All transactions imported into Receivables via AutoInvoice have an interface context. The interface context is the context field value for the transaction flexfield in the source application. A source application, such as Oracle Order Management, uses the interface context to identify each transaction.
BPA uses the interface context to synchronize the transaction flexfield. See: Synchronizing Flexfield Content Items.
Note: A Bill Presentment Architecture (BPA) template with a supplementary data source displays only those transactions, which have the same interface context as the supplementary data source.
For more information about transaction flexfields and the interface context, see: Transaction Flexfields, Oracle Receivables User Guide.
After you enable a data source, you can:
Use the data source as a source of content items when defining templates
Assign templates based on that data source to rules in Template Assignment
Create hyperlinks by selecting transaction attributes from the data source.
To change the status of a data source, select a data source from the list of registered data sources. From the list of values, select Mark as Enabled and click Go. After a data source is enabled, you can view its details, but you cannot make any changes.
Note: The primary data sources will always appear enabled. Oracle Order Management and Oracle Service Contracts must be enabled before you can use them as supplementary data sources.
You can disable a data source at any time, with the exception of Oracle Receivables and Oracle Receivables Balance Forward. You cannot disable these data sources because they provide the basic transaction line billing information for Bill Presentment Architecture.
You can update, synchronize flexfields, and delete a data source only if its status is disabled. You can also view disabled data sources.
Warning: Do not disable a data source while creating or updating a template, or while assigning templates to rules.
You can view the following information about a data source by clicking on the data source name:
The name, description, and interface context for the data source.
Each view registered for the data source, including the technical view name and the area where the view can be displayed.
The templates that currently use content items from the data source.
When viewing a data source, you can sort its associated views by clicking on a column heading. You can also drill down to view the details of the associated views, including the database view name and the content items for the view.
If you want to display transaction flexfields on a bill, then you must synchronize the transaction flexfield column information with Receivables transaction information. You can do this before or after you register views from the data source, but only if the status of the data source is disabled. To synchronize, select the content items to be available in Template Management.
Note: You do not have to synchronize the flexfield content items for the supplementary data source, Oracle Order Management. Content items from this seeded application have already been synchronized with Receivables.
For Oracle Service Contracts, only some content items have been synchronized. You can synchronize additional flexfield content items from this supplementary data source if you want to add them to a template.
You can unsynchronize flexfield content items that are not used in a template. Content items used in a template are grayed out. To unsynchronize a content item used in a template, you must first remove the item from the template and disable its data source.
Prerequisites
For each content item, BPA displays the column name, item name, and item display label. The template item column lets you to select the content items to include in your custom data source view.
Note: You can select the content items in Balance Forward Header view as both template items and assignment attributes.
BPA creates a default description for each content item using the format <Data Source Name>-Flexfield-<Item Name>. For example, the default description for the Amount content item is:
Oracle Service Contracts-Flexfield-Amount
This indicates the data source of the content item and identifies the item as a flexfield content item.
You can change the item display label on this page or in the Update Properties page.
From the Configuration tab, you can designate content items from the Oracle Receivables Invoice Header View, Balance Forward Header View or the header level flexfield synchronization for supplementary data sources as template assignment attributes by checking the corresponding check box. To make a content item unavailable as a template assignment attribute uncheck it. Items currently in use as template assignment attribute in rules will have grayed check boxes and cannot be updated.
Related Topics
Working with Bill Presentment Architecture
Implementing Bill Presentment Architecture
To obtain billing data from a source other than the seeded ones, you must first register the application (or other source) as a new data source in Bill Presentment Architecture (BPA).
See: Registering Data Sources.
After registering new data sources, you must complete your BPA configuration by creating any specific database views required, and then registering those views as data source views in BPA. This lets you access additional billing information from the new data sources.
Some database views from Oracle Receivables and seeded applications, such as Oracle Service Contracts and Oracle Order Management, are seeded as data source views in BPA. You can create other database views for these applications to provide any additional data required, but you must then register them as data source views in BPA.
You can create as many views as you need for the Header and Footer display area. The Lines and Tax display area and the Details Page display area may each have only one view.
Tip: When creating a database view, consider the type of information that you want the bill to display. When you later register the view in BPA, carefully set up the parameters so that the view will retrieve the correct information that you want the bill to display.
For example, suppose you create a view that will retrieve additional information for display on a bill. When you register the view in BPA, you might enter Transaction Number as the value for the Transaction Attribute parameter to successfully return the additional information. See: Selecting Parameters.
Create database views using a SQL query in the APPS schema.
If you create a new database view to supply content items for the Lines and Tax area of a billing template, then you must use the following SQL template to create the view.
Note: If you create a new database view for the Header and Footer or Details Page display areas, do not use this template. Create a SQL statement that will create a view for your requirements.
This template creates a view with the Receivables columns in the sequence required to display billing lines in the Lines and Tax area. The view must include all columns from CUSTOMER_TRX_ID to INTERFACE_LINE_ATTRIBUTE15. You can add additional columns at the end of the query.
Use the following SQL statement to create a new database view:
CREATE OR REPLACE FORCE VIEW <User created line view name> as SELECT
lines.customer_trx_id customer_trx_id,
lines.customer_trx_line_id customer_trx_line_id,
to_char(lines.line_number) line_number,
lines.line_type line_type,
nvl(AR_INVOICE_SQL_FUNC_PUB.get_description(lines.customer_trx_line_id ),
lines.description) description,
to_char(nvl(lines.quantity_invoiced, lines.quantity_credited)) quantity,
uom.unit_of_measure unit_of_measure_name,
to_char(nvl(lines.unit_selling_price,0),fnd_currency.get_format_mask
(trx.invoice_currency_code,40))
unit_price,
to_char(lines.extended_amount,fnd_currency.get_format_mask
(trx.invoice_currency_code,40))
extended_amount,
lines.sales_order,
lines.uom_code,
trx.trx_number,
AR_INVOICE_SQL_FUNC_PUB.GET_taxyn (lines.customer_trx_line_id)
tax_exists_for_this_line_flag,
AR_BPA_UTILS_PKG.FN_GET_LINE_TAXRATE(lines.customer_trx_line_id) line_tax_rate,
AR_BPA_UTILS_PKG.FN_GET_LINE_TAXCODE(lines.customer_trx_line_id) tax_code,
AR_BPA_UTILS_PKG.FN_GET_LINE_TAXNAME(lines.customer_trx_line_id) printed_tax_name,
lines.interface_line_attribute1,
lines.interface_line_attribute2,
lines.interface_line_attribute3,
lines.interface_line_attribute4,
lines.interface_line_attribute5,
lines.interface_line_attribute6,
lines.interface_line_attribute7,
lines.interface_line_attribute8,
lines.interface_line_attribute9,
lines.interface_line_attribute10,
lines.interface_line_attribute11,
lines.interface_line_attribute12,
lines.interface_line_attribute13,
lines.interface_line_attribute14,
lines.interface_line_attribute15,
to_char(nvl(lines.unit_selling_price,0)) unformatted_unit_price,
lines.ATTRIBUTE1,
lines.ATTRIBUTE2,
lines.ATTRIBUTE3,
lines.ATTRIBUTE4,
lines.ATTRIBUTE5,
lines.ATTRIBUTE6,
lines.ATTRIBUTE7,
lines.ATTRIBUTE8,
lines.ATTRIBUTE9,
lines.ATTRIBUTE10,
lines.ATTRIBUTE11,
lines.ATTRIBUTE12,
lines.ATTRIBUTE13,
lines.ATTRIBUTE14,
lines.ATTRIBUTE15,
lines.SET_OF_BOOKS_ID,
lines.REASON_CODE,
lines.QUANTITY_ORDERED,
lines.QUANTITY_CREDITED,
lines.UNIT_STANDARD_PRICE,
lines.SALES_ORDER_LINE,
lines.SALES_ORDER_DATE,
lines.ACCOUNTING_RULE_DURATION,
lines.ATTRIBUTE_CATEGORY,
lines.RULE_START_DATE,
lines.INTERFACE_LINE_CONTEXT,
lines.SALES_ORDER_SOURCE,
lines.REVENUE_AMOUNT,
lines.DEFAULT_USSGL_TRANSACTION_CODE,
lines.DEFAULT_USSGL_TRX_CODE_CONTEXT,
lines.LAST_PERIOD_TO_CREDIT,
lines.ITEM_CONTEXT,
lines.TAX_EXEMPT_FLAG,
lines.TAX_EXEMPT_NUMBER,
lines.TAX_EXEMPT_REASON_CODE,
lines.TAX_VENDOR_RETURN_CODE,
lines.GLOBAL_ATTRIBUTE_CATEGORY,
lines.GROSS_UNIT_SELLING_PRICE,
lines.GROSS_EXTENDED_AMOUNT,
lines.EXTENDED_ACCTD_AMOUNT,
lines.MRC_EXTENDED_ACCTD_AMOUNT,
lines.ORG_ID,
lines.GLOBAL_ATTRIBUTE1,
lines.GLOBAL_ATTRIBUTE2,
lines.GLOBAL_ATTRIBUTE3,
lines.GLOBAL_ATTRIBUTE4,
lines.GLOBAL_ATTRIBUTE5,
lines.GLOBAL_ATTRIBUTE6,
lines.GLOBAL_ATTRIBUTE7,
lines.GLOBAL_ATTRIBUTE8,
lines.GLOBAL_ATTRIBUTE9,
lines.GLOBAL_ATTRIBUTE10,
lines.GLOBAL_ATTRIBUTE11,
lines.GLOBAL_ATTRIBUTE12,
lines.GLOBAL_ATTRIBUTE13,
lines.GLOBAL_ATTRIBUTE14,
lines.GLOBAL_ATTRIBUTE15,
lines.GLOBAL_ATTRIBUTE16,
lines.GLOBAL_ATTRIBUTE17,
lines.GLOBAL_ATTRIBUTE18,
lines.GLOBAL_ATTRIBUTE19,
lines.GLOBAL_ATTRIBUTE20,
<Additional line column>,
< >
< >
FROM
mtl_units_of_measure uom,
ra_customer_trx_lines lines,
ra_customer_trx trx,
<Additional join table>
WHERE
trx.customer_trx_id = lines.customer_trx_id
AND trx.complete_flag = 'Y'
AND lines.uom_code = uom.uom_code(+)
and lines.line_type ='LINE'
and <Additional join condition>,
and < >
Related Topics
Working with Bill Presentment Architecture
Implementing Bill Presentment Architecture
When you register a data source view, you specify the content items that will be available for a specific display area of a bill. You must register views if you:
Register a new data source for use with Bill Presentment Architecture (BPA)
Want to use additional views in existing data sources as a source of content items
Before you can register a view, the status of the data source must be disabled.
To register a data source view:
Select a display area for the view
Select a database view
Note: BPA supports registration of one Lines and Tax data source view, one Details Page data source view, and multiple Header and Footer data source views.
Select the content items to be available for creating templates
Prerequisites
To register a data source view for a data source, first identify the display area for the view, and click Register.
Then, use the search function to find the database view that you want to use as a source for content items. For each view, enter a description and display name for the view. Create a display name that easily identifies the source of the content items that can be selected from the view. Later, the template designer selects content items based on this view's display name.
You can set parameters to retrieve specific values from the view when a bill is displayed at run time.
Select either Fixed Value or Transaction Attribute as a parameter type and click Go. Then select a database column and enter a value for this parameter. You can repeat the above steps to add more parameters.
For example, to have a view retrieve information associated with a particular customer, you can select the Fixed Value parameter type and the BILL_TO_CUSTOMER_NAME database column, and then enter the specific company name as the parameter value.
Or, to have a view retrieve information related to a transaction, you can select the Transaction Attribute parameter type and the CUSTOMER_TRX_ID database column, and then select the Transaction ID transaction attribute as the parameter value.
For the Header and Footer, and Lines and Tax display areas, the available list of values for the Transaction Attribute parameter type includes all content items in the Invoice Header view of the Oracle Receivables data source, except for these attributes:
Formatted Bill-To Address
Formatted Remit-To Address
Formatted Ship-To Address
Outstanding Balance with Tokens
See: Oracle Receivables Content Items.
For the Details Page display area, the available list of values for Transaction Attribute parameter type includes:
All content items in the Billing Lines view of the Oracle Receivables data source
All content items in the Billing Lines view of the supplementary data source that you are creating the view for.
Important: Ensure that you select proper parameters so that your registered views for the Header and Footer display area return only one row at run time. Even if a view returns multiple rows, the bill will display only the first row.
From the list of columns in the Content Items section, select the columns that you want to be available as content items during template design.
You can select or deselect column names only if the data source for the view is disabled. The Oracle Receivables data source, however, is always enabled because it provides transaction information to BPA. You can access views and update content items even though this data source is enabled.
If a column name is already used as a content item in an existing template, then the check box is grayed out. To make the content item unavailable for template design, you must first delete the content item from all templates that use the content item. You can then deselect the column.
For each column, you can modify the default item name and item display label. BPA creates a description for each content item, using the following format:
Content item description = data source name-view display name-item name
The description appears in Template Management. It may be helpful to design a naming convention for data sources, views, and content items that easily identifies these components for your billing personnel.
Note: The Item Display Label can also be modified in Template Management. See: Updating Properties.
If you checked the Assignment Attribute checkbox against a content item from the Primary Data Source or header level flexfield content items from supplementary data source, it will be available as a template assignment attribute while creating template assignment rules.
Related Topics
Working with Bill Presentment Architecture
Implementing Bill Presentment Architecture
You can view the content items that are available for a view in the View page. First, open the View Data Source page by selecting a data source name. Then select the view display name to open the View page. This page lists all items available in a view. Items are shown as:
Used in templates: Item is checked and check box is grayed out.
Available for use in templates: Item is checked and check box is active.
Not available: Item is not checked.
You can also access the View page by clicking the Views icon.
Related Topics
Working with Bill Presentment Architecture
Implementing Bill Presentment Architecture
The system administrator creates the hyperlinks that are available for a template designer to associate with content items in a template. These hyperlinks are the hyperlink addresses for the HTML pages that you can link to from an online bill.
Give a name and description to each hyperlink. Pick a name for the hyperlink that easily identifies the hyperlink for the template designer. For example, if you create the hyperlink that links to your company home page, then you could provide a name such as Company Home Page.
Enter the URL address. At run time, Bill Presentment Architecture (BPA) will automatically add the server name and port number to the beginning of the address.
If the hyperlink is linked to another Oracle application, you don't have to enter the full address. Otherwise, you must enter the full address.
You can also enter parameters for the hyperlink address.
To add a fixed value parameter, such as country=us click Add Another Row under Fixed Values. Enter the name and value for the parameter.
To select a transaction attribute, specify a data source level, data source and view. Click Add Another Row and search for the attribute you want to add. Select the Encrypt check box if you want to prevent external users from accessing to your internal web pages.
For information on associating hyperlinks to content items, see: Updating Properties.
Warning: If you associate a hyperlink to the Item Description content item in the Lines and Tax area, then you will override the default links that BPA automatically provides. The links from grouped transaction lines to transaction lines and from transaction lines to transaction details will no longer be functional.
Note: You can associate a hyperlink with a transaction attribute only to a content item of the same data source view. Hyperlinks with fixed value parameters, however, can be associated with any content item.
BPA provides four seeded hyperlinks that you can associate with content items:
Oracle Header Level Sales Order link
Oracle Lines Level Sales Order link
Oracle Applied Transaction Number link
Oracle Transaction Number Link
Related Topics