GI quantity Delta issue with 2LIS_02_SCL

Hi Friends !
We are facing delta issue in the BI Prod. Hence to look into the issue, performed few steps in Test environment to check whether delta is performing or not. Mentioned below are the steps which are carried :
1. BW Setup
a. Deletion of queues for Purchasing data in ECC
b. Data collection of purchasing documents for March 1 u2013 March 31 in ECC
c. Deletion of source system initialization in BW
d. Loaded collected data into SAP as delta initialization
Result - OK
2. ECC data entry
a. Created PO #5052422, intracompany STO from DDP1 to USC1
i. 1 line item (qty 5) with two schedule lines (qty 2 & 3)
3. First delta run
a. BW brings over 2 schedule lines for PO #5052422
Result - OK
4. ECC data entry
a. Created PO #5052423, intercompany from DDP1 (USC1) to IRP3 (BV11)
i. 1 line item (qty 5) with two schedule lines (qty 2 & 3)
5. Second delta run
a. BW brings over 2 schedule lines for PO #5052423
Result - OK
6. ECC data entry
a. Posted partial delivery for schedule line 1 of PO #5052422 with a quantity of 1
7. Third delta run
a. no records brought over (change to GI quantity should trigger delta)
Result - FAIL
8. ECC data entry
a. Posted partial delivery for remainder of schedule line 1 of PO #5052422 with and a partial delivery for schedule line 2 with a quantity of 1
9. Fourth delta run
a. no records brought over (change to GI quantity should trigger delta)
Result - FAIL
10. ECC data entry
a. Modified delivery date of both schedule lines of PO #5052422
11. Fifth delta run
a. Both schedule lines of PO #5052422 brought over with updated delivery dates and goods issue quantities
Result - OK
12. ECC data entry
a. Modified delivery date of both schedule lines of PO #5052423
13. Fifth delta run
a. Both schedule lines of PO #5052423 brought over with updated delivery dates
Result - OK
Ques :
1) When modified, GI quantity is not triggering delta. Please advise.
2) 2LIS_02_SCL extractor is build on which delta field.
3) How delta works & behaves with 2LIS_02_SCL extractor?
With Regards
Rekha

Good afternoon Rehka,
I believe that it is correct that the GL change you mention will not trigger a delta on the BW side. This functionality appears to be missing.
If you check in LBWE you will see that the EVENTS for 02: Purchasing -> MC02M_0SCL include the following:
MA: Purchase order
MB: Goods receipt
MC: Invoice receipt
MD: Scheduling agreement
The event associated with a Goods Issue is ML and not included in the list of events for this structure. This is the standard behavior.
I checked and I was unable to find a datastructure that does handle event ML. From what I see the only way to do this is through a custom datasource.
Kind Regards,
Des

Similar Messages

Issue with 2LIS_02_SCL Data source

Hi Everybody,
I am facing the below 2 issues with 2lis_02_scl data source,
1) This is fetching only the records ETENR (Delivery Schedule Line Counter) value with ' 1 ', It is ignoring others ex:2,3 and 4. Hence Data is not reconciling with ECC system.
2) The standard field GLMNG is not getting any data, Data was existed in table(EKET) level. So i have written the code and data is coming now. But the problem is, This is not considering the ROCANCEL indicator it seems. All the other key figures values are coming in with Negative sign When ROCANCEL Value is ' X ' or ' R ', But this field is getting all the positive values irrespective of ROCANCEL indicator. Hence showing the incorrect values compared to the ECC.
Can anybody help me on this,
Regards,
Gopinath

Hi Gopinath:
Have you already applied any SAP Note to solve this problem?
Please check if the SAP Note below is applicable to your system.
668177 - "LIS BW: wrong quantity for documents with invoice plan"
Regards,
Francisco Milán.

Issue with 0SRM_TD_IV data source delta

Hi experts,
I have an issue with the invoices numbers not updated correctly when one of invoice item is deleted in SRM.
For example:
In SRM:
Invoice number: 50001168
Invoice item : 1, quantity: 30 - deleted ( deletion indicator - x)
Invoice item : 2, quantity: 4
Invoice item : 3, quantity: 7
In standard extractor (0SRM_TD_IV) RSA3 : exactly same as SRM data.
In standard DSO (0SRIV_D3) : only invoice number and invoice item one is present, which suppose to be deleted in BI.
Invoice number: 50001168
Invoice item : 1, quantity: 30
When I did the full repair for this invoice number from SRM. I got all the 3 invoice items. It did not overwrite invoice item 1, which is deleted in SRM. the way it works in SRM is, it didn't delete the invoice item but flaged with the deletion indicator x.
Know every thing look good up to extractor RSA3. what should I do know to fix this issue? I see that we don't have tranformation rules in BI 7.0 insted we are using trnasfer rules and update rule. Please let me know.
Thanks,
Chandra

