Problem while sending mail to external mail ids

Hi All,
while trying to send mail to external mail ids through some custom program, i'm facing an error as "recipient not in address management".
Can anyone giude me why this is occuring and actually what is this Address management?
Thanks & Regards,
Anil.

Hi,
Check this sample code..
http://www.sapdevelopment.co.uk/reporting/email/email_mbody.htm
* Add the recipients email address
clear it_receivers.
refresh it_receivers.
 it_receivers-receiver = p_email.
it_receivers-rec_type = 'U'.
it_receivers-com_type = 'INT'.
it_receivers-notif_del = 'X'.
it_receivers-notif_ndel = 'X'.
append it_receivers.
what Fm you are using..?are you specifying like above for e-mail address..
Regards
vijay

Similar Messages

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.

Problem while sending Abap list to mail in the background

Hi all,
I am sending abap list to email in the background.
My code as folllows:
DATA: so_ali LIKE solisti1 OCCURS 100 WITH HEADER LINE.
DATA: listobject LIKE abaplist OCCURS 0 WITH HEADER LINE.
DATA: objpack LIKE sopcklsti1 OCCURS 2 WITH HEADER LINE.
DATA: objhead LIKE solisti1 OCCURS 1 WITH HEADER LINE.
DATA: objtxt LIKE solisti1 OCCURS 10 WITH HEADER LINE.
DATA: reclist LIKE somlreci1 OCCURS 5 WITH HEADER LINE.
DATA: doc_chng LIKE sodocchgi1.
DATA: tab_lines LIKE sy-tabix.
DATA: lt_user TYPE soud3 OCCURS 0 WITH HEADER LINE.
*Start of modification Tix 14411 for transport request D82K929044
DATA: it_user like SODLIENTI1 occurs 0 with header line.
*End of modification for Tix 14411 for transport request D82K929044
CLEAR: listobject, so_ali, objpack, objhead, objtxt, reclist, doc_chng.
REFRESH :
 listobject, so_ali, objpack, objhead, objtxt, reclist.
creation of the document to be sent
doc_chng-obj_name = 'BOFAREPORT'.
WRITE sy-datum TO doc_chng-obj_descr.
CONCATENATE 'Bank Activity Report for :'(025)
 company_itab_tr-company_code '-' doc_chng-obj_descr INTO
 doc_chng-obj_descr. "AN052799
objtxt = 'This is the bank activity report received for'(026).
APPEND objtxt.
CONCATENATE company_itab_tr-company_code '-'
 company_itab_tr-company_name '-'
 company_itab_tr-company_city INTO
 objtxt.
APPEND objtxt.
WRITE sy-datum TO objtxt.
CONCATENATE 'Date Received : '(027) objtxt INTO objtxt.
APPEND objtxt.
WRITE sy-uzeit TO objtxt.
CONCATENATE 'Time Received : '(028) objtxt INTO objtxt.
APPEND objtxt.
DESCRIBE TABLE objtxt LINES tab_lines.
READ TABLE objtxt INDEX tab_lines.
doc_chng-doc_size = ( tab_lines - 1 ) * 255 + STRLEN( objtxt ).
Creation of the entry for the compressed document
CLEAR objpack-transf_bin.
objpack-head_start = 1.
objpack-head_num = 0.
objpack-body_start = 1.
objpack-body_num = tab_lines.
objpack-doc_type = 'RAW'.
APPEND objpack.
Creation of the document attachment
CALL FUNCTION 'SAVE_LIST'
 EXPORTING
 list_index = '0'
 TABLES
 listobject = listobject
 EXCEPTIONS
 list_index_invalid = 1
 OTHERS = 2.
CALL FUNCTION 'TABLE_COMPRESS' "Schneller Tabellencopy
 TABLES
 in = listobject
 out = so_ali.
