SAP Netweaver Business Intelligence BI / BW

Symptom
General questions
1. Question: Where can I find the documentation for the DataSource?2. Question: How do I maintain the DataSource in the SAP ERP system?3. Question: Which extraction structure does the DataSource use?4. Question: How do I prepare the initial data load for the DataSource?5. Question: When and how is the delta data written for the DataSource?
Specific questions
1. Question: Why does the system not write any deletion records when an order is deleted (reverse images)?2. Question: Why does the system not write any delivery information for items supplied with quantity 0?3. Question: How is the data for the fields for the actual goods movement date of a delivery (MCEX_I_WADAT) and the actual delivery date of a delivery (MCEX_I_LFDAT) determined?4. Question: Can the DataSource also be used for immediate deliveries and are there any peculiarities here?5. Question: Can the DataSource also be used for scheduling agreements with delivery schedules (automotive)?

Other terms

MC11V_0SSL, sales document, order delivery, MCEX_UPDATE_CALL_11, LMCEXM04, form MC11V_0SSL_TAB_FILL, reverse image, VBAK-ABDIS, VBEP-ABART, delivery schedule type, scheduling agreement, scheduling agreement for suppliers

Reason and Prerequisites

FAQ

Solution
General questions
1. Question: Where can I find the documentation for the DataSource?
Answer:
You can find the documentation for the DataSource 2LIS_11_V_SSL in the documentation for BI Content – Customer Relationship Management – ERP Analytics – DataSources – Extraction SD Sales: Order Delivery. You can also use the search term “2LIS_11_V_SSL” to find the documentation.
2. Question: How do I maintain the DataSource in the SAP ERP system?
Answer:
The central maintenance of DataSources for sales documents can be found in transaction LBWE “LO Data Extraction: Customizing Cockpit” (logistics cockpit). Logistics application 11 contains all DataSources for sales documents in SAP ERP.
You can go to both the settings of the DataSource and to extraction structure maintenance from the logistics cockpit.
3. Question: Which extraction structure does the DataSource use?
Answer:
The DataSource 2LIS_11_V_SSL uses the extraction structure MC11V_0SSL.
4. Question: How do I prepare the initial data load for the DataSource?
Answer:
For the initial data load, you must fill the setup tables that are used for the initial data load by SAP BI. The initial data load does NOT read from the original document tables.
Call transaction OLI7BW “Statistical Setup from Old Documents: Orders” and execute the reconstruction with your required selection criteria.
Use transaction RSA3 to display the contents of the setup table.
5. Question: When and how is the delta data written for the DataSource?
Answer:
The system activates the queues for collecting delta data when the initial data load is executed.
The system writes the delta data for the sales document extractors when saving the sales document. A separate update module is called for the extractor data, which collects the data in the outbound queue.
Specific questions
1. Question: Why does the system not write any deletion records when an order is deleted (reverse images)?
Answer:
The DataSource 2LIS_11_V_SSL is an allocation structure. This means that data is written from the sales order AND from the related delivery or billing document. The system cannot write any deletion records for these allocation structures. All key figures are reset for the allocation structures during deletion. However, the entry itself must remain on the BI side and cannot be deleted.
2. Question: Why does the system not write any delivery information for items supplied with quantity 0?
Answer:
Order items supplied with quantity 0 are treated as undelivered order items – the system does not write any delivery information (for example, delivery note number).
3. Question: How is the data for the fields for the actual goods movement date of a delivery (MCEX_I_WADAT) and the actual delivery date of a delivery (MCEX_I_LFDAT) determined?
Answer:
See Note 797537 for more precise information about determining the two dates.
4. Question: Can the DataSource also be used for immediate deliveries and are there any peculiarities here?
Answer:
The DataSource 2LIS_11_V_SSL can also be used for immediate deliveries. An immediate delivery with order type ‘SO’ is created in the standard system. The delivery is also created directly when the order is saved.
Since both documents are posted together (logical unit of work (LUW)), the sequence of records in the DataSource cannot be guaranteed – the change record via the delivery is written before the creation record of the order.
However, this is not a problem since the key figures are updated via ‘Addition’. The records from the immediate order and delivery are written together and are then contained in the same InfoPackage.
5. Question: Can the DataSource also be used for scheduling agreements with delivery schedules (automotive)?
Answer:
The DataSource 2LIS_11_V_SSL CANNOT be used for scheduling agreements with delivery schedules. This usage is excluded. The DataSource was not designed for this document type.