You can map results returned from a remote operation into an MBO,
including mapping multiple results to the MBOs of a composite graph, for example, when
configuring Entity Read Operations.
The Output screen includes an output mapping figure that illustrates the
mappings and allows you to modify them in these ways:
- When an MBO developer maps an MBO to an XSLT, output table, or
result set, a line connects the two objects, and the attributes of the MBO are
mapped to the corresponding columns automatically according to
column-to-attribute matching.
- You can also change the mapping between individual attributes and
columns.
- If you remove the mapping between an MBO and the output, all the
individual attribute and column mappings between the MBO and the output are
removed.
Additional guidelines include:
- For SAP and Web services, SAP Mobile WorkSpace
retrieves the output metadata (columns of the operation result) without
executing an operation, but for JDBC the operation is executed to retrieve the
metadata.
- Each mapped result set must be a one-to-one mapping to the MBOs
in the composite graph (relationship). This is also true for Entity Read
operations, the difference is that Entity Read's output mapping must cover all
nodes in the composite graph. An error displays if you map columns from one
result set into attributes of different MBOs, or if you map columns from
different result sets into attributes of the same MBO.
- The Entity Read operation supports only a one-to-one mapping
between an output column and MBO attribute.
- The datatype and nullability of an attribute must match that of
the column to which it maps.