Extract Structure and its program

Hi Experts,
Is it possible to know what program/function module is used by datasource extract structure to get the data?
In my case i need to know this information regarding the extract structure HRMS_BIW_IO_OCCUPANCY (0EMPLOYEE_ATTR).
Thanks in advance.
Fabio

Since a lot of time ago (the last time I met him) he lent 10 euros to me, I was just remembering that I'm still in debt to him !
(but I'm thinking now that our answer can be evaluated around 10 euros, so...)

Similar Messages

Extract structure and table

Hi Experts,
How to know the fields of a extract structure are populated data from which tables?
Thanks,
Bill

Hi,
Datasource / tables in the source system
Go to RSA2 (DS Repository) in your source system and display your source system.
If Extraction Method is 'V' - you are lucky and you see table name where data is taken from.
If it is F* - function module is used, and you have to go thru its code to see all the tables it uses and logic how data is
processed.
Ext. Meth   Short text
V                 Transparent Table or DB View
D                  Fixed Domain Value
F1                Function Module (Complete Interface)
F2                Function Module (Simple Interface)
Q                 Extraction Using ABAP Query
A                 DataSource Append
or
Table ROOSOURCE in ERP.
Relevant fields EXMETHOD, EXTRACTOR.
IF EXMETHOD = V, EXTRACTOR is view or tablename
IF EXMETHOD = D, EXTRACTOR is name of domain
IF EXMETHOD = F1, F2 EXTRACTOR is name of FM
IF EXMETHOD = Q EXTRACTOR is name of Info set
OR
Since you have the extract structure and the extractor, you must have some transaction like the Extractor Checker RSA3. If so
then execute ST05, switch on the trace and execute the extractor checker. Once the extractor checker presents the results
switch off trace. The clcik on Display trace and you will see all the tables that were hit by the extractor checker to
retrieve data and present it to you.
Thanks,
JituK

How to find all the Master data extract structures and Extractors

I intend to create Master data dimensions closely similar to SAP BI in a 3rd party system. I would like to use SAP's standard extractors for populating the master data structures in SAP BI and then use a proprietary technology to create similar structures in a 3rd party database.
Question: How to get a complete list of all Master data extract structures and corresponding extractors?
Example: In ECC if I do SE80 and give 'Package' and 'MDX' and then press the 'display' spectacles, I get a list of structures and views under "dictionary objects" covering Material, Customer, Vendor, Plant Texts and attributes.
How do I get the remainder of the Master data extract structures viz. Purchase Info Records, Address, Org Unit etc?
Regards
Sasanka

Hi,
try the table ROOSOURCE and search the data source with string in astrick attr for master data and for text with text
This will give you the list of all the master data source in the system and it contains a column which tells about the extract structure and function module used by each.
Thanks
Ajeet

Difference between Extraction Structure and Datasource

Hi Gurus,
I have a very basic question here.Can anybody explain to me in detail the difference between an extraction structure and Datasource.
Thanks in advance

Hi:
I am pasting a summarized def. from sap notes.
http://help.sap.com/saphelp_bw30b/helpdata/en/ad/6b023b6069d22ee10000000a11402f/frameset.htm
Data Source:
Data that logically belongs together is stored in the source system in the form of DataSources. A DataSource contains a number of fields in a flat structure used to transfer data into BW (Extract Structure).
Extract Structure:
In the extract structure, data from a DataSource is staged in the source system. The extract structure contains the amount of fields that are offered by an extractor in the source system for the data loading process.
You can edit and enhance DataSource extract structures in the source system. To do this, in the BW Administrator Workbench choose Goto à Modeling à Source Systems à Your Source System à Context Menu (right mouse click) à Customizing Extractors à Subsequent Processing of DataSources.
While, you are on the topic, you have one more structure.
Transfer Structure:
The transfer structure is the structure in which the data is transported from the source system into the SAP Business Information Warehouse.
It provides a selection of the extract structure fields for the source system.
It may be a good idea to look into a sample Business Content extractor to get a better understanding of how they are related.
Chamarthy

How to Transport Extract Structure and datasource

Hi all!
I had recently made enhancements to 0CO_PC_PCP_01 datasource.When I transported the datasource and the Extract structure, I noticed that only the append structure has been transported. The datasource has not been transported.
Could some one tell me how to collect the datasource and the Appended extract structure and transport them.
Thanks,
S.P

Hi Jaya,
I had already tried this already. When I selected the dtasource and selected the transport button. I got the message, action successfully executed. When I checked in SE09, I see no transport. Unless it asks me for a transport request, I will not see it in SE09, right.
~S.P

Enhance extract structure and deltas

Hi All,
We are modifying our first extract structure (well looks like it). We need to determine a key figure based on lookups and values of other fields.
Should we enhance the extract structure to pass these fields and then determine the key figure in the update rules to the cube or should we determine the key figure on the SAP side and pass to BW? If we determine the key figure on the SAP side does it update the delta queue with this value?
So does the delta queue get updated with this key figure? Meaning, does the code in the extract structure get executed during the update to the delta queue or do we have to pass the "lookup" values (basically characteristics) to BW and then determine the value of the key figure?
Thanks so much!

Hi,
This can be done at either of the places. This is all dependant on where can we afford to.. in terms of system uitlization. That is, if the look up table is too big in SAP and we have a small volume in BW then its better in BW and the viceversa of it.
Either in BW or in SAP, the logic is going to take some time to execute and hence the decision relies mostly on this.
Yes the delta queue would be filled with this logic, if we add the key figure in SAP.
Hope I am clear.
Naveen.A

Issue in Dynamic Structure and Component Program

Hi,
I have a requirement of creating an inbound idoc program and populating dynamic structures. The program for the dynamic structure creation is as follows: ( I have been referencing Heilmans Blog ): The part for the inbound idoc creation works fine. The data will come in a flat file with Table name and 15 characterstcis. The table name is known at runtime. I need to create the dynamic table, find out the components and then populate the custom table with the dynamically created structures.
Custom table: 4 components
Internal table from file: 15 components with value.
There could be more than one table in the flat file and not all components or char in the flat file is mapped to the table. I would need some expertise in coding the OO part of the program.
Any inputs will be apprciated:
<removed 6845 lines of code (forum software cut off at this point, there was more!) - did you actually expect anyone to read that? Also, please use code tags (the "<>" icon on the toolbar)>
Edited by: Mike Pokraka on Aug 3, 2008 6:15 PM

Hi,
The program works fine fo creating inbound idocs. It is the dynamic structure population that seems to be the problem mentioned earlier: Here is the code:
*& Report /FACTGLB/GTDMI_VARTAB_IDOCS02 *
PROGRAM DESCRIPTION: Variant Table and Content Upload Interface.
 DEVELOPER: Aveek Ghose
 CREATION DATE: 2008-04-18
 RDD NUMBER: DCDD027
TRANSPORT NUMBER(S): RD2K902769
*-- REVISION HISTORY -
 DEVELOPER:
 DATE APPLIED: YYYY-MM-DD
 SCR NUMBER: <Scope Change Request ID>
 RDD NUMBER: <Toolset Object ID>
TRANSPORT NUMBER(S):
 DESCRIPTION:
REPORT ZGTDMI_VARTAB_IDOCS_DYNAMIC
 NO STANDARD PAGE HEADING
 LINE-SIZE 150
 LINE-COUNT 55
 MESSAGE-ID zfactglb.
**Include for Global Data Declaration
*INCLUDE /FACTGLB/GTDMI_VARTAB_TOP02.
**Include for Selection Screen
*INCLUDE /FACTGLB/GTDMI_VARTAB_SEL02.
**Include for Sub Routines
*INCLUDE /FACTGLB/GTDMI_VARTAB_FORMS02.
*& Include /FACTGLB/GTDMI_VARTAB_TOP02 *
*& Include /FACTGLB/GTDMI_VARTAB_TOP02 *
*& Include /FACTGLB/GTDMI_VARTAB_TOP
*& Include /FACTGLB/GTDMI_VARTAB_TOP
PROGRAM DESCRIPTION: Variant Table and Content Upload Interface.
 DEVELOPER: Aveek Ghose
 CREATION DATE: 2008-04-18
 RDD NUMBER: DCDD027
TRANSPORT NUMBER(S): RD2K902769
*-- REVISION HISTORY -
 DEVELOPER:
 DATE APPLIED: YYYY-MM-DD
 SCR NUMBER: <Scope Change Request ID>
 RDD NUMBER: <Toolset Object ID>
TRANSPORT NUMBER(S):
 DESCRIPTION:
TYPE POOLS
*Type declaration for ALV display
TYPE-POOLS : slis.
Include .
type-pools: col, "#EC *
 icon, "#EC *
 sym, "#EC *
 abap. "#EC *
Target structure definitions
tables:
E1CUVTM, "#EC *
E1DATEM, "#EC *
E1CUV1M, "#EC *
edp21, "#EC *
edi_dc40, "#EC *
edi_dd40, "#EC *
edi_ds40. "#EC *
GLOBAL TYPES
TYPES : BEGIN OF ty_vartab.
 include structure E1CUVTM.
TYPES: END OF ty_vartab.
TYPES : BEGIN OF ty_vartabdate.
 INCLUDE STRUCTURE E1DATEM.
TYPES : END OF ty_vartabdate.
*Structure for data retreived
TYPES : BEGIN OF ty_vardetails.
 INCLUDE STRUCTURE E1CUV1M.
TYPES : END OF ty_vardetails.
*Structure for data retreived from table tabinput.
TYPES : BEGIN OF ty_tabinput,
 lines type string,
 END OF ty_tabinput.
*Structure for data retreived from Table dsn_input.
TYPES : BEGIN OF ty_dsninput, "#EC *
 LINE(101) type c,
 END OF ty_dsninput.
*Structure for data retreived from Table dsn_input.
TYPES : BEGIN OF ty_newinput, "#EC *
 LINE(101) type c,
 flag(1) type c,
 END OF ty_newinput.
*Structure for keeping the values of all the custom tables
TYPES : BEGIN OF ty_custom_tabs,
 matnr TYPE matnr, "Material Number
 werks TYPE werks_d, "Plant
 lgort TYPE lgort_d, "Storage Location
 qunty TYPE P DECIMALS 2, "Standard Order Quantity
 det_loc TYPE CHAR6, "Detail Location
 class TYPE CHAR2, "Class
 rate TYPE P DECIMALS 2, "Rate
 END OF ty_custom_tabs.
*Type declared for the internal table and work area which will store
*fields for error log
TYPES : BEGIN OF ty_error_log,
 matnr TYPE matnr, "Material Number
 mtart TYPE mtart, "Material Type
 sel_data TYPE char10, "No of selectyed data
 END OF ty_error_log.
*Structure for keeping the output data
TYPES : BEGIN OF ty_final,
 VTNAM(018) type C,
 CHAR1(030) type C,
 CHAR2(030) type C,
 CHAR3(030) type C,
 CHAR4(030) type C,
 CHAR5(030) type C,
 CHAR6(030) type C,
 CHAR7(030) type C,
 CHAR8(030) type C,
 CHAR9(030) type C,
 CHAR10(030) type C,
 CHAR11(030) type C,
 CHAR12(030) type C,
 CHAR13(030) type C,
 CHAR14(030) type C,
 CHAR15(030) type C,
 FLAG(001) type C,
 END OF ty_final.
TYPES: begin of TY_CONTENTHD,
 VTNAM(018) type C,
 FLAG(001) type C,
end of TY_CONTENTHD.
TYPES: begin of TY_CONTENT,
 VTNAM(018) type C,
 CHAR1(030) type C,
 CHAR2(030) type C,
 CHAR3(030) type C,
 CHAR4(030) type C,
 CHAR5(030) type C,
 CHAR6(030) type C,
 CHAR7(030) type C,
 CHAR8(030) type C,
 CHAR9(030) type C,
 CHAR10(030) type C,
 CHAR11(030) type C,
 CHAR12(030) type C,
 CHAR13(030) type C,
 CHAR14(030) type C,
 CHAR15(030) type C,
 FLAG(001) type C.
TYPES: end of TY_CONTENT.
TYPES: BEGIN OF TY_E1CUVTM,
 MSGFN TYPE MSGFN,
 VAR_TAB TYPE APITABL,
 STATUS TYPE RCUTBST,
 VTGROUP TYPE RCUTBGR,
 AUTHSTRUC TYPE RCUTBBE,
 AUTHENTRY TYPE RCUFNBI,
 FLDELETE TYPE FLLKENZ,
 DBTABNAME TYPE TABNAME16,
 DBCONACTIVE TYPE DBCON_ACTI,
 PRESDEC TYPE VTDCT,
 END OF TY_E1CUVTM.
TYPES: BEGIN OF TY_E1CUV1M,
 MSGFN TYPE MSGFN,
 VTLINENO TYPE VTLINENO,
 VTCHARACT TYPE ATNAM,
 ATWRT TYPE ATWRT,
 ATFLV TYPE ATFLV,
 ATAWE TYPE MSEHI,
 ATFLB TYPE ATFLB,
 ATAW1 TYPE MSEHI,
 ATCOD TYPE ATCOD,
 ATTLV TYPE ATTLV,
 ATTLB TYPE ATTLB,
 ATPRZ TYPE ATPRZ,
 ATINC TYPE ATINC,
 VTLINENO5 TYPE VTLINENO5,
 END OF TY_E1CUV1M.
TYPES: BEGIN OF TY_E1DATEM,
 MSGFN TYPE MSGFN,
 KEY_DATE TYPE SYDATUM,
 AENNR TYPE AENNR,
 EFFECTIVITY TYPE CC_MTEFF,
 END OF TY_E1DATEM.
TYPES: BEGIN OF ty_vtnam,
 vtint TYPE vtint, " Internal number of variant table
 vtnam TYPE vtnam, " Name of variant table
 error TYPE char1, " Indicates error in data format
 reas TYPE char50, " Reason for failure
 END OF ty_vtnam.
Get data type for characteristic
TYPES: BEGIN OF ty_cabn,
 atinn TYPE atinn, "Internal characteristic
 atnam TYPE atnam, "Characteristic Name
 atfor TYPE atfor, "Data type of characteristic
 atson TYPE atson, "Indicator: Additional Values
 atprt TYPE atprt, "Check table
 atprr TYPE atprr, "Name of Check Report Program
 atprf TYPE atprf, "Function Module for Checking Values
 anzdz TYPE anzdz, "Number of Decimal Places
 check TYPE char1, "Indicates check required or not
 END OF ty_cabn.
Get field names of variant table
TYPES: BEGIN OF ty_cuvtab_fld,
 vtint TYPE vtint, " Internal number of variant table
 atinn TYPE atinn, " Internal characteristic
 vtpos TYPE vtpos, " Item number of characteristic in variant
 exist TYPE char1, " X Indictaes characteristic is part of fil
 END OF ty_cuvtab_fld.
Store all data in internal table
TYPES: BEGIN OF ty_file,
 vtnam TYPE vtnam,
 char1 TYPE atwrt,
 char2 TYPE atwrt,
 char3 TYPE atwrt,
 char4 TYPE atwrt,
 char5 TYPE atwrt,
 char6 TYPE atwrt,
 char7 TYPE atwrt,
 char8 TYPE atwrt,
 char9 TYPE atwrt,
 char10 TYPE atwrt,
 char11 TYPE atwrt,
 char12 TYPE atwrt,
 char13 TYPE atwrt,
 char14 TYPE atwrt,
 char15 TYPE atwrt,
 flag TYPE char1,
 error TYPE char50,
 END OF ty_file.
To check for duplicates
TYPES: BEGIN OF ty_dupl,
 vtnam TYPE vtnam,
 char1 TYPE atwrt,
 char2 TYPE atwrt,
 char3 TYPE atwrt,
 char4 TYPE atwrt,
 char5 TYPE atwrt,
 char6 TYPE atwrt,
 char7 TYPE atwrt,
 char8 TYPE atwrt,
 char9 TYPE atwrt,
 char10 TYPE atwrt,
 char11 TYPE atwrt,
 char12 TYPE atwrt,
 char13 TYPE atwrt,
 char14 TYPE atwrt,
 char15 TYPE atwrt,
 slnid TYPE slnid,
 END OF ty_dupl.
Get previously loaded characteristic values for internal table (CHAR)
TYPES: BEGIN OF ty_cuvtab_valc,
 vtint TYPE vtint, " Internal number of variant table
 slnid TYPE slnid, " Key for value combination in variant tab
 atinn TYPE atinn, " Internal characteristic
 valc TYPE atwrt, " Characteristic Value
 END OF ty_cuvtab_valc.
Get previously loaded characteristic values for internal table (NUM)
TYPES: BEGIN OF ty_cuvtab_valn,
 vtint TYPE vtint, " Internal number of variant table
 slnid TYPE slnid, " Key for value combination in variant tab
 atinn TYPE atinn, " Internal characteristic
 val_from TYPE atflv, " Internal floating point from
 END OF ty_cuvtab_valn.
Store column positions of characteristics
TYPES: BEGIN OF ty_col_pos,
 vtint TYPE vtint, " Internal number of variant table
 vtnam TYPE vtnam, " Variant table name
 atinn TYPE atinn, "Internal characteristic
 atnam TYPE atnam, "Characteristic Name
 field TYPE fieldname, "Field name
 req TYPE char1, " Required or not
 vtpos TYPE vtpos, " Item number of characteristics
 END OF ty_col_pos.
Store valid values for characteristics
TYPES: BEGIN OF ty_cawn,
 atinn TYPE atinn, " Internal characteristic
 atzhl TYPE atzhl, " Int counter
 atwrt TYPE atwrt, " Characteristic Value
 atflv TYPE atflv, " Internal floating point from
 lkenz TYPE lkenz, " Deletion indicator
 END OF ty_cawn.
Store error messages for individual lines
TYPES: BEGIN OF ty_error,
 vtnam TYPE vtnam, " Variant table name
 fname TYPE fieldname, " Fieldname
 atnam TYPE atnam, " Characteristic name
 atwrt TYPE atwrt, " Characteristic value
 row TYPE char5, " Row id
 END OF ty_error.
Begin TPR# 4618
To store unique number for variant
TYPES: BEGIN OF ty_vnt_ma,
 vtnam TYPE vtnam,
 unique_no TYPE ZGTDM_UNQN,
 no_chr TYPE ZGTDM_NO_CHR,
 END OF ty_vnt_ma.
To find out concatenated number for
TYPES: BEGIN OF ty_split,
 f1 TYPE char6,
 END OF ty_split.
TYPES: BEGIN OF ty_charval,
 char TYPE char30,
 END OF ty_charval.
TYPES: BEGIN OF TY_DATA,
 name TYPE string,
 value(15) type c,
 END OF TY_DATA.
DATA: I_DATATAB TYPE STANDARD TABLE OF TY_DATA.
TYPES:
TUMLS_MESSTYPE type /SAPDMC/LS_MESSTYPE,
TUMLS_MESSTYPETXT type EDI_TEXT60,
TUMLS_MESSCODE type EDIPMESCOD.
TYPES:
TUMLS_TABNAME TYPE TABNAME, "#EC *
TUMLS_SEGMENT TYPE TABNAME. "#EC *
TYPES:
TUMLS_PATHFILE TYPE /SAPDMC/LS_FILENAME,
TUMLS_FILENAME TYPE /SAPDMC/LS_FILENAME,
TUMLS_FILETEXT TYPE /SAPDMC/LS_FILETEXT.
TYPES:
BEGIN OF type_errorline,
 msgty type SYMSGTY,
 id type SYMSGID,
 msgno type symsgno,
 par1 type symsgv,
 par2 type symsgv,
 par3 type symsgv,
 par4 type symsgv,
END OF type_errorline.
TYPES:
type_errortab TYPE SORTED TABLE
 OF type_errorline
 WITH NON-UNIQUE KEY id msgno par1 par2 par3 par4.
DATA:
 LV_INDEX TYPE SY-INDEX,
 LV_INDEX2 TYPE SYINDEX,
 LV_TABLE1 TYPE REF TO DATA,
 LV_TABLE2 TYPE REF TO DATA,
 LV_TABLE3 TYPE REF TO DATA,
 LV_TABLE4 TYPE REF TO DATA,
 LV_LINE1 TYPE REF TO DATA,
 LV_LINE2 TYPE REF TO DATA,
 LV_LINE3 TYPE REF TO DATA,
 LV_LINE4 TYPE REF TO DATA,
 LV_OFFSET1 TYPE SYTABIX,
 ST_IS_LAYOUT_ALV TYPE SLIS_LAYOUT_ALV,
 L_IT_FCATLOG_ALV TYPE SLIS_T_FIELDCAT_ALV,
 L_IT_FLDCAT TYPE LVC_T_FCAT.
GLOBAL INTERNAL TABLES
DATA : i_newinput TYPE STANDARD TABLE OF ty_newinput INITIAL SIZE 0."#EC *
DATA : i_contentheader1 TYPE STANDARD TABLE OF ty_contenthd INITIAL SIZE 0."#EC *
DATA : i_contenttab1 TYPE STANDARD TABLE OF ty_content INITIAL SIZE 0."#EC *
DATA : i_contenttab2 TYPE STANDARD TABLE OF ty_content INITIAL SIZE 0."#EC *
DATA : i_contenttab3 TYPE STANDARD TABLE OF ty_content INITIAL SIZE 0."#EC *
DATA : i_contenttab4 TYPE STANDARD TABLE OF ty_content INITIAL SIZE 0."#EC *
DATA : i_E1CUV1M TYPE STANDARD TABLE OF E1CUV1M INITIAL SIZE 0."#EC *
DATA : i_errortab TYPE STANDARD TABLE OF solisti1 INITIAL SIZE 0."#EC *
GLOBAL WORK AREAS
**Internal Table for the structure TY_T001L
DATA : wa_vartab TYPE ty_vartab. "#EC *
DATA : wa_vartabdate TYPE ty_vartabdate. "#EC *
DATA : wa_vardetails TYPE ty_vardetails. "#EC *
DATA : wa_tabinput TYPE ty_tabinput. "#EC *
DATA : wa_dsninput TYPE ty_dsninput. "#EC *
DATA : wa_newinput TYPE ty_newinput. "#EC *
DATA : wa_gnewinput TYPE ty_newinput. "#EC *
DATA : wa_ginput_data TYPE ty_newinput. "#EC *
DATA : wa_final TYPE ty_final. "#EC *
DATA : wa_content TYPE ty_content. "#EC *
DATA : wa_contenthd TYPE ty_contenthd. "#EC *
DATA : wa_contentheader type ty_contenthd. "#EC *
DATA : wa_contenttab TYPE ty_content. "#EC *
DATA : wa_content1 TYPE ty_content. "#EC *
DATA : wa_contenthd1 TYPE ty_contenthd. "#EC *
DATA : wa_contentheader1 type ty_contenthd. "#EC *
DATA : wa_contenttab1 TYPE ty_content. "#EC *
DATA : wa_contenttab2 TYPE ty_content. "#EC *'
DATA : wa_contenttab3 TYPE ty_content. "#EC *
DATA : wa_contenttab4 TYPE ty_content. "#EC *
DATA : wa_E1CUVTM TYPE E1CUVTM. "#EC *
DATA : wa_E1CUV1M TYPE E1CUV1M. "#EC *
DATA : wa_E1DATEM TYPE E1DATEM. "#EC *
DATA : wa_error_tab TYPE solisti1. "#EC *
INTERNAL TABLES AND WORK AREAS FOR BDC
*Internal Table to store the data to display the error message
DATA : i_errormsg TYPE STANDARD TABLE OF solisti1 INITIAL SIZE 0."#EC *
*Internal Table to store the data to display the error message
DATA : i_error TYPE STANDARD TABLE OF solisti1 INITIAL SIZE 0."#EC *
DATA : itab_error TYPE STANDARD TABLE OF solisti1 INITIAL SIZE 0."#EC *
**Work area to store the data to display the error message
DATA : wa_errormsg TYPE solisti1. "#EC *
**Internal table which will store data for the error log
DATA:i_error_log TYPE STANDARD TABLE OF ty_error_log INITIAL SIZE 0."#EC *
GLOBAL VARIABLES
DATA: G_FILE TYPE string. "#EC *
DATA : g_ctr_input_recs(5) type c. "#EC *
DATA: g_ctr_output_recs(5) type p. "#EC *
data : g_msg(100) type c. "#EC *
data: g_struct_file TYPE string. "#EC *
data: g_login type FILEINTERN. "#EC *
data: g_phyin type string. "#EC *
DATA: g_lprnt type RSPOPSHORT. "#EC *
DATA: g_FNAME1 TYPE STRING. "#EC *
DATA : g_repid TYPE repid, "#EC *
 g_exit(1) TYPE C, "#EC *
 gx_variant type disvariant. "#EC *
DATA : g_lines TYPE i . "#EC *
data : g_save(1) type c. "#EC *
DATA : g_splid TYPE rspoid . "#EC *
data: p_login type FILEINTERN. "#EC *
data: p_phyin type string. "#EC *
DATA:
go_table TYPE REF TO cl_salv_table,
go_sdescr TYPE REF TO cl_abap_structdescr,
go_tdescr TYPE REF TO cl_abap_tabledescr,
gdo_data TYPE REF TO data,
gdo_handle TYPE REF TO data,
gs_comp TYPE abap_componentdescr,
gt_components TYPE abap_component_tab.
FIELD-SYMBOLS:
 TYPE table.
GLOBAL CONSTANTS
CONSTANTS c_msgar TYPE rslgarea VALUE 'F8'. "#EC *
CONSTANTS c_msgid TYPE rslgsubid VALUE 'E'. "#EC *
CONSTANTS c_urgnc TYPE char04 VALUE 'HIGH'. "#EC *
CONSTANTS C_X(1) TYPE C VALUE 'X'. "#EC *
CONSTANTS C_Y(1) TYPE C VALUE 'Y'. "#EC *
CONSTANTS C_Z(1) TYPE C VALUE 'Z'. "#EC *
CONSTANTS C_E(1) TYPE C VALUE 'E'. "#EC *
CONSTANTS C_SAP(3) TYPE C VALUE 'SAP'. "#EC *
CONSTANTS C_MOD(3) TYPE C VALUE 'MOD'. "#EC *
CONSTANTS C_MD1(3) TYPE C VALUE 'MD1'. "#EC *
CONSTANTS C_MD2(3) TYPE C VALUE 'MD2'. "#EC *
CONSTANTS C_MD3(3) TYPE C VALUE 'MD3'. "#EC *
constants: c_000001(6) type c value '000001', "#EC *
 c_e1cuv1m(7) type c value 'E1CUV1M', "#EC *
 c_02(2) type c value '02', "#EC *
 c_009(3) type c value '009', "#EC *
 c_0001(4) type c value '0001'. "#EC *
constants: c_e1datem(7) type c value 'E1DATEM'. "#EC *
constants: c_e1cuvtm(7) type c value 'E1CUVTM'. "#EC *
GLOBAL INTERNAL TABLES FOR ALV DISPLAY
*Internal tables for ALV Field cat
DATA :
i_fieldcat_ov TYPE STANDARD TABLE OF slis_fieldcat_alv INITIAL SIZE 0,"#EC *
i_fieldcat_dtl TYPE STANDARD TABLE OF slis_fieldcat_alv INITIAL SIZE 0,"#EC *
i_fieldcat_ov1 TYPE lvc_t_fcat, "#EC *
i_events TYPE slis_t_event. "#EC *
GLOBAL WORK AREAS FOR ALV DISPLAY
*Work area for ALV Field layout
DATA : wa_layout TYPE slis_layout_alv. "#EC *
*Work area for Field Cat. Table
DATA : wa_fieldcat TYPE slis_fieldcat_alv. "#EC *
GLOBAL VARIABLES FOR ALV DISPLAY
DATA : g_event TYPE slis_t_event. "#EC *
DATA : g_top_of_page TYPE slis_t_listheader. "#EC *
DATA : g_ok_code TYPE char4. "#EC *
DATA : g_variant type disvariant. "#EC *
GLOBAL CONSTANTS FOR ALV DISPLAY
BAL handling
data: iv_log_handle type BALLOGHNDL. "#EC *
data: is_log_header type bal_s_log. "#EC *
data: iv_object type bal_s_log-object value 'CAPI'. "#EC *
data: iv_subobject type bal_s_log-subobject value 'CAPI_LOG'."#EC *
data: iv_tcode type bal_s_log-altcode value 'SE38'. "#EC *
*MOD-005
RANGES:
 R_MESTYP FOR EDIDC-MESTYP, "#EC *
 R_CREDAT FOR EDIDC-CREDAT, "#EC *
 R_CRETIM FOR EDIDC-CRETIM, "#EC *
 R_SNDPRT FOR EDIDC-SNDPRT, "#EC *
 R_SNDPRN FOR EDIDC-SNDPRN. "#EC *
DATA:
 L_MESSTYPE TYPE TUMLS_MESSTYPE. "#EC *
*MOD-005
data: p_sndprn TYPE EDI_SNDPRN, "#EC *
 p_sndprt TYPE EDI_SNDPRT, "#EC *
 p_sndpor TYPE EDI_SNDPOR. "#EC *
data: p_rcvprn TYPE EDI_RCVPRN, "#EC *
 p_rcvprt TYPE EDI_RCVPRT, "#EC *
 p_rcvpor TYPE EDI_RCVPOR. "#EC *
data:
init_E1CUVTM type E1CUVTM, "#EC *
prev_E1CUVTM type E1CUVTM, "#EC *
init_E1DATEM type E1DATEM, "#EC *
prev_E1DATEM type E1DATEM, "#EC *
init_E1CUV1M type E1CUV1M, "#EC *
prev_E1CUV1M type E1CUV1M. "#EC *
Source structure definitions
data:
begin of LSMW_TAB_CONTENT, "#EC *
 VTNAM(018) type C,
 CHAR1(030) type C,
 CHAR2(030) type C,
 CHAR3(030) type C,
 CHAR4(030) type C,
 CHAR5(030) type C,
 CHAR6(030) type C,
 CHAR7(030) type C,
 CHAR8(030) type C,
 CHAR9(030) type C,
 CHAR10(030) type C,
 CHAR11(030) type C,
 CHAR12(030) type C,
 CHAR13(030) type C,
 CHAR14(030) type C,
 CHAR15(030) type C,
 FLAG(001) type C,
end of LSMW_TAB_CONTENT.
Counters
data:
g_cnt_VAR_TAB type i, "#EC *
g_cnt_TAB_CONTENT type i. "#EC *
Counter ct_xxxxxxxxxx: number of transferred records
data:
ct_edi_dc40 type i, "#EC *
cs_edi_dc40 type i, "#EC *
ct_E1CUVTM type i, "#EC *
cs_E1CUVTM type i, "#EC *
ct_E1DATEM type i, "#EC *
cs_E1DATEM type i, "#EC *
ct_E1CUV1M type i, "#EC *
cs_E1CUV1M type i. "#EC *
Global data definitions and data declarations
DATA: wa_cabn TYPE ty_cabn,
 wa_cawn TYPE ty_cawn,
 wa_file TYPE ty_file,
 wa_vtnam TYPE ty_vtnam,
 wa_cuvtab_fld TYPE ty_cuvtab_fld,
 wa_cuvtab_valn TYPE ty_cuvtab_valn,
 wa_cuvtab_valc TYPE ty_cuvtab_valc,
 wa_col_pos TYPE ty_col_pos,
 wa_error TYPE ty_error,
 wa_dupl TYPE ty_dupl,
 wa_dupl_file TYPE ty_dupl.
DATA: wa_vnt_ma TYPE ty_vnt_ma,
 wa_split TYPE ty_split.
DATA: wa_charval TYPE ty_charval. "#EC *
Internal table
DATA: i_cabn TYPE STANDARD TABLE OF ty_cabn, "#EC *
 i_cabn_temp TYPE STANDARD TABLE OF ty_cabn, "#EC *
 i_cabn_atinn TYPE STANDARD TABLE OF ty_cabn, "#EC *
 i_file TYPE STANDARD TABLE OF ty_file, "#EC *
 i_file_tmp TYPE STANDARD TABLE OF ty_file, "#EC *
 i_vtnam TYPE STANDARD TABLE OF ty_vtnam, "#EC *
 i_cuvtab TYPE STANDARD TABLE OF ty_vtnam, "#EC *
 i_cuvtab_fld TYPE STANDARD TABLE OF ty_cuvtab_fld, "#EC *
 i_cuvtab_valn TYPE STANDARD TABLE OF ty_cuvtab_valn, "#EC *
 i_cuvtab_valc TYPE STANDARD TABLE OF ty_cuvtab_valc, "#EC *
 i_col_pos TYPE STANDARD TABLE OF ty_col_pos, "#EC *
 i_cawn TYPE STANDARD TABLE OF ty_cawn, "#EC *
 i_cawn_n TYPE STANDARD TABLE OF ty_cawn, "#EC *
 i_cawn_c TYPE STANDARD TABLE OF ty_cawn, "#EC *
 i_cawn_i TYPE STANDARD TABLE OF ty_cawn, "#EC *
 i_cuv_error TYPE STANDARD TABLE OF ty_vtnam, "#EC *
 i_dupl TYPE STANDARD TABLE OF ty_dupl. "#EC *
DATA: i_vnt_ma TYPE STANDARD TABLE OF ty_vnt_ma, "#EC *
 i_split TYPE STANDARD TABLE OF ty_split. "#EC *
DATA: i_dupl_file TYPE STANDARD TABLE OF ty_dupl. "#EC *
DATA: i_charval TYPE STANDARD TABLE OF ty_charval. "#EC *
Constants
CONSTANTS: c_char TYPE atfor VALUE 'CHAR', "#EC *
 c_date TYPE atfor VALUE 'DATE', "#EC *
 c_time TYPE atfor VALUE 'TIME', "#EC *
 c_varcond TYPE atnam VALUE 'Z_VARCOND'. "#EC *
Field Symbols
FIELD-SYMBOLS: TYPE ANY.
Variables
DATA: g_raw(500) TYPE c, "#EC *
 g_invalid TYPE char1, "#EC *
 g_error TYPE char1, "#EC *
 g_message TYPE char50, "#EC *
 g_slnid_c TYPE slnid, "#EC *
 g_slnid_n TYPE slnid, "#EC *
 g_row TYPE char5. "#EC *
DATA: g_varcond TYPE varcond, "Variant condition "#EC NEEDED
 g_split_var TYPE i. "#EC *
Types: begin of ty_charname,
 name type atnam,
 end of ty_charname.
data: wa_charname type ty_charname, "#EC *
 i_charname type standard table of ty_charname. "#EC *
data: cnt_i type i, "#EC *
 g_tabix type char10. "#EC *
Types: begin of ty_itab_zedidc40.
 include structure edi_dc40.
TYPES: end of ty_itab_zedidc40.
Types: begin of ty_itab_zedidd40.
 include structure edi_dd40.
TYPES: end of ty_itab_zedidd40.
DATA: itab_zedidc40 type standard table of
 ty_itab_zedidc40 initial size 0. "#EC *
DATA: itab_zedidd40 type standard table of
 ty_itab_zedidd40 initial size 0. "#EC *
DATA: wa_itab_zedidc40 type ty_itab_zedidc40.
DATA: wa_itab_zedidd40 type ty_itab_zedidd40.
*MOD-009
data: itab_ze1cuvtm type e1cuvtm, "#EC *
 itab_ze1datem type e1datem, "#EC *
 itab_ze1cuv1m type e1cuv1m. "#EC *
data: wdocnum(16) type n value 0. "#EC *
data: wsegnum(6) type n value 0. "#EC *
data: witemno(10) type n value 0. "#EC *
data: witemno_new(10) type n value 0. "#EC *
data: witemno_gst(10) type n value 0. "#EC *
data: witemno_qst(10) type n value 0. "#EC *
TYPES: BEGIN OF ty_input_data1, "#EC *
 line(560) type c,
 flag(1) type c,
 END OF ty_input_data1.
DATA: i_input_data type standard table of
 ty_input_data1 initial size 0. "with header line.
DATA: i_input_data1 type standard table of
 ty_input_data1 initial size 0. "with header line.
DATA: wa_input_data type ty_input_data1. "#EC *
DATA: g_cnt_input_recs type i. "#EC *
DATA: g_flg_error type c. "#EC *
DATA: l_lines type i. "#EC *
DATA: l_tabix type i. "#EC *
DATA: wa_input_data1 type ty_input_data1. "#EC *
DATA: FILE TYPE STRING.
Fields that are made available to the user:
DATA:
g_cnt_records_read TYPE i, "#EC *
g_cnt_records_transferred TYPE i, "#EC *
g_cnt_transactions_read TYPE i, "#EC *
g_cnt_transactions_transferred TYPE i, "#EC *
g_cnt_idocs_package TYPE i. "#EC *
data: v_log_handle type balloghndl. "#EC *
DATA: gt_curr_edi_dc40 TYPE STANDARD TABLE OF edi_dc40 initial size 0."#EC *
DATA: gt_curr_edi_dd40 TYPE STANDARD TABLE OF edi_dd40 initial size 0."#EC *
DATA: wa_curr_edi_dc40 TYPE edi_dc40. "#EC *
DATA: wa_curr_edi_dd40 TYPE edi_dd40. "#EC *
internal table for error messages during conversion
DATA: g_error_tab TYPE type_errortab, "#EC *
 wa_errortab TYPE type_errorline. "#EC *
DATA: g_edidd_segnam type EDI4SEGNAM, "#EC *
 g_edidd_hlevel type EDI4HLEVEC. "#EC *
DATA: g_segnum(6) TYPE n.
DATA: g_objecttype(2) type C.
DATA: P_FNAME(128) TYPE C VALUE '/usr/sap/trans/vartabheader'. " MODIF ID MD1 OBLIGATORY.
DATA: P_FNAME1(128) TYPE C VALUE '/usr/sap/trans/vartabcontent'. " MODIF ID MD1 OBLIGATORY.
DATA: alv_fldcat TYPE slis_t_fieldcat_alv,
 it_fldcat TYPE lvc_t_fcat.
field-symbols: .
data: dy_table type ref to data,
 dy_line type ref to data,
 xfc type lvc_s_fcat,
 ifc type lvc_t_fcat.
data: l_wa_data TYPE TY_CONTENT,
 itab_data TYPE standard table of TY_CONTENT.
DECLARATION FOR SELECTION SCREEN
*selection-screen skip 1.
*For all the input field entries
SELECTION-SCREEN BEGIN OF BLOCK bl1 WITH FRAME TITLE text-001.
*Parameter for Input File Name:
PARAMETERS: p_inpt TYPE RLGRAP-FILENAME MODIF ID MOD . " Presentation server File Variant table
PARAMETERS: p_inpt1 TYPE RLGRAP-FILENAME MODIF ID MOD . " Presentation server File variant Content
SELECTION-SCREEN END OF BLOCK bl1.
IDoc creation
selection-screen begin of block idocpars
 with frame title text-006.
parameters:
 p_trfcpt as checkbox default C_X MODIF ID MD3,
 p_packge(5) type n default 1 MODIF ID MD3.
selection-screen end of block idocpars.
SELECTION-SCREEN BEGIN OF BLOCK bl3 WITH FRAME TITLE text-032.
Radio Buttons :
parameters:
rb_apsrv RADIOBUTTON GROUP RB1 DEFAULT 'X' USER-COMMAND UCOM,
rb_convt RADIOBUTTON GROUP RB1,
rb_idoc RADIOBUTTON GROUP RB1,
rb_proc RADIOBUTTON GROUP RB1.
SELECTION-SCREEN END OF BLOCK bl3.
INITIALIZATION
INITIALIZATION.
Check selection-screen entries *
*AT SELECTION-SCREEN.
PERFORM sub_get_physical_file USING p_fpath p_fname.
PERFORM sub_get_physical_file1 USING p_fpath1 p_fname1.
AT SELECTION SCREEN
*AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_fname.
PERFORM sub_get_file. " CHANGING p_fname. "#EC *
*AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_fname1.
PERFORM sub_get_file1. " CHANGING p_fname1. "#EC *
AT SELECTION-SCREEN ON VALUE-REQUEST FOR P_INPT.
CALL FUNCTION 'KD_GET_FILENAME_ON_F4'
 EXPORTING
 STATIC = C_X
 CHANGING
 FILE_NAME = P_INPT
 EXCEPTIONS
 MASK_TOO_LONG = 1
 OTHERS = 2.
IF SY-SUBRC <> 0.
 MESSAGE e241.
ENDIF.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR P_INPT1.
CALL FUNCTION 'KD_GET_FILENAME_ON_F4'
 EXPORTING
 STATIC = C_X
 CHANGING
 FILE_NAME = P_INPT1
 EXCEPTIONS
 MASK_TOO_LONG = 1
 OTHERS = 2.
IF SY-SUBRC <> 0.
 MESSAGE e241.
ENDIF.
At Selection Screen Output
AT SELECTION-SCREEN OUTPUT.
IF rb_apsrv = 'X'.
 LOOP AT SCREEN.
 IF SCREEN-GROUP1 = c_mod.
 SCREEN-INPUT = 0.
 ENDIF.
 IF SCREEN-GROUP1 = c_md2.
 SCREEN-INPUT = 0.
 ENDIF.
 IF SCREEN-GROUP1 = c_md3.
 SCREEN-INPUT = 0.
 ENDIF.
 MODIFY SCREEN.
 ENDLOOP.
endif.
IF rb_apsrv = 'X'.
LOOP AT SCREEN.
 IF SCREEN-GROUP1 = c_md1.
 SCREEN-INPUT = 0.
 ENDIF.
 IF SCREEN-GROUP1 = c_md2.
 SCREEN-INPUT = 0.
 ENDIF.
 IF SCREEN-GROUP1 = c_md3.
 SCREEN-INPUT = 0.
 ENDIF.
 MODIFY SCREEN.
ENDLOOP.
endif.
START-OF-SELECTION
START-OF-SELECTION.
*Subroutines for start of selection event
PERFORM sub_start_selection.
IF rb_apsrv = 'X'.
 PERFORM sub_upload_data_app.
 MESSAGE i256.
 LEAVE LIST-PROCESSING.
 EXIT.
ELSE.
 PERFORM sub_upload_data.
ENDIF.
PERFORM sub_upload_data.
Get characteristic details
PERFORM sub_get_cabn.
Get value for characteristics
PERFORM sub_get_cawn.
perform sub_convert_transaction.
END-OF-SELECTION.
END OF SELECTION
*MOD-012
Final message
perform sub_final_message_idoc.
Display errorneous variant tables.
perform sub_display_variant.
Display lines with incorrect data
perform sub_display_errorlines.
*Subroutines for end of selection event
PERFORM sub_end_selection.
perform sub_clear_source_tables.
*MOD-012
*& Include /FACTGLB/GTDMI_VARTAB_FORMS02 *
*& Include /FACTGLB/GTDMI_VARTAB_FORMS02 *

Extract image and its file path

Hi
Here is my HTML source and i want to extract all <img tag and its file path in comma separated string using javascript or in Java
<head>
<meta http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<meta name=ProgId content=Word.Document>
<meta name=Generator content="Microsoft Word 9">
<meta name=Originator content="Microsoft Word 9">
<link rel=File-List href="./index_files/filelist.xml">
<link rel=Edit-Time-Data href="./index_files/editdata.mso">

<title>Untitled Document</title>

<style>

</style>

</head>
<body bgcolor=white lang=EN-US link=blue vlink=blue style='tab-interval:.5in'>
<div class=Section1>
<div align=center>
<table border=0 cellspacing=1 cellpadding=0 width=100 bgcolor="#003399"
style='width:75.0pt;mso-cellspacing:.7pt;background:#003399;mso-padding-alt:
0in 0in 0in 0in'>
<tr>
<td style='background:white;padding:0in 0in 0in 0in'>
<div align=center>
<table border=0 cellspacing=0 cellpadding=0 width=549 style='width:411.75pt;
mso-cellspacing:0in;mso-padding-alt:0in 0in 0in 0in'>
<tr style='height:1.5pt'>
<td style='padding:0in 0in 0in 0in;height:1.5pt'>
<img width=247 height=36 id="_x0000_i1025" src="images\fsl.jpg">
</td>
</tr>
<tr style='height:1.5pt'>
<td style='background:#C6EAFD;padding:0in 0in 0in 0in;height:1.5pt'>
<img width=600
height=202 id="_x0000_i1026" src="images\banner1.jpg">
</td>
</tr>
<tr>
<td style='background:#C6EAFD;padding:0in 0in 0in 0in'>
<table border=0 cellspacing=0 cellpadding=0 width="100%" style='width:100.0%;
mso-cellspacing:0in;mso-padding-alt:1.5pt 1.5pt 1.5pt 1.5pt'>
<tr style='height:1.5pt'>
<td width="38%" style='width:38.0%;padding:1.5pt 1.5pt 1.5pt 1.5pt;
height:1.5pt'>
<![if !supportEmptyParas]> <![endif]><o:p></o:p>
</td>
<td width="62%" style='width:62.0%;padding:1.5pt 1.5pt 1.5pt 1.5pt;
height:1.5pt'>

</td>
</tr>
<tr>
<td colspan=2 style='padding:1.5pt 1.5pt 1.5pt 1.5pt'>
<table border=0 cellspacing=0 cellpadding=0 width="100%"
style='width:100.0%;mso-cellspacing:0in;mso-padding-alt:0in 0in 0in 0in'>
<tr>
<td width="27%" style='width:27.0%;padding:0in 0in 0in 0in'>
 
</td>
<td width="73%" style='width:73.0%;padding:0in 0in 0in 0in'>

</td>
</tr>
</table>
<o:p></o:p>
</td>
</tr>
<tr>
<td colspan=2 style='padding:1.5pt 1.5pt 1.5pt 1.5pt'>
<table border=0 cellspacing=0 cellpadding=0 width="100%"
style='width:100.0%;mso-cellspacing:0in;mso-padding-alt:0in 0in 0in 0in'>
<tr>
<td width="15%" style='width:15.0%;padding:0in 0in 0in 0in'>
 
</td>
<td width="85%" style='width:85.0%;padding:0in 0in 0in 0in'>

</td>
</tr>
</table>
<o:p></o:p>
</td>
</tr>
</table>
<o:p></o:p>
</td>
</tr>
<tr style='height:21.0pt'>
<td style='background:white;padding:0in 0in 0in 0in;height:21.0pt'>

</td>
</tr>
<tr style='height:1.5pt'>
<td valign=top style='background:white;padding:0in 0in 0in 0in;height:1.5pt'>
<div align=center>
<table border=0 cellspacing=0 cellpadding=0 width="100%" style='width:100.0%;
mso-cellspacing:0in;mso-padding-alt:3.0pt 3.0pt 3.0pt 3.0pt'>
<tr style='height:69.75pt'>
<td width="9%" style='width:9.52%;padding:3.0pt 3.0pt 3.0pt 3.0pt;
height:69.75pt'>
<img width=47
height=47 id="_x0000_i1027" src="images\1.gif">
</td>
<td width="28%" style='width:28.24%;padding:3.0pt 3.0pt 3.0pt 3.0pt;
height:69.75pt'>
 frontline ERP 
</td>
<td width="62%" style='width:62.24%;padding:3.0pt 3.0pt 3.0pt 3.0pt;
height:69.75pt'>
Enterprise Resource Planning An ERP system supports the planning of the utilization of the enterprises resources, primarily production, distribution and servicing resources, i.e. inventory, production capacity, logistics capacity, employee work hours, etc.<o:p></o:p>
 
The system works in the modular form and provides complete solution for a small to a large enterprise thus caters to their diverse needs from a simple to complex resource planning and management solution.
</td>
</tr>
<tr>
<td width="9%" style='width:9.52%;padding:3.0pt 3.0pt 3.0pt 3.0pt'>
 
</td>
<td width="28%" style='width:28.24%;padding:3.0pt 3.0pt 3.0pt 3.0pt'>
 
</td>
<td width="62%" style='width:62.24%;padding:3.0pt 3.0pt 3.0pt 3.0pt'>
 
</td>
</tr>
<tr style='height:69.75pt'>
<td width="9%" style='width:9.52%;padding:3.0pt 3.0pt 3.0pt 3.0pt;
height:69.75pt'>
<img width=47
height=47 id="_x0000_i1028" src="images\2.gif">
</td>
<td width="28%" style='width:28.24%;padding:3.0pt 3.0pt 3.0pt 3.0pt;
height:69.75pt'>
 frontline e-Showroom 
</td>
<td width="62%" style='width:62.24%;padding:3.0pt 3.0pt 3.0pt 3.0pt;
height:69.75pt'>
frontline has conceptualized, designed and developed B2B and B2C Portals. The portal provides business rules based shopping for bulk consumers, dealers, corporates & customers. Satellite shops could be setup from the portal that could sell selected / all products from the online shopping mall.

</td>
</tr>
<tr style='height:12.0pt'>
<td width="9%" style='width:9.52%;padding:3.0pt 3.0pt 3.0pt 3.0pt;
height:12.0pt'>
 
</td>
<td width="28%" style='width:28.24%;padding:3.0pt 3.0pt 3.0pt 3.0pt;
height:12.0pt'>
 
</td>
<td width="62%" style='width:62.24%;padding:3.0pt 3.0pt 3.0pt 3.0pt;
height:12.0pt'>
 
</td>
</tr>
<tr style='height:69.75pt'>
<td width="9%" style='width:9.52%;padding:3.0pt 3.0pt 3.0pt 3.0pt;
height:69.75pt'>
<img width=47
height=47 id="_x0000_i1029" src="images\3.gif">
</td>
<td width="28%" style='width:28.24%;padding:3.0pt 3.0pt 3.0pt 3.0pt;
height:69.75pt'>
 frontline SFA
</td>
<td width="62%" style='width:62.24%;padding:3.0pt 3.0pt 3.0pt 3.0pt;
height:69.75pt'>
<o:p></o:p>
A Sales Force Automation System
To organize, manage and improve sales call tracking - helps you SELL more. The most powerful sales force automation system - Automates your company�s sales efforts enabling sales people across the entire sales cycle with contact management, email, fax, SMS and task scheduling.
frontline SFA helps to make the sales pipeline completely transparent, enabling sales teams to track every lead and follow each deal throughout the sales cycle. It enables the Organization to standardize the sales process and to view, manage and control all the activities & information on a real time basis. <o:p></o:p>
 

</td>
</tr>
<tr>
<td width="9%" style='width:9.52%;padding:3.0pt 3.0pt 3.0pt 3.0pt'>
 
</td>
<td width="28%" style='width:28.24%;padding:3.0pt 3.0pt 3.0pt 3.0pt'>
 
</td>
<td width="62%" style='width:62.24%;padding:3.0pt 3.0pt 3.0pt 3.0pt'>
 
</td>
</tr>
<tr style='height:63.0pt'>
<td width="9%" style='width:9.52%;padding:3.0pt 3.0pt 3.0pt 3.0pt;
height:63.0pt'>
<img width=47
height=47 id="_x0000_i1042" src="images\4.gif">
</td>
<td width="28%" style='width:28.24%;padding:3.0pt 3.0pt 3.0pt 3.0pt;
height:63.0pt'>
 frontline CMS <o:p></o:p>
</td>
<td width="62%" style='width:62.24%;padding:3.0pt 3.0pt 3.0pt 3.0pt;
height:63.0pt'>
An Email marketing tool...
<o:p></o:p>
frontline CMS facilitates bulk e - mailing, bulk SMS and bulk mailing and is a very easy operable tool for marketing. It is a very strong web based application having user-friendly interface enabling user to reach thousand of his contacts round the globe through email and SMS just on one click. <o:p></o:p>
</td>
</tr>
<tr style='height:1.5pt'>
<td colspan=3 valign=top style='padding:3.0pt 3.0pt 3.0pt 3.0pt;
height:1.5pt'>
 
</td>
</tr>
<tr style='height:1.5pt'>
<td colspan=3 valign=top style='padding:3.0pt 3.0pt 3.0pt 3.0pt;
height:1.5pt'>
<table border=0 cellspacing=1 cellpadding=0 width="100%" bgcolor="#006699"
style='width:100.0%;mso-cellspacing:.7pt;background:#006699;mso-padding-alt:
3.0pt 3.0pt 3.0pt 3.0pt'>
<tr>
<td style='background:white;padding:3.0pt 3.0pt 3.0pt 3.0pt'>
<table border=0 cellspacing=0 cellpadding=0 width="100%"
style='width:100.0%;mso-cellspacing:0in;mso-padding-alt:0in 0in 0in 0in'>
<tr style='height:1.5pt'>
<td colspan=2 valign=bottom style='padding:0in 0in 0in 0in;
height:1.5pt'>
To know
more about the multi-fold Path rewards:
</td>
</tr>
<tr style='height:48.0pt'>
<td width="54%" style='width:54.0%;padding:0in 0in 0in 0in;
height:48.0pt'>
<ul type=disc>
<li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:
auto;mso-list:l0 level1 lfo3;tab-stops:list .5in'>Call Frontline at
91.11.2921.2331/2</li>
<li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:
auto;mso-list:l0 level1 lfo3;tab-stops:list .5in'>E-mail: <a
href="mailto:[email protected]">[email protected]</a></li>
<li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:
auto;mso-list:l0 level1 lfo3;tab-stops:list .5in'>Visit us at: <a
href="http://www.fsltechnologies.com" target="_blank">www.fsltechnologies.com
</a></li>
</ul>
</td>
<td width="46%" style='width:46.0%;padding:0in 0in 0in 0in;
height:48.0pt'>
<ul type=disc>
<li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:
auto;mso-list:l1 level1 lfo6;tab-stops:list .5in'>Contact us at 
M-6, M Block Market, 
Greater Kailash - II 
New Delhi - 110048, India</li>
</ul>
</td>
</tr>
</table>
<o:p></o:p>
</td>
</tr>
</table>
<o:p></o:p>
</td>
</tr>
<tr style='height:1.5pt'>
<td colspan=3 valign=top style='padding:3.0pt 3.0pt 3.0pt 3.0pt;
height:1.5pt'>
<a
href="www.fsltechnologies.com" target="_blank"><img border=0 width=250 height=60
id="_x0000_i1043" src="images\logo.gif"></a>
</td>
</tr>
<tr style='height:1.5pt'>
<td colspan=3 valign=top style='padding:3.0pt 3.0pt 3.0pt 3.0pt;
height:1.5pt'>
<table border=0 cellspacing=1 cellpadding=0 width="100%"
style='width:100.0%;mso-cellspacing:.7pt;mso-padding-alt:3.0pt 3.0pt 3.0pt 3.0pt'>
<tr>
<td style='padding:3.0pt 3.0pt 3.0pt 3.0pt'>
FSL Software Technologies Ltd an ISO
9001:2000 certified company and a leading software solutions provider,
we realize that in today's competitive environment, business must keep
pace with the speed of thought. And we believe that your ideas and
enterprises deserve substantial reinvention. We address the changing
needs of your business with solutions that are cost-effective, fast to
deploy, highly scalable and reliable
</td>
</tr>
</table>
<o:p></o:p>
</td>
</tr>
</table>
</div>
<o:p></o:p>
</td>
</tr>
</table>
</div>
<o:p></o:p>
</td>
</tr>
</table>
</div>
<![if !supportEmptyParas]> <![endif]><o:p></o:p>
</div>
</body>
</html>
How i do that
Regards
Shambhu

The functionality that you require is not available to VBA/COM - it is only exposed via C/C++.
However, you could retrieve the ENTIRE page image to the clipboard and then use whatever VB/VBA methods you choose to grab a section of the image.
Of course, this all assumes that Adobe Acrobat is installed on each person's computer that will be using the solution since Reader does not have the necessary APIs and Acrobat can't be installed on a server.

User include structure and routines/program/user exits

Hello Gurus,
     following is the step for modify the field catalog in material determination .
Modify the field catalog (OV26)
1.     Add the new field to the user include structure:
o     Header data KOMKDZ
o     Item data KOMPDZ.
2.     Add coding to the routines for assigning values to the new fields in order processing in program MV45AFZA. Use user exits:
o     USEREXIT_MOVE_FIELD_TO_KOMKD (header fields)
o     USEREXIT_MOVE_FIELD_TO_KOMPD (item fields)
3.     Add the new field to the field catalog (Customizing activity Basic Functions  Material Determination  Maintain prerequisites for material determination  Maintain field catalog).
Will you please tell me what the step 1 and step 2 mean ? and what 's the user include structure and USEREXIT_MOVE_FIELD_TO_KOMKD/USEREXIT_MOVE_FIELD_TO_KOMPD and program MV45AFZA ?
thanks very much!

Hi,
KOMKD is cummunication header and KOMPD is communication item which are actually contained in KOMGD structure. So automatically when you add a field to either of header or item it becomes a part of KOMGD. And moreover KOMGD contains all the fields of KOMKD and KOMPD which are required for materail determination.
USEREXIT_MOVE_FIELD_TO_KOMKD
Use this user exit to include or assign values to additional header fields in the communication structure KOMKD taken as a basis for the material determination. This is described in detail in the section "New fields for material determination" .
USEREXIT_MOVE_FIELD_TO_KOMPD
Use this user exit to include or assign values to additional item fields in the communication structure KOMPD taken as a basis for the material determination. This is described in detail in the section "New fields for material determination ".
regards
sadhu kishore

Different number of fields in extract structure and Datasource

Hi All,
There is a data source 0FUNCT_LOC_ATTR, which are showing 16 fields in the datasource. But when i went into the extract structure, it shows 25 fields. Is it any kind of bug?
thanks
Annie

Hi MTi,
Thanks for your reply. I checked in ROOSOURCE and ROOSFIELD table and found that we activated the datasource somewhere in 14.08.2008 and the delivered version is in 18.11.2008. Now i reactivated the datasource in RSA5 and could see all the fields in RSA6.
Actaully we posted the issue to SAP and they have come back with the same reply what you have mentioned.
Cheers
Annie

Extract structure and DS?

Hi Experts,
Some fields(needed) are in Extract structure but not in DS(0svy_data_1)(T-code RSA6) in CRM system.I want to know the reason and how to keep them consistancy?
Thanks and regards,
Gavin

Hi
Just try to maintain the DS in LBWE and see whether ur DS has selected the Hide for those fields.
Khaja

Function to extract characteristics and its value from PI sheet

Hi experts,
I am working on a report to generate Avg. deckle for the month form the PI sheet. In the PI sheet the data that is displayed is basically the message characteristcs and its value.
Please tell me ne function that will give me the related data to be displayed.
Thanks in advance..

reading the characteristics: CAVC_DB_READ_CFG_IN_CBASE.
reading the values according to the characteristics: CARD_CHARACTERISTIC_READ.
Note: the second FM is obsolete according to SAP. but it still works in opposition to the new ones.

Enhance extract structure and RSA7 (not LIS)

I have an extractor (not an LIS one) that I have enhanced to have an additional field. This extractor is delta enabled and uses the RSA7 delta queue. I am being told that to implement in production I have to
1) run a delta load to clear the delta queue
2) stop all users in R/3 from psoting
3) transport the change
It is the step 2) I question - is it really necessary to stop users posting. the argument is that the queue structure will change and may invalidate some delta records. But if I'm just adding a field to the structure I do not think this will mess up the delta's inthe delta queue?
Anyone know with confidence?

