Problem in sending a file

Hello..
i have a problem in sending a file with sender file adapter...
In adapter monitor it gives error like...
Last message processing started 15:58:36 2005-10-04, Error: Conversion of complete file content of 'fileinput.csv' to XML format failed around position 0 with java.lang.Exception: ERROR converting document line no. 3 according to structure 'substr':java.lang.Exception: Consistency error: field(s) missing - specify 'lastFieldsOptional' parameter to allow this
last retry interval started 15:58:36 2005-10-04
length 60,000 secs.
Let me know what might be the problem.
Thanks,
Padma

thanks for the reply and answering my question..
I'm getting the error in SXMB_moni...while i'm sending the file from FTP to lagacy system.
The error is in call adapter...at says like ....
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIProtocol</SAP:Category>
<SAP:Code area="MESSAGE">NOT_AUTHORIZED_FOR_PROC</SAP:Code>
<SAP:P1>XXXX</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>User XXXXXX has no authorization to process messages</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Can tell me what might be the wrong here..
Thanks.

Similar Messages

I have to send large files like 5MB or biger via mobile phone, but in that cases phone is telling mi to plug in power. And when I do that, there is no problem to send the file. For smaller files there is no problem. How can I solve the problem? Because wh

I have to send large files like 5MB or biger via mobile phone, but in that cases phone is telling mi to plug in power. And when I do that, there is no problem to send the file. For smaller files there is no problem. How can I solve the problem? Because when I'm not at home I can't plug in the power.

hi,
I am sending file from server to client i.e client will request for a file and service will send it back....... no socket connection is there...I am using JBOSS and apache axis.
pls help me out.....
Rashi

Problem to send PDF file

