Oracle Cloud offers a broad portfolio of software as a service applications, platform as a service, and social capabilities, all on a subscription basis. Oracle Cloud delivers instant value and productivity for end users, administrators, and developers alike through functionally rich, integrated, secure, enterprise cloud services.
 Get a Free Magzine ...Profit:The Executive's Guide to Oracle Applications

Subscribe to the OracleAppsHub to receive notifications when there are new posts:

 get RSS feed
 Oracle Fusion Applications (OFA) is a portfolio of next generation suite of software applications from Oracle Corporation. It is distributed across various product families; including financial management, human capital management, customer relationship management, supply chain management, procurement, governance, and project portfolio management
 Get a Free Magzine ...Profit:The Executive's Guide to Oracle Applications

A Quick Look at iPayment

Posted on February 26th, 2007 by Sanjit Anand ||Email This Post Email This Post

Oracle iPayments module supports online collection of receivables from customers of the organization.

One of the major feature of Oracle Applications, particularly the Distribution and Receivables modules can be extended to include this feature of online payments.

Oracle iPayments supports new payment methods in the form of purchase/credit cards and bank account transfers. It supports different kinds of payment processing namely, Credit Card Payments, Bank Account Transfers, Cyber Cash and CheckFree.

Oracle iPayments ensures effective risk mitigation setups to facilitate the process of web-enabling payment functions by identifying all levels of risk among transactions. For example, the categories of risk can be user-defined in order to assess credit ratings of each customer and to manage risk of processing payments over the internet.

A brief look at the features offered by iPayments :

  • Easy installation, administration and extension
  • Risk management by identifying fraudulent transactions
  • A separate iPayment administrative user (from the system administration)
  • Supports several routing options, payment methods, processing moeles and security features
  • Rule based payment processing
  • Single API integration with any web based or client server applications
  • Integration with iStore, Order Management and Receivables
  • Manual authorizations of credit card payments
  • Application of risk factors on parameters such as amount, frequency of payment, amount limits, payment history and bill-to/ship-to addresses
  • Holds created on credit cards based on the risk assessment of the customer
  • Encryption / masking of credit card details

iPayment and Integration with Oracle Applications

The APIs defined for iPayment processing do so for various transaction types like authorization of credit card, bank transfer of funds, cancellation / modification of funds query generation, transaction wise risk information, payment history etc.

Fig 1, below shows ipayment technology Schematic with istore Options.


The risk evaluation and management of the iPayment process can be performed at the customer setup in Order Management, which is used to capture the transaction details of each customer that opts for the functionality, after receiving appropriate authorizations. This will also include definition of clear credit risk management structure within Order management for each of those customers where the iPayment functionality is enabled.

dgreybarrow Integration and Interface

Oracle iPayment module tightly integrates with core Oracle modules such as:

  1. Order Management
  2. Accounts Receivables
  3. Accounts Payables
  4. Order Capture
  5. Telesales
  6. Collections
  7. Oracle iStore

Oracle iPayment is a single open application programming interface (API) that can be integrated with any web-based or client-server
application. Oracle iPayment supports both single and multi-site installation of electronic commerce (EC) and client-server applications.

dgreybarrow Ipayment Technology

  • Java Servlet-Based Data Communication
  • On-line and Batch Mode of Processing
  • Stand-Alone and Integrated with Apps
  • Public API

dgreybarrow Payment system Relationship Between Oracle

Ipayment, Payment Systems And Beps(Backend Payment Processors) Oracle has well-established relationships with Payment System Providers.

Names include VeriSign, Paymentech, Citibank, First Data (North) and Concord EFSnet.

These providers have compatible servlets, that are either seeded within Oracle Applications or can be easily installed.

The payment system interfaces with BEP’s on a real time basis. Few of the BEP service providers include Paymentech, AMEX and Merchant
eSolutions. There are few business entities (such as Paymentech), that provide both Payment System services as well as BEP services.

Quasi Integrated Vendors Verisign (Paypal) is also feasible options.

Posted in Oracle Receivable | No Comments »

My ERP supplier has been acquired – now what?

Posted on February 24th, 2007 by anand ||Email This Post Email This Post

