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

Procurement Cards – Reaching the Potential within ERP

Posted on August 30th, 2011 by Sanjit Anand ||Email This Post Email This Post

The procurement card, or P-card, is a form of company credit card that is issued to employees who can then purchase goods and services without having to process the purchase through a traditional purchasing procedure, such as using purchasing requisitions and purchase orders.

dgreybarrow Types of Commercial Cards

P-Cards are just one type of Commercial Card. Other Commercial Card comes with different name include the following. Each is intended to address different types of purchases and/or spend categories.

  • Corporate Card – commonly used by organizations for employee travel and entertainment (T&E) expenses; also referred to as a Travel Card
  • One Card – a single charge card that combines procurement with T&E and, in some cases, fleet and phone charges
  • Fleet Card – a card product used by organizations to pay for fuel, maintenance, repair and related expenses on company vehicles
  • Prepaid Card – debit-based card, allowing the user to pay now versus later, as the card transaction amounts are deducted from a funded account; for example, a Payroll Card “loaded” with an employee’s earned wages
  • Business Card – a credit card targeted for smaller businesses (in lieu of a P-Card), commonly used for a variety of expense types (e.g., goods, services, travel, etc.)
  • Supplier P-cards: Supplier P-cards (or Ghost Cards) are another way for companies to incorporate electronic payment and settlement procedures in order to streamline their procure-to-pay processes. Instead of having to maintain a separate employee p-card for each requester in the company and each requester having to use his/her own employee p-card to make purchases, companies can maintain a single supplier p-card for each supplier/supplier site in the system, and consolidate all purchases from that supplier/supplier site on the single supplier p-card.

dgreybarrowProcurement Card Pros & Cons


  • Procurement cards reduce the cycle time of purchasing transactions
  • Procurement cards can improve supplier relations as suppliers receive payment within 2-5 days
  • Procurement cards can reduce the number of supplier invoices, which could lead to a reduction in expenses on accounts payable personnel
  • With proper controls, procurement cards can restrict maverick buying as well as buying non-authorized categories of goods and services
  • Procurement card programs foster a feeling of empowerment among employees


  • Procurement card use exposes the organization to the potential for undetected credit card fraud and identity theft, which can result in lost money
  • Procurement cards generally don’t provide the same level of budget visibility as an ERP system does
  • Multiple ways of placing orders (e.g., Pcard, eProcurement, ERP, requisitions, etc.) can confuse requisitioners who may not know the proper method for each type of purchase
  • Procurement card spend data may not be integrated with other purchase data, resulting in incomplete information when conducting spend analysis

dgreybarrow P-Card in EBS

Within Oracle Applications, the Procurement Card Process to pay the supplier without compromising data security. This functionality can be used by any organization willing to pay the expenses of purchased goods from suppliers as well as service used by the individuals for company purpose.

Apart from that, the usage of P-card can be extended to pay suppliers that are currently in the process of self-billing. This process is new to oracle iExpense module but have great creditability and performance to its usage.

The card transaction files are received from the card issuer and then uploading into specified location of oracle server. Next upload these data into oracle interface table AP_EXPNESE_FEED_LINES_ALL. Then run the following oracle program from payables responsibility to generate the invoice. Once loaded, Oracle standard program will validate the transactions and generate distribution lines. Depending on the setup, users can verify the transactions as well as approve and invoice will be imported into AP through standard process which will execute sequentially as below:

  1. Procurement card Transaction Validation Program
  2. Procurement card Transaction Verification Program
  3. Procurement Card Transactions Approval Process
  4. Create Procurement card Issuer Invoice
  5. Payables Open Interface Import


In After successful execution of Procurement card Transaction Verification Program user can only change the distribution account and can validate the specific transactions. System have the provision to send notification for verification of transaction to the respective employee-manager hierarchy. The invoices are generated in payables with source as Procurement card .The payment can be made through Oracle standard payment process either with check or electronic payment.

