No backend PO in ECC5?

Hi Gurus,
Please can someone shed some light on the following error.
We have activated extended classic scen in srm 5.0, but our srm PO does not replicate over to ECC5 as a display only doc. The checks our basis team have undertaken are:
i. No idocs are visible in WE05
ii. errors are displayed in RZ20 say: (a) IDOC comms error: 'error sending IDoc to FI/CO backend for PO3xxxxxxxx, (b) Comm error checking account assignment for PO3xxxxxxxx in system
iii. the trans type and doc no's are consistent in srm.
iv. no entries in srm table REQREF
Any input would be appreciated
Thank you,
Mikey
Edited by: Mike Pallister on Aug 26, 2008 10:07 PM

Hi Muthu,
Thank you for the hint. I can now sucessfully get an outboubnd IDOC from our SRM system, however, the Inbound IDOC fails in R/3 with the message. Please can you elaborate what function module should be used for message type BBPCO01 as I am using Process Code 'BAPI' in R/3 transaction code WE20.
Thanking you,
M.
Function module not allowed: BAPI_IDOC_INPUT1
Message no. B1252
Diagnosis
The function module BAPI_IDOC_INPUT1 and the application object type which were determined are not valid for this IDoc.
Procedure
1. Please check that the process code in the inbound partner profile is correct.
2. If this is the case, you should check the ALE inbound methods ALE inbound methods for the process code and see whether the specified function module and application object type are correct.
3. If this is also the case, then the function module and the application object type are not permitted for the logical message type, message variant, message function and basis type that are contained in the IDoc control record. You should check whether the correct values have been assigned to these fields in the control record. If they do have the correct values, then the assignment to the function module and the application object type needs to be maintained.

