Siebel Order Management Guide > Product Data Service and Import Export API Reference >

ISS Authoring Import Export Business Service Reference

The main purpose of this business service is to let you move versioned object definitions (VODs) between databases. It supports the following VODs:

• ISS_ATTR_DEF - Product attribute Definition. Uses the Integration Object ISS Attr Def ImpExp.
• ISS_CLASS_DEF - Product Class Definition. Uses the Integration Object ISS Class Def ImpExp.
• ISS_PROD_DEF - Product Definition. Uses the Integration Object ISS Prod Def ImpExp.
• ISS_SIGNAL - Signal Definition. Uses the Integration Object ISS Signal ImpExp IntObj.
• ISS_VAR_MAP - Variable Map Definition. Uses the Integration Object ISS Variable ImpExp IntObj.

In addition, this business service allows you to fix S_PROD_INT records created with the EIM process so they are usable by the ISS framework. In the case of versioned objects, it creates the minimum set of necessary records that is needed.

NOTE:  You can import simple products using EIM and run a process to generate a default workspace. However, you cannot use EIM to import customizable objects, which you must import using ISS Authoring Import Export Service.

Modeling Data Before Using ISS Import Export Authoring Service

To be able to use the standard approach successfully, users must take some precautions during modeling. VODs manually created on two databases are be treated as different objects even if their VOD Names match.

CAUTION:  Therefore, you must never create 2 master copies of the same VOD manually on two different DBs. Instead move existing definitions from one DB to another through Import/Export, or ADM.

After import, you can freely modify replicated objects in any database and move them around.

Observe the following guidelines to make objects compatible when multiple development environments are required:

• Use only one development database to create new VODs.
• If a customer is upgrading from release earlier than Siebel CRM version 7.8:
  • Do not use upgraded development databases. Instead of using those databases, create a new one from single production master.
  • If you cannot possibly avoid using upgraded development databases, then do not use the VODs that were created during the upgrade of the development databases. Discard those definitions, and change the names of all VODs and products to show clearly that they have been discarded. Then, import necessary definitions from your production database.
• Use ADM or the Export/Import process to populate other development databases with existing VOD definitions.
• If you must create a new VOD in some database other than the master development database, then first check the master database to see if such object already exists, and move the existing object to your development database. If it does not exist, then create it in your development database and immediately move it to the master development database, so other modelers do not create a duplicate.

Methods of the ISS Import Export Authoring Service

This business service includes the following methods:

• Data Export Methods:
  • ExportVOD Method
  • ExportFullVOD Method
• Data Import Method:
  • ImportVOD Method
• Application Deployment Manager (ADM) specific Methods:
  • ADMValidate Method
  • ADMPreview Method
  • ADMExport Method
  • ADMImport Method
• Helper Methods:
  • ReleaseSingleObject Method
  • ReleaseJwsObjects Method
  • Post_EIM_Upgrade Method
  • CleanupSingleObject Method