Вы находитесь на странице: 1из 31

DataSources

PDF download from SAP Help Portal:


http://help.sap.com/saphelp_tm80/helpdata/en/b8/1385403e1b6e1de10000000a1550b0/content.htm
Created on September 01, 2016

The documentation may have changed since you downloaded the PDF. You can always find the latest information on SAP Help
Portal.

Note
This PDF document contains the selected topic and its subtopics (max. 150) in the selected structure. Subtopics from other structures are not included.

2016 SAP SE or an SAP affiliate company. 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 SE. The information contained herein may be changed without prior notice. Some software products marketed by SAP
SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are
provided by SAP SE 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. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE in
Germany and other countries. Please see www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.

Table of content

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 1 of 31

Table of content
1 DataSources
1.1 Extraction SD Sales: Document Header
1.2 Extraction SD Sales: Document Item
1.3 Extraction SD Sales: Order Conditions
1.4 Extraction SD Sales: Document Schedule Line
1.5 Extraction SD Order Header Status
1.6 Extraction SD Order Item Status
1.7 Extraction SD Sales: Document Item Billing
1.8 Extraction SD Sales: Document Schedule Line Billing
1.9 Extraction SD Sales: Order Delivery
1.10 Extraction of SD Billing Conditions
1.11 Message Status Data for FSSC

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 2 of 31

1 DataSources

1.1 Extraction SD Sales: Document Header


DataSource Transactional Data: 2LIS_11_VAHDR

The structure Extraction SD Sales: Document Header is used to extract header information from SD orders and quotations (but not requests) to a BI system.

Technical Data
Application Component

SD Sales (BW-BCT-SD-SLS)

Available as of Release

SAP R/3 4.0

Shipment

PlugIn 2000_1

Content Versions

There are no content versions

RemoteCube-Capable

No

Delta-Capable

Yes

Extraction from Archives

Yes

Verifiable

No

Data Modeling
Delta Update

Note
The delta update is supported using the delta method ABR. Note that when a change is made to the sales document, a delta update occurs only if one or
more fields in the extraction structure are affected by the change. You can find further information in SAP Note 576886.
Fields of Origin for the Extract Structure
Fields in the Extract Structure

Description of the Field in the Extract


Structure

Table of Origin

Field in the Table of Origin

ROCANCEL

Indicator: Cancellation of the data record

APOPLANNED

Planning in APO

ANGDT

Quotation/request valid from

VBAK

ANGDT

ANZAU

Number of orders

AUART

Sales document type

VBAK

AUART

AUGRU

Order reason (reason for transaction)

VBAK

AUGRU

BNDDT

Binding period of quotation for service


performance (valid to)

VBAK

BNDDT

BUKRS

Company code

VBAK

BUKRS

ERDAT

Date on which record was added

VBAK

ERDAT

FAKSK

Billing type block sales and distribution


document

VBAK

FAKSK

HWAER

Local currency

VBAK

HWAER

KUNNR

Sold-to party

VBAK

KUNNR

KURST

Exchange rate type

VBAK

KURST

KVGR1

Customer group 1

VBAK

KVGR1

KVGR2

Customer group 2

VBAK

KVGR2

KVGR3

Customer group 3

VBAK

KVGR3

KVGR4

Customer group 4

VBAK

KVGR4

KVGR5

Customer group 5

VBAK

KVGR5

LIFSK

Delivery note block document header

VBAK

LIFSK

PERIV

Fiscal year variant

T001

PERIV

PVRTNR

Sales representative

VBAK

PVRTNR

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 3 of 31

SPARA

Division order header

VBAK

SPART

STWAE

Statistics currency

VBAK

STWAE

VBELN

Sales and distribution document number VBUK

VBELN

VBTYP

Sales document category

VBAK

VBTYP

VDATU

Requested delivery date

VBAK

VDATU

VGTYP_AK

Sales document category of reference


document in the order header

VBAK

VGTYP

VKBUR

Sales office

VBAK

VKBUR

VKGRP

Sales group

VBAK

VKGRP

VKORG

Sales organization

VBAK

VKORG

VTWEG

Distribution channel

VBAK

VTWEG

WAERK

Currency of sales and distribution


document

VBAK

WAERK

Extractor Logic
Field VDATU has the same name as Update Date for Statistics Update for DataSources 2LIS_11_VAITM and 2LIS_11_VASCL. In 2LIS_11_VAHDR
however, the field VDATU contains the sold-to party's Requested Delivery Date .
If you need a field that can take over the Update Date for Statistics Update function, proceed as described in SAP Note 719603.
ROCANCEL - Cancellation of the data record
This field can have the following values:
Blank - new data record or after image
X - Cancellation of data record or before image
R - Deletion of data record

1.2 Extraction SD Sales: Document Item


DataSource Transactional Data: 2LIS_11_VAITM

The structure Extraction SD Sales: Document Item is used to extract item information from SD orders and quotations (but not requests) to a BI system.

Technical Data
Application Component

SD Sales (BW-BCT-SD-SLS)

Available as of Release

SAP R/3 4.0

Shipment

PlugIn 2000_1

Content Versions

There are no content versions

RemoteCube-Capable

No

Delta-Capable

Yes

Extraction from Archives

Yes

Verifiable

No

Data Modeling
Delta Update

Note
The delta update is supported using the delta method ABR. Note that when a change is made to the sales document, a delta update occurs only if one or
more fields in the extraction structure are affected by the change. You can find further information in SAP Note 576886.
Fields of Origin for the Extract Structure
Fields in the Extract Structure

Description of the Field in the Extract


Structure

Table of Origin

Field in the Table of Origin

ROCANCEL

Indicator: Cancellation of the data record

ABGRU

Reason for rejection for quotations and


orders

VBAP

ABGRU

ABSTA

Rejection status of sales and distribution VBUP


item

ABSTA

AEDAT

Last date on which object was changed

VBAP

AEDAT

ANGDT

Quotation/request valid from

VBAK

ANGDT

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 4 of 31

ANZAUPO

Number of order items

AUART

Sales document type

VBAK

AUART

AUGRU

Order reason (reason for transaction)

VBAK

AUGRU

AWAHR

Sales probability for item

VBAP

AWAHR

BNDDT

Binding period of quotation for service


performance (valid to)

VBAK

BNDDT

BRGEW

Gross weight of item

VBAP

BRGEW

BUKRS

Company code

VBAK

BUKRS

BWAPPLNM

Application component

VBAP

BWAPPLNM

BWVORG

SAP BW transaction key

VBAP

BWVORG

BZIRK

Sales district

VBKD

BZIRK

CHARG

Batch number

VBAP

CHARG

CMKUA

Exchange rate for credit data on

VBAP

CMKUA

requested delivery date


EAN11

European article number (EAN)

VBAP

EAN11

ERDAT

Date on which record was added

VBAP

ERDAT

ERNAM

Name of person who added the object

VBAP

ERNAM

ERZET

Time of entry

VBAP

ERZET

FAKSK

Billing type block sales and distribution


document

VBAK

FAKSK

FAKSP

Billing block item

VBAP

FAKSP

FBUDA

Date of services rendered

VBKD

FBUDA

FKDAT

Billing date for billing index and print

VBKD

FKDAT

GEWEI

Weight unit

VBAP

GEWEI

HWAER

Local currency

VBAK

HWAER

INCO1

Incoterms 1

VBKD

INCO1

INCO2

Incoterms 2

VBKD

INCO2

KBMENG

Cumulative confirmed quantity in sales

VBAP

KBMENG

units
KDGRP

Customer group

VBKD

KDGRP

KLMENG

Cumulative confirmed quantity in base

VBAP

KLMENG

units
KMEIN

Condition unit

VBAP

KMEIN

KNUMA_AG

Sales deal

VBAP

KNUMA_AG

KPEIN

Condition pricing unit

VBAP

KPEIN

KTGRD

Account assignment group debtor

VBKD

KTGRD

KUNNR

Sold-to party

VBAK

KUNNR

KURSK

Pricing exchange rate

VBKD

KURSK

KURSK_DAT

Translation date

VBKD

KURSK_DAT

KURST

Exchange rate type

VBAK

KURST

KVGR1

Customer group 1

VBAK

KVGR1

KVGR2

Customer group 2

VBAK

KVGR2

KVGR3

Customer group 3

VBAK

KVGR3

KVGR4

Customer group 4

VBAK

KVGR4

KVGR5

Customer group 5

VBAK

KVGR5

KWMENG

Cumulative order quantity in sales units

VBAP

KWMENG

KZWI1

Subtotal 1 from pricing procedure

VBAP

KZWI1

KZWI2

Subtotal 2 from pricing procedure

VBAP

KZWI2

KZWI3

Subtotal 3 from pricing procedure

VBAP

KZWI3

KZWI4

Subtotal 4 from pricing procedure

VBAP

KZWI4

KZWI5

Subtotal 5 from pricing procedure

VBAP

KZWI5

KZWI6

Subtotal 6 from pricing procedure

VBAP

KZWI6

LFMNG

Minimum delivery quantity in delivery


note processing

VBAP

LFMNG

LGORT

Storage location

VBAP

LGORT

LIFSK

Delivery note block document header

VBAK

LIFSK

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 5 of 31

LSMENG

Cumulative target delivery quantity (all

VBAP

LSMENG

delivery-relevant schedule lines)


MATKL

Merchandise category

VBAP

MATKL

MATNR

Material number

VBAP

MATNR

MATWA

Material entered

VBAP

MATWA

MCEX_APCAMPAIGN

Campaign of referred sales order item for VBKD


BW extraction

CAMPAIGN

MEINS

Base unit

VBAP

MEINS

MVGR1

Material group 1

VBAP

MVGR1

MVGR2

Material group 2

VBAP

MVGR2

MVGR3

Material group 3

VBAP

MVGR3

MVGR4

Material group 4

VBAP

MVGR4

MVGR5

Material group 5

VBAP

