Archive
APP-AR-11017: Recreation of Payment Schedules failed because the transaction has activity against it
APP-AR-11017: Recreation of Payment Schedules failed because the transaction has activity against it
one of the cause for this error in AR will be different Payment terms id in AR_PAYMENT_SCHEDULES and RA_CUSTOMER_TRX
check term_id in both table if they are not the same update accordingly
Localizzazioni Financials Rel 11i vs Rel 12: Reports
Please find the Localization Report Mapping between 11i vs 12
R12 Subledger Accounting Process Events
You can run accounting in two ways, one is Online other is batch mode. Online accounting is ideal when you want to generate accounting event for one transaction. Batch mode accounting process will be initiated by submitting accounting concurrent request (Create Accounting, Submit accounting)
There is no difference if you run online accounting or batch accounting in terms of the event generation. Only different is in detailed reporting
Tables that are involved in this process are
XLA_TRANSACTION_ENTITIES
XLA_EVENTS
XLA_AE_HEADERS
XLA_AE_LINES
GL_IMPORT_REFERENCES
GL_JE_LINES
GL_JE_HEADERS
GL_BALANCES
Links Between these tables
| GL_JE_LINES (JE_HEADER_ID, JE_LINE_NUM) | GL_IMPORT_REFERENCES (JE_HEADER_ID, JE_LINE_NUM) |
| GL_IMPORT_REFERENCES (GL_SL_LINK_TABLE, GL_SL_LINK_ID | XLA_AE_LINES (GL_SL_LINK_TABLE, GL_SL_LINK_ID) |
| XLA_AE_LINES (APPLICAITON_ID, AE_HEADER_ID) | XLA_AE_HEADERS (APPLICATION_ID, AE_HEADER_ID) |
| XLA_AE_HEADERS (APPLICATION_ID, EVENT_ID) | XLA_EVENTS (APPLICATION_ID, EVENT_ID) |
| XLA_EVENTS (APPLICATION_ID, ENTITY_ID) | XLA_TRANSACTION_ENTITIES (APPLICATION_ID, ENTITY_ID) |
Draft : Draft will create journal entries, which are not final, which means they are not ready to be transferred to GL.
You can create accounting on this transaction again and again, which will delete the old journal entries and create new ones. You can’t transfer these journal entries to GL.
xla_events.process_status_code = D
xla_events.event_status_code = U
xla_ae_headers.accounting_entry_status_code = D
Final : Final will create journal entries, which can be transferred to GL. Once it is finally accounted you can’t run create accounting on the particular transaction (specifically on that event).
Run Transfer Journal Entries to GL program
xla_events.process_status_code = P
xla_events.event_status_code = P
xla_ae_headers.accounting_entry_status_code = F
Final Post: Final Post will create journal entries in final mode, transfer them to GL and post them.
xla_ae_headers.accounting_entry_status_code = F
xla_ae_headers.transfer_status_code = Y
xla_events.process_status_code = P
xla_events.event_status_code = P
Difference between unapplied receipts and receipts on account
First lets start with Unapplied. An Unapplied receipt is one where the customer who submitted payment has been identified but the receipt has not been applied to a specific transaction or placed On Account. From a technical perspective, the status of the receipt remains open and the amount_applied NULL in AR_PAYMENT_SCHEDULES because the amount has not been applied to a customer balance. Furthermore, the applied_payment_schedule_id and applied_customer_trx_id are NULL in AR_RECEIVABLES_APPLICATIONS table because the receipt has not been applied to a specific transaction. There is no GL transaction in this case to reduce the amount of the Receivables account.
When you place a receipt On Account, you are then reflecting a credit for the receipt amount and subsequently debiting a Receivables account and crediting a Revenue account. You would supply the distribution lines for On Account credit since these would not be provide by any specific transaction. The appropriate lines are then created in RA_CUST_TRX_LINE_GL_DIST for these distributions.
The advantages to either scenario just depend on your business need to include or exclude receipts that have not been linked to a specific transaction, in your Receivables account balance.
Also, most reports that include receipt information give you the option to include or exclude both Unapplied and On Account receipts. This assists with reconciliation of account balances. There are also various places in the application where you can choose to include Unapplied amounts. For example, when printing dunning letters, Include Unapplied Receipts check box in the Dunning Letter Sets window, affects whether these receipts are actually printed on your dunning letters. In relation to printing statements, if there are on?account or unapplied receipts that are not associated with a specific customer location, Receivables summarizes these receipts as credits on consolidated statements that you produce by defining a statement site.
Reddy BHIMIREDDY 