SM58 - Error while sending IDOC

Hi,
I got the following error while sending the IDoc to a XI system.
"No service for system (Idoc adapter port), client 800 in Integration Directory"
Please let me know whether this is due to an error in network or application error.
Note: remote logon is not successful in the XI system
Thanks in advance
Edited by: RPN on Jul 1, 2008 11:46 AM

Hi RPN,
Plz do check the following things :
1. Verify the logical business system in SLD.
To verify --- Go to SLD home page ---> Technical Landscape --> Select Web AS ABAP --> Select the technical system --> Clients ---> Click on the client you used as Business system --> Here look for the logical system is defined or not.
2. Open ID---> Click on Objects --> Service Without party/Party > Double click on business system>On the tright side--> Service --> Adapter specific Identifiers ---> Check IDoc Adpater, Logical System.
3. Refresh the full CPA Cache (userid must be XIDIRUSER/PIDIRUSER)
http://<hostname>:50000/CPACache/refresh?mode=full
Regards,
Vinod.

Similar Messages

Company code does not exist error while sending idoc

Hi Expert
I am trying to send idoc from one client(800) to another client(810).I have faced error Company code does not exist, searched scn ,Got solution if company code does not exist in reciever system(810 client) ,it will show this error .Then i have tried to give specific company code which is exist in 810 client also .But same issue is coming . So what exactly the issue can any one say .
More Info:FI(Finance) header items and line items are sending .
Thanks & Regards

Hi,
Your company code not activated for material management. Few pre-requisites to create material and one is to activate company code for material management
Please activate in T.code: OMSY,
[For example: For Fiscal year variant K4]
In OMSY steps, u have to enteru2026u2026u2026..
Company Code (enter your company code name 2001)u2026u2026u2026u2026u2026.
Company Name..
Fiscal Year of Current Period 2009
Current period (posting period) 03( )
Fiscal year of previous period 2008( will come automatic)
Month of previous period 02( will come automatic)
Fiscal year of last period of previous year 2008
Last month of previous year 12
Allow Posting to Previous Period (Back posting)
Disallow back posting after a change of period
Now create material with T.code; MM01
Regards,
Biju K

Error: EDI: Error while assigning IDoc number

Hi Everybody,
using XI 3.0 on Linux 64 bit SLES9 with Oracle I got some probleme sending messages from mq series to sap:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30"
xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"
SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_METADATA</SAP:Code>
<SAP:P1>EDI: Error while assigning IDoc number</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error: EDI: Error while assigning IDoc number</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
What is missing here?
Kind regards,
Michael

Hi Jayakrishnan,
thanks a lot for your answer.
SM59 is working finde. In IDX1 I got the the correct RFC destination entered and a double click works fine also.
The other way around R3 -> XI -> mq series is working fine. Here we are trying mq -> XI -> R3 and it stops sending from XI to R/3.
How to check the IDOC type?
Regards,
Michael

Error while sending email to external mail - Urgent

Hi All,
I am getting error while sending email with attachement. The Error code is 02.
I am not able to identify the error. bold Please help me in solving this problem.
Is it anything wrong with the code or Any Configuration with SCOT/SOST.bold
the code i am using is :
REPORT YVR_F MESSAGE-ID XX .
TABLES : EDIDC, EDIDS, EDPAR.
SELECTION-SCREEN BEGIN OF BLOCK B1 WITH FRAME.
PARAMETERS : P_STATUS LIKE EDIDC-STATUS DEFAULT '51'.
SELECT-OPTIONS : S_DIRECT FOR EDIDC-DIRECT,
                 S_MESTYP FOR EDIDC-MESTYP,
                 S_CREDAT FOR EDIDC-CREDAT.
SELECTION-SCREEN END OF BLOCK B1 .
PARAMETER: P_EMAIL LIKE SOMLRECI1-RECEIVER,
           P_SENDER LIKE SOMLRECI1-RECEIVER no-display,
           P_DELSPL AS CHECKBOX,
           P_ONLINE NO-DISPLAY.
DATA : TB_EDIDC LIKE STANDARD TABLE OF EDIDC INITIAL SIZE 0 WITH HEADER
LINE.
DATA : TB_EDPAR LIKE STANDARD TABLE OF EDPAR INITIAL SIZE 0 WITH HEADER
LINE.
DATA : TB_KNA1 LIKE STANDARD TABLE OF KNA1 INITIAL SIZE 0 WITH HEADER
LINE.
DATA : TB_ADRC LIKE STANDARD TABLE OF ADRC INITIAL SIZE 0 WITH HEADER
LINE.
DATA: INT_PDF TYPE TABLE OF TLINE WITH HEADER LINE.
DATA : BEGIN OF TB_ED OCCURS 0,
         SNDPRN LIKE EDIDC-SNDPRN,
         LOC    LIKE ADRC-BUILDING,
         DOCNUM LIKE EDIDC-DOCNUM,
         IDOCTP LIKE EDIDC-IDOCTP,
         MESTYP LIKE EDIDC-MESTYP,
         DIRECT LIKE EDIDC-DIRECT,
         CREDAT LIKE EDIDC-CREDAT,
         STATUS LIKE EDIDC-STATUS,
       END OF TB_ED.
DATA:   IT_MESSAGE TYPE STANDARD TABLE OF SOLISTI1 INITIAL SIZE 0
                WITH HEADER LINE.
DATA:   IT_ATTACH TYPE STANDARD TABLE OF SOLISTI1 INITIAL SIZE 0
                WITH HEADER LINE.
Job Runtime Parameters
DATA: GD_EVENTID LIKE TBTCM-EVENTID,
      GD_EVENTPARM LIKE TBTCM-EVENTPARM,
      GD_EXTERNAL_PROGRAM_ACTIVE LIKE TBTCM-XPGACTIVE,
      GD_JOBCOUNT LIKE TBTCM-JOBCOUNT,
      GD_JOBNAME LIKE TBTCM-JOBNAME,
      GD_STEPCOUNT LIKE TBTCM-STEPCOUNT,
      GD_ERROR    TYPE SY-SUBRC,
      GD_RECIEVER TYPE SY-SUBRC.
DATA: W_RECSIZE TYPE I,
       W_SPOOL_NR LIKE SY-SPONO.
      %_print LIKE pri_params.
DATA: GD_SUBJECT   LIKE SODOCCHGI1-OBJ_DESCR,
      IT_MESS_BOD LIKE SOLISTI1 OCCURS 0 WITH HEADER LINE,
      IT_MESS_ATT LIKE SOLISTI1 OCCURS 0 WITH HEADER LINE,
      GD_SENDER_TYPE     LIKE SOEXTRECI1-ADR_TYP,
      GD_ATTACHMENT_DESC TYPE SO_OBJ_NAM,
      GD_ATTACHMENT_NAME TYPE SO_OBJ_DES.
Spool to PDF conversions
DATA: GD_SPOOL_NR LIKE TSP01-RQIDENT,
      GD_DESTINATION LIKE RLGRAP-FILENAME,
      GD_BYTECOUNT LIKE TST01-DSIZE,
      GD_BUFFER TYPE STRING.
Binary store for PDF
DATA: BEGIN OF IT_PDF_OUTPUT OCCURS 0.
        INCLUDE STRUCTURE TLINE.
DATA: END OF IT_PDF_OUTPUT.
DATA: GD_RECSIZE TYPE I.
CONSTANTS: C_DEV LIKE SY-SYSID VALUE 'DEV',
           C_NO(1)     TYPE C   VALUE ' ',
           C_DEVICE(4) TYPE C   VALUE 'LOCL'.
