Outbound IDoc - Error 29 - Tcode CI33

Hello,
I'm trying to send IDoc to an external system.
In BD64 the Distribution Model is configured and I also generated the partner profiles.
In WE20 and WE21 everything's OK (ports defined to the LS).
Logical systems also OK.
RFC connection testd and OK.
When I try to send IDoc via CI33 i get the following message of error (WE02):
" Error 29 - Error in ALE service - Entry in outbound table not found. "
And also the Port field is empty.
I can't see what's missing or wrong with it and just run out of ideas.
Any help would be most appreciated!
Thanks!
Carlos Colaço
Edited by: CColaco on Feb 22, 2010 11:06 AM

Hello,
I've double checked it again also on table EDP13 and everything is there as it should be.
Any more ideas?
Thanks in adavance!
Carlos Colaç

Similar Messages

Outbound Idoc error handling through workflow

Hi,
I am trying to set up the workflow for outbound error handling. I found that there is a task TS00007989 which need to set up.
How this task can be triggered when outbound idoc error occurs in the system?
Kr,
Vithalprasad
Edited by: Vittalprasad on Jun 9, 2010 11:52 AM

Hi,
Have a look
Outbound IDoc Error Handling via Workflow
Outbound idoc error handling through workflow

Handling outbound IDOC errors through workflow TS00007989

Hi,
I want to sent an notification e-mail to external mail box when an outbound idoc has an error status. This needs to be achieved through a workflow template.
I noted that there is a standard task TS00007989 in WE40 which is used for handling outbound idoc errors.
Moreover i couldnt find any trigerring events for the above task.
Can any one help me with a step by step guide for achieving this.
Regards,
Krishnakumar

Hi,
the single step task TS00007989 that you see is NOT TRIGGERED thru' any BO's event. It is created by the std. pgm RSEWFERR. If you go to the wflow log of the witem generated by it, you will see the Creator.
And you can control the activation / deactivation of these single step tasks for various inbound and outbound Error IDOC's thru' Transaction WE46.
If you want, create a single step task of your own and maintain that task here. But, you will ahve to know the exact BO like IDOCORDERS or IDOCEMBMAS etc. or look for events triggered by General IDOC objects like IDOCAPPL.
Hope this helps.
venu

Outbound IDoc Error: Status Code 37 'Sender Port' is invalid

Hi
I have an Error when the Outbound IDoc is triggered.
It shows that 'Sender Port in Control Record is invalid'.
Status Code: 37.
I know that there are some issues with the Sender Port Definition.
Please help me out to solve this problem using some checkpoints at each and every step.
Reward Points Assured.
Regards,
Baburaj

Hi Baburaj Manickam
Good
Follow this simple procedure
1) Send an outbound IDOC data(MATMAS) to a flat file on client1(SENDER).
- Create File Port (WE21) for outbound file.
- Maintain Distribution Model (BD64) for sender ->receiver system.
- Create Partner Profile (WE20) for logical system.
- You can use this program RBDSEMAT (t/code BD10) to generate IDoc MATMAS file(s).
_ Then you can FTP the file(s) to receiver system.
2) Upload the flat file as an IDOC on the inbound sytem
which is Client2(RECIEVER).
- Create File Port (WE21) for inbound file.
- Maintain Distribution Model (BD64) for receiver -> sender system.
- Create Partner Profile (WE20) for logical system.
- You can use this program RSEINB00 to upload IDoc MATMAS file(s).
INBOUND IDOC PROCESSING:
Firstly attach your idoc to a process code.
In the process cod you can tell the system that the specified program should be triggered whenever an idoc of that type comes to the system.
Then you want to have a Z-function module for your idoc processing, if I understand correctly.The steps should be:
1. Create a z function module for idoc inbound posting (copy from a function module idoc_input_*).
2. Set Function Modules as Inbound: - Transaction BD51
3. Assign Function Modules to Logical Messages and Idoc types:- Transaction WE57
4. Create process codes : Transaction WE42, and link the z-function module.
5. Create partner profile: transaction WE20 and attach the message type and process code.
6. In the Z- function module, extract data from the idoc segments, do whatever processing you want to do, and then call BAPI_CREATE_SALES_ORDER_FROMDAT2.
Try the Trasaction WE19 for testing your inbound and outbound IDOCs
Good Luck and Reward me for the same
Thanks
Ashok.N

