WHAT IS DATE BANDLING WHAT IS FIELD CATLOG IN ALV

WHAT IS DATE BANDLING WHAT IS FIELD CATLOG IN ALV
Explain clearly

i guess u mean date "Handling"
What abt date handling?

Similar Messages

What is field catlog...

Hi all,
 anybody explain field catelog.
 how to use in reports,what is the use of field catlog.
regards.
krish

Maintaining the Field Catalog
Storing aspect fields in the field catalog
The characteristics and basic key figures are stored in a field catalog when they are saved. This catalog can be seen as a EC-EIS/EC-BP-specific supplement to the ABAP Dictionary. Report-relevant attributes for the fields are also stored in the field catalog. The field catalog is aspect-independent. Once a field is contained in the field catalog, it may be copied to other aspects but may no longer be changed. This guarantees a uniform, cross-area use of evaluation groups and key figures.
You can create field groups to structure the fields in the field catalog. A Field Group is a user-defined grouping of characteristics and basic key figures.
Reorganization of the field catalog
The field catalog and ABAP Dictionary information on the aspect data structures must be consistent with one another - each data structure field must also exist in the field catalog. If this is no longer the case, you should reorganize the field catalog in order to restore the consistency. When you do this, the system reads the aspect structure from the ABAP Dictionary and reconciles it with the field catalog.
Deleting fields from the field catalog
Characteristics and basic key figures, that are no longer used in any aspect, can be deleted from the field catalog. Any relevant master data, comments, generated ABAP Dictionary objects will be deleted at the same time.
You can find more information on the field catalog in Customizing.
We can implement Field catalog by calling Function modules or classes..
See the sample code
REPORT ALV_FM.
TYPE-POOLS: SLIS.
DATA:
BEGIN OF FS_SPFLI,
 CARRID TYPE SPFLI-CARRID,
 CONNID TYPE SPFLI-CONNID,
 COUNTRYFR TYPE SPFLI-COUNTRYFR,
 CITYFROM TYPE SPFLI-CITYFROM,
 AIRPFROM TYPE SPFLI-AIRPFROM,
 COUNTRYTO TYPE SPFLI-COUNTRYTO,
 CITYTO TYPE SPFLI-CITYTO,
 AIRPTO TYPE SPFLI-AIRPTO,
 FLTIME TYPE SPFLI-FLTIME,
 DEPTIME TYPE SPFLI-DEPTIME,
 ARRTIME TYPE SPFLI-ARRTIME,
 DISTANCE TYPE SPFLI-DISTANCE,
 DISTID TYPE SPFLI-DISTID,
 FLTYPE TYPE SPFLI-FLTYPE,
 PERIOD TYPE SPFLI-PERIOD,
END OF FS_SPFLI.
DATA:
T_SPFLI LIKE STANDARD TABLE OF FS_SPFLI.
SELECT * FROM SPFLI
INTO CORRESPONDING FIELDS OF TABLE T_SPFLI.
DATA: T_FIELDCAT TYPE SLIS_T_FIELDCAT_ALV,
 FS_FIELDCAT LIKE LINE OF T_FIELDCAT.
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
EXPORTING
I_INTERFACE_CHECK = ' '
I_BYPASSING_BUFFER = ' '
I_BUFFER_ACTIVE = ' '
I_CALLBACK_PROGRAM = ' '
I_CALLBACK_PF_STATUS_SET = ' '
I_CALLBACK_USER_COMMAND = ' '
I_CALLBACK_TOP_OF_PAGE = ' '
I_CALLBACK_HTML_TOP_OF_PAGE = ' '
I_CALLBACK_HTML_END_OF_LIST = ' '
 I_STRUCTURE_NAME = 'SPFLI'
I_BACKGROUND_ID = ' '
I_GRID_TITLE =
I_GRID_SETTINGS =
IS_LAYOUT =
IT_FIELDCAT = T_FIELDCAT
IT_EXCLUDING =
IT_SPECIAL_GROUPS =
IT_SORT =
IT_FILTER =
IS_SEL_HIDE =
I_DEFAULT = 'X'
I_SAVE = ' '
IS_VARIANT =
IT_EVENTS =
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
I_HTML_HEIGHT_TOP = 0
I_HTML_HEIGHT_END = 0
IT_ALV_GRAPHICS =
IT_HYPERLINK =
IT_ADD_FIELDCAT =
IT_EXCEPT_QINFO =
IR_SALV_FULLSCREEN_ADAPTER =
IMPORTING
E_EXIT_CAUSED_BY_CALLER =
ES_EXIT_CAUSED_BY_USER =
TABLES
 T_OUTTAB = T_SPFLI
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.
Regards,
Pavan P.

DSO - What key fields and data fields in dso

Hi experts,
I need to create a dso in between the cube and 2 data sources(2lis_11_vaitm, 2lis_12_vcscl) to stage the data. My question is: what key fields and data fields to choose for the dso? is there a standard dso to copy? please explain in detail the model to set up, whether to connect both the ds's to dso and then to cube or one ds to dso and the other to the cube. more details will help.

Check this for standard DSO:
http://help.sap.com/saphelp_nw04/helpdata/en/43/fcdc387f34384f94c3227baf3837a8/content.htm
Thanks...
Shambhu

What does Field Label tab does in Data element properties

Hi,
Please explain What does Field Label tab does in Data element properties. It has following interface:
Length Field Label
Short
Medium
Long
Heading
Thanks!
~Sid
Max Points for precise answers

Hi
Short Field Label
Definition
One of the following:
- Short field label
- Medium field label
- Long field label
Can be assigned as prefixed text to a screen field referring to the ABAP Dictonary. The text is displayed on the screen in the logon language of the user (if the text was translated into this language).
A heading can be defined to output the field values in lists. This heading is automatically included in the list header row, in the logon language.
Medium Field Label
Definition
One of the following:
- Short field label
- Medium field label
- Long field label
Can be assigned as prefixed text to a screen field referring to the ABAP Dictonary. The text is displayed on the screen in the logon language of the user (if the text was translated into this language).
A heading can be defined to output the field values in lists. This heading is automatically included in the list header row, in the logon language.
Long Field Label
Definition
One of the following:
- Short field label
- Medium field label
- Long field label
Can be assigned as prefixed text to a screen field referring to the ABAP Dictonary. The text is displayed on the screen in the logon language of the user (if the text was translated into this language).
A heading can be defined to output the field values in lists. This heading is automatically included in the list header row, in the logon language.
Heading
Definition
One of the following:
- Short field label
- Medium field label
- Long field label
Can be assigned as prefixed text to a screen field referring to the ABAP Dictonary. The text is displayed on the screen in the logon language of the user (if the text was translated into this language).
A heading can be defined to output the field values in lists. This heading is automatically included in the list header row, in the logon language.
Reward If Usefull

