Delta Extraction for Custom Table

Hi All,
I have a Custom Table in R/3 with several fields and only one date field ( Creation Date ).
I need to Create a data source(Function Module extractor) and delta enable it.
Since i have no field *change date* on this table, is there a procedure/method to captures all
delta. Appreciate all your help.

Hi
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. 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.
Hope it helps and clear.

Similar Messages

Delta extraction for FI (AR & AP) data sources

I tried extracting the data from 2 standard SAP data sources under FI module for Accounts Receivable.
0FI_AR_10(Customer payment history via delta extraction)
0FI_AR_5 (customer payment history)
The data to be extracted into 0FIAR_C05(payment history) info cube.I assigned the 2 data sources to an info source and pumped the data into the cube via an ODS.Now the problem is with delta extraction.No records are picked in the delta extraction.So I checked in extractor checker RSA3 with delta update mode.I got the following error.
"Could not determine BW release of logical system"
Could some one resolve the issue?Thanks in advance.
Thanks & Regards
Vinay

Hi ,
Please go through 493422 note once . see if suits to your requirement follow it accordingly .
Thanks ,
Anil

How to populate date & time when user enter data for custom table in sm30

Can anyone tell me How to populate system date & time when user enter data for custom table in sm30..
Req is
i have custom table and using sm30 user can enter data.
after saving date i want to update date & time in table
Pls let me know where to write the code?
Thanks in Advance

You have to write the code in EVENT 01 in SE54 transaction. Go to SE54, enter your Ztable name and in the menu 'Environment-->Events'. Press 'ENTER' to go past the popup message. In the next screen, click on 'New Entries'. In the first column, enter 01 and in the next column give some name for your routine(say UPDATE_USER_DATE_TIME). Then click on the souce code icon that appears in blue at the end of the row. In the code, you need logic like below.
FORM update_user_date_time.
DATA: f_index LIKE sy-tabix.
DATA: BEGIN OF l_total.
          INCLUDE STRUCTURE zztable.
INCLUDE STRUCTURE vimtbflags.
DATA END OF l_total.
DATA: s_record TYPE zztable.
LOOP AT total INTO l_total.
    IF l_total-vim_action = aendern OR
       l_total-vim_action = neuer_eintrag.
      MOVE-CORRESPONDING l_total TO s_record.
      s_record-zz_user = sy-uname.
      s_record-zz_date = sy-datum.
      s_record-zz_time = sy-uzeit.
      READ TABLE extract WITH KEY l_total.
      IF sy-subrc EQ 0.
        f_index = sy-tabix.
      ELSE.
        CLEAR f_index.
      ENDIF.
      MOVE-CORRESPONDING s_record TO l_total.
      MODIFY total FROM l_total.
      CHECK f_index GT 0.
      MODIFY extract INDEX f_index FROM l_total.
    ENDIF.
ENDLOOP.
ENDFORM.                    " UPDATE_USER_DATE_TIME
Here ZZTABLE is the Z table and ZZ_USER, ZZ_DATE, and ZZ_TIME are the fields that are updated.

* Delta Extraction for 0ASSET_ATTR_TEXT

Hi All,
Can someone help me for the delta extraction for 0ASSET_ATTR_TEXT datasource.
Steps performed as per SAP Help
1. Activated the BADI
2. Ran the initialization without datatransfer infopackage.
3. Created new records in R/3 side
4. I can see the newly created records in the Table : BWFIAA_AEDAT_AS
5. Ran the delta infopackage ( no records are getting updated)
When i check in RSA3 with the delta update, its giving an error.
Please guide me if i am missing any steps
Regards
Ram

Hi Ram,
Check this note,
Note 816560 - DeltaInit w/o data transfer does not createe time stamp
https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=816560
Hope this helps....

Add Table maintenance program for custom table to an existing func group

Hi Guys,
Can I add Table maintenance program for custom table to an existing function group or I need to create a new
function group for each custom table.
Thanks,
mini

