Error in psa  quality system

hi all,
i am getting the problem with psa. 2 records i am getting worng. loading the data from r/3 system.
Record 181 :0IOBJSV : Data record 181 ('0CorD '): Version '0Cor ' is not valid
Record 182 :0IOBJSV : Data record 182 ('0CorE '): Version '0Cor ' is not valid
regards
kk

We had this problem in a test. I found SAP Note: 1075643. It doesn't read as though it is going to help, but if you go to the table, you will see that Cor is being changed to CRO.
At the time of writing, I am waiting for this note to be applied to the source system by the basis team. However rather than go to the trouble of changing the psa data (every time a full load is done) you can change the root cause of the problem.
It is real estate related so not everyone gets this.
Here is the note content:
Symptom
The three figure value for the object type 'J2' (correction object) will be renamed for the language key 'EN' as 'CRO', as the old value leads to problems (duplicate records) with the DataSource 0IOBJSV_TEXT.
Reason and Prerequisites
This problem is caused by a design error.
Solution
The correction is delivered by Support Package.
To implement the correction in advance use the table view maintenance (SM30) in the table TBO01 to change the value OBART_LD to "CRO" for the key SPRAS = "EN", OBART = "J2".

Similar Messages

  • Data source Replication error in BW Quality system

    hi experts,
    when i replicate the data source in BW QUALITY SYSTEM it is giving the below error.
    Invalid call sequence for interfaces when rec
    changes.
    plz find the long text
    Message no. TK425
    Diagnosis
    The function you selected uses interfaces to record changes made to your objects in requests and tasks.
    Before you save the changes, a check needs to be carried out to establish whether the objects may be changed. This check must be performed before you begin to make changes.
    System Response
    The function terminates.
    Procedure
    The function you have used must correct the two Transport Organizer interfaces required. Contact your system administrator.
    After replication of data source changes are not reflecting in BW QUALITY SYSTEM.
    REGARDS
    venuscm

    Hi,
    Hope you have checked whether the DS has been transported to R/3 Quality and got activated  before Replication in BW quality.
    Check RFC connections between the systems.
    Check RSLOGSYSMAP table in both Bw & R/3 to confirm the system mappings.
    Try replicating again.......
    Regards,
    Suman

  • Error while transporting database index into quality system

    Hello,
    I am getting an error while transporting a new index in quality system.
    I have created a new index for table VBFA in TRD and activity the object without errors. I even adjusted the database table using database utility.
    While transporting the request there was a strange error "R3TRTABLVBFA was repaired in this system".
    I retransported the objects using a new request. However I still got the same error.
    Please help.

    Navin,
    No idea about the error you have mentioned but check the SAP Notes 185530 and see if you can avoid creating an index.In this Notes it is clearly mentioned on how to use VBFA table without any performance issues.
    K.Kiran.

  • Error While transporting Crystal Reports from BW DEV to Quality System

    Hi.
    I have developed a crystal report using the SAP menu. We saved the  report to SAP BW dev server using the SAP menu and published it to BOE.
    Now i want to transport my Crystal report to Quality system, I followed the same mechanism to transport crystal report which are aplied to other BW objects, but when i am trying to transport its giving me a short dump error:
    The error appears something like this:
    Error in the ABAP Application Program
    The Current ABAP program u201CSAPLRSCR_CEu201D  had to be terminated because it has come across a  statement that unfortunately cannot be executed.
    Function module u201C/CRYSTAL/PUBLISH_REPORTu201D was called
    With the parameter u201CI_REFRESH_FOLDER_INFOu201D.
    This parameter is not defined.
    This is first time i am transporting any crystal report to other bw system.
    Is there any document for transporting Crystal reports, I had searched SDN but didnt got any relevant documents.
    or is their any setting which need to be done in BW side.
    Any help will be appriciable.
    Thanks
    Anish

    Hi,
    I would suggest you open a case with support so that they can look at your system. In general you should be able to transport the Crystal REports object in the same way you transport a Bex query.
    ingo

  • Error while transporting Crystal Report from BW dev to Quality system.

    Hi.
    I have developed a crystal report using the SAP menu. We saved the report to SAP BW dev server using the SAP menu and published it to BOE.
    Now i want to transport my Crystal report to Quality system, I followed the same mechanism to transport crystal report which are aplied to other BW objects, but when i am trying to transport its giving me a short dump error:
    The error appears something like this:
    Error in the ABAP Application Program
    The Current ABAP program u201CSAPLRSCR_CEu201D  had to be terminated because it has come across a  statement that unfortunately cannot be executed.
    Function module u201C/CRYSTAL/PUBLISH_REPORTu201D was called
    With the parameter u201CI_REFRESH_FOLDER_INFOu201D.
    This parameter is not defined.
    This is first time i am transporting any crystal report to other bw system.
    Is there any document for transporting Crystal reports, I had searched SDN but didnt got any relevant documents.
    or is their any setting which need to be done in BW side.
    Any help will be appriciable.
    Thanks
    Anish

    Hi,
    I would suggest you open a case with support so that they can look at your system. In general you should be able to transport the Crystal REports object in the same way you transport a Bex query.
    ingo

  • Error while Replicating the Data Source in Quality System....

    Dear Expert,
       I have created a generic data source in R/3 Dev system and I replicated the data source to BW DEV system.  Everything is fine in DEV system.
    I have transported the Data Source to R/3 Quality System. And transported the related  objects in BW DEV system to BW QUALITY system.
    Now I am getting the error as follows :
    BW QUA System --> RSA1 --> Source System --> Data source Overview --> Sales & Distribution --> _REPLICATE_
    *DATASOURCE*.( clicked )
    Its moving to another screen (R/3 QUALITY) , but it is coming as a LOGIN screen. Its askong for the USER name and Password. And when I click on BACK button , its givin following pop-up
    RFC connection to source system LOGSYS is damaged  ==> no Metadata upload
    What could be the issue ?? Please suggest.
    Thanks,
    Sanjana

    Hi saveen,
    Yes I transported in that manner.
    I checked in Source System ( RSA13):
    Its giveng the pop-up  ,
                                    RFC connection check failed. Check connection
    Please suggest, how can I proceed ?
    Thanks,
    Sanjana

  • Error While importing SAP query into quality system

    Hi,
    When Itried to import the dataset(Transport Request)  generated in develoment system into Quality system I am getting the following error.
    Query already exists and Infoset contains a structures which is not there in data dictionary .
    How to oversome this error to import successfully into quality system
    thanks

    hi,
    You need to transport your Z tables to the quality.
    Make sure you transport all the data elements , domain.. etc to the quality.
    Thats why its giving you the error.
    It does not find the Z tables in Quality
    Regards,
    Vinod

  • While transporting Key Figures from Dev to Quality system, error occured.

    Hello Experts,
    While transporting Key Figures from Development to Quality system, I am getting this error : " /BIC/AZPA1R_CT40-/BIC/ZPA1RBA10 (specify reference table AND reference
    field)".
    Here, I have changed the data type of the key figure from Number type to Amount type. Then I activated them, captured in request and when transported I got the error saying "/BIC/AZPA1R_CT40-/BIC/ZPA1RBAL9 (specify reference table AND reference field)"
    These Key Figures are used in ODS.
    Is there I am missing something, please tell how can I make these transports successfull.
    Thanks Ishdeep.

    While transporting Key Figures from Development to Quality system, I am getting this error : " /BIC/AZPA1R_CT40-/BIC/ZPA1RBA10 (specify reference table AND reference
    Yes you missed to transport reference object.
    Previously key figure data type is number then you have changed to Amount. While changing data type to amount You should maintain reference char  like 0currency, Doc_currency......in the Unit/currency tab. ( If you use fixed unit or currency no need to maintain any reference Object).
    During transpotation you need to collect this reference char with main key figure and then transport.
    With Regards,
    Kishore.

  • Error in transporting the Transformation to Quality system

    Hi All,
    I am trying to transport the transformation which has field level routine as well as start and end routine.
    I have basically ehanced the standard routine and it works perfectly fine in dev server . I have even loaded the data and generated reports on this cube.
    Now i am trying to transport it to Quality system. It throws up some "syntax error in routine" error. Very strange.
    All my routine in Dev is working but during transport ther is some issue.
    i saw some post on same but they are suggesting to regenerate a new transformation. For me this will be a nightmare as there are so many routnies at field level and as end routine.
    Kindly suggest how can i rectify this error.
    Note:- I had generated this transformation via old update rules with Migration function.
    Thanks & Regards,
    Anup

    Hi Anindya,
    Below is my source code for one field level routine in transformation.
    FORM routine_0080
      TABLES
       p_monitor         STRUCTURE rsmonitor
      USING
        COMM_STRUCTURE TYPE _ty_s_sc_1__rule_52
      CHANGING
        RESULT         TYPE _ty_s_tg_1_full-srvclen
        RETURNCODE     LIKE sy-subrc
        ABORT          LIKE sy-subrc
      RAISING
        cx_sy_arithmetic_error
        cx_sy_conversion_error.
    * init variables
    * fill the internal table "MONITOR", to make monitor entries
      DATA: ultimo LIKE sy-datum.
      IF g_record_no <> RECORD_NO.
        g_record_no = RECORD_NO.
        CLEAR: employee_wa, person_wa.
        CLEAR: employee_md, person_md.
      ENDIF.
      PERFORM read_md_employee
              USING    COMM_STRUCTURE-employee
                       COMM_STRUCTURE-calday
                       RECORD_NO
                       RECORD_ALL
                       SOURCE_SYSTEM
              CHANGING employee_wa
                       RETURNCODE.
      employee_md = employee_wa.
      PERFORM calculate_ultimo
              USING COMM_STRUCTURE-calday+0(6)
                     RECORD_NO
                     RECORD_ALL
                     SOURCE_SYSTEM
              CHANGING ultimo
                       RETURNCODE.
      IF NOT employee_md-entrydate IS INITIAL.
        RESULT = ultimo+0(4) - employee_md-entrydate+0(4).
        IF ultimo+4(4) LT employee_md-entrydate+4(4).
          RESULT = RESULT - 1.
        ENDIF.
      ENDIF.
    * result value of the routine
    * if the returncode is not equal zero, the result will not be updated
      RETURNCODE = 0.
    * if abort is not equal zero, the update process will be canceled
      ABORT = 0.
      p_monitor[] = MONITOR[].
      CLEAR:
        MONITOR[].
    CLASS lcl_transform IMPLEMENTATION.
      METHOD compute_0AGE_RANGE.
    *   IMPORTING
    *     request     type rsrequest
    *     datapackid  type rsdatapid
    *     SOURCE_FIELDS-CALDAY TYPE /BI0/OICALDAY
    *     SOURCE_FIELDS-EMPLOYEE TYPE /BI0/OIEMPLOYEE
    *    EXPORTING
    *      RESULT type _ty_s_TG_1-AGE_RANGE
        DATA:
          MONITOR_REC    TYPE rsmonitor.
    *$*$ begin of routine - insert your code only below this line        *-*
      Data:
        COMM_STRUCTURE   type _ty_s_SC_1__RULE_20,
        l_subrc          type sy-tabix,
        l_abort          type sy-tabix,
        ls_monitor       TYPE rsmonitor,
        ls_monitor_recno TYPE rsmonitors.
      data:
        l_monitor        type standard table of rsmonitor.
      REFRESH:
        MONITOR.
    * Runtime attributs
        SOURCE_SYSTEM  = p_r_request->get_logsys( ).
        MOVE-CORRESPONDING SOURCE_FIELDS to COMM_STRUCTURE.
    *  Migrated update rule call
      Perform routine_0070
      TABLES
        l_monitor
      USING
        COMM_STRUCTURE
      CHANGING
        RESULT
        l_subrc
        l_abort.
    *-- Convert Messages in Transformation format
        LOOP AT l_monitor INTO ls_monitor.
          move-CORRESPONDING ls_monitor to MONITOR_REC.
          append monitor_rec to MONITOR.
        ENDLOOP.
        IF l_subrc <> 0.
          RAISE EXCEPTION TYPE CX_RSROUT_SKIP_RECORD.
        ENDIF.
        IF l_abort <> 0.
          RAISE EXCEPTION TYPE CX_RSROUT_ABORT.
        ENDIF.
    I am not able to change the code which are marked with " * ". Where can i change the code here?
    Regards,
    Anup

  • Error in importing Business system in Quality System

    Hi
    We are currently on PI 7.1 EHP1 and SLD Setting on CIM 1.5 and CR 5.0 in XIA(Quality System) while XID (Developement) has CIM 1.6 and CR 4.5.We are having local SLD for XID and XIA both.
    We are trying to import the buisness system BS_CATALOG_REC in our Quality(XIA) which was created in our developement system(XID).While trying to do so we are getting the error as below while trying to import using CTS+ as well as from file system level(import/export option in Integration Builder)
    =================================================================================
      CTS Import Service - Version 0.94 04.04.2008
    ========================================================================
      Deploy Web service destination = CTSDEPLOY
      Directory = /usr/sap/trans/data
      SDM Deploy URL =
      SLD Deploy URL =
      XI Deploy URL = http://st2777.uname.telecom.co.nz:52400
      Start import with id:8021281385D31DEFBCC0F3EF281C9FB9
      DeployProxy (patch level:0) called with followingparameters:
      Deployable(0)
      Deployable-Type:1
      Deployable-Id:80144FF9C93B1DDFBCC0EDC64DC68BD6
      Deployable-TransportContainerId:XIDK900018
      Deployable-ContentLocator:/usr/sap/trans/data/XIDK900018/6d1af3e0f20711dfb8e000144ff9c93b
      Property(0)
      Property-key:TARGETSYSTEMID Property-value:XIA
      Begin CommunicationData-Type[0]:1
      CommunicationData-Address:http://st2777.uname.telecom.co.nz:52400/dir
      CommunicationData-Host:st2777.uname.telecom.co.nz
      CommunicationData-Port:52400
      CommunicationData-User:'filled'
      CommunicationData-Password:'filled'
      Importing archive:6d1af3e0f20711dfb8e000144ff9c93b
      com.sap.aii.ibtransportclient.XiTransportException: caused by: ClientServerException exception:Impo
      >>>rt failed because of business system transfer of object Communication Component   BS_Catalog_REC: O
      >>>bligatory transport target for business system BS_Catalog_REC not found in System Landscape Director
    >>>y caused by: com.sap.aii.ib.core.transport.api.PostprocessingException: Import failed because of bus
    >>>iness system transfer of object Communication Component   BS_Catalog_REC: Obligatory transport targ
    >>>et for business system BS_Catalog_REC not found inSystem Landscape Directory caused by: com.sap.aii
    >>>.util.hmi.api.HmiMethodFault: caused by: ClientServerException exception:Import failed because of b
    >>>usiness system transfer of object Communication Component   BS_Catalog_REC: Obligatory transport ta
    >>>rget for business system BS_Catalog_REC not foundin System Landscape Directory caused by: com.sap.a
    >>>ii.ib.core.transport.api.PostprocessingException:Import failed because of business system transfer
    >>>of object Communication Component   BS_Catalog_REC: Obligatory transport target for business system
    >>>BS_Catalog_REC not found in System Landscape Directory
    End CommunicationData-Type[0]:1
    End import with returncode:'8'
    Deployment
    End date and time : 20101117180041
    Ended with return code:  ===> 8 <===
    *These are options we tried in DEV*
    In Developement (XID) we tried creating the business groups
    TEST_DEV
    TEST_QA
    TEST_PRD
    Whn we try to assign buisness system to the above 3 groups,All systems in our XID are by default getting assigned to TEST_DEV Group and we are unable to give the target for business system (BS_CATALOG_REC) in target tab in PI 7.1 EHP1.
    In DEV SLD:
    In group TEST_DEV,we have assigned Buisness system BS_CATALOG_REC which is poinitng to XID Integration Server
    In Group TEST_QA,we are manually creating a Buisness system,BS_CATALOG_REC_QA to which we are unable to assign the Integration Server for XIA.
    In Group TEST_PRD, created theBusines system BS_CATALOG_REC_PRD and have left the integration server option "NONE"
    and Tried to create target for the BS_CATALOG_REC. But i could not able to select the target system.
    Can you pls guide if we need to have the entry for INTEGRATION_SERVER_XIA in our XID-Developement SLD landscape.We also have tried using "None" option,however in developement TEST_DEV buisness system target,we are not getting any values.
    We have just 1 Buisness system which needs to be imported into Quality and beacuase of this we are not able to import in ID the configuration objects as can be seen in error text above.
    Can anyone help !!
    Thanks

    Hello
    Check the link [Configuring Groups and Transport Targets|http://help.sap.com/saphelp_nwpi71/helpdata/EN/ef/a21e3e0987760be10000000a114084/frameset.htm]                                              
    If the groups and targets are correctly configured, apply the note #1059576 - XI Directory import fails due to inconsistent SLD host names.
    Regards
    Mark

  • Error on display of remodelling rule in Quality System

    Hi,
    I have created a remodelling rule to delete a characteristic infoobject from a cube and the same in working fine in the development system.
    I transported the remodelling rule to the Quality system. the same was transported with out any error.
    But when I go the RSA1 --> adminstration -->remodelling and select the remodelling rule from dropdown and click on display, I am getting an error message.
    Namespace '/BIC/' must be set to 'changeable' (transaction SE06)
    Message no. R7063
    Has anyone encoutered the same error ?
    Any help is resolving the above error will be highly appreciated and rewarded.
    Thanks in advance
    Venkata

    Hi Venkata,
    I have not worked with the remodelling. But Remodelling is changing the InfoCube definition in the QA/Prod systems directly.
    I had this issue earlier when I tried to modify something in the QA system directly. The issue was because the /BIC/ namespace was non-modifiable in QA. As this setting is system specific and need not be transported we had asked Basis to make the change in QA.
    Hope this helps.
    Regards
    Kumar

  • CX_RSR_X_MESSAGE Data load error in Quality system

    Hi
    We are on BI.7 and trying to load Technical content data for first time in Quality system .
    We get the following error :
    Runtime Errors UNCAUGHT_EXCEPTION
    Except. CX_RSR_X_MESSAGE
    for all the technical content data load.
    The other data loads are working fine in the quality system.
    We searched a lot on the forum and got various solutions like try out note 615389, 963760 etc.. But none of them are working fine for us.
    Please suggest.
    Thanks you for your help.
    Gaurav

    Hi
    The error log is as follows -
    Runtime Errors         UNCAUGHT_EXCEPTION
    Exception              CX_RSR_X_MESSAGE
    Date and Time          23.01.2009 10:06:08
    Short text
         An exception occurred that was not caught.
    What happened?
         The exception 'CX_RSR_X_MESSAGE' was raised, but it was not caught anywhere
          along
         the call hierarchy.
         Since exceptions represent error situations and this error was not
         adequately responded to, the running ABAP program 'SAPLRRMS' has to be
         terminated.
    What can you do?
         Note down which actions and inputs caused the error.
         To process the problem further, contact you SAP system
         administrator.
         Using Transaction ST22 for ABAP Dump Analysis, you can look
         at and manage termination messages, and you can also
         keep them for a long time.
    Error analysis
        An exception occurred which is explained in detail below.
        The exception, which is assigned to class 'CX_RSR_X_MESSAGE', was not caught
         and
        therefore caused a runtime error.
        The reason for the exception is:
        No text available for this exception
    How to correct the error
        If the error occures in a non-modified SAP program, you may be able to
        find an interim solution in an SAP Note.
        If you have access to SAP Notes, carry out a search with the following
        keywords:
        "UNCAUGHT_EXCEPTION" "CX_RSR_X_MESSAGE"
        "SAPLRRMS" or "LRRMSU13"
        "RRMS_X_MESSAGE"
        If you cannot solve the problem yourself and want to send an error
        notification to SAP, include the following information:
        1. The description of the current problem (short dump)
           To save the description, choose "System->List->Save->Local File
        (Unconverted)".
    It gives a error in the last step of executing infopackage wherein the data is to be updated to the infocube.
    I checked with Basis team. There is no tablespace problem as well.
    Regards
    Gaurav

  • Unable to load the data into Cube Using DTP in the quality system

    Hi,
    I am unable to load the data from PSA to Cube using DTP in the quality system for the first time
    I am getting the error like" Data package processing terminated" and "Source TRCS 2LIS_17_NOTIF is not allowed".
    Please suggest .
    Thanks,
    Satyaprasad

    Hi,
    Some Infoobjects are missing while collecting the transport.
    I collected those objects and transported ,now its working fine.
    Many Thanks to all
    Regards,
    Satyaprasad

  • Issue in Process Controlled workflow for Shopping cart in Quality system.

    Hello All,
    I ahve configured a Process controlled workflow in SRM 7.0  with custom resolver, and I am facing an issue taht the Workflow works well in Development but in Quality the approvers are dropped after SC is ordered in Quality system.
    The SC Workflow drops the approvers picked up from the Interface  method /SAPSRM/IF_EX_WF_RESP_RESOLVERGET_AREA_TO_ITEM_MAP and IF_EX_WF_RESP_RESOLVERGET_APPROVERS_BY_AREA_GUID of BADI /SAPSRM/BD_WF_RESP_RESOLVER. The approvers can be seen in the shopping cart Approval preview Tab until the SC is ordered.
    I have compared the OSS notes relevant for Workflow, all of them have been transported, Also I compared and checked general Workflow settings, BRF Config and  Process level  settings in Dev and Quality, everything is same.
    Also while debugging; the approvers can be seen in the decision set table in the create_process_forecast method of class /SAPSRM/CL_WF_PROCESS_MANAGER.
    Kindly let me know what else i can check to find the root cause.
    Thank you in advance for help!
    Regards
    Prasuna.

    Hello Vinita;
    Thanks for the input and sorry for the not so "ASAP" reply;
    From what I'm seeing in from your 2 screenshot, i strongly believe that the problem is even before the Z implementation /SAPSRM/IF_EX_WF_RESP_RESOLVER~GET_APPROVERS_BY_AREA_GUID (in which the FM i ZSRM_GET_USER_FROM_PGRP is called. I think the problem could be in the process level determination  ZSRM_WF_BRF_0EXP000_SC_APP100. Let me explain:
    In your  cases where not buyer is determined,  in the approval tab there is not even a process level for buyer approval. If the problem were indeed in the implementation  /SAPSRM/IF_EX_WF_RESP_RESOLVER~GET_APPROVERS_BY_AREA_GUID  then the process level would be there, but the system will display, instead of the name of the buyer(if the buyer determination fails) a red label with the message:  "With the strategy "Buyer determination" an approver could not be determined (or something like that..please check the image at the end of the text)".
    I can propose a way to discard this: Implement the method /SAPSRM/IF_EX_WF_RESP_RESOLVER~GET_FALLBACK_AGENTS of class ZCL_BADI_SC_WC (in case you didn't know, in this method you can specify an "default" approver in case that the determination of approver in GET_APPROVERS_BY_AREA_GUID fails). The idea is to specify an default approval and see how it behaves:
    If the user you indicated in the method GET_FALLBACK_AGENTS appears as approver, then yes, the problem is arises from implementation GET_APPROVERS_BY_AREA_GUID, in which case it could be a data problem (peharps in pposa_bbp?). You could also check in TX SU53 with the users with this problem to see if there's a missing authorization objetc.
    If, in the other hand, the "default" approver is not shown, it means that the process level buyer determination is not even called, so you should check in more detail ZSRM_WF_BRF_0EXP000_SC_APP100 and /SAPSRM/CL_WF_PROCESS_MANAGER > Determine process restart –method ----- (i have never used this method, so i could not tell if  it could be the source of the problem).
    Also, you could implement the method GET_FALLBACK_AGENTS in this way so the default approver would be the WF administrator indicated in the customizing (or you could just append directly any user you want):
    METHOD /SAPSRM/IF_EX_WF_RESP_RESOLVER~GET_FALLBACK_AGENTS.
       DATA: lv_admin_expr TYPE swd_shead-admin_expr,
             lv_admin      TYPE swd_shead-wfi_admin,
             lv_admin_type TYPE sy-input,
             ls_agent      TYPE  /sapsrm/s_wf_approver.
       CALL FUNCTION 'SWD_WF_DEFINITION_ADMIN_GET'
         IMPORTING
           default_admin_expr = lv_admin_expr
           default_admin      = lv_admin
           default_admin_type = lv_admin_type.
       ls_agent-approver_id = lv_admin.
       APPEND ls_agent TO rt_agent.
    ENDMETHOD.
    Error of agent determination:
    Please let me know the result of the test with the implementation of method GET_FALLBACK_AGENT. By doing this we could ensure if really the problem is in method GET_APPROVERS_BY_AREA_GUID or before.  I just made the test in our system and I'm almost sure that you wont get the default approver, but i could be wrong. 
    Any question please let me know.
    Best regards
    Cristian R.

  • Unable to view the messages in sxmb_moni - Quality System

    Hi,
    We have got a strange problem in the diaplay view for  TCode - sxmb_moni for our Quality system. 
    We have different scenarios - Idoc to Web Service (synchronous using BPM), Proxy to Web Service both inbound and outbound etc all to the same Webservice.
    Whenever a scenario executes in the Development system, we are able to view the WSDL data that is sent to the Web Service along with the response given by the Web Service in all the cases successfull or unsuccessful.
    But if the scenario is executed in the Quality system there are a few different cases for the display view in sxmb_moni :
    Case 1 ) Incase of IDoc to Webservice "Successfull " (ECC -> PI-> Webservice)Scenario we are able to see only the data that is sent to the Webservice. We are not able to view the WSDL sent to the Webservice and the Response received.
    Case 2)  Incase of IDoc to Webservice " Unsuccessfull / Error " (ECC -> PI-> Webservice) Scenario We are able to view all the data that is sent to the Webservice right from the Idoc to BPM, the WSDL, the response received.
    Case 3) In case of Proxy scenarios both inbound and outbound "Successfull ", we are neither able to view the data that is sent to the Webservice or the response received from the Web Service.
    Case 4 ) In case of Proxy scenarios both inbound and outbound "Unsuccessfull ", we are able to view only the error and not the data that is exchanged between both the systems.
    The point to be noted is that in case of Successfull executions the data is well received at the Web Service end.
    What could be  possibly missing between the two systems Development and Quality due to which we are not able to view messages in the T-Code SXMB_MONI
    Thanks a lot for all the inputs!

    Hi Lalit,
    In sxmb_ad transaction, go to configuration integration engine (edit) and set Trace Level = 3.
    See that:
    The specified item was not found.
    Regards,
    Carme.