Within Oracle ERP technology the functionality to store the sensitive information in system is compliant to PCI-DSS. This process is technically known as Encryption Process. Oracle standard single key encryption algorithm is used to store the sensitive data like credit card number, bank account number.

Posted in Oracle Payable | No Comments »

Integration of Oracle Service Contracts with other modules

Posted on August 30th, 2011 by Sanjit Anand ||Email This Post Email This Post

This post is to discuss the integration of various modules of e-Business Suite from an Oracle Service Contracts perspective. It should give an idea to consultants who wish to determine dependencies and to understand how the different modules communicate data between each others.To start , you can memorize this figure as below.

Integration of Oracle Service Contracts with other modules


  • With Inventory
    • Manages items associated with Oracle Service Contracts agreements and contracts: services, usages, warranties, subscriptions, and serviceable items
  • With Advanced Pricing
    • Supplies the information to price the services and usages sold on the contract.
  • With Order Management
    • Raises sales orders from which warranties and extended warranties are created.
    • Inventory is used to define serviceable products and service items (warranties and extended warranties)
  • With Quoting
    • Provides quotes for sales orders
  • With Receivables
    • Service Contract is integrated with the Oracle Receivables module for generating Invoices. In the Receivables we have to define Transaction sources and associated Transaction types which will be used for generating Invoices from Oracle SC. In the Service Contract we have to use the Accounting Rule, Payment Terms, and Invoicing Rule that will be used for the respective Contracts.
  • With Bills of Material
    • Associates warranties with serviceable items
  • With Install Base
    • Provides details of trackable items and the tracking of counters.
  • With CMRO (Complex Maintenance, Repair, and Overhaul)
    • Provides details of preventive maintenance programs, that may be associated with service contracts.
  • With TeleService
    • Manages service requests
    • Retrieves contract details for a customer such as account, end date, status,contract type& number on all of their contracts.
    • Looks for the preferred engineers for a particular service.
    • Has visibility to coverage levels & times, reaction & resolution times for coverage, billing rates and types for a specified coverage.
  • With iSupport
    • Provides customer access to service contracts to view entitlements, preferred technician, response and reaction times via self service mechanisms
  • With Depot Repair
    • Provides details for repairs, exchanges, replacements, and loaners, which may update the contract coverages.
    • Has visibility to coverage details.
  • With Field Service
    • Provides details about service and repairs to be carried out in the field.
    • Has visibility to coverage details

Hope this helps.

Posted in Service Contracts | No Comments »

PO Module Inter-dependency

Posted on August 29th, 2011 by Sanjit Anand ||Email This Post Email This Post

This post is to discuss the integration of various modules of e-Business Suite from an PO perspective. It should give an idea to consultants who wish to determine dependencies and to understand how the different modules communicate data between each others.

dgreybarrow With Account Payable

  • Matching need PO number to match Invoices
  • PO Distribution Details Default to Invoice Lines
  • Projects and Assets Information default to Invoice Line Distribution depending on PO Match
  • AP Invoice Holds depend on PO Tolerance limits and Paid When Holds are released and Tolerance level met

dgreybarrowWith Inventory

  • Items Setup in Inventory are Used in a PO
  • Item Attributes Assigned define behavior of Items on a PO
  • Categories Defined and assigned to Items are defaulted to Items Ordered in a PO

dgreybarrowWith Projects Dependency

  • Projects setup in Project Accounting can be selected at the PO Distribution level
  • Type of Project Determines the Project default
  • Accounting derived based on Defaults for Projects
  • Project status affects the use of specific project on a PO

dgreybarrowWith Fixed Assets

  • Items classified with Asset Category used on a PO derive the classification of Item on a PO line
  • PO Defaults are interfaced to Assets via APModule
  • Asset Category & Asset Clearing Account is interfaced to Assets from PO
  • Important to select Appropriate Account on PO, before the PO Line can interface to Assets via Mass Additions
  • Supplier information defaults to Assets from PO
  • Employee and Manufacturer information interfaced from PO to Assets

