Sunday, December 23, 2012

Accounts Payables Accounting Flow

Accounts Payables Accounting Flow

Below are few of the key concepts about Accounts Payables Accounting. Accounts Payables have multiple Flows which will be elaborated below. Even though the accounting engine has been moved to Sub Ledger accounting in r12, the Core Concepts of Payables accounting remain same.

Standard Accounts Payable Invoice/ Payment Accounting

One of the most commonly seen scenarios in Accounts payables is Standard Invoice and Payment. Below are the accounting entries for them

Standard invoice creation:

               Dr. Expense / Item Expense / Misc. Expense
                              Cr. Supplier / Liability

The “Expense / Item Expense / Misc. Expense are derived from the Payables Invoice Distribution where as “Supplier / Liability” Account id derived from Supplier’s Site, from the liability account code combination on that particular site. Although the liability account is defaulted from Payables’ Financial Setup, but you can change the account code according to your need. We can even change the liability account code combination on the Invoice Workbench by enabling the Column from Folders option.

Payment of the Standard invoice:

               Dr. Supplier / Liability
                              Cr. Bank / Cash / Cash Clearing

Now comes the payment, the liability account is fetched from the supplier whose invoice is being paid, the cash clearing or cash account is fetched from the bank you select during the payment. This account is defined during the Bank Account Setup.

PREPAYMENTS / ADVANCES:

Prepayment Invoice creation:

Dr.  Prepaid Expense / Advance Paid
               Cr. Supplier / Liability

Prepayment invoice Payment:

               Dr. Supplier / Liability
                              Cr.  Bank / Cash / Cash Clearing

Standard Invoice creation:

               Dr. Expense / Item Expense / Misc. Expense
                              Cr. Supplier / Liability

Prepayment Application to Standard invoice

               Dr. Supplier / Liability
               Cr. Prepaid Expense / Advance Paid

INVOICES with “TRACK AS ASSETS”:

Track as Asset” is a functionality for moving the items from Oracle Payables to Oracle Assets. It is a check box on the Invoice Line TAB and can be enabled on Distribution Line using the Folder View option. When you check this box and run the “Mass Addition Create Report” from Payables, the items on invoice line or distribution line moves to Oracle Assets. 

Invoice creation:

Dr. Asset Clearing
                              Dr. Supplier / Liability

Invoice transferred to oracle Assets:

               Dr. Asset
                              Cr. Asset Clearing

INVOICE with WITHHOLDING TAX

In the Payables invoices with Withholding tax Scenarios, accounting entry for the WHT payables or Liability account is selected from the supplier defined as a Tax Authority. The WHT expense is picked from the WHT setup.
Taking an example of withholding at time of Payment

Invoice Creation:

Dr. Expense / Item Expense / Misc. Expense
                              Cr. Supplier / Liability

Payment with Withholding Tax 

               Dr. Supplier / Liability
                              Cr. Bank / Cash / Cash Clearing
                              Cr. Withholding Tax

WITHHOLDING TAX INVOICE

               Dr. WHT Expense

                              Cr. Withholding Liability

Monday, October 1, 2012

Legal Entity in R12

Legal Entity:
Legal Entity represents a legal company for which Fiscal and Tax reports are prepared. A Legal Entity can Model to an Enterprise, a Designated Legal unit which is recognized by legal authorities in a country. Legal entity is a business entity that is known to exist to the outside world. Internal organizations or divisions are not legal entities themselves, but are just part of it. In the Multi Organization structure various legal entities could share the same ledger. Both legal entities and operating units are associated with the ledger and the relationship between the legal entity and operating unit is derived based on the ledger.
A legal Entity can be associated to Single Ledger, Multiple Legal Entities can be Associated to a Ledger.
A Legal Entity can be defined using two different Navigations.
  • Legal Entity pages of Accounting Setup Manager
  • Legal Entity pages in Legal Entity Configurator

The only difference between the above two is that Balancing Segment Value can be assigned to legal entities using Accounting Setup Manager.

