Tuesday, December 04, 2012

fnd_global.apps_initialize 11i, R12 and SQL

fnd_global.apps_initialize
In Oracle E-Business Suite, it becomes necessary to do this call when an API is called or SQL Query is run from
SQL Plus/TOAD like tools. This ‘fnd_global’ API calls sets the environment properly so that SQL Queries specific to few key base tables return rows back.
This ‘fnd_global’ API call has 3 key parameters
fnd_global.apps_initialize (user_id, responsibility_id, responsibility_application_id)
******************************************************************************
For example, in SQL Plus, this can be called as shown below:

Exec fnd_global.apps_initialize(125,400,700);
Where,
125 – user_id from fnd_user table
400 – responsibility_id from fnd_responsibility table
700 – application_id from fnd_application table
******************************************************************************
Release 12
begin
fnd_global.apps_initialiase(user_id, responsibility_id, responsibility_application_id );
mo_global.set_org_context(81,NULL,'SQLAP');
end;
 ******************************************************************************
Oracle 11i
BEGIN
fnd_global.apps_initialize(user_id, responsibility_id, responsibility_application_id);
END;
 ******************************************************************************

Tuesday, October 09, 2012

Parallel Pick Release in Oracle Shipping - R12 New Feature

Oracle has introduced lots of features in R12 (e-business Suite). 
It includes Parallel Pick Release:

With this feature user can now run the Pick Release processes in parallel and improve the over all performance.

Advantages:

One of Key Advantage of with Parallel Processing of the Pick release process is user can apply /engage additional (if available) resources to process the Pick release data that was previously process by 1 process only and hence save lot of time by submitting this process in Parallel.

Following are the changes made for this feature:
  • A new Parameter (No. Of Child Processes) has introduced in Pick release Concurrent Program.
  • A new profile option (WSH: No. Of pick release child processes) has introduced , it indicate how many child processes you want to spawn.

Note: If we run the Pick release from in Online Mode or Public API (online mode) then only 1 child processes to be spawned ( as good as existing behavior).

Some Constraints -

Irrespective of the parameter value and the profile option only 1 child process will be spawned if
1. Auto Create Delivery = Y and print Pick Slip is set as Immediate
2. Auto Create Delivery = Y and Delivery is enabled as Pick slip Grouping rule.

Setup

WSH: No. Of pick release child processes.
If value of this profile option is Null or 1 then only 1 Child Process will be submitted.
If value of this profile option is > = 2 (2 to 'n') then 'n' no. of Child Process will be submitted for Pick release ( some restriction applied , as discussed below).

By setting this profile option to any value doesn’t mean system will spawned that many child process. The # of child process spawned depend upon this profile option as well as the Unique item in the data SELECTED for the pick release.

Or more precisely we say No. of child process available for Pick release depend on the # of unique “Item and Organization “ combination.

Concurrent Program:

As explained earlier a new Parameter (No. of Child Processes) has been introduced in concurrent Program “ Pick Selection List Generation – SRS”. 





No. of child processes spawned are depend on the value you enter in this parameter , and by default value from the Profile option “WSH: No. of pick release child processes” defaulted for this parameter , but here we have advantage to overwrite the value of profile.


Note - # of pick slip reports not depend on this profile options, they still depend on the pick slip Grouping rules.

Other Considerations:
  • If we submit the pick release process from the Shipping Transaction UI, then only 1 process will be launch, parallel Pick release will not applicable, but if we launch the Pick Release process from Shipping transaction UI , Tools > then the Parallel Pick release Process will work fine.
  • In SRS window, all the child process will carry the Parent Request ID of the parent.
----------------End--------------

Monday, October 08, 2012

Inventory Setup for Intercompany Invoicing

Intercompany Invoicing Inventory Setup Information

Steps to Implement the Multiple Organization Support

1. Develop the Organization Structure
2. Define Ledger and GRE/Legal Entity
3. Define Organizations
4. Define Organization Relationships
5. Define Responsibilities
6. Set the Operating Unit Profile Option for Each Responsibility
7. Convert to Multiple Organization Architecture
8. Define Inventory Organization Security (optional)
9. Change Order Entry Profile Options (optional)
10. Update Profile Options Specific to Operating Units
11. Implement the Applications Products
12. Secure Balancing Segment Values by Legal Entity (optional)
13. Run the Setup Validation Report (recommended)

Prerequisites to Using the Intercompany Invoicing Process

1. Define your intercompany relations.
2. Define your Oracle Receivables system options.
3. Define your Oracle Payables system options.
4. Define your tax structures in Oracle Payables and Oracle Receivables.
5. Set up the Account Generator for the Cost of Goods Sold accounts.

Inventory Setup Confirmation Steps

