SAP to XI IDoc Outbound Error

Hi,
I am sending an IDoc from SAP R/3 to SAP XI . In WE02 IDoc showing Status as 03 (sucess) but in SM58 it showing as Error
*No service for system SAPTI2, client 030 in Integration Directory *
Any Info?
a®

Got answer from XI forum

Similar Messages

IDoc outbound errors - mail send step in WF to send info-mail to enduser

Hello specialists
I searched quite a lot in the forums now. I found lot of info but nothing regarding my issue.
I need to send an info-mail to the end user creating purchase orders. But only if the idoc (outbound ORDERS) could not be sent (failing for some reason, i.e. if rfc connection fails). This is what I've done to achieve this:
- in WE40 I linked my WF to process code EDIO
- the WF-BATCH user has an email address assigned to it (in SU01)
- the mail sending step in my WF is configured like this:
recipient type = G (organizational object)
Expression = &_WORKITEM.CREATEDBYUSER.ID& (this contains the enduser id)
subject = Test for &WORKITEM.CREATEDBYUSER.ID&
When testing the mail can not be delivered (error SO23).
When setting recipient type to U (E-Mail address) and giving a valid e-mail address, then it works fine (SCOT, etc. is configured and mailing to external systems works). But setting the e-mail address hard coded style in the mail send step is not an option here!
It seems that the send mail step (SELFITEM.SENDTASKDESCRIPTION) always requires a valid e-mail address. Is it not able to handle SAP user id's ?
Thanks in advance for some guideance on this one.
Renaud
Edited by: Renaud Desarzens on Feb 11, 2010 3:00 PM

Hello and thanks for your help.
I was able to solve it like this:
- don't use mail send step
- instead, add new activity with a new task (SELFITEM.SENDTASKDESCRIPTION)
- in the bindings (workflow -> step) set:
B --> &TYPEID&
&_WORKITEM.CREATEDBYUSER.ID& --> &ADDRESSSTRINGS&
Seems that the mail send step doesn't allow TYPEID to be "B" because each time I tried to tweak the generated bindings that way it messed up the recipient type and expression I set before.
Regards
Renaud

File to Idoc - Outbound Error

Hi,
I am doing File to IDOC scenario. I got error
in "Message has error status at outbound status" .. When
I opend that messeage then i got this ...
<SAP:IDOCTYP>ZIDOCIN</SAP:IDOCTYP>
<SAP:CIMTYP />
<SAP:MESTYP>ZMTIDOCIN</SAP:MESTYP>
<SAP:MESCOD />
<SAP:MESFCT />
<SAP:SNDPOR>SAPX11</SAP:SNDPOR>
<SAP:SNDPRN>Logi_01</SAP:SNDPRN>
<SAP:SNDPRT>LS</SAP:SNDPRT>
<SAP:SNDPFC />
<SAP:RCVPOR>SAPA11</SAP:RCVPOR>
<SAP:RCVPRN>A11CLNT200</SAP:RCVPRN>
<SAP:RCVPRT>LS</SAP:RCVPRT>
<SAP:RCVPFC />
<SAP:TEST />
Can any one tell me what to do to solve this.
thx,
Ansar.

Hi,
There is somethig worng with your Partner Function while defining the the Partner Profile, please check it. The Partner function is optionla and see if you need it
Go thru the link,
http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b80b543d711d1893e0000e8323c4f/content.htm
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/cdded790-0201-0010-6db8-beb9bb2b2660
Thanks,
Prakash
Thanks,
Prakash

IDOC OutBound Error 29: Entry in outbound table not found?

Dear All,
        I configed the customized IDOC,and used BD64,WE20 Generate Partner Profile.the partner type is u2018LSu2019,In We20,I clicked the check button .There is no error in check.Other config also correct.