DESCRIBE TABLE so_ali LINES tab_lines. "objbin
objhead = 'BOFA-REPORT'. APPEND objhead.
Creation of the entry for the compressed attachment
objpack-transf_bin = 'X'.
objpack-head_start = 1.
objpack-head_num = 1.
objpack-body_start = 1.
objpack-body_num = tab_lines.
objpack-doc_type = 'ALI'.
objpack-obj_name = 'BOFAREPORT'.
objpack-obj_descr = 'Bank Activity Report'.
objpack-doc_size = tab_lines * 255.
APPEND objpack.
Completing the recipient list
SELECT * FROM zwfi_yefap_paypr WHERE
 bukrs = company_itab_tr-company_code.
 IF NOT ( zwfi_yefap_paypr-list1 IS INITIAL ).
 clear it_user[].
 CALL FUNCTION 'SO_DLI_READ_API1'
 EXPORTING
 DLI_NAME = zwfi_yefap_paypr-list1
 DLI_ID = ' '
 SHARED_DLI = 'X'
 IMPORTING
 DLI_DATA =
 TABLES
 DLI_ENTRIES = it_user
 EXCEPTIONS
 DLI_NOT_EXIST = 1
 OPERATION_NO_AUTHORIZATION = 2
 PARAMETER_ERROR = 3
 X_ERROR = 4
 OTHERS = 5
 IF SY-SUBRC = 0.
 loop at it_user.
 if it_user-member_typ = 'A'.
 reclist-receiver = it_user-member_adr.
 reclist-rec_type = 'U'.
 reclist-com_type = 'INT'.
 reclist-notif_del = 'X'.
 reclist-notif_ndel = 'X'.
 append reclist.
 elseif it_user-member_typ = ''.
 reclist-receiver = it_user-member_nam.
 reclist-rec_type = 'B'.
 reclist-express = 'X'.
 append reclist.
 Endif.
 endloop.
 ENDIF.
 ENDIF.
 IF NOT ( zwfi_yefap_paypr-list2 IS INITIAL ).
 clear it_user[].
 CALL FUNCTION 'SO_DLI_READ_API1'
 EXPORTING
 DLI_NAME = zwfi_yefap_paypr-list2
 DLI_ID = ' '
 SHARED_DLI = 'X'
 IMPORTING
 DLI_DATA =
 TABLES
 DLI_ENTRIES = it_user
 EXCEPTIONS
 DLI_NOT_EXIST = 1
 OPERATION_NO_AUTHORIZATION = 2
 PARAMETER_ERROR = 3
 X_ERROR = 4
 OTHERS = 5
 IF SY-SUBRC = 0.
 loop at it_user.
 if it_user-member_typ = 'A'.
 reclist-receiver = it_user-member_adr.
 reclist-rec_type = 'U'.
 reclist-com_type = 'INT'.
 reclist-notif_del = 'X'.
 reclist-notif_ndel = 'X'.
 append reclist.
 elseif it_user-member_typ = ''.
 reclist-receiver = it_user-member_nam.
 reclist-rec_type = 'B'.
 reclist-express = 'X'.
 append reclist.
 Endif.
 endloop.
 ENDIF.
 endif.
ENDSELECT.
CLEAR error_text.
Sending the document
CALL FUNCTION 'SO_NEW_DOCUMENT_ATT_SEND_API1'
 EXPORTING
 document_data = doc_chng
 put_in_outbox = 'X'
 COMMIT_WORK = 'X'
 TABLES
 packing_list = objpack
 object_header = objhead
 contents_bin = so_ali "objbin
 contents_txt = objtxt
 receivers = reclist
 EXCEPTIONS
 too_many_receivers = 1
 document_not_sent = 2
 operation_no_authorization = 4
 OTHERS = 99.
CASE sy-subrc.
 WHEN 0.
 write: / 'Result of the send process:'.
 LOOP AT reclist.
 write: / reclist-receiver(48), ':'.
 IF reclist-retrn_code <> 0.
 write 'The document was sent'.
 else.
 CONCATENATE 'The document could not be sent to : '(029)
 reclist-receiver(48) INTO error_text.
 ENDIF.
 ENDLOOP.
 WHEN 1.
 error_text = text-030.
 WHEN 2.
 error_text = 'Document could not be sent to any recipient'(031).
 WHEN 4.
 error_text = 'No send authorization'(032).
 WHEN OTHERS.
 error_text = 'Error occurred while sending'(033).
ENDCASE.
IF NOT ( error_text IS INITIAL ).
 CONCATENATE 'Mail send Error : '(034) error_text INTO error_text.
 PERFORM WRITE_LOG(YEFAP_APERAK) USING ERROR_TEXT.
 PERFORM write_log(zwfi_yefap_bank_report) USING error_text.
ENDIF.
CALL FUNCTION 'LIST_FREE_MEMORY'
 TABLES
 listobject = listobject
 EXCEPTIONS
 OTHERS = 1.