The recent couple of years have seen lot many mergers and acquisitions, thus the flow of data and supply chain that might get affected as some of information get changed when your supplier get acquired.Sharon Crawford has nicely analyses the whole situation and potentially point out some of best case. Read the whole article

Posted in Blogroll, Misc | No Comments »

Depot Repair – Primer

Posted on February 23rd, 2007 by anand ||Email This Post Email This Post

The purpose of this article is to provide a brief background introduction for Depot Repair and underline product functionality within E-business suite.

Why this is required?
If you’re company is manufacturing product and selling to customer, then services after delivery would be a prime focus, as RMA would going to cost extra dollars. More important it is understood the depot repair department does have some time-consuming process that’s many times customer end up with frustration.

The question is why depot repair is more important now a day? The answers is simple “customer is king“, so any process that keeps customer happy is always a positive side of business. More important here are some others key benefits :

  • Increase customer satisfaction
    • Execute efficient and effective repairs
    • Exceed customer expectations
  • Reduce repair costs
    • Improve material / resource management
    • Minimize overhead
  • Protect and grow revenue
    • Improve quality and repair efficiency
    • Leverage repair knowledge capital

Then what is Depot Repair

A typical depot repair department has these kind of business process.

a)Issue identification :Here the Service can be captured. Service may come as

  • Inquire
  • Support
  • Complain
  • Request Repair
  • Return

b)Repair Processing:In this stage repair processing activity can be completed.Important sub process are:

  • Receive
  • Identify & Estimate
  • Route
  • Manage Materials / Resources
  • Approve
  • Repair

c)Repair Resolution

  • Exchange
  • Loan
  • Replace
  • Ship
  • Invoice

Thus Depot Repair can be redefined as:

  • An enterprise-wide solution for managing in-house repair businesses; designed to minimize customer down-time and bridge-the-gap during product repair.
  • An application that provides end-to-end service repair processing functionality for organizations committed to delivering a total service solution.
  • A centralized place where all core depot repair functions are easily performed and monitored.

Where this come in Oracle application.
Depot repair is part of oracle application CRM activity. Thus this comes with the oracle CRM product bundle.


What functionality Depot Repair of E business Suite offers?
Depot Repair is part of the Oracle E-Business Suite and offers an enterprise-wide solution for managing issue identification, repair processing and repair resolThe functionality option.

  • Makes repair management more effective by executing and tracking logistics processes quickly and accurately.
  • Is fully automated and integrated with the rest of the E-Business Suite to improve service efficiency and reduce operating costs.
  • Monitors the return of damaged and serviceable products, performs diagnoses and job estimates, processes approvals and repairs, and executes shipments back to customers.
  • Automatically factors time and material entitlements for repairs for invoice processing.
  • Manages the repair and refurbishment of internally-owned and customer products.

Is this a standalone product?
No, this is not standalone product that means it requires data sharing with other products with in Oracle EBS. If the company is using some other products then bolt-on tight integration would be a definite need.

These are the Oracle products with which Depot Repair is interacting in term of data flow and some functionality.

  • Assignment Manager
  • Bills of Material (BOM)
  • Work in Process (WIP)
  • Order Management
  • Inventory
  • Pricing
  • Purchasing
  • Charges
  • CountersField Service
  • Installed Base
  • iSupport
  • Notes
  • Knowledge Management
  • Resource Manager
  • Service Contracts
  • TeleService

Posted in 11i, Depot Repair, EBS Suite | 3 Comments »

Welcome to R12 Account Payable

Posted on February 22nd, 2007 by anand ||Email This Post Email This Post

As we learnt during Release 12, the E-Business Suite has couple of new products like Subledger Accounting, E-Business Tax thus significant changes have been observed in Account Payable data module as some of functionality is shared by some other products. Thus it is important to understand what is new. I would like to briefly outline the details of some of new changes and underlying impact on the objects. More details can be found in R12 release documents published by Oracle a month ago.

Let’s have a dissection view of R12 payable, with some of its core objects


We have seen in 11i

  • Suppliers defined in AP.
  • Supplier contacts replicated for each supplier site.

Where as in R12

  • Supplier becomes as TCA Party.
  • Suppliers Sites as TCA Party Site for each distinct address.
  • Contacts for each supplier/address , it means Single supplier address and contact can be leveraged by multiple sites, for each OU
    • A single change to an address can be seen instantly by all OUs
    • No longer need to manually ‘push’ updates across OUs.This can be best understood by the figure below.


