Export DS to temp. ODS. Transferred records?

Hello,
When I transfer data from one ODS to a copy to this ODS via export DataSource I do not get the same number of records in my "temp." ODS like in my "actual" ODS.
(E.g. actual ODS = 57666 transferred records; temp. ODS = 56.285 transferred records)
Thanks for explanation.

Hello Roberto,
I checked the tables (from both ODS Objects). Both got in the active the same number of records (56.285).
So the conclusion is that it is uninteresting how many records are transfered. Interesting is how many records are in the active table?
But nevertheless. Thanks for help.
CHEERS!

Similar Messages

  • Manage ODS : Difference of Transferred Records and Added Records

    Hi there,
      When I click on Manage ODS , I have the following fields
      Transferred Records and Added Records.
      Please advice the difference

    Hi,
    Transferred Record coloumn indicated how many records were tranferred from the source system to BW,means how many records were extracted at that point of time and another Column indicates that the total number of records added to your data target.these two cloumn vales may not be same for all the time,becoz if you have filters at the update rule level....in this case numbers records tranfered and numbers records added might be different.......
    Transferred refers to the number of records that are transferred from the datasource (arrive in BW). Added is the number records inserted into the ODS. Both can be different numbers, like due to any processing of the data.
    Added records refer to which is really inserted in ODS (your start routine, for example, can reduce the number of transferred records by deleting something!)
    Ex
    transferred records means the total records from source e.g ods. say data coming from ods
    docnumber docitem customer qty
    001 1 x 10
    001 2 y 20
    002 1 x 30 (3 records)
    and your infocube has char customer and keyfigure qty, so
    record added
    customer qty
    x 40
    y 20 (2 records)
    so here you have transferred records = 3 and added records = 2
    Refer these posts:
    Re: transferred records and added records
    Re: Transfered and Added Records
    Re: Clarification about ODS - Transferred & Added records
    -Shreya

  • What's the difference between Transferred Records and Added Records?

    When right click an ODS or a cube to select Manage, then under the 3rd tab called Requests, there are two columns called Transferred Records and Added Records, what's the difference between these two?
    Thanks

    Hello KeLviN,
    How r u ?
    Consider a realtime example.
    Assume a transfer of Transactional Data from R/3(with PSA) which is having Unit values in it.
    Now, I found in RSA3 2844168 of records. In BW I saw one Data Packet with 306 error records(because of a UNIT value is not available in BW T006 table, Eg. YDD) which are automatically collected in PSA. Now in the Monitor screen you could see 2 Monitor status with GREEN Signals for 2 set of data.
    1. with 2843862 records
    2. with 306 records
    Now, if u manage the Data Target you will get 2844168 in the Transferred Records & 2843862 in the Added Records. and the 306 error records are in the PSA.
    Hope this is clear.
    Best Regards....
    Sankar Kumar
    +91 98403 47141

  • Whats the diff between Transfered Records and Added Records

    Hi
    whats the diff between Transfered Records and Added Records in any data target Request Tab.
    Regards
    ll

    Hi.......
    Check this.......
    What's the difference between Transferred Records and Added Records?
    Manage ODS : Difference of Transferred Records and Added Records
    Regards,
    Debjani......

  • Difference i transfered records and added records

    Hi friends,
    I have loaded data into ODS and it was succesful,but when i check in the Requests tab in mangae i found that number of records transferd is 4000 but number of records added is just 1401. can anyone please advise me where ami going wrong.
    Regards
    Ananth

    Hi,
    The reason they could be different for an ODS is because in an ODS the record is identified based on the key fields.
    For example
    If I have GL posting document wherein the Posting document no. is the key field in the ODS. I may have modified the same GL posting document in R/3 for 6 times but wben it is uploaded into an ODS it will just contain one record for the final staus of the GL posting document.
    So in this case even if 6 records are transferred, only one record will be added to the ODS.
    As a result it is not always necessary that there might always be something wrong when the transferred and added records are different.
    But for ODS it is important that the key field is correctly identified, if that is not the case you might have records being overwritten (transferred records more than added records) which might be wrong.
    So I would suggest you to check the Key fields, and if your totals match with R/3 or the source data.
    Hope it helps
    Cheers
    Anurag

  • Difference in Transfered Records and Added Records

    Hello All,
    I did the delta load of my Sales Orders and Items for the first time. The load is successful but when I see in the Manage Screen of the ODS, I noticed that the number of the Transfered records and the Added Records are different i.e for ex: the Transfered records are 4 and the added records are 2.
    Why is this happening? Is this because I miss something?
    Rgds,
    Sharath.

    Hi Sharath,
    As manga said it might due to transformations - update / tranfer rules.
    Another reason would be the key of ODS for eg: if the extractor is pulling based on say three key fields from the base table say  A B C and if you defined only A B as the key in ODS  then these gets overritten
    Hope this helps
    Thanks,
    Raj

  • Data Load - Added & Transferred Record Miss Match

    Hi to all,
    I am loading data R/3 -> infoCube in 3.x, I can see that too much difference between Transferred and Added Record , Ex Transferred record -> 5032704 & Added record -> 3505696.
    I have checked there is no routine has been written .
    In Selection I have given a range for Object No.
    For 10000 to 99999 Object No Transferred and Added record is same.
    But KSM100 to KSM999 I am getting difference between added and transferred record.
    Please any one help me .
    Thanks in advance
    shalini

    Not all the times would the records would get added to your fact table. You may write an update rule for "not to update certain records". In such cases you may find the transfered and added records different. Another instance could be when you split the incoming record into 2 records in the update rules. In such an instance the no. of added records would be greater than transfered records.
    Re: difference i transfered records and added records
    Re: manage infocube

  • No.of transferred records do not match with delta records in RSA7

    Hi,
    The full update was failing since a number of days in 0vendor because of error in the source system. So I did an initialize with data transfer and corrected the PSA data and updated it using scheduler in the infoobject. In this case the number of transferred records was 24300 and added records was 0.Next I executed the delta infopackage and was expecting 0 records,since there were 0 records in rsa7. But I got 16000 records.Can you explain me why this happened?
    Regards,
    Shalaka

    Hi Shalaka,
    In which version of SAP you are working?
    You might want to have a look at the table BDCP2 which is a different table that handles the delta mechanism for the change pointers.
    You can reset the processing status using the program RSA1BDCP ex with following entries.
    Now, coming to your issue - to verify the initial loads I am listing some basic checks(step by step).
    You can give it a try in Dev/QAS if you have any restrictions in Prod.
    1. Check and verify if the RSA7 delta queue is present.
    2. In BW system, delete the INITIALIZATION request from infopackage - This should delete the delta queue from RSA7 in ECC system. (I am not 100% sure about this so try this once)
    3. Re-initialize the datasource from BW system and note the no. of incoming records in BW. This should match with LFA1 entries.
    4. Check the delta queue in RSA7 - There should be a new delta queue created
    5. Start the Delta load - The should not be any records coming in to BW
    6. Check the entries in table BDCP2 and its process indicator.
    7. Create a new vendor from XK01 and check the entry again in BDCP2 table.
    8. Run the delta again in BW and this time delta should have the newly created vendor.
    Also be aware that since its a master data datasource and deals with change pointers you will not see any entries in RSA7.
    A possible reason I could think of you getting 16000 records in delta is because you might have initialize the datasource is past and then started the FULL loads. So the deltas actually started accumulated in BDCP2 with processing status as BLANK and then when you triggered delta again back now all the historical deltas are processed.
    This apply with BDCPV too if you are on older version of SAP.
    Did you tried running delta's multiple times - you should not face any delta records when the processing status of change pointers is set to 'Processed' i.e. 'X'.
    PS: You can find the message type for 0VENDOR_ATTR in ROOSGEN table. This will be useful in looking at table BDCP2.
    Please let me know if there are any questions.
    Thanks
    Amit

  • Transferred Records 5463 but Added Records 0

    Hi Experts,
    My current project is CRM BI implementation. I am trying to load in 0BPARTNER Master data and DataSource 0BPARTNER_ATTR is enhanced by 44 customed attributes and it is 3.X DataSource. So, I created 44 InfoObjects, added those InfoObjects as an Attributes of 0BPARTNER. I created InfoSource, InfoPackage and Update Rule accordingly. I got data in PSA. But in DataTarget, I saw transferred records and no added records. Where should I troubleshoots and please tell me steps. Thank you.
    Md

    Md,
    The behaviour is perfectly fine. As its master data, 0BPARTNER already has the master data entries (primary keys in the P table). Only attributes to the same record have been added through the enhancement you have done.
    Please check that the attributes are filled in as you'd expect.
    In the scenario that BP was not loaded before and you load master data, you can see a > 0 figure for added records in manage screen as well.
    Hope this helps.
    Regards,
    Ashu

  • Why can I have a difference between Transferred Records and Added Records

    Hello gurus,
    What could be the reason for the difference between the Transferred records and the added records in the request for an InfoObjects?
    I have in RSA3 6452 Records and in the Manage-InfoObject 1002 Records.
    thanks for your help

    - already existing master data (changed but not new)
    - start routine with deletion
    - duplicate records (with error handling activated)
    - end routine

  • Added records and transferred records

    What is the difference between "transferred records" and "added records" in Infocube-> manage->requests ??
    Karthik

    Hi Karthik,
    You may have 2 records in the source data with same characteristic values. Then these two will be sumarized and added as a single record.
    say suppose:
    C01   M01   100   200
    C01   M02   200   400
    Now only one record is added to Infocube
    C01   M01   300   600
    -> When there are multiple records with in a same request with same characteristic combinations, They will be summarized while updated to Cube.
    In the above case: No. transferred records = 2
    No. Records Added = 1  
    In this kind of scenarios... Always No. transferred records will be more or equal to Added records.
    Some scenarios like where You split records into multiple records using Time distribution or return table... Example: You have monthly revenues in a flat file. But you want to split them into weekly records(based on averege model) and load to Cube. In this kind of scenarios the Added records will be more that Transferred records.
    So-> Dont expect the added records = Transferred records always.
    Hope this helps.
    Suman
    Message was edited by: suman kumar
    Message was edited by: suman kumar

  • Transferred records vs Added records

    Hi all,
    i've understood the differences between two fields shown in "Manage Data Target", then TAB "Request.These are the fields:
    - "transferred records";
    - "added records".
    Could you please help me on this?
    Thanks in advance,
    Federico

    Hi Federico,
    Please try to search the forums:
    Transferred and Added records
    transferred records and added records
    Hope this helps...

  • Difference between Transferred Records and Added records

    Hi,
    I am loading data into infocube ZPT_C01, a copy of 0PT_C01. In the "Manage function", under "Requests", I see two columns. One that says Transferred Records: 271370 and the other Added records: 30320.
    I understand that 271370 is the number of records in the PSA. Is 30320 the number of records added to the Infocube?
    Why aren't those two numbers identical? Are records lost? Can someone explain to me why the two record numers aren't the same?
    Thanks in advance
    Michalis

    Hi,
    the collapsing of a request is usually done when its data has been judged "correct" since a collapsed request cannot be deleted from an InfoCube.
    Now in your case, it seems that you are always having one request in your ICube and you systematically delete the datatarget content prior loading it; you could collapse your request or not. If you collapse it you might get less records in your E fact table with the corresponding increase of query runtime; however if the ratio #records collapsed (in E table) / #records collapsed (in F table) is close to 100%, you most probably don't need to collapse this request.
    In your scenario you have to be careful with the dimension tables; indeed when you delete the cube content via a chain, the dimension tables won't be deleted (that's good since when the next request will come the system won't have to recreate all the DIMIDs already present) and after a while many of these DIMIDs will perhaps not be used (you can run the corresponding RSRV check to verify this)...
    hope this helps...
    Olivier.

  • Transferred records and added records

    in Cube manager, I see the number of transferred records and added records in each request are always different.
    what's the exactly means of those two field ?  I guess added records is record loaded into cube without any duplicated, right?

    Hi Jie,
    Refer these links:
    Re: difference i transfered records and added records
    Re: manage infocube
    Bye
    Dinesh

  • Ods-  0 Record mode

    Hi friends,
    In ods we are adding 0Recordmode .am i right?can u tell me is it compulsory to add 0recordmode for ods?what does it do?
    thanks
    mano

    Hi Mano,
    Most of the time the system by itself would the 0recordmode. The 0recordmode is most useful in the delta loads from the ODS to another ODS/Cube.
    You would find lots of posts on the 0recordmode in this forum.
    <u><b>From SAPhelp:</b></u>
    RECORDMODE
    Definition
    This attribute describes how a record in the delta process is updated. The various delta processes differ in that they each only support a subset of the seven possible characteristic values. If a Data Source implements a delta process that uses several characteristic values, the record mode must be a part of the extract structure and the name of the corresponding filed must be entered in the Data Source as a cancellation field (ROOSOURCE-INVFIELD).
    The seven characteristic values are as follows:
    <b>' ':</b> The record delivers an after image.
    The status is transferred after something is changed or added. You can only update the record straight to an Info Cube if the corresponding before image exists in the request.
    <b>'X':</b> The record delivers a before image
    The status is transferred before data is changed or deleted.
    All record attributes that can be aggregated have to be transferred with a reverse +/- sign. The reversal of the sign is carried out either by the extractor (default) or the Service API. In this case, the indicator 'Field is inverted in the cancellation field' must be set for the relevant extraction structure field in the Data Source.
    These records are ignored if the update is a non-additive update of an ODS object.
    The before image is complementary to the after image.
    <b>'A':</b> The record delivers an additive image.
    For attributes that can be aggregated, only the change is transferred. For attributes that cannot be aggregated, the status after a record has been changed or created is transferred. This record can replace an after image and a before image if there are no non-aggregation attributes or if these cannot be changed. You can update the record into an Info Cube without restriction, but this requires an additive update into an ODS Object.
    <b>'D':</b> The record has to be deleted.
    Only the key is transferred. This record (and its Data Source) can only be updated into an ODS Object.
    <b>'R':</b> The record delivers a reverse image.
    The content of this record is the same as the content of a before image. The only difference is with an ODS object update: Existing records with the same key are deleted.
    <b>'N':</b> The record delivers a new image.
    The content of this record is the same as for an after image without a before image. When a record is created, a  new image is transferred instead of an after image.
    The new image is complementary to the reverse image.
    <b>'Y':</b> The record is an update image.
    This kind of record is used in the change log of an ODS object in order to save the value from the update. This is for a possible rollback and roll- forward for key figures with minimum or maximum aggregation. This record also has the update value for characteristics (in this case, it is the same as the after image). Null values are stored for key figures with totals aggregation. An update image is only required when the value from the update is smaller or larger than the before image for at least one key figure with minimum or maximum aggregation.
    The table RODELTAM determines which characteristic values a delta process uses (columns UPDM_NIM, UPDM_BIM UPDM_AIM, PDM_ADD UPDM_DEL and UPDM_RIM). The table ensures that only useful combinations of the above values are used within a delta process.
    When extracting in the 'delta' update mode in the extracted records for the record mode, a Data Source that uses a delta process can deliver only those characteristic values that are specified in the delta process.
    Hope this helps.
    Bye
    Dinesh
    Message was edited by: Dinesh Lalchand

Maybe you are looking for