Standard & Generic R/3 Extractor Differences

Hello,
Can someone please explain what the differences are between a "Standard R/3 Extractor" and a "Generic R/3 Extractor".
I'm slightly confused by the terminology.
Many thanks

Hi Mark,
Standard Extractors are the extractors which are provided by SAP.
Generic extractors are the extractors which are created by the developer according to the requirement.
Hope this helps
Regards
Karthik

Similar Messages

Standard Generic Delta Extractor 0CRM_SRV_COSTS - Delta stop working

Hello all,
Has anyone experienced an issue with the standard generic extractor 0CRM_SRV_COSTS (reside in SAP R/3 system) where its delta suddenly just stop working? The issue is that the datasource keeps extracting the same delta records and from RSA7 and SMQ1, only have the olda data records and no new data coming through (ie. from RSA7 data are only in the Delta Repetition).
The extractor uses Function Module and Numeric Pointer for the delta and I tried to investigate (via RSA2 and ROOSOURCE ) if there is a way to see what field is being used for the Numeric Pointer and how to trace it - but no luck so far.
Has anyone experienced the similar/same issue on other extractor which can provide some inputs?
Any ideas/suggestions will be very much appreciated.
Thanks,
Andy

Maybe someone knows if records in tables SMOXRELP_S and SMOXRELP should match perfectly? I see that table SMOXRELP lacks one record that I have in table SMOXRELP_S.

Delta for generic master data extractor

Hello,
Is it not possible to load deltas for a generic master data extractor?
I have created a generic extractor on R/3 table MEAN (EAN number assigned to material). I have also performed the init run which worked fine, but no deltas are being loaded.
Why is this?
Best regards,
Fredrik

hi,
its possible
how to generic delta
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/84bf4d68-0601-0010-13b5-b062adbb3e33
SAFETY DELTA
check these links
oss note 368739
Symptom
For the setup of summarization levels and summarization data in the Profitability Analysis a 'Safety delta' of half an hour is used. This means, the system only includes records which exist half hour already. You want to reduce this delta in order to get more current data in reporting.
Additional key words
Summarization levels, summarization data, safety delta, time stamp
Cause and prerequisites
The reason for the duration of these safety deltas are possible differences in the clocks on different application servers. If the delta is selected too short, when updating the summarization levels/data, records may not be taken into account. In particular the Account-based Profitability Analysis depends on the sufficient length of the delta, so that update processes which take longer do not cause inconsistencies. For the Costing-based Profitability Analysis a lock is set. If not active update processes exist, it fails and the update terminates.
Solution
The attached source code correction is not part of the standard system. With this change the safety delta is set from 30 to 5 minutes. You should only implement this, if exclusively the Costing-based Profitability Analysis is active in your system. If you also use Account-based Profitability Analysis we do not recommend the change for the above-mentioned reasons.
Generic delta safty intervals
oss note 392876
safety interval
0FI_GL_4 Safety Delta
Genric delta fro table
check this thread which already discussed about this topic
Generic Extractor - Delta
Shreya

Function Module in a Generic Function Module Extractor

I want to use a generic function module (ZFM_CONNECTION_DETAIL) in a Generic Function Module based Extractor.
After Creating, I have checked it in RSA3... Data is showing properly on the Extractor Check.
And replicated on BW side, after triggering the extractor using infopackageu2026 only one record is coming on the target side (BW).
And one job is running endless on the source system.
Generic extractor on the normal code is working properly on both sides.
But problem occurs while I was using Function Module in the Generic function Module extractor.
Waiting for a Reply with solution...........
Hi Siegfried Szameitat,
I have searched a lot to find out the solution of my Question (Problem). But there is no solution for the problem I have.
Please let me to find out a proper solution of my issue....
Thanks

FUNCTION zcrm_questionnaire.
Its a full Load...
Codes are as followed..........
DATA:lv_times     TYPE i.
DATA:lv_datapakid TYPE numc4.
CLEAR:lv_datapakid,lv_times .
STATICS: s_s_if TYPE srsc_s_if_simple,
           sd_no_more_data TYPE flag.
DATA: l_s_select TYPE srsc_s_select.
DATA : s_counter_datapakid LIKE sy-tabix,
          s_cursor TYPE cursor.
RANGES : date FOR zresult_lt-date.
DATA: lv_count TYPE i VALUE 1.
IF i_initflag = sbiwa_c_flag_on.
Initialization: check input parameters
                buffer input parameters
                prepare data selection