What table/fields show if a PO Item has a G/R Expected?

Hi experts,
I am coding a program in SRM, but not sure I'll find these answers there, so I'm likely going to do a RFC to ECC and get the values, but need to know how to identify.
In ECC:
(1) What table/field shows if a PO item has a G/R expected?
(2) Where can I find if the PO item has any open receipts?
(3) Where can I find the amount remaining to be invoiced on a PO item?
Thank you very much!
Mark

Hi,
I think EKPO-WEPOS = 'X' mentions that it is expecting G/R..Please see the data element WEPOS documentation for details...
1) The above is the answer
For 2) and 3) You can check the table EKBE...in that you can use the field VGABE to different between invoice receipt and goods receipt..
1 Goods Receipt
2 Invoice Receipt
Thanks
Naren

What is Field Label ? and where do we use it .

What is Field Label ? and where do we use it .

Hi,
You can assign text information to a data element with the field labels.
The field labels are used to display a screen field. You can copy structure components and table fields from the ABAP Dictionary to the input template when you define a screen in the Screen Painter (Get from Dict. function). You can also assign a field a field label that is derived from the data element of the field.
The text of the field label can be translated centrally with the translation tools. The text is then displayed in the input template in the users logon language.
Short, Medium and Long Field Labels
Keywords of different lengths for identifying screen fields. Since the space available for such texts depends on the input template, you can define the text information in three different lengths.
A maximum length must be assigned for each field label. It is the upper limit for the lengths of all translations of the given text. The maximum length of the field label therefore should be somewhat longer than the given text in the original language.
Headers
This text is used as a column header when you output the contents of fields as a list in the Data Browser. It can also be assigned to a field in the Screen Painter.
A maximum length must also be assigned for the header. It is the upper limit for the lengths of all translations of the header. Choose the maximum length of the header to be somewhat longer than the given text in the original language. Also note that the header is often displayed above the corresponding column when preparing list output. The length of the header therefore should not exceed the length of the data element.
Short Field Label
Definition
One of the following:
- Short field label
- Medium field label
- Long field label
Can be assigned as prefixed text to a screen field referring to the ABAP Dictonary. The text is displayed on the screen in the logon language of the user (if the text was translated into this language).
A heading can be defined to output the field values in lists. This heading is automatically included in the list header row, in the logon language.
Medium Field Label
Definition
One of the following:
- Short field label
- Medium field label
- Long field label
Can be assigned as prefixed text to a screen field referring to the ABAP Dictonary. The text is displayed on the screen in the logon language of the user (if the text was translated into this language).
A heading can be defined to output the field values in lists. This heading is automatically included in the list header row, in the logon language.
Long Field Label
Definition
One of the following:
- Short field label
- Medium field label
- Long field label
Can be assigned as prefixed text to a screen field referring to the ABAP Dictonary. The text is displayed on the screen in the logon language of the user (if the text was translated into this language).
A heading can be defined to output the field values in lists. This heading is automatically included in the list header row, in the logon language.
Heading
Definition
One of the following:
- Short field label
- Medium field label
- Long field label
Can be assigned as prefixed text to a screen field referring to the ABAP Dictonary. The text is displayed on the screen in the logon language of the user (if the text was translated into this language).
A heading can be defined to output the field values in lists. This heading is automatically included in the list header row, in the logon language.
Thanks,
Reward If Helpful.

What are field symbols and field groups.? Have you used "component idx of s

What are field symbols and field groups.? Have you used "component idx of structure"

Field Symbols and field groups
Field Groups / Extracts
http://help.sap.com/saphelp_46c/helpdata/EN/9f/db9ede35c111d1829f0000e829fbfe/frameset.htm
Field Symbols
http://help.sap.com/saphelp_46c/helpdata/EN/fc/eb387a358411d1829f0000e829fbfe/frameset.htm
Field symbols: are placeholders or symbolic names for other fields. They do not physically reserve space for a field, but point to its contents. A field symbol cam point to any data object. The data object to which a field symbol points is assigned to it after it has been declared in the program.
Whenever you address a field symbol in a program, you are addressing the field that is assigned to the field symbol. After successful assignment, there is no difference in ABAP whether you reference the field symbol or the field itself. You must assign a field to each field symbol before you can address the latter in programs.
Field Groups:
A field group is a user-defined grouping of characteristics and basic key figures from the EC-EIS or EC-BP field catalog.
Use
The field catalog contains the fields that are used in the aspects. As the number of fields grows, the field catalog becomes very large and unclear. To simplify maintenance of the aspects, you can group fields in a field group. You can group the fields as you wish, for example, by subject area or responsibility area. A field may be included in several field groups.
When maintaining the data structure of an aspect, you can select the field group that contains the relevant characteristics and basic key figures. This way you limit the number of fields offered.
A field group combines several existing fields together under one name
like
FIELD-GROUPS: fg.
then you can use one insert statement to insert values in fields of field-group.
INSERT f1 f2 ... INTO fg.
Field symbols
If u have experience with 'C', then understand this to be similar to a pointer.
It is used to reference another variable dynamically. So this field symbol will simply point to some other variable. and this pointer can be changed at runtime.
FIELD-SYMBOLS <FS>.
DATA FIELD VALUE 'X'.
ASSIGN FIELD TO <FS>.
WRITE <FS>.
Field symbols: are placeholders or symbolic names for other fields. They do not physically reserve space for a field, but point to its contents. A field symbol cam point to any data object. The data object to which a field symbol points is assigned to it after it has been declared in the program.
Whenever you address a field symbol in a program, you are addressing the field that is assigned to the field symbol. After successful assignment, there is no difference in ABAP whether you reference the field symbol or the field itself. You must assign a field to each field symbol before you can address the latter in programs.
Field Groups:
A field group is a user-defined grouping of characteristics and basic key figures from the EC-EIS or EC-BP field catalog.
Use
The field catalog contains the fields that are used in the aspects. As the number of fields grows, the field catalog becomes very large and unclear. To simplify maintenance of the aspects, you can group fields in a field group. You can group the fields as you wish, for example, by subject area or responsibility area. A field may be included in several field groups.
When maintaining the data structure of an aspect, you can select the field group that contains the relevant characteristics and basic key figures. This way you limit the number of fields offered.
Field Groups / Extracts
http://help.sap.com/saphelp_46c/helpdata/EN/9f/db9ede35c111d1829f0000e829fbfe/frameset.htm
Field Symbols
http://help.sap.com/saphelp_46c/helpdata/EN/fc/eb387a358411d1829f0000e829fbfe/frameset.htm

