WHAT IS SAFETY DELTA IN COPA

Hi Gurus,
WHAT IS SAFETY DELTA IN COPA?
Help me.
Regards,RAMU.

Hi,
Safety Delta
The delta method relies on a time stamp which is contained in each line item, record in the
segment level and summarization level. This time stamp makes it possible for the system to
decide which line items are already contained in the summarization level. However, if you are
using more than one computer (database/application servers), these could show a slight
difference in their system times. The system can correct inaccuracies of up to half an hour by
ignoring any postings made in the last half hour.
Refer Page 375
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/COPA/COPA.pdf
Hope this helps.
Thanks,
JituK

Similar Messages

  • What is safety delta time

    Hi Experts
    Can any one please explain me
    What is safety delta time in terms of delta data source
    Thanks

    Hi,
    Safety Interval Upper Limit of Delta Selection
    This field is used by DataSources that determine their delta generically using a repetitively-increasing field in the extract structure.
    The field contains the discrepancy between the current maximum when the delta or delta init extraction took place and the data that has actually been read.
    Leaving the value blank increases the risk that the system could not extract records arising during extraction.
    Example: A time stamp is used to determine the delta. The time stamp that was last read is 12:00:00. The next delta extraction begins at 12:40:00. In this case, the selection interval is 12:00:00 to 12:40:00. At the end of extraction, the pointer is set to 12:40:00.
    A record - for example, a document- is created at 12:40 but not saved until 12:40. It is not contained in the extracted data but, because of its time stamp, is not extracted the next time either.
    For this reason, the safety margin between read and transferred data must always be larger than the maximum length of time that it takes to create a record for this DataSource (with a time stamp delta), or it must display an interval that is sufficiently large (for determining delta using a serial number).
    Safety Interval Lower Limit
    This field contains the value taken from the highest value of the previous delta extraction to determine the lowest value of the time stamp for the next delta extraction.
    For example: A time stamp is used to determine a delta. The extracted data is master data: The system only transfers after-images that overwrite the status in the BW. Therefore, a record can be extracted into the BW for such data without any problems.
    Taking this into account, the current time stamp can always be used as the upper limit when extracting: The lower limit of the next extraction is not seamlessly joined to the upper limit of the last extraction. Instead, its value is the same as this upper limit minus a safety margin. This safety margin needs to be big enough to contain all values in the extraction which already had a time stamp when the last extraction was carried out but which were not read. Not surprisingly, records can be transferred twice. However, for the reasons above, this is unavoidable.
    these are used to determining the delta in a datasource:
    1. Time stamp - The field is a DEC15 field which always contains the time stamp of the last change to a record in the local time format.
    2. Calendar day - The field is a DATS8 field which always contains the day
    check the thread:
    safety intervels in genric delta extraction.?
    Sriram

  • What is safety delta?

    what is safety delta?

    From How to create Generic delta doc:
    If delta field is Date (Record Create Date or change date), then use Upper Limit of 1 day & leave Lower limit blank.This will load Delta in BW as of yesterday.
    If delta field is Time Stamp, then use Upper Limit of equal to 1800 Seconds (30 minutes).This will load Delta in BW as of 30 minutes old. Leave Lower limit blank.
    If delta field is a Numeric Pointer i.e. generated record # like in GLPCA table, then use Lower Limit. Use count 10-100. Leave upper limit blank. If value 10 is used then last 10 records will be loaded again. If a record is created when load was running, those records may get lost. To prevent this situation, lower limit can be used to backup the starting sequence number. This may result in some records being processed more than once; therefore, be sure this DataSources is only feeding an ODS Object already extracted to be extracted in the next run last extraction today
    refer:
    Re: Doubt on Generic DataSource

  • What are the delta mechanisms and tables used for  Lo Extraction & COPA

    Hi all
    what are the delta mechanisms and tables used for  Lo Extraction & COPA.
    please explain clealry.
    Thanks & Regards,
    James

    James,
    Please go through Roberto's weblog :
    /people/sap.user72/blog/2005/02/14/logistic-cockpit--when-you-need-more--first-option-enhance-it
    Anyways,
    As you know LO cockpit consists of different modules(MM, PP, SD, etc)
    They are called appl components. Each of them have a number (eg.MM=02) and for each appl comp they might be different Data sources and for each DS they might be different tables. So, unless you be specific we cant tell a specific table for a DS.
    coming to the delta mechanisms, there are " direct delta, queqed delta and serialized delta".
    Copa is based on the oepration concern. it can be created on " accouting based" or "costing based".
    Assign points if helpful
    Kalyan

  • What is safty delta and safety interval

    Hello,
            PLease tell me What is mean by Safety Delta and Safety Interval?

    Hi,
    Safety interval should be set so that no document is missed – even if it was not stored in the DB table when the extraction took place.
    Example for Determining Selection Intervals with a Generic Delta:
    1. If delta field is Date (Record Create Date or change date), then use Upper Limit of 1 day.
    This will load Delta in BW as of yesterday. Leave Lower limit blank.
    2. If delta field is Time Stamp, then use Upper Limit of equal to 1800 Seconds (30 minutes).
    This will load Delta in BW as of 30 minutes old. Leave Lower limit blank.
    3. If delta field is a Numeric Pointer i.e. generated record # like in GLPCA table, then use Lower Limit. Use count 10-100. Leave upper limit blank. If value 10 is used then last 10 records will be loaded again. If a record is created when load was running, those records may get lost.
    To prevent this situation, lower limit can be used to backup the starting sequence number. This may result in some records being processed more than once; therefore, be sure this DataSources is only feeding an ODS Object
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/84bf4d68-0601-0010-13b5-b062adbb3e33
    Assign points if this is needful.
    Rgs,
    I.R.K

  • How to change safety interval in COPA extractor

    Hi, guys!
    I had a problem with changing safety interval in COPA extractor. I created COPA datasource using keb0. In RSA2 it can only view security interval. It is 1800 sec by default. I cannot change it.
    How can I change it? I cant do it in RSO2, because it is not true generic delta.
    Note 808663 is not implemented (we have higher patch on R/3). Delta extraction is correct, but safety interval is very annoying
    Please help.
    Message was edited by: Emerald

    Thanks. I'll try to.
    I thought I should edit ROOSOURCE, but it's maintainable in productive system.
    Should I reInit delta after corrections implementation?

  • What type of delta does LO run ?

    Hi.. I understand that in COPA extraction there are no migration steps involved as it runs on "time stamp delta". If that is the case then please let me know what type of delta does LO and LIS run... If even LO and LIS run on time stamp then please let me know why are there no migration steps involved in COPA...?

    Logistic's Area use's three Types of Delta Mechanism's :
    1. Direct Delta
    2. Queued Delta
    3. Un-serialized V3 Update
    These are different work processes on the application server that takes the update LUW (which may have various DB manipulation SQLs) from the running program and execute it. These are separated to optimize transaction processing capabilities.
    Taking an example -
    If you create/change a purchase order (me21n/me22n), when you press 'SAVE' and see a success message (PO.... changed..), the update to underlying tables EKKO/EKPO has happened (before you saw the message). This update was executed in the V1 work process.
    There are some statistics collecting tables in the system which can capture data for reporting. For example, LIS table S012 stores purchasing data (it is the same data as EKKO/EKPO stored redundantly, but in a different structure to optimize reporting). Now, these tables are updated with the txn you just posted, in a V2 process. Depending on system load, this may happen a few seconds later (after you saw the success message). You can see V1/V2/V3 queues in SM12 or SM13.
    In a local update, the update program is run by the same work process that processed the request. The dialog user has to wait for the update to finish before entering further data. This kind of update is useful when you want to reduce the amount of access to the database. The disadvantage of local updates is their parallel nature. The updates can be processed by many different work processes, unlike asynchronous or synchronous update, where the update is serialized due to the fact that there are fewer update work processes (and maybe only one).

  • Realignment of delta in COPA ?

    Hi Gurus,
    What is Realignment of delta in COPA ?  In which Scenario we will go for this kind of delta ?
    I will assign points for your valuable answers.....

    Hi,
    Are you talking about changerun? If so, I could answer.
    ~Prem

  • Do any one willlet me know abt Safety Delta

    Hi All
    Do anyone let me know abt Safety Delta?What exactly it does I need concept of safety delta.How do it will be usefull and in which scenarios do we use this?
    Pls let meknow
    Regards
    Balji

    Hi,
    Safety delta for extraction from the CO-PA for the extraction out of the profitability analysis, a so-called 'Safety delta' is used for a half an hour during the initialization and delta upload. This means that only records that are already a half an hour old at the starting point of the upload are loaded into BW. You want to reduce this delta in order to have more current data available in the reporting.
    check this...
    Reagrading Safety delta

  • In Material Master Screen,functionally what is Safety time and safety time

    In Material Master Screen,functionally what is Safety time and safety time indicator in the MRP Screen.Pls explain its functionality

    Hi,
    The safety time / actual range of coverage ensures that the planned warehouse stock covers the requirements of a defined number of days. It therefore serves as a time float and thus works alongside the safety stock, which acts as quantity float.
    The system simulates bringing the requirements forward by the specified number of days and the planning for the receipts, created for these requirements in the planning run, is also brought forward by this number of days.
    Prerequisites
    ·   You have set the Safety Time indicator in the material master record (MRP 2 View) to define whether the safety time is only to apply to independent requirements or to all requirements.
    ·    In the material master record (MRP 2 View), in the Safety Time/Actual Range of Coverage field, you have entered the number of workdays by which the requirements are to be brought forward.
    ·    If, in addition to this actual range of coverage, you also want to define a different number of workdays in certain periods or a safety time less than one day then, in Customizing for MRP in the activity Define Period Profile for Safety Time/Actual Range of Coverage you can define a period profile and assign it to the material in the material master record.
    Regards,
    Vijay

  • What is a delta migration and is there any tool that support delta migration?

    Hi,
    We are migrating from MOSS 2007 to SharePoint 2013.
    What is a delta migration and is there any tool that supports delta migration...Please help me understand.

    hi
    there are many tools are availabe in market like DocAve,Metalogic-Content migration and Quest Migration
    so as per my experince Content Matrix is good to support all the feature while migration form Sharepoint 2007 and Sharepoint 2010 or Sharepoint 2013.
    See the below link
    http://www.metalogix.com/help/Content%20Matrix%20Console/SharePoint%20Edition/002_HowTo/003_MigrationActions/020_IncrementalCopying.htm
    Please mark the answer if this help full..

  • Working of deltas in copa and fisl

    hi gurus
                i am not able to understand the flow of data
    from r/3 to bw in copa and fisl.
    q1. when deltas data comes to rsa7 or not.
    if so from where data comes in fisl
    and copa
    q2.when i am doing deltas in copa  from which tables data is coming.
    q2.when i am doing deltas in fisl  from which tables data is coming.
    please send me the answer to my mail
    [email protected]
    i will assign full points

    Hi vishal,
    The question u posted is very general and indeed u need an understanding of underlying table and their contents and how the table contents are related to the Business process.. The best think i wud suggest you to look for is SAP course material related to Exraction it should be TBW30, or BW350 i believe. You can get a very clear idea of COPA and FISL extraction.. Sorry i dont have the material, but this is where u can look in to for a clear conceptual explanation.
    regards,
    kishore

  • What is reset delta.

    what is reset delta.

    Hello Satish this is used to restart delta from beginning. I mean deleting already loaded deltas and start from begining. Here is the procedure from help.sap.com
    Deleting Already Updated Data
    Use
    If you want to delete requests that have already been updated in connected data targets, you have to adjust the connected data targets manually.
    Procedure
           1.      In the administration of the data target, choose the tab page Requests. For your request to be deleted, choose  Data Mart Status for the Data Target. The following dialog box displays the request that was updated in additional data targets. Keep the description of this request in mind.
           2.      Choose  Monitor on this dialog box. You arrive at the monitor for this request.
           3.      Choose  Manage Data Targets. You arrive at the administration for the connected data targets.
           4.      Delete the respective request.
           5.      This takes you to the source ODS object administration screen.
           6.      Reset the delta administration. To do this, choose  Data Mart Status for the Data Target and from the subsequent dialog box, choose  Reset Delta Administration.
           7.      Now you can also delete the respective request from the source ODS object. You can now load data as full or data again.

  • WHAT IS GENERIC DELTA

    Please  explain me what is generic delta and how to create generic datasource for transaction data?

    Hi,
    Generic extraction
    Usage:
    1. When the standard extractors are not supporting the extraction what you need. If SAP does not have a standard extractor for your need to get data from R3, you would have to go for generic extractor.
    2. If you create a custom object say by combining certain base tables in R3 say custom tables ZTAB1 and ZTAB2. These two tables are not SAP provided tables and there will not be any standard extractors. So cases like this you will have to go for generic extractors.
    3. FI-SL requires generic extractors.
    How:
    You have to use RSO2 transaction and you can also set delta based on, one of the three characteristics such as timestamp, calday or pointer (a sequence no).
    once you create it and activate it. The extractor will be available in ROOSOURCE - (table in R3 where all the data sources are available).
    Steps
    Log on sap R/3.
    Step 1. create a table or view for generic extraction in se11.
    Step 2. Goto  t-code RSO2
    Step 3. Here u have to decide whether to extract transaction data or master data attributes or texts.
    Step 4. suppose if u have opted for transaction data,then give name in the column ex:ztd_m(data source name)
    Step 5. select create button,this will take u to another screen.
    Step 6. Here u have to decide from which application component u r extacting data.Ex: SD,MM,..
    Step 7. in this screen u have to fill short disciption,medium,long( these r mandatory).
    Step 8. then U have to Table name or view name which u have created in se11.
    Step 9. I f u want to maintain generic delta then u can select generic delta in top left hand side corner.
    Step 10. in next screen u have to give some field which is primary key.
    step 11. here u to specify whether time stamp or cal day or numeric pointer depending on u r requirement.
    step 12. then u have to specify  whether new status for changed records or additive delta.
            If u choose additive delta ,then u have to load data to infocube or ods object.
            If u choose new status for changed records, then u to load data  to ods object only.
    Step 13. then save it.
    Step 14. then logon to sap bw ,then replicate the data source then as usuall.
    Refer:
    /people/siegfried.szameitat/blog/2005/09/29/generic-extraction-via-function-module
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d3219af2-0c01-0010-71ac-db
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/84bf4d68-0601-0010-13b5-b0
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/84bf4d68-0601-0010-13b5-b0
    http://help.sap.com/saphelp_nw04/helpdata/en/3f/548c9ec754ee4d90188a4f108e0121/content.htm
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/84bf4d68-0601-0010-13b5-b062adbb3e33
    Thanks,
    JituK

  • How to set Delta for COPA Extraction

    Hi all,
    I want to do generic data source using Function Module for COPA can any one tell how to set the delta what fields i have to fill.
    thanks
    kavitha

    Hi kavitha,
    The easiest way to work out with Function Module is to copy the standard one and modify according to your reqirement.
    The standard one is RSAX_BIW_GET_DATA_SIMPLE .
    Dont forget to copy the Function grp RSAX into a custom defined Grp and Modify the Ranges options as per ur req.
    and in Function module, in Sourcecode and Tables, Do modify the E_T_data with ur Generic datasource ,make sure u also modify the select statements within the sourcecode. If you have an idea on ABAP its really easy to work out.
    And regarding the creation of Datasource.
    this blog may help for the same.
    Generic Extraction via Function Module
    Safety Interval Upper Limit of Delta Selection
    This field is used by DataSources that determine their delta generically using a repetitively-increasing field in the extract structure.
    The field contains the discrepancy between the current maximum when the delta or delta init extraction took place and the data that has actually been read.
    Leaving the value blank increases the risk that the system could not extract records arising during extraction.
    Example: A time stamp is used to determine the delta. The time stamp that was last read is 12:00:00. The next delta extraction begins at 12:30:00. In this case, the selection interval is 12:00:00 to 12:30:00. At the end of extraction, the pointer is set to 12:30:00.
    A record - for example, a document- is created at 12:25 but not saved until 12:35. It is not contained in the extracted data but, because of its time stamp, is not extracted the next time either.
    For this reason, the safety margin between read and transferred data must always be larger than the maximum length of time that it takes to create a record for this DataSource (with a time stamp delta), or it must display an interval that is sufficiently large (for determining delta using a serial number).
    Safety Interval Lower Limit
    This field contains the value taken from the highest value of the previous delta extraction to determine the lowest value of the time stamp for the next delta extraction.
    For example: A time stamp is used to determine a delta. The extracted data is master data: The system only transfers after-images that overwrite the status in the BW. Therefore, a record can be extracted into the BW for such data without any problems.
    Taking this into account, the current time stamp can always be used as the upper limit when extracting: The lower limit of the next extraction is not seamlessly joined to the upper limit of the last extraction. Instead, its value is the same as this upper limit minus a safety margin. This safety margin needs to be big enough to contain all values in the extraction which already had a time stamp when the last extraction was carried out but which were not read. Not surprisingly, records can be transferred twice. However, for the reasons above, this is unavoidable.
    these are used to determining the delta in a datasource:
    1. Time stamp - The field is a DEC15 field which always contains the time stamp of the last change to a record in the local time format.
    2. Calendar day - The field is a DATS8 field which always contains the day of the last change.
    3. Numerical pointer - The field contains another numerical pointer that appears with each new record .
    Regards,
    Anish

Maybe you are looking for