Field Catalog from data object..

Hi all,
data:
g_head_ref      TYPE REF TO data,
       g_item_ref      TYPE REF TO data.
    CALL BADI handle->set_header_item_data
      EXPORTING
        i_document_type    = g_document_type
        i_head_item        = g_head_item
        i_ab_document_type = doc_typ
        i_header_table     = g_header_table
        i_item_table       = g_item_table
        i_map_fields       = g_map_fields
      IMPORTING
        e_subrc            = l_subrc
        e_head_ref         = g_head_ref
        e_item_ref         = g_item_ref.
here i get the g_data_ref and g_item_ref filled with the values..
now i assigned these object to field symbols to display the same in the ALV.....
Issues is follwoing-->
I dont know the table structure or table name with which these ref object or the field symbols is type of now....
(in this case it can be a local prog type defined structure..)..
how can i create a fieldcatlog out of it..??
I have already tried
FM 'REUSE_ALV_FIELDCATALOG_MERGE' --> need an internal table with defined type...
cl_abap_structdescr=>describe_by_data --> need a DDIC structure (in this case it can be a local prog type defined structure..)..
if the class cl_abap_structdescr is the correct way to do it...please let me know exact flow of methods...if there is some other solution do let me know.
Regards,
Yadesh

Hi
i don't know what the variable g_map_fields, perhaps has it the definition of the table? if it's so you can use it to fill catalog table for ALV, else you can use CL_ABAP_STRUCTDESCR
data: g_head_ref TYPE REF TO data.
data: g_item_ref TYPE REF TO data.
field-symbols: <fs_head> type table.
field-symbols: <fs_wa> type any.
data: l_comp type flag.
DATA: MY_STRUCT TYPE REF TO CL_ABAP_STRUCTDESCR.
ASSIGN g_head_ref->* TO <fs_head>.
LOOP AT <fs_head> ASSIGNING <fs_wa>.
MY_STRUCT ?= CL_ABAP_TYPEDESCR=>DESCRIBE_BY_DATA( <fs_wa> ).
EXIT.
ENDLOOP.
Now in MY_STRUCT->COMPONENTS you have the definition of the table and u can use it in order to fill the catalog table for ALV
Max

Similar Messages

Runtime error when Transfering data from data object to a file

Hi everybody,
I'm having a problem when I transfer data from data object to file. The codes like following :
data : full_path(128).
OPEN DATASET full_path FOR OUTPUT IN TEXT MODE ENCODING DEFAULT.
and transfer data from flat structure to this file full_path
move:    tab                 to c_output-tab_5,
              tab                 to c_output-tab_4,
              tab                 to c_output-tab_3.
transfer c_output to full_path.      // Error Line
The detail error like the following:
For the statement
   "TRANSFER f TO ..."
only character-type data objects are supported at the argument position
"f".
In this case. the operand "f" has the non-character-type "u". The
current program is a Unicode program. In the Unicode context, the type
'X' or structures containing not only character-type components are
regarded as non-character-type.
transfer c_output to full_path. " Line error
Please help me to fix this issue !
Thank you in advance !
Edited by: Hai Nguyen on Mar 4, 2009 10:55 AM

Hi Mickey,
Thanks for your answer,
I found out that the structure c_output have the field with data type X. I know that the cause of the issue.
      begin of c_output,
         vbeln(10),
         tab_5 like tab,
         posnr(6),
         tab_4 like tab,
         topmat(18),
         tab_3 like tab,
     end of c_output.
data : tab type X value 9.
Could you tell me how to fix it ? What I have to do in this situation ?
Thank you very much !

Using instruction for creating field catalog to archive object "MM_MATNR"

Hi all,
I need a using instruction for creating a new field catalog to archive object "MM_MATNR". I'd like to create a field catalog using some fields of tables mara, makt, mvke and marc.
Thanks for your help!

Hi,
Go to following link;
[Material Master Archiving|http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/90f75a80-867f-2d10-7aa6-ac164e43e89f?quicklink=index&overridelayout=true]

Field catalog in abap objects

hi friends,
               i am using factory method to display my alv. now some of the fields in my internal table i have declared them as char fields, i want certain type of headings for these fields,so where can i give heading to these fields.
               where exactly do we create a field catalog for factory method.
pls advice me on this

hi
good
go throgh this code
*& Report Z_ALV_OOPS
REPORT Z_ALV_OOPS.
*Event class Definition                             "Event handler class
class event_handle definition.
public section.
    methods: handle_user
      for event user_command of cl_gui_alv_grid
      importing e_ucomm.
endclass.
*Event class Implementation
class event_handle implementation.
method handle_user.
    write:/ ''.
endmethod.
endclass.
Data: t_alv       type ref to cl_gui_alv_grid,           "ALV control
      t_cont      type ref to cl_gui_custom_container,   "Cust Container
      t_alv2      type ref to cl_gui_alv_grid,           "ALV control
      t_cont2     type ref to cl_gui_custom_container,   "Cust Container
      t_fieldcat type lvc_t_fcat with header line,      "Field Cat
      t_fieldcat2 type lvc_t_fcat with header line,      "Field Cat
      t_layout    type lvc_s_layo,                       "Layout
      t_event     type ref to event_handle,              "Event handler
      t_sort      type LVC_T_SORT with header line,      "Sort
      t_toolbar   type ui_functions with header line.    "Toolbar xclude
Types: begin of g_vbak,                                 "Header Table
         vbeln like vbak-vbeln,
         auart like vbak-auart,
         vkorg like vbak-vkorg,
         vtweg like vbak-vtweg,
         spart like vbak-spart,
         kunnr like vbak-kunnr,
         bstnk like vbak-bstnk,
         seltab,
       end of g_vbak.
Types: begin of g_vbap,                                  "Item Table
         vbeln like vbap-vbeln,
         posnr(6) type c,
        posrn like vbap-posnr,
         matnr like vbap-matnr,
         netwr like vbap-netwr,
         waerk like vbap-waerk,
       end of g_vbap.
Data: t_vbak type g_vbak occurs 0,
      t_vbap type g_vbap occurs 0.
Start-Of-Selection.
*Fetch data from DB Table
select vbeln auart vkorg vtweg spart kunnr bstnk
    from vbak into table t_vbak up to 20 rows.
End-Of-Selection.
*Call ALV screen
call screen 100.
*&      Module STATUS_0100 OUTPUT
      text
MODULE STATUS_0100 OUTPUT.
SET PF-STATUS 'ALV'.
SET TITLEBAR 'VBAK'.
if t_cont is initial.
create object t_cont
    exporting
      container_name = 'ALV'.
