APP-AR-11228: Please define all Periods in which Revenue is to be recognized or credited.

https://receivablesar.blogspot.com/2019/04/app-ar-11228-please-define-all-periods.html

Period Type Issue

Period Type not match with the Calendar Period Type

Oracle AR Period Close and Reconciliation

https://receivablesar.blogspot.com/2019/04/oracle-ar-period-close-and.html

Before Period Closure:

Check list Items	Oracle Processes
Ensure that all AR interfaces are Processed	Run Custom Interface Processes
Ensure that there is no data in AR Invoice Interface and if there is any data, import the same	Auto Invoice Import program
Ensure that all the Interfaces from OM or Service Contracts or AGIS modules are Processed
Ensure that all Transactions are in Complete status and Accounted and transferred to GL	Create Accounting
Ensure that receipt API's or Auto Lock Box interface (if any) are Processed
Ensure that there are no Exceptions for the Period under Subledger Exception Report	Oracle Subledger Exception Report
Ensure that any Pending Adjustments are either approved or Rejected
Ensure that Revenue Recognition Process is Run	Revenue Recognition
If you are using Cash Management Module, Reconcile AR Receipts with Bank Statements	Bank Reconciliation Process

Close the Period, if there are Exceptions, then you have an Option of Running "Unaccounted Transaction Sweep" Program to Sweep the Transactions to Next Period.

After Period Closure:

Internal Reconciliation:

For Example

Previous Month Aging Report	1,345,905.00
+ Current Month Transaction Register	16,500.00
+ Current Month Adjustment Register
+ Current Month Invoice Exceptions Report
- Current Month Applied Receipt Register
- Current Month Unapplied and Unresolved Receipts Register
= Current Month Aging Report	1,362,405.00

External Reconciliation:

Aging Report (As of last Day of the Month) should be equal to corresponding GL Account Inquiry Balance.
AR to GL Reconciliation Report.

Some Common Reasons for Reconciliation issue between AP and GL:

AR related Journal entries are deleted in GL before Posting

Manual entries are passed directly in GL using AR Receivable Account

AR related Transactions are transferred to GL  but not yet Posted

AR related Journals are Updated (for some reason) in GL before Posting

Revaluation Journals in GL

AR related Journal are Reversed in GL after Posting

AR related Journals Stucked in GL Interface for some Reason

Receipts Accounting in Oracle - Oracle EBS R12

https://receivablesar.blogspot.com/2019/04/httpsreceivablesar.html

Here below is the two types of the Receipts.

·         Standard Receipts:

Payment (such as cash or a check) that you receive from your customers for goods or services. Also known as cash receipts.

·         Miscellaneous Receipts:

The document that records payment received unrelated toreceivables, such as investments, interest, or refunds.

========================================================================

Accounting for Miscellaneous Receipt:

Cash	DR
Miscellaneous Cash		CR

Miscellaneous Cash Account is defined in Receivable Activities

Name: Miscellaneous Income

Type: Miscellaneous

GL Account Source: Activity GL Account

Activity GL Account: (01-001-222-33) Miscellaneous Cash Account

Cash Account is Defined in Receipt Classes > Bank Accounts

======================================================================= 

Accounting for Standard Receipt:

1. When you enter a Receipt without a Customer

Cash	DR
Unidentified Cash		CR

Cash Account and Unidentified Cash Account is defined in Receipt Classes.

2. When you select a Customer on the same Receipt

Unidentified Cash	DR
Unapplied Cash		CR

Unidentified Cash Account and Unapplied Cash Account are defined in Receipt Classes.

3. After Applying a Transaction on Receipt

Unapplied Cash	DR
Account Receivables		CR

Unapplied Cash Account is defined in Receipt Classes and Account Receivables Account is defined in Transaction types.

4. When Complete Receipt is entered at once. With Customer and Transaction Applied on the spot.

Cash	DR
Account Receivables		CR