You can add to an existing function group, there's nothing technically to stop you doing this. However, consider that this is creating generated function modules in this function group and you would be wise to avoid using a function group containing manually created modules.
I personally always create a new function group, using the name of the table as the name of the function group.
Regards,
Nick

Creating TPR for customized table

Hi,
I want to create transport a customized table to QA from Dev box.
I know how to create transport request for reports and smartforms and all.
But How do I create transport request for customized table ?
Is it thorugh SM30 ?
Please help me...

this depends on the Table maintenance dialog for the table. (utiliteis->table maint generator).
If it has the recording routine set as 'standard' then SM30 will automatically create a transport when you hit the save button after perfroming maint on the table.
For 'no, or user..' you will have to manually add entries to a transport.
Go to SE10. Display your transport. Double click on the development/correction line. Now you can see a list of objects belonging to the task. Hit the 'display/change' toggle button. Add an entry with program id R3TR and object TABU. Enter the table name in the object name. Double click opn the function icon to the right of the object name. Double click in the empty table key area. This pops to allow you to enter the keys you require to transport.

Transport Request for Custom Table??

Hi all,
I got the requriment for Custom Table.
"The table should have attributes such as the table contents can be transported from DEV to QA to PROD. Also the table can be maintained individually in QA or PROD too"
I have understood that I need to have "Delivery Class" as "C". But i want to know what should Transport request type: (Workbanch or Customizing)
thanks in advnace.

You say "the table can be maintained individually in QA or PROD too" I have understood that I need to have "Delivery Class" as "C".
If table must be maintained in QA and PRD, you need "Delivery Class" as "A". With "Delivery Class" as "C" you can only maintain table in DEV and transport entrie changes to the other systems.
Regards.

Is table maintenance generator only for custom table?

hi ,
i have doubt is table maintenance generator only for custom table?

hi swamya,
Table Maintanance Generator is used to create/change/delete table entries in a particular table.
In the production system, end-users will not be having access to transaction codes like SE11 and SE16. Developers will not be having access to many transaction codes including the above two.To view the contents of the database table, we will use SE16n in Production system. All these authorizations will be maintained by BASIS team, by creating access profiles.So in order to edit or create the contents of a database table, we should go for table maintenance generator. In real time, authorizations will be maintained in production system.
The second reason is, we can edit or create multiple entries at a time, using tablemaintenance generator.
Apart from that we have options like 'Enter conditions' in table maintenance screen SM30.
hope this helps in clearing ur doubt.
Regards
Saurabh

Delta extraction for masterdata object

hi,
can anybody tell me the procedure for delta extraction for master data object.
is it possible!

Master Data Datasources do allow for delta extraction. You can display datasource in RSA6 and check if it is delta enabled. You will have to initialize with delta to perform delta extraction. RSA7 will give you delta queues in R/3

Delta Extraction for 0FI_GL_6

Hi,
We are facing a problem in the delta extraction for the data source 0FI_GL_6. 0 Records are populated into BW whereas in the Extract checker (RSA3) of the source system shows 1000 records. Moreover the delta queue (RSA7) has an entry for 0FI_GL_6 but no data is displayed inside it.
Kindly advice.
Reagards,
Vidhya

Hi,
This extractor works based on time stamps so wait for a day to get the data.
have a look of the thread :
Re: delta not working for 0FI_GL_6 & 0EC_PCA_1
Regards
Happy Tony

Delta extraction for dunning history is not active

Hi all,
I am loading data to the FI Cube (Financial A/c -> Contract a/c receivables ) Dunning header .
This is a Standard infocube. This cube contains two DSOu2019S 0FC_DS08 , 0FC_DS11. When I starting the data loading from the DSO ( 0FC_DS08 ), I create the INIT package . When creating itself it throwing the error u201C Delta extraction for dunning history is not active u201D
When I check on SDN SAP , ( Use Tcode sbiw. Select 'Settings for apllication-specific datasources (PI) ->Contract Aacounts Receivable -> Make Central Settings'. Then tick 'Delta Extraction for Dunning Items Active'.) I got this link. But I could not proceed this link. Can you explain detailed step by step how to proceed to solve this issue.
Regards,
Baskaran.