Hi Chandu,
The way I understand your issue is that,
when you do a full upload, you get the information correctly in RSA3 and DSO.
when you run a delta, you are not getting all the line items.
1) Please check whether there are any relevant SAP notes for this extractor to fix this delta issue.
2) Please check whether there is any code in the update rule or transfer rule that deletes the missing line item
Thanks,
Krishnan

Issue with Delta in Function Module

Hi Team,
I have an issue with delta in Genric extraction using function module.Full load is working fine and i have taken post_date as delta field.plz chk the code if any delta related statements are missing.
FUNCTION ZRSAX_BIW_MANGEMENT_RAT .
""Local interface:
*" IMPORTING
*"     VALUE(I_REQUNR) TYPE SRSC_S_IF_SIMPLE-REQUNR
*"     VALUE(I_DSOURCE) TYPE SRSC_S_IF_SIMPLE-DSOURCE OPTIONAL
*"     VALUE(I_MAXSIZE) TYPE SRSC_S_IF_SIMPLE-MAXSIZE OPTIONAL
*"     VALUE(I_INITFLAG) TYPE SRSC_S_IF_SIMPLE-INITFLAG OPTIONAL
*"     VALUE(I_READ_ONLY) TYPE SRSC_S_IF_SIMPLE-READONLY OPTIONAL
*" TABLES
*"      I_T_SELECT TYPE SRSC_S_IF_SIMPLE-T_SELECT OPTIONAL
*"      I_T_FIELDS TYPE SRSC_S_IF_SIMPLE-T_FIELDS OPTIONAL
*"      E_T_DATA STRUCTURE ZQMBW_FUJ_MANAGEMENT OPTIONAL
*" EXCEPTIONS
*"      NO_MORE_DATA
*"      ERROR_PASSED_TO_MESS_HANDLER
Example: DataSource for table MANAGEMENT RATING
TABLES: ZQMBW_MANAGEMENT.
Auxiliary Selection criteria structure
DATA: L_S_SELECT TYPE SRSC_S_SELECT.
Maximum number of lines for DB table
STATICS: S_S_IF TYPE SRSC_S_IF_SIMPLE,
counter
          S_COUNTER_DATAPAKID LIKE SY-TABIX,
cursor
          S_CURSOR TYPE CURSOR.
RANGES: POST_DATE FOR ZMMTVEND_RATING-POST_DATE,
          VENDOR FOR ZMMTVEND_RATING-VENDOR.
Initialization mode (first call by SAPI) or data transfer mode
(following calls) ?
IF I_INITFLAG = SBIWA_C_FLAG_ON.
Initialization: check input parameters
                buffer input parameters
                prepare data selection
Check DataSource validity
    CASE I_DSOURCE.
      WHEN 'ZQMMANAGEMENT_DS'.
      WHEN OTHERS.
        IF 1 = 2. MESSAGE E009(R3). ENDIF.
this is a typical log call. Please write every error message like this
        LOG_WRITE 'E'                  "message type
                  'R3'                 "message class
                  '009'                "message number
                  I_DSOURCE   "message variable 1
                  ' '.                 "message variable 2
        RAISE ERROR_PASSED_TO_MESS_HANDLER.
    ENDCASE.
    APPEND LINES OF I_T_SELECT TO S_S_IF-T_SELECT.
Fill parameter buffer for data extraction calls
    S_S_IF-REQUNR    = I_REQUNR.
    S_S_IF-DSOURCE = I_DSOURCE.
    S_S_IF-MAXSIZE   = I_MAXSIZE.
Fill field list table for an optimized select statement
(in case that there is no 1:1 relation between InfoSource fields
and database table fields this may be far from beeing trivial)
    APPEND LINES OF I_T_FIELDS TO S_S_IF-T_FIELDS.
ELSE.                 "Initialization mode or data extraction ?
    IF S_COUNTER_DATAPAKID = 0.
