WORKFLOW FOR IDOCS

hi all
are there any standard w/f for idoc error handling.
i have a senarios in which a series of mails have to be send to different people when idoc error occurs witha workitem.
any pointeers will be really helpfull
regards
navjot

hai
these are some of the standard workflow
TS00008068----
Process code does not exist;
Error during forwarding to ALE services
TS00007989----
Error during forwarding using RFC;Error writing file
TS30000078----
Conversion error in EDI subsystem
TS30000020----
Inbound: Error reading file; Outbound:
Error generating IDoc from an MC record
TS70008037----
No process code in the additional partner profile MC parameters; Error when writing the application data in the IDoc.
hope it will be helpfull for u.
regards
rose.

Similar Messages

Workflow for Idoc errors

Hi,
I am new to workflow, I got a requirement for idoc error handling in workflow.
If the idocs fail a notification needs to be sent to an appropriate personnel. If it fails due to configuration or technical issue then the notification needs to go to the tech personnel ( A distribution list ) . If it is a data error then notification needs to go to functional personnel ( distribution list ).
Here i have created a WF using Object IDOCAPPL. Please let me know how i can handle this condition and want some document on orginization structure.
I have refered to documents in Saptechinical and Sdn.Plz let me have some other ideas and documents.
thanks
Arun.

You can create a custom rule and inside that you can have your own condition and populate the users accordingly.
Distribution list..you can create in SBWP itself.

Error monitoring through workflow for idoc with message type ORDRSP

Hi All,
Through WE19 I am trying to post a failed idoc ie idoc in 51 status for message type ORDRSP to check whether the event IDOCORDRSP-INPUTERROROCCURED event is triggering or not. Though the idoc is going into 51 status and partner profile is maintained I cannot find this event in SWEL. I checked in fm IDOC_INPUT_ORDRSP fm and found that workflow_result is 99999.
Can anybody tell me why the event is not getting triggered for the message type ORDRSP or where do I debug to find out what is going wrong. IDOC_INPUT_ORDRSP fm is getting called from BUS2012 'S method confirmfromORDRSP which is very strange.So I am not getting where do I debug.
Regards
Suchandra

Hi All,
Solved it by my self.. To trigger the event we need to populate the EDIDC control record in WE19 and press standard inbound button 'not test by inbound fm) and then the inputerroroccured event will trigger...
Regards
Suchandra

Vendor Confirmation workflow ( TS00008075 ) issue for IDOCs in Error ( 51 )

Hi All,
          When IDOCs (Basic type: ORDERS02, Message type : ORDRSP ) goes in error with status 51 & comes to SAP system it calls event u2018INPUTERROROCCURREDu2019 which is correct but it creates problem when it get re processed as it triggers event u2018INPUTSUCCESSu2019 resulting in firing vendor confirmation workflows to respective user ( this batch job re process each ORDRSP IDOC twice a day & hence 2 workflows per IDOC in error to clientu2019s inbox by triggering event u2018INPUTSUCCESSu2019).
Could you please tell me why these IDOCs are triggering event u2018INPUTSUCCESSu2019 in case of error ( status 51 ) when they get RE PROCESSED. These kind of Idocs must only trigger u2018INPUTERROROCCURREDu2019 once and should not create anything when these get reprocessed. Please note that these issues arise after EHP4 upgrade. Please let me know if any setting is there for triggering Vendor COnfirmation workflow ( TS00008075 ) when IDOCs in error get re processed.
Please help us , thanks.
Regards,
Kartikey Rawat.

Hello Kartikey Rawat !
                    INPUTSUCCESS event gets fired just because it is configured as terminating event in the task.
                    If you don't want this event to get fired, either you can deactivate it or delete the bindings related to the event INPUTSUCCESS(doing so should not affect other two terminating events that may be required for you scenario) .
                    If you want know why it is fired, you can get to know in debug mode or check whether the event is defined through related function modules configured in WE57,BD51,WE42 AND WE20 transaction codes.
                    In WE05 or WE02 transactions, you will get error description.Based on it too, you can figure out the reason.
Regards,
S.Suresh

Enable service of objects -workflow overview-workflow log for IDOCS?

Hi everyone,
I need to enable service of objects -workflow overview-workflow log for IDOCS. Using object key i know how to go to log.Users need that functionality to be enabled for Idocs.For po and pr I can see so its not parameter settings.I feel its configuration somewhere I dont know where?
Can someone help?
Thanks in advance..

