Extraction SD Sales: Document Schedule Line Billing

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 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.

End of the note.

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	`VBUP`	`ABSTA`
`B_DELAY`	BW extraction SD/LE: Confirmation delay
`BMENG`	Confirmed quantity	`VBEP`	`BMENG`
`BUKRS`	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`
`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 BW extraction	`VBKD`	`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`
`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 document	`VBUP`	`POSNR`
`PRODH`	Product hierarchy	`VBAP`	`PRODH`
`PS_POSID`	Work breakdown structure element (WBS element)	`VBAP/PRPS`	`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 schedule lines	`VBEP`	`WLDATBE`
`WMENG`	Order quantity for customer in sales units	`VBEP`	`WMENG`
`> PI 2004.1`
`APOPLANNED`	Planning in APO

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 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	1	10	0

2. Supply of the order schedule line:

ROCANCEL	VBELN	POSNR	ETENR	OLFMNG	VSMNG
	4711	10	1	-6	6

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.

End of the example.

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 Example

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

ROCANCEL	VBELN	POSNR	ETENR	OLFMNG	VSMNG
X	4711	10	1	-4	-6
	4711	10	1	3	7

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

End of the example.

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 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	1	7	-7

The following values arise in the DataStore object via billing:

DataStore Object	VBELN	POSNR	ETENR	OLFMNG	VSMNG
	4711	10	1	3	7 <- Status before deletion of the delivery
	4711	10	1	10	0

End of the example.

Note 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.

End of the note.

If the order is also deleted, the following screen appears:

ROCANCEL	VBELN	POSNR	ETENR	OLFMNG	VSMNG
	4711	10	1	-10	0

The following values arise in the DataStore object via billing:

DataStore Object	VBELN	POSNR	ETENR	OLFMNG	VSMNG
	4711	10	1	10	7 <- Status before deletion of the order
	4711	10	1	0	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	1	10	0 Create order
	4711	10	1	-6	6 Create delivery
X	4711	10	1	-4	-6 Change delivery before image
	4711	10	1	3	7 Change delivery after image
	4711	10	1	7	-7 Delete delivery
	4711	10	1	-10	0 Delete order

Note 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.

End of the note.

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.