MVGR5

MWSBP

Tax amount in document currency

VBAJP

MWSBP

NETPR

Net price

VBAP

NETPR

NETWR

Net value of order item in document


currency

VBAP

NETWR

NTGEW

Net weight of item

PABLA

Unloading point for ship-to party

VBAP

PABLA

PERIV

Fiscal year variant

T001

PERIV

PKUNRE

Bill-to party

VBAP

PKUNRE

PKUNRG

Payer

VBAP

PKUNRG

PKUNWE

Ship-to party

VBAP

PKUNWE

POSNR

Item number of the sales and distribution VBUP

NTGEW

POSNR

document
PRODH

Product hierarchy

VBAP

PRODH

PRSDT

Date for pricing and exchange rate

VBKD

PRSDT

PS_POSID

Work breakdown structure element (WBS VBAP/PRPS


element)

PS_PSP_PNR/POSID

PSPDNR

Forwarding agent

VBAP

PSPDNR

PSTYV

Item category sales and distribution


document

VBAP

PSTYV

PVRTNR

Sales representative

VBAP

PVRTNR

ROUTE

Route

VBAP

ROUTE

SOBKZ

Special stock indicator

VBAP

SOBKZ

SPARA

Division order header

VBAK

SPART

SPART

Division

VBAP

SPART

STADAT

Statistics date

VBAP

STADAT

STCUR

Exchange rate for statistics (exchange

VBAP

STCUR

rate upon creation)


STWAE

Statistics currency

VBAK

STWAE

SUGRD

Reason for material substitution

VBAP

SUGRD

UEBTK

Unlimited overdelivery allowed

VBAP

UEBTK

UEBTO

Tolerance for over-delivery

VBAP

UEBTO

UMVKN

Denominator for conversion of sales


quantity into SKU

VBAP

UMVKN

UMVKZ

Numerator for conversion of sales


quantity into SKU

VBAP

UMVKZ

UMZIN

Denominator for conversion factor of

VBAP

UMZIN

UMZIZ

Numerator for conversion factor of target VBAP


quantity to storage quantity

UMZIZ

UNTTO

Tolerance for under-delivery

VBAP

UNTTO

UVALL

Incompleteness status of general item

VBUP

UVALL

UVFAK

Incompleteness status of item in relation


to billing document

VBUP

UVFAK

UVPRS

Item incomplete in relation to pricing

VBUP

UVPRS

UVVLK

Incompleteness status of item in relation

VBUP

UVVLK

target quantity to storage quantity

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 6 of 31

to delivery
VBELN

Sales and distribution document number VBUK

VBELN

VBTYP

Sales document category

VBAK

VBTYP

VDATU

Update date for statistics update

VBAP

VDATU

VGBEL

Document number of the reference

VBAP

VGBEL

document
VGPOS

Item number of the reference business


item

VBAP

VGPOS

VGTYP

Preceding sales document category

VBAP

VGTYP

VGTYP_AK

Sales document category of reference

VBAK

VGTYP

document in the order header


VKBUR

Sales office

VBAK

VKBUR

VKGRP

Sales group

VBAK

VKGRP

VKORG

Sales organization

VBAK

VKORG

VOLEH

Volume unit

VBAP

VOLEH

VOLUM

Item volume

VBAP

VOLUM

VRKME

Sales unit

VBAP

VRKME

VSTEL

Shipping point/goods receiving point

VBAP

VSTEL

VTWEG

Distribution channel

VBAK

VTWEG

WAERK

Currency of sales and distribution

VBAP

WAERK

document
WAERK_VBAK

Currency of sales and distribution


document

VBAK

WAERK

WAKTION

Action

VBKD

WAKTION

WAVWR

Cost in document currency

VBAP

WAVWR

WERKS

Plant

VBAP

WERKS

WMINR

Catalog number

VBKD

WMINR

ZIEME

Target quantity unit of measure

VBAP

ZIEME

ZMENG

Target quantity in sales units

VBAP

ZMENG

ZWERT

Target value for outline agreements in

VBAP

ZWERT

document currency
> PI 2004.1
APOPLANNED

Planning in APO

Extractor Logic
Determination of Update Date for Statistics Update (field VDATU): The update date for the statistics update is filled in the delta update with the local date of
the user (SY-DATLO). In reorganization, the field VDATU is filled with the creation date of the SD document (XVBAP-ERDAT).
ROCANCEL - Cancellation of the data record
This field can have the following values:
Blank - new data record or after image
X - Cancellation of data record or before image
R - Deletion of data record

Extraction SD Sales: Order Conditions


Technical name: 2LIS_11_VAKON

Technical Data
DataSource type
Application components

Transaction data
SD Sales (BW-BCT-SD-SLS)

Available from OLTP release

4.0B

Available from PlugIn release

PlugIn 2004_1

RemoteCube enabled

No

Delta enabled

Delta update is supported

Archivable

Yes

Verifiable

No

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 7 of 31

Prerequisites
Prerequisite for the use of the extractor is the R/3 core SAP Note 673964 or the corresponding support package.
For the R/3 Release 4.6c, SAP Note 726902 is a prerequisite, or support package SAPKIPZ141.

Use
With the 1.3 Extraction SD Sales: Order Conditions structure, you can extract active condition lines that contribute to the pricing result of a order item to a
BW system.

Delta Update
Delta update is supported.

Origin Fields of the Extraction Structure


Field in the Extraction Structure

Description of Field in the Extraction

Origin Table

Field in the Origin Table

Structure
ROCANCEL

Indicator: Cancellation of the data record

VBELN

Sales and distribution document number VBUK

VBELN

POSNR

Item number of the sales and distribution VBUP

POSNR

document
ABSTA

Rejection status of sales and distribution VBUP

UVPRS

item
UVPRS

Item incomplete regarding pricing

VBUP

UVPRS

AUART

Sales and distribution document type

VBAK

AUART

AUGRU

Order reason (reasons for process)

VBAK

AUGRU

BUKRS

Company code

VBAK

BUKRS

FAKSK

Billing type lock sales and distribution

VBAK

FAKSK

document
HWAER

Local currency

VBAK

HWAER

KUNNR

Sold-to party

VBAK

KUNNR

KURST

Exchange rate type

VBAK

KURST

KVGR1

Customer group 1

VBAK

KVGR1

KVGR2

Customer group 2

VBAK

KVGR2

KVGR3

Customer group 3

VBAK

KVGR3

KVGR4

Customer group 4

VBAK

KVGR4

KVGR5

Customer group 5

VBAK

KVGR5

STWAE

Statistics currency

VBAK

STWAE

VBTYP

Sales and distribution documents

VBAK

VBTYP

VKBUR

Sales office

VBAK

VKBUR

VKGRP

Sales group

VBAK

VKGRP

VKORG

Sales organization

VBAK

VKORG

VTWEG

Distribution channel

VBAK

VTWEG

ABGRU

Reason for rejection for offers and orders VBAP

ABGRU

AEDAT

Date of last change

VBAP

AEDAT

BWAPPLNM

Application components

VBAP

BWAPPLNM

BWVORG

SAP BW transaction key

VBAP

BWVORG

EAN11

European article number (EAN)

VBAP

EAN11

ERDAT

Date on which the record was added

VBAP

ERDAT

ERNAM

Name of the person who added the

VBAP

ERNAM

object
ERZET

System time

VBAP

ERZET

FAKSP

Billing block item

VBAP

FAKSP

KWMENG

Cumulated order quantity in sales units

VBAP

KWMENG

MATKL

Merchandise category

VBAP

MATKL

MATNR

Material number

VBAP

MATNR

MATWA

Material entered

VBAP

MATWA

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 8 of 31

MVGR1

Material group 1

VBAP

MVGR1

MVGR2

Material group 2

VBAP

MVGR2

MVGR3

Material group 3

VBAP

MVGR3

MVGR4

Material group 4

VBAP

MVGR4

MVGR5

Material group 5

VBAP

MVGR5

PKUNRE

Bill-to party

VBAP

PKUNRE

PKUNRG

Payer

VBAP

PKUNRG

PKUNWE

Ship-to party

VBAP

PKUNWE

PRODH

Product hierarchy

VBAP

PRODH

PSTYV

Item type sales and distribution

VBAP

PSTYV

document
PVRTNR

Sales representative

VBAP

PVRTNR

SPART

Division

VBAP

SPART

STADAT

Statistics date

VBAP

STADAT

STCUR

Translation exchange rate for statistics

VBAP

STCUR

(exchange rate upon creation)


VRKME

Sales unit

VBAP

VRKME

WAERK

Currency of sales and distribution

VBAP

WAERK

document
ZIEME

Target quantity unit of measure

VBAP

ZIEME

ZMENG

Target quantity in sales units

VBAP

ZMENG

BZIRK

Sales district

VBKD

BZIRK

FBUDA

Date of services rendered

VBKD

FBUDA

FKDAT

Billing date for billing index and print

VBKD

FKDAT

INCO1

Incoterms part 1

VBKD

INCO1

INCO2

Incoterms part 2

VBKD

INCO2

KDGRP

Customer group

VBKD

KDGRP

KTGRD

Account assignment group debitor

VBKD

KTGRD

KURSK

Exchange rate for pricing

VBKD

KURSK

KURSK_DAT

Translation date

VBKD

KURSK_DAT

PRSDT

Date for pricing and exchange rate

VBKD

PRSDT

WAKTION

Action

VBKD

WAKTION

KAPPL

Application

KOMV

KAPPL

KHERK

Condition origin

KOMV

KHERK

KINAK

Condition is inactive

KOMV

KINAK

KNTYP

Condition type: Freight, tax, basic price = KOMV

KNTYP

revenue, price, retail value


KOAID

Condition class

KOMV

KOAID

KSCHL

Condition type

KOMV

KSCHL

KSTAT

Condition is statistical

KOMV

KSTAT

KVARC

Condition for configuration

KOMV

KVARC

