Wednesday, 8 June 2016

You have VMI or consigned from supplier enabled entries in your operating unit. You cannot use Encumbrance Accounting with VMI.


As per functionality of Oracle Applications, you will not be allowed to use Encumbrance
in the Set of Books or Operating Unit where you have VMI (Vendor Managed Inventory)
enabled. Otherwise, you will get the error message:

"You have VMI or consigned from supplier enabled entries.
You cannot use Encumbrance Accounting. "

In order to disable the VMI and or Consigned, you will have to find all the Item/Supplier combinations.
The simple way to do this is described as follows:

1- Please run the following queries:

Select * from po_asl_attributes where enable_VMI_flag = 'Y';
Select * from po_asl_attributes where consigned_from_supplier_flag = 'Y';

2- This will provide a list of records with the mtl item ids and the ASL ids also.
This will identify all Item - Supplier combinations that have VMI and or Consigned enabled.

3- Navigate to Purchasing - Supply base - Approved Supplier List
Query for the item with Item_id equal to the one in the records above.
Then click on Attributes button in the form.
Here click on Inventory Tab.
Here disable :   the VMI enabled and/or Consigned from Supplier button.

This will disable VMI / Consigned for that Item and Supplier combination.
This must be completed for each record obtained above.

4- Navigate to Setup- Organizations- Financial Options,
and enable Encumbrance Flag.

Note: Following activity is not enough resolve this error.
1. Find out VMI enabled entries from front end using 'Summary Approved Supplier List' 
2. Disble all entries one by one, found by step 1
Because there is no flag provided on 'Summary Approved Supplier List' so that one can find entries and disable it.

So it is necessary to retrieve data using sql queries given above and then disable following flags from all entries one by one.
a. VMI enabled,
b. Consigned from Supplier flag

Tuesday, 1 December 2015

The keyflexfield with application name Receivables (AR), name Territory Flexfield (CT#), and structure Customer Territory Flexfield (CUSTOMER_TERRITORY_FLEXFIELD) is not frozen. Please contact your system administrator.

Following is the error:-
The keyflexfield with application name Receivables (AR), name Territory Flexfield (CT#), and structure Customer Territory Flexfield (CUSTOMER_TERRITORY_FLEXFIELD) is not frozen. Please contact your system administrator.

  


Cause:-
Receivables Key Flexfield 'Territory Flexfield' is not frozen.

Solution:-
Freeze and Compile this KFF and ensure 'Flexfield View Generator' program completes successfully.

Check the program:-
Now you will be able to create Customer succesfully

Monday, 23 November 2015

Order Import request did not return with error when even the order is not imported

Explanation:-

Oracle Order Management - Version: 11.5 to 12.1.3 - Release: 11.5 to 12.1

Order import program will not error out if validation for some attributes fail.
In case of failure, child concurrent program 'Order Import Child Req1 (Order Import)' will not get spawn. Secondly, the log file will tell the total number of orders processed
This is the expected behavior.

Order Import corrections form will show records in red color under the following scenarios :

Case 1.

If the validation for any of the header attribute fails, it doesn't matter whether the validation of lines under it passes/fails. In this case the header record will be set as error_flag='Y' and shown in red where as the lines will NOT be in red color (even though a line contains invalid attributes)

Case 2.

If the header validation passes and any of the line validation fails, then both the header record and the line will be marked as erred and shown in red color.

For example :

If there is an invalid price list at line level, there will be many error occurred at header level. So as per Case1, it will not show the line record in red color. If there are no errors at header level and if there occurs at error at line level then only the line will be shown in red color.

If the order has more than one line and you want to find which line has failed in validation, first you have to ensure that all the validation for the header record is successful. After the header validation is successful and if there is any validation failure for a line, then that particular line will be shown in red color (the header record will also be in red).

Friday, 13 November 2015

'Function not available to this responsibility. Change responsibilities or contact your System Administrator' when go to see 'View Accounting' for PO Receipt through view receiving transaction summary window



Solution:-
1.Go to System Administrator Responsibility
2.Click Application/Menu
3.Query the menu = INV_NAVIGATE
4.Write down the submenu name = INV_TRANSACTIONS 

5.Click Application/Menu
6.Query the menu = INV_TRANSACTIONS
7.Write down the submenu name = INV_RECEIVING 

8.Click Application/Menu
9.query out Menu = INV_RECEIVING
10. Add a new entry:
     Prompt = Accounting
    Submenu = Accounting:
    Function = Blank
    Description = Blank





Tuesday, 3 November 2015

Accrual Reconciliation Report is disabled in upgraded version R12

Our Application is an upgraded version and it is upgraded from 11i to R12.2.4. Accrual Reconciliation Report is disabled.

I enabled it and tried to run from Purchasing Application. Its parameter gave following error:-

1. APP-FND-01564: ORACLE error 942 in FDFGDF 

Cause: FDFGDF failed due to ORA-00942: table or view does not exist. 
On clicking on OK, system showed following error:-

APP-FND-00730: This flexfield has an invalid value set 

Solution:-

Please run AP and PO Accrual Reconciliation Report as this is the newly introduced report for accrual reconciliation in R12 instead of Accrual Reconciliation Report in previous releases. 


Please note that you will need to run Accrual reconciliation load run program first to populate accruals tables where AP and PO Accrual Reconciliation Report reads from . Please Note that the Load Program is the counterpart of the Rebuild manager in Release11i. The Load Program populates CST_AP_PO_RECONCILIATION and CST_RECONCILIATION_SUMMARY with net po_distribution amounts. When the accrual load run program is run for the first time, it will not consider the start date given by the User. It will instead build the data in cst_ap_po_reconciliation, cst_reconciliation_summary, cst_misc_reconciliation tables using the first transaction date available in XLA that has been transferred to GL. It will however build the data to the End Date provided by the User.
 

Friday, 30 October 2015

Is EBTax applicable on Quotations in Oracle Purchasing Release 12?

There is an existing ER BUG 4765613 - INTERNAL REQUISITION TRANSFER CHARGE.

Current R12 Behavior: 


Tax Classification or any tax attributes are not supported in RFQ/Quotation Oracle E-Business Tax User Guide 

Release 12.2 Part Number E48751-03 Section - Managing Configuration Owners and Service Providers - Managing Event Class Settings 

----------------------------------------------------- 
This table lists the event classes that are applicable to E-Business Tax: Application Event Class Payables Standard Invoices Payables Prepayment Invoices Payables Expense Reports Purchasing Requisition Purchasing Purchase Order and Agreement Purchasing Release ..... 


-- > RFQ/Quotation are not applicable to EBtax.

Query to change distribution account wrongly entered by User while processing Inventory Miscellaneous Transaction Form

To change the account for already created distribution you would need to update both MMT and MTA data. 

update mtl_material_transactions 
set distribution_account_id = &new_acct_id -- Get correct account 
where transaction_id in (&trans_ids) 
and distribution_account_id = &old_acct_id; ---Incorrect account 

update mtl_transaction_accounts mta 
set reference_account = &correct_account_id 
where transaction_id in (&your_problematic_txns) 
and reference_account = &prior_wrong_account_id; 

commit; 


Note: The GL Period that the transaction date of the record that is update must be open for the record to be transferred to GL. 

-The Inventory Period is not required to be open for the record to be transferred to GL.