Attribute Length Set Incorrectly for Operation and Load Arguments

Problem: Due to JDBC driver metadata retrieval related API limitations, SAP Mobile WorkSpace does not always set the correct attribute length, especially for operation arguments and load arguments. For STRING and BINARY types, if the lengths are unknown, SAP Mobile WorkSpace sets them to STRING(300) and BINARY(32767) by default, and gives a warning to adjust the length to avoid wasting device database space, and/or getting runtime data truncation.

Solution: Examine the EIS database metadata and adjust the attribute length, the types and lengths of operation arguments, and the load arguments in SAP Mobile WorkSpace to avoid run-time errors.

Related concepts
AutoCommit Option for JDBC MBOs Using an ASE Data Source
Passing an Empty String or Byte into a Required Binary Column in ASE
Related tasks
Binding an MBO to a Database Fails
Multilevel Insert Operation Fails
Unable to properly update the CDB because the partition was improperly assigned
Related reference
MBO Retrieves Incorrect Data
Relationship Error
Warning Message When Creating Relationships
Troubleshooting Default Values for Adaptive Server Anywhere uniqueidentifiers
Preview Errors for a Web Service Mobile Business Object with date/time Types
Web Service Mobile Business Object Must Be Connected to Connection Profile
Refresh Fails Due to Missing Load Argument Default Values
Input Parameters Fail to Generate for Complex Data Sources
Output Mapping Warning Message for Multilevel Insert Operations
Syntax Errors When Creating a Database Mobile Business Object
SAP MBOs That Invalidate the Cache