What is the procedure to create field catalog in alv

what is the procedure to create field catalog in alv?
with a example please.

Hi,
U can use the function module REUSE_ALV_FIELDCAT_MERGE...If we use a structure that is exactly
identical to the datadictionary other wise u hav to hard code as in the following example.
**ALV EXAMPLE
*& Report ZJE_ALV_EXAMPLE
REPORT zje_alv_example.
TYPE-POOLS: slis.
*type declaration for values from ekko
TYPES: BEGIN OF i_ekko,
 ebeln LIKE ekko-ebeln,
 aedat LIKE ekko-aedat,
 bukrs LIKE ekko-bukrs,
 bsart LIKE ekko-bsart,
 lifnr LIKE ekko-lifnr,
 END OF i_ekko.
*type declaration for values from ekpo
TYPES: BEGIN OF i_ekpo,
 ebeln LIKE ekpo-ebeln,
 ebelp LIKE ekpo-ebelp,
 matnr LIKE ekpo-matnr,
 menge LIKE ekpo-menge,
 meins LIKE ekpo-meins,
 netpr LIKE ekpo-netpr,
 END OF i_ekpo.
DATA: it_ekko TYPE STANDARD TABLE OF i_ekko INITIAL SIZE 0,
 wa_ekko TYPE i_ekko.
DATA: it_ekpo TYPE STANDARD TABLE OF i_ekpo INITIAL SIZE 0,
 wa_ekpo TYPE i_ekpo .
*variable for Report ID
DATA: v_repid LIKE sy-repid .
*declaration for fieldcatalog
DATA: i_fieldcat TYPE slis_t_fieldcat_alv,
 wa_fieldcat TYPE slis_fieldcat_alv.
DATA: it_listheader TYPE slis_t_listheader.
declaration for events table where user comand or set PF status will
be defined
DATA: v_events TYPE slis_t_event,
 wa_event TYPE slis_alv_event.
declartion for layout
DATA: alv_layout TYPE slis_layout_alv.
declaration for variant(type of display we want)
DATA: i_variant TYPE disvariant,
 i_variant1 TYPE disvariant,
 i_save(1) TYPE c.
*PARAMETERS : p_var TYPE disvariant-variant.
*Title displayed when the alv list is displayed
DATA: i_title_ekko TYPE lvc_title VALUE 'FIRST LIST DISPLAYED'.
DATA: i_title_ekpo TYPE lvc_title VALUE 'SECONDRY LIST DISPLAYED'.
INITIALIZATION.
v_repid = sy-repid.
PERFORM build_fieldcatlog.
PERFORM event_call.
PERFORM populate_event.
START-OF-SELECTION.
PERFORM data_retrieval.
PERFORM build_listheader USING it_listheader.
PERFORM display_alv_report.
*& Form BUILD_FIELDCATLOG
Fieldcatalog has all the field details from ekko
FORM build_fieldcatlog.
wa_fieldcat-tabname = 'IT_EKKO'.
wa_fieldcat-fieldname = 'EBELN'.
wa_fieldcat-seltext_m = 'PO NO.'.
APPEND wa_fieldcat TO i_fieldcat.
CLEAR wa_fieldcat.
wa_fieldcat-tabname = 'IT_EKKO'.
wa_fieldcat-fieldname = 'AEDAT'.
wa_fieldcat-seltext_m = 'DATE.'.
APPEND wa_fieldcat TO i_fieldcat.
CLEAR wa_fieldcat.
wa_fieldcat-tabname = 'IT_EKKO'.
wa_fieldcat-fieldname = 'BUKRS'.
wa_fieldcat-seltext_m = 'COMPANY CODE'.
APPEND wa_fieldcat TO i_fieldcat.
CLEAR wa_fieldcat.
wa_fieldcat-tabname = 'IT_EKKO'.
wa_fieldcat-fieldname = 'BUKRS'.
wa_fieldcat-seltext_m = 'DOCMENT TYPE'.
APPEND wa_fieldcat TO i_fieldcat.
CLEAR wa_fieldcat.
wa_fieldcat-tabname = 'IT_EKKO'.
wa_fieldcat-fieldname = 'LIFNR'.
wa_fieldcat-no_out = 'X'.
wa_fieldcat-seltext_m = 'VENDOR CODE'.
APPEND wa_fieldcat TO i_fieldcat.
CLEAR wa_fieldcat.
ENDFORM. "BUILD_FIELDCATLOG
*& Form EVENT_CALL
we get all events - TOP OF PAGE or USER COMMAND in table v_events
FORM event_call.
CALL FUNCTION 'REUSE_ALV_EVENTS_GET'
EXPORTING
i_list_type = 0
IMPORTING
et_events = v_events
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. "EVENT_CALL
*& Form POPULATE_EVENT
Events populated for TOP OF PAGE & USER COMAND
FORM populate_event.
READ TABLE v_events INTO wa_event WITH KEY name = 'TOP_OF_PAGE'.
IF sy-subrc EQ 0.
 wa_event-form = 'TOP_OF_PAGE'.
 MODIFY v_events FROM wa_event TRANSPORTING form WHERE name =
 wa_event-form.
ENDIF.
READ TABLE v_events INTO wa_event WITH KEY name = 'USER_COMMAND'.
IF sy-subrc EQ 0.
 wa_event-form = 'USER_COMMAND'.
 MODIFY v_events FROM wa_event TRANSPORTING form WHERE name =
 wa_event-name.
ENDIF.
ENDFORM. "POPULATE_EVENT
*& Form data_retrieval
retreiving values from the database table ekko
FORM data_retrieval.
SELECT ebeln aedat bukrs bsart lifnr
 FROM ekko
 INTO TABLE it_ekko.
