Scribd
Upload
234 views22 pages

BPA Customization Migration Document

The document discusses customizing invoice reports in Oracle Receivables. It provides steps to create a new data source view to display additional columns, register the view, create a customized invoice template assigning the new data source, and configure the template properties and assignment rules. It also describes automatically populating a transaction identifier field using a sequence to trigger the customized template.

Uploaded by

rktadi
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
234 views22 pages

BPA Customization Migration Document

The document discusses customizing invoice reports in Oracle Receivables. It provides steps to create a new data source view to display additional columns, register the view, create a customized invoice template assigning the new data source, and configure the template properties and assignment rules. It also describes automatically populating a transaction identifier field using a sequence to trigger the customized template.

Uploaded by

rktadi
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 22

OS658 BPA Customization

Requirement: Go to Receivables Responsibility.


Select Transactions
Again Select Transactions
Now Query for a particular transaction number.
When we click on the search button next to the transaction number
It generates an Invoice report
In the Invoice report, we have to add two columns: Item Number
Line Number

And if the Transaction DFF (DFF Context Field) is populated, then only the
customizations should be in effect else it should display the Standard template

And this Transaction DFF should get populated automatically. (Still User should be
able to enter it manually or modify the value that has come automatically)

Functional Overview of BPA


Bill Presentment Architecture is a responsibility that provides a customized invoice
requested by customers due to Government policies or tax deduction norm. Usually
customers request their vendors to develop invoices in various formats, they do not
agree with the standard format already present in Oracle Application.

Bill Presentment architecture is a responsibility that develops template based


configuration of bills for online presentation and printing. Earlier in Release 11i
people used to develop customized invoices with the help of forms and reports, any
other tools or using the same responsibility however due to lack of supplementary
data source it was restricted to the Receivables only.

Now in R12 there are three more responsibilities involved as supplementary in it i.e.
Oracle Order Management and Oracle Projects. Additionally transaction sources also
available for creating templates.

In R12 to develop customized bill, it has become simple by creating templates and
assigning the same to a particular customer. There are five steps to complete the
template creation procedure where we need to define Header, Lines and Tax and
Footer of the bill. In Line and Tax, Item description option is required, rest of the
fields are optional as per the requirement of the customer. There are again various
layouts available to create template and print it as per the size of the paper. If you
don’t want to create various new templates, then you can copy an existing template
modify it and assign the same as per the requirement. We can have one more option
to upload the external files and printed bills instead of creating a new template;
however uploaded bill will not be able to update.
Prior to the release of Bill Presentment Architecture (BPA), Oracle Receivables
seeded document printing programs such as Invoice or Statement print which provided a
rigid structure of output that you could not change. If you needed to make modifications
to the layout or data in the Invoice, you would have to write a custom program to replace
the seeded print program.

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
Following is the sample Bill Layout that can be achieved, it shows:
 Company Logo
 Invoice details such as the Invoice Number, Billing Date, description of the items
being billed for in the invoice
 Option for Special instructions
 Summary of amount to be paid

Solution:

Execute the following View script in apps Schema

arbpa_detailpage_v.
sql

Execute the following sequence in Apps schema.( Purpose to create the sequence: For
the first time when we create transactions, it will take the Transaction Context Type:
<as defined CLAIM>, but after that it will ask us to enter all the other fields too like
Claim Number, Customer reference etc etc as per the Context type specified while
defining, hence this sequence will automatically populate the Claim Number field)

XXHFT_INT_HEADER
_CONTEXT_S.sql

For Customization one can refer Oracle Note: 786553.1


The Customization process is detailed in the screenshots below:

Log into - Bill Presentment Super User

Configuration  Register
Data Source Name: HFT Oracle Receivables
Interface Context: CLAIM

Query for Data source and select Views


Select Display Area as Lines and Tax and click on Register
Add parameter : Transaction Attribute  Go
Give the value as ‘Transaction Id ’ for Attribute Customer_trx_id
The Column Name: CUSTOMER_TRX_ID is the link between standard view and the
view created by us.
Note: if we do not add this Column Name, then in the Invoice Template, it will
display all the records for all the transactions.

Under Content Items, select ‘Segment1’ checkbox.


And Similarly if the customised view has any more additional columns, we need to
select them.
And Click on Finish.
Query for the Data source , select and make it as ‘Mark as Enabled’.
Go to Template Management Tab,
Now select Template Name: Default
Primary Data Source: Oracle Receivables
Transaction Class: Invoice
And click on “Go” then Default Invoice Template from the search results and click
on the duplicate icon for the same in order to duplicate it.

Query for Default Invoice Template and Duplicate it.


Select Supplementary data source that we created earlier.

Query for the created template and select Update.


Under Page lines area, select icon ‘select content’
Select ‘Apply’.

Again under Page lines area select ‘Update Properties’ Icon.


Modify Item display Label and Printed Column width as shown above.
Apply the change.

Next  next  Finish.

Query for the template and mark it as Complete.


Go to Template Assignment tab.
Now Click on “Add Another Row”
And then add the Template Created: HFT Invoice Template
And Give only the From date (Prefer to give any date less than sysdate for testing
purpose)

Select the template that we defined earlier and assign it here and then finish the
changes.

NOTE:
This is only for the Invoice as the Invoice tab is selected
If we want to select the same template for the Credit Memo or the Debit Memo then
we can repeat the same as for the Invoice

Here we can also add the rules to display the designed template using Attribute
Matching Criteria Section
The “Add Attribute” select the limiting parameter to implement the conditional
display of the Template designed.
Form Personalization:

When transaction DFF field gets populated automatically then only run the cutomized
template

Else run the standard template.

Select Receivables Responsibility  Transactions.


10 - Default Interface Header Context for existing Transactions
Trigger event: WHEN-NEW-RECORD-INSTANCE
Trigger object : TGW_HEADER
Condition : :SYSTEM.RECORD_STATUS = 'QUERY'
AND :TGW_HEADER.INTERFACE_HEADER_CONTEXT IS NULL

Actions:

10: Property
Object type: Item
Target Object: TGW_HEADER.INTERFACE_HEADER_CONTEXT
Property name: VALUE
VALUE: CLAIM
20: Property
Object type: Item
Target Object: TGW_HEADER.INTERFACE_HEADER_ATTRIBUTE1
Property name: VALUE
VALUE: = (XXHFT_INT_HEADER_CONTEXT_S.NEXTVAL)

30: BuiltIn
Built Type: execute_trigger
Argument: key-commit.

20 - Default Interface Header Context for New Transactions


Trigger event: WHEN-VALIDATE-RECORD
Trigger object : TGW_HEADER
Condition : :SYSTEM.RECORD_STATUS = 'NEW'

Processing mode: ‘not in enter query mode’


Actions:

10: Property
Object type: Item
Target Object: TGW_HEADER.INTERFACE_HEADER_CONTEXT
Property name: VALUE
VALUE: CLAIM

11: Property
Object type: Item
Target Object: TGW_HEADER.INTERFACE_HEADER_ATTRIBUTE1
Property name: VALUE
VALUE: = (XXHFT_INT_HEADER_CONTEXT_S.NEXTVAL)

You might also like