All fields are not found in Table Maitainence Generator

Hi all,
I have create a table with ZPFT_TRAY with 6 fields and created table maitainence generator for the table.
But when i check in SM30 i can see only 5 fields in Table maitainence generator.
will anybody let me know why it is showing only five fields.
Regards,
Madhavi

Hi madhavi,
do one thing delete your old table maintenance generator and again create a new TMG , generate it properly and save it and then check in sm30. and if u have defined your own data element then fill the field label of that data element and activate ur table. because when ever you do any modification in your Ztable then you have to create again table maintenance generator othervise your modification will not reflect in sm30.
hope this will help you.
Regards
Saurabh

Similar Messages

All fields are not mapped in transformation 0IC_C03 to 2LIS_03_BF_TR

I have replicated BI7 data sources of 2lis_03_BF,BX & UM from ECC. All the infosources are BI7 infosources.After installing the BI Content for 0IC_C03, infosource 2LIS_03_BF_TR is not active.When I am trying to activate the transformation it is showing a error in START ROUTINE & also all fields are not mapped.
Please suggest a solution.
Thanx in advance.
Edited by: Aritra on Nov 28, 2011 11:37 AM

Hi,
i think you have done some modification manually(either added something and deleted something in transformation) thats why code isn't maching with standard sorce package.
so to resolve this error just remove changes you manually did. or remove that code and again create start routine and paste the code which u need.
Thanks & Regards,
NIKHIL

All fields are not displayed in SM30

Dear All,
I have created one Z-Table with 5 fields. For that Z-Table I have maintained table maintenance generator. Now in SM30 I am able to see only 3 fields, I have checked all the options but I am not able to find out what is the problem that 2 fields are not getting displayed.
Please tell me what might be the issue?
warm regards,
nishu

HI,
While generating the TM there is oneoption which can disable some fields in sm30.
I think they may be the reason in your case.
regards,

All fields are not coming in view

Hi,
I have created a view with 6 fields but when i am accessing it with SM30 only first 4 fields are showing (key fields) not the last two fields.
how to display the all fields.
thanks

Hi
May be the problem is you have done a 2 screen table maintenance. First screen in table control will display only the key fields. When you select that row by double clicking you shall be displayed with the other two fields.
~ Ranganath

All fields are not displaying in the infotype screen control

Hello Everybody,
All the fields from infotype 2001 and 2002 are not getting displayed in the screen control for these infotypes and
when I checked the screens for these infotypes, the mod. groups/functions has not been set for field 'Group3' for those
infotype fields.
Is there a way I could set this field ' Group3' for these infotype fields also ? Can it be done thru screen exit and if yes could
anyone tell me what's the screen exit for these infotypes ?
Thanks
Alok

solved it myself.

All fields are not visible while creating transformation

Hi experts,
I am trying to create transformaion between a LO datasource and DSO designed by me. In R3, in RSA6 I can see more than 45 fields but while creating transformation only 30 fields are available.
I tried by replicating the datasource multiple times but no change.
kindly suggest where I am doing wrong.
thanks and regards,
rajesh.

Hi Rajesh, Please follow the follwing steps:
Goto RSA6, select your data source and then click on change and save button.
this will take you to transfer structure. There check the fiels you want to see have hide check box or not. If yes then un hide them. Then save the transfer structure.
Execute the datasource in RSA3. You should be able to see the filds you have unhide in previous step.
replicate the data source in in BW
Goto transfomation in change mode and then to routine. Now you will be able to see the fileld in the routine.

Report error- All fields are not taking

