My Portfolio

AR Adjustments to SLA Link R12 Accounting Data Model – Adjustments •Where postable <> ‘N’ •Status should be ‘A’ •Distributions stored in AR_DISTRIBUTIONS_ALL (source_table=ADJ) •Debit & credit amounts should match •Adjustments Status = ‘W’ (Waiting for Approval) to either A or R •Adjustments with status R (Reject) should not be processed i.e. EVENT_STATUS_CODE=N •PROCESS_STATUS_CODE=U in XLA_EVENTS AR_ADJUSTMENTS table Important columns in the AR_ADJUSTMENTS table include: ADJUSTMENT_ID column AMOUNT column CUSTOMER_TRX_ID column TYPE column PAYMENT_SCHEDULE_ID column CODE_COMBINATION_ID column The AR_ADJUSTMENTS table stores information about invoice adjustments. Each adjustment is stored as a unique record, based on the primary key adjustment_id. The amount column stores the amount of the adjustment. Receivables uses the customer_trx_id and payment_schedule_id to link the adjustment to the adjusted transaction and to update the amount_due_remaining and amount_adjusted colum...

1 2 3 4 5 6 7 8 9 10 11 12 13 SELECT frv.responsibility_name, fpov.profile_option_value org_id, hou.NAME FROM apps.fnd_profile_options_vl fpo, apps.fnd_responsibility_vl frv, apps.fnd_profile_option_values fpov, apps.hr_organization_units hou WHERE hou.NAME = < OU Name > AND fpov.profile_option_value = TO_CHAR (hou.organization_id) AND fpo.profile_option_id = fpov.profile_option_id AND fpo.user_profile_option_name = 'MO: Operating Unit' AND frv.responsibility_id = fpov.level_value ORDER BY frv.responsibility_name

Query to find Org ID attached to responsibility Get Org id from Responsibility Name 1 2 3 4 5 6 7 8 9 10 11 12 13 14 SELECT frv.responsibility_name, fpov.profile_option_value org_id, hou.NAME FROM apps.hr_organization_units hou, apps.fnd_profile_options_vl fpo, apps.fnd_profile_option_values fpov, apps.fnd_responsibility_vl frv WHERE frv.responsibility_name = < Responsibility Name > AND fpov.level_value = frv.responsibility_id AND fpo.profile_option_id = fpov.profile_option_id AND fpo.user_profile_option_name = 'MO: Operating Unit' AND fpov.profile_option_id = fpo.profile_option_id AND hou.organization_id = TO_NUMBER (fpov.profile_option_value) ORDER BY frv.responsibility_name

Creating Implementation Project in Fusion Financials Login to application with user name and password. Select Setup and Maintenance Select Implementation Projects Select create to create implementation project Enter required details and then select  “Next” Select offering that you want to perform implementation setup then select “Save and Open Project” Then select button “Done”

AR Reconciliation – Internal (Within AR) and External (GL) in R12 Ref: Oracle Webcast – Oracle receivables posting & Reconciliation in R12

Data flow between AR and SLA Queries to retrieve data from XLA tables for a given AR transaction Q1) Get the customer_trx_id for the transaction number SELECT * FROM ra_customer_trx_all WHERE trx_number = &trx_number; Q2) Get the entity_id of the transaction SELECT * FROM xla_transaction_entities_upg WHERE application_id = 222 AND ledger_id = 62 AND source_id_int_1 = &customer_trx_id_from_Q1; Q3) Get the events associated to the entity SELECT * FROM xla_events WHERE application_id = 222 AND entity_id = &entity_id_from_Q2; Q4) Get the headers associated to the event SELECT * FROM xla_ae_headers WHERE application_id = 222 AND event_id in (&event_id_from_Q3); Q5) Get the lines associated to the headers SELECT * FROM xla_ae_lines WHERE application_id = 222 AND ae_header_id in (&ae_header_id_from_Q4); Q6) Get the distributions associated to the headers SELECT * FROM xla_distribution_links WHERE application_id = 222 AND ae_header_id in (&ae_header_id_from_Q4); Data fl...

The Link between GL to SLA and reference columns in GL_IMPORT_REFERENCES Since there is always a one-to-one correspondence between XLA_AE_LINES and GL_IMPORT_REFERENCES, they are used to link GL and the subledgers.  GL_IMPORT_REFERENCES.gl_sl_link_id => XLA_AE_LINES.gl_sl_link_id  GL_JE_BATCHES.group_id => XLA_AE_HEADERS.group_id 6 reference columns REFERENCE5 to REFERENCE10 in GL_IMPORT_REFERENCES can be link to entity_id, event_id, ae_header_id, ae_line_num, and either accounted_cr or accounted_dr.  REFERENCE5 => entity_id REFERENCE6 => event_id REFERENCE7 => ae_header_id REFERENCE8 => ae_line_num REFERENCE9 => accounted_cr REFERENCE10 => accounted_dr Q1. How many group_ids are created during the transfer process when there is a primary ledger and associated ALC/reporting ledger? The primary ledger data and associated ALC/reporting ledger data goes into one group_id. Data from this one group_id can be split across multiple GL Batch...