My outbound program main code is :
WA_IDOC_CONTROL_RECORD-MESTYP = 'ZMSGTYPE_WE81'.
WA_IDOC_CONTROL_RECORD-IDOCTP = 'ZIDOCTYPE_WE30'.
Receiver
WA_IDOC_CONTROL_RECORD-RCVPOR = 'A000000003'.           "Port
WA_IDOC_CONTROL_RECORD-RCVPRN = 'target100'.        "Partner number
WA_IDOC_CONTROL_RECORD-RCVPRT = 'LS'."Partner type
WA_IDOC_CONTROL_RECORD-RCVPFC = 'LS'."Partner function
Sender
wa_idoc_control_record-sndpor = 'A000000001'.           "Port
wa_idoc_control_record-sndprn = 'source500'.           "Partner number
wa_idoc_control_record-sndprt = 'LS'.             "Partner type
WA_IDOC_CONTROL_RECORD-SNDPFC = 'LS'."Partner function
DATA L_ITEM TYPE I.
LOOP AT GT_IDOC.
    L_ITEM = L_ITEM + 1.
    WA_EDIDD-SEGNAM = 'ZSEG_WE31'.
    WA_EDIDD-SEGNUM = L_ITEM.
    WA_EDIDD-SDATA = GT_IDOC.
    APPEND WA_EDIDD TO IT_EDIDD.
ENDLOOP.
CLEAR L_ITEM.
SORT IT_EDIDD BY SEGNUM.
CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE'
       EXPORTING
            MASTER_IDOC_CONTROL            = WA_IDOC_CONTROL_RECORD
          OBJ_TYPE                       = ''
          CHNUM                          = ''
       TABLES
          COMMUNICATION_IDOC_CONTROL     = IT_COMMUNICATION_IDOC_CONTROL
            MASTER_IDOC_DATA               = IT_EDIDD
       EXCEPTIONS
            ERROR_IN_IDOC_CONTROL          = 1
            ERROR_WRITING_IDOC_STATUS      = 2
            ERROR_IN_IDOC_DATA             = 3
            SENDING_LOGICAL_SYSTEM_UNKNOWN = 4
            OTHERS                         = 5
IF SY-SUBRC <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ELSE.

hi Sun,
The value 'X' means ABAP_TRUE, which means the outbound ALE settings for your message type are OK.
Did you check the sy-subrc value after the FM 'MASTER_IDOC_DISTRIBUTE' is called ? and if yes what is the value ?
Also did u check the IT_EDIDD table, whether is contains any values ?
If all of the above is fine then call the FM 'EDI_DOCUMENT_DEQUEUE_LATER' by passing the document number of the outbound IDoc created, this number you will from the 'communication_idoc_control' table which you need to pass to your FM MASTER_IDOC_DISTRIBUTE.
for your reference attached is code for it
    CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE'
      EXPORTING
        master_idoc_control            = wf_edidc
      TABLES
        communication_idoc_control     = int_comm_cntl
        master_idoc_data               = int_edidd
      EXCEPTIONS
        error_in_idoc_control          = 1
        error_writing_idoc_status      = 2
        error_in_idoc_data             = 3
        sending_logical_system_unknown = 4
        OTHERS                         = 5.
if sy-subrc = 0.
APPEND LINES OF lt_idoc_comm_control TO g_idoc_comm_control.
endif.
LOOP AT g_idoc_comm_control.
    CALL FUNCTION 'EDI_DOCUMENT_DEQUEUE_LATER'
      EXPORTING
        docnum = g_idoc_comm_control-docnum.
ENDLOOP.
{/code}
hope this will solve your problem
Edited by: Ashwinee on Dec 26, 2008 12:09 PM

ALE / IDOC Outbound Error Handling

Hi Experts,
I got an error in Outbound Process.
An IDOC gets the status 36 - Timed out.
Can anyone tell me how can i resolve this Error?.
Thanks in advance,
Sudhakar

Hi ,
Best option is to keep a sql trace on the outbound idoc which will tell you at which perform or functional module ,the performance is taking time to fetch .
all check with basis in terms of timed out ,they would have set a paramater for time out in terms of mins or hrs.

Send changes of Artical master data from sap to nonsap (idoc outbound prog)