DATA:   T_PACKING_LIST LIKE SOPCKLSTI1 OCCURS 0 WITH HEADER LINE,
        T_CONTENTS LIKE SOLISTI1 OCCURS 0 WITH HEADER LINE,
        T_RECEIVERS LIKE SOMLRECI1 OCCURS 0 WITH HEADER LINE,
        T_ATTACHMENT LIKE SOLISTI1 OCCURS 0 WITH HEADER LINE,
        T_OBJECT_HEADER LIKE SOLISTI1 OCCURS 0 WITH HEADER LINE,
        W_CNT TYPE I,
        W_SENT_ALL(1) TYPE C,
        W_DOC_DATA LIKE SODOCCHGI1.
DATA : MSTR_PRINT_PARMS LIKE PRI_PARAMS,
       MC_VALID,
       P_REPID LIKE SY-REPID,
       WF_ID LIKE TSP01-RQIDENT,
       LOC_BYTECOUNT TYPE I.
*start-of-selection.
MSTR_PRINT_PARMS-PDEST = 'LOCL'.
P_REPID = SY-REPID.
CALL FUNCTION 'GET_PRINT_PARAMETERS'
EXPORTING
    authority= ' '
   COPIES                       = '1'
   COVER_PAGE                   = SPACE
   DATA_SET                     = SPACE
   DEPARTMENT                   = SPACE
   DESTINATION                  = 'LP01'
   EXPIRATION                   = '1'
   IMMEDIATELY                  = 'X'
   LAYOUT                       = 'X_65_132'
   MODE                         = SPACE
   NEW_LIST_ID                  = 'X'
   NO_DIALOG                    = 'X'
   USER                         = SY-UNAME
IMPORTING
   OUT_PARAMETERS               = MSTR_PRINT_PARMS
   VALID                        = MC_VALID
EXCEPTIONS
   ARCHIVE_INFO_NOT_FOUND       = 1
   INVALID_PRINT_PARAMS         = 2
   INVALID_ARCHIVE_PARAMS       = 3
   OTHERS                       = 4.
     SUBMIT (P_REPID) TO SAP-SPOOL WITHOUT SPOOL DYNPRO
                      SPOOL PARAMETERS MSTR_PRINT_PARMS.
                      AND RETURN.
NEW-PAGE PRINT ON NO DIALOG PARAMETERS
MSTR_PRINT_PARMS.
perform data.
NEW-PAGE PRINT OFF. "This marks the end of the screen for which the
*SPOOL NO WAS GENERATED.
WF_ID = SY-SPONO.
*converting spool to pdf
CALL FUNCTION 'CONVERT_ABAPSPOOLJOB_2_PDF'
     EXPORTING
          SRC_SPOOLID              = WF_ID "SPOOL NUMBER
          NO_DIALOG                = SPACE
          PDF_DESTINATION          = 'X'
     IMPORTING
          PDF_BYTECOUNT =
             LOC_BYTECOUNT "NUMBER OF BYTES TRANSFERRED
     TABLES
          PDF                      = INT_PDF "TABLE FOR PDF REPORT
     EXCEPTIONS
          ERR_NO_ABAP_SPOOLJOB     = 1
          ERR_NO_SPOOLJOB          = 2
          ERR_NO_PERMISSION        = 3
          ERR_CONV_NOT_POSSIBLE    = 4
          ERR_BAD_DESTDEVICE       = 5
          USER_CANCELLED           = 6
          ERR_SPOOLERROR           = 7
          ERR_TEMSEERROR           = 8
          ERR_BTCJOB_OPEN_FAILED   = 9
          ERR_BTCJOB_SUBMIT_FAILED = 10
          ERR_BTCJOB_CLOSE_FAILED = 11
          OTHERS                   = 12.
*CALL FUNCTION 'DOWNLOAD'
*EXPORTING
*bin_filesize = loc_bytecount "NO. OF BYTES
*filename = 'C:/EMAILPDF.PDF'
*filetype = 'BIN'
**IMPORTING
**act_filename = loc_filename
*TABLES
*data_tab = int_pdf.
IF P_DELSPL EQ 'X'.
PERFORM DELETE_SPOOL.
ENDIF.
Transfer the 132-long strings to 255-long strings
LOOP AT INT_PDF.
TRANSLATE INT_PDF USING ' ~'.
CONCATENATE GD_BUFFER INT_PDF INTO GD_BUFFER.
ENDLOOP.
TRANSLATE GD_BUFFER USING '~ '.
DO.
IT_MESS_ATT = GD_BUFFER.
APPEND IT_MESS_ATT.
SHIFT GD_BUFFER LEFT BY 255 PLACES.
IF GD_BUFFER IS INITIAL.
    EXIT.
ENDIF.
ENDDO.
DESCRIBE TABLE IT_MESS_ATT LINES GD_RECSIZE.
CHECK GD_RECSIZE > 0.
PERFORM SENDMAIL USING P_EMAIL..
*&      Form sendmail
      text
--> p1        text
<-- p2        text
FORM SENDMAIL USING P_EMAIL.
CHECK NOT ( P_EMAIL IS INITIAL ).
REFRESH IT_MESS_BOD.
Default subject matter
GD_SUBJECT         = 'Subject'.
GD_ATTACHMENT_DESC = 'IDOC LIST'.
CONCATENATE 'attach_name' ' ' INTO gd_attachment_name.
IT_MESS_BOD        = 'List Of Failed Idocs'.
APPEND IT_MESS_BOD.
IT_MESS_BOD        = 'List Of Failed Idocs'.
APPEND IT_MESS_BOD.
If no sender specified - default blank
IF P_SENDER EQ SPACE.
    GD_SENDER_TYPE = SPACE.
ELSE.
    GD_SENDER_TYPE = 'INT'.
ENDIF.
Send file by email as .xls speadsheet
PERFORM SEND_FILE_AS_EMAIL_ATTACHMENT
                               TABLES IT_MESS_BOD
                                      IT_MESS_ATT
                                USING P_EMAIL
                                      'Document attachment'
                                      'PDF'
                                      GD_ATTACHMENT_NAME
                                      GD_ATTACHMENT_DESC
                                      P_SENDER
                                      GD_SENDER_TYPE
                             CHANGING GD_ERROR
                                      GD_RECIEVER.
ENDFORM.                    " sendmail
*&      Form DELETE_SPOOL
      text
--> p1        text
<-- p2        text
FORM DELETE_SPOOL.
DATA: LD_SPOOL_NR TYPE TSP01_SP0R-RQID_CHAR.
LD_SPOOL_NR = WF_ID.   "GD_SPOOL_NR.
CHECK P_DELSPL <> C_NO.
CALL FUNCTION 'RSPO_R_RDELETE_SPOOLREQ'
       EXPORTING
            SPOOLID = LD_SPOOL_NR.
ENDFORM.                    " DELETE_SPOOL
*&      Form SEND_FILE_AS_EMAIL_ATTACHMENT
      text
     -->P_IT_MESS_BOD text
     -->P_IT_MESS_ATT text
     -->P_P_EMAIL text
     -->P_0846   text
     -->P_0847   text
     -->P_GD_ATTACHMENT_NAME text
     -->P_GD_ATTACHMENT_DESC text
     -->P_P_SENDER text
     -->P_GD_SENDER_TYPE text
     <--P_GD_ERROR text
     <--P_GD_RECIEVER text