How Legal Entity Is Mapped to Different Functionalities in Oracle Application R12:

  • Accounting Structures --> Legal Entity is mapped to Balancing Segment Values and Ledgers
  • E Business Tax --> Legal entity is used to identify the Jurisdiction and the parties and where they are registered or located to determine the Tax applicability
  • Bank Accounts --> In Oracle Applications R12 Legal Entity is the Owner of the particular bank account be it a Internal or Remittance bank account. And can be used by The Operating Unit which shares the same ledger as that of the Owning Legal entity.
  • Payables and Receivables -->  the Legal Entity is stamped on the transactions and used to identify the Legal Owner for Legal reporting as well as Tax calculation. The transactions exists within an OU and that OU has a ledger which will account the transactions, if a transaction has more than one LE associated with it then a hierarchy of LE derivation is used to default an LE. Ideally The Legal entity is the owner of that transaction.
  • Intercompany Accounts and Intercompany Processing Rules --> Intercompany journals involve balancing segment values that map to different legal entities. These journals are balanced for each legal entity by using their intercompany accounts.

Thursday, August 23, 2012

Application Implementation methodology (AIM) Template list

Application Implementation methodology (AIM) Template list

Application Implementation Method is a proven approach for all the activities required to implement oracle applications. there are eleven processes of implementation.

1. Business Process Architecture [BP] – This phase outlines:

    *
      Existing Business Practices
    *
      Catalog change practices
    *
      Leading practices
    *
      Future practices

BP.010 Define Business and Process StrategyBP.020 Catalog and Analyze Potential Changes
BP.030 Determine Data Gathering Requirements
BP.040 Develop Current Process Model
BP.050 Review Leading Practices
BP.060 Develop High-Level Process Vision

BP.070 Develop High-Level Process Design

BP.080 Develop Future Process Model
BP.090 Document Business Procedure



2. Business Requirement Definition [RD] - This phase explains about the initial baseline questionnaire and gathering of requirements.

RD.010 Identify Current Financial and Operating Structure RD.020 Conduct Current Business Baseline RD.030 Establish Process and Mapping Summary RD.040 Gather Business Volumes and Metrics RD.050 Gather Business Requirements RD.060 Determine Audit and Control Requirements RD.070 Identify Business Availability Requirements RD.080 Identify Reporting and Information Access Requirements

3. Business Requirement Mapping [BR] – In this phase the requirements of business are matched with the standard functionality of the oracle applications.
BR.010 Analyze High-Level GapsBR.020 Prepare mapping environment
BR.030 Map Business requirements
BR.040 Map Business Data
BR.050 Conduct Integration Fit Analysis
BR.060 Create Information Model

BR.070 Create Reporting Fit Analysis

BR.080 Test Business Solutions

BR.090 Confirm Integrated Business Solutions

BR.100 Define Applications Setup
BR.110 Define security Profiles



4. Application and Technical Architecture [TA] – This outlines the infrastructure requirements to implement oracle applications.

TA.010 Define Architecture Requirements and StrategyTA.020 Identify Current Technical Architecture
TA.030 Develop Preliminary Conceptual Architecture
TA.040 Define Application Architecture
TA.050 Define System Availability Strategy
TA.060 Define Reporting and Information Access Strategy

TA.070 Revise Conceptual Architecture

TA.080 Define Application Security Architecture

TA.090 Define Application and Database Server Architecture

TA.100 Define and Propose Architecture Subsystems

TA.110 Define System Capacity Plan

TA.120 Define Platform and Network Architecture

TA.130 Define Application Deployment Plan

TA.140 Assess Performance Risks
TA.150 Define System Management Procedures



5. Build and Module Design [MD] – This phase emphasizes the development of new functionality (customization) required by the client. It mainly details how to design the required forms, database and reports.
MD.010 Define Application Extension StrategyMD.020 Define and estimate application extensions
MD.030 Define design standards
MD.040 Define Build Standards
MD.050 Create Application extensions functional design
MD.060 Design Database extensions

MD.070 Create Application extensions technical design

MD.080 Review functional and Technical designs

MD.090 Prepare Development environment

MD.100 Create Database extensions

MD.110 Create Application extension modules
MD.120 Create Installation routines



