Hierarchy
SAP_FIN (Software Component) SAP_FIN⤷
FI-LOC (Application Component) Localization⤷
ID-CIAP-BR (Package) CIAP solution for Brasil
Basic Data
| Data Element | J_1BSERNO |
| Short Description | CIAP Document Number |
Data Type
| Category of Dictionary Type | Direct Type Entry | |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | ||
| Data Type | NUMC | Character string with only digits |
| Length | 4 | |
| Decimal Places | 0 | |
| Output Length | 4 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | J_1BSERNO | |
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | CIAP DocNo |
| Medium | 15 | CIAP Doc. No. |
| Long | 20 | CIAP Document Number |
| Heading | 20 | CIAP Document Number |
Documentation
Definition
A sequential number assigned by the system each time a CIAP document is generated from a CIAP-relevant transaction.
Use
Dependencies
Example
Assume that for the same fiscal year, nota fiscal (NF), NF item, and tax type, three transactions are performed that are relevant to CIAP reporting. Each transaction generates a CIAP document, and the system assigns them the CIAP document number 1, 2, and 3 - in the order they are generated.
It is also possible that a single CIAP-relevant transaction generates several CIAP documents - for instance, if an internal order (associated with a single NF) is settled to three assets, then three CIAP documents are generated. If this transaction occurs after the example above, they would be assigned the CIAP document number 4, 5, and 6, respectively.
History
| Last changed by/on | SAP | 20050411 |
| SAP Release Created in | 600 |
