ALE Workflow

We're implementing ALE between our financials server and HR server.
We would like to set up some sort of monitoring to make sure the IDocs are processed successfully and want to notify users via some sort of Workflow.
From what I understand, the program RSEIDOCA collects the Idocs based on the status/message type etc.. criteria selected and sends them via SAP Mail to the appropriate people
And, I need to make sure all the partner profiles have an Agent assigned to them - this would be the person who's notified of errors.
I'm sure there's a lot left out. Can someone explain ALE workflow? How similar is it to normal workflow used on FI side?
thanks,
robert.

Hi Robert,
SAP provides std WF for error handling. The link below will give you some useful information to get started. Hope this helps.
<a href="http://www.asug.com/client_files/Calendar/Upload/ ASUG%20EDI%20IDoc%20Error%20Handling%20Using%20SAP%20Workflow.ppt">IDOC Error Handling using Workflow Presentation</a>
Cheers
VJ

Similar Messages

  • ALE Workflow setup

    Hello Gurus,
    I want to setup workflow for ALE/Idoc error handling. Sap version 4.6B.
    Can anyone please tell me in detail the steps need to be configured/setup for
    the workflow. This is for customer master distribution.
    Urgent please.
    Thanks in advance.
    Rgs,
    Anant

    Hi Ananth,
    If you want to know how to activate the workflow for handling the idoc errors then here is the explabatio.
    Go to tcode : WE42.
    Choose any inbound processcode: ex : INVC and click on details.
    Here usually the events are defined(Start and END event) for IDOC Error handling through workflow.
    For process code : INVC
    Object Type                         IDOCINVCON
    Start Event                         INPUTERROROCCURRED
    End event                           INPUTFINISHED
    If any error is occured when IDOC for message type INVCON  is created then IDOCINVCON.INPUTERROROCCURRED event will be triggered. You need to use this event in the start condition of workflow "which in turn will send the workitem to user who is responsible for correcting the errors".
    Reward if it helps.
    Thanks
    Praveen

  • ALE: Workflow Objects

    HI,
    do yo have some information about ALE / IDoc (Monitoring/Exception handling/Processing) Workflow processing ?
    - Which BOR can be used ?
    -Which classes can be used ?
    - sample workflows.
    - can i use the alerting framework with workflows ?
    Thanks,
    Gordon

    Hi,
    Check
    http://help.sap.com/saphelp_46c/helpdata/EN/d4/09c276a3a811d189be0000e829fbbd/content.htm
    http://help.sap.com/saphelp_45b/helpdata/EN/72/c18ee5546a11d182cc0000e829fbfe/frameset.htm
    Edited by: Neenu Jose on Oct 28, 2008 10:57 AM
    Edited by: Neenu Jose on Oct 28, 2008 11:00 AM

  • ALE Workflow Scenario

    Hi,
    Can somebody tell me how we can handle errors in ALE on Inbound side using workflow?
    All the help is appreciated.
    Thanks,
    Sneha.

    HI Sneha,
    Please go to transction WE20, pick the Partner / Idoc that you would like to assign the Org. chart to.
    Then you should configure "post processing :permitted agent" Tab with the Organizational unit.
    Then double click the process code associated with the Idoc Type and click the button next to the Function Module associated with this process code.
    Check IDoc Tab and see if Stanard Event INPUTERROROCCURRED is present in the field called start event.
    Regards
    Saurabh Goel
    Edited by: Saurabhgoels on Jul 9, 2009 1:37 PM

  • Workflow & ALE

    Hi,
    I am aware that workflow can be used for triggering idoc as well as for error notification.However I have no clue about how Workflow can be used for the same.
    Is anybody aware of any documents that will give some examples explaining these also the bare minimum terms related to workflow ,that I need to know in order to execute the process.
    Thanks & Regards,
    Vanita

    Hi!
    Refer to:
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/webas/abap/an advanced guide to implementing application link enabling.pdf
    Your sections of interest:
    4.2.9 Make basic settings for Workflow
    4.3.17 Setting up Workflow
    4.4.5 ALE Workflow Configuration Procedure
    Hope it helps.
    Regards,
    Maxim.

  • Creating the job to execute automatically the program RSWUWFML2

    Hi guys,
    Iu2019m setting up the job to send Workitems to internet periodically with the program RSWUWFML2, when I create the job It ask me for a responsible user in the u201Cstepu201D, this user is going to be the one to execute this job, I usually call this user u201CWORKFLOWu201D and I need to set the Email account (Workflow) for this user (Tcode SU01) because on this Email account  the system will be sending a kind of log for the workitems sent to users and which of them have been opened by the user.
    The question I have is in SU01 which u201CROLESu201D have to be set for this user to be able to make all the thinks to send the workitmes to the users and send this Email as a log and make all the things related to execute the RSWUWFML2 report.
    Tanks a lot

    >
    FelipeUribe wrote:
    > Hi Ravi, tanks a lot for your answer, The problem using user  WF-BACH as a user to be placed in the Job (Tcode SM36  -> Step u2026 field u201CUser = Background User Name for Authorization Checku201D) is that I get an error because this user canu2019t be a u201Ccommunicationu201D useru2026.the Tcode SWU3 create this user WF-BATCH automatically with this features.
    Hi Felipe
    Here's Help from the user type field in SU01 for B it says,
    System 'B'
    Use the system user type for internal system processes (-> background processing) or system-related processes (-> ALE, workflow, TMS, CUA).
    Dialog logon (using SAP GUI) is not possible.
    A user of this type is excluded from the general settings for password validity. Only user administrators can change the password using transaction SU01 (Goto -> Change Password).
    Multiple logons are permissible.
    I have checked one of our productive systems and it is set to B for WF-BATCH. The error message you get is because your WF-BATCH is a C type.
    Hope this helps.
    Good Luck
    Ravi

  • User IDs in adapters - XI Proxy, RFC

    Hi mates,
    I've created receiver adapters of type XI and RFC for an SAP R/3 business system. In these adapter parameters, what is the <b>ideal</b> user ID that needs to be specified? Should it be a service user id or dialog user id? What should be the optimal authorizations for it.
    At the moment, I've specified my own user id and the adapters are working successfully. But, I foresee an issue with this method as I would be required to change the password at regular intervals.
    What are the best practices regd the user ids in adapters? Please share your experiences.
    I appreciate your inputs.
    thx in adv
    praveen

    Hi Praveen,
    I would suggest the use of a user of type "Communications" and have SAP_ALL assigned....
    a user of type "Service" still has dialgo access whihc i donot think you would want...
    pls see the types of users and their help...
    User Type
    Dialog 'A'
    A normal dialog user is used by one person only for all types of logon.
    During a dialog logon, the system checks for expired and initial passwords and provides an option to change the password.
    Multiple dialog logons are checked and logged if necessary.
    System 'B'
    You use a user of type System for communication without dialog within one system (for RFC or CPIC service users) or for background processing within one system.
    Dialog logon is not possible.
    A user of this type is excluded from the general settings for password validity. Only the user administrator can change the password using transaction SU01 (Goto -> Change Password).
    Communication 'C'
    You use a user of type Communication for communication without dialog between systems (for RFC or CPIC service users for various applications, for example, ALE, Workflow, TMS, CUA).
    Dialog logon is not possible.
    Service 'S'
    A user of the type Service is a dialog user that is available to an anonymous, larger group of users. Generally, this type of user should only be assigned very restricted authorizations.
    For example, service users are used for anonymous system access via an ITS service. Once an individual has been authenticated, a session that started anonymously using a service user can be continued as a personal session using a dialog user.
    During logon, the system does not check for expired and initial passwords. Only the user administrator can change the password.
    Multiple logon is allowed.
    Reference 'L'
    Like the service user, a reference user is a general user, not assigned to a particular person. You cannot log on using a reference user. The reference user is only used to assign additional authorization. Reference users are implemented to equip Internet users with identical authorizations.
    On the Roles tab, you can specify a reference user for additional rights for dialog users. Generally, the application controls the allocation of reference users. You can allocate the name of the reference user using variables. The variables should begin with "$". You assign variables to reference users in transaction SU_REFUSERVARIABLE.
    This assignment applies to all systems in a CUA landscape. If the assigned reference user does not exist in one of the CUA child systems, the assignment is ignored.
    Thanks,
    Renjith.

  • Meaning of User types & their use....

    Hi all,
    Please explain me below user types and their significance in brief:
    USR02-USTYP  Description
    A             Dialog
    B             System User (Internal RFC and Background Processing)
    C             Communication User (External RFC)
    L             Reference User
    S             Service User
    Regards,
    Sachin

    User Type
    Dialog 'A'
    A normal dialog user is used by one person only for all types of logon.
    During a dialog logon, the system checks for expired and initial passwords and provides an option to change the password.
    Multiple dialog logons are checked and logged if necessary.
    System 'B'
    Use the system user type for internal system processes (-> background processing) or system-related processes (-> ALE, workflow, TMS, CUA).
    Dialog logon (using SAP GUI) is not possible.
    A user of this type is excluded from the general settings for password validity. Only user administrators can change the password using transaction SU01 (Goto -> Change Password).
    Multiple logons are permissible.
    Communication 'C'
    Use users of type Communication for dialog-free communication between systems (-> RFC or CPIC) .
    Dialog logon (using SAP GUI) is not possible.
    The general settings for the validity period of a password apply to users of this type. Users of this type can change their passwords (like dialog users). The dialogs for changing the password must be provided by the caller (RFC/CPIC client). You can use the RFC function module USR_USER_CHANGE_PASSWORD_RFC or the RFC API function RfcOpenEx() to change the password.
    Service 'S'
    A user of the type Service is a dialog user that is available to an anonymous, larger group of users. Generally, this type of user should only be assigned very restricted authorizations.
    For example, service users are used for anonymous system access using an ITS service or a public Web service. Once an individual has been authenticated, a session that started anonymously using a service user can be continued as a personal session using a dialog user (see SUSR_INTERNET_USERSWITCH)
    During logon, the system does not check for expired and initial passwords. Only the user administrator can change the password.
    Multiple logon is allowed.
    Reference 'L'
    Like the service user, a reference user is a general user, not assigned to a particular person. You cannot log on using a reference user. The reference user is only used to assign additional authorization. Reference users are implemented to equip Internet users with identical authorizations.
    On the Roles tab, you can specify a reference user for additional rights for dialog users. Generally, the application controls the allocation of reference users. You can allocate the name of the reference user using variables. The variables should begin with "$". You assign variables to reference users in transaction SU_REFUSERVARIABLE.
    This assignment applies to all systems in a CUA landscape. If the assigned reference user does not exist in one of the CUA child systems, the assignment is ignored.

  • Difference between a Service user and Dailog user ?

    Hi All,
    Can anybody tell me the difference between a service user and a dailog user?
    Why can't we use a service user for BSP applications?
    We are on a 620 system and use bsp system login.
    With a dialog user it works, but when I switch this user to a service user the login returns an empty login screen.
    Thanks in advance.
    Rob

    A service user can only be used for background processing and communication within a system (such as RFC users for ALE, Workflow, TMS, and CUA). Dialog screens are not allowed for these users.
    Dialog users however have individual, interactive system access.
    [user types|http://help.sap.com/saphelp_nw70/helpdata/EN/3d/3272396ace5534e10000000a11405a/content.htm]

  • BAtch Job Error Reson CPIC..

    Hi,
    I submitted two jobs and the status is Active.I looked in SM50 and the staus is Stopped and Reson is CPIC.Can anybody tell me what it means.The status is still Active in SM37.
    Points will be awarded.
    Thanks..

    Hi,
    CPIC users are users with type c .
    Communication 'C'
    Use the user type Communikation for dialog-free communication between systems (for RFC or CPIC service users of different applications, for example, ALE, Workflow, TMS ZBV).
    Dialog logon is not possible.
    Cheers
    VJ

  • Tcode questions

    hi experts
    pls let me know to ans this
    If a tcode is taking too long time to finish and I want to end the work process in sm50 how to find which work process is currently executing that tcode? 
    Can I configure STMS on a single system on windows 2003 server if so what are the prerequisite. why I am getting the error "tp distribution failed"  ?
    how a transport request will be transported after being released . how it had to be carried to production system ?
    SAP there are different type of Users one of them is System User I want to know why the system user is created and if created what is use of them and how they are associated with the Dialogue User ,As we all know Dialogue user can perform all work in Sap by logging in the sap server , so why the system user is created and how they are associated with Dialogue user With Rgds  ?

    Hi Hasan,
    1. If a tcode is taking too long time to finish and I want to end the work process in sm50 how to find which work process is currently executing that tcode?
    -->  You can verify which user is executing long running Tcode via Tcode SM04/AL08 in system currently. Once you get to know , which user session is causing the issue , you need to kill that workprocess.
    I would suggest to view workprocesses via Tcode SM66 globally including all application server details. Once you locate perticuler work process along with PID number and user iD , you can kill his session.
    2. Can I configure STMS on a single system on windows 2003 server if so what are the prerequisite. why I am getting the error "tp distribution failed" ?
    --> Yes you can make STMS configuration on single SAP system by making itself as Domain controller and later adding SAP systems as per requirement.
    If your STMS configuration is inconsistant or incorrect , you get this error while distibuting changes across STMS systems.
    You can verify STMS configurations , via Tcode STMS_DOM  : SAP system --> Check --> Connection Test, Transport Tool, Transport Directory
    3.how a transport request will be transported after being released . how it had to be carried to production system ?
    --> Depending upon your STMS path configuration , TR gets migrated. specially target selection made during TR creation.
    Please read concept of Consolidation and Delivery type of transport routes to migrate TRs within SAP systems
    4.SAP there are different type of Users one of them is System User I want to know why the system user is created and if created what is use of them and how they are associated with the Dialogue User ,As we all know Dialogue user can perform all work in Sap by logging in the sap server , so why the system user is created and how they are associated with Dialogue user With Rgds ?
    --> pls read concept of different SAP User Type.
    System 'B'
    Use the system user type for internal system processes (-> background processing) or system-related processes (-> ALE, workflow, TMS, CUA).
    Dialog logon (using SAP GUI) is not possible.
    A user of this type is excluded from the general settings for password validity. Only user administrators can change the password using transaction SU01 (Goto -> Change Password).
    Multiple logons are permissible.
    Regards,

  • Difference between service and communication user

    Hi,
    We ran into a big problem in our CRM system getting millions of Dynpro_Send_in_background dumps while processing inbound queues R3AD* from R/3 system to CRM. Lots of Updates getting failed with CRM_SCHEDLIN_UPDATE_DU function module while executing report LCRM_SCHEDLIN_DUU01.
    Error Details - CRM_ORDER_MISC 002: Error in updating object SCHEDLIN
    We posted to SAP as well but did not find root cause. SAP saying we need to change RFC user "S_ECC_PR0400" from Service user to Communication user, that would stop the dump problem.
    I want to know what is the unique difference between these users(Service & Comm) which will resolve the dump problem though I know the common difference between these users.
    Thanks
    Anju

    Hi Anju ,
    Communication 'C' User :
    Use the user type Communikation for dialog-free communication between systems (for RFC or CPIC service users of different applications, for example, ALE, Workflow, TMS ZBV).
    Dialog logon is not possible.
    Service 'S' User :
    A user of type Service is a dialog user available to a large anonymous set of users. It usually has closely-restricted authorizations.
    Service users are e.g. used for anonymous system access via an ITS service. You can change a session which began as an anonymous session with a service user into a personal session under a dialog user with an individual authentification.
    There is no check for obsolete/initial passwords at logon. Only the user administrator can change the password.
    Multiple logon is allowed.
    Hope this may help you.
    Thanks
    Gyan

  • Reference and service users

    what exactly this reference and service users do and for what kind of activities these user types has to be assigned?

    Hello Veera ,
    Hope you looking for this  ....
    Characterization of user types
    Dialog user 'A'
    Individual system access (personalized)
    Logon with SAPGUI is possible. The user is therefore interaction-capable with the SAPGUI.
    Expired or initial passwords are checked.
    Users have the option of changing their own passwords.
    Multiple logon is checked.
    Usage: For individual human users (also Internet users)
    System user 'B'
    System-dependent and system-internal operations
    Logon with SAPGUI is not possible. The user is therefore not interaction-capable with the SAPGUI.
    The passwords are not subject to to the password change requirement, that is, they cannot be initial or expired.
    Only an administrator user can change the password.
    Multiple logon is permitted.
    Usage: Internal RFC, background processing, external RFC (for example, ALE, workflow, TMS, CUA)
    Communication user 'C'
    Individual system access (personalized)
    Logon with SAPGUI is not possible. The user is therefore not interaction-capable with the SAPGUI.
    Expired or initial passwords are checked but the conversion of the password change requirement that applies in principle to all users depends on the caller (interactive/not interactive). (*)
    Users have the option of changing their own passwords.
    Usage: external RFC (individual human users)
    Service user 'S'
    Shared system access (anonymous)
    Logon with SAPGUI is possible. The user is therefore interaction-capable with the SAPGUI.
    The passwords are not subject to the password change requirement, that is, they cannot be initial or expired.
    Only a user administrator can change the password.
    Multiple logon is permitted.
    Usage: Anonymous system access (for example, public Web services)
    Reference user 'L'
    Authorization enhancement
    No logon possible.
    Reference users are used for authorization assignment to other users.
    Usage: Internet users with identical authorizations
    Regards ,
    Santosh

  • Determination of login type

    Hi all,
    I'd like to understand in ABAP program how user logged on in system either from GUI for Windows or from Web (GUI for HTML - ITS, WEB Dynpro for ABAP etc )?
    Could you help me please?

    Hi,
    Go to SUIM Tcode.
    under USER -click on logon details
    enter your user id  and execute
    you will get the details in areport
    see the USER TYPE column in the report, there it is mentioned
    based on this field User Type you will know how you logged in:
    see the doc:
    Dialog 'A'
    A normal dialog user is used by one person only for all types of logon.
    During a dialog logon, the system checks for expired and initial passwords and provides an option to change the password.
    Multiple dialog logons are checked and logged if necessary.
    System 'B'
    Use the system user type for internal system processes (-> background processing) or system-related processes (-> ALE, workflow, TMS, CUA).
    Dialog logon (using SAP GUI) is not possible.
    A user of this type is excluded from the general settings for password validity. Only user administrators can change the password using transaction SU01 (Goto -> Change Password).
    Multiple logons are permissible.
    Communication 'C'
    Use users of type Communication for dialog-free communication between systems (-> RFC or CPIC) .
    Dialog logon (using SAP GUI) is not possible.
    The general settings for the validity period of a password apply to users of this type. Users of this type can change their passwords (like dialog users). The dialogs for changing the password must be provided by the caller (RFC/CPIC client). You can use the RFC function module USR_USER_CHANGE_PASSWORD_RFC or the RFC API function RfcOpenEx() to change the password.
    Service 'S'
    A user of the type Service is a dialog user that is available to an anonymous, larger group of users. Generally, this type of user should only be assigned very restricted authorizations.
    For example, service users are used for anonymous system access using an ITS service or a public Web service. Once an individual has been authenticated, a session that started anonymously using a service user can be continued as a personal session using a dialog user (see SUSR_INTERNET_USERSWITCH)
    During logon, the system does not check for expired and initial passwords. Only the user administrator can change the password.
    Multiple logon is allowed.
    Reference 'L'
    Like the service user, a reference user is a general user, not assigned to a particular person. You cannot log on using a reference user. The reference user is only used to assign additional authorization. Reference users are implemented to equip Internet users with identical authorizations.
    On the Roles tab, you can specify a reference user for additional rights for dialog users. Generally, the application controls the allocation of reference users. You can allocate the name of the reference user using variables. The variables should begin with "$". You assign variables to reference users in transaction SU_REFUSERVARIABLE.
    This assignment applies to all systems in a CUA landscape. If the assigned reference user does not exist in one of the CUA child systems, the assignment is ignored.
    Reward if useful.
    regards,
    Anji

  • Differentiate the following user types?

    1.Dialog user
    2.Service user
    3.System user
    4.Reference user

    Hi
    <b>Dialog</b> :  Individual, interactive system access.
    <b>System</b> : Background processing and communication within a system (such as RFC users for ALE, Workflow, TMS, and CUA).
    <b>Communication</b> : Dialog-free communication for external RFC calls.
    <b>Service</b> : Dialog user available to a larger, anonymous group of users.
    <b>Reference</b> : General, non-person related users that allows the assignment of additional identical authorizations, such as for Internet users created with transaction SU01. No logon is possible.
    Thanks
    Prince Jose

Maybe you are looking for