Category Archives: Apps Functional Modules

Issuing Miscellaneous Receipt

Create stock for item using Miscellaneous Receipt

Navigate to Inventory > Transactions > Miscellaneous Transaction, and enter the following information:
Type : Miscellaneous receipt
Click on the Transaction Lines button


Save the Record after entering the Quantity:



Check the On Hand Quantity by Navigating to Inventory –> On-hand, Availability –> On-hand Quantity :


Check the Availability:


Inventory Organization Overview

Inventory Organization Overview

Let us see the basic structure of the definition of an inventory organization by looking at the data already defined in the Vision database.
Note: Do not change any data we see below.
Change the Responsibility to Inventory and Navigate to Setup –> Organizations –> Organizations.

Query by the name ‘Seattle Manufacturing’. This is the organization (organization code M1) we commonly use in the Vision Database to create Inventory transactions, including shipment of sales orders. Notice the entry ‘Inventory Organization’ under Organization Classifications. Place the cursor on that row, and click on the button Others.


Select ‘Accounting Information’ from the list.

  • Place cursor anywhere in the Accounting Information field to see details.
  • Notice this is where the organization is associated with its ‘Set of Books, Legal Entity and Operating Unit’.
  • The concept of Operating Unit will often come up, so it is good to know where this relationship is defined, ie. which Operating Unit the Inventory Organization (warehouse) belongs to.
  • Close the Accounting Information window and Additional Organization Information screen.



Place the cursor on the classification Inventory Organization again, click on the Others button and select ‘Inventory Information’ from the list.

  • Notice this is where the Inventory organization parameters are defined.
  • This screen can also be accessed directly from Inventory > Setup > Organizations > Parameters.
  • Notice this is where the organization code ‘M1’ is specified, and the Item Master Organization is specified as ‘Vision Operations’ (V1). This sets the relationship for Seattle Manufacturing (child org) and Vision Operations (master org).



As an optional step, you can query the organization ‘Vision Operations’ and check that it is classified as both a Legal Entity and Operating Unit as well as an Inventory Organization. If you check the Inventory Organization Parameters for ‘Vision Operations’ you will notice that the organization code is defined as ‘V1’. The master org is itself.

As another optional step, you can go to Edit > Preferences > Profiles, and run a query with the profile name ‘MO:%’. You will see the value for the profile option ‘MO: Operating Unit’ being ‘Vision Operations’. This is the Operating unit in which the OM transactions are created when logged into the responsibility used in this testflow (for R11i).

Reference: oracle metalink


Create Purchasable Item


Create a New Item used in Order to Cash Flow

Create an item that will be entered in the sales order.

Change the Responsibility to Inventory and Navigate to Items –> Master Items:

When Prompted select the Organization as V1 or M1 which is the Master Organization. Even when M1 is selected which is an inventory Org V1 would be displayed for creating the Item in the Master Org. We want to create the item in M1 and the ship the item from M1.

Enter a name for the Item and Description as shown below.


Go to Tools –> Copy From.
Select the Template ‘Purchased Item’.
Click on ‘Apply’ and then click on ‘Done’.



The seeded template ‘Purchased Item’ will assign the necessary item attributes to go through this basic OM testflow. For example, check some of the following item attributes that you did not need to set manually because they were assigned from the template.

Got to Inventory tab and we can see Inventory Item, Stockable, Transactable, Reservable flags are checked.
Go to Order Management tab  (click on the arrow to the right of all the tabs) and can see
Customer Ordered, Customer Orders Enabled, Shippable, OE Transactable flags are enabled Automatically by selecting the Template.

So far defined the item in the Item Master Organization, V1. Next, go to Tools > Organization Assignment. Alternatively, click on the 3rd tab on the left side of the screen as circled in red in the below screenshot.

This is where you will find a list of organizations (child organizations) that have V1 as their master organization. M1 shows at the top if we have selected M1 while changing the Organization while creating the Master Item. The item attributes defined in V1 can be assigned to the child organizations by checking the Assigned box.


