Problem in the configuartion SAP BW 3.5!

hello all,
i`am in a process of installing SAP BW 3.5 on SAPWAS along with SAPGUI6.40.i`am facing problems in configuring the SAPGUI as well as SAP BW JAVA components.
In SAPGUI configuration,i`am giving all the parameters like application server,system id and system number correctly but still when you log on to the system it says "waiting for response" and never connetcs after that.
In SAP BW JAVA componets configuartion , i had configured all the connectors namely BI-JDBC,BI-ODBO,BI-SAP QUERY and BI-XMLA.when i check the connector installation by displaying connector pages (using URL) it is giving me again error saying " not found ".it is the case with all the four connectors.
can i get any suggestions for remedy of my problems?
thanks in advance
ravi

1. Trying reboothing your pc and try again
2. Try from a friends pc
3. Try logging to other systems
4. Try to ping that server name or IP address from your run->cmd command
Rgds

Similar Messages

  • There is a problem with the server's security certificate. The security certificate is not from a trusted certifying authority. SAP Business One is unable to connect to the server

    Hello,
    I have an issue with connecting client SB1H on Windows, the scenario is as follows:
    1.- Server:
         Suse Linux Enterprise Server 11.3 kernel version: 3.0.76-0.11 IBM
         NDB and Server are review 69 SP06
    2.- Client:
         Windows 8 Pro Virtual Machine on Microsoft Hyper-V
         SB1H PL 11 version 32bits    
         SAP HANA Studio version 1.0.60
    When I run SB1H the following message appears:
    There is a problem with the server's security certificate. The security certificate is not from a trusted certifying authority. SAP Business One is unable to connect to the server.
    Any idea what could be the solution?

    Hi,
    Please check SAP notes:
       1993392 - Server components setup wizard: New default values for certificates and single sign-on option
    1929288 - Do not configure SSL for XApp during installation or upgrade if XApp is installed on a different machine than the SAP HANA server
    Thanks & Regards,
    Nagarajan

  • SAP CRM middleware problem (sysfail ) The current application has triggered a termination with short dump

    i'm having a proplem during  starting initial load although i'm using the best practice documents C71 and B09 and all the configration was done by them .... could any one help ??

    this is the first dump error for my RFCUSER on the ECC server
    Category               ABAP Programming Error
    Runtime Errors         MESSAGE_TYPE_X
    ABAP Program           SAPLCRMC
    Application Component  CA
    Date and Time          05.03.2014 17:50:47
    Short Text
         The current application has triggered a termination with a short dump.
    What happened?
         The current application program has detected a situation that should
         not occur. A termination with short dump has therefore been triggered
         by the key word MESSAGE (type X).
    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
    Error analysis
        Short text of the error message:
        See SAP Note 1498111
        Long text of the error message:
         Diagnosis
         System Response
         Procedure
             Refer to the SAP Note that was mentioned.
         Procedure for System Administration
        Technical information about the message:
        Message class....... C_
        Number.............. 330
        Variable 1.......... 1498111
        Variable 2..........
        Variable 3..........
        Variable 4.......... " "
    How to correct the error
        Probably the only way to eliminate the error is to correct the program.
        If the error occurs in a non-modfied SAP program, you might be able to
        find a solution in the SAP Notes system. If you have access to the SAP
        Notes system, check there first using the following keywords:
        "MESSAGE_TYPE_X"
        "SAPLCRMC" bzw. LCRMCF0C
        "CHECK_CRMATAB"
        If you cannot solve the problem yourself, please send the following
        information to SAP:
        1. This description of the problem (short dump)
        To do this, choose  System -> List -> Save -> Local File (unconverted)
        on the screen you are in now.
        2. A suitable system log
        To do this, call the system log in transaction SM21. Restrict the time
        interval to ten minutes before the short dump and five minutes after
        it. In the display, choose System -> List -> Save -> Local File
        (unconverted).
    3. If these are programs of your own, or modified SAP programs: Source
    code of these programs
    To do this, choose  More Utilities -> Upload/Download -> Download in
    the Editor.
    4. Details regarding the conditions under which the error occurred or
    which actions and input caused the error.
    thanks

  • Space problems with the SAP Database MS SQL 2000

    Hi,
    Actually, I have a size problem with the database, I have MS SQL Server 2000 with Service Pack4 on a Windows 2003 Server environment that is my DataBase Server of my ERP ECC 6.0. On the other hand I have a storage where I have 229 Gb of free space used only for the database files of the SAP data and the SAP log file.
    But when I check the DB space allocation on trx. DB02 I saw this:
    3 Database files and 1 transaction log:
    The 3 database files are: PRDDATA1 (size 15,313 MB used 15016 MB) , PRDDATA2 (size 14106 MB used 13984 MB), PRDDATA3 (size 14472 MB used 14352 MB) and the log file is PRDLOG1 ( size 1000 MB) all of them with no limit option and growth by 10%.
    So I went to the SQL Enterprise Manager and I saw that my Database PRD properties and I got this information:
    My database size is 44892.48 Mb size with only 1330.36 Mb of free space and that is alarming.
    So the question here is how ,if I have a storage where the sap data is storing with 229 Gb of free space, can I make the database files grow up in order to use all the available space of my storage.
    Can you help me please because it is critical being my productive system?
    Best Regards
    Erik Espinosa

    I resolved this issue myself. Thanks for all your help.
    Best Regards,
    Erik Espinosa

  • Problems with the sap* password

    Hi,
    i have a problem with the sap* password.
    I tried my masterpassword but it did not work.
    So i tired the following from the Tread: Password problem with user DDIC
    resetting password for sap*
    sqlplus "/as sysdba"
    sql> update sapsr3.usr02 set bname='SAP1' where bname='SAP' and MANDT=000;
    sql> commit;
    Bud it did not work. After i tried to delete the sap*1 from the table sapsr3.usr02 but it did not work.
    sql>delete from sapsr3.usr02 where mandt='000' and bname = 'SAP*1';
    I also restarted the instance after the commands. But i can not logon with 'sap*' and the password   'pass' .
    Mybe someone can help me?
    Regards
    Mike

    Starting with release 7.00 based system you have to set
    login/no_automatic_user_sapstart=0
    in your instance profile and restart the instance.
    Markus

  • A Problem with the SAP NetWeaver Installation

    Hello Everybody,
    I'm installing the sap netweaver application but I Have a problem after the definition of the 4 passwords.
    After that step I Have a step named :" DVD/CD Browser > Software Package Check" And the SapInst ask me to enter the location of the "Migration Export" Package, But I didn't find it and I cannot go to the next step and continue the installation.
    I Thank u all for your helps.
    Enjoy.

    Check out these weblogs.........
    /people/sugree.phatanapherom/blog/2005/08/17/a-visual-installation-guide-on-sneak-preview-sap-netweaver-04-abap-edition
    /people/rich.heilman2/blog/2005/08/17/netweaver-sneak-preview--abap-stack-installation--my-experience

  • Problem in connection from SAP to XI

    Hi Guys,
    I have problem to connect from SAP to XI.  We have existing SAP R/3 (IS-H) and we newly installed XI. We decided to use ABAP proxy to send data from SAP to XI. When I go to SPROXY system showing ‘No Connection to Integration Builder’. Please kindly advice what configuration we need to in SAP side in order to connect XI.
    It’s Very Urgent. Please advice me.
    Thanks in Advance.
    Regards,
    Anil.

    Anil,
    could you please have a look to SAP Note 689847 - XI 3.0: SPROXY - No connection to the Integration Builder
    Cheers,
    -Sunil

  • Urgant problem for the updating problem  HELP

    Dear sir/miss,On 2008.12.01 one of our partner company consultant,setup an update(SAPKH50016 AND SAPKH50017) page on our production system without and test in the test system.
    Now our transaction code CV03N,CV02N,CV01N can not be used,jump out abap problems as below:
    It's already give us very big impact to our SAP system,so please tell me how to deal with it.
    "Runtime Errors MOVE_CAST_ERROR
    Exceptn CX_SY_MOVE_CAST_ERROR
    Date and Time 2008.12.02 08:23:43
    ShrtText
    A dynamic type conflict occurred during reference assignment.
    What happened?
    Error in ABAP application program.
    The current ABAP program "CL_EX_DOCUMENT_MAIN02=========CP" had to be
    terminated because one of the
    statements could not be executed.
    This is probably due to an error in the ABAP program.
    What can you do?
    Print out the error message (using the "Print" function)
    and make a note of the actions and input that caused the
    error.
    To resolve the problem, contact your SAP system administrator.
    You can use transaction ST22 (ABAP Dump Analysis) to view and administer
    termination messages, especially those beyond their normal deletion
    date.
    is especially useful if you want to keep a particular message.
    Error analysis
    An exception occurred. This exception is dealt with in more detail below
    . The exception, which is assigned to the class 'CX_SY_MOVE_CAST_ERROR', wa
    neither
    caught nor passed along using a RAISING clause, in the procedure
    "IF_EX_DOCUMENT_MAIN02~D100_BEFORE_PAI" "(METHOD)"
    Since the caller of the procedure could not have expected this exception
    to occur, the running program was terminated.
    The reason for the exception is:
    A 'CAST' operation ('?=' or 'MOVE ?TO') tried to assign an object or
    interface variable to a reference variable.
    However, the contents of the source variable do not fit in the target.
    Source type. "\CLASS=ZCL_IM_DOCUMENT_MAIN02"
    Target type: "\INTERFACE=IF_EX_DOCUMENT_MAIN02"
    How to correct the error
    If the error occurred in one of your own programs or in an SAP program
    that you modified, try to correct it yourself.
    You may able to find an interim solution to the problem
    in the SAP note system. If you have access to the note system yourself,
    use the following search criteria:
    "MOVE_CAST_ERROR" CX_SY_MOVE_CAST_ERRORC
    "CL_EX_DOCUMENT_MAIN02=========CP" or "CL_EX_DOCUMENT_MAIN02=========CM007"
    "IF_EX_DOCUMENT_MAIN02~D100_BEFORE_PAI"
    If you cannot solve the problem yourself and you wish to send
    an error message to SAP, include the following documents:
    1. A printout of the problem description (short dump)
    To obtain this, select in the current display "System->List->
    Save->Local File (unconverted)".
    2. A suitable printout of the system log
    To obtain this, call the system log through transaction SM21.
    Limit the time interval to 10 minutes before and 5 minutes
    after the short dump. In the display, then select the function
    "System->List->Save->Local File (unconverted)".
    3. If the programs are your own programs or modified SAP programs,
    supply the source code.
    To do this, select the Editor function "Further Utilities->
    Upload/Download->Download".
    4. Details regarding the conditions under which the error occurred
    or which actions and input led to the error.
    The exception must either be prevented, caught within the procedure
    "IF_EX_DOCUMENT_MAIN02~D100_BEFORE_PAI"
    "(METHOD)", or declared in the procedure's RAISING clause.
    To prevent the exception, note the following:
    System environment
    SAP Release.............. "640"
    Application server....... "ciserver"
    Network address.......... "172.31.120.37"
    Operating system......... "Linux"
    Release.................. "2.6.9-11.19AXsmp"
    Hardware type............ "x86_64"
    Character length......... 16 Bits
    Pointer length........... 64 Bits
    Work process number...... 3
    Short dump setting....... "full"
    Database server.......... "diserver"
    Database type............ "ORACLE"
    Database name............ "PRD"
    Database owner........... "SAPPRD"
    Character set............ "C"
    SAP kernel............... "640"
    Created on............... "May 22 2006 19:43:51"
    Created in............... "Linux GNU SLES-9 x86_64 cc3.3.3"
    Database version......... "OCI_920 "
    Patch level.............. "129"
    Patch text............... " "
    Supported environment....
    Database................. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE
    10.2.0.."
    SAP database version..... "640"
    Operating system......... "Linux 2.6"
    Memory usage.............
    Roll..................... 16192
    EM....................... 12569568
    Heap..................... 0
    Page..................... 57344
    MM Used.................. 2076240
    MM Free.................. 2111024
    SAP Release.............. "640"
    User and Transaction
    Client.............. 600
    User................ "MENGQC001"
    Language key........ "E"
    Transaction......... "CV03N "
    Program............. "CL_EX_DOCUMENT_MAIN02=========CP"
    Screen.............. "SAPLCV110 0100"
    Screen line......... 43
    Information on where terminated
    The termination occurred in the ABAP program "CL_EX_DOCUMENT_MAIN02=========CP"
    in "IF_EX_DOCUMENT_MAIN02~D100_BEFORE_PAI".
    The main program was "SAPLCV110 ".
    The termination occurred in line 134 of the source code of the (Include)
    program "CL_EX_DOCUMENT_MAIN02=========CM007"
    of the source code of program "CL_EX_DOCUMENT_MAIN02=========CM007" (when
    calling the editor 1340).
    Processing was terminated because the exception "CX_SY_MOVE_CAST_ERROR"
    occurred in the
    procedure "IF_EX_DOCUMENT_MAIN02~D100_BEFORE_PAI" "(METHOD)" but was not
    handled locally, not declared in the
    RAISING clause of the procedure.
    The procedure is in the program "CL_EX_DOCUMENT_MAIN02=========CP ". Its source
    code starts in line 1
    of the (Include) program "CL_EX_DOCUMENT_MAIN02=========CM007 ".
    ource Code Extract
    ine SourceCde
    104 CLEAR data_ref.
    105 GET REFERENCE OF OKCODE INTO data_ref.
    106 CALL METHOD <flt_cache_line>-eo_object->set_parameter(
    107 im_parmname = 'OKCODE'
    108 im_value = data_ref ).
    109
    110 CLEAR data_ref.
    111 GET REFERENCE OF DRAW INTO data_ref.
    112 CALL METHOD <flt_cache_line>-eo_object->set_parameter(
    113 im_parmname = 'DRAW'
    114 im_value = data_ref ).
    115
    116 CALL METHOD <flt_cache_line>-eo_object->evaluate
    117 IMPORTING
    118 ex_exception = exc
    119 EXCEPTIONS
    120 raise_exception = 1
    121 OTHERS = 2.
    122 IF sy-subrc = 2.
    123 MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
    124 WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
    125 ELSEIF sy-subrc = 1.
    126 CASE exc-exceptn_nm.
    127 WHEN 'CANCEL'.
    128 MESSAGE ID exc-msgid TYPE exc-msgty NUMBER exc-msgno
    129 WITH exc-msgv1 exc-msgv2 exc-msgv3 exc-msgv4
    130 RAISING CANCEL.
    131 ENDCASE.
    132 ENDIF.
    133 WHEN OTHERS.
    EXITINTF ?= <flt_cache_line>-OBJ.
    135 CALL METHOD EXITINTF->D100_BEFORE_PAI
    136 EXPORTING
    137 TCODE = TCODE
    138 CHANGING
    139 OKCODE = OKCODE
    140 DRAW = DRAW
    141 EXCEPTIONS
    142 CANCEL = 1.
    143 case sy-subrc.
    144 when 1.
    145 raise CANCEL.
    146 endcase.
    147 ENDCASE.
    148
    149 CALL FUNCTION 'PF_ASTAT_CLOSE'
    150 EXPORTING
    151 OPENKEY = 'S61ZFJapGHhX00002X5BGm'
    152 TYP = 'UE'.
    153 ENDLOOP.
    Contents of system fields
    Name Val.
    SY-SUBRC 0
    SY-INDEX 0
    SY-TABIX 14
    SY-DBCNT 14
    SY-FDPOS 1
    SY-LSIND 0
    SY-PAGNO 0
    SY-LINNO 1
    SY-COLNO 1
    SY-PFKEY D100DISPLAY
    SY-UCOMM BACK
    SY-TITLE Display Document: Initial Screen
    SY-MSGTY
    SY-MSGID
    SY-MSGNO 000
    SY-MSGV1
    SY-MSGV2
    SY-MSGV3
    SY-MSGV4
    Active Calls/Events
    No. Ty. Program Include Line
    Name
    3 METHOD CL_EX_DOCUMENT_MAIN02=========CP CL_EX_DOCUMENT_MAIN02=========CM007 134
    CL_EX_DOCUMENT_MAIN02=>IF_EX_DOCUMENT_MAIN02~D100_BEFORE_PAI
    2 FORM SAPLCV110 LCV110F19 124
    D100_CONSUME_EVENTS
    1 MODULE (PAI) SAPLCV110 LCV110I08 10
    D100_FCODE
    Chosen variables
    Name
    Val.
    No. 3 Ty. METHOD
    Name CL_EX_DOCUMENT_MAIN02=>IF_EX_DOCUMENT_MAIN02~D100_BEFORE_PAI
    TCODE
    CV03
    45332222222222222222
    36030000000000000000
    00000000000000000000
    00000000000000000000
    OKCODE
    BACK
    4444222222222222222222222222222222222222222222222222222222222222222222
    213B000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000
    DRAW
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    SY-MSGV1
    22222222222222222222222222222222222222222222222222
    00000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    EXC-MSGV1
    22222222222222222222222222222222222222222222222222
    00000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    SY-MSGV2
    22222222222222222222222222222222222222222222222222
    00000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    EXC-MSGV2
    22222222222222222222222222222222222222222222222222
    00000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    SY-MSGV3
    22222222222222222222222222222222222222222222222222
    00000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    EXC-MSGV3
    22222222222222222222222222222222222222222222222222
    00000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    SY-MSGV4
    22222222222222222222222222222222222222222222222222
    00000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    EXC-MSGV4
    22222222222222222222222222222222222222222222222222
    00000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    EXITINTF
    F0000000
    F0000000
    <FLT_CACHE_LINE>-OBJ
    E0001000
    E0001000
    SYST-REPID
    CL_EX_DOCUMENT_MAIN02=========CP
    4454554445444554444333333333334522222222
    3CF58F4F35D5E4FD19E02DDDDDDDDD3000000000
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    SY-REPID
    CL_EX_DOCUMENT_MAIN02=========CP
    4454554445444554444333333333334522222222
    3CF58F4F35D5E4FD19E02DDDDDDDDD3000000000
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    %_DUMMY$$
    2222
    0000
    0000
    0000
    SY-SUBRC
    0
    0000
    0000
    No. 2 Ty. FORM
    Name D100_CONSUME_EVENTS
    LF_ACT_IMP_EXISTING
    X
    5
    8
    0
    0
    %_SPACE
    2
    0
    0
    0
    SY-REPID
    SAPLCV110
    5454453332222222222222222222222222222222
    310C361100000000000000000000000000000000
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    SEEX_TRUE
    X
    5
    8
    0
    0
    LF_EXIT
    F0000000
    0000F000
    %_DUMMY$$
    2222
    0000
    0000
    0000
    GF_OI_CALLED_DISPLAY
    2
    0
    0
    0
    SYST-REPID
    SAPLCV110
    5454453332222222222222222222222222222222
    310C361100000000000000000000000000000000
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    SCREEN
    MCDOK-REFVR
    4444425445522222222222222222222222222222222222222222222222222222222222222222222222222222222222
    D34FBD2566200000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    GF_TRANSACTION
    CV03
    45332222222222222222
    36030000000000000000
    00000000000000000000
    00000000000000000000
    OK_CODE
    BACK
    4444222222222222222222222222222222222222222222222222222222222222222222
    213B000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000
    DRAW
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    CL_WB_REQUEST=>TO_IMMEDIATE_START
    PROP_STRING
    360
    6000
    8100
    BITMAP_STRETCH
    2
    0000
    2000
    SY-SUBRC
    0
    0000
    0000
    SS_CENTER
    1
    0000
    1000
    C_DMS_PHIO_MASTER_CLASS
    DMS_PCD1
    4455544322
    4D3F034100
    0000000000
    0000000000
    PROP_TABINDEX
    230
    E000
    6000
    SPACE
    2
    0
    0
    0
    LF_FCODE
    2222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000
    No. 1 Ty. MODULE (PAI)
    Name D100_FCODE
    TREEV_ITEM_CLASS_CHECKBOX
    3
    0000
    3000
    Internal notes
    The termination occurred in the function "RxMoveCastErrorObj" of the SAP
    Basis System, specifically in line 2995 of the module
    "//bas/640_REL/src/krn/runt/abmove1.c#7".
    The internal operation just processed is "CAST".
    The internal session was started at 20081202082340.
    Active Calls in SAP Kernel
    Lines of C Stack in Kernel (Structure Differs on Each Platform)
    (CTrcStack2+0x7a)0x63b29a
    (CTrcStack+0xb)0x63b8db
    (ab_rabax+0x2f02)0xa4b1e2
    (_Z18RxMoveCastErrorObj4RUDIS_PKt+0xa5)0x7b7a45
    (_Z8ab_jcastv+0x673)0x7bdec3
    (_Z8ab_extriv+0x219)0x7ab4d9
    (_Z9ab_xeventPKt+0x29a)0x8f9b4a
    (ab_dstep+0x1a7)0xa5ec77
    (dynpmcal+0x39a)0x69d84a
    (dynppai0+0x933)0x69f393
    (dynprctl+0x414)0x69e324
    (dynpen00+0x444)0x693034
    (Thdynpen00+0x2df)0x50a24f
    (TskhLoop+0x307)0x514347
    (tskhstart+0x1ae)0x522fae
    (DpMain+0x28f)0x49b1bf
    (nlsui_main+0x9)0x475159
    (main+0x2e)0x47518e
    /lib64/libc.so.6(__libc_start_main+0xa9)0x2a97124b49
    List of ABAP programs affected
    Index Ty. Program Group Date Time Size Lang.
    0 Prg SAPLCV110 0 2008.12.01 10:13:43 671744 E
    1 Prg SAPMSSYD 0 2008.12.01 02:17:53 21504 E
    2 Prg SAPFSYSCALLS 0 2003.11.06 20:52:59 7168 E
    3 Typ DRAW 0 2008.04.29 10:29:35 11264
    4 Typ DRAT 0 1999.03.10 18:52:49 3072
    5 Typ DMS_DB_DRAT 0 1999.03.10 18:36:01 3072
    6 Typ TDWS 0 2003.09.10 16:46:37 6144
    7 Typ TDWST 0 1997.05.12 16:50:34 2048
    8 Typ AENR 0 2008.11.20 14:51:32 7168
    9 Typ USR03 0 1997.05.12 16:51:23 6144
    10 Typ T024X 0 1998.02.14 10:32:35 2048
    11 Typ MCDOK 0 2004.12.08 17:17:49 28672
    12 Prg SAPLCV121 12 2008.12.01 10:09:17 152576 E
    13 Prg CL_GUI_CFW====================CP 13 2003.11.06 20:53:18 176128 E
    14 Prg CL_GUI_PROPS_CONSUMER=========CP 14 2003.11.06 20:52:43 30720 E
    15 Prg %_CCNTL 14 2003.11.06 20:52:41 16384 E
    16 Prg SAPLTHFB 16 2008.12.01 02:18:03 368640 E
    17 Prg SAPLOLEA 17 2008.12.01 02:00:50 93184 E
    18 Prg SAPLSGUI 18 2008.12.01 02:18:03 76800 E
    19 Prg SAPLSTTM 19 2006.09.21 08:17:23 86016 E
    20 Prg SAPLSBDC 20 2006.09.21 08:24:43 45056 E
    21 Prg SAPLSFES 21 2008.12.01 02:18:03 278528 E
    22 Prg SAPLSPLUGIN 22 2003.11.06 21:28:25 8192 E
    23 Prg SAPFGUICNTL 17 2003.11.06 20:57:18 24576 E
    24 Typ DMS_FRONTEND_DATA 0 2001.06.07 17:41:14 2048
    25 Typ ITDWA 0 1999.12.09 18:54:10 3072
    26 Typ DNTAB 0 2000.11.09 14:07:14 6144
    27 Typ DMS_AUDITS 0 1998.12.10 18:00:41 3072
    28 Typ DRAD 0 1999.12.01 15:17:34 4096
    29 Typ DRAZ 0 1998.04.01 02:05:08 4096
    30 Typ DRAP 0 1995.04.04 16:53:07 3072
    31 Typ DRAOZ 0 1995.04.04 16:53:05 6144
    32 Typ DRAO 0 1995.04.04 16:53:03 6144
    33 Typ TOAV0 0 1996.06.14 09:51:26 3072
    34 Typ DMS_REC_FILE 0 2006.10.12 17:53:17 8192
    35 Typ DMS_DOC_FILE 0 1999.04.21 13:22:51 12288
    36 Prg SAPLCADM 36 2003.11.06 20:53:00 14336 E
    37 Typ TDWA 0 2001.06.07 17:50:38 6144
    38 Prg SAPLCV115 38 2008.12.01 10:13:43 220160 E
    39 Prg SAPLCV118 39 2008.11.30 22:54:57 86016 E
    40 Prg SAPLCV130 40 2008.12.01 09:57:54 342016 E
    41 Prg SAPLCLO0 41 2006.09.21 11:31:12 55296 E
    42 Typ API_CHAR 0 1997.07.09 23:48:05 2048
    43 Typ API_VALI 0 1998.04.23 14:46:27 5120
    44 Typ API_KSSK 0 1996.01.29 18:00:54 3072
    45 Typ API_VALI 0 1998.04.23 14:46:27 5120
    46 Prg SAPLCLFM 46 2008.12.01 03:27:54 711680 E
    47 Typ RMCLF 0 2004.03.15 16:55:47 31744
    48 Typ RMCLKSSK 0 2001.09.18 10:03:47 5120
    49 Typ RMCLAUSP 0 2001.09.18 10:03:46 7168
    50 Typ RMCLDEL 0 1997.08.13 12:51:45 3072
    51 Typ AUSP 0 2001.09.18 10:02:23 6144
    52 Prg SAPLCLSE 52 2008.11.20 14:51:39 188416 E
    53 Prg SAPLCTMS 53 2008.12.01 03:28:16 985088 E
    54 Prg SAPLCTCV 54 2008.12.01 03:27:56 197632 E
    55 Prg SAPLCTCF 55 2008.12.01 03:27:07 20480 E
    56 Typ USR01 0 1998.02.14 15:22:01 4096
    57 Prg SAPLCLPR 57 2001.11.19 16:12:29 64512 E
    58 Typ CLPROF 0 2001.06.07 17:40:33 12288
    59 Typ RMCLPAR 0 2001.06.07 17:45:28 13312
    60 Typ AGR_USERS 0 2003.01.20 16:27:01 3072
    61 Prg SAPLCTCU 61 2008.05.18 09:34:46 189440 E
    62 Prg %_CCXTAB 53 2003.11.06 21:51:14 7168 E
    63 Typ SCXTAB_CONTROL 0 2003.11.06 20:31:00 6144
    64 Prg SAPLCUDB 64 2008.11.30 22:48:18 332800 E
    65 Prg SAPLCUD0 65 2008.12.01 09:57:54 196608 E
    66 Prg SAPLCUEV 66 2001.06.07 18:26:56 12288 E
    67 Prg SAPLSUNI 67 2008.05.18 09:44:54 151552 E
    68 Typ TFDIR 0 1998.07.29 19:49:08 3072
    69 Typ CABN 0 2001.09.18 10:02:26 12288
    70 Typ CABN 0 2001.09.18 10:02:26 12288
    71 Typ DDB_C05 0 1997.08.28 08:44:01 2048
    72 Typ DDB_C02 0 1997.07.09 23:52:49 3072
    73 Typ DDB_ITP 0 1997.08.28 08:44:01 2048
    74 Typ DDB_C07 0 1997.07.09 23:52:50 2048
    75 Prg SAPLCUTM 75 2006.09.21 11:40:39 68608 E
    76 Prg SAPLCUPM 76 2008.05.18 11:52:42 472064 E
    77 Prg SAPLSLG0 77 2003.11.06 20:53:05 64512 E
    78 Prg SAPLSBAL_SERVICE 78 2008.05.18 09:48:19 172032 E
    79 Typ BALOBJ 0 1997.08.13 13:16:25 2048
    80 Typ BALSUB 0 1997.08.13 13:16:26 2048
    81 Typ BAL_S_LFIL 0 2000.12.04 12:45:13 12288
    82 Prg SAPLSBAL 82 2008.05.18 09:48:19 327680 E
    83 Typ BAL_S_LOG 0 2000.12.04 13:04:00 7168
    84 Typ BAL_S_CONT 0 1998.11.02 09:43:07 2048
    85 Typ BAL_S_PARM 0 2000.12.04 12:45:14 3072
    86 Typ BAL_S_CLBK 0 1998.11.02 09:43:07 2048
    87 Typ BAL_S_SCNT 0 1998.11.30 15:52:33 3072
    88 Typ BAL_S_SDEF 0 2000.12.04 12:45:15 2048
    89 Prg CL_ABAP_CHAR_UTILITIES========CP 89 2004.11.12 14:02:13 14336 E
    90 Prg SAPLSYGU 90 2003.11.06 20:55:40 29696 E
    91 Prg SAPLCUXP 91 2008.12.01 10:09:15 147456 E
    92 Typ CUXP_01 0 1995.04.10 15:58:58 3072
    93 Typ T100 0 1997.08.28 09:04:45 2048
    94 Typ CUXP_02 0 1995.04.10 15:58:59 2048
    95 Typ CUXP_02 0 1995.04.10 15:58:59 2048
    96 Typ TMS_JUST 0 1995.04.10 16:02:55 2048
    97 Typ CUXP_02 0 1995.04.10 15:58:59 2048
    98 Prg SAPLCUTC 98 2003.11.11 20:31:28 89088 E
    99 Prg SAPLCUTRC 99 2008.12.01 02:26:11 87040 E
    100 Typ CTMS_01 0 1997.08.13 12:25:20 3072
    101 Typ INCL_BILD 0 1997.05.12 15:10:50 2048
    102 Typ AUSP 0 2001.09.18 10:02:23 6144
    103 Prg SAPLCCRL 103 2008.11.30 22:34:49 144384 E
    104 Typ AEOIB 0 2001.09.18 10:02:18 7168
    105 Typ TCC09 0 1999.03.17 16:24:37 2048
    106 Typ AEOI 0 2001.09.18 10:02:17 5120
    107 Prg SAPLCCCN 107 2008.11.20 14:51:39 293888 E
    108 Typ AEOIT 0 2001.09.18 10:02:18 3072
    109 Typ CCIN 0 2001.10.09 13:06:55 6144
    110 Typ CCCN_XFACE 0 2001.10.09 13:06:55 7168
    111 Prg SAPLCCBU 111 2008.11.20 14:51:39 33792 E
    112 Prg SAPLCV150 112 2008.11.20 14:51:40 144384 E
    113 Prg SAPFSPOR 0 2008.12.01 07:23:38 14336 E
    114 Prg SAPLSCNT 114 2003.11.06 20:53:04 30720 E
    115 Typ DYCBOX 0 1998.08.20 11:16:53 3072
    116 Prg SAPLSVSM 116 2006.09.21 08:56:23 29696 E
    117 Prg CL_DATAPROVIDER===============CP 117 2003.11.06 20:52:43 52224 E
    118 Typ OBJ_RECORD 0 1998.02.14 08:30:43 2048
    119 Prg SAPLSTUP 119 2006.09.21 08:34:57 75776 E
    120 Prg SAPLCNDP 120 2006.09.21 09:10:54 208896 E
    121 Prg SAPSHDTV 114 2003.11.06 20:57:23 33792 E
    122 Typ SHDTVCIU 0 1998.12.14 23:15:37 3072
    123 Typ SHDSTU 0 1998.12.14 23:15:34 2048
    124 Typ SHDSTCIU 0 1998.12.14 23:15:34 2048
    125 Typ ARFCRDATA 0 2000.11.09 14:04:16 6144
    126 Prg SAPLGRFC 126 2003.11.06 20:53:02 16384 E
    127 Typ SWCBCONT 0 2000.11.15 17:55:11 3072
    128 Typ OLE_VERBS 0 1995.04.04 16:02:20 2048
    129 Typ OLE_PA 0 1995.04.04 16:02:19 2048
    130 Prg CL_DYNAMIC_GUI_EXTENSIONS=====CP 130 2003.11.06 20:52:43 37888 E
    131 Prg CL_GUI_DATAMANAGER============CP 131 2006.09.21 09:11:48 77824 E
    132 Prg CL_EXITHANDLER================CP 132 2008.12.01 02:24:29 34816 E
    133 Prg SAPLSEXV 133 2008.12.01 02:05:16 124928 E
    134 Prg CL_BADI_FLT_DATA_TRANS_AND_DB=CP 134 2008.12.01 02:24:26 44032 E
    135 Typ SXS_ATTR 0 2001.08.20 12:23:27 4096
    136 Typ V_EXT_ACT 0 2000.11.09 14:27:05 2048
    137 Typ SXC_EXIT 0 2000.11.09 14:23:43 2048
    138 Prg CL_EX_DOCUMENT_MAIN02=========CP 138 2008.04.29 10:29:37 80896 E
    139 Prg IF_EX_DOCUMENT_MAIN02=========IP 132 2008.04.29 10:29:39 30720 E
    140 Prg %_CSXRT 138 2004.11.12 13:45:31 16384 E
    141 Prg CL_EXIT_MASTER================CP 141 2006.09.21 09:10:54 24576 E
    142 Typ SXS_MLCO 0 2000.12.04 14:59:55 2048
    143 Prg CL_EX_BADI_LAYER==============CP 143 2006.09.21 09:10:54 32768 E
    144 Prg IF_EX_BADI_LAYER==============IP 132 2006.09.21 08:51:19 9216 E
    145 Typ V_EXT_IMP 0 2003.11.06 20:40:20 3072
    146 Typ V_EXT_IMP 0 2003.11.06 20:40:20 3072
    147 Typ SXC_IMPSWH 0 2000.11.09 14:23:44 2048
    148 Prg ZCL_IM_DOCUMENT_MAIN02========CP 148 2008.12.01 14:50:50 7168 E
    149 Prg SAPLASTAT_TRIG 149 2003.11.06 20:53:00 13312 E
    150 Typ ASTAT_TYP2 0 1998.11.10 05:35:18 2048
    151 Typ ASTAT_TYP1 0 1998.11.30 15:54:16 2048
    152 Prg CX_SY_MOVE_CAST_ERROR=========CP 152 2003.11.06 20:41:23 11264 E
    153 Typ SCX_SRCPOS 0 2000.11.09 14:12:15 2048
    154 Prg CX_DYNAMIC_CHECK==============CP 154 2003.11.06 21:33:04 10240 E
    155 Prg CX_ROOT=======================CP 155 2003.11.06 21:56:05 12288 E
    156 Prg CX_NO_CHECK===================CP 156 2003.11.06 21:33:04 10240 E
    157 Prg CX_SY_NO_HANDLER==============CP 157 2003.11.06 21:33:04 10240 E
    158 Typ SYST 0 2000.12.04 14:54:51 31744
    159 Typ SFBM_XCPTN 0 2000.12.04 14:54:21 3072
    160 Prg CL_WB_REQUEST=================CP 160 2008.12.01 02:25:56 71680 E
    irectory of Application Tables
    ame Date Time Lngth
    Val.
    rogram SAPLCV110
    YST . . : : 00004608
    \0\0\0\0\x0001\0\x000E\0\0\0\0\0\0\0\0\0\0\0\0\0\x000E\0
    RAW 2008.04.29 10:29:35 00003196
    RAT . . : : 00000236
    MS_DB_DRAT . . : : 00000238
    DWS . . : : 00000268
    DWST . . : : 00000048
    ENR . . : : 00000496
    00 00000000 00000000
    SR03 . . : : 00000876
    T024X . . : : 00000074
    MCDOK 2004.12.08 17:17:49 00013650
    TDWA 2001.06.07 17:50:38 00000340
    0000
    Program CL_GUI_PROPS_CONSUMER=========CP
    EUDB . . : : 00004068
    %C002380004933B6098D9166C5E1000000AC1F7825 \0\0\0
    Program SAPLCLFM
    RMCLF . . : : 00003736
    Program SAPLCTMS
    RCTMS 2002.04.17 10:32:13 00002034
    Program SAPLCTCF
    USR01 . . : : 00000220
    Program SAPLCLPR
    RMCLPAR . . : : 00000418
    SAPPROFILE
    CLPROF . . : : 00000272
    600BMENGQC001 X X XXX
    AGR_USERS . . : : 00000164
    0000000000000
    Program SAPLSUNI
    TFDIR . . : : 00000188
    CUD0_CUSTOM_CONFIG_INITIALIZERSAPLCUD0
    Program SAPLCCRL
    AENR . . : : 00000496
    00 00000000 00000000
    AEOI . . : : 00000436
    00
    Program SAPLCCCN
    CCIN . . : : 00000600
    00 0
    Program SAPSHDTV
    SHDSTU . . : : 00000106
    SHDSTCIU . . : : 00000100
    ABAP Control Blocks (CONT)
    Index Name Fl PAR0 PAR1 PAR2 PAR3 PAR4 PAR5 PAR6 SourceCde Line
    409 DWRI 01 0042 CL_EX_DOCUMENT_MAIN02=========CM007 128
    410 WRIT 00 C026 CL_EX_DOCUMENT_MAIN02=========CM007 128
    411 PAR1 C0 0000 CL_EX_DOCUMENT_MAIN02=========CM007 128
    412 JEND A6 0000 CL_EX_DOCUMENT_MAIN02=========CM007 128
    413 DWRI 01 0043 CL_EX_DOCUMENT_MAIN02=========CM007 128
    414 WRIT 00 C027 CL_EX_DOCUMENT_MAIN02=========CM007 128
    415 PAR1 C0 0000 CL_EX_DOCUMENT_MAIN02=========CM007 128
    416 JEND A6 0000 CL_EX_DOCUMENT_MAIN02=========CM007 128
    417 FUNE 01 006E CL_EX_DOCUMENT_MAIN02=========CM007 128
    418 ENDF 00 0000 CL_EX_DOCUMENT_MAIN02=========CM007 128
    419 MESS 00 0000 CL_EX_DOCUMENT_MAIN02=========CM007 128
    420 BRAX 00 0015 CL_EX_DOCUMENT_MAIN02=========CM007 133
    CAST 00 0000 C006 C028 CL_EX_DOCUMENT_MAIN02=========CM007 134
    423 METH 03 0003 0000 8001 0000 0000 0000 0000 CL_EX_DOCUMENT_MAIN02=========CM007 135
    427 PAR1 01 C000 CL_EX_DOCUMENT_MAIN02=========CM007 135
    428 PAR1 81 C001 CL_EX_DOCUMENT_MAIN02=========CM007 135
    429 PAR1 81 C002 CL_EX_DOCUMENT_MAIN02=========CM007 135
    430 PAR2 00 0000 0002 0000 CL_EX_DOCUMENT_MAIN02=========CM007 135
    432 PAR2 00 0000 006E 0001 CL_EX_DOCUMENT_MAIN02=========CM007 135
    434 BREL 04 0000 CL_EX_DOCUMENT_MAIN02=========CM007 143

    Hi,
    As per your query, pls contact any abap consultant regarding this he will provide the solution. Because some times programe given some error then the abaper see the programe and take action accordingly.
    Anil

  • Error: There was a problem logging on to SAP BusinessObjects Enterprise

    I am trying to use Crystal Reports Enterprise XI 4.0 with BusinessObjects Enterprise 4.0 using a Bex Query on an SAP NetWeaver 7.01 SPS 9 BW system. I have been using the SAP Press book u201CIntegrating SAP BusinessObjects BI Platform 4.x with SAP NetWeaveru201D as my guide, attempting to follow it step by step. Please bear with me as I have only started working with this set of products within the last month. (Very new at this and do not have a very good grounding of the way it all works together. Trying to learn as quickly as possible as I am expected to support this set of tools for our developers / users.)
    I have been trying to follow along with the book to get everything connected. At this point, I have BOE set up to attach to the SAP NetWeaver BW system. I have created a test Bex Query on the BW system. From within BOE, using CMC, I can configure the Bex Query as an OLAP connection. I have set it up for SSO. I have also exchanged certificates between the BOE and the SAP NetWeaver systems which I believe will allow the exchange of tokens.
    I then go into Crystal Reports for Enterprise XI 4.0 on my PC. (I am running Windows 7 64-bit on the PC. I installed the BOE 4.0 suite of client tools except for SAP BO Live Office and SAP BO Analysis for MS Office). I can attach to my BOE system and can browse to see the OLAP connections in the BOE. I then try to select one as the data source for a new report. I then get a pop-up window stating:
       Unable to Logon
         There was a problem logging on to SAP BusinessObjects Enterprise.
           Please check your logon credentials and make sure your network is properly configured before trying again. If the problem 
           persists please contact your Administrator.
    I cannot find a log / trace / error file on my PC, the BOE system or the BW system to indicate any additional information as to what the root problem is. Has anyone seen a similar error and might know where I can find more information, how to increase trace levels so that I get some additional information or provide hints as to what the root problem might be?
    I am also trying to figure out how the authentication works between the PC, BOE and SAP NetWeaver. If using a token, there has to be consistency with the username (or some value) and I am not certain that is happening. Right now, my BOE sources its UME from the SAP NetWeaver BW system. So its user accounts are in the form SID123/ACCOUNT where SID is the SID of the SAP NetWeaver system and the string u201C123u201D is the client on that SID. When I log into the BOE system from within Crystal Reports, I am using the account in that format whereas the account on the SAP NetWeaver BW system in actuality is only the string ACCOUNT. So is the token stripping the string u201CSID123/u201D from the account name when it is sent so that the accounts match? Or do I have to manually configure some kind of account alias (in the BOE system?) so that the two recognize each other? Or something else?
    Any hints or ideas around where I can find additional information or where I have gone wrong, would be greatly appreciated.
    Thank-you in advance,
    Deb Nugent.

    Henry,
    Many thanks and excellent suggestions. But I am still not able to get this to work and (once again) am stuck.
    RE: Server Connections: When I check my server connection, I have not ticked SSL and am using the non-secure server port for my BOE system. When I click on u201CTest connectionu201D, I can successfully log in using my username / password on the SAP NetWeaver BW system. If I tick the SSL box without changing the port, I get the error message u201CFailed to establish a connection. The cause was u201CCannot connect to SAP BusinessObjects Enterprise at this time. Please try again later.u201D If I tick the SSL box and change the port to use the secure server port for the BOE system, I get the same error.
    RE: Preferences: I am using the default settings under Preferences -> Network Settings. We do not manually configure proxy settings on our network so I have ticked u201CUse system proxy configurationu201D and under SSL settings, have ticked u201CUse system keystore / trust storeu201D. I have swapped keys between the BOE system and the SAP NetWeaver system but I have not swapped any keys between my PC and the BOE system or the SAP NetWeaver system (which I do not expect to do but am mentioning here in case I am wrong).
    RE: BILaunchPad: I do not have any references for BILaunchPad. Is this u201CWeb Intelligence Rich Clientu201D? If so, I tried starting it, it reported an error: u201CAn error occurred at session creation.u201D Details showed u201CSSL mode is being requested but the following argument(s) are not present: passphrase (FWM 01012)u201D I went into the CMC and checked my SAP connections under Authentications. On the tab u201COptionsu201D, there is the section u201CSAP SSO Serviceu201D where I typed in the KeyStore password. When I created the key store file, I only specified a keystore password and did not specify a private key. Originally, I had it set with the private key blank with the correct password on the keystore. I also tried entering the same password as the private keystore and saving it. I verified that the connection services for Web Intelligence had restarted but I still am getting that same message when I try to start the Web Intelligence Rich Client.
    At OS level on the BOE server, I logged in as my boe1 account and checked the parameters that can be entered for the PKCS12Tool.jar file that I used to create the ketstore file I had used. There does not appear to be an option for anything other than the keystore password. There is no private key password field listed.
    I searched for the FWM 01012 error and found the HTML and PDF help files form SAP explaining errors. However, it only states u201CEnsure that all SSL arguments are presentu201D but gives no details as to what, exactly needs to be checked.
    I will be talking with co-workers today to see if any of them can make sense of this (anoterh set of eyes sometimes helps). Any other suggestions about areas to look for addiitonal details / increased traces / logs?
    Deb Nugent.

  • Problem with the hierarchial fields in a Purchase order xml report

    Hi,
    I am having a problem with the hierarchy problem. We are populating attribute 15 of a PO header. some times it can be null. FYI, we are using 11.5.10 instance where oracle supports direct PO template rather than having a rdf file.
    And now in the xml report, if attribute15 of po header is not null then it is fine.
    But if attribute15 is null, then the template is picking from the next available attribute15 that is from the po lines. As the line level group of "LINES" is between the "PO_DATA" (header group), hence the template is checking for next available attribute15.
    Can any one please suggest how to design the template where we can make the template to check only for that tag at the header level group rather than the line level group tag?
    Thank You in advance.
    Regards,
    Srinivas.

    Hi
    Incase you want to transfer attachements from SRM to R/3, then you try implementing the BADI in SRM side. The BADI which will help in this case is
    <b>BBP_CREATE_PO_BACK</b> BADI.
    <b>Please read the standard SAP documentation of this BADI using SE18 Transaction, before making any code changes.</b>
    <u>Few Important SAP OSS notes to refer in this case -></u>
    Note 989184 - Transferred shopping cart with internal attachments
    Note 550071 - FAQ: EBP - Shopping Cart
    Note 916347 - Transfer shopping cart with internal attachments
    Note 1001130 - FAQ - Attachment questions (Buyside)
    <u>Few useful links -></u>
    <b>http://help.sap.com/saphelp_srm50/helpdata/en/49/b32640632cea01e10000000a155106/frameset.htm
    Re: Attachments to backend
    Re: Document Attachments in Shopping Cart
    Re: Attachment in SRM
    Re: SRM Documents and Attachments
    Re: Limit in Attachments of an item in Shopping Cart
    Re: return delivery text from material document is not passed to SUS
    </b>
    Do let me know, incase you face any problems.
    Regards
    - Atul

  • Can we Set the Default SAP Component while Creating Support Message

    Hi Friends,
        I Have got requirement like, when we create the support desk message from any application system by default the sap component should get selected which we have determined in Solman.Our Business secnario is too complex user give create the support message without giving the Sap Component or they give wrong sap Component, so we want to set the sap component get selected by default while creating the support desk message, guide me in solving this issue.
      Regards
        Charan

    I think your logic is reversed.  I think it's better to let users create messages from the application areas from which they are having the problem.  Based on the standard SAP component which defaults into the component field, the ticket can be routed to one of your 20 teams.  This is where the agent detemination rule for support team can be configured.  There are a number of message on the forum regarding support team configuration.  This way, if your 20 teams can't solve the problem (for example SAP defect) then the message can be forwarded directly to SAP using the correct component.  Good luck.

  • Validate xslt against JDK5 so we can remove the 'Use SAP XML Toolkit' flag

    We are working on PI7.1 and have hit an issue with an XSLT mapping. We were getting an error when testing that said:
    TransformerException during XSLT processing:
    javax.xml.transform.TransformerException: com.sun.org.apache.xalan.internal.xsltc.TransletException: com.sun.org.apache.xalan.internal.xsltc.TransletException: java.io.FileNotFoundException
    We found a few threads on SDN pointing us to using the 'Use SAP XML Toolkit' flag, which we'd not even noticed before. Ticking this flag did get us around the problem. Further investigation suggested to us, however, that this flag will not be available in future releases, so I guess our best solution would be to try and resolve the issues in our mapping against the current version of java (JDK5). When we use other tools such as XMLSPY they do not detect a problem with the XSLT. Can anyone point me to a tool that would enable us to validate our XSLT file against JDK5, which will provide us with error messages that will enable us to fix the error and therefore remove the 'Use SAP XML Toolkit' flag?
    thanks,
    Malcolm.

    > Can anyone point me to a tool that would enable us to validate our XSLT file against JDK5, which will provide us with error messages that will enable us to fix the error and therefore remove the 'Use SAP XML Toolkit' flag?
    I am sorry to have to say that even inside SAP nobody can answer this question.
    In principle it will work when it is pure XSLT 1.1 but some commands from XSLT 2.0 might work also.

  • "Performance" problems with the File adapter on Plain J2SE Adapter Engine

    Hi,
    At the moment I'm on a customer side to solve some XI issues for a few days. One of the issues is the performance of the Plain J2SE Adapter Engine, using the file adapter to transfer XML messages(already XI message format) from the legacy system to the Integration Engine. The File adapter has to deal with "large" XML messages(max at the moment is 65 Mb) and the engine fails with the following error when transferring the big XML file: "ERROR: Finished sending to Integration Engine with error "java.lang.OutOfMemoryError". Skip confirmation and quit this loop".
    As far I got the information from the customer the memory use of the Plain adapter engine is set to 512Mb. This is maybe to low. But I don't know where to look for this, I only have the adapter web interface in front of me, no access to the OS it self via for example remote connection.
    On the Integration Engine I know there is the ability to split large message with the file adapter(File Content Conversion), but I don't know this for the Plain Adapter Engine. Is there a possibility to do this also on the Plain Adapter Engine?
    Thanks in advance for any input.
    Greetings,
    Patrick

    Hi Sameer,
    Thanks for your answers.
    On the first solution, yes that is possible, we first decided to see if the legacy system can do the splitting, before starting developing a Java program.
    On the second solution, as far as I know is this solution possible on the Integration Engine. But we are facing the problems on the Plain J2SE Adapter Engine. I went trough that documentation(link:
    http://help.sap.com/saphelp_nw04/helpdata/en/6f/246b3de666930fe10000000a114084/frameset.htm ), to look for I similiar solution in the Plain Adapter Engine. So my question is, is this possible with the Plain Adapter? And if so, what kind of parameters I need to use to achieve this.
    Regards,
    Patrick

  • Problem while printing from SAP GUI for HTML

    Hello,
    We are trying to print a delivery confirmation from the portal using SAP GUI for HTML. We have followed note 771683 to do this. However we are facing the following problems:
    1) The print action(PDF creation) is not triggered until the user performs some action
    2) the PDF that is created is corrupted(does not open)
    In order to correct this we tried to implement note 957292. However, the changes to the object FRONTEND_PRINTPOLL_FRONT_REQUEST.HTM mentioned in this note created problems. So we decided to do the changes to this object manually. But we see that the SAP note doesn't contain any information on changes that should be implemented for this object.
    Question:
    Is the note 957292 only way to solve the printing(PDF) problem? If not, how can we trigger the automatic creation of the PDF and remove the error from the PDF file?
    If yes, any idea what is causing the problem during the note implementation?
    We are on NW2004s - EP7.0 SP10
    ITS 7.0
    Thanks in advance.
    Regards,
    Reena

    Hi,
    configure printer in SPAD  , no setting for JAVA GUI
    check note
    605467:SAPscript/Smart Forms: Print preview in SAP GUI for Java
    634158      SAPscript/Smart Forms: Print preview in SAP GUI for Java (2)
    1024624 SAPscript/Smart Forms: Print preview in SAP GUI for Java (3)       
    regards,
    kaushal
    regards,
    kaushal

  • Getting run time errors while executing the copied SAP programs

    Hi folks,
    i want to copy an sap program.after coping i need to change some coding there.then i have to create a new transaction for that.
    i am just copying the sap program RQEEAL10(transaction-QA32) to Z_RQEEAL10. it has 4 include  programs.i am copying them to z programs like
    RQ00MF10 copied to z_RQ00MF10
    RQALVF14 copied to z_RQALVF14
    RQALVF16 copied to z_RQALVF16
    RQALVTOP copied to z_RQALVTOP.
    now i am executing that program Z_RQEEAL10.but i am getting run time errors as given below.
    <b>runtime error---</b>
    The termination occurred in the ABAP program "Z_RQEEAL10" in           
    "SELECT_FIELDS_MANIP2_F16".                                           
    The main program was "Z_RQEEAL10 ".                                                                               
    The termination occurred in line 257 of the source code of the (Include)
    program "RQALVF16"                                                    
    of the source code of program "RQALVF16" (when calling the editor 2570).
    --Error in ABAP statement when processing an internal table.  
    --When changing or deleting one or more lines of the internal table         
    "\PROGRAM=Z_RQEEAL10\DATA=SELECT_FIELDS" or when inserting in the table   
    "\PROGRAM=Z_RQEEAL10\DATA=SELECT_FIELDS", 0 was used as                  
    the line index. An index less than or equal to zero is not                
    allowed.                                                                               
    The error can occur when using the following options:                     
    1. "INDEX idx" for specifying the line number in the table                
    "\PROGRAM=Z_RQEEAL10\DATA=SELECT_FIELDS"                                 
       where you want to change, insert or delete.                            
    2. "FROM idx" for specifying the start index when deleting a line         
       area from or inserting a line area into the table                      
    "\PROGRAM=Z_RQEEAL10\DATA=SELECT_FIELDS".                                
    3. "TO idx" for specifying the end index when deleting a line             
       area from or inserting a line area into the table                      
    "\PROGRAM=Z_RQEEAL10\DATA=SELECT_FIELDS".                                                                               
    When the program terminated, the table had 2 lines.                       
    these r the runtime errors what i am getting.where is the problem?i have activated all interface & includes.plz advice.
    Thanks & regards

    Hi Madhu,
    I will give you one more check point where you have to give your concentration while copying the standard programs....
    Call Customer-Function (Function Exists) if any in the Program when copied will not get executed. Instead you need to call the FM Directly.
    one more is also here
    You are likely to have some problems with the text-elements and translation that may have been maintained for the original report.
    ~~Guduri

Maybe you are looking for