dgreybarrowWith GL

  • All Account details defined on Items, Projects or Item Categories determine the account on a PO Shipment’s Distribution
  • Employee Default account information determines the account on a PO Distribution for Expense related PO/Requisition
  • Default account selected on a Requisition derives the account on a PO Distribution
  • SLA Definition derives the account upon GL Transfer

dgreybarrowWith Order Manager

  • Items defined as Outside Processing (OSP) are defaulted on a Internal Sales Order, which then converts it into a Internal Requisition and a PO
  • Drop-shipment functionality affects PO Item behavior

dgreybarrow With HRMS

The purchasing module uses the HR employee database for the following purposes:

  • Designate employees as buyers
  • To assign documents (purchase orders, requisitions, etc.) against them when these documents are created.

The module can use either the supervisory or the position hierarchy for routing approvals

Posted in Oracle Purchasing | No Comments »

Secuity : Oracle Application Module Security with R12

Posted on August 28th, 2011 by Sanjit Anand ||Email This Post Email This Post

This post is more on revisiting EBS Application Module Security.

1. HRMS Security

In HRMS there are two major Securities concept

  • Standard
  • Security Groups Enabled

Standard HRMS Security is a simple security used within a single legislation and a single business group. In this model, typically a Security Profile is created for each distinct group of employees and it is assigned to a responsibility.Its very simple.

For enabling Standard HRMS Security, Security Profile screen (US Super HRMS Manager -> Security -> Profile) can be used to create a Security Profile.

In Security Groups Enabled Security a single responsibility can be assigned to more than one business group and so users can access records from multiple business groups. In this model, multiple security profiles can be assigned to a single responsibility.

Typical example you can understand in this way : an HR Manager and Assistant HR Manager can use the same responsibility, but will be able to view different data.

For Security Groups Enabled Security, use Global Security Profiles window.

2. Multi Organization Access Control (MOAC)

This means Role based access to Operating Units.

Single installation of EBS can support different types of organizations and this feature is ability to access multiple organizations from a single responsibility, which is avaiable in majority of Oracle application modules.

Typical example of MOAC may be similar to senario listed here:

  • Limit users to their relevant organizations through security profiles.
  • Assign inventory organizations to inventory users.
  • Enter Purchase Orders in one organization and receive goods into any other organization.
  • Internal Requisitions from one organization and ship from another organization, with Intercompany invoicing.

Now, I’m going to explain how to define a security profile. Using Oracle HRMS, you can define your security profile using two forms: The Security Profile form or the Global Security Profile form that is shown here. Both forms look almost identical.

The Security Profile Form allows you to select operating units from only one Business Group. The Global Security profile Form allows you to select operating units from multiple Business Groups.

The decision on which form to use is really up to you and depends on your HR implementation and how you want to partition data. All you need to do is enter a name, and select the Security Type called “Secure organizations by organization hierarchy and/or organization list”. This allows you to assign multiple OUs. When assigning operating units, first select classification Operating Unit, and then select the organization or Operating Unit name. You can assign as many operating units as you want.



3 Bank Account Security

Bank Account Maintenance security secures the creation and update of bank accounts, whereas Bank Account Access security secures the use of bank accounts.

Bank Account Maintenance Security, which secures the creation and update of bank accounts, grants user the access to one or more legal entities. Users can create and update the bank accounts whose owner legal entity is registered in the Bank Account Maintenance Security.

Users can create Bank accounts for which the list of legal entities in Bank Account Owner LOV will be restricted by this security. Users can query and update only those bank accounts whose owner is registered in this security.

The security setup is done in a wizard called “Bank Account Security Management”.

Define bank account use and link organization for every account.
Navigation: Cash management Superuser (R) -> Setup -> Banks -> Bank Accounts -> Click Account Access (T).

Bank security1

Assign organization (Operating Units, Ledger Entities and Business Groups) and bank account use to a Role.

Navigation: User Management ( R) -> Roles & Role Inheritance -> Security Wizards -> CE UMX Security wizard.

Bank Security

