NodeInfo(LogQuestCust.X) ): structure field Add_Documents not found

Hy All,
after reimport of the model and some changes in the CustomController, I got an error message with the text:
"com.sap.tc.webdynpro.progmodel.context.ContextConfigurationException: NodeInfo(LogQuestCust.X): structure field Add_Documents not found
     at com.sap.tc.webdynpro.progmodel.context.AttributeInfo.init(AttributeInfo.java:446)
     at com.sap.tc.webdynpro.progmodel.context.NodeInfo.initAttributes(NodeInfo.java:692)
     at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:677)
     at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:682)
     at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:682)
     at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:682)
     at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:38)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)
I have looked at the model binding of the controller.
I have looked at the context mapping of the WD View.
I can't find the errror !
Thanks for Help !
By Jürgen Berndt

Hi Jürgen,
if you import a model, there are often some structures generated, which you can see at "Dictionaries->Local Dictionary->Data Types->Structures".
If you bind context model nodes to models, the corresponding structures are automatically used to determine the simple types of the node's attributes.
If you reimport the model and the corresponding interface was changed, maybe renaming Add_Documents to Add_DocumentsX, the structure attribute which were used for the initial binding, doesn't exist any longer. Then you should get an error in the Tasks view of the NWDS about the missing structure attribute. Isn't that the case?
Please recheck the context nodes of the controller, which are bound to the model. Missing attributes should be marked by a red cross. If you rebind the model, build and deploy, it should work.
Regards
Stefan