Hi,
Yes you have to clear you delta queue; don't forget that you have to run a delta twice since the repeat of a delta needs to be cleared as well.
At the end you have 0 (LUWs) in RSA7
You can also check the number of LUWs pending in SMQ1.
You need to empty your delta queue before transporting your changes.
Simply because if you have data in the queue and you import your changes not only the structure will change, all related programs as well (internal SAP programs not your extractor itself). When you'll request the next delta, the system may not find your new field for the data or just by checking timestamps and versions of the objects will simple refuse to extract it! And if you can't extract it then you'll have to reinit.
Since you need to have an empty queue, how could you ensure that it remains empty other than preventing users to post transactions?
If your point is to NOT disrupt operations and your are able to reload the possible missed transactions, then empty your queue, delete the init, import your changes and then re init your delta; which I think will suits you better.
In theory you are right, you don't need downtime for postings and we have tested that with no issue for NON LIS sources (the data is stored at posting time); still I don't recommend it.
In any case, if you are well prepared, the disruption is only 5 or 10 minutes max in the source system during which you stop background processing with BTCTRANS1 (if I remember correctly) and you lock/kick user out (during the night for example).
We have done that lots of times and are running R/3 with different time zones.... so we always take the opportunity when R/3 guys need a downtime for any parameter changes or DB stuff...
hope this helps
Olivier.
Message was edited by:
Olivier Cora

Regarding LIS Extract Structure and Delta Queues

Hi All,
We are extracting data using 2LIS_01_S001. But we are unable to pull Delta loads. When we verified we found that the structure (Fields)of the Delta queues are not in same order as S001 table. So, we modified the structures of delta queues using the access key. Now the order of fields in S001, S001BIW1 and S001BIW1 are all same. Till now I was unable to load the deltas for the data source. Now my doubt is should I have to do the LIS setups again (Statistical Information Setup)or can I do a Full Load and do deltas directly???

Hi,
You have to setup the tables once again.If your requirement is to load the customer data donot depend on LIS because there are lot of problems with this LIS.SAP is not recommending this LIS.Simply load customer attribute data and load transaction LOS also.
This is a better option.
Hope this helps.
Assign points if useful.
Regards,
venkat

The link Query and its programe

Dear All,
We have a transaction code, like as ZCCOR09. And we can check it in SE93, finding it's created from a program based from Query.
The name of the program is "AQZZ/SAPQUERY/AM01========".
The question is that how can we know the name of the that query?
Thanks,
James

Hi Keritesh,
Thank you for you kind answer.
Thanks,
James

Extract Structure and its program

Similar Messages

Maybe you are looking for