Bank Account Access security rule is composed of 2 parts :

  1. Bank Account Access Setup => Bank Account Access setup defines organizations that can use existing bank account
  2. Cash Management Security Profiles => Cash Management Security Profiles provide a list of organizations where an user has access to.

4. Purchasing Security

Purchasing documents can have 4 levels of security:

  • Public: Any user may access these documents.
  • Private: Only the document owner and subsequent approvers can access the document.
  • Purchasing: Document owner, subsequent approvers and users listed as buyers can access.
  • Hierarchy: Document owner, team members, approvers and others in the security hierarchy higher than document owner.



5.iSupplier Security

If you have created custom responsibilities that will be assigned to supplier users,securing attributes must be included in your custom responsibility definition.

There are three securing attributes that can be used to control access. These attributes are all seeded with the pre-defined Oracle iSupplier Portal responsibilities that are released with the product:

  • ICX_SUPPLIER_ORG_ID – Identifier for the supplier.
  • ICX_SUPPLIER_SITE_ID – Identifier for the supplier site.
  • ICX_SUPPLIER_CONTACT_ID – Identifier for the supplier contact

You can enable them from Navigation: System Administrator ( R) -> Security -> Responsibility -> Define.


6.Flexfield Security Rules

Flexfield Value Security gives you the capability to restrict the set of values a user can use during data entry. With easy-to-define security rules and responsibility level control, you can quickly set up data entry security on your flexfield segments and report parameters.

Flexfield Value Security lets you determine who can use flexfield segment values and report parameter values. Based on your responsibility and access rules that you define, Flexfield Value Security limits what values you can enter in flexfield pop-up windows and report parameters.

Security rules for the Accounting Flexfield also restrict query access to segment values in the Account Inquiry, Funds Available, and Summary Account Inquiry windows. In these windows, you cannot query up any combination that contains a secure value. However in all other forms, you will be able to query up a value even if it is restricted to the user.

In order to use, you just need to define Security Rules window to define value security rules for ranges of flexfield and report parameter values.

Navigation: Application -> Validation -> Security -> Define.

Use Assign Security Rules window to assign the flexfield security rules to an application responsibility.

Navigation: Application -> Validation -> Security -> Assign.

7.Fixed Assets Security

You can manage your Asset Book Security, as mention in one of previous post.This Functionality you can understood as:

  • Secure access to each depreciation book / Ledger
  • Create a flexible hierarchy of asset organizations
  • Associate a responsibility with one or more depreciation books

Asset Book Security allows multiple asset books/registers to be manage/administered independently

Fixed Assets responsibility can be secured by linking a Fixed Asset Book / Ledger, by executing the following steps:

  • Link an Asset organization to the Fixed Asset Set of Book/Ledger.
  • Establish an Organization hierarchy for the asset organization.
  • Navigation: Fixed Assets Manager ( R) -> Setup -> Security -> Organization -> Description -> Query Asset Organization -> Select ‘Asset
  • Organization’ -> Click ‘Others’ -> Assign FA Book.

8. Oracle Projects Security

Oracle Projects provides several integrated security mechanisms to help you define user access to organization, project, and resource information, as well as a variety of Oracle Projects functions. These mechanisms are all based on function security, which is the foundation of Oracle Applications security.

Using these integrated security mechanisms, you can define Oracle Projects security at the following levels:

  • Responsibility level, across projects.
  • Project level, using project roles.
  • Organization level, using predefined organization authority roles.

9. Inventory Organization Access

Inventory organizations can be assigned to responsibilities with inventory screens, thereby restricting the access to only those inventory organizations.

Navigation: Inventory ( R) -> Setup -> Organizations -> Organization Access.


It is a very straight forward Form that you can assign which Inventory Organization(s) available to a responsibility. The Rule behind this Form is that once a responsibility is used, the default is that this responsibility does not allow to access all Inv. Org., unless you explicitly assign it. The good side is that this setting is effective immediately; no need to submit what-is-the-name-again process, setup all-look-like-the-same profile options

10. Manufacturing Organization Access

Manufacturing organizations can be assigned to responsibilities with manufacturing screens, thereby restricting the access to only those organizations.