Check InfoSource validity
    CASE i_dsource.
      WHEN 'ZCRM_QUESTIONNAIRE'.
      WHEN OTHERS.
        IF 1 = 2. MESSAGE e009(r3). ENDIF.
        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.
    s_s_if-requnr    = i_requnr.
    s_s_if-dsource   = i_dsource.
    s_s_if-maxsize   = i_maxsize.
    APPEND LINES OF i_t_fields TO s_s_if-t_fields.
ELSE.                 "Initialization mode or data extraction
    IF NOT sd_no_more_data IS INITIAL.
      RAISE no_more_data.
    ENDIF.
    LOOP AT s_s_if-t_select INTO l_s_select .
      MOVE-CORRESPONDING l_s_select TO date.
    ENDLOOP.
    DATA : v_questionire TYPE crm_svy_db_sid.
    DATA : itab_questionire TYPE zsurveyid.
    DATA : e_tt_data_get TYPE zresult_lt OCCURS 10.
    v_questionire = 'CALL CENTER'.
    APPEND v_questionire TO itab_questionire.
    v_questionire = 'METER INSTALLATION TEAM'.
    APPEND v_questionire TO itab_questionire.
    v_questionire = 'METER READING & BILLING'.
    APPEND v_questionire TO itab_questionire.
    v_questionire = 'NO SUPPLY'.
    APPEND v_questionire TO itab_questionire.
    v_questionire = 'CASH COLLECTION CENTER'.
    APPEND v_questionire TO itab_questionire.
    v_questionire = 'STREET LIGHT'.
    APPEND v_questionire TO itab_questionire.
    v_questionire = 'CONSUMER CARE CENTER'.
    APPEND v_questionire TO itab_questionire.
    v_questionire = 'WEBSITE'.
    APPEND v_questionire TO itab_questionire.
    DATA : counter TYPE i,
          high LIKE sy-datum,
           low LIKE sy-datum.
    CONCATENATE
    l_s_select-high+6(4)
    l_s_select-high+3(2)
    l_s_select-high+0(2)
    INTO
    high.
    CONCATENATE
    l_s_select-low+6(4)
    l_s_select-low+3(2)
    l_s_select-low+0(2)
    INTO
    low.
    BREAK-POINT.
   do i_maxsize times.
    CALL FUNCTION 'ZCRM_SURVEY_REPORTING'
      EXPORTING
        e_date_frm    = low
        e_date_to     = high
        e_questionire = itab_questionire
      CHANGING
        it_result     = e_tt_data_get.
    IF sy-subrc IS INITIAL.
      e_t_data[] = e_tt_data_get[].
      APPEND e_t_data.
    ELSE.
      EXIT.
    ENDIF.
     sd_no_more_data = 'X'.
ENDIF.              "Initialization mode or data extraction ?
ENDFUNCTION.
lk

ACE SSL Sticky class-map generic vs class default differences.

There was a thread recently titled "ACE 3.0(0) SW / LB with SSL Session-ID" where Giles Dufour outlined a configuration for an ACE performing sticky based on SSL Session ID.
Can anyone explain the benefits and differences of using a specific class-map generic such as this:
class-map type generic match-any SSL-v3-32
2 match layer4-payload regex "\x16\x03\x00..\x01.*"
3 match layer4-payload regex "\x16\x03\x01..\x01.*"
Versus just matching class default?
So if I have a configuration such as this:
policy-map type loadbalance generic first-match SSL-v3-Sticky
class SSL-v3-32
sticky-serverfarm ssl-v3
vs
policy-map type loadbalance generic first-match SSL-v3-Sticky
class class-default
sticky-serverfarm ssl-v3
What's the benefit or drawback?

The SSL session id is only available in version 3.0.1 and 3.1.1
So you can match this particular version and then attempt to do stickyness.
You are guaranteed to find what you're looking for.
If you match a class-default it means you apply stickyness to any version of ssl packet.
So there is a risk to misinterpret the content of the packet and stick on something else than the session id.
Gilles.

Standard function for returninf time difference in days and hours.

Hello all,
Can somebody tell me whether there exists some standard function module which can calculate the time difference and returns the calculated time in the form of days and hours ?
e.g. the time difference between the date 1.12.2007 from 7.00 pm to the date 1.1.2008 till 9.00 pm is
30 days and 2 hours or 30 : 2.
answer as soon as possible.
Thanks and regards,
me

Thanks a lot ya..
thats an absolutely correct solution to my problem. )

Generic extraction :DTFIAP_3, Extractor: BWFID_GET_FIAP_ITEM