STUNR

Level number

KOMV

STUNR

VARCOND

Variant condition

KOMV

VARCOND

KWERT

Condition value

KOMV

KWERT

ZAEHK

Condition Count

KOMV

ZAEHK

WAERK_VBAK

Currency of sales and distribution


document

VBAK

WAERK

SPARA

Division order header

VBAK

SPARA

VGTYP_AK

Sales and distribution document type of


reference document in the order header

VBAK

VGTYP

PS_POSID

Work breakdown structure element (PSP Field is determined

PS_POSID

element)
PERIV

Fiscal year variant

T001

PERIV

Features of the Extractor


The key figures KWMENG, ZIEME and ZMENG are not suitable for reporting in BW. They may only be used for calculation purposes because these fields
represent key figures on the item level.

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 9 of 31

There is a 1:n relation between items and conditions which could result in the key figures in the query having multiple values. For calculation purposes,
however, it is necessary that these fields be added to the extraction structure.
During reorganization, this structure is formed below the order data (application 11) in the table MC11VA0KONSETUP.
This extractor is used to extract item conditions. Header conditions are not extracted.
Due to the increased data volume, loss in performance can occur, especially during reorganization. This can also affect the LIS update and the reorganization
of LIS structures.
During reorganization of the order conditions, you should temporarily deactivate the other DataSources for application 11. See SAP Note 602260 for general
procedures for reorganization.
The recommended update method is queued delta. The unserialized V3 update is offered as a selection in the Logistic Customizing Cockpit, but it is not
suitable for extracting changes in the correct order. Thus it should never be selected.

1.4 Extraction SD Sales: Document Schedule Line


DataSource Transactional Data: 2LIS_11_VASCL

The structure Extraction SD Sales: Document Schedule Line is used to extract schedule line information from SD orders and quotations (but not requests) to
a BI system.

Technical Data
Application Component

SD Sales (BW-BCT_SD-SLS)

Available as of Release

SAP R/3 4.0

Shipment

PlugIn 2000_1

Content Versions

There are no content versions

RemoteCube-Capable

No

Delta-Capable

Yes

Extraction from Archives

Yes

Verifiable

No

Data Modeling
Delta Update

Note
The delta update is supported using the delta method ABR. Note that when a change is made to the sales document, a delta update occurs only if one or
more fields in the extraction structure are affected by the change. For more information, see SAP note 576886.
Fields of Origin for the Extract Structure
Fields in the Extract Structure

Description of the Field in the Extract

Table of Origin

Field in the Table of Origin

Structure
ROCANCEL

Indicator: Cancellation of the data record

ABGRU

Reason for rejection for quotations and


orders

VBAP

ABGRU

ABSTA

Rejection status of sales document item

VBUP

ABSTA

AEDAT

Last date on which object was changed

VBAP

AEDAT

ANGDT

Quotation/request valid from

VBAK

ANGDT

AUART

Sales document type

VBAK

AUART

AUGRU

Order reason (reason for transaction)

VBAK

AUGRU

AWAHR

Sales probability for item

VBAP

AWAHR

BMENG

Confirmed quantity

VBEP

BMENG

BNDDT

Binding period of quotation for service

VBAK

BNDDT

performance (valid to)


BUKRS

Company code

VBAK

BUKRS

BZIRK

Sales district

VBKD

BZIRK

CHARG

Batch number

VBAP

CHARG

CMENG

Corrected quantity in sales units

VBEP

CMENG

CMKUA

Exchange rate for credit data on

VBAP

CMKUA

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 10 of 31

requested delivery date


EAN11

European article number (EAN)

VBAP

EAN11

EDATU

Schedule line date

VBEP

EDATU

ERDAT

Date on which record was added

VBAP

ERDAT

ERNAM

Name of person who added the object

VBAP

ERNAM

ERZET

Time of entry

VBAP

ERZET

ETENR

Item category of schedule line

VBEP

ETENR

ETTYP

Schedule line category

VBEP

ETTYP

FAKSK

Billing type block sales and distribution

VBAK

FAKSK

document
FAKSP

Billing block item

VBAP

FAKSP

FBUDA

Date of services rendered

VBKD

FBUDA

FKDAT

Billing date for billing index and print

VBKD

FKDAT

GEWEI

Weight unit

VBAP

GEWEI

HWAER

Local currency

VBAK

HWAER

INCO1

Incoterms 1

VBKD

INCO1

INCO2

Incoterms 2

VBKD

INCO2

KDGRP

Customer group

VBKD

KDGRP

KMEIN

Condition unit

VBAP

KMEIN

KPEIN

Condition pricing unit

VBAP

KPEIN

KTGRD

Customer account assignment group

VBKD

KTGRD

KUNNR

Sold-to party

VBAK

KUNNR

KURSK

Pricing exchange rate

VBKD

KURSK

KURSK_DAT

Conversion date

VBKD

PRSDT

KURST

Exchange rate type

VBAK

KURST

KVGR1

Customer group 1

VBAK

KVGR1

KVGR2

Customer group 2

VBAK

KVGR2

KVGR3

Customer group 3

VBAK

KVGR3

KVGR4

Customer group 4

VBAK

KVGR4

KVGR5

Customer group 5

VBAK

KVGR5

LDDAT

Loading date

VBEP

LDDAT

LGORT

Storage location

VBAP

LGORT

LIFSK

Delivery note block document header

VBAK

LIFSK

LIFSP

Delivery block schedule line

VBEP

LIFSP

LMENG

Requirement quantity for materials

VBEP

LMENG

management in stockkeeping units


MATKL

Material group

VBAP

MATKL

MATNR

Material number

VBAP

MATNR

MATWA

Material entered

VBAP

MATWA

MBDAT

Material availability date

VBEP

MBDAT

MCEX_APCAMPAIGN

Campaign of referred sales order item for VBKD


BW extraction

CAMPAIGN

MEINS

Base unit of measure

VBEP

MEINS

MVGR1

Material group 1

VBAP

MVGR1

MVGR2

Material group 2

VBAP

MVGR2

MVGR3

Material group 3

VBAP

MVGR3

MVGR4

Material group 4

VBAP

MVGR4

MVGR5

Material group 5

VBAP

MVGR5

NETPR

Net price

VBAP

NETPR

PABLA

Unloading point for ship-to party

VBAP

PABLA

PERIV

Fiscal year variant

T001

PERIV

PKUNRE

Bill-to-party

VBAP

PKUNRE

PKUNRG

Payer

VBAP

PKUNRG

PKUNWE

Ship-to Party

VBAP

PKUNWE

POSNR

Item number of sales document

VBUP

POSNR

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 11 of 31

POSNR

VBUP

POSNR

PRODH

Product hierarchy

VBAP

PRODH

PRSDT

Date for pricing and exchange rate

VBKD

PRSDT

PS_POSID

Work breakdown structure element (WBS VBAP/PRPS

PS_PSP_PNR/POSID

element)
PSPDNR

Forwarding agent

VBAP

PSPDNR

PSTYV

Item category sales and distribution

VBAP

PSTYV

document
PVRTNR

Sales representative

VBAP

PVRTNR

ROUTE

Route

VBAP

ROUTE

SPARA

Division order header

VBAK

SPART

SPART

Division

VBAP

SPART

STADAT

Statistics date

VBAP

STADAT

STCUR

Exchange rate for statistics (exchange


rate upon creation)

VBAP

STCUR

STWAE

Statistics currency

VBAK

STWAE

SUGRD

Reason for material substitution

VBAP

SUGRD

TDDAT

Transportation planning date

VBEP

TDDAT

UMVKN

Denominator for conversion of sales

VBAP

UMVKN

quantity into SKU


UMVKZ

Numerator for conversion of sales


quantity into SKU

VBAP

UMVKZ

UMZIN

Denominator for conversion factor of


target quantity to storage quantity

VBAP

UMZIN

UMZIZ

Numerator for conversion factor of target VBAP

UZIZ

quantity to storage quantity


UVALL

Incompleteness status of general item

VBUP

UVALL

UVFAK

Incompleteness status of item in relation

VBUP

UVFAK

to billing document
UVPRS

Item incomplete in relation to pricing

VBUP

UVPRS

UVVLK

Incompleteness status of item in relation

VBUP

UVVLK

VBELN

Sales and distribution document number VBUK

VBELN

VBTYP

Sales document category

VBAK

VBTYP

VDATU

Update date for statistics update

VBAP

VDATU

VGTYP

Preceding sales document category

VBAP

VGTYP

VGTYP_AK

Sales document category of reference

VBAK

VGTYP

to delivery

document in the order header


VKBUR

Sales office

VBAK

VKBUR

VKGRP

Sales group

VBAK

VKGRP

VKORG

Sales organization

VBAK

VKORG

VOLEH

Volume unit

VBAP

VOLEH

VRKME

Sales unit

VBEP

VRKME

VSTEL

Shipping point/goods receiving point

VBAP

VSTEL

VTWEG

Distribution channel

VBAK

VTWEG

WADAT

Goods issue date

VBEP

WADAT

WAERK

Currency of sales and distribution

VBAP

WAERK

document
WAERK_VBAK

Currency of sales and distribution


document

VBAK

WAERK

WERKS

Plant

VBAP

WERKS

WLDATBE

Requested delivery date in confirmed

VBEP

WLDATBE

schedule lines
WMENG

Order quantity for customer in sales units VBEP

WMENG

ZIEME

Target quantity unit of measure

ZIEME

VBAP

> PI 20004.1
APOPLANNED

Planning in APO

FACELOC

Customer-facing location

FLOCTYPE

Type of customer-facing location

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 12 of 31

EXECLOC

Executing location

ELOCTYPE

Type of executing location

LOGSYS

Logical system

VWPOS

Item usage

STOCKLOC

First stockholding location

SLOCTYPE

Type of first stockholding location