create object t_alv
    exporting
      i_parent = t_cont.
*Create event handlers
create object t_event.
set handler t_event->handle_user for t_alv.
perform build_fieldcatlog.
perform build_layout.
perform xclude_toolbar.
CALL METHOD t_alv->SET_TABLE_FOR_FIRST_DISPLAY
    EXPORTING
     I_BUFFER_ACTIVE               =
     I_BYPASSING_BUFFER            =
     I_CONSISTENCY_CHECK           =
     I_STRUCTURE_NAME              =
     IS_VARIANT                    =
     I_SAVE                        =
     I_DEFAULT                     = 'X'
      IS_LAYOUT                     = t_layout
     IS_PRINT                      =
     IT_SPECIAL_GROUPS             =
      IT_TOOLBAR_EXCLUDING          = t_toolbar[]
     IT_HYPERLINK                  =
     IT_ALV_GRAPHICS               =
     IT_EXCEPT_QINFO               =
    CHANGING
      IT_OUTTAB                     = t_vbak[]
      IT_FIELDCATALOG               = t_fieldcat[]
     IT_SORT                       =
     IT_FILTER                     =
   EXCEPTIONS
     INVALID_PARAMETER_COMBINATION = 1
     PROGRAM_ERROR                 = 2
     TOO_MANY_LINES                = 3
     others                        = 4
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
             WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
endif.
ENDMODULE.                 " STATUS_0100 OUTPUT
*&      Module USER_COMMAND_0100 INPUT
      text
MODULE USER_COMMAND_0100 INPUT.
Data: lt_rows type lvc_t_row,
      wa_rows type line of lvc_t_row,
      wa_vbak type g_vbak,
      l_lines type i.
refresh: t_vbap.
case sy-ucomm.
when 'DET'.                                  "Item details
Get selected rows from ALV
    call method t_alv->get_selected_rows
        importing
            et_index_rows = lt_rows.
Fetch corresponding Item details from VBAP
    loop at lt_rows into wa_rows.
      read table t_vbak into wa_vbak index wa_rows-index transporting
                                                                vbeln.
      select vbeln posnr matnr netwr waerk from vbap
          appending corresponding fields of table t_vbap
          where vbeln = wa_vbak-vbeln.
    endloop.
Prepare fieldcatlog
Display Item details in ALV
    call screen 200 starting at 8 5.
when 'SHOW'.                                  "Display order
    call method t_alv->get_selected_rows
        importing
            et_index_rows = lt_rows.
    Describe table lt_rows lines l_lines.
    if l_lines > 1.
      message e999(z_error).
    else.
      read table lt_rows into wa_rows index 1.
      read table t_vbak into wa_vbak index wa_rows-index transporting
                                                                vbeln.
      set parameter id 'AUN' field wa_vbak-vbeln.
      call transaction 'VA03' and skip first screen.
    endif.
endcase.
ENDMODULE.                 " USER_COMMAND_0100 INPUT
*&      Form build_fieldcatlog
      text
form build_fieldcatlog .
clear t_fieldcat.
t_fieldcat-col_pos = '1'.
t_fieldcat-fieldname = 'VBELN'.
t_fieldcat-ref_table = 'VBAK'.
t_fieldcat-ref_field = 'VBELN'.
append t_fieldcat.
t_fieldcat-col_pos = '2'.
t_fieldcat-fieldname = 'AUART'.
t_fieldcat-ref_table = 'VBAK'.
t_fieldcat-ref_field = 'AUART'.
append t_fieldcat.
t_fieldcat-col_pos = '3'.
t_fieldcat-fieldname = 'VKORG'.
t_fieldcat-ref_table = 'VBAK'.
t_fieldcat-ref_field = 'VKORG'.
append t_fieldcat.
t_fieldcat-col_pos = '4'.
t_fieldcat-fieldname = 'VTWEG'.
t_fieldcat-ref_table = 'VBAK'.
t_fieldcat-ref_field = 'VTWEG'.
append t_fieldcat.
t_fieldcat-col_pos = '5'.
t_fieldcat-fieldname = 'SPART'.
t_fieldcat-ref_table = 'VBAK'.
t_fieldcat-ref_field = 'SPART'.
append t_fieldcat.
t_fieldcat-col_pos = '6'.
t_fieldcat-fieldname = 'KUNNR'.
t_fieldcat-ref_table = 'VBAK'.
t_fieldcat-ref_field = 'KUNNR'.
append t_fieldcat.
t_fieldcat-col_pos = '7'.
t_fieldcat-fieldname = 'BSTNK'.
t_fieldcat-ref_table = 'VBAK'.
t_fieldcat-ref_field = 'BSTNK'.
append t_fieldcat.
endform.                    " build_fieldcatlog
*&      Module LEAVE INPUT
      text
module LEAVE input.
case sy-ucomm.
when 'BACK' or 'EXIT' or 'CANCEL'.
    leave program.
endcase.
endmodule.                 " LEAVE INPUT
*&      Form build_layout
      text
--> p1        text
<-- p2        text
form build_layout .
t_layout-zebra = 'X'.
t_layout-sel_mode = 'A'.
t_layout-grid_title = 'Header Details'.
endform.                    " build_layout
*&      Form build_fcat_vbap
      text
form build_fcat_vbap .
clear t_fieldcat2.
t_fieldcat2-scrtext_m = 'Sales Doc'.
t_fieldcat2-col_pos = 1.
t_fieldcat2-fieldname = 'VBELN'.
t_fieldcat2-tabname = 'T_VBAP'.
t_fieldcat2-no_zero = 'X'.
t_fieldcat2-ref_table = 'VBAP'.
t_fieldcat2-ref_field = 'VBELN'.
append t_fieldcat2.
clear t_fieldcat2.
t_fieldcat2-col_pos = 2.
t_fieldcat2-scrtext_m = 'Item'.
t_fieldcat2-fieldname = 'POSNR'.
t_fieldcat2-tabname = 'T_VBAP'.
t_fieldcat2-intlen = '6'.
t_fieldcat2-inttype = 'C'.
t_fieldcat2-no_zero = 'X'.
t_fieldcat2-ref_table = 'VBAP'.
t_fieldcat2-ref_field = 'POSNR'.
append t_fieldcat2.
clear t_fieldcat2.
t_fieldcat2-col_pos = 3.
t_fieldcat2-fieldname = 'MATNR'.
t_fieldcat2-ref_table = 'VBAP'.
t_fieldcat2-ref_field = 'MATNR'.
append t_fieldcat2.
clear t_fieldcat2.
t_fieldcat2-col_pos = 4.
t_fieldcat2-fieldname = 'NETWR'.
t_fieldcat2-ref_table = 'VBAP'.
t_fieldcat2-ref_field = 'NETWR'.
t_fieldcat2-do_sum = 'X'.
append t_fieldcat2.
clear t_fieldcat2.
t_fieldcat2-col_pos = 5.
t_fieldcat2-fieldname = 'WAERK'.
t_fieldcat2-ref_table = 'VBAP'.
t_fieldcat2-ref_field = 'WAERK'.
append t_fieldcat2.
endform.                    " build_fcat_vbap
*&      Module STATUS_0200 OUTPUT
      text