When I excute the same program in the foreground, Attachment in the mail is showing all the pages of the report output.
But when I excute the same program in the background only last page is shown in the mail attachemnt.
I think the problem is with the function module SAVE_LIST function module.
I replaced the SAVE_LIST function module with LIST_TO_MEMORY and LIST_FROM_MEMORY function modules.
It is also giving the same result.
In the foreground excution email attachemnt showing all the pages and in the background excution only last page is shown in the attachemnt.
I want all the pages dispalyed in the background mode excution in the email attachment.
How to slove this issue.
Thanks in advance.
Raja

I have seen this problem before. Please have a look at this example program. This works very well when ran in background as well as foreground
* This program works in the background,
report zrich_0003 .
data: maildata like sodocchgi1.
data: mailtxt like solisti1 occurs 10 with header line.
data: mailrec like somlrec90 occurs 0 with header line.
data: list type table of abaplist with header line.
data: ascilines(1024) type c occurs 0 with header line.
data: htmllines type table of w3html with header line.
parameters: p_check.
start-of-selection.
submit zrich_0004 exporting list to memory and return.
call function 'LIST_FROM_MEMORY'
 tables
 listobject = list
 exceptions
 not_found = 1
 others = 2.
call function 'LIST_TO_ASCI'
 tables
 listobject = list
 listasci = ascilines
 exceptions
 empty_list = 1
 list_index_invalid = 2
 others = 3.
call function 'WWW_HTML_FROM_LISTOBJECT'
 tables
 html = htmllines
 listobject = list.
clear: maildata, mailtxt, mailrec.
refresh: mailtxt, mailrec.
maildata-obj_name = 'TEST'.
maildata-obj_descr = 'Test Subject'.
loop at htmllines.
 mailtxt = htmllines.
 append mailtxt.
endloop.
mailrec-receiver = '[email protected]'.
mailrec-rec_type = 'U'.
append mailrec.
call function 'SO_NEW_DOCUMENT_SEND_API1'
 exporting
 document_data = maildata
 document_type = 'HTM'
 put_in_outbox = 'X'
 tables
 object_header = mailtxt
 object_content = mailtxt
 receivers = mailrec
 exceptions
 too_many_receivers = 1
 document_not_sent = 2
 document_type_not_exist = 3
 operation_no_authorization = 4
 parameter_error = 5
 x_error = 6
 enqueue_error = 7
 others = 8.
if sy-subrc <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
* WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
endif.
commit work.
wait up to 2 seconds.
submit rsconn01 with mode = 'INT'
 with output = 'X'
 and return.
Regards,
Rich Heilman

Problem while sending Abap list to mail

Hi All,
I am sending an abap list to mail using function module SO_NEW_DOCUMENT_ATT_SEND_API1.
Report output is going to mail id but only last page is showing.
The flow i followed in the code is as follows:
First I used Function module SAVE_LIST
Next I used Function module TABLE_COMPRESS
And finally i used function module SO_NEW_DOCUMENT_ATT_SEND_API1
Report output is going to mail id but last page is showingup.
I want all the pages to show in the email.
How it can be solved?
Thanks in Advance,
Raja

Raja,
Please provide your code that builds the ABAP List and the code that builds the mail package.

Excel problem while sending report output as mail!!

Hi,
I am sending an excel file as attachment in the mail id provided on the selection screen but once we open the attachment the first column value is not displayed in excel , but if we click on the excel cell twice , it does display the content otherwise it's seen as blank ..what may be the reason?
I am using FM SO_DOCUMENT_SEND_API1 for sending mail...
Points for sure .....
Regards
Gunjan

Hello,
DO like this:
CONSTANTS: CON_CRET TYPE X VALUE '0D', "OK for non Unicode
             CON_TAB TYPE X VALUE '09'.   "OK for non Unicode
*If you have Unicode check active in program attributes thnen you will
*need to declare constants as follows
*class cl_abap_char_utilities definition load.
*constants:
*    con_tab type c value cl_abap_char_utilities=>HORIZONTAL_TAB,
*    con_cret type c value cl_abap_char_utilities=>CR_LF.
CONCATENATE 'EBELN' 'EBELP' 'AEDAT' 'MATNR'
         INTO IT_ATTACH SEPARATED BY CON_TAB.
