Importing Intercompany Transactions Part2(AGIS)

-

 

Importing Intercompany Transactions

Importing Transactions Part -2

Intercompany Open Interface Tables

Intercompany transactions from the external source populate the following
Intercompany Interface tables:

• FUN_INTERFACE_CONTROLS, which groups the data imported in each run.

• FUN_INTERFACE_BATCHES, which stores batch information.

• FUN_INTERFACE_HEADERS, which stores information about the transaction
header for each recipient.

• FUN_INTERFACE_DIST_LINES, which stores distributions for initiator and
recipient.

Running the Intercompany Import Program
Run the Intercompany Import Program in the Schedule Requests page to import the
Intercompany transactions from Interface tables to Intercompany tables. Before
importing, the transactions are validated by the Transaction API.
On successful completion of the import program, an import execution report is printed
which lists the status of the transactions being imported.
The following table describes selected fields in the Intercompany Import Program.

Parameters                                                 Description

Source                                               Specify the application source.
Group                                                Enter the Group ID.
Send Transactions                              Enter Yes to send the transactions as initiator transactions and
start the recipient workflow.                Print Rejected Only Specify No if you want to print all the transactions in the report.
Debug                                                 Helps you to query, rectify and re-import rejected transactions.

Successful transactions are purged from the interface tables.

Importing Intercompany Transactions Using WebADI

WebADI enables you to enter transactions in a spreadsheet application and upload
them into AGIS. The advantages of using WebADI for entering intercompany
transactions are:

• You only need a browser and spreadsheet application such as Excel in your desktop
to run WebADI.

• You can enter transactions in a transaction entry worksheet in a spreadsheet that is
similar to the transaction entry page in Intercompany.

• You can define a spreadsheet specific to intercompany transactions and use
powerful spreadsheet features.

For example, you can define formulae for allocation entries in the spreadsheet. You
can save, manage the transaction entry worksheet and upload it later, regardless of
being connected to AGIS. You can also define a spreadsheet to define intercompany
templates for modifying and uploading repeatedly (for recurring transactions).
• You can quickly enter intercompany journal lines by copying and pasting journal
lines, then performing incremental modifications in the spreadsheet worksheet.

• You can validate accounts by enforcing security and cross validation rules.

• You can use the following items in the WebADI menu in the spreadsheet:

• Upload Journal: Select this option to choose the upload parameters.

• List of Values: Select this option to invoke a List of Values when entering


AGIS Tables(FUN):

FUN_BAL_ERRORS_GT
FUN_BAL_ERRORS_T
FUN_BAL_GENERATE_LINES
FUN_BAL_HEADERS_GT
FUN_BAL_INTER_INT_GT
FUN_BAL_HEADERS_T
FUN_BAL_INTER_BSV_MAP_T
FUN_BAL_INTER_INT_T
FUN_BAL_INTRA_INT_GT
FUN_BAL_INTRA_BSV_MAP_T
FUN_BAL_INTRA_INT_T
FUN_BAL_LE_BSV_MAP_GT
FUN_BAL_LINES_GT
FUN_BAL_LINES_T
FUN_BAL_RESULTS_GT
FUN_BAL_RESULTS_T
FUN_BALANCE_ACCOUNTS
FUN_BALANCE_OPTIONS
FUN_BATCH_DISTS
FUN_CONTACTUS_REQUEST_DATA
FUN_CONTACTUS_SETUP
FUN_CUSTOMER_MAPS
FUN_INTER_ACCOUNTS_ADDL
FUN_DIST_LINES
FUN_INTER_ACCOUNTS
FUN_INTERFACE_BATCHDISTS
FUN_INTERFACE_BATCHES
FUN_INTERFACE_CONTROLS
FUN_INTERFACE_DIST_LINES
FUN_INTERFACE_HEADERS
FUN_INTERFACE_REJECTIONS
FUN_NET_AGREEMENTS_ALL
FUN_NET_AP_INV_TYPES_ALL
FUN_NET_AP_INVS_ALL
FUN_NET_AR_TRX_TYPES_ALL
FUN_NET_BATCHES_ALL
FUN_NET_AR_TXNS_ALL
FUN_NET_CUSTOMERS_ALL
FUN_NET_SUPPLIERS_ALL
FUN_RICH_MESSAGES_B
FUN_PERIOD_STATUSES
FUN_RULE_BULK_RESULT_GT
FUN_RICH_MESSAGES_TL
FUN_RULE_CRIT_PARAMS_B
FUN_RULE_CRITERIA
FUN_RULE_CRIT_PARAMS_TL
FUN_RULE_DETAILS
FUN_RULE_OBJ_ATTRIBUTES
FUN_RULE_OBJECTS_B
FUN_RULE_OBJECTS_TL
FUN_RULE_PARAM_VALUES
FUN_RULE_TEST_MULTIRULE
FUN_RULE_TEST_MVAL_RES
FUN_RULE_TEST_PARAMS
FUN_RULE_TEST_RESULTS
FUN_RULE_TESTS
FUN_SEQ_ASSIGNMENTS
FUN_SEQ_CONTEXTS
FUN_SEQ_ENTITIES
FUN_SEQ_BATCH_GT
FUN_SEQ_REQUESTS
FUN_SEQ_HEADERS
FUN_SEQ_RULES
FUN_SEQ_VERSIONS
FUN_SUBSIDIARY_PARTY_MAPPINGS
FUN_TRADE_RELATIONS
FUN_SUPPLIER_MAPS
FUN_SYSTEM_OPTIONS
FUN_TRANSFERS
FUN_TRX_ACCT_DEFINITIONS
FUN_TRX_BATCHES
FUN_TRX_LINES
FUN_TRX_HEADERS
FUN_TRX_TYPES_B
FUN_TRX_TYPE_AR_MAPS
FUN_TRX_TYPES_TL
FUN_XLA_TAB_GT
FUN_BAL_INTER_INT2_GT
FUN_BAL_INTER_INT2_T