module STATUS_0200 output.
SET PF-STATUS 'ITEM1'.
SET TITLEBAR 'VBAP'.
perform build_fcat_vbap.
perform sort_alv2.
if t_cont2 is initial.
create object t_cont2
    exporting
      container_name = 'ITEM'.
create object t_alv2
    exporting
      i_parent = t_cont2.
t_layout-grid_title = 'Item Details'.
CALL METHOD t_alv2->set_table_for_first_display
    EXPORTING
     I_BUFFER_ACTIVE               =
     I_BYPASSING_BUFFER            =
     I_CONSISTENCY_CHECK           =
     I_STRUCTURE_NAME              =
     IS_VARIANT                    =
     I_SAVE                        =
     I_DEFAULT                     = 'X'
      IS_LAYOUT                     = t_layout
     IS_PRINT                      =
     IT_SPECIAL_GROUPS             =
      IT_TOOLBAR_EXCLUDING          = t_toolbar[]
     IT_HYPERLINK                  =
     IT_ALV_GRAPHICS               =
     IT_EXCEPT_QINFO               =
     IR_SALV_ADAPTER               =
    CHANGING
      it_outtab                     = t_vbap[]
      IT_FIELDCATALOG               = t_fieldcat2[]
      IT_SORT                       = t_sort[]
     IT_FILTER                     =
   EXCEPTIONS
     INVALID_PARAMETER_COMBINATION = 1
     PROGRAM_ERROR                 = 2
     TOO_MANY_LINES                = 3
     others                        = 4
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
             WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
else.
CALL METHOD t_alv2->refresh_table_display
   EXPORTING
     IS_STABLE      =
     I_SOFT_REFRESH =
   EXCEPTIONS
     FINISHED       = 1
     others         = 2
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
             WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
endif.
endmodule.                 " STATUS_0200 OUTPUT
*&      Module USER_COMMAND_0200 INPUT
      text
module USER_COMMAND_0200 input.
case sy-ucomm.
when 'GOBACK'.
    leave to screen 0.
endcase.
endmodule.                 " USER_COMMAND_0200 INPUT
*&      Form sort_alv2
      text
--> p1        text
<-- p2        text
form sort_alv2 .
clear t_sort.
t_sort-spos = '1'.
t_sort-fieldname = 'VBELN'.
t_sort-up = 'X'.
t_sort-subtot = 'X'.
append t_sort.
endform.                    " sort_alv2
*&      Form xclude_toolbar
      text
--> p1        text
<-- p2        text
form xclude_toolbar .
t_toolbar = '&DETAIL'.
append t_toolbar.
t_toolbar = '&&SEP00'.
append t_toolbar.
t_toolbar = '&&SEP01'.
append t_toolbar.
t_toolbar = '&&SEP02'.
append t_toolbar.
t_toolbar = '&SORT_ASC'.
append t_toolbar.
t_toolbar = '&SORT_DSC'.
append t_toolbar.
t_toolbar = '&FIND'.
append t_toolbar.
t_toolbar = '&MB_FILTER'.
append t_toolbar.
t_toolbar = '&&SEP04'.
append t_toolbar.
t_toolbar = '&MB_SUM'.
append t_toolbar.
t_toolbar = '&MB_SUB_TOTAL'.
append t_toolbar.
t_toolbar = '&PRINT_BACK'.
append t_toolbar.
t_toolbar = '&MB_VIEW'.
append t_toolbar.
t_toolbar = '&MB_EXPORT'.
append t_toolbar.
t_toolbar = '&GRAPH'.
append t_toolbar.
t_toolbar = '&COLO'.
append t_toolbar.
t_toolbar = '&&SEP06'.
append t_toolbar.
t_toolbar = '&&SEP07'.
append t_toolbar.
t_toolbar = '&INFO'.
append t_toolbar.
t_toolbar = '&&SEP03'.
append t_toolbar.
endform.                    " xclude_toolbar
reward point if helpful.
thanks
mrutyun^

Drop Indexes from Data Object in DOE

Hi,
I have created the index for data object by using Mobile Appli Attrib tab in DOE workbench. But now I need to remove it. Everytime I remove checkbox and index name and save it. Now I open the data object again index will be there,it will not be removed.
Thanks & Regards,
Manisha Dabour.

Hi Monisha,
I tried the same in 710 SP11 system and I could delete the index name and uncheck check boxes.
Below are the steps I did.
-- Selected the root node of a DO.
-- Clicked on "Mobile Appln Attribute.
-- Chose client type in the popup as "JAVACLNT" .
-- Checked few fields and entered a index name.
-- Saved the changes.
-- repeated the above and uncheckd fields/removed index and did some changes.
Observed that everytime my latest changes were captured.
Can you please open a OSS message for the same.
Regards
Rohith

Lookup field in external data-object????

Hi All.
Is it possible to create lookup field in data object with external data-source?

Hi ,
yes you can create.look ups for any Data Objects.
Regards
Siva Sankar

Getting Day, month and year from Date object

hello everybody,
Date mydate = Resultset.getDate(indexField);
Now i would like to get day, month and year from mydate.
In another words, i'm looking for something equivalent to
mydate.getDay() as this method is deprecated.
Can somebody help me out please?
Thank you in advance,

