Behavior about asset_version and sec_asset_version colomons of multi table at ATG PUB DB level.

Behavior about asset_version and sec_asset_version  colomons of multi table at PUB DB level.

Example table is dcs_cat_chldprd
The following are behavior of this columns.
1) When category is only updated, then asset_version value is increased (mapping to dcs_category).
2)When product is only updated, then sec_asset_version value is increased (mapping to dcs_product).
3)If both are changed in a single project, the following behavior occurs.
  a)First the latest version(increased version) of asset_version holds the last version of sec_asset_version (product).Even if we remove by backed system(DB), it won't cause any issue at BCC level.
  b)And also the next/updated  version of sec_asset_version  is mapped with latest version asset_version
4)The seq_number won't be updated along with asset_version   and sec_asset_version.
5)The seq_number is changed only when the order of the products changed at category level.
6)If seq_number order is changed/corrupted(0,1,3,4,...) instead of proper order (0,1,2,3...), BCC won't allow to change that particular category.

All the above steps are verified practically.