Error in IDOC generation

Hi Gurus,
I have got an Error in IDOC Processing from other interface.
The IDOC status is 51 and we are using it to create Promotion Deal in
SAP ERP through IDOC from other interface.
The Error i am getting in Status Record is that "Promotion is Duplicated
along with Promotion Deal Number"
I have also checked the Promotion Deal No in VB 33 but it is not existing.
Please could you suggest where is the possible error.
I have also checked the Control Record it is correct.
Awaiting for response.
Thanks,
Sam.
+

Hi,
Reprocess the IDOC by using the T.Code "BD87".
Even if the same error persists,try to change the data manually by using the T.Code "WE19".
Check with the ABAPer for debugging the code.
Regards,
Krishna.

Similar Messages

  • Error in IDOC generation in LSMW

    I am getting the following error when I generate the IDOC in LSMW.
    "Event for starting inbound processing was not triggered".
    Can anyone help me on this? I have created the partner profiles, ports everything. Can anybody give a step by step approach for this.
    Thanks

    Hi Pratap,
    You can go through this link for LSMW Documentation.
    http://sapabap.iespana.es/sapabap/manuales/pdf/lsmw.pdf
    Reward points if helpful.
    Regards,
    Harini

  • LSMW error message during "Start Idoc generation"

    Hi ,
    I am getting error message "'/tmp/YS.lsmw.conv' File Has Not Been Accepted for Processing"
    during the step "Start Idoc generation" in transaction LSMW.
    Please help to solve this issue.
    Thanks & regards,
    Yogita

    Hi,
    I already have set port and partner function.
    As per the details of the error message, it says "
    System Response
    Clarify if the inbound file is a Unicode file.
    Procedure
    If it is not a Unicode file, change the port definition and then start inbound processing again.
    If it is a Unicode file, then the file must be generated with the 'EDI_DC40_U' indicator. This must be clarified with the creator of the file.
    I have added the check Unicode fomat while defining the port.
    Can you please help?
    Regards,
    Yogita

  • Reason for errors in IDOCS ? pls tell small scenarios

    hi pls tell practical scenarios reason for errors in idocs? all ale configuration are done.

    goto se16 and look at table EDIDS....in that look at field status text...you will see different reasons when something goes wrong in idoc generation...
    there should be a lot of practical scenario examples for you inside it...

  • Reg: Idoc  generation

    Hi All,
    AS per my understanding for SPEC2K idoc generation, SAP generates two IDOCS. one of standard SAP message type and another is of SPEC2K type .
    <b>My requirement</b> : if the customer requested items are not available then both the SAP message IDOC and SPEC2K idocs should be generated.
    If the customer requested items are available then only SAP message type idoc should be triggered and <b>SPEC2K idoc should not be triggered</b>.
    Is there any settings by which I can achive this.
    Thanks in Advance.
    Vijay.

    Go through the following Steps
    Try with the follwoing steps
    Sending System(Outbound ALE Process)
    Tcode SALE „³ for
    a) Define Logical System
    b) Assign Client to Logical System
    Tcode SM59-RFC Destination
    Tcode BD64 ¡V Create Model View
    Tcode BD82 ¡V Generate partner Profiles & Create Ports
    Tcode BD64 ¡V Distribute the Model view
    This is Receiving system Settings
    Receiving System(Inbound ALE )
    Tcode SALE „³ for
    a) Define Logical System
    b) Assign Client to Logical System
    Tcode SM59-RFC Destination
    Tcode BD64 ¡V Check for Model view whether it has distributed or not
    Tcode BD82 -- Generate partner Profiles & Create Ports
    Tcode BD11 Getting Material Data
    Tcode WE05 ¡V Idoc List for inbound status codes
    Message Type MATMAS
    Tcode BD10 ¡V Send Material Data
    Tcode WE05 ¡V Idoc List for watching any Errors
    1)a Goto Tcode SALE
    Click on Sending & Receiving Systems-->Select Logical Systems
    Here Define Logical Systems---> Click on Execute Button
    go for new entries
    1) System Name : ERP000
    Description : Sending System
    2) System Name : ERP800
    Description : Receiving System
    press Enter & Save
    it will ask Request
    if you want new request create new Request orpress continue for transfering the objects
    B) goto Tcode SALE
    Select Assign Client to Logical Systems-->Execute
    000--> Double click on this
    Give the following Information
    Client : ERP 000
    City :
    Logical System
    Currency
    Client role
    Save this Data
    Step 2) For RFC Creation
    Goto Tcode SM59-->Select R/3 Connects
    Click on Create Button
    RFC Destination Name should be same as partner's logical system name and case sensitive to create the ports automatically while generating the partner profiles
    give the information for required fields
    RFC Destination : ERP800
    Connection type: 3
    Description
    Target Host : ERP000
    System No:000
    lan : EN
    Client : 800
    User : Login User Name
    Password:
    save this & Test it & RemortLogin
    3)
    Goto Tcode BD64 -- click on Change mode button
    click on create moduleview
    short text : xxxxxxxxxxxxxx
    Technical Neme : MODEL_ALV
    save this & Press ok
    select your just created modelview Name :'MODEL_ALV'.
    goto add message type
    Model Name : MODEL_ALV
    sender : ERP000
    Receiver : ERP800
    Message type :MATMAS
    save & Press Enter
    4) Goto Tcode BD82
    Give Model View : MODEL_ALV
    Partner system : ERP800
    execute this by press F8 Button
    it will gives you sending system port No :A000000015(Like)
    5) Goto Tcode BD64
    seelct the modelview
    goto >edit>modelview-->distribute
    press ok & Press enter
    6)goto Tcode : BD10 for Material sending
    Material : mat_001
    Message Type : MATMAS
    Logical System : ERP800
    and Execute
    7)goto Tcode : BD11 for Material Receiving
    Material : mat_001
    Message Type : MATMAS
    and Execute --> 1 request idoc created for message type Matmas
    press enter
    Thanks & regards
    Sreenivas
    Here Master Idoc set for Messge type MATMAS-->press Enter
    1 Communication Idoc generated for Message Type
    this is your IDOC
    Thanks & Regards
    Abhay.
    rewards point

  • Error in Idoc is 51

    I have posted one Idoc and it was succesfully generated.
    But I don't want duplicate Idocs  ( with same data ) using we19.I was using function module to avoind duplicates.
    But I have generated next Idoc...
    Have got
    Error in Idoc is 51.
    Check if invoice already entered under accounting doc. no. 1600002035 20
    Is it okay.. is it considered as stoping of duplicate Idoc generation.
    Thank you.

    Hi,
    I believe when you write avoiding duplicate Idocs ,it means same data should not get posted in SAP via IDOC.
    The error which you have got means -- there is already a document in the system posted by another IDoc & the current IDoc can't be posted due to duplicate data.
    This is avoiding duplication of invoice posting.
    Not avoiding duplicate IDoc creation.
    Thanks.
    Mark points if helpful.

  • Error in report generation-Load report failed

    I have installed crystal reports  for VS2005 runtime in my live environment.When i try to load the report file from a .Net page i am getting the error'Error in Report generation-Load report failed'.
    This works fine in development and testing but when moved to production we are having issues.
    I believe i have a workaround i.e i need to open the rpt in a VS 2005 environment and re-write the connection string again.This fix had worked in development and testing when we had the same issue.
    But not sure if this is a known issue with crystal reports and if so do we have any hot fixes for the same.
    Please help.

    Hi Don,
    The reason why i posted the item on 'data Connectivity issues' is because i suspect the problem is with the connection string.Though i had provided the correct connection string,re-writing the connection string with the same info might help to fix the issue with loading the report.
    Does it mean that there is a problem in the connectivity?
    I have a risk here that i cant re-write the connection string..i.e to open the RPT file in VS2005 and bind it.The production web server & database server sits in a  third party environment and it is not in the company network.So i cant connect to this server to re-write from any other severs in the network.
    Is there any fix which can applied to the server to get this issue resolved?
    Cheers
    Nithya.

  • Error in code generation for deleting table BUT000_TD

    Hi,
    Did anyone encounter this error while working on EEWB ?
    I created the project extension via EEWB and completed the wizard setting with the package (dev. class) value as $temp as I wanted to test it locally.
    One of the errors, that I got is:
    Error in code generation for deleting table BUT000_TD
        Message no. DA464
    Diagnosis
        This error message indicates that internal inconsistencies exist.
    Procedure
        Please consult SAP.

    Hi,
    As I mentioned in my previous post kindly check the consistency of the structure BUT000_TD.
    Regards,
    Sudheer.

  • ERROR 38994 - CSN Generation

    Hello,
    I have 2 pre-production DSEE 7.0 servers in multi-master replication topology with the error:
    ERROR<38994> - CSN Generation - conn=-1 op=-1 msgId=-1 - Internal error  csngen_adjust_time: adjustment limit exceeded; value - 952477, limit - 86400
    This was caused by a change in our NTP servers and now I can't find a way to make this error go away.
    Checked the replication and its working, there are no changes pending on any server.
    Also, tried restarting and reinitializing them via replication agreements but the error persists.
    Looking at the archived threads, there is no clear method to get rid of it.
    Any ideas?

    SylvainDuloutre escribió:
    Hello,
    Is the time on your servers synchronized now ?
    The CSN generator uses persistent timestamps as a point of reference for generating new CSNs. I don't know all the details, but the practical consequence is that once they get out of sync, you pretty much have to wipe out all of the CSN related data to make the problem go away. That means replication configuration, changelogs, and maybe even replication metadata embedded in the database.
    -Sylvain
    Yes, the servers time are synchronized now.
    So, to get rid of all the CSN related data I need to delete replication agreements and re initialize each server from a clean LDIF?

  • Error in Rule Generation

    We are configuring RAR 5.3, and so far we successfully uploaded all text files. But when we try to generete the rules for logical systems in a background job, after 45 minutes the following error is shown:
    Nov 4, 2008 9:56:02 AM com.virsa.cc.comp.VirsaXSR3_01Interface execute
    WARNING: VIRSAXSR3_01: Cannot execute BAPI RoleList
    java.lang.NullPointerException
         at com.virsa.cc.common.ModelNodeUtil.copyNodeTreeToModel(ModelNodeUtil.java:42)
         at com.virsa.cc.comp.VirsaXSR3_01Interface.execute(VirsaXSR3_01Interface.java:267)
         at com.virsa.cc.comp.wdp.InternalVirsaXSR3_01Interface.execute(InternalVirsaXSR3_01Interface.java:1341)
         at com.virsa.cc.comp.wdp.InternalVirsaXSR3_01Interface$External.execute(InternalVirsaXSR3_01Interface.java:1376)
         at com.virsa.cc.comp.BackendAccessInterface.executeBAPIModel(BackendAccessInterface.java:3314)
         at com.virsa.cc.comp.BackendAccessInterface.execBAPI(BackendAccessInterface.java:398)
         at com.virsa.cc.comp.BackendAccessInterface.executeBAPI(BackendAccessInterface.java:301)
         at com.virsa.cc.comp.wdp.InternalBackendAccessInterface.executeBAPI(InternalBackendAccessInterface.java:4227)
         at com.virsa.cc.comp.BackendAccessInterface.searchRole(BackendAccessInterface.java:776)
         at com.virsa.cc.comp.wdp.InternalBackendAccessInterface.searchRole(InternalBackendAccessInterface.java:4283)
         at com.virsa.cc.comp.wdp.InternalBackendAccessInterface$External.searchRole(InternalBackendAccessInterface.java:4740)
         at com.virsa.cc.dataextractor.bo.DataExtractorSAP.searchObj(DataExtractorSAP.java:382)
         at com.virsa.cc.xsys.riskanalysis.AnalysisEngine.getObjArray(AnalysisEngine.java:395)
         at com.virsa.cc.xsys.riskanalysis.AnalysisEngine.performActPermAnalysis(AnalysisEngine.java:695)
         at com.virsa.cc.xsys.riskanalysis.AnalysisEngine.riskAnalysisRE(AnalysisEngine.java:2706)
         at com.virsa.cc.xsys.riskanalysis.AnalysisDaemonWS.start(AnalysisDaemonWS.java:78)
         at com.virsa.cc.comp.BgJobInvokerView.wdDoModifyView(BgJobInvokerView.java:434)
         at com.virsa.cc.comp.wdp.InternalBgJobInvokerView.wdDoModifyView(InternalBgJobInvokerView.java:1223)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doModifyView(DelegatingView.java:78)
         at com.sap.tc.webdynpro.progmodel.view.View.modifyView(View.java:337)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doModifyView(ClientComponent.java:480)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doModifyView(WindowPhaseModel.java:551)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:148)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:299)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:711)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:665)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:232)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46)
         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:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         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:102)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    Nov 4, 2008 9:56:02 AM com.virsa.cc.comp.VirsaXSR3_01Interface execute
    WARNING: VIRSAXSR3_01: Cannot execute BAPI RoleList
    java.lang.NullPointerException
         at com.virsa.cc.common.ModelNodeUtil.copyNodeTreeToModel(ModelNodeUtil.java:42)
         at com.virsa.cc.comp.VirsaXSR3_01Interface.execute(VirsaXSR3_01Interface.java:267)
         at com.virsa.cc.comp.wdp.InternalVirsaXSR3_01Interface.execute(InternalVirsaXSR3_01Interface.java:1341)
         at com.virsa.cc.comp.wdp.InternalVirsaXSR3_01Interface$External.execute(InternalVirsaXSR3_01Interface.java:1376)
         at com.virsa.cc.comp.BackendAccessInterface.executeBAPIModel(BackendAccessInterface.java:3314)
         at com.virsa.cc.comp.BackendAccessInterface.execBAPI(BackendAccessInterface.java:398)
         at com.virsa.cc.comp.BackendAccessInterface.executeBAPI(BackendAccessInterface.java:301)
         at com.virsa.cc.comp.wdp.InternalBackendAccessInterface.executeBAPI(InternalBackendAccessInterface.java:4227)
         at com.virsa.cc.comp.BackendAccessInterface.searchRole(BackendAccessInterface.java:776)
         at com.virsa.cc.comp.wdp.InternalBackendAccessInterface.searchRole(InternalBackendAccessInterface.java:4283)
         at com.virsa.cc.comp.wdp.InternalBackendAccessInterface$External.searchRole(InternalBackendAccessInterface.java:4740)
         at com.virsa.cc.dataextractor.bo.DataExtractorSAP.searchObj(DataExtractorSAP.java:382)
         at com.virsa.cc.xsys.riskanalysis.AnalysisEngine.getObjArray(AnalysisEngine.java:395)
         at com.virsa.cc.xsys.riskanalysis.AnalysisEngine.performActPermAnalysis(AnalysisEngine.java:695)
         at com.virsa.cc.xsys.riskanalysis.AnalysisEngine.riskAnalysisRE(AnalysisEngine.java:2706)
         at com.virsa.cc.xsys.riskanalysis.AnalysisDaemonWS.start(AnalysisDaemonWS.java:78)
         at com.virsa.cc.comp.BgJobInvokerView.wdDoModifyView(BgJobInvokerView.java:434)
         at com.virsa.cc.comp.wdp.InternalBgJobInvokerView.wdDoModifyView(InternalBgJobInvokerView.java:1223)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doModifyView(DelegatingView.java:78)
         at com.sap.tc.webdynpro.progmodel.view.View.modifyView(View.java:337)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doModifyView(ClientComponent.java:480)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doModifyView(WindowPhaseModel.java:551)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:148)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:299)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:711)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:665)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:232)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46)
         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:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         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:102)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    Whe try then to generete the rules in foreground to see what happens and we got a different error:
    Error in Rule Generation! Reason:ResourceException in method ConnectionFactoryImpl.getConnection():
    com.sap.engine.services.connector.exceptions.BaseResourceException: Cannot get connection for 120 seconds.
    Possible reasons:
    1) Connections are cached within SystemThread(can be any server service or any code invoked within SystemThread in the SAP J2EE Engine),
    2) The pool size of adapter "SAPSR3DB" is not enough according to the current load of the system or
    3) The specified time to wait for connection is not enough according to the pool size and current load of the system.
    In case 1) the solution is to check for cached connections using the Connector Service list-conns command,
    in case 2) to increase the size of the pool and
    in case 3) to increase the time to wait for connection property. In case of application thread,
    there is an automatic mechanism which detects unclosed connections and unfinished transactions.
    Reading the descriptions in both errors, it seems like the RAR application is trying to connect to the back end system during rule generation. Is this correct?
    We followed all the recommendations indicated in the post-installation for RAR 5.3.
    Any ideas??

    Dear Pablo,
    Please check if you have changed your Jco pool configuration as below :
    JCo pool configuration            Original      Change u2013 as per
                                                                    SAP note
    Maximum pool size            50     100
    Maximium connections     100     1800
    Connection timeout ( milli sec )     100     10000
    Max waiting time ( milli sec )     30     30000
    also check if you have done eisk analysis performance tuning
    for :
    batch size - 1000,
    number of web service threads - 5,
    number of background job worker threads - 3,
    rfc timeout for web services/background job worker threads ( min) -  1441.
    Hope this is useful to you.
    Edited by: Yajuvendra Subhash Sonalkar on Nov 7, 2008 9:00 AM

  • Error in template generation...

    Hi,
    I´m doing an app, but when i click in apply template under the component controller, appear this error:
         Status ERROR
    Plugin : com.sap.ide.metamodel.common.services.eclipse
    code=0
    Internal error
       Plugin name: Metamodel Common Services for Eclipse
       Internal error  : com.sap.ide.metamodel.common.services.eclipse
       Class      : com.sap.ide.mmservices.common.eclipse.internal.template.apply.ApplyTemplateWizard$1
       Method     : performFinish()
       Message    : Error in template generation
       Exception  : java.lang.NullPointerException: null
    java.lang.NullPointerException
    at com.sap.tc.mobile.wdlite.ide.servicetemplate.generation.GeneratorHelper.insertCodeInController(GeneratorHelper.java:87)
    at com.sap.tc.mobile.wdlite.ide.servicetemplate.generation.GeneratorHelper.insertCodeInMethod(GeneratorHelper.java:80)
    at com.sap.tc.mobile.wdlite.ide.servicetemplate.generation.ServiceTemplateGeneration.generateCoding(ServiceTemplateGeneration.java:197)
    at com.sap.ide.mmservices.common.eclipse.internal.template.generation.GenerationStartup.generateFragments(GenerationStartup.java:246)
    at com.sap.ide.mmservices.common.eclipse.internal.template.generation.GenerationStartup.generate(GenerationStartup.java:87)
    at com.sap.ide.mmservices.common.eclipse.internal.template.apply.ApplyTemplateWizard$1.run(ApplyTemplateWizard.java:65)
    at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:67)
    at com.sap.ide.mmservices.common.eclipse.internal.template.apply.ApplyTemplateWizard.performFinish(ApplyTemplateWizard.java:62)
    at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:742)
    at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:373)
    at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:616)
    at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:227)
    at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
    at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:938)
    at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3682)
    at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3293)
    at org.eclipse.jface.window.Window.runEventLoop(Window.java:820)
    at org.eclipse.jface.window.Window.open(Window.java:796)
    at com.sap.ide.mmservices.common.eclipse.template.actions.ApplyTemplateAction.run(ApplyTemplateAction.java:28)
    at com.sap.ide.mmservices.common.eclipse.template.TemplateInvoker.startApplyTemplateAction(TemplateInvoker.java:78)
    at com.sap.ide.mmservices.common.eclipse.template.TemplateInvoker.startApplyTemplateWizard(TemplateInvoker.java:34)
    at com.sap.ide.webdynpro.wdexplorer.actions.other.ApplyTemplateAction.run(ApplyTemplateAction.java:48)
    at com.sap.ide.tools.core.viewerfwk.internal.actions.BaseDelegateSingleAction.runInternal(BaseDelegateSingleAction.java:65)
    at com.sap.ide.tools.core.viewerfwk.internal.actions.BaseDelegateSingleAction.run(BaseDelegateSingleAction.java:58)
    at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:256)
    at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:545)
    at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:490)
    at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:402)
    at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
    at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:938)
    at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3682)
    at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3293)
    at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2389)
    at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2353)
    at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2219)
    at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:466)
    at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:289)
    at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:461)
    at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
    at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:106)
    at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:153)
    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:106)
    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:76)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:363)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:176)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:504)
    at org.eclipse.equinox.launcher.Main.basicRun(Main.java:443)
    at org.eclipse.equinox.launcher.Main.run(Main.java:1169)
    at org.eclipse.equinox.launcher.Main.main(Main.java:1144)
    What happend?
    Too, appear this error when i try to import the data object:
    Could be anything bad install?
    Thanks in advance,
    Regards,

    Hi Victor,
    it seems you have a general problem in the way you create your data model. Actually from this point I can not say what is wrong- but if I take all your problems together, you have done something wrong in the creation already - and so the import fails. Check your model prior to import please.
    Regards,
    Oliver

  • Error during context generation

    Dear Friends,
    In interactiveForm UI, when i put adobe form name in Templatesource and try to generate context automatically,
    i get an error message ' Error during context generation ' and an empty context node is created.
    i manually create attributes under that node and populate them in wddoinit method.
    but i dont get those values on PDF output.
    What may be the error ??
    Kindly suggest.

    Hi Otto,
    I want to display data of an internal table in adobr form using web dynpro abap and adobe interactive form.
    my web dynpro abap application is ready and adobe form is also ready.
    when i integrate adobe interactive form on WDA and put form name in TEMPLATESOURCE and press enter
    it throws an error message - 'Error in context generation' and an empty node is generated in WDA.
    on running the application adobe form is displayed but no data is displayed.
    what may be the error ?
    i maintained attributes of node manually but then also no data is displayed.
    that means data binding is not successful.
    what may be the case ???
    kindly suggest

  • Error in Idoc with status 26

    Hi,
    IDOC  showing an error messge when syntex check.
    EDI: Syntax error in IDoc (segment cannot be identified)
    Diagnosis:
    The segment E1EDP19 does not occur at the current level of the basic type ORDERS01 (extension ).
    This error can have several reasons:
    The segment E1EDP19 is assigned to a group whose header segment does not occur.
    The segment E1EDP19 does not exist in the syntax description of the basic type ORDERS01 (extension ).
    The sequence of segments in the group in which the segment appears is incorrect.
    Previous errors ('mandatory' segment or group missing) may be due to this error.
    Please help me....
    Regards,
    Sudha

    Hi,
    I have pasted a portion of my code:
    DATA: BEGIN OF GT_EDIDC OCCURS 0.
            INCLUDE STRUCTURE EDIDC.
    DATA :END OF GT_EDIDC.
    DATA: BEGIN OF GT_EDIDC1 OCCURS 0.
            INCLUDE STRUCTURE EDIDC.
    DATA :END OF GT_EDIDC1.
    DATA: BEGIN OF GT_EDIDD OCCURS 0.
            INCLUDE STRUCTURE EDIDD.
    DATA :END OF GT_EDIDD.
    DATA : BEGIN OF GT_Z1ZPSOBJLOC OCCURS 0.
            INCLUDE STRUCTURE Z1ZPSOBJLOC. ' segment name
    DATA : END OF GT_Z1ZPSOBJLOC.
    * Control Record
    FORM BUILD_CONTROL_RECORD .
      GT_EDIDC-MESTYP = C_MESTYP.
      GT_EDIDC-IDOCTP = C_IDOCTP.
      GT_EDIDC-DIRECT = C_1.
      APPEND GT_EDIDC.
    ENDFORM.                    " built_control_record
    *&      Form  built_data_record
    * Data record
    FORM BUILD_DATA_RECORD .
      LOOP AT GT_Z1ZPSOBJLOC INTO WA_Z1ZPSOBJLOC.
        GT_EDIDD-MANDT = SY-MANDT.
        GT_EDIDD-SEGNAM = C_SEG.
        GT_EDIDD-SDATA = WA_Z1ZPSOBJLOC.
        APPEND GT_EDIDD .
      PERFORM DISTRIBUTE_DATA.
      ENDLOOP.
    ENDFORM.                    " built_data_record
    *&      Form  distribute_data
    * Distribute Data
    FORM DISTRIBUTE_DATA .
      CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE'
        EXPORTING
          MASTER_IDOC_CONTROL            = GT_EDIDC
        TABLES
          COMMUNICATION_IDOC_CONTROL     = GT_EDIDC1
          MASTER_IDOC_DATA               = GT_EDIDD
        EXCEPTIONS
          ERROR_IN_IDOC_CONTROL          = 1
          ERROR_WRITING_IDOC_STATUS      = 2
          ERROR_IN_IDOC_DATA             = 3
          SENDING_LOGICAL_SYSTEM_UNKNOWN = 4
          OTHERS                         = 5.
      CASE SY-SUBRC.
          WHEN 1.
          MESSAGE E004.
        WHEN 2.
          MESSAGE E005.
        WHEN 3.
          MESSAGE E006.
        WHEN 4.
          MESSAGE E007.
        WHEN 5.
          MESSAGE E008.
        WHEN OTHERS.
    * Do Nothing
      ENDCASE.
      COMMIT WORK.
    * Clear IDOC data internal table after use
      CLEAR GT_EDIDD.
      REFRESH GT_EDIDD.
    ENDFORM.                    " distribute_data
    Hope it proves useful.
    Regards,
    Gayathri

  • VLD-1141: Internal error during mapping generation.

    I am getting the "VLD-1141: Internal error during mapping generation" error when deploying a mapping. This mapping was previously working fine. As part of a re-factoring effort, for all the underlying tables and views, we replace 2 existing columns with a new column. All the objects were successfully re-imported and synchronized in the mapping. The mapping is using Mapping Input Parameter, Lookups, Expression Transformations, Splitter, Set Operator, Source & Target Tables. All these transformation were part of the earlier working version of the mapping.
    On doing validation within the mapping, I get a success message followed by 4 warning for the Lookup Condition on key Lookup does not contain a complete unique key. Before the re-factoring effort, I was getting the same 4 warning messages, however the mapping was executing correctly.
    When I do Generate within the mapping, I get the following message:
    Code cannot be generated.
    Click the message tab for details.
    In the Design Center, when I do a validation on the mapping I get the following error:
    VLD-1141: Internal error during mapping generation.
    java.lang.NullPointerException
    at oracle.wh.service.impl.mapping.component.Sequence.getSequenceExpressions(Sequence.java:138)
    at oracle.wh.service.impl.mapping.component.Sequence.doSequenceValidation(Sequence.java:239)
    at oracle.wh.service.impl.mapping.component.entity.EntitySqlDelegate.prepareOutputContext2(EntitySqlDelegate.java:123)
    at oracle.wh.service.impl.mapping.component.entity.EntitySqlDelegate.prepareOutputContext2(EntitySqlDelegate.java:97)
    at oracle.wh.service.impl.mapping.component.entity.EntitySqlDelegate.prepareOutputContext(EntitySqlDelegate.java:78)
    at oracle.wh.service.impl.mapping.generation.WBMappingGenerator.generate(WBMappingGenerator.java:240)
    at oracle.wh.service.impl.mapping.generation.PlSqlGenerationMediator.assembleSetBasedInternal(PlSqlGenerationMediator.java:2108)
    at oracle.wh.service.impl.mapping.generation.PlSqlGenerationMediator.assembleSetBased(PlSqlGenerationMediator.java:2090)
    at oracle.wh.service.impl.mapping.generation.PlSqlGenerationMediator.assemble(PlSqlGenerationMediator.java:541)
    at oracle.wh.service.impl.mapping.generation.WBMappingGenerator.generate(WBMappingGenerator.java:798)
    at oracle.wh.service.impl.mapping.generation.WBMappingGenerator.generate(WBMappingGenerator.java:335)
    at oracle.wh.service.impl.mapping.generation.WBDeployableMappingGenerator.generate(WBDeployableMappingGenerator.java:102)
    at oracle.wh.service.impl.generation.common.WBGenerationService.generateCode(WBGenerationService.java:433)
    at oracle.wh.service.impl.generation.common.WBGenerationService.generateCode(WBGenerationService.java:311)
    at oracle.wh.service.impl.generation.service.WhValidationGenerationTransaction.run(WhValidationGenerationTransaction.java:251)
    Any help in this regards would be appreciated.
    Naval

    Hi,
    I think your mapping is corrupted by converting two columns to one. The owb has always a problem if you change the structure of a table which is bound to a table operator. The way to avoid this is to drop the table operator after changing the table in the table editor and recreate it with the changed table definition.
    Make a test: select the new attribut in the table operator and look left on the configuration window. To which table and attribute it's bound?
    Regards,
    Detlef

  • Error in the generation of check sums of library

    Hello
    I am getting below error when trying to logon to xMII.
    com.sap.engine.services.deploy.container.ExceptionInfo: Error in the generation of check sums of library files of application sap.com/xappsxmiiear in operation startApp.
    This is a new installation on windows 2003 on SQL server.
    Server is up and running clean with out any issues.
    But not able to logon to the home page.
    Regards
    Basis Dude

    Every time I have to manually start service "sap.com/xappsxmiiear " in VA.
    But if I restart system it is not comming up automatically, I have to manually start again.
    Any one had same issue before ?

Maybe you are looking for