Structure Filed Not Found

Hi
When i was using BAPI
i bind model context to Cust Controller
and Cust Controller to View Context
when i am executing this its showing the follwing error.
The initial exception that caused the request to fail, was:
   com.sap.tc.webdynpro.progmodel.context.ContextConfigurationException: DataNodeInfoCustController_SrmaPartReturn.Ybapi_Srma_Returns_Input.Srma_Output): structure field Quantity 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)
    ... 47 more
regards
mmukesh

HI mukesh,
Try to reimport the model and try it may help you
With Regards
Naidu

Similar Messages

Exception Structure Field not Found

Hi all!
I'm having a strange trouble with a webdynpro app.
I have a BAPI with a structure as an Input parameter, and another structure as an Output parameter, as well as the Return table.
I imported the model to my app, created the custom controller, added the fields to the view, everything seems all right, but when I deploy and run the app, I get the exception that the field Versn of the Output structure is not found:
com.sap.tc.webdynpro.progmodel.context.ContextConfigurationException: DataNodeInfo(Main.Zbapi_Wty_Codigo_Averia_Input.Output.Wa_Averia_Output): structure field Versn not found
    at com.sap.tc.webdynpro.progmodel.context.DataAttributeInfo.init(DataAttributeInfo.java(Compiled Code))
    at com.sap.tc.webdynpro.progmodel.context.NodeInfo.initUnmappedAttributes(NodeInfo.java(Compiled Code))
    at com.sap.tc.webdynpro.progmodel.context.DataNodeInfo.doInit(DataNodeInfo.java(Compiled Code))
    at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java(Compiled Code))
    at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java(Compiled Code))
    ... 29 more
This is the first time it happens, I've used other BAPIs with a similar structure, but I got no errors, so I don't understand what might be wrong this time.
Has any of you have a problem like this??
Thanx.
Jesus

hii ,
Thanks for your response.
I did rebuild the project, restarted my j2ee engine, re-deployed my application but still getting the same error:
com.sap.tc.webdynpro.progmodel.context.ContextConfigurationException: DataNodeInfo(Tdc_DataCust.Zsm_Add_New_Project_Input.Project_Data_AddProject): structure field Skill_Id not found
    at com.sap.tc.webdynpro.progmodel.context.DataAttributeInfo.init(DataAttributeInfo.java:299)
    at com.sap.tc.webdynpro.progmodel.context.NodeInfo.initAttributes(NodeInfo.java:672)
    at com.sap.tc.webdynpro.progmodel.context.DataNodeInfo.doInit(DataNodeInfo.java:233)
    at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:657)
    at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:660)
Please do suggest.

Call SAP function from VB - Structure member not found " unknown "

Hello,
(I don't know if this is the appropriate forum, but I didn't find any which seem to match my topic ...)
I use the following VB code to call the SAP function ARCHIV_PROCESS_RFCINPUT:
    Dim bapiControl As SAPBAPIControl
    Dim logonControl As SAPLogonControl
    Dim functions As SAPFunctions
    Set bapiControl = New SAPBAPIControl
    Set logonControl = New SAPLogonControl
    Set functions = New SAPFunctions
    Set bapiControl.Connection = logonControl.NewConnection
    ' do login
    Set functions.Connection = bapiControl.Connection
    Dim myFunction As SAPFunctionsOCX.Function
    Set myFunction = functions.Add("ARCHIV_PROCESS_RFCINPUT")
    Dim myStructure As SAPFunctionsOCX.Structure
    Set myStructure = functions.CreateStructure("OARFCIN")
    ' the following values are just examples
    myStructure("ARCHIV_ID") = "01"
    myStructure("ARC_DOC_ID") = "1234567890123457890"
    myStructure("AR_OBJECT") = "TIF"
    myStructure("DOC_TYPE") = "FIIINVOICE"
    myStructure("BARCODE") = "1"
    myFunction.Exports("DOCUMENT_ENTRY") = myStructure
At this point execution stops with the following error message:
Err.Number: 1006
Err.Description: Structure member not found "<unknown>"
Err.Source: wdtfuncs
What is wrong? The function ARCHIV_PROCESS_RFCINPUT needs one input parameter called "DOCUMENT_ENTRY" which is of type OARFCIN ...
ARCHIV_CONNECTION_INSERT, which has only Strings as input parameters (no structures), works fine ...
I tried all variations I could think of:
myStructure.Value("ARCHIV_ID") = G_csDefaultRepository
instead of myStructure("ARCHIV_ID") = G_csDefaultRepository
declaring bapiControl, logonControl and functions as Object, and instanciating them with CreateObject(...)
myFunction.Exports(0).Insert "DOCUMENT_ENTRY", myStructure
instead of myFunction.Exports("DOCUMENT_ENTRY") = myStructure
(which gave me a "Collection member not found" error) ...
Nothing worked ...
What is wrong with this code??
Thanks for help!
Regards
Steffi