6. Data Conversion [CV] – Data Conversion is the process of converting or transferring the data from legacy system to oracle applications. Ex. Transferring customer records from the legacy to the Customer Master.
CV.010 Define data conversion requirements and strategyCV.020 Define Conversion standards
CV.030 Prepare conversion environment
CV.040 Perform conversion data mapping
CV.050 Define manual conversion procedures
CV.060 Design conversion programs

CV.070 Prepare conversion test plans

CV.080 Develop conversion programs

CV.090 Perform conversion unit tests

CV.100 Perform conversion business objects

CV.110 Perform conversion validation tests

CV.120 Install conversion programs
CV.130 Convert and verify data



7. Documentation [DO] – Documentation prepared per module that includes user guides and implementation manuals.
DO.010 Define documentation requirements and strategyDO.020 Define Documentation standards and procedures
DO.030 Prepare glossary
DO.040 Prepare documentation environment
DO.050 Produce documentation prototypes and templates
DO.060 Publish user reference manual

DO.070 Publish user guide

DO.080 Publish technical reference manual
DO.090 Publish system management guide



8. Business System Testing [TE] – A process of validating the setup’s and functionality by QA(functional consultant) to certify status.
TE.010 Define testing requirements and strategyTE.020 Develop unit test script
TE.030 Develop link test script
TE.040 Develop system test script
TE.050 Develop systems integration test script
TE.060 Prepare testing environments

TE.070 Perform unit test

TE.080 Perform link test

TE.090 perform installation test

TE.100 Prepare key users for testing

TE.110 Perform system test

TE.120 Perform systems integration test
TE.130 Perform Acceptance test



9. Performance Testing [PT] - Performance testing is the evaluation of transactions saving time, transaction retrieval times, workflow background process, database performance, etc
PT.010 – Define Performance Testing StrategyPT.020 – Identify Performance Test Scenarios
PT.030 – Identify Performance Test Transaction
PT.040 – Create Performance Test Scripts
PT.050 – Design Performance Test Transaction Programs
PT.060 – Design Performance Test Data

PT.070 – Design Test Database Load Programs

PT.080 – Create Performance Test TransactionPrograms

PT.090 – Create Test Database Load Programs

PT.100 – Construct Performance Test Database

PT.110 – Prepare Performance Test Environment
PT.120 – Execute Performance Test



10. Adoption and Learning [AP] – This phase explains the removal of the legacy system and oracle application roll out enterprise wide.
AP.010 – Define Executive Project StrategyAP.020 – Conduct Initial Project Team Orientation
AP.030 – Develop Project Team Learning Plan
AP.040 – Prepare Project Team Learning Environment
AP.050 – Conduct Project Team Learning Events
AP.060 – Develop Business Unit Managers’Readiness Plan

AP.070 – Develop Project Readiness Roadmap

AP.080 – Develop and Execute CommunicationCampaign

AP.090 – Develop Managers’ Readiness Plan

AP.100 – Identify Business Process Impact onOrganization

AP.110 – Align Human Performance SupportSystems

AP.120 – Align Information Technology Groups

AP.130 – Conduct User Learning Needs Analysis

AP.140 – Develop User Learning Plan

AP.150 – Develop User Learningware

AP.160 – Prepare User Learning Environment

AP.170 – Conduct User Learning Events
AP.180 – Conduct Effectiveness Assessment




11. Production Migration [PM] – The process of “decommissioning” of legacy system and the usage(adoption) of oracle application system.

PM.010 – Define Transition Strategy

PM.020 – Design Production Support Infrastructure

PM.030 – Develop Transition and Contingency Plan

PM.040 – Prepare Production Environment

PM.050 – Set Up Applications

PM.060 – Implement Production Support Infrastructure

PM.070 – Verify Production Readiness

PM.080 – Begin Production

PM.090 – Measure System Performance

PM.100 – Maintain System

PM.110 – Refine Production System

PM.120 – Decommission Former Systems

PM.130 – Propose Future Business Direction


PM.140 – Propose Future Technical Direction

Wednesday, July 25, 2012

Different Documents Used at Different Levels in Application Implementation Methodology ::