your Navigation is: Advanced Planning Administrator ( R) -> Admin -> Organization Security.

11. Shipping Grants & Warehouse Access

Shipping roles can enable or disable access to individual functions within Shipping.

Navigation: Order Management ( R) -> Setup -> Shipping -> Grants and Role Definitions -> Define Roles.

shipping execution

Then you can assocaite shipping roles then can be assigned to individual users.

Navigation: Order Management ( R) -> Setup -> Shipping -> Grants and Role Definitions -> Grants.

12. Order Holds

In Order Management, when further processing has to be prevented on an order, a hold can be placed and released later.
Navigation: Order Management ( R) -> Setup -> Orders -> Holds.
Order Book

13. Advance pricing

Pricing security enables you to restrict pricing activities such as updating and viewing pricing entities to users who are granted specific access privileges. Pricing entities include price lists, pricing agreements, and modifiers.

Pricing security can be set up and maintained in the HTML user interface by a user who is assigned the Oracle Pricing Administrator responsibility. The Oracle Pricing Administrator has the authorization to access and update all pricing entities for all functional users.

With pricing security, you can implement a higher level of control by:

  • Assigning pricing entities to operating units: A pricing entity can be assigned ownership to a specific operating unit. You can restrict usage to one operating unit or by all operating units.
  • Assigning privileges that control which grantee (Global, Operating Unit, Responsibility, or User level) can view or maintain the specified entity: You can use security privileges to control user’s access to pricing entities in the following ways:
    • Grant view-only or maintain access privileges to functional users at the Global, Operating Unit, Responsibility, or User level.
      Assign or reassign Operating Unit ownership to price lists and modifiers and control which operating units can use them for pricing transactions.
    • Create entity sets (a set consists of grouped pricing entities) and assign access privileges to the entire set. The Entity Set function is available only with license to Advanced Pricing.
  • Setting default rules for security access for new pricing entities.

Take a Note , before turning on pricing security, you must create privileges for existing pricing entities.

Navigate (N) Oracle Pricing Administrator Setup –> Security –> Privileges


Hope this post will surly help you in address some of security and audit need for Clients/Customer.

dgreybarrow Suggested Reading

Posted in Security | No Comments »

What are the Security Attributes?

Posted on August 27th, 2011 by Sanjit Anand ||Email This Post Email This Post

Securing attributes are used by some Oracle HTML-based applications to allow rows (records) of data to be visible to specified users or responsibilities based on the specific data (attribute values) contained in the row.

You may assign one or more values for any of the securing attributes assigned to the user.

If a securing attribute is assigned to both a responsibility and to a user, but the user does not have a value for that securing attribute, no information is returned for that attribute.

Isupplier, iexpense have using these feature, but still you can take advantage by creating your own depending upon the need.

dgreybarrow Defining new/Custom

Here are the steps to define Security Attributes

  1. Navigate to the Summary Security/Text.
  2. Select the security type from the drop down list. The valid values are:
    • Group: This specifies contract group security
    • User: This specifies user security
  3. Select the Group or User Name from the list of values, depending on the security type.
  4. Select the security level appropriate to the security type. The valid values are:
    • Modify: This allows update access to given contract.
    • Read Only: This allows on display or read access to the given contract.
  5. Save your changes

Posted in Security | No Comments »

Oracle Advanced Security – TDE (Transparent Data Encryption )

Posted on August 26th, 2011 by Sanjit Anand ||Email This Post Email This Post

This is one of the advance feature of security, where Encryption is done automatically when written to the database file and transparently decrypts the data when accessed inside the database.

Files are secure from unauthorized access at the OS level, discarded disk drives and off-site backup media.[Adopted from Oracle Documentation]

Network encryption transparently encrypts all SQL*Net traffic between the Oracle EBS and the database.

Oracle Advanced Security supports both industry standard Secure Sockets Layer (SSL) encryption and an Oracle native encryption capability for customers that do not want to deploy X509 Public Key Infrastructure (PKI) certificates.

