Could not create header data delivery 0180000229, system ERP_800

Hi EWM Gurus,
Kinldy help us in resolving the below issue .
When we save the inbound delivery in ERP system , we get the below error in SCM(EWM) system.
System is not creating the inbound delviery notification in SCM due to this error.
ERRORS
1.Could not create header data delivery 0180000229, system ERP_800
2.Application error: Exception in method EXECUTE of Determ. IDR_HDR_044
3.Application error
4.An error occurred during validation of the object     
Thanks in advance
Jayamohan

Hi,
I am receiving the same message. Can you please let me know the solution if you have resolved this one.
Thanks in advance...
Sam

Similar Messages

  • E : could not create header data delivery in EWM system

    Hi Experts.
    Inbound delivery (vl60) from ERP (itu2019s stuck in outbound queue: smq1) to EWM. Application log EWM system below.
    ERP/EWM Interface Appl log
    E: could not create header data delivery < dly number >, system < BS System >  (Msg id: /SCWM/ERPINTEGRATOIN012)
    S: supply chain unit < SU NO > found for erp warehouse number < WM NO>
    S: EWM Document type INB for ERP delivery type EL found.
    W: No date/time type found for ERP date/time IDDOCUMENT.. (Msg id: /SCWM/ERPINTEGRATOIN054)
    W: No date/time type found for ERP date/time IDINTRANS.
    W:No date/time type found for ERP date/time IDVERSION.
    S: Date/time type TDELIVERY found for ERP date/time WSHDRLFDAT
    S: Business partner <BP NO > for ERP Partner <P NO> found.
    S: NO document found
    E: application error
    E:an error occurred during validation of object.
    POST-Processing Framework Appl log
    Processing /SCDLT/TS_TRANSFER is started
    messages for doc:IDR < dly no >
    Started Transition successfull
    preparation for database access successfull
    start access to document flow successfull
    step determination successfull
    step proecssing successfull
    start checking whether action 022 successfull
    start data transfer successfull
    start checking whether action 020 in ERROR
             Action not executable
            config. error method CHECK of validation PDI_HDR_ERP_PARTNER Not implemented
            config. error method EXECUTE of validation PDI_HDR_ERP_PARTNER Not implemented
             error in step processing
            action 020 not allowed
            transition failed
           Action not be successfully executed
    could any one guide me to solve the issue.
    Kind regards
    Edited by: Rahman Abdul on Jun 20, 2011 9:33 PM
    Edited by: Rahman Abdul on Jun 20, 2011 9:33 PM
    Edited by: Rahman Abdul on Jun 20, 2011 9:34 PM

    Hello,
    In SPRO, you need to maintain the entries for:
    No date/time type found for ERP date/time IDDOCUMENT.. (Msg id: /SCWM/ERPINTEGRATOIN054)
    W: No date/time type found for ERP date/time IDINTRANS.
    W:No date/time type found for ERP date/time IDVERSION.
    This can be found in EWM > EWM > Interfaces > ERP Integration > Delivery Processing > Map Date Types from ERP System to EWM.
    Cheers,
    Paulo

  • Could not create Delivery in VL01N

    Hi
    Previously our Client use to sell some Trading type of material to their customer on Third Party Scenario basis....ie) They place the order with Vendor, inturn he directly send it to the Customer....
    Now Our Client wants that material has to come to his W/H and Customer should come to his W/H and do the inspection and has to take the delivery.
    ie) Based on Customer PO, he will create Sales order
        Based on Item catogary  BANC and Order Type OR, the Item catogary TAB will be Triggered and Based on   Item catogary TAB, the Schd.Line catogary CB will be triggered....and Based on Schd.Line catogary CB the PR will be automatically triggered with Acc.***.Catogary "E'....this will be converted in to PO and for the same GR will be done and the stock is updated as Special Stock as "SALE ORDER STOCK"
    My problem is if I Create Delivery in VL01N to the customer based on that Sale Order...The Warning mesage is coming as  "No Schedule Lines Due for delivery up to Selected Date" and I could not create the delivery...
    It will be highly appreciated if anybody can help me in this regard
    Regards
    S.Baskaran

    Hi baskaran,
    Check the Delivery Date of that order( In schedule lines u can find the Delivery Date) and check the VL01N Transaction code delivery date
    these two should be same.
    Regards..
    Praveen Kumar.D

  • Ad Hoc Query - While executing - System could not read any data

    Hello Techies,
    When I am excuting my Ad hoc query - for one personnel number for which Infotype 28 subtype 0001 has been maintained
    But system is throwing this error -
    System could not read any data
    Message no. AQ_AD_HOC226
    Diagnosis
    There is no data available for the specified selections.
    System response
    The results list in the lower part of the screen still displays the last list to be created.
    Please let me know why does it happening ?
    Thanks
    Jaydeep

    It was an date selection issue - as while executing the Ad hoc query - the reporting date is today -
    changed to all

  • Could not create JCOClientConnection for logical System: MUSA_MODEL_DATA

    Hi,
    I am facing a big problem...I have created WebDynpro Application & when I am running that application from WebDynpro, it's showing the page but giving me the error message as:-
    Could not create JCOClientConnection for logical System: MUSA_MODEL_DATA - Model: class com.bcone.bcool.musa.model.MUSABAPI. Please assure that you have configured the RFC connections and/or logical system name properly for this model!
    What do I do? what connections I have to check?
    pls help.

    Hey if you are connecting to SAP system making use of adaptive RFC model you hav to create logical systems(JCOs).So while creating the model you have to specify 2 logical system names(one for model data or on for the meta data).If you have not created the JCOs or if the JCOs are not active  then you are going to get this type of error.To activate those JCOs ask your administrator to activate the JCO for metadata of your application.If you are having proper credentials then log on to portal
    System administration>webdynpro>expand the local directory>select your project>click on maintain JCOs and activate the JCO for the metadata.
    Or else change the logical system in your application.

  • Java system error: Server repository could not create function template

    Hi, Our BI person is trying to  publish/broadcast a query to the PRODCTION  portal, she gets the below error message.  I am
    attaching the defaulttracelog file
    "Java system error: Server repository could not create function template for RSRD_X_PRODUCE_PROXY caused by: com.sap.mw.jco.JCO$Exception: (103)"
    <!LOGHEADER[START]/>
    <!HELP[Manual modification of the header may cause parsing problem!]/>
    <!LOGGINGVERSION[1.5.3.7185 - 630]/>
    <!NAME[./log/defaultTrace.trc]/>
    <!PATTERN[defaultTrace.trc]/>
    <!FORMATTER[com.sap.tc.logging.ListFormatter]/>
    <!ENCODING[UTF8]/>
    <!FILESET[8, 20, 10485760]/>
    <!PREVIOUSFILE[defaultTrace.7.trc]/>
    <!NEXTFILE[defaultTrace.9.trc]/>
    <!LOGHEADER[END]/>
    #1.5 #002264F9350800600000022F000019C000048E9B91EF3AB3#1282698726384#com.sap.security.core.persistence#sap.com/irj#com.sap.security.core.persistence#J2EE_GUEST#0##n/a##4dba6f30af8111df934c002264f93508#SAPEngine_Application_Thread[impl:3]_35##0#0#Error#1#/System/Security/Usermanagement#Java#An exception was thrown in the UME/ABAP user management connector that was caused by unavailability of the RFC communication with the backend system: "". ##An exception was thrown in the UME/ABAP user management connector that was caused by unavailability of the RFC communication with the backend system: "". #1#Connect to SAP gateway failed
    Connect_PM  TYPE=A ASHOST=localhost SYSNR=00 GWHOST=localhost GWSERV=sapgw00 PCS=1
    LOCATION    CPIC (TCP/IP) on local host with Unicode
    ERROR       partner '127.0.0.1:sapgw00' not reached
    TIME        Tue Aug 24 21:12:06 201
    RELEASE     700
    COMPONENT   NI (network interface)
    VERSION     38
    RC          -10
    MODULE      nixxi.cpp
    LINE        2823
    DETAIL      NiPConnect2
    SYSTEM CALL connect
    ERRNO       10061
    ERRNO TEXT  WSAECONNREFUSED: Connection refused
    COUNTER     56
    #1.5 #002264F93508006000000230000019C000048E9B91EF47C8#1282698726384#com.sap.engine.services.monitor.mbeans.Monitor#sap.com/irj#com.sap.engine.services.monitor.mbeans.Monitor#J2EE_GUEST#0##n/a##4dba6f30af8111df934c002264f93508#SAPEngine_Application_Thread[impl:3]_35##0#0#Error##Plain###Caller J2EE_GUEST not authorized, user J2EE_GUEST is not available from user management, reason: com.sap.security.api.NoSuchUserException:USER_AUTH_FAILED: User account for logonid "J2EE_GUEST" not found!#
    #1.5 #002264F93508006000000231000019C000048E9B91EF4CD5#1282698726384#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##4dba6f30af8111df934c002264f93508#SAPEngine_Application_Thread[impl:3]_35##0#0#Error##Plain###com.sap.engine.services.jmx.exception.JmxSecurityException: Caller J2EE_GUEST not authorized, user J2EE_GUEST is not available from user management, reason: com.sap.security.api.NoSuchUserException:USER_AUTH_FAILED: User account for logonid "J2EE_GUEST" not found!
         at com.sap.engine.services.jmx.auth.UmeAuthorization.checkMBeanPermission(UmeAuthorization.java:63)
         at com.sap.engine.services.jmx.JmxServerFrame.checkMBeanPermission(JmxServerFrame.java:98)
         at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.unregisterMBean(MBeanServerSecurityWrapper.java:395)
         at com.sap.engine.services.jmx.ClusterInterceptor.unregisterMBean(ClusterInterceptor.java:1327)
         at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.unregisterMBean(MBeanServerInterceptorChain.java:258)
         at com.sap.engine.services.monitor.mbeans.Monitor.unregister(Monitor.java:106)
         at com.sap.engine.library.monitor.impl0.AbstractMonitorNode.remove(AbstractMonitorNode.java:154)
         at com.sap.engine.library.monitor.impl0.MonitorObjectFactory.uninstallMonitorNode(MonitorObjectFactory.java:483)
         at com.sap.engine.services.monitor.install.MonitorInstaller.uninstallMonitors(MonitorInstaller.java:595)
         at com.sap.engine.services.monitor.install.MonitorInstaller.uninstallMonitors(MonitorInstaller.java:581)
         at com.sap.engine.services.monitor.install.MonitorInstaller.uninstallMonitors(MonitorInstaller.java:581)
         at com.sap.engine.services.monitor.install.MonitorInstaller.uninstallMonitors(MonitorInstaller.java:581)
         at com.sap.engine.services.monitor.install.MonitorInstaller.uninstallMonitors(MonitorInstaller.java:581)
         at com.sap.engine.services.monitor.install.MonitorInstaller.uninstallMonitors(MonitorInstaller.java:581)
         at com.sap.engine.services.monitor.install.MonitorInstaller.uninstallMonitors(MonitorInstaller.java:581)
         at com.sap.engine.services.monitor.install.MonitorInstaller.uninstallMonitors(MonitorInstaller.java:568)
         at com.sap.engine.services.monitor.server.ApplicationLifeCycleImpl.applicationStopped(ApplicationLifeCycleImpl.java:52)
         at com.sap.engine.services.monitor.deployment.MonitorDeploymentContainer.commitStop(MonitorDeploymentContainer.java:630)
         at com.sap.engine.services.deploy.server.application.StopTransaction.commonCommitFinished(StopTransaction.java:244)
         at com.sap.engine.services.deploy.server.application.StopTransaction.commitCommon(StopTransaction.java:290)
         at com.sap.engine.services.deploy.server.application.StopTransaction.commitLocal(StopTransaction.java:278)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:374)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:132)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:250)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.stopApplicationLocalAndWait(DeployServiceImpl.java:4569)
         at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.stopApplicationLocalAndWait(DeployCommunicatorImpl.java:628)
         at com.sap.portal.prt.sapj2ee.SAPJ2EEPortalRuntime$2.run(SAPJ2EEPortalRuntime.java:602)
         at java.security.AccessController.doPrivileged(Native Method)
         at java.lang.ClassLoader$NativeLibrary.load(Native Method)
         at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1586)
         at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1482)
         at java.lang.Runtime.load0(Runtime.java:737)
         at java.lang.System.load(System.java:811)
         at com.sapportals.wcm.service.fsmount.FSMountService.loadDLL(FSMountService.java:736)
         at com.sapportals.wcm.service.fsmount.FSMountService.<clinit>(FSMountService.java:796)
         at java.lang.Class.forName0(Native Method)
         at java.lang.Class.forName(Class.java:219)
         at com.sapportals.wcm.repository.runtime.CmConfigurationProvider.convertGS(CmConfigurationProvider.java:637)
         at com.sapportals.wcm.repository.runtime.CmConfigurationProvider.convertServiceConfig(CmConfigurationProvider.java:601)
         at com.sapportals.wcm.repository.runtime.CmConfigurationProvider.readConfiguration(CmConfigurationProvider.java:205)
         at com.sapportals.wcm.crt.CrtSystemImpl.createComponentManager(CrtSystemImpl.java:108)
         at com.sapportals.wcm.repository.runtime.CmSystem.startUp(CmSystem.java:202)
         at com.sapportals.wcm.repository.runtime.CmSystem.getInstance(CmSystem.java:164)
         at com.sapportals.wcm.repository.runtime.CmAdapter.getResourceImpl(CmAdapter.java:974)
         at com.sapportals.wcm.repository.runtime.CmAdapter.getResource(CmAdapter.java:192)
         at com.sapportals.wcm.portal.service.KMServiceImpl.afterInit(KMServiceImpl.java:249)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.__initServiceInstanceStep2(PortalServiceItem.java:877)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.startServices(PortalServiceItem.java:1118)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.startLoadOnStartupServices(PortalAppBroker.java:1707)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.start(PortalAppBroker.java:1662)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.startNonCoreApplications(PortalAppBroker.java:1592)
         at com.sapportals.portal.prt.runtime.Portal.init(Portal.java:422)
         at com.sapportals.portal.prt.core.PortalCoreInitializer.coreInit(PortalCoreInitializer.java:54)
         at com.sapportals.portal.prt.dispatcher.PortalInitializer.<init>(PortalInitializer.java:129)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doSetupPortalInitializer.run(Dispatcher.java:161)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.initDispatcher(Dispatcher.java:361)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.access$000(Dispatcher.java:42)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$InitRunner.run(Dispatcher.java:114)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.init(Dispatcher.java:394)
         at com.sap.engine.services.servlets_jsp.server.runtime.context.WebComponents.addServlet(WebComponents.java:139)
         at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadInitializer.loadServlets(ApplicationThreadInitializer.java:386)
         at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadInitializer.run(ApplicationThreadInitializer.java:110)
         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:104)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
    #1.5 #002264F93508005C0000042300002CF00004939AAEE9AEB7#1288192475655#com.sapportals.wcm.repository.manager.reporting.RPRepositoryManager#sap.com/irj#com.sapportals.wcm.repository.manager.reporting.RPRepositoryManager#J2EE_GUEST#0##n/a##c7d00e00e1dc11dfa36d002264f93508#SAPEngine_Application_Thread[impl:3]_29##0#0#Error##Plain###setting initial ACL on /reporting_backend/reports/System Administration/CM Store/cm.crawlcontent - com.sap.security.api.NoSuchRoleException: Role with uniqueName system_admin_role not found!
         at com.sap.security.core.imp.RoleFactory.getRoleByUniqueName(RoleFactory.java:1783)
         at com.sapportals.wcm.repository.manager.reporting.RPRepositoryManager.getRoles(RPRepositoryManager.java:1474)
         at com.sapportals.wcm.repository.manager.reporting.RPRepositoryManager.syncReportResources(RPRepositoryManager.java:1334)
         at com.sapportals.wcm.repository.manager.reporting.RPRepositoryManager.initBackend(RPRepositoryManager.java:489)
         at com.sapportals.wcm.repository.manager.reporting.RPRepositoryManager.getResource(RPRepositoryManager.java:581)
         at com.sapportals.wcm.repository.RMAdapter.getResource(RMAdapter.java:228)
         at com.sapportals.wcm.repository.runtime.CmAdapter.findResource(CmAdapter.java:1349)
         at com.sapportals.wcm.repository.runtime.CmAdapter.findManagerAndResource(CmAdapter.java:1322)
         at com.sapportals.wcm.repository.runtime.CmAdapter.getResourceImpl(CmAdapter.java:979)
         at com.sapportals.wcm.repository.runtime.CmAdapter.getResource(CmAdapter.java:192)
         at com.sapportals.wcm.service.reporting.ReportingService.localConfigure(ReportingService.java:294)
         at com.sapportals.wcm.service.reporting.ReportingService.startUpImpl(ReportingService.java:74)
         at com.sapportals.wcm.service.AbstractService.start(AbstractService.java:167)
         at com.sapportals.wcm.crt.CrtThreadSafeComponentHandler.tryToStart(CrtThreadSafeComponentHandler.java:247)
         at com.sapportals.wcm.crt.CrtThreadSafeComponentHandler.handleLookup(CrtThreadSafeComponentHandler.java:109)
         at com.sapportals.wcm.crt.CrtComponentManager.lookup(CrtComponentManager.java:322)
         at com.sapportals.wcm.crt.CrtComponentManager.lookupChildComponent(CrtComponentManager.java:403)
         at com.sapportals.wcm.crt.CrtContainerManager.lookupComponent(CrtContainerManager.java:44)
         at com.sapportals.wcm.crt.CrtSystemImpl.lookupComponentByUri(CrtSystemImpl.java:131)
         at com.sapportals.wcm.crt.CrtComponentManager.startUp(CrtComponentManager.java:278)
         at com.sapportals.wcm.crt.CrtSystemImpl.startUpComponentManager(CrtSystemImpl.java:166)
         at com.sapportals.wcm.repository.runtime.CmSystem.startUp(CmSystem.java:227)
         at com.sapportals.wcm.repository.runtime.CmSystem.getInstance(CmSystem.java:164)
         at com.sapportals.wcm.repository.runtime.CmAdapter.getResourceImpl(CmAdapter.java:974)
         at com.sapportals.wcm.repository.runtime.CmAdapter.getResource(CmAdapter.java:192)
         at com.sapportals.wcm.portal.service.KMServiceImpl.afterInit(KMServiceImpl.java:249)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.__initServiceInstanceStep2(PortalServiceItem.java:877)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.startServices(PortalServiceItem.java:1118)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.startLoadOnStartupServices(PortalAppBroker.java:1707)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.start(PortalAppBroker.java:1662)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.startNonCoreApplications(PortalAppBroker.java:1592)
         at com.sapportals.portal.prt.runtime.Portal.init(Portal.java:422)
         at com.sapportals.portal.prt.core.PortalCoreInitializer.coreInit(PortalCoreInitializer.java:54)
         at com.sapportals.portal.prt.dispatcher.PortalInitializer.<init>(PortalInitializer.java:129)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doSetupPortalInitializer.run(Dispatcher.java:161)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.initDispatcher(Dispatcher.java:361)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.access$000(Dispatcher.java:42)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$InitRunner.run(Dispatcher.java:114)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.init(Dispatcher.java:394)

    Go to visual admin -> server -> services -> JCO RFC provider.
    Check the RFC that connects to the BI Abap.
    Its reporting the J2EE_GUEST user in the SAP with the system nr 00.
    Is this BI java portal?
    Is the java portal a addon to Abap or having seperate SID?
    Check the connection definitions are correct and the gateway is running.

  • Could not find any data to display - how to modify system message

    Hi,
    We created an exception report in the Web Application Designer.
    If there are no exceptions (so there is no data to display) the following standard system message is shown:
    Could not find any data to display. This might be due to the current selection of variable or filter values
    We would however like to modify/remove this message.
    How can this be done?
    Thanks
    Dave

    Hi,
    Please check the link:
    /people/marc.bernard/blog/2008/10/10/how-to-filter-messages-created-by-bi-ip-planning-functions-and-sequences
    Please check the Q&A section of above weblog which mentions about
    function module RRMS_MESSAGE_HANDLING which could be helpful.
    Please also refer to SDN thread:
    Re: WAD - messages - message type
    Regards,
    Amit

  • Error 25109 : The install program could not create the config data store. Is this a know issue with a solution?

    Hi I cant install the Management Console.
    I keep getting
    Error 25109 : The installation program could not create the configuration data store. Please see the installation log for more info.
    Has someone come across this problem before?
    I am using
    MS Server 2008 Std x86
    SQL Server 2005 SP2 Std x86
    MDOP 2008 R2
    APP-V 4.5
    Please can someone help.
    Thanks

    I'm running into the same problem myself, I have an almost identical setup.
    Trying to do a clean install of App-V Management Server 4.5 from the MDOP 2008 R2 CD.
    Server OS: Windows Server 2008 Enterprise SP1 (Has WDS and IIS installed (IIS 6 Management Compatibility too), as well as .Net 3.5 SP1 Framework)
    Database: Microsoft SQL Server 2005 Enterprise (Version 9.00.3068.00) (Note: SQL server is running on a different server than the server App-V is being installed on.)
    Installer gets to the point where it starts creating the database than dies, reporting a 25109 error.
    Checked out the logfile the installer created, here's a snip of the last few lines before is starts rolling back the install:
    1
    [2008-12-23 15:58:35] (2284:3084) SQL state: ``01000'', Native: 0, Text: ``[Microsoft][ODBC SQL Server Driver][SQL Server]<<< CREATED TRIGGER dbo.TR_U_SYSTEM_OPTIONS >>>''. 
    2
    [2008-12-23 15:58:36] (2284:3084) SQL state: ``42000'', Native: 18058, Text: ``[Microsoft][ODBC SQL Server Driver][SQL Server]Failed to load format string for error 16873, language id 1033.  Operating system error: 122(The data area passed to a system call is too small.). Check that sqlevn70.rll is installed in C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\Resources\1033, where 1033 is the language ID of US English, or the appropriate folder for the locale in use. Also check memory usage.''. 
    3
    [2008-12-23 15:58:36] (2284:3084) SQL state: ``01000'', Native: 3621, Text: ``[Microsoft][ODBC SQL Server Driver][SQL Server]The statement has been terminated.''. 
    4
    [2008-12-23 15:58:36] (2284:3084) ::SQLExecDirectW error 0xffffffff. 
    5
    [2008-12-23 15:58:36] (2284:3084) Failed to execute SQL ``/* ------------------------------------------------------------------------- *\ 
    6
        Copyright (c) Microsoft Corporation.  All rights reserved. 
    7
    8
        Description: 
    9
            This script creates all user-defined messages. 
    10
    11
            The types of messages allowed (and their severities) are: 
    12
            FATAL   - SQL Server Severity = 17; ours = 1 
    13
            ERROR   - SQL Server Severity = 16; ours = 2 
    14
            WARNING - SQL Server Severity = N/A; ours = 3 
    Can anyone help me shed some light on what's going on here?

  • Error: Could not create system variants in multiple client system

    Hello ,
    I am trying to make changes to the variant CUS&_FINAL_AT in se38 , but the error message is coming while saving .
    error :Could not create system variants in multiple client system
    Could you please help?

    Hi Huynh,
    Did you ever figure out how to add custom fields to an e-recruit infoset?  I need to so same and would love a heads up on how.
    Leena

  • SRM: Create Contact Person Could not create user; contact your system admin

    Hi All,
    First, I am not sure this question should be posted here, or SRM General. From my point of view, here is more suitable.
    Our Problem:
    Activity "Create Contact Person With Reference" error with message:
    Step to reproduce:
    1. Login to SRM JAVA as super administrator
    2. Open tab "SRM Administration"
    3. Using the current query, search for Business-Partner no: 30000725
    4. Press "Create Contact Person with Reference"
    5. Fill all required fields, tick "Is contact person" checkbox
    6. Put: /SAPSRM/SUPPLIER as Role
    7. Save
    The following Message appear:
    Could not create user; contact your system administrator
    SPML Service error: Error reading request status.  Display Help
    Contact Person 2000000214 Created Successfully for BP 30000725  Display Help
    E-mail was sent
    The first error is intriguing. The username & password is created successfully in ABAP System (Our UME is in ABAP).
    QUESTIONS:
    1. What cause this problem? How to trace the error?
    2. We want the user have portal role automatically. How to achieve that?
    Thank you for any responses and helps.
    SRM ABAP Version:
    SRM_PLUS     700     0009     SAPKIBK209     SRM_PLUS for mySAP SRM
    SRM_SERVER     700     0009     SAPKIBKV09     SRM_SERVER
    SAP_ABA     701     0007     SAPKA70107     Cross-Application Component
    SAP_BASIS     701     0008     SAPKB70108     SAP Basis Component
    PI_BASIS     701     0007     SAPK-70107INPIBASIS     Basis Plug-In
    SRM JAVA Version:
    SRM JAVA: Release 7 SP Level 9.0
    BP SRM: Release 7 SP Level 9.0
    Edited by: Nur Agus Suryoko on Mar 11, 2011 11:36 AM
    Version information added

    Hi Fernando,
    Can you please tell me how you resolved this issue ??
    Regards,
    Adren

  • The system could not create any outputs for mv type 561

    Hi,
    I tried to print out a goods receipt others in MIGO and i received "The system could not create any outputs" when i tick on output control. I tried to follow the steps in How to print the material document in MB1C movement 561 I stuck at step 4 where i cannot find MvT 561. Please help
    Chk your setting as below to get GR print out.
    . Maintain the Printer Name in MM->Inv Mgmt and Phy Inv->Print Control-> Gen Settings-> Printer Setting Enter the local printer where you want to print your Goods posting document
    2. Ensure that in MM->Inv Mgmt and Phy Inv->Print Control->Gen Settings->Item Print Indicator, 1 stands for Matl Doc print out
    3. In MM->Inv Mgmt and Phy Inv->Print Control->Gen Settings->Print Version, maintain Print Version 2
    4. In MM->Inv Mgmt and Phy Inv->Print Control->Maintain Print Indicator for Goods Receipt/GI/Transfer Posting Documents
    Here for Particular mvt type 101,201,121,311,313,501,521,561 etcu2026 Maintain the Print item as 1--Material document printout
    5. In MM->Inv Mgmt and Phy Inv->Output Determination->Maintain Output Types, for the Output types WE01, WE02 and WE03, ensure the following--
    Select the particular Output type then goto Details
    a. Default Values: Dispatch Time is 3 or 4 as per reqmt. and Transmission medium is 1
    b. Print Parameter is 7
    6. In MM->Inv Mgmt and Phy Inv->Output Determination->Printer Det->Printer Determination by Plant/Str Loc , Maintain the Output device for all your Plants
    7. Go to MN21, for Tr Type WE, Print Version 3, maintain Print Item as 1.
    Now the settings are ready for Printing Material doc
    8. While doing MIGO, ensure that in General Tab, you get "3 Collective Slip" beside the Print Indicator and you tick mark the field.
    9. Now depending on the setting in 5a, the Matl doc is printed. If it is 3, you have to print it using MB90. If it is 4, it is printed immediately.

    issue is resolved

  • Could not create JCOClientConnection for logical System: WD_MODELDATA_DEST

    Hi ,
    I am getting the below error:
    Could not create JCOClientConnection for logical System: WD_MODELDATA_DEST - Model: class com.eligibilitymodel1.EligibilityModel1. The SSO ticket needed for authentication to WD_MODELDATA_DEST has expired. Close all applications and logon anew!
    Regards
    Anumit

    Anumit,
    when will you get this error?
    if you are getting this while using adaptive rfc model follow this link Could not create JCOClientConnection for logical System:
    if it doesnot work
    try to reimport the certificate or restart the server
    Thanks
    Bala Duvvuri

  • Could not create JCOClientConnection for logical System:

    Hi,
    I am facing a wierd problem in using the JCO destinations.
    I created a page where it is using some JCO destinations say SAP_R3_HumanResources.
    when i open the page it is working for the first time .without closing the page if i open the same page again it is giving the following error
    Error connecting using JCO.Client: null
    Error connecting using JCO.Client: null
    Pernr:Could not create JCOClientConnection for logical System: SAP_R3_HumanResources - Model: class com.swissre.CustomData. Please assure that you have configured the RFC connections and/or logical system name properly for this model!
    Please let me know how to solve this issue
    Thanks
    Bala Duvvuri

    Hi Bala,
    It seems that this is a custom webdynpro application which when executed causes such problem.  This might be due to JCO connection not released back to the pool.
    Please refer to the following threads and that might be helpful. 
    Re: JCO Connection close
    How to close a model object connection for Adaptive RFC?
    You might have to call disconnectIfAlive method on your model.
    Regards,
    Jigar

  • Could not create JCOClientConnection for logical System: SAP_R3_HumanResour

    Hi,
    For all the standard ESS (sap.com) the JCo connection used is SAP_R3_HumanResources .
    All the applications are working fine.
    I am trying to add a test Component in one of the (sap.com~eepro) for testing a standard BAPI call for getting user details.
    I have used the same Model and the same SAP_R3_HumanResources destination name.
    But i get the following error when i try to execute the standard BAPI_USER_GETDetails (non - HR).The other applications for standard components (Vc ) work when i run the application.
    My question here is why a custom , local webdynpro when try to make a RFC call using the running already existing JCO connection throws such error.
    How could this be solved.Note the connection is running and working fine for all the ESS webdynpros!!
    Error:
    Could not create JCOClientConnection for logical System: SAP_R3_HumanResources - Model: class com.test.hr.model.Test. Please assure that you have configured the RFC connections and/or logical system name properly for this model!
    Your experience would be worthy enough.
    Regards,
    Swathi

    Hi Swathi,
    Here are some suggestions to trace down to the actual problem.
    1) First check if all users are having this issue. (All other applications working and only one application giving problem)
    2) If no, then take list of users having this problem and check their portal and SAP accounts
    3) If yes, then concentrate on testing the JCo connections and the user account mapped in JCo settings
    Possible things u can check is user's portal account (locked or not), SAP account (lock or validity), pernr mapped (validity), JCo user (check for lock), ping and test JCo connections
    If none of them are issue, check the logs if there are any trace for this issue. I believe there must be certainly one. That can help u going further.
    Regards,
    Harini S

  • Could not create a valid GL date rejection for PA transactions to GL

    Hi All,
    PRC: Interface Labor Costs to General Ledger has the Rejection "Could not create a valid GL date".
    I have verified all Periods are Opened. Still there is a a rejection.
    Thanks,
    Praveen

    Praveen Bharadwaj wrote:
    Hi All,
    PRC: Interface Labor Costs to General Ledger has the Rejection "Could not create a valid GL date".
    I have verified all Periods are Opened. Still there is a a rejection.
    Thanks,
    PraveenPlease see these docs.
    PAGGLT, PASGLT gives 'Could Not Create A Valid GLDate', even when GL data is re-open. [ID 330874.1]
    PRC: Interface Labor Costs to GL (PALDLC) Will Not Interface, CDL.Batch_Name Is Null [ID 437301.1]
    PALDLC and PASDUC Error - Could Not Create A Valid GL Date For Provider [ID 338330.1]
    Distribute Labor Cost Exception-Could Not Create A Valid GL Date [ID 418675.1]
    PAXACCPB - PRC: Create Accounting Gets Error 95325 Gl Date Not An Open Or Future Enterable Period [ID 951452.1]
    Thanks,
    Hussein

Maybe you are looking for