Different Documents Used at Different Levels in Application Implementation Methodology ::

1. Business Process Architecture [BP] –

This Document Addresses ::
  • Existing Business Practices
  • Catalog change practices
  • Leading practices
  • Future practices
2. Business Requirement Definition [RD]

            This phase explains about the initial baseline questionnaire and gathering of requirements

3. Business Requirement Mapping [BR]

In this phase the requirements of business are matched with the standard functionality of the oracle applications.

4. Application and Technical Architecture [TA]

 This outlines the infrastructure requirements to implement oracle applications.

5. Build and Module Design [MD]

            This phase emphasizes the development of new functionality (customization) required by the client. It mainly details how to design the required forms, database and reports.

6. Data Conversion [CV]

            Data Conversion is the process of converting or transferring the data from legacy system to oracle applications. Ex. Transferring customer records from the legacy to the Customer Master.

7. Documentation [DO] 
             Documentation prepared per module that includes user guides and implementation manuals.

8. Business System Testing [TE] – A process of validating the setup’s and functionality by QA(functional consultant) to certify status.

9. Performance Testing [PT] - Performance testing is the evaluation of transactions saving time, transaction retrieval times, workflow background process, database performance, etc

10. Adoption and Learning [AP] – This phase explains the removal of the legacy system and oracle application roll out enterprise wide.


11. Production Migration [PM] – The process of “decommissioning” of legacy system and the usage(adoption) of oracle application system.

Monday, July 23, 2012

Application Implementation Methodology

Application Implementation Methodology::


AIM consists of a project management methodology together with the underlying documentation templates that support the tasks you perform within this methodology. This combination of a methodology together with documentation templates makes AIM a powerful tool for assisting implementation participants in running and managing projects successfully.

There are 6 phases in AIM


  1. Definition ::
    1. Establish the business objectives and related Requirements,
    2. Define the Project Plan

  1. Operations Analysis :
    1. Analyze the operations and identify the fit between Organizational requirements and Standard Applications Functionality

  1. Design :
    1. Develop detailed design for the optimal Solutions to meet the future business requirements

  1. Build : (Implementation)
    1. Physical Software system Build and testing

  1. Transition:
    1. Deploying the Finished solution in to Organization

  1. Production Go live

** Each Phase has Number of tasks to be followed.


** There are more than 150 templates, which can be used through out the AIM Process.

There are two types of AIM Documentation template:
-        Project management related (Project plan, Change Orders, Quality control document. Etc.)

-        Oracle Applications Implementation related Docs (RD50, BR100, MD200 etc.)

Saturday, June 23, 2012

Security Profiles in Oracle Application R12

Security Profiles

Oracle Applications 11i had a limitation where, the Business Personnel’s responsible for a particular business function who had access to multiple organizations had to navigate to individual Organization specific responsibilities for taking action on the transactions. For example: a buyer who can create Purchase orders for multiple organizations will have to Navigate to each operating Unit specific responsibility to create or manage purchasing Documents.

R12 comes as a blessing for such user of Oracle applications where Multi Organization Access control features enabled such users to take action on documents and transactions without navigating between various organizations specific responsibilities. This feature can be implemented using Security Profiles in R12.

Security profiles is a feature in R12 which can be used for grouping the organizations logically such that a set of users can access a Set of Organizations using the responsibility which are assigned with particular Security profile.

There are two types of Security Profiles.

Security Profile: If it is required to group multiple operating units for the same business group.
Global Security Profile: If it is required to group multiple operating units for the different business group.
After the security profiles are defined it is required to run the Security List Maintenance program, before assigning the Security profile to the Responsibilities





A Security profile can be assigned to a responsibility by using the MO: Security Profile option.





If you set the MO: Security Profile option, you can also set the MO: Default Operating Unit profile option to specify a default operating unit.
It is important to note that if the MO: Security Profile option is not set for the responsibility it will behave same as R11i.

The MO: Operating Unit profile option still exists in R12 but it should only be used if Multi organization access control is not desired.

HR: Security Profile