Hi,
I
have created Program for the report ,But it does ,not selecting all foelds,
What will the possible reason.
I have created report for rows as
Notification Inspection lot qty Ok Qty Rejected Qty Defect Group Defect Code Code Qty Code Description.
But Report is picking data for the coloumns of NOTIFICATION and CODE QTY.
Is there i am missing in program?
Details as following
*& Report ZQMLOTDTL
REPORT ZQMLOTDTL.
*Table Declarations.
TABLES:QALS,QMEL,QMFE,QPCT.
*Data Declarations
TYPE-POOLS : slis.
TYPES : BEGIN OF ty_qals,
 werk TYPE qals-werk,
 budat TYPE qals-budat,
 prueflos TYPE qals-prueflos,
 matnr TYPE qals-matnr,"'Part Number'.
 maktx TYPE makt-maktx,
 mblnr TYPE qals-mblnr,
 zeile TYPE qals-zeile,
 losmenge TYPE qals-losmenge,
 lmenge01 TYPE qals-lmenge01,
 lmenge04 TYPE qals-lmenge04,
 compd TYPE makt-maktx,
END OF ty_qals.
DATA :it_qals TYPE STANDARD TABLE OF ty_qals WITH HEADER LINE.
TYPES:BEGIN OF ty_qmfe,
 qmnum TYPE qmfe-qmnum,
 fegrp TYPE qmfe-fegrp,
 fecod TYPE qmfe-fecod,
 kurztext TYPE qpct-kurztext,
 anzfehler TYPE qmfe-anzfehler,
 werks TYPE qmfe-werks,
 compd1 TYPE qpct-kurztext,
END OF ty_qmfe.
DATA:it_qmfe TYPE STANDARD TABLE OF ty_qmfe WITH HEADER LINE.
TYPES:BEGIN OF ty_qmel,
 qmnum TYPE qmel-qmnum,
 erdat TYPE qmel-erdat,
 matnr TYPE qmel-matnr,
 maktx TYPE makt-maktx,
 prueflos TYPE qmel-prueflos,
 mblnr TYPE qmel-mblnr,
 mblpo TYPE qmel-mblpo,
 compd TYPE makt-maktx,
END OF ty_qmel.
DATA:it_qmel TYPE STANDARD TABLE OF ty_qmel WITH HEADER LINE.
*----------------------FINAL ITAB------------------------
TYPES:BEGIN OF itab,
 werk TYPE qals-werk,
 budat TYPE qals-budat,
 prueflos TYPE qals-prueflos,
 matnr TYPE qals-matnr,
 maktx TYPE makt-maktx,
 mblnr TYPE qals-mblnr,
 zeile TYPE qals-zeile,
 losmenge TYPE qals-losmenge,
 lmenge01 TYPE qals-lmenge01,
 lmenge04 TYPE qals-lmenge04,
 qmnum TYPE qmfe-qmnum,
 fegrp TYPE qmfe-fegrp,
 fecod TYPE qmfe-fecod,
 kurztext TYPE qpct-kurztext,
 anzfehler TYPE qmfe-anzfehler,
 werks TYPE qmfe-werks,
 compd TYPE makt-maktx,
 compd1 TYPE qpct-kurztext,
 erdat TYPE qmel-erdat,
 mblpo TYPE qmel-mblpo,
END OF itab.
DATA : it_itab TYPE STANDARD TABLE OF itab with HEADER LINE.
*Internal Table for field catalog
DATA : t_fieldcat TYPE slis_t_fieldcat_alv WITH HEADER LINE.
DATA : fs_layout TYPE slis_layout_alv.
*Internal Table for sorting
DATA : t_sort TYPE slis_t_sortinfo_alv WITH HEADER LINE.
"For Variant.
DATA : g_variant LIKE disvariant,
 g_save(1) TYPE c,
 gx_variant LIKE disvariant,
 g_exit(1) TYPE c,
 g_tabname_header TYPE slis_tabname,
 g_tabname_item TYPE slis_tabname.
