Creating lookup definition

Hi
I want to create a lookup definition which will populate values of one of the user field.
Ex: I have created a form which has one field named UserType and type of the field is LookupField. Now I want to populate all the available User's USR_KEY column in this field.
I have absolutely no idea how to create such a lookup field.
Any help would be appreciated.
Thanking You
Kiran Thakkar

Add an Attribute tag in the FormMetaData.xml file similar to the following
<Attribute name="-15" label="global.label.employeeType" displayComponentType="LookupField" variantType="String" dataLength="255" map="Users.Role">
<ValidValues lookupQuery="SELECT LKV_ENCODED,LKV_DECODED FROM LKU,LKV WHERE LKU.LKU_KEY=LKV.LKU_KEY AND LKU.LKU_TYPE_STRING_KEY LIKE 'Lookup.Users.Role' ORDER BY 1" selectionColumn="LKV_ENCODED"/>
</Attribute>
This is an example i have taken from the existing metadata file. Change the values accordingly. Also change the query according to your requirement.

Similar Messages

Lookup definition - what it is for? how it could be used?

Dear All,
I have a few questions regarding lookup definition.
1.What lookups are for?How they can be used?
2.I noticed a lot of out of the box pre-configured lookups are empty. Why? Hmmmm.... Does not make any sense...
Example,
Lookup.AD.FieldsForValidation
3. It looks like Group field might be empty. Why? Is this when lookup definition used by more than 1 form?
4. What is the naming convention for code field?
I carefully reviewed documentation below:
http://download.oracle.com/docs/cd/B32386_01/generic.902/b32143/oimadm.htm#BABIBJAF
I would appreciate your feedback

My apologies I think I confused you and my question was not clear. (80% already answered by Kevin. Thank you!)
Please let me try to rephrase this for you. (I appreciate your help and guidance!!!!!!)
Lookups are stored in the OIM database .
The purpose:
1. Allow user to select a value from the list.
2. meta data storage (configuration information for adapters, triggers for events, list of available countries, etc. ).Lookups are used by connectors or OIM application itself.
How they can be populated:
1. Through API within your custom task.
2. Out of the box connectors (Lookups for Groups, Organization in AD adapter)
3. Manually by creating lookup definition from Design console.
How they can be used:
1. Set up a query code for the field directly on the Form Designer (Properties tab of the form). FYI There are a few meta link articles regarding lookup manipulation.
2. through FormMetaData.xml configuration.
What is still unclear for me:
I am planning to create a custom lookup that will contain information that will be used for provisioning.
1. Is there a naming convension for Code field that I have to follow for custom lookup definition? Some of the existing out of the box lookups start with Lookup. , some does not..... They follow some kind of a hierarchy. For example, Group.Object Permissions.Allow Delete
2. Why group field sometimes populated, sometimes not? (It is not required for custom lookup definition)
3. How to filter lookup data through API?
http://download.oracle.com/docs/cd/B32386_01/generic.902/b32143/oimadm.htm#BABIBJAF
I will be greatful if you can help me.

Problem using BAPI_BUS2001_CREATE to create project definition

Hi,
i have a problem using BAPI_BUS2001_CREATE to create project definition.
i have customer fields in CI_PROJ structure.
i used help structure BAPI_TE_PROJECT_DEFINITION in EXTENSIONIN table
the problem is that customer fields that i have populated in BAPI_TE_PROJECT_DEFINITION are not processed.
please help.
thanks.

solved,
applay oss note 637345

.xsd in XML Schema in 'Create Data Definition' window

I need to know the following about .xsd file while definining it in the XML Schema in 'Create Data Definition' window:
1. Why to use this file?
2. How to create this file ?
3. Is .xsd file should be different for each different report?
4. Is this file creation is one-time activity for each report?
5. Any details about .xsd file.
Thanks.

The XML Schema is only required if you are using a PDF template (the template file itself is PDF) with field-mapping. For other template types the schema is optional.
The XML Schema is used to define a "class" of XML documents, so to speak. The define the semantics and structure of the XML documents more thoroughly.
If you have closely related reports, you could use a single schema to standardize (in a sense) the XML to be output from the class of related reports. In that case you could have a single schema file uploaded to multiple reports/data-definitions.
The W3C has good documentation on XML Schema.
If you want to see samples, you can use tools such as dtd2xs to create sample schemas from your DTD.