Similar Messages

  • Structure field Igsurl not found - MySAP ERP ESS SP07

    Hi All,
    We have installed ESS SP07 mySAP ERP business package on WAS
    6.40 SP11 and we are getting java stack trace complaining about "structure field Igsurl not found" error while trying to create a travel plan through "Travel and Expenses" tab. However we have alreaady configured IGS as per sap documentation.
    Have anyone experienced the same problem? Any solution?
    Detaled Trace
    Error stacktrace:
    com.sap.tc.webdynpro.progmodel.context.ContextConfigurationException: NodeInfo(FcTraCustomizing.CustomizingGet.CustomizingGet_Output.Et_Country_Plan): structure field Igsurl not found
         at com.sap.tc.webdynpro.progmodel.context.AttributeInfo.init(AttributeInfo.java:469)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.initAttributes(NodeInfo.java:771)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:756)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:761)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:761)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:761)
         at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:346)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.createComponent(ClientComponent.java:854)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.createComponent(ClientComponent.java:157)
         at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.createComponentInternal(ComponentUsage.java:139)
         at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.createComponent(ComponentUsage.java:131)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent$ComponentUsageManager.createBLCComponentUsage(FPMComponent.java:628)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:773)
         at com.sap.xss.tra.trp.fc.plan.FcTrpPlan.onInit(FcTrpPlan.java:518)
         at com.sap.xss.tra.trp.fc.plan.wdp.InternalFcTrpPlan.onInit(InternalFcTrpPlan.java:2756)
         at com.sap.xss.tra.trp.fc.plan.FcTrpPlanInterface.onInit(FcTrpPlanInterface.java:125)
         at com.sap.xss.tra.trp.fc.plan.wdp.InternalFcTrpPlanInterface.onInit(InternalFcTrpPlanInterface.java:2369)
         at com.sap.xss.tra.trp.fc.plan.wdp.InternalFcTrpPlanInterface$External.onInit(InternalFcTrpPlanInterface.java:2547)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:774)
         at com.sap.xss.tra.trp.fc.flight.FcTrpFlight.onInit(FcTrpFlight.java:330)
         at com.sap.xss.tra.trp.fc.flight.wdp.InternalFcTrpFlight.onInit(InternalFcTrpFlight.java:4005)
         at com.sap.xss.tra.trp.fc.flight.FcTrpFlightInterface.onInit(FcTrpFlightInterface.java:138)
         at com.sap.xss.tra.trp.fc.flight.wdp.InternalFcTrpFlightInterface.onInit(InternalFcTrpFlightInterface.java:3558)
         at com.sap.xss.tra.trp.fc.flight.wdp.InternalFcTrpFlightInterface$External.onInit(InternalFcTrpFlightInterface.java:3694)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:774)
         at com.sap.xss.tra.trp.vc.planbuild.VcTrpPlanBuild.onInit(VcTrpPlanBuild.java:495)
         at com.sap.xss.tra.trp.vc.planbuild.wdp.InternalVcTrpPlanBuild.onInit(InternalVcTrpPlanBuild.java:3050)
         at com.sap.xss.tra.trp.vc.planbuild.VcTrpPlanBuildInterface.onInit(VcTrpPlanBuildInterface.java:172)
         at com.sap.xss.tra.trp.vc.planbuild.wdp.InternalVcTrpPlanBuildInterface.onInit(InternalVcTrpPlanBuildInterface.java:139)
         at com.sap.xss.tra.trp.vc.planbuild.wdp.InternalVcTrpPlanBuildInterface$External.onInit(InternalVcTrpPlanBuildInterface.java:215)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:466)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.doEventLoop(FPMComponent.java:354)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:179)
         at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdDoInit(InternalFPMComponent.java:105)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:95)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:346)
         at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:349)
         at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:599)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)
         at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:251)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:48)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:391)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:265)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:345)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:323)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:865)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:240)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
         at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)

    Try if this helps:
    NodeInfo(LogQuestCust.X) ): structure field Add_Documents not found
    /Micke

  • Portal Internal Error - structure field Umskd not found

    Hi Experts,
    I am facing a problem in ESS leave application screen.
    The error is:-
    com.sap.tc.webdynpro.progmodel.context.ContextConfigurationException: DataNodeInfo(FcForm.Orig_Request.Item_to_Check_Orig): structure field Umskd not found
        at com.sap.tc.webdynpro.progmodel.context.DataAttributeInfo.init(DataAttributeInfo.java:299)
        at com.sap.tc.webdynpro.progmodel.context.NodeInfo.initUnmappedAttributes(NodeInfo.java:687)
        at com.sap.tc.webdynpro.progmodel.context.DataNodeInfo.doInit(DataNodeInfo.java:238)
        at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:671)
        at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:674)
        ... 67 more
    My server details are:-
    - ESS Business Package: SP13
    - J2EE engine: Netweaver 7.0 SP16
    - Portal: SP16
    - SAP ECC 6.0 EA-HR 600 Level 27
    I have search through SDN and I even applied SAP note 1058240 but it is not working too.

    Hi Prasad,
    Sorry for late reply. I will try my best to help you.
    First of all, you may apply the note 1058240 to solve your JAVA error. Remember, apply in R/3 server and NOT portal server. Make sure it is imported and then you MUST restart yout portal server. Then everything will be fine. Make sure your EA-HR version is suitable to apply this note.
    Then for configuration, the first thing is to change the agent for workflow WS12300111 and all it's task to General Task. I think you had done this. This is good.
    Then you must maintain SPRO. Normally I will use the IMG path Personnel Management -> Employee Self-Service -> Service-Specific Setting -> Working Time. In here, you will see all the configuration you can do for ESS Leave Application.
    Then you go to Leave Request -> Processing Processes -> Specify Processing Processes for Types of Leave. This is the same thing you do in the IMG path Personnel Time Management - Web Applications - Leave Request - Link Absence Type & Workflow Teplets.
    You must maintains this so that the leave type will display on ESS Leave Application. Please remeber that the leave type is base on PSG and if you have a lot of PSG, then you must create all of them in this configuration. Assign the workflow WS12300111 or your own workflow here if the leave type required a workflow.
    Above is the important things that need to configure. You may configure others stuffs in the same path Personnel Management -> Employee Self-Service -> Service-Specific Setting -> Working Time.
    Regards,
    WaiWeng

  • ESS Error Structure field Region not found

    Hello everyone,
    In Netweaver I installed the ESS/MSS and i'm getting the following error, when I go to "Travel and Expenses" -> "Create Travel Plan"
    com.sap.tc.webdynpro.progmodel.context.ContextConfigurationException: DataNodeInfo(FcTrpPlan.PlanBookAndSave.PlanBookAndSave_I_Address): structure field Region not found
        at com.sap.tc.webdynpro.progmodel.context.DataAttributeInfo.init(DataAttributeInfo.java:299)
        at com.sap.tc.webdynpro.progmodel.context.NodeInfo.initUnmappedAttributes(NodeInfo.java:687)
        at com.sap.tc.webdynpro.progmodel.context.DataNodeInfo.doInit(DataNodeInfo.java:238)
        at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:671)
        at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:674)
        ... 54 more
    Do you have an idea how to solve the problem? Thanks a lot!

    Hi All
    We are also getting a similar error. It seems the error is related to SP Levels. Have you been able to resolve this error. Can you please share the details...Thanks

  • Structure field Umskd not found when access team calendar view in MSS.

    Hello.
    I am keep getting the following error message in my portal when access team calendar view in MSS portal. I am running EP 7.0 with ERP2005 as my back-end system:
    com.sap.tc.webdynpro.progmodel.context.ContextConfigurationException: DataNodeInfo(FcSelectionList.SelectList.Output.Ex_Request_List): structure field Umskd not found
        at com.sap.tc.webdynpro.progmodel.context.DataAttributeInfo.init(DataAttributeInfo.java:299)
        at com.sap.tc.webdynpro.progmodel.context.NodeInfo.initUnmappedAttributes(NodeInfo.java:687)
        at com.sap.tc.webdynpro.progmodel.context.DataNodeInfo.doInit(DataNodeInfo.java:238)
        at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:671)
        at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:674)
    Since I am new to MSS portal, I don't know what infor I am missing. Please advice.
    Best regards,
    Phuong.

    Hi Vinod Patil,
    I just get the problem solved. I may show you the way and hope it help.
    First you should apply the SAP note 1058240 (I am in EA-HR 600 level 27 but we still need to apply) into R/3 server. This note is asking you to patch a .SAR (I have no idea on this file) and you may ask your basis to import it. Make should it is imported and the restart the portal server.
    This is what we do to solve the problem. Thanks.
    Regards,
    WaiWeng

  • Configuring Personal Information - structure field Default_Begda not found

    Hello,
    I am using ECC5 and EP7.  I get the below Internal Server error when attempting to view -
    Addresses
    Bank Information
    Personal Data
    The initial exception that caused the request to fail, was:
       com.sap.tc.webdynpro.progmodel.context.ContextConfigurationException: DataNodeInfo(FcPersInfo.InitPernr.InitPernrOutput.Subtypes): <b>structure field Default_Begda not found</b>
        at com.sap.tc.webdynpro.progmodel.context.DataAttributeInfo.init(DataAttributeInfo.java:299)
        at com.sap.tc.webdynpro.progmodel.context.NodeInfo.initUnmappedAttributes(NodeInfo.java:687)
        at com.sap.tc.webdynpro.progmodel.context.DataNodeInfo.doInit(DataNodeInfo.java:238)
        at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:671)
        at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:674)

    Hi,
    I am using ECC 5.0 with EP 6.0 SP 19.
    HR-Package support pack is 15.
    I am also facing the same issue.
    Kindly let me know the solution to this problem.
    Regards,
    Manoj

  • Creating Travel Request Error( structure field City_Districtadr not found )

    Hi All
    While creating travel request from EP, we are encountering the following "error:com.sap.tc.webdynpro.progmodel.context.ContextConfigurationException: DataNodeInfo(FcTreGeneralData.GeneralDataCheck.GeneralDataCheck_Output.GeneralDataCheck_E_General_Data): structure field City_Districtadr not found "
    I believe the issue is related to SP levels. Can anyone help resolve this.
    Thanks
    R Kumar

    Hi,
    As other said you may need to update software components SAP-HR , EA-HR for this check this
    SAP Note 761266 - Self Services Patches
    Regards
    Vijay
    Edited by: Vijay Mohan on Jun 27, 2008 3:11 PM

  • Structure field Etix_Automatic not found

    Hi all,
    We are using Travel Management from ESS, And i get the below error when i click on Create Travel Request or Expense Report
    com.sap.tc.webdynpro.progmodel.context.ContextConfigurationException: DataNodeInfo(FcTraCustomizing.CustomizingGet.CustomizingGet_Output.E_Plan_Control_Param): structure field Etix_Automatic not found
    I have done all the back-end configuration. Don't know what is wrong, Please help.
    Thanks,
    John

    Please check that OSS notes 1391756 and 1337535 are fully implemented - there were some legal changes implemented in ETIX
    Make sure ALL manual steps are fully followed!

  • ESS Configuration error structure field Roundtrip_Strategy not found

    we have ep7 and ecc6 our HR guyz are getting this issue when trying to create a travel request,its working in back end can any one help..?

    Hi,
    As other said you may need to update software components SAP-HR , EA-HR for this check this
    SAP Note 761266 - Self Services Patches
    Regards
    Vijay
    Edited by: Vijay Mohan on Jun 27, 2008 3:11 PM

  • "Field Catalog not found" ...problem in ALV reporting !!

    Hi,
    When i execute my report program where in I generate a Selection screen, I am able to select the values in the selection screen. Once I click on the execute button I get the message
    "Field Catalog not found"...
    The elabore message is
    "Field Catalog cannot be determined becaus the output table structure name was not specified"
    Where am I wrong ??
    Find below my code ...
    *& Report  Z_MIGO_TXJCD_REPORT
    REPORT  Z_MIGO_TXJCD_REPORT.
    TYPE-POOLS: slis.
    TABLES:  makt,mseg,zmigo_extend,ttxj,mkpf.
    DATA: BEGIN OF migo_data OCCURS 0,
           matnr LIKE mseg-matnr,
           werks LIKE mseg-werks,
           lgpla LIKE mseg-lgpla,
           bwart LIKE mseg-bwart,
           menge LIKE mseg-menge,
           dmbtr LIKE mseg-dmbtr,
           budat LIKE mkpf-budat,
           txjcd LIKE zmigo_extend-txjcd,
          END OF migo_data.
    DATA: it_cat TYPE slis_t_fieldcat_alv,
          wa_lay TYPE slis_layout_alv.
    FIELD-SYMBOLS: <fs_cat> LIKE LINE OF it_cat.
    SELECT-OPTIONS: so_matnr FOR makt-matnr,
                    so_budat FOR mkpf-budat,
                    so_werks FOR mseg-werks,
                    so_lgpla FOR mseg-lgpla,
                    so_bwart FOR mseg-bwart,
                    so_txjcd FOR ttxj-txjcd.
    START-OF-SELECTION.
      SELECT amatnr awerks algpla abwart
             amenge admbtr bbudat ctxjcd INTO TABLE
             migo_data
        FROM mseg AS a INNER JOIN mkpf AS b ON amblnr = bmblnr INNER JOIN
             zmigo_extend AS c ON amblnr = cmblnr
       WHERE a~matnr IN so_matnr
         AND b~budat IN so_budat
         AND a~werks IN so_werks
         AND a~lgpla IN so_lgpla
         AND a~bwart IN so_bwart
         AND c~txjcd IN so_txjcd.
      CALL FUNCTION 'REUSE_ALV_FIELDCATALOG_MERGE'
        EXPORTING
          i_program_name         = sy-cprog
          i_internal_tabname     = 'migo_data'
          i_inclname             = sy-cprog
        CHANGING
          ct_fieldcat            = it_cat
        EXCEPTIONS
          inconsistent_interface = 1
          program_error          = 2
          OTHERS                 = 3.
      LOOP AT it_cat ASSIGNING <fs_cat>.
        CLEAR <fs_cat>-key.
      ENDLOOP.
      wa_lay-zebra = 'X'.
      CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
        EXPORTING
          i_grid_title  = 'MIGO report with Tax Jurisdiction Code'
          is_layout     = wa_lay
          it_fieldcat   = it_cat
        TABLES
          t_outtab      = migo_data
        EXCEPTIONS
          program_error = 1
          OTHERS        = 2.

    Give 'migo_data' in uppercase as ''MIGO_DATA'.

  • 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

  • Field tagReuseDefault not found??

    Hi:
    I tried to run the BC4J sample application after installed BC4J on OC4J and got the following message. Can someone tell me what does it mean?
    Thanks
    Teng Kam
    ===============================================================
    java.lang.NoSuchFieldError: oracle.jsp.runtime.OracleJspRuntime: field tagReuseDefault not found
    at oracle.jsp.runtimev2.JspServlet.init(JspServlet.java:268)
    at com.evermind[Oracle9iAS (9.0.2.0.0) Containers for J2EE].server.http.HttpApplication.loadServlet(HttpApplication.java:1653)
    at com.evermind[Oracle9iAS (9.0.2.0.0) Containers for J2EE].server.http.HttpApplication.findServlet(HttpApplication.java:3893)
    at com.evermind[Oracle9iAS (9.0.2.0.0) Containers for J2EE].server.http.HttpApplication.getRequestDispatcher(HttpApplication.java:2341)
    at com.evermind[Oracle9iAS (9.0.2.0.0) Containers for J2EE].server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:560)
    at com.evermind[Oracle9iAS (9.0.2.0.0) Containers for J2EE].server.http.HttpRequestHandler.run(HttpRequestHandler.java:250)
    at com.evermind[Oracle9iAS (9.0.2.0.0) Containers for J2EE].util.ThreadPoolThread.run(ThreadPoolThread.java:62)

    hi
    if you are using custom structure in ur program its a must to pass fieldcat.
    uncomment the field cat parameter in the function module reuse_alv_list_display or reuse_alv_grid_display
    ao populate the fieldcat and pass it to the fm
    regards
    prasanth

  • Field Catalog Not Found in ALV

    Hi Experts,
    I am trying to exceute the below code its shows the Field CataLog Not Found
    Code is:
    TYPE-POOLS:slis.
    TABLES:ekpo,mseg.
    TYPES: BEGIN OF ty_ekpo,
           ebeln TYPE ekpo-ebeln,
           ebelp TYPE ekpo-ebelp,
           matnr TYPE ekpo-matnr,
           menge TYPE ekpo-menge,
           END OF ty_ekpo.
    TYPES: BEGIN OF ty_mseg,
           ebeln TYPE mseg-ebeln,
           ebelp TYPE mseg-ebelp,
           matnr TYPE mseg-matnr,
           menge TYPE mseg-menge,
           bwart TYPE mseg-bwart,
           END OF ty_mseg.
    TYPES: BEGIN OF ty_final,
            ebeln TYPE ebeln,
            ebelp TYPE ebelp,
            qtysup TYPE MENGE_D,
            qtyact TYPE MENGE_D,
            qtyrej TYPE MENGE_D,
           END OF ty_final.
    DATA: it_mseg  TYPE  TABLE OF ty_mseg WITH HEADER LINE,
          it_ekpo  TYPE  TABLE OF ty_ekpo WITH HEADER LINE,
          it_final TYPE  TABLE OF ty_final WITH HEADER LINE.
    DATA: wa_fieldcat TYPE slis_fieldcat_alv,
          it_fieldcat TYPE slis_t_fieldcat_alv.
    DATA:wa_mseg LIKE LINE OF it_mseg,
         wa_ekpo LIKE LINE OF it_ekpo ,
         wa_final LIKE LINE OF  it_final.
    SELECT-OPTIONS: p_ebeln FOR ekpo-ebeln.
    START-OF-SELECTION.
    SELECT ebeln ebelp matnr menge FROM ekpo
                                     INTO TABLE it_ekpo
                                     WHERE ebeln IN p_ebeln.
      IF it_ekpo[] IS NOT INITIAL.
        SELECT ebeln ebelp matnr menge bwart FROM mseg
                                                    INTO TABLE it_mseg
                                                    FOR ALL ENTRIES IN it_ekpo[]
                                                    WHERE ebeln EQ it_ekpo-ebeln
                                                    AND   ebelp EQ it_ekpo-ebelp
                                                    AND bwart EQ '122'.
      ENDIF.
      LOOP AT  it_mseg  .
        READ TABLE it_ekpo WITH KEY ebeln = it_mseg-ebeln.
        IF sy-subrc EQ 0.
          it_final-qtyrej = it_mseg-menge.
          it_final-qtysup = it_ekpo-menge.
          it_final-ebeln  = it_mseg-ebeln.
          it_final-ebelp  = it_mseg-ebelp.
        ENDIF.
    IF sy-subrc EQ 0.
          it_final-qtyact = ( it_final-qtysup ) - ( it_final-qtyrej ).
        ENDIF.
        APPEND it_final.
      ENDLOOP.
      wa_fieldcat-fieldname = 'EBELN'.
      wa_fieldcat-tabname   = 'IT_FINAL'.
      wa_fieldcat-seltext_l = 'Purchase Doc'.
      wa_fieldcat-seltext_m = wa_fieldcat-seltext_l.
      wa_fieldcat-seltext_s = wa_fieldcat-seltext_l.
      wa_fieldcat-col_pos     = 1.
      wa_fieldcat-outputlen   = 10.
      APPEND wa_fieldcat TO it_fieldcat.
      CLEAR wa_fieldcat.
      wa_fieldcat-fieldname = 'EBELP'.
      wa_fieldcat-tabname   = 'IT_FINAL'.
      wa_fieldcat-seltext_l = 'Item'.
      wa_fieldcat-seltext_m = wa_fieldcat-seltext_l.
      wa_fieldcat-seltext_s = wa_fieldcat-seltext_l.
      wa_fieldcat-col_pos     = 2.
      wa_fieldcat-outputlen   = 5.
      APPEND wa_fieldcat TO it_fieldcat.
      CLEAR wa_fieldcat.
      wa_fieldcat-fieldname = 'QTYSUP'.
        wa_fieldcat-tabname   = 'IT_FINAL'.
      wa_fieldcat-seltext_l = 'QuatitySupply'.
      wa_fieldcat-seltext_m = wa_fieldcat-seltext_l.
      wa_fieldcat-seltext_s = wa_fieldcat-seltext_l.
      wa_fieldcat-col_pos     = 3.
      wa_fieldcat-outputlen   = 13.
      APPEND wa_fieldcat TO it_fieldcat.
      CLEAR wa_fieldcat.
      wa_fieldcat-fieldname = 'QTYACT'.
        wa_fieldcat-tabname   = 'IT_FINAL'.
      wa_fieldcat-seltext_l = 'QualityAccepted'.
      wa_fieldcat-seltext_m = wa_fieldcat-seltext_l.
      wa_fieldcat-seltext_s = wa_fieldcat-seltext_l.
      wa_fieldcat-col_pos     = 4.
      wa_fieldcat-outputlen   = 13.
      APPEND wa_fieldcat TO it_fieldcat.
      CLEAR wa_fieldcat.
      wa_fieldcat-fieldname = 'QTYREJ'.
      wa_fieldcat-tabname   = 'IT_FINAL'.
      wa_fieldcat-seltext_l = 'QualityRejected'.
      wa_fieldcat-seltext_m = wa_fieldcat-seltext_l.
      wa_fieldcat-seltext_s = wa_fieldcat-seltext_l.
      wa_fieldcat-col_pos     = 5.
      wa_fieldcat-outputlen   = 13.
      APPEND wa_fieldcat TO it_fieldcat.
      CLEAR wa_fieldcat.
      DATA: repid LIKE sy-repid.
      repid = sy-repid.
    CALL FUNCTION 'REUSE_ALV_LIST_DISPLAY'
       EXPORTING
          I_CALLBACK_PROGRAM             = repid
        TABLES
          t_outtab                       = it_final[]
      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.
    Thanks In Advance
    Poorna

    Hi,
    pass parametrs as it is given below...
    CALL FUNCTION 'REUSE_ALV_LIST_DISPLAY'
    EXPORTING
      I_INTERFACE_CHECK              = ' '
      I_BYPASSING_BUFFER             =
      I_BUFFER_ACTIVE                = ' '
      I_CALLBACK_PROGRAM             = repid
      I_CALLBACK_PF_STATUS_SET       = ' '
      I_CALLBACK_USER_COMMAND        = ' '
      I_STRUCTURE_NAME               =
      IS_LAYOUT                      =
      IT_FIELDCAT                    = it_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
      IR_SALV_LIST_ADAPTER           =
      IT_EXCEPT_QINFO                =
      I_SUPPRESS_EMPTY_DATA          = ABAP_FALSE
    IMPORTING
      E_EXIT_CAUSED_BY_CALLER        =
      ES_EXIT_CAUSED_BY_USER         =
      TABLES
        t_outtab                       = it_final[]
    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.
    Thanks & Regards
    Ashu

  • Error ,Field catalog not found while doing billing with DP90

    Dear Guru's
    while doing billing with DP90 transaction code.i have given service order no xxxx and execute.Then i received the below error
    Field catalog not found , Message no. 0K530.Kindly help me in solving the issue.
    Thank u
    S Babu

    hi naga suribabu,
    I am also facing same issue. can you please help, where to  check the configuration for this issue

Maybe you are looking for