Purpose If you followed the directions of the Admin Console documentation, youknow how to define Replication Rules for a BDoc type. There willprobably be some data inconsistency in your defined Replication Rules.For example, the BDoc type was changed/deleted and references to theBDoc type are lost in the Replication Rules. Data inconsistency in theReplication Rules may result in failures during the generation or in ashort-dump during program execution. You can check the Replication Rules for all defined BDoc types on theserver side to avoid such errors. Integration The consistency check is carried out in a hierarchically structuredform. The consistency check starts from the Replication Rulesdefinition for a BDoc type, then goes on to its segments and fieldreferences and finally to the internal links (e.g. check thedependencies of defined Replication Rules between different BDoctypes). Features Selection You can enter one BDoc type or a set of BDoc types to be checked, byspecifying their names or their IDs. You can also set display options. Output The results of the check are displayed in an application log. At the first level of the hierarchical structure you can see themessage type of the result. At the second level of the hierarchicalstructure, you can see detailed information for a selected Bdoc type. BITMAP SMOH_RR_CHECK_OUTPUT OBJECT GRAPHICS ID BMAP TYPE BCOL |