ENDFORM. "data_retrieval
*& Form bUild_listheader
text
-->I_LISTHEADEtext
FORM build_listheader USING i_listheader TYPE slis_t_listheader.
DATA hline TYPE slis_listheader.
hline-info = 'this is my first alv pgm'.
hline-typ = 'H'.
ENDFORM. "build_listheader
*& Form display_alv_report
text
FORM display_alv_report.
v_repid = sy-repid.
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
EXPORTING
i_callback_program = v_repid
I_CALLBACK_PF_STATUS_SET = ' '
i_callback_user_command = 'USER_COMMAND'
i_callback_top_of_page = 'TOP_OF_PAGE'
i_grid_title = i_title_ekko
I_GRID_SETTINGS =
IS_LAYOUT = ALV_LAYOUT
it_fieldcat = i_fieldcat[]
IT_EXCLUDING =
IT_SPECIAL_GROUPS =
IT_SORT =
IT_FILTER =
IS_SEL_HIDE =
i_default = 'ZLAY1'
i_save = 'A'
is_variant = i_variant
it_events = v_events
TABLES
t_outtab = it_ekko
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. "display_alv_report
*& Form TOP_OF_PAGE
text
FORM top_of_page.
CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
EXPORTING
it_list_commentary = it_listheader
i_logo =
I_END_OF_LIST_GRID =
ENDFORM. "TOP_OF_PAGE
*& Form USER_COMMAND
text
-->R_UCOMM text
-->, text
-->RS_SLEFIELDtext
FORM user_command USING r_ucomm LIKE sy-ucomm
rs_selfield TYPE slis_selfield.
CASE r_ucomm.
 WHEN '&IC1'.
 READ TABLE it_ekko INTO wa_ekko INDEX rs_selfield-tabindex.
 PERFORM build_fieldcatlog_ekpo.
 PERFORM event_call_ekpo.
 PERFORM populate_event_ekpo.
 PERFORM data_retrieval_ekpo.
 PERFORM build_listheader_ekpo USING it_listheader.
 PERFORM display_alv_ekpo.
ENDCASE.
ENDFORM. "user_command
*& Form BUILD_FIELDCATLOG_EKPO
text
FORM build_fieldcatlog_ekpo.
wa_fieldcat-tabname = 'IT_EKPO'.
wa_fieldcat-fieldname = 'EBELN'.
wa_fieldcat-seltext_m = 'PO NO.'.
APPEND wa_fieldcat TO i_fieldcat.
CLEAR wa_fieldcat.
wa_fieldcat-tabname = 'IT_EKPO'.
wa_fieldcat-fieldname = 'EBELP'.
wa_fieldcat-seltext_m = 'LINE NO'.
APPEND wa_fieldcat TO i_fieldcat.
CLEAR wa_fieldcat.
wa_fieldcat-tabname = 'I_EKPO'.
wa_fieldcat-fieldname = 'MATNR'.
wa_fieldcat-seltext_m = 'MATERIAL NO.'.
APPEND wa_fieldcat TO i_fieldcat.
CLEAR wa_fieldcat.
wa_fieldcat-tabname = 'I_EKPO'.
wa_fieldcat-fieldname = 'MENGE'.
wa_fieldcat-seltext_m = 'QUANTITY'.
APPEND wa_fieldcat TO i_fieldcat.
CLEAR wa_fieldcat.
wa_fieldcat-tabname = 'I_EKPO'.
wa_fieldcat-fieldname = 'MEINS'.
wa_fieldcat-seltext_m = 'UOM'.
APPEND wa_fieldcat TO i_fieldcat.
CLEAR wa_fieldcat.
wa_fieldcat-tabname = 'I_EKPO'.
wa_fieldcat-fieldname = 'NETPR'.
wa_fieldcat-seltext_m = 'PRICE'.
APPEND wa_fieldcat TO i_fieldcat.
CLEAR wa_fieldcat.
ENDFORM. "BUILD_FIELDCATLOG_EKPO
*& Form event_call_ekpo
we get all events - TOP OF PAGE or USER COMMAND in table v_events
FORM event_call_ekpo.
CALL FUNCTION 'REUSE_ALV_EVENTS_GET'
EXPORTING
i_list_type = 0
IMPORTING
et_events = v_events
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. "event_call_ekpo
*& Form POPULATE_EVENT
Events populated for TOP OF PAGE & USER COMAND
FORM populate_event_ekpo.
READ TABLE v_events INTO wa_event WITH KEY name = 'TOP_OF_PAGE'.
IF sy-subrc EQ 0.
 wa_event-form = 'TOP_OF_PAGE'.
 MODIFY v_events FROM wa_event TRANSPORTING form WHERE name =
 wa_event-form.
ENDIF.
ENDFORM. "POPULATE_EVENT
*& Form TOP_OF_PAGE
text
FORM f_top_of_page.
CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
EXPORTING
it_list_commentary = it_listheader
i_logo =
I_END_OF_LIST_GRID =
ENDFORM. "TOP_OF_PAGE
*& Form USER_COMMAND
text
-->R_UCOMM text
-->, text
-->RS_SLEFIELDtext
*retreiving values from the database table ekko
FORM data_retrieval_ekpo.
SELECT ebeln ebelp matnr menge meins netpr
 FROM ekpo
 INTO TABLE it_ekpo.
ENDFORM. "DATA_RETRIEVAL_EKPO
*& Form BUILD_LISTHEADER_EKPO
 text
 -->I_LISTHEADER text
FORM build_listheader_ekpo USING i_listheader TYPE slis_t_listheader.
DATA: hline1 TYPE slis_listheader.
hline1-typ = 'H'.
hline1-info = 'CHECKING PGM'.
ENDFORM. "BUILD_LISTHEADER_EKPO
*& Form DISPLAY_ALV_EKPO
 text
FORM display_alv_ekpo.
CALL FUNCTION 'REUSE_ALV_GRID_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 = 'F_USER_COMMAND'
i_callback_top_of_page = 'TOP_OF_PAGE'
I_CALLBACK_HTML_TOP_OF_PAGE = ' '
I_CALLBACK_HTML_END_OF_LIST = ' '
I_STRUCTURE_NAME =
I_BACKGROUND_ID = ' '
i_grid_title = i_title_ekpo
I_GRID_SETTINGS =
IS_LAYOUT =
it_fieldcat = i_fieldcat[]
IT_EXCLUDING =
IT_SPECIAL_GROUPS =
IT_SORT =
IT_FILTER =
IS_SEL_HIDE =
I_DEFAULT =
i_save = 'A'
IS_VARIANT =
it_events = v_events
TABLES
t_outtab = it_ekpo
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. "DISPLAY_ALV_EKPO
Reward if Helpful

What is field symbols?

Hi all,
Can anyone explains what is Fiels symbol and significance of that with examples?
Thanks
Shiva

HI Shiva
Field symbols are placeholders or symbolic names for other fields. They do not physically reserve space for a field, but point to its contents. A field symbol cam point to any data object. The data object to which a field symbol points is assigned to it after it has been declared in the program.
Whenever you address a field symbol in a program, you are addressing the field that is assigned to the field symbol. After successful assignment, there is no difference in ABAP whether you reference the field symbol or the field itself. You must assign a field to each field symbol before you can address the latter in programs.
Field symbols are similar to dereferenced pointers in C (that is, pointers to which the content operator * is applied). However, the only real equivalent of pointers in ABAP, that is, variables that contain a memory address (reference) and that can be used without the contents operator, are reference variables in ABAP Objects. (For more information, see Data References).
All operations programmed with field symbols are applied to the field assigned to it. For example, a MOVE statement between two field symbols moves the contents of the field assigned to the first field symbol to the field assigned to the second field symbol. The field symbols themselves point to the same fields after the MOVE statement as they did before.
You can create field symbols either without or with type specifications. If you do not specify a type, the field symbol inherits all of the technical attributes of the field assigned to it. If you do specify a type, the system checks the compatibility of the field symbol and the field you are assigning to it during the ASSIGN statement.
Field symbols provide greater flexibility when you address data objects:
If you want to process sections of fields, you can specify the offset and length of the field dynamically.
You can assign one field symbol to another, which allows you to address parts of fields.
Assignments to field symbols may extend beyond field boundaries. This allows you to address regular sequences of fields in memory efficiently.
You can also force a field symbol to take different technical attributes from those of the field assigned to it.
The flexibility of field symbols provides elegant solutions to certain problems. On the other hand, it does mean that errors can easily occur. Since fields are not assigned to field symbols until runtime, the effectiveness of syntax and security checks is very limited for operations involving field symbols. This can lead to runtime errors or incorrect data assignments.
While runtime errors indicate an obvious problem, incorrect data assignments are dangerous because they can be very difficult to detect. For this reason, you should only use field symbols if you cannot achieve the same result using other ABAP statements.
For example, you may want to process part of a string where the offset and length depend on the contents of the field. You could use field symbols in this case. However, since the MOVE statement also supports variable offset and length specifications, you should use it instead. The MOVE statement (with your own auxiliary variables if required) is much safer than using field symbols, since it cannot address memory beyond the boundary of a field. However, field symbols may improve
To declare a field symbol, use the statement
FIELD-SYMBOLS <FS> [<type>|STRUCTURE <s> DEFAULT <wa>].
For field symbols, the angle brackets are part of the syntax. They identify field symbols in the program code.
If you do not specify any additions, the field symbol <FS> can have data objects of any type assigned to it. When you assign a data object, the field symbol inherits its technical attributes. The data type of the assigned data object becomes the actual data type of the field symbol.
Note: it is possible to assign reference variables and structured data objects to untyped field symbols. However, the static field symbol is only a pointer to the field in memory, and does not have the complex type attributes of a reference or structured field until runtime. You can only use the field symbol to address the whole field (for example, in a MOVE statement). Specific statements such as CREATE OBJECT <FS> or LOOP AT <FS> are not possible.
Typing Field Symbols
The <type> addition allows you to specify the type of a field symbol. When you assign a data object to a field symbol, the system checks whether the type of the data object you are trying to assign is compatible with that of the field symbol. If the types are not compatible or convertible, the system reacts with a syntax or runtime error. If however, you want to assign the type of the field symbol to the data object by means of casting, you must do so explicitly using the ASSIGN statement. The system then treats the assigned data object as if it had the same type as the field symbol.
You specify the type of a field symbol using the same semantics as for formal parameters in procedures. For <type> you can enter either TYPE <t> or LIKE <f>. You can specify the type either generically or in full. If you specify a generic type, the type of the field symbol is either partially specified or not specified at all. Any attributes that are not specified are inherited from the corresponding data object in the ASSIGN statement. If you specify the type fully, all of the technical attributes of the field symbol are determined when you define it. You can then only assign data objects to it that have exactly the same data type.
You should always specify a type for each field symbol. If you cannot avoid defining a generic field symbol, make this clear by using an appropriate generic type declaration.
Generic Type Specification
The following types allow you more freedom when using actual parameters. The data object only needs to have the selection of attributes specified.
Typing
Check for data object
No type specification
TYPE ANY
All types of data object are accepted. The field symbol adopts all of the attributes of the data object.
TYPE C, N, P, or X
Only data objects with type C, N, P, or X are accepted. The field symbol adopts the field length and DECIMALS specification (type P) of the data object.
TYPE TABLE
The system checks whether the data object is a standard internal table. This is a shortened form of TYPE STANDARD TABLE (see below).
TYPE ANY TABLE
The system checks whether the data object is an internal table. The field symbol inherits all of the attributes (line type, table type, key) from the data object.
TYPE INDEX TABLE
The system checks whether the data object is an index table (standard or sorted table). The field symbol inherits all of the attributes (line type, table type, key) from the data object.
TYPE STANDARD TABLE
The system checks whether the data object is a standard internal table. The field symbol inherits all of the remaining attributes (line type, key) from the data object.
TYPE SORTED TABLE
The system checks whether the actual parameter is a sorted internal table. The field symbol inherits all of the remaining attributes (line type, key) from the data object.
TYPE HASHED TABLE
The system checks whether the actual parameter is a hashed internal table. The field symbol inherits all of the remaining attributes (line type, key) from the data object.
If you specify a type generically, remember that the attributes inherited by the field symbol from the program are not statically recognizable in the program. You can, at most, address them dynamically.
TYPES: BEGIN OF line,
 col1 TYPE c,
 col2 TYPE c,
 END OF line.
DATA: wa TYPE line,
 itab TYPE HASHED TABLE OF line WITH UNIQUE KEY col1,
 key(4) TYPE c VALUE 'COL1'.
FIELD-SYMBOLS <fs> TYPE ANY TABLE.
ASSIGN itab TO <fs>.
READ TABLE <fs> WITH TABLE KEY (key) = 'X' INTO wa.
The internal table ITAB is assigned to the generic field symbol <FS>, after which it is possible to address the table key of the field symbol dynamically. However, the static address
READ TABLE <fs> WITH TABLE KEY col1 = 'X' INTO wa.
is not possible syntactically, since the field symbol does not adopt the key of table ITAB until runtime. In the program, the type specification ANY TABLE only indicates that <FS> is a table. If the type had been ANY (or no type had been specified at all), even the specific internal table statement READ TABLE <FS> would not have been possible.
If you adopt a structured type generically (a structure, or a table with structured line type), the individual components cannot be addressed in the program either statically or dynamically. In this case, you would have to work with further field symbols and the method of assigning structures component by component.
Specifying the Type Fully
When you use the following types, the technical attributes of the field symbols are fully specified. The technical attributes of the data objects must correspond to those of the field symbol.
Typing
Technical attributes of the field symbol
TYPE D, F, I, or T
The field symbol has the technical attributes of the predefined elementary type
TYPE <type>
The field symbol has the type <type>. This is a data type defined within the program using the TYPES statement, or a type from the ABAP Dictionary
TYPE REF TO <cif>|DATA
The field symbol is a reference variable for the class or interface <cif>, or for a data object.
TYPE LINE OF <itab>
The field symbol has the same type as a line of the internal table <itab> defined using a TYPES statement or defined in the ABAP Dictionary
LIKE <f>
The field symbol has the same type as an internal data object <f> or structure, or a database table from the ABAP Dictionary
When you use a field symbol that is fully typed, you can address its attributes statically in the program, since they are recognized in the source code. If you fully specify the type of a field symbol as a reference or structured data object, you can address it as you would the data object itself, once you have assigned an object to it. So, for example, you could address the components of a structure, loop through an internal table, or create an object with reference to a field symbol.
REPORT demo_field_symbols_type .
DATA: BEGIN OF line,
 col1(1) TYPE c,
 col2(1) TYPE c VALUE 'X',
 END OF line.
