!--a11y-->
Purchasing Data (Schedule Line
Level) 
Technical name: 2LIS_02_SCL
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 |
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 |
HWAER |
Local Currency |
T001 |
WAERS |
KDATB |
Validity Period Start Date |
EKKO |
KDATB |
KDATE |
End of Validity Period |
EKKO |
KDATE |
LBLIF |
Field is not used |
EKKO |
|
LIFNR |
Vendor’s Account Number |
EKKO / T001W |
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 |
AFNAM |
Name of Requester |
EKPO |
AFNAM |
AKTNR |
Action |
EKPO |
AKTNR |
BSGRU |
Reason for Ordering |
EKPO |
BSGRU |
BWAPPLNM |
Application Component |
TMCLVBW |
APPLNM |
BWVORG |
SAP BW - Transaction Key |
hard-coded |
|
EBELP |
Item Number of Purchasing Document |
EKPO |
EBELP |
ELIKZ |
Final Delivery Indicator |
EKPO |
ELIKZ |
EMATN |
Material Number |
EKPO |
EMATN |
EREKZ |
Final Invoice Indicator |
EKPO |
EREKZ |
KONNR |
Number of Principal Agreement |
EKPO |
KONNR |
KTPNR |
Item Number of Principal Agreement |
EKPO |
KTPNR |
LGORT |
Storage Location |
EKPO |
LGORT |
LMEIN |
Base Unit of Measure |
EKPO |
LMEIN |
MATKL |
Material Group |
EKPO |
MATKL |
MATNR |
Material Number |
EKPO |
MATNR |
MEINS |
PO Unit |
EKPO |
MEINS |
NETPR |
Net Price |
calculated |
|
PEINH |
Price Unit |
EKPO |
PEINH |
PSTYP |
Item Category in Purchasing Document |
EKPO |
PSTYP |
TXZ01 |
Description |
EKPO |
TXZ01 |
UMREN |
Denominator for Converting PO UoM into Base UoM. |
EKPO |
UMREN |
UMREZ |
Counter for Converting PO UoM into Base UoM. |
EKPO |
UMREZ |
WEBRE |
GR-Based Invoice Verification Indicator |
EKPO |
WEBRE |
WERKS |
Plant |
EKPO |
WERKS |
XERSY |
Evaluated Receipt Settlement (ERS) |
EKPO |
XERSY |
BANFN |
Purchase Requisition Number |
EKET |
BANFN |
BNFPO |
Item Number of Purchase Requisition |
EKET |
BNFPO |
BWBRTWR |
Gross Purchase Order Value in Order Currency |
calculated |
|
BWEFFWR |
Effective Order Value |
calculated |
|
BWGEO |
BW: Purchase Value in Local Currency |
calculated |
|
BWGEOO |
BW: Purchase Value in Order Currency |
calculated |
|
BWGVO |
BW: Sales Value in Local Currency |
calculated |
|
BWGVP |
BW: Retail Value with Tax in Local Currency. |
calculated |
|
BWKZWI1 |
Condition Subtotal 1 from Calculation Schema |
calculated |
|
BWKZWI2 |
Condition Subtotal 2 from Calculation Schema |
calculated |
|
BWKZWI3 |
Condition Subtotal 3 from Calculation Schema |
calculated |
|
BWKZWI4 |
Condition Subtotal 4 from Calculation Schema |
calculated |
|
BWKZWI5 |
Condition Subtotal 5 from Calculation Schema |
calculated |
|
BWKZWI6 |
Condition Subtotal 6 from Calculation Schema |
calculated |
|
BWMNG |
BW: Quantity in Order Unit |
calculated |
|
BZGWR |
Planned Delivery Costs for Purchase Order from Invoice in Local Currency |
calculated |
|
CHARG |
Batch Number |
EKET |
CHARG |
DBWGEO |
Delta PO/GR SP |
calculated |
|
DBWMNG |
Delta PO/GR in Base UoM |
calculated |
|
EINDT |
Item Delivery Date |
EKET |
EINDT |
ETENR |
Schedule Line Counter |
EKET |
ETENR |
MAHNZ |
Number of Reminders |
EKET |
MAHNZ |
SLFDT |
Delivery Date Relevant for Statistics |
EKET |
SLFDT |
UZEIT |
Time of Day |
EKET |
UZEIT |
PERIV |
Fiscal Year Variant |
T001 |
|
SCL_BEDAT |
Schedule Line Date |
EKET |
BEDAT |
NOSCL |
Counter for Scheduling Agreement Schedule Lines |
hard-coded |
|
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 |
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
· the item data such as material, purchase order quantity, order unit, net price, and so on
· the purchasing document delivery schedule lines, such as schedule line number, delivery date, schedule line quantity, value of schedule line quantity, and so on
The DataSource also provides information about the documents that are posted with regard to the purchase order, such as goods receipts and invoices. In addition, the DataSource provides information about how these documents are assigned to the schedule lines.
The assignment of purchase order history information and schedule lines is not stored in a database table. As a result, this information is only created during the posting of the documents or during initialization of the DataSource.
In the ERP system, this information is contained in the following tables:
· Header data in the table EKKO (Purchasing Document Header)
· Item data in the table EKPO (Purchasing Document Item)
· Schedule lines in the table EKET (Scheduling Agreement Delivery Schedule Lines)
· Purchase order history in the table EKBE (History of Purchasing Document)
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 identifies the event that is based on the information in the DataSource. The contents of this field determines the importance and the behavior of other fields in the DataSource. The field ALIEF (Number of Deliveries) is, for example, only filled if the event is a goods receipt.
For more information, see SAP Note 684465: BWVORG for Purchasing Data Sources.
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.
The system always converts the net price to the local currency and to the base unit of measure.
For further information, see SAP Note 670313: BW: Field NETPR for DataSource 2LIS_02_ITM and 2LIS_02_SCL.
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.
The calculation is based on the item information and schedule line information.
For documents with purchase order quantity, the following applies:
bweffwr = ekpo-effwr / ekpo-menge * eket-menge
bweffwr = Effective Price / Item Quantity * Schedule Line Quantity
For documents with target quantity, the following applies:
bweffwr = ekpo-effwr / ekpo-menge * eket-menge
bweffwr = Effective Price / Item Target Quantity * Schedule Line Quantity
The value contained in this field depends on the information stored in the field BWVORG (BW Transaction Key).
The field determines if the value is derived from a purchase order, a goods receipt, or an invoice. This means, for example, that the values for the goods receipt are available when the contents of the BWVORG field are based on a goods receipt process and not on a purchase order or invoice.
For purchase orders, the following applies:
bwgeo = bwgeoo converted using WKURS
For goods receipts, the following applies:
bwgeo = Goods Receipt Value
For invoices, the following applies:
bwgeo = Assigned Invoice Quantity * Invoice Value / Total Invoice Value
bwgeo = eket-menge * ekbe-dmbtr / ekbe-menge
The value contained in this field depends on the information stored in the field BWVORG (BW Transaction Key).
The conversion of values in this field is always based on the exchange rate (WKURS) in the purchase order.
For purchase orders, the following applies:
bwgeoo = eket-menge * ekpo-effwr / ekpo-menge.
bwgeoo = Schedule Line Quantity * Effective Price / Item Quantity
For goods receipts, the following applies:
bwgeoo = bwgeo converted using WKURS
For invoices, the following applies:
bwgeoo = bwgeo converted using WKURS
The information in this field also depends on BWVORG, since it determines whether the quantity specified is based on the purchase order, goods receipt, or invoice.
The information in this field indicates the difference between the purchase order value and the goods receipt value. The system only calculates this delta if a purchase order item is completed. This is the case, if:
· The item was completely delivered
· The Delivery completed indicator (ELIKZ) has been set
· The item has been deleted
The information is only available if one of these conditions is met for a purchase order item.
Since the DBWGEO field displays the difference between purchase order and goods receipt, this field is also dependent on the BWVORG field.The delta information is not available for invoices, but only for purchase order and goods receipt processes.
The information in this field indicates the difference between the purchase order quantity and the goods receipt quantity in the base unit of measure. The system only calculates this delta if a purchase order item is completed. This is the case, if:
· The item was completely delivered
· The Delivery completed indicator (ELIKZ) has been set
· The item has been deleted
The information is only available if one of these conditions is met for a purchase order item.
Since the DBWMNG field displays the difference between purchase order and goods receipt, this field is also dependent on the BWVORG field.The delta information is not available for invoices, but only for purchase order and goods receipt processes.
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_SCL in last two views mentioned.
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 following DataSource fields with the original document data in the ERP system:
· Document Date (BEDAT)
· Purchasing Document Type (BSART)
· Purchasing Document Number (EBELN)
· Purchasing Group (EKGRP)
· Purchasing Organization (EKORG)
· Vendor’s Account Number (LIFNR)
· Item Number of Purchasing Document (EBELP)
· Material Number (MATNR)
· Material Group (MATKL)
· Plant (WERKS)
· Storage Location (LGORT)
· Order Unit (MEINS)
If you choose the Scheduling Lines view in the transaction ME80FN, you can compare the data in the following DataSource fields with the original document data in the ERP system:
· Item Delivery Date (EINDT)
· Quantity in Order Unit (BWMNG, if BWVORG=1)
· Schedule Line Date (SCL_BEDAT)
If you select the Purchase Order History view in the transaction ME80FN, you can check the information of documents that were posted with regard to a purchasing document, such as goods receipt documents, invoices, subsequent debits, and credit memos.