Required upload column was not in upload and has no default value defined

Error -

Getting error “Required upload column was not in upload and has no default value defined” while uploading the WebADI.

 

Cause –

There will be one NOT NULL column in interface and passed no values in upload.

 

Resolution -

Either provide the value or define the default values.

 

Select List of Values option (put the cursor on error message in excel) from Menu ( Oracle Add in).

 

This will help to know the problematic column name.

 

 

Remove Control M Character from unix file

Use Dos2unix command to remove control M characters from any shell script or prog files.

Syntex
Dos2unix <file_name>

Example
Dos2unix Sandeep.sh
Dos2unix Sandeep.prog  

Value for the Flexfield Segment does not Exist in the Value Set

 

 

Defining a value set on any DFF will disallow to search records having non eligible (out of value set range) segment values.

 

A good example of this is to create a DFF of segment project task name. Initially associate a value set of Table type which shows all tasks from pa_tasks_all.

We create some records using assigned DFF. After sometime update value set definition to restrict disabled/end dated tasks.

 

Now search for records which has been created earlier and having disabled tasks assigned. Oracle form will throw below error message –

 

 

Approach – Try restricting the validation query while search.  

 

Solution – We faced similar issue and did below steps to overcome issue –

           1) Created a profile (XXXXX_SANDEEP_PRF) and set value as N

           2) Updated the value set query as

 

           Current condition –

           WHERE   sysdate between start_date and nvl(completion_date,sysdate)

 

           Updated Condition –

            WHERE  (sysdate between start_date and nvl(completion_date,sysdate))

                               OR

                               (nvl(:$PROFILES$.XXXXX_SANDEEP_PRF,'Y')='N')

           3) Use form personalization to change the profile value in cache in search and edit mode

           4) Set the profile value =Y, when in Edit mode. This will fail the second condition and only first 

                     condition will be valid and so only active task will appear in LOV.

          Set the profile value = N when in search mode. First condition will be failed since task is  

              end dated but profile condition will pass and so record will appear without error.

            5)  Did not try this in same form. We have created 2 form functions ( Entry (profile Y) and 

                 Enquiry (profile N) mode)

 
 

 

Change the profile value at run time in Core Forms

We have one custom profile which value is set at different levels. Need is to change the value while working on core forms.

                                                

This can be achieved using form personalization. Form personalization has 4 different actions type.

    1)    Property

    2)    Message

    3)    Builtin

    4)   Menu

 

Builtin provides capability to change the profile value during run time in cache.

 

 

This will change the profile value in cache during run time J

 

 
 

 

Increase no of Searched Records on OAF page

Requirement:

 OAF page search result appears in table and display by default 10 rows. We need to click next to see another 10 records and keep pressing next.

This will be frustrating when the number of records is more than 100.

 

 

Resolution:

Default search results count can be increased by OAF personalization.

 

Steps:

1)     Enable the personalization link on OAF page ( if not available)

2)     Click on the highlighted link

 

 

3)       Click on pencil icon

 

4)       Set the value at required level

 

5)       Click on apply and return to application

 

6)       Check the result count. It is increased to 49 now J

 

 
 

FNDLOAD for Audit Configurations

Below is the LCT file and syntex to download the LDT version of oracle Audit configurations


File Name - affaudit.lct

FNDLOAD apps/$apps_Pwd 0 Y DOWNLOAD $FND_TOP/patch/115/import/affaudit.lct $file_Name.ldt FND_AUDIT_GROUPS GROUP_NAME="$Group_Name"

 

oracle.jbo.JboException: JBO-29000: Unexpected exception caught:

Error Message :

Exception Details. 
oracle.apps.fnd.framework.OAException: oracle.jbo.JboException: JBO-29000:
Unexpected exception caught: oracle.classloader.util.AnnotatedNoClassDefFoundError, msg=
  
Missing class: XXXX.oracle.apps.po.document.order.webui.XXXXOrderPaymentDetailsCO (wrong name: oracle.apps.po.document.order.webui.XXXXOrderPaymentDetailsCO)

 Dependent class: XXXX.oracle.apps.po.document.order.webui.XXXXOrderPaymentDetailsCO
          Loader: oacore.root:0.0.0
     Code-Source: /oracle/ebs/apps/apps_st/comn/java/classes/
   Configuration: <library> in /oracle/ebs/apps/apps_st/comn/webapps/oacore/

The missing class is not available from any code-source or loader in the system.


Cause :
Above error message states that extended CO (XXXXOrderPaymentDetailsCO) is not available at ight place. As per EBS practise all custom code should be placed on cstom top  whch reference are provided on personalization (controller path).

In JAVA file, first line denotes package reference,it's like location of CO files, The above error occurs if package name location <> 
cumtom path given in personalization page <>
custom CO is not avaialble at location


Resolution :
Ensure all 3 things ate having same path. i.e.
Custom code are placed @ right location
Same location is mentioned in java file @ first line ( package)
same path is referenced while personalization



 

Remove VO personalization

Personalization page supports to extend and remove the controller (CO) but no interface to extend the VO. 

VO extension requires Jdeveloper to create substitute, which will generate .jpx and server.xml files.
Later JPXImporter will apply extended VO to system.

To backout the extended VO, we can use database scripts to delete personalizations .

refer OAF migration

Steps to back out VO extension -
1)  Get the original VO name ( with complete path). This will be document path.
      Example /oracle/apps/po/lov/server/DocumentNumbersVO 

===========================================================
Use listcustomization to find the personalization details

BEGINJDR_UTILS.LISTCUSTOMIZATIONS('/oracle/apps/po/lov/server/DocumentNumbersVO');
END;

===========================================================
Use delete script to delete the personalization

Begin

jdr_utils.deletedocument(p_document=>'/oracle/apps/po/lov/server/customizations/site/0/DocumentNumbersVO');
END;

=========================================================== 

How to restrict LOV data in EBS

Requirement is to restrict some data from LOV available on OAF pages or Core Forms.

 

If LOV is available at Core forms, it’s difficult to restrict data as core form personalization does not support this level restriction.

If we are at OAF page view extension (OAF customization) is the option to restrict LOV data. In next lines we shall discuss an easy method to restrict data in LOV for both Core forms and OAF pages.

 

How to achieve this?

It’s quite easier to restrict LOV data using Oracle provided data restriction method. Oracle recommends VPD for data restriction, which can be a better approach over OAF customization.

This can be useful for core forms as well.

 

Use below steps to implement this –

>Find out the source for LOV data –

OAF Page – Go to about this page >> Find associated VO >> Check the underlying SQL

>> Find the table/view having actual data >> Use VPD to restrict the data on source table/view

 

Core Form – Get the fmb file (from AU_TOP) and open in form builder >> Find the associated LOV >> Find Attached Data Source

>> Find the table/view having actual data >> Use VPD to restrict the data on source table/view

 

Use of VPD over OAF customization will be easy to maintain and deploy to higher instances.

 

Example:

Restrict Create Order options on order (Buyer work center) page:

Create LOV has 2 options 1) SPO and 2) CSPO >> we need to exclude SPO option

 

Find the source for LOV data and got that source table is PO_DOC_STYLE_LINES_TL

 

Created function to restrict SPO on the source table

   

                     

                      

                       

 

 

 

 

 

 

Add this function to policy.

 

 

 

 

 

 

 

 

 

 

 

Go to application and check the create option –

 
 

What is Virtual Private Database (VPD)

VPD is new Oracle Database feature to enable policies on database objects ( i.e Table, Synonyms, View etc) This is used to control data access for security reasons.

 

What actually VPD does >> this append additional where condition to objects based on defined policies.  

 

How to use VPD>> below are the steps used to implement VPD in system.

1)     Identify the object:  Lest take APPS.PO_HEADERS_ALL (Synonym) for VPD testing.  

2)     Create the function: Create a function ( or package.function) which will return the required filter condition

3)     Add to policy – Use standard oracle API to create a policy for created function ( step 2)

  

Example –

Step#1) Assume PO_HEDAERS_ALL has 100 records. Will update DFF Column (Attribute1) =’Sandeep’ for any 10 records.

Requirement is  to restrict data having DFF value as ‘Sandeep’ for schema ‘xxxxx’.

 

Step#2) Created function Sandeep

 

 

 

 

 
 

 

 Step#3) 

 

 

 

 

 

 

  

Now run the below statement –

 

APPS Schema

Select count (1) from PO_Headers_all  

>> 100 rows selected

 

XXXXX Schema

Select count (1) from PO_Headers_all  

>> 10 rows selected

 

APPSQUERY Schema

Select count (1) from PO_Headers_all  

>> 100 rows selected

 

 

VPD is one of the major changes in MOAC concepts in R12.