Fill range tables BW will only pass down simple selection criteria
of the type SIGN = 'I' and OPTION = 'EQ' or OPTION = 'BT'.
      LOOP AT S_S_IF-T_SELECT INTO L_S_SELECT WHERE FIELDNM = 'VENDOR'.
        MOVE-CORRESPONDING L_S_SELECT TO VENDOR.
        CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
          EXPORTING
            INPUT = VENDOR-LOW
          IMPORTING
            OUTPUT = VENDOR-LOW.
        CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
          EXPORTING
            INPUT = VENDOR-HIGH
          IMPORTING
            OUTPUT = VENDOR-HIGH.
        APPEND VENDOR.
      ENDLOOP.
      LOOP AT S_S_IF-T_SELECT INTO L_S_SELECT WHERE FIELDNM = 'POST_DATE'.
        MOVE-CORRESPONDING L_S_SELECT TO POST_DATE.
        CONCATENATE L_S_SELECT-LOW6(4) L_S_SELECT-LOW3(2) L_S_SELECT-LOW+0(2) INTO POST_DATE-LOW.
        CONCATENATE L_S_SELECT-HIGH6(4) L_S_SELECT-HIGH3(2) L_S_SELECT-HIGH+0(2) INTO POST_DATE-HIGH.
        APPEND POST_DATE.
      ENDLOOP.
**Get Management rating details
      OPEN CURSOR WITH HOLD S_CURSOR FOR
      SELECT VENDOR POST_DATE OVERALL_MNGT_RAT OVERALL_DEV_RAT FROM ZMMTVEND_RATING WHERE VENDOR IN VENDOR AND POST_DATE IN POST_DATE .
    ENDIF.
Fetch records into interface table.
    FETCH NEXT CURSOR S_CURSOR
               APPENDING CORRESPONDING FIELDS
               OF TABLE E_T_DATA
               PACKAGE SIZE S_S_IF-MAXSIZE.
    S_COUNTER_DATAPAKID = S_COUNTER_DATAPAKID + 1.
    IF SY-SUBRC <> 0.
      CLOSE CURSOR S_CURSOR.
      RAISE NO_MORE_DATA.
    ENDIF.
ENDIF.              "Initialization mode or data extraction ?
ENDFUNCTION.

Hi
Check URLs:
How to populate the ranges using FM for the SELECTs
Re: Generic Delta Function Module

Issue with Delta Request

Hi Friends,
I have an issue with loading.
1. From source 2lis_13_VDITM, data loads to 2 targets.
ZIC_SEG, 0SD_C03.and from 0sd_C03 it again loads to ZSD_C03W and ZSD_C03M through DTP.
I have done a repair full load on 08.08.2011 to PSA and loaded this request manually to cube ZIC_seg.
I forgoted to delete this request in PSA as i dont want to load this to other targets.
Before i notice ,already delta requests got loaded and has pulled my repair full request also to other targets.
As i have not done any selective deltions on other cubes there may be double entries.
I am planning to do the below steps inorder to rectify the issue.
1. Do a selective deletion of the delta request in all 3 targets which got loaded on 8th along with repair full.
2. Delete the repair full request from PSA.
So now delta request which got loaded after repair full request, is left in PSA.
My question is if my PC runs today will this delta request in PSA also pulls again to cube through DTP?
Kindly share any other ideas please urgent...
Regards,
Banu

Hi Banu,
If the data in the CUBE's is not compressed, then follow the below steps
1)Delete the latest request in CUBE ZIC_SEG
2)Delete the latest request from cubes ZSD_C03W and ZSD_C03M and then from 0SD_C03.
3)load the delta request manually using DTP from your cubes(in DTP you can load by giving request number). to cubes ZIC_SEG and 0SD_C03.
3)now run the delta DTP to load the delta request from 0SD_C03 to ZSD_C03W and ZSD_C03M.
Next when your PC runs it will load only that particular day delta request.
It will work
Regards,
Venkatesh

Issue with generic extraction (Generic Delta)

I have one more issue with Generic Delta Extraction. Here I selected the field related to my requirement but when I am trying to save I am getting error Still OLTP have errors.
I need some help when we select generic delta wht are the settings. Like now I am working on Inventory Management.
Please Some one help me as soon as possible.
Thanks In advance.....
Regds
SDR.

Hi ,
I think there are some of the Keyfigure fields which needs 0Unit or 0Currency field to be present in the Extract Structure but they are not present . Check All unit of measure and Currency unit fields are not hidden .
Regards,
Vijay.

No purchasing date in delta extraction (2LIS_02_ITM, 2LIS_02_SCL)