Hi all,
have a nice day for all.
generic extraction ,Source structure: BSIK, BSAK
Extractor: BWFID_GET_FIAP_ITEM
Extract structure OLTP: DTFIAP_3
some fields are append the structure but in funtion module ,
where i am going to declare the data: fieldname, table name ,any one before write the code for finance account payable please send me the coding part.
Regards
Priya
FUNCTION BWFID_GET_FIAP_ITEM.
""Lokale Schnittstelle:
*" IMPORTING
*"     VALUE(I_ISOURCE) TYPE SBIWA_S_INTERFACE-ISOURCE OPTIONAL
*"     VALUE(I_RLOGSYS) TYPE RSAOT_LOGSYS OPTIONAL
*"     VALUE(I_REQUNR) TYPE SBIWA_S_INTERFACE-REQUNR
*"     VALUE(I_MAXSIZE) TYPE SBIWA_S_INTERFACE-MAXSIZE DEFAULT 1000
*"     VALUE(I_INITFLAG) TYPE SBIWA_S_INTERFACE-INITFLAG OPTIONAL
*"     VALUE(I_UPDMODE) TYPE SBIWA_S_INTERFACE-UPDMODE OPTIONAL
*"     VALUE(I_READ_ONLY) TYPE SBIWA_FLAG DEFAULT 'X'
*" TABLES
*"      I_T_SELECT TYPE SBIWA_T_SELECT OPTIONAL
*"      I_T_FIELDS TYPE SBIWA_T_FIELDS OPTIONAL
*"      E_T_DTFIAP_3 STRUCTURE DTFIAP_3 OPTIONAL
*" EXCEPTIONS
*"      NO_MORE_DATA
*"      ERROR_PASSED_TO_MESS_HANDLER
...general data declaration...........................................
DECLARE_GENERAL.
...local data.........................................................
DATA: T_DELTA_DATA TYPE BWFI_T_DATA_BSIK WITH HEADER LINE.
...begin of main program coding.......................................
...function module called in intialization mode? .....................
IF NOT I_INITFLAG IS INITIAL.
...set data base tables to be read....................................
    REFRESH R_TABLE.
    APPEND_R_TABLE: TABLE_BSIK,
                    TABLE_BSAK.
...general initialization of infosource...............................
    GENERAL_DELTA_INITIALIZATION.
...Generate database index (if necessary).............................
   if s_updmode = sbiwa_c_updmode_deltainit
   or s_updmode = sbiwa_c_updmode_delta.
     call function 'BWFIU_GENERATE_DB_INDEX'
       exporting
         i_tabname                          = 'BSID'
         i_isource                          = i_isource
       exceptions
         no_index_required                  = 1
         error_passed_to_mess_handler       = 2
        OTHERS                             = 3
     if sy-subrc = '2'.
       raise error_passed_to_mess_handler.
     endif.
     call function 'BWFIU_GENERATE_DB_INDEX'
       exporting
         i_tabname                          = 'BSAD'
         i_isource                          = i_isource
       exceptions
         no_index_required                  = 1
         error_passed_to_mess_handler       = 2
        OTHERS                             = 3
     if sy-subrc = '2'.
       raise error_passed_to_mess_handler.
     endif.
     call function 'BWFIU_GENERATE_DB_INDEX'
       exporting
         i_tabname                          = 'BWFI_AEDAT'
         i_isource                          = i_isource
       exceptions
         no_index_required                  = 1
         error_passed_to_mess_handler       = 2
        OTHERS                             = 3
     if sy-subrc = '2'.
       raise error_passed_to_mess_handler.
     endif.
   endif.
...check initialization options for old data source 0FI_AP_3..........
    IF S_UPDMODE = SBIWA_C_UPDMODE_DELTAINIT.
      CLEAR: S_OLD_SOURCE_ACTIVE,
             LD_LINES.
      CALL FUNCTION 'RSA1_SINGLE_OLTPSOURCE_GET'
           EXPORTING
                I_OLTPSOURCE = '0FI_AP_3'
                I_OBJVERS     = 'A'
                I_RLOGSYS     = S_RLOGSYS
           IMPORTING
                E_T_ROOSPRMSF = L_T_ROOSPRMSF
           EXCEPTIONS
                NO_AUTHORITY = 1
                NOT_EXIST     = 2
                INCONSISTENT = 3
                OTHERS        = 4.
      IF SY-SUBRC IS INITIAL.
        DESCRIBE TABLE L_T_ROOSPRMSF LINES LD_LINES.
        IF LD_LINES <> 0.
          MOVE 'X' TO S_OLD_SOURCE_ACTIVE.
        ENDIF.
      ENDIF.
    ENDIF.