swvc2000,
Here is a sample class that demonstrates two ways in which to do this.import java.util.*;
import java.text.*;
public class DateSplitter {
   public static void main(String args[]) {
      /* even though your date is from a result set,
         pretend the following date is your date that
         you are using. The try catch block is used
         because I hand-crafted my date using
         SimpleDateFormat. Substitute your date.*/
      Date yourDate = null;
      try {
         SimpleDateFormat formatter = new SimpleDateFormat("MM/dd/yyyy");
         yourDate = formatter.parse("05/06/2000");
      } catch (ParseException e) { }
      //the following gets the current date
      Calendar c = Calendar.getInstance();
      //use the calendar object to set it to your date
      c.setTime(yourDate);
      //note months start at zero
      int month = c.get(Calendar.MONTH);
      int year = c.get(Calendar.YEAR);
      int dayOfMonth = c.get(Calendar.DAY_OF_MONTH);
      System.out.println("Calendar Month: "+month);
      System.out.println("Calendar Day: "+dayOfMonth);
      System.out.println("Calendar Year: "+year);
      System.out.println();
      /* Simple date format can also be used to strip them
         out of your date object. When you use it, notice that
         months start at 1. Also, it returns string values. If
         you need integer values, you will have to use
         Integer.parseInt() as I did below. If you are
         only concerned about the string values, just remove
         the Integer.parseInt part. */
      DateFormat formatter = new SimpleDateFormat("M");
      month = Integer.parseInt(formatter.format(yourDate));
      System.out.println("SDF Month: "+ month);
      formatter = new SimpleDateFormat("d");
      dayOfMonth = Integer.parseInt(formatter.format(yourDate));
      System.out.println("SDF Day: "+ dayOfMonth);
      formatter = new SimpleDateFormat("yyyy");
      year = Integer.parseInt(formatter.format(yourDate));
      System.out.println("SDF Year: "+ year);
   }//end main
}//end DateSplitter classtajenkins

Fields missing from Data Source but displayed in RSA3

Hello Experts
I have an issue while finding for a field in the data source. As I am looking for some fields : MABST, MINBE, EISBE on BW Side but not found. When I llok the same fields in ECC Side in the table RSOSFieldmap, then I get these fields in 0MAT_PLANT_ATTR Data Source. In the same time , the fields are not available in the Data source on BW Side as well as on ECC Side(while goin thru RSA6). Also when I execute the RSA3 for the data source, I am getting the data in the Missing Fields. How it can be possible? Also plz let me know how can I make these fields available in Data Source.
I replicate the data source, also i looked for the hidden fields, but still not succeed.
Thanks in advance
Neha

Hello,
TO unhide the field,
Just Goto T.code RSO2 > press change button.> unhide the filds and --> Generate the Datasource
or
Goto RSA6 --> select the Datasource and --> press change button (pencil icon) --> unhide the filed --> Save and Generate the Datasource.
Try the above two option and check if it is working.
also go thru the below post
BI : Hidden field Datasource
Hope this helps,
Sri...

Field label from data element (language dependent)

I have 2 development systems and am struggling to get different language from a standard sap data element.
On Dev system 1 the program is:
parameters: l_file1 like filename-fileintern.
In the selection texts of the program I select "Dictionary ref." and the text is automatically populated with the value "Logical File" i.e. it picks it up from the data element FILEINTERN of the parameter.
Now I log out and log back in in German and in this field I have "logische Datei" i.e. as expected this is the value in the data element of FILEINTERN.
When I logon in English and execute the program, the selection screen has "Logical File", and when I login in German and execute the program the selection screen has "logische Datei".
All well and good at this point and everything works as expected.
On Dev system 2 I have exactly the same program i.e. the same parameter, and same selection text settings.
However when I logon in English and execute the program I get "Logical File", but when I log on in German and execute it displays "L_FILE1" i.e. the name of the parameter and not the data element text value?
Any help greatly appreciated.

Hi Edgar and Sree,
Yes I have checked the data element in both systems and it is identical. In fact in the 2nd system when I log in in German and display the selection text it is correctly in German, only when I execute the program I don't get the value on the screen!
I realise I can simply uncheck this "dictionary ref." and translate the value myself but i want to understand why this doesn't work.... argh.

Unable to create Model from DOE Data Object

Hi,
I created a Mobile Laptop WebDynpro DC in NWDS 7.1, the build and deploy work fine.
The problem is that when I attempt to create a Model based on a Data Object from the
Mobile Middleware 7.1 DOE, I always get an exception when the Data Object metadata is
imported (the last step of the Model Creation Wizard).
Here's the exception :
Status ERROR
Plugin : com.sap.ide.cmi.core
code=0
Internal error
   Plugin name: Common Model Tools Core
   Internal error : com.sap.ide.cmi.core
   Class      : com.sap.tc.mobile.dt.metaimp.ModelImportWizard
   Method     : run(IProgressMonitor)
   Message    : Failed to create model
   Exception : com.sap.ide.metamodel.general.exception.ObjectRequiredException: ModelClassPropertySetting "//WebDynpro/ModelClass:ca.test.sandbox.mitest1.test3.ZTESTDATAOBJ/Property:ACTUAL/Setting:backendKey", Role "SettingDefinition": A minimum of 1 object(s) is required
ObjectRequiredException: ModelClassPropertySetting "//WebDynpro/ModelClass:ca.test.sandbox.mitest1.test3.ZTESTDATAOBJ/Property:ACTUAL/Setting:backendKey", Role "SettingDefinition": A minimum of 1 object(s) is required
at com.sap.ide.metamodel.webdynpro.implementation.ModelClassPropertySettingProxy._validate(ModelClassPropertySettingProxy.java:358)
at com.sap.ide.metamodel.core.DevelopmentObjectProxy.validate(DevelopmentObjectProxy.java:825)
at com.sap.tc.mobile.dt.metaimp.MBOModelImporter.doImport(MBOModelImporter.java:170)
at com.sap.tc.mobile.dt.metaimp.ModelImportWizard.createModel(ModelImportWizard.java:200)
at com.sap.ide.cmi.core.model.importer.CMIWizard$2.run(CMIWizard.java:197)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:113)
I know this is not related to Middleware authorization, I tested with a userid with full DOE authorization.
When I display the Data Object metadata from the Middleware, it shows as status 'active'.
The exception seems to complain about the backend key, but there is a backend key field in
the Data Object.
I have the same exception even with any SAP delivered Data Objects (MAM30_001, etc..).
any thoughts on what the problem is ?
thanks,
Yanick.

Hi Yannick,
This type of error can occur with local non-dc Mobile App when some jars required for the model generation are missing.
The easiest way to fix this is to create a DC for your Mobile app from the
Mobile App Offline perspective.
Let me know if it works
Genevieve

Calculation Field to be mapped to different data object's column name in Oracle BAM 12c

Hi,
I am having a challenge to enable drill down to 2nd level report by passing calculation field as parameter.
As an alternative, I am thinking to point calculation field to another data object’s column name and generate report so that I would be able to pass that as parameter to drilling report view.
Is there any way to map calculation field to different Data object’s column name? Thanks in advance.
Regards
Amik Basu

1. Yes, you can.
SQL> create table ÜÝÞ( ßàá number(10));
Table created.
SQL> insert into ÜÝÞ values (10);
1 row created.1.1 and 1.2 and 2. You can choose UTF as your default character set. It allows the user of non-English characters in VARCHAR columns in your whole database. It is not per tablespace.
SQL> create table ÜÝÞ( ßàá varchar2(100));
Table created.
SQL> insert into ÜÝÞ values ('âãäçìé');
1 row created.