Outbound IDoc Error status 26

Hello All,
I have got one issue in outbound IDoc scenario. ( Basic type is ORDERS02 ). The IDoc failure status shown in WE02 as 26 (Error during syntax change of IDoc outbound). To solve this I am trying to Repeat Output through VA02 ( as this is related to salesorder) , it does not give the same error status 26 . Rather it gives status as 30 i.e. IDoc Ready for dispatch which I then process through BD87 gives status 03 i.e. Data passed to port OK .
I repeted this for 4-5 times, everytime I do not get any error status (as that was occured at the very first time) .
Kindly suggest what should be done to overcome this.
Thanks in anticipation...

Hi Ubhaka,
In that case you should check the segments associated with the message type.Also, check the partner profile settings.
At first (when you got the error) what was IDOC generation method - was it through VA02 or some custom/standard program? If the methods were different for generating Idocs then check the program.
Hope that helps!
Regards,
Saba

Outbound idoc error message

Dear all,
When i am manually create a direct request for POS outbound, the system shows the error message as below. It cannot generate an outbound idoc. Do anyone know how to detect this error and how to solve this problem?
Error message:
Processing Status
Recipient: XX01
IDocs created
     None
     Trigger file for status ID: 00000000260056
     does not have to be created       No messages needed
Thanks and regards
Chris

Dear all,
i have solved the problem. thanks you for your attention.
Chris

Outbound Idoc Error Handling by creating workitem

Hi ,
I have a question regarding the Outbound IDoc.
What we need to implement is to create a workitem in SAP Inbox when there is a failure on the Outbound IDoc.
in a similar way as we do for the inbound IDoc's.
Is there is a standard way of achieving this ?
Thanks in advance

Hi Ankur,
Have you looked standard program RBDCONCH?
Regards,
Ferry Lianto

Outbound IDOC( Error passing data to port)

Hi,
We have an interface running daily configured such that the idocs are converted to files and placed on a directory path.
All the idocs are processed successfully but for one hour the idocs failed and the error message says:
Status: Error passing data to port
Error at OPEN (Directory path) with operating system error msg.:No such file or directory.
The missed data from the error idocs have been sent via PFAL.
But again after this one hour the idocs were successfully posted for the same directory path.
Please let me know what the issue can be here or how can we avoid this.
Thanks.

Hi
*Some times it may happen that IDOC doesnt reach to the port , in case if you are using Transactional RFC port so*
*you can use the report RSEOUT00 for sending the IDOC to port .*
*Hope it may help you .*

Outbound idoc error

