Error during sending sales idoc

hi all,
i m getting error during sending idoc for sales.................
Error:Check value field assignment for Condition PN10.....
How to solve this...?
Regards,
Imran

friends.......argent.......

Similar Messages

HTTP response code 500 : Error during Sender Agreement Determination

I am trying a simple file to file scenario and messages are not being received in Integration Server.
Through communication channel monitoring, i have received the below error message.
Error Transmitting the message to
endpoint http://<hostname>:50000/sap/xi/engine?type=entry using
connection File_http://sap.com/xi/XI/System failed, due
to:
com.sap.engine.interfaces.messaging.api.exception.MessagingException:
Received HTTP response code 500 : Error during Sender
Agreement Determination.
Can you please help
Regards
Harish

Hi Harish,
http://<hostname>:50000/sap/xi/engine?type=entry
it should be http://<hostname>:8000/sap/xi/engine?type=entry not 50000 as port It should be your HTTP port...please .make the changes !!
In SXMB_ADM transaction under Integration engine configuration please change the settings to http://<hostname>:8000/sap/xi/engine?type=entry
make sure with your basis team that ur http port is 8000 or 8001 ..as per that make the necessary changes..
Regards,

Error during sending IDoc from XI to R/3

Hi,
I get following error (transaction: sxmb_moni), when I try to send a IDoc from XI to R/3.
Error: Transaction IDX1: Port SAPI14_921, client , RFC destination contain errors.
When I go to transaction sm 59 and start this rfc-destination so it works fine.
Can anybody help me please?
Thanks.
Regards
Stefan

Hi,
I dont now how you pushed the IDOC form R/3 to XI..
Follow this particular way ....
Go to WE19 and execute the IDOC which you want to send and clicl the tab startoutboundprocessing....
then it hits the XI after couple of minutes and then
Go to the XI in that IDX5 where you can see the IDOC messages....
Amaresh

Va01:errors during posting sales order

