From AX User Guide,
The Global Accounting Engine does not support the following actions during a Customer or Supplier Merge because they violate reconciliation principles ensured by Global Accounting Engine reports:
- Deleting a customer after a merge.
- Creating accounting entries after a multiple merge.
- Merging unsuccessfully, such as a merge in Payables where only some of the invoices have been merged.
- Merging suppliers, when the new supplier site code already exists in another organization that has the same set of books ID.
R12 - GL / XLA / FAH - How to disable Create Reporting Sequence Number (which used to run when a period is closed in GL)?Submitted by vamsi kasina on Sun, 2009-06-07 04:00
Note that if Create Reporting Sequence Number is disabled, Reporting Sequences will not be generated in GL/SLA.
1. Log in as sysadmin user.
2. Choose the responsibility Workflow Administrator Web Applications.
3. Select the page Business Events.
4. Search for "oracle.apps.gl.CloseProcess.period.close" (enter this in the name field and press Go).
5. Click on Subscription
6. Update the Event, which is having the function as "xla_reporting_sequence_pkg.period_close".
7. Make it Disable.
AX (Global Accounting Engine) creates journal entries only when the accounted amount is not equal to Zero.
As AX summarizes the journal entries by Plan Name (Accounting Class), Code Combination Id, Third Pary Id and Sub Id, if the accounted amount becomes zero, in those cases AX won't create Journal Entries.
Hope you haven't selected Report parameter as "No Report".
Create Accounting has mainly two templates.
"Subledger Accounting Program Report - Standard" inturn calls "Subledger Accounting Program Report - Sub Template".
"Subledger Accounting Program Report - Sub Template" is a sub template and shouldn't be used directly while submiting the Create Accounting.
If the output is blank, the template needs to be crosschecked, which is available in the Options Button of the SRS window.
SELECT text FROM all_source WHERE name = UPPER('&package_name') AND line = 2;
Are you using MO view like ap_invoices? For all org_ids' data -> Use ap_invoices_all For specific org_id's data -> 11i -> dbms_application_info.set_client_info(&org_id); R12 -> mo_global.set_policy_context('S',&org_id);
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.xla_transaction_entities (application_id, entity_id)
R12 - XLA / FAH - Create Accounting (with Transfer to GL parameter as Yes) is not transferring all the journal entries to GLSubmitted by vamsi kasina on Sat, 2009-06-06 12:59
Create Accounting (with Transfer to GL parameter as Yes) will transfer only the journal entries to GL, which have been created by the same Create Accounting run.
To transfer the journal entries to GL, which have been accounted by previous Create Accounting (with Transfer to GL parameter as No) runs, "Transfer Journal Entries to GL" concurrent program needs to be run.
Online Accounting: (For single entity / transaction)
Only few subledgers are providing this feature.
Draft will create journal entries, which are not final, which means they are not ready to be transferred to GL.
You can see the accounting in xla_ae_headers and xla_ae_lines.
Client Industry - Professional Services Firm implementing Oracle Project Accounting which has Global Operations.
Business Case - Canadian employee travels to US to work on a US project.