SAP's RFC_READ_TABLE function limits data retrieval to 512 bytes
per row of data. Many SAP tables have more than 512 bytes of data
per row. However, most business objects represent a small subset of
all the database fields. Therefore, the total length of all
attributes in a business object rarely exceeds the 512 byte
maximum.
In those cases that require the connector to retrieve more than
512 bytes of data from a single database table, the additional
fields must be represented in separate single-cardinality child
business objects. For example, if a business object must represent
1500 bytes of data from a single table, the top-level business
object contains at least two single-cardinality child business
objects. Neither the parent nor either child has attributes whose
total length (that is, the sum of their maximum length) exceeds 512
bytes.
- Note:
- If a business object represents more than one database table,
the total length of the values in the attributes that represent
each table cannot exceed 512 bytes. However, this limit does not
pertain to the total length of the values of all attributes. For
example, if a business object represents data from the tables that
store information about Customers and CustomerPartners, the value
of those attributes representing Customers cannot exceed 512 bytes,
and the value of those attributes representing CustomerPartners
cannot exceed 512 bytes, but the combined value of these attributes
can exceed 512 bytes.
- Important:
- When you use Advanced Outbound Wizard to create business object
definitions, and it encounters an object that represents more than
512 bytes of data from a single table, it stops adding attributes
to the child business object when the length exceeds 512 bytes. If
your business processing requires a business object to represent
more than 512 bytes of data from a single table, you must manually
create the additional child business objects.
