!--a11y-->
Purchasing Data (Header Level) 
Technical name: 2LIS_02_HDR
Type of DataSource |
Transaction Data (Movement Data) |
Application Component |
Materials Management (MM) |
Available as of OLTP Release |
SAP R/3 4.0B |
Available as of Plug-In Release |
PI 2000.1 |
RemoteCube Compatibility |
no |
Activation of the DataSource.
The DataSource is used to extract the basic data for analyses of purchasing documents consistently to a BW system.
A delta update is supported. Delta process: ABR – Complete delta update with deletion indicator using delta queue (Cube-compatible).
Field in Extraction Structure |
Description of Field in Extraction Structure |
Table of Origin |
Field in Table of Origin |
HDRVORG |
Process for Purchasing Document |
hard-coded |
|
ALIEF |
Number of Deliveries |
counted |
|
ARECH |
Number of Invoices for Vendor |
counted |
|
BEDAT |
Date of Purchasing Document |
EKKO |
BEDAT |
BSART |
Purchasing Document Category |
EKKO |
BSART |
BSTYP |
Purchasing Document Category |
EKKO |
BSTYP |
BUDAT |
Posting Date of Goods Receipt or Invoice Receipt for the Purchase Order |
EKKO / EKBE |
BUDAT |
EBELN |
Document Number of Purchasing Document |
EKKO |
EBELN |
EKGRP |
Purchasing Group |
EKKO |
EKGRP |
EKORG |
Purchasing Organization |
EKKO |
EKORG |
KDATB |
Validity Period Start Date |
EKKO |
KDATB |
KDATE |
End of Validity Period |
EKKO |
KDATE |
LBLIF |
Field is not used |
EKKO |
LBLIF |
LIFNR |
Vendor’s Account Number |
EKKO T001 |
LIFNR |
LIFRE |
Different Invoicing Party |
EKKO |
LIFRE |
LLIEF |
Supplying Vendor |
EKKO |
LLIEF |
LOGSY |
Logical System |
EKKO |
LOGSY |
ORGLOGSY |
Logical System |
|
|
RESWK |
Issuing Plant for Stock Transport Order |
EKKO |
RESWK |
STATU |
Status of Purchasing Document |
EKKO |
STATU |
SYDAT |
Purchasing Document Creation Date |
EKKO / EKBE |
BEDAT |
WAERS |
PO Currency |
EKKO |
WAERS |
WKURS |
Exchange Rate |
EKKO |
WKURS |
NOHDR |
Counter for Documents |
counted |
|
PWLIF |
Goods Supplier |
EKPA |
LIFNZ |
PREST |
Invoicing Party |
EKPA |
LIFNZ |
PLIWK |
Supplying Plant to Which Partner Roles Have Been Assigned |
EKPA |
LIFNZ |
PLIEF |
Vendor to Whom Partner Roles Have Been Assigned |
EKPA |
LIFNZ |
PBEST |
Ordering Address |
EKPA |
LIFNZ |
PERIV |
Fiscal Year Variant |
T001 |
|
ROCANCEL |
Cancellation of Data Record |
hard-coded |
|
This DataSource provides information about the header data of a purchasing document, such as vendor, purchasing organization, order currency, and so on.
In the ERP system, information about the header data of a purchasing document is contained in the EKKO table (Purchasing Document Header).
Note that if you change a purchasing document, the system only takes into consideration the data that is relevant for extraction. The system therefore only executes a delta update for this DataSource if changes are made to purchasing document header data that has a corresponding field in the DataSource.
By reading the purchase order history during restructuring, multiple records are created with the Purchase Order or Purchase Order/Item or Purchase Order/Item/Schedule Line key for multiple goods receipts for a purchase order or item or schedule line.
For this reason, all key figures in a DataStore object that contains the corresponding key definition are updated in an additive process. This applies to all key figures whose source field in the DataSource definition has the inversion indicator. These key figures must not be set to Overwrite. For more information, see the DataStore object definition 0PUR_O01 (Purchase Order Items).
For further information about purchasing documents, see the SAP Library under Materials Management ® Purchasing.
This field can contain the following values:
· ‘blank‘ – New data record
· ‘X’ – Cancellation of data record
· ‘R’ – Deletion of data record
For more information, see SAP Note 578471: Deleted Items in BW and Statistics
If the information in this field relates to an event in the purchase order, the field is filled with the posting date of the purchase order. If the information relates to a goods receipt or an invoice, the field is filled with the posting date of the corresponding document.
For purchasing documents that were created in a currency other than the local currency, or to which documents such as invoices were posted in a different currency; The contents of this field specifies the conversion factor with which you can convert the foreign currency to the local currency.
In the Purchasing component, you can use the General Reports transaction (transaction code ME80FN) to select, aggregate, and summarize information about purchasing activities. You can assemble the information that is to be reported according to selection criteria such as material, purchasing document, vendor, plant, and purchasing organization.
To assign the information in the list of issued purchasing documents clearly according to your wishes, you can use functions such as Sort, Filter, Aggregate Across Various Fields, Add Totals and Subtotals. You can also display the detail data for a purchasing document, a vendor, or a material.
If you select Change View, you can choose between the following views to display the output list:
· Header/Item Data(data from the tables EKKO and EKPO)
· Delivery Schedule Lines (data from the table EKET)
· Purchase Order History(data from the table EKBE)
You can check the data from the DataSource 2LIS_02_HDR with the Header/Item Data view.
If you select Choose Layout, you have access to all the SAP List Viewersfunctions. In other words, you can change the existing layout (such as add or hide fields and columns, change the sort sequence, add subtotals, set filters), save the changed layout, and choose a different layout.
If you choose the Header/Item Data view in the transaction ME80FN, you can compare the data in the DataSource fields with the original document data in the ERP system, such as:
· Document Date (BEDAT)
· Purchasing Document Type (BSART)
· Purchasing Document Number (EBELN)
· Purchasing Group (EKGRP)
· Purchasing Organization (EKORG)
· Vendor’s Account Number (LIFNR)