Difference b/w DATA TYPE and DATA OBJECT & differences b/w TYPE and LIKE

hai
can any one say the differences between Data type and Data Object.
And also differences between TYPE and LIKE
thanks
Gani

hi,
_Data Types and Data Objects_
      Programs work with local program data that is, with byte sequences in the working memory. Byte sequences that belong together are called fields and are characterized by a length, an identity (name), and as a further attribute by a data type. All programming languages have a concept that describes how the contents of a field are interpreted according to the data type.
      In the ABAP type concept, fields are called data objects. Each data object is thus an instance of an abstract data type. There are separate name spaces for data objects and data types. This means that a name can be the name of a data object as well as the name of a data type simultaneously.
Data Types
   As well as occurring as attributes of a data object, data types can also be defined independently. You can then use them later on in conjunction with a data object. The definition of a user-defined data type is based on a set of predefined elementary data types. You can define data types either locally in the declaration part of a program using the TYPESstatement) or globally in the ABAP Dictionary. You can use your own data types to declare data objects or to check the types of parameters in generic operations.
     All programming languages distinguish between various types of data with various uses, such as .. type data for storing or displaying values and numerical data for calculations. The attributes in question are described using data types. You can define, for example, how data is stored in the repository, and how the ABAP statements work with the data.
Data types can be divided into elementary, reference, and complex types.
a. Elementary Types
These are data types of fixed or variable length that are not made up of other types.
The difference between variable length data types and fixed length data types is that the length and the memory space required by data objects of variable length data types can change dynamically during runtime, and that these data types cannot be defined irreversibly while the data object is being declared.
Predefined and User-Defined Elementary Data Types
You can also define your own elementary data types in ABAP using the TYPES statement. You base these on the predefined data types. This determines all of the technical attributes of the new data type. For example, you could define a data type P_2 with two decimal places, based on the predefined data type P. You could then use this new type in your data declarations.
b. Reference Types
Reference types are deep data types that describe reference variables, that is, data objects that contain references. A reference variable can be defined as a component of a complex data object such as a structure or internal table as well as a single field.
c. Complex Data Types
Complex data types are made up of other data types. A distinction is made here between structured types and table types.
Data Objects
      Data objects are the physical units with which ABAP statements work at runtime. The contents of a data object occupy memory space in the program. ABAP statements access these contents by addressing the name of the data object and interpret them according to the data type.. For example, statements can write the contents of data objects in lists or in the database, they can pass them to and receive them from routines, they can change them by assigning new values, and they can compare them in logical expressions.
       Each ABAP data object has a set of technical attributes, which are fully defined at all times when an ABAP program is running (field length, number of decimal places, and data type). You declare data objects either statically in the declaration part of an ABAP program (the most important statement for this is DATA), or dynamically at runtime (for example, when you call procedures). As well as fields in the memory area of the program, the program also treats literals like data objects.
        A data object is a part of the repository whose content can be addressed and interpreted by the program. All data objects must be declared in the ABAP program and are not persistent, meaning that they only exist while the program is being executed. Before you can process persistent data (such as data from a database table or from a sequential file), you must read it into data objects first. Conversely, if you want to retain the contents of a data object beyond the end of the program, you must save it in a persistent form.
Declaring Data Objects
      Apart from the interface parameters of procedures, you declare all of the data objects in an ABAP program or procedure in its declaration part. These declarative statements establish the data type of the object, along with any missing technical attributes. This takes place before the program is actually executed. The technical attributes can then be queried while the program is running.
     The interface parameters of procedures are generated as local data objects, but only when the procedure is actually called. You can define the technical attributes of the interface parameters in the procedure itself. If you do not, they adopt the attributes of the parameters from which they receive their values.
ABAP contains the following kinds of data objects:
a. Literals
Literals are not created by declarative statements. Instead, they exist in the program source code. Like all data objects, they have fixed technical attributes (field length, number of decimal places, data type), but no name. They are therefore referred to as unnamed data objects.
b. Named Data Objects
Data objects that have a name that you can use to address the ABAP program are known as named objects. These can be objects of various types, including text symbols, variables and constants.
Text symbols are pointers to texts in the text pool of the ABAP program. When the program starts, the corresponding data objects are generated from the texts stored in the text pool. They can be addressed using the name of the text symbol.
Variables are data objects whose contents can be changed using ABAP statements. You declare variables using the DATA, CLASS-DATA, STATICS, PARAMETERS, SELECT-OPTIONS, and RANGESstatements.
Constants are data objects whose contents cannot be changed. You declare constants using the CONSTANTSstatement.
c. Anonymous Data Objects
Data objects that cannot be addressed using a name are known as anonymous data objects. They are created using the CREATE DATAstatement and can be addressed using reference variables.
d. System-Defined Data Objects
System-defined data objects do not have to be declared explicitly - they are always available at runtime.
e. Interface Work Areas
Interface work areas are special variables that serve as interfaces between programs, screens, and logical databases. You declare interface work areas using the TABLES and NODESstatements.
What is the difference between Type and Like?
Answer1:
TYPE, you assign datatype directly to the data object while declaring.
LIKE,you assign the datatype of another object to the declaring data object. The datatype is referenced indirectly.
Answer2:
Type is a keyword used to refer to a data type whereas Like is a keyword used to copy the existing properties of already existing data object.
Answer3:
type refers the existing data type
like refers the existing data object
reward if useful
thanks and regards
suma sailaja pvn

Data types and data objects

diff b/w data types and data objects

