Displaying Application is specified in Generic Extraction

Hi All,
I am working on Generic Extraction,
I had created ZMASTER in SE11 and in next screen I entered 2 fields 1 is MATNO and MATNAME,
and I had assigned MATNO as Primary Key and Inti option, while I am entering ZMATNO and activating it is displaying Application is not specified
What does that mean, I tried in several ways but result has not come
2) when I click F4 at Dataelemts it is leading to Varient screen and asking to assign or create a variant(thugh I created its not getting activated my cretaed fields
Pls tell me the scenario or any other methods and about the VARIENT
i just want to create some fields and enter data manually
Thanks for the friends who is going to help me in it
Mohhan

Hi Mohhan..........
U r trying to create a table ZMASTERt..............In that table u are using two fields......MATNO and MATNAME.........right?.......
Then where did u get this ZMATNO...............did u want to create field also...............?
Look........we can create field....................Domain ...........as well as Data element......but for that u hav to use the correct sequesnce............
First u hav to create a Domain.......assign the Domain to a Data element............then u hav to create a field.........and assign this Data element in to that field...........then athe u can use this field to create a table............u can use an existing Domain also........and using it create a field............that is also possible..........I think u r doing something wrong........
Field,Domain...........u can create these in SE11........
Regards,
Debjani.........

Similar Messages

Generic Extraction-example

hello EXPERTS
I am trying to give one presentation about 'Generic Extraction using View'...I know how to explain the process.But as I donot have project experience,I have never worked with Generic Extraction.
Can any one give an example where they used generic extraction(by view) on SAP standard tables.Its enough if you can mention the fields you used and from which tables you took these fields?
Thanks
S

Hi,
Processing steps for creating the Generic Datasource by useing View:
1.Goto RSo2.
Datasource can be created for
a). Transaction Data
b). Master data Attributes
c). Master data Text
2.Specify Application component(SD/MM..)
3.There are three extraction methods to fill datasource.
    i).Transparent table or Database view
    ii).InfoSets of the SAP query
    iii).Using a Function Module
4.Select extraction method extracts the data from a transparent table or database view.
5.select Extraction from View, then we have to create the View.
   a).specify the view name.
   b).choose the view type (Database view) from bellow mentioned views.
      Database view.
      projection view.
      maintainance view.
      help view.
6. Specify Tables and Join Conditions and define view fields.
7. Assign View to Datasource
8. Once you specify view in Data source, the extract structure willgenerate.
9. then select the filds in selection column.
10. Specify Delta-Specific Field and type.
11. Specify Safety Interval and Delta Type and select Save button.
12. Testing the Generic extraction.
Select Datasource option from menu bar-->select Test Extraction or you can check in RSA3.
Regards,
Suman.

Where to find deltas in generic extraction

hi experts,
could you please explain me tcodes which are used to find the delta data while we go for generic extraction. Also can anyone explain me the full process of extracting the data using
infoset query and function module.
Cheers,
Pragya.

Hi
You can define delta's in generic using " calendr day, numeric pointer, time stamp."
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.
Example for Determining the Selection Interval for a Generic Delta
Safety Interval Upper Limit
The delta-relevant field is a timestamp.
The timestamp that was read last is 12:00:00. Delta extraction begins at 12:30:00. The safety interval for the upper limit is 120 seconds. The safety interval for the delta request is: 12:00:00 to 12:28:00. Upon completion of the extraction, the pointer is set to 12:28:00.
Safety Interval Lower Limit
The delta-relevant field is a timestamp. After images are transferred. In other words, the record is overwritten with the status after the change in BW, for example for master data. Any duplicate records that appear have no effect upon the BW system.
The last changed timestamp is 12:28:00. Delta extraction begins at 13:00. The safety interval for the lower limit is 180secs. The safety interval for the delta request is: 12:25:00 to 13:00:00. Upon completion of the extraction, the pointer is set to 13:00:00.
source: help.sap.com
Hope it helps
kalyan

Give me details about differrent views in generic extraction give details

give me details about differrent views in generic extraction give details such as database view, projection view, help view, etc please give detail