Hello Baskaran,
Did you ever solve this issue?
We do not have the link in SBIW (ERP 6.0 EHP6).
Thanks,
Andreas

Problems with Delta Extraction for 0CRM_OPPT_H (no data found)

Hi,
I've some problems with the Delta Extraction of the Infosource 0crm_oppt_h (CRM Opportunities Header). After initialization I get no delta data from the CRM system.
What I already did:
Activated 0crm_oppt_h Data Source (checked functionality with rsa3)
Started Info Package (Init) on BW side (worked fine)
Checked the status of the Data Source on the CRM system using BWA7 ("initial upload" is unmarked; "delta active" is marked and what makes me worry is that the column "Queue exists" in unmarked...)
If I change anything (like Phase, Expected Sales Vol.) in the opportunity, the Delta Extraction get no changes.
Could You help me out, please?
Best regards,
Markus Svec

hi Markus,
try to check oss note 788172
Release Status Released for Customer
Released on 23.03.2005
Priority Correction with high priority
Category Program error
Symptom
No data exists in delta extraction from the CRM server to the BW system for business transactions, if parallel processing is applied as per note 639072. But Data is extracted if parallel processing is switched off.ie. when BWA_NUMBER_OFF_PROCESSES is set to 1,there is data during delta. This applies to the following DataSources:
0BBP_TD_CONTR_1
0CRM_COMPLAINTS_I
0CRM_LEAD_ATTR
0CRM_LEAD_H
0CRM_LEAD_I
0CRM_OPPT_ATTR
0CRM_OPPT_H
0CRM_OPP T_I
0CRM_QUOTATION_I
0CRM_QUOTA_ORDER_I
0CRM_SALES_ACT_1
0CRM_SALES_CONTR_I
0CRM_SALES_ORDER_I
0CRM_SRV_CODES
0 CRM_SRV_CONFIRM_H
0CRM_SRV_CONFIRM_I
0CRM_SRV_CONTRACT_H
0CRM_SRV_PROCESS_H
0CRM_SRV_PROCESS_I
Other terms
DataSources, BWA, initial extraction, delta init, parallel processing, no data in delta.
Reason and Prerequisites
There is an update on the generated delta table which causes data corruption in running delta initializations as the changed delta sets will be deleted with every further update on documents. An open cursor statement is there without fetch data in SMOX3_GET_DATA.
Solution
The problem is solved with the attached corrections.After applying the corrections a new initialization of the affected datasources is necessary.

Delta extraction for a generic datasource

Hi BWers,
I want put in Delta the extraction of a generic datasource.
Currently this generic datasource is based on the table VBPA (Sales Document: Partner). Any time field exists.
We need a time field in order to converse to a Delta extraction. This time field exists in the table VBAP (Sales Document: Item data). In fact two time fields exist: one which is filled at the creation of the sales order (ERDAT), another at the change of the sales order (AEDAT).
The fields VBELN, POSNR and MANDT are keys in the tables VBAP and VBPA.
The table VBAP changes when partner functions is created or changed in a sales order (VBELN) :
- When it is a creation of a new sales order (with new partner functions), a new record is created in VBAP and the field ERDAT (Created on) is filled. The field AEDAT (Changed on) is empty.
- When is a change of an existing sales order, the corresponding record in VBAP changed, and the field AEDAT is filled. ERDAT stays unchanged.
In order to converse to the Delta extraction, i need a only one time-field (calendar day) in RSO2 / Generic Delta.
But there is 2 time-fields ERDAT and AEDAT. So i just need to get AEDAT if it is filled, else if AEDAT is empty I will get ERDAT.
I would base my datasource on a view between VBPA and VBAP with one field which will be filled by AEDAT or ERDAT (with the conditions below). But it seems it is not possible.
Can you give me other ideas ?
Thanks a lot.
Cheers,
Vince.

