Delta load for a data source not enabled

Dear Experts,
We have got the requirement to create reports on shipment details.
Based on the requirement we have identified the
Infosouce/ Data source : 0OI_TD_OIGSII
Info Cube: 0OI_TDC01. we think this cube will satisfy the requiremnt.
But the problem is the data source is not delta enabled. so how do we extract the data and how to capture the delta.
when we checked in Roosource table the delta field is blank (Delta only with Full Upload (ODS or InfoPackage Selection))
These data sources are IS OIL specific, so dont know the data extraction procedure.
Please through some light and help me.
Please advise.
Regards
venu

Delete duplicate request is a process chain variant, which will allow you to set the duplicate request deletion options. You need to explore those options.
Now say you have a routine in the DTPs.
DTP1 = Current Month
DTP2 = Prevoius Month
In the month of July,
DTP1 = 07/2009
DTP2 = 06/2009
On daily basis DTP1 will load data for July and DTP2 will load data for June. Now delete duplicate request will delete the previous requests loaded by each of them for the same month. Meaning delete duplicate request for DTP1, will delete the request loaded for 07/2009 and DTP2 will delete the duplicate request for 06/2009.
Now when you will be in Aug, the routine will change the selection criteria
DTP1 = 08/2009
DTP2 = 07/2009, so now DTP2 will delete teh duplicate request for 07/2009 and load the new data. Now the data changed for 06/2009 is not possible to load as you have only 2 DTPs.
For safer side, you can create 3 DTPs to take care of the last 3 months, but first test the logic for two DTPs and then go further for the third DTP.
- Danny