FORM SEND_FILE_AS_EMAIL_ATTACHMENT TABLES   IT_MESSAGE
                                          IT_ATTACH
                                    USING P_EMAIL
                                          P_MTITLE
                                          P_FORMAT
                                          P_FILENAME
                                          P_ATTDESCRIPTION
                                          P_SENDER_ADDRESS
                                          P_SENDER_ADDRES_TYPE
                                 CHANGING P_ERROR
                                          P_RECIEVER.
DATA: LD_ERROR    TYPE SY-SUBRC,
         LD_RECIEVER TYPE SY-SUBRC,
         LD_MTITLE LIKE SODOCCHGI1-OBJ_DESCR,
         LD_EMAIL LIKE SOMLRECI1-RECEIVER,
         LD_FORMAT TYPE SO_OBJ_TP ,
         LD_ATTDESCRIPTION TYPE SO_OBJ_NAM ,
         LD_ATTFILENAME TYPE SO_OBJ_DES ,
         LD_SENDER_ADDRESS LIKE SOEXTRECI1-RECEIVER,
         LD_SENDER_ADDRESS_TYPE LIKE SOEXTRECI1-ADR_TYP,
         LD_RECEIVER LIKE SY-SUBRC.
DATA:   T_PACKING_LIST LIKE SOPCKLSTI1 OCCURS 0 WITH HEADER LINE,
          T_CONTENTS LIKE SOLISTI1 OCCURS 0 WITH HEADER LINE,
          T_RECEIVERS LIKE SOMLRECI1 OCCURS 0 WITH HEADER LINE,
          T_ATTACHMENT LIKE SOLISTI1 OCCURS 0 WITH HEADER LINE,
          T_OBJECT_HEADER LIKE SOLISTI1 OCCURS 0 WITH HEADER LINE,
          W_CNT TYPE I,
          W_SENT_ALL(1) TYPE C,
          W_DOC_DATA LIKE SODOCCHGI1.
LD_EMAIL   = P_EMAIL.
LD_MTITLE = P_MTITLE.
LD_FORMAT              = P_FORMAT.
LD_ATTDESCRIPTION      = P_ATTDESCRIPTION.
LD_ATTFILENAME         = P_FILENAME.
LD_SENDER_ADDRESS      = P_SENDER.
LD_SENDER_ADDRESS_TYPE = P_SENDER_ADDRES_TYPE.
Fill the document data.
W_DOC_DATA-DOC_SIZE = 1.
Populate the subject/generic message attributes
W_DOC_DATA-OBJ_LANGU = SY-LANGU.
W_DOC_DATA-OBJ_NAME = 'SAPRPT'.
W_DOC_DATA-OBJ_DESCR = LD_MTITLE .
W_DOC_DATA-SENSITIVTY = 'F'.
Fill the document data and get size of attachment
CLEAR W_DOC_DATA.
READ TABLE IT_ATTACH INDEX W_CNT.
W_DOC_DATA-DOC_SIZE =
     ( W_CNT - 1 ) * 255 + STRLEN( IT_ATTACH ).
W_DOC_DATA-OBJ_LANGU = SY-LANGU.
W_DOC_DATA-OBJ_NAME   = 'SAPRPT'.
W_DOC_DATA-OBJ_DESCR = LD_MTITLE.
W_DOC_DATA-SENSITIVTY = 'F'.
CLEAR T_ATTACHMENT.
REFRESH T_ATTACHMENT.
T_ATTACHMENT[] = IT_ATTACH[].
Describe the body of the message
CLEAR T_PACKING_LIST.
REFRESH T_PACKING_LIST.
T_PACKING_LIST-TRANSF_BIN = SPACE.
T_PACKING_LIST-HEAD_START = 1.
T_PACKING_LIST-HEAD_NUM = 0.
T_PACKING_LIST-BODY_START = 1.
DESCRIBE TABLE IT_MESSAGE LINES T_PACKING_LIST-BODY_NUM.
T_PACKING_LIST-DOC_TYPE = 'RAW'.
APPEND T_PACKING_LIST.
Create attachment notification
T_PACKING_LIST-TRANSF_BIN = 'X'.
T_PACKING_LIST-HEAD_START = 1.
T_PACKING_LIST-HEAD_NUM   = 1.
T_PACKING_LIST-BODY_START = 1.
DESCRIBE TABLE T_ATTACHMENT LINES T_PACKING_LIST-BODY_NUM.
T_PACKING_LIST-DOC_TYPE   = LD_FORMAT.
T_PACKING_LIST-OBJ_DESCR = LD_ATTDESCRIPTION.
T_PACKING_LIST-OBJ_NAME   = LD_ATTFILENAME.
T_PACKING_LIST-DOC_SIZE   = T_PACKING_LIST-BODY_NUM * 255.
APPEND T_PACKING_LIST.
Add the recipients email address
CLEAR T_RECEIVERS.
REFRESH T_RECEIVERS.
T_RECEIVERS-RECEIVER = p_EMAIL.
T_RECEIVERS-REC_TYPE = 'U'.
T_RECEIVERS-COM_TYPE = 'INT'.
T_RECEIVERS-NOTIF_DEL = 'X'.
T_RECEIVERS-NOTIF_NDEL = 'X'.
APPEND T_RECEIVERS.
DATA: objhead LIKE solisti1 OCCURS 1 WITH HEADER LINE.
W_SENT_ALL = 'X'.
CALL FUNCTION 'SO_NEW_DOCUMENT_ATT_SEND_API1'
       EXPORTING
            DOCUMENT_DATA              = W_DOC_DATA
            PUT_IN_OUTBOX              = 'X'
           SENDER_ADDRESS             = LD_SENDER_ADDRESS
           SENDER_ADDRESS_TYPE        = LD_SENDER_ADDRESS_TYPE
            COMMIT_WORK                = 'X'
       IMPORTING
            SENT_TO_ALL                = W_SENT_ALL
       TABLES
            PACKING_LIST               = T_PACKING_LIST
            object_header              = objhead
            CONTENTS_BIN               = T_ATTACHMENT
            CONTENTS_TXT               = IT_MESSAGE
            RECEIVERS                  = T_RECEIVERS
       EXCEPTIONS
            TOO_MANY_RECEIVERS         = 1
            DOCUMENT_NOT_SENT          = 2
            OPERATION_NO_AUTHORIZATION = 4
            OTHERS                     = 99.
IF SY-SUBRC NE 0.
    MESSAGE E000 WITH 'Error occurred while sending'.
ELSE.
    MESSAGE I000 WITH 'The document was sent'.
ENDIF.
ENDFORM.                    " SEND_FILE_AS_EMAIL_ATTACHMENT
*&      Form data
      text
--> p1        text
<-- p2        text
FORM data.
SELECT SNDPRN
         DOCNUM
         IDOCTP
         MESTYP
         DIRECT
         CREDAT
         STATUS
         FROM EDIDC
         INTO CORRESPONDING FIELDS
         OF TABLE TB_EDIDC
         WHERE STATUS = P_STATUS
         AND MESTYP IN S_MESTYP
         AND DIRECT IN S_DIRECT
         AND CREDAT IN S_CREDAT.
SELECT KUNNR
       INPNR
       FROM EDPAR
       INTO CORRESPONDING FIELDS
       OF TABLE TB_EDPAR
       FOR ALL ENTRIES IN TB_EDIDC
       WHERE KUNNR = TB_EDIDC-SNDPRN.
