This document aims to clarify the behavior of assets with CIAP in the routine Acquisition by Transfer (ATFA251).
In the routine, you can use assets with a linked CIAP, the behaviors of which follow a certain flow as break-ups or consolidations are performed.
In an asset with CIAP, all assets desired are grouped, the CIAP values selected being grouped in the new asset, generating a new CIAP code. If an asset that has no CIAP is grouped with another that does, it groups the CIAP values in this new asset without problems.
|
When breaking up an asset with CIAP, the assets are broken up in divided form based on the percentage, dividing the CIAP value among the assets to be created and generating new CIAP codes for the assets broken-up.
Example:
In this example, the asset is broken up in 2 (50%), having an ICMS value of 60. For both assets, new CIAP codes are created. If field Generate CIAP is set to No, the broken-up assets keep the same CIAP code, but at least one asset must have the total value of ICMS and Generate CIAP = YES. Undistributed ICMS Message;
Example:
In this case, the asset was broken up in 2 (50%), but only the first had the field Generate CIAP = Yes. The second had it set to No, so it was linked to the same CIAP code with the total value entered in the first line. If one of the assets selected has CIAP and, when breaking up with more assets, none has Generate CIAP? set to Yes on the grid, the HELP AF251REGRA is displayed.
|
