Problem while sending Smartform through Fax

Hi Folks,
I am sending a Smartform through fax by setting the essential Control Parameters and Output Options while calling the function module of the Smartform.
In SOST I get the status message 710(Message transferred to node FAX(...) ) and later in around 20 minutes the message 812(No delivery to FAX(.......fax no) ) occurs for some requests.
Only few requests are sent successfully by the same program and same O/P Type and shows the status message 701(Delivered to FAX (................)).
There is no much time difference between those requests while creating.
Do you know what could be the problem?
Can you help me in solving the issue?

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.

Similar Messages

Sending Smartform through Fax

Hai All,
could anyone help me with the sample code..I want to know the parameters for fax while calling the function module..
Thanks

HI LAXMI,
CHECK THESE THREADS...
Sending Smartforms through Fax
Sending SMARTFORM output to FAX gateway
How to fax a smartform?

Sending Smartforms through Fax

Hi,
Can anybody suggest me, how to send the smartform through FAX? The output need not be printed instead it should be sent as FAX.
Thanks and Regards,
Lakshmi

Hi,
Check this sample code helps your purpose.If so,kindly reward points by clicking the star on the elft of reply,if it helps.
The following program shows you how to send a fax from within ABAP/4. The report is delivered
in the standard system and is used in Transaction SCOM for the function "Send test fax".
Only the method via the call of SAPscript with DEVICE='TELEFAX', described below, ensures the
generation of a correct transmission request, independent of the R/3 release and of the used
fax server solution and its configuration.
The regular printing (for example, with NEW-PAGE PRINT ON...) on an output device created in
the spool administration of the device class 'Telefax' does generally not work!
REPORT RSKSENDF MESSAGE-ID SK.
Test report to send a test fax
sends a fax to the number <TO_CNTRY>-<TO_NMBER>
containing an automatically generated message text.
TABLES: USR03.
PARAMETERS: TO_CNTRY LIKE T005-LAND1 OBLIGATORY,
TO_NMBER LIKE TSP01-RQTELENUM OBLIGATORY,
FROM_USR(30) TYPE C DEFAULT SY-UNAME,
TO_RECIP(30) TYPE C DEFAULT SY-UNAME.
SAPscript content ITAB
DATA: BEGIN OF TEST_DOC OCCURS 10.
INCLUDE STRUCTURE TLINE.
DATA: END OF TEST_DOC.
SAPscript header struct
DATA BEGIN OF HEADER.
INCLUDE STRUCTURE THEAD.
DATA END OF HEADER.
INITIALIZATION.
get county from user addres in usr03
system->user profile->user address
check if not empty
SELECT SINGLE * FROM USR03 WHERE BNAME = SY-UNAME.
IF SY-SUBRC = 0 AND USR03-LAND1 <> SPACE.
TO_CNTRY = USR03-LAND1.
ENDIF.
START-OF-SELECTION.
PERFORM FILL_UP_TEST_DOC.
PERFORM SHOW_TEST_DOC.
AT PF08.
PERFORM SEND_FAX TABLES TEST_DOC USING TO_CNTRY
TO_NMBER.
AT SELECTION-SCREEN ON TO_NMBER.
PERFORM CHECK_NUMBER USING TO_CNTRY TO_NMBER.
*& Form CHECK_NUMBER
FORM CHECK_NUMBER USING
COUNTRY
NUMBER.
DATA: SERVICE LIKE TSKPA-SERVICE VALUE 'TELEFAX',
LEN LIKE SY-FDPOS.
FIELD-SYMBOLS .
windows GUI push the ? from mandatory input instead
of overwriting it
LEN = STRLEN( TO_NMBER ).
IF LEN > 1.
SUBTRACT 1 FROM LEN.
ASSIGN TO_NMBER+LEN(1) TO .
IF = '?'.
 = SPACE.