SELECT KUNNR
       ADRNR
       FROM KNA1
       INTO CORRESPONDING FIELDS
       OF TABLE TB_KNA1
       FOR ALL ENTRIES IN TB_EDPAR
       WHERE KUNNR = TB_EDPAR-INPNR.
SELECT ADDRNUMBER
       BUILDING
       FROM ADRC
       INTO CORRESPONDING FIELDS
       OF TABLE TB_ADRC
       FOR ALL ENTRIES IN TB_KNA1
       WHERE ADDRNUMBER = TB_KNA1-ADRNR.
LOOP AT TB_EDIDC WHERE STATUS = P_STATUS
                 AND MESTYP IN S_MESTYP
                 AND DIRECT IN S_DIRECT
                 AND CREDAT IN S_CREDAT.
TB_ED-SNDPRN = TB_EDIDC-SNDPRN.
TB_ED-DOCNUM = TB_EDIDC-DOCNUM.
TB_ED-IDOCTP = TB_EDIDC-IDOCTP.
TB_ED-MESTYP = TB_EDIDC-MESTYP.
TB_ED-DIRECT = TB_EDIDC-DIRECT.
TB_ED-CREDAT = TB_EDIDC-CREDAT.
TB_ED-STATUS = TB_EDIDC-STATUS.
READ TABLE TB_EDPAR WITH KEY KUNNR = TB_EDIDC-SNDPRN.
READ TABLE TB_KNA1 WITH KEY KUNNR = TB_EDPAR-INPNR.
READ TABLE TB_ADRC WITH KEY ADDRNUMBER = TB_KNA1-ADRNR.
TB_ED-LOC = TB_ADRC-BUILDING.
APPEND TB_ED.
ENDLOOP.
WRITE :/02 'CustomerNo',
        15 'Location Code',
        30 'Idoc Number',
        55 'Basic Type',
        70 'Message Type',
        95 'Direction',
        110 'Received Date',
        130 'Status'.
ULINE.
LOOP AT TB_ED.
WRITE :/02 TB_ED-SNDPRN,
          15 TB_ED-LOC,
          30 TB_ED-DOCNUM,
          55 TB_ED-IDOCTP,
          70 TB_ED-MESTYP,
          95 TB_ED-DIRECT,
          110 TB_ED-CREDAT,
          130 TB_ED-STATUS.
ENDLOOP.
ENDFORM.                    " data
Kindly help me in solving the issue.
Thanks in advance.
Suki.

Hi,
Check in transaction SCOT. If your mail is in error status in SCOT, you can assure that there is no problem with your code. If your message has not reached till SCOT, then the problem will be with the code.
If the mail is there in scot with error status tell the BASIS to configure it. I feel this could be the problem.
Regards,
Renjith Michael.

Error while sending transaction

Hi All,
We are facing below error while sending transactions,
We are able to send successfully OAGIS file to supplier using custom documnet over internet, but in the reports after couple of sceond it showing one blank error.
EX:
Machine Info: (usstlz-pinfwi11)
Description: Unable to identify the document protocol of the message
StackTrace:
Error -: AIP-50083: Document protocol identification error
     at oracle.tip.adapter.b2b.engine.Engine.identifyDocument(Engine.java:3245)
     at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:1666)
     at oracle.tip.adapter.b2b.msgproc.Request.postTransmit(Request.java:2384)
     at oracle.tip.adapter.b2b.msgproc.Request.outgoingRequestPostColab(Request.java:1827)
     at oracle.tip.adapter.b2b.msgproc.Request.outgoingRequest(Request.java:976)
     at oracle.tip.adapter.b2b.engine.Engine.processOutgoingMessage(Engine.java:1167)
     at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:833)
     at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:400)
     at java.lang.Thread.run(Thread.java:534)