...convert selection criteria into internal format....................
    REFRESH T_INTERNAL_FISEL.
    CALL FUNCTION 'BWFIU_CONVERT_ICSEL_TO_FISEL'
         TABLES
              I_SELECTION_TABLE = T_EXTERNAL_FISEL
              I_FISEL           = T_INTERNAL_FISEL
         EXCEPTIONS
              OTHERS            = 1.
...set fields to select from database.................................
    CALL FUNCTION 'BWFIU_TRANSFORM_FIELDLIST'
         EXPORTING
              I_TABLE       = 'BSIK'
         TABLES
              I_OLAP_FIELDS = I_T_FIELDS
              E_OLTP_FIELDS = T_FIELDLIST
         EXCEPTIONS
              OTHERS        = 1.
    CLEAR   T_FIELDLIST_BSEG.
    REFRESH T_FIELDLIST_BSEG.
...append logical system to selection criteria........................
    CALL FUNCTION 'BWFIU_GET_AWSYS_SELECTION'
         TABLES
              I_FISEL = T_INTERNAL_FISEL
         EXCEPTIONS
              OTHERS = 1.
...get timestamps for selection (dependent on update mode)............
    CALL FUNCTION 'BWFIT_GET_TIMESTAMPS'
         EXPORTING
              I_OLTPSOURCE                = S_ISOURCE
              I_LEADING_SOURCE            = LEADING_SOURCE
              I_UPDMODE                   = S_UPDMODE
         IMPORTING
              E_DATE_LOW                  = SD_DATE_LOW
              E_DATE_HIGH                 = SD_DATE_HIGH
              E_TZONE                     = SD_TZONE
              E_DAYST                     = SD_DAYST
         EXCEPTIONS
              TIME_INTERVAL_NEGATIVE      = 1
              TIMESTAMPS_WRONG            = 2
              LEADING_TIMESTAMP_NOT_FOUND = 3
              OTHERS                      = 4.
    CASE SY-SUBRC.
      WHEN 1.
        RAISE NO_MORE_DATA.
      WHEN 2.
        RAISE ERROR_PASSED_TO_MESS_HANDLER.
      WHEN 3.
        RAISE NO_MORE_DATA.
    ENDCASE.
...move timestamp into selection criteria.............................
    IF S_UPDMODE NE SBIWA_C_UPDMODE_FULL.
      MOVE: SPACE        TO T_INTERNAL_FISEL,
            'CPUDT'      TO T_INTERNAL_FISEL-FIELDNM,
            'I'          TO T_INTERNAL_FISEL-SIGN,
            'BT'         TO T_INTERNAL_FISEL-OPTION,
            SD_DATE_LOW TO T_INTERNAL_FISEL-LOW,
            SD_DATE_HIGH TO T_INTERNAL_FISEL-HIGH.
      APPEND T_INTERNAL_FISEL.
      MOVE: SPACE        TO T_INTERNAL_FISEL,
            'AEDAT'      TO T_INTERNAL_FISEL-FIELDNM,
            'I'          TO T_INTERNAL_FISEL-SIGN,
            'BT'         TO T_INTERNAL_FISEL-OPTION,
            SD_DATE_LOW TO T_INTERNAL_FISEL-LOW,
            SD_DATE_HIGH TO T_INTERNAL_FISEL-HIGH.
      APPEND T_INTERNAL_FISEL.
    ENDIF.
...function module called in data extraction mode (I_INITFLAG = ' ')..
ELSE.
...get data...........................................................
    IF S_UPDMODE NE 'S'.
      GET_DELTA_DATA.
    ELSE.                               "Simulation of Delta-Init
      CLEAR S_CURSOR_FLAG.
    ENDIF.
...process selected data..............................................
    REFRESH E_T_DTFIAP_3.
    LOOP AT T_DELTA_DATA.
      CALL FUNCTION 'BWFIU_CONVERT_FIAP_ITEM'
           EXPORTING
                I_S_DELTA_DATA = T_DELTA_DATA
                R_FISCPER      = R_FISCPER
           TABLES
                E_T_DTFIAP_3   = E_T_DTFIAP_3.
    ENDLOOP.
