Unit of measure conversions are numerical factors that enable you to perform transactions in units other than the primary unit of the item being transacted.
You can define:
A conversion common to any item (Standard)
A conversion for a specific item within a unit of measure class (Intra-class)
A conversion for a specific item between unit of measure classes (Inter-class)
A conversion for a specific item within a unit of measure class (Intra-class)
A conversion for a specific item between unit of measure classes (Inter-class)
- Unit of measure conversions are not organization-specific.
- You must define a conversion between a non-base unit of measure and the base unit of measure before you can assign the non-base unit of measure to an item
Specifying Which Conversion to Use
When you define an item you decide which type of unit of measure conversion to use:- Itemspecific: Only uses unit of measure conversions unique to this item. If none exist, you can only transact this item in its primary unit of measure.
- Standard: Uses standard unit of measure conversions for this item if an item-specific conversion is not available.
- Both: Uses both item-specific and standard unit of measure conversions. If both exist for the same unit of measure and item combination, the item-specific conversion is used.
Value Sets in Oracle Apps-Oracle Apps R12
Value Set as the name specifies refers to a set of values. Theses vales can be used to validate the values entered in a felx-field segment, concurrent program parameters and report parameters.
For Creating Value sets the user needs to navigate to a value set and specify the details of the value set.
The user needs to specify the name of the value set.
The main details that need to be entered are:
Name : The name of the value set
Architecture Overview:
Oracle Applications R12 is Three Tired, consisting of
- Desktop Tier
- Application Tier
- Database Tiers
Three Tier Architecture of Oracle Applications |
Desktop Tier :
This is usually any Desktop or a Browser enabled system, that an end user can use to navigate to Oracle applications. In general for accessing core oracle application forms, the Forms client applet must be run within a Java Virtual Machine (JVM) on the desktop client. The Sun J2SE Plug-in component allows use of the Oracle JVM on web clients, instead of the browser’s own JVM. Generally the JVM is installed as a browser Plugin.
Oracle Payments:
Oracle Payments Release 12 is a new, highly configurable product used to disburse and receive payments. It offers organizations
- · Centralized payment processing across Multiple organizations, currencies, and regions
- · Enhanced functionality to take advantage of new payment architecture
Oracle Payments is a fundamental part of the Oracle Applications architecture, and is provided with multiple products that requires support for payment processing. As the E-Business Suite’s new central payment engine, Oracle Payments processes invoice payments from Accounts Payable, bank account transfers from Oracle Cash Management, and settlements against credit cards and bank accounts from Oracle Receivables. Oracle Payments provides the infrastructure needed to connect these applications and others with third party payment systems and financial institutions. The centralization of payment processing in the Oracle Payments engine offers many benefits. Companies are able to efficiently centralize the payment process across multiple organizations, currencies, and regions. Oracle Payments enables better capital management by providing cash manager’s real-time visibility into cash inflows and outflows. Payments R12 provides a full audit trail and control through a single point of payment administration.
Setp1: Create XML Template
When you create a template, you assign it a data definition and upload your template layout files. Assigning the data definition makes the template available to the corresponding data source at run time.
Navigation: Parables --> Setup --> Payments --> Payment Administrator
General:
Name
|
Application
|
Type
|
Code
|
Data Definition
|
Start Date
|
End Date
|
Default Output type
|
Description
|
Test Standard Format
|
Payments
|
RTF
|
Test
|
Oracle Payments Funds Disbursement Payment Instruction Extract 1.0
|
13-Dec-2012
|
Template File:
File
|
Language
|
Territory
|
Translatable
|
IBYDC_STD1.rtf
|
English
|
Apply.
Define Bank:
You can define a bank or a clearing house. Define Banks to record internal banks, where you are the account holder of a receipt and/or disbursement account. If you use Payables, you can define external
banks where your suppliers are the account holders. Also, if you use Oracle Receivables, define banks to record external banks where your customers are the account holders of disbursement accounts. Define
Clearing Houses to record banks that process a magnetic tape of your receipt information which you send to them. These clearing institutions then create tapes of your customer receipt information which they forward to each of your remittance banks.
Setups for Defining the Banks
1.Define Grants and Roles:
Navigation: User Management --> Role & Role Inheritance.
Select the User Management Responsibility.
Click on Roles & Role Inheritance.
You can define a bank or a clearing house. Define Banks to record internal banks, where you are the account holder of a receipt and/or disbursement account. If you use Payables, you can define external
banks where your suppliers are the account holders. Also, if you use Oracle Receivables, define banks to record external banks where your customers are the account holders of disbursement accounts. Define
Clearing Houses to record banks that process a magnetic tape of your receipt information which you send to them. These clearing institutions then create tapes of your customer receipt information which they forward to each of your remittance banks.
Setups for Defining the Banks
1.Define Grants and Roles:
Navigation: User Management --> Role & Role Inheritance.
Select the User Management Responsibility.
Click on Roles & Role Inheritance.
1. Define Common Accounts Receivable Configuration
Common Accounts configuration pertains to the Accounting Flexfield setup. This is done in the General Ledger (GL) application. The assumption of this case study is that you have already defined your accounting flexfield segments, and can create and complete manual transactions using the Transaction Workbench.2. Manage Receivables Descriptive Flexfields
Oracle Receivables uses the transaction flexfields to uniquely identify each transaction line that is imported though AutoInvoice.AutoInvoice is capable of using information from four types of transaction flexfields:
- Line Transaction Flexfield
- Link-to Transaction Flexfield
- Reference Transaction Flexfield
- Invoice Transaction Flexfield
For this case study, you need to setup a Line Transaction Flexfield as shown below.
How to enable DFF on Customer form and add Segments-Oracle apps r12
By Jag - April 23, 2014
Background:
We got a requirement to add 2 fields on the customer page. This article explains how to add DFF segments on the Customer form.
Solution:
1. First find the DFF that is attached to the Customer form.
Application Developer > Flexfield > Descriptive > Register
Query for Table Name: HZ_CUST_ACCOUNTS
Make a note of Title. This is the DFF that is attached to the Customer form.
2. Application Developer > Flexfield > Descriptive > Segments
Query for Title: Customer Information > Uncheck Freeze Flexfield Definition > Save
We got a requirement to add 2 fields on the customer page. This article explains how to add DFF segments on the Customer form.
Solution:
1. First find the DFF that is attached to the Customer form.
Application Developer > Flexfield > Descriptive > Register
Query for Table Name: HZ_CUST_ACCOUNTS
Make a note of Title. This is the DFF that is attached to the Customer form.
2. Application Developer > Flexfield > Descriptive > Segments
Query for Title: Customer Information > Uncheck Freeze Flexfield Definition > Save
Define Values for Accounting Flexfield Segments-General Ledger
By Jag - April 23, 2014
What is a cross validation rule?
Cross-validation (also known as cross-segment validation) controls the combinations of values you can create when you enter values for key flexfields.
A cross-validation rule defines whether a value of a particular segment can be combined with specific values of other segments.
Solution:
Step1: Enable 'Cross-Validate Segments'
Login to user 'TATAUSER' created by us.
Navigation: Tata General Ledger Responsibility > Setup > Financials > Flexfields > Key > Segments
1. Query by entering following info
Application: General Ledger
Flexfield Title: Accounting Flexfield
2. Then again query for the Code 'Tata Coa'
3. Uncheck 'Freeze Flexfield Definition'
4. Check 'Cross-Validate Segments'
5. Check 'Freeze Flexfield Definition'
Step2: Create Cross Validation Rule and add a add a Include Rule
Navigation: Tata General Ledger Responsibility > Setup > Financials > Flexfields > Key > Rules
1. Query for Structure: Tata Coa
2. Under Cross-Validation Rules
Select Name, Description, Error Message as below
3. Under Cross-Validation Rule Elements
Create a Include Rule by selecting value 'Include' under 'Type'
Note: Every Cross-Validation Rule must have an 'Include' rule. An include rule is used to include all the combinations between the segments.
In the following screen we gave Company: 01 to 99 and Division: 00 to 99. This means that we've included all Companies and Divisions.
Cross-validation (also known as cross-segment validation) controls the combinations of values you can create when you enter values for key flexfields.
A cross-validation rule defines whether a value of a particular segment can be combined with specific values of other segments.
Solution:
Step1: Enable 'Cross-Validate Segments'
Login to user 'TATAUSER' created by us.
Navigation: Tata General Ledger Responsibility > Setup > Financials > Flexfields > Key > Segments
1. Query by entering following info
Application: General Ledger
Flexfield Title: Accounting Flexfield
2. Then again query for the Code 'Tata Coa'
3. Uncheck 'Freeze Flexfield Definition'
4. Check 'Cross-Validate Segments'
5. Check 'Freeze Flexfield Definition'
Step2: Create Cross Validation Rule and add a add a Include Rule
Navigation: Tata General Ledger Responsibility > Setup > Financials > Flexfields > Key > Rules
1. Query for Structure: Tata Coa
2. Under Cross-Validation Rules
Select Name, Description, Error Message as below
3. Under Cross-Validation Rule Elements
Create a Include Rule by selecting value 'Include' under 'Type'
Note: Every Cross-Validation Rule must have an 'Include' rule. An include rule is used to include all the combinations between the segments.
In the following screen we gave Company: 01 to 99 and Division: 00 to 99. This means that we've included all Companies and Divisions.
Oracle Apps Tutorial: Processing a Sales Order in Oracle Order Management
By Jag - April 22, 2014
The order process has 5 main steps. In these steps, you will enter an order, book the order, pick the order, ship the order, and then close the order. Since Order Management relies heavily on the workflow technology, I will show you the workflow status for each step along with the order and line status. Below is a summary of the status for each step:
Step | Order Header Status | Order Line Status | Order Flow Workflow Status (Order Header) | Line Flow Workflow Status (Order Line) |
---|---|---|---|---|
1. Enter an Order | Entered | Entered | Book Order Manual | Enter – Line |
2. Book the Order | Booked | Awaiting Shipping | Close Order | Schedule ->Create Supply ->Ship – Line |
3. Pick the Order | Booked | Picked | Close Order | Ship – Line |
4. Ship the Order | Booked | Shipped | Close Order | Fulfill – Deferred |
Booked | Closed | Close Order | Fulfill ->Invoice Interface ->Close Line -> End | |
5. Close the Order | Closed | Closed | End | End |
Step 1. Entering an Order
Let’s assume that all the master data (customers, items) have been entered and that the basic Order Management configuration is in place. To enter the order header information, you will need to know :
1. Your customer’s name or number