Then the question is what will happen if any one can come from existing financial products. The Impact from upgrade can summarize as:

1. When we upgrade supplier tables replaced with backward compatible views.

2. One party site for each distinct supplier site address

Country and address line1 are required, this is because creation of suppliers in Party in TCA data model would requires Country and address information, but it also understood if there is no country or address line 1 specified for a supplier site in cases when upgrades takes place, Payables derives the country based on the most frequently used operating unit of the Supplier’s historical transactions.

3. Employee as suppliers: address NOT migrated to party site in TCA remains in Oracle HR for data security reasons.

As we know in 11i employees are part of internal supplier’s record in order for Oracle Payables to create payments for their expense reports. Employees defined in Oracle Human Resources and associated with an Oracle Payables supplier record have existing party information. During the upgrade, Oracle Payables updates the existing party information to have a party usage of supplier but it does not migrate the employee address to the party site in TCA, they remain in Oracle Human Resources for data security reasons.

4. Utilize TCA Party relationships for franchise or subsidiary and its parent company.


Till 11i version, we have seen invoices:

  • Had only distributions line.
  • Allocation of freight and special charges are captured at the distribution level only
  • Tax and payment and Project accounting Payment was captured through global Descriptive Flexfields.

But in R12,

1. Invoice Lines as a new additional line accommodated in Invoice data model.


Because of introduction of invoice line there is significant improvement of data flow with n other oracle modules like

  • Fixed Asset – Asset Tracking
  • Business Tax – Tax line
  • Payment – Payment
  • SubLedger Accounting – Accounting


2. Allocate freight and special charges are captured to the lines on the invoice
3. Invoice distributions created at the maximum level of detail similar to 11i.
4. Core functionality

The impact with Upgrade can be summarized as:

1. One invoice line for every distribution in 11i
2. Sub Ledger Accounting requires that Payables transform the invoice distributions to be stored at the maximum level of detail
3. Global Descriptive Flexfields migrated to named columns.

          That’s means functional testing is more required while upgrade takes place.

Banks and Bank Details

Now a days corporate treasury role has been greatly enhanced thus picking up a global bank as partner for all banking need is demand of time in global working model. The recent couple of years have seen drastic increase in acquisition and merger of company thus global working as well as global instance get popularity in ERP areana, and this is one of reason of the reason bank data model has been significant changes from 11 to 11i and 11i to R12.

Internal Bank Accounts
In 11i we have seen internal Banks defined in AP and that is shared by AP/AR/CE, Payroll and Treasury and they are bank accounts often replicated in multiple OUs

Where as in R12,

  • Bank and Branch become part of TCA Parties.
  • Internal Bank Account in Cash Management which is owned by a Legal Entity. Here the Operating units have granted usage rights.

Suppliers Bank Accounts
In 11i

  • Banks/Branches defined in AP
  • Bank accounts often replicated in multiple OUs Before


  • Suppliers, Banks and Branches are defined as Parties in TCA
  • Supplier (party’s) payment information and all payment instruments (Bank Accounts, Credit Cards) moved into Oracle Payments.

The typical data model for bank can be summarized as:


Impact of Upgrade

1. With Upgrade banks and branches migrated to TCA parties
2. Banks merged if the following attributes are all the same:

  • a. Bank Number
    b. Institution type
    c. Country
    d. Bank admin email
    e. Bank name alt
    f. Tax payer ID
    g. Tax reference number
    h. Description, Effective dates

3. Bank accounts, bank account uses are migrated into cash management.
4. Transactions are stamped with the bank account uses identifiers as part of the upgrade

 Integration with Oracle E-Business Tax

In 11i

  • Oracle standard functionality was based out of User which determines tax by assigning Tax Codes at line level of invoice and Tax rules was controlled at underline code.
  • There was global descriptive flex fields were captured for country-specific tax attributes.
  • More importanta most of the setup performed at OU level.

In R12

  • A new module eBusinessTax determines tax based on facts about each transaction, this is reason why Oracle has introduced additional line information at invoice level.
  • The module “ebusiness Tax” set and configure Tax rules which can be viewed
  • Tax attributes collected in fields on key entities
  • Configure tax rules once per regime and share with your legal entities