Hi.
We have been experiencing some issues with delta extraction of purchasing data, using 2LIS_02_ITM and 2LIS_02_ITM.
In particular, the posting date's field (BUDAT) is not always filled: for example, I noticed that when users set the final delivery flag even if the purchase delivered quantity does not correspond to the whole order's quantity or the flag has been set later than the change of the delivery date, the field (BUDAT) in the delta queue is not filled.
By this way, the field may be overwritten: however, we need to keep the posting date value.
I am wondering whether I am correct and, in this case, it is possible to keep that value: however, it seems that the only way is to use a full extraction of data.
Thanks a lot

Roberto Negro,
While filling setup table by using T-code OLI3BW (Purchasing) it is taking very long time.
Please let me is there any way to rerduce this time.
We are at BW 7.3 version.
Regards,

Performance issues with 0CO_OM_WBS_1

We use BW3.5 & R/3 4.7 and encounter huge performance issues with 0CO_OM_WBS_1? Always having to do a full load involving approx 15M records even though there are on the average 100k new records since previous load. This takes a longtime.
Is there a way to delta-enable this datasource?

Hi,
This DS is not delta enabled and you can only do a full load. For a delta enabled one, you need to use 0CO_OM_WBS_6. This works as other Financials extractors, as it has a safety delta (configurable, default 2 hours, in table BWOM_SETTINGS).
What you should do is maybe, use the WBS_6 as a delta and only extract full loads for WBS_1 for shorter durations.
As you must have an ODS for WBS_1 at the first stage, I would suggest do a full load only for posting periods that are open. This will reduce the data load.
You may also look at creating your own generic data source with delta; if you are clear on the tables and logic used.
cheers...

Issue with 0HRPOSITION_ATTR extractor

We are live with BW HR application and having issue with 0HRPOSITION master data. We are extracting data from SAP using 0HRPOSITION_ATTR datasource. I noticed that data is not maintained correctly in master data tables in BW and giving us incorrect results in reporting. Consider below mentioned scenario:
Position A created as vacant on 04/01/2006 with start date (BEGDA/ Valid from) as 04/01/2006 and End date (ENDDA/ Valid to) as 12/31/9999 and is vacant. Below mentioned entry is shown under maintain master data for 0HRPOSITION in BW:
Position Valid To   Valid From Position Vacant
A        03/31/2006 01/01/1000
A        12/31/9999 04/01/2006        X
Position A is now delimited on 09/15/2006 as its no more required. In SAP, position has record only from 04/01/2006 till 09/15/2006 as vacant. When record is extracted in BW, it creates below mentioned entry in master data table.
Position Valid To    Valid From Position Vacant
A         03/31/2006 01/01/1000
A         09/15/2006 04/01/2006        X
A         12/31/9999 09/16/2006        X
Entry 09/16- 12/31 is incorrect as position doesnt exist for this duration. If we report on 0HRPOSTION with key date as 09/30/2006, it shows position A as vacant though position no longer exists.
Has anyone come across this situation. any help is greatly appreciated.
Thanks,
Milind

Hi
I have nt worked with this data source.
1)Is your data source delta enabled?
2)Try running RSA3 and check for record which is not coming fine. If in RSA3 record is fine then check calculations(if any ) in update/transfer rule.
Let me know if it helps..
Sorabh
Assign point if it helps**
Message was edited by: Sorabh Arora

Issue with Report

Hi Friends,
Pls find the issue below
There is a issue with the customer report, When i look at the contracts on R3 - transaction code ME3M - material 34007071 , contract 46.38450 advises contract quantity of 250,759. when i run a BW report it advises contract 46.38450 as 759. Diff = 250,000.
Can any one please advice on this ?

First check in RSA3 whether the data source is bringing correct value or not.
If in RSA3 value is correct then you need to check your transformation.
Cheers,
Neel.

Delta issue on a Generic Datasource

Hi
   I had a Generic Datasource on a Z table.
   The Z table had a Date field on which Delta is based.The Postings are performed manually.
How to solve the delta issue in the below scenario.
Ex; A user made a manual posting with a date 09AUG2010 today and delta is extracted to BW.
    But tommorow a used made another posting with a date 14JULY2010....
Currently that record is not being extracted....how can i resolve this
Thanks

Hi,
Once the data source is created you will extract the data till that date and as the delta is set it will fetch the newly updated records .But i dont think one can post with the back dates in R/3 side.
If i'm not wrong if you are asking regarding record got missed out them wht need to be done?
Then do the repair full request and pull the missed delta records and it wont effect the delta settings.
Regards
KP

