Advanced Global Intercompany Sytem(AGIS) in Oracle Apps

                 Oracle Advanced Global Intercompany System (AGIS)  is a new module that allows companies to streamline intercompany processing and facilitates the reconciliation of intercompany transactions.  It replaces global intercompany system(GIS) feature provided by General Ledger in  Release 11i. All setup and transaction data is moved to a new data model and all oracle forms in the global intercompany systems are replaced by browser based user interface pages. changes include:

• Subsidiaries are replaced by intercompany organisations. The Represent trading partners  and can be used as initiators and receipts of Advanced Global Intercompany System Transactions.
• As part of the Grant-based Security Model, intercompany trading partner are mapped to users instead of responsibilites. A user may be given access to many different intercompany trading partners regardless of the responsibility used to log in.
• The intercompany accounts set up in GIS are upgraded as the new intracompany balancing Rules set up in GIS are not upgraded and need to be set up in the new subledger accounting transaction account builder.
• All GIS new and completed Transactions are upgraded as AGIS transacton batches. Generally, for each GIS Transactions, a batch is created.
• Release 11i GIS profile Options are obsolete and are not upgraded. All options are available on the AGIS System Options page.

PO Matching Concept: Two Way, Three Way & Four Way in Oracle Apps

Matching Concept plays a vital role in Procure to Pay(P2P) Cycle. Matching Concept will acts as check (Quantity & Price) between Purchase Order, Receipt, Inspection Report and Invoices. Matching Method will be defined at Purchasing Options, which will default to supplier, Supplier site and  Purchase order shipment lines. Which you change as per your organisation requirement basis before approval of Purchase Order. There are three types of Matching Methods.

        1) 2 Way Matching .

        2) 3 Way Matching.

        3) 4 Way Matching.

2 Way Matching: It verifies that purchase order and invoice information match within your tolerances as follows:
Quantity billed is less than or equal to Quantity ordered
Invoice price is less than or equal to Purchase order price.
3 Way Matching: It adds a third criterion to verify that receipt and invoice information match with the quantity tolerances you define:
Quantity billed is less than or equal to Quantity received.
Quantity billed is less than or equal to Quantity ordered
Invoice price is less than or equal to Purchase order price.
4 Way Matching: It adds a fourth criterion to verify that acceptance documents and invoice information match within the quantity tolerances you define:
Quantity billed is less than or equal to Quantity received.
Quantity billed is less than or equal to Quantity ordered
Invoice price is less than or equal to Purchase order price.
Quantity billed is less than or equal to Quantity accepted
Note: If the invoice and purchase order do not match within the tolerances you define for quantity and price, System Pop-up with a Note Message and Approval process places a matching hold on the invoice. You must release the hold and validate the invoice.

RMA(Return Material Authorization) Concept in Oracle Apps