Scheduled task that populates Lookup Definitions from database in oim11gr2

Hi Friends,
How to write a scheduled task that populates the Lookup Definitions from database tables in oim 11g r2.
Regards,
jdev

Check this link http://docs.oracle.com/cd/E27559_01/dev.1112/e27150/refsched.htm#CIHBFCJG

How to create Lookup field in user form in OIM 11g - Urgent

Hi Experts,
How to create Lookup field in User Form - OIM 11g.
Pls. provide your support on priority.
Regards
Karan

Thanks all for your suggestion.
Our requirement, is we need to have a user defined field similar to how its there in "Organisation".
For example we need to create an user defined field like "Service Holding" which holds different services say like Service 1, Service 2, Service 3 etc.
Under each service there are multiple roles....
Eg:
Service 1 - Role 1, Role 2, Role 3
Service 2 - Role 4, Role 5
Service 3 - Role 6, Role 7, Role 8
Is there a way to store multi-valued attribute in OIM UDF? If so, pls. guide us
If its not possible we would need to create a Lookup field (something similar to Organization or Manager). User clicks on the button (lens button), which should invoke an API wherein he can select specific Roles and save in User. Eg. like Service 1 - Role 1#Service 2 # Role 5 and store in the backend database.
Is this possible. Pls. guide.
Regards,
Karan

Create Lookup[Taxonomy] field for same taxonomy in two main tables

In MDM 7.1 SP03,
1) We have two main tables MTable1 and MTable2 in repository
2) One Taxonomy table Taxo1
3) In MTable1, Created a Lookup[Taxonomy] field for Taxo1 table
4) In MTable2, not able to create Lookup[Taxonomy] field for Taxo1
table.
Why is it not allowed to use Lookup[Taxonomy] in multiple main tables?
Thanks,
Rajesh
Edited by: Rajesh Penagalapati on Nov 12, 2009 4:53 AM
Edited by: Rajesh Penagalapati on Nov 12, 2009 4:54 AM

Hi,
Thats a limitation .Multiple Main tables cannnot share the same Taxonomy table.
You can refer the features of MDM 7.1 at
http://help.sap.com/saphelp_nwmdm71/helpdata/en/43/D7AED5058201B4E10000000A11466F/frameset.htm
Regards
Nisha

Error when create project definition and 2 wbs by bapi BAPI_PROJECT_MAINTAI

Hello everyone,
I have to create project definition and 2 wbs, I use function BAPI_PROJECT_MAINTAI but I have the error:
"WBS element 0033.3332.01.R already exists" but that wbs it's created.
This is my code.
data:
         I_WBS_ELEMENT_TABLE type BAPI_WBS_ELEMENT occurs 0 with header line,
         I_WBS_ELEMENT_TABLE_UPDATE type BAPI_WBS_ELEMENT_UPDATE occurs 0 with header line,
         I_PROJECT_DEFINITION like BAPI_PROJECT_DEFINITION,
         I_PROJECT_DEFINITION_UPD like BAPI_PROJECT_DEFINITION_UP,
         I_METHOD_PROJECT type BAPI_METHOD_PROJECT occurs 0 with header line,
        E_MESSAGE_TABLE like BAPI_METH_MESSAGE occurs 0 with header line,
        RETURN type BAPIRETURN1,
        lv_index    LIKE bapi_method_project-refnumber.