In order to create a generic delta from two source fields, ERDAT and AEDAT in this case, you're going to have to create your generic extractor from a Function Module. Otherwise you'll only have the standard functionality available to you for creating the generic delta, which allows you to base it on only one column.
Here's a sample you can use, that was created for VBFA, and change for your DataSource.
FUNCTION y_docu_flow.
*"*"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 YSDS_DOCU_FLOW OPTIONAL
*" EXCEPTIONS
*" NO_MORE_DATA
*" ERROR_PASSED_TO_MESS_HANDLER
*& Global Data Declarations
* Type for VBFA Data
TYPES : BEGIN OF ty_vbfa ,
 mandt TYPE vbfa-mandt ,
 vbelv TYPE vbfa-vbelv ,
 posnv TYPE vbfa-posnv ,
 vbeln TYPE vbfa-vbeln ,
 posnn TYPE vbfa-posnn ,
 vbtyp_n TYPE vbfa-vbtyp_n ,
 rfmng TYPE vbfa-rfmng ,
 meins TYPE vbfa-meins ,
 rfwrt TYPE vbfa-rfwrt ,
 waers TYPE vbfa-waers ,
 vbtyp_v TYPE vbfa-vbtyp_v ,
 plmin TYPE vbfa-plmin ,
 erdat TYPE vbfa-erdat ,
 aedat TYPE vbfa-aedat ,
 END OF ty_vbfa .
* Internal Tables and Selection Criteria Structure
DATA : t_vbfa TYPE STANDARD TABLE OF ty_vbfa ,
 l_s_select TYPE srsc_s_select .
* Field Symbols
FIELD-SYMBOLS : <fs_fields> TYPE rsfieldsel.
* Constants
CONSTANTS : c_error_msgty TYPE rslogparms-msgty VALUE 'E' ,
 c_error_msgid TYPE rslogparms-msgid VALUE 'YAERO_WTY_VSR',
 c_error_msgv1 TYPE rslogparms-msgv1 VALUE ' MESSAGE_V1 ' ,
 c_error_msgv2 TYPE rslogparms-msgv1 VALUE ' MESSAGE_V2 ' ,
 c_error_msgv3 TYPE rslogparms-msgv1 VALUE ' MESSAGE_V3 ' ,
 c_error_msgv4 TYPE rslogparms-msgv1 VALUE ' MESSAGE_V4 ' ,
 c_error_msgno TYPE rslogparms-msgno VALUE 999 ,
 c_alias(2) TYPE c VALUE 'A~' ,
 c_vbfa TYPE dntab-tabname VALUE 'VBFA' .
* Maximum Database Lines, Data Package Counter and Cursor
STATICS : s_s_if TYPE srsc_s_if_simple ,
 s_counter_datapakid TYPE sy-tabix ,
 s_cursor TYPE cursor .
* Select Ranges
RANGES : r_erdat FOR vbfa-erdat ,
 r_aedat FOR vbfa-aedat ,
 r_vbelv FOR vbfa-vbelv ,
 r_posnv FOR vbfa-posnv ,
 r_vbeln FOR vbfa-vbeln ,
 r_posnn FOR vbfa-posnn .
*& Processing Logic
* Refresh Internal Table and Clear work area
REFRESH: t_vbfa ,
 e_t_data .
* Check the Extraction Mode (Delta Initialization Or Delta)
IF i_initflag EQ sbiwa_c_flag_on.
* Determine DataSource Validity
 IF i_dsource NE 'YSDDS_DOCU_FLOW'.
* Call Function to Write Log
 CALL FUNCTION 'RSAL_LOG_WRITE'
 EXPORTING
 i_msgty = c_error_msgty
 i_msgid = c_error_msgid
 i_msgno = c_error_msgno
 i_msgv1 = c_error_msgv1
 i_msgv2 = c_error_msgv2
 i_msgv3 = c_error_msgv3
 i_msgv4 = c_error_msgv4.