ENDIF.
ENDIF.
official check FM
CALL FUNCTION 'TELECOMMUNICATION_NUMBER_CHECK'
EXPORTING
COUNTRY = COUNTRY
NUMBER = NUMBER
SERVICE = SERVICE.
on old 21?/22? release you may have to handle the
exception
because the Function uses RAISE instead of
MESSAGE... RAISING....
ENDFORM. " CHECK_NUMBER
*& Form FILL_UP_TEST_DOC
fills test text in itab TEST_DOC *
real life example needs to get real life data *
FORM FILL_UP_TEST_DOC.
DATA: DATUM(12) TYPE C,
UZEIT(10) TYPE C.
SAPscript initialization
of course, you may want to set a few parameter
(FORM,LAYOUT,....)
CALL FUNCTION 'INIT_TEXT'
EXPORTING
ID = 'ST '
LANGUAGE = SY-LANGU
NAME = 'FOO-BAR'
OBJECT = 'TEXT'
IMPORTING
HEADER = HEADER
TABLES
LINES = TEST_DOC
EXCEPTIONS
OTHERS = 1.
IF SY-SUBRC <> 0.
MESSAGE A400 WITH 'INIT_TEXT'.
ENDIF.
PERFORM ADD_EMPTY_LINE.
WRITE: SY-DATUM TO DATUM.
WRITE: SY-UZEIT TO UZEIT.
PERFORM ADD_LINES USING 'This is test Telefax'(001)
DATUM UZEIT.
PERFORM ADD_EMPTY_LINE.
PERFORM ADD_LINES USING 'From: &'(002) FROM_USR SPACE.
PERFORM ADD_LINES USING 'To: &'(003) TO_RECIP SPACE.
PERFORM ADD_LINES USING 'Fax number: & &'(004)
TO_CNTRY TO_NMBER.
PERFORM ADD_EMPTY_LINE.
PERFORM ADD_LINES USING
'This is a test fax send by Report RSKSENDF'(005)
SPACE SPACE.
PERFORM ADD_LINES USING 'on SAP system & '(006)
SY-SYSID SPACE.
PERFORM ADD_EMPTY_LINE.
PERFORM ADD_LINES USING
'the quick brown fox jumps over the lazy dog.'(101)
SPACE SAPCE.
PERFORM ADD_LINES USING
'THE QUICK BROWN FOX JUMPS OVER THE LAZY DOG.'(102)
SPACE SAPCE.
PERFORM ADD_EMPTY_LINE.
PERFORM ADD_LINES USING 'End of test'(007) SPACE
SPACE.
ENDFORM. " FILL_UP_TEST_DOC
*& Form ADD_LINES
printf a line an appends it in test_doc *
--> cformat format.
--> p1 param1
--> p2 param2
FORM ADD_LINES USING CFORMAT P1 P2.
TEST_DOC-TDFORMAT = '/'.
TEST_DOC-TDLINE = CFORMAT.
IF TEST_DOC-TDLINE CA '&'.
REPLACE '&' WITH P1 INTO TEST_DOC-TDLINE.
IF TEST_DOC-TDLINE CA '&'.
REPLACE '&' WITH P2 INTO TEST_DOC-TDLINE.
ENDIF.
ENDIF.
APPEND TEST_DOC.
ENDFORM. " ADD_LINES
*& Form ADD_EMPTY_LINE
appends an empty line to test_doc *
FORM ADD_EMPTY_LINE.
TEST_DOC-TDFORMAT = '/'.
CLEAR TEST_DOC-TDLINE.
APPEND TEST_DOC.
ENDFORM. " ADD_EMPTY_LINE
*& Form SHOW_TEST_DOC
lists the test doc for aproval *
*>>>> this is for fun only because PRINT_TEXT also
offers a preview *
FORM SHOW_TEST_DOC.
FORMAT COLOR COL_BACKGROUND INTENSIFIED OFF.
WRITE: / 'Test fax would look like this:'(020).
ULINE.
SKIP.
LOOP AT TEST_DOC.
IF TEST_DOC-TDLINE <> SPACE.
WRITE:/ TEST_DOC-TDLINE.
ELSE.
SKIP.
ENDIF.
ENDLOOP.
SKIP.
ULINE.
FORMAT COLOR COL_POSITIVE INTENSIFIED OFF.
WRITE: 'Press PF8 to send it'(021).
ENDFORM. " SHOW_TEST_DOC
*& Form SEND_FAX
send fax by calling SAPscript *
Note: Instead of using PRINT_TEXT you may also *
call OPEN_FORM / WRITE_FORM_LINES / CLOSE_FORM, *
this allows you to use a similar program structure *
as with NEW-PAGE PRINT ON / WRITE / NEW-PAGE PRINT
OFF *
FORM SEND_FAX
TABLES DOC2FAX STRUCTURE TEST_DOC
USING COUNTRY
NUMBER.
DATA: SID(5) TYPE N.
DATA BEGIN OF POPT.
INCLUDE STRUCTURE ITCPO.
DATA END OF POPT.
DATA BEGIN OF PRES.
INCLUDE STRUCTURE ITCPP.
DATA END OF PRES.
CLEAR POPT.
POPT-TDCOPIES = 1. " one copy
POPT-TDDEST = " done internaly by script,
POPT-TDPRINTER = " do not fill !!!
POPT-TDNEWID = 'X'. " do not reuse old spool request
POPT-TDDATASET = 'TEST'(022). " fill as you want
POPT-TDSUFFIX1 = 'FAX'(023). " fill as you want
POPT-TDSUFFIX2 = SY-UNAME. " fill as you want
POPT-TDIMMED = 'X'. " send now
POPT-TDLIFETIME = 8. " keep 8 days in spool
POPT-TDTELENUM = NUMBER. " number without country code
POPT-TDTELELAND = COUNTRY. " country of recipient
POPT-TDCOVER = 'test fax'(024).
POPT-TDCOVTITLE = 'test fax'(024).
POPT-TDIEXIT = 'X'.
CALL FUNCTION 'PRINT_TEXT'
EXPORTING
APPLICATION = 'TX'
ARCHIVE_INDEX = ' '
ARCHIVE_PARAMS = ' '
DEVICE = 'TELEFAX' "<<< here we say: fax it !
DIALOG = 'X'
HEADER = HEADER
OPTIONS = POPT
IMPORTING
RESULT = PRES
TABLES
LINES = DOC2FAX
EXCEPTIONS
OTHERS = 01.
do not bother with exception in sample code
CANCELED = 01
DEVICE = 02
FORM = 03
OPTIONS = 04
UNCLOSED = 05
UNKNOWN = 06
FORMAT = 07
TEXTFORMAT = 08
EXTERNAL = 09.
IF SY-SUBRC = 0.
arriving here means we could send:
SID = PRES-TDSPOOLID.
IF SID > '00000'.
MESSAGE S433 WITH SID.
ENDIF.
LEAVE .
ELSE.
do not bother with exception in sample code
MESSAGE A400 WITH 'PRIN_TEXT'.
ENDIF.
ENDFORM. " SEND_FAX