Hi VJ,
I'm facing the same issue, the workflow overview is not displaying the log from ME52N. But i have delegate my business object. Is there anything need to be done further.
Thanks & Regards,
Tina

Workflow notification is not tiggered for IDoc of message type 'WPUWBW'

Hi All,
        I would like to know the setting up of workflow notification for IDoc message type 'WPUWBW' (idoc of different message type is getting notified). Please provide pointers and also the steps for the above issue.
Regards,
PSS

Hi Ferry,
System checks for the IDOC version and then calls the EXIT if the versions are different .Following is the code snippet that ensures the above thing in include LBD11F0T :
Change IDOC version if target <> current version.
IF F_EXCEPTION-MSGTY IS INITIAL
    AND (    F_IDOC_CONTROL-IDOCTP <> TARGET_IDOCTP
          OR F_IDOC_CONTROL-CIMTYP <> TARGET_CIMTYP ).
    PERFORM CHANGE_IDOC_VERSION TABLES   T_IDOC_DATA
                                USING    TARGET_IDOCTP
                                         TARGET_CIMTYP
                                CHANGING F_IDOC_CONTROL
                                         CHANGED_FLAG
                                         F_EXCEPTION.
ENDIF.                               "End of if subrc = 0
Have you tested it ? Pls suggest if I am wrong somewhere.
Thanks and Regards
Gurpreet Singh

Workflow for inbound idoc failures

Hi Gurus,
Can anybody please point me to a place where i can start to see how i can setup workflow to notify users via SBWP whenver there is an inbound idoc error happens. We want to derive the standard functionality to its fullest even before thinking of putting any custom code. I'm specifically looking for hte order acknowledgemetns and shiipping notifications errors of idocs coming from the vendor
Thanks
anusha
Edited by: anusha vemulapati on Jul 2, 2011 4:43 PM

Hi Anusha,
The simplest way is to link the partner profile to a specific user ID. This is done in trs WE20 - you have the link to the WF recipient both generally for the partner (on the initial screen of WE20 when the partner has been selected) and specifically for the different message types - double-click on the inbound message type and choose the tab "Post processing - permitted agent".
You link the partner profile to a specific user by choosing the user type = "US" (user") and then specifying the user name below it. If you want several users to receive the same WF, you can link the partner profile to another user type, e.g. O = Organisational unit. Then you link the users to the organisational unit in trs PPOME.
As far as I remember, the WF for IDoc's in error is activated in the standard system, i.e. the setting above shall be sufficient.
BR
Raf

Workflow for INBOUND IDOC

Hi,
I want to set you a workflow for one IBOUND idoc coming via edi partner. I want to use the organization units and then assign the user to it. what are the steps required for setting up a new workflow totally from the start for a IDOC / Message type and config.
Thanks in adv
/Manik

STEP 1.       USE   SALE -> Error Handling
STEP 2.   Go To Basic Workflow Settings.Use Auto-customise button to allow the system to configure most of the options.
STEP 3
a)Go to SAP MENU -> TOOLS-> BUSINESS WORKFLOW ->
DEVELOPMENT ->DEFINITION TOOLS->TASKS
b) Create a customised task putting IDOCCLFMAS for example   as object type and    INPUTFOREGROUND as object method.
c)Associate the triggring event InputErrorOccurred with the standard task.
d)Associate the terminating event InputFinished with the standard task
e) Assign appropiate agent to the customised task. For this GO TO
     Additional data -> Agent assignment -> Maintain
STEP 4 -- Go to transaction WE20.In the partner profile of the message type CLFMAS enter for the post processing permitted agent.Enter the agent type (Organisational unit,Workcenter,Job,Person,Position or User),agentId and the language.
STEP 5- In case of any error in processing of Idoc a workflow notification is sent to concerned agents.The message is sent to the inboxes of concerned persons which indicates which interface has erred,the associated IDOC number ,status of the IDOC and the date and time of error.
Regarding the complete set up you can check the workflow tutorial in help.sap.com.
regards
Aveek

Trigger workflow when IDOC Status 51 & with Basic Type "ORDERS003"

Hi Experts,
Can any one explaine how to create worlflow for "When Idoc status is 51 with the combination of Basic Type "ORDERS003" . If this condition will satisfy i need to send a mail using worklflow. For this one Bussiness type is BUS2102".
Can you explaine any one please i am new to Workflow.
Regards,
Sri