Dear Deba,
Projection view - Just retrieves some fields from a single table.
Help View - This is used for search help.
Database View - This is inner join view of one or more tables
Maintenance View - Helps in creating maintaining data of the application object. The data can be distributed among several tables
Data Base View:
A database view is defined in the ABAP Dictionary and automatically created on the database during
activation. Accesses to a database view are passed directly to the database from the database interface.
The database software performs the data selection.
If the definition of a database view is changed in the ABAP Dictionary, the view created on the database
must be adjusted to this change. Since a view does not contain any data, this adjustment is made by
deleting the old view definition and creating the view again in the ABAP Dictionary with its new definition.
The maintenance status defines whether you can only read with the view or whether you can also write
with it. If a database view was defined with more than one table, this view must be read only.
The data read with a database view can be buffered. View data is buffered analogously to tables. The
technical settings of a database view control whether the view data may be buffered and how this should
be done. The same settings (buffering types) can be used here as for table buffering. The buffered view
data is invalidated when the data in one of the base tables of the view changes.
Maintainance View:
Data that is distributed on more than one table often forms a logical unit, called an application object.
You should be able to display, change and create the data of such an application object together. Users
usually are not interested in the technical implementation of the application object, such as the distribution of the data on several tables.
You can maintain complex application objects in a simple way using a maintenance view. The data is
automatically distributed on the underlying database tables.
All the tables used in a maintenance view must be linked with a foreign key. This means that the join
conditions are always derived from the foreign key in the maintenance view. You cannot enter the join
conditions directly as in a database view.
A maintenance interface with which the data of the view can be displayed, changed and created must be
generated from the definition of a maintenance view in the ABAP Dictionary.
When the maintenance interface is created, function modules that distribute the data maintained with the
view on the underlying tables are automatically generated.
The maintenance interface is generated with the Transaction Generate Table View (Transaction SE54)
or from the view maintenance screen with Environment -> Tab.maint.generator.
Database views implement an inner join. You only get those records which have an entry in all the tables
included in the view.
Maintenance views implement an outer join.
Help View:
A help view is defined analogously to a maintenance view. Help views can only be used as selection
methods in search helps. Since the R/3 System cannot pass the selection directly to the database using
a help view, it must generate its own access routines. The database view should therefore be used as
selection method in preference to the help view.
http://help.sap.com/saphelp_nw2004s/helpdata/en/cf/21ecf9446011d189700000e8322d00/frameset.htm
Difference between "Help View" and "Search Help"
http://help.sap.com/saphelp_nw04/helpdata/en/cf/21ed06446011d189700000e8322d00/frameset.htm
for more detailed info look on:
http://www.sap-img.com/abap/what-is-the-different-types-and-usage-of-views.htm
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/abap+dictionary&
Regards,
Ram.

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 extractions

Can anyone give me a screen shots of how to do generic extractions by extraction by view/table & also how to add fields of different tables in a view method.pls suggest.
Thanks in Advance.

Dear Suresh,
Generic Data Source is created whenever the SAP Content Data source doesnu2019t support our requirement And then we can create a data source with respect to our requirement.
There are two ways you can enter into the creation screen of generic data source:
1)     By entering SBIW as the T-code.
Expand the Generic Data sources icon and press on the clock symbol (IMG activity)
Or      Instead of all the above steps you can simply use T-code: RSO2
Now you have the option to create, change or display a Data source for transaction Data, Master Data attributes or Texts.
Give a Proper technical name of the Data Source you want to create and press create
Now select the Application Component in which you want to create the datasource
After selecting the application component. Fill the Description fields. And now select the mode of extraction you want to do like
1)     Extraction from View/Table
2)     Extraction from SAP Query
3)     Extraction by function module
And once you give the name of the view/table from where you want to extract. Press Generic delta button at the top.
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.
After giving the required selections of all the above options save the data source.
Then you will get a screen where you have options like:
1)     Selection:
Check it when you want to select the range of the values to be picked from this field. Once we select this field, it will be available in the infopackage under the Data Selection tab for selecting the range.
2)      Hide Field:
Check it when you donu2019t want this field to be extracted.
3)      Inversion:
This will give the negative value of the field.
4)       Field Only:
If a field is required only for certain calculation purpose and not for extraction then we can check this option.
Once we give all the above selections, save it and replicate the Data source in BW.
Also check these links for Views..
http://help.sap.com/saphelp_nw04/helpdata/en/cf/21ed06446011d189700000e8322d00/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/cf/21ed06446011d189700000e8322d00/content.htm
Hope this helps u...
Best REgards,
VVEnkat..