...migration from old extractor 0FI_AP_3 to the new 0FI_AP_4..........
    IF S_UPDMODE = SBIWA_C_UPDMODE_DELTAINIT AND
       S_OLD_SOURCE_ACTIVE = 'X'.
      LOOP AT E_T_DTFIAP_3.
        CALL FUNCTION 'FBW4_INIT_SELECT_CHECK'
             EXPORTING
                  I_OLTPSOURCE = '0FI_AP_3'
                  I_STRUCTURE = E_T_DTFIAP_3
             EXCEPTIONS
                  INVALID_ITEM = 1
                  OTHERS       = 2.
...reject record, if it is a valid record of the old extractor........
        IF SY-SUBRC NE 1.
          DELETE E_T_DTFIAP_3.
        ENDIF.
      ENDLOOP.
    ENDIF.
...if there is no more data to read: set corresponding flag...........
    IF S_CURSOR_FLAG IS INITIAL.
      NO_MORE_DATA_FLAG = 'X'.
...and write timestamp interval into table BWOM2_TIMEST...............
      CALL FUNCTION 'BWFIT_UPDATE_TIMESTAMPS'
           EXPORTING
                I_OLTPSOURCE = S_ISOURCE
                I_UPDMODE    = S_UPDMODE
                I_DATE_LOW   = SD_DATE_LOW
                I_DATE_HIGH = SD_DATE_HIGH
                I_TZONE      = SD_TZONE
                I_DAYST      = SD_DAYST
                I_READ_ONLY = S_READ_ONLY.
    ENDIF.
...delta-init simulation: raise no_more_data..........................
    IF S_UPDMODE = 'S'.
      RAISE NO_MORE_DATA.
    ENDIF.
ENDIF.
ENDFUNCTION.

Gentlemen,
Please be aware, enhancing GL, AP and AR datasource are completely different then enhanceing LIS datasource or most other datasources. You cannot (the last time I knew) populated fields in the User Exit for GL, AP and AR, to enhance these, you need to follow this OSS message to the "t".
/Steve
OSS message: 410799.
See below OSS message:
Symptom
The extraction structures for datasources 0FI_GL_4 (General ledger: line item), 0FI_AP_4 (vendors: line item) and 0FI_AR_4 (customers: line item) should be enhanced by additional fields.
By doing so, additional information can be transferred for each line item from the R/3 system to the BW system.
Other terms
(for example, customer or vendor master data).
Customer enhancement, extraction structure, extraction, FI_GL, general ledger, FI-AP creditors, FIAP vendors, line items, datasources/infosources:
0FI_GL_4, 0FI_AP_4, 0FI_AR_4
Reason and Prerequisites
There is missing documentation on the customer enhancement of datasources/infosources 0FI_GL_4, 0FI_AP_4, 0FI_AR_4
Solution
In the R/3 source system, the following structures participate in the extraction of line items from the applications FI-GL, FI-AP, FI-AR:
Applic. datasource read structure extractionsstr. customer-INCLUDE
FI-GL 0FI_GL_4 BSIS DTFIGL_4 CI_BSIS
FI-AP 0FI_AP_4 BSIK DTFIAP_3 CI_BSIK
FI-AR 0FI_AR_4 BSID DTFIAR_3 CI_BSID
The data sources provide the fields of the assigned extraction structure from the R/3 source system to the BW system.
These extraction structures can be enhanced by creating the respective customer include in the data dictionary of the R/3 source system. After creating this, generate the customer include in the data dictionary.
The fields for the customer enhancement in the customer include has to be filled during the data extraction in the R/3 source system. In doing so, two cases arise:
1. All the fields of the customer enhancement in the customer include are contained in the read structure (see the table above).
           Then no additional action is required. The fields of the customer enhancement are filled automatically by the datasource from the assigned read structure via "move-corresponding".
           Example:
           The extraction structure DTFIGL_4 for datasource 0FI_GL_4 (General ledger: line item) should be enhanced by the VALUT (value date) field.
           To do this, create structure CI_BSIS in the data dictionary of the R/3 source system and include the VALUT field in it. The data dictionary in the R/3 source system shows that the VALUT field is contained in the read structure of the datasource (table BSIS). For that reason the VALUT field is automatically filled by datasource 0FI_GL_4.
           ATTENTION:
           By using Note 430303 you can enhance DataSource 0FI_GL_4 by all fields from table BSEG (instead of BSIS); then the fields are filled automatically in the extractor.