Extractor Logic
Determination of Update Date for Statistics Update (VDATU):
The update date for the statistics update is filled in the delta update with the local date of the user (SY-DATLO).
In reorganization, VDATU is filled with the creation date of the SD document (XVBAP-ERDAT).
ROCANCEL - Cancellation of the data record
This field can have the following values:
Blank New data record or after image
X Cancellation of data record or before image
R Deletion of data record

1.5 Extraction SD Order Header Status


Technical name: Name: 2LIS_11_VASTH

Technical Data
Type of DataSource

Transaction data

Application Component

SD Sales (BW-BCT-SD)

Available from OLTP Release

SAP R/3 Enterprise Core 4.70 (SAP_APPL 470)

Available from Plug-In Release

2002.1

RemoteCube Compatibility

No

Use
The structure Extraction SD Order Header Status helps extract essential header status fields from the sales order consistently to an SAP BW system.

Delta Update
A Delta update is supported.

Fields of Origin in the Extract Structure


Field in Extract Structure

Description of Field in the Extract


Structure

Table of Origin

Field in Table of Origin

ROCANCEL

Indicator: Cancellation of data record

BESTK

Confirmed status

VBUK

BESTK

FKSAK

Billing status of sales order-related


billing documents

VBUK

FKSAK

FKSTK

Billing status

VBUK

FKSTK

GBSTK

Overall processing status of sales


document

VBUK

GBSTK

LFGSK

Overall delivery status of all items

VBUK

LFGSK

LFSTK

Delivery status

VBUK

LFSTK

VBELN

Sales document number

VBUK

VBELN

VBTYP

Sales document category

VBUK

VBTYP

1.6 Extraction SD Order Item Status


PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 13 of 31

Technical Name:
2LIS_11_VASTI

Technical Data
Type of DataSource

Transaction data

Application Component

SD Sales (BW-BCT-SD)

Available from OLTP Release

SAP R/3 Enterprise Core 4.70 (SAP_APPL 470)

Available from Plug-In Release

2002.1

RemoteCube Compatibility

No

Use
The structure Extraction SD Order Item Status helps extract essential item status fields from the sales order consistently to an SAP BW system.

Delta Update
A Delta update is supported.

Fields of Origin in the Extract Structure


Field in Extract Structure

Description of Field in the Extract


Structure

Table of Origin

Field in Table of Origin

ROCANCEL

Indicator: Cancellation of data record

BESTA
FKSAA

Confirmed status of document item

VBUP

BESTA

Billing status of sales order-related


billing documents

VBUP

FKSAA

FKSTA

Billing status of delivery-related billing VBUP


documents

FKSTA

GBSTA

Overall processing status of sales


document item

VBUP

GBSTA

LFGSA

Overall delivery status of item

VBUP

LFGSA

LFSTA

Delivery status

VBUP

LFSTA

POSNR

Item number of sales document

VBUP

POSNR

VBELN

Sales document number

VBUP

VBELN

VBUK_VBTYP

Sales document category

VBUK

VBTYP

1.7 Extraction SD Sales: Document Item Billing


DataSource Transactional Data: 2LIS_11_V_ITM

The structure Extraction SD Sales: Document Item Billing is used to extract open sales order values from SD order items to a BI system.

Technical Data
Application Component

SD Sales (BW-BCT-SD-SLS)

Available as of Release

SAP R/3 4.0

Shipment

PlugIn 2000_1

Content Versions

There are no content versions

RemoteCube-Capable

No

Delta-Capable

Yes

Extraction from Archives

Yes

Verifiable

No

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 14 of 31

Data Modeling
Delta Update

Note
The delta update is supported using the delta method ABR. Note that when a change is made to the sales document, a delta update occurs only if one or
more fields in the extraction structure are affected by the change. You can find further information in SAP Note 576886.
Fields of Origin for the Extract Structure
Fields in the Extract Structure

Description of the Field in the Extract


Structure

Table of Origin

ROCANCEL

Indicator: Cancellation of the data record Table of origin

Field of origin

ABGRU

Reason for rejection for quotations and


orders

VBAP

ABGRU

ABSTA

Rejection status of sales document item

VBUP

ABSTA

ANZOAUPO

Number of open order items

BUKRS

Company code

VBAK

BUKRS

BZIRK

Sales district

VBKD

BZIRK

CHARG

Batch number

VBAP

CHARG

EAN11

European article number (EAN)

VBAP

EAN11

ERDAT

Date on which record was added

VBAP

ERDAT

FAKSK

Billing type block sales and distribution


document

VBAK

FAKSK

FAKSP

Billing block item

VBAP

FAKSP

HWAER

Local currency

VBAK

HWAER

INCO1

Incoterms 1

VBKD

INCO1

INCO2

Incoterms 2

VBKD

INCO2

KDGRP

Customer group

VBKD

KDGRP

KUNNR

Sold-to party

VBAK

KUNNR

KURSK

Pricing exchange rate

VBKD

KURSK

KURSK_DAT

Translation date

VBKD

KURSK_DAT

KURST

Exchange rate type

VBAK

KURST

KVGR1

Customer group 1

VBAK

KVGR1

KVGR2

Customer group 2

VBAK

KVGR2

KVGR3

Customer group 3

VBAK

KVGR3

KVGR4

Customer group 4

VBAK

KVGR4

KVGR5

Customer group 5

VBAK

KVGR5

LFIMG_AVME

Actual delivered quantity in sales units

LIFSK

Delivery note block document header

VBAK

LIFSK

MATKL

Merchandise category

VBAP

MATKL

MATNR

Material number

VBAP

MATNR

MATWA

Material entered

VBAP

MATWA

MCBW_LFWRT

BW: Delivery order value

MCBW_NETPR_AVKM

BW: Net price of order item sales units

MCEX_APCAMPAIGN

Campaign of referred sales order item for VBKD


BI extraction

CAMPAIGN

MEINS

Base unit

VBAP

MEINS

MVGR1

Material group 1

VBAP

MVGR1

MVGR2

Material group 2

VBAP

MVGR2

MVGR3

Material group 3

VBAP

MVGR3

MVGR4

Material group 4

VBAP

MVGR4

MVGR5

Material group 5

VBAP

MVGR5

OAUME

Open order quantity

OAUWE

Open net sales order value

PERIV

Fiscal year variant

T001

PERIV

PKUNRE

Bill-to party

VBAP

PKUNRE

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Field in the Table of Origin

Page 15 of 31

PKUNRG

Payer

VBAP

PKUNRG

PKUNWE

Ship-to party

VBAP

PKUNWE

POSNR

Item number of the sales and distribution VBUP


document

POSNR

PRODH

Product hierarchy

PRODH

PS_POSID

Work breakdown structure element (WBS VBAP/PRPS


element)

PS_PSP_PNR/POSID

PSPDNR

Forwarding agent

VBAP

PSPDNR

PVRTNR

Sales representative

VBAP

PVRTNR

ROUTE

Route

VBAP

ROUTE

SHKZG

Return item

VBAP

SHKZG

SPARA

Division order header

VBAK

SPART

SPART

Division

VBAP

SPART

STADAT

Statistics date

VBAP

STADAT

STCUR

Exchange rate for statistics (exchange

VBAP

STCUR

VBAP

rate upon creation)


STWAE

Statistics currency

VBAK

STWAE

UMVKN

Denominator for conversion of sales


quantity into SKU

VBAP

UMVKN

UMVKZ

Numerator for conversion of sales


quantity into SKU

VBAP

UMVKZ

VBELN

Sales and distribution document number VBUK

VBELN

VBTYP

Sales document category

VBAK

VBTYP

VKBUR

Sales office

VBAK

VKBUR

VKGRP

Sales group

VBAK

VKGRP

VKORG

Sales organization

VBAK

VKORG

VRKME

Sales unit

VBAP

VRKME

VSTEL

Shipping point/goods receiving point

VBAP

VSTEL

VTWEG

Distribution channel

VBAK

VTWEG

WAERK

Currency of sales and distribution

VBAP

WAERK

document
WAKTION

Action

VBKD

WAKTION

WERKS

Plant

VBAP

WERKS

Extractor Logic
The delivery relevance of the order item is crucial for extraction with the DataSource 2LIS_11_V_ITM. If the order item is not delivery-relevant, no data is
extracted.
Fields that are calculated at runtime are not saved on the database, because their value is influenced by order- and delivery processing. This affects the
two key figures Open Order Quantity (OAUME) and Open Order Value (OAUWE) in particular, as well as Actual Delivered Quantity (LFIMG_AVME) .
The key figures Open Order Quantity and Open Order Value are established when creating an order and reduced by the delivery of order items. The
key figure Actual Delivered Quantity is established by the creation of a delivery.

Example
With the creation of an order item, an open order quantity of 10 pieces is established. The item is then delivered, with a partial delivery of 6 pieces.
The open order quantity is reduced by 6 pieces. An open order quantity of 4 pieces remains. The extractor delivers the following records:
1. Creation of order item:
ROCANCEL

VBELN

POSNR

OAUME

LFIMG_AVME

4711

10

10

10

VBELN

POSNR

OAUME

LFIMG_AVME

4711

10

-6

2. Delivery of order item:


ROCANCEL

After billing the values, an open order quantity of 4 pieces remains in the BI system. The update type Addition therefore determines the difference in
billing between the order and the delivery for these key figures in DataStore objects. You can find further information in SAP Note 401919.
ROCANCEL - Cancellation of the data record
Blank - New data record or after image
X - Cancellation of data record or before image
Before image = State before changes were made to the data record
After image = State after changes were made to the data record
Changes in the order and delivery are mapped by before- and after images.
The field ROCANCEL accepts the value X for before images and the value Blank for after images. The key figures of the before image are sent with
reversed (as a rule, negative) signs.

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 16 of 31

Example
In the delivery, the delivered quantity is increased to 7 pieces:
ROCANCEL

VBELN

POSNR

OAUME

LFIMG_AVME

4711

10

-4

-6

4711

10