Urgent: Problems in Generic Extraction by Function Module

Hi BW Gurus,
I am new to SDN and also new to generic extraction using function module. My requirement is to extract long text(142 char) from CRM to BW as the text is not stored in database table I used function module read_text with in another ZXXX function module copy of (RSAX_BIW_GET_DATA_SIMPLE). In my extract structure I used GUID(char,32), Langu, long text(142 char) and 2 placeholders. Text can be extracted by passing STXH table fields(Tdname, Tdid, Tdobject, Tdspars) to read_text as parameters and i also need to use CRMD_ORDERADM_H field GUID(32 char) to compare 1st 32 chars of tdname(70 char) with Guid to select Guids and loop thru this Guids and for each Guid i need to append lines of text to e_t_data but as i donot know ABAP i unable to write the code for this. Through my friends help i wrote code when i check in RSA3 it is displaying the text but when i replicate into BW and load into data target in monitor the status is red with records initially but afterwards it will be red status again with 0 from 0 records for initial load again.when i check on job logs the errors i have are:
The background job has created a job log file of 2Gb size and it is currently on a infinite loop writing entries into the SAP System Log that it cannot write to the Job log file due to Error 22 for write/read access to a file this is because of the datasource i have created. Please find my Function module and if anyone would please correct FM and send me that will be really great.I appreciate it in advance.
MY Function Module is:
FUNCTION Z_CRMORDERH_STR_TXT.
""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 YCRM_TEXT_STR OPTIONAL
*" EXCEPTIONS
*" NO_MORE_DATA
*" ERROR_PASSED_TO_MESS_HANDLER
***" EXCEPTIONS NO_MORE_DATA
*" ERROR_PASSED_TO_MESS_HANDLER
Tables: CRMD_ORDERADM_H, STXH.
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.
data: i_crmtext type standard table of TLINE .
types: begin of xsreph ,
 GUID type CRMD_ORDERADM_H-guid,
 end of xsreph.
 data: i_guid type standard table of xsreph.
data: I_TEXT type STXH-TDNAME.
data: xempl like YCRM_TEXT_STR occurs 0 with header line.
data: t_tab like dd03l-tabname.
Select ranges
ranges: l_r_guid for CRMD_ORDERADM_H-guid.
 l_r_connid for sflight-connid.
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 'yCRM_TEXT'. " for S_SREPH1
 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.
we will do our selection based on what is in the p table for the
infoobject
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 = 'GUID'.
 MOVE-CORRESPONDING L_S_SELECT TO L_R_GUID.
 APPEND L_R_GUID.
 ENDLOOP.
 case i_dsource.
 when 'YCRM_TEXT'. " for S_SREPH1
 t_tab = 'CRMD_ORDERADM_H'.
 endcase.
 select GUID
 from (t_tab)
 into table i_guid where PROCESS_TYPE = 'ZACI' and ( OBJECT_ID < '0000000042').
 select tdname from stxh into i_text where tdobject = 'TEXT'.
 if sy-subrc ne 0.
 message e009(r3).
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
 'No master data found'. "message variable 2
 raise error_passed_to_mess_handler.
 endif.
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
 select (s_s_if-t_fields) from CRMD_ORDERADM_H
 where GUID in L_R_GUID .
 ENDIF.
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.
as we are doing this only once can use the select statement.
***data: crmtext like tline occurs 0 with header line.
**data: i_crmtext type standard table of TLINE.
**data: i_guid type standard table of xsreph.
data: l_guid type THEAD-TDNAME.
data: st_guid type xsreph.
data: st_crmtext type TLINE.
data: lan type THEAD-TDSPRAS.
lan = 'E'.
loop at i_guid into st_guid.
l_guid = st_guid-guid.
CALL FUNCTION 'READ_TEXT'
 EXPORTING
 CLIENT = SY-MANDT
 ID = 'A002'
 LANGUAGE = lan
 NAME = l_guid
 OBJECT = 'CRM_ORDERH'
 ARCHIVE_HANDLE = 0
 LOCAL_CAT = ' '
IMPORTING
 HEADER =
 TABLES
 LINES = i_crmtext.