Oracle Applications also has HR: Security Profile feature. This profile option is used for defining association between a Business group and the Organizations hierarchy. HR: Security Profile options needs to be setup before defining any new organizations or organization hierarchies under a Business group.




Monday, April 23, 2012

Setting up Inventory Organization in Oracle R12

Setting up Inventory Organization in Oracle R12:

Any Organization which needs to be defined as an Inventory Organization needs to be classified as an Inventory Organization.



Define the Ledger, Legal Entity, and Operating Unit (Optional) for the Inventory organization in the 
accounting Information.


Setup the Inventory Organization Parameter for defining the Control for particular Org. Following Major inventory Organization Related setups can be done in the Inventory Parameter screen.
·        We can define the Organization as an Master Inventory org or we can attach one.
·        The Workday calendar can be defined.
·        Set up Locator Control option
·        Enable the Inventory organization for other peripheral Products such as Ware house management, Landed Cost management, Process Manufacturing etc.









Costing Information
The Costing Information is a vital component of the organization definition. The Costing Organization displayed in the Costing Information tab of Organization Parameters is based on the control level that you set for the item attributes Costing Enabled and Inventory Asset Value. If the control level for these attributes is set to Master, then the item master organization defaults as the costing organization. The current organization is displayed if the control is set to Organization level.

Valuation Accounts :

The Material Account is required for all organizations. Material costs represent the cost of raw material component at the lowest level of the assembly. For asset items, the material account is used as the default requisition account when you create purchase requisitions for Inventory Items.
The Outside Processing Account is used for tracking Outside Processing (OSP) costs. OSP costs represent work performed by a supplier on a discrete job or repetitive schedule.

The Material Overhead Account tracks material overhead or burden costs. These are the costs required to bring items into or out of inventory locations.

The Overhead Account tracks costs related to resource or department overhead.

The Resource Account captures resource costs which are direct service costs required to manufacture products.

The Expense Account is used to record the value of items issued to a non-tracked and/or expense Inventory transactions.

Other Accounts:
This Tab is used for deriving Other accounts which will be used while creation of accounting entries for the transactions such as Purchase price variance, Invoice Price Variance, Inventory Accruals Account etc.


Receiving options:
Setting Up Receiving options is another important setup step while setting up Inventory Organization, Although the receiving options can also be setup while Purchasing Setups.


Friday, March 23, 2012

Inventory Organization in Oracle Applications

Inventory Organization in Oracle Applications.

In this Article we will see the importance, setup steps, Prerequisites of Inventory organization in Oracle Applications R12.
An Inventory Organization represents a business entity which can Store and Transact Item. Setting up Inventory organization is a Preliminary step for defining and using Oracle Inventory module.
In real world an inventory organization represents a physical entity like a manufacturing facility, warehouse, distribution center or a branch office where inventory is stored and transacted or it can also represent a Logical Entity such as Master Inventory Organization which can be used for Defining Items..
Some of the applications which secure information by inventory organization are: Oracle Inventory, Bills of Material, WIP, MRP, and Purchasing receiving functions. Hence to use such applications for transactions, it is required to select an organization that has been classified as an inventory organization.
Below Mentioned is a Sample Structure which shows how Inventory Organization fits in th Oracle applications Multi-Organization Structure.




An Inventory Organization has one or more Sub-inventories which in turn can have one or more Locators.

Sub-Inventory:

Subinventory is a business Entity which represents a Physical or Logical Separation Of Inventory, For Eg. Finished Goods Inventory, Raw material Inventory. the Inventory Transactions can be Tracked or Restricted as per Subinventories. It is required to define at least one Subinventory for every Inventory Organization.

Locators:

Locators are physical places where an Inventory Item is stored with in a Subinventory or Inventory. Locator Control is an Optional feature in Oracle Inventory Module.
It is also required to define below mentioned Multi organization Entities before defining an Inventory organization.
  • ·        Ledger
  • ·        Location
  • ·        Legal Entity
  • ·        Operating Unit (Optional)

Wednesday, February 1, 2012

Designing Payables Interface

Designing Payables Interface

Designing a Payables interface is a very important task of any Oracle Applications Payables Implementation. Hence it is always required to create a payables Interface.

