Hierarchy
SLL-NFE (Software Component) xNFE⤷
SLL-NFE-MGM (Application Component) NF-e: Communication Management & Monitoring⤷
/XNFE/CUS (Package) Customizing
IMG Activity
| ID | /XNFE/XMLVERSDETMDFE | MDF-e: Maintain Version of Message Types |
| Transaction Code | /XNFE/83000042 | (empty) |
| Created on | 20140603 | |
| Customizing Attributes | /XNFE/XMLVERSDETMDFE | MDF-e: Maintain Version of Message Types |
| Customizing Activity | /XNFE/XMLVERSDETMDFE | MDF-e: Maintain Version of Message Types |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | /XNFE/XMLVERSDETMDFE |
Use
In this Customizing activity, you determine which XML version is used for individual message types when communicating with authorities.
Requirements
In Customizing activity "MDF-e: Maintain Connected Authority Systems" you have defined the authority system you want to communicate with.
Standard settings
Activities
Enter your logical system and your tax number. A blank tax number is also permitted. To achieve this, you can either delete the tax number after selecting the default values, or you can manually enter the logical system. Then select the document type, the message type, and the desired XML version.
To determine the XML version, the system first searches an entry for the respective tax number. If no such entry is found, the system uses the entry with a blank tax number. If no such entry can be determined, the system stops the process and returns the error ("D" - discrepancy; resend from ERP) to the ERP system.
The following document types must be defined for each tax number you use:
MFE for MDF-e
Document type MDF-e
Maintain the XML versions for the following message types:
MDFE: Generic layout
RODOMFE: Mode of transport = road
AEREOMFE: Mode of transport = air
AQUAVMFE: Mode of transport = ship
FERROVMFE: Mode of transport = rail
Document type MDF-e
Sending of MDF-e events (document type EV3) requires an XML version for the generic layout (attribute 'versao' in tag <eventoMDFe>) as well as another version for the event type-dependent layout that was used (attribute 'versaoEvento' in tag <detEvento>).
For example, if you want to use layout 1.00 for sending MDF-e events with type 'cancellation', you need to maintain two entries: one for message type 'EVENTO' and one for message type '110111'.
EVENTO: Issue Event
110111: Cancellation
110112: Close:
110114: Addition of Driver
Example
Business Attributes
| ASAP Roadmap ID | 203 | Establish Master Data |
| Mandatory / Optional | 1 | Mandatory activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | /XNFE/XMLVERSDETMDFE | 0 | /XNFE/KSU2000001 | Nota Fiscal Eletronica (NF-e) |
Maintenance Objects
| Maintenance object type | C | Customizing Object |
| Assigned objects | ||||||
|---|---|---|---|---|---|---|
| Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
| /XNFE/V_XMLVERMF | V - View | SM30 |
History
| Last changed by/on | BECKOL | 20140603 |
| SAP Release Created in | 900 |
