Delta loading to BW and archiving

Hi Expert
We have ERP2004 and BW.   For loading data from ERP2004, we use both full and delta upload.  We are currently planning to implement archiving in ERP2004.
Especially MM PO (purchasing order) documents is the target for archiving.  I have question here.
If we archiving tables which are loaded to BW with delta upload,  is data in BW also deleted?
We do full loading to BW for PO document table, but related tables like STXH, STXL, ADR2, ADRCT, we do delta upload. I am afraid that data inconsistency will occur.
Thank for your advice in advance.

In my opinion, if you are using standard data sources for loading in delta mode, it will delete archived documents from BW tables also unless you write a specific routine for field ROCANCEL and value R (used for deleted records).
In case of full load, data will not be deleted from BW system unless you are doing a delete and full.
If you are doing a delta load using generic data sources, it will not bring any deletion to BW system unless you have specifically written some code to find the deleted records and send those to BW.
I hope it helps.
Regards,
Gaurav

Similar Messages

  • Delta Load on DSO and Infocube

    Hi All,
            I would like to know the procedure for the scenario mentioned below.
    Example Scenario:
    I have created a DSO with 10 characteristics and 3 keyfigure. i have got 10 Customers whose transactions are happening everyday. A full upload on the DSO was done on 7th October 09. How can i load their changing data's from 8th Oct to till date to DSO? and what will be the situation for the same in the case of Infocube??
    Step by step guidance will be a great help
    Thanks in advance
    Liquid

    Hi,
    The key-fields take an important role at DSO level alone as you get the power of overwritting records. Once thats done at the DSO level you can simply carry on with a Delta load into the cube from your Change Log table and you don't have to worry about anything. Just to add, all the characteristics in the cube are key-fields so you will get a new records for each different value only the key-figures will sum up for a set of all the same characteristics.
    Thanks,
    Arminder

  • Delta Loads for 2lis_02_scl and 2lis_02_itm

    Hi Experts,
    I am facing an issue, After initializing the setup tables and doing the init load for 2lis_02_scl and 2lis_02_itm whenever I do the delta loading for these two, all the dataload finish with green status and extracting 0 from 0 records.
    I can see the queues for both these datasources in RSA7 in R/3, yet no record is extracted.
    Any help will be appreciated.
    Regards.

    Hi,
    have a look into transaction smq1. there you should be able to see your extraction queues with the entry MCEX02 (or likewise)
    Please schedule the program RMBWV302 and when this one is finished, start the deltapackage.
    hth
    cheers
    sven

  • SAP Mobile Sales 2.0 delta load issue for Sales Orders

    Hello,
    we have used Mobile Sales 2.0 with a Windows app for a while now. Our current issue is that sales reps won't see any historical sales order data on their devices.
    Background
    Due customer requirements, we need to make small changes to customer master data attributes and reload all customers from ERP to CRM. Then we ran delta loads (MAS_PARTNER followed by all other objects) to DOE, in which virtually all 5000+ customer accounts were compared. The delta load ran for about 3 days (some performance bottleneck we haven't located yet).
    During the delta load, data on devices was inconsistent. Accounts were missing and all transaction data disappeared. After the delta loads, all accounts and contacts are OK, save for a few. Data from activities (appointments, tasks) have reappeared, as they should. Only sales orders won't reappear. The sales orders exist in the backend and belong to active accounts and sales reps.
    Settings and troubleshooting so far
    We don't have any limitations for sales orders in CRM Sales Mobile configuration.
    We've run delta loads for all objects in transaction SDOE_LOAD.
    MAS_CUSTOMIZATION etc seem fine.
    We've re-run initial load for sales orders from CRM.
    In the test system, we've even reinitialized the whole CDS database on DOE and on the devices, then re-ran the loads.
    Checked steps suggested in discussion
    SAP CRM 2.0 initial load issue
    Historical sales orders (those created before the master data reload) exist in the backend, but don't show up on the device.
    If I change one of those historical sales orders in the backend, it gets sent to the device.
    If I create a new sales order in the backend or on the device, it is saved and replicated just fine.
    To sum it up, it seems DOE is unable to identify the sales orders relevant for replication.

    First Doubt i got clarify by my self as we can go with Unwired Runtime option .
    But i still have doubt in :
    2. How can i Modifying the Main Menu for iOS.
    i am able to customize the same for windows using files SybaseCRM.Configuration.xml file.
    Same how can i do for iphone/ipad.

  • Issues with 0PP_C03 delta loads

    Hi,
    I loaded the data from 2LIS_04_P_ARBPL & 0PP_WCCP to 0PP_C03. Initialization of the data load went fine. Did the delta loads to BI and observed that I am not getting any of the Key figure data in the cube. All the values are showing as Zero.
    When I observed the in the PSA table and in the RSA3 , I observed that for every order 2 entries got created, One is with +ve values and another with u2013ve. So at the end while updating to cube its nullifying the values. Because of this reason I am not able to view the latest data which is updated as Deltas.
    I am not sure what settings I missed. Could some one please help me to fix this issue.
    Thanks & Regards,
    Shanthi.

    Thanks Francisco Milan and Shilpa for the links. Itu2019s very useful. But still I didnu2019t able to find the cause of the issue.
    My data source 2LIS_04_P_ARBPL is of ABR type and the update mode for KF is Summation. In the data source level, I am getting the values with before & after image (same entries one with +ve & another with u2013ve) and as I am using the u201CSummation as my update type for KF its getting nullified.
    Because of this reason I could not able to get the values in my report. Could any one pls help me on this as I am reaching the go-live date. I need to address this issue immediately. Thanks for all your inputs.
    Regards,
    Shanthi.

  • Table on delta loads from data mart

    Hi,
    I am loading data from two DSO's (let's call them A and B) to another DSO (B) in BI 7 with a BW3.5 delta infopackage.
    Now I want to know where I can find information on the timestamp or last request from the last delta load from A and B to C.
    So in fact I would like to know how the system knows which requests in A en B have not been loaded to C yet at the next delta load.
    In which table can I find the information for ODS A and B that is used by the system to define what data in the change log has been loaded or not to ODS C or other targets. (In fact I should have a comparison table in BW as ROOS* in R3)
    Thanks in advance!
    Kind regards,
    Bart

    Hi Guys,
    Thanks for the answers.
    I know how to check everything in the Workbench, but I want to know where the information of the delta is stored technically.
    Just for the sake of completeness:
    Due to some issues; several successive loads from A and B were correctly loaded into DSO C (the 'new' table), but could not be activated. It is not possible to do a repeat or anything else. I am not going into too much detail, but just take this for granted.
    The only way we can 'solve' the problem is to make the system believe that the 3 last loads (activated data) in A and the two last loads in B have not been loaded to C yet. Just deleting the last delta's in C and do a new delta from A and B to C will not work.
    Therefore I want to 'manipulate' the table that is being read by a delta load. If I can change the timestamp or request numbers in that table, I can make the system believe that some requests have not been loaded to C yet.
    Dirty, but it should work I think. But I am still figuring out what table contains information about the datamart data source (8A and 8B) and the last delta load to the targets.
    Hope this is more clear.
    Thanks in advance!
    Kind regards,
    Bart

  • Delta load after upgrade to 2004s - Functional changes

    Hi All,
    I have some doubts about Delta using DTP.
    Our BI landscape has been upgraded to 2004s from 3.1 (technical upgrade). There are many existing delta loads and we cannot afford to mess anything at all. So my question to you all
    When we do a functional upgrade...
    1. The existing delta from 0FIL_GL_4, AP_4, AR_4, WBS_6, NWA_2 etc all having delta loads right now and go to DSO. The records are in many millions. It is highly unlikely they will allow me to delete the PSA and reload all, because it will take couple of months. So that is out of the question.
    We have 3 situations.
    1. Delta from Data Source into DSO.
    2. Delta from DSO to Cubes
    3. Delete from few Cube to Cube.
    Questions
    1. After converting from Info Package to DTP I will still load the delta from Data Source to PSA, but the data source need to migrated to 2004s. WIll it cause any issues in loading delta data?.
    2. The DSO to further targets are using delta info package, I believe I change the info package to DTP with load mode selected as DELTA. Is this correct?
    Thanks in advance.
    Alex.

    DTP is used to load data only from PSA to Datatargets and DELTA DTP Loads the last PSA request which was transferred to PSA from source.
    So 2 plausible ways could be -
    1)Delete all PSA data and so your DELTA DTP will get the DELTA load only or new changed posted to PSA only and not all the previous requests ..but you may not want to delete the PSA now.
    2)Fake the DTP using some infoobject FILTER selection criteria as blank which acts like INIT w/t data transfer and then do DELTA DTP as mentioned below -
    https://forums.sdn.sap.com/click.jspa?searchID=10026965&messageID=4743634
    1. After converting from Info Package to DTP I will still load the delta from Data Source to PSA, but the data source need to migrated to 2004s. WIll it cause any issues in loading delta data?.
    NO
    2. The DSO to further targets are using delta info package, I believe I change the info package to DTP with load mode selected as DELTA. Is this correct?
    YES
    Hope it Helps
    Chetan
    @CP..

  • 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

  • Re: Delta Load for master attribute CUSTOMER

    Dear All,
    I have got the delta loading into 0customer_attr and 0 material_attr in production. Yesterday the load failed because the previous change run run has been terminated and locked the attributes of characterstics 0 material and 0customer.
    To solve this i went back and ran the attribute change run and all the locks got released.
    Now i know that i need to repaeat the delta load.
    If we go to the RSMO for the failed load i see that under details tab in processin option we have as follows
    Transfer rules(67-->67 records):No errors(This is Green)
       Master data received:Processing being started(Green)
       Transfer 67 data records in communication structure(Green)
    This is where the processing stopped.
    Update(0new/0changed)(in red): Errors occured
    My doubt is if i now repeat the load in process chain will the 67 records come into the0customer infoobject.
    Will this have any impact on the next day  delta load.
    Kindly advice.
    Regards
    Madhuri

    Hi abhijit,
    When i tried to do a repeat delta  the load failed again and when i check  for the error message i get the following
    Diagnosis
        The application program for the extraction of the data was called using
        update mode R . However, this is not supported by the InfoSource.
    System Response
        The data extraction is terminated.
    Procedure
        Check for relevant OSS Notes, or send a problem message of your own.
    Procedure for System Administration
    How do i proceed further.
    Regards
    Madhuri

  • How to achieve Delta Loads

    Hi All,
    Can any one throw some light on how to achieve initial and delta loads having cleansing and Matching records?
    Many Thanks
    Rajeev

    Hi All,
    Can any one throw some light on how to achieve initial and delta loads having cleansing and Matching records?
    Many Thanks
    Rajeev

  • No initial load of Customers, Material and delta load of Sales Orders.

    Hi Experts,
    I am facing a very troublesome issue. I am not able to setup the Middleware portion for initial and delta loads. I read a lot of documents and corrected a lot of things. finally, the connectivity is done with R/3 and CRM. Initial load of all objects is successful (as per Best PRactices guide). Customizing load is successful.
    But after now I have these open issues for which I am unable to find any answers (am really exhausted!!):
    - Customer_main load, it was succesful, but no BP's of R/3 are available.
    - Material, it failed in SMW01, SMQ2, the errors are:
    Mat. for Initial Download: Function table not supported
    EAN xxxxxxxxxxxxxxxxxx does not correspond to the GTIN format and cannot be transferred
    EAN yyyyyyyyyyyyyyyyyy does not correspond to the GTIN format and cannot be transferred
    Plant xx is not assigned to a business partner
    - Sales order, it shows green bdoc, but error segments says "No upload to R/3" and the order does not flow to R/3.
    We had our system setup 3 years back for data transfer and Middleware. But few things changed and connectivity stopped. I did all that again now, but am not yet successful. Any inputs will be greatly appreciated.
    Thanks,
    -Pat

    Hi Ashvin,
    The error messages in SMW01 for MAterial initial load is :
         Mat. for Initial Download: Function table not supported
         EAN 123456789000562 does not correspond to the GTIN format and cannot be transferred
         EAN 900033056531434 does not correspond to the GTIN format and cannot be transferred
         Plant 21 is not assigned to a business partner
    I have done the DNL_PLANT load successfully. Why then the plant error?
    Some of the messages for BP:
    Messages for business partner 1331:
    No classification is assigned to business partner 1331
    For another,
         Partner 00001872(469206A60E5F61C6E10000009F70045E): the following errors occurred
         City Atlanta does not exist in country US
         Time zone EST_NA does not exist
         You are not allowed to enter a tax jurisdiction code for country US
         Validation error occurred: Module CRM_BUPA_MAIN_VAL, BDoc type BUPA_MAIN.
    Now, the time zone EST is assigned by default in R/3. Where do I change that? I do not want to change time zones as this may have other impacts. Maybe CRM I cna change this, not for sure in R/3. City check has been deactivated in R/3 and CRM, still the error.
    Till these 2 are not solved, I cannot go into the Sales order loads.
    Any ideas will be greatly appreciated.
    Thanks,
    -Pat

  • Delta loading and Process chain BI

    Hi experts,
    Two Issues.
    1)As i am loading FI data into dso through a process chain which includes Start process>Delta infopackage(which gets data upto psa)>Delta dtp-->Datastore activation.
    But infopackage is picking up deltas but DTP is picking up all the previous records plus deltas.
    100 records  -- 1st day throught Intialization of Delta with Data Transfer
    2 delta records  --   2nd day
    But DTP is picking up 102 Records on the 2nd Day, which means it is also  picking the old records as well.
    The DSO must have just 102 records but it is having 202 records.
    2) A process chain in running daily as scheduled , but I rescheduled with new scheduling options without deactivating the Process chain.
    My Question is
    Will the Process chain run for the OLD and the New Schedule or
    Is it going to run for new schedule or old one?
    or
    will I face any Problem because I did not deactivate and made changes to the Change.
    Please help me in this matter.
    Thanks in advance.
    Bhadri.

    First query:
    I believe that u have used FUll update type DTP is instead of the Delta DTP.. Please cross check the Update mode of the DTP once.
    To resolve this issue, delete the total content of the DSO as u have Init and delta loads in PSA. And then using the Delta DTP of the Process chain, load the data. It will extract the total cotent what ever is there in PSA, and later the same DTP will act as the Delta type  and will pick the data from the New request of the PSA.
    Second Query:
    Its always suggested to deschedule the process chain before changing the schedule timings. When ever u do this type of scheduling, just check how many number of JObs available in Schedule mode, if u can see more than one, then delete the older one and keep the new one as it is.
    But I always suggest you to deschedule the process chain and reschedule  PC with the new timings and then activate the same.
    Thanks
    Assign points if this helps

  • Can we use both 0FI_AP_3 and 0FI_AP_4 for Delta Loads at the same time.....

    Hi Gurus:
    Currently my company uses 0FI_AP_3 for some A/P reporting. It has been heavily customized & uses Delta loading. However, SAP recommends the use of "0FI_AP_4" for A/P data fro delta loads. I was able to Activate 0FI_AP_4 as well & do some Full Loads in Dev/Test boxes. Question is whether I can use both the extractors for "Delta" loads at the same time......? If there are any issue, what is the issue and how ccan I resolve it? Is the use of only one extractor recommended......??
    Please let me know as this impacts a lot of my development....! Thanks....
    Best...... ShruMaa
    PS:  I had posted this in "BI Extractors" forum but there has been no response......  Hope to get some response.......!  Thanks

    Hi,
    I would recommend you to use 0FI_AP_4 rather using both, particularly for many reasons -
    1. DS: 0FI_AP_4  replaces DataSource 0FI_AP_3 and still uses the same extraction structure. For more details refer to the OSS note 410797.
    2. You can run the 0FI_AP_4 independent of any other FI datasources like 0FI_AR_4 and 0FI_GL_4 or even 0FI_GL_14. For more details refer to the OSS note: 551044.
    3. Map the 0FI_AP_4 to DSO: 0FIAP_O03 (or create a Z one as per your requirement).
    4. Load the same to a InfoCube (0FIAP_C03).
    Hope this helps.
    Thanks.
    Nazeer

  • Loading through Process Chains 2 Delta Loads and 1 Full Load (ODS to Cube).

    Dear All,
    I am loading through Process chains with 2 Delta Loads and 1 Full load from ODS to Cube in 3.5. Am in the development process.
    My loading process is:
    Start - 2 Delta Loads - 1 Full Load - ODS Activation - Delete Index - Further Update - Delete overlapping requests from infocube - Creating Index.
    My question is:
    When am loading for the first am getting some data and for the next load i should get as Zero as there is no data for the next load but am getting same no of records for the next load. May be it is taking data from full upload, i guess. Please, guide me.
    Krishna.

    Hi,
    The reason you are getting the same no. of records is as you said (Full load), after running the delta you got all the changed records but after those two delta's again you have a full load step which will pick whole of the data all over again.
    The reason you are getting same no. of records is:
    1> You are running the chain for the first time.
    2> You ran this delta ip's for the first time, as such while initializing these deltas you might have choosen "Initialization without data transfer", as such now when you ran these deltas for the first time they picked whole of the data.Running a full load after that will also pick the same no. of records too.
    If the two delats you are talking are one after another then is say u got the data because of some changes, since you are loading for a single ods to a cube both your delta and full will pick same "For the first time " during data marting, for they have the same data source(ODS).
    Hope fully this will serve your purpose and will be expedite.
    Thax & Regards
    Vaibhave Sharma
    Edited by: Vaibhave Sharma on Sep 3, 2008 10:28 PM

  • ALE and IDOC Delta loads

    ALE Delta is used for all Master data delta extracts and referencing change pointer tables
    IDOC Delta Loads are used for transactional delta and access source system queues
    Are the above statements correct? Thanks

    Nitesh
    As you know there are two types of Transfer Methods (PSA & IDOC). Info Idoc are used for both the types of Transfer Methods. Only ALE is used to transfer InfoIDocs.
    The Transfer Method only determine how the data is transfered.
    IN PSA Transfer Method Trfc is used to transfer data directly from Source system to BW.
    Thanks
    Sat

Maybe you are looking for