R12 - 6 Months

All 6 months have just passed since I had started updating this blog. I am very thankful to all the readers who have visited the blog and gained oracle R12 knowledge. I also specially thank the visitors who had left me comments on my posts. I am planning to spend more time behind the blog than before, so its my request to all visitors to kindly give your comments and suggestions about how you find this blog and the posts. Also let me know how I can improve this blog and what topics actually you like to read in Oracle Release 12. I will definitely try to work on it ! You can also email me at onlyappsr12@gmail.com.

Have a Good Time !!!!!!

R12 Banks and Branches Model

As discussed in earlier post about the new tables in R12 Banks and Branches, today lets go through the internal and external uses of bank accounts. When a bank account is created in Cash Management they are created as Internal bank Accounts, and the bank accounts created using the Supplier form or customer form through are created as External Bank Accounts. To be more specific when the user defines a new bank account using the supplier form the information is stored in the IBY_EXT_BANK_ACCOUNTS and the internal bank accounts are stored in the CE_BANK_ACCOUNT.

The ability to share bank and bank account information between internal bank account definitions from different modules like Payables, Receivables, Treasury, Payroll and Global Financials is provided by Cash Management.

As we know TCA party model is used to model banks and bank branches as parties with the associated Relationships, Address, Contacts and Locations. Cash Management uses the following TCA tables for modeling banks and bank Branches

1) HZ_PARTIES
2) HZ_RELATIONSHIPS
3) HZ_RELATIONSHIP_TYPES
4) HZ_CONTACT_POINTS
5) HZ_PARTY_SITES
6) HZ_LOCATIONS
7) HZ_ORGANIZATION_PROFILES
8) HZ_ORG_CONTACTS
9) HZ_ORG_CONTACT_ROLES

HZ_ORGANIZATION_PROFILES --Stores attributes of banks and bank branches with the history of changes made to banks and bank branches.
HZ_PARTIES -- The contacts of a person at the bank, bank branch and bank account are defined as a party
HZ_CONTACT_POINTS -- Stores the contact details
HZ_ORG_CONTACTS --Stores the contact’s title
HZ_ORG_CONTACT_ROLES --Stores the contact’s purpose or role
HZ_LOCATIONS -- Stores the address details of banks and bank branches
HZ_PARTY_SITES --Stores party sites

CE_GL_ACCOUNTS_CCID -- Stores the accounting data pertaining to the bank account use

The bank, branch and bank account related attributes in AP_BANK_BRANCHES and AP_BANK_ACCOUNTS_ALL tables will be upgraded to HZ_PARTIES and the new tables in Cash Management as mentioned in my earlier post. The new data model allows the bank and bank branch entities to be defined separately allowing users more flexibility and to establish a hierarchical relationship between them.

R12 Bank Data

1.What are the new tables in R12?

The following tables were obsoleted in R12:

AP_BANK_BRANCHES
AP_BANK_ACCOUNTS_ALL
AP_BANK_ACCOUNTS_USES_ALL

The new tables in R12 are now under Cash Management module: Here are the tables

CE_BANK_ACCOUNTS: This table contains Legal Entity Level bank account information. Each bank account must be affiliated with one bank branch.

CE_BANK_ACCT_USES_ALL: This table stores Operating Unit level bank account use information

CE_PAYMENT_DOCUMENTS: This table Payment Documents to be used for Printed type Payments

CE_BANK_BRANCHES_V: view: Bank/Branches Info

CE_BANK_ACCT_USES_OU_V: view: Internal Bank Account Uses Info

The bank setup has been moved from AP to CE module, one should use Cash Management responsibility with all grants and permissions in order to create and maintain bank accounts. All the grants and permissions are done by Sysadmin using User management responsibility.

BI/XML Publisher Notes

Before going into more details of XML Publisher, lets have a look at some of the XML standards.

The XML language specification defines the rules for XML document structure and how XML processors should read the document.

The DTD (document type definition) validates an XML document and provides the relationships of elements contained in the document.

XML Namespaces helps us to distinguish elements with different definitions having same name in the XML document.

The XML Path Language (XPath) provides syntax for searching the XML documents.

The Extensible Style Sheet Language (XSL) uses XSLT (Transformations) to transform an XML document to another document.

An XML Schema describes the XML document structure using DTD and namespaces.

Oracle BI Publisher - OPP (Output Post Processor)

The Output Post Processor (OPP) is mainly used to process post actions of concurrent requests. For instance once the concurrent manager finishes running the concurrent program, it will communicate with OPP to apply the XML Publisher template and create the final output. The services run by OPP are managed through OAM (Oracle Applications Manager). A minimum of one OPP process should always be available in the system to process the concurrent request, otherwise OPP will complete with status WARNING. Depending on the availability the concurrent manager may contact local or remote OPP while running a concurrent request. The OPP service is a multi threaded and initiates a new thread for every concurrent request it processes. We can also view more details of OPP service in OAM. So depending on your work, one can manage the workshifts and the number of threads per process to handle the workload.

Oracle BI Publisher Process Flow

As you have seen a brief introduction to BI/XML Publisher in my last post, today let us see the steps involved in processing a report using BI/XML Publisher.

1.Run the desired concurrent program.
2.The concurrent program calls the data template using the XDO (Extensible
data object) engine.
3.The data template calls the SQL query.
4.The query runs in the database and output is converted to XML.
5.XML output is generated by XML engine.
6.The OPP (Output post processor) formats the output based on the XML Publisher
template you have chosen and creates the final output like pdf, word, excel
and web page.
7.Output delivered to the User.

BI/XML Publisher XDO data engine plays an important role in generating the reports.The XMLP Report business service is the interface to this logical component that initiates the Java services to load the JAR files to the JVM. The Oracle BI Publisher XDO Engine then processes the XML data, XSL template to generate the report. We can also configure the XDO engine to create log files that can capture detail information and errors while generating the reports. The log files are more helpful in determining the cause of problems with the JAR files or the Oracle BI/XML Publisher layout templates.

Oracle BI/XML Publisher

Oracle BI Publisher is a powerful report generation tool. It is a template based publishing tool available with Oracle E-Business suite. The report designing generated is mainly driven by desktop tools and XML technology. Lot of people get confused by the terms BI publisher and XML publisher, but to let you know both are same.The older version was known as XML Publisher, which is now called as BI Publisher.BI Publisher can be used as stand alone product whereas XML Publisher is always included in EBS.

Compared to traditional oracle reports, XML publisher provides output of the
file in various formats like excel, word, pdf and HTML at runtime. The data structure and presentation layer can separated unlike the standard oracle reports where data logic, presentation are in one file.

BI/XML Publisher can be integrated with E-Business suite as:

BI Publisher + Data Templates
BI Publisher + Oracle Reports
BI Publisher + OA Framework

BI/XMl Publisher can be mainly used for types of reports like Invoices,
sales orders, purchase orders, statements, pay slips, financial and business reports.