If I check the payload it showing empty and wire message is below
Date=Tue, 23 Feb 2010 11:59:38 GMT
Server=Microsoft-IIS/6.0
X-Powered-By=ASP.NET
Content-Length=0
We are ableto receiving a MDN back from them.
Could you please tell what we need to set in below for both inbound and outbound transactions
Functional acknowledgement required?
Is acknowledgement handled by Integration B2B?
for custom document over internet...
p[lease help me to resolve this
Regards
cnu
Edited by: B2B_GoToGuY on Feb 23, 2010 4:36 AM

Anuj ,
here is the log and i send it ur ID also
Parameters
-- listing properties --
http.sender.timeout=0
2010.02.22 at 10:03:53:844: Thread-20: B2B - (DEBUG) scheme null userName null realm null
2010.02.22 at 10:03:57:590: Thread-20: B2B - (DEBUG)
Protocol = HTTP
Version = HTTP/1.1
Transport Header
Date:Mon, 22 Feb 2010 16:03:57 GMT
X-Powered-By:ASP.NET
Server:Microsoft-IIS/6.0
Content-Length:0
2010.02.22 at 10:03:57:594: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.transport.TransportInterface:send Message Successfully Transmitted
2010.02.22 at 10:03:57:597: Thread-20: B2B - (INFORMATION) oracle.tip.adapter.b2b.msgproc.Request:outgoingRequestPostColab Send Successful!, Request Message sucessfully Transmitted
2010.02.22 at 10:03:57:600: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:outgoingRequestPostColab Calling postTransmit to do post transmit processing of request message
2010.02.22 at 10:03:57:602: Thread-20: B2B - (DEBUG) DBContext beginTransaction: Enter
2010.02.22 at 10:03:57:605: Thread-20: B2B - (DEBUG) DBContext beginTransaction: Transaction.begin()
2010.02.22 at 10:03:57:607: Thread-20: B2B - (DEBUG) DBContext beginTransaction: Leave
2010.02.22 at 10:03:57:610: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:postTransmit Enter
2010.02.22 at 10:03:57:613: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:postTransmit AckMode is SYNC
2010.02.22 at 10:03:57:615: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertNativeEvtTblRow(2 params) Enter
2010.02.22 at 10:03:57:657: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertNativeEvtTblRow(2 params) Exit
2010.02.22 at 10:03:57:660: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:postTransmit Update the Message Table Row with message state Wait for Incoming Acknowledgment
2010.02.22 at 10:03:57:679: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:postTransmit Commit
2010.02.22 at 10:03:57:683: Thread-20: B2B - (DEBUG) DBContext commit: Enter
2010.02.22 at 10:03:57:690: Thread-20: B2B - (DEBUG) DBContext commit: Transaction.commit()
2010.02.22 at 10:03:57:693: Thread-20: B2B - (DEBUG) DBContext commit: Leave
2010.02.22 at 10:03:57:695: Thread-20: B2B - (DEBUG) DBContext beginTransaction: Enter
2010.02.22 at 10:03:57:697: Thread-20: B2B - (DEBUG) DBContext beginTransaction: Transaction.begin()
2010.02.22 at 10:03:57:699: Thread-20: B2B - (DEBUG) DBContext beginTransaction: Leave
2010.02.22 at 10:03:57:702: Thread-20: B2B - (INFORMATION) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage Enter
2010.02.22 at 10:03:57:711: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage Identify Business Protocol
2010.02.22 at 10:03:57:713: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.as2.AS2ExchangePlugin:AS2ExchangePlugin:identifyExchange Enter
2010.02.22 at 10:03:57:715: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.as2.AS2ExchangePlugin:AS2ExchangePlugin:identifyExchange Exit
2010.02.22 at 10:03:57:718: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage Do Unpack using the BP specific package class
2010.02.22 at 10:03:57:721: Thread-20: B2B - (DEBUG) MimePackaging:unpack:Enter
2010.02.22 at 10:03:57:723: Thread-20: B2B - (DEBUG) MimePackaging:doUnpack:Enter
2010.02.22 at 10:03:57:726: Thread-20: B2B - (DEBUG) MimePackaging:unpackNonMimeMessage:Enter
2010.02.22 at 10:03:57:728: Thread-20: B2B - (DEBUG) MimePackaging:unpackNonMimeMessage:encoding = UTF-8
2010.02.22 at 10:03:57:731: Thread-20: B2B - (DEBUG) MimePackaging:unpackNonMimeMessage:oracle.tip.adapter.b2b.packaging.Component@7cb44d
2010.02.22 at 10:03:57:733: Thread-20: B2B - (DEBUG) MimePackaging:unpackNonMimeMessage:Exit
2010.02.22 at 10:03:57:735: Thread-20: B2B - (DEBUG) MimePackaging:unpack:Exit
2010.02.22 at 10:03:57:738: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage Decode the Incoming Message into B2B Message
2010.02.22 at 10:03:57:740: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:GenericExchangePlugin:decodeIncomingMessage Enter
2010.02.22 at 10:03:57:743: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:GenericExchangePlugin:decodeIncomingMessage Number of Components = 1
2010.02.22 at 10:03:57:746: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:decodeIncomingMessage Transport Protocol = {HTTP}
2010.02.22 at 10:03:57:749: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:decodeIncomingMessage remote host name = null
2010.02.22 at 10:03:57:752: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:decodeIncomingMessage host name = null
2010.02.22 at 10:03:57:754: Thread-20: B2B - (DEBUG) calling setInitiatingPartyId() changing from null to TPName: null Type: Generic Identifier Value: 127.0.0.1
2010.02.22 at 10:03:57:757: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:decodeIncomingMessage fromParty = 127.0.0.1
2010.02.22 at 10:03:57:760: Thread-20: B2B - (DEBUG) calling setFromPartyId() changing from null to TPName: null Type: Generic Identifier Value: 127.0.0.1
2010.02.22 at 10:03:57:762: Thread-20: B2B - (DEBUG) calling setToPartyId() changing from null to TPName: null Type: Generic Identifier Value: 127.0.0.1
2010.02.22 at 10:03:57:764: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:GenericExchangePlugin:decodeIncomingMessage security info NULL
2010.02.22 at 10:03:57:767: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:GenericExchangePlugin:decodeIncomingMessage Exit
2010.02.22 at 10:03:57:770: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processHubMessage Enter
2010.02.22 at 10:03:57:772: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processHubMessage toTP 127.0.0.1
2010.02.22 at 10:03:57:775: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processHubMessage hubUrl null
2010.02.22 at 10:03:57:777: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processHubMessage Exit
2010.02.22 at 10:03:57:779: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage ProtocolCollabId = null
2010.02.22 at 10:03:57:781: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage CollaborationName null
2010.02.22 at 10:03:57:784: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:checkDuplicate Enter
2010.02.22 at 10:03:57:786: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:checkDuplicate check non-RosettaNet Message
2010.02.22 at 10:03:57:800: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:checkDuplicate Exit
2010.02.22 at 10:03:57:803: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage Protocol Collaboration Id : null
2010.02.22 at 10:03:57:805: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:identifyIncomingDocument Enter
2010.02.22 at 10:03:57:893: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:identifyIncomingDocument errcode = SetData failed - CECToolsException thrown - HRESULT[30005], description[The size of blob is wrong: must be greater then zero]
2010.02.22 at 10:03:57:897: Thread-20: B2B - (ERROR) com.edifecs.shared.jni.JNIException: SetData failed - CECToolsException thrown - HRESULT[30005], description[The size of blob is wrong: must be greater then zero]
     at com.edifecs.shared.jni.xdata.INativeToXData.SetDataNative(Native Method)
     at com.edifecs.shared.jni.xdata.INativeToXData.SetData(Unknown Source)
     at com.edifecs.shared.jni.xdata.INativeToXData.SetData(Unknown Source)
     at oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin.identifyIncomingDocument(EDIDocumentPlugin.java:367)
     at oracle.tip.adapter.b2b.engine.Engine.identifyDocument(Engine.java:3226)
     at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:1666)
     at oracle.tip.adapter.b2b.msgproc.Request.postTransmit(Request.java:2384)
     at oracle.tip.adapter.b2b.msgproc.Request.outgoingRequestPostColab(Request.java:1827)
     at oracle.tip.adapter.b2b.msgproc.Request.outgoingRequest(Request.java:976)
     at oracle.tip.adapter.b2b.engine.Engine.processOutgoingMessage(Engine.java:1167)
     at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:833)
     at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:400)
     at java.lang.Thread.run(Thread.java:534)
2010.02.22 at 10:03:57:900: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument Enter
2010.02.22 at 10:03:57:956: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument non-XML Payload
2010.02.22 at 10:03:57:958: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument iDoc ECS = null
2010.02.22 at 10:03:57:961: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument continuing
2010.02.22 at 10:03:57:964: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument non-XML Payload
2010.02.22 at 10:03:57:967: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument iDoc ECS = null
2010.02.22 at 10:03:57:970: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument could not get start pos
2010.02.22 at 10:03:57:972: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument could not get end pos
2010.02.22 at 10:03:57:975: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument non-XML Payload
2010.02.22 at 10:03:57:978: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument iDoc ECS = null
2010.02.22 at 10:03:57:981: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument continuing
2010.02.22 at 10:03:57:983: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument non-XML Payload
2010.02.22 at 10:03:57:986: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument iDoc ECS = null
2010.02.22 at 10:03:57:988: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument could not get start pos
2010.02.22 at 10:03:57:990: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument could not get end pos
2010.02.22 at 10:03:57:993: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument Exit
2010.02.22 at 10:03:58:000: Thread-20: B2B - (ERROR) Error -: AIP-50083: Document protocol identification error
     at oracle.tip.adapter.b2b.engine.Engine.identifyDocument(Engine.java:3245)
     at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:1666)
     at oracle.tip.adapter.b2b.msgproc.Request.postTransmit(Request.java:2384)
     at oracle.tip.adapter.b2b.msgproc.Request.outgoingRequestPostColab(Request.java:1827)
     at oracle.tip.adapter.b2b.msgproc.Request.outgoingRequest(Request.java:976)
     at oracle.tip.adapter.b2b.engine.Engine.processOutgoingMessage(Engine.java:1167)
     at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:833)
     at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:400)
     at java.lang.Thread.run(Thread.java:534)
2010.02.22 at 10:03:58:004: Thread-20: B2B - (ERROR) Error -: AIP-50083: Document protocol identification error
     at oracle.tip.adapter.b2b.engine.Engine.identifyDocument(Engine.java:3245)
     at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:1666)
     at oracle.tip.adapter.b2b.msgproc.Request.postTransmit(Request.java:2384)
     at oracle.tip.adapter.b2b.msgproc.Request.outgoingRequestPostColab(Request.java:1827)
     at oracle.tip.adapter.b2b.msgproc.Request.outgoingRequest(Request.java:976)
     at oracle.tip.adapter.b2b.engine.Engine.processOutgoingMessage(Engine.java:1167)
     at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:833)
     at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:400)
     at java.lang.Thread.run(Thread.java:534)