EXCEPTIONS
 ID = 1
 LANGUAGE = 2
 NAME = 3
 NOT_FOUND = 4
 OBJECT = 5
 REFERENCE_CHECK = 6
 WRONG_ACCESS_TO_ARCHIVE = 7
 OTHERS = 8
e_t_data-guid = l_guid.
loop at i_crmtext into st_crmtext.
move lan to e_t_data-langu.
move st_crmtext-tdline to e_t_data-description.
append e_t_data.
endif.
endloop.
clear: st_guid,l_guid.
refresh: i_crmtext.
endloop.
S_COUNTER_DATAPAKID = S_COUNTER_DATAPAKID + 1.
endif.
ENDFUNCTION.
please Gurus as I donot know ABAP i appreciate if anyone would write a FM based on requirement and send me that will be really great this is my request. I gurantee of award points for good answers.
Regards
Kishore

Hi,
The statement RAISE NO_MORE_DATA should be active (uncommented) in your code. Otherwise, the infinte loop occurs.
See also, the Siggi's blog:
/people/siegfried.szameitat/blog/2005/09/29/generic-extraction-via-function-module
BTW, was it your thread here:
Re: Urgent: problems in extracting Long Text
Best regards,
Eugene

Generic Extraction (or) How to use table in R/3 system as datasource in BW?

Hi all,
Hope all are having a great day
Can any1 tell me the steps, for Generic Extraction.
It will be very helpful, if the steps are as much as simpler as posible.
I know to create a simple cube in BW.
I have this much knowledge, depending on this can any1 tell me the steps for Generic Extraction from R/3.
examples wud be vry useful
Regards,
Sourav

hi,
Maintaining Generic DataSources
Use
Independently of application, you can create and maintain generic DataSources for transaction data, master data attributes or texts from any kinds of transparent tables, database views, InfoSets of the SAP query or using a function module. As a result, you can make use of the generic extraction of data.
Procedure
Creating a Generic DataSource(RSO2)
       1.      Select the DataSource type and give it a technical name.
       2.      Choose Create.
The creating a generic DataSource screen appears.
       3.      Choose an application component to which the DataSource is to be assigned.
       4.      Enter the descriptive texts. You can choose any text.
       5.      Choose from which datasets the generic DataSource is to be filled.
                            a.      Choose Extraction from View, if you want to extract data from a transparent table or a database view. Enter the name of the table or the database view.
After generation, you get a DataSource whose extract structure is congruent with the database view or the transparent table view.
For more information about creating and maintaining database views and tables, see the ABAP Dictionary Documentation.
                            b.      Choose Extraction from Query, if you want to use a SAP query InfoSet as the data source. Select the required InfoSet from the InfoSet catalog.
Notes on Extraction Using SAP Query
After generation, you now have a DataSource whose extract structure matches the InfoSet.
For more information about maintaining the InfoSet, see the System Administration documentation.
                            c.      Choose Extraction using FM, if you want to extract data using a function module. Enter the function module and extract structure.
The data must be transferred by the function module in an interface table E_T_DATA.
Interface Description and Extraction Process Flow
For information about the function library, see the ABAP Workbench: Tools documentation.
                            d.      With texts, you also have the option of extraction from domain fixed values.
       6.      Maintain the settings for delta transfer where appropriate.
       7.      Choose Save.
When extracting, look at SAP Query: Assigning to a User Group.
Note when extracting from a transparent table or view:
If the extract structure contains a key figure field, that references to a unit of measure or currency unit field, this unit field must appear in the same extract structure as the key figure field.
A screen appears in which you can edit the fields of the extract structure.
       8.      Editing the DataSource:
        Selection
When scheduling a data request in the BW Scheduler, you can enter the selection criteria for the data transfer. For example, you may want to determine that data requests are only to apply to data from the previous month.
If you set the Selection indicator for a field within the extract structure, the data for this field is transferred in correspondence with the selection criteria in the scheduler.
        Hide field
You should set this indicator to exclude an extract structure field from the data transfer. As a result of your action, the field is no longer made available in BW when setting the transfer rules and generating the transfer structure.
        Inversion
