Conventions for Hierarchy Paths

The following convention is used for hierarchy paths in a number of service methods:

Hierarchy paths are inputs of the form IC1.IC2.IC3…, where IC1, IC2, IC3, and so on, are Integration Component Names that tell the method how to traverse the object definition to find the correct place to put the child. For example, when placing a business address under the account under the opportunity object, the path would read Opportunity.Account.

For the Set Child Type method, a slightly different methodology in the hierarchy path is used, as follows:

For Set Child Type, refer to IC1, IC2, IC3, and so on as the actual structure of the Siebel hierarchy. The examples listed come from the ANI Shopping Cart Message (PRM ANI) Integration object.

The first three substrings appear as follows: ChildObject.ListOfMessageType.RootComponentName. An example is:

SiebelMessage.ListOfANI Shopping Cart Message (PRM ANI).Message Details 

The following substrings alternate between ListOf Component Names and the Component Names themselves. An example is:

ListOfChannel Partner.Channel Partner.ListOfChannel Partner Business 
Address.Channel Partner Business Address