Mapping Validation Rules

Make sure that, you map the key parameters from your data source to each operation in the Data Model. Failure to do so will result in warnings.

Later, you must define the Property (key parameter) as key.

• The cardinality of the target Data Object must be the same as that of the source Data Object.

• You cannot merge fields from two different source Data Objects with cardinality 0..n into the same target Data Object.

• Property names must be unique in a node, and the node names must be unique in a model.

  The generator renames additional fields with similar name and type as a Property that has already been defined as key.

• The generator will not propose to assign the key to a Property with a name that is different from the parameter set as key in the data source.

  In addition, it will not assign an a key to an import parameter for Query, or an export parameter for Read, Update, and Delete.

• There is no duplicate mapping for objects of type export.

• Merging of data sources with cardinality 0..n is not possible. Parameters of a table in a data source can be mapped only to a Property in the specific related node with cardinality 0..n

• You can have more than one data source entity of type import mapped to the same Data Model attribute. Also, you can have a single data source entity of type export mapped to the Data Model.

• You can only map import and export parameters to the Properties in the root Data Object.

  Usually, import fields are used for filtering or as constants.

• You must map all root Data Object Properties to the output structure of the Query.

• You must map one output parameter.

• If you are selecting a table, you can only select one table at a time.

• The generator tool checks that, each Data Model has a single data source entity mapped to it, with a maximum of one input and one output mapping.

• If RFC or BOR is your data source, you must select one table.

  Note

  You can select more than one ranges table.

• You must map at least one input parameter.

• You can either map importing single attributes to Data Model Properties or you can assign constant values to them.

• You can either 'flatten out' fields of importing structures and map them to Data Model root Properties (they cannot be mapped to nested Data Objects in the Data Model) or you can assign constant values to them.

• You cannot map tables; you can only assign constant values to the table fields, but then you can only pass one line filled with these constants.

• The mapping proposal in the Delete operation for all the attributes is set as constant, Initial.

• For Read, you must map at least one input and one output parameter.

• For Update and Delete, you must map at least one input parameter.

When you want to create or change a mapping, the generator tool provides suggestions for mapping, referred to as mapping proposals.

The generator tool checks for the following:

• When a Property has already been mapped to an attribute from the data source and it is in the root node of an operation, the same attribute will used as the mapping proposal for each operation and type (import and export), so long as it has a similar name and type.

• When mapping an operation, the tool can detect whether a node or an attribute to be mapped already exists in another operation that has already been mapped.

  If detected, the attribute is automatically renamed by adding an underscore character and a number to the end of the name. The number is added incrementally depending on the number of such instances.

  For example, if the attribute Name is already mapped, it will be rename as, Name_1