Similar Messages

  • Problem in career and job iview

    Hi all,
    We have installed ESS 60.1 on our EP(ep6 sp11) and was later upgraded to EP6 SP16. The backend used is ECC5.0 IDES. Almost all the iViews work fine. But there is a problem with the Career and Job iView.
    When the 'Apply directly' or the other option in Career & Job is clicked, it throws an object not found exception. The Patch applied on the backend is ERECRUIT 300: Add-On Installation.
    Please let me know what the problem could be and the possible solution for this.
    Regards,
    Prathamesh.

    HI prathmesh,
    After installing SAP e-Recruiting 3.00 with Support Package 1, or higher,for career and job workset related applications to work,have you made the following settings in the Implementation Guide (IMG):
    1.Choose the following IMG path: Cross-Application Components ? Homepage Framework ? Resources ? Define Server for Resources. Enter the server name and the port of your e-Recruiting system.
    2.Assign the server to all e-recruiting resources and add the URL parameters stored.  To do so, choose the following IMG path: Cross-Application Components ? Homepage Framework ? Resources ? Define Resources.
    Enter the e-recruiting server for the following resources. Add the relevant URL parameters by replacing in the BSP client the 000 client with the client of your e-recruiting system.
    EMPLOYEE_CANDIDATE_APPLICATIONS_SERVICE
    EMPLOYEE_CANDIDATE_DATA_OVERVIEW
    EMPLOYEE_CANDIDATE_DIRECT_APPL_SERVICE
    EMPLOYEE_CANDIDATE_FAVORITES_SERVICE
    EMPLOYEE_CANDIDATE_PERSONAL_SETTINGS
    EMPLOYEE_CANDIDATE_PROFILE_RELEASE
    EMPLOYEE_CANDIDATE_PROFILE_SERVICE
    EMPLOYEE_CANDIDATE_SEARCH_JOBS_SERVICE
    Ho[pe this helps,
    Regards,
    Siddhartha

  • MSS and BW Reporting

    Hello - does any one have any experience with MSS and BW reporting?
    We have a requirement to implement BW reports to Line Managers through MSS.
    For R/3 Reports we have no issue as we can use the standard structural authorisation function module to restrict access to empoyees directly reporting to the manager.
    How can we restrict BW reports in the same way? i.e. When Manager runs the report they should only see data about the employees that report to them in the Org structure.
    We are using BW 7.0.

    Hi Mike,
    Did You implement this scenario. Even we are trying to do the same.
    I am kind of no clue about which authorizations a manager needs in BW system.
    We are using EP6.0 SP16 and backend system is ECC5.0.
    I have couple of questions.
    1. What authorizations in BW system the portal user (Me with content admin, system admin, user admin roles) needs to view the BW reports or BW iviews?
    2. Manager (MSS) can not view  crystal reports in the work set 'Reporting' assigned to a manager in ECC5.0. Other iviews within the BP60.1 are working fine.
    3. When manager tried to see a crystal report , it threw an error saying that
    Portal Runtime Error
    An exception occurred while processing a request for :
    iView : N/A
    Component Name : N/A
    Unable to lookup System 'SAP_BW_HumanResources'. Please check the system object and the alias..
    See the details for the exception ID in the log file
    com.sap.portal.appintegrator.sap.CrystalReport::CrystalReport/SSOLayer
    Could you please help in finding proper documentation on setting up manager to see the reports in BW system.
    Thanks!

  • External ASN Generation - SNC Mapping

    Hi,
    We are in process of configuring externally generated ASN (from 3rd party supplier) send to SNC through XI/PI and then automatically route it to backend ECC system(ECC5.0) through existing interface ( DespatchDeliveryNotification_Out - from SNC).
    We considered SAP Note - 944125 ( SNC/ICH-ASN: Routing of externally created ASNs through ICH/SNC) but this note is applicable to SCM 500 and we are in SCM 510. We verified that its been already implemented in SCM 510 version
    We processed ASN's from 3rd party system and sent to SCM/SNC system and now ASN's are with Publish status in SNC system and But the routing process of ASN info didn't happend! Its still stuck up with ASN publish message in SNC. Did we miss any other configuration to make this routing successful?
    Or Is there any other solution to configure this routing of externally created ASN through SNC to the backend ECC system?
    -Chriss

    Hi,
    Do we have standard content available in PI to create ASN in SNC with reference to ECC- outbound delivery
    DESADV.DELVRY 03  convert to DISPATCHDELIVERYNOTIFICATION.

  • Webdynpro cat2 r3 4.7

    Hi All,
      I have been given a task to develop a webdynpro application which resembles cat2 transaction. The users didnt like the ITS iview.
    I would have easily implemented this if my backend system is ECC5.0 by deploying the ESS Business package, as it is specified in the requirement list that ECC5.0 IS MANDATORY.
    I have a couple of questions
    1) isnt the ESS BP iviews are "webdynpro java" applications? if that is the case, since I have WAS 6.40 ( MY PORTAL IS EP6.0 SP19), I should be able to run the web dynpro applciations, so why wouldnt the ESS BP WD appls doesnt run on my WAS 6.40. what are the major changes done in the backend systems (i.e. R3 4.7 VS ECC5.0). I am not asking to list all the differences. I just wnat to know why wouldnt the ESS BP WD applciations doenst run with R3 4.7 as backend?
    2) How should I start developing a WD appl, if it has to have all the features that CAT2 does, how much time will it usually take? and how to get started with developing a WD appl for CAT2?
    Please help.
    Shiva
    Message was edited by:
            shiva shiva

    The anwser to your question 1 can be found in the <a href="http://help.sap.com/saphelp_erp2005vp/helpdata/en/f6/263359f8c14ef98384ae7a2becd156/frameset.htm">System Landscape</a> required to implement the Business Package for ESS(mysap ERP) 1.0
    Question 2 -->If you have a WAS640 Portal, you can develop a WebDynpro application in the DevStudio and still connect to the 47 system. Regarding the development effort, it depends on how far you have customized the CAT2 in the backend.. if you are using CAT2 out-of-the-box, I would say 3/4 week period should be sufficient. you will have to do the frontend design in the DevStudio, encpsulate the backend logic in a custom Rfc and call it from the webdynpro application.
    You will still need a portal resource to set up with the DevStudio, the backend connections & the deployment of the WebDynpo Application.
    I too am still stuck on a 47(for the last  4 years )& my above response is purely based on what I have understood from the online help.
    ~Suresh

  • Create purchase order in backend ECC5

    Hi,
    have the following scenario:
        we have a SRM-system(SRM 4.0) with many R/3 backend (46B, 46C, 4.7, ECC5)
    I need to save some customer fields in Purchase Order item, when it is generated by SRM.
    When SRM will generate a PO in backend (R/3) with release ECC5, it calls B470_PO_CREATE function module and inside it calls BAPI_PO_CREATE1 in R/3.
    in SRM the system using Badi BBP_PO_CREATE_BACK method FILL_PO_CREATE1_INTERFACE, but we have a problem: the parameter is empty.  Anyone know why?
        Can you help me?
    Best regards
    Alessio

    Hi
    Please go through the links as well ->
    Re: Creating of PO in backend
    Re: BAPI_PO_CREATE1
    Re: PO doesn't get created, backend returns PO number with "S" message
    Re: User defined fields
    Re: Modify print price indicator in PO using BBP_CREATE_PO_BACK
    Regards
    - Atul

  • SAPGUI Requirements for ECC5.0 Backend

    Sir or Madam, 
    I'm just starting the planning phase for an upgrade to ECC5.0 and was curious what SAPGUI version is required for use with ECC5.0.  All of my users are currently using the 6.2 front-end.
    Many Thanks,
    Shane

    We use already ECC5.0
    Our SAPGUI is 6.20 patch-level 60 without any problems.
    regards
    Friedel

  • Creation of backend vendor master from SUS

    Hi
    We are on SRM4.0 and ECC5.0 with SUS3.0 and having following <b>scenario</b>.
    Suppliers gets registered in registration system in SRM.
    Purchaser will do screening and select the supplier.
    <b>Requirement</b>
    Want to create Vendor master in backend system(ECC5.0) for the above selected supplier from SRM system itself without login to ECC system(that means no manual creation of vendor master in ECC).
    Is this scenario possible?
    Did anyone come across such requirement?
    Please share your experience on how to achive this.
    Thanks in advance
    Jagdish

    Hi,
      You can create a custom WF for vednor replication using BUS1006.We have done the same thing at our place.
    BR,
    Disha.
    (Please open a new thread so that points can be rewarded)
    Pls reward points for useful answers.

  • Change in backend system

    Hi SRM Gurus,
    Project Scenario is ECC5 as backend system integrated with SRM 4.0( SSP scenario and with Catalog CCM2.0)
    Implementation scenario is Extended classic.
    Backend system will be changed to ECC6 from ECC 5.0 with company code consolidation.
    ECC6 is installed on separate server for implementing changes in FI (separate Dev, QA, Prod environment ) and will be integrated with SRM4.0
    Question is that when we integrate SRM4.0 with ECC6, do we need to run transaction BDLS to change logical system name in SRM for backend system?
    As all product categories and vendor are same in ECC 6.0 will this work.
    Also there is GUID reference in table CRMLSSGUID & CRMPRLS in R3. How this will be taken care.
    Option 2:
    no need to run BDLS in SRM. We need to define new backend system and  replicate all master data (product categories, UOM & vendor master) from ECC6 to SRM4.0.
    SRM experts, please suggest as for me option 2 is suitable way.
    Thanks & Regards,
    Avinash

    Hi SRM experts,
    In Org structure   Product categories will be maintained with Source system (new backend system) in extended attributes. Also for vendors new  backend system maintained in attributes.
    With these settings user will able to see the product categories, vendors pertaining to New backend system.
    Please share your views.
    Regards,
    Avinash

  • Error during determn of backend follow-on doc. for shopping cart

    I am using Classic Scenario in SRM 4.0 and R/3 ECC5.
    When I am making PO in SOCO against approved shopping cart I am facing following error and PO is not getting created.
    "Error during determn of backend follow-on doc. for shopping cart XXXXXXXXXX"
    I have Checked up following :
    1. Product Cat defined in backend and in Org plan attribute
    2. Object for Prod Cat Vs. PGR defined in SPRO
    3. Doc type in R/3 attribute defiend in BSA attribute of Org Plan.
    Still problem is coming.
    Any clue form some one.
    Sanjay

    Hi Sanjay/Vadim,
    We are also having a simialr issue..
    for SRM server 500 SAPKIBKS08...
    R/3 4.7
    "But this issue comes up only in the Test system and works fine with the Dev sys.." Double checked all the config steps and looks alike..
    We are using the classic scenario RFx process to create a backend PO from the bidding engine after the bid is accepted..
    it alwayz throws up the error SC/ Local Error..
    : Error during determn of backend follow-on doc. for shopping cart 0010000103 / 0000000001....
    we just started debugging from the web by breaking it at META_BAPI_DISPATCH and still looking into it..
    but in the mean while just want to know if this is more a config issue or and RFC connection issue..
    could you forward me any OSS notes if any regarding this issue..
    thanks in advance..
    Regards
    Manoj

  • Master data in SRM when backend system change

    Hi SRM Gurus,
    Our scenario is ECC5 as backend system integrated with SRM 4.0(  SSP scenario and  iwith Catalog CCM2.0) Tech Implementation scenario is Extended classic .
    Now our backend system will be changed to ECC6 from ECC 5.
    ECC6 is installed on separate server for implementing changes in FI  ( separate Dev, QA, Prod environment )
    Question is that when we integrate SRM4.0 with ECC6, all master data (product categories, products & vendor master) needs to be replicated from ECC6 to SRM4.0
    As SRM system will remain same what will happen to present master data in Production system.
    As deletion is not suggested what is the correct approach.
    We can delete this master data in SRM Dev and QA.
    Can we keep master data pertaining to ECC5 as it is in SRM.
    Any idea as to what type of impacts one can expect if backend system changed from ECC5 to ECC6? Is there a recommended approach for this?
    I already referred note SAP note 418886 /995771.
    Regards,
    Avinash

    Hi
    By changing to ECC6.0 you would be entering a new backend system. Since the master data in SRM is linked to the respective backend system, it should not impact you.The old master data would still be there but linked to old backend system. You can let the data remain as it is if you want.
    Regards
    Sanjeev

  • Impact on shopping cart due to change in backend system

    Hi All,
    Our client is changing the backend ECC5 system to ECC6 on new server (new logical sys) with FI restructring in ECC6.
    We have SRM4.0 system ( with CCM on same client) with Extended classic scenario.
    What will be impact on Shopping carts which are awaiting for approval or in Held status( used by client as template) .There is only product category and vendor and no material number in Shopping cart  from catalog.
    As the product categories and vendors are same in ECC6 also , during cutover can the shopping cart with held/open status  be posted after changing backend system, Or we need to upload it.
    Any thoughts on this please.
    Best regards,
    Avinash

    Hi Laurent,
    In ECC6 ,consolidation of many company codes  to single company code will happen, whereas in SRM as there is only one backend purchasing org we need to map this with new backend purchasing org of ECC6.0(which is unique for SRM)
    As per my understanding, as backend system change we need to replicate same product categories from ECC6 to SRM4.0 as SRM creates GUIDs for backend product categories and passes a sych GUID in ECC also.
    Will the existing shopping carts in Held/open condition get processed which had been already created with old Product categories and vendor details (which are replicated from ECC5) when backend system changed to ECC6
    Is this applicable for open purchase orders also as company code consolidates in ECC6. Do we need to close open PO or upload open with change data?
    Please suggest.
    Regards,
    Avinash

  • Contract price is zero in the shopping cart  for backend contract

    Hi
    <b>Our environment</b>
    SRM5.5   SP07 
    Classic scenario
    Backend ECC 5.0
    <b>Business process</b>
    Created a Contract in ECC5.0 for services and Materials (Goods) separately.
    While crating the shopping cart for services or Goods, contract is picked and showed up in the Source of supply section of the shopping cart.
    But Contract price shows "0". Where as in backend a price is maintained in the contract for the services/Goods.
    Before orderin the shopping cart, the Business users want to see the contract price in the shopping cart when a contract is assigned.
    <b>Question</b>
    How to show up the backend contract price in the shopping cart when a backend contract is picked up in the Source of supply section.
    Is it standard? If so, any SAP notes are to be applied?
    Did any one come accross this scenario. Please throw some light on the above issue.
    Thanks in advance.
    Regards
    Jagadish

    Ruben
    Thanks for your response.
    I already looked at this option. This will not work for my business case.
    The BADI can only change the data in the backgroung when a SC is saved and the user will not be able to view the backend Contract price before ordering the Shopping cart.
    The users want to see the contract price when a backend Contract is assigned in the Source of Supply section before ordering the Shopping cart.
    Regards
    Jagadish

  • NW04 EP6 Sp13 & ECC5.0 - Problem previewing MSS iviews

    We have just completed an install of NW06 EP6 SP13 & ECC5.0 at the back-end and are looking to implement ESS and MSS. In trying to preview an MSS iview, I am getting errors with the connection. A pre-requisite may be missing. This is our landscape:
    ECC5.0
    Abap Stack
    EP6 SP13
    Java Stack
    latest versions of MSS and ESS BPs
    The system connectivity, aliase, SAP Logon Tickets have been configured. The test connection is working. The userids in Portal and ECC5.0 are the same. LDAP is being used for initial Portal authentication.
    With EP6 SP2, a back-end plug-in was required and we are unable to find one for ECC5.0. What do we need on the back-end for the front-end and the back-end to communicate and allow us the capability of previewing the ESS and MSS iviews?
    Any help on this will be greatly appreciated.
    Thanks in advance.
    Regards, Neeta

    Hi,
    Note that I am running EP6 SP13 in NW04 and our backend is ECC5.0. The link I am trying to preview/run is, per Ketuls suggestion :
    http://sapptdapp1:50800/webdynpro/dispatcher/sap.com/pcui_gp~xssutils/XssMenu
    The error message I get is (rather long....):
    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.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve JCOClient name 'SAP_R3_SelfServiceGenerics_MetaData'. No such JCO destination is defined in the SLD
        at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter(JCOClientConnection.java:493)
        at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.init(AbstractJCOClientConnection.java:247)
        at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.<init>(AbstractJCOClientConnection.java:221)
        at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.<init>(JCOClientConnection.java:101)
        at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:144)
        ... 53 more
    See full exception chain for details.
    Correction Hints
    Retrieving a JCO destination with name 'SAP_R3_SelfServiceGenerics_MetaData' from the System Landscape Directory (SLD) failed, as the destination could not be found in the SLD. The most probable reason for that is that the destination has not been maintained yet.
    Use the preinstalled Web Dynpro Content Admin application to check/edit the destination. Use the Ping and Test functions of the Content Admin to verify that each destination is properly configured.
    Additional information about the System Landscape Directory and the Web Dynpro Content Admin can be found in the SAP Developer Network (SDN) and in the Online Help for the SAP Web Application Server (installed with SAP NetWeaver Developer Studio and available online).
    Note: the above hints are only a guess. They are automatically derived from the exception that occurred and therefore can't be guaranteed to address the original problem in all cases.
    System Environment
    Client
    Web Dynpro Client Type HTML Client
    User agent Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1)
    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.4013.00.0000.20050628104636.0000 (release=630_VAL_REL, buildtime=2005-07-19:20:18:44[UTC], changelist=356134, host=PWDFM026)
    J2EE Engine 6.40 patchlevel 95420.313
    Java VM Java HotSpot(TM) 64-Bit Server VM, version:1.4.2_06-b03, vendor: Sun Microsystems Inc.
    Operating system SunOS, version: 5.10, architecture: sparcv9
    Other
    Session Locale en_US
    Time of Failure Wed Sep 28 08:42:46 EDT 2005 (Java Time: 1127911366734)
    Web Dynpro Code Generation Infos
    sap.com/pcui_gp~xssutils
    SapDictionaryGenerationCore 6.4013.00.0000.20050606171348.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:02:08[UTC], changelist=351717, host=PWDFM026.wdf.sap.corp)
    SapDictionaryGenerationTemplates 6.4013.00.0000.20050606171348.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:02:19[UTC], changelist=351717, host=PWDFM026.wdf.sap.corp)
    SapGenerationFrameworkCore 6.4012.00.0000.20041104141254.0000 (release=630_VAL_REL, buildtime=2005-04-21:19:52:59[UTC], changelist=298452, host=PWDFM026.wdf.sap.corp)
    SapIdeWebDynproCheckLayer 6.4013.00.0000.20050606172055.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:08:32[UTC], changelist=351729, host=PWDFM026.wdf.sap.corp)
    SapMetamodelCommon 6.4013.00.0000.20050606171700.0000 (release=630_VAL_REL, buildtime=2005-07-04:19:56:31[UTC], changelist=351724, host=PWDFM026.wdf.sap.corp)
    SapMetamodelCore 6.4013.00.0000.20050606171700.0000 (release=630_VAL_REL, buildtime=2005-07-04:19:56:22[UTC], changelist=351724, host=PWDFM026.wdf.sap.corp)
    SapMetamodelDictionary 6.4013.00.0000.20050606171352.0000 (release=630_VAL_REL, buildtime=2005-07-04:19:59:38[UTC], changelist=351719, host=PWDFM026.wdf.sap.corp)
    SapMetamodelWebDynpro 6.4013.00.0000.20050609113138.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:05:19[UTC], changelist=352442, host=PWDFM026.wdf.sap.corp)
    SapWebDynproGenerationCTemplates 6.4013.00.0000.20050628104636.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:19:30[UTC], changelist=356134, host=PWDFM026)
    SapWebDynproGenerationCore 6.4013.00.0000.20050606172055.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:09:01[UTC], changelist=351729, host=PWDFM026.wdf.sap.corp)
    SapWebDynproGenerationTemplates 6.4013.00.0000.20050628104636.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:19:30[UTC], changelist=356134, host=PWDFM026)
    sap.com/tcwddispwda
    No information available
    sap.com/pcui_gp~xssfpm
    SapDictionaryGenerationCore 6.4013.00.0000.20050606171348.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:02:08[UTC], changelist=351717, host=PWDFM026.wdf.sap.corp)
    SapDictionaryGenerationTemplates 6.4013.00.0000.20050606171348.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:02:19[UTC], changelist=351717, host=PWDFM026.wdf.sap.corp)
    SapGenerationFrameworkCore 6.4012.00.0000.20041104141254.0000 (release=630_VAL_REL, buildtime=2005-04-21:19:52:59[UTC], changelist=298452, host=PWDFM026.wdf.sap.corp)
    SapIdeWebDynproCheckLayer 6.4013.00.0000.20050606172055.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:08:32[UTC], changelist=351729, host=PWDFM026.wdf.sap.corp)
    SapMetamodelCommon 6.4013.00.0000.20050606171700.0000 (release=630_VAL_REL, buildtime=2005-07-04:19:56:31[UTC], changelist=351724, host=PWDFM026.wdf.sap.corp)
    SapMetamodelCore 6.4013.00.0000.20050606171700.0000 (release=630_VAL_REL, buildtime=2005-07-04:19:56:22[UTC], changelist=351724, host=PWDFM026.wdf.sap.corp)
    SapMetamodelDictionary 6.4013.00.0000.20050606171352.0000 (release=630_VAL_REL, buildtime=2005-07-04:19:59:38[UTC], changelist=351719, host=PWDFM026.wdf.sap.corp)
    SapMetamodelWebDynpro 6.4013.00.0000.20050609113138.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:05:19[UTC], changelist=352442, host=PWDFM026.wdf.sap.corp)
    SapWebDynproGenerationCTemplates 6.4013.00.0000.20050628104636.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:19:30[UTC], changelist=356134, host=PWDFM026)
    SapWebDynproGenerationCore 6.4013.00.0000.20050606172055.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:09:01[UTC], changelist=351729, host=PWDFM026.wdf.sap.corp)
    SapWebDynproGenerationTemplates 6.4013.00.0000.20050628104636.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:19:30[UTC], changelist=356134, host=PWDFM026)
    sap.com/tcwdcorecomp
    No information available
    Detailed Error Information
    Detailed Exception Chain
    com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Error while obtaining JCO connection.
         at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker$1.fillSldConnection(DataTypeBroker.java:90)
         at com.sap.dictionary.runtime.ProviderFactory.internalResolveLogicalNameToJCODestination(ProviderFactory.java:408)
         at com.sap.dictionary.runtime.ProviderFactory.resolveLogicalNameToJCODestination(ProviderFactory.java:354)
         at com.sap.dictionary.runtime.ProviderFactory.internalGetProvider(ProviderFactory.java:215)
         at com.sap.dictionary.runtime.ProviderFactory.getProvider(ProviderFactory.java:180)
         at com.sap.dictionary.runtime.DdDictionaryPool.getProvider(DdDictionaryPool.java:87)
         at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:73)
         at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:48)
         at com.sap.dictionary.runtime.DdBroker.getDataType(DdBroker.java:149)
         at com.sap.dictionary.runtime.DdBroker.getSimpleType(DdBroker.java:170)
         at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getSimpleType(DataTypeBroker.java:242)
         at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getDataType(DataTypeBroker.java:213)
         at com.sap.tc.webdynpro.progmodel.context.AttributeInfo.init(AttributeInfo.java:485)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.initAttributes(NodeInfo.java:771)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:756)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:761)
         at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)
         at com.sap.tc.webdynpro.progmodel.controller.Component.getCustomControllerInternal(Component.java:436)
         at com.sap.tc.webdynpro.progmodel.controller.Component.getController(Component.java:365)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.getPublicInterface(DelegatingComponent.java:142)
         at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdGetBackendConnectionsController(InternalFPMComponent.java:204)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:170)
         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:346)
         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.doGet(DispatcherServlet.java:48)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java: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:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:95)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:159)
    Caused by: com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscapeException: Error while obtaining JCO connection.
         at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:146)
         at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnectionUnMapped(SystemLandscapeFactory.java:172)
         at com.sap.tc.webdynpro.services.sal.sl.core.SystemLandscapeInternal.getJCOClientConnectionUnMapped(SystemLandscapeInternal.java:83)
         at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker$1.fillSldConnection(DataTypeBroker.java:77)
         ... 50 more
    Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve JCOClient name 'SAP_R3_SelfServiceGenerics_MetaData'. No such JCO destination is defined in the SLD
         at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter(JCOClientConnection.java:493)
         at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.init(AbstractJCOClientConnection.java:247)
         at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.<init>(AbstractJCOClientConnection.java:221)
         at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.<init>(JCOClientConnection.java:101)
         at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:144)
         ... 53 more
    Thanks, Neeta

  • Configure Managers Approval of Overtime in ECC5

    Hi,
    I'm trying to find where I can configure the columns for the managers approval of overtime view in the backend for ECC5.
    The IMG path in ECC6 Time sheet>Setting for all user interfaces>Approval procedure>Approve working times> Define field selection for Individual approval view, doesn't appear to exist in ECC5.
    Any help appreciated.
    Rob

    When the manager opens the overtime approval item, it displays the Sender Cost Centre, I need to display the Receiver Cost Centre and not the Sender Cost Centre.
    How can I do this in ECC5?

Maybe you are looking for