Reverse postings are possible for customer-defined key figures. For this reason, inversion is only possible for certain transaction data DataSources. These include DataSources that have a field that is indicated as an inversion field, for example, the field update mode in the DataSource 0FI_AP_3. If this field has a value, then the data records are interpreted as reverse records in BW.
Set the Inversion indicator if you want to carry out a reverse posting for a customer-defined field (key figure). The value of the key figure is then transferred in inverted form (multiplied by 1) into BW.
        Field only known in exit
You can enhance data by extending the extract structure for a DataSource using fields in append structures.
The indicator Field only known in Exit is set for fields of an append structure. In other words, by default these fields are not passed onto the extractor from the field list and selection table.
Deselect the indicator Field Only Known in Exit to enable the Service API to pass on the append structure field to the extractor together with the fields of the delivered extract structures in the field list as well as in the selection table.
9. Choose DataSource ® Generate.
The DataSource is now saved in the source system.
Maintaining Generic DataSources
        Change the DataSource
To change a generic DataSource, in the initial screen of DataSource maintenance, enter the name of the DataSource and choose Change.
You can change the assignment of a DataSource to an application component as well as the texts of a DataSource. Double-clicking on the name of the table, view, InfoSet or extract structure takes you to the appropriate maintenance screen. Here you can make changes required to add new fields. You can fully swap transparent tables and database views, but not InfoSets. If you return to the DataSource maintenance and choose Create, the screen for editing a DataSource appears. To save the DataSource in the SAP source system, choose DataSource ® Generate.
If you want to test extraction in the source system independently of a BW system, choose DataSource ® Test Extraction.
        Delta DataSource
In the Change Generic DataSource screen, you can delete any DataSources that are no longer relevant. If you are extracting data from an InfoSet, delete the associated query. If you want to delete a DataSource, this must not be connected to a BW system.
For more information about extracting using SAP Query, see Extraction using the SAP Query.
hope this helps.
assign point if so
partha

When we go for Views and Function Modules for Generic Extraction

Hi Experts,
Can you please explain when we go for extracting the data using Views and when we got using Function Modules using Generic Extraction from R/3 system to BW with examples. And also can you explain when we go for delta for the above both scenarios.
Thanks for you help in advance
Rohith