Problem while sending mail through posprocess event hadler inOIM 11g r2

Hi,
i am sending mail through posprocess event hadler inOIM 11g r2 when user is created.But i am getting following error in resolver class.
java.lang.NullPointerException
at oracle.iam.identity.usermgmt.impl.UserDetailsProviderImpl.getUserDetails(UserDetailsProviderImpl.java:102)
at oracle.iam.notification.impl.util.NotificationUtil.getUserPreferences(NotificationUtil.java:83)
at oracle.iam.notification.impl.NotificationServiceImpl.notify(NotificationServiceImpl.java:523)
at oracle.iam.notification.impl.NotificationServiceImpl.notify(NotificationServiceImpl.java:271)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307)
at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
at oracle.iam.platform.utils.DMSMethodInterceptor.invoke(DMSMethodInterceptor.java:25)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
at oracle.iam.notification.impl.util.NotificationUtil.getUserPreferences(NotificationUtil.java:83)
at oracle.iam.notification.impl.NotificationServiceImpl.notify(NotificationServiceImpl.java:523)
at oracle.iam.notification.impl.NotificationServiceImpl.notify(NotificationServiceImpl.java:271)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307)
at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
at oracle.iam.platform.utils.DMSMethodInterceptor.invoke(DMSMethodInterceptor.java:25)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
Edited by: 853559 on Sep 25, 2012 6:27 AM

If you are using Custom Notification XML, make sure to have StaticData element in it. StaticData defines the entitites that can be used in the notification template, and these entities attributes are used to define substitution tokens in the template.

Problem With Sending Notification Through Fax While Creating A PO

Hi All,
While creating a purchase order with the output medium set to as FAX, once we click on save the entire information is actually faxed to the Number provided in the communication medium.
Now if a problem occurs, usually a notification message is displayed, the issue is, the notification message is not getting displayed anymore even if the the fax is not being sent.
Hence the user has no way of know that a fax was sent or not unless he check his inbox.
I have spoken to the Basis and the Functional Consultants and they say that there is nothing wrong with the Configuration Part.
Hence can you tell me what could be the possible reasons for this problem that is happening?
Please Advise!!!
Pablo

Hi,
Which Scenario are you implementing??This BADI is to be implemneted for PO only if you are in the Extended classic scenario and the PO in SRM is the leading PO.
BR,
Disha.
Pls reward points for useful answers.

Problems when trying to send a smartform through fax

Hi,
Im currently confronting a problem when sending smartforms through fax to multiple recipients.
This is the scenario Im working on:
The client needs to be able to send a document, could be a PO or invoices, to diferent recipients at the same time. So far in case of purchase orders, we have been able to find the respective faxes and emails for each of the partner functions.
Functionality for email is working as desired but when sending faxes I have problems.
Reviewing the output through SOST I get all my receipients which are email and faxes. Emails are fine since it creates a PDF attachment with the order and all of its details.
For fax I get the same even though the paramenters are set for fax.
Here is my code if you could please help me here on this one.
SELECT lifn2 FROM EkPA into l_ekpa-lifn2
 WHERE EBELN = a_EBELN.
 APPEND l_EKPA.