hi prasanth,
Data Types and Data Objects
Programs work with local program data that is, with byte sequences in the working memory. Byte sequences that belong together are called fields and are characterized by a length, an identity (name), and as a further attribute by a data type. All programming languages have a concept that describes how the contents of a field are interpreted according to the data type.
In the ABAP type concept, fields are called data objects. Each data object is thus an instance of an abstract data type. There are separate name spaces for data objects and data types. This means that a name can be the name of a data object as well as the name of a data type simultaneously.
Data Types
Data types are templates for creating data objects. Data types can be defined independently in the ABAP program or in the ABAP Dictionary. As attributes of a data object, data types can also exist in a non-independent state. Data types do not use any memory space for work data, but may require memory for administration information.
As well as occurring as attributes of a data object, data types can also be defined independently. You can then use them later on in conjunction with a data object. The definition of a user-defined data type is based on a set of predefined elementary data types. You can define data types either locally in the declaration part of a program using the TYPESstatement) or globally in the ABAP Dictionary. You can use your own data types to declare data objects or to check the types of parameters in generic operations.
All programming languages distinguish between various types of data with various uses, such as .. type data for storing or displaying values and numerical data for calculations. The attributes in question are described using data types. You can define, for example, how data is stored in the repository, and how the ABAP statements work with the data.
Data types can be divided into elementary, reference, and complex types.
a. Elementary Types
These are data types of fixed or variable length that are not made up of other types.
The difference between variable length data types and fixed length data types is that the length and the memory space required by data objects of variable length data types can change dynamically during runtime, and that these data types cannot be defined irreversibly while the data object is being declared.
Predefined and User-Defined Elementary Data Types
You can also define your own elementary data types in ABAP using the TYPES statement. You base these on the predefined data types. This determines all of the technical attributes of the new data type. For example, you could define a data type P_2 with two decimal places, based on the predefined data type P. You could then use this new type in your data declarations.
b. Reference Types
Reference types are deep data types that describe reference variables, that is, data objects that contain references. A reference variable can be defined as a component of a complex data object such as a structure or internal table as well as a single field.
c. Complex Data Types
Complex data types are made up of other data types. A distinction is made here between structured types and table types.
Data Objects
A data object is an instance of a data type and occupies as much memory space as its type specifies. An ABAP program only works with data that is available as content of data objects. Data objects are either created implicitly as named data objects, or exanonymous data objects using CREATEDATA.
Data objects are the physical units with which ABAP statements work at runtime. The contents of a data object occupy memory space in the program. ABAP statements access these contents by addressing the name of the data object and interpret them according to the data type.. For example, statements can write the contents of data objects in lists or in the database, they can pass them to and receive them from routines, they can change them by assigning new values, and they can compare them in logical expressions.
Each ABAP data object has a set of technical attributes, which are fully defined at all times when an ABAP program is running (field length, number of decimal places, and data type). You declare data objects either statically in the declaration part of an ABAP program (the most important statement for this is DATA), or dynamically at runtime (for example, when you call procedures). As well as fields in the memory area of the program, the program also treats literals like data objects.
A data object is a part of the repository whose content can be addressed and interpreted by the program. All data objects must be declared in the ABAP program and are not persistent, meaning that they only exist while the program is being executed. Before you can process persistent data (such as data from a database table or from a sequential file), you must read it into data objects first. Conversely, if you want to retain the contents of a data object beyond the end of the program, you must save it in a persistent form.
Declaring Data Objects
Apart from the interface parameters of procedures, you declare all of the data objects in an ABAP program or procedure in its declaration part. These declarative statements establish the data type of the object, along with any missing technical attributes. This takes place before the program is actually executed. The technical attributes can then be queried while the program is running.
The interface parameters of procedures are generated as local data objects, but only when the procedure is actually called. You can define the technical attributes of the interface parameters in the procedure itself. If you do not, they adopt the attributes of the parameters from which they receive their values.
ABAP contains the following kinds of data objects:
a. Literals
Literals are not created by declarative statements. Instead, they exist in the program source code. Like all data objects, they have fixed technical attributes (field length, number of decimal places, data type), but no name. They are therefore referred to as unnamed data objects.
b. Named Data Objects
Data objects that have a name that you can use to address the ABAP program are known as named objects. These can be objects of various types, including text symbols, variables and constants.
Text symbols are pointers to texts in the text pool of the ABAP program. When the program starts, the corresponding data objects are generated from the texts stored in the text pool. They can be addressed using the name of the text symbol.
Variables are data objects whose contents can be changed using ABAP statements. You declare variables using the DATA, CLASS-DATA, STATICS, PARAMETERS, SELECT-OPTIONS, and RANGESstatements.
Constants are data objects whose contents cannot be changed. You declare constants using the CONSTANTSstatement.
c. Anonymous Data Objects
Data objects that cannot be addressed using a name are known as anonymous data objects. They are created using the CREATE DATAstatement and can be addressed using reference variables.
d. System-Defined Data Objects
System-defined data objects do not have to be declared explicitly - they are always available at runtime.
e. Interface Work Areas
Interface work areas are special variables that serve as interfaces between programs, screens, and logical databases. You declare interface work areas using the TABLES and NODESstatements.
regards,
sravanthi

Question about performance (entities & data object)

Hello:
I know that this can be, maybe, a silly question, but I've got the doubt
I get a local reference to a entity ( myEntityLocal ) and I'm going to get many values from it.
For example
myEntityLocal.getId();
myEntityLocal getName();
myEntityLocal.getAddr();
etc etc
My question is
Would be better, in performance terms, to fill all fields into a data object myEntityData ) and retrieve them from it ?
I mean
myEntityData = myEntityLocal.getData() // where getData() calls getter methods on myEntityLocal
myEntityData.getId();
myEntityData.getName();
myEntityData.getAddr();
I think the result is the same because is a local reference, but I've got that doubt
Thanks and regards

This will be san=me if you are considering the Local interfaces.
For remote interface(like accessing EJB from Servlets resides in diffferent Apps Server) use the DTO(data Transfer Object) patterns.
Regards
Sushil

Field catalog run time error

When I use Field catalog merge I get an error
i Get a runtime error where it says the internal table passes to field catalog marge has a different fields than I_INTERNAL_TABNAME . What could be the problem.
Thank you

Are you passing the internal table name and field name as the same or different and also check the data type of the fieldcatalog internal table that you are passing to this FM
Check this code for ur reference.
REPORT ZMK_SHIPMENT_ALV
         no standard page heading
         line-size 105
         line-count 50(5)
         message-id zz.
       TABLES                  *
tables : vttk, "Shipment Header
         vttp, " Shipment Item
         lips. " Delivary Item
***TYPE-POOLS                    *
type-pools : slis.
*WORK AREAS                      *
Work area for field catalog table
data : wa_fldcat type slis_fieldcat_alv.
Work area for Events table
data : wa_events type slis_alv_event.
Work area for layout.
data : wa_layout type slis_layout_alv.
*INTERNAL TABLES                  *
Shimpment Details
data : begin of itab occurs 0,
       tknum like vttk-tknum,
       shtyp like vttk-shtyp,
       tpnum like vttp-tpnum,
       vbeln like vttp-vbeln,
       end of itab.
data : begin of itab1 occurs 0,
       vbeln like lips-vbeln,
       posnr like lips-posnr,
       matnr like lips-matnr,
       lfimg like lips-lfimg,
       meins like lips-meins,
       end of itab1.
