Oracle Receivables Transaction Types R12

Below post will give details about Transaction Types in Oracle Receivables R12. We have consolidated the information provided here from various sources and our self learning .        
                                                                                       

In which order Transaction types have to be defined?

1.       Credit memo

2.      Invoice

3.      Debit memo

4.      Chargeback

5.      Deposit

6.   Guarantee

How to define Transaction types in Receivables?

Navigation:

Example Invoice Transaction Type Screen:

Example Credit MemoTransaction Type Screen:

Details about the columns given in the above screens:

Fields	Description
Class	Categorize transaction types by assigning them to a class of Invoice, Credit Memo, Debit Memo, Deposit, Guarantee, or Chargeback. Transaction types are displayed in windows as lists of values
Creation Sign	Positive, Negative, or Any Sign for initial sign of transaction. Positive required for guarantees and deposits
Transaction Status	Assign a status of Open, Closed, Pending, or Void to this transaction Note: When creating transactions via Autoinvoice, even if  you use a transaction type that is setup with  Transaction Status = Closed, once the data is interfaced, it will have an OPEN status. “Autoinvoice does not provide a feature to interface CLOSED or INCOMPLETE transactions”.
Printing Option	Specify whether to print transactions with this transaction type
Terms	default payment terms for this transaction, this field  is disabled when Class is Bills Receivable or Credit memo
Open  Receivable	Select this check box to have transactions update customer balances and aging reports. Required for  deposits and guarantees. This simply indicates whether this transaction's balance impacts a Customer's Receivable balance
Post to GL	Select this check box to post transactions with this transaction type to the Oracle General Ledger. Required for deposits and guarantees
Allow Freight	indicates whether or not you can associate freight to this transaction type
Default Tax  Classification	defaults tax classification code for this transaction. This value is only relevant in release 11.5 or a release 12 instances that are using E-business tax setups defaulted from an upgraded release 11.5 instance
Natural Application Only	Restrict the direction in which invoices, debit memos, deposits, guarantees, credit memos, and on-account credits can be updated by applications entered against them. Natural application does not apply to adjustments and chargebacks. If Natural Application Only is selected, clear the Allow Overapplication check box
Allow Over application	Allow items to be overapplied. Check box defaults to cleared for guarantees and deposits. If this check box is selected, clear Natural Application Only check box. In other words, activities against this transaction can cause the sign of the balance to change Example: an original positive amount ($150), can change to negative amount (-$50) due to receipt applications
Interaction between “Natural Application Only” and “Allow Over application”	"Natural Application Only" Checked and "Allow Overapplication" Not Checked Oracle Receivables allows any application, other than adjustments and chargebacks, that reduces the transaction amount toward or to zero without changing the sign of the transaction.  "Natural Application Only" Unchecked and "Allow Overapplication" Checked or Unchecked Oracle Receivables allows any application that reduces or increases the transaction, even if the application changes the sign of the transaction.
Receivable  and Revenue  accounts	for all classes of transaction types
Freight Account	if Allow Freight is selected and the transaction type class is set to Invoice, Debit Memo, Credit Memo, or Chargeback.
Clearing Account	if the transaction type class is set to Invoice, Debit Memo, Credit Memo, or Chargeback. The account holds differences between the revenue amount and selling price (pro-rated discounts from Oracle Order Entry).
Unbilled Account	if the transaction type class is set to Invoice, Debit Memo, Credit Memo, or Chargeback. Used when billing in arrears
Unearned Account	if the transaction type class is set to Invoice, Debit Memo, Credit Memo, or Chargeback. Used when billing in advance.
Tax Account	if Tax Calculation is selected and the transaction type class is set to Invoice, Debit Memo, Credit Memo, or Chargeback

Payables Open Interface Import Parameters

 Payables Open Interface Import Parameters

In this below post, I had published information about the parameters related to “Payables Open Interface Import” Program. Info from R12.1.1 instance.

Mandatory Parameters:

1.       Source: It can be any of the below list

Ø      Invoice Gateway - Invoice records you entered in the Invoice Gateway window

