Skip to main content

Bill Presentment Architecture (BPA) in Oracle Receivables

Oracle Receivables

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.
You need to follow below mentioned steps to implement Bill presentment Architecture –
BPA IMPLEMENTATION
Responsibility:
Bill Presentment Super User, Vision Operations (USA) > Bill Management
Select Create button for creating manual template.
There are 5 steps to create a manual template:
  • Enter Template name and Template description.
  • Enter Transaction class as Invoice, Credit Memo, Debit Memo, Chargeback, Deposit and Guarantee
  • Primary Data Source > Oracle Receivables or Oracle Receivable Balance Forward.
  • Optionally you can select Supplementary Data Source as per the Organization’s need.
  • Tax Format > you can customize the Tax else keep Oracle Receivables Tax printing Option.
Select Next
In primary page design we can enter the information with the help of Header, Lines and Taxes and Footer.
Select content and layout for Header.
Select available contents to add in to the content area. You can select all the available options with the help of Move All items.
Select Billing Lines for Lines and Tax.
Select Content and Layout for Footer
After selecting all of the contents in the line and footer, select the next button for the next step.
Select Next
Print setups are available on the 4th stage, modify it as per your requirement.
Select Next for Preview stage. Here you can view the customized setup of your invoice.
Select Finish, to complete the process.
Once you finish the process, Query the template which you have created and select the Go for Mark as complete.
Here your template will be completed.
Use this template in your existing customers.
Select Interactive.
You have to query e.g.
  • Operating Unit > Vision Operations
  • Customer Name > Hilman and Associates
  • Select > GO
List of invoices will be appeared on the screen.
Select any one of the invoice for Print Preview.
You will be able to view your customized bill in PDF format.You will be able to view your customized bill in PDF format.
You can also download an invoice in external template but it should be in PDF or RTF.
There are four steps to create, the steps are as same as the manual invoice template but there is no Header, Lines, Taxes and Footer.

Comments

Popular posts from this blog

Create Accounting for a Payment generates errors 95333 and 95359

Create Accounting for a Payment generates errors 95333 and 95359 Error: 95333: A conversion rate does not exist to convert USD to AUD for the conversion type Corporate and conversion date 20-MAR-09 for line -25. Please use the Daily Rates form in General Ledger to enter a conversion rate for these currencies, conversion date and conversion type. 95359: There is no accounted amount for the subledger journal entry line. Please inform your system administrator or support representative that: The source assigned to the accounting attribute Accounted Amount has no value for extract line number 88547. Please make sure the source assigned to the accounting attribute Accounted Amount has a valid value, or assign a different source to this accounting attribute. Solution: 1. Specify a conversion rate for the currencies and conversion date mentioned in the error message 95333 Navigation under the General Ledger responsibility: Setup > Currencies > Currency Rates Manager > Daily Rates ...

Public API’s for FA Transactions

Public API’s for FA Transactions So far Oracle FA is have all the good things except the lack on reporting.Oracle FA is now offer lot of public API's that can be used to interfacing with third party or Oracle application other modules. Here are some of transaction's API's:   Additions API if you have requirement to add assets directly via PL/SQL then use  FA_ADDITION_PUB.DO_ADDITION. If you have selected the Allow CIP Assets check box on the Book Controls window of a tax book when adding CIP assets using the Additions API, the this API automatically adds those CIP assets to that tax book at the same time that they are added to the corporate book. Adjustments API you can make cost adjustments to your assetsdirectly via PL/SQL using  FA_ADJUSTMENT_PUB.DO_ADJUSTMENT  for any  process adjustment. Detail can be found in appendix H) You can use this API if you have a custom interface that makes it difficult to use with the existing Oracle Assets interfaces for adjusti...

AP Table Relation Oracle Apps

AP Table Relation Oracle Apps ORACLE PAYABLE TABLE RELATION Source Table Dependent Table Condition AP_INVOICE_LINES_ALL AIL ZX_LINES_SUMMARY ZLS AIL.invoice_id = ZLS.trx_id and  ZLS.application_id  = 200 and  ZLS.entity_code  = 'AP_INVOICES' and  ZLS.event_class_code  in ('STANDARD INVOICES', 'PREPAYMENT INVOICES', 'EXPENSE REPORTS') and  AIL.summary_tax_line_id = ZLS.summary_tax_line_id AP_INVOICE_LINES_ALL AIL ZX_LINES ZL AIL.invoice_id = ZL.trx_id and  ZL.application_id  = 200 and  ZL.entity_code  = 'AP_INVOICES' and  ZL.event_class_code  in ('STANDARD INVOICES', 'PREPAYMENT INVOICES', 'EXPENSE REPORTS') and  AIL.line_number = ZL.trx_line_number AP_INVOICE_DISTRIBUTIONS_ALL AID ZX_REC_NREC_DIST ZD AID.invoice_id = ZD.trx_id and  ZD.application_id  = 200 and  ZD.entity_code  = 'AP_INVOICES' and  ZD.event_class_code  in ('STANDARD INVOICES', 'PREPAYMENT INVOICES', 'EXPENSE REPORTS') and...