Hi there,
can anyone help me on the error log during posting sales order via va01? the checking of sales order is correct.
Runtime Errors         MESSAGE_TYPE_X
Date and Time          2009.02.17 10:11:37
Short dump has not been completely stored (too big)
|Short text          |
|    The current application triggered a termination with a short dump. |
|What happened?      |
|    The current application program detected a situation which really   |
|    should not occur. Therefore, a termination with a short dump was    |
|    triggered on purpose by the key word MESSAGE (type X). |
|What can you do?    |
|    Note down which actions and inputs caused the error.   |
|       |
|       |
|    To process the problem further, contact you SAP system |
|    administrator. |
|       |
|    Using Transaction ST22 for ABAP Dump Analysis, you can look         |
|    at and manage termination messages, and you can also   |
|    keep them for a long time.   |
|Error analysis      |
|    Short text of error message: |
|    Maintain the current CRM release (table CRMPAROLTP)    |
|       |
|    Long text of error message: |
|     Diagnosis      |
|         Various transfer errors occur when transferring SAP sales orders to         |
|         CRM or there is no status update or the status update has errors            |
|         when transferring from CRM to the SAP system. This is caused by an          |
|         incorrect entry for the CRM release in the SAP table CRMPAROLTP, or         |
|         no entry is maintained at all.       |
|     System Response|
|         To avoid data inconsistencies, this message causes a short dump.            |
|     Procedure      |
|         Maintain table CRMPAROLTP in your SAP system as is described in SAP         |
|         Note 691710 and then repeat the process again.    |
|     Procedure for System Administration      |
|       |
|    Technical information about the message: |
|    Message class....... "V3"    |
|    Number.............. 302     |
|    Variable 1.......... " "     |
|    Variable 2.......... " "     |
|    Variable 3.......... " "     |
|    Variable 4.......... " "     |
|How to correct the error         |
|    Probably the only way to eliminate the error is to correct the program.          |
|    - |
|       |
|    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:       |
|       |
|    "MESSAGE_TYPE_X" " "         |
|    "SAPMV45A" or "MV45AF0B_BAPIDATEN_ERMITTELN"           |
|    "BAPIDATEN_ERMITTELN"        |
|       |
|    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.       |
|       |
|User and Transaction|
|    Client.............. 200     |
|    User................ "SAMSON"|
|    Language key........ "E"     |
|    Transaction......... "VA01 " |
|    Program............. "SAPMV45A"           |
|    Screen.............. "SAPMV45A 4001"      |
|    Screen line......... 65      |
|Information on where terminated |
|    Termination occurred in the ABAP program "SAPMV45A" - in "BAPIDATEN_ERMITTELN". |
|    The main program was "SAPMV45A ".         |
|       |
|    In the source code you have the termination point in line 338       |
|    of the (Include) program "MV45AF0B_BAPIDATEN_ERMITTELN".            |
|Source Code Extract |
|Line |SourceCde     |
| 308|    else.     |
| 309|*-----Nicht unterstu9EF7zt, Abbruch        |
| 310|      message a301(v3).    |
| 311|    endif.    |
| 312| endif.      |
| 313| |
| 314|*-Szenario A pru9EE4en        |
| 315| if lv_scenario_a   = 'A'.|
| 316|    vbak-vbkla+2(1) = lv_scenario_a.    |
| 317| endif.      |
| 318| |
| 319|*-ermitteln CRM-Release    |
| 320| call function func_name |
| 321|        exporting          |
| 322|            i_paraname = 'CRM_RELEASE' |
| 323|        importing          |
| 324|            e_parval1 = lv_parval1.    |
| 325| lv_release_crm = lv_parval1+0(3).     |
| 326| |
| 327|* If lv_release_crm empty => X-message (correct download not possible)         |
| 328| if da_download_active = charx.        |
| 329|    CALL FUNCTION 'CRM_CONNECTED'       |
| 330|     IMPORTING|
| 331|       CRM_CONNECTED       = lv_crm_connected        |
| 332|     EXCEPTIONS            |
| 333|       NO_CRMRFCPAR        = 1          |
| 334|       OTHERS = 2          |
| 335| .            |
| 336|    IF sy-subrc = 0 and lv_release_crm = space and   |
| 337|       lv_crm_connected = charx.        |
|>>>>>|        message x302(v3). |
| 339|    ENDIF.    |
| 340|   endif.     |
| 341| |
| 342|*-Fu9EEElen der View fu9EF5 das Ermitteln der Auftragstabellen          |
| 343| da_sales_view-partner    = charx.     |
| 344| da_sales_view-sdcond     = charx.     |
| 345| da_sales_view-sdcond_add = charx.     |
| 346| da_sales_view-contract   = charx.     |
| 347| da_sales_view-text       = charx.     |
| 348|*-bei mehr als 1000 Belegflusssu92DEzen werden Daten nicht ermittelt |
| 349| if lv_tabix_vbfa < 1000. |
| 350|    da_sales_view-flow     = charx.     |
| 351| endif.      |
| 352| da_sales_view-billplan   = charx.     |
| 353| da_sales_view-configure = charx.     |
| 354| da_sales_view-credcard   = charx.     |
| 355| |
| 356|*-Im Standardszenario soll eine manuelle u818Ederung eines CRM Belegs|
| 357|* (ab CRM Release 30A) nicht zuru9EDEk ins CRM gesendet werden. Das |
any responses will be awarded,
regards,
samson

Hi,
Maintain the current CRM release.
The dump might have occurred when transferring SAP sales order to CRM.
This has caused a error in SAP table CRMPAROLTP .
Go to SE91 provide the message class & message number, then click where-used-list & select the program check box.It will show you the program name MV45AF0B_BAPIDATEN_ERMITTELN.
Just check the program with the ABAPer.
Hope this helps.
Regds.......
Sumit

Error to send a IDOC from ECC to SUS

Hi,
I am trying to connect to SAP SUS System using HTTP adapter using PI 7.0.The scenario is
ECC ->PI->SAP SRM. I have configured HTTP adapter as the receiver with addressing type as HTTP Destination. I have created a RFC destination of type H pointing to SAP SUS on PI. I have encountered the following error after executing the scenario.
<?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="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_SERVER</SAP:Code>
<SAP:P1>500</SAP:P1>
<SAP:P2>Internal Server Error</SAP:P2>
<SAP:P3>Error during parsing of SOAP header</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>HTTP server code 500 reason Internal Server Error explanation Error during parsing of SOAP header</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
I have configured HTTP receiver with Addressing type HTTP Destination and configured the HTTP destination field with RFC destination(Connection Type H) created on PI. Here my source and target structures are same i.e DELVRY03. I have triggered DELVRY03 idoc from ECC and i am expecting same xml to be sent to SAP SUS but stuck up with the above mentioned error.
Someone know how fix this problem?
Tks,
Erik