**********************SELECTION-SCREEN**************************
SELECTION-SCREEN:BEGIN OF BLOCK b1 WITH FRAME TITLE text-001.
SELECT-OPTIONS:s_werk FOR qals-werk.
SELECT-OPTIONS:s_budat FOR qals-budat.
SELECTION-SCREEN:END OF BLOCK b1.
" Added By Mayur% on 07.03.2013.
"For Variant
SELECTION-SCREEN BEGIN OF BLOCK 0 WITH FRAME TITLE text-p01.
PARAMETERS: s_var TYPE slis_vari.
SELECTION-SCREEN END OF BLOCK 0.
"Get the default variant
"F4-Help for variant
AT SELECTION-SCREEN ON VALUE-REQUEST FOR s_var.
INITIALIZATION.
PERFORM default_var.
"Validates the diplay variant
*********************END-OF-SELECTION**************************
START-OF-SELECTION.
PERFORM data_select.
PERFORM data_collect.
PERFORM sort_list.
PERFORM data_fieldcat.
*& Form DATA_SELECT
* text
FORM data_select.
SELECT
 qmnum
 fegrp
 fecod
 anzfehler
 werks
FROM qmfe INTO CORRESPONDING FIELDS OF TABLE it_itab
 WHERE werks = it_itab-werks.
SORT it_qmfe BY qmnum.
IF it_qmfe IS NOT INITIAL.
SELECT
 qmel~qmnum
 qmel~erdat
 qmel~prueflos
 qmel~matnr
 makt~matnr
 qmel~mblnr
 qmel~mblpo
* makt~compd
INTO CORRESPONDING FIELDS OF TABLE it_itab
FROM qmel INNER JOIN makt ON qmel~matnr = makt~matnr
FOR ALL ENTRIES IN it_itab
WHERE qmnum = it_itab-qmnum
AND prueflos = it_qals-prueflos.
SORT it_qmel BY prueflos.
SELECT
 prueflos
 FROM qals INTO CORRESPONDING FIELDS OF TABLE it_itab
 FOR ALL ENTRIES IN it_qmfe
 WHERE prueflos = it_qmel-prueflos
 AND werk = it_qmfe-werks
 AND matnr = it_qmel-matnr
 AND mblnr = it_qmel-mblnr
 AND zeile = it_qmel-mblpo
 AND losmenge = it_itab-losmenge
 AND lmenge01 = it_itab-lmenge01
 AND lmenge04 = it_itab-lmenge04.
ENDIF.
ENDFORM. " SELECT_DATA
*& Form fill_fieldcatalog
* text
FORM data_fieldcat.
PERFORM f_fieldcatalog USING '1' 'QMNUM' 'Notification number'.
PERFORM f_fieldcatalog USING '2' 'PRUEFLOS' 'Inspection Lot Number'.
PERFORM f_fieldcatalog USING '3' 'LOSMENGE' 'Inspection Lot Quantity'.
PERFORM f_fieldcatalog USING '4' 'MBLNR' 'Material Document'.
perform f_fieldcatalog USING '5' 'ZEILE' 'Item Number'.
PERFORM f_fieldcatalog USING '6' 'MATNR' 'Material Number'.
PERFORM f_fieldcatalog USING '7' 'MAKTX' 'Material Description'.
PERFORM f_fieldcatalog USING '8' 'WERK' 'Plant'.
PERFORM f_fieldcatalog USING '9' 'BUDAT' 'Date'.
PERFORM f_fieldcatalog USING '10' 'LMENGE01' 'OK'.
PERFORM f_fieldcatalog USING '11' 'LMENGE04' 'Rejected'.
PERFORM f_fieldcatalog USING '12' 'FRGRP' 'Codegroup'.
PERFORM f_fieldcatalog USING '13' 'FRCOD' 'Code'.
PERFORM f_fieldcatalog USING '14' 'kurztext' 'Code Text'.
PERFORM f_fieldcatalog USING '14' 'ANZFEHLER' 'DefectQty'.
PERFORM g_display_grid.
ENDFORM. " DATA_FIELDCAT
*& Form f_fieldcatalog
* text
* -->VALUE(X) text
* -->VALUE(Y) text
* -->VALUE(Z) text
* -->VALUE(W) text
FORM f_fieldcatalog USING value(x) value(y) value(z).
t_fieldcat-col_pos = x.
t_fieldcat-fieldname = y.
t_fieldcat-seltext_l = z.
t_fieldcat-no_zero = 'X'.
APPEND t_fieldcat.
CLEAR t_fieldcat.
ENDFORM. "f_fieldcatalog
*& Form COLLECT_DATA
* text
FORM DATA_COLLECT.
LOOP AT it_qmfe.
it_itab-qmnum = it_qmfe-qmnum.
it_itab-fegrp = it_qmfe-fegrp.
it_itab-fecod = it_qmfe-fecod.
it_itab-anzfehler = it_qmfe-anzfehler.
READ TABLE it_qmel WITH KEY qmnum = it_qmfe-qmnum.
it_itab-prueflos = it_qmel-prueflos.
it_itab-qmnum = it_qmel-qmnum.
READ TABLE it_qals WITH KEY prueflos = it_qmel-prueflos.
it_itab-werk = it_qals-werk.
 it_itab-matnr = it_qals-matnr .