FIELD-SYMBOLS <fs> LIKE line.
ASSIGN line TO <fs>.
MOVE <fs>-col2 TO <fs>-col1.
The field symbol <FS> is fully typed as a structure, and you can address its components in the program.
Attaching a structure to a field symbol
The STRUCTURE addition forces a structured view of the data objects that you assign to a field symbol.
FIELD-SYMBOLS <FS> STRUCTURE <s> DEFAULT <f>.
The structure <s> is either a structured local data object in the program, or a flat structure from the ABAP Dictionary. <f> is a data object that must be assigned to the field symbol as a starting field. However, this assignment can be changed later using the ASSIGN statement.
When you assign a data object to the field symbol, the system only checks that it is at least as long as the structure. You can address the individual components of the field symbol. It has the same technical attributes as the structure <s>.
If <s> contains components with type I or F, you should remember the possible effects of alignment. When you assign a data object to a field symbol with a structure, the data object must have the same alignment, otherwise a runtime error may result. In such cases, you are advised to assign such data objects only to structured field symbols, which retain the same structure as the field symbol at least over the length of the structure.
The STRUCTURE is obsolete; you should no longer use it. Field symbols defined using the STRUCTURE addition are a mixture of typed field symbols and a utility for casting to either local or ABAP Dictionary data types. If you want to define the type of a field symbol, include the TYPE addition in a FIELD-SYMBOLS statement. If you want to use casting, include the CASTING addition in an ASSIGN statement.
Example using the obsolete STRUCTURE addition:
DATA: wa(10) VALUE '0123456789'.
DATA: BEGIN OF line1,
 col1(3),
 col2(2),
 col3(5),
 END OF line1.
DATA: BEGIN OF line2,
 col1(2),
 col2 LIKE sy-datum,
 END OF line2.
FIELD-SYMBOLS: <f1> STRUCTURE line1 DEFAULT wa,
 <f2> STRUCTURE line2 DEFAULT wa.
WRITE: / <f1>-col1, <f1>-col2, <f1>-col3,
 / <f2>-col1, <f2>-col2.
Example using the correct syntax (TYPE and CASTING):
DATA: wa(10) VALUE '0123456789'.
DATA: BEGIN OF line1,
 col1(3),
 col2(2),
 col3(5),
 END OF line1.
DATA: BEGIN OF line2,
 COL1(2),
 COL2 LIKE sy-datum,
 END OF line2.
FIELD-SYMBOLS: <f1> LIKE line1.
ASSIGN wa TO <f1> CASTING.
FIELD-SYMBOLS: <f2> LIKE line2.
ASSIGN wa TO <f2> CASTING.
WRITE: / <f1>-col1, <F1>-col2, <F1>-col3,
 / <f2>-col1, <F2>-col2.
In both cases, the list appears as follows:
012 34 56789
01 2345/67/89
This example declares two field symbols to which different structures are attached. The string WA is then assigned to each of them. The output shows that the field symbols assign the strings component by component according to the type of the components.
Assigning Components of Structures to a Field Symbol
For a structured data object <s>, you can use the statement
ASSIGN COMPONENT <comp> OF STRUCTURE <s> TO <FS>.
to assign one of its components <comp> to the field symbol <FS>. You can specify the component <comp> either as a literal or a variable. If <comp> is of type C or a structure that has no internal tables as components, it specifies the name of the component. If <comp> has any other elementary data type, it is converted to type I and specifies the number of the component. If the assignment is successful, SY-SUBRC is set to 0. Otherwise, it is set to 4.
This statement is particularly important for addressing components of structured data objects dynamically. If you assign a data object to a field symbol either generically or using casting, or pass it generically (or using casting) to the parameter interface of a procedure, you cannot address its components either statically or dynamically. Instead, you must use the above statement. This allows indirect access either using the component name or its index number.
DATA: BEGIN OF LINE,
 COL1 TYPE I VALUE '11',
 COL2 TYPE I VALUE '22',
 COL3 TYPE I VALUE '33',
 END OF LINE.
DATA COMP(5) VALUE 'COL3'.
FIELD-SYMBOLS: <F1>, <F2>, <F3>.
ASSIGN LINE TO <F1>.
ASSIGN COMP TO <F2>.
DO 3 TIMES.
ASSIGN COMPONENT SY-INDEX OF STRUCTURE <F1> TO <F3>.
WRITE <F3>.
ENDDO.
ASSIGN COMPONENT <F2> OF STRUCTURE <F1> TO <F3>.
WRITE / <F3>.
The output is:
11 22 33
33
The field symbol <F1> points to the structure LINE, <F2> points to the field COMP. In the DO loop, the components of LINE are specified by their numbers and assigned one by one to <F3>. After the loop, the component COL3 of LINE is specified by its name and assigned to <F3>. Note that ASSIGN COMPONENT is the only possible method of addressing the components of <F1>. Expressions such as <F1>-COL1 are syntactically incorrect.
Regards,
Laxmi.

What is FIELD CATALOG means

I saw in the forum field catalog using alv, reuse_alv_Fieldcatalog etc
Actually What is meant by field catalog?????
Can i know the purpose of it.
thanks arvind

Hi Aravind,
see the below code how to declare field catalog and declare the heading and output..
Declare field catalog..
DATA : gc_selfield     TYPE slis_selfield,
       gt_fieldcat_drd TYPE slis_t_fieldcat_alv WITH HEADER LINE.