We can use the Assign All button to Assign the Items to all the Inventory Organizations. Check the Assigned box as shown above for the organization M1. Items needs to be enabled in the organizations in which they will be transacted.

Use the below SQL to Check the Details:

Finding the organization code of the organization_id’s from Inventory parameters using below SQL:

The item attributes can be changed at each individual child organization level by clicking on the Org Attributes button in the screenshot above, or by going to Inventory > Items > Organization Items. Note, however, that this depends on whether the item attribute is controlled at the master org level or the child org level, which is defined in Inventory > Setup > Items > Attribute Controls.



Create Customer

Create a New Customer

Navigate to Order Management Super User Vision Operations responsibility and Customers –> Standard.


Enter a new customer name in the Name field, and press Find.
If the customer name already exists, go back and enter a name that does not already exist.  Press the ‘Create’ button.


Enter the Customer Information as shown:


Enter the Account Information as shown:


Enter Account Site Address:


Enter Account Site Details:


Save and Add details:


Create a New Organization:


Note: If we have any issue while create a New customer regarding the Amounts then we need to setup the Profile Amounts from Receivables Vision Operations Responsibility and navigate to Customers –> Profile Classes and Modify the Amounts for the Profile class given at Customer Creation. As we took it as DEFAULT we intent to modify the Amounts as shown below:


Save the Profile class.

Once added we can Modify the Customer to add Ship to Site:


Goto Site details:


and Navigate to Business Purpose and Add a New Row as Ship To so the same address is used for both Shipping and Billing.


Notice the ‘Open’ button in the above screenshot. This is where you can enter additional details specific to the business purpose. So, if the cursor is on the ‘Ship To’ row as seen here, clicking on Open will allow to enter information specific to the Ship To Location. This can be examined further in the Defaulting Rules section.

Make Both Purposes or Site Uses as Primary by Checking the Primary Flag and click on Apply:


After this we can see the Site has both Ship To and Bill To as its Sites Uses and New record is inserted in HZ_CUST_SITE_USES_ALL.


Oracle Trading Community Architecture (TCA)

Oracle Trading Community Architecture (TCA)

Oracle Trading Community Architecture (TCA) is a data model that allows you to manage complex information about the parties, or customers, who belong to your commercial community, including organizations, locations, and the network of hierarchical relationships among them using the TCA registry.

TCA registry is the single source of trading community information for Oracle E-Business Suite applications which provide user interfaces, batch data entry functionality, and other features to view, create, and update Registry information.

TCA key entities:

Parties:  Parties are the entities of type person/organization that enter into a business relationship

Party Sites: Addresses of the parties

Customers: Parties with whom you have a selling relationship

Customer Accounts: The business relationships between you and your customers

Customer Account Sites: Address of the party used in the case of customer accounts

Locations: Geo-spatial points, usually defined by an address

Contacts: People who have a contact or employment relationship with an organization or person

Contact Points: Means of contact, for example, phone and e-mail address

Process Flow:

This diagram shows the process flow for managing, searching, creating, and updating customer information.

R12 Trading Community Architecture:

Includes following new trading entities:

  • Bank and Bank Branches
  • Customers
  • Suppliers

TCA-Bank and Bank Branches:

The TCA tables used by Cash Management for modeling Banks and Bank Branches are listed below:

Three key CE tables now as:

    • CE_BANK_ACCOUNTS for bank accounts
    • CE_BANK_ACCT_USES_ALL for account uses by Operating Units & Legal Entities
    • CE_GL_ACCOUNTS_CCID for bank account use accounting data


The word “Customer” is the combination of both the “Party layer” and the “Account layer”.

  • Party layer exists independent of any selling or buying relationship.
  • Customer Account layer exists in the context of a Party and only when a selling      relationship exists.
  • The Party Layer captures intrinsic truths about a person or organization.
  • The Account Layer captures the details describing the Party’s financial relationship with the implementing organization.
  • The Account Layer cannot exist without the Party Layer.


Following are the three new AP tables’ technical details for R12 Supplier in TCA. They have the links to TCA tables which are listed below.


TCA ER-Diagram:




Related posts: