Make Dependent VS Enterable Without Passing Parent VS

While creating dependent value set in EBS, we found dependent (child) field is greyed (disabled) at beginning until parent field gets some value.

Requirement is to enable child field from beginning even though parent field does not have any value passed.

Supplier site is dependent on supplier and hence is disable initially and get enabled once supplier name will have value.

Above will be achieved by adding below in where condition –

WHERE and ORDER BY

Vendor_id = :$FLEX$.Supplier_test

Solution dependent VS can be enabled since beginning by modifying the above WHERE condition as below –

WHERE and ORDER BY

Vendor_id = :$FLEX$.Supplier_test:NULL

This will enable site value set.

From : Dixidha

More than 2 column values in LOV

To enable LOV on a parameter, a Table value set is associated with parameter field. While running LOV displays Value and Meaning values in LOV window.

Requirement is to add extra additional fields in LOV.

Fox example if we have supplier site LOV along with site code and site name, supplier name will add extra advantage to pick the right site if we have same name sites available.  

Solution is additional columns option available on value set definition form.

Syntax

Column_name1 “Alias” (*),Column_name2 “Alias” (*),….

                                                                                                                                                                                                                       

 

Craeted VS supplier site and added below in additional columns

 segment1 “VendorName”(*),vendor_id ”Vendor_id”(*)

Supplier LOV shows vendor name, vendor number and vendor id.

From : Dixidha

Initialize Apps Context in Java file while creating dependent VS in WEBADI

Oracle provides standard class which can be used to initialize the apps context (set policy context) in java files if required –

 

Class Name – PaMoInit

Method – MoInit

Location - oracle.apps.pa.webadi.utilities

 

Call –

PaMoInit.MoInit(paramBneWebAppsContext);

 

 

This can be simply import if we are in PA module. Please check if same exist for any other modules otherwise creates below method and register (place) at some places.

 

 

package oracle.apps.pa.webadi.utilities;

import java.sql.CallableStatement;

import java.sql.Connection;

import java.sql.SQLException;

import oracle.apps.bne.exception.BneException;

import oracle.apps.bne.framework.BneWebAppsContext;

import oracle.apps.fnd.common.VersionInfo;

 

public class PaMoInit

{

  public static void MoInit(BneWebAppsContext paramBneWebAppsContext) throws SQLException, BneException

  {

    Connection localConnection = paramBneWebAppsContext.getJDBCConnection();

    String str = "";

    CallableStatement localCallableStatement = null;

 

    StringBuffer localStringBuffer = new StringBuffer();

 

    localStringBuffer.append("begin PA_MOAC_UTILS.INITIALIZE; end;");

    localCallableStatement = localConnection.prepareCall(localStringBuffer.toString());

    localCallableStatement.execute();

    localCallableStatement.close();

  }

}

 
 

No Parameter List Definition at Parameter list id

 

Issue Cause – Such issue will occur only when integrator is being created by modifying existing integrator LDT file.

Integrator definition section contains upload (UPL) and import (IMPORT) and import list details. Integrator

 

This error occurs if defined details at integrator level do not have correct definition-  

 

IMP_TRANS_GROUP in XXXXX schema is one of the import list associated to integrator.

 

Import list definition is as below -

 

Seems the definition is also defined in XXXXX schema only still we got above error.

 

Root Cause – There is a difference in STRING_VALUE.

275:IMP_TRANS_GROUP , this is not a simple string this is APPLICATION_ID:IMPORT_List Name

 

Solution –

STRING_VALUE = "2000:IMP_TRANS_GROUP"

Will be the right value since XXXXX, application is 20000.

 

Change the LDT and upload, issue will be resolved.