1. Verify Set of Books, Legal Entity, & Operating Unit:
A) Navigation: Inventory-> Setup-> Organizations
B) Select the particular organization in question (Both organizations, i.e. Japan, US).
C) Select the Inventory Organization under "Organization Classifications" and click on the "Others" button.
D) Select "Accounting Information".
E) Open up the "Additional Organization Information".
F) "Accounting Information" flexfield will open with Set of Books, Legal Entity, and Operating Unit.
G) Confirm that the information in these fields is accurate and relevant to the particular organizations involved in the Intercompany process.

2. Intercompany Relations Defined:
A) Navigation: Inventory-> Setup-> Organizations-> Intercompany Relations
B) Confirm the Operating Units:
Shipping:
Selling:
C) AR Invoicing for Shipping:
Customer:
Number:
Location:
Transaction Type:
D) AP Invoicing for Selling:
Supplier:
Site:
Freight Account:
E) Revalue Average:

3. Verify Ledger:
A) Navigation: Inventory-> Setup-> Financials-> Books
B) Select the particular Ledger
C) Chart of Accounts defined
D) Functional Currency defined
E) Accounting Calendar defined

4. Verify Currency Codes:
A) Navigation: Inventory-> Setup-> Financials> Currencies-> Currency Codes
B) Ensure that the currency codes used are active and have not been disabled (Scroll to the right)

Profiles Options:

1. Consistent Profile Option Values:
All responsibilities in one operating unit must share the same profile option values and the same sequence numbering option. The Validation Report indicates an error if this is not the case, and notes when profile options should be set at the responsibility level.
2. HR:Business Group
This section applies to you only if you have multiple business groups, or if you do not choose to use the default business group provided by Oracle Applications.

If you have multiple business groups, you must associate each responsibility with one and only one business group. You associate a responsibility with a business group via the HR:Business Group system
profile option. If you are upgrading to Multi-Org, you must also associate each existing responsibility with a business group.

After you have associated business groups with responsibilities, you can enter business group setup information such as additional organization information and business group classifications.

If you have multiple business groups, verify the HR:Business Group profile option before you define organizations in each business group.

3. MO:Operating Unit
You must set the MO:Operating Unit profile option for each responsibility.
Set this profile option to the appropriate operating unit id (ORG_ID) for each responsibility. The operating unit context for each responsibility is set via this profile option.

This profile option must be set for Oracle Training Administration (OTA) responsibilities when OTA is used in a Multi-Org environment. This is to ensure that the OTA customer and supplier functions work correctly in a Multi-Org environment.

You must also define the default operating unit by setting the MO:Operating Unit profile at the site level. If this is a fresh installation, the default operating unit can be any operating unit you have defined. If this is an existing installation, you should assign as the default operating unit the operating unit to which all existing data should belong.

4. The following profile options affect the operation of the Create Intercompany AR Invoices process:
a) INV: Intercompany Currency Conversion
Determines the conversion type for foreign currency invoices.

b) Tax: Allow Override of Tax Code
Determines whether tax code information should be passed to AR for freight.

c) Tax: Invoice Freight as Revenue
Indicates whether freight lines should be invoiced as revenue lines.

d) Tax: Inventory Item for Freight
Use this inventory item when freight lines are invoiced as revenue lines.

e) OE: Item Validation Organization
Inventory organization in which the freight item specified in the profile
Tax: Inventory Item for Freight is defined.

5. OE:Item Validation Organization
The OE:Item Validation Organization profile option determines the inventory organization that Order Entry uses to validate items. Some inventory item attributes for Receivables and Order Entry, including
Tax Code and Sales Account, are specific to an operating unit or an accounting flexfield structure. Therefore, you should use the OE:Item Validation Organization profile option to define an item validation organization for each operating unit.

NOTE: Profile OE:Item Validation Organization is no longer used from 11.5.x forward. Instead a system parameter in order management is used to set the OM (order management)item validation org.
Responsibility: Order Management Super User
Navigate to: Setup > System Parameters > Values
Select the applicable operating unit (for instance: Vision Operations)
Select the category as Generic Parameters
Review the line for parameter = Item Validation Organization

Also, it is important that profile QP: Item Validation Organization is set to the same value as defined for the OM system parameter for item validation.

6. Update Profile Options Specific to Operating Units
Use the Update System Profile Options window to set profile options that are specific to each operating unit. You must set these profile option values for all relevant responsibilities that connect to each operating unit.

Some profile options, including AR:Receipt Batch Source and AR:Transaction Batch Source, reference data that is secured by operating unit. You must set these profile options at the responsibility level.