CONCATENATE CON_CRET IT_ATTACH INTO IT_ATTACH.
APPEND IT_ATTACH.
LOOP AT IT_EKPO INTO WA_CHAREKPO.
    CONCATENATE WA_CHAREKPO-EBELN WA_CHAREKPO-EBELP
                WA_CHAREKPO-AEDAT WA_CHAREKPO-MATNR
           INTO IT_ATTACH SEPARATED BY CON_TAB. " Check here
    CONCATENATE CON_CRET IT_ATTACH INTO IT_ATTACH. " Check here
    APPEND IT_ATTACH.
ENDLOOP.
VAsanth

Problem while sending the mail from sap

Hi experts,
                 I am facing some problem while sending mail from sap to external mail.
this is th code i am using but it is not working. plz check and tell me.
REPORT ZMAIL_DEMO.
data: maildata type sodocchgi1.
data: mailtxt type table of solisti1 with header line.
data: mailrec type table of somlrec90 with header line.
start-of-selection.
break-point.
clear: maildata, mailtxt, mailrec.
refresh: mailtxt, mailrec.
maildata-obj_name = 'TEST'.
maildata-obj_descr = 'Test'.
maildata-obj_langu = sy-langu.
mailtxt-line = 'This is a test'.
append mailtxt.
mailrec-receiver = 'SOME MAIL ID'.
mailrec-rec_type = 'U'.
append mailrec.
call function 'SO_NEW_DOCUMENT_SEND_API1'
exporting
document_data = maildata
document_type = 'RAW'
put_in_outbox = 'X'
tables
object_header = mailtxt
object_content = mailtxt
receivers = mailrec
exceptions
too_many_receivers = 1
document_not_sent = 2
document_type_not_exist = 3
operation_no_authorization = 4
parameter_error = 5
x_error = 6
enqueue_error = 7
others = 8.
if sy-subrc = 0.   "( did not receive any mail) *
write : 'mail sent'.
endif.

Hi,
Please check with the following code.
TABLES: KNA1.
data for send function
DATA DOC_DATA LIKE SODOCCHGI1.
DATA OBJECT_ID LIKE SOODK.
DATA OBJCONT   LIKE SOLI OCCURS 10 WITH HEADER LINE.
DATA RECEIVER LIKE SOMLRECI1 OCCURS 1 WITH HEADER LINE.
SELECT * FROM KNA1 WHERE ANRED LIKE 'C%'.
WRITE:/ KNA1-KUNNR, KNA1-ANRED.
send data internal table
CONCATENATE KNA1-KUNNR KNA1-ANRED
                         INTO OBJCONT-LINE SEPARATED BY SPACE.
APPEND OBJCONT.
ENDSELECT.
insert receiver (sap name)
REFRESH RECEIVER.
CLEAR RECEIVER.
MOVE: 'any_email'_ TO RECEIVER-RECEIVER,                " SY-UNAME
        'X'      TO RECEIVER-EXPRESS,
        'U'      TO RECEIVER-REC_TYPE.
APPEND RECEIVER.
insert mail description
WRITE 'Sending a mail through abap'
                 TO DOC_DATA-OBJ_DESCR.
CALL FUNCTION 'SO_NEW_DOCUMENT_SEND_API1'
     EXPORTING
          DOCUMENT_DATA              = DOC_DATA
     IMPORTING
          NEW_OBJECT_ID              = OBJECT_ID
     TABLES
          OBJECT_CONTENT             = OBJCONT
          RECEIVERS                  = RECEIVER
     EXCEPTIONS
          TOO_MANY_RECEIVERS         = 1
          DOCUMENT_NOT_SENT          = 2
          DOCUMENT_TYPE_NOT_EXIST    = 3
          OPERATION_NO_AUTHORIZATION = 4
          PARAMETER_ERROR            = 5
          X_ERROR                    = 6
          ENQUEUE_ERROR              = 7
          OTHERS                     = 8.

Send Workitem to external mail ID and Execute?

Hi all,
I have requirement to send a WorkItem to Approvers External Mail ID and executes there.I have tried to send text mail to Approver's external mail id using Fm SO_NEW_DOCUMENT_SEND_API1.
It is working fine but how to send WI to external mail id?
Is there any way?
Regards,
Arpita

