Preparing to Import the Enterprise Objects to Siebel Tools

Before importing EBMs to Siebel Tools, you must first edit a number of enterprise objects so that they conform to Siebel CRM requirements. In particular, the following differences exist between Siebel CRM and Oracle AIA objects:

  • The document tag used by Oracle AIA objects exceeds the limit of 255 characters for comments in Siebel CRM.

  • Weakly typed schema (##any, ##other) are not supported in Siebel CRM.

To prepare to import the enterprise objects into Siebel Tools, perform the steps in the following procedure.

To prepare to import the enterprise objects into Siebel Tools

  1. Using an XML editor, navigate in turn to each of the files listed in the File column of the following table.

  2. Edit each file as indicated in the Changes Required column of the following table.

File Changes Required

\EnterpriseObjectLibrary\Industry\BankingAndWealthManagement\EBO\Enity\V1\EnityEBM.xsd

Entity is the specific Enterprise Object Library object, for example, Loan Account.

None

\EnterpriseObjectLibrary\Industry\BankingAndWealthManagement\EBO\Enity\V1\EnityEBO.xsd

Entity is the specific Enterprise Object Library object, for example, Loan Account.

Put <xsd:documentation> tag text in a comment.

\EnterpriseObjectLibrary\Industry\BankingAndWealthManagement\Common\V2\Meta.xsd

None

\EnterpriseObjectLibrary\Industry\BankingAndWealthManagement\Common\V2\CommonComponents.xsd

Put <xsd:documentation> tag text in a comment.

\EnterpriseObjectLibrary\Industry\BankingAndWealthManagement\Common\V2\CodeLists.xsd

None

\EnterpriseObjectLibrary\Industry\BankingAndWealthManagement\Common\V2\DataTypes.xsd

None

\EnterpriseObjectLibrary\Industry\BankingAndWealthManagement\Custom\Common\V2\CustomCommonComponents.xsd

None

\EnterpriseObjectLibrary\Industry\BankingAndWealthManagement\Custom\EBO\LoanAccount\V1\CustomLoanAccountEBO.xsd

None

\EnterpriseObjectLibrary\Industry\BankingAndWealthManagement\Common\V2\WS-Addressing.xsd

None

\EnterpriseObjectLibrary\Industry\BankingAndWealthManagement\Common\V2\access_control-xacml-2.0-context-schema-cd-04.xsd

None

\EnterpriseObjectLibrary\Industry\BankingAndWealthManagement\Common\V2\access_control-xacml-2.0-policy-schema-cd-04.xsd

None

\EnterpriseObjectLibrary\Infrastructure\V1\Meta.xsd

  • Put <xsd:documentation> tag text in a comment.

  • Put the import of the following file in a comment:

<xsd:import namespace="http://schemas.xmlsoap.org/ws/2003/03/addressing" schemaLocation="WS-Addressing.xsd"/>

This file refers to the http://schemas.xmlsoap.org/ws/2003/03/addressing file which contains ##other namespaces.

\EnterpriseObjectLibrary\Infrastructure\V1\CodeLists.xsd

Put <xsd:documentation> tag text in a comment.

\EnterpriseObjectLibrary\Infrastructure\V1\DataTypes.xsd

Put <xsd:documentation> tag text in a comment.

\EnterpriseObjectLibrary\Infrastructure\Custom\V1 \CustomMeta.xsd

Put <xsd:documentation> tag text in a comment.

\EnterpriseObjectLibrary\Infrastructure\V1\WS-Addressing.xsd

Put elements where namespace is ##other in a comment. These elements are not required because this include file is commented in the Meta.xsd file.

\EnterpriseObjectLibrary\Infrastructure\V1 \access_control-xacml-2.0-context-schema-cd-04.xsd

Put elements where namespace is ##any in a comment.

\EnterpriseObjectLibrary\Infrastructure\V1 \access_control-xacml-2.0-policy-schema-cd-04.xsd

Put elements where namespace is ##any in a comment.