No Delta records for SRM Confirmations (Extractor - 0BBP_TD_CONF_1)

Hi,
We are getting zero records for delta update from 0BBP_TD_CONF_1 after successfull init w/data.
Delta queue is empty, and no records  for delta extraction in RSA3 too in source system. Its sure that  data ( changes/new confimations) is entered, but some how they are not updated to BW delta queue.
I saw couple of threads with same issue, but no solutions. If any one has any ideas/suggestions/solutions, please let me know.
Thanks,
S

Hi,
Did you checked the User exit wether you are doing any manupulations or selections.
since before populating the delta queue we can have our own code to populate the data.
So better check any such code is there in user exit.
Regards,
aanand

Similar Messages

  • Missing delta records for the Z extractor

    Hi,
    I have created a Z extractor for the table BUT050 in CRM. I have created a function module and have included the delta logic on CRDAT which is the created date, CRTIM - created time, CHDAT - change date, CHTIM - Change time. I have initialed the delta and started doing the delta loads. I found that there are few missing records in the extractor when compared to the table. I'm attaching my code below.Can anyone please look into it and tell me what the issue is.
    Text removed by moderator
    Thanks
    FUNCTION Z_BI_CC_BUT050.
    *"*"Local Interface:
    *"  IMPORTING
    *"     VALUE(I_REQUNR) TYPE  SRSC_S_IF_SIMPLE-REQUNR
    *"     VALUE(I_DSOURCE) TYPE  SRSC_S_IF_SIMPLE-DSOURCE OPTIONAL
    *"     VALUE(I_MAXSIZE) TYPE  SRSC_S_IF_SIMPLE-MAXSIZE OPTIONAL
    *"     VALUE(I_INITFLAG) TYPE  SRSC_S_IF_SIMPLE-INITFLAG OPTIONAL
    *"     VALUE(I_READ_ONLY) TYPE  SRSC_S_IF_SIMPLE-READONLY OPTIONAL
    *"     VALUE(I_REMOTE_CALL) TYPE  SBIWA_FLAG DEFAULT SBIWA_C_FLAG_OFF
    *"  TABLES
    *"      I_T_SELECT TYPE  SRSC_S_IF_SIMPLE-T_SELECT OPTIONAL
    *"      I_T_FIELDS TYPE  SRSC_S_IF_SIMPLE-T_FIELDS OPTIONAL
    *"      E_T_DATA STRUCTURE  ZBI_BUT050 OPTIONAL
    *"  EXCEPTIONS
    *"      NO_MORE_DATA
    *"      ERROR_PASSED_TO_MESS_HANDLER
    * Auxiliary Selection criteria structure
       DATA: l_s_select TYPE srsc_s_select.
    * Maximum number of lines for DB table
       STATICS: s_s_if TYPE srsc_s_if_simple,
    * counter
               s_counter_datapakid LIKE sy-tabix,
    * cursor
               s_cursor TYPE cursor.
    * Select ranges
       RANGES: l_r_RELNR FOR ZBI_BUT050-RELNR,
               l_r_PARTNER1 FOR ZBI_BUT050-PARTNER1,
               l_r_PARTNER2 FOR ZBI_BUT050-PARTNER2,
               l_r_DATE_TO FOR ZBI_BUT050-DATE_TO,
               l_r_ZZTMSTMP FOR ZBI_BUT050-ZZTMSTMP.
       DATA : startdate LIKE sy-datum,
              starttime LIKE sy-uzeit,
              enddate LIKE sy-datum,
              endtime LIKE sy-uzeit,
              tstamp LIKE tzonref-tstamps,
              timezone type TZONREF-TZONE.
       RANGES: l_r_CRDAT FOR ZBI_BUT050-CRDAT,
                       l_r_CRTIM FOR ZBI_BUT050-CRTIM.
    * Initialization mode (first call by SAPI) or data transfer mode
    * (following calls) ?
       IF i_initflag = sbiwa_c_flag_on.
    * Initialization: check input parameters
    *                 buffer input parameters
    *                 prepare data selection
    * Check DataSource validity
         CASE i_dsource.
           WHEN 'ZCC_MA_BUT050'.
           WHEN OTHERS.
             IF 1 = 2. MESSAGE e009(r3). ENDIF.
    * this is a typical log call. Please write every error message like this
             log_write 'E'                  "message type
                       'R3'                 "message class
                       '009'                "message number
                       i_dsource   "message variable 1
                       ' '.                 "message variable 2
             RAISE error_passed_to_mess_handler.
         ENDCASE.
         APPEND LINES OF i_t_select TO s_s_if-t_select.
    * Fill parameter buffer for data extraction calls
         s_s_if-requnr    = i_requnr.
         s_s_if-dsource = i_dsource.
         s_s_if-maxsize   = i_maxsize.
    * Fill field list table for an optimized select statement
    * (in case that there is no 1:1 relation between InfoSource fields
    * and database table fields this may be far from beeing trivial)
         APPEND LINES OF i_t_fields TO s_s_if-t_fields.
       ELSE.                 "Initialization mode or data extraction ?
    * Data transfer: First Call      OPEN CURSOR + FETCH
    *                Following Calls FETCH only
    * First data package -> OPEN CURSOR
         IF s_counter_datapakid = 0.
    * Fill range tables BW will only pass down simple selection criteria
    * of the type SIGN = 'I' and OPTION = 'EQ' or OPTION = 'BT'.
           LOOP AT s_s_if-t_select INTO l_s_select WHERE fieldnm = 'RELNR'.
             MOVE-CORRESPONDING l_s_select TO l_r_RELNR.
             APPEND l_r_RELNR.
           ENDLOOP.
          LOOP AT s_s_if-t_select INTO l_s_select WHERE fieldnm = 'PARTNER1'.
             MOVE-CORRESPONDING l_s_select TO l_r_PARTNER1.
             APPEND l_r_PARTNER1.
           ENDLOOP.
           LOOP AT s_s_if-t_select INTO l_s_select WHERE fieldnm = 'PARTNER2'.
             MOVE-CORRESPONDING l_s_select TO l_r_PARTNER2.
             APPEND l_r_PARTNER2.
           ENDLOOP.
           LOOP AT s_s_if-t_select INTO l_s_select WHERE fieldnm = 'DATE_TO'.
             MOVE-CORRESPONDING l_s_select TO l_r_DATE_TO.
             APPEND l_r_DATE_TO.
           ENDLOOP.
    * Timestamp is delivered as a selection criterion.
    * Split the timestamp into date and time
          LOOP AT s_s_if-t_select INTO l_s_select WHERE fieldnm = 'ZZTMSTMP'.
             tstamp = l_s_select-low.
             timezone = 'EST'.
             CONVERT TIME STAMP tstamp TIME ZONE timezone
              INTO DATE startdate TIME starttime.
             tstamp = l_s_select-high.
             CONVERT TIME STAMP tstamp TIME ZONE timezone
              INTO DATE enddate TIME endtime.
             l_r_CRDAT-low = startdate.
             l_r_CRDAT-sign = l_s_select-sign.
             l_r_CRDAT-option = l_s_select-option.
             l_r_CRDAT-high = enddate.
             APPEND l_r_CRDAT.
             l_r_CRTIM-low = starttime.
             l_r_CRTIM-sign = l_s_select-sign.
             l_r_CRTIM-option = l_s_select-option.
             l_r_CRTIM-high = endtime.
             APPEND l_r_CRTIM.
           ENDLOOP.
    * Determine number of database records to be read per FETCH statement
    * from input parameter I_MAXSIZE. If there is a one to one relation
    * between DataSource table lines and database entries, this is trivial.
    * In other cases, it may be impossible and some estimated value has to
    * be determined.
           OPEN CURSOR WITH HOLD s_cursor FOR
    * Use the l_r_erdat and l_r_erfzeit for both creation and change selections
    * This way we can pick up both the creations and changes in a given time period.
           SELECT * FROM BUT050
                  WHERE RELNR IN l_r_RELNR
                   AND PARTNER1 IN l_r_PARTNER1
                   AND PARTNER2 IN l_r_PARTNER2
                   AND DATE_TO IN l_r_DATE_TO
                   AND ( CRDAT >= startdate AND ( CRTIM >= starttime OR ( CRDAT <= enddate AND CRTIM <= endtime ) ) )
                   OR ( CHDAT >= startdate AND (  CHTIM >= starttime OR ( CHDAT <= enddate AND CHTIM <= endtime ) ) ).
         ENDIF.
         "First data package ?
    * Fetch records into interface table.
    *   named E_T_'Name of extract structure'.
         FETCH NEXT CURSOR s_cursor
                    APPENDING CORRESPONDING FIELDS
                    OF TABLE e_t_data
                    PACKAGE SIZE s_s_if-maxsize.
         IF sy-subrc <> 0.
           CLOSE CURSOR s_cursor.
           RAISE no_more_data.
         ENDIF.
         s_counter_datapakid = s_counter_datapakid + 1.
       ENDIF.              "Initialization mode or data extraction ?
    ENDFUNCTION.
    Message was edited by: Matthew Billingham

    Hi,
    As per my knowledge you want load particular period of data try repair request may issue solve.
    Regards
    Sivaraju

  • Postings in SAP HR for creating delta records for Time Management

    Hi Experts,
                      I am trying to test delta load for SAP HR Time Management Datasources. I am fairly new to SAP HR and need some help.
    Where do we create postings in  SAP HR for creating delta records which can be imported to BW. This is for the data sources 0HR_PT_1 and 0HR_PT_2.
                   Any help is appreciated. Will assign full points
    Regards
    Sunil Kumar.

    Hi,
    In order to test the above data sources you need to have some employee enter his time details or change the entered time details.  That will create some delta records for the planned or actual times.  CAT2 transaction should help entering the time details in SAP. 
    Hope it helps.

  • Missing Delta Records for 2LIS_02_ITM & SCL

    Hi Experts,
    this is how my problem goes.
    i have done my set up table filled on 12th Dec 2010 and from that time onwards the delta were running everyday and filling the DSO and Cube.
    Accidently by some others PC in prod all my delta loads and the setup table load is being deleted except yesterday in PSA for these 2 extractors and now because of some change i have to do a full load to DSO.
    But as the PSA is emply and have only yesterday's request i have, deleted that one as well and done a Init Delta to it and i found out that only the Set up table is comming now and all the deltas in between are missing.
    i have tried a full LOAd to PSA and the result is same.
    How can i get those missing delta records from 12th Dec last year till today with out doing another set up table fill  or Do i have to have fill the set up table again till today and thats the only way? i will set the delta again after that.
    Do we have to have all the user locked for the setup table fill (for Queued Delta type) ? Lot of people says yes you have to and others says no you don't require. i got one white paper and it clearly says no user locking is required. please find the link below. what is the correct way?
    [http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d019f683-eac1-2b10-40a6-cfe48796a4ca?quicklink=index&overridelayout=true]

    Hi,
    As per my knowledge you want load particular period of data try repair request may issue solve.
    Regards
    Sivaraju

  • Delta upload for total fisl extractor

    Hello,
    Its said that the BALANCE field in the transfer structure is not supplied with data during Delta upload . 
    Would you know the reason for this?
    I assume this is for the totals extractor only since balance is not available otherwise.
    Regards
    Pascal

    Because the change record updates the movements not the balance
    And you can back post - ie post to a period already gone - so if yuu wanted balance to be provided you would then have to change every periods balance b/f in the extractor from the backposted period onwards
    Easiest way to do it - do it in the cube (as per the OSS note) and let compression deal with getting rid of the extra records created

  • Changes in contract-data: No delta-record for BW

    Hi,
    when in transaction VA02, changes are made to contract data (start date, end date), no delta record is generated in datasource 2LIS_11_VAITM. The contract data is stored in table VEDA.
    Currently we have an enhanced datasource that gets the dates at extraction time, but changes to contracts afterwards are not generating delta records.  Therefore after a while BW is not in sync with ECC R/3.
    Is this a known problem, and does anybody have a solution or suggestion?

    Hi T. Jans-Beken,
    Did you create a datasource on VEDA table to load in full mode to BW?

  • How can I get delta records for Generic Delta

    Hi BW Gurus,
    I am using Generic Extractor using View from CATSDB and CATSCO talbes. At the time of modifying and changing records I am unable to get those records in BW despite enabling delta in RSO2 screen. I am able to view those modified and added records in R/3 in tables. Plz help me how I get those records to BW.

    hi,
    After we loaded all the historical data uing full upadate . Implemenattion process is over , But we will have the Transaction data that will raise daily , So we have to store that New / changed data in Delta q , And extract them each day by Delta Update
    So we will create an Info packege with the update mode as Delta , And schedule them when to start extraction , So we create the process chain uisng RSPC by giving the Info packege name . And extract the Detla daily as per schedule .
    award pts if helpful..

  • No condition maintained for Order Confirmation output type but still active

    Hi,
    I have NOT maintained any Condition record for Order confirmation Output(BAFX) but still it is generated and Fax instruction is being sent to the Sold to Party. Also i found that NO condition record for Order confirmation output(BA00) is also maintained but still Order confirmation is still being triggered.
    Actually i want that NO Fax instruction is to be sent for Order confirmation for some of the customers.
    Kindly advise.
    Thanks,

    Hi vk@sap,
               Check in the output analysis how the output was determined, so that you can know why they're still determined.
    Thanks,
    Mariano.

  • Delivery Delta Records missing

    Hi Friends !
    We have missd the delta records for 4 days. Only way I know to run the setup table again & get all the records till date. Then schedule V3 jobs & next day onwards delta records will be pulled. Do we have any other way to get those missed records? Please advise.
    With Regards
    Rekha

    Hi Rekha,
    Please follow the below steps in R3 side
    goto RSA3-->give DS name press enter
    below you will get selection screen
    give you delivery numbers as selections
    then execute, if you get records here then definitely you should get records when you run the IP.
    Hope this helps
    Regards,
    Venkatesh.

  • Delta records are not found in RSA7 but can be seen in RSA3

    0HR_PY_1
    Delta records for 0HR_PY_1 is not showing in RSA7 for the month of April
    but showing in RSA3.How can we load to BI when they are not appearing in RSA7?
    Can any one please guide what and how many  transactions should exactly lead to the updation of RSA7 delta queue?
    If the list of the transactions can be given,I can cross verify with the users whether these transactions are already over or not.Help is sincerely expected..Kindly help.
    Regards
    Sharif.

    Hi,
    Please examine this note for RSA7 : 380078

  • Record Mode in SRM Std Extractor.

    Hi All,
    In the SRM std extractor for POs we are having an issue. The POs which are deleted in SRM are supposed to be deleted in BW DSO as well. But this doesn't always happens for POs with limit Line items. Rest all the records are deleted and one Limit Item remains as the record mode for the rest of the records come as 'D' and for Limit Item is blank. It is an AIMD extractor. If anyone has faced the issue please let us know how this was solved.
    Alternatively Is there any way to find how record mode is populated in a standard extractor. Please let us know.
    Thanks In Advance,
    Aparna

    Hi Aparna:
        Could you please provide more details? For example:
    - Which is the DataSource you're working with?
    - Are you loading data to a Standard DSO? Which one?
    - What are the InfoObjects included in the "Key fields" of your DSO?
    Regards,
    Francisco Milán.

  • Delta records are not populating for enhanced fields in 2LIS_17_I3HDR

    Hello,
           I have an issue with 2LIS_17_I3HDR datasource, i have enhanced the DS with Zfields, these are populated from AUFK through user exit. When i fill setup table, i can see the values being populated for enhanced fields, but for delta records, i dont find any values for these enhanced fields, even though the values exists in the AUFK table and i even tried degugging the user exit code, it doesnt go through it during the posting of delta records.
    Can some one give some suggestion on this issue.
    Thanks,
              Pavan

    Hello Ravi,
                     Yes, delta records cannot be populated by enhanced fields. Here the issue is different,
    i have added a closed date to the extract structure, this is order specific, so when i create a new PM order after the full load, and release the order and close it, the AUFK table get an entry for closed date, my exit compare the object number of the extractor to object number in AUFK and get the closed date value to the DS, this is not same as enabling delta on the enhanced fields (which cant be done).
    Thanks,
                Pavan

  • Delta field for LO Extractor Datasources

    Hi All,
    Can anyone tell me how to find the delta field for LO Extractor. Because currently i am facing some problem in Delta like, if i do any changes in sales order in Item Level those changes are not reflected in RSA7. And the next change if i do it in header level i cld see the change along with my previos change being displayed. Problem is i dont find as seperate record for my changes in ITEM level.
    Ex. x   3040404  001 oooo ppppp oooo hhhh kkkk
            3040404  001 oooo bbbbb oooo hhhh kkkk  - this is for header level chnage
    Item level chnage: Not shown as seperate records
    Next header change displayed properly as above.
    Pls advise me this is a very urgent issue.
    Thanks.
    Bhu.

    Hi Nagesh,
    Thanks for your reply.
    Onething to tell is i am handling diff clients. All my clients r using 3.5 except this client. Very Unfortunate. They r using 2.1c. Its long back i used this version
    In LBWE i found they have only one update type i.e V3 update.
    I have checked SM13 also. There is one update records for each change in header level data. Also this time i found when i change Route i found one update record. But not when i change Schedule line date.
    Pls let me know if u need any further info. Anyideas welcome.
    Cheers!
    Bhuvana.

  • Initialize loads for all Purchasing extractors w/o affecting delta for SCL

    Hi Gurus,
    I have to initialize and start the loads for all the Purchasing extractors except the Scheduled Line Item extractor which is already running. I have to make sure I am not disturbing the daily delta for the Scheduled Line Item(SCL) extractor while initializing and running the other loads for Purchasing. How do I get this done.
    Any help is deeply apprecited and will be rewarded with points.This is pretty urgent
    Thanks

    Hi John,
    You can go ahead with the following approach:
    I am assuming that the type of delta that u use here is queued delta. This can be viewed in transaction LBWE (Under purchasing (02)).
    When you are dealing with LO cockpit extractions, make sure the extraction queue (LBWQ) and delta queue (RSA7) show up as either 0 records or dont list up in the specific transactions.
    For example, if there are entries in LBWQ against MCEX02, this means the scheduling extractor still has some data in the extraction queue which needs to be moved to delta queue (RSA7) and then pushed to BW.
    Make sure when transports go to production, there are no entries for delta either in LBWQ (check entry MCEX02) or RSA7 (check entry 2LIS_02_SCL). If not do repeat the following process until both of them are empty. Only then release the transports.
    1. In LBWE, click on job control for 02 (Purchasing). Click on Start date. And select immediate and save. Come back to job control screen and schedule job. This should move data from extraction queue (LBWQ) to delta queue (RSA7).
    2. Run the delta infopackage for scheduling item on the BW side. This would clear the delta queue.
    Do the above process continuously until you see MCEX02 does not show up in LBWQ and no entries in RSA7 for the specific scheduling extractor.
    Then you would be on a safer side.
    A better approach here would also be to get to know a no-posting zone, where you migght get less postings.
    With Best Regards,
    Hariharan. M

  • Confirmation against Backend PO for SRM@ERP2005

    Hi,
    I'm having a problem in posting confirmation for a B/E PO. I have received an error message in the inbox of the userid that I have used to carried out the confirmation which says 'Entry in outbound table not found'. I have clicked on the linked provided in the message and it brings me to one of the IDOC transactions. In it, I saw additional info such as Basic type MBGMCR01 and status which says Error in ALE service.
    I have included message types BBPCO, BBPIV and ACLPAY in the Maintain Distribution Model and Distribute Views. I remember that there is an additional message type to be maintained called MBGMCR but the system doesn't allow me to maintain this value in that config as it says it's actually a BAPI. I have also tried adding this as a BAPI but the system prompted to enter other mandatory info such as method which I have no clue at all.
    Appreciate if anyone can help me and points will be rewarded. Thanks.
    Regards,
    Li Ping

    Yes , I did check it .
    However , I dont think this works for SRM 7.0 extended classic scenario .
    I have defined some custom fields in PO and want the values to be transferred to the backend PO .
    Does this work with BBP_ECS_PO_OUT_BADI ?
    Regards,
    Ambar

Maybe you are looking for