For field catalog table
data : it_fldcats type slis_t_fieldcat_alv.
For Events table
data : it_event type slis_t_event.
For layout.
data : it_layout type slis_layout_alv.
For field catalog table
data : it_fldcats1 type slis_t_fieldcat_alv.
For Events table
data : it_event1 type slis_t_event.
data : v_repid like sy-repid.
*Data Declaration
data: v_index type sy-index,
      v_vbeln like lips-vbeln.
*SELECT-OPTIONS
selection-screen begin of block b with frame title text-001.
          select-options : s_tknum for vttk-tknum .
selection-screen end of block b.
*INITIALIZATION
initialization.
v_repid = sy-repid.
*START-OF-SELCTION
start-of-selection.
perform populate-data.
sort itab by tknum.
top-of-page.
write : 'Shipment wise Delivary Report'.
end-of-selection.
perform build-fieldcatalog.
perform modify-fieldcatalog.
perform build-events.
perform modify-events.
perform set-layout.
perform set-pfstatus.
perform list-display.
*&      Form populate-data
    Retrives the Shipment data depending on the selection criteria   *
FORM populate-data.
select vttk~tknum
       vttk~shtyp
       vttp~tpnum
       vttp~vbeln
       into table itab
       from vttk
       join vttp
       on vttptknum = vttktknum
       where vttk~tknum in s_tknum.
   if sy-subrc <> 0.
    message e999 with 'NO DATA FOUND'.
    exit.
endif.
ENDFORM.                    " populate-data
*&      Form build-fieldcatalog
      text
--> p1        text
<-- p2        text
form build-fieldcatalog.
call function 'REUSE_ALV_FIELDCATALOG_MERGE'
exporting
    i_program_name               = v_repid
    i_internal_tabname           = 'ITAB'
I_STRUCTURE_NAME             =
I_CLIENT_NEVER_DISPLAY       = 'X'
    i_inclname                   = v_repid
I_BYPASSING_BUFFER           =
I_BUFFER_ACTIVE              =
changing
    ct_fieldcat                  = it_fldcats
exceptions
    inconsistent_interface       = 1
    program_error                = 2
    others                       = 3
if sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
endif.
endform.                    " BUILD-FIELDCATALOG
*&      Form build-events
      text
--> p1        text
<-- p2        text
FORM build-events.
CALL FUNCTION 'REUSE_ALV_EVENTS_GET'
EXPORTING
   I_LIST_TYPE           = 0
IMPORTING
   ET_EVENTS             = it_event
EXCEPTIONS
   LIST_TYPE_WRONG       = 1
   OTHERS                = 2
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM.                    " build-events
*&      Form set-layout
      text
--> p1        text
<-- p2        text
FORM set-layout.
wa_layout-zebra          = 'X'.
wa_layout-colwidth_optimize = 'X'.
wa_layout-no_colhead = space.
wa_layout-no_vline = space.
ENDFORM.                    " set-layout
*&      Form list-display
      text
--> p1        text
<-- p2        text
FORM list-display.
CALL FUNCTION 'REUSE_ALV_LIST_DISPLAY'
EXPORTING
I_INTERFACE_CHECK              = ' '
I_BYPASSING_BUFFER             =
I_BUFFER_ACTIVE                = ' '
   I_CALLBACK_PROGRAM             = v_repid
I_CALLBACK_PF_STATUS_SET       = ' '
   I_CALLBACK_USER_COMMAND        = 'USER_COMMAND'
I_STRUCTURE_NAME               =
   IS_LAYOUT                      = wa_layout
   IT_FIELDCAT                    = it_fldcats
IT_EXCLUDING                   =
IT_SPECIAL_GROUPS              =
IT_SORT                        =
IT_FILTER                      =
IS_SEL_HIDE                    =
I_DEFAULT                      = 'X'
I_SAVE                         = ' '
IS_VARIANT                     =
   IT_EVENTS                      = it_event
IT_EVENT_EXIT                  =
IS_PRINT                       =
IS_REPREP_ID                   =
I_SCREEN_START_COLUMN          = 0
I_SCREEN_START_LINE            = 0
I_SCREEN_END_COLUMN            = 0
I_SCREEN_END_LINE              = 0
IMPORTING
E_EXIT_CAUSED_BY_CALLER        =
ES_EXIT_CAUSED_BY_USER         =
TABLES
    T_OUTTAB                       = itab
EXCEPTIONS
   PROGRAM_ERROR                  = 1
   OTHERS                         = 2
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM.                    " list-display
*&      Form modify-fieldcatalog
      text
--> p1        text
<-- p2        text
FORM modify-fieldcatalog.
loop at it_fldcats into wa_fldcat.
    case wa_fldcat-fieldname.
      when 'TKNUM'.
        wa_fldcat-seltext_l = 'Ship No.'.
        wa_fldcat-col_pos = 1.
        wa_fldcat-ddictxt = 'L'.
        when 'SHTYP'.
        wa_fldcat-seltext_l = 'Ship Type'.
        wa_fldcat-col_pos = 2.
        wa_fldcat-ddictxt = 'L'.
     when 'TPNUM'.
        wa_fldcat-seltext_l = 'Item No.'.
        wa_fldcat-col_pos = 3.
        wa_fldcat-ddictxt = 'L'.
     when 'VBELN'.
        wa_fldcat-seltext_l = 'Delivary No.'.
        wa_fldcat-hotspot = 'X'.
        wa_fldcat-col_pos = 4.
        wa_fldcat-ddictxt = 'L'.
    endcase.
   modify it_fldcats from wa_fldcat.
   endloop.
ENDFORM.                    " modify-fieldcatalog
*&      Form modify-events
      text
--> p1        text
<-- p2        text
form modify-events.
    read table it_event with key name =
slis_ev_top_of_page into wa_events.
   if sy-subrc = 0.
    wa_events-form = 'HEADER-OF-REPORT'.
    modify it_event from wa_events index sy-tabix.
    clear wa_events.
   endif.
   read table it_event with key name =
slis_ev_end_of_page into wa_events.
   if sy-subrc = 0.
    wa_events-form = 'FOOTER-OF-REPORT'.
    modify it_event from wa_events index sy-tabix.
    clear wa_events.
endif.
endform.                    " modify-events
*&      Form HEADER-OF-REPORT
      text
--> p1        text
<-- p2        text
FORM HEADER-OF-REPORT.
write : 'Shipment Wise Delivary Report'.
ENDFORM.                    " HEADER-OF-REPORT
*&      Form FOOTER-OF-REPORT
      text
--> p1        text
<-- p2        text
FORM FOOTER-OF-REPORT.
write : 'End of Report'.
ENDFORM.                    " FOOTER-OF-REPORT
*&      Form USER_COMMAND
      User command for Calling Transaction VT03N, Execute and Refresh