* Raise Exception
 RAISE error_passed_to_mess_handler.
 ENDIF. " IF i_dsource NE 'YSDDS_DOCU_FLOW'.
* Append the Selection Criteria
 APPEND LINES OF i_t_select TO s_s_if-t_select.
* Fill parameter buffer for data extraction calls
 MOVE : i_requnr TO s_s_if-requnr ,
 i_dsource TO s_s_if-dsource ,
 i_maxsize TO s_s_if-maxsize .
* Append Fields to be Selected
 APPEND LINES OF i_t_fields TO s_s_if-t_fields.
* Add the Alias to Fields
 LOOP AT s_s_if-t_fields
 ASSIGNING <fs_fields>.
 CONCATENATE c_alias
 <fs_fields>-fieldnm
 INTO <fs_fields>-fieldnm.
 CONDENSE <fs_fields>-fieldnm NO-GAPS.
 ENDLOOP. " LOOP AT s_s_if-t_fields..
ELSE. " IF i_initflag EQ sbiwa_c_flag_on
* For First Data Package, Open Cursor
 IF s_counter_datapakid EQ 0.
* Clear Ranges
 CLEAR : r_erdat ,
 r_aedat ,
 r_vbelv ,
 r_posnv ,
 r_vbeln ,
 r_posnn .
* Fill Selection Ranges
 LOOP AT s_s_if-t_select
 INTO l_s_select.
* Determine Selection Range Field Name
 CASE l_s_select-fieldnm.
* Created On Date
 WHEN 'ERDAT'.
 MOVE : l_s_select-sign TO r_erdat-sign ,
 l_s_select-option TO r_erdat-option ,
 l_s_select-low TO r_erdat-low ,
 l_s_select-high TO r_erdat-high .
 APPEND r_erdat.
* Fill the change date too
 MOVE r_erdat[] TO r_aedat[].
* Predecessor Document Number
 WHEN 'VBELV'.
 MOVE : l_s_select-sign TO r_vbelv-sign ,
 l_s_select-option TO r_vbelv-option ,
 l_s_select-low TO r_vbelv-low ,
 l_s_select-high TO r_vbelv-high .
 APPEND r_vbelv.
* Predecessor Document Line Item
 WHEN 'POSNV'.
 MOVE : l_s_select-sign TO r_posnv-sign ,
 l_s_select-option TO r_posnv-option ,
 l_s_select-low TO r_posnv-low ,
 l_s_select-high TO r_posnv-high .
 APPEND r_posnv.
* Successor Document Number
 WHEN 'VBELN'.
 MOVE : l_s_select-sign TO r_vbeln-sign ,
 l_s_select-option TO r_vbeln-option ,
 l_s_select-low TO r_vbeln-low ,
 l_s_select-high TO r_vbeln-high .
 APPEND r_vbeln.
* Successor Document Line Item
 WHEN 'POSNN'.
 MOVE : l_s_select-sign TO r_posnn-sign ,
 l_s_select-option TO r_posnn-option ,
 l_s_select-low TO r_posnn-low ,
 l_s_select-high TO r_posnn-high .
 APPEND r_posnn.
 ENDCASE. " CASE l_s_select-fieldnm.
 ENDLOOP. " LOOP AT s_s_if-t_select..
* Open Cursor on View to Fetch data
* If full load with Selection on Fiscal Year
 IF r_aedat[] IS INITIAL.
* Full Extraction
 OPEN CURSOR
 WITH HOLD s_cursor FOR
 SELECT (s_s_if-t_fields)
 FROM vbfa AS a
 JOIN pnwtyv AS b
 ON a~vbelv EQ b~sdvbeln
 WHERE a~vbelv IN r_vbelv
 AND a~posnv IN r_posnv
 AND a~vbeln IN r_vbeln
 AND a~posnn IN r_posnn
 AND a~rfmng NE 0
 AND a~erdat IN r_erdat
 AND b~sdvbeln NE space.
 ELSE.
