Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM-LOC-BR (Application Component) Brazil⤷
J1BA (Package) Localization Brazil
Basic Data
| Data Element | J_1BNFEAUTHCODE |
| Short Description | Protocol Number |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | J_1BNFEAUTHCODE | |
| Data Type | CHAR | Character String |
| Length | 15 | |
| Decimal Places | 0 | |
| Output Length | 15 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Prot. No. |
| Medium | 15 | Protocol No. |
| Long | 20 | Protocol Number |
| Heading | 35 | Protocol Number |
Documentation
Definition
Shows the code that the tax authorities issue with each response message about an electronic fiscal document.
Use
On the output screen of the Monitor, the system displays the initial protocol number that was issued in the Document Overview section. In the Document History section, the system lists the protocol numbers that are received with the follow-on messages.
For outgoing documents, the protocol number that comes with the authorization is printed on the DANFE or DACTE. To check the validity of the printed version before accepting goods, recipients must compare the protocol number printed on the paper with the protocol number on the tax authorities# server.
When you post an incoming electronic fiscal document, you enter the protocol number manually in the NF Writer on the Electronic Doc. Data tab page.
Dependencies
Examples
History
| Last changed by/on | SAP | 20130529 |
| SAP Release Created in | 604 |