FORM user_command USING    p_ucomm    LIKE sy-ucomm
                         p_selfield TYPE slis_selfield.
V_INDEX = P_SELFIELD-TABINDEX.      " holds the selected table index
CASE p_ucomm.
    WHEN '&IC1'.
     IF p_selfield-fieldname eq 'VBELN'.
      perform secondary_list.
     ENDIF.
ENDCASE.
ENDFORM.                    " USER_COMMAND
*&      Form secondary_list
      text
--> p1        text
<-- p2        text
FORM secondary_list.
perform get_data1.
perform build-fieldcatalog1.
perform modify-fieldcatalog1.
perform build-events1.
perform modify-events1.
perform set-layout.
perform set-pfstatus.
perform list-display1.
ENDFORM.                    " secondary_list
*&      Form build-fieldcatalog1
      text
--> p1        text
<-- p2        text
FORM build-fieldcatalog1.
call function 'REUSE_ALV_FIELDCATALOG_MERGE'
exporting
    i_program_name               = v_repid
    i_internal_tabname           = 'ITAB1'
I_STRUCTURE_NAME             =
I_CLIENT_NEVER_DISPLAY       = 'X'
    i_inclname                   = v_repid
I_BYPASSING_BUFFER           =
I_BUFFER_ACTIVE              =
changing
    ct_fieldcat                  = it_fldcats1
exceptions
    inconsistent_interface       = 1
    program_error                = 2
    others                       = 3
if sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
endif.
ENDFORM.                    " build-fieldcatalog1
*&      Form modify-fieldcatalog1
      text
--> p1        text
<-- p2        text
FORM modify-fieldcatalog1.
loop at it_fldcats into wa_fldcat.
    case wa_fldcat-fieldname.
      when 'VBELN'.
        wa_fldcat-seltext_l = 'Delivary No.'.
        wa_fldcat-col_pos = 1.
        wa_fldcat-ddictxt = 'L'.
        when 'POSNR'.
        wa_fldcat-seltext_l = 'Item No'.
        wa_fldcat-col_pos = 2.
        wa_fldcat-ddictxt = 'L'.
     when 'MATNR'.
        wa_fldcat-seltext_l = 'Material'.
        wa_fldcat-col_pos = 3.
        wa_fldcat-ddictxt = 'L'.
     when 'LFIMG'.
        wa_fldcat-seltext_l = 'Quantity'.
        wa_fldcat-col_pos = 4.
        wa_fldcat-ddictxt = 'L'.
     when 'MEINS'.
        wa_fldcat-seltext_l = 'Unit of Measure'.
        wa_fldcat-col_pos = 5.
        wa_fldcat-ddictxt = 'L'.
    endcase.
   modify it_fldcats from wa_fldcat.
   endloop.
ENDFORM.                    " modify-fieldcatalog1
*&      Form build-events1
      text
--> p1        text
<-- p2        text
FORM build-events1.
CALL FUNCTION 'REUSE_ALV_EVENTS_GET'
EXPORTING
   I_LIST_TYPE           = 0
IMPORTING
   ET_EVENTS             = it_event1
EXCEPTIONS
   LIST_TYPE_WRONG       = 1
   OTHERS                = 2
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM.                    " build-events1
*&      Form modify-events1
      text
--> p1        text
<-- p2        text
FORM modify-events1.
read table it_event1 with key name =
slis_ev_top_of_page into wa_events.
   if sy-subrc = 0.
    wa_events-form = 'HEADER_OF_REPORT_2'.
    modify it_event1 from wa_events index sy-tabix.
    clear wa_events.
   endif.
ENDFORM.                    " modify-events1
*&      Form list-display1
      text
--> p1        text
<-- p2        text
FORM list-display1.
CALL FUNCTION 'REUSE_ALV_LIST_DISPLAY'
EXPORTING
I_INTERFACE_CHECK              = ' '
I_BYPASSING_BUFFER             =
I_BUFFER_ACTIVE                = ' '
   I_CALLBACK_PROGRAM             = v_repid
I_CALLBACK_PF_STATUS_SET       = ' '
I_CALLBACK_USER_COMMAND        = 'USER_COMMAND'
I_STRUCTURE_NAME               =
   IS_LAYOUT                      = wa_layout
   IT_FIELDCAT                    = it_fldcats1
IT_EXCLUDING                   =
IT_SPECIAL_GROUPS              =
IT_SORT                        =
IT_FILTER                      =
IS_SEL_HIDE                    =
I_DEFAULT                      = 'X'
I_SAVE                         = ' '
IS_VARIANT                     =
   IT_EVENTS                      = it_event1
IT_EVENT_EXIT                  =
IS_PRINT                       =
IS_REPREP_ID                   =
I_SCREEN_START_COLUMN          = 0
I_SCREEN_START_LINE            = 0
I_SCREEN_END_COLUMN            = 0
I_SCREEN_END_LINE              = 0
IMPORTING
E_EXIT_CAUSED_BY_CALLER        =
ES_EXIT_CAUSED_BY_USER         =
TABLES
    T_OUTTAB                       = itab1
EXCEPTIONS
   PROGRAM_ERROR                  = 1
   OTHERS                         = 2
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM.                    " list-display1
*&      Form get_data1
      text
--> p1        text
<-- p2        text
FORM get_data1.
READ TABLE itab INDEX V_INDEX.
v_vbeln = itab-vbeln.
select vbeln
        posnr
        matnr
        lfimg
        meins
        from lips
        into table itab1
        where vbeln eq v_vbeln.
ENDFORM.                    " get_data1
*&      Form header_of_report_2
      text
--> p1        text
<-- p2        text
FORM header_of_report_2.
write: 'Delivary item list'.
ENDFORM.                    " header_of_report_2
*-- callling a transaction code by passing the initial screen value.
*&      Form USER_COMMAND
form user_command using    p_ucomm    like sy-ucomm
                         p_selfield type slis_selfield.
data : l_index like sy-index,
         l_refbn like cooi-refbn.
l_index = p_selfield-tabindex.       " holds the selected table index
clear l_refbn.
case p_ucomm.
    when '&IC1'.
      clear l_refbn.
      read table it_outtab index l_index.
      if sy-subrc eq 0.
        l_refbn = it_outtab-refbn.
        if not l_refbn is initial.
          set parameter id 'BES' field l_refbn.
          call transaction 'ME23' and skip first screen.
        endif.
      else.
        message e999 with text-014.
      endif.
endcase.
endif.

Field Catalog from data object..

Similar Messages

Maybe you are looking for