on 05-06-2014 7:16 AM
Hi,
For reporting we must transfer the data, listed below, to BW. It seems enough to use 2LIS_11_VASCL and 2LIS_11_V_SSL datasources because our keys on DSO are VBELN (Sales Document), POSNR (Item), ETENR (Schedule Line Number). However, KWMENG (Cumulative Order Quantity) and NETWR ( Net Value) is on 2LIS_11_VAITM datasource where ETENR does not exist. How can we integrate these fields on BW with three key fields?
VA05-EN | BW | SAP | 2LIS_11_VAITM | 2LIS_11_VASCL | 2LIS_11_V_SSL |
Sales Document | 0DOC_NUMBER | VBELN | |||
Item (SD) | 0S_ORD_ITEM | POSNR | |||
Schedule Line Number | 0SCHED_LINE | ETENR | |||
Sales Document Type | 0DOC_TYPE | AUART | |||
Confirmed Quantity | 0CONF_QTY | BMENG | |||
Delivery Date | 0DSDEL_DATE | EDATU | |||
Billing block | 0BILL_BLOCK | FAKSK | |||
Sold-to party | 0SOLD_TO | KUNNR | |||
Exchange Rate | 0EXCHG_RATE | KURSK | |||
Order Quantity | 0CML_OR_QTY | KWMENG | |||
Material | 0MATERIAL | MATNR | |||
Net Value | 0NET_VALUE | NETWR | |||
Status | 0DLV_STS | LFSTA | |||
Goods Issue Date | 0GI_DATE | WADAT | |||
Plant | 0PLANT | WERKS | |||
Order quantity | 0ORDER_QTY | WMENG | |||
Pricing date | 0PRICE_DATE | PRSDT | |||
Created on | 0CREATEDON | ERDAT |
Hi Mohammed,
I am also planning to extract VA05 data to BW. I am planning to use 2LIS_11_V_SCL extractor for this. Have you extracted the data to BW? Which extractor you used for this? Pls let me know.
Thanks,
Deepa.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Deepa,
Sorry for the late response. I used the following datasource:
2LIS_11_VAHDR: Using for the order date and 0bill_block as the 0DOC_NUMBER attribute. In VASCL and V_SSL, the date can be different for every item.
2LIS_11_V_SSL: Using delivery quantity and delivery date per order,item,schedule line.
2LIS_11_VASCL: The other data came from via this datasource. KWMENG and NETWR was added using Customer exit in R/3 side.
I used a DSO to hold all data. Then, I create a cube and refilled every day for only open sales order.
I hope, this information is useful for you.
Hi Muhammed,
Sales Documents have 3 levels, Header, Item and Schedule Lines.
Schedule Lines usually can get deleted quite often during sales document stock availability rescheduling. Sales line item data in most configurations can just be rejected.
If you just want to know the order quantity you could use:
2Lis_11_VAITM
2LIS_11_V_ITEM
That works well to identify the order quantity as it will not get deleted or modified so often with daily rescheduling.
But if you are looking for confirmed sales line item quantity for partial deliveries. The solution used here was to create a custom cube with routines to handle business scenarios.
Hope that helps.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Carlos,
Thanks for reply, the aim of the report is tracking the open order with three keys and without blocking bills; your second statement, "confirmed sales line item quantity for partial deliveries" is what we want, plus net value...
Is that possible to use customer exit on SAP side for adding LFSTA, NETWR and KWMENG in 2LIS_11_VASCL datasource? If this is possible, which table can we use for adding these values?
Hi Muhammed,
I am not sure in regards of adding the fields to the data source. It is a trick one because the schedule lines are always getting deleted and re-created as I mention before.
I would imagine it would not work appropriate as sales line items with values would disappear if the sales line item is not confirmed or confirmed and them deleted.
(of course this would also depended on the ATP( available to promise ) settings in SD. Check with you SD friends.
But certainly if you bring the item sales data and schedule line data in separate DSO. You could them mash it up with routines in one cube to achieve all your required key figures.
I would recommend using the sales line item as the main source of the information and look up for the cancelled and confirmed schedule line in say schedule line DSO.
This way you could even provide information like when it was confirmed and the actual delivered date. Very important information for the logistic KPI's.
Hope that helps.
User | Count |
---|---|
90 | |
10 | |
10 | |
10 | |
7 | |
7 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.