2. Fields of the customer enhancement in the customer include are not contained in the read structure (see the table above).
            In this case you have to program a function module to fill the field of the customer enhancement. To do this, there is a Business Transaction Event available (open FI interface for process 00005021). Create any function module you like and use function module SAMPLE_PROCESS_00005021 as a template for the interface (input parameter, changing parameter).
           Interface of function module SAMPLE_PROCESS_00005021:
            Input-parameter I_OLTPSOURCE: datasource that is currently extracting data from the R/3 source system.
            Changing-Parameter C_STRUCTURE: Extraction structure of the data source currently extracting including fields from the assigned customer include. When you call this customer defined function module, all the fields of the extract structure are transferred filled.
           Check whether the type pool SBIWA is declared in the TOP include of the function group.
If not, add it with the statement TYPE-POOLS: SBIWA.
           Then maintain table TPS31 with Transaction SM30. Create the following entry:
           PROCS LAND APPLK FUNCT
           00005021 <fname>
           <fname> stands for the customer defined function module.
            By doing so, the function module you defined is called for each extracted record. Note that in this case the performance of the extraction may be reduced significantly regardless of the table read and the complexity of the programmed logic.
           Example:
           You want to enhance the extraction structure DTFIAR_3 for datasource 0FI_AR_4 (customers: line item) by the ORT01 (city) field from the customer master record.
            To do this, create structure CI_BSID in data dictionary of the R/3 source system and include the ORT01 field in that. The data dictionary in the R/3 source system displays that the ORT01 field is NOT contained in the read structure of datasource 0FI_AR_4 (Table BSID).
            Therefore you have to program a function module that reads the customer master in the R/3 system (table KANN1) and fills the ORT01 field of the customer enhancement. In the changing parameter C_STRUCTURE the filled fields of the extraction structure DTFIAR_3 are available to you. With the KUNNR field of extraction structure DTFIAR_3, you can select the respective master data record from table KNA1 and determine field ORT01 of the customer enhancement.
After you create the customer include in the R/3 source system you have to postprocess the accompanying datasource with Transaction RSA6. Select the application component according to the above table and change the datasource that fits the customer include. The "Hide fields" flag should be removed in the field list for the fields of the customer include. Then save the field list.
If the fields of the customer include is not displayed in Transaction RSA6, refer to note 415530.
Then you have to replicate the enhanced datasource again in your BW system. Select the infosource that belongs to the datasource in the Administration Workbench of your BW system (Transaction RSA1 --> Modeling --> InfoSources) and replicate the datasource from the R/3 source system (right mouse button on the appropriate R/3 source system for the infosource).
You have to create the appropriate infoobjects for the fields of the customer enhancement in the BW system if they do not already exist.
Then in your BW system make sure that the accompanying infosources (communication structures and transfer rules) and data targets (ODS objects and InfoCubes) have been extended by the new field or infoobject. All the objects which have been changed in the BW system must also be activated there.

Generic Fn Module Extractor Issue

Hi guys,
As i understand the function module extraction, when i use the open cursor and if i have to delete the datA in e_t_data, what kind of impact does it have in my data package as the size gets reduced by the above operation.
Thanks,
Your help is greatly appreciated.

The thing is i open the cursor with selection fields right, what if i have
to manipulate this data reduce it in the function module, the datapacket size gets reduced right. so what should i do to tackle this and also what should i do so if the data packet data from each packet is interrelated.
Thanks,
Your help is greatly appreciated

Delta loading through Generic extractor - function module not found

Hi,
I'm working on a BW3.5 system and we have some generic delta FM extractors. One of these is called ZBW_CONF_DELTA and the FM is also called ZBW_CONF_DELTA. It is a delta-enabled extractor. Whenever an extraction is done in the init delta mode, the data gets picked up from SAP.
However, whenever we load subsequent deltas, the extractor brings zero records. When I look in the SM37 logs in R/3, it says "Function module /BIC/QIZBW_CONF_DELTA0001 does not exist"
I'm not sure where the "/BIC/QIZBW_CONF_DELTA0001" function module name came from, because I haven't given it like that (if I did, the init load would also have failed).
Due to this problem, I'm unable to perform any delta loads. Is there anything I could be doing to fix this?
Regards

Hi,
First check how extractor works in R/3 side using RSA3
Make a full load.
Now check the generic delta field of your generic extractor, lets say changed on date.
Do the SAP transaction ( take help from some Functional COnsultant ) to update that delta field. Note that record.
Now if u do the delta load with same extractor, you are suppose to get that record.
If not then there is some problem with FM or extracor.
Let me know what happens.
Thank-You.
Regards,
Vinod

Generic Extractor: enriching GL Data with Purchasing Data

