LOV in WebADI - Component

Interface property can be used to set the value set. This will provide list option in excel sheet and will have limitation on values.

Usages of component will provide standard EBS LOV option. Steps are as below -

 

 

1)      Desktop Integration Manager (R) >> Manage Component >> Create Component

Provide display name, internal name and application.

Component Type:

LOV-Table -  

Ø  SQL details will be provided into interface column properties

Ø  Component name should be provided in interface column properties

 

LOV-JAVA (Please click here)

Complete component details and apply.

Table_column-alias – Interface column name

Table_column – Value set column name (Meaning)

Table-select-column - Interface column name

 

 

Go to interface >> properties window and provide the component created.

 

 

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.

 
 

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.

 

 

Desktop Integrator - A webADI Introduction

Introduction :

For single records transaction Oracle suggest to use the application and
provides open interface and public APIs for bulk transaction.

webADI is another strong feature provided by Oracle for bulk operations,
which allows user to provide input in MS application (Word or Excel..etc).

Why WebADI ? :

It requires technical expertise for both interface and API usages.

For interface user should know to insert all transactional data into interface table and API needs transactional data to be imported in any portable format to server.

WebADI does not have such technical dependency as it is available to user as function and Launch desktop integrator (Excel) to feed transactional data.

This provides reporting option also.

How It works :

        For this one interface package required to do  initial validations.

Post it we can use any of options -   

1) Either insert all data into Interface Tables and run the Import
    Program Manually

2) Call API inside the interface program and do transactions directly  

Components  :  

1) Integrator  - Basic definition and includes user name, internal
                       name and application name

2) Interface   -  Most Important section , which directs data to flow (can
                       be either of Table or Procedure/Function type)

3) Content  -    This is required if webADI is being used for reporting
                       purpose also

4)  Upload    -   Controls the upload options

5)  Importer –  Definition of import options

6)  Layout  -     Attributes arrangement on excel

    

Responsibility - Desktop Integration Manager