Many of you might have known it earlier, but people who don’t know, setup of Banks are moved into the Cash Management Module. The short name for Cash Management is CE.  In this Article, we will discuss how to Create Banks / Bank Branches , step by step.
Responsibility – Cash Management Super User
Navigation – Setup – Banks – Banks
Clicking on this opens an OAF page
Click on Create – opens the following.
Enter the necessary details required and click Save and Next.
Update the Bank Addresses by clicking on Create
Enter the information and click on Finish
Click on Save and Next
Click on Create Contact .
Enter the necessary information required.
Click Apply once the details are entered.
Click on Finish.  The bank details are here in this screen.
Bank is Created Successfully. Now we will see how to create a Branch underneath the Bank which we just Created.
Click on Create Branch icon
Click on Continue from the below screen
In the below screen enter the Branch Details as shown
Click Save and Next.
Click on Create button in the above screen to add the Branch’s address
Enter the address and then click Apply.
Click Save and Next
Click on Create Contact button to add the Contact Details
Click on Apply
Click on Finish.
To Create Account – click on the Icon below…
Click on Create button from the below screen
Enter the details in the screen below
Click on Continue
Enter the necessary details in the screen above
Click on Next
Click on Save and Next
Retainage refers to a portion of the payment that is withheld until the completion of a project. In that case the client doesn’t pay the contractor/party the retainage until all work on the project is complete. Retainage is negotiated upfront and is stated as a percentage or amount of the overall cost of the project.  There is no limit for Retainage.
Steps Involved in Retainage
1. Create a document style in Oracle Purchasing
2. Create Retainage Account through Payables
Let’s discuss the steps below …
1. Create a document style in Oracle Purchasing.
Responsibility: Purchasing
Navigation:  Setup –  Purchasing – Document Styles  – Create
Click – Create
Click Apply
2. Create a retainage account in Financials Options setup.
Responsibility: Payables
Navigation:  Setup – Options – Financials Options
Enter the retainage account to use during accounting.
Enter the Retainage Account –
  1. Create a procurement purchase order in Oracle Purchasing.
    Responsibility: Purchasing
    Navigation: / Buyer Work Center / Orders
    Select the complex PO document style in the Create drop down box or select ‘More’ to find the complex PO document style if it is not listed in the LOV.
  2.  Create –Choose  Complex PO
Click Go
Enter the Details here
Enter the Header info and click on Lines.
Enter the line information
Click on Update icon to enter the Financing  Options.
Enter the Distributions details
Click Save
Part -I: Online Accounting: (For single entity)

DRAFT will create Journal Entries, which are NOT final, which means they are NOT ready to be transferred to GL.
  • You can see the accounting in XLA_AE_HEADERS and XLA_AE_LINES.

         XLA_AE_HEADERS.accounting_entry_status_code is ‘D’
         XLA_EVENTS.process_status_code is ‘D’
         XLA_EVENTS.event_status_code is ‘U’ 

  • You can run create accounting on this transaction again and again, which will delete the old journal entries and create new ones.
  • You can’t transfer these journal entries to GL.
FINAL will create journal entries, which can be transferred to GL.

  • You can see the accounting in XLA_AE_HEADERS and XLA_AE_LINES.

         XLA_AE_HEADERS.accounting_entry_status_code is ‘F’
         XLA_EVENTS.process_status_code is ‘P’
         XLA_EVENTS.event_status_code is ‘P’

  • Once it is finally accounted you can NOT run create accounting on the particular transaction (specifically on that event).
  • You can transfer them to GL using Transfer Journal Entries to GL program.
FINAL POST will create journal entries in Final Mode, Transfer them to GL and Post them.
  • You can see the accounting in XLA_AE_HEADERS and XLA_AE_LINES.

         XLA_AE_HEADERS.accounting_entry_status_code is ‘F’
         XLA_EVENTS.process_status_code is ‘P’
         XLA_EVENTS.event_status_code is ‘P’

  • Once it is finally accounted you can NOT run create accounting on the particular transaction (specifically on that event).
  • It will transfer the journal entries to GL using Journal Import and you can find the data in GL_JE_HEADERS and GL_JE_LINES.

         XLA_AE_HEADERS.transfer_status_code is Y.
         It will post to gl_balances also (GL_JE_HEADERS.status is ‘P’).

Part -II: Create Accounting (Concurrent Program): (For more entities)

1. Accounting Mode: Draft
It is same as Draft online accounting.

2. Accounting Mode: Final, Transfer to GL: No
It is same as Final online accounting.

