How to update Supplier bank or Supplier bank branch details in Oracle EBS R12?

I’m sure you will find this demo very useful as it’s showing the correct way to update supplier bank and supplier bank branch details in Oracle EBS Release 12x. In many occasions I saw users creating new bank and/or branches due to lack of knowledge, training or access.

Instead to update or correct the existing banks and/or branches users will create new ones that in fact means duplicated information in your database and later on your will pay a lot of effort to clean you master data.

When a new supplier Bank or Branch will be created this information will be shared and visible together with all Banks or Branches created during the Internal bank accounts setup. This is way any implementation/upgrade should have a strict process in place to manage and keep a clean list of banks and branches.




Snapshot with supplier Banking Details page

 

Snapshot with manage Banks and Branches page

If you liked this article feel free to share it with your fellows. Thank you! 

For some other helpful videos check my YouTube Channel. 

To receive notifications for new articles follow me

Or subscribe by email

Email Address

Overview of Oracle EBS R12.2 Bank Payment Acknowledgement Processing in Payments Module

 

In this post I'm showing the EBS Payment Acknowledgement functionality delivered by Oracle starting with Release 12.2, or higher.

To prepare this demo I have used Oracle Support note 1493240.1 - R12.2: Bank Payment Acknowledgement Processing in Oracle Payments/Payables.

I have found this new functionality very useful as in my past projects we identified as a gap the payment acknowledgement process when the bank messages were handled outside EBS (by email) or by a custom solution (custom tables to store bank messages and custom reports to be published to business users).

Payment Acknowledgement functionality is about to load and display in EBS the bank processing status for each of your supplier/employee payments after successful transmission of the payment file to your bank.

Starting with release 12.2 a standard API is available to load acknowledgement file but the load of files to EBS database and call of API is subject of additional development.

From a setup point of view only Bank Acknowledgement Code Setup is required as your bank status codes should be mapped to ISO statuses provided by Oracle Payments:

• Accepted technical, syntactical and profile; passed to back office          (BACKOFF)
• Accepted back office; passed to clearing          (CLEAR)
• Accepted with change   (ACCC)
• Pending further processing        (PEND)
• Rejection          (REJECT)

From EBS process point of view this functionality will just show to you the bank status of your payment but will NOT:

• Void/change EBS payment status in Oracle Payments/Payables 
•  Impact bank reconciliation process in Cash Management

View end to end demo about EBS Payment Acknowledgement functionality delivered by Oracle starting with Release 12.2, or higher. 

For this demonstration I have used the E-Business Suite 12.2.4 VM Virtual Appliances provided by Oracle Software Delivery Cloud 

 

If you liked this article feel free to share it with your fellows. Thank you! 

For some other helpful videos check my YouTube Channel. 

To receive notifications for new articles follow me

Or subscribe by email

Email Address

How to View AP Invoice or PO details from Asset Source Line in Oracle EBS?

Often Fixed Assets team members have to find more details about AP invoices in case asset is purchased and asset source lines came from Oracle EBS Account Payables module.

These details may be related to freight or tax lines, when invoice was entered, who approved the invoice in case approval flow is enabled, if invoice was paid, if are any invoice attachments and so no.

Also PO details may be useful for further investigation - when and who approved PO, if is any requisition link to PO, what was PO need by date and so on.

These details may be found within Oracle E-Business Suite modules but will required time, additional responsibilities and at the end FA clerk is tired about number of steps to go trough.

This post will show to you how to improve user experience with Oracle E-Business Suite Fixed Assets module when integration exists with Account Payables and Purchasing.

View invoice details starting from asset source line

View PO details starting from asset source line

View end to end demo for getting Invoice and PO details right from asset source line


This solution was implemented using Oracle EBS form personalization functionality and by adding required menus and/or function to FA responsibility menu.

o Step 1 - Enable Menu entries for each screen
o Step 2 - Assign action to each Menu entry
o Step 3 - Save Invoice number in a Global Variable
o Step 4 - Save PO number in a Global Variable
o Step 5 - Sent invoice number value to Invoices Summary screen
o Step 6 - Sent PO number value to Purchase Order Summary screen
o Step 7 - Add required menus/functions

View end to end demo for setting up. You may download setup details also.


If you liked this article feel free to share it with your fellows. Thank you! 

For some other helpful videos check my YouTube Channel. 

To receive notifications for new articles follow me

Or subscribe by email

Email Address

How to create a custom Disbursement Validation Set – Payment level in Oracle EBS R12?

For companies using Oracle E-Business Suite R12.1 or above and paying their suppliers in multiple currencies from a multi-currency bank account it was a challenge to set up a validation rule at payment batch run to exclude any payments under a specific amount using standard functionality.

As an example, company X has to avoid sending to bank any payments equal or less then equivalent of 20 USD. As I mentioned above payments may be issued in different currency so is not possible to use standard validation rule due to its limit to one single currency.

If not included as a out-of-the-box functionality Oracle always provides some options to develop and implement your own logic. Using standard documentation http://docs.oracle.com/cd/E18727_01/doc.121/e13416/T387353T419293.htm and IBY_VALIDATIONSETS_CALLS_PUB standard package as an example I have implemented below solution.

• Validation set name: Greater Than_USD
• Validation set level: Payment
• Validation code language: PLSQL
• Validation set objective: Reject payments with amount less than or equal with equivalent of 20 USD
• 20 is a front end parameter and can be changed
• USD is hard-coded parameter

Steps:

1. Create your validation package - download1
2. Seed Your Validation Set - download2 and download3
3. Link it to Payment Instruction Format
4. Test running a payment batch

For steps 1 to 3 view below video


For step 4 view below video

If you liked this article feel free to share it with your fellows. Thank you! 

For some other helpful videos check my YouTube Channel. 

To receive notifications for new articles follow me

Or subscribe by email

Email Address