Hi,
Please refer to the below thread. Hope it helps.
Triggering workflow upon idoc fail
Regards,
Sridhar

Materials for idoc

Hi am interested to learn about idocs can you provide me some useful links

Hi saranya srithar ,
IDoc is an Intermediate document that holds application data.
A container used to exchange data
It is independent of the complex SAP structure to store data.
It serves as the vehicle for data transfer.
IDoc Type defines the structure and format in which the data is exchanged.
It is similar to a structure in SAP
IDoc data is an instance of IDoc Type
IDoc acts as a standard SAP interface to exchange business data through ALE.
From an SAP system, an IDoc can be sent to and received from
An SAP R/3 system
An SAP R/2 system
An EDI subsystem
Any third-party application software
Segments . Idoc data is arranged in Rows, The rows make up segments of an idoc. Each segment consists of fields/segments. Fields can contain data.
These r all the t/codes which we will come across in IDocs:
TCODE     TTEXT
BD10     Send Material
BD100     IDoc display object channel view
BD101     Consistency check
BD102     Outbound registry
BD103     Inbound registry
BD104     maintain tbd53
BD105     Maintain Supported Business Objects
BD11     Get Material
BD12     Send customer
BD13     Get customer
BD14     Send vendor
BD15     Open vendor
BD16     Send Cost Center
BD17     Get Cost Center
BD18     Send General Ledger Account
BD19     Get General Ledger Account
BD20     IDoc passed to application
BD21     Select change pointer
BD22     Delete change pointers
BD23     Delete serialization data
BD24     Send Cost Elements
BD25     Send Activity Type
BD26     Get Activity Type
BD27     Send cost center activity prices
BD28     Send obj/cost element control data
BD30     Distribute material object list
BD31     Distribute document object list
BD32     Distribute plant allocations(matBOM)
BD33     Distribute material variants (ALE)
BD34     Distribute order BOM
BD35     Send Business Process Groups
BD36     Send Business Processes
BD37     Send Business Process Price
BD40     Read change pointer for group
BD41     Dispatch IDocs for group
BD42     Check IDocs for group
BD43     Post IDocs for group
BD44     Assign Message Types to Serlz. Group
BD47     Dependencies between methods
BD48     Dependency method - message
BD50     Activate Change Ptrs for Mess. Type
BD51     Maintain function modules (inbound)
BD52     Activ.change pointer per chng.doc.it
BD53     Reduction of Message Types
BD54     Maintaining Logical Systems
BD55     Maintain IDoc Conversion
BD55OLD     Maintain IDoc Conversion
BD56     Maintain IDoc Segment Filters
BD57     Maintain link and serialization ty.
BD58     Convert organizational units
BD59     Allocation object type -> IDoc type
BD60     Additional data for message type
BD61     Activate Change Pointers - Generally
BD62     Define Segment Conversion Rule
BD62OLD     Define Segment Conversion Rule
BD63     Transport ALE Tables of Message Type
BD64     Maintenance of Distribution Model
BD65     Maintain IDoc type required fields
BD66     IDoc type field -> change doc.field
BD67     Maintain methods (inbound)
BD68     Maintain Lists
BD68OLD     Maintain Lists
BD69     Assignment of Message Type to IDoc
BD70     Synchronize Number Ranges
BD71     Define FM for dependent bus. object
BD72     Activate Events
BD73     Reposting of IDocs (ALE)
BD75     Convert IDoc Status
BD77     Distribution of control data
BD78     Monitoring control data distribution
BD79     Maintain IDoc Conversion Rules
BD79OLD     Maintain IDoc Conversion Rules
BD81     Filter objects parameter filtering
BD82     Generate Partner Profiles
BD83     Send IDocs after an ALE error
BD84     Post IDocs after ALE error
BD85     Consistency check for transfer
BD86     Consistency check for sales
BD87     Status Monitor for ALE Messages
BD89     Control data model. - initial screen
BD91     Send Characteristic
BD92     Send Class
BD93     Send Classification
BD95     Specify ALE object types
BD96     filter objects of receiver determin.
BD97     Assign RFC dest. to Logical Systems
BD98     Consistency Check Workflow Connectn.
BD99     Message type dependencies
WE02     Display IDoc
WE05     IDoc Lists
WE06     Active IDoc monitoring
WE07     IDoc statistics
WE08     Status File Interface
WE09     Search for IDocs by Content
WE10     Search for IDoc in Archive
WE11     Delete IDocs
WE12     Test Modified Inbound File
WE14     Test Outbound Processing
WE15     Test Outbound Processing from MC
WE16     Test Inbound File
WE17     Test Status File
WE18     Generate Status File
WE19     Test tool
WE20     Partner Profiles
WE21     Port definition
WE23     Verification of IDoc processing
WE24     DefaultValuesForOutboundParameters
WE27     DefaultValues for Inbound Parameters
WE30     IDoc Type Development
WE31     Development IDoc Segment
WE32     Development IDoc View
WE34     Object for Display of XML IDocs
WE40     IDoc Administration
WE41     Process codes, outbound
WE42     Process codes, inbound
WE43     Funct.module: Status record display
WE44     Partner Types and Checks
WE45     Forward (inbound) (V3, EDILOGADR)
WE46     Error and Status Processing
WE47     Status Maintenance
WE50     System process codes: Texts
WE51     System process codes: Change texts
WE54     FMs for changing file names
WE55     Function Module for Path Names
WE56     IDoc Administration
WE57     Assignment Messages for Appl. Objs
WE58     Status process codes: Texts
WE59     Change status process codes
WE60     Documentation for IDoc types
WE61     Documentation for IDoc record types
WE62     Documentation for segments
WE63     Documentation
WE64     Documentation message types
WE70     Conversion: Basic types
WE71     Conversion: Extensions
WE72     Conversion: IDoc types
WE73     Conversion: Logical messages
WE81     Logical message types
WE82     Assign Messages for IDoc Type
WE84     Assignment of IDoc and appl. fields
WE85     Create Rule Names
WEBU     Printing Labels via Assortment List
WEDI     EDI Basis
WEINBQUEUE     IDoc Inbound Queue
WEKF     Purchase order SAP Retail
WEL0     Forward (inbound) (EDILOGADR)
WEL1     EDI: Interface Invoice for EDILOGADR
WELI     Maintain Status Groups
cheers!
gyanaraj

