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.

Similar Messages

Problem while sending fax through a SAP Smart Form

Hi,
I am trying to send fax through a smartform but it is not working, please see the details below.
I am calling the Function Module "SSF_FUNCTION_MODULE_NAME" in a PAI event. After storing the FM name "/1BCDWB/SF00000029"in a local variable "ls_frm_name", I am using that for printing the Form and at the same time to fax out the same by passing the following export parameters.
control_parameters type ssfctrlop with values
la_ssfctrlop_struc-device      = 'TELEFAX'.
la_ssfctrlop_struc-no_dialog   = 'X'.
la_ssfctrlop_struc-langu       = ls_supplier_info-spras.
output_options type ssfcompop with values
ls_ssffaxop_struc-tdteleland   = ls_supplier_info-land1.
ls_ssffaxop_struc-tdtelenum    = lfa1-telfx.
ls_ssffaxop_struc-tdfaxuser    = syst-uname.
ls_ssffaxop_struc-tdnoprint    = 'X'.
along with "fax_details = ls_zap1_fax_details" declared as interface parameters to the Smart Form.
But the Function Module is throwing following exception and not sending any Fax.
SY-MSGID-->OL
SY-MSGNO-->356
SY-MSGV1-->NOAUTHORITYCHECK
Do I need to pass any other values to the FM, I felt that this is not an authorization problem after debugging.
Can any one please help me in handling this exception and send the fax,
Thanks,
Srinivas.
Edited by: Venkata Srinivas Inavilli on May 20, 2008 2:40 PM

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 FAX (Error Message 802 if checked in SOST)

Hi all,
I'm using FM SO_NEW_DOCUMENT_SEND_API1 to send Email and Fax through ABAP prog.
The Email is going fine but there is a problem in sending Fax, when i chek in SOST i get the following message.
Msg No 802 No delivery to 0091802299922, as recipient unknown.
This is my Fax No. +91 91-80-2299922
My selection screen is as follows
Email ID : External Email id
Fax No: 802299922 ( Passing Fax No in this format )
Country IND
The following is the code of my program, please show up some light on any mistake made in the same.
*& This is my Source Code
report z_email.
tables : somlreci1.
data : e_document_data like sodocchgi1,
e_document_type like soodk-objtp value 'RAW',
e_put_in_outbox like sonv-flag value 'X',
e_commit_work like sonv-flag value 'X'.
data : it_object_header type table of solisti1 with header line,
it_object_content type table of solisti1 with header line,
receivers type table of somlreci1 with header line.
data : i_lines type i.
select-options : s_mailid for somlreci1-receiver no intervals.
parameters : p_faxno type somlreci1-fax,
p_contry type somlreci1-country.
start-of-selection.
e_document_data-obj_name = 'Test'.
e_document_data-obj_descr = 'Email Test'.
e_document_data-obj_langu = sy-langu.
e_document_data-proc_type = '1'.
*--Information
it_object_content-line = 'This is a report used to send starts and'.
append it_object_content.
clear it_object_content.
it_object_content-line = ' stops to foreign distri. via E-Mail or Fax'.
append it_object_content.
clear it_object_content.
*--For Doc Size
describe table it_object_content lines i_lines.
e_document_data-doc_size = ( i_lines - 1 ) * 255 +
strlen( it_object_content ).
*--Email ID
loop at s_mailid.
receivers-receiver = s_mailid-low.
receivers-rec_type = 'U'.
append receivers.
clear : receivers.
endloop.
*--Fax
if p_faxno is not initial.
receivers-rec_type = 'F'.
receivers-fax = p_faxno.
receivers-country = p_contry.
receivers-com_type = 'TELFAX'.
append receivers.
clear : receivers.
endif.
*--Call function module
call function 'SO_NEW_DOCUMENT_SEND_API1'
exporting
document_data = e_document_data
document_type = e_document_type
put_in_outbox = e_put_in_outbox
commit_work = e_commit_work
IMPORTING
SENT_TO_ALL =
NEW_OBJECT_ID =
tables
OBJECT_HEADER =
object_content = it_object_content
CONTENTS_HEX =
OBJECT_PARA =
OBJECT_PARB =
receivers = receivers
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.
commit work.
wait up to 2 seconds.
submit rsconn01 with mode = 'INT'
with output = 'X'
and return.
write :/ 'Message sent successfully..!'.
endif.
Regards,
Balavardhan.K

Hi ,
I am facing similar problem , in case you have a resolution about the FAX number , then please let me know .
Thanks,
Abhishek
([email protected])

Line Alignment Problem while sending Fax from SAP Script

Moderator message: please do not post the same question in different forums
Hi Experts,
While sending fax the horizontal lines are not displaying till the end of the page.
But in the print preview the lines are displying till the end.
If this is printed using local printer the lines are printing fine but the problem is with the fax.
Please provide me a solution for this.
Regards,
Rajesh.
Edited by: Matt on Nov 25, 2008 2:51 PM