2010.02.22 at 10:03:58:006: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleExceptionBeforeIncomingTPA Enter
2010.02.22 at 10:03:58:009: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: handleInboundException Enter
2010.02.22 at 10:03:58:011: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: handleInboundException Error message is Error -: AIP-50083: Document protocol identification error
2010.02.22 at 10:03:58:013: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: isFARequired Enter
2010.02.22 at 10:03:58:016: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: isFARequired {Date=Mon, 22 Feb 2010 16:03:57 GMT, X-Powered-By=ASP.NET, Server=Microsoft-IIS/6.0, Content-Length=0}
2010.02.22 at 10:03:58:018: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: isFARequired returning false
2010.02.22 at 10:03:58:021: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: handleInboundException FA not required
2010.02.22 at 10:03:58:024: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleInboundException Updating Error Message: Error -: AIP-50083: Document protocol identification error
2010.02.22 at 10:03:58:027: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Enter
2010.02.22 at 10:03:58:030: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Wire message found
2010.02.22 at 10:03:58:032: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Creating new b2berror object
2010.02.22 at 10:03:58:036: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState enum0 not null
2010.02.22 at 10:03:58:040: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Updating wire message error information
2010.02.22 at 10:03:58:054: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Updating wire message protocol message id
2010.02.22 at 10:03:58:061: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Updating wire message payload storage
2010.02.22 at 10:03:58:087: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Creating new business message
2010.02.22 at 10:03:58:089: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertMsgTblRow Enter
2010.02.22 at 10:03:58:129: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertMsgTblRow toparty name null
2010.02.22 at 10:03:58:132: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertMsgTblRow toparty type and value Generic Identifier127.0.0.1
2010.02.22 at 10:03:58:187: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertMsgTblRow BusinessAction for the given name null null
2010.02.22 at 10:03:58:242: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Updating business message error information
2010.02.22 at 10:03:58:277: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Exit
2010.02.22 at 10:03:58:280: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleInboundException Updating Native Event Tbl Row
2010.02.22 at 10:03:58:282: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:updateNativeEvtTblRow Enter
2010.02.22 at 10:03:58:295: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateNativeEvtTblRow msgInfo.id = 0A10482B126F66BB0BC000001BE47920
2010.02.22 at 10:03:58:298: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:
** DbAccess:updateNativeEvtTblRow:tip_wireMsg protocolCollabID = null
2010.02.22 at 10:03:58:307: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleInboundException notifying App
2010.02.22 at 10:03:58:311: Thread-20: B2B - (DEBUG) Engine:notifyApp Enter
2010.02.22 at 10:03:58:324: Thread-20: B2B - (DEBUG) notifyApp:notifyApp Enqueue the ip exception message:
<Exception xmlns="http://integration.oracle.com/B2B/Exception" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<correlationId>null</correlationId>
<b2bMessageId>0A10482B126F66BB08B000001BE47910</b2bMessageId>
<errorCode>AIP-50083</errorCode>
<errorText>Document protocol identification error</errorText>
<errorDescription>
<![CDATA[Machine Info: (usstlz-pinfwi25.dev.emrsn.org)
Description: Unable to identify the document protocol of the message
StackTrace:
Error -: AIP-50083: Document protocol identification error
     at oracle.tip.adapter.b2b.engine.Engine.identifyDocument(Engine.java:3245)
     at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:1666)
     at oracle.tip.adapter.b2b.msgproc.Request.postTransmit(Request.java:2384)
     at oracle.tip.adapter.b2b.msgproc.Request.outgoingRequestPostColab(Request.java:1827)
     at oracle.tip.adapter.b2b.msgproc.Request.outgoingRequest(Request.java:976)
     at oracle.tip.adapter.b2b.engine.Engine.processOutgoingMessage(Engine.java:1167)
     at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:833)
     at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:400)
     at java.lang.Thread.run(Thread.java:534)
]]>
</errorDescription>
<errorSeverity>2</errorSeverity>
</Exception>
2010.02.22 at 10:03:58:344: Thread-20: B2B - (DEBUG) Engine:notifyApp Exit
2010.02.22 at 10:03:58:347: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleInboundException Updated the Error Message Successfully: Error -: AIP-50083: Document protocol identification error
2010.02.22 at 10:03:58:350: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: handleInboundException Exit
2010.02.22 at 10:03:58:352: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleExceptionBeforeIncomingTPA Exit
2010.02.22 at 10:03:58:355: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:postTransmit Exit
2010.02.22 at 10:03:58:358: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:outgoingRequestPostColab Exit
2010.02.22 at 10:03:58:360: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:outgoingRequest Exit
2010.02.22 at 10:03:58:363: Thread-20: B2B - (INFORMATION) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage:
Edited by: B2B_GoToGuY on Feb 23, 2010 4:57 AM

Error While sending infopackages from OLTP to BI/urgent

Hi BW friends
im workin on production support and im new to it.while
running infopackage X ,it is throwing a error
error:While sending infopackages from OLTP to BI/urgent
In status tab it shows traingular yellow colour
and diagnosis says that No idocs could be sent to bi using rfc.
so if u know please reply me
Thank you
Amarnath k

while loading data into the target we got this message and the solution is do manual update for that.

SOAP Receiver- Error While Sending Message: 500 Internal Server Error

Hello,
Our scenario: IDoc to SOAP
I have added a third party system in the SLD and have used the same in my ID configuration.
An idoc will be triggered from R/3, which will received in PI, PI will transform the IDoc into SOAP message for the third party system.
I have tested the scenario in ID from Interface Determination and its successful.
But when i try to try to test it from RWB, using Test Message in Adapter Engine, I get an error,
"Error while sending message:500 Internal server error"
If we test it using a testing software like SOAP UI, it works fine but from PI we get the error mentioned above.
Regards,
Abhishek

Hello,
Since the IDOC adapter resides on the ABAP stack, you can use this URL instead (it will be sent to the integration engine as Venkata suggested)
http://host:port/sap/xi/engine?type=entry
Also check your firewall settings from PI to the third-party system.
Hope this helps,
Mark
Edited by: Mark Dihiansan on Feb 7, 2012 11:48 AM

Error - ATTRIBUTE_IDOC_METADATA - EDI: Error while assigning IDoc number

Hi,
I'm attempting to create a simple interface which converts cutomer data from a flat file and loads it into a SAP enterprise system as an DEBMAS06 IDoc type. I am getting the error message Error - ATTRIBUTE_IDOC_METADATA - EDI: Error while assigning IDoc number in the XI message monitor.
Has anyone come accross this error before and if so, what is the resolution???
Thanks, in advance,
Pete

Hi Peter,
did you fixed it?
How did you?
got the same problem
Kind regards,
Michael

Error while sending data from XI to BI System