Hi Experts,
I am new to interfaces
I have one requirement in Idocs, i.e the changes of artical master data is send to sap to nonsap system through idoc.
idoc type is ARTMAS05, msg typ is ARTMAS.
I am giving some information for my object.
For article (MATNR) by site (WERKS plant)
     If MRP Type (MARC-DISMM) = u201CX0u201D
          Then if changes to fields:
          MARC-KZAUS     Discontinuation ind.
          MARC-AUSDT     Effective date out
          MARC-NFMAT     Follow-up article
Then send idoc type ARTMAS05 with the following data
segment E1BPE1MATHEAD
     MATERIAL
segment E1BPE1MARCRT
MATERIAL             PLANT                     DISCONTINU
EFF_O_DAY            FOLLOW_UP
Systems Referred to:
The planning system for our client is nonsap system. This software requires to be informed of relevant changes on articles in order to start its planning runs. When an article is superseded by another we have to send the replacement article (if any) as well as the discontinuation date.
Dependencies/Prerequisites :
     Change pointers for Article master active
     Change pointers active for fields:
     MARC-KZAUS      Discontinuation indicator
     MARC-AUSDT     Effective date out
     MARC-NFMAT     Follow-up article
Idoc ARTMAS05 required with reduction in order to only send relevant fields
Filter to only send idocs for materials in the u201CAutomotiveu201D type where MARC-DISMM = u201CX0u201D.
So this is my requirement, please send some sample code or idea how to complete object.
with regards,
gs reddy.

Hi,
All the details mentioned seems to be correct.
just change one "automotive" material and check change documents are getting generated.
i hope partner profiles are already in place.
once change docuements are inpalce check RBDMIDOC program is scheduled in back ground or you can manually execute the program for testing.
and check the IDoc generated.
do you want supress some segements?
di your NOn-sap ssytem can accept Idoc?
Suresh

IDOC Outbound processing using SAP BC

Hello Experts,
I am trying to develop a simple IDOC outbound processing scenario using SAP BC. In this an IDOC from SAP ECC server will be sent to an external webserver via SAP BC, for this i have done all the setup i.e Establishing connection between SAP BC & SAP ECC, ALE settings, creating a new Routing rule, but when i try to run this scenario, i am getting the following error 'IDocMetaDataUnavailableException: (3) IDOC_ERROR_METADATA_UNAVAILABLE' , is there any way to import the IDOC metadata, just like how we do in SAP XI using IDX2. Please Help...
Thanks & Regards,
Amit Naik

Hi Michal,
Following is the error which i am getting :-
2009-03-12 21:56:59 IST com.sap.conn.idoc.IDocMetaDataUnavailableException: (3) IDOC_ERROR_METADATA_UNAVAILABLE: The meta data for the IDoc type "" is unavailable.
     at com.sap.conn.idoc.rt.DefaultIDocDocument.<init>(DefaultIDocDocument.java:132)
     at com.sap.conn.idoc.jco.JCoIDocDocument.<init>(JCoIDocDocument.java:74)
     at com.sap.conn.idoc.jco.JCoIDocDocument.createIDocDocument(JCoIDocDocument.java:117)
     at com.sap.conn.idoc.jco.JCoIDocRuntime.createIDocDocumentList(JCoIDocRuntime.java:83)
     at com.sap.conn.idoc.jco.DefaultJCoIDocServerWorker$IDocDispatcher.handleRequest(DefaultJCoIDocServerWorker.java:88)
     at com.sap.conn.jco.rt.DefaultServerWorker.dispatchRequest(DefaultServerWorker.java:141)
     at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.dispatchRequest(MiddlewareJavaRfc.java:2621)
     at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.executePlayback(MiddlewareJavaRfc.java:2298)
     at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.playbackTRfc(MiddlewareJavaRfc.java:2130)
     at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.handletRfcRequest(MiddlewareJavaRfc.java:2012)
     at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.listen(MiddlewareJavaRfc.java:1903)
     at com.sap.conn.jco.rt.DefaultServerWorker.dispatch(DefaultServerWorker.java:258)
     at com.sap.conn.jco.rt.DefaultServerWorker.loop(DefaultServerWorker.java:320)
     at com.sap.conn.jco.rt.DefaultServerWorker.run(DefaultServerWorker.java:219)
     at com.wm.util.TimeWrappingProvider$TimeMesuredTask.run(TimeWrappingProvider.java:40)
     at com.wm.pkg.sap.rfc.ListenerThread.run(ListenerThread.java:70)
