Dear BI-colleagues,
we are actually facing an issue with the standard extractor 2LIS_02_SCL - schedule line Level of purchase orders.
Our system setup:
The data of this extractor needs to be used to measure a supplier service sevel based upon single schedule lines. My predecessor actually changed the standard definition of this extractor in the System (which might be a reason for our issue?!).
In the BW-System, one standard staging DSO has been created with the folling key:
- PO document number
- PO document position
- PO document schedule line
- field BWVORG --> process key to distinguish between purchasing, goods receipt and invoice receipt data
Coming to the issue....
We are using the following fields to measure the (on time) Service Level:
SLFDT statistical delivery date = "to be" date
BUDAT booing date of GR / IR = "as is" date
--> whenever the BUDAT is higher than SLFDT, the delivery was not in time
In case a purchase order position has more than one schedule line, we get into trouble using this logic. When the final delivery indicator (field ELIKZ) is set on position level, there are update records passed to the BW for all schedule lines of this position showing as BUDAT the date when ELIKZ was set. Example:
Record Record date Sched. line SLFDT BUDAT Comment
1 01.04.2014 1 01.04.2014 01.04.2014 on time
2 10.04.2014 2 10.04.2014 10.04.2014 on time
3 15.04.2014 3 15.04.2014 15.04.2014 with this partial delivery the ELIKZ was set
4 15.04.2014 1 01.04.2014 15.04.2014 not in time
5 15.04.2014 2 10.04.2014 15.04.2014 due to record 3, a new BUDAT arrives for line 2 --> not in time
Unfortunately it's not as easy as e.g. just deleting incoming records having the same BUDAT as the last schedule line, as there are some intended processes which can lead to a later BUDAT (e.g. cancellations, corrections...)
Does anyone know if this is the Standard behaviour of this Extractor? How can I solve my issue?
Thank you in advance,
Andre