Hello Friends,
I m facing an error while sending data from XI to BI. XI is successfully recived data from FTP.
Given error i faced out in communication channel monitoring:-
Receiver channel 'POSDMLog_Receiver' for party '', service 'Busys_POSDM'
Error can not instantiate RfcPool caused by:
com.sap.aii.af.rfc.RfcAdapterException: error initializing RfcClientPool:com.sap.aii.af.rfc.core.repository.RfcRepositoryException: can not connect to destination system due to: com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed
Connect_PM TYPE=A ASHOST=10.1.45.35 SYSNR=01 GWHOST=10.1.45.35 GWSERV=sapgw01 PCS=1
LOCATION CPIC (TCP/IP) on local host with Unicode
ERROR partner '10.1.45.35:sapgw01' not reached
TIME Fri Apr 16 08:15:18 2010
RELEASE 700
COMPONENT NI (network interface)
VERSION 38
RC -10
MODULE nixxi.cpp
LINE 2823
DETAIL NiPConnect2
SYSTEM CALL connect
ERRNO 10061
ERRNO TEXT WSAECONNREFUSED: Connection refused
COUNTER 2
Error displaying in message monitoring:-
Exception caught by adapter framework: RfcAdapter: receiver channel has static errors: can not instantiate RfcPool caused by: com.sap.aii.af.rfc.RfcAdapterException: error initializing RfcClientPool:com.sap.aii.af.rfc.core.repository.RfcRepositoryException: can not connect to destination system due to: com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=10.1.45.35 SYSNR=01 GWHOST=10.1.45.35 GWSERV=sapgw01 PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR partner '10.1.45.35:sapgw01' not reached TIME Fri Apr 16 08:15:18 2010 RELEASE 70
Delivery of the message to the application using connection RFC_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: RfcAdapter: receiver channel has static errors: can not instantiate RfcPool caused by: com.sap.aii.af.rfc.RfcAdapterException: error initializing RfcClientPool:com.sap.aii.af.rfc.core.repository.RfcRepositoryException: can not connect to destination system due to: com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=10.1.45.35 SYSNR=01 GWHOST=10.1.45.35 GWSERV=sapgw01 PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR partner '10.1.45.35:sapgw01' not reached TIME.
Kindly suggest me & provide details of error.
Regards,
Narendra

Hi Narendra,
Message is clearly showing that your system is not reachable
102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=10.1.45.35 SYSNR=01 GWHOST=10.1.45.35 GWSERV=sapgw01 PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR partner '10.1.45.35:sapgw01' not reached
Please check to ping the BI server IP 10.1.45.35 from your XI server , in case its working you can check telnet to SAP standard port like 3201/3601/3301/3901 etc.
It seems to be connectivity issue only.
Make sure your both the systems are up and running.
Revert back after checking above stuff.
Regards,
Gagan Deep Kaushal

Error while sending a message 501 not implemented

Hi all,
running some tests checking some Xi interfaces we have the following problem :
going to Runtime Workbench --> Component Monitoring --> Adapter Engine e clicking on the Tab "Test Message" we insert Service, Interface, Namespace, Quality of Service, user and password
On "send message to" we insert the string:
http://apl06gjbx:8031/XISOAPAdapter/MessageServlet?channel=:BSY_CDFS_CRISP_DX8:CC_SOAP_IF_KE_02_In
Executing "Send Message", we get the following error :
"error while sending message : 501 not implemented"
Any suggestion ?
thanks in advance

Hi all,
using a 53100 port and xml code in payload it seems better but we get the following error:
com.sap.engine.services.servlets_jsp.server.exceptions.WebServletException: Error in dispatching request to servlet [/sub/componentmonitoringpageprocessor].
Display Stack Trace
com.sap.engine.services.servlets_jsp.server.exceptions.WebServletException: Error in dispatching request to servlet [/sub/componentmonitoringpageprocessor].
     at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:328)
     at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
     at jsp_FC_Secure1185456171353._jspService(jsp_FC_Secure1185456171353.java:24)
     at com.sap.engine.services.servlets_jsp.server.jsp.JspBase.service(JspBase.java:112)
     at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:544)
     at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:186)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
     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(AccessController.java:215)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: java.lang.NullPointerException
     at com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmDynPage.doProcessAfterInput(CmDynPage.java:60)
     at com.sapportals.htmlb.page.PageProcessor.handleRequest(PageProcessor.java:101)
     at com.sapportals.htmlb.page.PageProcessorServlet.handleRequest(PageProcessorServlet.java:62)
     at com.sapportals.htmlb.page.PageProcessorServlet.doPost(PageProcessorServlet.java:22)
     at com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmPageProcessor.doPost(CmPageProcessor.java:35)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
     ... 20 more

Error while sending the email notifcation

Hi All
I am getting this error while sending the email notifcation.If any one of you have any idea regarding this please suggest
[2012-09-12T03:55:41.288-10:00] [soa_server1] [ERROR] [SDP-26102] [oracle.sdp.messaging.driver.email] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: OracleSystemUser] [ecid: f5c1f5acbf0bb7a6:22e05768:139ba096e4d:-8000-00000000000006ef,0] [APP: usermessagingdriver-email] Error while writing e-mail message content.[[
java.lang.ArrayIndexOutOfBoundsException: 0 >= 0
     at java.util.Vector.elementAt(Vector.java:427)
     at javax.mail.Multipart.getBodyPart(Multipart.java:157)
     at javax.mail.internet.MimeMultipart.getBodyPart(MimeMultipart.java:256)
     at oracle.sdpinternal.messaging.driver.email.EmailDriver.getHeaderEncoding(EmailDriver.java:1079)
     at oracle.sdpinternal.messaging.driver.email.EmailDriver.send(EmailDriver.java:670)
     at oracle.sdpinternal.messaging.driver.email.EmailManagedConnection.send(EmailManagedConnection.java:50)
     at oracle.sdpinternal.messaging.driver.DriverConnectionImpl.send(DriverConnectionImpl.java:41)
     at oracle.sdpinternal.messaging.dispatcher.DriverDispatcherBean.onMessage(DriverDispatcherBean.java:296)
     at sun.reflect.GeneratedMethodAccessor2553.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at com.bea.core.repackaged.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:310)
     at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
     at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
     at com.bea.core.repackaged.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89)
     at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
     at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
     at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
     at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
     at com.bea.core.repackaged.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
     at $Proxy346.onMessage(Unknown Source)
     at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:574)
     at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:477)
     at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:379)
     at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:4659)
     at weblogic.jms.client.JMSSession.execute(JMSSession.java:4345)
     at weblogic.jms.client.JMSSession.executeMessage(JMSSession.java:3821)
     at weblogic.jms.client.JMSSession.access$000(JMSSession.java:115)
     at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:5170)
     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