Ø      E-Commerce Gateway- Supplier invoices transferred through EDI

Ø      Credit Card- Procurement cards transactions from the credit card issuer

Ø      Oracle Property Manager- Lease invoices from Oracle Property Manager.

Ø      Oracle Assets- Lease payments from Oracle Assets.

Ø      User-defined- For invoice loaded from legacy Systems

2.       Invoice Batch Name

Ø      Use Batch Control Payables Profile option need to be enabled to use this parameter

Ø      Payables groups the invoices created from the invoice records you import and creates an invoice batch with the batch name you enter

Ø      While Re-importing the error invoices make sure the batch name remains the same

Optional Parameters:

3.       Operating Unit: Filtering predicate when null import program process invoice from all operating units.

4.       Hold Name: When this parameter is provided with the hold name, then the import program creates the invoices and blocks them with mentioned hold.

5.       Hold Reason: Corresponds to Hold Name

6.       GL Date: This value is used as a GL date for the invoices whose GL_DATE columns in interface tables are not populated.

7.       Purge. Enter Yes if you want Payables to delete from the Payables Open Interface tables all successfully imported invoice records that match the Source and Group ID of this import

8.       Summarize Report: Provides a Summarize report when ‘YES’

PROFILE OPTIONS IN ORACLE APPS R12 - OVERVIEW (FND PROFILE)

Definition:

Profiles are the changeable options which affect the way Oracle Application runs. Moreover, Moreover, The profile option acts like a Global Variable in Oracle. It is needed to provide the flexibility to Oracle Applications.

Types:

The profiles are of two types those are given below.

1. System Profile and

2. User Profile.

About DIFFERENT LEVELS a Profile value can be set:

The Profile values will be set in different levels those are given below.

1. Site

2. Application

3. Responsibility

4. User

5. Server

6. Organization

Site: This field displays the current value, if set, for all users at the installation site.

Application: This field displays the current value, if set, for all users working under responsibilities owned by the application identified in the Find Profile Values block.

Responsibility: This field displays the current value, if set, for all users working under the responsibility identified in the Find Profile Values block.

User: This field displays the current value, if set, for the application user identified in the Find Profile Values block.

Profile: Enter the name of the profile option whose values you wish to display.

Navigation to set Profile Values

 SYSTEM PROFILE: 

Responsibility SYSTEM ADMINISTRATOR -->

You may search for profile options using character strings and the wildcard symbol (%). For example, to find all the profile options prefixed by "Concurrent:” you could enter "Conc%" and press the Find button.

  

PERSONAL PROFILE:

Responsibility SYSTEM ADMINISTRATOR -->

To view personal profiles enter into the query mode and enter the profile name which we have already then we get profile value details.

To check the validation done against the Profile value while setting:

Responsibility APPLICATION DEVELOPER -->

Use of the API FND_PROFILE

It is used to perform various actions related to profile values through PL/SQL. Some of the important ones are listed below

1. FND_PROFILE.GET(‘Name of the Profile’, variable name);

Example

SELECT fnd_profile.value('PROFILEOPTION')

      ,fnd_profile.value('MFG_ORGANIZATION_ID')

      ,fnd_profile.value('ORG_ID')

      ,fnd_profile.value('LOGIN_ID')

      ,fnd_profile.value('USER_ID')

      ,fnd_profile.value('USERNAME')

      ,fnd_profile.value('CONCURRENT_REQUEST_ID')

      ,fnd_profile.value('GL_SET_OF_BKS_ID')

      ,fnd_profile.value('SO_ORGANIZATION_ID')

      ,fnd_profile.value('APPL_SHRT_NAME')

      ,fnd_profile.value('RESP_NAME')

      ,fnd_profile.value('RESP_ID')

  FROM DUAL;

2. variable name := FND_PROFILE.VALUE(‘Name of the profile’);

3. FND_PROFILE.PUT(‘Name of the profile’, value of the profile);

Example

SET SERVEROUTPUT ON;

DECLARE

   v_conc_login_id      NUMBER;