Tcode for IDOC

Dear friends ,
can any one give me important Tcodes for IDOC & workflow
Reddy

Tcode list for ALE IDOC:
ALE / EDI/ IDOCS TRANSACTION CODES
Transaction Code     Description
WE02     List Of All Idocs Created. (Default, Additional, EDI)
WE05     List Of Idocs Created.    (Standard, Additional)
WE06     Active Monitoring For Idoc Processing.
WE07     Idoc Statistics.
WE08     Display View u201CFile Statusu201D:Overview-Path Name.
WE09     Idoc Search For Business Contents (Database).
WE10     Idoc Search For Business Contents (Archive).
WE12     Modification Of Outbound File, Triggering Inbound Processing.
WE14     Process All Selected Idocs.
WE15     Selection Program For Issuing Output.
WE16     Trigger Inbound Processing.
WE17     Trigger Status Processing.
WE18     Generate Test Status File For Outbound Idocs.
WE19     Test Tool For Idoc Processing
WE20     Partner Profile.
WE21     Ports In Idoc Processing.
WE23     Display Test Catalog Test Idoc Interface.
WE24     Maintain Table View. Direction-1.(Outbound)
WE27     Maintain Table View. Direction-2.(Inbound)
WE30     Develop Idoc Type.
WE31     Develop Idoc Segments.
WE32     View Development.
WE33     Maintain Table Views.
WE34     Change View u201CTable Of Style Ids With The Objects To Be Loadedu201D
WE40     Display System Process Code.
WE41     Display View: Logical Msg Overview. For Outbund.
WE42     Display View: Logical Msg Overview. For Inbound.
WE43     Display Status Records.
WE44     Display Partner Types
WE45     Maintenance Interface: Forwarding Inbound/EDILOGADR For Application
WE46     Global Parameter For Idoc Interface.
WE47     Status Maintenance.
WE50     Display Text For Process Code System.
WE54     Idoc Function Module For File Name
WE56     Display Status Process Code
WE57     Idoc Assignment Of FM To Log. Message And Idoc Type.
WE58     Text For Process Code Status.
WE60     Documentation For Idoc Type.
WE61     Documentation For Idoc Record Type.
WE62     Documentation For Idoc Segment Type.
WE63     Documentation For Idoc Record Types And Idoc Types (Parser).
WE64     Process Code In Idoc Inbound And Outbound.
WE70     Conversion Table For Basic Types.
WE71     Conversion Table For Extensions.
WE72     Conversion Table For Field DOCTYP.
WE73     Conversion Table For Logical Message Type.
WE81          EDI:Logical Message Type.
WE82     Message Types And Assignment To Idoc Types.
WE84     Assignment Table Between Idoc And Application Field.
ALE / EDI/ IDOCS TRANSACTION CODES
Transaction Code     Description
BD10     Send Material (Matmas)
BD11     Get Material.
BD12     Send Customer.
BD13     Get Customers
BD14     Send Vendor.
BD15     Get Vendor.
BD16     Send Cost Center. (Cosmas)
BD17     Request Cost Center.
BD18     Send G/L Accounts.
BD19     Get Master Data G/L Accounts.
BD20     Inbound Processing Of Idocs Ready For Transfer.
BD21     Creating Idoc Types For Change Pointers.
BD22     Delete Change Pointers.
BD23     Serialization Using Time Stamp: Deletion Of Old Time Stamp.
BD24     Send Cost Elements.
BD25     Send Activity Type (COAMAS)
BD26     Request Activity Type
BD27     Cost Center/Activity Types: Transmit Plan Quantities And Acty Prices.
BD28     Cost Center/ Cost Elements: Send Control Records.
BD30     Material Bom Distribution. (Bommat).
BD31     Document Structure Distribution. (Bomdoc)
BD32     Plant Allocation To Material Boms Distribution.
BD33     Distribution Of Material Variants. (STTMAT)
BD34     Distribution Of Boms (BOMORD)
BD35     ALE: Send Business Process Group.
BD36     ALE: Send Business Process.
BD37     ALE: Send Business Process Price.
BD40     Generate Idocs For Serialization Group From Change Pointers.
BD41     Dispatch Of Idocs Of Serialization Group.
BD42     Check Dispatch Status Of Idocs Of Serialization Group.
BD43     Processing Inbound Idocs Of Serialization Group.
BD44     Change View u201CSerialization Groupu201D.
BD47     Dependence Between Methods.
BD48     Dependence Between Methods And Message Type.
BD50     Activate Change Pointers For Message Type.
BD51     Characteristics Of Inbound Function Module.
BD52     Determine Work Area.
BD53     Reduce Message Type.
BD54     Change View: Logical Systems
BD55     Idoc Conversion.
BD56     Maintain Idoc Segment Filters.
BD57     Link Type And Serialization Type Of Message Type.
BD58     Convert Organizational Unit.
BD59     Allocation Of Object Type.
BD60     Additional Data For Message Type.
BD61     Activate Change Pointers Generally.
BD62     Display Conversion Rule.
BD63     Transport Of Ale Tables For A Message Type.
BD64     Display Distribution Model.
BD65     Maintain Idoc Type Required Fields.
BD66     Change Idoc Fields.
BD67     Function Module For ALE/EDI Overview.
BD68     Maintain List.
BD69     Assignment Of Idoc Type To Message Type.
BD70     Cross-System Comparison Of Number Range Objects.
BD71     Attributes For Receiver Determination.
BD72     Active Events For ALE/EDI
BD73     Start Error Handling For Non-Posted Idocs.
BD75     Status Conversion With Trfc Execution.
BD77     Generate Transport Requests For Distributing ALE Customizing Data.
BD78     Monitoring Ale Customizing Data Transport
BD79     ALE IDOC Segments - Conversion Rule
BD81     Filter Objects For BAPI Parameter Filtering
BD82     Generating Partner Profile
BD83     Re-Processing Incorrect Outbound Odocs.
BD84     Re-Processing Of Idocs After ALE Input Error.
BD85     Consistency Check: Reassignment Between Two System.
BD86     ALE Consistency Check: Create Purchase Order From Sales Order.
BD87     Select Idocs
BD89     Customizing Data Modeling For Distribution Model.
BD91     Distribute All Characteristics Via ALE.
BD92     Distribute Class Via ALE: Send Direct.
BD93     Distribution Of Classification Data Via ALE.
BD95     Ale Object View
BD96     Filter Object For Receiver Determination Of Methods.
BD97     Assign RFC Destination For Synchronous Method Calls.
BD98     Consistency Check With Workflow Link
BD99     Dependencies Between Message Types.
BD100     Display Serialized Idocs. (Serialization Using Object Types)
BD101     Serialization Using Object Types: Consistency Check.
BD102     Ale: Outbound Channel Registry.