ENDSELECT.
SELECT adrnr
 FROM lfa1
 INTO itab-q_adrnr
 FOR ALL ENTRIES IN l_ekpa WHERE lifnr = l_ekpa-lifn2.
 APPEND itab.
ENDSELECT.
*& End of partner address
*& Selection of Address or Fax number from ADR3 & ADR6 according to ADRNR
*& Nato
IF sy-subrc EQ 0.
 loop at itab.
 SELECT SINGLE smtp_addr INTO (itab-q_mail)
 from adr6 where addrnumber = itab-q_adrnr and flg_nouse eq space.
 IF itab-q_mail ne Space.
 Move 'U' to itab-q_typ2(1).
 Move 'X' to itab-q_express(1).
 Move 'EXT' to itab-XOBJT.
 ENdIF.
 SELECT SINGLE FAXNR_LONG INTO (itab-q_fax)
 SELECT SINGLE country FAX_NUMBER INTO (itab-q_cty, itab-q_fax )
 from adr3 where addrnumber = itab-q_adrnr and flg_nouse eq space.
 If itab-q_fax ne space.
 Move 'F' to itab-q_typ(1).
 Move 'TELEFAX' to itab-q_com.
 Endif.
 Modify itab.
 endloop.
*& END of ITAB
 CLEAR : DOC_CHNG.
 REFRESH LINES.
 IF NAST-NACHA eq '7'.
* Fill both the fax & email Receiver lists
 clear: reclist, reclist2.
 refresh: reclist, reclist2.
*& loop table itab to update receipient list in table Reclist
*& Nato
 loop at itab.
 IF not itab-q_typ is initial.
 concatenate itab-q_cty itab-q_fax into reclist2-RECNAM separated by space. "FAX NUMBER
 move itab-q_fax to reclist2-receiver. "FAX NUMBER
*&>>>>>>>>>>>>>>>>>>>new entry for testing nato 080206<<<<<<<<<<<&
 move itab-q_cty to RECLIST2-COUNTRY. "Country Code
 move itab-q_fax to Reclist2-FAX. "Fax number
*&>>>>>>>>>>>>>>ENd of entry<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<&
 move itab-q_typ to REClist2-REC_TYPE. "Communication type for fax
 move itab-q_EXPRESS to Express. "comment for testing
 move itab-q_com to REClist2-COM_TYPE.
 Move 'X' to reclist2-NOTIF_DEL.
 Move 'TELEFAX' to reclist2-SNDART. "TYPE OF DEVICE
 Move a_ebeln to sood-OBJDES. "new addition for testing nato
 append Reclist2.
 endif.
 IF not itab-q_typ2 is initial.
 move itab-q_mail to REclist-receiver. "SMT ADDRESS
 move itab-q_typ2 to REClist-REC_TYPE.
 move itab-q_EXPRESS to REClist-express.
 move 'X' to reclist-TO_ANSWER.
 Move a_ebeln to sood-OBJDES. "new addition for testing nato
 move itab-q_com to REClist-COM_TYPE. "comment for testing only
 append Reclist.
 Endif.
 move reclist-receiver to address.
 endLoop.
*& END OF RECipient
 ENDIF.
 DOC_CHNG-OBJ_DESCR = nast-objky.
ELSE.
 IF RECLIST IS INITIAL.
 LOOP AT reclist INTO RECIPIENT . " This logic might get commented or deleted. Nato 08/01/06
 ENDLOOP.
 ENDIF.
 DOC_CHNG-OBJ_DESCR = L_TITLE.
ENDIF.
IF RECLIST[] IS INITIAL.
 MESSAGE E573(VE) RAISING RECEIVER_NOT_FOUND.
ENDIF.
*& New entry to determine path according to communication
*& type
*& If comm type eq U follow convert_otf
*& then Read text, finaly send API
*& If comm type eq F follow path to "Convert OTF & FAX
*& Nato 080106
REFRESH : HOTFDATA, LT_SOLIX, OBJBIN.
LOOP AT JOB_OUTPUT_INFO-OTFDATA INTO HOTFDATA.
 APPEND HOTFDATA.