--------------------------------------------------------------------------------------------------------------------------

Standard Receipt (on Account):

Receivables let you apply a receipt with an existing on-account credit to close one or more of your customer's open debit items. ... When the customer remits payment or $400, you can simultaneously apply this receipt with the on-account credit to close both the open invoices and their on-account credit.

In case of an On-Account receipt, there is no identified invoice against the receipt. Advance money is received from the customer and the invoice for the same can be raised at a later date.

Enter the Receipt with a Customer and select On Account in the Apply to Field, if the Invoice will have to be received in the Future or the Invoice is Unidentified or Advance has been received from Customer and the Invoice for the same can be received in the Future.

Cash	DR
On Account Cash		CR

Cash Account and On Account Cash Account is defined in Receipt Classes > Bank Account

When Invoice is Received or Identified for a particular Receipt then you can uncheck On Account and select the Particular Receipt.

On Account Cash	DR
Account Receivables		CR

On Account Cash Account is defined in Receipt Classes and Account receivables Account is defined on Transaction Types

How to Disable Delete Button on AR Header

https://receivablesar.blogspot.com/2017/07/how-to-disable-delete-button-on-ar.html

How to Disable Delete Button on AR Header

--------------------------------------------

WHEN-NEW-RECORD-INSTANCE
RGW_FOLDER

Type: Property
Block
RGW_FOLDER
DELETE_ALLOWED
FALSE

FRM-40735 POST-QUERY Trigger raised unhandled exception ORA-06502

http://receivablesar.blogspot.com/2017/06/frm-40735-post-query-trigger-raised.html

When you try to query that bank account, nothing is returned.
This happens after adding a new bank to your Receipt Method
The error message is :

FRM-40735 POST-QUERY Trigger raised unhandled exception ORA-06502

To reproduce this issue,
Using your Receivables responsibility
Navigate to Setup / Receipts / Receipt Classes
Query your receipt class and receipt method.
Click on Bank Accounts button.

If there is more than one bank account, you may see one bank account, but
cannot see the newly added bank account.

-------------------------------------------------------------------------------

Issue is happening because the size of the BANK_BRANCH_NAME field is larger
than supported. The Bank Branch Name can only be 60 characters long.
In this case, the customers bank branch was in Arabic language and was taking more
than the supported number of bytes.

To resolve this issue, change the bank branch name to a new value that is equal to
or less than 60 characters

----------------------------------------------------------------------------

In my case Account Name Length was 71. So I minimized and the Issue got Resoved

How to Sweep Unprocessed Receipt in Next Month of AR (Not for data Corruption Receipts only to change GL Dates of the Receipt)

http://receivablesar.blogspot.com/2016/10/how-to-sweep-unprocessed-receipt-in.html

Issue:

Period not Closing due to Unprocessed Receipts

Solution:

IN this case please run the following update to sweep the data:

1. backup

create table ar_rcpt_hist_4781 as
select * from AR_CASH_RECEIPT_HISTORY_ALL
where CASH_RECEIPT_HISTORY_ID in (4861, 4862)
and CASH_RECEIPT_ID = 4781;

create table ar_rec_appl_4781 as
select * from AR_RECEIVABLE_APPLICATIONS_ALL
where CASH_RECEIPT_ID = 4781;


create table ar_pmt_sched_4781 as
select * from AR_PAYMENT_SCHEDULES_ALL
where CASH_RECEIPT_ID = 4781;

create table xla_ev_4781 as
select ev.* from XLA_EVENTS ev
where ev.entity_id in (select et.entity_id from xla.xla_transaction_entities et
where et.source_id_int_1 = 4781
and et.application_id = 222)
and ev.APPLICATION_ID = 222;


2. datafix
update AR_CASH_RECEIPT_HISTORY_ALL
set REVERSAL_GL_DATE = to_date('01-OCT-2016','DD-MON-YYYY')
where CASH_RECEIPT_HISTORY_ID in (4861)
and CASH_RECEIPT_ID = 4781;

