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

Similar Messages

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

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

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

IDOC treking through workflow

Hi All,
I am working on a requirement where we need to trek IDOCs through workflow. I have got a standard task(TS30000206) which does error handling for outbound IDOC. If i send 10 outbound IDOC and 9 are processed successfully they should be changed with the success status. But the 1 which could not get the response/acknowledgment back in 24 hours should be marked as failed??
My question is How can i setup a workflow to error out the IDOCs which are unable to make the postback/ackn within 24 hours?
Your quick response is highly appreciated....
Thanbks
Ritesh

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

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

Triggering E-mail for failed outbound idoc (Without using workflow)

Hi Experts,
In my secnario Idoc to file, where any failures of Idoc( Inbound/Outbound ) at SAP R/3 side will generate and send Emails to the required group. How to do this without using Work flow. If anybody knws please help me out its very urget.
Regards,
venkatesh

Hi,
Create a Distribution list using SO23 and add Users whom to recieve messages.
Modify your Inbound function module to handle if idoc failed to post by calling the function module: SO_NEW_DOCUMENT_SEND_API1
Reward points if it is helpful.
Ashok

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

IDOC Error Notification - WorkFlow

ALE-IDOC Master Data Distribution
We have a busines requirement to email/notify an agent when an incoming idoc has an error-status. Please let me know how to proceed with this.
Thanks in advance!

Hi,
if you are using the Inbound FM to process the IDoc, then you can very well use the work flow.
after processing the IDoc you will come to know the status of the IDoc .if any errors are there you can generate workflow.
Regards
vijay

IDoc Error Processing workflow

Invoices are posted from SRM to ECC as IDocs whose message type is BBPIV. When there is an error in the IDoc input such as invalid IO and GL, invalid company code etc., these IDocs will be moved to status 51.
When IDoc is moved to status 51, work item need to be sent to approvers saying this IDoc has an error and need to be corrected. For this a workflow task needs to be developed.
In our system, there are two types of IDoc invoices sent to ECC. One is of type INVOIC01 and another is of type BBPIV01. There already exists a standard task TS00008057 which is activated for the event INPUTERROROCCURREDMM for IDOCINVOIC object type.
I shouldn't use the same event (INPUTERROROCCURREDMM) and IDoc object type(IDOCINVOIC) for BBPIV01, because responsible agents for both type of invoices are different in our company.
Please help us in getting this resolved. Also let me know if my approach is wrong towards this problem.
Thanks,
Rajesh

Hi Rajesh,
Using the same BOR object and event for two different idoc types is not necessarily wrong. There are ways to differentiate the responsible agents based on the idoc type if needed.
Here is how I would solve this:
Prerequisite: you need to make sure that event IDOCINVOIC.INPUTERROROCCURREDMM is triggered when your BBPIV01 iDoc is in error. To check that, you can activate the event trace and test your idoc (activate with tx SWELS, display with tx SWEL).
If the event does not trigger then you need to find out which event is getting triggered (using the event trace as well).
Now the serious business:
1. Create a copy of standard task TS00008057 that will be used for when BBPIV01 iDocs are in error.
2. Link this task to your event IDOCINVOIC.INPUTERROROCCURREDMM in transaction SWETYPV
3. Check in SWO1 if you have an attribute that gives the idoc type (or anything else which you can use to determine wich workflow should start in each case).
If not you need to create a subtype of IDOCINVOIC and in the subtype create an attribute that returns the iDoc type. Then you would need to delegate IDOCINVOIC to your subtype.
4. Create start conditions (tx SWB_COND) in which you check that TS00008057 starts only when idoctype is INVOIC01 and your new task starts only when idoc type is BBPIV01.
Cheers,
Patrick

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ç

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

Handling Batch Input errors in workflow

Greetings Friends,
I got a Subworkflow (Pa. process) to get aproves to unblock a Salesdocument.
After everyone aproves it, the process return to my main-workflow for a Batch input inside in a background task. But the batch input can result in somekind of error and fail. At this time, the workitem is already "lost" (processed?).
There is a way to recreate the workitem for another user? (I got one hint here at SDN about FM SAP_WAPI_PUT_BACK_WORKITEM)
There is a container that saves the last workitem processed?
Att,
José.
<Subject edited. Please use a meaningful subject, see the Rules of Engagement (link at the top of each forum) for further info>
Edited by: Mike Pokraka on Dec 16, 2008 1:54 PM

Hi Sunny,
What release are you on? If the workflow errors out, then it must be telling you some sort of exception message.
Either at the header level, or at the individual task, where the red lights are. (if you are on ECC6, you may need to hit CTRL/P to get to the more comprehensive WF Technical Log).
By all means, populate a custom table with exceptions if you must, or pass the error into the workflow container, but if your task goes into error, it doesn't complete, therefore it can't write the error into the container.
Give standard SAP functionality a try before building too much into capturing the exception. It's already done for you, and it works.
Hope this helps,
Sue

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

Handling outbound IDOC errors through workflow TS00007989

Similar Messages

Maybe you are looking for