BEGIN

   FND_PROFILE.put ('CONC_LOGIN_ID',1425);

   fnd_profile.get ('CONC_LOGIN_ID', v_conc_login_id);

   DBMS_OUTPUT.put_line (v_conc_login_id);

END;

Output:

1425

PL/SQL procedure successfully completed

The 1st and 2nd are same but, the only difference is FND_PROFILE.GET is the procedure and FND_PROFILE.VALUE is the function so, it return a value.  

Apart from the above procedures we have another important one named FND_PROFILE.SAVE used to set the profile values from backend. A detail regarding this API is available in another article. 

The table fnd_profile_options_tl, profile options names are kept.  Now find the corresponding the Profile option name for which you need to update from backend. For this example I took my favorite “ORG_ID”

SELECT profile_option_name
  FROM fnd_profile_options_tl
 WHERE user_profile_option_name LIKE 'MO%'

It returns more than one row but i can make out that "ORG_ID" is the PROFILE_OPTION_NAME for MO: Operating Unit. Now I need to know the Org_ID of the Org whose value is to be set in MO: Operating Unit. SO I use the simple select as below

SELECT organization_id, NAME
  FROM hr_all_organization_units;

From the organization name I find the one which will be the default Operating Unit, and I note the ID. In my case the ID for my default Operating Unit is 286. Now with the code below I set the profile option value using fnd_profile.save.

DECLARE
   stat   BOOLEAN;
BEGIN
   DBMS_OUTPUT.DISABLE;
   DBMS_OUTPUT.ENABLE (100000);
   stat := fnd_profile.SAVE ('ORG_ID', 286, 'SITE');
   IF stat
   THEN
      DBMS_OUTPUT.put_line ('Stat = TRUE - profile updated');
   ELSE
      DBMS_OUTPUT.put_line ('Stat = FALSE - profile NOT updated');
   END IF;
   COMMIT;
END;

TRADING COMMUNITY ARCHITECTURE (TCA) API’S IN R12 ORACLE APPS

Below give you the list of Trading Community Architecture API’s with the links to their test script. All the test scripts are tested in R12.1.1 Version.

SI NO	Tested API's List
1	HZ_CUST_ACCOUNT_V2PUB.CREATE_CUST_ACCOUNT
2	HZ_CUSTOMER_PROFILE_V2PUB.CREATE_CUSTOMER_PROFILE
3	HZ_CUST_ACCOUNT_SITE_V2PUB.CREATE_CUST_ACCT_SITE
4	HZ_CUST_ACCOUNT_SITE_V2PUB.CREATE_CUST_SITE_USE
5	HZ_PARTY_SITE_V2PUB.CREATE_PARTY_SITE
6	HZ_PARTY_SITE_V2PUB.CREATE_PARTY_SITE_USE)
7	HZ_CONTACT_POINT_V2PUB.CREATE_CONTACT_POINT
8	HZ_LOCATION_V2PUB.UPDATE_LOCATION
9	HZ_CUST_ACCOUNT_V2PUB.UPDATE_CUST_ACCOUNT
10	HZ_PARTY_V2PUB.CREATE_GROUP
11	HZ_CUST_ACCOUNT_V2PUB.CREATE_CUST_ACCOUNT
12	HZ_CUST_ACCOUNT_V2PUB.CREATE_CUST_ACCOUNT
13	HZ_LOCATION_V2PUB.CREATE_LOCATION
14	HZ_TAX_ASSIGNMENT_V2PUB. CREATE_LOC_ASSIGNMENT
15	HZ_CUST_ACCOUNT_V2PUB.UPDATE_CUST_ACCT_RELATE
16	HZ_CUSTOMER_PROFILE_V2PUB.UPDATE_CUSTOMER_PROFILE
17	HZ_PARTY_V2PUB.CREATE_ORGANIZATION
18	HZ_CUST_ACCOUNT_V2PUB.CREATE_CUST_ACCT_RELATE
19	HZ_PARTY_CONTACT_V2PUB.CREATE_ORG_CONTACT