commit;

update AR_CASH_RECEIPT_HISTORY_ALL
set GL_DATE = to_date('01-OCT-2016','DD-MON-YYYY')
where posting_control_id = -3
and gl_date between to_date('01-SEP-2016','DD-MON-YYYY')
and to_date('30-SEP-2016', 'dd-mon-yyyy')
and CASH_RECEIPT_ID = 4781;

commit;

update AR_RECEIVABLE_APPLICATIONS_ALL
set GL_DATE = to_date('01-OCT-2016','DD-MON-YYYY')
where posting_control_id = -3
and gl_date between to_date('01-SEP-2016','DD-MON-YYYY')
and to_date('30-SEP-2016', 'dd-mon-yyyy')
and CASH_RECEIPT_ID = 4781;

commit;

update AR_PAYMENT_SCHEDULES_ALL
set GL_DATE_CLOSED = to_date('01-OCT-2016','DD-MON-YYYY'),
ACTUAL_DATE_CLOSED = to_date('01-OCT-2016','DD-MON-YYYY'),
GL_DATE = to_date('01-OCT-2016','DD-MON-YYYY')
where CASH_RECEIPT_ID = 4781;

commit;

update xla.XLA_EVENTS ev
set ev.EVENT_DATE = to_date('01-OCT-2016','DD-MON-YYYY')
where ev.event_date between to_date('01-SEP-2016','DD-MON-YYYY')
and to_date('30-SEP-2016', 'dd-mon-yyyy')
and ev.event_status_code <> 'P'
and ev.APPLICATION_ID = 222
and ev.ENTITY_ID in (
select et.entity_id
from xla.xla_transaction_entities et
where et.source_id_int_1 = 4781
and et.application_id = 222);

commit;

AR Checking Query

http://receivablesar.blogspot.com/2016/09/ar-checking-query.html

Customer Checking

select count(*)
  from RA_CUSTOMER_TRX_ALL          ll,
       ar_customers                 kk,
       RA_CUST_TRX_LINE_GL_DIST_ALL jj,
       gl_code_combinations         gcc,
       Ra_Cust_Trx_Types_all tt
 where kk.CUSTOMER_ID = ll.BILL_TO_CUSTOMER_ID
   and jj.CUSTOMER_TRX_ID = ll.CUSTOMER_TRX_ID
   and gcc.CODE_COMBINATION_ID = jj.CODE_COMBINATION_ID
   and tt.CUST_TRX_TYPE_ID=ll.CUST_TRX_TYPE_ID
   and ll.ORG_ID=jj.ORG_ID
   and tt.ORG_ID=  jj.ORG_ID
   and jj.ORG_ID=82   --479

 
 and gcc.SEGMENT2 = '001'
 and kk.customer_id !=1040 --001

  --and gcc.SEGMENT2='002'
 --and kk.CUSTOMER_ID !=1043 --002

-- and gcc.SEGMENT2='002'
 -- and kk.CUSTOMER_ID !=1047 --002


---------------------------------------------------------

Transaction Type and Line Item Location Checking

select count(*)
  from RA_CUSTOMER_TRX_ALL          ll,
       ar_customers                 kk,
       RA_CUST_TRX_LINE_GL_DIST_ALL jj,
       gl_code_combinations         gcc,
       gl_code_combinations gc,
       Ra_Cust_Trx_Types_all tt
 where kk.CUSTOMER_ID = ll.BILL_TO_CUSTOMER_ID
   and jj.CUSTOMER_TRX_ID = ll.CUSTOMER_TRX_ID
   and gcc.CODE_COMBINATION_ID = jj.CODE_COMBINATION_ID
   and tt.CUST_TRX_TYPE_ID=ll.CUST_TRX_TYPE_ID
   and gc.CODE_COMBINATION_ID=tt.GL_ID_REC
   and gcc.SEGMENT2!=gc.SEGMENT2