All the fields declared in gt_fieldcat_drd-fieldname are fields in the Internal table and output tbale..
*     Building field catalog
    gt_fieldcat_drd-seltext_m = 'STO / ICSTO'.
    gt_fieldcat_drd-fieldname = 'EBELN'.
    APPEND gt_fieldcat_drd.
    CLEAR : gt_fieldcat_drd.
    gt_fieldcat_drd-seltext_m = 'Item '.
    gt_fieldcat_drd-outputlen = 4.
    gt_fieldcat_drd-fieldname = 'EBELP'.
    APPEND gt_fieldcat_drd.
    CLEAR : gt_fieldcat_drd.
    gt_fieldcat_drd-seltext_m = 'Material'.
    gt_fieldcat_drd-outputlen = 18.
    gt_fieldcat_drd-fieldname = 'MATNR'.
    APPEND gt_fieldcat_drd.
    CLEAR : gt_fieldcat_drd.
    gt_fieldcat_drd-seltext_m = 'Material Desc'.
    gt_fieldcat_drd-outputlen = 30.
    gt_fieldcat_drd-fieldname = 'MAKTX'.
    APPEND gt_fieldcat_drd.
    CLEAR : gt_fieldcat_drd.
    gt_fieldcat_drd-seltext_m = 'RecPlnt'.
    gt_fieldcat_drd-outputlen = 4.
    gt_fieldcat_drd-fieldname = 'WERKS'.
    APPEND gt_fieldcat_drd.
    CLEAR : gt_fieldcat_drd.
    gt_fieldcat_drd-seltext_m = 'ShipPlnt'.
    gt_fieldcat_drd-outputlen = 4.
    gt_fieldcat_drd-fieldname = 'RESWK'.
    APPEND gt_fieldcat_drd.
    CLEAR : gt_fieldcat_drd.
    gt_fieldcat_drd-seltext_m = 'BatchNum'.
    gt_fieldcat_drd-fieldname = 'CHARG'.
    APPEND gt_fieldcat_drd.
    CLEAR : gt_fieldcat_drd.
*   Begin of PJ040809
    gt_fieldcat_drd-seltext_m = 'Vendor Lot'.
    gt_fieldcat_drd-outputlen = 30.                               "Field size declaration
    gt_fieldcat_drd-fieldname = 'VENLOT'.
    APPEND gt_fieldcat_drd.
    CLEAR : gt_fieldcat_drd.
*   End of PJ040809
    gt_fieldcat_drd-seltext_m = 'OpenQty'.
    gt_fieldcat_drd-fieldname = 'MENGE'.
    APPEND gt_fieldcat_drd.
    CLEAR : gt_fieldcat_drd.
if delivery date is not initial.                         "in the Outptu if delivery date is there the it will show column else it will not show
    gt_fieldcat_drd-seltext_m = 'Delvry Date'.            "Field Heading
    gt_fieldcat_drd-fieldname = 'EINDT'.
    APPEND gt_fieldcat_drd.
    CLEAR : gt_fieldcat_drd.
endif.
Then call the function moduel to dispaly..
and pass the field catalog..
Regards,
Prabhudas

What is field symols

hiiiii friends..
i m new to this website...
plz do help to grow in this abap field..
what is field symbols and use of this ??
diffrence between hide and get cursor in the interactive report..

Field Symbols:
Field symbols are placeholders or symbolic names for other fields. They do not physically reserve space for a field, but point to its contents. A field symbol cam point to any data object. The data object to which a field symbol points is assigned to it after it has been declared in the program.
Ex:-
DATA: wa(10) VALUE '0123456789'.
DATA: BEGIN OF line1,
 col1(3),
 col2(2),
 col3(5),
 END OF line1.
DATA: BEGIN OF line2,
 col1(2),
 col2 LIKE sy-datum,
 END OF line2.
FIELD-SYMBOLS: <f1> STRUCTURE line1 DEFAULT wa,
 <f2> STRUCTURE line2 DEFAULT wa.
WRITE: / <f1>-col1, <f1>-col2, <f1>-col3,
 / <f2>-col1, <f2>-col2.
HIDE:
The HIDE statement is one of the fundamental statements for interactive reporting. You use the HIDE technique when creating a basic list. It defines the information that can be passed to subsequent detail lists.
Ex: See demo_list_read_line Program in SE38
GET CURSOR:
Use the statements GET CURSOR FIELD and GET CURSOR LINE to pass the output field or output line on which the cursor was positioned during the interactive event to the ABAP program.
Ex:
See SAPMZTST Program in SE38.
Plz Reward if help,
Mahi.

What is Field catalog pls urgent

Right now I am working on ALV, in that I am using REUSE_ALV_GRID_DISPLAY FM, but the parameters for this FM are an internal table name and a field catalog so i am confused that what field catalog is? Please help me out its very urgent. Thanks in advance.
By Ashok V

Hi,
Field catalog
The field catalog describes the internal data table fields. It is itself an internal table containing an entry for each column in the data table. The field catalog entry determines column output options.
Creating the field catalog
The field catalog can be constructed in various ways:
Manual
Each field catalog entry is explicitly coded into the field catalog by the ALV caller.
Fields with DDIC link must have at least the following field catalog entries:
FIELDCAT-FIELDNAME " Internal output table field name
FIELDCAT-REF_TABNAME " DDIC reference structure name
Fields with no DDIC link must have at least the following field catalog entries:
FIELDCAT-FIELDNAME " Internal output table field name
FIELDCAT-DATATYPE " Internal output table field data type
FIELDCAT-OUTPUTLEN " Column width
and at least one of the four text fields FIELDCAT-SELTEXT_L, FIELDCAT-SELTEXT_M, FIELDCAT-SELTEXT_S, REPTEXT_DDIC.
The field FIELDCAT-TABNAME in the field catalog of hierarchical-sequential lists must also contain the name of the internal output table, to assign columns uniquely to the header or item table. This field must not be filled manually in simple lists.
Automatic
A field catalog need not be passed to ALV under the following condition:
the structure of the internal output table is identical to a DDIC structure or table.
The name of the structure or table is passed to ALV instead of the field catalog.
All columns in the structure are displayed.
Semi-automatic
This mode is a combination of automatic and manual:
the automatically created field catalog can be modified by a manually created field catalog.
If a structure name for an automatic field catalog and a field catalog are both passed, the system determines the field catalog information from them both:
 If the manually created and passed field catalog contains entries for fields which are not described by the DDIC structure, they are added to the field catalog created by the System.
 If the manually created and passed field catalog contains entries for fields which are also described by the DDIC structure, they overwrite the DDIC information.
The system creates field catalogs automatically and semi-automatically from the DDIC reference structure passed to ALV. ALV calls the function module REUSE_ALV_FIELDCATALOG_MERGE which creates the field catalog and adjusts it with an explicit field catalog (semi-automatic mode). This function module can also be called directly by the application (before ALV). This makes the creation of the field catalog by the application flexible.
Hope u understood.
Kindly reward points if u find it useful.
Thanks&Regards,
Ruthra

