Friday, June 29, 2018

Can Not Change Supplier Type in Create Supplier Page

While Create Supplier the attribute 'Supplier type = Standard supplier' is disabled and can not be changed.

Cause : 

As part of the functional design for R12, only users who have access to 
the function POS_HT_SP_EMP_SUPPLIER can create/update employee suppliers. By 
default the creation/update of employee suppliers is disabled.

Solution : 

As part of the functional design for R12, only users who have access to
the function POS_HT_SP_EMP_SUPPLIER can create/update employee suppliers. By
default the creation/update of employee suppliers is disabled. The customer
needs to implement a few setup steps to grant access to it. This can be done
by either:

1. Include the function POS_HT_SP_EMP_SUPPLIER with the grant flag checked in
the menu of the customized responsibility which the customer plans to have
access to both standard and employee vendors.

2. Check the grant flag for the function POS_HT_SP_EMP_SUPPLIER in the menu
POS_HT_SP_FULL_ACCESS_MENU. However then all users that can create standard
supplier will also be able to create employee supplier.
After making and saving the change as in 1 or 2 above, the system will recompile the menus through a concurrent request. Please record the concurrent request id and wait for request to complete.
Once the concurrent request is completed, the customer should bounce the Apache middle tie server so that the function security related caches will be clear and your changes above can be effective. Users having the grant will be able to create employee suppliers.

If you can not bounce the Apache server, you can clear the caches by selecting:
  1. Functional Administrator responsibility
  2. Go to Core Services tab
  3. Click Caching Framework
  4. Tuning in the sidebar
  5. Search all caches with Application Name of Application Object Library
  6. Select and click Clear Cache. Please clear all of them, not just the first 20 shown.
After this, you can see the Supplier used to process expense payments to internal employees in the supplier type drop-down list in the create supplier page.

Below is the Step by Step solution to solve this issue

 


In the below picture, supplier type is the only value. LOV is not available.




Query the Menu PO_SUPERUSER_GUI – India


Choose sub menu Purchasing SuperUser GUI


Query the sub menu Purchasing SuperUser GUI


Choose sub menu Supply Base:  Management


Query sub menu Supply Base:  Management


Choose sub menu Supplier Information Management (Buyer View)


Query sub menu Supplier Information Management (Buyer View)

Include the function POS_HT_SP_EMP_SUPPLIER with the grant flag checked in 
the menu of the customized responsibility which the customer plans to have 
access to both standard and employee vendors.

Check the grant flag for the function POS_HT_SP_EMP_SUPPLIER in the menu 
POS_HT_SP_FULL_ACCESS_MENU. However then all users that can create standard 
supplier will also be able to create employee supplier.

After making and saving the change as in 1 or 2 above, the system will recompile the menus through a concurrent request. Please record the concurrent request id and wait for request to complete.



Add the same in Purchasing SuperUser GUI sub menu also



Once the concurrent request is completed, the customer should bounce the Apache middle tie server so that the function security related caches will be clear and your changes above can be effective. Users having the grant will be able to create employee suppliers.

If you can not bounce the Apache server, you can clear the caches by selecting:
  1. Functional Administrator responsibility
  2. Go to Core Services tab
  3. Click Caching Framework
  4. Tuning in the sidebar
  5. Search all caches with Application Name of Application Object Library
  6. Select and click Clear Cache. Please clear all of them, not just the first 20 shown.
After this, you can see the Supplier used to process expense payments to internal employees in the supplier type drop-down list in the create supplier page.


Ref : R12: Can Not Change Supplier Type in Create Supplier Page (Doc ID 433746.1)


****************************நன்றி****************************


Wednesday, June 27, 2018

PLS-00201: identifier must be declared


Today I tried to compile an Invalid Object and faced the below.

Issue : 

SQL> ALTER PACKAGE OWAPUB.OWA_OPT_LOCK COMPILE BODY;

Warning: Package Body altered with compilation errors.

SQL> show error
Errors for PACKAGE BODY OWAPUB.OWA_OPT_LOCK:

LINE/COL ERROR
-------- -----------------------------------------------------------------
40/12    PL/SQL: Statement ignored
40/12    PLS-00201: identifier 'SYS.DBMS_SYS_SQL' must be declared
72/5     PL/SQL: Statement ignored
72/5     PLS-00201: identifier 'SYS.DBMS_SYS_SQL' must be declared
102/6    PL/SQL: Statement ignored
102/6    PLS-00201: identifier 'SYS.DBMS_SYS_SQL' must be declared
144/6    PL/SQL: Statement ignored
144/6    PLS-00201: identifier 'SYS.DBMS_SYS_SQL' must be declared
SQL>


Reason : In this case, the PLS-00201 error indicates that the referenced package (SYS.DBMS_SYS_SQL) does not exist, does not have execute permission or is invalid.

Solution : Grant Execute permission to the desired identifier.                                                 
SQL> grant execute on SYS.DBMS_SYS_SQL to OWAPUB;

Grant succeeded.

SQL> ALTER PACKAGE OWAPUB.OWA_OPT_LOCK COMPILE BODY;

Package body altered.



****************************நன்றி****************************











IAS Cache initialization failed

 Today I faced an Issue in R12.2 instance. The solution I followed to overcome the issue is very simple, but they are more than one solution...