Impact of Upgrade
1. Payables Tax setup, Tax Code defaulting rules defined per OU are migrated to eBusiness Tax.
2. OUs migrated to tax content owner in R12
3. Tax information in tax codes are transformed to Regime-Rate flow.
4. E-Business Tax takes information from the AP invoice lines and creates summary and detail tax lines in the E-Business Tax repository.

Multi Org Access Control

MOAC is new enhancement to the Multiple Organizations feature of Oracle Applications.

This feature enables user to access data from one or many Operating Units while within a set given responsibility. Due to this change, all processing and some Reporting in Oracle Payables is available across Operating Units from a single Applications responsibility. Hence you can isolate your transaction data by Operating unit for security and local level compliance while still enabling shared Service centre processing.Data security is maintained using the Multiple Organizations Security Profile, defined in Oracle HRMS, which specifies a list of operating units and determines the data access privileges for a user.

Impact of Upgrade
R12 Upgrade does not automatically create security profiles, thus is important if any one want to use Multiple Organizations Access Control, the first things is to define security profiles, then link them to respective responsibilities or users.

Reference: Details can be found more on R12 RCD documents, from Oracle site.

Posted in Oracle Payable, R12 | 28 Comments »

EDI & E-Business Suite – Part II

Posted on February 15th, 2007 by anand ||Email This Post Email This Post

This is a continuation of last article for EDI, here are the add-on details for most of the EDI been offered within E-Business suite. More importantly, the two different widely acceptable standards are mostly used in different continent. For example the in North America and Canada ASC X12 is widely accepted across industry where as well as Europe and Asia has EDIFACT as preferred standards.

Now, here is the extensive list of EDI with categorization with E business suite module wise.

Oracle Purchasing

  • Outbound 850/ORDERS
  • Outbound 860/ORDCHG
  • Inbound 832/PRICAT
  • Inbound 843/QUOTES
  • Inbound 856/857/DESADV
  • Outbound 824/APERAK

Order Management

  • Inbound 850/ORDERS
  • Inbound 875/ORDERS
  • Outbound 855/ORDRSP
  • Inbound 860/ORDCHG
  • Outbound 865/ORDRSP


  • Outbound 856/DESADV


  • CUSDEC (No ASCX12 equivalent)


  • Inbound 810/INVOIC
  • Outbound 820/PAYORD-REMADV
  • Outbound 824/APERAK


  • Outbound 810/INVOIC
  • Outbound 812/DEBADV-CREADV

Supplier Scheduling

  • Outbound 830/DELFOR
  • Outbound 862/DELJIT

Release Management

  • Inbound 830/DELFOR
  • Inbound 862/DELJIT
  • Inbound 866 (No EDIFACT equivalent)

Hope this helps a fair idea about the EDI messaging usage in EBS suite. Will write couple of more article under this head for setting up EDI message in EBS Suite with one business case.

Posted in 11i, EBS Suite, EDI | 2 Comments »

EDI & E-Business Suite

Posted on February 9th, 2007 by anand ||Email This Post Email This Post

This is an article is all about EDI, deal mostly with basics and some information with underline Oracle E business Product within the suite. This article start with a typical business case and describe how this is evolves and how important is in ERP, the article helps you understand the high-level overview of the EDI process.

Why EDI Evolved?

Let us consider a simple business scenario. A Customer from PO department who wants to purchase an item creates a purchase order and then faxes it to the suppliers. At the moment vendor receives the purchase order and manually keys in a sales order. The vendor’s system generates a confirmation date that is sent back to the customer via fax or mail. The vendor then ships the goods via a carrier. The carrier delivers the products to the customer. When the goods are shipped, the vendor invoices the customer. The customer makes the payment by check, and the vendor deposits the check in the bank. Finally, funds are transferred from the customer’s account to the vendor’s account.



Figure: Typical business documents exchanged by business partners

Now It clears how much of information needs to be transferred and tracked to run the business, which in reality it is called trading partner. This simple scenario requires the exchange of various documents between several business partners at different times.

