New status for changed records or Additive Delta

Hi Guys,
I have a design question for ODS and Extractor.
The requirement is as follows...
There is a table in CRM with service point as primary key. The fields in the table for example are bill account and Meter ID. Key figure is a XYZ value. In CRM for that Bill account Meter ID combination the XYZ value will change every year. In CRM the same record is being updated with changed value of XYZ. But in BW when the delta is being sent I do not want it to update the existing record but add it as  a new record. This way the history can be tracked for previous years XYZ value.
What is required to make this happen?
When creating the extractor I think I should give the delta as new status or additive delta?
What should I indicate as delta specified field?
For the ODS ( I am on BI 7.0) should I create the normal ODS or should I create the write Optimized or something for this requirement ( I dont remember right now the 3 types of ODS we can create).
Your inputs will be greatly appreciated.
Thanks
Kumar.

Thanks Puneet!
Good Answer.
New and Changed records does help in getting the records as desired.
But the problem is while loading into BW I cannot create a new record. The primary key is only Service Point. So even if the key figures and dates associated with that record changes, BW will still update my existing record.
Is there a possibility of using the dates as a pointer that a new record should be created.
Let me explain it better. Following is the structure of table.
Service Point (primary key)
Product GUID (key in CRM)
Circuit ID
Installation date
Effective date
Termination date
CRC (some key figure)
Scenario is - This year Service Point A with CRC value as 50 with effective and termination date for example .. May1 2009 - Apr 31 2010.
Service Point   CRC   EffectiveDate   TerminationDate
A                     50      5/1/2009         4/31/2010
Next year the same service point will have different values and CRM system will update the record in CRM table.
Service Point   CRC   EffectiveDate   TerminationDate
A                     60      5/1/2010         4/31/2011
1) So I was wondering if there is a way or some code can be written to check if effective and termination dates are not same it should be added to ODS as a new record.
2) Another way is to make some sort of Time dependency. Like use Valid From and Valid To dates to track the changes to the record and display all the different values for every record when the CRC values were valid between what dates.
3) or some other way you can suggest

