SQL to register custom Interface

Question

Steps to register a custom interface are given below.
1) Assign iSetup super user role.
2) Create Function
3) Create Menu
4) Create Grant
5) Register Interface.
Since it consumes good amount some time, it may not be required in development or UT environments. I have provided the query that would directly register interface with iSetup schema without having to go through the above flow.
Also, this provides a chance for customer who are on 11.5.10.2CU to create and register customer interfaces with iSetup.
Please note that this short cut must be used only in development and UT environments.
INSERT INTO az_apis
API_NAME,
APPLICATION_SHORT_NAME,
SEQ ,
DISPLAY_NAME,
DESCRIPTION,
COMMIT_IF_WARNING,
TYPE_CODE,
METHOD_NAME,
PATH,
CREATED_BY,
CREATION_DATE,
LAST_UPDATED_BY,
LAST_UPDATE_DATE,
LAST_UPDATE_LOGIN,
API_CODE,
SEQ_NUM,
API_DESC,
COMMIT_IF_WARNING_FLAG,
API_TYPE,
REPORT_LAYOUT,
FILTERING_PARAMETERS,
DATA_SOURCE_NAME,
UPDATABLE_FLAG,
CHANGE_UPDATABLE_FLAG,
ALLOW_SET_TARGETVAL_FLAG,
ALLOW_FILTER_FLAG,
API_STANDALONE_FLAG,
ACTIVE,
DISABLE_REPORT_FLAG
VALUES
NULL ,
:1 ,
NULL ,
:2,
NULL ,
NULL ,
NULL ,
'importFromXML',
:3,
1,
to_timestamp('03-JAN-07','DD-MON-RR HH.MI.SSXFF AM'),
1,
to_timestamp('21-MAR-07','DD-MON-RR HH.MI.SSXFF AM'),
0,
:4,
NULL,
NULL,
'N',
:5,
'MULTIPLE',
:6,
NULL,
NULL,
NULL,
NULL,
'Y',
'Y',
'Y',
NULL
Where
          *:1 => APPLICATION_SHORT_NAME* => Product code under which you would like to register the interface.
          *:2 => DISPLAY_NAME* => Any user friendly name to identify the API. This would appear as data object name while creating custom selection set.
*:3 => PATH* => Path to lct file or Java path to refer AM.
Example, for BC4J iSetup framework API => oracle.apps.az.isetup.server.ReportCurrenciesAM
for Generic Loader (FNDLOAD) API => patch/115/import/mysamplelct.lct
*:4 => API_CODE* => A unique identifier to register the API.
                              Naming convention => Application Short Name + “_” + API Name without any spaces.
                              Example => AZ_Currencies
*:5 => API_TYPE* => Type of API.
For iSetup framework BC4J APIs => BC4J
                              For generic Loader APIs => FNDLOAD          
          *:6 => FILTERING_PARAMETERS* => Filtering Parameters is stored as XML. Keep it NULL if there are no filtering_parameters.
I have provided a sample XML.
<?xml version="1.0"?>
<parameters>
<conjunction>AND</conjunction>
<language></language>
<mode type = "Export">
<param type = "NameValuePair" seq = "1" display = "DisplayEnabled" editable = "Editable">
<operator>=</operator>
<separator></separator>
<name>PRODUCT_CODE</name>
<value></value>
<msgcode>AZ_R12_PRODUCT_CODE</msgcode>
<appcode>AZ</appcode>
<filtercode></filtercode>
<datatype>java.lang.String</datatype>
<sqlforlov>select distinct product_code from fnd_application_vl</sqlforlov>
<sqlforlovcol>PRODUCT_CODE</sqlforlovcol>
</param>
</mode>
</parameters>
Delete Record Query
          DELETE FROM az_apis WHERE api_code= :1;
where
*:1 => API_CODE* => A unique identifier to register the API.
                              Naming convention => Application Short Name + “_” + API Name without any spaces.
                              Example => AZ_Currencies

Answer 1

Have your signed your assembly ??
Microsoft Dynamics CRM Training|Our Blog |
Follow US |
Our Facebook Page |
Microsoft Dynamics CRM 2011 Application Design
Make sure to "Vote as Helpful" and "Mark As Answer",if you get answer of your question.