Experts,
This is my first time with Generic Extractor.
Requirement:
We have a requirement to enrich GL data with Purchasing data via the Material Document Number.
I need to provide this upto to the datawarehouse layer wherein another team will take over.
Solution idea:
Material Document is not part of the datasource 2LIS_02_SCL.
a. Should I enhance this datasource to include material number OR
b. Develop a concept to create a generic delat enabled extractor that pulls data from EKBE, GR and IR information.
In EKBE multiple material documents can exist per PO. The extractor returns 2 record per PO (before and after image) with the updated information.So if we have the first GR with Material document 901 and then a second GR with material doc 902 the extractor loads 3 records. New record, Before image and after image and the only one stored in BI is the after image. material doc would have value 902 if enhanced.
For the generic extractor approach the the ability to load deltas is crucial, since the EKBE table is very big. Maybe
"CPUDT-Day On Which Accounting Document Was Entered" and "CPUTM-Time of Entry" can be leveraged as delta hook.
Any ideas???
Thanks,
Jain

No one answered

Generic FM extractor with Delta

Hello all,
I am trying to create a delta function module extractor on a table. I have creation date ANDAT, last change date AEDAT and a deletion flag on the table.
FM has to handle history, new and changes.
How can I generate delta? Can I just use RSO2 to set up delta? How can it be done? Also, can I get the code for a generic FM delta extractor?
Please help.
Thanks,
Anirudh.

Hi Sajeed,
So, I do not have to handle delta in the extractor at all? Just create a function module based extractor with all the fields and actually take care of delta in the infopackage??
The creation date is for newly created records and the change date is for changed records.
My email is [email protected]
Thanks,
Anirudh.

Severe Magenta Cast Some Cameras Adobe Standard

Adobe Standard
Generic Daylight Profile for Canon G10 Created by me with a Macbeth Chart and the DNG Profile Editor (not of this scene specifically) and Adobe Standard as the Base Profile.
Images from a Canon Powershot G10. Both have exactly the exactly the the same settings. White Balance Auto and then Auto Tone with Brightness set back to default of 50.
Download DNG file here
Download Generic Daylight Profile for G10 used in this example here.
Happens with my 5D (original) as well. Does not happen with Leica M9 and can't say for any other cameras at this time.

Actually, I wouldn't expect that much difference between most camera sensors under the same controlled conditions. I suspect if you divided up the Adobe Standard profiles into sensors and other factors more meaningful than make and model, the differences might be more obvious.
So, for example, I see little difference between a Nikon D80 and a Canon (which uses the same APC sensor technology [down to the manufacturer], I think) there is little difference. But when I compare Nikon and Ricoh I see a much more obvious difference. The fact is that the image guts of most DSLRs these days are made from one of at most three manufacturers. The majority come from two. A few others that I recall had similar sensors and image processing engines also seemed pretty similar.
The Adobe Standard is not about trying to pull the wool over our eyes. It is about establishing a baseline for raw image manipulation. The fact that most sensors and bodies will really respond pretty closely aside, there could be outliers. Making the standard based on the make and model allows for a more natural way to handle presets and what-not from the point of an application. The fact that, under the covers, most cameras really respond quite similarly in similar median conditions is not all that interesting.
It is at the extreme edges of image reproduction that the makes, models and even specific bodies will be most drastic (which is why getting to know your camera in extreme shooting conditions is important, and why being able to make your own profiles is so powerful.)
At any rate, if your particular make and model (or even specific body) is not to your liking, it is pretty easy to make your own standard. Because I don't have a studio, I've gone ahead and made "standards" like based on things like time of day (for natural light) or "my living room" which sometimes give me an easy out. No one needs to use Adobe Standard. Heck, if you really like the in-camera settings and Adobe profiling doesn't work then it may be that the vendor software is the way to go. Double heck, some professionals still think this whole raw thing is stupid and shoot JPEG. This solves a whole raft of problems -- decisions one doesn't even have to make. Just get exposure right and go!

If Generic R3 Data Extraction does it all, why other extraction techniques?

Hi,
I am reviewing some documents about data extraction and I have a quick question.
With
1. standard Business Content extraction and
2. Generic R/3 Data Extraction (which by definition, can be used to extract any data from R/3)
why are there other techniques for extraction?
For example, I do not recall but I remember that there was a different technique to extract FI data and another to extract CO data.
Why is the need for these other techniques if Generic R/3 Data Extraction can do it all?
(By the way, if you recall the FI and CO extraction techniques you may give me some hints)
Thanks