Similar Messages

  • What is difference between additive delta and new status for change record

    Hi Experts
    Can any one explain me about the difference between additive delta and new status for change record with example
    if any one has a document please post it iam thank full to u
    thanks
    Ahmed
    Please search the forum before posting a thread
    Edited by: Pravender on Feb 12, 2012 1:54 PM

    Hi
    Additive delta --- We will get the changed quantity.
    say suppose you have sales order and quantity like  1111   30 which is loaded to cube(BW).
    now same record qty has changed from 30 to 40. As we have additive delta, we will get new record as 1111  10.
    new status for change record: This is same as like After image delta type in standard SAP data sources. for every change in record you should have new record.
    say if you have any number which will be generated by system for new/changed record, then you can use this.
    You can use this option when delta option set to "numeric pointer"
    Regards,
    Venkatesh

  • CProjects- Customizing New Status in "Change Status"

    I need to customize new status in "Change Status" drop down of cProjects tool. Now the status available are "Created, Released, Locked etc" as we all know. But i need to customize my own status for "Projects Phases and Tasks" I create. Can i do that. Please help me on the same. It is urgent.
    Edited by: Visvesh Ramanathan on Jan 10, 2008 4:00 PM

    Hi
    As Vivek already explained, you can have user status in bs02
    now here you can maintain the status as one maintains in R/3 or ECC
    create an auth Key in BS52 for status which needs approval
    maintain the same auth key in bs02 against status
    what you have to do is create a role using pfcg and assign that key in that role
    assign the role to user which ll approve the status to next status.
    Select object type which will give you the applicability of status profile.
    e.g the status profile is to be used for project / task / checklist etc etc...
    The user statusses are visible once you select the status in 3rd tab of project
    Niranjan
    Award points if useful

  • Process Status & Release Status for Condition Record

    Hi Gurus,
    Pls help me out in the the following scenario.
    I want to activate Authorization level check for Condition records.
    For example, Product price PR00 is being entered by first level.
    After verification done by second level only, that condition record to be used for sales order processing.
    I have gone through Process status & Release Status. But not getting full clarity on this.
    Rgds,
    Senni.B

    Hi,
    Please go through the following information.
    [Relase Procedure for Condition Record|http://help.sap.com/saphelp_47x200/helpdata/en/a4/af9e78e69611d2ace10000e8a5bd28/frameset.htm]
    [Release Procedure for PR|http://www.sap123.com/showthread.php?t=59]
    Reward if helpful.
    Thanks and Regards,
    Naveen Dasari

  • Set new status for reas for rejection

    Dear gurus
    I need to set a new status D Order on hold when the rejection is set to a sale order
    how to do that
    Regards
    Saad.

    Resolved
    by doing enhancement

  • Release status for condition records

    Hello,
    When ever a user changes the price in the condition record, I want the price to be in blocked status initially. Sales document should only pick tht price when it is release by the concerned person.
    Could you tell me how is the authorization given to some users based on the processing status.
    Thanks and Regards,
    Pavan P.

    I tried to make the Processing status as blank and tried to save it and assigned the release status "Blocked". This doesn't seem to work. Any other ideas?

  • Configuring Line item in IP - for Change records

    Hi guys,
    I just finsihed implementing the "How to" paper for Line-items in BI Intergrated Planning.
    It works just fine, except for one minor thing.
    For some reason when I look at my records in the planning cube, it's filling my '0BBP_0GUID' field with my
    0UNAME, and at the same time my '0UNAME'  in the cube is blank. So my cube looks like:
    0BBP_0GUID =  S23237 (user ID)
    0DATE   = 9/22/2008
    0TIME   =  15:23:10
    0UNAME = 'Blank'
    It looks like a mapping problem at first. Anyone ran into this issue, any advice??
    Thanks
    Edited by: Ehab Mansour on Sep 22, 2008 2:59 PM

    Hi,
    Here's how the code looks.
    FIELD-SYMBOLS: <l_chavl> TYPE ANY.
    fill ID
    ASSIGN COMPONENT 'BBP_OBGUID' OF STRUCTURE c_s_chas
    TO <l_chavl>.
    CALL FUNCTION 'GUID_CREATE'
    IMPORTING
    ev_guid_32 = <l_chavl>.
    fill user
    ASSIGN COMPONENT 'USERNAME' OF STRUCTURE c_s_chas
    TO <l_chavl>.
    <l_chavl> = sy-uname.
    fill date
    ASSIGN COMPONENT 'DATE0' OF STRUCTURE c_s_chas
    TO <l_chavl>.
    <l_chavl> = sy-datlo.
    fill time
    ASSIGN COMPONENT 'TIME' OF STRUCTURE c_s_chas
    TO <l_chavl>.
    get time field <l_chavl>.
    I don't see anything wrong, do you?

  • When merging data into a PDF form, can it create a new form for every record in your data set?

    I have a vendor database that I want to use to populate a pre-created PDF form in Adobe Pro XI. I figured out how to rename the form data fields and how import the data from my data set but can't figure out how to have it create another copy of the form for the next record in the data set.... if its even possible. Any help is appreciated!

    This can be achieved with a mail-merge type script.

  • How to display multiple records in smart forms in new page for each record

    Hi,
              How to display the data from a internal table in a smart form.
    I want each record to be displayed in seperate page.
    please tell me with example.
    thank u,
    Sarath

    Do this ,
       in the main window - open a loop on your internal table ,
    within the loop open the text and give the output fields,
    after this text  use the Command node and in this set the next page as page1,
    so when the loop gets executed its first record will be on the first page and the second record will be on the next page and so on ..
    Reward to usefull answers.

  • How can we get changed records in delta in case of numeric pointer

    Deall All,
    Thanks to all of you gurus i have been able to Get delta update for my query.
    There is one last issue how can i include changes records in my delta update when i am using numeric pointer for data selection.
    or
    It can only be doen by time stamp.
    can you explain me details of using time stamp.
    Thanks & regards,
    Gaurav Sood

    Dear Gaurav,
    Here we have three options for delta updation:
    Time Stamp:   If we want to update change in the records with respect to the time interval then this option is selected.
    Calend. Day:   If we want to update change in the records with respect to day to day basis then this option is selected.
    Numeric Pointer:  If we want to update in case of record which is completely new with respect to Field name then we use this option.
    And we have got some settings like:
    Safety Interval upper limit:
    This field is used by Data Sources 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.
    Data Source Is Real-Time Enabled
    The 'real time enabled' indicator determines whether a delta-enabled Data Source can be used as a supplier of data for a real-time daemon.
    And there are two options provided like
    1)     New Status for changed records:
    If you select this option each record to be loaded delivers the new status for the key figures          and characteristics. DataSources with this delta type can write to ODS objects or master data tables.
    2)     Additive Delta:
    The key figures for extracted data are added up in BW. Data Sources with this delta type can supply data to ODS objects and Info Cubes.
    Hope this helps u..
    Best Regards,
    VVenkat..

  • BI7 : Change full load to delta load - things to do?

    http://wiki.sdn.sap.com/wiki/display/profile/2007/04/30/Differencebetweenfull,intialanddeltaupdatemodes
    Difference: Full load, Delta Load & INIT load in BW
    Hi.
    Since am not familiar with BW request clarity as to how to achieve the following :
    We are on BI 7.
    On our BW server, One of the Existing process chain loads data as full load daily Till date.
    This schedule runs for about 4 to 6 hours during the nights. And the data seems to be growing.
    And doing full load, now seems, not that meaningful for data analysis.
    So we now feel we need not do a full load every day. But do only the incremental load.
    How to make this effective in our existing process chains.
    I went thro the 2 links above, but a few things am not clear.
    What exactly needs to be done to change a full load into a delta load.
    Also do not wish to have any data loss happening.
    We run the schedules on a particular process chain for BW around 1 am.
    Say from tomorrow I want to have the data loading as delta.
    What exactly are the steps to be followed.
    Precautions to be taken
    So that we have the correct data load and no data is lost - while doing this.
    Things to do am not clear :
    do initialization with data transfer / or without data tranfer ?
    The make it delta?
    So that from tomorrow all data loading becomes delta ?
    Or
    since in our scenario,
    daily basis it is full load.
    Just make it delta load,
    so that whatever changes will run in the next days schedule.
    What all things are to be done stepwise.
    if anyone could advise.
    That would be very helpful.
    Also any documentation which explains all these if someone could share the link please ?
    Many thanks
    indu
    Edited by: Indumathy Narayanan on Aug 26, 2011 5:50 PM

    Hi,
    Kindly look at following links as well
    http://help.sap.com/saphelp_nw04s/helpdata/en/44/9821620553053de10000000a1553f6/content.htm
    Generic Delta
    If a field exists in the extract structure of a DataSource that contains values which increase monotonously over time, you can define delta capability for this DataSource. If such a delta-relevant field exists in the extract structure, such as a timestamp, the system determines the data volume transferred in the delta method by comparing the maximum value transferred with the last load with the amount of data that has since entered the system.  Only the data that has newly arrived is transferred.
    To get the delta, generic delta management translates the update mode into a selection criterion. The selection of the request is enhanced with an interval for the delta-relevant field. The lower limit of the interval is known from the previous extraction. The upper limit is taken from the current value, such as the timestamp or the time of extraction. You can use security intervals to ensure that all data is taken into consideration in the extractions. After the data request was transferred to the extractor, and the data was extracted, the extractor then informs generic delta management that the pointer can be set to the upper limit of the previously returned interval.
    The delta for generic DataSources cannot be used with a BW system release prior to 3.0. In older SAP BW releases, the system does not replicate DataSources for master data and texts that were made delta-enabled using the delta for generic DataSources.
    Determining the Generic Delta for a DataSource
           1.      Choose Generic Delta.
           2.      In the subsequent dialog box, specify the delta-determining field and the type for this field.
           3.      Maintain the settings for the generic delta:
                                a.      Specify a security interval.
    The purpose of a security interval is to make the system take into consideration records that appear during the extraction process but which remain unextracted (since they have yet to be saved) during the next extraction.
    You have the option of adding a security interval to the upper limit/lower limit of the interval.
    A security interval should only be specified for the lower limit when the delta method results in a new status for changed records, in other words, when the status is overwritten in BW. In this case, duplicate data records that could arise in such a safety interval have no affect on BW.
                                b.      Choose the delta type for the data to be extracted.
    The delta type is used to determine how extracted data is interpreted in BW and which data targets in which it can be posted.
    With the delta type additive delta, the record to be loaded for summarizable key figures only returns the change to the key figure. The extracted data is added in BW. DataSources with this delta type can supply both ODS objects and InfoCubes with data.
    With the delta type New Status for Changed Records, every record to be loaded returns the new status for all key figures and characteristics. The values are overwritten in BW. DataSources with this delta type can write the data into ODS objects and master data tables.
           4.      Save your entries.
    Delta transfer is now possible for this DataSource.
    After generating the DataSource, you can see this from the marking for the field Delta Update on the DataSource: Customer Version screen.
    In systems from release 4.0B, you can display the current value of the delta-relevant field in the delta queue.
    Thanks and regards

  • Generic Datasource with Additive Delta

    Hi all
    I have a question.
    In whic case can I use a generic datasource with additive delta?
    Does this delta mode make sens only with function module extraction?
    If I extract data directly from a table, can I use this delta mode only if a field represents changes?
    Thanks for your help!
    S.

    Stefania,
        To my knowledge what you are thinking is wrong.
    we have 2 Methods for Generic DS.
    1. New status for changed Records.
    2. Additive delta.
    New status for changed records means
    New Order
    order no    quantity
    1000          10
    order changed to quntity 8. then 2 records will posted 2 BW in first case.
    1000          -10
    1000            8
    if you come to Additve delta.
    for the same case it will send the same record as
    1000          10
    changed records
    1000          -2
    this is the difference. New status with changed records should be used only in association with ODS not cube becoz we don't have overwrite option.
    Additive delta we can use for ODS and Cubes with update mode Addition.
    Hope this is clear.
    Regards,
    Nagesh Ganisetti.

  • Question on SFSF Adapter : Delta sync to fetch only changed records.

    Hi All ,
    As per the SAP Document on SFSF Communication channel, one of the feature supported by SP00 release of the connectivity add-on 1.0 is :-
    1. Delta sync to fetch only changed records
    SFSF Adapter: Delta Sync
    The delta sync features enables you to fetch only the records that were modified after the last successful data fetch from the SuccessFactors system.
    This increases the efficiency of query operation.
    So below are my question accross Successfull run date feature :
    Is it SAP PI Connector internally maintains this last successful run date ?
    what would be Time-Zone of Successful run date : Is it where SF DC is located or where PI Box is Located ?
    what is it mean from successful run date ? - is it process successful run date or is it just communication channel successful run date ?
    For Delta extraction - This Successful Run Date - Is it maintained internally for  Interface wise or Communication Channel wise ?
    eg. If i have 5 Delta Interface - will SAP PI maintain 5 Successfull run dates w.r.t to each connector or w.r.t each Process ?
    for more information please open below URL.
    http://help.sap.com/saphelp_nw-connectivity-addon100/helpdata/en/1e/22aaf0780d4b78b6f889157f6a8035/frameset.htm
    Regards
    Prabhat Sharma

    Hello all,
    I have the same question : in the "official" documentation (SuccessFactors (SFSF) Adapter for SAP NetWeaver Process Integration) is mentioned this :
    Delta Sync - The delta sync features enables you to fetch only the records that were modified after the last successful data fetch from the SuccessFactors system. This increases the efficiency of the query operation.
    Anyway I cant find any specification on how to use this feature. Do you have any suggestion on how to implement it or any reference to an existing documentation?
    Do I need to write you an email to get the info?
    Regards

  • Diff between additive delt and delta

    Hi all,
    what is the difference between additive delta and delta?
    sridevi

    Hi,
    the records which are generated after the last update is called delta.
    In some datasources the changed records are stored with before and after images.
    But some datasoures the changed records are stored with only new image we call it as additive delta.
    regards,
    haritha

  • Confirmation status is changed

    Hi Folks.I am working on SNC7.0.I created New PO and then iam confirming PO.While click on save button confirmed status will be CONFIRMED but after click on publish button confirmed status is changed to NOT CONFIRMED.These changes are in Po details screen.In that PO header General tab.
    Any suggestions how to resolve this issue.
    Thanks in advance.

    Hi Srinivas,
    In path:SPRO>Supply Network Collaboration>Basic settings>Validation>Own setting you will not get any values(even if you press F4 also).
    There is no check here if you enter any junk value also system will save.
    As i suggested earlier you need to maintain validation setting manually(do not press F4).
    Save the validation setting as suggested and recheck now.
    About validation check PO_CONF_RELEVANCE_CTRL :"Set Confirmation Status for Changed PO Item to "Not Confirmed"
    If this validation check is active, SAP SNC sets the confirmation status of a purchase order (PO) item to Not Confirmed if the customer has changed the following item data in the customer back-end system and has sent the changed PO to SAP SNC:
    ■Goods recipient
    ■Ship-to location
    ■Product
    ■Requested delivery date
    ■Incoterm
    ■Price
    Validation check PO_CONFIRMATION_DELETE:"Delete Confirmation Schedule Lines for Changed Purchase Order Items"
    If this validation check is active, SAP SNC deletes the confirmations schedule lines of a purchase order item if the customer has performed a change that requires confirmation by the supplier. Changes that trigger deletion include the following: Quantity changes and the changes listed in the description for validation check PO_CONF_RELEVANCE_CTRL
    Regards,
    Nikhil

Maybe you are looking for