The open order quantity of the order item is now 3 pieces.


For technical reasons, ROCANCEL =R cannot be sent in the case of billing extractors such as the DataSource 2LIS_11_V_ITM for deletion records
(refer to SAP Note 426731). In the case of a deletion, an after image with a reversed sign is sent instead. This means that a created order item is not
deleted from the DataStore, but rather the values of the key figures via billing are set to zero. You can find further information about the update of
DataSource 2LIS_11_V_ITM in DataStore objects in SAP Note 440679.

Example
The delivery created above is deleted. The deletion of the delivery means that the open order quantity is completely re-established.
ROCANCEL

VBELN

POSNR

OAUME

LFIMG_AVME

4711

10

-7

The following values now arise in the DataStore object via billing:
DataStore Object

VBELN

POSNR

OAUME

LFIMG_AVME

4711

10

<- Status before deletion


of the delivery

4711

10

10

<- Status after deletion of


the delivery

Note
If you call transaction RSA7, you can find records there that show the value U in the field ROCANCEL. These values are required for the
conversion of deletion records in after images with reversed signs via the S-API. The values V and W also exist, and are likewise only used
internally. These values should never occur in the BI system. This only happens if you have set all the key figures of the DataSource to nonreversible in transaction RSA6. These settings are not correct. You can find further information about the attributes of field ROCANCEL in SAP Note
757487.
If the order is also deleted, the following screen appears:
ROCANCEL

VBELN

POSNR

OAUME

LFIGM_AVME

4711

10

-10

The following values arise in the DataStore object via billing:


DataStore Object

VBELN

POSNR

OAUME

LFIMG_AVME

4711

10

10

<- Status before deletion


of the order

4711

10

<- Status after deletion of


the order

The key figures of the item receive the value 0.


In a summarized form, the data in the Persistent Staging Area (PSA) for the order item appears as follows:
ROCANCEL

VBELN

POSNR

OAUME

LFIMG_AVME

4711

10

10

Create order item

4711

10

-6

Create delivery

4711

10

-4

-6

Change delivery before

4711

10

image
Change delivery after
image
4711

10

-7

Delete delivery

4711

10

-10

Delete order item

Note
Note that only after images are extracted when creating and deleting the order or delivery. These data records deliver the values by which the key
figure was changed - not, as perhaps expected, the last state of the key figure. In contrast to this, when changing the order or the delivery, both
before- and after images are sent, which reflect the state of the order before and after the change. This enables you to identify changes to the
delivery.
In contrast to DataSource 2LIS_11_VAITM, enhancements to the DataSource 2LIS_11_V_ITM are heavily restricted. Not all fields of the communication
structures MCVBUK, MCVBUP, MCVBAK, MCVBAP, and MCVBKD are offered for enhancement in the Logistic Customizing Cockpit (LBWE). The
reason for this is that the DataSource is updated for events VA (order) and VC (delivery). While all the information for filling the fields for event VA is
available, not all necessary information is available in the extraction from the delivery (event VC). This would lead to the relevant fields for event VC not
being filled.

1.8 Extraction SD Sales: Document Schedule Line Billing


PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 17 of 31

DataSource Transactional Data: 2LIS_11_V_SCL

The structure Extraction SD Sales: Document Schedule Line Billing is used to extract open quantities to be delivered from SD order schedule lines to a BI
system.

Technical Data
Application Component

SD Sales (BW-BCT-SD-SLS)

Available as of Release

SAP R/3 4.0

Shipment

PlugIn 2000_1

Content Versions

There are no content versions

RemoteCube-Capable

No

Delta-Capable

Yes

Extraction from Archives

Yes

Verifiable

No

Data Modeling
Delta Update

Note
The delta update is supported using the delta method ABR. Note that when a change is made to the sales document, a delta update occurs only if one or
more fields in the extraction structure are affected by the change. You can find further information in SAP Note 576886.
Fields of Origin for the Extract Structure
Fields in the Extract Structure

Description of the Field in the Extract


Structure

Table of Origin

Field in the Table of Origin

ROCANEL

Indicator: Cancellation of the data record

ABSTA

Rejection status

B_DELAY

BW extraction SD/LE: Confirmation delay

VBUP

ABSTA

BMENG
BUKRS

Confirmed quantity

VBEP

BMENG

Company code

VBAK

BUKRS

BZIRK

Sales district

VBKD

BZIRK

CHARG

Batch number

VBAP

CHARG

EAN11

European article number (EAN)

VBAP

EAN11

EDATU

Schedule line date

VBEP

EDATU

ERDAT

Date on which record was added

VBAP

ERDAT

ETENR

Item category of schedule line

VBEP

ETENR

ETTYP

Schedule line category

VBEP

ETTYP

FAKSK

Billing type block

VBAK

FAKSK

FAKSP

Billing block item

VBAP

FAKSP

HWAER

Local currency

VBAK

HWAER

INCO1

Incoterms 1

VBKD

INCO1

INCO2

Incoterms 2

VBKD

INCO2

KDGRP

Customer group

VBKD

KDGRP

KUNNR

Sold-to party

VBAK

KUNNR

KURSK

Pricing exchange rate

VBKD

KURSK

KURST

Exchange rate type

VBAK

KURST

KVGR1

Customer group 1

VBAK

KVGR1

KVGR2

Customer group 2

VBAK

KVGR2

KVGR3

Customer group 3

VBAK

KVGR3

KVGR4

Customer group 4

VBAK

KVGR4

KVGR5

Customer group 5

VBAK

KVGR5

LDDAT

Loading date

VBEP

LDDAT

LIFSK

Delivery note block document header

VBAK

LIFSK

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 18 of 31

LIFSP

Delivery block schedule line

VBEP

LIFSP

MATKL

Merchandise category

VBAP

MATKL

MATNR

Material number

VBAP

MATNR

MBDAT

Material availability date

VBEP

MBDAT

MCBW_BWERT

BW: Value of the confirmed quantity

MCBW_NETPR_AVKM

BW: Net price of order item sales units

MCBW_OLFWRT

BW: Open sales order value for schedule


line

MCBW_VSWRT

BW: Delivery value for schedule line

MCBW_WWERT

BW: Value of requested quantity

MCEX_APCAMPAIGN

Campaign of referred sales order item for VBKD

CAMPAIGN

BW extraction
MEINS

Base unit

VBAP

MEINS

MVGR1

Material group 1

VBAP

MVGR1

MVGR2

Material group 2

VBAP

MVGR2

MVGR3

Material group 3

VBAP

MVGR3

MVGR4

Material group 4

VBAP

MVGR4

MVGR5

Material group 5

VBAP

MVGR5

OLFMNG

Open quantity to be delivered in sales


units

PERIV

Fiscal year variant

T001

PERIV

PKUNRE

Bill-to party

VBAP

PKUNRE

PKUNRG

Payer

VBAP

PKUNRG

PKUNWE

Ship-to party

VBAP

PKUNWE

POSNR

Item number of the sales and distribution VBUP


document

POSNR

PRODH

Product hierarchy

PRODH

PS_POSID

Work breakdown structure element (WBS VBAP/PRPS


element)

PS_PSP_PNR/POSID

PSPDNR

Forwarding agent

VBAP

PSPDNR

PVRTNR

Sales representative

VBAP

PVRTNR

ROUTE

Route

VBAP

ROUTE

SHKZG

Return item

VBAP

SHKZG

SPARA

Division order header

VBAK

SPART

SPART

Division

VBAP

SPART

STADAT

Statistics date

VBAP

STADAT

STCUR

Exchange rate for statistics (exchange


rate upon creation)

VBAP

STCUR

STWAE

Statistics currency

VBAK

STWAE

TDDAT

Transportation planning date

VBEP

TDDAT

UMVKN

Denominator for conversion of sales


quantity into SKU

VBAP

UMVKN

UMVKZ

Numerator for conversion of sales


quantity into SKU

VBAP

UMVKZ

VBELN

Sales and distribution document number VBUK

VBELN

VBTYP

Sales document category

VBAK

VBTYP

VKBUR

Sales office

VBAK

VKBUR

VKGRP

Sales group

VBAK

VKGRP

VKORG

Sales organization

VBAK

VKORG

VRKME

Sales unit

VBEP

VRKME

VSMNG

Delivered quantity in sales units

VTWEG

Distribution channel

VBAK

VTWEG

WADAT

Goods issue date

VBEP

WADAT

WAERK

Currency of sales and distribution


document

VBAP

WAERK

WERKS

Plant

VBAP

WERKS

WLDATBE

Requested delivery date in confirmed

VBEP

WLDATBE

VBAP

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 19 of 31

schedule lines
Order quantity for customer in sales units VBEP

WMENG

WMENG

> PI 2004.1
Planning in APO

APOPLANNED

Extractor Logic
The delivery relevance of the order item is crucial for extraction with the DataSource 2LIS_11_V_SCL. If the order item is not delivery-relevant, no data
is extracted.
Fields that are calculated at runtime are not saved on the database, because their value is influenced by order- and delivery processing.
This particularly affects the two key figures Open Quantity to Be Delivered (field OLFMNG) and the Shipped Quantity (field VSMNG).
The key figures are established when creating an order and change when the order items are delivered.

Example
With the creation of an order schedule line, an open quantity to be delivered of 10 pieces is established. The schedule line is then delivered, with a
partial delivery of 6 pieces. The open quantity to be delivered is reduced by 6 pieces. An open quantity to be delivered of 4 pieces remains.
The extractor delivers the following records:
1. Creation of order item:
ROCANCEL

VBELN

POSNR

ETENR

OLFMNG

VSMNG

4711

10

10

VBELN

POSNR

ETENR

OLFMNG

VSMNG

4711

10

-6

2. Supply of the order schedule line:


ROCANCEL