ENDLOOP.
*& Prepare content to be converted to PDF format
*& nato
CALL FUNCTION 'CONVERT_OTF'
 EXPORTING
 FORMAT = 'PDF'
 MAX_LINEWIDTH = 132
 IMPORTING
 BIN_FILESIZE = DOC_SIZE
 BIN_FILE = LD_BINFILE
 TABLES
 OTF = HOTFDATA
 LINES = HTLINE
 EXCEPTIONS
 ERR_MAX_LINEWIDTH = 1
 ERR_FORMAT = 2
 ERR_CONV_NOT_POSSIBLE = 3
 OTHERS = 4.
*& new entry just for test today 080306
*&nato
*endif.
*&--end of entry--
I = 0.
N = XSTRLEN( LD_BINFILE ).
WHILE I < N.
 LT_SOLIX-LINE = LD_BINFILE+I.
 APPEND LT_SOLIX.
 I = I + 255.
ENDWHILE.
*& end of convertion pdf
LOOP AT LT_SOLIX INTO WA_SOLIX.
 CLEAR WA_SOLI.
 ASSIGN WA_SOLI TO <PTR_HEX> CASTING.
 MOVE WA_SOLIX TO <PTR_HEX>.
 APPEND WA_SOLI TO OBJBIN.
ENDLOOP.
*& Prepare send mail
CLEAR : NAME, DOCNAME.
REFRESH : OBJTXT, OBJPACK.
CONCATENATE NAST-KAPPL NAST-KSCHL INTO NAME.
CONDENSE NAME.
IF NAST-NACHA NE '7'.
 CALL FUNCTION 'READ_TEXT'
 EXPORTING
CLIENT = SY-MANDT
 ID = 'STAM'
 LANGUAGE = SY-LANGU
 NAME = NAME
 OBJECT = 'OCS'
ARCHIVE_HANDLE = 0
LOCAL_CAT = ' '
IMPORTING
HEADER =
 TABLES
 LINES = LINES
 EXCEPTIONS
 ID = 1
 LANGUAGE = 2
 NAME = 3
 NOT_FOUND = 4
 OBJECT = 5
 REFERENCE_CHECK = 6
 WRONG_ACCESS_TO_ARCHIVE = 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.
ENDIF.
CONCATENATE NAST-OBJKY '.PDF' INTO DOCNAME .
CONDENSE DOCNAME.
*endif. "temp nato -080406
if reclist-rec_type eq 'U'.
 DOC_CHNG-OBJ_NAME = 'Delivery'.
 LOOP AT LINES.
 OBJTXT = LINES-TDLINE.
 APPEND OBJTXT.
 ENDLOOP.
 DESCRIBE TABLE OBJTXT LINES TAB_LINES.
 IF TAB_LINES > 0.
 READ TABLE OBJTXT INDEX TAB_LINES.
 DOC_CHNG-DOC_SIZE = ( TAB_LINES - 1 ) * 255 + STRLEN( OBJTXT ).
 ENDIF.
 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.
 DESCRIBE TABLE OBJBIN LINES TAB_LINES.
 OBJHEAD = DOCNAME.
 APPEND OBJHEAD.
 OBJPACK-TRANSF_BIN = 'X'.
 OBJPACK-HEAD_START = 1.
 OBJPACK-HEAD_NUM = 1.
 OBJPACK-BODY_START = 1.
 OBJPACK-BODY_NUM = TAB_LINES.
 OBJPACK-DOC_TYPE = 'PDF'.
 OBJPACK-OBJ_NAME = 'Delivery'.
OBJPACK-OBJ_DESCR = NAST-OBJKY.
 OBJPACK-OBJ_DESCR = A_EBELN.
 OBJPACK-DOC_SIZE = TAB_LINES * 255.
 APPEND OBJPACK.
 break nhernandez.
 CALL FUNCTION 'SO_NEW_DOCUMENT_ATT_SEND_API1'
 EXPORTING
 DOCUMENT_DATA = DOC_CHNG
 PUT_IN_OUTBOX = 'X'
COMMIT_WORK = ' '
IMPORTING
SENT_TO_ALL =
NEW_OBJECT_ID =
 TABLES
 PACKING_LIST = OBJPACK
 OBJECT_HEADER = OBJHEAD
 CONTENTS_BIN = OBJBIN
 CONTENTS_TXT = OBJTXT
CONTENTS_HEX =
OBJECT_PARA =
OBJECT_PARB =
 RECEIVERS = RECLIST
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 E081(ZGLO) WITH SY-SUBRC RAISING MAIL_SENDING_ERROR.
 ENDIF.
endif.
AM I missing something?