Inbound logic for idoc

hello experts,
I have a query regarding inbound idoc.The input file is placed at application server and i need to read it and post it in SAP.My queries are:
1. In order to create an idoc using the file, we will use program RSEINB00 which will create idoc's with status 50 and then i need to link the correspiodning Function module in partner profile's inbound type and set it to automatic so that it gets posted into SAP? Is this correct? If yes, does it mean that there is no custom code needed for this case(Assuming that the FM linked in WE20 is standard)?
2. Can we dynamically process the file?Meaning, as soon as the file is placed at application server is there a way to invode the program RSEINB00 automatically
or should we run it manually ?
Please help with the process pls as it is slightly confusing.
Thanks,
Prem

yes your understanding is right and if you want the files are pulled from the server automatically then you run the report RSEINB00 in a job or you can create workflows for this.

Trigger condition for IDOC

Hi,
I have trigger condition for IDOC
All materials where:
"Finished Goods" Technical Names MARA-MTART = "Z001", and the Plants are "Granollers" MARC-WERKS="ES11", MARC-WERKS="ES12", goods that are "ready" or "ready for manufacturing", MARC-MMSTA = "02" or "03".
All the materials which satisfy this criteria will need to be triggered whenever a new material is created in SAP which meets the above criteria, or if any materials are modified which meet the above criteria in SAP.
How do I trigger my IDOC based on these conditions.
Regards,
Subhashini