Hi,
Scenario for Extarction using FM
Imagine the scenario where you need to extract data from
tables having no common field between them and thereby preventing you from creating a view on top of those tables..
Or simply consider tables that are highly unrelatd in terms of fields, but you have a requiremnt to extract data from them.
Also Refer.
create generic extractor based on 2 tables
Generic Extraction via Function Module
/people/siegfried.szameitat/blog/2005/09/29/generic-extraction-via-function-module
Steps.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a0f46157-e1c4-2910-27aa-e3f4a9c8df33
http://help.sap.com/saphelp_nw04/helpdata/en/86/1c8c3e94243446e10000000a114084/frameset.htm
Scenario for Extraction using View
If there are more number of tables and data in those tables can be represented using joins then we can use this type of extraction
For more info Refer these links
http://help.sap.com/saphelp_nw2004s/helpdata/en/cf/21ecf9446011d189700000e8322d00/frameset.htm
Difference between "Help View" and "Search Help"
http://help.sap.com/saphelp_nw04/helpdata/en/cf/21ed06446011d189700000e8322d00/frameset.htm
for more detailed info look on:
http://www.sap-img.com/abap/what-is-the-different-types-and-usage-of-views.htm
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/abap+dictionary&
For GEneric Delta refer these links
[generic with delta;
[https://forums.sdn.sap.com/click.jspa?searchID=11388803&messageID=5164737]

Deltas in generic extraction

how can we set delta updates in generic extraction?can any one help in this

Hi Praveen,
Please do check the link for step by step for generic extraction
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/84bf4d68-0601-0010-13b5-b062adbb3e33
check the following
http://help.sap.com/bp_biv235/BI_EN/html/bw.htm
business content
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/biw/g-i/how%20to%20co-pa%20extraction%203.0x
https://websmp203.sap-ag.de/co
http://help.sap.com/saphelp_nw04/helpdata/en/37/5fb13cd0500255e10000000a114084/frameset.htm
(navigate with expand left nodes)
Check these links:
/people/sap.user72/blog/2004/12/16/logistic-cockpit-delta-mechanism--episode-one-v3-update-the-145serializer146
/people/sap.user72/blog/2004/12/23/logistic-cockpit-delta-mechanism--episode-two-v3-update-when-some-problems-can-occur
/people/sap.user72/blog/2005/01/19/logistic-cockpit-delta-mechanism--episode-three-the-new-update-methods
/people/sap.user72/blog/2005/02/14/logistic-cockpit--when-you-need-more--first-option-enhance-it
/people/sap.user72/blog/2005/04/19/logistic-cockpit-a-new-deal-overshadowed-by-the-old-fashioned-lis
For Generic:
>Go to Tcode : RSO2,
>There give the name of data source which you want to create like transaction data source or master data attribue or Text data source.
>enter
>again in the next screen you need to give application like SD or MM etc
>in the same screen need to select table/view or infosetquery or function module. these are different ways of creating data sources.
>Give the name for the same like if u r creating data source on table give the name of table.
>click on Generic delta which will there in application tool bar and fill the required columns in that screen like type of delta and all
>continue and save
>it will give all the fieds
>enable the check boxes based on your requirement like selection or hide or field only..
>save
Hope This Helps.
Regards,
Ravikanth

LIS and Generic Extraction

Hi All,
Could someone please send me some information regarding LIS extraction and Generic extraction.
Thanks in advance,
Sekhar

Hi Sekhar,
Please do check the link for step by step for generic xtraction
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/84bf4d68-0601-0010-13b5-b062adbb3e33
check the following
http://help.sap.com/bp_biv235/BI_EN/html/bw.htm
business content
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/biw/g-i/how%20to%20co-pa%20extraction%203.0x
https://websmp203.sap-ag.de/co
http://help.sap.com/saphelp_nw04/helpdata/en/37/5fb13cd0500255e10000000a114084/frameset.htm
(navigate with expand left nodes)
also co-pa
http://help.sap.com/saphelp_nw04/helpdata/en/53/c1143c26b8bc00e10000000a114084/frameset.htm
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/fb07ab90-0201-0010-c489-d527d39cc0c6
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/1910ab90-0201-0010-eea3-c4ac84080806
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/ff61152b-0301-0010-849f-839fec3771f3
LO Extraction
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f83be790-0201-0010-4fb0-98bd7c01e328
Check these links:
/people/sap.user72/blog/2004/12/16/logistic-cockpit-delta-mechanism--episode-one-v3-update-the-145serializer146
/people/sap.user72/blog/2004/12/23/logistic-cockpit-delta-mechanism--episode-two-v3-update-when-some-problems-can-occur
/people/sap.user72/blog/2005/01/19/logistic-cockpit-delta-mechanism--episode-three-the-new-update-methods
/people/sap.user72/blog/2005/02/14/logistic-cockpit--when-you-need-more--first-option-enhance-it
/people/sap.user72/blog/2005/04/19/logistic-cockpit-a-new-deal-overshadowed-by-the-old-fashioned-lis
Re: LO-Cockpit V1 and V2 update
Also Refer this link:
http://www.sap-img.com/business/lo-cockpit-step-by-step.htm
FI-CO 'Data Extraction -Line Item Level-FI-CO
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/a7f2f294-0501-0010-11bb-80e0d67c3e4a
FI-GL
http://help.sap.com/saphelp_nw04/helpdata/en/c9/fe943b2bcbd11ee10000000a114084/frameset.htm
http://help.sap.com/saphelp_470/helpdata/en/e1/8e51341a06084de10000009b38f83b/frameset.htm
http://www.sapgenie.com/sapfunc/fi.htm
FI-SL
http://help.sap.com/saphelp_nw2004s/helpdata/en/28/5ccfbb45b01140a3b59298c267604f/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/41/65be27836d300ae10000000a114b54/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/ee/cd143c5db89b00e10000000a114084/frameset.htm
How to do basic LO extraction for SAP-R3-BW
1. Go to transaction code RSA3 and see if any data is available related to your DataSource. If data is there in RSA3 then go to transaction code LBWG (Delete Setup data) and delete the data by entering the application name.
2. Go to transaction SBIW --> Settings for Application Specific Datasource --> Logistics --> Managing extract structures --> Initialization --> Filling the Setup table --> Application specific setup of statistical data --> perform setup (relevant application)
3. In OLI*** (for example OLI7BW for Statistical setup for old documents : Orders) give the name of the run and execute. Now all the available records from R/3 will be loaded to setup tables.
4. Go to transaction RSA3 and check the data.
5. Go to transaction LBWE and make sure the update mode for the corresponding DataSource is serialized V3 update.
6. Go to BW system and create infopackage and under the update tab select the initialize delta process. And schedule the package. Now all the data available in the setup tables are now loaded into the data target.
7.Now for the delta records go to LBWE in R/3 and change the update mode for the corresponding DataSource to Direct/Queue delta. By doing this record will bypass SM13 and directly go to RSA7. Go to transaction code RSA7 there you can see green light # Once the new records are added immediately you can see the record in RSA7.
8.Go to BW system and create a new infopackage for delta loads. Double click on new infopackage. Under update tab you can see the delta update radio button.
9.Now you can go to your data target and see the delta record.
find your scenario and find what data sources do you need on R3 side and ensure they are active as well:
http://help.sap.com/saphelp_nw04/helpdata/en/37/5fb13cd0500255e10000000a114084/frameset.htm
find your scenario -> data sources -> go to R3 -> sbiw and activate required data source
replicate data sources in BW:
RSA1 -> source systems -> right click on your source system -> replicate
then activate your BC:
service.sap.com/bi -> BI Business Content -> General Information -> SAP BW Business Content - Activation
and execute infopackage (it should be delivered with BC)
Useful links:
http://help.sap.com/saphelp_nw04/helpdata/en/e3/e60138fede083de10000009b38f8cf/frameset.htm
service.sap.com/bi -> BI InfoIndex
sdn.sap.com -> Business Information Warehouse -> How-To guides (under Quick Links)
Hope This Helps.
****Assign Points If Helpful****
Regards,
Ravikanth

Bussiness Scenario for GENERIC EXTRACTION

Hi friends,
 can any one explain me... in what situation we go for Generic Extractions..
The normal reason is When the Bussiness Content Datasource is not matching with our requirement.. we go for Generic extraction..
 I told like this only... but they are not satisfied with my answer.. and they asked .. tell me the bussiness scenario( in what situation u done generic extraction)
so, friends... could any one plz explain me any scenario... which you done for generic extraction...
 i will appriciate by giving points to the appropriate answers..
Thanks
babu

Hi,
These 2 below links may be helpful,
GENERIC DATA EXTRACTION USING FUNCTION MODULE
Difference between Generic Extraction and Enhancement of existing Extractor
1)Go to RSA6 and find the data source you need to enhance.--> Display
2)Double click on the Extract structure.
3)Now click on the append structure button to add the required field on to the existing structure.
4) add your required fields with ZZ appended to your field.
5) Save & Activate the append structure. Then go back and make sure you activate the extract structure also.
6) Now again go back to RSA6 and select your Data Source. But this time go to change Data Source to remove the hide option to the enhanced fields. By default theyll be in hide mode. If you dont remove the hide field then this field will not be seen in BW side.
7) Now go to SE38 to write the logic to populate the data into the enhanced field. Program name to write the logic is ZXRSAU01.
8) Check + Save + Activate.
9) Check in RSA3 if data is populated as per your requirement.
10) Replicate your Data Source.
11) Now go to Data Source/ Trans. Structure screen. Now you can see the enhanced field on the right hand side.Enhancements:
Enhancements:BW Side:
Go to CMOD.
1. To Save give Description  createcreate new projectgive the project name
2. Select the radio button Enhancement Assignment and give the Enhancement name you want and press Enter.
3. If the Enhancement is already assigned to some other project it will display the same message saying it is already assigned it some other project. Click on
4. If the Enhancement is not assigned to any project save.
5. Give RSR00001 (For Variable Exits)
6. Activate the Project.
7. and click on the components button.Now go to Display
8. Now Double click on EXIT_SAPLRRS0_001. In that you can see an include ZXRSRU01.
9. Double click on that include, it will say program name ZX are reserved for includes of exit Functions groups.
10. Just Press Enter.
11. Itll Pop-Up a window Create Object.saying Include ZX. Does not exits
12. That is where you have to write the code for the variable exits. BW: Virtual
13. RSR00002 Chars and Key Figures. BW: Moving Characteristics.
14. RSR00003
Thanks,
Aby Jacob

