Error – trigger ja_in_ap_aida_before_trg on ap_invoice_distributions_all : Attribute DEDUCTOR_TYPE is not defined

While validating Invoice on which TDS is applied via DFF - additional information for India , system is giving this error - trigger ja_in_ap_aida_before_trg on ap_invoice_distributions_all : Attribute DEDUCTOR_TYPE is not defined

As mentioned in the error message Deductor type is not defined, hence system is not allowing to validate the Invoice’s. Do the following setup in your instance.

Navigation:

India Local Payables > India TCS/VAT/Service Tax/FBT > Setup > Regime Registration

Query the TDS tax regime

In the Regime Registration Details section, add the value Registration Type = 'Others' and Registration Name = 'Deductor Type'. Select the appropriate value for the field 'Registration Value' and Save.

After doing this setup system will allow to valide the Invoice.

---X---

How to bring Excise/VAT Invoice number in ‘Reference’ field on Receivables Transaction Workbench in Oracle R12 ?

For displaying Excise and VAT Invoice number in the Reference field the profile option ‘JAI: Include Excise and VAT Invoice Number in AR transactions – Reference’ should be set to ‘Yes’

A new procedure has been introduced in Release 12.1.3 for updation of Excise/VAT invoice Number on Receivable Transaction Workbench Reference. JAI_AR_MATCH_TAX_PKG.display_vat_invoice_number. 

If the VAT/Excise Invoice number has already been generated before the Auto Invoice import process then run ‘India - Local Concurrent for Processing Order Lines to AR’ which fires the necessary procedure and brings the VAT/Excise Invoice number in Reference field.

Run concurrent ‘India - Importing Excise/VAT Invoice Numbers in AR’, if the VAT/Excise Invoice number is generated after the auto invoice import process.

In case of Manual Receivable transactions, concurrent Program 'India - Update Excise/VAT Invoice Number in Reference of Receivables Invoice' shall be invoked to populate Excise/VAT invoice Number on Receivable transaction workbench reference. This concurrent will be invoked on its own as soon as the Manual AR transaction is being completed.

Note:

The Invoice source used in Manual Invoice should be a bonded one; else Excise Invoice number won’t be generated.

---X---

ORA-06503: PL/SQL Function returned without value in Package INV_Validate_Trolin Procedure Attributes

When trying to create a new batch, following error is occurring:

ORA-06503: PL/SQL Function returned without value in Package INV_Validate_Trolin Procedure Attributes 

Cause:

The issue is occurring when, an item is used in the formula with an UOM that is neither primary or secondary item UOM and there is no conversion defined between the formula UOM and primary or secondary UOM.

Solution:

Check whether wrong UOM is entered mistakenly in Formula. If UOM’s were entered as required then define correct UOM conversions for items used in formula.

---X---

How to change the order in which the Periods appear in Control Purchasing Periods page ?

By default the sorting in the Control Purchasing Periods page happens in the following order - Closed, Never Opened and then Open. This does not make any business sense and it should be sorted by the Period name like the latest period first, then the previous periods and so on. Right now to view the open periods it is necessary to move to the nth page (depending upon the number of years Oracle Apps is in use) to obtain the data. 

Even-though currently there is no functionality to sort based on the Period status, through the following workaround we can achieve the above mentioned purpose.

Click on “Personalize Page”

Expand Advanced Table: Control Purchasing Period > Column: (NumberColumn) > Column Header > Sortable Header: Period Number.

Click Update button

At all the levels “Inherit” will be defaulting.

 

Against “Sort Allowed” change it to “Yes” at the desired level.

Log out of the application. Sign back on.

Open Control Purchasing Periods page, type a value into the “Fiscal year” field & Click Go

Now by clicking on the “Period Number” it should sort ascending and descending.

Note:

This is applicable only for versions 12.0.0 to 12.1

Customers have already raised an enhancement request to display Purchasing periods in chronological order like in all other modules. Hope Oracle will rectify this bug in 12.2 releases.

---X---