Traditional access controls including those enforced by Database Vault, Label Security and Virtual Private Database (VPD) also apply and so data will not be decrypted until the users are authenticated to the Oracle database.

TDE column encryption can be used to protect individual columns in application tables containing credit card numbers or other personally identifiable information (PII).

dgreybarrow Scenarios

You are told to explore the options for implementing Oracle Advanac Security Option(ASO) in Oracle financial application. Probally you might have these questions in mind?

  • What tool or function , should needed and how this handle with advance options?
  • Does this tool encrypt the table column in the database at all time and only decrypt the table column?
  • Is that needed through Oracle Financial or any OracleApps UI or is sitting standalone inside/outside application?
  • Is there any different treatment for some sensetive data like Credit card, Bank Account and or SSN values ?

In above senarios , you might have a similar requirement to encrypt the SSN value in an Oracle table at all time and only make it viewable(decrypted) when a authorized user via Oracle financial application tries added or update a record to database.

If you already aware about TDE , then you should not have much issue in doing fitment . Fundamentally the TDE have functionality is the same irrespective of the application. It’s encrypts the column data at rest meaning in the storage it is kept encrypted, to protect the data in the event of stolen storage or when someone has direct access to the storage disks. Database automatically decrypts the data for whoever got privilege to access to this data, say SELECT privilege.

The best place is to start with Oracle documentation and get the details/

If you are doing with existing data value of Oracle Financial ref to these note in metalink that will be helpful.

  • Doc ID 862708.1 : R12 – Customer’s Taxpayer ID and SSN On Customers Form Need To Be Encrypted
  • Doc ID 403537.1 : Best Practices For Securing Oracle E-Business Suite Release 12
  • Doc ID 828229.1 : Using TDE Tablespace Encryption with Oracle E-Business Suite Release 12
  • Doc ID 863053.1 : How To Encrypt Credit Card Data In Release 12
  • Doc ID 732764.1 : Using TDE Column Encryption with Oracle E-Business Suite Release 12
  • Doc ID 1301337.1 : How To Enable Oracle Payments Data Encryption Functionality

If you are looking the for the possiblity to encrypt and decrypt data using triggers or some other database object without changing an application, then probally you can use the the dbms_obfuscation_ toolkit within a trigger.

Posted in Oracle Application, Security | No Comments »

Security : Oracle Database Vault

Posted on August 20th, 2011 by Sanjit Anand ||Email This Post Email This Post

Oracle Database Vault restricts access to specific areas in an Oracle database from any user, including users who have administrative access. For example, you can restrict administrative access to employee salaries, customer medical records, or other sensitive information.

This enables you to apply fine-grained access control to your sensitive data in a variety of ways. It hardens your Oracle Database instance and enforces industry standard best practices in terms of separating duties from traditionally powerful users.

Oracle Database Vault this addresses common regulatory compliance requirements and reduces the risk of insider threats like.

  • Preventing highly privileged users (DBA) from accessing application data.
  • Enforcing separation of duty (DBA can’t create users, view data).
  • Providing controls over who, when, where and how applications, data and databases can be accessed.
  • Can be added to existing application environments without changes to the existing application code.

For Consulting people, lets try to understand three most important concept required from security .

1) Realms – These are boundaries within the Oracle database that act like a firewall to prevent privileged users from using their special privileges to access application data.

The realms can be used to protect an entire application or a specific set of tables within an application, providing highly flexible and adaptable security enforcement.

Look at the following diagram the DBA has been denied access to view the application data, in spite of the special privileges.

Oracle Databse Vault

2) Command Rules – Security rules that can be created for creating, dropping and altering tables inside the database and decide whether to block a command.

Factors – It can also reference out-of-the-box factors such as IP address, authentication method and program name.

In the diagram below, Database Vault has denied access as the applications are accessed either through wrong IP address or tool.

Oracle Audit Vault-2

3) Separation of duty – Oracle Database Vault systematically separates DBA duties to strengthen security controls and helps satisfy requirements found in many regulations.