lv_index = 1.
I_METHOD_PROJECT-OBJECTTYPE = 'ProjectDefinition'.
I_METHOD_PROJECT-METHOD = 'Create'.
I_METHOD_PROJECT-OBJECTKEY = '0033.3332'.
I_METHOD_PROJECT-REFNUMBER = lv_index.
append I_METHOD_PROJECT.
lv_index = lv_index + 1.
I_METHOD_PROJECT-OBJECTTYPE = 'WBS-Element'.
I_METHOD_PROJECT-METHOD = 'Create'.
I_METHOD_PROJECT-OBJECTKEY = '0033.3332.01'.
I_METHOD_PROJECT-REFNUMBER = lv_index.
append I_METHOD_PROJECT.
lv_index = lv_index + 1.
clear I_METHOD_PROJECT.
I_METHOD_PROJECT-OBJECTTYPE = 'WBS-Element'.
I_METHOD_PROJECT-METHOD = 'Create'.
I_METHOD_PROJECT-OBJECTKEY = '0033.3332.01.R'.
I_METHOD_PROJECT-REFNUMBER = lv_index.
append I_METHOD_PROJECT.
clear I_METHOD_PROJECT.
I_METHOD_PROJECT-OBJECTTYPE = space.
I_METHOD_PROJECT-METHOD = 'Save'.
I_METHOD_PROJECT-OBJECTKEY = space.
I_METHOD_PROJECT-REFNUMBER = space.
append I_METHOD_PROJECT.
I_PROJECT_DEFINITION-PROJECT_DEFINITION = '0033.3332'.
I_PROJECT_DEFINITION-DESCRIPTION = 'Training project'.
I_PROJECT_DEFINITION-PROJECT_PROFILE = 'ZAF0001'.
I_PROJECT_DEFINITION-COMP_CODE = '0033'.
I_PROJECT_DEFINITION-RESPONSIBLE_NO                  = 1.
I_PROJECT_DEFINITION-APPLICANT_NO                    = 1.
I_PROJECT_DEFINITION-PLANT = '033A'.
I_WBS_ELEMENT_TABLE-PROJECT_DEFINITION              = '0033.3332'.
I_WBS_ELEMENT_TABLE-WBS_ELEMENT                     = '0033.3332.01'.
I_WBS_ELEMENT_TABLE-DESCRIPTION                     = 'WBS 1'.
I_WBS_ELEMENT_TABLE-RESPONSIBLE_NO                  = 1.
I_WBS_ELEMENT_TABLE-APPLICANT_NO                    = 1.
I_WBS_ELEMENT_TABLE-COMP_CODE                       = '0033'.
I_WBS_ELEMENT_TABLE-PROFIT_CTR                      = '0033A99999'.
I_WBS_ELEMENT_TABLE-PLANT = '033A'.
append i_wbs_element_table.
clear I_WBS_ELEMENT_TABLE.
I_WBS_ELEMENT_TABLE-PROJECT_DEFINITION              = '0033.3332'.
I_WBS_ELEMENT_TABLE-WBS_ELEMENT                     = '0033.3332.01.R'.
I_WBS_ELEMENT_TABLE-DESCRIPTION                     = 'WBS 2'.
I_WBS_ELEMENT_TABLE-RESPONSIBLE_NO                  = 1.
I_WBS_ELEMENT_TABLE-APPLICANT_NO                    = 1.
I_WBS_ELEMENT_TABLE-COMP_CODE                       = '0033'.
I_WBS_ELEMENT_TABLE-PROFIT_CTR                      = '0033A99999'.
I_WBS_ELEMENT_TABLE-PLANT = '033A'.
append i_wbs_element_table.
PERFORM fill_update_flags USING    'BAPI_PROJECT_DEFINITION_UP'
                          CHANGING I_PROJECT_DEFINITION_UPD.
PERFORM fill_update_flags USING    'BAPI_WBS_ELEMENT_UPDATE'
                          CHANGING I_WBS_ELEMENT_TABLE_UPDATE.
append I_WBS_ELEMENT_TABLE_UPDATE.
append I_WBS_ELEMENT_TABLE_UPDATE.
CALL FUNCTION 'BAPI_PROJECT_MAINTAIN'
EXPORTING
    I_PROJECT_DEFINITION               = I_PROJECT_DEFINITION
    I_PROJECT_DEFINITION_UPD           = I_PROJECT_DEFINITION_UPD
TABLES
    I_METHOD_PROJECT                   = I_METHOD_PROJECT
    I_WBS_ELEMENT_TABLE_UPDATE         = I_WBS_ELEMENT_TABLE_UPDATE[]
    I_WBS_ELEMENT_TABLE                = I_WBS_ELEMENT_TABLE[]
   E_MESSAGE_TABLE                    = E_MESSAGE_TABLE
write: / 'Finish'.
*&      Form FILL_UPDATE_FLAGS
FORM fill_update_flags USING    value(p_ddic_name)
                       CHANGING p_struc_upd.
DATA: lt_dd03l LIKE dd03l OCCURS 0,
        ls_dd03l LIKE dd03l.