Hi Nat,
You can check this link which shows how to use the PRINT_TEXT for sending fax.
http://www.sap-img.com/abap/sending-fax-from-abap.htm
Also you can check these
Smartforms
Sending Smartforms through Fax
Sending SMARTFORM output to FAX gateway
How to fax a smartform?
/people/pavan.bayyapu/blog/2005/08/30/sending-html-email-from-sap-crmerp
ftp
Cheers
VJ

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.

Configuration to send the smartform through fax

Hi,
I have used CONVERT_OTF_AND_FAX and SO_OBJECT_SEND FM's to send the smartform through fax.After executing SO_OBJECT_SEND function module,I am getting sy-subrc alue as 9(OBJECT_NOT_SEND).I am able to send the document through fax.But when I click on display in SOST transaction it is just printing the output of the smartform.It is not coming in PDF format.
The code looks fine.I think there is some problem with confuration settings.Is there any configuration to be done to send the smartform output through fax?
Please reply.
Regards,
Hema

Hi,
Actually,my requirement is to send the smartform output through email with medium 'external send'.I have done some coding for that.it is working fine and I am able to send the smartform through email and open the attachment in PDF format.
But if the email id of the recipient is not present then the smartform output has to be sent through fax with the same medium 'external send'.
So I have done some coding to send the smartform through fax when the email id is not present.
I am able to send the output of smartform through fax.But when I clicked on display in SOST transaction,it is not coming in PDF format.It is coming in RAW format.
Is it possible to send the smartform output through fax with medium 'external send'?
Regards,
Hema

Error in sending smartform as fax

Hi everyone,
I am trying to send a smartform through Fax, and i am getting the following error;
Cannot process message in node, parameters cannot be converted
     Message no. XS821
Diagnosis
     The message cannot be processed in the node as parameters such as 'Send
     time' or 'Priority' cannot be converted. It is possible that entire
     parameters such as 'Recipient list' or 'Packet list' are missing.
System Response
     Processing was terminated.
     SAP system additional information (error number, if available):
     MRSUM
     Additional information of the node used (in the system language of the
     node)
Can you guys please help me solving this problem?
Thanking you,
Kind regards,
I have changed my code several times, using different functions to send the fax and i am getting the same error message each time.
Please find below the piece of code i am using to send the fax.
DATA:GT_MAIL_LINES TYPE STANDARD TABLE OF soli.
data: gs_mail_lines TYPE soli.
DATA: ls_object_hd TYPE sood1,
ls_receivers TYPE soos1,
lt_receivers TYPE STANDARD TABLE OF soos1,
l_lines TYPE i,
ls_sadrfd TYPE sadrfd.
CLEAR: ls_object_hd, ls_receivers.
REFRESH lt_receivers.
ls_object_hd-objla = sy-langu.
ls_object_hd-objnam = 'NOTE'.
ls_object_hd-objdes = 'Fax subject line in here'.
"Calculate size of table
DESCRIBE TABLE gt_mail_lines LINES l_lines.
READ TABLE gt_mail_lines INDEX l_lines INTO gs_mail_lines.
ls_object_hd-objlen = ( l_lines - 1 ) * 255 + STRLEN( gs_mail_lines ).
"Set Fax control structure
"Fax number in structure must have no leading zero
"as this is added by SAPOffice from the country code
ls_sadrfd-rec_fax = '4421844
ls_sadrfd-rec_street = 'Addr'.
ls_sadrfd-rec_town = 'Addr'.
ls_sadrfd-rec_name1 = 'Name'.
ls_sadrfd-rec_state = 'MU'.
ls_sadrfd-form_langu = 'EN'.
ls_sadrfd-fax_form = 'Z_FAX_COVER'.
ls_sadrfd-send_comp = 'USER'
ls_sadrfd-send_immi = 'X'.
ls_sadrfd-send_nam = sy-uname.
ls_sadrfd-send_date = sy-datum.
ls_sadrfd-send_time = sy-uzeit.
"Convert Receiver information to char field
CALL FUNCTION 'C147_WORKAREA_TO_CHARFIELD'
EXPORTING
I_WORKAREA = ls_sadrfd
IMPORTING
E_CHARFIELD = ls_receivers-recextnam.
ls_receivers-recesc = 'F'.
ls_receivers-mailstatus = 'E'.
ls_receivers-sndart = 'FAX'.
ls_receivers-sndpri = '1'.
APPEND ls_receivers TO lt_receivers.
"Send fax
CALL FUNCTION 'SO_OBJECT_SEND'
EXPORTING
object_hd_change = ls_object_hd
object_type = 'RAW'
owner = sy-uname
originator_type = 'B'
TABLES
objcont   = gt_mail_lines
receivers = lt_receivers
EXCEPTIONS
OTHERS = 01.
break buantoch.
"The function doesn't commit so we must
"do it if successful.
IF sy-subrc = 0.
COMMIT WORK AND WAIT.
ELSE.
WRITE: / 'Fax failed RAISE ERROR '(012).
ENDIF.

