Source message Message Type: POR does not exist in software component versi

HI All,
I have a .tpz file exported from an SRM 4.0 PI system which i have imported in SRM 7.0 ECC 6.0 PI.
I have imported the .tpz file through the import through "client" option.
I am able to open all the objects but i am not able to open the Message mappings.....
It is throwing the following error:
Source message Message Type: PurchaseOrderRequest does not exist in software component version xx_xx_PO_PROCESSING, 1.0 of xx.com Check whether software component version xx_xx_PO_PROCESSING, 1.0 of xx.com is in the Enterprise Services Repository. Import this or a newer version if necessary.
This needs to resolved very urgently...
Kindly help...
Thanx in advance..
Nandan

Hi,
I'd say you need to import some other SWCV which has all the IDOC typos you use in your scenario
probably this is a prerequisite for importing your SWCV
I don't think this is related to sp level or anything like that
it's just that SWCV is missing
Regards,
Michal Krawczyk

Similar Messages

  • ESRfor PI 7.1) source message idoc does not exist in software componet

    Hi ,
    When using the sap predelivered integration content in the repository the above error (ESR ( for PI 7.1)  error : source message idoc does not exist in software component version id) is coming while opening the message mapping interface. Is it due to some content missing or a sp level mismatch ?
    Thanks
    Sri

    Hi,
    I'd say you need to import some other SWCV which has all the IDOC typos you use in your scenario
    probably this is a prerequisite for importing your SWCV
    I don't think this is related to sp level or anything like that
    it's just that SWCV is missing
    Regards,
    Michal Krawczyk

  • Production scheduling profile for production order type 10 does not exist – SAP Message No.10085

    When i tried to make confirmation for Production Order through CO15 transaction , i receive the following error message “ Production scheduling profile for production order type 10 does not exist – SAP Message No.10085 “
    In Work Scheduling view, Production Scheduling Profile is maintained as per OPKP only.
    How to check whether production scheduling profile is maintained for relevant order type 10.
    To do this , i went to OPKP & KOT2_OPA transactions but i don’t know how to check. I guide me through with a screen shot.
    Also, pls explain about  “Order Type 10” and how it is linked with material and order execution.
    Looking for a detailed explanation with screen shots , since i am new to SAP.
    Thanks With Regards,
    Dinesh Kumar V.

    Hello Dinesh,
    Please check the order type dependent parameter in OPL8 here you will get the Substitute Scheduler
    Then go to OPCH and check valid production scheduling profile assign here as per OPKP to your production scheduler for your plant.
    Production order have Order category as 10  Process Order  40 in standard SAP you can check this in OPJH.
    Best Regards,
    R.Brahmankar

  • Command $TAB : message Transaction $TAB does not exist Message no. S#343

    when i use the command $TAB to refresh the buffers the system gives me the message
    " Transaction $TAB does not exist
    Message no. S#343 "
    In some systems it works as intended. How can i correct that position.

    try /$TAB

  • S_ALR_87011774 returns the message u0093Program 9PSM does not exist

    Hi Dear Gurus,
    I have been given a   task to add a t-code to a role and i did that but when the user execute the transaction
    the transaction S_ALR_87011774 returns the message “Program 9PSM does not exist.
    how to fix it.
    i did run the SU53 report and it says
    activity : 03
    co trasaction  rks
    and these two are maintained in the object.
    please help me how to resolve this issue.
    Kind Regards,
    vamsi,

    as far as I can tell, it is not actually the program that does not exist, but the report group.
    when changes have been made to the layout, it is sometimes necessary to regenerate them.  this can be done through GR52.
    I'm curious to know what the SU53 will display for the user who's executing the transaction, because I don't find a reason to assume this is related to authorizations?
    for more info on report groups, have a look [over here|http://help.sap.com/saphelp_47x200/helpdata/en/5b/d2308343c611d182b30000e829fbfe/frameset.htm|sap help]
    it may have something to do with logging on in a different language than the report was setup to be displayed in?
    If reports are to be available in several languages,
    you must define the languages concerned in Customizing.
    For more information, see the Implementation Guide (IMG)
    for Special Purpose Ledger under Information System ->
    Define Report Writer Languages.
    Edited by: Dimitri van Heumen on Feb 21, 2008 11:36 AM (messing up the layout...)

  • Error message "Location XYZ does not exist for item1" Message no. BBP_PD047

    Hi all,
    When i do confirmation for PO in SRM, the system gives error message "Location XYZ does not exist for item1" when i enter Location for the plant thought the Location is mapped to Plant in ECC system. System shows error when i click on check button,  it allowing me add locations.
    This is happening when confirming the PO line items having differernt plants and it is not happeing all the time, sometimes it does't work. I
    f all the line items have same Plants, there is no issue.
    I am not able to understand why it is working some time and not working other time.(message no: BBP_PD047 in SLG1)
    can some one help me in understanding this?
    Thanks,
    Ravi

    Is this thread still valid? If not, please close the thread.
    If so, as no response has been submitted, please rephrase your question and/or provide further information to describe your requirement.
    Thanks
    Jason
    SDN SRM Moderator Team

  • Message Entry MK001 does not exist in T499S-

    Hi,
    Would like to seek for your help as i have try to configure new fix
    asset location in T-code:OIAS and successfully save it however when i
    select the new location in the time dependent tab in the asset master
    it prompt me an error message Entry MK001 does not exist in T499S-
    check your entry.
    Please advise whether i have miss out the step or the SAP system bug
    and I am using Sap R/3 version 4.7 level 31 patch.
    Please advise.
    thank you.

    Hi,
    Please check the below thread, in which i have specified few SAP notes, which might sort your issue.
    [AS02 : Location entry not possible in Timedependent tab;
    Please check the attached notes too.
    Thanks,
    Srinu

  • Can't Delete A Message: Destination mailbox does not exist

    Got a spam email today and Mail won't let me delete it. Clicking Delete grays the message, but it won't move to the Trash. If I try and drag it manually, I get the error message "destination mailbox does not exist."
    And it's right: the To: address is a fake one and NOT one of my accounts.
    Anyone know how in the world I can get rid of this message?

    Hi Ernie,
    Thanks for your help. In the end, my solution was to delete the GMail account completely from Mail.app, recreate it and let it synchronise my mail back from Google (I have Mail.app set to leave messages on the server, for GMail). I now of course have all the 'correct' emails back in Mail.app, without the ones I could not delete.
    I can tell you, though, that there were indeed no other files in the old INBOX.mbox folder other than the ones you mentioned. What other files might there have been?

  • "Port 'A000000001' of type ALE does not exist"

    Hi Guys,
    I am getting the following error message when I am trying to activate the Source System in RSA1. This connection is self connection to BW system.
    "Port 'A000000001' of type ALE does not exist"
    When I go and try to create the port in WE21 for the port "A000000001". I am getting the following error message.
    Choose another name! Name Range reserved.
    As far as I know that the source system is pointing to 'A000000001" port which I could not find in WE21. So how do i point this particular port to this system. Is there any way where I can go ahead and change the table entries.
    Waiting for your suggestions.
    Regards
    Pooja

    Thanks for update.
    I am the one responsible for al.
    I went to we21 under TRFC type a port XXXXXXXXX9 alreday exists pointing to the logical client rfc.
    I tried to create a new port entry with A0000000001 but no sucess.
    I tried to edit the 1st entry but the port filed comes disabled.
    Please assist in this regard.
    Thanks
    Pooja

  • Middleware initial load error on funcloc segment type (ADR2) does not exist

    Hello,
    We are doing initial loads of data into a new CRM 7.0 system.
    So far all objects have been done except Functional locations (FUNCLOC).
    During the initial load of the functional locations the various BDOCs all go into error state.
    The error is the same everywhere: segment type adr2 does not exist.
    If we deactivate the adr2 table In transaction R3AC1 and process again, we get the error message for the next table
    (Like:  segment type IFLOTX does not exist) and so on.
    IS there any settings we can do to manage these 'segments' or would there be another wa to solve this?
    Thanks.
    Joram

    Hello,
    Take a look at note 1271465, it does not talk about the ADR2 segment but about segment errors in SMW01 for functional location download. It might be useful. Observe especially the constraint in ERP version number, it might be that your ERP system is out-of-date/incompatible for this scenario.
    Second thing to check, go to SPRO>CRM>Master Data>Installed Base>Replication of technical objects from ERP
    There you'll find a mandatory customizing activity for Functional location download.
    And in the documentation of activity "Replication of Functional locations: Prerequisites and General information" you'll find all the necessairy actions to perform.
    This helped me in setting up funcloc replication in CRM 7.0.
    Hope this helps,
    Kind regards,
    Joost

  • Type com.sap.xss.ser.xssmenu.model.types.P_Pernr does not exist

    Hi there,
    same Thread I post in "Portal Developement". Now I try my luck in ths category...
    we implement ESS (ERP2004 with WebDynpros) in our testsystem, but we got an error and don´t know what to do...
    System Landscape:
    - mySAP Enterprise Portal 6.0 SP17
    - Java Application Server (excluding from HR)
    - mySAP ERP2004 HR-System
    The Connections from the portal runs to the Java-App-Server, not direct to the HR-System (HR-System has no Java Installation and our Customer don´t want a installation, because it could be a bad performance)
    We implement the Jco´s and fill out the usermapping. If we want to call the firstpage of the new ESS-Role we get this error.
    Can anyone help us? Do we need some installations?
    Best regards
    Christian
    Error
    500 Internal Server Error
    Web Dynpro Container/SAP J2EE Engine/6.40
    Failed to process request. Please contact your system administrator.
    Error Summary
    While processing the current request, an exception occured which could not be handled by the application or the framework.
    If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
    Root Cause
    The initial exception that caused the request to fail, was:
    com.sap.dictionary.runtime.DdException: Type com.sap.xss.ser.xssmenu.model.types.P_Pernr does not exist
    at com.sap.dictionary.types.mdi.util.ProviderUtil.createAbapTypeXmlMap(ProviderUtil.java:400)
    at com.sap.dictionary.runtime.mdi.DataProvider.createSimpleTypeFromAbapType(DataProvider.java:586)
    at com.sap.dictionary.runtime.mdi.DataProvider.getDataType(DataProvider.java:286)
    at com.sap.dictionary.runtime.DdDictionary.getDataType(DdDictionary.java:95)
    at com.sap.dictionary.runtime.DdBroker.getDataType(DdBroker.java:164)
    ... 54 more
    See full exception chain for details.
    System Environment
    Client
    Web Dynpro Client Type HTML Client
    User agent Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322; InfoPath.1; .NET CLR 2.0.50727)
    Version
    DOM version
    Client Type msie6
    Client Type Profile ie6
    ActiveX enabled
    Cookies enabled
    Frames enabled
    Java Applets enabled
    JavaScript enabled
    Tables enabled
    VB Script enabled
    Server
    Web Dynpro Runtime Vendor: SAP, Build ID: 6.4015.00.0000.20051123162612.0000 (release=630_VAL_REL, buildtime=2005-12-14:21:51:22[UTC], changelist=377533, host=PWDFM026)
    J2EE Engine No information available
    Java VM Classic VM, version:1.4.2, vendor: IBM Corporation
    Operating system AIX, version: 5.2, architecture: ppc64
    Other
    Session Locale de
    Time of Failure Thu Jan 11 16:14:11 GMT+00:00 2007 (Java Time: 1168532051021)
    Web Dynpro Code Generation Infos
    sap.com/pcui_gp~xssutils
    SapDictionaryGenerationCore 6.4018.00.0000.20060530191647.0000 (release=630_REL, buildtime=2006-09-20:21:03:45[UTC], changelist=405154, host=PWDFM027.wdf.sap.corp)
    SapDictionaryGenerationTemplates 6.4018.00.0000.20060530191647.0000 (release=630_REL, buildtime=2006-09-20:21:03:57[UTC], changelist=405154, host=PWDFM027.wdf.sap.corp)
    SapGenerationFrameworkCore 6.4015.00.0000.20050818152155.0000 (release=630_VAL_REL, buildtime=2005-11-24:21:18:08[UTC], changelist=363812, host=PWDFM026.wdf.sap.corp)
    SapIdeWebDynproCheckLayer 6.4018.00.0000.20060823112633.0000 (release=630_REL, buildtime=2006-09-20:21:14:40[UTC], changelist=415262, host=PWDFM027.wdf.sap.corp)
    SapMetamodelCommon 6.4018.00.0000.20060302125746.0000 (release=630_REL, buildtime=2006-09-20:20:56:46[UTC], changelist=392271, host=PWDFM027.wdf.sap.corp)
    SapMetamodelCore 6.4018.00.0000.20060302125746.0000 (release=630_REL, buildtime=2006-09-20:20:56:36[UTC], changelist=392271, host=PWDFM027.wdf.sap.corp)
    SapMetamodelDictionary 6.4018.00.0000.20060302125547.0000 (release=630_REL, buildtime=2006-09-20:21:00:39[UTC], changelist=392265, host=PWDFM027.wdf.sap.corp)
    SapMetamodelWebDynpro 6.4018.00.0000.20060823112248.0000 (release=630_REL, buildtime=2006-09-20:21:09:40[UTC], changelist=415252, host=PWDFM027.wdf.sap.corp)
    SapWebDynproGenerationCTemplates 6.4018.00.0000.20060915154217.0000 (release=630_REL, buildtime=2006-09-20:21:52:30[UTC], changelist=417774, host=PWDFM027)
    SapWebDynproGenerationCore 6.4018.00.0000.20060823112633.0000 (release=630_REL, buildtime=2006-09-20:21:15:10[UTC], changelist=415262, host=PWDFM027.wdf.sap.corp)
    SapWebDynproGenerationTemplates 6.4018.00.0000.20060915154217.0000 (release=630_REL, buildtime=2006-09-20:21:52:30[UTC], changelist=417774, host=PWDFM027)
    sap.com/tcwddispwda
    No information available
    sap.com/pcui_gp~xssfpm
    SapDictionaryGenerationCore 6.4018.00.0000.20060530191647.0000 (release=630_REL, buildtime=2006-09-20:21:03:45[UTC], changelist=405154, host=PWDFM027.wdf.sap.corp)
    SapDictionaryGenerationTemplates 6.4018.00.0000.20060530191647.0000 (release=630_REL, buildtime=2006-09-20:21:03:57[UTC], changelist=405154, host=PWDFM027.wdf.sap.corp)
    SapGenerationFrameworkCore 6.4015.00.0000.20050818152155.0000 (release=630_VAL_REL, buildtime=2005-11-24:21:18:08[UTC], changelist=363812, host=PWDFM026.wdf.sap.corp)
    SapIdeWebDynproCheckLayer 6.4018.00.0000.20060823112633.0000 (release=630_REL, buildtime=2006-09-20:21:14:40[UTC], changelist=415262, host=PWDFM027.wdf.sap.corp)
    SapMetamodelCommon 6.4018.00.0000.20060302125746.0000 (release=630_REL, buildtime=2006-09-20:20:56:46[UTC], changelist=392271, host=PWDFM027.wdf.sap.corp)
    SapMetamodelCore 6.4018.00.0000.20060302125746.0000 (release=630_REL, buildtime=2006-09-20:20:56:36[UTC], changelist=392271, host=PWDFM027.wdf.sap.corp)
    SapMetamodelDictionary 6.4018.00.0000.20060302125547.0000 (release=630_REL, buildtime=2006-09-20:21:00:39[UTC], changelist=392265, host=PWDFM027.wdf.sap.corp)
    SapMetamodelWebDynpro 6.4018.00.0000.20060823112248.0000 (release=630_REL, buildtime=2006-09-20:21:09:40[UTC], changelist=415252, host=PWDFM027.wdf.sap.corp)
    SapWebDynproGenerationCTemplates 6.4018.00.0000.20060915154217.0000 (release=630_REL, buildtime=2006-09-20:21:52:30[UTC], changelist=417774, host=PWDFM027)
    SapWebDynproGenerationCore 6.4018.00.0000.20060823112633.0000 (release=630_REL, buildtime=2006-09-20:21:15:10[UTC], changelist=415262, host=PWDFM027.wdf.sap.corp)
    SapWebDynproGenerationTemplates 6.4018.00.0000.20060915154217.0000 (release=630_REL, buildtime=2006-09-20:21:52:30[UTC], changelist=417774, host=PWDFM027)
    sap.com/tcwdcorecomp
    No information available
    Detailed Error Information
    Detailed Exception Chain
    com.sap.tc.webdynpro.services.exceptions.WDTypeNotFoundException: type com.sap.xss.ser.xssmenu.model.types.P_Pernr could not be loaded: com.sap.dictionary.runtime.DdException: Type com.sap.xss.ser.xssmenu.model.types.P_Pernr does not exist
    at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getSimpleType(DataTypeBroker.java:250)
    at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getDataType(DataTypeBroker.java:213)
    at com.sap.tc.webdynpro.progmodel.context.DataAttributeInfo.init(DataAttributeInfo.java:314)
    at com.sap.tc.webdynpro.progmodel.context.NodeInfo.initAttributes(NodeInfo.java:669)
    at com.sap.tc.webdynpro.progmodel.context.DataNodeInfo.doInit(DataNodeInfo.java:233)
    at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:654)
    at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:657)
    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:347)
    at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.createComponent(ClientComponent.java:855)
    at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.createComponent(ClientComponent.java:158)
    at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.createComponentInternal(ComponentUsage.java:143)
    at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.createComponent(ComponentUsage.java:135)
    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.ser.xssmenu.vc.header.VcXssMenuHeader.onInit(VcXssMenuHeader.java:196)
    at com.sap.xss.ser.xssmenu.vc.header.wdp.InternalVcXssMenuHeader.onInit(InternalVcXssMenuHeader.java:225)
    at com.sap.xss.ser.xssmenu.vc.header.VcXssMenuHeaderInterface.onInit(VcXssMenuHeaderInterface.java:162)
    at com.sap.xss.ser.xssmenu.vc.header.wdp.InternalVcXssMenuHeaderInterface.onInit(InternalVcXssMenuHeaderInterface.java:144)
    at com.sap.xss.ser.xssmenu.vc.header.wdp.InternalVcXssMenuHeaderInterface$External.onInit(InternalVcXssMenuHeaderInterface.java:220)
    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:110)
    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:347)
    at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:370)
    at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:608)
    at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)
    at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:248)
    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.doPost(DispatcherServlet.java:55)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
    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: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(Compiled Code))
    at java.security.AccessController.doPrivileged1(Native Method)
    at java.security.AccessController.doPrivileged(AccessController.java(Compiled Code))
    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java(Compiled Code))
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java(Compiled Code))
    Caused by: com.sap.dictionary.runtime.DdException: Type com.sap.xss.ser.xssmenu.model.types.P_Pernr does not exist
    at com.sap.dictionary.types.mdi.util.ProviderUtil.createAbapTypeXmlMap(ProviderUtil.java:400)
    at com.sap.dictionary.runtime.mdi.DataProvider.createSimpleTypeFromAbapType(DataProvider.java:586)
    at com.sap.dictionary.runtime.mdi.DataProvider.getDataType(DataProvider.java:286)
    at com.sap.dictionary.runtime.DdDictionary.getDataType(DdDictionary.java:95)
    at com.sap.dictionary.runtime.DdBroker.getDataType(DdBroker.java:164)
    at com.sap.dictionary.runtime.DdBroker.getSimpleType(DdBroker.java:170)
    at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getSimpleType(DataTypeBroker.java:242)
    ... 52 more

    Hi,
    uhm... good question, long time ago...
    Error should be in the JCO-Destinations, where you can choose a targetsystem for each Jco-Destination.
    Since them we installed a java on the abap-system, so we have a doublestack.
    In the Jco Destiantions must be the ABAP-System.
    Application via SAPTicket and MetaData via fix User like DDIC.
    Regards
    Christian

  • Configured source directory .... does not exist was suppressed

    Hi,
    Below log is from PI 7.1 EHP1 system. I have tried to execute simple use cases from SDN but got below exception. The folder actually is there and there is not typing error. What could be the problem and any solution?
    Kind regards,
    Altug
    #2.0 #2010 05 11 01:57:10:002#+0300#Error#com.sap.aii.adapter.file.File2XI#
    #BC-XI-CON-AFW#com.sap.aii.af.lib#000C293D9117124200000000000007B0#9722350000001755##com.sap.aii.adapter.file.File2XI.getFileList(File2XIConfiguration.FileSource[])#J2EE_GUEST#0##488CE8105C4F11DF9D42000C293D9117#488ce8105c4f11df9d42000c293d9117#488ce8105c4f11df9d42000c293d9117#0#XI File2XI[XiPatternChannel_FileSender/PI7_FileSystem_XIPattern1/]_4767#Plain##
    Channel XiPatternChannel_FileSender: Directory C:
    work
    XIPattern1 does not exist#
    #2.0 #2010 05 11 01:57:10:002#+0300#Error#com.sap.aii.af.service.administration.impl.AlertingStatusListener#
    #BC-XI-CON-AFW#com.sap.aii.af.lib#000C293D9117124300000000000007B0#9722350000001755##com.sap.aii.af.service.administration.impl.AlertingStatusListener.run()#J2EE_GUEST#0##488CE8105C4F11DF9D42000C293D9117#488ce8105c4f11df9d42000c293d9117#488ce8105c4f11df9d42000c293d9117#0#XI AF AAM AlertingStatusListener$AsyncAlerter@67c2a0d6_4768#Java##
    Unable to raise alert for fatal process status (adapter :, channel ): com.sap.aii.af.service.alerting.AlertingException: An alert with suppress information:  Error Code:  Error Category:  Error text: Configured source directory 'C:
    work
    XIPattern1' does not exist was suppressed!Host:w2k3x64_PI7_00|AdapterType:File|Sender::PI7_FileSystem_XIPattern1|Receiver::|Interface:XiPatternInterface1:http://sap.com/xi/XI/System/Patterns|MsgID:null#3#http://sap.com/xi/XI/System#File#7be7f5b9e06c30cc97f90f55a21e150e#
    #2.0 #2010 05 11 01:57:20:002#+0300#Error#com.sap.aii.adapter.file.File2XI#
    #BC-XI-CON-AFW#com.sap.aii.af.lib#000C293D9117124400000000000007B0#9722350000001755##com.sap.aii.adapter.file.File2XI.getFileList(File2XIConfiguration.FileSource[])#J2EE_GUEST#0##488CE8105C4F11DF9D42000C293D9117#488ce8105c4f11df9d42000c293d9117#488ce8105c4f11df9d42000c293d9117#0#XI File2XI[XiPatternChannel_FileSender/PI7_FileSystem_XIPattern1/]_4769#Plain##
    Channel XiPatternChannel_FileSender: Directory C:
    work
    XIPattern1 does not exist#
    #2.0 #2010 05 11 01:57:20:017#+0300#Error#com.sap.aii.af.service.administration.impl.AlertingStatusListener#
    #BC-XI-CON-AFW#com.sap.aii.af.lib#000C293D9117124500000000000007B0#9722350000001755##com.sap.aii.af.service.administration.impl.AlertingStatusListener.run()#J2EE_GUEST#0##488CE8105C4F11DF9D42000C293D9117#488ce8105c4f11df9d42000c293d9117#488ce8105c4f11df9d42000c293d9117#0#XI AF AAM AlertingStatusListener$AsyncAlerter@1cfe7a5d_4770#Java##
    Unable to raise alert for fatal process status (adapter :, channel ): com.sap.aii.af.service.alerting.AlertingException: An alert with suppress information:  Error Code:  Error Category:  Error text: Configured source directory 'C:
    work
    XIPattern1' does not exist was suppressed!Host:w2k3x64_PI7_00|AdapterType:File|Sender::PI7_FileSystem_XIPattern1|Receiver::|Interface:XiPatternInterface1:http://sap.com/xi/XI/System/Patterns|MsgID:null#3#http://sap.com/xi/XI/System#File#7be7f5b9e06c30cc97f90f55a21e150e#
    #2.0 #2010 05 11 01:57:30:002#+0300#Error#com.sap.aii.adapter.file.File2XI#
    #BC-XI-CON-AFW#com.sap.aii.af.lib#000C293D9117124600000000000007B0#9722350000001755##com.sap.aii.adapter.file.File2XI.getFileList(File2XIConfiguration.FileSource[])#J2EE_GUEST#0##488CE8105C4F11DF9D42000C293D9117#488ce8105c4f11df9d42000c293d9117#488ce8105c4f11df9d42000c293d9117#0#XI File2XI[XiPatternChannel_FileSender/PI7_FileSystem_XIPattern1/]_4771#Plain##
    Channel XiPatternChannel_FileSender: Directory C:
    work
    XIPattern1 does not exist#
    #2.0 #2010 05 11 01:57:30:017#+0300#Error#com.sap.aii.af.service.administration.impl.AlertingStatusListener#
    #BC-XI-CON-AFW#com.sap.aii.af.lib#000C293D9117124700000000000007B0#9722350000001755##com.sap.aii.af.service.administration.impl.AlertingStatusListener.run()#J2EE_GUEST#0##488CE8105C4F11DF9D42000C293D9117#488ce8105c4f11df9d42000c293d9117#488ce8105c4f11df9d42000c293d9117#0#XI AF AAM AlertingStatusListener$AsyncAlerter@d023a80_4772#Java##
    Unable to raise alert for fatal process status (adapter :, channel ): com.sap.aii.af.service.alerting.AlertingException: An alert with suppress information:  Error Code:  Error Category:  Error text: Configured source directory 'C:
    work
    XIPattern1' does not exist was suppressed!Host:w2k3x64_PI7_00|AdapterType:File|Sender::PI7_FileSystem_XIPattern1|Receiver::|Interface:XiPatternInterface1:http://sap.com/xi/XI/System/Patterns|MsgID:null#3#http://sap.com/xi/XI/System#File#7be7f5b9e06c30cc97f90f55a21e150e#
    #2.0 #2010 05 11 01:57:40:002#+0300#Error#com.sap.aii.adapter.file.File2XI#
    #BC-XI-CON-AFW#com.sap.aii.af.lib#000C293D9117124800000000000007B0#9722350000001755##com.sap.aii.adapter.file.File2XI.getFileList(File2XIConfiguration.FileSource[])#J2EE_GUEST#0##488CE8105C4F11DF9D42000C293D9117#488ce8105c4f11df9d42000c293d9117#488ce8105c4f11df9d42000c293d9117#0#XI File2XI[XiPatternChannel_FileSender/PI7_FileSystem_XIPattern1/]_4773#Plain##
    Channel XiPatternChannel_FileSender: Directory C:
    work
    XIPattern1 does not exist#
    #2.0 #2010 05 11 01:57:40:002#+0300#Error#com.sap.aii.af.service.administration.impl.AlertingStatusListener#
    #BC-XI-CON-AFW#com.sap.aii.af.lib#000C293D9117124900000000000007B0#9722350000001755##com.sap.aii.af.service.administration.impl.AlertingStatusListener.run()#J2EE_GUEST#0##488CE8105C4F11DF9D42000C293D9117#488ce8105c4f11df9d42000c293d9117#488ce8105c4f11df9d42000c293d9117#0#XI AF AAM AlertingStatusListener$AsyncAlerter@76395415_4774#Java##
    Unable to raise alert for fatal process status (adapter :, channel ): com.sap.aii.af.service.alerting.AlertingException: An alert with suppress information:  Error Code:  Error Category:  Error text: Configured source directory 'C:
    work
    XIPattern1' does not exist was suppressed!Host:w2k3x64_PI7_00|AdapterType:File|Sender::PI7_FileSystem_XIPattern1|Receiver::|Interface:XiPatternInterface1:http://sap.com/xi/XI/System/Patterns|MsgID:null#3#http://sap.com/xi/XI/System#File#7be7f5b9e06c30cc97f90f55a21e150e#
    #2.0 #2010 05 11 01:57:50:002#+0300#Error#com.sap.aii.adapter.file.File2XI#
    #BC-XI-CON-AFW#com.sap.aii.af.lib#000C293D9117124A00000000000007B0#9722350000001755##com.sap.aii.adapter.file.File2XI.getFileList(File2XIConfiguration.FileSource[])#J2EE_GUEST#0##488CE8105C4F11DF9D42000C293D9117#488ce8105c4f11df9d42000c293d9117#488ce8105c4f11df9d42000c293d9117#0#XI File2XI[XiPatternChannel_FileSender/PI7_FileSystem_XIPattern1/]_4775#Plain##
    Channel XiPatternChannel_FileSender: Directory C:
    work
    XIPattern1 does not exist#
    #2.0 #2010 05 11 01:58:00:002#+0300#Error#com.sap.aii.adapter.file.File2XI#
    #BC-XI-CON-AFW#com.sap.aii.af.lib#000C293D9117124B00000000000007B0#9722350000001755##com.sap.aii.adapter.file.File2XI.getFileList(File2XIConfiguration.FileSource[])#J2EE_GUEST#0##488CE8105C4F11DF9D42000C293D9117#488ce8105c4f11df9d42000c293d9117#488ce8105c4f11df9d42000c293d9117#0#XI File2XI[XiPatternChannel_FileSender/PI7_FileSystem_XIPattern1/]_4777#Plain##
    Channel XiPatternChannel_FileSender: Directory C:
    work
    XIPattern1 does not exist#
    #2.0 #2010 05 11 01:58:00:002#+0300#Error#com.sap.aii.af.service.administration.impl.AlertingStatusListener#
    #BC-XI-CON-AFW#com.sap.aii.af.lib#000C293D9117124C00000000000007B0#9722350000001755##com.sap.aii.af.service.administration.impl.AlertingStatusListener.run()#J2EE_GUEST#0##488CE8105C4F11DF9D42000C293D9117#488ce8105c4f11df9d42000c293d9117#488ce8105c4f11df9d42000c293d9117#0#XI AF AAM AlertingStatusListener$AsyncAlerter@37d6d40_4778#Java##
    Unable to raise alert for fatal process status (adapter :, channel ): com.sap.aii.af.service.alerting.AlertingException: An alert with suppress information:  Error Code:  Error Category:  Error text: Configured source directory 'C:
    work
    XIPattern1' does not exist was suppressed!Host:w2k3x64_PI7_00|AdapterType:File|Sender::PI7_FileSystem_XIPattern1|Receiver::|Interface:XiPatternInterface1:http://sap.com/xi/XI/System/Patterns|MsgID:null#3#http://sap.com/xi/XI/System#File#7be7f5b9e06c30cc97f90f55a21e150e#

    Hi,
    Use this as a source directory mention the \ at last "C:
    work
    XIPattern1\"
    This doesn't help me. But later I give a permisson to the directory for everyone group. This time PI process worked and processed file.
    Thanks.
    Altug

  • Source system 8(ODS name) does not exist

    Hi experts!
    When I transport some Process Chane from DEV to PRD I faced with issue that the source system 8(ODS name) does not exist.
    Is anyone faced with same error?
    Thx!

    Hi.......
    Look.......
    U cannot Transport it........First Right click on the Infoprovider in PRD >> Export Datasource...........then replicate it from bw myself........
    U hav to generate it in Production also.............hav u done this before replication.....?
    Regards,
    Debjani....

  • Basic type CREMAS03 does not exist

    Hi all.
    We have SRM 7 Classic Scenario with ECC 6.4
    My problem is in scenario MM-SUS. When we try to replicate a vendor data from MM to SUS the idoc MM is processed correctly, but in (SUS) has an error in trx WE05: Basic type CREMAS03 does not exist.
    I review the settings and I can not find the cause.
    any idea about that?
    Regards

    Hi,
    I am not clear with your issue. Why are you checking for idoc status in SUS system?
    IDOC is sent from the ERP system and check what the status of IDOC is in ERP. Next check whats the xml status in PI system and if its successful in PI then check xml in SUS system/. You can check xml status using tcode: sxi_monitor.
    Regards
    Sam

  • Set type COMM_PR_UNIT does not exist

    Hi All
    How do i make set types available for assignment to categories if they are not available but are there in comm_settype. Getting errors as follows: Set type COMM_PR_UNIT does not exist.
    Please assist
    Regards,
    Patrick
    Edited by: Patrick Chidarara on Jul 22, 2008 10:14 AM

    Hi Patrick,
    Please see OSS note Note 966072 - Download of material fails - set type COMM_PR_UNIT
    Regards,Nishant

Maybe you are looking for