RMA functionality allows the user to return the goods delivered to customer against Sales Order. Return from customer can occur for various reasons like goods damaged, Defective Product, Product doesn't meet customer expectations, Sampling ...etc.
Note: For internal Order we can't perform RMA transaction.
The following are the different RMA Order Types avaliable in oracle apps.
1. RMA with Credit Memo Only.
2. RMA with Receipt and Credit Memo.
3. RMA with Receipt and No Credit Memo.
RMA with Credit Memo Only: The company issues a credit Memo without the customer returning the product. Examples: For service Item no physical Product is returned, in such a case only Credit memo will be given to customer.
RMA with Receipt and Credit Memo: The Customer returns a product and receives credit Memo as a result of goods Returned. Example: Defective Product, Product don't not meet expections of Customer.
RMA with Receipt and no Credit Memo: The customer returns a product you sent to them on a trial basis or at no charge, therefore they receive no credit memo. Examples: Sample Products.
RMA can be created in two different ways in Oracle: 
1. Create a New Return which will create the RMA from scratch 
2. Copy an original order into an order with an RMA Order Type 
Sales Order Line Status: (For RMA with Receipt and Credit Memo)
1. Entered (Sales is entered or Copies before SO is booked)
2. Awaiting return (When Sales Order is booked, Immediatily the Sales Order line status will be Awating Return)
3. Returned (In Purchasing Module, When enter Receipt, the SO Line status will be"Returned"
4. Closed (After Workflow background process program is completed, the SO line Status will be " Closed")
Setup Steps:
STEP 1: The following Item attributes should be set for an item to perform RMA trasactions 
                 1. Returnable (In OM Tab) 
                 2. Shippable (In OM Tab). 
                 3. Invoice Enable (In Invoice Tab). 
STEP 2:Create OM Transaction Types for "Line" with Order Category as "Return".
STEP 3: Create Om Transaction Types for "Order" with Order Category as "Return".
STEP 4:Assign the Transaction Type Line to Transaction type Order with line workflow assignment window. Select the process name as "Line Flow - Return for Credit with Receipt".
STEP 5:Create Document Sequence for Return Purpose 
STEP 6:Query the Document Category  Which is automatically created from Transaction type created.
STEP 7: Assign Sequence and Category through Assignment Window.STEP 8: Item must be assigned in Price list
STEP 9: Return reason should be defined or use the existing one.
STEP 10: Define Transaction Sources and Transaction Type(Credit Memo) for RMA transaction in AR Module.

Sales Order line status is "Awaiting Invoice Interface - Incomplete Data". Unable to create RMA Credit Memo in AR

Solution 1:
Query the Sales Order, The Sales order Line status will be " Awaiting Invoice Interface - Incomplete Data"
Now go to 'Actions' > 'Progress Order' > Choose 'Invoice Interface - Eligible'.

Then Sales Order Line Status will be"Closed"

Now the 'Autoinvoice Master Program' and 'Autoinvoice Import Program' will be launched automatically. Check the invoice in the AR.

Solution 2:
Query your OM Transaction Type and check whether AR Transaction Source and Transaction Type are assign to it or not.
If not assigned, assign it and run the workflow background process program.
Now the 'Autoinvoice Master Program' and 'Autoinvoice Import Program' will be launched automatically, and invoice will be generated.

Accounts Receivables Period Closing Process in Oracle Apps

1. Complete the manual invoices, credit memos & corrections for the period, to find the detail run “Incomplete Invoices Report”.
Action: Go to transaction Window and Complete the Transaction 
2. Complete and review the unapplied receipts. 
3. Reconcile the Receipts to bank statement activity (Remittance Activity) for the period 
4. Run the General Ledger Transfer Program. To transfer all transaction and receipts activities to GL.
5. This will be queried in the Journal Entry form with source as “Receivables” and posting status as “Unposted”. These Journal entries will be reviewed and Posted into the GL.
6. You can review the "Unposted Items Report" to determine if any exceptions have been encountered, that will need to be resolved, to ensure all accounting has been successful for all transactions.
7. Report used for reconciliation the customer outstanding Balances    
            A) Aging Report. 
            B) Transaction Register 
            C) Applied Receipts Register 
            D) Unapplied Receipts Register 

Opening/Closing of AR periods 
Navigation: Control --> Accounting  --> Open/Close Periods. 
1. Complete the Transfer to General Ledger from the Receivables for the period to be closed. 
2. Select the period to close. Select ‘Closed’ from list of values in the Period Status and save the record. Select the Next period to open. Click Open Next Period Button

General Ledger Period Closing Process in Oracle Apps

1. Ensure the Next Accounting Period Status is Set to Future Entry
2. Complete Oracle Sub-ledger Interfaces to Oracle General Ledger
3. Upload Journals from ADI (Applications Desktop Integrator) to Oracle General Ledger
4. Complete Non-Oracle Sub-ledger Interfaces to Oracle General Ledger (Optional)
5. Generate Reversal Journals (Optional)
6. Generate Recurring Journals (Optional)
7. Generate Mass Allocation Journals (Optional)
8. Review and Verify Journal Details of Unposted Journal Entries
9. Post All Journal Batches
10. Run General Ledger Trial Balances and Preliminary Financial Statement Generator Reports (FSGs)
11. Revalue Balances (Optional)
12. Translate Balances (Optional)
13. Consolidate Sets of Books (Optional)
14. Review and Correct Balances (Perform Reconciliations)
15. Enter Adjustments and / or Accruals and Post
16. Perform Final Adjustments
17. Close the Current Oracle General Ledger Period
18. Open the Next Oracle General Ledger Period
19. Run Financial Reports for the Closed Period
20. Run Reports for Tax Reporting Purposes (Optional)
21. Perform Encumbrance Year End Procedures (Optional)