Hi,
Please create the Idoc type / segments , create message type and link Idoc and message.
Steps to customize a new IDoc >>>
1. Define IDoc Segment (WE31)
2. Convert Segments into an IDoc type (WE30)
3. Create a Message Type (WE81)
4. Create valid Combination of Message & IDoc type(WE82)
5. Define Processing Code(WE41 for OUT / WE42 for IN)
6. Define Partner Profile(WE20)
2. Yes, you need LS & Partner profile
3. Yes use MASTER_IDOC_DISTRIBUTE
4. Can use IDOC_CREATE_ON_DATABASE instead of MASTER_IDOC_DISTRIBUTE and then process the Idoc.
Message Type :: The message type defines the semantic context of an IDoc. The message type tells the processing routines, how the message has to be interpreted. The same IDoc data can be sent with different message types.
IDoc Type :: An IDoc type defines the syntax of the IDoc data. It tells which segments are found in an Idoc and what fields the segments are made of.
Processing Code :: The processing code is a logical name that determines the processing routine. This points usually to a function module, but the processing routine can also be a workflow or an event.
The use of a logical processing code makes it easy to modify the processing routine for a series of partner profiles at once.
Partner profile :: Every sender-receiver relationship needs a profile defined. This one determines
The processing code
The processing times and conditions
In the case of outbound IDoc 1. The media port used to send the IDoc and 2. Triggers used to send the IDoc
Partner Type :: The IDoc partners are classified in logical groups. Such as : LS, KU, LI.
LS - Logical Systems : It is meant to be a different computer and was primarily introduced for use with the ALE functionality.
KU - Customer : The partner type customer is used in classical EDI transmission to designate a partner, that requires a service from your company or is in the role of a debtor with respect to your company, e.g. the payer, sold-to-party, ship-to-party.
LI - Supplier : The partner type supplier is used in classical EDI transmission to designate a partner, that delivers a service to your company.
thanks & Regards,
ShreeMohan

Triggering workflow upon idoc fail

Hi Gurus,
I have to trigger emails to users thru workflow whenver an idoc fails. Please teach me how can I achieve this.
Your help is highly appreciated.

Hi
Here is the link for idoc error handling workflow.
[idoc error handaling|https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/609e6465-15de-2a10-859d-da7bcbca54a3]
[idoc description|https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/8088e6fc-5637-2b10-c189-9733fa621cf1]
Regards
vijay

Configure Workflow for mailing

Hi,
I am looking for step-by-step documents or link how to configure workflow to send external mails if CUSTOM IDoc failed.
Your help appreciated
Thanks
Sa_R

Hi,
/people/sapna.modi/blog/2007/04/27/workflows-for-dummies--workflow-builderpart-ii
aRs

WORKFLOW FOR IDOCS

Similar Messages

Maybe you are looking for