Payables Interface has significantly changed from 11i to R12.
Even though the R12 has Three levels of details on a payables Invoice which are

Invoice Header
Invoice Line
Invoice Distribution.

The Payables Interface Still continue to have two level of details, which are

Invoice Header
Invoice Line.

Below is a Insert script which can be leveraged for Inserting records in Payables Interface Header Table. AP_INVOICES_INTERFACE

Payables Invoice Header Interface Insert

INSERT
INTO apps.ap_invoices_interface
  (
    invoice_id,
    invoice_type_lookup_code,
    invoice_date,
    invoice_num,
    vendor_id,
    vendor_site_id,
    invoice_amount,
    source,
    org_id,
    INVOICE_CURRENCY_CODE,
    EXCHANGE_RATE_TYPE,
    --TERMS_NAME,
    DESCRIPTION,
    GLOBAL_ATTRIBUTE18,
    GLOBAL_ATTRIBUTE19,
    GLOBAL_ATTRIBUTE20,
    --GROUP_ID,
    --PAY_GROUP_LOOKUP_CODE,
    GL_DATE
  )

  VALUES

  (
    AP.AP_INVOICES_INTERFACE_S.NEXTVAL
   ,'STANDARD'
   ,SYSDATE --<invoice date>
   ,'KTICAP081801'
   ,24699    --<vendor_id validated against po_vendors.vendor_id>,
   ,35433     --<vendor_site_id validated against po_vendor_sites.vendor_site_id>,
   ,111     --<invoice_amount>
   ,<SOURCE>
   ,<ORG_ID>
   ,'USD'
   ,'Corporate'
   ,'KTEST for ICO'
   ,'Services In Country'
   ,'01-AUG-2014'
   ,'18-AUG-2014'
   ,trunc(Sysdate)
  );

 
Below is a Insert script which can be leveraged for Inserting records in Payables Interface Header Table. AP_INVOICE_LINES_INTERFACE


Payables Invoice Lines Interface Insert

INSERT
INTO APPS.ap_invoice_lines_interface
  (
    invoice_id
    ,invoice_line_id
    ,line_number
    ,line_type_lookup_code
    ,amount
    ,accounting_date
    ,DESCRIPTION
   --,PO_HEADER_ID
   --,PO_DISTRIBUTION_ID
   --,SHIP_TO_LOCATION_CODE
    ,DIST_CODE_COMBINATION_ID
    ,ATTRIBUTE_CATEGORY
    ,ATTRIBUTE1
    ,ATTRIBUTE2
    ,ATTRIBUTE15
  --  ,GLOBAL_ATTRIBUTE_CATEGORY
    ,GLOBAL_ATTRIBUTE18
    ,GLOBAL_ATTRIBUTE19
    ,GLOBAL_ATTRIBUTE20
    --,PROJECT_ID
    --,TASK_ID
    --,EXPENDITURE_TYPE
    --,EXPENDITURE_ITEM_DATE
    --,EXPENDITURE_ORGANIZATION_ID
    ,ORG_ID
   
    ,CONTROL_AMOUNT
    ,TAX_CLASSIFICATION_CODE
  )

  VALUES
  (
    AP.AP_INVOICES_INTERFACE_S.CURRVAL
   ,AP.AP_INVOICE_LINES_INTERFACE_S.NEXTVAL
   ,1       
   ,'ITEM'   --<ITEM>/<FREIGHT>/<TAX>
   ,100     
   ,SYSDATE
   ,'KT ICO INVOICE DIST DESCRIPTION'
   ,'2906440' --'<Derive from Code Combination>'
   ,<ATTRIBUTE CONTEXT>
   ,'12-AUG-2014'
   ,'BIL'
   ,'987654321'
   --,'JE.IL.APXINWKB.GOOD_SERVICES'
   ,'Services In Country'
   ,'01-AUG-2014'
   ,'18-AUG-2014'
   ,<ORG_ID>
   ,'11'
,<TAX CODE>

  );

Sunday, January 1, 2012

Designing Accounts Receivables Interface