DATA: s(40), c(40), sc(80) TYPE c.
FIELD-SYMBOLS: <s>, <c>, <sc> TYPE ANY.
TRANSLATE p_ddic_name TO UPPER CASE.
SELECT * FROM dd03l INTO TABLE lt_dd03l WHERE tabname = p_ddic_name.
s = 'P_STRUC_UPD'.
ASSIGN (s) TO <s>.
LOOP AT lt_dd03l INTO ls_dd03l.
    ASSIGN ls_dd03l-fieldname TO <c>.
    ASSIGN COMPONENT <c> OF STRUCTURE <s> TO <sc>.
    <sc> = 'X'.
ENDLOOP.
ENDFORM.                    " FILL_UPDATE_FLAGS
Please help me!
Thank you!
Edited by: kishan P on Sep 10, 2010 9:37 AM

Hi,
Please try creating the project definition and then call the FM again to create the WBS.
http://help.sap.com/erp2005_ehp_04/helpdata/EN/4c/226a7246e611d189470000e829fbbd/frameset.htm
Hope it helps.
Sujay

Create page definition option on a method call

I have been developing my first application using ADF with JDeveloper 12c. After reading all of the documentation, it would appear that I should be able to create a page definition for a method call on a task flow, but when I right-click on my method calls, there is no option to do so. What am I doing wrong? Any help would be greatly appreciated. Maybe I have a setting wrong or something. Thank you all in advance.

Hi Frank,
Thanks for the response. I did try to right click on the method call, the option to Create Page Definition is absent from the context menu. That was my source of the problem which prompted me to write the thread. However, your alternate solution of dropping the operation from the data control panel onto the method call worked like a charm. It created the page def and bound the method to the call. Thank you for that one. I am still curious as to why the option on the context menu is missing for me.

Filtering Lookup Definition entries while displaying

Hi Experts,
I have a Lookup definition which has 100+ entries. While displaying it to users in an object form , I would like not to display some of the entries (very minimal entries).
Does OIM provides any kind of filtering options? Can you suggest me how to implement this?
Thanks & Regards
Inbaa

Here is a previous post that explains how to use the custom lookup:
Re: Form Field Validation.
-Kevin

Create CAPI definition problem with Headstart 6i / Designer 6i rel. 4.3

During migration from hsd50/des60 to hsd65/des6i rel 4.3 of an application using CDM ruleframe: according to the migration guide, one step is "Upgrading Existing CDM RuleFrame objects", which includes running the Create CAPI definition (Headstart utility). After that step we assume de created CAPI's should be generated together with the Table API. But executing the CAPI-scripts results in errormessages. After comparing the 60 and 6i versions, we found a bug, probably caused by the Headstart utility: In the package body, after the header of the first function of the Business Rule Check Functions, suddenly the declaration section of the package is again inserted, and after that the first function is again defined followed by the rest, causing also a missing end statement at the end of the package.
Is this known, and if so, is there a fix available?
Regards, Paul.

Paul,
We have found the cause for your other problem (the repeating of the declaration section).
With 6.5 a new package property Private Declaration was introduced in Designer.
This property should officially be used instead of PL/SQL block to specify package body declaration
(assuming you define all package procedures and functions in separate PL/SQL Definitions).
However, at first the migration from an earlier version of Designer did not pose any problems
because of Designer bug 1470283. That's why you won't find anything about this in the Headstart Migration Guide.
Now that Designer bug is fixed, migrating a CAPI causes part of the PL/SQL Block to be moved to the Private Declaration.
If you then generate the CAPI package to the database, it works fine, but when you run the CAPI utility again,
it inserts the package declarations again in the PL/SQL Block (leaving the Private Declaration in tact).
That's when you get duplicate package declarations. We logged this as Headstart bug 2527128.
You already found a workaround: deleting the CAPI and generating it again. Another workaround is
moving the Private Declaration to the top of the PL/SQL Block (this allows you to keep your existing
Revision History).
Hope this helps,
Sandra

How to see structure under schema when Create External Definition

Hi ...we have scenario like RFC<>XI<>SOAP
The request payload(SOAPIN) for SOAP is:
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
    <AddressValidator xmlns="http://tempuri.org/geostan3/AddressValidator">
      <LicenseFile>string</LicenseFile>
       <Z9Path>string</Z9Path>
      <House>string</House>
      <Street>string</Street>
        </soap:Body>