Hi AC,
there is a way out for the problem which you have where the user doesnt want to put his SAP userid and pwd and wants him to take directly to the SAP screen.
For this you need to create a shortcut in your SAP logon pad for the transaction.
and since you want him/her to go directly to the tcode, you need to put an entry in your sapshortcut.ini
-pw "password"
So what this entry does is the moment user clicks the workitem in Outlook, it would directly take him to the t-code for which you have created the shortcut, without asking him/her credentials.
For your second issue, yes if 2 users get workitem, if any one reserves or executes the workitem, it automatically deletes from the other users SAP inbox.
Hope it helps.
Aditya

Problem with sending and receiving e-mail through exchange [GMail]

Hello I have problem with sending and receiving e-mail.
all is well set, username and password are correct, the server set m.google.com. verification of data is about like stepping into a post and want to check the post office gives me an error message: Can not Get Mail. The connection to the server has failed
I have this problem on my two iPhone

http://www.zdnet.com/google-drops-exchange-activesync-support-for-free-email-acc ounts-7000008836/

Problem in sending messages using java mail api

Hi All,
I have a problem in sending messages via java mail api.
MimeMessage message = new MimeMessage(session);
String bodyContent = "ñSunJava";
message.setText (bodyContent,"utf-8");using the above code its not possible for me to send the attachment. if i am using the below code means special characters like ñ gets removed or changed into some other characters.
MimeBodyPart messagePart = new MimeBodyPart();
 messagePart.setText(bodyText);
 // Set the email attachment file
 MimeBodyPart attachmentPart = new MimeBodyPart();
 FileDataSource fileDataSource = new FileDataSource("C:/sunjava.txt") {
 public String getContentType() {
 return "application/octet-stream";
 attachmentPart.setDataHandler(new DataHandler(fileDataSource));
 attachmentPart.setFileName(filename);
 Multipart multipart = new MimeMultipart();
 multipart.addBodyPart(messagePart);
 multipart.addBodyPart(attachmentPart);
 message.setContent(multipart);
 Transport.send(message);is there any way to send the file attachment with the body message without using MultiPart java class.

Taken pretty much straight out of the Javamail examples the following works for me (mail read using Thunderbird) // Define message
 Message message = new MimeMessage(session);
 message.setFrom(new InternetAddress(from));
 // Set the 'to' address
 for (int i = 0; i < to.length; i++)
 message.addRecipient(Message.RecipientType.TO, new InternetAddress(to));
// Set the 'cc' address
for (int i = 0; i < cc.length; i++)
message.addRecipient(Message.RecipientType.CC, new InternetAddress(cc[i]));
// Set the 'bcc' address
for (int i = 0; i < bcc.length; i++)
message.addRecipient(Message.RecipientType.BCC, new InternetAddress(bcc[i]));
message.setSubject("JavaMail With Attachment");
// Create the message part
BodyPart messageBodyPart = new MimeBodyPart();
// Fill the message
messageBodyPart.setText("Here's the file ñSunJava");
// Create a Multipart
Multipart multipart = new MimeMultipart();
// Add part one
multipart.addBodyPart(messageBodyPart);
// Part two is attachment
for (int count = 0; count < 5; count++)
String filename = "hello" + count + ".txt";
String fileContent = " ñSunJava - Now is the time for all good men to come to the aid of the party " + count + " \n";
// Create another body part
BodyPart attachementBodyPart = new MimeBodyPart();
// Get the attachment
DataSource source = new StringDataSource(fileContent, filename);
// Set the data handler to this attachment
attachementBodyPart.setDataHandler(new DataHandler(source));
// Set the filename
attachementBodyPart.setFileName(filename);
// Add this part
multipart.addBodyPart(attachementBodyPart);
// Put parts in message
message.setContent(multipart);
// Send the message
Transport.send(message);

Can SAP send e-mail to external mail with attached file?

Hi ABAP Guru.
Can SAP send the E-Mail to external mail server? (e.g. Hotmail, Yahoo and so on.)
And Can the E-Mail sent with attached file?
And How to do that?
Please give me your advice.
Thank you and Best Regard,
Nattapash C.

Thank you very much! Amit Gujargoud.
And I'm so sorry for my question that not clear for you and everyone.
What I need to know is How to do with ABAP Code.
I found the Function Module
'SO_DOCUMENT_REPOSITORY_MANAGER' with method 'SEND' is being used for my case.
but I don't know what field of structure RECIPIENTS (Table parameter of this Func. Module) that used for define recipient's E-Mail Address.
Does anyone know the field or Have any method to solved my case?
Please give me your advice.
Thank you and Best regard.
Nattapash C.

How to send sapmails to external mail systems

Hi,
how to send sapmails to external mail systems....
like if we want to mail a purchase order from SAP System to *@yahaoo.com or @.com.
TY.

hi manish,
u can do it.
chk this .
chk this code
DATA: objpack LIKE sopcklsti1 OCCURS 2 WITH HEADER LINE.
DATA: objhead LIKE solisti1 OCCURS 1 WITH HEADER LINE.
DATA: objbin LIKE solisti1 OCCURS 10 WITH HEADER LINE.
DATA: objtxt LIKE solisti1 OCCURS 10 WITH HEADER LINE.
DATA: reclist LIKE somlreci1 OCCURS 5 WITH HEADER LINE.
DATA: doc_chng LIKE sodocchgi1.
*& Form f_send_mail
text
--> p1 text
<-- p2 text
FORM f_send_mail .
*store the vendor name, vendor email id , employee name and employee
*email id in the internal table int_crb
Creation of the document to be sent
CLEAR doc_chng.
REFRESH objpack.
REFRESH objhead.
REFRESH reclist.
REFRESH objtxt.
File Name
doc_chng-obj_name = 'SHIPMENT'.
Mail Subject
CONCATENATE 'Shipment Document No.' int_crb_mail-shipdocnum
'Cleared.'
INTO doc_chng-obj_descr SEPARATED BY ' '.
Mail Contents
objtxt-line = 'Hi,'.
APPEND objtxt.
objtxt-line = ' '.
APPEND objtxt.
CONCATENATE 'Shipment Document Number ' int_crb_mail-shipdocnum
' cleared for move.' INTO objtxt-line SEPARATED BY ' '.
APPEND objtxt.
objtxt-line = ' '.
APPEND objtxt.
CLEAR objtxt.
objtxt-line = 'Regards '.
APPEND objtxt.
objtxt-line = ' '.
APPEND objtxt.
objtxt-line = 'SAP '.
APPEND objtxt.
CLEAR objtxt.
APPEND objtxt.
DESCRIBE TABLE objtxt LINES tab_lines.
READ TABLE objtxt INDEX tab_lines.
doc_chng-doc_size = ( tab_lines - 1 ) * 255 + STRLEN(
objtxt ).
Creation of the entry for the compressed document
CLEAR objpack-transf_bin.
objpack-head_start = 1.
objpack-head_num = 0.
objpack-body_start = 1.
objpack-body_num = tab_lines.
objpack-doc_type = 'RAW'.
APPEND objpack.
Completing the recipient list
target recipent
CLEAR reclist.
reclist-receiver = int_crb_mail-empperid. "employee email ID
"wf_empperid.
reclist-express = 'X'.
reclist-rec_type = 'U'.
APPEND reclist.
copy recipents
CLEAR reclist.
reclist-receiver = int_crb_mail-smtp_addr."vendor email id
reclist-express = 'X'.
reclist-rec_type = 'U'.
reclist-copy = 'X'.
APPEND reclist.
Sending the document
CALL FUNCTION 'SO_NEW_DOCUMENT_ATT_SEND_API1'
EXPORTING
document_data = doc_chng
TABLES
packing_list = objpack
object_header = objhead
contents_bin = objbin
contents_txt = objtxt
receivers = reclist
EXCEPTIONS
too_many_receivers = 1
document_not_sent = 2
operation_no_authorization = 4
OTHERS = 99.
COMMIT WORK.
SUBMIT rsconn01
WITH mode = 'INT'
WITH output = ' '
AND RETURN.
ENDFORM. " f_send_mail
for any clarifiaction pls mail me.
pls reward points, if this helped u.
regards,
anversha.
[email protected]

Send Alerts to external email ids

Dear All,
I am using ALERT MANAGEMENT to raise alerts and send mail to recipients. I am able to send external mails to
those users who have got a SAP Userid where the email id is maintained in the user profile. But suppose I want
to send mails to external users who do not have SAP Userid, then how to do it. I checked the program
RSALERTTEST where it gives the option to send mails to external email ids.
Regards,
Pravat.

Hi Pravat,
You can do this with SALRT_CREATE_API. But you have to create a alert category. go to ALRTCATDEF with a user role " SAP_XI_ADMINISTRATOR".
Then create category and give your receivers.
Then write a program like rsalrtdemo1 . This shows you how an alert can be called directly by a function module.
Also you can get more detailed information from these links :
Creating Alert Categories : http://help.sap.com/saphelp_nw70/helpdata/en/d0/d4b54020c6792ae10000000a155106/frameset.htm
Triggering Alerts : http://help.sap.com/saphelp_nw04s/helpdata/en/d0/5e073c8e56f658e10000000a114084/content.htm
I hope they help you.
Regards,
Orhan

Problem while sending the message using RWB

Dear All,
I am facing a problem while sending a message from RWB. I sent the message using Test Message in component monitoring, it says message sent but I am not able to see any message in sxi_monitor.
When I send the same message using the http client it successfully processed by XI and I can see the success message in sxi_monitor.
Please let me know if anyone has face similar kind of issue.
Thanks,
Alok
Edited by: Alok Raoka on May 26, 2008 5:08 PM

Dear All,
I am facing a problem while sending a message from RWB. I sent the message using Test Message in component monitoring, it says message sent but I am not able to see any message in sxi_monitor.
When I send the same message using the http client it successfully processed by XI and I can see the success message in sxi_monitor.
Please let me know if anyone has face similar kind of issue.
Thanks,
Alok
Edited by: Alok Raoka on May 26, 2008 5:08 PM

Problem while sending FAX through PRINT_TEXT FM

Hi All,
I have a problem while sending a fax.
we are sending fax through the FM PRINT_TEXT.
Below is the FM we are passing paramenters.
CALL FUNCTION 'PRINT_TEXT'
 EXPORTING
 APPLICATION = 'TX'
 DEVICE = 'TELEFAX'
 DIALOG = SPACE
 HEADER = fs_header
 OPTIONS = fs_popt
 IMPORTING
 RESULT = fs_pres
 TABLES
 LINES = int_fax
 EXCEPTIONS
 CANCELED = 1
 DEVICE = 2
 FORM = 3
 OPTIONS = 4
 UNCLOSED = 5
 UNKNOWN = 6
 FORMAT = 7
 TEXTFORMAT = 8
 COMMUNICATION = 9
 BAD_PAGEFORMAT_FOR_PRINT = 10
 OTHERS = 11.
if sy-subrc ne 0.
 p_flag = lit_x.
endif.
In INT_FAX internal table we have two fields one is tdformat second one is tdline
The lengh of the TDLINE is 132 char,Initially for all reocords we have only 108 char length,But according to user requirement we added one more field in taht
Now the lengh increased to 132 for each records.
When i checked in debugg mode the INT_FAX internal table have all 132 characters.
The problem is while checking in SOST trnasaction it is showing 108 characters in one line and remaining in second line,can you please help on this.
Thanks In advance
Sriman.

may it be that in those cases where it doesnt work, that you got no fax number?
Since it works soemtimes, it seems there are no errors, but rather in some cases some important info is missing, fax number may be one of thsoe important info in a FAX scenario.

Problem while sending IDOC to File Senario

Hi Experts
 I am having problem while sending the Idoc from SAP R/3 to File
 I have done all the setting in SAP as well in XI but while pushing IDOC
 I am getting error in the transaction sm58 in SAP R/3
" The service for the client 300(My SAP R/3 client) is not present in Integration
Directory"
I can any one explain me what to done on this....all the connections are fine
Waiting for Response
Adv points and thanx
Rakesh

Reason and Prerequisites
You send IDocs from system ABC to the exchange infrastructure (XI) of system XIZ, and error messages are issued in system ABC (Transaction SM58) for the IDOC_INBOUND_ASYNCHRONOUS function module.
This note proposes solutions for the following error messages:
a) No service for system SAPABC client 123 in the integration directory
b) Transaction IDX1: Port SAPABC, client 123, RFC destination
c) ::000
d) NO_EXEC_PERMISSION: "USER" "Business_System"
e) IDoc adapter inbound: Error error ...
Solution
a) Error message: No service for system SAPABC client 123 in the integration directory
Solution:
You send IDocs from system ABC to XI. In the control record of the IDoc, the SNDPOR field contains the value "SAPABC". The client of the sending system is determined by the MANDT field of the control record. The system ID and client are then used to determine a service without party of the type (business-system/business-service):
Business system
Activities in the System Landscape Directory (SLD)(Create technical system):
Create a technical system for system ABC in the SLD, and create the client for this. Do not forget to assign an "ALE logical system" (for example, "ABCCLNT123") to this technical system.
SLD (Business system):
You can now explicitly assign a business system to this client.
For more details, refer to the SLD documentation.
Activities in system ABC (self-registration in the SLD):
Alternatively, you can register the system in the SLD in system ABC with Transaction RZ70. You will find detailed information about the SLD registration of systems on the SAP Service Marketplace for the "Exchange Infrastructure" in the document "Exchange_Installation_Guide.pdf".
In system ABC, you can check your configuration with TransactionSLDCHECK.
Activities in Integration Directory (import business system from SLD):
You will find the business systems under Services Without Party in the Integration Services. In the Service menu, you will find the system identifiers, the client, and the corresponding ALE logical system under "Objects"->"Adapter-specific identifiers".
Use the Import/Update button to copy the data from the SLD, to create business systems, or to update their identifiers.
Business service
Activities in the Integration Builder directory:
You want to create a service without party that is not part of your system infrastructure and is therefore not maintained in the SLD.
In the Integration Builder directory, you will find the "Business-Services" under Services Without Party. In the Service menu, you will find the system identifiers, the client, and the corresponding ALE logical system under "Objects"->"Adapter-specific identifiers".
Activate the change list in Integration Directory.
In system ABC, you can restart the incorrect entry from Transaction SM58 .
b) Error message: Transaction IDX1: Port SAPABC, client 123, RFC destination
Solution:
The Integration Server tries to load the IDoc metadata from the sending system. The IDoc schemas from the Integration Repository cannot be used because they are release-dependent.
The sending system is determined by the value of the "SNDPOR" field from the IDoc control record (for example, "SAPABC").
Activities in the central XI system:
In Transaction IDX1, you can assign an RFC destination to the sending system (for example, "SAPABC"). This must be created beforehand in Transaction SM59.
Note that the IDoc metadata is cross-client data. In Transaction IDX1, only one entry must be maintained for each system. Only the lowest client is used by the runtime for Idoc metadata retrieval with RFC.
Ensure that only SAPABC and not "SAPABC_123" is entered in the port name.
c) Error message: "::000"
Solution:
This error occurs if the central XI system tries to load the IDoc metadata from the sending system by RFC.
There may be several different reasons for the failure of the metadata import, the error is not transferred in full by tRFC completely, and this results in the error message above.
User cannot log onto sending system
User/password/client is not correct or the user is logged due to too many failed logons.
Activities in sender system ABC:
Transaction SM21 contains entries for failed logons.
Activities in the central XI system:
Determine the sending port from the IDoc control record of the IDoc. If the ID of the sending system has the value "ABC", the value of the sending port is "SAPABC". You will find the RFC destination used for the "SAPABC" sending port with the lowest client in Transaction IDX1. In Transaction SM59, you will find the RFC destination containing the maintained logon data .
User does not have the required authorizations
Activities in the sender system ABC:
In Transaction SM21, you will find entries relating to authorization problems and more exact details.
Contact your system administrator and, if necessary, assign the user the required roles in user administration.
IDoctyp/Cimtyp cannot be loaded
Activities in sender system ABC:
In the sender system, you can check your IDoc types in Transaction WE30 (IDoc type editor) Take note not only of the errors, but also of the warnings.
The most common errors are:
- IDoc type or segments not released
- Segments that no longer exist are listed in the IDoc type
- Data elements that do not exist in the DDIC are assigned to fields
in the segment.
Contact your system administrator and correct these errors in the IDoc type.
d) Error message: NO_EXEC_PERMISSION: "User" "Business_System"
Solution:
You created a list of users in the directory who are authorized to use the "Business_System". The user in the error message is not on the list.
Alternatively, the same error is used if you have created a sender agreement with a channel of the IDoc type for the "Business_System" and the interface used. The user in the error message is not contained in the list of all authorized users defined there.
e) Error message: IDoc adapter inbound: Error error
Solution:
You send IDocs to the central XI system, where they are received by the IDoc adapter. The IDocs are converted into IDoc XML, and a corresponding XI message is generated and transferred to the XI Runtime Engine. The Engine tries to read its own business system from the "Exchange Profile". If the Exchange Profile is currently unavailable, the message is not processed and it is returned to the sending system with an error message.
Regard's
Prabhakar.....

Problem while sending mail to external mail ids

Similar Messages

Maybe you are looking for