The BDoc Modeler allows you to perform a consistency check on a BDoc type. You use this procedure to ensure that the BDoc type you modeled does not contain any errors before it is activated. A consistency check can be performed on Active or Inactive BDoc types. After you perform the consistency check, if the BDoc type does not contain any errors, you can activate the BDoc type. However, if there are errors in the BDoc type, you need to rectify the errors before you activate the BDoc type.

A consistency check is performed on the BDoc header, segments, maps, fields, and WHERE clauses. In addition, the check is performed on the dependent services such as Replication and Realignment.

When you perform the consistency check on a BDoc type, it checks for the following information:

• The number of versions of the BDoc type and their status.

• Whether joins have been removed for any of the joined tables.

• Whether the BDoc parameter has the same data domain as the table field.

• If no segment field exists, a check is done on the pending database field entries.

• Whether the child segment has at least one parent key.

• Whether primary key, update tables and R/3 structure name is defined for a segment.

• Whether illegal characters for BDoc type, parameter and segment names have been used.

• Whether mBDoc types are mapped only to sBDoc types.

• Whether Site Types are mapped only to synchronization or messaging BDoc types and not to Mobile Application (read only or modifiable read) BDoc types.

• Whether the parent-child relationship for a segment is valid.

• Whether the segment SMOMEMO is a root segment. It also checks whether mBDoc types have a segment with the name SMOMEMO.

• Whether the segments of synchronization and Mobile Application modifiable read BDoc types have only one updateable map.

• Whether the primary key or parent key of a segment of a BDoc type is mapped to the key field of the update table.

• Whether any primary key is defined for a segment of a BDoc type.

• Whether the segments of a BDoc type have only one primary key.

• Whether parent key is defined for all the child segments of a BDoc type.

• Whether all the child segments of a BDoc type have only one parent key.

• Whether the segment field defined as a parent key or primary key is a GUID.

• Whether the parameters used in the WHERE Clause exist.

• If the same table is mapped to root segments of more than one BDoc type, it checks whether the where clause for this segment is static.

• Whether the segment name to, which the table SMO_MEMO is mapped, is SMOMEMO.

• Whether the mapped table has two key fields. It also checks the data types of the two key fields. The data type of the first key field must be CLNT and the data type of the second key field must be CHAR32 or RAW16.