Thanks & Regards,
Amit

Error 26: Error during syntax check of IDoc (outbound)

Hi all,
   I am getting error when we try to generate IDoc in Outbound process (to send data from SAP to external Interface).
Error no is 26. And I have checked the status records, it shows the below error message. "EDI: Syntax error in IDoc (too many repetitions of a group). According to the syntax description of the basic type SHPMNT05 (customer enhancement ZSHPMNT05), the segment group E1EDL37 can be repeated a maximum of 0000000260 times. However, this segment group occurs more frequently in the IDoc. Please check the IDoc or the syntax description of the basic type SHPMNT05 (customer enhancement ZSHPMNT05).
Can any one tell me is there any limitation for data records for segment E1EDL37?
Kindly suggest me what is the problem & what needs to be done to fix this.
Thanks in advance.
Regards
Mohammad.

Hi Guys,
This is a problem which occurs throughout lots of SAP systems. This occurs due to someone changing the IDOCSYN table without making the neccessary changes to the EDISYN table.
For more information on this you can check out the note - 370021. Also if you run the following program in your system and make the changes to your IDOC segment, this error will go away.
(Please note that this program is provided by SAP and I just made a small adjustment by adding the COMMIT WORK AND WAIT statement) .
Hope this helps.
REPORT ze1edp19.
TABLES: idocsyn, edisyn, cimsyn.
DATA: old_idocsyn TYPE idocsyn,
      lt_idocsyn TYPE STANDARD TABLE OF idocsyn,
      ls_idocsyn TYPE idocsyn,
      old_edisyn TYPE edisyn,
      lt_edisyn   TYPE STANDARD TABLE OF edisyn,
      ls_edisyn   TYPE edisyn.
PARAMETER idoc_typ TYPE idocsyn-idoctyp DEFAULT 'ORDERS05'.
PARAMETER idoc_seg TYPE idocsyn-segtyp DEFAULT 'E1EDP19'.
PARAMETER occmax   TYPE idocsyn-occmax DEFAULT '99'.
PARAMETER upd_flag AS   CHECKBOX        DEFAULT space.
START-OF-SELECTION.
table IDOCSYN
SELECT * FROM idocsyn
         INTO TABLE lt_idocsyn
         WHERE idoctyp = idoc_typ.
READ TABLE lt_idocsyn INTO ls_idocsyn
                        WITH KEY idoctyp = idoc_typ
                                 segtyp = idoc_seg.
IF sy-subrc = 0.
    MOVE ls_idocsyn TO old_idocsyn.
    ls_idocsyn-occmax = occmax.
    IF upd_flag EQ 'X'.
      UPDATE idocsyn FROM ls_idocsyn.
     COMMIT WORK AND WAIT.
      WRITE: 'Table IDOCSYN updated',
             /,'         Idoctype:      ',idoc_typ,
             /'         segment number: ',ls_idocsyn-nr.
      WRITE: /,'OCCMAX changed from',old_idocsyn-occmax,
             ' to ',ls_idocsyn-occmax.
    ELSE.
      WRITE: 'No UPDATE done in table IDOCSYN',
             /,'         Idoctype:      ',idoc_typ,
             /'         segment number: ',ls_idocsyn-nr.
      WRITE: /,'OCCMAX changed from',old_idocsyn-occmax,
             ' to ',ls_idocsyn-occmax.
    ENDIF.
ELSE.
    WRITE: 'no such record in table IDOCSYN'.
ENDIF.
ULINE.
table EDISYN
SELECT * FROM edisyn
         INTO TABLE lt_edisyn
         WHERE idoctyp = idoc_typ AND
               cimtyp = space.
READ TABLE lt_edisyn INTO ls_edisyn
                       WITH KEY idoctyp = idoc_typ
                                cimtyp = space
                                segtyp = idoc_seg.