All this electronic data was exchanged using floppy disks and other secondary devices. So, ANSI committee was formed to define the standards. Hence the electronic exchange of business documents in a standard format gave birth to what is known as EDI, today the business world had accepted as one of most important entity.

What is EDI?

EDI (Electronic Data Interchange) is the electronic exchange of business documents between the computer systems of business partners, with a standard format over a communication network. It can also be called as paperless exchange.

EDI, electronic funds transfer (EFT), electronic mail and fax are increasingly being used to schedule operations, streamline order fulfilment, and optimise cash flow.


Standard Formats
The business documents that are been exchanged between business partners need to be in a standard format. ANSI X12 (American National Standards Institute) or EDIFACT (Electronic Data Interchange For administration, Commerce, and Transport) are two standards, which supply a common language for formatting the information content that is been exchanged.

There are five major Components in the EDI Process:

o Sender
o Receiver
o Language
o Content
o Medium

In EDI, the senders and receiver are called trading partners (Customers and Vendors) and the ANSI X12 or EDIFACT standards supply a common language for formatting the information content of common messages.

Oracle’s e-Commerce Gateway (EDI Gateway):

A standards-based integration product for Oracle Applications, which allows for companies to integrate Oracle Applications with applications residing inside or outside of the enterprise; communicating via Intranet, Extranet, or Internet.

Oracle’s e-Commerce Gateway is independent of all EDI standards and can be integrated with any upstream or downstream process via an ASCII file. Thus, any EDI translator or third party application, that best suits a company’s business requirements, can be selected.


The major advantage of using Oracle e-Commerce Gateway are listed below:

1. Reduction in labor hours dedicated to data entry
2. Increased data accuracy
3. Quicker communication of key information to and from customers/suppliers resulting in reduced business cycle times and more efficient planning
4. Promotes commonality of business documents and processes

Know the Terminology used in EDI

  • Transaction Set – Business document transmitted between companies (e.g. Purchase Order).
  • Data Segment – Units of data used to communicate specific information within a message (e.g. the header).
  • Data Element – Specific unit of data within a data segment.
  • Trading Partner – Entity such as a customer, supplier, or sister organization with whom electronic commerce is executed.
  • EDI Standards – Agreed to formats for exchanging electronic data (typically developed by representatives of industry verticals).
  • Translator – Software application that translates data into or out of a specific format or standard for processing by an ERP system.

Oracle EDI Gateway – functionality

  • Define Trading Partner Relationships
  • Define Code Conversions
  • Customize Flat File Formats
  • Use Standard Report Submission
    • Initiate Extract Process
    • Initiate Import Process
    • View Extract/Import Process Status

A typical flow can be understood as:


A note on File

  • ASC X12 is the EDI standard for North America and Canada.
  • EDIFACT is the EDI standard for Europe and Asia.

Transaction Supported in Oracle Apps

  • v10.6 – supports 4 transactions
  • v10.7 – supports 4 transactions
  • v11.0 – supports 14 transactions
  • v11i – supports 18 transactions
  • v11i10.2 – supports 23 transactions
  • R12 – data not available

Some Important EDI’s Details with Orcle E business suite Modules

Some Important EDI’s Details with Orcle E business suite Modules


Posted in 11i, EBS Suite, EDI | 11 Comments »

R12 :Released with 18 new Products

Posted on February 2nd, 2007 by anand ||Email This Post Email This Post

As expected, finally Oracle has announced and released five major product lines in there “Applications Unlimited” program at 31st Jan 2007 , the big event was much awaited . Few highlights on the event are:

  • Oracle E-Business Suite Release 12: What they call “Global Business Release”, 18 new products with 2443 new enhancements.
  • PeopleSoft Enterprise Release 9.0: This contains two new products and 1478 enhancements
  • Siebel CRM 8: This offers ten new products and 366 enhancements.
  • JD Edwards World A9.1: This they called Renaissance Release as this is major release of JD Edwards World in ten years, this new version offers 4 new products and 1297 enhancements.
  • JD Edwards EnterpriseOne 8.12: The Continued Innovation Release. The latest EnterpriseOne had 5 new products, including a new Operational Sourcing and three new modules for the food and beverage industry, as well as 291 enhancements.

More information can be browsed @Link

Posted in News | No Comments »