Defining XML Database Schema Translation Properties

You need to define translation properties for each attribute in an XML database schema. The translation properties indicate to the system how data is converted from XML for storage in Eclipse, and how data is converted from Eclipse for transmission using XML.

Each data definition in the database schema requires that you define the following:

The type of data that is stored in Eclipse, such as Text or Numeric.
The type of information that is received or sent in XML, such as String or Integer.

To define XML schema translation properties:

From the System > Custom menu, select XML Schema Maintenance to display the XML Schema Maintenance screen.
In the XML Database Schema field, enter or select the XML database schema for which you want to define properties.

The Eclipse data files and their associated XML information display for each line in the schema. See Creating XML Database Schemas for additional information.

Select the line for which you want to define properties and use the Properties hot key to display the XML Schema Properties screen.
In the attribute and sub-value fields, for example AM and SSVM, the system displays the information as it was defined in the XML Schema Maintenance screen. Update the values as necessary.

As you define the properties for the attribute, update the attribute mark, value mark, and sub-value marks as necessary for the data.

Note: Although you can change the values for attribute marks, value marks, and any sub-value marks, we recommend that you do not do so. These markers change how data is stored.

For additional information about attributes, values, and sub-values, see Eclipse Data and XML Database Schemas.

In the Eclipse Database Data Type field, select one of the following to identify the type of data stored:

Data Type	Description
Text	The Eclipse data stored is a text string, such as the name or address in a customer or contact record. If you are unsure what type of data you are defining, use Text as the default setting. In the Wrap Width field, enter the number of characters that display before wrapping occurs if the data for this field can wrap from one line to the next. In the Delimiter field, enter the character or marker in the data that indicates a new item. Typically, the delimiter for text is a value marker.
Date	The Eclipse data stored is a calendar date. The Domain Object Data Type field defaults to Integer to reflect that the data for a date is a number, such as 06/04/2004.
Numeric	The Eclipse data stored is a number, such as the credit limit or past due days defined for a customer in a customer record, or the unit weight for a product. If you select Numeric as the data type, indicate the number of places after the decimal the system allows in the Decim field. For example, if you are defining properties for unit weight for a product, you might determine that a product can be measured to two decimal places, such as 10.25 lbs.
Y/N Only	The Eclipse data stored is yes or no, such as the flag that indicates whether the entity address should be used for a contact.
* Only	The Eclipse data stored is an asterisk (*), such as, an attribute where more than one value can be set. For example, lists where you can indicate more than one option, such as indicating a bill-to/ship-to customer.
Time	The Eclipse data is a time of day, such as a normal delivery time of 8:00 am for a customer or the last updated date for a contact.
Order Qty	The Eclipse data stored is a product quantity on an order, such as total quantity of an item order, or a total ship quantity.

In the Domain Object Data Type field, the system displays the XML data type that is associated with the domain object data type you entered in the Eclipse Data Type field. You can change the value, if necessary.

Select one of the following data types:

Date type	Description
String	The data is text, such as a contact's first name or last name. String is the default setting for the Text Eclipse data type.
Boolean	The data is a yes or no value, such as a flag that indicates whether the entity address should be used for a contact. Boolean is the default setting for the Y/N Eclipse data type.
Integer	The data is a number, such as a date or a quantity. Integer is the default setting for the Date, Numeric, and Time Eclipse data types.
Real	The data is a number value that is counted, such as an order quantity or a dollar amount. Real is the default setting for the Order Qty Eclipse data type.

To nest an XML database schema within an element in the Business Connect XML mapping utility's tree structure, enter the schema in the Pointer to Database Schema field. Use the Multi hot key to insert multiple schemas.

For example, if the bill-to address contains all the same information for an entity address, you might point the BillTo data definition to the Entity schema. When a transaction is defined that uses the schema in the Business Connect XML mapping utility, the nested element in the Pointer to Database Schema field displays as a child element.

If the data definition can have multiple values, continue with the procedure below. If it does not allow multiple values, press Esc to save the property settings and return to the XML Schema Maintenance screen.

To define multiple value settings for an XML schema translation:

Complete the procedure above.
In the Can this position have Multiple Values field, enter Yes.
In the XML Table Name field, enter the Eclipse database table where they system stores the XML data.

For example, if you are defining properties for a contact's credit cards, your Contact XML database schema might contain two pieces of data: Credit Card Types and Credit Card Numbers. A contact can use more than one credit card to pay for orders, so the attributes contain more than one credit card type and credit card number. These values can be stored in a table called Credit Card Information with values and sub-values.

In the Will this Table Always contain a value field, enter Yes to indicate that the XML table you indicated in the previous field requires a value. If the table does not always need to contain a value, enter No.
Press Esc to save your changes and return to the XML Schema Maintenance screen.