Scenarios for Generic extraction

Hello experts ,
Please give me some scenarios where we will go for the extraction using
function module,
infoset query,
View.
Thanks in advance,
pragya.

Hi Pragya,
Generic extractors are of 3 types:
1. Based on table/view
2. Based on Infoset Query
3. Based on Function module
In some cases Business Content will not give your required data sources , In such scenarios you need to develop your own data sources ( Views / Function modules ) , Then you can bring that data source to BW and use that .
if you can't find the suitable business content data source then you have to create
your own data source ( Generic )
or enhance the given data source.
Need for customized generic extractor
Business Content may not have a suitable
Data Source for your application.
Business Content may require additional enhancements that need data that is not supplied by SAP BW.
The application may not have its own generic data extraction method.
We have used our own custom programs to populate tables in SAP system.
Please see link below
http://help.sap.com/saphelp_nw04s/helpdata/en/3f/548c9ec754ee4d90188a4f108e0121/frameset.htm
Good weblogs
/people/siegfried.szameitat/blog/2005/09/29/generic-extraction-via-function-module
/people/sap.user72/blog/2005/04/19/logistic-cockpit-a-new-deal-overshadowed-by-the-old-fashioned-lis
/people/sap.user72/blog/2004/12/16/logistic-cockpit-delta-mechanism--episode-one-v3-update-the-145serializer146
/people/sap.user72/blog/2004/12/23/logistic-cockpit-delta-mechanism--episode-two-v3-update-when-some-problems-can-occur
/people/sap.user72/blog/2005/01/19/logistic-cockpit-delta-mechanism--episode-three-the-new-update-methods
Regards, ABY