Hi Ralf,
try substituting following code:
' the following values are just examples
myStructure("ARCHIV_ID") = "01"
myStructure("ARC_DOC_ID") = "1234567890123457890"
myStructure("AR_OBJECT") = "TIF"
myStructure("DOC_TYPE") = "FIIINVOICE"
myStructure("BARCODE") = "1"
myFunction.Exports("DOCUMENT_ENTRY") = myStructure
with that one:
Set myStructure = myFunction.Exports("DOCUMENT_ENTRY")
' the following values are just examples
myStructure.Fields("ARCHIV_ID") = "01"
myStructure.Fields("ARC_DOC_ID") = "1234567890123457890"
myStructure.Fields("AR_OBJECT") = "TIF"
myStructure.Fields("DOC_TYPE") = "FIIINVOICE"
myStructure.Fields("BARCODE") = "1"
Let me know!
Enjoy!!

Structure SI_BBSEG not found during upgrade from 4.6C to ECC 6.0

Hi
We are upgradingour SAP system from 4.6c to ECC 6.0 and we are having an issue while generating the programs, error says '.INCLUDE SI_BBSEG ' not found. It seems like structure SI_BBSEG was not created by SAP'. How would i resolve this issue? i couldnt find any OSS note on this. Please advice.
thank you,
- A

Anil
SI_BBSEG is Include structure of BBSEG & comes already included in it as std SAP. (u can see it in SE11 >> BBSEG)
It does not exist till you want to enhance BBSEG & add your custom fields. Normally those fields will be added to Std SAP screens as custom enhancements . You can go to SE11 & double click; it will ask Do you want to create ?
What is the process you are following for moving Enhancements from 4.6 to ECC6 (user Exits, screen exits) ? If this SI_BBSEG exists in old system, then there must be std screen enhanced which uses the fields of this structure. There could be some programs too which are using this structure while creating FI Documents using std BAPI. recomended that these should move to ECC6 together.
If you have not enhanced BBSEG in 4.6 then refer note : 590977

"Additional DSD Data:Driver Data" filed not found

Hi,
we have activeted Direct store delivery in our system.But when we are trying to create Driver we are unable to fine the field /button "Additional DSD Data:Driver Data".
Please help to resolve the issue.
Thanks in advance for your help.
regards
Sandip

Hi,
Can you post the relevant <jdbc-resource> element in server.xml? Also, your res-ref in ejb xml?
Thanks.
-Tuan.

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

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

Organizational structure not found in production server need advice

HELLO
suddenly posting date was go back to 2008 then our fi consultant get it back to current date but in hr module complit organizational structure was not in PPOM_OLD but positions are in the position screen but not showing the org unit abbr respective positions .
org unit abbr was blank. And when I search the org unit with the object key massage display "object not found"
so kindly give me solution that how can that structure recovered to production Server?

Hi Siba,
hope u r doing good.
Go to table T778P and check whether plan version 01 is set to active and current.
Also try to check with Tcodes : PPOME or PP01 .
Dont worry your Org Stru wont go anywer, Pls scout forum for more clues.
Re: Plan version and org structure
check this thread for more info on Plan versions
Regards
Rohit.S

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

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

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

MDIS ValueX XML Structure, element TEXT not found in xml schema

When you extract ECC Contract through MECCM using port ERP Contract Data Transmission, if your mapping isn't correct 2 exception types are created: StructuralX or ValueX (and ImportX but I haven't seen this type of exception yet).
Anyone noticed that the structure of the XML messages are actually different? The XSD for structuralX files are the same as the files placed in the "ready" folder, where as the XSD for the valueX files are DIFFERENT, and contain a tag called <TEXT>.
This raises an issue when we're trying to handle exceptions in Import Manager using the type Port. We get error "Logon Error: Source file does not conform to XML Schema. Element <TEXT> not found in xml schema".
We can process exceptions in the structuralX folder, but not in the valuex folder because the xml file structure in the valuex folder is different.
Just wondering if anyone else has had this issue or has resolved it. We will open message with SAP.
Thanks.

Hello
What is your MDM version ?
this issue happened in old MDM 7.1 versions but was fixed in SP-2 unless you mapped Clone fields and in this case the fix is a bit later.
In MDM 7.1 the latest builds of SP-2 and SP-3 should have the fix for all issues. But if you use MDM 5.5 then some issues regarding XSD conversion for exception where not addressed due to technical issues.
The workaround for MDM 5.5 (If you use a late build of SP-6 Patch-4 or SP-6 Patch-5) is to use the original file to fix the exception and not the file in the exception folder.
Please notice that when you have Structural exception then all the Source XML file will go to the Exception folder.
But in case of Value Exception - The source XML file will be dropped in the archive folder and another XML file containing VXR's (Virtual Extended Records) will be dropped in the exception folder, Therefore will have a different structure.
Hope it helps.
Thanks.
Best Regards.
Yaron.

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!

Structure Filed Not Found

Similar Messages

Maybe you are looking for