For profile options that need to differ at the operating unit level, including OE:Item Validation Organization, OE:Set of Books, and GL Set of Books, you must set the values at the responsibility level. Oracle General Ledger windows use the GL Set of Books profile option to determine your current set of books. If you have different sets of books for your operating units, you should set the
GL Set of Books profile option for each responsibility that includes Oracle General Ledger windows.

For profile options that need to differ at the set of books level, including Sequential Numbering, set the values at the responsibility level.

Profile options specify default values that affect system processes, system controls, and data entry. In a multiple organization environment you may want to confine the effect to a specific operating unit. Therefore, you may want to change your profile options to be visible and updatable at the responsibility level.


-----------------End--------------- 

Profile Options used by Intercompany


  1. INV: Always suffix inter-Company AP Invoice number
  2. INV: Intercompany Currency Conversion
  3. INV: Intercompany Transfer Price Date
  4. INV: Use Intercompany AR Tax for inter-Company AP
  5. INV:Advanced Pricing for Intercompany Invoice
  6. INV:Intercompany Invoice for Internal Orders
  7. INV: Use Model & Options for Configuration Pricing
  8. TAX: Inventory Item for Freight
  9. TAX: Invoice Freight as Revenue
  10. TAX: Allow Override of Tax Code
  11. QP: Item Validation Organization
  12. QP: Pricing Transaction Entity
  13. QP: Source System Code
  14. CST: Transfer Pricing Option

------------------End------------------------

Friday, September 28, 2012

How to Enable Personalization link in OAF Pages (Web page)

Set the values of following profiles (site) to enable Personalization page link to OAF (Web) page.

Sl No:Profile Name Profile Value set to Site level
1FND: Personalization Region Link EnabledYes
2Personalize Self-Service DefnYes
3Disable Self-Service PersonalNo





When you click Personalize Page and update the Personalize




Click update and do accordingly as per client requirement



---------------------------------------------

Thursday, September 27, 2012

What is the difference between spot, corporate, user, and fixed rate types?

Using Rate Types: Examples

There are four seeded conversion rate types in Oracle Fusion applications:
  • Spot
  • Corporate
  • User
  • Fixed
 Spot, corporate, user, and fixed conversion rate types differ based on the fluctuations of your entered foreign currency and your company procedures for maintaining daily rates.

Rate Type Usage
Spot For currencies with fluctuating conversion rates or when exact currency conversion is needed.
Corporate For establishment of a standard rate across your organization for a stable currency.
User For infrequent entries where your daily rates for the entered foreign currency are not set up.
Fixed For rates where the conversion is constant between two currencies.

If you have infrequent foreign currency transactions, the user rate type can simplify your currency maintenance while providing an accurate conversion rate on the date of the transaction.

Scenario

You are the general ledger accountant for In Fusion America Inc. You are entering a journal entry to capture three transactions that were transacted in three different foreign currencies:
  • Canadian dollar (CAD): A very stable currency
  • Mexican Peso (MXP): A fluctuating currency
  • Hong Kong dollar (HKD): An infrequently used currency
You enter two lines with accounts and amounts for each foreign currency transaction. Based on your company procedures, you select the appropriate rate type to populate the rate for Corporate and Spot rate types from your daily rates table. You manually enter the current rate for the User rate type.

Currency Selected Rate Type Selected Reason
CAD Corporate Entered a periodic type of transaction. Your company has established a daily rate to use for the entire month across divisions for all transactions in CAD. CAD is a stable currency that only fluctuations slightly over the month.
MXP Spot Entered a periodic type of transaction. Your company enters daily rates each day for MXP because this currency is unstable and fluctuates.
HKD User Entered a one time transaction. Your company does not maintain daily rates in HKD.

Note
Your company does not currently use the Fixed rate type. From January 1, 1999, the conversion rate of the French franc (FRF) against the euro currency (EUR) was set at a fixed rate of 1 EUR to 6.55957 FRF. Your French operations were started in 2007, so you maintain all your French business records in the EUR.

Soft Reservation and Hard Reservation in Oracle Sales Order

By definition "Soft Reservation"

  • Sales order demand is a soft reservation.
  • When you are entering sales order go to tools and check the "reserve" that is soft reservation.
  • In Planning parameter form not enabled the check box Net reservation, the planning process considers all Sales Order demand as soft reservation.
  
"Hard Reservation"

  • Hard reservation is sales order demand that you *firm * by reserving selected inventory for the purposes of material planning.
  • Available to promise (ATP) calculations and customer service issues. 
  • In the planning parameter form whenever you enable the check box  Net reservations, the planning process satisfy hard reservation demand before soft reservations.
  • Further we have to set Pegging Method under MPS/MRP planning tab.
  • If the order is pick released for the customer that is hard release.

 -------------------------------------------