It_itab-mblnr = it_qals-mblnr.
It_itab-zeile = it_qals-zeile.
it_itab-losmenge = it_qals-losmenge.
it_itab-lmenge01 = it_qals-lmenge01.
it_itab-lmenge04 = it_qals-lmenge04.
 APPEND it_itab.
CLEAR :it_itab,it_qals,it_qmel,it_qmfe.
ENDLOOP.
ENDFORM.
*& Form SORT_LIST
* text
FORM sort_list .
* t_sort-spos = '1'.
* t_sort-fieldname = 'werk'.
* t_sort-tabname = 'it_itab[]'.
* t_sort-up = 'X'.
* t_sort-subtot = 'X'.
* append t_sort.
* t_sort-spos = '2'.
* t_sort-fieldname = 'BUKRS'.
* t_sort-tabname = 'it_itab[]'.
* t_sort-up = 'X'.
* t_sort-subtot = 'X'.
* append t_sort.
ENDFORM. " SORT_LIST
*& Form G_DISPLAY_GRID
* text
FORM g_display_grid.
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
 EXPORTING
 i_callback_program = sy-repid
 is_layout = fs_layout
 i_callback_top_of_page = 'TOP-OF-PAGE'
 it_fieldcat = t_fieldcat[]
 it_sort = t_sort[]
 i_save = 'X'
 TABLES
 t_outtab = it_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 4.
ENDIF.
ENDFORM. " G_DISPLAY_GRID
*& Form top-of-page
* text
FORM top-of-page.
DATA: t_header TYPE slis_t_listheader,
 wa_header TYPE slis_listheader,
 t_line LIKE wa_header-info,
 ld_lines TYPE i,
 ld_linesc(10) TYPE c.
* Title
wa_header-typ = 'H'.
wa_header-info = 'QMLOTDTL'.
APPEND wa_header TO t_header.
CLEAR wa_header.
DESCRIBE TABLE it_itab LINES ld_lines.
ld_linesc = ld_lines.
CONCATENATE 'Total No. of Records Selected: ' ld_linesc
 INTO t_line SEPARATED BY space.
wa_header-typ = 'A'.
wa_header-info = t_line.
APPEND wa_header TO t_header.
CLEAR: wa_header, t_line.
CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
 EXPORTING
 it_list_commentary = t_header.
ENDFORM.
 "top-of-page
*& Form SORT_LIST
* text
* --> p1 text
* <-- p2 text
*& Form DEFAULT_VAR
* text
* --> p1 text
* <-- p2 text
FORM DEFAULT_VAR .
g_variant-report = sy-repid.
g_variant-username = sy-uname.
g_variant-variant = s_var.
CALL FUNCTION 'REUSE_ALV_VARIANT_DEFAULT_GET'
EXPORTING
 I_SAVE = 'A'
CHANGING
 cs_variant = g_variant
EXCEPTIONS
 NOT_FOUND = 2.
IF sy-subrc = 0.
 s_var = g_variant-variant.
ENDIF.
 " DEFAULT_VAR
