Posts

AP Invoice Rejection - Errors

Account Required.  Accounting information is missing for this line. Acct Date Beyond Enc Year.  Accounting date (ACCOUNTING_DATE) is beyond the encumbrance year and the Use PO Encumbrance Financials option is enabled. Acct Date Not In Open Pd.  Accounting date (ACCOUNTING_DATE) is not in an open period. Amount Billed Would Be Below Zero.  This transaction would reduce the amount billed on the purchase order to below zero. Amount Unpaid Too Small.  The prepayment amount that you are trying to apply (PREPAY_APPLY_AMOUNT) exceeds the invoice amount. Note:  For invoices that include prepayments (that is, the invoice amount has already been reduced by the amount of the prepayment) the prepayment amount cannot exceed the unpaid invoice amount. Applying More Than Avail.  You are applying a prepayment to the invoice and the amount you are applying is greater than the prepayment amount available for application. You can see a prepayment’s available a...

AP Invoice Rejections

Select aii.Invoice_num , air.PARENT_TABLE, air.REJECT_LOOKUP_CODE, air.parent_id From apps. AP_INTERFACE_REJECTIONS air, apps. AP_INVOICE_LINES_INTERFACE aili, apps. AP_INVOICES_INTERFACE aii WHere aii.invoice_id=aili.invoice_id AND  aili.invoice_id=air.parent_id AND aii.Invoice_num = ‘Invoice Number’ aii.INVOICE_ID, aii.SOURCE, aii.invoice_num, (select decode(count(*),0,'Invoice N/A','Invoice Available') from ap_invoices_all where org_id = aii.ORG_ID and invoice_num = aii.INVOICE_NUM) Inv_in_Base, aii.CREATION_DATE, aii.invoice_date,  aii.GL_DATE, ail.LINE_NUMBER, aii.REQUEST_ID, aii.invoice_currency_code, nvl(airh.REJECT_LOOKUP_CODE,airl.REJECT_LOOKUP_CODE) Rejection_Reason, (select decode(count(INACTIVE_DATE),0,'Site is Active','Site is Inactive') from po_vendor_sites_All where vendor_site_id = aii.VENDOR_SITE_ID) Site_STatus from ap_invoice_lines_interface ail, AP_INTERFACE_REJECTIONS airh, AP_INTERFACE_REJECTIONS airl, ap_invoices_interface aii,...

Journal Entries using Sub Ledger Accounting

Image
Journal Entries using Sub Ledger Accounting http://oraapps-raghuraman.blogspot.com/2012/01/journal-entries-using-sub-ledger.html Key points of creation of journal entry through SLA: There is a new functionality to enter subledger journals through SLA: Create Journal Entry page. Add the function SLA: Create Subledger Journal Entry, if not available in relevant module. All the modules by default will have this function unless specifically restricted. Very important point is manual subledger journal entry is not associated with transaction of any subledger application. Meaning we can’t transfer the entries to both Subledgers and GL without customization. This is true whether we use FAH or DRM (Data Relationship Management, which is part of Hyperion) applications. If required to use Manual SLA Journals functionality to represent accounting treatment in legacy systems, one can use API which allows importing legacy transactions into SLA, change the accounting treatment as per Oracle...

GL Interface

STATUS NOT NULL VARCHAR2(50)   LEDGER_ID   NUMBER(15)   ACCOUNTING_DATE NOT NULL DATE   CURRENCY_CODE NOT NULL VARCHAR2(15)   DATE_CREATED NOT NULL DATE   CREATED_BY NOT NULL NUMBER(15)   ACTUAL_FLAG NOT NULL VARCHAR2(1)   USER_JE_CATEGORY_NAME NOT NULL VARCHAR2(25)   USER_JE_SOURCE_NAME NOT NULL VARCHAR2(25)   CURRENCY_CONVERSION_DATE   DATE   ENCUMBRANCE_TYPE_ID   NUMBER   BUDGET_VERSION_ID   NUMBER   USER_CURRENCY_CONVERSION_TYPE   VARCHAR2(30)   CURRENCY_CONVERSION_RATE   NUMBER   AVERAGE_JOURNAL_FLAG   VARCHAR2(1)   ORIGINATING_BAL_SEG_VALUE   VARCHAR2(25)   SEGMENT1   VARCHAR2(25) ...