Comments

Post a Comment

Popular posts from this blog

Oracle Purchasing Module Step by Step in R12

-
Image
PURCHASING  All the Purchasing related activity information will be declared in Purchasing              Procure 2 Pay Cycle : Requisition à RFQ à Quotation à Quotation Analysis à Purchasing à Receiving à Invoice  à  Payment à Reconciliation PO-Integration :  PO  is integrated by GL, AP, I Supplier, Procurement, and Project Accounting  PO  Responsibility             Step1: Define  PO  Responsibility                         Nav: System administrator à Security à Responsibility à Define             Step2: Assign  PO  options to the PO Responsibility                         Nav: System administrator à Profile à system             Step3: Assign  PO  Responsibility to User                         Nav: System administrator à security à user à define Note:  PO  is including some of i.e. Options, Supplier, Item, Expenses, and Purchasing . Options : Options nothing but a Controlling future at the operating unit level.                         Th
Read more

Difference between ATO and PTO in oracle apps

-
Difference between ATO and PTO in oracle apps 1) MAKE TO ORDER: This is based on Customer specification, you make the product and supply it to them. This is applicable for Engineering items or any Product which you can make based on Customer order Example: Engineering Items 2) ASSEMBLE TO ORDER: This is you have items in parts and it needs to be assembled according to customer requirements For example you have Laptop coming with standard configuration of 160GB Hard disk and 1 GB RAM. But there are customer orders coming in asking for 200GB Hard Disk and 2 GB RAM and if you can assemble them to suit Customer Requirement 3) CONFIGURE TO ORDER: This is Configuring the Product itself to suit Customer requirements Example. The Thread Manufacturing unit Machineries are configured. I have seen Laxmi Machine Works in INDIA which manufactures textile Machineries configure the machineries based on No.of spindles 4) PICK TO ORDER: This is same as Computer Example in ATO. But the  difference is
Read more

Sub Ledger Accounting SLA (Complete Functional Information)

-
Image
SubLegder Accounting in R12 SLA Part -1 In these article, we will explore the very basics of SLA and why it exists. Firstly, what exactly does SLA do? SLA is a module which now sits between the SubLedgers like AP/AR etc and the General Ledger. Have a look at this diagram below.  As you will notice, SLA can act as a mediator between the subledgers and Oracle General Ledger. Before we progress, some terminologies of R12 must be revisited. In 11i we had set of books, and in R12 we call them Ledgers. Likewise in R12 we also have secondary ledgers and reporting ledgers. Hence from 11i perspective think of Ledger as Set of Books. As for Subledger, a Subledger is nothing but a module like AP/AR/PO/Inventory etc. In the diagram below, the second scenario is explained whereby let's say that payables module generates a charge account segment combination for an invoice distribution line as A.B.C.D. In such case, if SLA module is not customized, then the very same A.B.C.D
Read more