hi experts.
Iidoc type is ACC_DOCUMENT03. for header details(bkpf values) idoc is sucess .
while passing item details along with header details it is giving error status 26.
LOOP AT gt_bkpf INTO gs_bkpf.
    gs_e1bpache09-doc_date   = gs_bkpf-bldat.
    gs_e1bpache09-doc_type   = gs_bkpf-blart.
    gs_e1bpache09-comp_code = gs_bkpf-bukrs.
    gs_e1bpache09-pstng_date = gs_bkpf-budat.
    gs_e1bpache09-fis_period = gs_bkpf-monat.
    gs_e1bpache09-ref_doc_no = gs_bkpf-xblnr.
    gs_e1bpache09-header_txt = gs_bkpf-bktxt.
    gs_e1bpache09-reason_rev = gs_bkpf-stgrd.
    gs_e1bpache09-ac_doc_no =   gs_bkpf-belnr.
    gs_idocdata-segnam = c_e1bpache09.
    gs_idocdata-sdata = gs_e1bpache09.
    APPEND gs_idocdata TO gt_idocdata.
    CLEAR gs_idocdata.
    LOOP AT gt_bseg INTO gs_bseg WHERE bukrs EQ gs_bkpf-bukrs
                                 AND   belnr EQ gs_bkpf-belnr
                                 AND   gjahr EQ gs_bkpf-gjahr.
      IF gs_bseg-bschl EQ 40 OR
         gs_bseg-bschl EQ 50.
        gs_e1bpacgl09-ITEMNO_ACC    = gs_bseg-BUZEI.
        gs_e1bpacgl09-ac_doc_no =   gs_bseg-belnr.
        gs_e1bpacgl09-acct_key    = gs_bseg-bschl.
        gs_e1bpacgl09-gl_account = gs_bseg-saknr.
        gs_e1bpacgl09-tax_code    = gs_bseg-mwskz.
        gs_e1bpacgl09-costcenter = gs_bseg-kostl.
        gs_e1bpacgl09-sales_ord   = gs_bseg-vbel2.
        gs_e1bpacgl09-po_number   = gs_bseg-ebeln.
        gs_e1bpacgl09-item_text   = gs_bseg-sgtxt.
        gs_e1bpacgl09-p_el_prctr = gs_bseg-zz_kotsl.
        gs_e1bpacgl09-cs_trans_t = gs_bseg-zz_exptyp.
        gs_idocdata-segnam = c_e1bpacgl09.
        gs_idocdata-sdata = gs_e1bpacgl09.
        gs_idocdata-hlevel = 2.
        APPEND gs_idocdata TO gt_idocdata.
        CLEAR gs_idocdata.
      ELSE.
         gs_e1bpacar09-ITEMNO_ACC    = gs_bseg-BUZEI.
       gs_e1bpacar09-ac_doc_no =   gs_bseg-belnr.
        gs_e1bpacar09-pmtmthsupl = gs_bseg-bschl.
        gs_e1bpacar09-gl_account = gs_bseg-saknr.
        gs_e1bpacar09-item_text   = gs_bseg-sgtxt.
        gs_idocdata-segnam = c_e1bpacar09.
        gs_idocdata-sdata = gs_e1bpacar09.
        gs_idocdata-hlevel = 2.
        APPEND gs_idocdata TO gt_idocdata.
        CLEAR gs_idocdata.
      ENDIF.
      gs_e1bpaccr09-ITEMNO_ACC    = gs_bseg-BUZEI.
      gs_e1bpaccr09-currency    = gs_bkpf-waers.
      gs_e1bpaccr09-amt_doccur = gs_bseg-wrbtr.
      gs_idocdata-segnam = c_e1bpaccr09.
      gs_idocdata-sdata = gs_e1bpaccr09.
      gs_idocdata-hlevel = 2.
      APPEND gs_idocdata TO gt_idocdata.
      CLEAR gs_idocdata.
please provide me solution.

