Skip to content

Datafix for Costing

Case: Request ended in Completed – Warning when run:

  1. Create Accounting – Cost Management
  2. Accounting Program


In Subledger Accounting Program Report, found out an error for Miscellaneous Transaction as follows


Analysis: Found out that there are corruption data in XLA tables that caused the error in Create Accounting program. We have to perform datafix on the record. The XLA Event created in 31-Oct-2014 and have no transaction entity. Please find below the datafix script to execute.


1.Check the event

SELECT * FROM xla_events
WHERE application_id IN (401, 707)
AND TRUNC (event_date) = TO_DATE (’31-OCT-2014′, ‘DD-MON-RRRR’)
AND (event_status_code <> ‘P’ OR process_status_code <> ‘P’);

2.Check transaction entity

SELECT * FROM xla_transaction_entities
WHERE entity_id IN (SELECT entity_id FROM xla_events
WHERE application_id IN (401, 707)
AND TRUNC (event_date) = TO_DATE (’31-OCT-2014′, ‘DD-MON-RRRR’)
AND (event_status_code <> ‘P’ OR process_status_code <> ‘P’)


UPDATE xla_events
SET event_status_code = ‘P’, process_status_code = ‘P’
WHERE event_id = &event_id;

Hope this helps.




View : Invoice

Add View Invoice into Purchase Order Summary is as follow:

Go to SysAdmin and check for Function for “View Invoices”. Attach that function to your Purchasing Inquiry resposibility.

Other way is…use below query to find out the list of function attached to any Resposibility. Check for function name for any resposibility where it is enabled and attached it to enquiry resposibility.

SELECT DISTINCT faa.application_name application, rtl.responsibility_name,
ffl.user_function_name, ff.function_name, ffl.description,
FROM fnd_compiled_menu_functions cmf,
fnd_form_functions ff,
fnd_form_functions_tl ffl,
fnd_responsibility r,
fnd_responsibility_vl rtl,
apps.fnd_application_all_view faa
WHERE cmf.function_id = ff.function_id
AND r.menu_id = cmf.menu_id
AND rtl.responsibility_id = r.responsibility_id
AND cmf.grant_flag = ‘Y’
AND ff.function_id = ffl.function_id
AND faa.application_id(+) = r.application_id
AND r.end_date IS NULL
AND rtl.end_date IS NULL
AND rtl.responsibility_name = ‘&Resposibility’
ORDER BY rtl.responsibility_name;




Defining Organization Access

You can specify which organizations a responsibility can access by mapping responsibilities to organizations.

To define access mappings between organizations and responsibilities:
1. Navigate to the Organization Access window.
2. Enter the organization code for the organization to which you are restricting access.
3. Enter the Oracle Applications product containing the responsibility you want to map to the organization entered in the Org field.
4. Enter the name of the responsibility you are mapping to the organization entered in the Org field. You must enter an application before entering a responsibility.
The combination of organization, application, and responsibility determines the access mapping. Each combination must be unique.
5. Save your work.




Inventory Items Type

I’ve got this insight from Oracle Community. One of the authors informed about the kind of inventory item type in simple languange. So, this is it:

The terminology of items is rather confusing from a Purchasing/Inventory
point of view.

For easy understanding, these will be referred to as A , B and C,
A – Expense Items
B – Inventory Expense Items
C – Inventory Asset Items

A – These items have attributes checked

B – These terms have the following attributes checked
a – inventory item = YES
b – stockable
c – transactable
d – Inventory Asset Value = NO
e – Costing Enabled = No

C – These items have the following attributes checked
a – inventory item = YES
b – stockable.
c – transactable
d – Inventory Asset Value = YES
e – Costing Enabled = YES

Hope this helps.



PO Pre-Approved Status

Please find below, the situation where PO will go to Pre-approved status :
1. Pre–Approved document is one in which approvar approves the document but then forwards it to someone else for additional approval, then it goes in to pre approved status

2. Your organization uses encumbrance budgeting (reserves funds for documents), and the purchasing document is eligible for approval but funds have not yet been reserved for it.

Hence if you are using the encumbrance , the Period should be open. If the PO that is in Pre approved is an old PO and the corresponding GL / purchasing period is already closed .
So the issue could be due to the closing of the period for the each month in this case .

If it was working earlier, and if you are not sure of the changes, please Run the program “Fill employee Hierarchy Program” and once it’s completed successfully, you may reset the document to Incomplete status again using the below note

How To Reset a Purchase Order or Requisition From In Process or Pre-Approved To Incomplete/Requires Reapproval For Isolated Cases ( Doc ID 390023.1 ) and submit again.

Before submitting the PO, please check if funds check is passing and able to reserve the document.
Once its done, please submit for approval and make sure that there a default hierarchy is populated while submitting for approval

Hope this clarifies!


Status PO Rejected but in View Action History is APPROVED, What should we do?

(SR 3-17235453221)

Problem Summary
Status PO Rejected but in View Action History is APPROVED, What should we do?

Problem Description
There are 2 PO with status REJECTED but, in View Action History result is APPROVED.

Analytical Files
File: Diagnostics__Apps_Check_060418.txt
File: POAPPANALYZER_Analyzer_PROD_2018-04-06_05_18.html
File: 316542.png;po_12_316542.html

Analyzer execution information
Analyzer Execution Details
Applications Release: 12.1.3
Analysis Mode: SINGLE
Is Cloud environment: N
Analyzer version: 200.15

Operating Unit: 81
Document Type: PO
Document Number: 316542
Release Number: NULL

Profile Options:
User Profile Option Name Profile Option Value Set At
===================================== =========================== ======
PO: MFG Organization ID ** Not Set At Any Level **
PO: Price Tolerance (%) for Catalog Updates ** Not Set At Any Level **
PO:Workflow Processing Mode ONLINE Site

POAPPANALYZER_Analyzer_PROD_2018-04-06_05_18.html shows the following details:
This PO has Authorization Status NULL and is not eligible for reset. Only documents with authorization_status ‘IN PROCESS’ or ‘PRE-APPROVED’ are eligible to be reset.

— Script Output —
File Name or Source:

Description :


06-APR-18 09:04:28 06-APR-18 09:05:00 APPROVE_PO_SUB_PROCESS / UNABLE_TO_APPROVE_DOC Approve PO Unable To Approve Document COMPLETE SEND_BACK_TO_PREPARER FELIX.PARLINDUNGAN 762235 CLOSED 06-APR-18 09:05:00 06-APR-18 09:05:00 APPROVE_PO_SUB_PROCESS / REJECT_PO Approve PO Reject The PO COMPLETE Y 06-APR-18 09:05:00 06-APR-18 09:05:00 APPROVE_PO_SUB_PROCESS / GET_NOTIFICATION_ATTRIBUTE Approve PO Get Preparer Notification Attribute COMPLETE ACTIVITY_PERFORMED 06-APR-18 09:05:00 06-APR-18 09:05:00 APPROVE_PO_SUB_PROCESS / PO_PO_REJECTED Approve PO PO Rejected COMPLETE #NULL BAYU.PUTRA 762238 OPEN 06-APR-18 09:05:00 06-APR-18 09:05:00 APPROVE_PO_SUB_PROCESS / PO_NEW_COMMUNICATION-1 Approve PO PO New Communication COMPLETE Y

WFStat: Notification Attributes

ONLINE_REPORT_TEXT Line 1 Schedule # 1: The Need-By Date and/or Promised Date does not fall within an open purchasing accounting period.


Set the profile option PO: Check open periods to N,

~ Ann

Profile Option “SLA: Enable Diagnostics” : How not to use it

Originally posted 23 December 2008 on

As diagnostics functionality tends to be very useful, most implementers when arriving at a site immediately enable all diagnostics. In case of profile option “SLA: Enable Diagnostics” this might cause more bad than good, and here is why:

First of all it’s important to understand the basic concept of SLA. When SLA creates accounting it doesn’t physically store all the data from the subledgers into the XLA tables. Instead SLA uses views to look directly at the subledger data it requires (you can see these views in the SLA Accounting Event Class Options window under the Transaction Objects tab).

But when profile option “SLA: Enable Diagnostics” is set to Yes, SLA will not only look at the subledger data through the abovementioned views, but it will also physically copy over all that data into an SLA diagnostics table (XLA_DIAG_SOURCES).

The reason why SLA does this is because you enabled SLA diagnostics, so SLA expects that you will want to run the Transaction Objects Diagnostics report. But in order for this report to be able to pick up data, SLA first needs to make the data available, therefore it copies over all the subledger data to the SLA tables so afterwards the Transaction Objects Diagnostics report can print the data for you.

This copy process happens during Create Accounting so when you run Create Accounting while the profile option is set to Yes you should also notice a decrease in the Accounting Program’s performance (because all the inserts into XLA_DIAG_SOURCES are being executed).

Correct order of events when diagnosing SLA:

1) Enable profile option “SLA: Enable Diagnostics”
2) Run “Create Accounting”
3) Disable profile option “SLA: Enable Diagnostics”
4) Run “Transaction Objects Diagnostics” report
5) Run “Purge Transaction Objects Diagnostics”

Keep the profile option away from so-called “overenthusiastic profile option switchers”. I’ve seen a case where the profile option was set to Yes at Site level meaning every single run of Create Accounting copied all source data from all subledgers to the XLA scheme eventually causing the database to run out of space. Although this was in a DEV instance without security policy it still proves that this (and in fact any) profile option should be handled with care – if you don’t know it then please don’t touch it.

When you do use the profile option then use it as it was intended to be used: run Create Accounting for a very small amount of data. It really doesn’t make any sense to try and diagnose a large volume of data because you will get lost in the Transaction Objects Diagnostics’ output file.

When you’re done diagnosing do not forget to switch the profile option back to No.

As soon as you’ve run your Transaction Objects Diagnostics report you can run Purge Transaction Objects Diagnostics request. This will purge the diagnostics data from XLA_DIAG_SOURCES. You can still continue looking at the data because that’s saved in the Transaction Objects Diagnostics’ output file.

taken from