After billing the values, an open quantity to be delivered of 4 pieces remains in the BI system.
The update type Addition therefore determines the difference in billing between the order and the delivery for these key figures in DataStore objects.
More information is available in SAP Note 401919.
ROCANCEL - Cancellation of the data record
This field can have the following values:
Blank - new data record or after image
X - Cancellation of data record or before image
Before image = State before changes were made to the data record
After image = State after changes were made to the data record
Changes in the order and delivery are mapped by before- and after images.
The field ROCANCEL accepts the value X for before images and the value Blank for after images. The key figures of the before image are sent with
reversed (as a rule, negative) signs.

Example
In the delivery, the delivered quantity is increased to 7 pieces:
ROCANCEL

VBELN

POSNR

ETENR

OLFMNG

VSMNG

4711

10

-4

-6

4711

10

The order schedule line's open quantity to be delivered is now 3 pieces.


For technical reasons, ROCANCEL =R cannot be sent in the case of billing extractors such as the DataSource 2LIS_11_V_SCL for deletion records
(refer to SAP Note 426731). In the case of a deletion, an after image with a reversed sign is sent instead. This means that an existing order schedule
line is not deleted from the DataStore object, but rather the values of the key figures via billing are set to zero. You can find further information about the
update of DataSource 2LIS_11_V_ITM in DataStore objects in SAP Note 440679.

Example
The delivery created above is deleted. The deletion of the delivery means that the open quantity to be delivered is completely re-established.
ROCANCEL

VBELN

POSNR

ETENR

OLFMNG

VSMNG

4711

10

-7

The following values arise in the DataStore object via billing:


DataStore Object

VBELN

POSNR

ETENR

OLFMNG

VSMNG

4711

10

7 <- Status before

4711

10

10

deletion of the delivery


0

Note
If you call transaction RSA7, you can find records that show the value U in the field ROCANCEL. These values are required for the conversion of
deletion records in after images with reversed signs via the S-API. The values V and W also exist, and are likewise only used internally. These
values should never occur in the BI system. This only happens if you have set all the key figures of the DataSource to non-reversible in transaction
RSA6. These settings are not correct. You can find further information about the attributes of field ROCANCEL in SAP Note 757487.
If the order is also deleted, the following screen appears:
ROCANCEL

VBELN

POSNR

ETENR

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

OLFMNG

VSMNG

Page 20 of 31

4711

10

-10

The following values arise in the DataStore object via billing:


DataStore Object

VBELN

POSNR

ETENR

OLFMNG

VSMNG

4711

10

10

7 <- Status before


deletion of the order

4711

10

0 <- Status after deletion


of the order

The key figures of the schedule line receive the value 0.


In a summarized form, the data in the Persistent Staging Area (PSA) for the order schedule line appears as follows:
ROCANCEL

VBELN

POSNR

ETENR

OLFMNG

VSMNG

4711

10

10

0 Create order

4711

10

-6

6 Create delivery

4711

10

-4

-6 Change delivery
before image

4711

10

7 Change delivery after


image

4711

10

-7 Delete delivery

4711

10

-10

0 Delete order

Note
Note that only after images are extracted when creating and deleting the order or delivery. These data records deliver the values by which the key
figure was changed - not, as perhaps expected, the last state of the key figure.
In contrast to this, when changing the order or the delivery, both before- and after images are sent, which reflect the state of the order before and
after the change. This enables you to identify changes to the delivery.
Extensibility of the DataSource
In contrast to DataSource 2LIS_11_VASCL, enhancements to the DataSource 2LIS_11_V_SCL are heavily restricted. Not all fields of the
communication structures MCVBUK, MCVBUP, MCVBAK, MCVBAP, MCVBEP, and MCVBKD are offered for enhancement in the Logistic Customizing
Cockpit (LBWE).
The reason for this is that the DataSource is updated for events VA (order) and VC (delivery). While all the information for filling the fields for event VA is
available, not all necessary information is available in the extraction from the delivery (event VC). This would lead to the relevant fields for event VC not
being filled.

1.9 Extraction SD Sales: Order Delivery


Technical Name: 2LIS_11_V_SSL

Technical Data
Type of DataSource

Transaction data

Application Component

SD Sales (BW-BCT-SD)

Available from OLTP Release

4.0

Available from Plug-In Release

2002.1

RemoteCube Compatibility

No

Use
Use the structure Extraction SD Sales: Order Delivery to extract essential information about the delivery of order schedule lines to an SAP BW system.

Delta Update
A Delta update is supported.

Fields of Origin in the Extract Structure


Field in Extract Structure

Description of Field in the Extract


Structure

Table of Origin

VBELN

Sales document number

VBAP

POSNR

Item number of sales document

VBAP

ETENR

Schedule line number

VBEP

VBELN_VL

Delivery

LIPS

POSNR_VL

Delivery item

LIPS

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Field in Table of Origin

Page 21 of 31

ROCANCEL

Cancellation of data record

WMENG

Requested quantity of order schedule


line in Sales ME

VBEP

Definition

Rquested order quantity of a single


schedule line in the extract structure
MC11V_0SSL.
Use
Because a schedule line in the extract
structure MC11V_0SSL can be assigned
to several delivery items, you only fill in
the requested quantity once for the first
data record in the schedule line during
an extraction process.

BMENG

Confirmed quantity of an order


schedule line in Sales ME

VBEP

Definition

Confirmed quantity of an order schedule


line in the extract structure
MC11V_0SSL.
Use
Because a schedule line in the extract
structure MC11V_0SSL can be assigned
to several delivery items, you only fill in
the requested quantity once for the first
data record in the schedule line during
an extraction process.

VSMNG

Delivered quantity in Sales ME of


order schedule line

WVBEP
Dynamic part of the schedule lines

Definition

Share of the delivery quantity of a


delivery item assigned to a confirmed
schedule line in the extract structure
MC11V_0SSL.
Use
In this field, the quantities delivered for
an order item are assigned to the
confirmed quantities of the schedule line
for the order item. This assignment is
basically dynamic and is determined
anew with each extraction process.
There is no fixed assignment between
order schedule lines and order items.
The quantity shipped is therefore
basically displayed in the sales unit of
the order schedule line.
For individual conversion, the conversion
factors in the base unit of measure from
the order schedule line are available in
the extract structure as well.
An order schedule line with delivery
block is only assigned a quantity when
you are dealing with the last schedule
line for an item and the entire quantity of
available delivery items could not yet be
assigned.

VRKME

Sales unit

VBEP

LFGSA

Overall delivery status of item

VBUP

LFSTA

Delivery status

VBUP

WBSTA

Goods movement status

VBUP

MCEX_WBSTA_LOW

Smallest goods movement status of


an order item

Field is determined dynamically

Definition

This field contains the smallest goods


movement status of all delivery items of
an order item.
Use
The field is only used and filled in the
extract structure MC11V_0SSL
(DataSource 2LIS_11_V_SSL).
There, this status is determined for one
order item at a time, and is assigned to
all data records for the order item.
This status is basically empty for items
not yet completely delivered.
If an order item is controlled so that the
item is already completed with the first

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 22 of 31

partial delivery, then the lowest goods


issue status for the order item is not
empty, even if a delivery item cannot be
assigned to all schedule lines.

MCEX_W_LFDAT

Requested delivery date of an order


schedule line

Field is determined dynamically

Definition

This field contains the requested delivery


date of an order schedule line.
Use
The field is only used and filled in the
extract structure MC11V_0SSL
(DataSource 2LIS_11_V_SSL).
For schedule lines with a positive
requested quantity, the requested
delivery date is the schedule line date.
For schedule lines without a requested
quantity, the requested delivery date is
taken from the last available schedule
line with a positive requested quantity.

MCEX_W_LFUHR

Requested delivery time of an order


schedule line

Field is determined dynamically

Definition

This field contains the requested delivery


time of an order schedule line.
Use
The field is only used and filled in the
extract structure MC11V_0SSL
(DataSource 2LIS_11_V_SSL).
For schedule lines with a positive
requested quantity, the requested
delivery time is the arrival time of the
schedule line.
For schedule lines without a requested
quantity, the requested delivery time is
taken from the arrival time of the last
available schedule line with positive
requested quantity.

MCEX_B_LFDAT

Confirmed delivery date

Field is determined dynamically

Definition

This field contains the confirmed delivery


date of an order schedule line.
Use
The field is only used and filled in the
extract structure MC11V_0SSL
(DataSource 2LIS_11_V_SSL).
For schedule lines with a positive
confirmed quantity, the confirmed
delivery date is the schedule line date.
This date is basically not filled for
schedule lines without a confirmed
quantity.

MCEX_B_LFUHR

Confirmed delivery time

Field is determined dynamically

Definition

This field contains the confirmed delivery


time of an order schedule line.
Use
The field is only used and filled in the
extract structure MC11V_0SSL
(DataSource 2LIS_11_V_SSL).
For schedule lines with a positive
confirmed quantity, the confirmed
delivery time is the arrival time of the
schedule line.
This field is basically not filled for
schedule lines without a confirmed
quantity.

MCEX_B_WADAT

Planned goods issue date of a


confirmed schedule line

Field is determined dynamically

Definition

This field contains the planned goods


issue date of an order schedule line with
a confirmed quantity.
Use
The field is only used and filled in the

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 23 of 31

extract structure MC11V_0SSL


(DataSource 2LIS_11_V_SSL).
For schedule lines with a positive
confirmed quantity, the confirmed
planned goods issue date is the goods
issue date of the schedule line.
This date is basically not filled for
schedule lines without a confirmed
quantity.

MCEX_I_WADAT

Actual goods movement date of a


delivery

Field is determined dynamically

Definition

This field contains the actual goods


movement date of a delivery of an item
order.
Use
The field is only used in the extract
structure MC11V_0SSL (DataSource
2LIS_11_V_SSL).
There, this date is determined for one
delivery at a time, and is assigned to all
data records for this delivery.
In these data records, you are dealing
with confirmed quantities of order
schedule lines, which are assigned a
corresponding delivery item as delivery.
The date is only assigned if it was
entered in the associated delivery.