</soap:Envelope>
and we are expecting response message from SOAP:
diffgr:diffgram xmlns:msdata="urn:schemas-microsoft-com:xml-msdata" xmlns:diffgr="urn:schemas-microsoft-com:xml-diffgram-v1">
- <AddressCheck xmlns="">
- <Address diffgr:id="Address1" msdata:rowOrder="0" diffgr:hasChanges="inserted">
<Addline1>220 W MAIN ST</Addline1>
<Addline2 />
<URB />
<Lastline>LOUISVILLE, KY 40202-1395</Lastline>
<Location>-85754010, 38256144</Location>
<OutBlock>211110049001067</OutBlock>
<OutCBSA>31140</OutCBSA>
<MatchCode>SE0</MatchCode>
<LocationCode>AS0</LocationCode>
<DPVConfirm />
<FootNote1 />
<FootNote2 />
<FootNote3 />
<Msg>OK</Msg>
</Address>
</AddressCheck>
so when we created external definition using wsdl file into XI, it showing only schema as SOAPOUT (I couldn't see those fields in XI/under schema).
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
    <AddressValidatorResponse xmlns="http://tempuri.org/geostan3/AddressValidator">
      <AddressValidatorResult>
        <xsd:schema>schema</xsd:schema>xml</AddressValidatorResult>
    </AddressValidatorResponse>
</soap:Body>
</soap:Envelope>
SXMB_MONI showing(Response):
<?xml version="1.0" encoding="UTF-8" ?>
- <ns0:AddressValidatorResponse xmlns:ns0="http://tempuri.org/geostan3/AddressValidator">
- <ns0:AddressValidatorResult>
<ns1:schema xmlns:ns1="http://www.w3.org/2001/XMLSchema" />
</ns0:AddressValidatorResult>
</ns0:AddressValidatorResponse>
So my question is how do I map response fields to RFC response? Auctully this schema is like table structure which is having all response fields.
I could see all response structure with data in sxmb_moni-->Response Msg ID > inbound message>payloads(main document). Is there any way to send this response to RFC ?
or can you suggest me any other way to send this response to RFC.
Thanks,
Edited by: PILearn on Jun 2, 2008 10:21 PM

Here you go..
<?xml version="1.0" encoding="utf-8"?>
<wsdl:definitions xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:tns="http://tempuri.org/geostan3/AddressValidator" xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" targetNamespace="http://tempuri.org/geostan3/AddressValidator" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
<wsdl:types>
    <s:schema elementFormDefault="qualified" targetNamespace="http://tempuri.org/geostan3/AddressValidator">
      <s:import namespace="http://www.w3.org/2001/XMLSchema" />
      <s:element name="AddressValidator">
        <s:complexType>
          <s:sequence>
            <s:element minOccurs="0" maxOccurs="1" name="LicenseFile" type="s:string" />
            <s:element minOccurs="0" maxOccurs="1" name="LicensePassword" type="s:string" />
            <s:element minOccurs="0" maxOccurs="1" name="SearchPath" type="s:string" />
            <s:element minOccurs="0" maxOccurs="1" name="Z9Path" type="s:string" />
            <s:element minOccurs="0" maxOccurs="1" name="House" type="s:string" />
            <s:element minOccurs="0" maxOccurs="1" name="Street" type="s:string" />
            <s:element minOccurs="0" maxOccurs="1" name="AddLine2" type="s:string" />
            <s:element minOccurs="0" maxOccurs="1" name="AddLastLine" type="s:string" />
            <s:element minOccurs="0" maxOccurs="1" name="URB" type="s:string" />
            <s:element minOccurs="0" maxOccurs="1" name="Matchmode" type="s:string" />
            <s:element minOccurs="0" maxOccurs="1" name="Datum" type="s:string" />
          </s:sequence>
        </s:complexType>
      </s:element>
      <s:element name="AddressValidatorResponse">
        <s:complexType>
          <s:sequence>
            <s:element minOccurs="0" maxOccurs="1" name="AddressValidatorResult">
              <s:complexType>
                <s:sequence>
                  <s:element ref="s:schema" />
                  <s:any />
                </s:sequence>
              </s:complexType>
            </s:element>
          </s:sequence>
        </s:complexType>
      </s:element>
      <s:element name="DataSet" nillable="true">
        <s:complexType>
          <s:sequence>
            <s:element ref="s:schema" />
            <s:any />
          </s:sequence>
        </s:complexType>
      </s:element>
    </s:schema>
</wsdl:types>
<wsdl:message name="AddressValidatorSoapIn">
    <wsdl:part name="parameters" element="tns:AddressValidator" />
</wsdl:message>
<wsdl:message name="AddressValidatorSoapOut">
    <wsdl:part name="parameters" element="tns:AddressValidatorResponse" />
</wsdl:message>
<wsdl:message name="AddressValidatorHttpGetIn">
    <wsdl:part name="LicenseFile" type="s:string" />
    <wsdl:part name="LicensePassword" type="s:string" />
    <wsdl:part name="SearchPath" type="s:string" />
    <wsdl:part name="Z9Path" type="s:string" />
    <wsdl:part name="House" type="s:string" />
    <wsdl:part name="Street" type="s:string" />
    <wsdl:part name="AddLine2" type="s:string" />
    <wsdl:part name="AddLastLine" type="s:string" />
    <wsdl:part name="URB" type="s:string" />
    <wsdl:part name="Matchmode" type="s:string" />
    <wsdl:part name="Datum" type="s:string" />
</wsdl:message>
<wsdl:message name="AddressValidatorHttpGetOut">
    <wsdl:part name="Body" element="tns:DataSet" />
</wsdl:message>
<wsdl:message name="AddressValidatorHttpPostIn">
    <wsdl:part name="LicenseFile" type="s:string" />
    <wsdl:part name="LicensePassword" type="s:string" />
    <wsdl:part name="SearchPath" type="s:string" />
    <wsdl:part name="Z9Path" type="s:string" />
    <wsdl:part name="House" type="s:string" />
    <wsdl:part name="Street" type="s:string" />
    <wsdl:part name="AddLine2" type="s:string" />
    <wsdl:part name="AddLastLine" type="s:string" />
    <wsdl:part name="URB" type="s:string" />
    <wsdl:part name="Matchmode" type="s:string" />
    <wsdl:part name="Datum" type="s:string" />
</wsdl:message>
<wsdl:message name="AddressValidatorHttpPostOut">
    <wsdl:part name="Body" element="tns:DataSet" />
</wsdl:message>
<wsdl:portType name="AddressCheckSoap">
    <wsdl:operation name="AddressValidator">
      <wsdl:input message="tns:AddressValidatorSoapIn" />
      <wsdl:output message="tns:AddressValidatorSoapOut" />
    </wsdl:operation>
</wsdl:portType>
<wsdl:portType name="AddressCheckHttpGet">
    <wsdl:operation name="AddressValidator">
      <wsdl:input message="tns:AddressValidatorHttpGetIn" />
      <wsdl:output message="tns:AddressValidatorHttpGetOut" />
    </wsdl:operation>
</wsdl:portType>
<wsdl:portType name="AddressCheckHttpPost">
    <wsdl:operation name="AddressValidator">
      <wsdl:input message="tns:AddressValidatorHttpPostIn" />
      <wsdl:output message="tns:AddressValidatorHttpPostOut" />
    </wsdl:operation>
</wsdl:portType>
<wsdl:binding name="AddressCheckSoap" type="tns:AddressCheckSoap">
    <soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document" />
    <wsdl:operation name="AddressValidator">
      <soap:operation soapAction="http://tempuri.org/geostan3/AddressValidator/AddressValidator" style="document" />
      <wsdl:input>
        <soap:body use="literal" />
      </wsdl:input>
      <wsdl:output>
        <soap:body use="literal" />
      </wsdl:output>
    </wsdl:operation>
</wsdl:binding>
<wsdl:binding name="AddressCheckHttpGet" type="tns:AddressCheckHttpGet">
    <http:binding verb="GET" />
    <wsdl:operation name="AddressValidator">
      <http:operation location="/AddressValidator" />
      <wsdl:input>
        <http:urlEncoded />
      </wsdl:input>
      <wsdl:output>
        <mime:mimeXml part="Body" />
      </wsdl:output>
    </wsdl:operation>
</wsdl:binding>
<wsdl:binding name="AddressCheckHttpPost" type="tns:AddressCheckHttpPost">
    <http:binding verb="POST" />
    <wsdl:operation name="AddressValidator">
      <http:operation location="/AddressValidator" />
      <wsdl:input>
        <mime:content type="application/x-www-form-urlencoded" />
      </wsdl:input>
      <wsdl:output>
        <mime:mimeXml part="Body" />
      </wsdl:output>
    </wsdl:operation>
</wsdl:binding>
<wsdl:service name="AddressCheck">
    <wsdl:port name="AddressCheckSoap" binding="tns:AddressCheckSoap">
      <soap:address location="http://sap-ccs-geo02/geostan3/AddressValidator.asmx" />
    </wsdl:port>
    <wsdl:port name="AddressCheckHttpGet" binding="tns:AddressCheckHttpGet">
      <http:address location="http://sap-ccs-geo02/geostan3/AddressValidator.asmx" />
    </wsdl:port>
    <wsdl:port name="AddressCheckHttpPost" binding="tns:AddressCheckHttpPost">
      <http:address location="http://sap-ccs-geo02/geostan3/AddressValidator.asmx" />
    </wsdl:port>
</wsdl:service>
</wsdl:definitions>

Tool to create XML definition, a tool for creating XSD

I need a tool to create XML definition, a tool for creating XSD.
I was trying to do this with Oracle packages. But again there are some problems. Could you tell me which one, I should use?
Can I do it with the Oracle SQL Developer?

Hello,
i get the error message and I don't know, what I can do
The user have the permissions to use DBMS_LOB package.
Is it the sofware, do I need a license version tool for XML generation
SQL> select DBMS_XMLSCHEMA.GENERATESCHEMA( 'HR', 'EMP_DATA' )
2 from dual;
select DBMS_XMLSCHEMA.GENERATESCHEMA( 'HR', 'EMP_DATA' )
ERROR at line 1:
ORA-00904: "DBMS_XMLSCHEMA"."GENERATESCHEMA": invalid identifier

Can't create path definition point?

I'm doing a vector world map drawing and I keep running into this problem. All I am turning to do is connect two end points and I keep getting this window reading "Can't create path definition point, can't add anchor point." I'm exhausted but I'm I missing something simple here? All help is much appreicated!

Dogherty,
If you just want to close a path, you may select it normally and Ctrl/Cmd+J to join the hitherto endpoints.
If you have two different paths, you may select the end points (by clicking on them with the Direct Selection Tool, also to avoid selecting possible ghost points) andCtrl/Cmd+J to join the paths.

Creating template definitions

Hi,
I'm new to WebLogic Process Integrator and I just want to know
if it's possible for me to create a template definition without
using the Studio. Instead, I would like to create a separate
client application whose function is similar to it. I've read in
the API that this is possible thru the methods in
com.bea.wlpi.server.admin.Admin, one of which is public
java.lang.String createTemplateDefinition ( java.lang.String
templateId, java.lang.String name, java.lang.String xml).
However, I can't find any resource or documentation as to where
the xml document that defines the template definition should be placed/located. Also,
are there any additional configurations that I need to do?
Any help on this would be greatly appreciated.
Thanks!

Chris,
Creating the template definition is a two step process. After creating the
definition with the API you mentioned below, use the
setTemplateDefinitionContent method of the Admin bean to set the XML content
of the definition.
Mike
"Chris Co" <[email protected]> wrote in message
news:3cc4d168$[email protected]..
>
Hi,
I'm new to WebLogic Process Integrator and I just want to know
if it's possible for me to create a template definition without
using the Studio. Instead, I would like to create a separate
client application whose function is similar to it. I've read in
the API that this is possible thru the methods in
com.bea.wlpi.server.admin.Admin, one of which is public
java.lang.String createTemplateDefinition ( java.lang.String
templateId, java.lang.String name, java.lang.String xml).
However, I can't find any resource or documentation as to where
the xml document that defines the template definition should beplaced/located. Also,
are there any additional configurations that I need to do?
Any help on this would be greatly appreciated.
Thanks!

Creating lookup definition

Similar Messages

Maybe you are looking for