Cash Management Period Closing Process in Oracle Apps

1. Load Bank Statements

2. Reconcile Bank Statements
3. Create Miscellaneous Transactions
4. Review AutoReconciliation Execution Report
5. Resolve Exceptions on the AutoReceonciliation Execution Report
6. Run Bank Statement Detail Report
7. Run Transactions Available for Reconcilaition Report
8. Resolve Un-reconciled Statement Lines
9. Run the GL Reconciliation Report
10. Run the Account Analysis Report for the General Ledger Cash Account
11. Review the Account Analysis Report
12. Correct any Invalid Entries to the General Ledger Cash Account (Optional)
13. Perform the Bank Reconciliation

Fixed Assets Period Closing Process in Oracle Apps

1. Complete All Transactions for the Period Being Closed
2. Assign All Assets to Distribution Lines
3. Run Calculate Gains and Losses (Optional)
4. Run Depreciation
5. Create Journal Entries
6. Rollback Depreciation and/or Rollback Journal Entries (Optional)
7. Create Deferred Depreciation Journal Entries (Optional)
8. Depreciation Projections(Optional)
9. Review and Post Journal Entries
10. Reconcile Oracle Assets to Oracle General Ledger Using Reports.
11. Run Responsibility Reports (Optional)
12. Archive and Purge Transactions (Optional)

Order Management Period Closing Process in Oracle Apps

Order Management
1. Complete All Transactions for the Period Being Closed
2. Ensure all Interfaces are Completed for the Period (Optional)
3. Review Open Orders and Check the Workflow Status
4. Review Held Orders
5. Review Discounts
6. Review Backorders
7. Review and Correct Order Exceptions
8. Reconcile to Inventory
9. Reconcile to Receivables (Optional)
10. Run Standard Period End Reports
Receivables
1. Complete All Transactions for the Period Being Closed
2. Reconcile Transaction Activity for the Period
3. Reconcile Outstanding Customer Balances
4. Review the Unapplied Receipts Register
5. Reconcile receipts.
6. Reconcile Receipts to Bank Statement Activity for the Period
7. Post to the General Ledger
8. Reconcile the General Ledger Transfer Process
9. Reconcile the Journal Import Process
10. Print Invoices
11. Print Statements (Optional)
12. Print Dunning (Reminder) Letters (Optional)
13. Close the Current Oracle Receivables Period
14. Reconcile Posted Journal Entries
15. Review Unposted Items Report
16. Open the Next Oracle Receivables Period
17. Run Reports for Tax Reporting Purposes (Optional)
18. Run Archive and Purge programs (Optional)

Purchasing Period Closing Process in Oracle Apps

Purchasing
1. Complete All Transactions for the Period Being Closed
2. Review the Current and Future Commitments (Optional)
3. Review the Outstanding and Overdue Purchase Orders (Optional)
4. Follow up Receipts-Check with Suppliers
5. Identify and Review Un-invoiced Receipts (Period End Accruals)
6. Follow Up Outstanding Invoices
7. Complete the Oracle Payables- Period End Process
8. Run Receipt Accruals - Period End Process
9. Reconcile Accounts - Perpetual Accruals
10. Perform Year End Encumbrance Processing. (Optional)
11. Close the Current Purchasing Period.
12. Open the Next Purchasing Period.
13. Run Standard Period End Reports (Optional)
Inventory/WIP
1. Complete All Transactions for the Period Being Closed.
2. Check Inventory and Work In Process Transaction Interfaces.
3. Check Oracle Order Management Transaction Process.
4. Review Inventory Transactions.
5. Balance the Perpetual Inventory.
6. Validate Work In Process Inventory.
7. Transfer Summary or Detail Transactions
Close the Current Oracle Payables and Oracle Purchasing Periods.
9. Close the Current Inventory Period
10. Open the Next Inventory Period
11. Run Standard Period End Reports (Optional)