Hello,
I try to send pdf file as attachments file to mail with XI.
I use with this blog
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/6d967fbc-0a01-0010-4fb4-91c6d38c5816
My problems is:
1. to all mails that I send have another e file Untiteld.doc, how I can avoid this file?
2. When I received the pdf file I not succeed to open it I received the message:
Adobe reader could not open 'elad.pdf' because it is either not supported
File type or because the file has been damaged (for example, it was sent as an
Email attachment and wasn't correctly decoded)
Regards
Elad Peleg

hi
ref this
Receiver Mail Adapter message with PDF attachment
PDF attachment in mail adapter
File adapter with attachment to mail
File with attachment to mail scenario
File To Mail Scenario With An Attachment

Problem to send text file to mail from ALV report

Hi Friends,
I have a problem in my ALV report with text file. As per the requirment, when we execute the program then text attachment should go to the particual email.
When i am using file type as XLS i am getting attachment with all 4 recoreds( input for 4 records) in mail. But all 4 records are coming in SAME ROW. It should come 4 records in 4 rows. when I use file type as TXT and separated by pipe symble in code, it is showing only one recored for same above input.
When i use file type as XLS and click the attachment in email, it will triggire one popul with three options like SAVE, OPEN, CANCEL.
But when i click on text file attachment, it is directly showing ony one recored.
Please correct me on this.
my code is
PERFORM send_file_as_email_attachment
                               tables i_message
                                      i_attach
                                using v_email
                                      'User last log on details'
                                      'XLS'
                                      'User log on list'
                             changing v_error
                                      v_reciever.
FORM send_file_as_email_attachment tables pi_message
                                          pi_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: l_error    TYPE sy-subrc,
          l_reciever TYPE sy-subrc,
          l_mtitle LIKE sodocchgi1-obj_descr,
          l_email LIKE somlreci1-receiver,
          l_format TYPE so_obj_tp ,
          l_attdescription TYPE so_obj_nam ,
          l_attfilename TYPE so_obj_des ,
          l_sender_address LIKE soextreci1-receiver,
          l_sender_address_type LIKE soextreci1-adr_typ,
          l_receiver LIKE sy-subrc.
l_email   = p_email.
l_mtitle = p_mtitle.
l_format              = p_format.
l_attdescription      = p_attdescription.
l_attfilename         = p_filename.
l_sender_address      = p_sender_address.
l_sender_address_type = p_sender_addres_type.
Fill the document data.
v_doc_data-doc_size = 1.
Populate the subject/generic message attributes
v_doc_data-obj_langu = sy-langu.
v_doc_data-obj_name = 'SAPRPT'.
v_doc_data-obj_descr = l_mtitle .
v_doc_data-sensitivty = 'F'.
Fill the document data and get size of attachment
CLEAR v_doc_data.
READ TABLE i_attach INDEX v_cnt.
v_doc_data-doc_size =
     ( v_cnt - 1 ) * 255 + STRLEN( i_attach ).
v_doc_data-obj_langu = sy-langu.
v_doc_data-obj_name   = 'SAPRPT'.
v_doc_data-obj_descr = l_mtitle.
v_doc_data-sensitivty = 'F'.
CLEAR i_attachment.
REFRESH i_attachment.
i_attachment[] = pi_attach[].
Describe the body of the message
CLEAR i_packing_list.
REFRESH i_packing_list.
i_packing_list-transf_bin = space.
i_packing_list-head_start = 1.
i_packing_list-head_num = 0.
i_packing_list-body_start = 1.
DESCRIBE TABLE i_message LINES i_packing_list-body_num.
i_packing_list-doc_type = 'RAW'.
APPEND i_packing_list.
Create attachment notification
i_packing_list-transf_bin = 'X'.
i_packing_list-head_start = 1.
i_packing_list-head_num   = 1.
i_packing_list-body_start = 1.
DESCRIBE TABLE i_attachment LINES i_packing_list-body_num.
i_packing_list-doc_type   = l_format.
i_packing_list-obj_descr = l_attdescription.
i_packing_list-obj_name   = l_attfilename.
i_packing_list-doc_size   = i_packing_list-body_num * 255.
APPEND i_packing_list.
Add the recipients email address
CLEAR i_receivers.
REFRESH i_receivers.
i_receivers-receiver = l_email.
i_receivers-rec_type = 'U'.
i_receivers-com_type = 'INT'.
i_receivers-notif_del = 'X'.
i_receivers-notif_ndel = 'X'.
APPEND i_receivers.
CALL FUNCTION 'SO_DOCUMENT_SEND_API1'
       EXPORTING
            document_data              = v_doc_data
            put_in_outbox              = 'X'
            sender_address             = l_sender_address
            sender_address_type        = l_sender_address_type
            commit_work                = 'X'
       IMPORTING
            sent_to_all                = v_sent_all
       TABLES
            packing_list               = i_packing_list
            contents_bin               = i_attachment[]
            contents_txt               = i_message
            receivers                  = i_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.
Populate zerror return code
l_error = sy-subrc.

Hi,
declare the following constant in u r program and concatenate at the end of each and every record in your internal table.
CONSTANTS : LV_CRLF TYPE C VALUE CL_ABAP_CHAR_UTILITIES=>CR_LF.
for eg.
if u internal table has values like
row1
row2
row3
concatenate the 1st record lv_crlf into first record.
conactenate second record lv_crlf into second record.
concatenate third record lv_crlf into third record.
now attach the internal table to the FM which u use for sending email. Each and every row will come in new line. The LV_CRLF will hold nothing but a line feed character (#).
Hope it will solve u r problem
Regards,
Rose.

Problem with Sender Adapter File Content Conversion

Hi all!
I have a question about file content conversion in sender file adapter.
I have file like:
{field1
field2
field3
field4
$
{field5
field6
field7
field8
And i need to get file like:
<dealings>
<deal>
<field1>{field1</field1>
<field2>field2</field2>
<field3>field3</field3>
<field4>field4</field4>
<field5>-}*</field5>
</deal>
<deal>
<field1>{field5</field1>
<field2>field6</field2>
<field3>field7</field3>
<field4>field8</field4>
<field5>-}*</field5>
</deal>
</dealings>
I put content conversion parameters:
deal.fieldSeparator = $
deal.fieldNames = field1,field2,field3,field4,field5
And i get a file like:
<ns:mt_swift_file>
<dealings>
<deal>
<field1>{field1</field1>
</deal>
<deal>
<field1>field2</field1>
</deal>
<deal>
<field1>field3</field1>
</deal>
<deal>
<field1>field4</field1>
</deal>
<deal>
<field1>-}*</field1>
</deal>
<deal>
<field1/>
</deal>
<deal>
<field1>{field5</field1>
</deal>
<deal>
<field1>field6</field1>
</deal>
<deal>
<field1>field7</field1>
</deal>
<deal>
<field1>field8</field1>
</deal>
<deal>
<field1>-}*</field1>
</deal>
</dealings>
</ns:mt_swift_file>
What i do wrong?
As i understand, XI put string to a separate tag after symbol 'nl', but how can i get structure without unnecessary tags?

Hi,
Check some links for FCC
Introduction to simple(File-XI-File)scenario and complete walk through for starters(Part1)
Introduction to simple (File-XI-File)scenario and complete walk through for starters(Part2)
File Receiver with Content Conversion
Content Conversion (Pattern/Random content in input file)
NAB the TAB (File Adapter)
Introduction to simple(File-XI-File)scenario and complete walk through for starters(Part1)
Introduction to simple (File-XI-File)scenario and complete walk through for starters(Part2)
How to send a flat file with various field lengths and variable substructures to XI 3.0
Content Conversion (Pattern/Random content in input file)
NAB the TAB (File Adapter)
File Content Conversion for Unequal Number of Columns
Content Conversion ( The Key Field Problem )
The specified item was not found.
File Receiver with Content Conversion
http://help.sap.com/saphelp_nw04/helpdata/en/d2/bab440c97f3716e10000000a155106/content.htm
Regards,
Phani

Problem while sending a FILE?

Here is my scenario: FILE->XI->RFC
My settings:
SENDER
sender business service name: FILE_SEND
sender outbound interface: MAT_OB_ASYNC_MI
communication channel: FILE
RECEIVER
receiver business service name: RFC
receiver inbound interface: MAT_IB_ASYNC_MI
communication channel: RFC
RECEIVER DETERMINATION
sender: service - FILE_SEND, interface - MAT_OB_ASYNC_MI
receiver: service - RFC
INTERFACE DETERMINATION
sender: serive - FILE_SEND, interface - MAT_OB_ASYNC_MI
receiver: service - RFC
configured inbound interface - MAT_IB_ASYNC_MI
interface mapping - MAT_IM
SENDER AGREEMENT
sender: service - FILE_SEND, interface - MAT_OB_ASYNC_MI
sender communication channel - FILE
RECEIVER AGREEMENT
sender: service - FILE_SEND
receiver: service - RFC, interface - MAT_IB_ASYNC_MI
receiver communication channel - RFC
File adapter settings:
adapter type - file (sender)
transport protocol - File system(FNS)
adapter engine - integraion server
source directory - E:
file name - text_xi_input.dat
Qos - EO
Poll interval(secs) - 60
processing mode - archive
add time stap - yes
archive directory - E:\temp
processing sequence - By name
file type - text
adapter status - active
Sender outbound interface(MAT_OB_ASYNC_MI) settings:
category - outbound
mode - async
output message type - M_MATERIAL
message type(M_MATERIAL) structure settings:
data type used - D_MATERIAL
structure - M_MATERIAL,category - element,type-D_MATERIAL
MATERIAL,category - element,type - xsd:string
Receiver inbound interface(MAT_IB_ASYNC_MI) settings:
category - inbound
mode - async
input message type - ZMAT (this is imported from RFC)
message type(ZMAT) structure settings:
structure - ZMAT,category - element,type-D_MATERIAL
MATERIAL,category - element,type - xsd:string
message mapping(MAT_MM) settings:
source message type - M_MATERIAL
target message type - ZMAT
(just only one element MATERIAL exist for mapping)
The text file(text_xi_input.dat)content:
(this has only one line of material number)
TEST_MATERIAL1
After I activated all, I don't see any message comming across. I'm not sure what I'm missing?
I appreciate your response.
Regards
felix.

Hi felix,
From the log you have posted, i could find that, the pipeline URL http://xxx:port/sap/xi/engine/entry?action=execute is wrong. It should have been
http://<hostname>:<port>/sap/xi/engine?type=entry
Try changing this parameter in Integration server-> sxmb_adm-->Global Configuration data.
Also check in SLD>Business Landscape>( your XI System)-->pipeline URL
Hope this solves your problem.
Cheers,
Siva Maranani.
Message was edited by: siva maranani

Problem in sending .doc file as an attachment.!

Hi SDN,
I am using FM 'SO_NEW_DOCUMENT_ATT_SEND_API1' to send a .doc file as an attachment i am filling the the table contents_hex with my internal table containing the data in hex format but the attachment coming to the SAP office inbox is not showing the actual data it's showing the file with all hex values.
can any one tell the reason?
Please give sample code if possible for sending a word file as an attachment..
Regards,
Rahul

Hi Rahul,
I am sending you the sample code I have written for TXT.
you can use the same code for .doc with small modification.
You use this code and check once and let me know.
Sample code:
Declaration:
DATA : w_name TYPE sos04-l_adr_name.
DATA: sent_to_all LIKE sonv-flag.
DATA:
l_datum(10),
ls_docdata TYPE sodocchgi1,
lt_objpack TYPE TABLE OF sopcklsti1 WITH HEADER LINE,
lt_objhead TYPE TABLE OF solisti1 WITH HEADER LINE,
lt_objtxt TYPE TABLE OF solisti1 WITH HEADER LINE,
lt_objbin TYPE TABLE OF solisti1 WITH HEADER LINE,
lt_reclist TYPE TABLE OF somlreci1 WITH HEADER LINE,
lt_listobject TYPE TABLE OF abaplist WITH HEADER LINE,
l_tab_lines TYPE i,
l_tab_lines1 TYPE i,
l_tab_lines2 TYPE i,
l_att_type LIKE soodk-objtp.
CONSTANTS : c_tab TYPE x VALUE '09'.     "tab delimiter between records.
CONSTANTS : c_line(2) TYPE x VALUE '0D'.
CONSTANTS : l_newline(2) TYPE x VALUE '0D0A'.        "To insert Newline.
DATA: v_str LIKE lt_objbin.
*Program logic
Main Text
lt_objtxt = 'Dummy heading. ' .
    APPEND lt_objtxt.
    lt_objtxt = '' .
    APPEND lt_objtxt.
lt_objtxt = 'Dummy second line.'.
    APPEND lt_objtxt.
    lt_objtxt = '' .
    APPEND lt_objtxt.
    lt_objtxt = 'Regards,'.
     APPEND lt_objtxt.
    lt_objtxt = 'Field Service Team' .
    APPEND lt_objtxt.
    lt_objtxt = '----
    APPEND lt_objtxt.
lt_objtxt = 'This is system-generated email;please do not reply to this
message.' .
    APPEND lt_objtxt.
lt_objtxt = 'If there are any questions regarding this error message'.
    APPEND lt_objtxt.
lt_objtxt = '----
    APPEND lt_objtxt.
Write Packing List (Main)
    DESCRIBE TABLE lt_objtxt LINES l_tab_lines.
    READ TABLE lt_objtxt INDEX l_tab_lines.
ls_docdata-doc_size = ( l_tab_lines - 1 ) * 255 + STRLEN( lt_objtxt ).
    CLEAR lt_objpack-transf_bin.
    lt_objpack-head_start = 1.
    lt_objpack-head_num = 0.
    lt_objpack-body_start = 1.
    lt_objpack-body_num = l_tab_lines.
    lt_objpack-doc_type = 'RAW'.
    APPEND lt_objpack.
Create Message Attachment   "Attachmant of file
    LOOP AT itab1.
      CONCATENATE itab1-bldat itab1-blart itab1-bukrs itab1-budat
                  itab1-monat itab1-waers itab1-xblnr itab1-bktxt
                   INTO lt_objbin SEPARATED BY c_tab .
      CONCATENATE l_newline lt_objbin INTO lt_objbin.
      APPEND lt_objbin.
      CLEAR lt_objbin.
    ENDLOOP.
Write Packing List (Attachment)
    l_att_type = 'txt'.
    DESCRIBE TABLE lt_objbin LINES l_tab_lines.
    READ TABLE lt_objbin INDEX l_tab_lines.
    lt_objpack-doc_size = ( l_tab_lines - 1 ) * 255
                                    + STRLEN( lt_objbin ).
    lt_objpack-transf_bin = 'X'.
    lt_objpack-head_start = 1.
    lt_objpack-head_num = 0.
    lt_objpack-body_start = 1.
    lt_objpack-body_num = l_tab_lines.
    lt_objpack-doc_type = l_att_type.
    lt_objpack-obj_name = 'Header file name'.
    lt_objpack-obj_descr = 'Header file name'.
    APPEND lt_objpack.
*refresh bdclm.     "Attachemnt of second file
   CLEAR lt_objbin.
    LOOP AT bdclm.
      CONCATENATE itab2-indate itab2-intime itab2-tcode
                  itab2-longtext
                  INTO lt_objbin SEPARATED BY c_tab.
      CONCATENATE l_newline lt_objbin INTO lt_objbin.
      APPEND lt_objbin.
      CLEAR lt_objbin.
    ENDLOOP.
    CLEAR lt_objbin.
Write Packing List (Attachment)
    l_att_type = 'txt'.
    DESCRIBE TABLE lt_objbin LINES l_tab_lines1.
    l_tab_lines2 = l_tab_lines1 - l_tab_lines.
    READ TABLE lt_objbin INDEX l_tab_lines2.
lt_objpack-doc_size = ( l_tab_lines2 - 1 ) * 255 + STRLEN( lt_objbin ).
    lt_objpack-transf_bin = 'X'.
    lt_objpack-head_start = l_tab_lines2.
    lt_objpack-head_num = 0.
    lt_objpack-body_start = l_tab_lines + 1.
    lt_objpack-body_num = l_tab_lines2.
    lt_objpack-doc_type = l_att_type.
    lt_objpack-obj_name = 'file name '.
    lt_objpack-obj_descr = 'file name '.
    APPEND lt_objpack.
Create receiver list
    lt_reclist-receiver = '[email protected]'.
    lt_reclist-rec_type = 'U'.
    APPEND lt_reclist.
Send Message
    CALL FUNCTION 'SO_NEW_DOCUMENT_ATT_SEND_API1'
         EXPORTING
            document_data = ls_docdata
            put_in_outbox = 'X'
             commit_work = 'X '
*put_in_outbox = ''
        IMPORTING
            sent_to_all = sent_to_all
VALUE(NEW_OBJECT_ID) LIKE SOFOLENTI1-OBJECT_ID
         TABLES
             packing_list = lt_objpack
             object_header = lt_objhead
             contents_bin = lt_objbin
             contents_txt = lt_objtxt
             receivers = lt_reclist
*COMMIT_WORK = X
         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.
Thanks,
Yuvaraj

Problem in sending the file as an attachment through mail

Hi,
I have developed a Zreport. The functionality is like on executing this report it should send an e-mail with an attachment of the data in the xcel format.
So, while execting this report in background mode in ECC 5.0, it is able to send the mail as an attachment but the file doesn't contain the data in it But, the same report while trying to execute in back ground mode in ECC 6.0, it is able to send the mail with the attachment and the file also has the data.
So, my question is like are there any patches that has to be installed in ECC 5.0 system to get this successfully done.
Thanks in advance for your answers.
Rohith

Hello,
Are you using the standad sap function module or using OLE objects to generate excel?
First try creating the excel file in foreground and see if the data is being populated.
Kind Regards,
Niky.

How to send a file through the portal

Hello,
I have a problem in sending the file. I have selected a file kris.ppt and from context menu, I have selected sent to option and I have sent a file. I got a copy of that to my lotus notes but in that I had a format as kris.ppt.html. I cannot open the file. I can open the file when the portal is running. But I want to open the file when the portal is closed. Can anyone tell me the solution.
cheers
kris

Hello Shankar,
I tried that option also by default I'm getting 2 options.
One is the kris.ppt.html and other is the kris.ppt. I cannot open the first one rather I could open the second. I can open the 1st one if the portal is opened. Can you suggest anything regarding that one.
cheers
kris

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
" <b>The service for the client 300(My SAP R/3 client) is not present in Integration
Directory</b>"
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.....

Hi, I bought this some 80 euros option, but now when I triet to send BDF-file 88.0000 kt, it didn´t work at all. Said "couldn´t do this work". I am very disappointed. Can you do asap something for this problem. Vesa Laukkanen, LL.Lic. laki.vesa@pp.kpnet.f

Hi, I bought this some 80 euros option, but now when I triet to send BDF-file 88.0000 kt, it didn´t work at all. Said "couldn´t do this work". I am very disappointed. Can you do asap something for this problem. [email protected] This is very important service but it must work!

Hi vesa laukkanen,
It sounds like you're referring to an Adobe PDF Pack subscription. What process are you having trouble with? Are you trying to create PDF files, or combine them? Please give me a little more info about where you're running into trouble, and I'll do what I can to help.
Best,
Sara

Running Yosemite, printing to xerox c75 digital press. InDesign will send a file to the printer, then crashes every time. I know there was a patch for this problem. Where do I find it?

Whenever I send a file to my Xerox C75 from my Mac (Yosemite), the file goes to the printer okay, then InDesign crashes.
I think there is a patch specifically for this issue. Where do I find it?

Yes, I have Fiery Hot Folders Console. That is certainly an alternative that should work as I can then avoid having to choose Fiery Features from the print dialog box in order to choose the paper tray and other features I need.
I am about to try a clean install of OS 10.9.3, and I am not the least bit happy about it. Adobe CC is my main set of go-to applications for my work, and those are the only applications that give me ANY problems with printing. I have forked out real money on different versions since I started using Adobe in the late 1990's, and my troubles seem to increase with every new release.

Problem with Sending files over Sockets

Hi. I have a problem when I try to send files over sockets. When I send text files it works well but when I try to send .jpg or other kind of files it doesn't work well because some characters are wrong, I hope you can help me.
Here is my code:
//Sender code
import java.io.*;
import java.net.*;
class Servidor{
     Servidor(){
          try{
               String arch="art.jpg";
               ServerSocket serv=new ServerSocket(125);
               Socket socket=serv.accept();
               System.out.println("Conectado");
               int c;
               BufferedWriter bw=new BufferedWriter(new OutputStreamWriter(socket.getOutputStream()));
               FileInputStream fis=new FileInputStream(arch);
               File f=new File(arch);
               bw.write(""+f.length());
               bw.newLine();
               bw.flush();
               System.out.println("Escribiendo");
               while((c=fis.read())!=-1){
                    bw.write(c);
               bw.flush();
               fis.close();
               System.out.println("Terminado");
               while(true){
          }catch(Exception e){
               System.out.println(e);
     public static void main(String arg[]){
          new Servidor();
//Client code
import java.io.*;
import java.net.*;
class Cliente{
     Cliente(){
          try{
               Socket socket=new Socket("localhost",125);
               System.out.println("Conectado");
               BufferedReader br=new BufferedReader(new InputStreamReader(socket.getInputStream()));
               long tam=Long.parseLong(br.readLine());
               long act=0;
               FileOutputStream fos=new FileOutputStream("resp.jpg");
               System.out.println("Recibiendo: "+tam);
               while(act<tam){
                    fos.write(br.read());
                    act++;
               System.out.println("Terminado: "+act+" / "+tam);
               fos.close();
          }catch(Exception e){
               System.out.println(e);
     public static void main(String arg[]){
          new Cliente();
}

I don't think you want BufferedReader and OutputStreamWriter, you want ByteArrayOutputStream and ByteArrayInputStream . The problem is that you are sending jpegs (binary data) as text.

Have been trying all weekend to upload Jpegs- either Send does not work or shows files uploading then shows error- never had this problem with Send Now-16 images total size 92MB-largest image 13MB

Have been trying all weekend to upload Jpegs- either Send does not work or shows files uploading then shows error- never had this problem with Send Now-16 images total size 92MB-largest image 13MB

Hi Ciaran19,
Are you sending files from the Adobe Send interface, Adobe Reader, or the Outlook plug-in?
Have you checked to see whether the files that you're sending appear in the Recent Files/Sent Files list when you're logged on to https://cloud.acrobat.com? (It could be that they're uploading, but not being sent.)
It would also be worthwhile to send the files in smaller batches, to see whether a particular file or files is problematic, and causing the error.
Please let us know how it goes. If you're still having trouble, please let us know where you're sending from, and whether you're able to send the files in smaller batches. It would also be helpful to know the exact error message that you're receiving.
Best,
Sara

HT3042 Please show us the video tutorial for this because i am having so much problem with my iphone5 bluetooth and can not send any file . So plz plz help me

Please show us the video tutorial for this because i am having so much problem with my iphone5 bluetooth and can not send any file . So plz plz help me

You have to use airdrop which is on iOS 7

Problem in sending a file

Similar Messages

Maybe you are looking for