Puzzling.
I've seen where the printed output doesn't match the print preview but not a fax not matching a print.
Do you use SAPConnect or the older SAPComm method for faxing?
How do you produce the horizontal lines? BOX commands, ULINE, '-', etc.?

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 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.

"Let others send fax through this computer" - problem: modem not showing up

I have a macbook that does not have an internal modem for faxing. I am using another networked mac in our office that has an internal modem for faxing. I have set up the printing and fax preferences to "let others send faxes through this computer" on the mac that can fax. It has worked in the past, but this morning when I went to fax from my macbook, I cannot see the modem in the mac that can fax. I have also checked with other macs in the office and they can't see it either. Network is okay, I can access the computer through connect to server, I have repaired permissions, restarted and still no modem showing up or shared printers showing up. I have not updated anything on the mac that can fax. Any ideas?

http://docs.info.apple.com/article.html?path=Mac/10.4/en/mh1801.html
Strange, not sure why it's not showing up.
Have you confirmed that the fax printer is working on the host Mac? Maybe try turning off the sharing and deleting the existing Fax Printer in the Fax List with /Applications/Utilities/Printer Setup Utility, and creating the Fax Printer again, and turn on sharing again.

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 unicode (utf-8) xml to IE.

Hi,
I have encoding problem while sending utf-8 xml from servlet to IE (Client), where i am parsing the xml using Ajax.
In the log I can see proper special characters that are being sent from the servlet. but when same is seen in the client end,, it is showing ? symbols instead of special charcters.
This is the code that sends the xml from servlet.
ByteArrayOutputStream stream = new ByteArrayOutputStream(2000);
transformer.transform(new DOMSource(document), new StreamResult(new OutputStreamWriter(stream, "iso-8859-1")));
_response.setContentType("text/xml; charset=UTF-8");
_response.setHeader("Cache-Control", "no-cache");
_response.getWriter().println(new String(stream.toByteArray(), "UTF-8"));
In the log i can see :
<response status="success" value="1154081722531" hasNextPage="false" hasPreviousPage="false" ><row row_id="PARTY_test_asdasd" column_0="PARTY_test_asdasd" column_1="asdasd �" mode="edit" column_en_US="asdasd �" column_de_DE="? xyz" column_fr_FR="" ></row></response>
But in the Client side I am able to see
<?xml version = '1.0' encoding = 'UTF-8'?>
<response status="success" value="1154082795061" hasNextPage="false" hasPreviousPage="false"><row row_id="PARTY_test_asdasd" column_0="PARTY_test_asdasd" column_1="asdasd ?" mode="edit" column_en_US="asdasd ?" column_de_DE="? xyz" column_fr_FR=""/></response>
I am getting ? instead of �.
It will be greatful if somebody tell how to send utf xml from servlet, for ajax purpose.
Thanks,
Siva1

This is the code that sends the xml from servlet.
ByteArrayOutputStream stream = new
ByteArrayOutputStream(2000);
transformer.transform(new DOMSource(document), new
StreamResult(new OutputStreamWriter(stream,
"iso-8859-1")));Here you produce XML that's encoded in ISO-8859-1. (!!!)
_response.setContentType("text/xml; charset=UTF-8");Here you tell the browser that it's encoded in UTF-8.
_response.getWriter().println(new String(stream.toByteArray(), "UTF-8"));Here you convert the XML to a String, assuming that it was encoded in UTF-8, which it wasn't.
Besides shooting yourself in the foot by choosing ISO-8859-1 for no good reason, you're also doing a lot of translating from bytes to chars and back again. Not only is that a waste of time, it introduces errors if you don't do it right. Try this instead:_response.setContentType("text/xml; charset=UTF-8");
_response.setHeader("Cache-Control", "no-cache");
_transformer.transform(new DOMSource(document_),
new StreamResult(_response.getOutputStream()));

Send faxes through F110 and Interest Indicator

Hello all,
we have SAP ECC 6.0. , and it is needed to send faxes through F110 ,
1) I would like to know the steps to send a fax through the f110 transaction
2) Only send faxes for the vendors with interest indicator
3) Do you know some user exit to calculate interest with different interest indicators?
Regards
Olga

Hi Olga,
For customers, to use different interest rates, and calculate the interest amount in the payment file created by transaction F110, program RFFOBR_A, you need to:
1) Go to "Define Interest Calculation Types", in customizing (SPRO).
2) Go to "Define Reference Interest Rates" in customizing (SPRO).
3) Go to "Define Time-Based Terms" in customizing (SPRO).
4) Go to Enter Interest Values in customizing (SPRO).
After, go to the customer master data, Company Code data, folder account management and fill the field "Interest Indicato" with the code created in the step 1 above.
When you run the proposal, the payment file will have the interest amount calculated considering the billing amount and the interest rate defined to the customer.
Her in Brazil, we work in this way.....
I hope that this could help you solve your issue....!!!!
Best Regards,
Francisco Moya

Problem while sending FAX through PRINT_TEXT FM

Similar Messages

Maybe you are looking for