*& Form VARIANT
* text
* --> p1 text
* <-- p2 text
*----------------------------------------------------------------------*form VARIANT .
g_variant-report = sy-repid.
g_variant-username = sy-uname.
g_variant-variant = s_var.
CALL FUNCTION 'REUSE_ALV_VARIANT_F4'
 EXPORTING
 is_variant = g_variant
* I_TABNAME_HEADER =
* I_TABNAME_ITEM =
* IT_DEFAULT_FIELDCAT =
 I_SAVE = 'A'
* I_DISPLAY_VIA_GRID = ' '
 IMPORTING
 E_EXIT = g_exit
 ES_VARIANT = g_variant
 EXCEPTIONS
 NOT_FOUND = 1
 PROGRAM_ERROR = 2
 OTHERS = 3.
IF sy-subrc = 2.
 MESSAGE ID sy-msgid TYPE 'S' NUMBER sy-msgno
 WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ELSE.
 IF g_exit = space.
 s_var = g_variant-variant.
 ENDIF.
ENDIF.
ENDFORM.
With Regards,
Dev

Hello Dev,
have a look at the select:
SELECT
 qmel~qmnum
 qmel~erdat
 qmel~prueflos
 qmel~matnr
 makt~matnr
 qmel~mblnr
 qmel~mblpo
* makt~compd
INTO CORRESPONDING FIELDS OF TABLE it_itab
This probably does not fill any column in it_itab because the "CORRESPONDING FIELDS" part does not find columns named "qmel~erdat", for example, but only "erdat".
So you may want to change your select to something like this:
SELECT
 qmel~qmnum AS qmnum
 qmel~erdat AS erdat
 qmel~prueflos AS prueflos
 qmel~matnr AS matnr
 qmel~mblnr AS mblnr
 qmel~mblpo AS mblpo
* makt~compd AS compd
INTO CORRESPONDING FIELDS OF TABLE it_itab
In addition, using it_itab in the select as data sink (INTO ... TABLE it_itab) and at the same time as data source (FOR ALL ENTRIES IN it_itab) is probably also not a good idea and may lead to unexpected side effects.
Best regards,
Frank.

PO screen custom fields are not in correct order

Hi Experts,
After creating Shopping cart and purchase order successfully created.
Added my custom fields for PO structure INCL_EEW_PD_ITEM_CSD_PO fields are visible in PO screen automatically with out adding my custom fields in PO layout /SAPSRM/WDC_DODC_PO_I_BD
when i go to PO screen i can see my custom fields but all fields are not in correct order.How can my fields should be in order.
and i added two custom buttons in my PO layout for WD component /SAPSRM/WDC_DODC_PO_I_BD i am not able to see my buttons?
Could you please help me out in this issues its urgent.
Thanks,
Venkatesh G

I've had this problem. There may be a more elegant solution, but what I do is make a playlist of the album and put the movements in the correct order in the playlist. I've also put numbers (01, 02, etc.) in front of the name of the movements. Either one works.
Hope this helps.
Ben

Issue with DEBMAS IDoc,not all fields are reflected in the IDoc Seg E1KNB1M

For IDoc type DEBMAS, there is a segment E1KNB1M. This segment is relate to the customer correspondence details (XD02 -> company code data -> Correspondence).
For any change to the customer master a DEBMAS IDoc is triggered which has data in segments including the E1KNB1M.
In my case for few customers, the not all fields in the segment E1KNB1M contain data. Few fields contain data but the rest are filled with u2018\u2019. This is happening only in the production system, for the same customer in the quality system the data is there as required.
I checked in debugging, and found that the data is correctly passed to the segment in program SAPLVV01 Include LVV01F01. And the segment contains data till the IDoc is triggered. I.e. the fields are not getting cleared at any point.
Can anyone suggest what is happening and how to fix this? Please note that the issue is only in the production system and not in the quality system ( for the same customer).

BTT... Need some help on the above

Key fields are not visible in output condition table

Hi,
     I have created few conndition tables using V/61. But i can not see Key field. It is not displaying. But when I check thru VK11 i can see that all fields are marked as key fields. example of table B018.