Similar Messages

  • Delta Option for Generic Data Source

    Hi ,
    My requirement is Delta Option for Generic Data Source. This Data Source is getting Extracted from Function Module.
    For this requirement I have followed below steps.
    1) Added the Field (On which Delta gets enabled) to the extract structure by using Append Structure
    2) Enabled Delta On this Filed.
    3) If I try to save the Data Source,  I have gone to a screen where I am able to see 4 coloumns
    a) Selection
    b) Hide Field
    c) Inversion
    d) Filed Only known in User Exit.
    By default Hide Field and Filed Only known in User Exit check boxes have been checked.
    Would you please tell what is the use of Filled Only known in User Exit check biox.
    As My data source is getting the data buy using the Function Module, Shall I uncheck this Check Box.
    Thanks and Regards,
    K.Krishna Chaitanya.

    Hi Krishna,
    The "FIELD" should be checked if we write any enhancement in CMOD, so that system can identify that this particular field has enhancement written to it,
    But even in real time systems i usually find that even though we check the "FIELD" or not , there is no effect .
    So Checking "FIELD" or not will not impose any isses .
    Regards,
    Krishna

  • Delta Activation for a data source

    Hi All,
    Thank You Very much for reading this query.
    In Source System, I have enabled Delta on Calday field for a generic data source by clicking on Generic Delta Button.
    For this data Source, extraction is from data base table.
    Now Do I need to write any function module for this data source, as I have enabled Delta.
    Would you please help me on this.
    Thanks and Regards,
    K.Krishna Chaitanya.

    Delete duplicate request is a process chain variant, which will allow you to set the duplicate request deletion options. You need to explore those options.
    Now say you have a routine in the DTPs.
    DTP1 = Current Month
    DTP2 = Prevoius Month
    In the month of July,
    DTP1 = 07/2009
    DTP2 = 06/2009
    On daily basis DTP1 will load data for July and DTP2 will load data for June. Now delete duplicate request will delete the previous requests loaded by each of them for the same month. Meaning delete duplicate request for DTP1, will delete the request loaded for 07/2009 and DTP2 will delete the duplicate request for 06/2009.
    Now when you will be in Aug, the routine will change the selection criteria
    DTP1 = 08/2009
    DTP2 = 07/2009, so now DTP2 will delete teh duplicate request for 07/2009 and load the new data. Now the data changed for 06/2009 is not possible to load as you have only 2 DTPs.
    For safer side, you can create 3 DTPs to take care of the last 3 months, but first test the logic for two DTPs and then go further for the third DTP.
    - Danny

  • Delta loading of generic data source.

    Hi,
    please tell me the procedure for How to load Delta data For generic data source?

    Hi
    You can use the following procedue
    Enabling Delta Load
    Use
    You must first configure and modify the DataSource to be used for delta loading in CAF and SAP BW integration and define delta-relevant attribute fields.
    Prerequisites
    You have launched the Maintain Generic DataSources tool of SAP BW.
    Procedure
    1. Configuring Generic DataSources
         1.      In the DataSource pane, choose  next to the Transaction data field to select the DataSource to use for CAF and SAP BW integration and choose Change.
         2.      In the Change DataSource maintenance screen:
               a.      Set Applic. Component to BW.
                b.      Choose Save.
        3.      In the Create Object Directory Entry dialog box:
                a.      Choose Local Object to see the DataSource information.
                 b.      Choose Save to return to the Change DataSource maintenance screen.
      4.      Choose Generic Delta. In the Generic Delta dialog box:
                a.      Browse Field Nm. to select the delta-relevant field.
               b.      Mark the Time stamp radio button.
                c.      Mark New Status for Changed Records.
    5.      In the Selection of field determining delta dialog box, select the following delta-relevant fields:
    ○       For the entity service DataSource, select the field corresponding to LASTCHANGEDAT.
    ○       For the application service DataSource, select the field corresponding to delta-relevant field specified by BW extractor method developer.
    6.      In the DataSource: Customer version Edit screen, save all data.
    2. Activating DataSources
           1.      Launch the SAP BW Administrator Workbench and go to Modeling.
          2.      Open the list of InfoSources and select the DataSource assignment you want.
          3.      With the secondary mouse button, choose Replicate DataSources.
          4.      Select the same object from step 3 and choose Change Transfer Rules with the secondary mouse button.
          5.      In the InfoSource Change screen, choose with the quick info text Activate.
    Initializing Delta Load
    Prerequisites
    You have configured the DataSource for the delta loading process. For more information, see Enabling Delta Load.
    Procedure
    1. Starting Delta Initialization
         1.      Launch the SAP BW Administrator Workbench and go to Modeling.
         2.      From the Modeling pane, click InfoSource to populate the InfoSource pane and select the InfoPackage you created for the InfoSource in, for example, Example of Data Extraction.
          3.      From the Update tab page, activate the Initialize Delta Process indicator.
          4.      To define parameters to be used for the delta load process, go to the Data Selection tab page and define relevant parameters.
          5.      In the Schedule tab page, choose Start to begin delta initialization.
    If you defined parameters to be used in delta load (step 4 above), use PSA in the modeling component of Administrator Workbench  to view the request results.
         6.      To check when delta initialization is finished, go to the Maintain InfoPackage screen of the Monitor u2013 Administrator Workbench and press F6.
    2. Monitoring Delta Initialization
         1.      Launch the BW Delta Queue Maintenance and select the DataSource in question.
         2.      Use the secondary mouse button to see the current pointer value in Generic Delta Current Status.
         3.      You can delete the delta initialization (if you want, and subsequently create a new delta initialization) in Scheduler (Maintain InfoPackage) by choosing the delta request from Initialization Options For Source System and choosing Remove.
    In this screen, you can also check the status of the delta initialization request.
    To see the content and results of the delta initialization request, go to PSA in the modeling component of Administrator Workbench  to view the request results. 
    3. Running Delta Load
    You can run the delta load process only after delta initialization has been completed.
         1.      Open the InfoPackage and in the Update tab page activate the Delta Update indicator.
          2.      Go to the Schedule tab page and choose Start.
    *Enabling Delta Load *
    Use
    You must first configure and modify the DataSource to be used for delta loading in CAF and SAP BW integration and define delta-relevant attribute fields.
    Prerequisites
    You have launched the Maintain Generic DataSources tool of SAP BW.
    Procedure
    1. Configuring Generic DataSources
          1.      In the DataSource pane, choose  next to the Transaction data field to select the DataSource to use for CAF and SAP BW integration and choose Change.
         2.      In the Change DataSource maintenance screen:
            a.      Set Applic. Component to BW.
            b.      Choose Save.
        3.      In the Create Object Directory Entry dialog box:
               a.      Choose Local Object to see the DataSource information.
                b.      Choose Save to return to the Change DataSource maintenance screen.
       4.      Choose Generic Delta. In the Generic Delta dialog box:
           a.      Browse Field Nm. to select the delta-relevant field.
           b.      Mark the Time stamp radio button.
           c.      Mark New Status for Changed Records.
      5.      In the Selection of field determining delta dialog box, select the following delta-relevant fields:
    ○       For the entity service DataSource, select the field corresponding to LASTCHANGEDAT.
    ○       For the application service DataSource, select the field corresponding to delta-relevant field specified by BW extractor method developer.
       6.      In the DataSource: Customer version Edit screen, save all data.
    2. Activating DataSources
       1.      Launch the SAP BW Administrator Workbench and go to Modeling.
       2.      Open the list of InfoSources and select the DataSource assignment you want.
      3.      With the secondary mouse button, choose Replicate DataSources.
        4.      Select the same object from step 3 and choose Change Transfer Rules with the secondary mouse button.
      5.      In the InfoSource Change screen, choose with the quick info text Activate.
    Hope this helps
    Regards
    Shilpa

  • About delta loading for master data attribute

    Hi all,
    We have a master data attribute loading failed which is a delta loading. I have to fix this problem but I have two questions:
    1. how can I find the those delta requests because I need to delete all these failed requests first, am I right ? Master data is not like cube or ods that we can find the requests in Manage, for master data how can we find them ?
    2. Could you please let me know the detailed procedures to perform this delta loading again ?
    Thanks a lot

    Hi...
    1. how can I find the those delta requests because I need to delete all these failed requests first, am I right ? Master data is not like cube or ods that we can find the requests in Manage, for master data how can we find them ?
    Look.....for master data.....no need to delete request from the target..........just make the status red.......and repeat the load.....But problem is that master data sometimes does'nt support Repeat delta..........if u repeat......then load will again fail with Update mode R.........in that case u hav to do re-init.......
    1) delete the init flag.......(In the IP scheduler >> in the top Scheduler tab >> Initialization option for source system)
    2) Init with data transfer(if failed load picks some records)..........otherwise .....init without data transfer.....if the last delta failed picking 0 records.......
    3) then Delta.......
    2. Could you please let me know the detailed procedures to perform this delta loading again ?
    1) Make the QM status red.........to set back the init pointer.......
    2) Repeat the load.....
    After that.........if again load failed with Update mode R.....
    1) delete the init flag.......
    2) Init with data transfer(if failed load picks some records)..........otherwise init without data transfer.....
    3) then Delta.......
    Regards,
    Debjani.....

  • Delta upload  for generic data sources.

    Hai All,
    I tried as per SAP online document , but still i am not getting the result i.e delta upload from the BW side. Here i explained  everything what i did.
    In R/3
    1. I have created a table with 3 fields SNO, SNAME, DOB
    2. Then i created some entries in that table.
    3. With Tr Code RSO2 i created one data source. Here i took Master Attribute Datasource
    4. In generic delta i took the Generic field as DOB. and Time stamp and upper limit 10 sec.
    In BW side
    1. I have replicated the data sources under application compone in which i have creatred in R/3..
    2. Then i activated that data source and created infopackage for that.
    3. in the selection i have specified 01.01.1900 to 01.01.9999
    4. First i made  Full Update then i get all the records from R/3.
    5. In R/3 i have created 2 more entries.
    6. In Infopackage UPDATE Tab i have selected the Initilize Delta Process ( Initialization with Data Transfer).
    For this i am getting the error message as follows.
    Error message from the source system
    Diagnosis
    An error occurred in the source system.
    System Response
    Caller 09 contains an error message.
    Further analysis:
    The error occurred in Extractor .
    Refer to the error message.
    Procedure
    How you remove the error depends on the error message.
    Note
    If the source system is a Client Workstation, then it is possible that the file that you wanted to load was being edited at the time of the data request. Make sure that the file is in the specified directory, that it is not being processed at the moment, and restart the request.
    Here i closed the all things in R/3 as per the note mentioned above. Still it is giving the error message.
    If i select the Intilization Delta Process( Intilization with out Data Transfer) then i am getting the option Delta Update . I selected this Delta update and scheduled but no data is coming.
    Please help.
    Regards
    Prashanth K

    Hai  Sachin,
                       I am getting the problem at PSA only. Actually that is connected to ODS Object only. Until unless we don't get the delta data into PSA we can't proceed futher. So please help. I am working on NW 2004S.
    Regards
    Prashanth K

  • PLIKZ field for COPA data source not there in Extract structure.

    Hello all,
    When I create a data source for COPA the PLIKZ field from the segment level is not maintained in the Extract structure and it is not replicated to BW also. But the other field GJHAR is maintained in the Extract structure which is also there in the segment level!!
    Clarify me why it is not available in extract structure? Also we are in 4.7 version and 3, 5 in BW.
    Points will be assigned!!!
    Thanks
    Ram

    Hello Friends,
    Could some one help me why the field PLIKZ is not available in the Extract structure when i create a COPA Data source?
    Need ur suggestions urgently!!!
    Helps please
    Thanks in advance once again

  • Time Stamp Delta field for Generic Data Source

    Hi Experts,
    I have a requirement to create a Generic Data Source based on view. This view on PA0006 and PA0105 tables.
    Will you please suggest me which field i have to take as delta field.
    Thanks In Advance.

    Also, make sure that whenever a new record is created in those tables, field AEDTM is getting updated with system date else you will miss new records in delta unless there is a change in those newly created records.
    Regards,
    Gaurav

  • Delta field for generic data source based on view EKBE

    Hello,
    I am creating a generic datasource based on table EKBE. Can anyone please tell me what field should I use for delta. Is it BUDAT(Posting Date in the Document) or CPUDT(Day On Which Accounting Document Was Entered).
    Thanks for the help.
    Praveen

    Hello Ajeet Singh,
    Thank you very much for the reply.
    I will go ahead with CPUDT.
    BUDAT is the date which can be changed. I can change the date in system and chances are it will not pick in delta.
    CPUDT is the date on which document was created/changed.
    Thanks,
    Praveen

  • Delta load for 0customer

    Hi Friends,
    I have a issue in delta load for 0customer. The load was initialized with data transfer for the first time load ,The data was loaded succesfully , now we have enhaced the 0customer_attr with customer group .In RSA3 if we check we are getting values for customer group. we created one delta infopackage with update status as delta and scheduled the load .we are getting data load success status but with 0 records. Please can anybody share the process for delta load for master data objects. Iam facing similar problem while uploading delta load for 0MATERIAL.
    Regards,
    Dippy

    Hi
    in source system, check whether your enhanced field is with hide check box ticked.
    As soon as you add filed in append structure by default it is having that field is hidden. You have to uncheck it.
    Then replicate the datasource in BW.
    Now if delta is the issue that you are not getting ant record, that may be because there is no change in master data, delta will only bring records when there will be nay change in master data update.
    So my suggestion is to crate a full repair infopackage, extract everything in to PSA and then load the data with FULL DTP.
    I hope this will work.
    Thank-You.
    Regards,
    Vinod

  • How to enable the Delta for the data source 0CO_OM_OPA_7

    Hi Experts,
    I have a business content data source 0CO_OM_OPA_7 and I need to activate and enable Delta for this data source.
    This data source is activated (but not delta enabled) and used for full load in my system for the past three year. As this is a full load this data source is carrying more than 4 million records every day with adding 2 millions records every year. The load takes every day 4 to 5 hours for completion.
    Now I need to enable the delta for this data source. To enable the delta for this data source I used the transaction RSA5 and clicked on the 'Activate DataSources' but the data source is not enabled the 'Delta'
    I have also checked in the RSA6 transaction, the check box for 'Delta' is not checked for this data source.
    Can anybody help in enabling the 'Delta' for this data source.
    Thanks in Advance
    Narendra

    Hi,
    DS "0CO_OM_OPA_7" won't support deltas, so load to ODS then to Cube. Else delete the overlaping request then load this you can set in InfoPackage level.
    You check any Period/Month fields in 0CO_OM_OPA_7 then write simple routine in Infopackage and the set the overlaping deletion.
    Use the followng code and change it for your requirement in Infopackage level.
    I'm using 0CO_PC_01 DataSource, so it won't have delta so I'm using the following code in InfoPackageag and set delete overlaping req. So eveyday it will delete the old req for that period and then it will load data againg for that period (Full loads).
    DATA: l_idx LIKE sy-tabix,
            zzdate LIKE sy-datum,
            zzbuper LIKE t009b-poper,
            zzbdatj LIKE t009b-bdatj,
            zzperiod(7) TYPE c.
      READ TABLE l_t_range WITH KEY
           fieldname = 'FISCPER'.
      l_idx = sy-tabix.
      zzdate = sy-datum - 1.
      CALL FUNCTION 'DATE_TO_PERIOD_CONVERT'
        EXPORTING
          i_date               = zzdate
    *             I_MONMIT             = 00
          i_periv              = 'V3'
               IMPORTING
         e_buper              = zzbuper
         e_gjahr              = zzbdatj.
    *           EXCEPTIONS
    *             INPUT_FALSE          = 1
    *             T009_NOTFOUND        = 2
    *             T009B_NOTFOUND       = 3
    *             OTHERS               = 4
      IF sy-subrc <> 0.
    * MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    *         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
      CONCATENATE zzbdatj zzbuper INTO zzperiod.
      l_t_range-low = zzperiod.
      l_t_range-option = 'EQ'.
      l_t_range-sign = 'I'.
      MODIFY l_t_range INDEX l_idx.
    Thanks
    Reddy

  • Deltas for Financial data source

    Hi,
    For logistics we set deltas at LBWE.
    But coming to FI data surces how the deltas are picked up.?
    Can you please tell  me>?
    I know that system internally maintains Time stamp for fi Transactions.
    Can i know a little  more on it.?
    Regards,
    Naresh.

    HI
    FI -Delta Mode:
    A time stamp on the line items serves to identify the status of the delta. Time stamp intervals that have already been read are then stored in a time stamp table (BWOM2_TIMEST).
    (Info object 0Recordmode plays vital role deciding delta's .Check the field "delta "in ROOSOURCE /RODELTAM table to identify the image)
    The Financial Accounting line items are extracted from the SAP R/3 system in their most recent status (after-image delta method).
    AIE: This delta method is not suitable for filling Info Cubes directly in the BW system. To start with therefore, the line items must be loaded in the BW system in an ODS object that identifies the changes made to individual characteristics and key figures within a delta data record. Other data destinations (Info Cubes) can be provided with data from this ODS object.
    It uses delta type E(pull) means the delta data records are determined during the delta update by the data source extractor, updated to the delta queue and passed on to BI directly from there.
    thx

  • Data Not coming Properly for 0HR_PA_OS_1 Data Source?

    Hi Experts,
    I am trying to load data to 0PAOS_C01 using 0HR_PA_OS_1 data source. For field 0POS_OCCVAC key figure i am not getting any data from Data Source.
    I checked in RSA3 for 0HR_PA_OS_1 data source and  in that it is not populating data for filed OCC_VAC_PERC  field. I checked with HR functional team and they mentioned its a BI issue.
    Kindly tell me how can i populate values for the particular field. FYI i am getting correct data for other fields.
    Please help me.
    Thanks

    The possible reasons
    1.Your user id might not be having the proper authorization to pull the HR data.This you can confirm with your basis guy,if you are unable to find what are the authorization roles required for HR data, for the time being you can take SAP_ALL authorization in development box and try to pull.
                            OR
    2.Try to pull from BW side,you may be able to see the data there because this uses the background user id used in RFC connection ( provided if your background user id having proper authorization ).

  • Delta On CALDAY Filed for Generic Data Source

    Hi,
    I have enabled delta option on CALDAY Field for Generic Data Source.
    I thought of giving Safety Interval for Upper Limit as 1 and Safety Interval for Upper Limit as ZERO.Would you please advise me on this, This fetches all delta data?.
    Would you please advise me on this.
    Thanks and Regards,
    K.Krishna Chaitanya.

    Hi Krishna,
    If your delta enabled field is Date then try this,
    Safety Interval Upper Limit                                                                     Calend. Days
    Safety Interval Lower Limit                         1                                        Calend. Days
    Then test your delta, will get good result.
    I created 4 GDS with this safety interval and working fine for me.
    regards,
    Kiran

  • Power View in SharePoint Server - The data extension type for a data source is not valid

    Hi All,
    All of a sudden I am getting following error when trying to create Power View report using shared report data source (no error testing the connection):
    "The current action cannot be completed. The data extension type for a data source
    'http://dev/Shared Ducuments/Sales.rsds' is not valid for this operation"
    I already have a data source (I had created it after creating my site collection a week ago) and when I use this source to create Power View report then there is no error but I am getting above error when I create another similar data source and use it to create
    a Power View report.
    Please help me to resolve the error.
    Thanks

    I am going nuts! I had selected 'Analysis Services' instead of 'Microsoft BI Semantic Model for Power View'

Maybe you are looking for