Designing Accounts Receivables Interface

Designing a Receivables interface is a very important task of any Oracle Applications Receivables Implementation. Hence it is always required to create a Receivables Interface.
In Oracle Application R12 the Receivables Invoice Interface has two level of details, which are

AR Invoice transaction Lines

Transaction lines can be used for populating the Majority of details in the AR invoice interfaces. And hence this is the most important table to insert the data in.

AR invoice Transaction Distribution

Though the Distributions are used for deriving the accounting of an AR transaction, and this can directly be done using the AR Auto accounting rules, data can be inserted in this table for Recevables and Revenue Accounting if Accounting required on lines is more complex than Auto Accounting rules and cannot be managed there.

Below is a Insert script which can be leveraged for Inserting records in AR Invoice transaction Lines

RA_INTERFACE_LINES_ALL

AR Invoice transaction Lines Interface Insert


INSERT INTO Apps.ra_interface_lines_all
(
INTERFACE_LINE_ID,
INTERFACE_LINE_CONTEXT,
--INTERFACE_LINE_ATTRIBUTE1,
--INTERFACE_LINE_ATTRIBUTE2,
INTERFACE_LINE_ATTRIBUTE3,
BATCH_SOURCE_NAME,
SET_OF_BOOKS_ID,
LINE_TYPE,
DESCRIPTION,
CURRENCY_CODE,
AMOUNT,
CUST_TRX_TYPE_NAME,
CUST_TRX_TYPE_ID,
--TERM_NAME,
TERM_ID,
ORIG_SYSTEM_BILL_CUSTOMER_ID,
ORIG_SYSTEM_BILL_ADDRESS_ID,
CONVERSION_TYPE,
CONVERSION_DATE,
CONVERSION_RATE,
TRX_DATE,
TRX_NUMBER,
-- LINE_NUMBER,
UOM_CODE,
UOM_NAME,
ORG_ID
)

VALUES
(
AR.RA_CUSTOMER_TRX_LINES_S.NEXTVAL,
<INTERFACE ATTRIBUTE CONTEXT 9IF ANY),
'GL|98765432|8',
<AR INVOICE SOURCE>,
1002,
'LINE',
'KTEST FOR NBL IC AR INV 090208- with DIST',
'USD',
111,
<AR TRANSSACTION TYPE>,
11920,
--NA
4,
<CUSTOMER ID>,
<CUTOMER SITE ID>,
'User',
TRUNC(SYSDATE),
1,
TRUNC(SYSDATE),
<AR INVOICE NUMBER>,
--NA
'EA',
'EA',
<ORG_ID>
);

Below is a Insert script which can be leveraged for Inserting records in AR Invoice transaction Distribution

RA_INTERFACE_DISTRIBUTIONS_ALL

AR Invoice transaction Distribution Interface Insert

INSERT INTO Apps.RA_INTERFACE_DISTRIBUTIONS_ALL
(
INTERFACE_DISTRIBUTION_ID,
INTERFACE_LINE_ID,
INTERFACE_LINE_CONTEXT,
INTERFACE_LINE_ATTRIBUTE3,
ACCOUNT_CLASS
,AMOUNT
,PERCENT
,CODE_COMBINATION_ID
,SEGMENT1
,SEGMENT2
,SEGMENT3
,SEGMENT4
,SEGMENT5
,SEGMENT6
,SEGMENT7
,ORG_ID
)
VALUES
(
AR.RA_CUST_TRX_LINE_GL_DIST_S.NEXTVAL,
AR.RA_CUSTOMER_TRX_LINES_S.CURRVAL,
<ATTRIBUTE CONTEXT if required>,
'GL|98765432|8',
'REV' (DEFINE THE DISTRIBUTION TYPE “REV” FOR Revenue and “REC” for receivables)
,111
,100
,20798 <code combination id derived on the basis of Code> this is over written if you pop[ulate the actual segment values.>
,'<SEGMENT1>'
, <SEGMENT2>
, <SEGMENT3>
, <SEGMENT4>
, <SEGMENT5>
, <SEGMENT6>
, <SEGMENT7>
,ORG_ID
);