Hi Suma,
LOOP AT gt_bkpf INTO gs_bkpf.
gs_e1bpache09-doc_date = gs_bkpf-bldat.
gs_e1bpache09-doc_type = gs_bkpf-blart.
gs_e1bpache09-comp_code = gs_bkpf-bukrs.
gs_e1bpache09-pstng_date = gs_bkpf-budat.
gs_e1bpache09-fis_period = gs_bkpf-monat.
gs_e1bpache09-ref_doc_no = gs_bkpf-xblnr.
gs_e1bpache09-header_txt = gs_bkpf-bktxt.
gs_e1bpache09-reason_rev = gs_bkpf-stgrd.
gs_e1bpache09-ac_doc_no = gs_bkpf-belnr.
gs_idocdata-segnam = c_e1bpache09.
gs_idocdata-sdata = gs_e1bpache09.
APPEND gs_idocdata TO gt_idocdata.
CLEAR gs_idocdata.
LOOP AT gt_bseg INTO gs_bseg WHERE bukrs EQ gs_bkpf-bukrs
AND belnr EQ gs_bkpf-belnr
AND gjahr EQ gs_bkpf-gjahr.
IF gs_bseg-bschl EQ 40 OR
gs_bseg-bschl EQ 50.
gs_e1bpacgl09-ITEMNO_ACC = gs_bseg-BUZEI.
gs_e1bpacgl09-ac_doc_no = gs_bseg-belnr.
gs_e1bpacgl09-acct_key = gs_bseg-bschl.
gs_e1bpacgl09-gl_account = gs_bseg-saknr.
gs_e1bpacgl09-tax_code = gs_bseg-mwskz.
gs_e1bpacgl09-costcenter = gs_bseg-kostl.
gs_e1bpacgl09-sales_ord = gs_bseg-vbel2.
gs_e1bpacgl09-po_number = gs_bseg-ebeln.
gs_e1bpacgl09-item_text = gs_bseg-sgtxt.
gs_e1bpacgl09-p_el_prctr = gs_bseg-zz_kotsl.
gs_e1bpacgl09-cs_trans_t = gs_bseg-zz_exptyp.
gs_idocdata-segnam = c_e1bpacgl09.
gs_idocdata-sdata = gs_e1bpacgl09.
gs_idocdata-hlevel = 2.
APPEND gs_idocdata TO gt_idocdata.
CLEAR gs_idocdata.
ELSE.
gs_e1bpacar09-ITEMNO_ACC = gs_bseg-BUZEI.
gs_e1bpacar09-ac_doc_no = gs_bseg-belnr.
gs_e1bpacar09-pmtmthsupl = gs_bseg-bschl.
gs_e1bpacar09-gl_account = gs_bseg-saknr.
gs_e1bpacar09-item_text = gs_bseg-sgtxt.
gs_idocdata-segnam = c_e1bpacar09.
gs_idocdata-sdata = gs_e1bpacar09.
gs_idocdata-hlevel = 2.
APPEND gs_idocdata TO gt_idocdata.
CLEAR gs_idocdata.
ENDIF.
gs_e1bpaccr09-ITEMNO_ACC = gs_bseg-BUZEI.
gs_e1bpaccr09-currency = gs_bkpf-waers.
gs_e1bpaccr09-amt_doccur = gs_bseg-wrbtr.
gs_idocdata-segnam = c_e1bpaccr09.
gs_idocdata-sdata = gs_e1bpaccr09.
gs_idocdata-hlevel = 2.
APPEND gs_idocdata TO gt_idocdata.
CLEAR gs_idocdata.
Can you please tell me why this additional record is required..Please try to concentrate on this part may be it will be helpful.
Regards.
SRinivas

Outbound idoc error - REFINT field

I am trying to send orders.orders05 idoc from ecc to xi
the message that I get in we02 in ECC is
EDI: Field REFINT in control record with value 'T080902134731A ' is invalid
Does somebody knows where this field is configured ?
when I edited this idoc in we02 and erased this value the process was sucessfuly
but when I try using we19 it assigns this value automatically
thx
Shai

u ask ur functional person wat is the importance of this field.
I think it is not required and if it is required then the data which is coming is wrong which is not accepted by this element.
and accordingly u trigger the idoc.
chirag

Query on User exit for outbound idoc

Hi ,
Can u all pls help me out to solve these queries
1. when we extend a new segment (at we31) and create a new idoc type(at we30), say,for DELVRY05 idoc type-what is the logic to be written inside the Exit(at Transaction code - CMOD -where a project is created and the exit is found for the enhancement) ,to view our extended segment -that needs to be appended (viewed below the existing segment)at we02?
2.Can we delete the outbound idoc generated with errors from development server?
3.How to recify the outbound idoc errors-like runtime,syntax,port unreachable errors(at the status record and data records listed inside we02 transaction code)?
4.How to check values populated at our extended segment inside we02-Transaction code.
say,the logic required inside the exit may be,
Select single ladel from eikp into wa_ladel where refnr = (inbound delivery)
In this,the ladel exists in eikp table as EIKP-LADEL field.
The main thing is- an inbound delivery is created at transaction code VL31N for which an outbound idoc(using an Exit )should be generated with few more validations for the fields like
i) ekpo-pstyp(corresponding IDOC segments are E1EDL26-PSTYV )
ii)ekko-lifnr and ekko-lichn(E1EDL24-LICHN )
Segment name-item(at transaction we63) Segment no.
iii) E1TXTP8-TDLINE => SCAC Code. 11
 E1TXTH8-TDID => Z001. 10
iv) E1TXTP8- TDLINE => Primary seal number. 13
 E1TXTH8-TDID => Z002. 12
v) E1TXTP8- TDLINE => Secondary seal number. 15
 E1TXTH8-TDID => Z003. 14