HI,
As per my understanding to your scenario, You want to send one IDoc from ECC to SAP SUS system using SAP PI.
So i hope you must have configured on all the steps required to Send one IDoc to PI syste, Secondly, are you using any Standard interface in PI to send data to SAP SUS system? If yes, you need to create an HTTP Destination for that system and then you have to create XI Receiver Adapter with that HTTP destination to post incoming message to SAP SUS system.
Your error suggests you are using Plain HTTP adapter to post data to SAP SUS, which is in my understanding is incorrect.
Regards
Aashish Sinha
Edited by: Aashish Sinha on Feb 21, 2011 9:15 AM

Error while sending sales order form by fax

hi,
Sending Sales order by fax is not working. While adding output type for Sales order choosing device as 'FAX' is throwing an error saying that 'Error while sending fax with SO_OBJECT_SEND, return code 9'. Anything needs to be configured or we have to code anything in SAPScript program. Please advise.

Hi Harry,
You don't need to write any particular code for sending FAX in SAPscript. But you may need to check some configurations regarding it.
We configure SCOT to send Fax and mails to outside SAP. Check SAP Note 455140 for the configuration of SCOT tcode.
Please refer this link [Sending FAX |Sending FAX from SAP;
It might be helpful.
Thanks,
Daya.

Error during variable substitution: idoc to file

Hi Friends,
I have a got a issue which is Idoc to file scenario.
Iam getting the following error.
Attempt to process file failed with com.sap.aii.adapter.file.configuration.DynamicConfigurationException: Error during variable substitution: com.sap.aii.adapter.file.varsubst.VariableDataSourceException: The following variable was not found in the message payload: date_processing
Could you please tell me waht could be the reason for the same?
as per my analysis, I observed that the field date_processing has been declared

Hi Sandeep ,
If the variable date_processing refers to an element in XML schema, Please check if you have added the prefix payload: to the information under Reference.
The reference then comprises a pseudo path description in the form of a comma-separated list with the schema namea,na,nameb,nb,....
Where namea,nameb,... corresponds to the element name and na,nb,... corresponds to the occurrence of the element name at the respective level in the document.
The description begins at the root of the document and ends at the respective element.
Also please check
Re: Variable substitution
Regards,
Jyoti

Error in sender sap idoc side

Hi Experts,
            1, When the sender post idoc to PI it shows the following
              error in sender sap system.
               Error:No service for system SAPQ01 client 118 in integration directory
            2, Is it possible to post the idoc to PI With out activating the integ directory Object in PI(Integ.repoistery activated).
            3, If possible, where can i see the idoc datas in PI before activation.
Thanks

Hi Raja,
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 Transaction SLDCHECK.
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 .
Regds,
Pinangshuk.

No Objects Found error during Sender agreement in ID

I created all objects, activated in IR and refreshed Cache with SXI_Cache.
Created Scenario in ID.
During Sender agreement creation, I gave Sender Service ( Which doesn't have to be in SLD ). Then Iam trying to pick Interface from drop down. Surprisinglt I cant see any object instead it throws error "No Objects Found" .
What should I do to see the Interfaces from Design?. Any suggestion here ?
Iam doing File to File scenario with Business Service.
Thanks

S T,
from what you've said, you're using Business Services and not Business Systems.
Business Services are simpler (in the sense that you don't need to refer them in SLD and all), but the catch is that they don't have some useful stuff that Business Systems have.
One of these is that, for Business Systems, all the interfaces that are in SWCVs which belong to that BSy are automatically considered as valid interfaces for that BSy.
As for Business Services, you have to define all the interfaces that you want in the BSe, one by one. The good news is that you can use the Message Interfaces of any SWCV of Integration Repository, without having to specifically add the SWCV to the BSe (which can be a pain in the @$$ some times...).
To see and/or include message interfaces for a Business Service, just double click on it on Scenario or Objects tabs of Integration Directory.
Regards,
Henrique.

Error when sending message: 500 Error during Sender Agreement Determination

Hi,
Am getting this error, while testing to post a data from RWB. can anyone tell me what the problem is? its IDOC to JDBC scenario. i've checked all the config objects in the scenario and they all seem to be fine.
Regards,
Rashmi

Hi Prateek,
i have created sender agreement, as i ran config wizard to create the scenario and it forced me to create a sender agreement.
Seshagiri, i tried using the test tool you mentioned, Interface Mapping step is failing and the error i'm getting is:
During the application mapping com/sap/xi/tf/_outCustomerDetails_DEBMAS_DEBMAS03~ a com.sap.aii.utilxi.misc.api.BaseRuntimeException was thrown: RuntimeException in Message-Mapping transformatio~
any clue?
Regards,
Rashmi

Error when sending INVOICE01 iDoc to SAP R/3 system

Hi,
I was trying to send an INVOICE01 iDoc to SAP R/3 system. I checked the iDoc list (transaction code we02), the iDoc I sent was in the status 51 with the error message as "Program parameters LS <Logic System Name> <Company code> have not been set". Could someone help me how to resolve this error?
Thanks,
Trifire

SLG1 or IDOC in idoc status WEDI

ALE Error while sending PO IDOC through EDI

Hi Experts,
                  I am sending one PO IDOC through EDI but I am getting the following error:-
                  Message no. B1130.
                  "Too many recipients found for message type ORDERS in the ALE model"
                  How can I solve this error ? Please guide me in this regards as this is an
                  important issue with urgency.
Thanks & Regards
Jitendra Gujarathi

Please check this discussion thread
Re: Too many recipients found for message type in the ALE model

Mapping Error with Sender JDBC- Idoc scenario

Hi Guru's,
I've got a simple asyncronous sender JDBC to Idoc scenario, and I encounter a strange problem with the mapping.
When I test the mapping it works fine, but when I run the scenario, only the first element (a constant) of the Idoc gets mapped, and mapping stops with no errors.
Does someone know where to find the error?
Thanks,
Karst

Hi Karst,
There might be several reasons that you do not see the IDOC structures are not created/mapped:
1. Most of the IDOC structures are optional (minOccrs = 0), so you have to make sure the structure itself (not just the fields within that structure) is mapped to something that does exist in the source data.
2. Make sure your JDBC generated source data does have the right namespace as you used in your mapping. I once had a similar problem, but finally found the source data generated in run time is slightly different from the one used in mapping in terms of namespace.
3. Test your mapping with the source data generated in runtime (you can copy it from SXMB_MONI). Then you may be able to find the problem.
Hope this helps.
Hart

Error during sending a PDF attachment of a mail

Hi everebody,
                  I'm using a custom program [ see below ] ( in which there is the call to the std function SO_DOCUMENT_SEND_API1) to send a PDF attachment to an user's SAPOFFICE: in release 4.6C it works correctly but the same programm in ECC6 it doesn't work correctly. I mean: the mail is sent correctly with the attachment, but when I try to open the attachment this one doesn't open correctly showing a PDF error message.
Any help?
            gino bonfiglioli
*& Report Z_UT_CONVERT_SPOOL_PDF
REPORT z_ut_convert_spool_pdf.
TABLES: tsp01.
variabili globali
*data: fm_name            type rs38l_fnam,
     output_options     type ssfcompop,
     control_parameters type ssfctrlop,
     job_output_info    type ssfcrescl,
     job_output_options type ssfcresop,
DATA: spoolno            LIKE tsp01-rqident,
      dir_pdf            LIKE rlgrap-filename,
      numbytes           TYPE i,
      pagecount          TYPE i,
      w_cnt              TYPE i,
      wk_subrc           LIKE sy-subrc,
      pdfspoolid         LIKE tsp01-rqident,
      gd_buffer          TYPE string,
      pdf                LIKE tline OCCURS 100 WITH HEADER LINE,
      stampante          LIKE usr01-spld,
      tot_line   TYPE sy-tabix,
      tot_line2 TYPE sy-tabix,
      start_line TYPE sy-tabix.
tabelle interne per 1a mail
DATA: BEGIN OF it_email OCCURS 100.
        INCLUDE STRUCTURE solisti1.
DATA: END OF it_email.
DATA: BEGIN OF email_data.
        INCLUDE STRUCTURE sodocchgi1.
DATA: END OF email_data.
DATA: BEGIN OF email_send OCCURS 10.
        INCLUDE STRUCTURE somlreci1.
DATA: END OF email_send.
DATA: packing_list TYPE STANDARD TABLE OF sopcklsti1 WITH HEADER LINE,
      it_mess_att LIKE solisti1 OCCURS 0 WITH HEADER LINE,
      receivers    TYPE STANDARD TABLE OF somlreci1 WITH HEADER LINE.
fine tabelle interne per 1a mail
PARAMETER: p_spool LIKE tsp01-rqident.
START-OF-SELECTION.
PERFORM conversione_spool_pdf USING wk_subrc.
IF wk_subrc EQ 0.
    PERFORM invio_mail.
ENDIF.
*&      Form CONVERSIONE_SPOOL_PDF
      text
     -->P_P_SUBRC text
FORM conversione_spool_pdf USING    p_subrc.
**- Conversione in PDF
CALL FUNCTION 'CONVERT_OTFSPOOLJOB_2_PDF'
      EXPORTING
        src_spoolid                    = p_spool
        no_dialog                      = ' '
      DST_DEVICE                     =
      PDF_DESTINATION                =
      IMPORTING
        pdf_bytecount                  = numbytes
        pdf_spoolid                    = pdfspoolid
        otf_pagecount                  = pagecount
       btc_jobname                    = jobname
       btc_jobcount                   = jobcount
      TABLES
        pdf                            = pdf
      EXCEPTIONS
        err_no_otf_spooljob            = 1
        err_no_spooljob                = 2
        err_no_permission              = 3
        err_conv_not_possible          = 4
        err_bad_dstdevice              = 5
        user_cancelled                 = 6
        err_spoolerror                 = 7
        err_temseerror                 = 8
        err_btcjob_open_failed         = 9
        err_btcjob_submit_failed       = 10
        err_btcjob_close_failed        = 11.
p_subrc = sy-subrc.
ENDFORM.                    " CONVERSIONE_SPOOL_PDF
*&      Form invio_mail
      text
--> p1        text
<-- p2        text
FORM invio_mail .
Transfer the 132-long strings to 255-long strings
LOOP AT pdf.
    TRANSLATE pdf USING ' ~'.
    CONCATENATE gd_buffer pdf INTO gd_buffer.
ENDLOOP.
TRANSLATE gd_buffer USING '~ '.
DO.
    it_mess_att = gd_buffer.
    APPEND it_mess_att.
    SHIFT gd_buffer LEFT BY 255 PLACES.
    IF gd_buffer IS INITIAL.
      EXIT.
    ENDIF.
ENDDO.
Testo della mail
CLEAR it_email. REFRESH it_email.
it_email-line = 'Testo della mail'.
APPEND it_email.
Creazione messaggio
email_data-obj_name      = 'MESSAGE'.
email_data-obj_descr     = 'Conversione spool n.'.
email_data-obj_descr+26 = p_spool.
email_data-obj_langu     = 'I'.
email_data-sensitivty    = 'F'.
READ TABLE it_mess_att INDEX w_cnt.
email_data-doc_size =
     ( w_cnt - 1 ) * 255 + STRLEN( it_mess_att ).
start_line = 1.
DESCRIBE TABLE it_email LINES tot_line.
packing_list-transf_bin = ' '.
packing_list-doc_type   = 'RAW'.
packing_list-head_start = 1.
packing_list-head_num   = 0.
packing_list-body_start = 1.
packing_list-body_num   = tot_line.
packing_list-obj_langu = sy-langu.
APPEND packing_list.
APPEND LINES OF it_mess_att TO it_email.
CLEAR packing_list.
Riga iniziale = ultima riga messaggio precedente + 1
start_line = tot_line + 1.
DESCRIBE TABLE it_mess_att LINES tot_line.
packing_list-transf_bin = 'X'.
packing_list-head_start = 1.
packing_list-head_num   = 1.
packing_list-body_start = 1.
DESCRIBE TABLE it_mess_att LINES packing_list-body_num.
packing_list-doc_type   = 'PDF'.
packing_list-obj_descr = 'Allegato PDF.'.
packing_list-doc_size   = packing_list-body_num * 255.
packing_list-obj_langu = sy-langu.
APPEND packing_list.
destinatario interno a SAP
receivers-receiver = sy-uname.
receivers-rec_type = 'B'.
receivers-express = 'X'.
APPEND receivers.
destinatario esterno a SAP: deve essere un idirizzo email:
receivers-receiver = '[email protected]'.
receivers-rec_type = 'U'.
APPEND receivers.
CALL FUNCTION 'SO_DOCUMENT_SEND_API1'
EXPORTING
    document_data                    = email_data
    put_in_outbox                    = 'X'
   SENDER_ADDRESS                   = SY-UNAME
    sender_address_type              = 'B'
   COMMIT_WORK                      = 'X'
IMPORTING
SENT_TO_ALL                      =
NEW_OBJECT_ID                    =
SENDER_ID                        =
TABLES
    packing_list                   = packing_list
    contents_bin                   = it_mess_att
    contents_txt                   = it_email
    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.
errore invio mail
ENDIF.

Hi,
Try to use fm 'SO_NEW_DOCUMENT_ATT_SEND_API1' instead of SO_DOCUMENT_SEND_API1.
Please check documentation of fm SO_DOCUMENT_SEND_API1 in ECC 6.
a®

Error during sending mail from solaris 9

Hi All,
I am trying to send mail from solaris machine.I am using sendmail 8.12.9+Sun.When I am trying to send mail a mail using
#echo "Test mail"|mailx -s "welcome to Solaris" [email protected]
#it is execuitng sucessfully but when I am seeing the /var/log/syslog file,then It showing the error--
/etc/mail/aliases.db out of date
Aug 6 15:51:33 mgsun sendmail[823]: [ID 801593 mail.notice] n76ALXfa000823: <Sang@mgsun>... User unknown
Aug 6 15:51:33 mgsun sendmail[813]: [ID 801593 mail.info] n76ALXZo000813: to=Sang, delay=00:00:00, xdelay=00:00:00, mailer=relay, pri=31096, relay=[127.0.0.1] [127.0.0.1], dsn=5.1.1, stat=User unknown
00823: from=<>, size=1096, class=0, nrcpts=0, proto=ESMTP, daemon=MTA, relay=localhost [127.0.0.1]
00813: n76ALXZp000813: return to sender: User unknown
Aug 6 15:51:33 mgsun sendmail[823]: [ID 801593 mail.info] n76ALXfc000823: from=<>, size=3566, class=0, nrcpts=1, msgid=<200908061021.n76ALXZp000813@mgsun>, proto=ESMTP, daemon=MTA, relay=localhost [127.0.0.1]
Aug 6 15:51:33 mgsun sendmail[813]: [ID 801593 mail.info] n76ALXZp000813: to=postmaster, delay=00:00:00, xdelay=00:00:00, mailer=relay, pri=32120, relay=[127.0.0.1] [127.0.0.1], dsn=2.0.0, stat=Sent (n76ALXfc000823 Message accepted for delivery)
Aug 6 15:51:33 mgsun sendmail[824]: [ID 702911 mail.info] alias database /etc/mail/aliases.db out of date
Aug 6 15:51:33 mgsun sendmail[824]: [ID 801593 mail.info] n76ALXfc000823: to=root, delay=00:00:00, xdelay=00:00:00, mailer=local, pri=33739, dsn=5.3.0, stat=unknown mailer error 5
Aug 6 15:51:33 mgsun sendmail[824]: [ID 801593 mail.info] n76ALXfc000823: n76ALXfY000824: postmaster notify: unknown mailer error 5
Aug 6 15:51:33 mgsun sendmail[824]: [ID 801593 mail.info] n76ALXfY000824: to=root, delay=00:00:00, xdelay=00:00:00, mailer=local, pri=31024, dsn=5.3.0, stat=unknown mailer error 5
Aug 6 15:51:33 mgsun sendmail[824]: [ID 801593 mail.info] n76ALXfY000824: n76ALXfZ000824: return to sender: unknown mailer error 5
Aug 6 15:51:33 mgsun sendmail[824]: [ID 801593 mail.info] n76ALXfZ000824: to=root, delay=00:00:00, xdelay=00:00:00, mailer=local, pri=31024, dsn=5.3.0, stat=unknown mailer error 5
Aug 6 15:51:33 mgsun sendmail[824]: [ID 801593 mail.alert] n76ALXfY000824: Losing ./qfn76ALXfY000824: *savemail panic*
Aug 6 15:51:33 mgsun sendmail[824]: [ID 801593 mail.crit] n76ALXfY000824: SYSERR(root): s*avemail: cannot save rejected email anywhere*Please help me to resolve it.
Thanks in advance..

Here's some pointers on troubleshooting sendmail:
[http://docs.hp.com/en/B2355-90110/ch05s08.html]
and
qualify my own domain
[http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=149991]
newaliases error - Executable files not allowed
[http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=39966]
HP forums can be good for SUN too. :)

Error during sending sales idoc

Similar Messages

Maybe you are looking for