Whats blue field indicating in MC02M_0ITM (Extraction Purchasing (Item)

Hi,
whats blue field indicating in MC02M_0ITM (Extraction Purchasing (Item),
is this structure is related with mceeko and mcekpo?
Best Regards,
dushyant.

Hi,
MC02M_ITM is mainly getting data from EKPO.
You can see that in Tx LBWE in the maintenance of the extract structure: you'll see MCEKKO and MCEKPO which usually relates to EKKO and EKPO respectively.
hope this helps...
Olivier.
Message was edited by:
Olivier Cora

What is field group?

hello all,
what is field group?

Hi,
A field group combines several fields under one name. For clarity, you should declare your field groups at the end of the declaration part of your program.
A field group does not reserve storage space for the fields, but contains pointers to existing fields. When filling the extract dataset with records, these pointers determine the contents of the stored records.
Once you have declared the possible record types as field groups and defined their structure, you can fill the extract dataset using the following statements: EXTRACT . When the first EXTRACT statement occurs in a program, the system creates the extract dataset and adds the first extract record to it. In each subsequent EXTRACT statement, the new extract record is added to the dataset EXTRACT HEADER. When you extract the data, the record is filled with the current values of the corresponding fields. As soon as the system has processed the first EXTRACT statement for a field group , the structure of the corresponding extract record in the extract dataset is fixed. You can no longer insert new fields into the field groups and HEADER. If you try to modify one of the field groups afterwards and use it in another EXTRACT statement, a runtime error occurs. By processing EXTRACT statements several times using different field groups, you fill the extract dataset with records of different length and structure. Since you can modify field groups dynamically up to their first usage in an EXTRACT statement, extract datasets provide the advantage that you need not determine the structure at the beginning of the program.
give the logical database name as F1S in the attributes of the program
NODES: spfli, sflight.
FIELD-GROUPS: header, flight_info, flight_date.
INSERT: spfli-carrid spfli-connid sflight-fldate
INTO header,
spfli-cityfrom spfli-cityto
INTO flight_info.
START-OF-SELECTION.
GET spfli.
EXTRACT flight_info.
GET sflight.
EXTRACT flight_date.
end-of-selection.
loop.
write:/ spfli-carrid,spfli-connid,sflight-fldate.
endloop.
Regards,
Priyanka.

What is Field Exit--Step By Step procedure..

Hi,
What is Field Exit.
And How to validate a field on any screen using field exit.
what is the Procedure.
Please give me Step by Step Procedure.
Points will be given for straight answers..
Regards,
Kiran

Please find below the step by step procedure for field exit :-
There are eight steps to creating a field exit:
Step 1: Determine Data Element
Step 2: Go To Field Exit Transaction
Step 3: Create Field Exit
Step 4: Create Function Module
Step 5: Code Function Module
Step 6: Activate Function Module
Step 7: Assign Program/Screen
Step 8: Activate Field Exit
Step 1: Determine Data Element
Before you can begin adding the functionality for a field exit, you must know the corresponding data element.
An easy way to determine the data element associated to a particular screen field is to:
Go the appropriate screen.
Position the cursor in the appropriate field.
Press F1 for field-level help.
Click on the Technical info pushbutton (or press F9) on the help dialog box.
On this Technical Information dialog box, the data element will be specified if the field is 'painted' from the ABAP/4 Dictionary.
Step 2: Go To Field Exit Transaction
The transaction to create field exits is CMOD.
You can use the menu path Tools -> ABAP/4 Workbench -> Utilities -> Enhancements -> Project management.
From the initial screen of transaction CMOD, choose the Text enhancements -> Field exits menu path.
After choosing this menu path, you will be taken to the field exits screen. From here, you can create a field exit.
NOTE : Even though you use transaction CMOD to maintain field exits, you do not need to create a project to activate field exits.
Step 3: Create Field Exit
From the field exit screen of transaction CMOD, choose the Field exit -> Create menu path.
After choosing this menu path, a dialog box will prompt you for the appropriate data element .
Enter the data element name and click the Continue pushbutton.
Now, you will be able to create the function module associated to the data elements field exit.
Step 4: Create Function Module
You will automatically be taken to the Function Library (SE37) after entering a data element name and clicking the Continue pushbutton.
In the Function module field, a function module name will be defaulted by the system based on the data element specified. This name will have the following convention:
FIELD_EXIT_<data element>
You can add an identifier (an underscore followed by a single character ).
The first function module for a data elements field exit must be created without an identifier.
To create the function module, click on the Create pushbutton, choose menu path Function module -> Create, or press F5.
After choosing to create the function module, you will get the warning: "Function module name is reserved for SAP". This message is just a warning so a developer does not accidentally create a function module in the field exit name range. By pressing Enter, you will be able to go ahead and create the function module.
Before coding the function module, you will have to specify the function modules attributes -- function group, application, and short text.
Step 5: Code Function Module
From the function modules attributes screen, click on the Source code pushbutton or choose the Goto -> Function module menu path to the code of the function module.
Here you will add your desired functionality for the field exit.
Remember that field exits function module will have two parameters -- one importing parameter called "INPUT" and one exporting parameter called "OUTPUT". These parameters will be set up automatically by the system.
You must remember to assign a value to the OUTPUT field. Even if the value does not change, it must be moved from the INPUT field to the OUTPUT field.
Step 6: Activate Function Module
After coding the function module, you must remember to activate it.
Use the Function module -> Activate menu path to activate the function module.
At this point, you can return to the field exit transaction.
You should be able to 'green arrow' back to this transaction.
When you return to the field exit transaction, you will see an entry for the newly created field exit.
At this point, the field exit is global. That is, it applies to all screens that use a particular data element. On any screen that uses the data element, the corresponding field exit function module will be triggered, once it is active.
Also, the field exit will not be triggered yet because it is inactive.
Step 7: Assign Program/Screen
This step is only needed if you want to make a field exit local.
To make a field exit local, select the field exit and click on the Assign prog./screen pushbutton.
In the dialog box , indicate the appropriate program name and screen number.
This information indicates that the field exit is local to the specified screen in the specified program.
In the dialog box, you determine which function module gets executed for the field exit by specifying the identifier in the Fld. Exit field.
If this field is left blank, the function module triggered will be 'FIELD_EXIT_<data element>'.
If a single-character identifier is entered into the field, the function module triggered will be 'FIELD_EXIT_<data element>_<identifier>'.
Step 8: Activate Field Exit
The field exit must be active for it to be triggered by the system.
Activate the field exit by choosing the Field exit -> Activate menu path.
After assigning the field exit to a change request, its status will change to Active and it will be triggered automatically on the appropriate screen(s).
NOTE : In order to activate the field exit the profile parameter abap/fieldexit = YES must be set on all application servers
Regards
Kiran

WHAT IS DATE BANDLING WHAT IS FIELD CATLOG IN ALV

Similar Messages

Maybe you are looking for