IF sy-subrc = 0.
    MOVE ls_edisyn TO old_edisyn.
    ls_edisyn-occmax = occmax.
    IF upd_flag EQ 'X'.
      UPDATE edisyn FROM ls_edisyn.
      WRITE: 'Table EDISYN updated',
             /,'         Idoctype:      ',idoc_typ,
             /'         segment number: ', ls_edisyn-posno.
      WRITE: /,'OCCMAX changed from',old_edisyn-occmax,
             ' to ',ls_edisyn-occmax.
    ELSE.
      WRITE: 'No UPDATE done in table EDISYN',
             /,'         Idoctype:      ',idoc_typ,
             /'         segment number: ',ls_idocsyn-nr.
      WRITE: /,'OCCMAX changed from',old_idocsyn-occmax,
             ' to ',ls_idocsyn-occmax.
    ENDIF.
ELSE.
    WRITE: 'no such record in table EDISYN'.
ENDIF.

Outbound error IDoc reprocessing

I have a scenario like whenever an outbound idoc is in error status, should be able to correct the idoc n reprocess it.
Suppose outbound idoc is in status 02. System process code will notify the agent assigned in partner profile. When i execute the workitem and corrected the port and try to reprocess, this status is set to 30. My requirement is once i correct the port status should become 03. How do we acheive this ? (not through report rseout00 )
1. In general scenario how do we handle outbound error idocs?
2. Is system process codes are used only for notifications or error processing?
Inputs will be appreciated regd outbound error reprocessing .
Thanks.

Hi Indira,
1. In general scenario how do we handle outbound error idocs?
You can use transaction BD87 to monitor the IDoc statuses.
and use the following programs to reprocess outbound and inbound error IDoc(s).
RBDAGAI2 - Re-processing of IDocs after ALE Input Error
RBDAGAIE - Reprocessing of Edited IDocs
RBDAGAIN - Process Outbound IDocs with Errors Again
RBDAGAIP - New Posting of Partially Posted IDocs
RBDMANI2 - Manual Processing of IDocs: Post IDocs Not Yet Posted
RBDINPUT
2. Is system process codes are used only for notifications or error processing?
The process code ise used in both ALE and EDI framework to identify the function module or API (Application Programming Interface) to be invoked for subsequent processing. Inbound as well as outbound interfaces use process code but for different purposes. Outbound process codes are stored in table TEDE1, while inbound process codes are stored in TEDE2.
Hoep this will help.
Regards,
Ferry Lianto

AES filing error - Idoc Outbound Processing: EDI number cannot be compiled

Hi Gurus,
We are configuring the AES filing.
we've done the EDI configI and initally we got the error that EDI partner is not maintained. As per the suggestions from this Forum we've added the cusoms office details in geography tab.
Now when we are trying to process the same, we are getting the error "Idoc Outbound Processing: EDI number cannot be compiled"
All suggestions are welcome.........
Thanks in Advance.

Hi Shiva,
Here goes the solution: you need to maintain the Number of the Number Ranges starting with "10" and this applies only to GTS system as this is HARD-CODED in the Program, apart from 10 any number of the number range will result in an "EDI Number Range compilation" error.
Cheers
Harsha

26 Error during syntax check of IDoc (outbound)

Hi Experts
I am using TPSDLS - Idoc(outbound).
When we view in WE02 : for few of the deliveries it is working fine , but for some it is giving the following error
26 Error during syntax check of IDoc (outbound)
Please any one help me out for the same
Thanks & Regards
Shaveta

Please check the segments for the idocs in error status in WE02. The segments in the idoc should be in the same sequence as defined while creating idoc in WE30.
For eg. taking the case of invoic02 idoc.
Segment E1EDP01 cannot come prior to segment E1EDK01.
As in WE30 it is defined to come after E1EDK01\
Please reward the points if this information is useful.

HRMD_A IDocs in Error Status 02

