Error while sending Material Master IDOC to Auto ID 2.1
Hello All,
I am using Auto ID 2.1 with SP1 on NW04.
Integration server is XI 3.0 with corresponding XI Content for Auto ID.
The backend is ERP2004.
I am using the config guide for Auto ID 2.1.
After completing the configuration, I tried sending the Material Master IDOC to Auto ID.
IDOC gets created successfully. XI says the message transfer is successfully.
In the log of Auto ID. I am getting the following error while importing the Material Master product:
Product ID AUTOIDAII_MAT has an invalid format
Internal error in /AIN/DM_PROD_COMMIT
Message no. COM_PRODUCT897
The description says that it may be a program error.
Or the program expects some variable to be filled which has not occured.
Any idea what could be the error. Or where should I try looking for to get more detail info.
Do some one knows what should be the patch levels for the different components in all three servers for Auto ID 2.1 SP1.
Thanks for any kind of input.
Regards,
Arundeep Singh
HI Arundeep,
use the following
1) XI 3.0 SP level 12
2) AII 2.1 SP2
3) check in rfid outbound configuration guide for any customising for product to be done in AII
regards,
ashit singh
Similar Messages
-
Error while sending Material Master IDOC to Auto ID
Hello All,
I am using Auto ID 4.0 on NW04s.
The backend is ERP2005.
I am trying scenario from RFID-Enabled Outbound Processing - Conf Guide (SAP AII 4.0)
After completing the configuration on the backend, I tried sending the Material Master IDOC to Auto ID.
I get a message that IDOC is just being created. I could not find it in the transaction WE02.
Also, they are not appearing in the AII system.
Thanks for any kind of input.
Regards,
Message was edited by:
Rahul GavandeHi Rahul,
I have not worked on these version of products. And I don't know what changes have been done in the new versions.
But still, can you let me know, what is the exact configuration that you have done and also
which partner are you trying to send the IDOC. And if you are trying to send the IDOC then I will suggest to debug the transaction and see till what level it proceeds.
Best of luck,
Arundeep -
Runtime error while creating material master data
hello sir,
i am facing one prolem while creating MATERIAL MASTER DATA.
AFTER GIVING ALL REQUIRED INFORMATION WHEN I AM GOING TO SAVE THE DOCUMENT ITS SHOWING ABAP RUNTIME ERROR.
MESSAGE TYPE: - MDS_KEYMAP.
MESSAGE CLASS: 001.
PLEASE TELL ME WHAT TO DO?
REGARDS..SIR THANK YOU FOR YOUR REPLY.
I ALREADY DONE THAT DUMP ANALYSIS.
SO PLEASE KINDLY GIVE ME IN DETAILS ABOUT THAT SOLUTION... -
Error while loading material master data
I am loading delta data for material master and its giving me the following error:
"Programs not generated for InfoSource 0MATERIAL_ATTR and source system".
How to resolve this error?
Need ur help urgently.
ThanksHi,
While loading attributes U have to select the transfer structure of the 0MATERIAL_ATTR then activate it..now proceed if it is already replicated in to BW system... other wise first do that..then go ahead....Similar to Text also...
Regards
Siddhu -
Error while creating material master
hi,
I'm getting this error message when I'm creating a material master in a specific plant/sloc. I'm probably guessing its in config. I really need some help here.
"Tables TCURM and T001W inconsistent; notify your system administrator" .
could any one draw some light on this.
thanks regards,
chintathis is not application server specific problem.
Suggest you to go to [Logistic/MM forum|SAP ERP - Logistics Materials Management (SAP MM);.
regards,
Vincent -
Error While Uploading Material Master Through Bdc Call Transaction
Hi Sap Gurus,
I am doing Bdc call Transaction for Material Master Uploading.
But After Entering data for 4-5 screen i got a error_
Field Mara-iprkz doesn,t exit in the screen saplmgmm 4000
Field Mara-prctr doesn,t exit in the screen saplmgmm 4000
Field Mbew-stprs doesn,t exit in the screen saplmgmm 4000
Field Marc-mtvfe doesn,t exit in the screen saplmgmm 4000
Enter Valuation class.
This is my Programme....................................
<removed by moderator>
Thanks in advance.
Arindam
Moderator message: please post only relevant code parts, your post must be less than 5000 characters to preserve formatting.
Edited by: Thomas Zloch on Apr 16, 2011 9:29 PMSorry for my obvious answer, but you should ask a more precise question.
Your errors are that you try to enter fields but they don't exist, so it sounds logic.
And the error "Enter Valuation class." means that the field is mandatory. So you must enter it.
Re-record the transaction using SHDB (eventually play with the http://wiki.sdn.sap.com/wiki/display/ABAP/Recordduringplay), run it in A display mode, and correct your program.
Sandra
perform bdc_dynpro using 'SAPLMGMM' '4000'.
perform bdc_field using 'MVKE-SKTOF'
'X'.
perform bdc_dynpro using 'SAPLMGMM' '4000'.
perform bdc_field using 'MARC-PRCTR'
wa_mara-prctr."'MUMBAI'.
perform bdc_dynpro using 'SAPLMGMM' '4000'.
perform bdc_field using 'MARA-IPRKZ'
'D'. -
ERROR -WHILE LOADING MATERIAL MASTER FROM A FLAT FILE
HI GUYS ,
I AM TRYING TO CREATE MATERIAL MASTER FROM A FROM FLAT FILE
IAM GETTIGN AN ERROR MESSAGE
'YOU HAVE NOT FULLY MAINTAINED THE DESCRIPTIONS'
REQUIRE HELP ON THIS
THANKSHello Nishant
All the inputs that are required to create a material in dialog (MM01) should be mandatory as well if you are going for LSMW or BAPI. Obviously your material requires a description (which will end up in MAKT). If you have this description in your flat file then there are additional (perhaps language-dependent) descriptions required.
You could try to use BAPI_MATERIAL_SAVEDATA in your test environment to find out the minimum input that is required to create a material in R/3.
You may also have a look at thread what are the parameters have to pass to bapi material creation?
Regards
Uwe -
UoM conversion error while loading Material Master
Hi,
Our Legacy system is also SAP (lower version) and we're trying to move the data to ECC6.0. We're using MATMAS_MASS_BAPI03 to move Material master records.
All the Alternative UoM to be moved with 'no change'. Everything gets moved except for LBs and FT3s and we get message 'UoM Conversions are inconsistent'.
I entered LBs, for example, online in the new system and found that conversion factors (NUmerator and Denominator) were indeed different.
Legacy LB: Numerator - 4756 and Denominator - 65113
New System LB: Numerator - 2564 and Denominator - 35103
If you have noticed, we will get the same result if you divide Numerator by Denominator.
Note: KG values were same in the both systems without any issue.
What should we do to get it right?
Best Regards,
RamHi,
While loading attributes U have to select the transfer structure of the 0MATERIAL_ATTR then activate it..now proceed if it is already replicated in to BW system... other wise first do that..then go ahead....Similar to Text also...
Regards
Siddhu -
Error while creatting the Material Master IDOC in ERP 2005
Hello All,
I am trying to create scenario from RFID-Enabled Outbound Processing - Conf Guide (SAP AII 4.0).
I am using Auto ID 4.0 on a NW04s system. The backend is a ERP2005 system.
The scenario requires that I need to create a material in the backend and send it to the NW04s system using IDOCs.
After completing the configuration on the backend, I tried sending the Material Master IDOC to Auto ID from the transaction AIDMM. I get a message that IDOC is just being created. But I could not find it in the transaction WE02.
On debugging I found that the function MARD_GENERIC_READ_MATNR_PLANT resulted in error.
Thanks for any kind of input.
Regards,
Rahul
Message was edited by:
Rahul GavandeDear,
Check ABAPer for file settings.
- CANNOT_SKIP_ATTRIBUTE_RECORD : The attributes could not be read in the EPS parcel. The file cannot be opened for reading, because it may have been deleted in the meantime.
- CANNOT_DETERMINE_EPS_PARCEL : The EPS parcel is not in the EPS Inbox, because it may have been deleted. You must download the relevant patch again (for example, Hot Package).
- CANNOT_DETERMINE_DATA_FILES : The name of a data file could not be determined, because a profile parameter was not correctly configured. Check the settings using the report RSPARAM.
- CANNOT_DISASSEMBLE_R_DATA_FILE : An R3trans data file could not be unpacked. A possible error source is that the relevant EPS parcel was not found. The data file could not be opened for writing. An error occurred when transmitting a 20K block from the EPS Inbox to the directory /usr/sap/trans/data (UNIX).
- CANNOT_DISASSEMBLE_D_DATA_FILE : An ADO data file could not be unpacked. The reasons are the same as with the message CANNOT_DISASSEMBLE_R_DATA_FILE .
- CANNOT_CREATE_COFILE : The cofile could not be created from the relevant data file. One possible error source is that <sys>adm does not have write authorization for the directory /usr/sap/trans/cofiles (UNIX).
Check Note: 70752.
Regards,
Syed Hussain. -
Error Message no. MM214 while creating material master
Hi folks!!
While creating material master, when i fill the MRP controller field and press enter, I get the message...
The MRP controller 391 does not exist for plant
Message no. MM214
I have checked, the MRP controller is availble in Master Data for MRP Controller. And we have already created many material master with this MRP Controller.
What could be the possible cause for this error. Please help.
Best regardsHi Qamar,
Please go thru the bellow threads,
Assignement of MRP controller to Plant
MRP CONTROLLER
MRP Controller
Re: MRP controller extension from plant 1 to plant 2
Thanks,
Swamy H P -
Hello Rescue Team,
I am facing the following error :\
16.06.2014 23:22:42.164
Error
Error before sending due to idoc parsing error: (7) IDOC_ERROR_PARSE_FAILURE: An IDocConversionException occurred while parsing IDocXML for type <ZORDERS10>: state=READING_FIELD_VALUE_TAG, charPosition=526, lineNumber=1, columnNumber=527
16.06.2014 23:22:42.166
Error
MP: exception caught with cause com.sap.aii.af.idoc.exception.IDOCAdapterException: Error before sending due to idoc parsing error: (7) IDOC_ERROR_PARSE_FAILURE: An IDocConversionException occurred while parsing IDocXML for type <ZORDERS10>: state=READING_FIELD_VALUE_TAG, charPosition=526, lineNumber=1, columnNumber=527
16.06.2014 23:22:42.190
Error
Exception caught by adapter framework: (7) IDOC_ERROR_PARSE_FAILURE: An IDocConversionException occurred while parsing IDocXML for type <ZORDERS10>: state=READING_FIELD_VALUE_TAG, charPosition=526, lineNumber=1, columnNumber=527
16.06.2014 23:22:42.190
Error
Transmitting the message to endpoint <local> using connection EDISeparator_http://sap.com/xi/XI/EDISeparator failed, due to: com.sap.aii.af.idoc.exception.IDOCAdapterException: Error before sending due to idoc parsing error: (7) IDOC_ERROR_PARSE_FAILURE: An IDocConversionException occurred while parsing IDocXML for type <ZORDERS10>: state=READING_FIELD_VALUE_TAG, charPosition=526, lineNumber=1, columnNumber=527
and the payload transferred is as attached in the attachment below.
I have refered various blogs, however I am still not able to understand how to get the exact location of the error location..According to me, the value that is giving trouble is OTH in <BSARK> however I have checked the permitted values for BSARK on ECC and OTH is maintained.
Can you please help how I can resolve this error.
Thanks
SaurabhHi Guys,
This is solved..I corrected the date format of the ZZTIME segment from 1157 to 115700.
Thanks
Saurabh -
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 AMHi 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. -
Batch management error while creating material
Hi All,
My client does not want to have qty updating and only value udating for his all materials. we are managing thro by removing qty updating tick for plants.
Now issue is while craeting material master for semi finished material and while activating batch management tick we are getting below error. While selecting display error icon message read as follows
" Batch management may not be defined for value-only materials."
Need all of your help to fix this
Thanks
A.GururajanBatches are used to manage stocks not only at material level, you do Batch managment because you require more details for the stock.
Value-only materials are just the oposite of this:
Represents a group of articles whose inventory is to be managed on a value basis, but not on an article basis.
So value-only articles with batch managment does not make any sense. -
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 AMAnuj ,
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
Maybe you are looking for
-
Select in pl/sql stored proc.
Hi friends, I am new to oracle development and were trying to write some basic stored procedure,when i try to put a simple stored select statment in between my 'BEGIN' and 'END' clause it never let me do that,it says that 'INTO' clause is expected,I
-
Currently we are using terminologies "Sender" and "Receiver" for the charge codes in Duet. Is it OK if we replace the terms Sender and Receiver with the following. Sender: Debited from Receiver: Credited to Are these new terminologies OK in the FICO.
-
How to remove extra pages in numbers document?
It used to be, when creating a spreadsheet, you could begin with "Page View" so that one has parameters so as not to create extra pages in the document. In using the latest version, I'm not seeing this. Result: I have 4 pages to my spreadsheet, bu
-
Plantronics GameCom Pro mic generates static on MB Pro but not on old iMac.
I just bought a Plantronics GameCom Pro 1 (GCP1) headset and it generates lots of static on my 17in MB Pro, when the GCP1 mic is used. I tried the GCP1 on my old iMac and the sound was crystal clear. I tried all three USB ports on the MB Pro and rebo
-
I want to save a project to an external hard drive.
I've tried to export a movie from Imovies to an external harddrive but whilst it appears to be doing this the file never appears in my external harddrive. I've also tried to copy the file manually but this does not work either.