[2012-09-12T03:55:41.331-10:00] [soa_server1] [WARNING] [SDP-25107] [oracle.sdp.messaging.engine.store] [tid: [ACTIVE].ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: OracleSystemUser] [ecid: f5c1f5acbf0bb7a6:22e05768:139ba096e4d:-8000-00000000000006ef,0] [APP: usermessagingserver] Message ID bac38bd50a1f32a129c5c739335a7855 in Status object does not match previously recorded Message ID b7e259a30a1f32a12c981a3ffd343f6d.
[2012-09-12T03:55:41.362-10:00] [soa_server1] [ERROR] [] [oracle.soa.services.notification] [tid: weblogic.work.j2ee.J2EEWorkManager$WorkWithListener@3066bad4] [userId: <anonymous>] [ecid: 0000Jau4qHj9Lex_w9w0yW1GK6Rn000003,1:32530] [APP: soa-infra] <.> Error status received from UMS.[[
Status detail :
     Status type : DELIVERY_TO_GATEWAY:FAILURE,
     Status Content : Failed to set message headers: java.lang.ArrayIndexOutOfBoundsException: 0 >= 0,
     Addressed to : EMAIL:[email protected],
     UMS Driver : Farm_base_domain/base_domain/soa_server1/usermessagingdriver-email:oracle_sdpmessagingdriver_email#Email-Driver,
     UMS Message Id : b7e259a30a1f32a12c981a3ffd343f6d,
     Gateway message Id : ,
     Status Received at : Wed Sep 12 03:55:41 HST 2012.
Check status details and fix the underlying reason, which caused error.
[2012-09-12T03:55:51.492-10:00] [soa_server1] [WARNING] [] [oracle.soa.services.notification] [tid: weblogic.work.j2ee.J2EEWorkManager$WorkWithListener@3066bad4] [userId: <anonymous>] [ecid: 0000Jau4qHj9Lex_w9w0yW1GK6Rn000003,1:32530] [APP: soa-infra] <.> Could not find notification record corresponding to failed notification : (Channel message id) : b7e259a30a1f32a12c981a3ffd343f6d[[
Hence it will not be retried.
Possible cause could be purging of notification data after sending out notification, but before receiving status.
]]

Are you using your email address to send the email notifications if it Is not configured with AD? Have you populated the mail attribute in weblogic console-->realms-->my realms-->users
In addition are you sure you have configured the 'Email Driver Properties' correctly in EM ?? have you specified the Notification Mode to Email ?
Please make sure that the outgoing mail server and port along with the username and password are correct.
Also validate the workflow settings in your EM?
In addition, please validate that when you logon to BPM worklist using the admin account and click on the name for e.g. weblogic, you see the email attribute populated properly.
Thanks
ACM

Error while sending mail from SAP

Hello All,
Recently we are facing an error while sending mail from SAP. When we try to compose a message ,it is moving to a dump error RAISE_EXCEPTION.
The details from ST22,
Short text
    Exception condition "FOLDER_NOT_EXIST" raised.
Error analysis
    A RAISE statement in the program "SA
    condition "FOLDER_NOT_EXIST".
    Since the exception was not intercep
    program, processing was terminated.
Kindly suggest..
Thank You,
Regards,
Hasan

Hello Priyanka,
Actually, I performed the following two steps in order to solve the issue:
- In transaction SICF, the node for SAPConnect must be active. In our system, this node was in inactive state. Hence I activated it.
- Then In transaction SCOT-> Settings menu--> default domain should be 'xyz.com' if the email addresses in your company are maintained with a suffix xyz.com.
But for me the problem didnt get solved here..
The problem that i am facing now is that if in my user profile, I have the email address maintained, then i get an error saying 'Sender address rejected'. However, if i goto transaction SU01 and clear the email id, the mail is successfully sent to outer world.
You can try the above mentioned two steps using SICF and SCOT. If the problem does not get solved then try clearing the mail id in ur user profile.
Hope this helps. If you find an answer to the problem of the mail id getting cleared, then please let me know..
Regards,
Himanshu

Error while sending emails from SOA 11G BPEL

Hi All,
I have configured an error email in my catch/catch-all blocks. Incase I dont have any retry action in my faultpolicies.xml file, the error email is sent fine. However if any remote/binding fault occurs and retry is done on partnerlink, in those cases the Error Notification service fails with below error:
ORABPEL-31015
Error while sending notification.
Error while sending notification to email.
Possible causes : SDPMessaging Driver not configured; Invalid To Address is used; Email server/Messaging gateway is down; using IP address as part of email ID instead of domain name;.
Caused by: javax.naming.NameNotFoundException: While trying to look up comp/env/ejb/services/NotificationServiceBean in /app/ejb/ejb_ob_engine_wls.jar#BPELActivityManagerBean.; remaining name 'comp/env/ejb/services/NotificationServiceBean'
sendEmailNotification WSIF Exception occured. Please check stack trace "Cannot get Object part 'Responses'. No parts are set on the message"
If I throw a remote/binding fault (throw activity), the error email gets sent. However whenever the retry happens incase of a fault, the above error comes.
Any idea what can be reason behing this...
Regards
Subhankar

try to call a sub process from your catch all block and use the email activity in that subprocess. this should work

Error while sending SMS

Hi ,
I have done the setup for SMPP Driver properties.
We have a clickatell account and registered the server IP with them.
I am getting the following error while running the BPEL process to send SMS. Please help.
Error while sending notification to 'sms:919876543210; 7074de6c8d92005d036d07190f170cb5'.
Possible causes : SDPMessaging Driver not configured; Invalid To Address is used; Email server/Messaging gateway is down; using IP address as part of email ID instead of domain name;.
Regards,
Surendra
Edited by: svsingh on Mar 18, 2010 5:09 AM

Hallo,
Possible Error Sources
●     The database is not running, or the database URL is incorrect
                -> The problem can be solved using the Visual Administrator or by a manual modification of the data-sources.xml file
●     Wrong user or password parameters
                -> The problem can be solved via the Visual Administrator or by a manual modification of the data-sources.xml file.
●     Maximum count of simultaneous connections to the database has been reached
                -> To increase the maximum number of opened connections and/or the time to wait for a new connection you should change the DataSource properties in the Visual Administrator or manually modify of the data-sources.xml file.
●     Problem with connection sharing if J2EE transaction is running
               -> The problem is caused while in an active JTA transaction there is an inappropriate attempt to open a second connection. There is either an attempt to get a second connection from an un-shareable non-XA DataSource, or an attempt to get it from another non-XA DataSource.
Br,
Rajesh Gupta.

Error while sending message.

Hi,Could anyone explain the below error message and tell me how can we solve this?
Error while sending message: com.sap.aii.af.ra.ms.api.ConfigException: ConfigException in XI protocol handler. Failed to determine a receiver agreement for the given message. Root cause: com.sap.aii.af.service.cpa.impl.exception.CPALookupException: Couldn't retrieve outbound binding for the given P/S/A values: FP=;TP=;FS=NDE_CLNT200;TS=;AN=Z_FI_OUTBOUND_SAP_TO_SIP;ANS=urn:sap-com:document:sap:rfc:functions;
Regards,
sai.

Hello,
I have the same problem here. I already did many times redefine the wohle szenario and also tried out many different adapters. But any time I get the same error message. I checked the agreements and determinations very carefully. The Test in IDR said this:
Senderagreement
<not found>
<Trace level="1" type="B">SENDER AGREEMENT SIMULATION</Trace> <Trace level="1" type="T">Simulating Adapter Engine...</Trace> <Trace level="1" type="T">Simply trying to loolup for the most specific Sender Agreement object</Trace> <Trace level="1" type="T">no objects found</Trace> <Trace level="1" type="T">Note that real results may differ</Trace>
Receiverdetermination
| BusSys_A | MI_HTTPtoJDBC_HTTP
<Trace level="1" type="B">CL_RD_PLSRV-ENTER_PLSRV</Trace>... (4 Zeilen)
Interface-determination
| BusSys_A | MI_HTTPtoJDBC_HTTP | | BusSys_B
<Trace level="1" type="B">CL_ID_PLSRV-ENTER_PLSRV</Trace>... (4 Zeilen)
Interface-Mapping
<not found>
Runtimeerror
com.sap.aii.utilxi.misc.api.BaseRuntimeException thrown during application mapping com/sap/xi/tf/_MM_HTTPtoJDBC_Input_: RuntimeException in Message-Mapping transformatio~
<Trace level="1" type="B">CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV</Trace>... (152 Zeilen)
I hope you can help me getting it working. thank you

SM58 - Error while sending IDOC

Similar Messages

Maybe you are looking for