MCEX_I_WADATLATE

Last actual goods movement date of


an order item

Field is determined dynamically

Definition

This field contains the last actual goods


movement date of all delivery items of an
order item.
Use
The field is only used in the extract
structure MC11V_0SSL (DataSource
2LIS_11_V_SSL).
There, this date is determined for one
order item at a time, and is assigned to
all data records for the order item.
This date is basically empty for items not
yet completely delivered.
If an order item is completed delivered
but goods issue has not yet been posted
for all deliveries, then the field contains
the last goods movement date of all
deliveries already posted.
If an order item is controlled so that the
item is already completed with the first
partial delivery, then the last actual
goods movement date for the order item
is filled even if an delivery item cannot be
assigned to all schedule lines.

MCEX_I_LFDAT

Actual delivery date of a delivery

Field is determined dynamically

Definition

This field contains the actual delivery


date of a delivery of an item order.
Together with the actual delivery time,
the actual delivery date forms the point in
time when the delivered goods arrive at
the customer.
Use
The field is only used in the extract
structure MC11V_0SSL (DataSource
2LIS_11_V_SSL).
There, the time is calculated for one
delivery at a time from the actual goods
movement date, and is assigned to all
data records for this delivery.
In these data records, you are dealing
with confirmed quantities of order
schedule lines, which are assigned a
corresponding delivery item as delivery.
The date is calculated via the following
rules:
For every schedule line receiving the
delivery concerned, the deviation

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 24 of 31

between the confirmed goods movement


date and the actual goods movement
date is added to the confirmed delivery
date The actual delivery date is thereby
equated with the actual goods movement
date, if the calculated value were to get
smaller.
The actual delivery time is taken from the
confirmed delivery time of the schedule
line.
The latest actual delivery time-spot
calculated in this way is assigned to all
delivered schedule line quantities.
This time-spot is used if the actual
delivery date and actual delivery time are
created as of R/3-Release 4.6 via the
acknowledgement of receipt of goods.

MCEX_I_LFUHR

Actual delivery time of a delivery

Field is determined dynamically

Definition

This field contains the actual delivery


time of a delivery of an item order.
Together with the actual delivery date,
the time forms the point in time when the
delivered goods arrive at the customer.
Use
The field is only used in the extract
structure MC11V_0SSL (DataSource
2LIS_11_V_SSL).
There, the delivery time-spot is
determined for one delivery at a time,
and is assigned to all data records for
this delivery.
In these data records, you are dealing
with confirmed quantities of order
schedule lines, which are assigned a
corresponding delivery item as delivery.
For more information on determining
actual delivery time-spots, see Actual
Delivery Date.

MCEX_I_LFDATLATE

Last actual delivery date of an order


item

Field is determined dynamically

Definition

This field contains the last actual delivery


date of all delivery items of an order item.
Together with the actual delivery time,
this field forms the point in time when the
last delivery for an order item arrives at
the customer.
Use
The field is only used in the extract
structure MC11V_0SSL (DataSource
2LIS_11_V_SSL).
There, this date is determined for one
order item at a time, and is assigned to
all data records for the order item.
This field is basically empty for items not
yet completely delivered.
If an order item is completed delivered
but the goods issue has not yet been
posted for all deliveries, then the field
contains the last actual delivery date of
all deliveries already posted.
If an order item is controlled so that the
item is already completed with the first
partial delivery, then the last actual
delivery time-spot for the order item is
determined even if an delivery item
cannot be assigned to all schedule lines.

MCEX_I_LFUHRLATE

Last actual delivery time of an order


item

Field is determined dynamically

Definition

This field contains the last actual delivery


time of all delivery items of an order item.
Together with the actual delivery date,
this field forms the point in time when the
last delivery for an order item arrives at
the customer.
Use
The field is only used in the extract
structure MC11V_0SSL (DataSource

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 25 of 31

2LIS_11_V_SSL).
There, this date is determined for one
order item at a time, and is assigned to
all data records for the order item.
This field is basically empty for items not
yet completely delivered.
If an order item is completed delivered
but the goods issue has not yet been
posted for all deliveries, then the field
contains the last actual delivery time-spot
of all deliveries already posted.
If an order item is controlled so that the
item is already completed with the first
partial delivery, then the last actual
delivery time-spot for the order item is
determined even if an delivery item
cannot be assigned to all schedule lines.

LIFSP

Delivery block item

VBAP

MEINS

Base unit of measure

VBEP

UMVKN

Denominator for conversion of sales


unit into SKU.

VBEP

UMVKZ

Numerator for conversion of sales unit VBEP


into SKU.

VBTYP

Sales document category

VBEP_DELETED

Schedule line deleted

Field is determined dynamically

Definition

This indicator for DataSource


2LIS_11_V_SSL signals that the
respective schedule line for the current
document change was deleted.
Use
The field is only used and filled in the
extract structure MC11V_0SSL
(DataSource 2LIS_11_V_SSL).
There, this indicator is determined for
one order schedule line item at a time,
and is assigned to all data records for the
order schedule line.
Because the DataSource
2LIS_11_V_SSL basically does not
transfer any deletion information to the
SAP BW system, this indicator can be
used to delete the schedule line within
the start routine when you update an
ODS with Order Number, Item Number
and Schedule Line Number as key fields.
In such an update, the schedule line
usually remains in the SAP BW system
with blank indicators.

RECORD_DELETED

Order schedule line delivery deleted

Field is determined dynamically

Definition

This indicator for DataSource


2LIS_11_V_SSL signals that a unique
data record of the DataSource was
deleted during the current document
change.
A data record is uniquely determined via
the five key fields Order Number, Item
Number, Schedule Line Number,
Delivery Number and Delivery Item
Number.
Use
The field is only used and filled in the
extract structure MC11V_0SSL
(DataSource 2LIS_11_V_SSL).
There, this indicator is determined for
each combination of order schedule line
and delivery item, and is assigned to the
corresponding data record. Order
schedule lines not yet assigned a
delivery item are flagged with blank
delivery number and delivery item
number.
Because the DataSource
2LIS_11_V_SSL basically does not
transfer any deletion information to the
SAP BW system, this indicator can be

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 26 of 31

used to delete the corresponding data


record within the start routine when you
update an ODS with Order Number, Item
Number, Schedule Line Number,
Delivery Number and Delivery Item
Number as key fields.
In such an update, the corresponding
data record usually remains in the SAP
BW system with blank indicators.

Features of Extractor
A data record is uniquely determined via the five key fields Order Number, Item Number, Schedule Line Number, Delivery Number and Delivery Item
Number .
The transfer of Deltas from this extract structure occurs during document changes as well as delivery changes.
In reconstruction, this structure is set up under the order data (application 11) in the table MC11V_0SSLSETUP.
The data records for the extract structure contain requested schedule lines as well as confirmed schedule lines of the order items. If there are delivery
items for the order items, then the delivery quantities are assigned to the confirmed schedule lines.
If there are no deliveries available for a schedule line, then a data record is transferred to the schedule line in which the delivery number, delivery item
number and all further delivery-related data record is unfilled.
If several delivery items can be assigned to the schedule line, then several data records containing different delivery numbers, delivery item numbers and
the associated delivered quantity, are transferred to the schedule line.
On the other hand, if a delivery item delivers to more than one confirmed schedule line at the same time, then this results in several data records for the
same delivery item with different schedule line numbers. The delivery quantity is distributed across the schedule lines as shipped quantity.

Extraction of SD Billing Conditions


Technical name: 2LIS_13_VDKON

Technical Data
DataSource type

Transaction data

Application components

BW-BCT-SD-BIL

Available from OLTP release

4.0 B

Delivery with

PlugIn 2004_1

RemoteCube enabled

No

Delta enabled

Delta update is supported

Archivable

Yes

Verifiable

No

Prerequisites
Prerequisite for the use of the extractor is the R/3 core SAP Note 673964 or the corresponding support package.

Use
With the Extraction SD Billing Conditions structure, you can extract active condition lines that contribute to the pricing result of a billing item to a BW
system.

Delta Update
Delta update is supported.

Origin Fields of the Extraction Structure


Field in the Extraction Structure

Description of Field in the Extraction


Structure

Origin Table

ROCANCEL

Indicator: Cancellation of the data record

VBELN

Sales and distribution document number VBUK

VBELN

POSNR

Item number of the sales and distribution VBUK


document

POSNR

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Field in the Origin Table

Page 27 of 31

AEDAT

Date of last change

VBRK

AEDAT

BUKRS

Company code

VBRK

BUKRS

BZIRK

Sales district

VBRK

BZIRK

FKART

Billing type

VBRK

FKART

FKDAT

Billing date for billing index and print

VBRK

FKDAT

FKTYP

Billing type

VBRK

FKTYP

HWAER

Local currency

VBRK

HWAER

KDGRP

Customer group

VBRK

KDGRP

KUNAG

Sold-to party

VBRK

KUNAG

KUNRG

Payer

VBRK

KUNRG

KURRF

Exchange rate for FI postings

VBRK

KURRF

STWAE

Statistics currency

VBRK

STWAE

VBTYP

Sales and distribution documents

VBRK

VBTYP

VKORG

Sales organization

VBRK

VKORG

VTWEG

Distribution channel

VBRK

VTWEG

WAERK

Currency of sales and distribution


document

VBRK

WAERK

AKTNR

Action

VBRP

AKTNR

AUBEL

Sales and distribution document

VBRP

AUBEL

AUPOS

Sales and distribution document item

VBRP

AUPOS

BONUS

Bonus group

VBRP

BONUS

BWAPPLNM

Application components

VBRP

BWAPPLNM

BWVORG

SAP BW transaction key

VBRP

BWVORG

EAN11

European article number (EAN)

VBRP

EAN11

ERDAT

Date on which the record was added

VBRP

ERDAT

ERNAM

Name of the person who added the


object

VBRP

ERNAM

FBUDA