5.Can you help me out to know the logic by which we can validate few fields from different tables like eikp,ekpo and ekko inside our Exit (in the project created at CMOD transaction?
With Regards,
Srividya

Hi Swati Choudhary,
please ask your question in devlopment forum, please see its 2 yr old thread, and i don;t think Phileas Fogg still remember his stuffs.

Handle Idoc errors through workflow

How to handle inbound idoc errors through workflow and How to handle outbound idoc errors through workflow
Thanks,
Asha

in transaction SALE go to menu Basic Settings/Perform Automatic Workflow Customizing
then in WE46 you can assign a workflow task to various errors
in partner profiles (WE20) you can assign post processing agent per partner/message type

Automated error email notification when outbound IDOC fails

Hi,
The requirement is that whenever the outbound IDOC of message type PAYEXT, basic type PEXR2002, fails, then email has to be trigerred to a group id.
I had suggested to write a report program that runs as a job. If the IDOC goes to error status then mail will be sent from this report. Client prefers it to be done through workflow.
There is a standard process code for outbound IDOC failure handling EDIO (we40). standard task 7989 has been assigned to this process code. I dont want to modify this standard task as I am not sure of impact.
Terminating event for this task is 'ERRORPROCESSCOMPLETD'.
I have developed the workflow that has trigerring event 'ERRORPROCESSCOMPLETD' and bound with the IDOC number. This will send mail to the group id with the IDOC details
Now issue is that, I am not sure if standard process EDIO will be trigerred automatically, or should we configure anywhere. Since this is standard outbound IDOC, I am not able to add the process code in partner profile.
Please give your inputs or any other alternate solution to send mail through workflow when outbound IDOC fails.
Thanks in advance.

Hi,
I guess in your outbound partner profile for PAYEXT. you need to add process code EDIO in message control TAb. WHich will cause to trigger the workflow which will send the notification.

Error while creating an outbound idoc using idoc type delvry02

hi,
i getting the following error while creating an outbound idoc(outbound shipping notification) using message type " DESADV" and IDOC TYPE " DELVRY02"
ERROR:
" SPECIFY EITHER ADDRESS NO OR ADDRESS HANDLE"
MESSAGE NO: AM053
Help would be appreciated.
regards
leo

The message is kind of self-explanatory. It seems that some address (delivery address ?) is required but is missing from the IDoc. If it's a syntax error, then the segment with error will appear in red in WE05 transaction.
It is also possible that you have filled some field that you should have left blank and now SAP is trying to find an address based on that field.
Check your IDoc contents. It's really hard to tell from the distance since the requirements and configuration could be very different in different systems. Sometimes the OSS note search by message ID and number is also helpful.

Procedure to Error Out Outbound IDocs

Hello,
 I have a Requirement in which I am using ORDERS05 IDoc Type and extended it to ZORDER05 to populate Custom Fields and sending the Purchase Order Outbound IDoc to the Vendor from SAP System. Now, my requirement is that if any of the Custom Fields are not maintained in SAP and not populated in the IDoc, I need to Error Out the IDoc with Error Status 26. I am currently working on the SAP ECC 5.0. I have implemented similar Error Handling Mechanism earlier by using Enhancement Framework as I was working in ECC 6.0 environment where I've added the Code by Creating an Enhancement Implementation in the Function Module IDOC_CREATE_ON_DATABASE. But since ECC 5.0 does not have the Enhancement Framework feature, please let me know how to achieve this.
Thank You,
Venkata Phani Prasad K

Hi
why don't you try using the standard method for validation of data?
By implementing the customer-function EXIT_SAPLEINM_002 or BAdI MM_EDI_ORDERS_OUT you can make checks of completeness of the idoc segments (in your case, additional custom data) and, if they were not complete, report an error message raising the exception DATA_NOT_RELEVANT_FOR_SENDING
ie
if <Idoc Custom Field> is initial.
MESSAGE ID 'S1'
 TYPE 'E'
 NUMBER '333'
 WITH Additional data are incomplete'
 RAISING data_not_relevant_for_sending.
endif.
Thus you have the evidence of the error in the processing log of the output message while the IDOC is not created.
The solution works very well and is not invasive.
Regards.
Andrea

Outbound IDoc - Error 29 - Tcode CI33

Similar Messages

Maybe you are looking for