You might face a situation where you need to interchange the values of two columns in an Oracle database table. This article will explore ways to achieve this.

Last week, I worked on schema refresh in 11g database from one box to another box using data pump.

Schema size: around 90 GB.
Version: 11.1.0.7

Method 1:

Normally we follow below steps: (I have sufficient space in file system, so I am using below steps)
1.Export the schema using expdp/exp utility.
2.Compress the dump file.
3.Transfer the data through ftp to another box.
4.Just import it.

Step 2, depend upon dump size.

Note:
I have sufficient space in file system, so I am using method 1.

Method 2:

1.Export the schema using expdp/exp utility (during export they used

During a quite evening of my last on-call bout I was alerted from our monitors that the UNDO tablespace was running out of free space. Thought of adding of a new data file and be done with it; When I checked the current allocation for this tablespace it was already at 40G - couldn't believe what I was seeing. The undo_retention was set to 7200 and max query length in v$undostat was not that high. One column that did caught my eye was the tuned_undoretention, its value was way very high.

Database tables are structured in columns and rows. However, some data lends itself to switching row data as column data for expository purposes. The pivot operation in SQL allows the developer to arrange row data as column fields. For example, if there are two customers who have both visited a store exactly four times, and you want to compare the amount of money spent by each customer on each visit, you can implement the pivot operation.

AX (11i)                                                                        SLA (R12)

Daily Journal Book - Line Descriptions Payable/Receivable/Inventory       Journal Entries Report
Daily Journal Book - Header Descriptions Payable/Receivable/Inventory     Journal Entries Report
Final Daily Journal Book - Header Descriptions                            Journal Entries Report
Italian Journal Book                                                      Journal Entries Report

Sometimes Drilldown from GL will open OA pages and sometimes Oracle Forms.

Here is the reason:

• When the data is from 11i and not upgraded to R12 (means it is not in XLA tables and gl_je_headers.je_from_sla_flag is NULL), then it will open the subledger form directly.
• When the data is from R12 or from 11i and upgraded to R12 (means it is in XLA tables and gl_je_headers.je_from_sla_flag is 'Y' or 'U'), then it will open the SLA OA page first, so that we can check the XLA data and we can open the subledger form through View Transactions button.

If the following error occurs while submitting AX Posting Manager/Post Transactions, then set the profile options, AX Application Name and GL Set of Books Name.
Which will automatically set the other two profiles.

The following are the important profile options, which need to be set to submit AX Posting Manager/Post Transactions.

• AX Application Id
• AX Application Name
• GL Set of Books ID
• GL Set of Books Name

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.

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.