Hi,
Then, you can test the FAX fuctionality like:
go to System->Short Message->give a test message,give recipient as the FAX number,type as FAX->Shift+F8 the see if it works... else only SCOT errors will be there...
See:
http://help.sap.com/saphelp_nw2004s/helpdata/en/2b/d925bf4b8a11d1894c0000e8323c4f/frameset.htm
Also see:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/4b4fa090-0201-0010-d3b7-b233296d95ff
Regards,
Renjith Michael.

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.

Uncaught Exception occured while sending mail through abap code.

Hi,
Uncaught Exception occured while sending mail through abap code.Run time Errors "UNCAUGHT_EXCEPTION" occured after excuting the call method CALL METHOD SEND_REQUEST->SEND( ).kindly help in resolving the issue.

HI,
Runtime Error: UNCAUGHT_EXCEPTION details.
Runtime Errors         UNCAUGHT_EXCEPTION
Exception              CX_ADDRESS_BCS
Short text
     An exception occurred that was not caught.
What happened?
     The exception 'CX_ADDRESS_BCS' was raised, but it was not caught anywhere along
     the call hierarchy.
     Since exceptions represent error situations and this error was not
     adequately responded to, the running ABAP program 'SAPLZSEND_MAIL' has to be
     terminated.
Error analysis
    An exception occurred that is explained in detail below.
    The exception, which is assigned to class 'CX_ADDRESS_BCS', was not caught in
    procedure "SEND_MAIL" "(FORM)", nor was it propagated by a RAISING clause.
    Since the caller of the procedure could not have anticipated that the
    exception would occur, the current program is terminated.
    The reason for the exception is:
    An exception occurred
How to correct the error
    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:
    "UNCAUGHT_EXCEPTION" "CX_ADDRESS_BCS"
    "SAPLZSEND_MAIL" or "LZSEND_MAILU01"
    "ZSEND_EMAIL"
    If you cannot solve the problem yourself and want to send an error
    notification to SAP, include the following information:
    1. The description of the current problem (short dump)
       To save the description, choose "System->List->Save->Local File
    (Unconverted)".
    2. Corresponding system log
       Display the system log by calling transaction SM21.
       Restrict the time interval to 10 minutes before and five minutes
    after the short dump. Then choose "System->List->Save->Local File
    (Unconverted)".
    3. If the problem occurs in a problem of your own or a modified SAP
    program: The source code of the program
       In the editor, choose "Utilities->More
    Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
The exception must either be prevented, caught within proedure
"SEND_MAIL" "(FORM)", or its possible occurrence must be declared in the
RAISING clause of the procedure.
Please help me to resolve this issue.

Problem in sending mail through dynamics actions

Hi Friends,
I have a problem in sending mail through dynamics actions . In this we pass a subroutine in dynamics actions which send an mail when promotion action occured.
Problem is that sometimes it will send an mail or sometimes not. I have no idea to solve this problem.
Can anyone suggest me .
Thanks ,
Anish
Moderator message : Duplicate post locked.
Edited by: Vinod Kumar on Sep 5, 2011 9:45 AM

Hi,
Check that all the bindings have been done in proper way as it is configured.. Try to do the binding manualy..This could also be the problem..
thank You

Problem while sending mail inOIM 11g r2 after usercreation

