Unable to apply Prepayment to standard Invoice. System not showing any error Message.

Problem Identification: In Prepayment Invoice distribution line the user has reversed the distribution line and then, the negative amount reversal line he made it zero and validated the invoice. As header amount and distribution are equal. System has validated the invoice. while applying standard invoice to Prepayment system is not showing prepayment invoice.
Solution: From SQL Query, I have verified the AP_Invoices_All and AP_Invoice_distributions_all Tables and found that, reversal_flag column as 'Yes' (Which should be Nil) and Prepayment_remaining_amount column as nil(As prepayment status is available Prepayment_remaining_amount column should have available prepayment amount value). Now, with update SQL Query, we have set Reversal_flag column as null and Prepayment_remaining_amount column with available amount. Now, system show Prepayment invoice, while applying with standard Invoice.

Automatic offset Method

This feature is used to create offset credit side liability a/c's in payables in such a way that all balancing segment of debit should be equal to credit. There are three type of automatic offset Method
          1) Balancing Account.
          2) Natural Account.
          3) None
Balancing: If you are select balancing as your automatic offset method, To create offset credit lines, Payables picks the balancing segment part accounting from Invoice Distribution lines a/c and remaining code combination will be picked up from Supplier Liability a/c.
Natural Account: If you are select natural as your automatic offset method then to create offset credit lines, The system will pick natural a/c part from Supplier Liability a/c and remaining code combination will be picked from Invoice Distribution a/c.
None:If you are select none as your automatic offset method. It means automatic offset method concept is not applicable.
Illustration:
Invoice “123” is created on Supplier “ABC” for an amount of Rs.10000/-. The invoice distribution accounts given as 01-001-0001-0001-000 The liability account defined at the supplier site is “01-002-0002-0002-000”.
The current accounting entry is
Account Combination                             Debit              Credit
01-001-0001-0001-000                           10000
01-002-0002-0002-000                                                   10000
For Balancing automatic offset method the desired accounting entry will be as follows
Account Combination                             Debit               Credit
01-001-0001-0001-000                           10000
01-002-0002-0002-000                                                   10000
For Natural automatic offset method the desired accounting entry will be as follows
Account Combination                             Debit               Credit
01-001-0001-0001-000                           10000
01-001-0002-0001-000                                                   10000

After Ship Confirmation, The Delivery status is closed but Sales Order status is "Picked". After running Interface Trip Stop SRS program again but Sales Order line is Still with "Picked" Status. Unable to interface the Sales Order

Solution: It's Foreign Currency Sales order. Currency Conversion Type and Conversion Rate are not defined at the Sales Order Level. Now, Updated Conversion Types and Currency Rate. and Rerun Interface trip Stop SRS Program, The sales order line status will changed to "Shipped" and then Run workflow background program, Now the status of sales Order will change to" Closed". Now run the autoinvoice master program, the invoice will be successfully imported to Accounts Receivable.

In India - Debtors Ledger Report particular customer Name and customer No is not found.

Solution: The user has not not created customer in Customer additional info Form. After creating the same, the name of that particular customer appeared in the India - Debtors Ledger Report parameters.

Payables Period Closing Procedure

1. Review and Complete All Open Transactions for the Period Being Closed. (Complete all pending Invoices, Expenses Report Export Program, Unvalidated Invoices, Clear holds, Journal Import). 
Use the following Reports to complete Pending Transactions.  
    A) Invoice Register (with Unvalidated Invoices parameter as “YES”).

    B) Invoice on Hold Report.

    C) Unaccounted Transaction Report.
2. Run the Payables Auto Approval Process for All Invoices / Invoice Batches.
3. Complete all Payment against the period being closed. Ensure you process all Payment Process request(PPR) before you close the period.
4. Reconcile Payments to Bank Statement for the Period.
5. Run Create Accounting Program. It will create and transfer accounting for Payables Modules to General Ledger.
6. Review the Payables to General Ledger Posting Process After Completion
7. Submit the Unaccounted Transactions Sweep Program
8.  Run Mass Additions Transfer to Oracle Assets
9. Close the Current Oracle Payables Period
10. Open the Next Payables Period
11. Reconcile with the General Ledger. The following standard reports from payables module can be used for reconciliation.
     A) Account Payables Trial Balance.   
     B) Posted Invoice Register.
     C) Posted Payment register.

Requisition Not Getting Imported for Drop Shipment Order

Step 1:You will need to run: 
select * from PO_Requisitions_interface_all 
and see what the transaction_id is 
Then run 
update po_requisitions_interface_all 
set request_id = null 
, process_flag = null 
where transaction_id = (from above) 
Then rerun the Requisition Import. 

Step 2:Please run Run "Requisition Import Exceptions Report" & choose yes in delete exceptions in parameter.

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.