Maybe you are looking for

  • Getting the standard Notes App for Mac

    My ipad and iphone have the notes app. How do i get notes on my Mac? It is not available in the Mac AppStore and I can not find it among the apps included with the Mac. I have Mobile Me but I can't sync my notes only the contacts and calendar.?

  • Financial reporting studio - Invalid Picture

    Hi; I am trying to add a new logo into one of our reports (Oracle Hyperion Financial reporting studio, Fusion Edition), however after inserting the new image I get the following error message " Invalid Picture". I have changed the format of the pictu

  • New g4 MDD user fan question

    hey ya'll, i just picked up a dual 1.25, airport, bluetooth, superdrive, 17inch studio display, and pair of 120 gig harddrives MDD g4, for a ridiculously low price. how loud are these fans supposed to be? i'm hearing sort of a clunking sound, havn't

  • Any help on this? UI Designer not allowing edit.

    I created a new solution in 3.5... Added a Webservice.. then Created a new Workcenter.. However when trying to edit that view in the UI Designer i get Exception Message: Display/Edit operation failed to execute. InnerException Message:Metadata-Backen

  • Disable synchronization in Mail

    This request is probably the opposite of what everyone else wants, and that´s why I can´t find the answer anywhere. I have 2 macs using Mail, and with the 3 same e-mail accounts set up in both. I used to have POP mails, and a few weeks ago I changed