EDM IDE INVOIC
-
Upload
gergo-paksy -
Category
Documents
-
view
52 -
download
5
description
Transcript of EDM IDE INVOIC
INVOIC vs. SAP-INVOIC
1. General ___________________________________________________________ 4
2 INVOIC - Segments _________________________________________________ 6
2.1 UNH – Message Header _______________________________________________ 6
2.2 BGM – Start of Message _______________________________________________ 7
2.3 DTM – Date/Time/Time Frame__________________________________________ 7
2.4 IMD – Product/Service Description ______________________________________ 7
2.5 RFF – Reference Specifications _________________________________________ 8
2.6 DTM – Date/Time/Time Frame__________________________________________ 8
2.7 NAD – Name and Address ______________________________________________ 8
2.8 LOC - Location_______________________________________________________ 9
2.9 FII – Credit Institute _________________________________________________ 10
2.10 RFF – Reference Specifications ________________________________________ 10
2.11 CTA – Contact Partner _______________________________________________ 10
2.12 COM - Communication _______________________________________________ 11
2.13 CUX – Currency Specifications_________________________________________ 11
2.14 PAT – Payment Conditions ____________________________________________ 11
2.15 DTM – Date/Time/Time Frame_________________________________________ 12
2.16 LIN – Item Data _____________________________________________________ 12
2.17 PIA – Additional Product Identification __________________________________ 12
2.18 QTY – Quantity _____________________________________________________ 13
2.19 MOA – Monetary Amount _____________________________________________ 14
2.20 PAT – Payment Conditions ____________________________________________ 14
2.21 DTM – Date/Time/Time Frame_________________________________________ 14
2.22 PRI – Price Specifications _____________________________________________ 15
2.23 RFF – Reference Specifications ________________________________________ 15
2.24 LOC - Location______________________________________________________ 15
2.25 TAX – Tolls, Taxes, and Fees __________________________________________ 16
2.26 MOA – Monetary Amount _____________________________________________ 17
2.27 NAD – Name and Address _____________________________________________ 17
2.28 UNS – Section Control________________________________________________ 18
2.29 MOA – Monetary Amount _____________________________________________ 18
2.30 TAX – Tolls, Taxes, and Fees __________________________________________ 18
2.31 MOA – Monetary Amount _____________________________________________ 19
2.32 UNT – End of Message Segment________________________________________ 19
3 XML und INVOIC _________________________________________________ 19
Copyright ____________________________________________________________ 20
1. General
When processing business processes, it is usually necessary for information to be exchanged between participating utility companies. The German Electricity Association (VDEW) have defined a number of message categories in order to standardize information exchange. These include the following message categories:
Message category Used to transfer
MSCONS Measured values (consumption data)
UTILMD Master data
DELFOR Schedules
REMADV Payment advice notes
APERAK Application errors and confirmation notifications
CONTTRL Syntax and transfer control messages
REQDOC Document requests
INVOIC Billings for grid and energy services
This document describes the INVOIC message category and the corresponding SAP implementation.
The INVOIC message is intended for invoicing grid and energy services. The data used in the bill is, for example, prepared on the basis of measured load profiles that are generally sent as MSCONS and in UN/EDIFACT D 99A. Version 1.4a of INVOIC was released on October 30th 2001.
The figures below describe the individual segments of an INVOIC message and the corresponding SAP structures: An INVOIC message consists of the following segments:
• Start of message (UNH, BGM)
• Message date (DTM)
• Bill category (IMD)
• Message references (REF, DTM)
• Sender and recipient ID (NAD, LOC, FII)
• VAT (REF)
• Contact partner (CTA, COM)
• Currency (CUX)
• Due date (PAT, DTM)
• Product ID (LIN, PIA)
• Quantity specifications (QTY)
• Item amount (MOA)
• Payment conditions (PAT, DTM)
• Price (PRI)
• Customer references (REF)
• Location of meter (LOC)
• Tax specifications and quantities (TAX, MOA, NAD)
• Section control (UNS)
• Bill totals (MOA)
• Tax specifications and quantities (TAX, MOA)
• End of message (UNT)
2 INVOIC - Segments
This section describes the individual INVOIC segments and the corresponding SAP data structures.
2.1 UNH – Message Header
Segment UNH is implemented as segment E1VDEWUNH and is used to open, identify, and specify messages.
UNH E1VDEWUNH
0062 Message reference number REFERENCENUMBER
0065 Message category ID IDENTIFIER
0052 Version number of message category VERSIONNUMBER
0054 Release number of message category RELEASENUMBER
0051 Administrative organization, coded CONTROLAGENCY
0057 Application code of appropriate organization ASSOCCODE
0068 General allocation reference ACCESSREF
0070 Transfer sequence number TRANSFERNUMBER
0073 Indicator for first/last message INDICATOR
2.2 BGM – Start of Message Segment BGM is implemented as segment E1VDEWBGM and is used to display the category and function of a message as well as to transfer the ID number.
BGM E1VDEWBGM
1001 Document/message name, coded NAME
1131 Code list, qualifier CODELIST
3055 Place responsible for code maintenance, coded CODELISTAGENCY
1000 Document/message name FULLNAME
1004 Document/message number DOCUMENTNUMBER
1056 Version VERSION
1060 Revision number REVISION
1225 Message function, coded DOCUMENTFUNC
4343 Response type, coded RESPONSETYPE
2.3 DTM – Date/Time/Time Frame Segment DTM is implemented as segment E1VDEWDTM and is used to specify the document date. The segment also specifies whether the billing period of the bill is valid for one month or one year. If necessary, you can specify the start date and start time of the billing period here.
DTM E1VDEWDTM
2005 Date/time/time frame, qualifier DATUMQUALIFIER
2380 Date/time/time frame DATUM
2379 Date/time/time frame, format qualifier FORMAT
2.4 IMD – Product/Service Description Segment IMD is implemented as segment E1VDEWIMD and is used to describe the bill category.
IMD E1VDEWIMD
7077 Product/service description, type, coded ITEM_DESCR_TYPE
7081 Product characteristic ITEM_CHAR_CODE
1131 Code list, qualifier ITEM_CHAR_CODE_LIST_ID
3055 Place responsible for code maintenance, coded
ITEM_CHAR_AGENCY
7009 Product/service description, identification ITEM_DESCR_ID
1131 Code list, qualifier ITEM_DESCR_CODE_LIST_ID
3055 Place responsible for code maintenance, coded
ITEM_DESCR_AGENCY
7008 Product/service description ITEM_DESCR_DESCRIPTION_1
7008 Product/service description ITEM_DESCR_DESCRIPTION_2
3453 Language, coded ITEM_DESCR_LANGUAGE
7383 Interface/level, coded LAYER
2.5 RFF – Reference Specifications Segment RFF is implemented as segment E1VDEWRFF_1 and is used to specify references that refer to the entire message (for example, the number of a corresponding request (REQDOC) or a previous bill or contract number).
RFF E1VDEWRFF_1
1153 Reference, qualifier REFERENCEQUALIFIER
1154 Reference number REFERENCENUMBER
1156 Line number LINENUMBER
4000 Reference number VERSIONNUMBER
1060 Revision number REVISION
2.6 DTM – Date/Time/Time Frame Segment DTM is implemented as segment E1VDEWDTM_2 and is used to specify dates of previous RFF segments (for example, a request date).
DTM E1VDEWDTM_2
2005 Date/time/time frame, qualifier DATUMQUALIFIER
2380 Date/time/time frame DATUM
2379 Date/time/time frame, format qualifier FORMAT
2.7 NAD – Name and Address Segment NAD is implemented as segment E1VDEWNAD and is used to identify the data exchange partners involved in the process. You must specify both the sender and the recipient. If the bill issuer and the bill recipient are not the sending and receiving companies, you must identify these as well.
NAD E1VDEWNAD
3035 Participant, qualifier ACTION
3039 Identification of participant PARTNER
1131 Code list, qualifier CODELIST
3055 Place responsible for code maintenance, coded CODELISTAGENCY
3124 Line for name and address NAMEADDRESS1
3124 Line for name and address NAMEADDRESS2
3124 Line for name and address NAMEADDRESS3
3124 Line for name and address NAMEADDRESS4
3124 Line for name and address NAMEADDRESS5
3036 Name of participant PARTNERNAME1
3036 Name of participant PARTNERNAME2
3036 Name of participant PARTNERNAME3
3036 Name of participant PARTNERNAME4
3036 Name of participant PARTNERNAME5
3045 Name of participant, format, coded PARTNERFORMAT
3042 Street and house number or PO box STREET1
3042 Street and house number or PO box STREET2
3042 Street and house number or PO box STREET3
3042 Street and house number or PO box STREET4
3164 City CITY
3229 Region, identification REGION
3251 Postal/zip code ZIPCODE
3207 Country, coded COUNTRY
2.8 LOC - Location Segment LOC is implemented as segment E1VDEWLOC_1.
LOC E1VDEWLOC_1
3227 Location, qualifier PLACE_QUALIFIER
3225 Location, identification PLACE_ID
1131 Code list, qualifier CODE_LIST_QUALIFIER_1
3055 Place responsible for code maintenance, coded
CODE_LIST_RESPONSIBLE_AGENCY_1
3224 Location PLACE
3223 Related place/location 1, identification
RELATED_PLACE_COMPANY_1
1131 Code list, qualifier CODE_LIST_QUALIFIER_2
3055 Place responsible for code maintenance, coded
CODE_LIST_RESPONSIBLE_AGENCY_2
3222 Related place/location 1 RELATED_PLACE_AREA_1
3233 Related place/location 2, identification
RELATED_PLACE_COMPANY_2
1131 Code list, qualifier CODE_LIST_QUALIFIER_3
3055 Place responsible for code maintenance, coded
CODE_LIST_RESPONSIBLE_AGENCY_3
3232 Related place/location 2 RELATED_PLACE_AREA_2
5479 Allocation, coded RELATION_CODE
2.9 FII – Credit Institute Segment FII is implemented as segment E1VDEWFII and specifies the credit institute of the partner identified in the NAD segment.
FII E1VDEWFII
3035 Participant, qualifier PARTY_ID
3194 Account number ACCOUNT_NUMBER
3192 Account holder ACCOUNT_HOLDER_1
3192 Account holder ACCOUNT_HOLDER_2
6345 Currency, coded ACCOUNT_CURRENCY
3433 Bank, ID BANK_ID
1131 Code list, qualifier BANK_CODE_LIST_1
3055 Place responsible for code maintenance, coded BANK_RESP_AGENCY_1
3434 Branch number BANK_BRANCH
1131 Code list, qualifier BANK_CODE_LIST_2
3055 Place responsible for code maintenance, coded BANK_RESP_AGENCY_2
3432 Name of credit institute BANK_NAME
3436 Branch location BANK_BRANCH_PLACE
3207 Country, coded COUNTRY
2.10 RFF – Reference Specifications Segment RFF is implemented as segment E1VDEWRFF_2 and is used to specify references that refer to the current business partner (for example, tax identification number).
RFF E1VDEWRFF_2
1153 Reference, qualifier REFERENCEQUALIFIER
1154 Reference number REFERENCENUMBER
1156 Line number LINENUMBER
4000 Reference number VERSIONNUMBER
1060 Revision number REVISION
2.11 CTA – Contact Partner Segment CTA is implemented as segment E1VDEWCTA and is used to identify contact partners within the company specified in the previous NAD segment.
CTA E1VDEWCTA
3139 Function of contact partner, coded CONTACTFUNC
3413 Department or agent, identification CONTACTID
3412 Department or agent CONTACTNAME
2.12 COM - Communication Segment COM is implemented as segment E1VDEWCOM and is used to specify the communication number and the communication category of the agent or department specified in the previous CTA segment.
COM E1VDEWCOM
3148 Communication number COMMNUMBER
3155 Communication method/service, qualifier COMMQUALF
2.13 CUX – Currency Specifications Segment CUX is implemented as segment E1VDEWCUX and is used to make currency specifications for the entire bill.
CUX E1VDEWCUX
6347 Currency details, qualifier CURRENCY_DETAILS_1
6345 Currency, coded CURRENCY_ID_1
6343 Currency qualifier CURRENCY_QUALIFIER_1
6348 Currency conversion rate basis CURRENCY_RATE_BASE_1
6347 Currency details, qualifier CURRENCY_DETAILS_2
6345 Currency, coded CURRENCY_ID_2
6343 Currency qualifier CURRENCY_QUALIFIER_2
6348 Currency conversion rate basis CURRENCY_RATE_BASE_2
5402 Exchange rate EXCHANGE_RATE
6341 Currency exchange, coded EXCH_RATE_CURR_MARKET_ID
2.14 PAT – Payment Conditions Segment PAT is implemented as segment E1VDEWPAT and is used by the sender to specify the payment conditions for the entire bill. It specifies that the due date has been determined and is given in the following DTM segment. PAT E1VDEWPAT
4279 Payment conditions type, qualifier PAYMENT_TERMS_TYPE
4277 Payment conditions, identification PAYMENT_TERMS_ID
1131 Code list, qualifier PAYMENT_TERMS_CODE_LIST
3055 Place responsible for code maintenance, coded
PAYMENT_TERMS_AGENCY
4276 Payment conditions PAYMENT_TERMS_1
4276 Payment conditions PAYMENT_TERMS_2
2475 Payment reference date, coded TIME_REFERENCE
2009 Time reference, coded TIME_RALATION
2151 Type of time frame, coded TIME_PERIOD
2152 Number of time frames TIME_NR_PERIODS
2.15 DTM – Date/Time/Time Frame Segment DTM is implemented as segment E1VDEWDTM_3 and is used for the due date.
DTM E1VDEWDTM_3
2005 Date/time/time frame, qualifier DATUMQUALIFIER
2380 Date/time/time frame DATUM
2379 Date/time/time frame, format qualifier FORMAT
2.16 LIN – Item Data Segment LIN is implemented as segment E1VDEWLIN and is used to display the start of the item portion within a bill. The item portion is created from repetition of segment groups, which always begin with a LIN segment. During bill processing, when the amounts are determined for multiple points of delivery, the segment group is repeated in the message in relation to the number of points of delivery.
LIN E1VDEWLIN
1082 Item number LINE_ITEM_NUMBER
1229 Action request/notification, coded ACTION_REQUEST_NOT_CODE
7140 Product/service number ITEM_NUMBER
7143 Product/service number, type, coded ITEM_NUMBER_TYPE
1131 Code list, qualifier CODE_LIST_QUALIFIER
3055 Place responsible for code maintenance, coded
CODE_LIST_RESPONSIBLE_AGENCY
5495 Display for subitem, coded SUBLINE_INDICATOR
1082 Item number SUBLINE_ITEM_NUMBER
1222 Configuration level CONFIGURATION_LEVEL
7083 Subitem allocation, coded CONFIGURATION
2.17 PIA – Additional Product Identification Segment PIA is implemented as segment E1VDEWPIA and is used to identify the product for the relevant item by means of the EDIS code. This identification process can only be used for exchanging energy data in the German energy industry.
PIA E1VDEWPIA
4347 Product identification function, qualifier
PRODUCT_ID
7140 Product/service number ITEM_NUMBER_1
7143 Product/service number, type, coded
ITEM_NUMBER_TYPE_1
1131 Code list, qualifier CODE_LIST_QUALIFIER_1
3055 Place responsible for code maintenance, coded
CODE_LIST_RESPONSIBLE_AGENCY_1
7140 Product/service number ITEM_NUMBER_2
7143 Product/service number, type, coded
ITEM_NUMBER_TYPE_2
1131 Code list, qualifier CODE_LIST_QUALIFIER_2
3055 Place responsible for code maintenance, coded
CODE_LIST_RESPONSIBLE_AGENCY_2
7140 Product/service number ITEM_NUMBER_3
7143 Product/service number, type, coded
ITEM_NUMBER_TYPE_3
1131 Code list, qualifier CODE_LIST_QUALIFIER_3
3055 Place responsible for code maintenance, coded
CODE_LIST_RESPONSIBLE_AGENCY_3
7140 Product/service number ITEM_NUMBER_4
7143 Product/service number, type, coded
ITEM_NUMBER_TYPE_4
1131 Code list, qualifier CODE_LIST_QUALIFIER_4
3055 Place responsible for code maintenance, coded
CODE_LIST_RESPONSIBLE_AGENCY_4
7140 Product/service number ITEM_NUMBER_5
7143 Product/service number, type, coded
ITEM_NUMBER_TYPE_5
1131 Code list, qualifier CODE_LIST_QUALIFIER_5
3055 Place responsible for code maintenance, coded
CODE_LIST_RESPONSIBLE_AGENCY_5
2.18 QTY – Quantity Segment QTY is implemented as segment E1VDEWQTY and is used to specify quantities for items.
QTY E1VDEWQTY
6063 Quantity, qualifier QUANTITY_QUALIFIER
6060 Quantity QUANTITY
6411 Measurement unit, qualifier MEASURE_UNIT_QUALIFIER
2.19 MOA – Monetary Amount Segment MOA is implemented as segment E1VDEWMOA and is used to specify the monetary amount that relates to the current item.
MOA E1VDEWMOA
5025 Monetary amount type, qualifier MONETARY_AMOUNT_TYPE
5004 Monetary amount MONETARY_AMOUNT_VALUE
6345 Currency, coded CURRENCY_ID
6343 Currency qualifier CURRENCY_QUALIFIER
4405 Status, coded STATUS
2.20 PAT – Payment Conditions Segment PAT is implemented as segment E1VDEWPAT_2 and is used by the sender to specify the payment conditions for a payment plan item. (This function helps you during budget billing.). It specifies that the due date has been determined and is given in the following DTM segment.
PAT E1VDEWPAT_2
4279 Payment conditions type, qualifier PAYMENT_TERMS_TYPE
4277 Payment conditions, identification PAYMENT_TERMS_ID
1131 Code list, qualifier PAYMENT_TERMS_CODE_LIST
3055 Place responsible for code maintenance, coded
PAYMENT_TERMS_AGENCY
4276 Payment conditions PAYMENT_TERMS_1
4276 Payment conditions PAYMENT_TERMS_2
2475 Payment reference date, coded TIME_REFERENCE
2009 Time reference, coded TIME_RALATION
2151 Type of time frame, coded TIME_PERIOD
2152 Number of time frames TIME_NR_PERIODS
2.21 DTM – Date/Time/Time Frame Segment DTM is implemented as segment E1VDEWDTM_4 and is used for the due date.
DTM E1VDEWDTM_4
2005 Date/time/time frame, qualifier DATUMQUALIFIER
2380 Date/time/time frame DATUM
2379 Date/time/time frame, format qualifier FORMAT
2.22 PRI – Price Specifications Segment PRI is implemented as segment E1VDEWPRI and is used to make price specifications for the current item.
PRI E1VDEWPRI
5125 Price, qualifier PRICE_QUALIFIER
5118 Price PRICE
5375 Price type, coded PRICE_TYPE
5387 Price type, qualifier PRICE_TYPE_QUALIFIER
5284 Price basis - quantity PRICE_BASIS
6411 Measurement unit, qualifier MEASURE_UNIT
5213 Price reference for subitem, coded SUB_LINE
2.23 RFF – Reference Specifications Segment RFF is implemented as segment E1VDEWRFF_3 and is used to specify references that refer to the current item (for example, customer number, meter number, or contract number). It links the process to a customer of the bill recipient if, for example, no point of delivery ID exists. If multiple transactions are used in a bill, the individual processes can be identified by means of an application reference number.
RFF E1VDEWRFF_3
1153 Reference, qualifier REFERENCEQUALIFIER
1154 Reference number REFERENCENUMBER
1156 Line number LINENUMBER
4000 Reference number VERSIONNUMBER
1060 Revision number REVISION
2.24 LOC - Location Segment LOC is implemented as segment E1VDEWLOC_2 and is used to specify a country/city/location of a corresponding city 1 / corresponding city 2.
LOC E1VDEWLOC_2
3227 Location, qualifier PLACE_QUALIFIER
3225 Location, identification PLACE_ID
1131 Code list, qualifier CODE_LIST_QUALIFIER_1
3055 Place responsible for code maintenance, coded
CODE_LIST_RESPONSIBLE_AGENCY_1
3224 Location PLACE
3223 Related place/location 1, identification
RELATED_PLACE_COMPANY_1
1131 Code list, qualifier CODE_LIST_QUALIFIER_2
3055 Place responsible for code maintenance, coded
CODE_LIST_RESPONSIBLE_AGENCY_2
3222 Related place/location 1 RELATED_PLACE_AREA_1
3233 Related place/location 2, identification
RELATED_PLACE_COMPANY_2
1131 Code list, qualifier CODE_LIST_QUALIFIER_3
3055 Place responsible for code maintenance, coded
CODE_LIST_RESPONSIBLE_AGENCY_3
3232 Related place/location 2 RELATED_PLACE_AREA_2
5479 Allocation, coded RELATION_CODE
2.25 TAX – Tolls, Taxes, and Fees Segment TAX is implemented as segment E1VDEWTAX. It is used to specify the franchise fees of the service location, or which franchise fee rate is applicable.
TAX E1VDEWTAX
5283 Toll/tax/fee class, qualifier DTF_FUNCTION
5153 Toll/tax/fee type, coded TYPE_CODED
1131 Code list, qualifier TYPE_CODE_LIST
3055 Place responsible for code maintenance, coded TYPE_AGENCY
5152 Toll/tax/fee type TYPE
5289 Indicator for clearing tolls, taxes, and fees ACCOUNT_ID
1131 Code list, qualifier ACCOUNT_CODE_LIST
3055 Place responsible for code maintenance, coded ACCOUNT_AGENCY
5286 Tolls/taxes/fees, assessment basis ASSESSMENT_BASIS
5279 Toll/tax/fee rate, identification DETAIL_RATE_ID
1131 Code list, qualifier DETAIL_CODE_LIST_1
3055 Place responsible for code maintenance, coded DETAIL_AGENCY_1
5278 Toll/tax/fee rate DETAIL_RATE
5273 ID of calculation basis for tolls, taxes, and fees DETAIL_RATE_BASIS
1131 Code list, qualifier DETAIL_CODE_LIST_2
3055 Place responsible for code maintenance, coded DETAIL_AGENCY_2
5305 Toll/tax/fee category, coded CATEGORY
3446 Tax number PARTY_TAX_ID
1227 Calculation sequence, coded CALCULATION_SEQUENCE
2.26 MOA – Monetary Amount Segment MOA is implemented as E1VDEWMOA_2 and is used to specify the due tax rates for the item lines.
MOA E1VDEWMOA_2
5025 Monetary amount type, qualifier MONETARY_AMOUNT_TYPE
5004 Monetary amount MONETARY_AMOUNT_VALUE
6345 Currency, coded CURRENCY_ID
6343 Currency qualifier CURRENCY_QUALIFIER
4405 Status, coded STATUS
2.27 NAD – Name and Address Segment NAD is implemented as segment E1VDEWNAD_2 and is used to identify the premise. This segment is used for testing if there is insufficient coding for the point of delivery.
NAD E1VDEWNAD_2
3035 Participant, qualifier ACTION
3039 Identification of participant PARTNER
1131 Code list, qualifier CODELIST
3055 Place responsible for code maintenance, coded CODELISTAGENCY
3124 Line for name and address NAMEADDRESS1
3124 Line for name and address NAMEADDRESS2
3124 Line for name and address NAMEADDRESS3
3124 Line for name and address NAMEADDRESS4
3124 Line for name and address NAMEADDRESS5
3036 Name of participant PARTNERNAME1
3036 Name of participant PARTNERNAME2
3036 Name of participant PARTNERNAME3
3036 Name of participant PARTNERNAME4
3036 Name of participant PARTNERNAME5
3045 Name of participant, format, coded PARTNERFORMAT
3042 Street and house number or PO box STREET1
3042 Street and house number or PO box STREET2
3042 Street and house number or PO box STREET3
3042 Street and house number or PO box STREET4
3164 City CITY
3229 Region, identification REGION
3251 Postal/zip code ZIPCODE
3207 Country, coded COUNTRY
2.28 UNS – Section Control Section UNS is implemented as segment E1VDEWUNS and is used to separate the item section of a message from the totals section.
UNS E1VDEWUNS
0081 Section ID, coded SECTION_ID
2.29 MOA – Monetary Amount Segment MOA is implemented as segment E1VDEWMOA_3 and is used to specify advance payments or full amounts for the bill.
MOA E1VDEWMOA_3
5025 Monetary amount type, qualifier MONETARY_AMOUNT_TYPE
5004 Monetary amount MONETARY_AMOUNT_VALUE
6345 Currency, coded CURRENCY_ID
6343 Currency qualifier CURRENCY_QUALIFIER
4405 Status, coded STATUS
2.30 TAX – Tolls, Taxes, and Fees Segment TAX is implemented as segment E1VDEWMOA_2 and is used to specify advance payments or full amounts for the bill.
TAX E1VDEWTAX_2
5283 Toll/tax/fee class, qualifier DTF_FUNCTION
5153 Toll/tax/fee type, coded TYPE_CODED
1131 Code list, qualifier TYPE_CODE_LIST
3055 Place responsible for code maintenance, coded TYPE_AGENCY
5152 Toll/tax/fee type TYPE
5289 Indicator for clearing tolls, taxes, and fees ACCOUNT_ID
1131 Code list, qualifier ACCOUNT_CODE_LIST
3055 Place responsible for code maintenance, coded ACCOUNT_AGENCY
5286 Tolls/taxes/fees, assessment basis ASSESSMENT_BASIS
5279 Toll/tax/fee rate, identification DETAIL_RATE_ID
1131 Code list, qualifier DETAIL_CODE_LIST_1
3055 Place responsible for code maintenance, coded DETAIL_AGENCY_1
5278 Toll/tax/fee rate DETAIL_RATE
5273 ID of calculation basis for tolls, taxes, and fees DETAIL_RATE_BASIS
1131 Code list, qualifier DETAIL_CODE_LIST_2
3055 Place responsible for code maintenance, coded DETAIL_AGENCY_2
5305 Toll/tax/fee category, coded CATEGORY
3446 Tax number PARTY_TAX_ID
1227 Calculation sequence, coded CALCULATION_SEQUENCE
2.31 MOA – Monetary Amount Segment MOA is implemented as segment E1VDEWMOA_4 and is used to specify the due amount for the record in the TAX segment, which applies for the entire bill.
MOA E1VDEWMOA_4
5025 Monetary amount type, qualifier MONETARY_AMOUNT_TYPE
5004 Monetary amount MONETARY_AMOUNT_VALUE
6345 Currency, coded CURRENCY_ID
6343 Currency qualifier CURRENCY_QUALIFIER
4405 Status, coded STATUS
2.32 UNT – End of Message Segment Segment UNT is implemented as segment E1VDEWUNT. This segment is mandatory in UN/EDIFACT. It must always be the last segment in a message.
UNT E1VDEWUNT
0074 Number of segments in the message NUMSEG
0062 Message reference number REFNUM
3 XML und INVOIC
XML (Hypertext Markup Language) is increasingly becoming the standard format for exchanging electronic data. We can assume that in the future data exchange will occur exclusively by means of XML. In March 2002, the German electricity association (VDEW) released an XML schema for message category INVOIC. XML data can be exported and imported using the Business Connector.
Copyright © Copyright 2005 SAP AG. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.
Microsoft, Windows, Outlook, and PowerPoint
are registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation in the United States and/or other countries.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are
trademarks or registered trademarks of Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide
Web Consortium, Massachusetts Institute of Technology.
Java is a registered trademark of Sun Microsystems, Inc.
JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.
MaxDB is a trademark of MySQL AB, Sweden.
SAP, R/3, mySAP, mySAP.com, xApps, xApp, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.
These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.