3201: The publisher display name FooBar, specified in the package doesn't match the publisher name, FooBar

I've updated a WP 8.0 application to WP 8.1 Silverlight. When I try to deploy a demo application I get the following error;
3201: The publisher display name, FooBar, specified in the package doesn’t match the publisher name,
FooBar, that’s associated with the developer account.
I've seen several cases with people encounter this issue and then solved by modifying WPAppManifest or the Packages file. My problem is that the
display name and publisher name is exactly the same. Both in the application xml files and in the error message displayed by windows phone store.
Any suggestions?

There is no requirement that source code files are in the correct directory structure. If you want javac to be able to automatically compile dependent files, then the source code must be in an appropriate structure and find-able from the classpath.
Also, when you use the -d option, javac will create an appropriate directory relative to the directory specified in the -d option. That's how it is supposed to work.
So it is working as designed and specified.

Errors occurred during the extraction(Generic Extraction)

Hi All,
I am facing problems in solving BW Production issues .
The following are the Problem details.
Actually there are two Datasources connected to BW System One is from R/3 and other is from CRM.
The problem is with Delta Request which has been failed in ODS while uploading Data from R/3 in Background Scheduling but other DataSource is loading perfectly into BW System.
Its a generic extraction created based on View.
When i checked BW Side the error is displaying as follows:                                                                                Error occurred in the Data Selection.
     Error occurred in the Source System.
        No Data has been extracted from R/3 into BW.
But when i checked R/3 (Source system)
Firslty i executed RSA7 for checking Delta Records. The records are 0 for the Datasource.
I executed RSA3 with Full UpdateMode, the number of records extracted were displayed
when i checked with Delta Update Mode its giving the following error.
Errors occurred during the extraction
Message no. RJ 012
Diagnosis
There was an error during the extraction phase of the extractor. An exception 'error_passed_to_mess_handler' has been triggered.
Procedure
Check the function module and the call from the extractor check program
Messages from source system
see also Processing Steps Request
These messages are sent by IDoc from the source system. Both the extractor itself as well as the service API can send messages. When errors occur, several messages are usually sent together.
From the source system, there are several types of messages that can be differentiated by the so-called Info-IDoc-Status. The IDoc with status 2 plays a particular role here; it describes the number of records that have been extracted in a source system and sent to BW. The number of the records received in BW is checked against this information.
Regards,
Chakri
Message was edited by: Chakri
Message was edited by: Chakri

Hi,
If Idoc are already sent to BW then goto Monitor in BW and in Details tab note the Idoc no in OLTP, and goto R?3 and BD20 tcode and give the Idoc no and execute it.And see the records are came or not in BW.
Thanks
Reddy

Displaying Application is specified in Generic Extraction

Similar Messages

Maybe you are looking for