Hi Amanda,
Would like to put something from my side as well.
Generic extractor are a strong a tool but with lot of limitations like...if you have seen it there...only three kinds of delta menthod is supported and that too changes to only one field is captired and cannnot be used with cluster and pool tables which form a mojor portion of FI domain.Even if you can write FM for that but then it has its limitations with delta enabeling and capturing delta and performance which again leaves lot of work to be done by us.
What SAP has coded for standard FI-CO data sources internally is very complex and if tried to be achieved through standard generic data sources and coding all the time......will make SAP very tough to be used by masses and to learn for the beginners like me and you.
A standard transaction in SAP may hit several tables and to capture exact changes may require to write quite a complex logic and lot of thorough testing.
We do build out own data sources for FICO as well but most of the time the need is satisfied by the existing data sources.
I think SAP knows what kind of reports are required by the users in R/3 as they did thorough study about this and then came up with these extractors to make possible same kind of reports in BW.
This is the advantage of SAP over other tools that it has inbuilt logic to extract the data from standard tables and capture all kind of changes in delta and manage delta easily without being bothred too much about internal complications...all you have to do intially is start the work by having a knowledge of FI and BW data sources...slowly you can start playing with them and come up with customized one and explore SAP.....as your requirement grows.
Rest others have already explained.
Thanks
Ajeet

Function Module extractor extracting as a Single Package?

Hi All,
I have created a generic function module extractor, which works fine, but extracts all the records in a single package. The default is set in SBIW as 50000 records. But right now I have only 2500 records. But I changed the packet size to 100 in my info package setting and also specified as 100 with in the function module.
But still I get all the data come as a single package of 2500. I want to make sure that this extractor will not create any problem in production, so I want to test the data packet size. Any suggestion. I have used he standard function module DATASIMPLE and I do setup I_MAXSIZE as 100 in the IMPORT parameter in the function and hav ethe following code in the function module...
         APPEND mgremp_stru to E_T_DATA.
          mseq = mseq + 1.
          if mseq = 100.
             G_COUNTER_DATAPAKID = G_COUNTER_DATAPAKID + 1.
             mseq = 0.
          endif.
    endloop.
    IF SY-SUBRC <> 0.
       RAISE NO_MORE_DATA.
    ENDIF.
    S_COUNTER_DATAPAKID = S_COUNTER_DATAPAKID + 1.
Any Suggestions?
Thx,
Alex.

Ramesh,
The simple truth is that what ever you define as a data structure for E_T_DATA should be exactly matching to your selections in the CUSOR. My scenario is way too trichy not just because too many sqls, but because of the nature of HR Tables. Same field will have two different values such as in one record SOBID refers to Org Unit, in the next record the same is Person and in the next record it is Position. So I should have the same field 3 times in a single record. But it is not possible. SO what I did was found 3 different fields whose length and type are same as what I need and selected them but inside my function module I manipulated with internal tables. So the extractor thinks I declare cursor for the same fields I defined in the data source (the value you use in E_T_DATA) and extract them in the FETCH. In the fetch all it checks internally is that whether the only the CURSOR selected fields are extracted , because you will update the E_T_DATA. I know this is little more than what I explained here, but this is the concept.
I am planning to have a weblog or a white paper published on this in a week or two.
If this idea helps assign points.
Goodluck,
Alex.

Urgent Help in Standard Costing

Dear sap friends
Company want to use standard costing in sap, however they are changing their standard costs sometimes in the middle of the month and various times per month. The discussion is around what the best practice should be and to understand why theya re changing these so frequently. Accordingly we will need to find a soultion for them and/ or they need to be educated and use standard costing as it should be.
Kindly give me your advise about the standard price changing every time in the best practise. what i suppose to give them feed back and what is the best soultion i can provide the client.
Regards,
Henry
Moderator: Please observe the [forum rules|/thread/931177 [original link is broken];. This is the second thread of yours we have to lock due to an inappropriate thread title - please DO NOT use the word "urgent" in the title.
Edited by: Karl Helm on Jul 11, 2008 9:58 AM

Hi Satesh,
As per your email we can change the standard price only period end. if customer wants to change middle of month or weekly what i suppose to be do.. what advice i can give to the client. also can you explain to me about standard price, and document price. i got a note standard price and document price difference will go to variance. please explain standard price and documnet price. When they are calcuallating vairance.
Regards
Paul

Standard & Generic R/3 Extractor Differences

Similar Messages

Maybe you are looking for