Dear SAP Peeps,
Upon generation of outbound HRMD_A idocs, an error occurs. Error status is "02 - Could not find code page for receiving system".
Can you guys assist me here? What does code page mean? How the error will be solve? The error occurs in every two weeks upon sending the idocs. Sending system is a unicode system while the receiving system is a non-unicode system.
Thanks!

i Think u have run some personnel acitons
than u need to check the table T529A and check have u assigned the feature which standrad in sap for certain acions
for Ex MSN20 MSN10 check these thr PE03
in IMg
check SEt up personnel Acitons

Data Manipulation - IDOC outbound

Hi ALL,
I would like to send material numbers from my SAP system in an outbound idoc to another SAP system.
How can I make sure in my IDOC processing user exit - the material numbers I'm sending could be processed without any errors?
For example -
In our SAP system - Material numbers start with AXXXXX
Other SAP syetem - Material numbers start with NXXXXX
Any input appreciated.

Hi Meghana,
for every idoc there is a message type ..
for every message type there is a function module attaached ( see in we57)..
for every Function module there is a customer exir and Badi available after the segment append..
you need to write your own code under the customer exit..
or
you can go to T-code we02 and put your message type and direction 02 and today's date and execute..
check the latest record and check the status if it is 03 that means success else check the status and error attached
Regards,
Prabhudas
Edited by: Prabhu Das on Apr 20, 2009 10:04 PM

Idoc outbound & inbound

Hi,
I have to extend Idoc , i have extended it by inserting new segments, but how i can handle outbound and inbound things like where i have to do coding.
san

Hi san,
below links might help you.
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2004/helpdata/en/72/c18eff546a11d182cc0000e829fbfe/frameset.htm
http://help.sap.com/saphelp_erp2004/helpdata/en/9c/2744f5fa7464429a13345be4050fb6/frameset.htm
http://www.sappoint.com/ppt/ale.ppt
below details might help you.
WE09 / WE02    IDoc lists according to content. View IDocs via specific IDoc number or business application detail contained within the contents of a segment.
WE05        View IDocs
WE19        EDI test tool. Use to test inbound Function module changes.
WE20        Partner profile configuration. Add partner detail together with inbound and outbound relationships. We also incorporate message control on the outbound IDocs. Utilize the organizational units to trap functional errors for further processing
WE30        Create IDoc extension type
WE31        Segment create
WE57        Assign function module to logical message and IDoc type
WE60        IDoc type documentation tool
WE82        Link Release detail to Extension IDoc Type
BD55         Conversion rule user exit. Link conversion rule user exit to the different system \ partner combinations
BD87         Reprocess IDocs in error or waiting for action. (Both inbound and outbound in 4.6. Use BD88 in prior versions)
BALA        ALE Application Distribution
BALM        ALE Master Data Distribution
reward points for helpful answers and close the thread if your question is solved.
regards,
venu.

Issues in IDoc Sender Scenario:IDoc with errors added

Hi all
Am working on an IDoc to JDBC scenario. In R/3 system, I have created distribution model, partner profile, RFC destination and port.The IDoc is generated and is sent to XI successfully. But in XI , there is no entry in SXI_MONITOR for this (unfortunately IDX5 is not available in the XI server! ;as of now). Instead an entry is made in WE05 and WE02 with stautus 56(IDoc with errors added). In the status record:
status 56 : External segment name E2KOMG003 cannot be interpreted
status 60 : Basic IDoc type COND_A03 could not be found.
And the segments displayed in data record are different from the segments in the data record of the IDoc generated at R/3. (say for E1KOMG at R/3, E2KOMG003 in XI).Earlier the flow was working fine and the DB table was updated successfully. And the entire stuff is believed to be 'unmodified' .
Would any one help in resolving the issue.
Thanks,
Chilanka

Hi,
>>>>I have created partenr profile in R/3.Need I create a partner profile in XI for R/3 system?
no you cannot create any partner profiles in XI
for more about IDOC configuration in XI check :
<a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi"><b>Mastering IDoc Business Scenarios with SAP XI</b></a>
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

SAP to XI IDoc Outbound Error

Similar Messages

Maybe you are looking for