3. Accounting Mode: Final, Transfer to GL: Yes, Post to GL: No

  • It will create journal entries in Final mode, transfer them to GL.
  • You can see the accounting in XLA_AE_HEADERS and XLA_AE_LINES.
  • Once it is finally accounted you can NOT run create accounting on the particular transaction (specifically on that event).

         XLA_AE_HEADERS.accounting_entry_status_code is ‘F’
         XLA_EVENTS.process_status_code is ‘P’
         XLA_EVENTS.event_status_code is ‘P’

  • It will transfer the journal entries to GL using Journal Import and you can find the data in GL_JE_HEADERS and GL_JE_LINES.

         XLA_AE_HEADERS.transfer_status_code is ‘Y’
         GL_JE_HEADERS.status is ‘U’.

4. Accounting Mode: Final, Transfer to GL: Yes, Post to GL: Yes


It is same as Final Post online accounting.
Often times, WebADI can be very confusing to work with. There are just too many issues if it is not properly set up. Sometimes you may encounter VBProject Runtime Error when trying to open Web-ADI template file, or sometimes the Excel spreadsheet just hangs up, or can’t be opened.

There are few steps you will have to take before WebADI can be properly used:

  • Microsoft Office Version
  • Microsoft Excel Settings
  • Internet Explorer Settings


Follow the steps below given in the screenshots and apply the settings exactly as they are depicted. The screenshots are from Excel 2010, however the settings should also work for 2000, 2003, 2007 versions.

A)  Check the Microsoft Office Version
Make sure you are using 32-bit version of Microsoft Office. Click on Excel –> File –> Help. If you are running 64-bit version, you may want to uninstall 64-bit and re-install the 32-bit version of Microsoft Office.

B)  Open Microsoft Excel –> File –> Options –> Trust Center –> Trust Center Settings

B-1)  Trusted Documents:
Make sure to check “Allow documents on a network to be trusted“.


B-2)  Add-Ins:
Make sure to uncheck all the options.


B-3)  ActiveX Settings:
Check only “Enable all controls without restrictions and without prompting“. All other options should be unchecked.




B-4)  Macro Settings:

Check “Enable all macros” and “Trust access to the VBA project object model” options.




B-5)  Protected View:

Check only “Enable Protected View for Outlook attachments” and “Enable Data Execution Prevention mode” options. All other options should be unchecked.


In case the WebADI still does not work, then keep all the options unchecked, and retry.

B-6)  Message Bar:

Check “Show the Message Bar in all applications when achieve content, such as ActiveX controls and macros, has been blocked“.




B-7)  External Content:

Check the “Enable all Data Connections” and “Enable automatic update for all Workbook Links” options only.



C)  Internet Explorer Settings:

Open Internet Explorer –> Tools –> Internet Options –> Security Tab –> Custom Level.



C-1)  Downloads

Scroll down to Downloads section, and make sure File Download is Enabled.



C-2)  Miscellaneous: 

Scroll down to Miscellaneous section, and make sure to match the following setting.



C-3)  Scripting: 

Scroll down to Scripting section, and make sure to match the following setting. Then press OK.



Now log out from your Oracle Applications and re-log back in. Retry the Web-ADI upload.

Oracle Apps tables ending with _ALL holds transaction data for multiple org ( Operating Units).

In 11i we had views on these tables. It requires setting context in order to fetch data from these views. This  is for security concerns as these objects holds transaction details.

The SQL command to set the ORG_ID prior to running a script is:

SQL> EXECUTE DBMS_APPLICATION_INFO.SET_CLIENT_INFO(&ORG_ID);

Enter the org_id when prompted.

If using Toad:

BEGIN
     FND_CLIENT_INFO.SET_ORG_CONTEXT (&ORG_ID);
END;   

In R12 oracle uses VPD (Virtual Private Database) to secure these transactional data .This is one of major difference in application architecture between 11i and R12.

In order to retrieve data from transactional objects, set policy context first ( as below ) –

BEGIN
     MO_GLOBAL.SET_POLICY_CONTEXT(‘MODE’ CHAR(1),ORG_ID NUMBER);
END;

    MODE – This is  either “S” – For Single Operating Unit OR “M” – For Multiple Operating Unit

    Org_ID – Operating unit (Value from column ORG_ID in all transactional objects)
                         This is mandatory for “S” mode.
Example :-

BEGIN
    MO_GLOBAL.SET_POLICY_CONTEXT(‘S’, 123);
END;