Out-of-the-box, Database Vault creates following 3 distinct responsibilities within the database

  • Account Management :A user with account management responsibility can create, drop, or modify database users
  • Security Administration :A security administrator can manage realms, command rules, factors etc., but prevented from self-authorizing access to secured business data
  • Database Administration :Database administration responsibility enables a user to continue performing normal management and maintenance, such as backup and recovery without having access to secured business data

Therefore, Oracle Database Vault is an integral component of your enterprise.Typically companies configure Oracle Database Vault to manage the security of an individual Oracle Database instance.

Posted in Security | No Comments »

TCA & Business Objects

Posted on August 19th, 2011 by Sanjit Anand ||Email This Post Email This Post

Do you know In R12 , there is New Public API’s for Business Objects, which can be used with a single API call. This Covers a total of 16 objects
of 4 Composite objects as

  • Person
  • Organization
  • Person Customer
  • Organization Customer

It also covers granular objects like Customer Account, Address etc.

There are four action avaiable in these API’s as Create / Update / Save / Get
This provides API’s to Map Business objects in TCA to Source system identifier of other systems.

Public API for logical Person is HZ_PERSON_BO_PUB

  • create_person_bo – Creates person related elements
  • update_person_bo – Updates person related elements
  • save_person_bo – Saves person related elements
  • get_person_bo – Retrieves person related elements

where as Person Customer API is HZ_PERSON_CUST_BO_PUB

Public API for logical Organization is HZ_ORGANIZATION_BO_PUB

Public API for Organization Customer is HZ_ORG_CUST_BO_PUB

There is Business Object Events which can be used to notify the Spoke/custom systems for updates done to TCA data.

Posted in Oracle TCA | No Comments »

Global Withholding

Posted on August 18th, 2011 by Sanjit Anand ||Email This Post Email This Post

In the UK, Spain, France, Australia, Singapore, and many other countries, when an invoice is paid, a certain part of the payment is deducted and paid to the tax authorities as a withholding tax.

The global withholding architecture in any accounting appliction should provides functionality to meet the majority of processing and reporting requirements worldwide.

It Required various methods of calculating and reporting like :

  • Statement of basis amount subject to Withholding by vendor/class – No Withholding per say and no accounting (Belgium, France).
  • Percentage calculation, accounting and reporting (UK, Spain).
  • Mixed mode of the two previous methods (Canada).
  • Tier-based withholding percentage (Argentina, Japan)
  • Additional withholding surcharges (India)
  • Period-based withholding calculation with recalculation when it exceeds the threshold limit.
  • Jurisdiction-dependent withholding percentage
  • Withholding calculation based on relationship between business unit and vendor
  • Ability to exonerate a vendor from withholding on a percentage basis.

Posted in Oracle Payable | No Comments »

Security : Oracle Audit Vault

Posted on August 15th, 2011 by Sanjit Anand ||Email This Post Email This Post

In security series, lets know another product.

Oracle Audit Vault is a security product that automates the consolidation of audit data into a secure repository, enabling efficient monitoring and reporting. This makes Oracle Audit Vault is a powerful solution providing a secure repository, built-in reporting, event alerting.This uses Oracle data security to protect audit data end-to-end. It helps to:

  • Consolidate and secure audit data from multiple instances of these databases – Oracle, Microsoft SQL Server, Sybase, IBM DB2.
  • Oracle Audit Vault is having out-of-the box compliance reports such as SOX, PCI and HIPAA requirements.
  • This also have entitlement reports for Oracle database to showing users, privileges and roles.
  • Policies can be created for SQL statements, schema objects, database privileges like alter, create, drop, grant etc.
  • Oracle Audit Vault raise alerts for suspicious activity on sensitive data like employee salaries, credit card numbers etc.
  • This have feature to capture before/after data value changes from Oracle database transaction logs.
  • Audit Vault can be administered and managed separately through Audit Vault server and Console

Oracle Audit Vault

Read the rest of this entry »

Posted in Oracle Application | 2 Comments »

« Previous Entries