Hi,
By default OIM sends mail to user mail id when the user created. i have tested this scenario using test mail server, it is working fine . when i am trying this scenario using exchange mail server, it is throwing errors. for Exchange just i have changed IT resource parameters.
Authentication true
Server Name ip address of the Exchange server
User Login [email protected]
User Password *************
is there anything missing. for SMTP server is ums nedded ?.
<Oct 1, 2012 7:07:51 AM EDT> <Error> <oracle.iam.notification.impl> <BEA-000000> <Provider UMSEmailServiceProvider has encountered exception : javax.xml.soap.SOAPException: javax.xml.soap.SOAPException: Message send failed: Connection refused>
<Oct 1, 2012 7:07:51 AM EDT> <Error> <oracle.iam.notification.impl> <BEA-000000> <Sending notification with Provider UMSEmailServiceProvider has encountered exception : Error occured while Sending Notification through Provider UMSEmailServiceProvider : javax.xml.soap.SOAPException: javax.xml.soap.SOAPException: Message send failed: Connection refused>
<Oct 1, 2012 7:07:51 AM EDT> <Error> <oracle.iam.notification.impl> <BEA-000000> <Sending notification with Provider UMSEmailServiceProvider detailed exception : javax.xml.soap.SOAPException: javax.xml.soap.SOAPException: Message send failed: Connection refused>
<Oct 1, 2012 7:07:52 AM EDT> <Error> <oracle.iam.notification.provider> <BEA-000000> <300>
<Oct 1, 2012 7:07:52 AM EDT> <Error> <oracle.iam.notification.impl> <BEA-000000> <Provider SOAEmailServiceProvider has encountered exception : java.lang.IllegalArgumentException: 300>
<Oct 1, 2012 7:07:52 AM EDT> <Error> <oracle.iam.notification.impl> <BEA-000000> <Sending notification with Provider SOAEmailServiceProvider has encountered exception : Error occured while Sending Notification through Provider SOAEmailServiceProvider : java.lang.IllegalArgumentException: 300>
<Oct 1, 2012 7:07:52 AM EDT> <Error> <oracle.iam.notification.impl> <BEA-000000> <Sending notification with Provider SOAEmailServiceProvider detailed exception : java.lang.IllegalArgumentException: 300>
<Oct 1, 2012 7:07:52 AM EDT> <Error> <oracle.iam.notification.impl> <BEA-000000> <Provider EmailServiceProvider has encountered exception : null>
Thanks,

Given below steps in oracle doc for UMS configuration. you can try the same
Configuring UMS Provider for Sending Notifications (Optional)
To configure Unified Messaging Service (UMS) provider for sending notifications:
Edit the oim-config.xml file by using MBeans. To do so:
Log in to Oracle Enterprise Manager.
Navigate to Identity and Access, oim.
Right-click oim(11.1.1.x.x), and select System MBean Browser.
In the System MBean Browser, navigate to Application Defined MBeans, oracle.iam, Server: oim_server1, Application:oim, XMLConfig, Config, XMLConfig.NotificationConfig, EmailProvider.
Click the EmailProvider attribute, and replace the value oracle.iam.notification.provider.EmailServiceProvider with oracle.iam.notification.provider.UMSEmailServiceProvider.
Click Apply.
Configure the Email Provider Instance - UMS IT resource with the UMS Web service details. To do so:
Login to Oracle Identity Manager Administrative and User Console, and navigate to Advanced Administration.
Click the Configuration tab, click Resource Management, and then click Manage IT Resource.
Click Search. The list of IT resources is displayed.
For the Email Provider Instance - UMS IT resource, click the Edit icon. The Edit IT Resource Details and Parameters page is displayed.
Specify values in the following fields:
Web service URL: The URL of the UMS web service to be invoked. For example, http://<SOA_host>:<SOA_Port>/ucs/messaging/webservice.
Policies: The OWSM policy attached to the given web service. Leave this field as blank.
Username: The username provided in the security header. If no policy is attached, then leave this field as blank.
Password: The password provided in the security header. If no policy is attached, then leave this field as blank.
Click Apply, and then close the popup window.
Configure UMS Server for using a mail server other than the local LINUX mail server, which is picked by default. For example, to setup the mail server to use stbeehive email server:
Stop the Linux Local sendmail email server running on the host, if this is a LINUX host, by running the following command:
/usr/local/redhat/packages/aime/ias/run_as_root "/sbin/service sendmail stop"
Configure Mail Server information in UMS Email Driver. To do so:
i. Login to Oracle Enterprise Manager.
ii. Expand User Messaging Service, and select usermessagingdriver-email (soa_server1).
iii. From the Driver-Specific Configuration list, select Email Driver Properties.
iv. Configure the following mandatory fields:
OutgoingMailServer: The name of the SMTP server, for example, mailserver.mycompany.com.
OutgoingMailServerPort: The port number of the SMTP server, for example, 465.
OutgoingMailServerSecurity: The security setting used by the SMTP server. Possible values can be None, TLS, or SSL.
OutgoingUsername: Any valid username similar to your mail client configuration, such as in the [email protected].
OutgoingPassword: The password used for SMTP authentication. This consists of the following fields:
Type of Password: Select Indirect Password, Create New User.
Indirect Username/Key: Enter a unique string, for example, OIMEmailConfig. This masks the password and does not expose it in clear text in the configuration file.
Password: Enter a valid password for this account.
v. Click Apply.
Right-click usermessagingdriver-email (soa_server1), and select Control, Shutdown.
Allow at least 2 minutes to pass, after which you can restart the email driver. To so so, right-click usermessagingdriver-email (soa_server1), and select Control, Restart.

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 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 Smartform through Fax

Similar Messages

Maybe you are looking for