Date of services rendered

VBRP

FBUDA

FKIMG

Amount actually billed

VBRP

FKIMG

KORKS

Controlling area

VBRP

KORKS

KOSTL

Cost center

VBRP

KOSTL

KURSK

Exchange rate for pricing

VBRP

KURSK

KURSK_DAT

Translation date

VBRP

KURSK_DAT

KVGR1

Customer group 1

VBRP

KVGR1

KVGR2

Customer group 2

VBRP

KVGR2

KVGR3

Customer group 3

VBRP

KVGR3

KVGR4

Customer group 4

VBRP

KVGR4

KVGR5

Customer group 5

VBRP

KVGR5

MATKL

Merchandise category

VBRP

MATKL

MATNR

Material number

VBRP

MATNR

MATWA

Material entered

VBRP

MATWA

MVGR1

Material group 1

VBRP

MVGR1

MVGR2

Material group 2

VBRP

MVGR2

MVGR3

Material group 3

VBRP

MVGR3

MVGR4

Material group 4

VBRP

MVGR4

MVGR5

Material group 5

VBRP

MVGR5

PKUNRE

Bill-to party

VBRP

PKUNRE

PKUNWE

Ship-to party

VBRP

PKUNWE

POSAR

Item type

VBRP

POSAR

PRODH

Product hierarchy

VBRP

PRODH

PROVG

Commission group

VBRP

PROVG

PRSDT

Date for pricing and exchange rate

VBRP

PRSDT

PSPDNR

Forwarding agent

VBRP

PSPDNR

PSTYV

Item type sales and distribution


document

VBRP

PSTYV

PVRTNR

Sales representative

VBRP

PVRTNR

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 28 of 31

SPARA

Division order header

VBRP

PVRTNR

SPART

Division

VBRP

SPART

STADAT

Statistics date

VBRP

STADAT

VGBEL

Document number of the reference


document

VBRP

VGBEL

VGPOS

Item number of the reference business


item

VBRP

VGPOS

VKBUR

Sales office

VBRP

VKBUR

VKGRP

Sales group

VBRP

VKGRP

VRKME

Sales unit

VBRP

VRKME

KAPPL

Application

KOMV

KAPPL

KHERK

Condition origin

KOMV

KHERK

KINAK

Condition is inactive

KOMV

KINAK

KNTYP

Condition type: Freight, tax, basic price = KOMV


revenue, price, retail value

KNTYP

KOAID

Condition class

KOMV

KOAID

KSCHL

Condition type

KOMV

KSCHL

KSTAT

Condition is statistical

KOMV

KSTAT

KVARC

Condition for configuration

KOMV

KVARC

STUNR

Level number

KOMV

STUNR

VARCOND

Variant condition

KOMV

VARCOND

KWERT

Condition value

KOMV

KWERT

ZAEHK

Condition count

KOMV

ZAEHK

PS_POSID

Work breakdown structure element (PSP Field is determined


element)

PS_POSID

PERIV

Fiscal year variant

PERIV

T001

Features of the Extractor


The key figure FKIMG is not suitable for reporting in BW. It may only be used for calculation purposes because this field represents a key figure on the item
level. There is a 1:n relation between item and condition which would result in the key figure in the query having multiple values. For calculation purposes,
however, it is necessary that this field be added to the extraction structure.
During reorganization, this structure is formed below the order data (application 11) in the table MC13VDOKONSETUP.
This extractor is used to extract item conditions. Header conditions are not extracted.
Due to the increased data volume, loss in performance can occur, especially during reorganization. This can also affect the LIS update and the reorganization
of LIS structures.
During reorganization of the order conditions, you should temporarily deactivate the other DataSources for application 11. See SAP Note 602260 for general
procedures for reorganization.
The recommended update method is queued delta. The unserialized VS update is offered as a selection in the Logistic Customizing Cockpit, but it is not
suitable for extracting changes in the correct order. Thus it should never be selected.

1.11 Message Status Data for FSSC


DataSource Transactional Data: 0FSSC_SLA_1

This DataSource is used to extract message status data that is used to indicate that electronic billing was used during processing. This information can then
be used to calculate internal Key Performance Indicators (KPIs) that measure the effectiveness of your shared services center.

Technical Data
Application Component

Sales and Distribution (SD)

Available as of Release

SAP enhancement package 5 for SAP ERP 6.0

Shipment

SAP NetWeaver 7.0 BI Content Add-On 5, SP01

Content Versions

605

RemoteCube-Capable

No

Delta-Capable

Yes

Extraction from Archives

No

Verifiable

No

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 29 of 31

Data Modeling
Fields of Origin for the Extract Structure
Fields in the Extract Structure

Description of the Field in the Extract

Table of Origin

Field in the Table of Origin

Structure
KAPPL

Application for message conditions

NAST

KAPPL

OBJKY

Object key

NAST

OBJKY

KSCHL

Message type

NAST

KSCHL

SPRAS

Message language

NAST

SPRAS

PARNR

Message partner

NAST

PARNR

PARVW

Partner function (for example SH for


ship-to party)

NAST

PARVW

ERDAT

Date on which status record was created NAST

ERDAT

ERUHR

Time at which status record was created

NAST

ERUHR

ADRNR

Address number

NAST

ADRNR

NACHA

Message transmission medium

NAST

NACHA

ANZAL

Number of messages (original + copies)

NAST

ANZAL

VSZTP

Dispatch time

NAST

VSZTP

VSDAT

Requested date for sending message

NAST

VSDAT

VSURA

Requested time for sending message


(from)

NAST

VSURA

VSURB

Requested time for sending message


(to)

NAST

VSURB

MANUE

Message processed manually

NAST

MANUE

DATVR

Processing date

NAST

DATVR

UHRVR

Processing time

NAST

UHRVR

DATRE

Date of the expected response to a


message

NAST

DATRE

USNAM

User name

NAST

USNAM

VSTAT

Processing status of message

NAST

VSTAT

AKTIV

Active

NAST

AKTIV

TCODE

Communication strategy

NAST

TCODE

LDEST

Spool: Output device

NAST

LDEST

DSNAM

Spool request: Name

NAST

DSNAM

DSUF1

Spool request: Suffix 1

NAST

DSUF1

DSUF2

Spool request: Suffix 2

NAST

DSUF2

DIMME

Print immediately

NAST

DIMME

DELET

Release after output

NAST

DELET

TELFX

Fax number

NAST

TELFX

TELX1

Telex number

NAST

TELX1

TELTX

Teletex number

NAST

TELTX

AENDE

Change message flag

NAST

AENDE

REPET

Repeatability of message

NAST

REPET

REPID

Unused field

NAST

REPID

PFLD1

Unused field

NAST

PFLD1

PFLD2

Unused field

NAST

PFLD2

PFLD3

Unused field

NAST

PFLD3

PFLD4

WFMC: SAPscript form in 30-character


field

NAST

PFLD4

PFLD5

WFMC: Function module for print


formatting

NAST

PFLD5

PMID1

Unused field

NAST

PMID1

PMID2

Unused field

NAST

PMID2

PMID3

Unused field

NAST

PMID3

PMID4

Unused field

NAST

PMID4

PMID5

Unused field

NAST

PMID5

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 30 of 31

TDNAME

Object key (long)

NAST

TDNAME

TDID

Text ID

NAST

TDID

TDSPRAS

Language Key

NAST

TDSPRAS

EDIKEY

Dunning Date (Used in Retail)

NAST

EDIKEY

EDITRANS

Dunning Time (Used in Retail)

NAST

EDITRANS

SNDDR

Send: As disregard

NAST

SNDDR

SNDEX

Unused field

NAST

SNDEX

SNDCP

Unused field

NAST

SNDCP

SNDBC

Address type (1=Organization,


2=Person, 3=Contact person)

NAST

SNDBC

FORFB

Requested Status

NAST

FORFB

PRIFB

Setting for Which Statuses Are Reported


by Mail

NAST

PRIFB

ACALL

Unused field

NAST

ACALL

OBJAC

Unused field

NAST

OBJAC

OBJRR

Unused field

NAST

OBJRR

OBJRN

Unused field

NAST

OBJRN

OUTFL

Unused field

NAST

OUTFL

OBJSNS

Unused field

NAST

OBJSNS

OBJPRI

Unused field

NAST

OBJPRI

OBJCP

Unused field

NAST

OBJCP

NAUTO

Message determined via conditions

NAST

NAUTO

TDRECEIVER

Recipient (Print Parameters)

NAST

TDRECEIVER

TDDIVISION

Department on Cover Page (Print


Parameters)

NAST

TDDIVISION

TDOCOVER

Print: SAP cover page

NAST

TDOCOVER

TDCOVTITLE

Text for Cover Page (Print Parameters)

NAST

TDCOVTITLE

TDAUTORITY

Print: Authorization

NAST

TDAUTORITY

TDARMOD

Print: Archiving mode

NAST

TDARMOD

OPTARCNR

Archive number for optical archives

NAST

OPTARCNR

CMFPNR

Error management number

NAST

CMFPNR

USRNAM

WFMC: Address number, 12 characters

NAST

USRNAM

EVENT

Event

NAST

EVENT

SORT1

Sort criteria for message status records

NAST

SORT1

SORT2

Sort criteria for message status records

NAST

SORT2

SORT3

Sort criteria for message status records

NAST

SORT3

OBJTYPE

Object type

NAST

OBJTYPE

TDSCHEDULE

Send time request

NAST

TDSCHEDULE

TLAND

Country Key

NAST

TLAND

TIMESTAMP

UTC Time Stamp in Short Form


(YYYYMMDDhhmmss)

NAST

TIMESTAMP

Extractor Logic
The extractor extracts data directly from the database table.

Unsychronized Backup Recovery in BI System


This DataSource uses timestamp management for the delta mechanism. The timestamp can be reset to the synchronization time point automatically, for
example in relation to the time zone used by the source system.

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 31 of 31