My problem is that , i want to make few filed non key fields rest of fileds as key fields so that there should not be any duplicate ntry based on key fields. also I do not want to maintain these two fields for each record.
Is there any exit to modify and view thesefields? or it is a security issue...bold
Your earliest response is highly appreciated.\
Thanks,
AKS

Hi Raga,
Please check the documentation under the customizing path:
IMG -> Sales and Distribution -> System Modifications ->
Create New Fields (Using Condition Technique) ->
New Fields For Pricing
Then click on the paper icon
Here is explained how to setup additional fields for pricing,
not present in the standard.
Notice the following rules:
1. the new fields must have name beginning with 'ZZ' or 'YY' in order
   to avoid problem after upgrade
2. add the new field in the table T681F for the application 'V' and the
   usage 'A'
3. these new fields must be appened to the structures KOMKAZ or KOMPAZ
   (depending they are header or item fields)
4. you should provide these fields by implementing the userexits
   USEREXIT_PRICING_PREPARE_TKOMK (header fields)
   USEREXIT_PRICING_PREPARE_TKOMP (item fields)
   in program MV45AFZZ for sales order, RV60AFZZ for invoice.
In that documentation there are some examples too.
Please check it.
Regards,
Alex

Problem with Change Document FM - Not all fields are tracked in CDPOS

Hello everybody,
Using transaction SCDO and following necessary steps described in forum, I have created a change document ZFBR to track changes of a table ZFBR. The problem is, the generated FM ZFBR_WRITE_DOCUMENT does not track changes of some fields of the table (inserts are always ok, problem is with updates). After some debugging I realized that the FM DDIF_NAMETAB_GET was returning the table DFIES_TAB where the LOGFLAG was empty for some fields (which are not tracked) so that changes of these fields were not visible in table CDPOS. However, fields with LOGFLAG = 'X' are tracked succesfully (changes are visible in table CDPOS).
I did not specify any fields to be get logged or not during the steps in SCDO (can we do such a specification anywhere?), does anyone know why the field LOGFLAG has the value '' (space)?
Best regards;
Ozcan.

Hi again,
The problem has been solved.
The data elements used in a table are the reason for the problem I have described above. When displaying the details of a data element, under tab "Further Characteristics" , the "Change Document" checkbox has to be selected to enable change document tracking. I have copied the problematic data elements with Z prefix and made the necessary enabling. I have replaced the data elements with their Z equivalents.
Best regards.
Ozcan.

Not All Fields are Displayed in RSA3 for a Generic Extractor ??

Hi all,
 I have a created a Generic Extarctor based on a View and enhanced the Extract Structure with 3 ZZ Fields. Now it has 26 fields with width of 273. In RSA3, I could see inly 12 fields with width of 147 only.
 No field has checked as HIDE in DataSource.
 I have checked Settings --> Layout --> Current, there are NO columns in Hidden Fields box which is on right side. All fields are there in left side box under Line 1.
 I could see all the fields in ROOSFIELD table for this DataSource.
When I copy it into Spreadsheet from RSA3, I could see all the fields with data including ZZ fields (Appended Fields).
 What is the problem and how could I fix it, PLEASE ?
 Thanks in advance.
Regards,
Venkat,
Message was edited by:
 Venkat Kodi

Hi Venkat
sorry for late response.
Anyway did you solve your issue.
Forget about the icon now and check again in ROOSFIELD table and check if the missing field for selection has any parameter value. If so (shoudl be a P value ) then maintain it and put a blank value save the changes.
this should solve your issue.
hope this could help you
regards
Boujema

Field catalog not found...

hi all,
when i try to create billing request for a service order (using dp90), i am getting the following message :
Field catalog not found
    Message no. 0K530
Diagnosis
    The field catalog cannot be determined because the output table
    structure name was not specified.
what can i do?