* Delta Extraction Using ERDAT and AEDAT
 OPEN CURSOR
 WITH HOLD s_cursor FOR
 SELECT (s_s_if-t_fields)
 FROM vbfa AS a
 JOIN pnwtyv AS b
 ON a~vbelv EQ b~sdvbeln
 WHERE a~vbelv IN r_vbelv
 AND a~posnv IN r_posnv
 AND a~vbeln IN r_vbeln
 AND a~posnn IN r_posnn
 AND a~rfmng NE 0
 AND ( a~erdat IN r_erdat
 OR a~aedat IN r_aedat )
 AND b~sdvbeln NE space.
 ENDIF. " IF r_aedat[] IS INITIAL
 ENDIF. " IF s_counter_datapakid..
* Fetch Records into Interface Table
 FETCH NEXT CURSOR s_cursor
 APPENDING CORRESPONDING FIELDS
 OF TABLE t_vbfa
 PACKAGE SIZE s_s_if-maxsize.
* No More Data, Raise Exception
 IF sy-subrc NE 0.
* Close the Cursor
 CLOSE CURSOR s_cursor.
* Raise Exception
 RAISE no_more_data.
 ELSE.
* Move Extracted Data to Output Structure
 MOVE t_vbfa[] TO e_t_data[].
* Release Memory
 FREE t_vbfa.
* Sort Output Structure
 SORT e_t_data BY vbelv
 posnv
 vbeln
 posnn
 vbtyp_n.
* Delete Duplicate Records from Output Structure
 DELETE ADJACENT DUPLICATES
 FROM e_t_data
 COMPARING vbelv
 posnv
 vbeln
 posnn
 vbtyp_n.
* Increment Data Package Number
 s_counter_datapakid = s_counter_datapakid + 1.
 ENDIF. " IF sy-subrc NE 0
ENDIF. " IF i_initflag EQ sbiwa_c_flag_on
ENDFUNCTION.
Edited by: Dennis Scoville on Jul 16, 2009 8:29 AM
Edited by: Dennis Scoville on Jul 16, 2009 8:29 AM

ALE delta extract for HR master data

We want to create some R/3 delta extracts based on the HR PA* tables using the ALE delta extract function of generic extractor. Has anyone done this before? Are there any OSS notes or documents that I should look at? Thanks!

Hi Bill Faison,
This is very old message. I think your problem must be solved. If it is not then: yes we can extract Data from R/3 with ALE Delta .
You have to perform below steps.
1.     In your Table you need to activate ALE change   pointer.
2.     Create change documents for required table.
3.     Created Generic Extractor with ALE Delta.
Hope this will help.
Let me know if you have any concern or issue in this regards
Best Regards
Sharad Verma

Delta Extraction: Cross Application Table

Hello Gurus,
While enhancing an LO extractor, I understand that we need to create a structure with the fields needed for extraction and then append this to the main extract structure and populate this through the user exit. Now what I am worried about is if the fields happend to be a from a cross application table, how the delta would be taken care of?
As an Example, if I need to add in couple of fields of the delivery tables (LIPS and LIKP) in the Purchasing extractor (2LIS_02_SCL), am I going to get changed fields during the delta extraction?
Thanks...

Is that always true? Please look through the following scenario that Sunmit mentioned in response to Roberto's one of the blogs:
If a scenario demands a cross application enhancement
eg: Enhancing shipment relevant field in a delivery data source/extractor or delivery relevant field in an invoice relevant data source.
Is the delta relevance of these enhanced fields retained by enhancing the datasource at communication structure level? I guess, the delta of these enhanced fields would still be lost, since they are not included in the events that are used to create the delta.
(ie a shipment document (our field) may change without change in delivery document).
Any ideas???

Delta Extraction for Custom Table

Similar Messages

Maybe you are looking for