Issue with Query on a virtual infoprovider

Hello,
I am getting the following error message while executing a query on a virtual infoprovider. We have recently gone through upgrade from BI 3.5 to BI 7.0 EHP1 (SP5) and from SEM BCS 4.0 to BCS 6.0.
EVersion not specified or not unique                                                             UCR0                006
EError reading the data of InfoProvider ZBCS_CV11                                    DBMAN             305ZBCS_CV11
EError while reading data; navigation is possible                                          BRAIN               289
I>> Row: 11 Inc: RAISE_READ_ERROR Prog: CL_RSDRV_VPROV_BASE   RS_EXCEPTION        301CL_RSDRV_VPROV_BASE
this query has been running fine before the upgrade. In the selection screen there are two fields - version1 and version2, if I am specifying same value in both the fields then the query runs fine and if I am providing different values then the above stated error message appears.
I have tried different settings with properties - Read mode: H,A,X and also different combination from the properties of the virtual infoprovider - with and w/o hierarchies; with and w/o navigation attributes but it did not workout.
the only thing which has changed on this virtual provider is that I had enabled delta caching as this was supposed to be used in a multiprovider.
Has anyone experienced similar issue or have an idea as to what is going wrong here. Please advice.
Regards,
Manish

Hi Manish,
I have exactly the same issue with a query on a virtual infoprovider after upgrading from BI 3.5 to BI 7.0 EHP1 (SP5) and from SEM BCS 4.0 to BCS 6.0.
Would you be so kind to tell me how you fixed this. (other queries seem to be working)
Kind regards,
Jamie Flaxman

Issue with Freight condition with scales

HI Experts
We have requirement like below.
When customer send an order
o     if the order contains materials for a minimum quantity the system should not apply freight condition
o     if the order contains materials for less than minimum quantity the system should apply freight condition
For example: sales condition freight has scale
     scale qty     unit     amount     unit
From     0     PC     18,3     u20AC
     4     PC     0     u20AC
e.g.1  customer send order that contain 9 PC, so system NOT apply freight condition
material     quantity
x1     1
x2     1
x3     2
x4     5
e.g.2  customer send order that contain 2 PC, so system apply freight condition
material     quantity
x1     1
x2     1
For this we have maintained Group condition and maintained scales up to 3 Order quantity 18 EUR . If order quantity is greater than 4 condition should not apply.
But Now our issue is when ever Material determination is occurring in Order our condition is going to fail. For example order quantity is 2 with TAPA item(parent item) and so substitute Item also 2 quantity (Tan item). In this case system is reading order quantity as 4 and our condition is 0. But actual quantity is 2 condition should apply in Order.
Could you please suggest us where we can control this kind of scenario.
Regards, Lakshmikanth

Done through user exit

Goods Issue with reference to Material document

Hello,
I would like to create Goods Issue with reference to material document (Transfer Posting document) , but the following message appears :
"Selected material document does not correspond with action to be executed".
Is it possible to create Goods Issue with reference to Transfer Posting (mov.type 311 - from stor.loc. to stor.loc.) ?
Thanks

Thanks,
probably I'll have to find another way to solve this business requirement of copying the transfer document data in GI.
We have an auto created transfer postings via interface from another system and the main idea was to use already entered fields in transfer posting document such as material , quantity , text , goods recepient , etc. and not to enter them twice when GI should be created. In our case (it's a case for certain materials) it's always 1:1 relationship, so the idea was to facilitate the job of creating the GI, because GI should contain the same data as in transfer posting document.

Issue with copy control of Delivery document to Billing document

Hi All,
I am having some issue with copy control of Delivery document to Billing document.
I am having two line items in Delivery documetn, one is for item to be delivered to customer and other which is created due to batch determination.
Now , when I create billing document (VF01) with reference to this delivery document , I want only one line item (for the one which needs to be delivered to customer).
I have used following things in copy contro from ZLF to ZF2:
Copying requirements: 004 ( Deliv-related item)
Data VBRK/VBRP: 007 "(Inv.Split (Rec/Div))
Is it correct or shall I use something else, so I have only one line item in Billing document.
Regards
Nidhi

Pls. search the forum.
Pls. refer the below link -
Line with 0 quantity for main item with batch split
Thanks

GI quantity Delta issue with 2LIS_02_SCL

Similar Messages

Maybe you are looking for