I assume this error happens when you save the billing document, and it is a billing output issue. As said, you could verify this by removing all outputs before saving, and afterwards in change mode add them again one by one to figure out which is failing. Alternatively use the blue i icon to analyze the outputs.
Transaction NACE can be used for output setup across all modules. If the assumption regarding billing is correct, we are dealing with application V3. Mark this in the left side. Press 'output types' button and check the output types you saw in the billing document by double clicking. On the 'General data' is the access sequence assigned. Double click that. Probably will multiple output types be attached to the same access sequence. Mark the access sequence, and unfold the 'Accesses' to the left. Check out the condition tables in the Tab column. All condition tables below 599 is standard and probably OK. Note down the high numbers.
Go back to the initial screen of NACE. With the application (V3) marked, select EDIT - CONDITION TABLES in the menu.
Check each of the used condition tables here. Use utilities - Generate in the menu. Mark all boxes and execute. You can even select the entire range 500-999 at one time if you prefer. At least one condition table should give errors in the generation.

Sap upgrade-Error when using DP90-OK 530-field catalog not found

Hello,
We are upgrading from 4.6c to mySAP ERP 2004 version. In 4.6c, we are using VA90 to create a sales order from service order to bill the customer. However in mySAP ERP 2004 version, VA90 does not exist. So we created DP profile and are using transaction code DP90 to create billling request for the service order. However, System gives an error 'Field catalog not found'. The diagnosis says that -The field catalog cannot be determined because the output table structure name was not specified.
Please help us how to solve the above problem.
Thanks
Mala

hi mala,
did you see SAP-message 442170?
it is all about conversion VA90/DP90.
hope this helps.
br,
matthias
Message was edited by: Matthias Leitner

ALV field catalog not found

Hello there,
I am having problem changing a classic ABAP report to ALV as am hitting the error "field catalog not found".
I am using this 2 functions to help me convert it to ALV format.
and a snippet from my code :
    MODIFY gt_i_data FROM wa_i_data TRANSPORTING priokx.
     ENDLOOP .
gt_report[] = gt_i_data[].
perform f_assign_alv.
perform f_display_alv.
1.f_assign_alv
CALL FUNCTION 'REUSE_ALV_FIELDCATALOG_MERGE'
       EXPORTING
            i_program_name     = c_repid
            i_internal_tabname = 'GT_REPORT'
            i_inclname         = c_repid
       CHANGING
            ct_fieldcat        = gt_fieldcat.
2._display_alv.
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
       EXPORTING
            i_grid_title = v_grid_title
            is_layout     = v_layout
            it_fieldcat   = gt_fieldcat
       TABLES
            t_outtab      = GT_REPORT
       EXCEPTIONS
            program_error = 1
            OTHERS        = 2.
IF sy-subrc NE 0.
    MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
            WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
I noticed during debug,inside 'REUSE_ALV_GRID_DISPLAY' the possible location of error cud be at :
if i_screen_start_column is initial and -
>all these values are empty
     i_screen_start_line   is initial and
     i_screen_start_column   is initial and
     i_screen_end_line     is initial.
    gt_grid-flg_popup = space.
    call screen 500. else. -
>point of error
    gt_grid-flg_popup = 'X'.
    call screen 700
              starting at i_screen_start_column i_screen_start_line
              ending   at i_screen_end_column i_screen_end_line.
endif.
Need your expert advice, please guide.Thanks so much!!

Hi Neesha,
If you are using FM 'REUSE_ALV_FIELDCATALOG_MERGE', during data/types declaration, you have to use the LIKE keyword and not the TYPE keyword.
If you use TYPE, the fieldcat will not be populated.
DATA: BEGIN OF GT_REPORT OCCURS 0,
ebeln LIKE ekpo-ebeln,
ebelp LIKE ekpo-ebelp,
matnr LIKE ekpo-matnr,
werks LIKE ekpo-werks,
menge LIKE ekpo-menge,
netpr LIKE ekpo-netpr,
peinh LIKE ekpo-peinh,
netwr LIKE ekpo-netwr,
END OF GT_REPORT.
Regards,
Jovito.
Edited by: dsouzajovito on Jan 10, 2011 11:32 AM

All fields are not found in Table Maitainence Generator

Similar Messages

Maybe you are looking for