Skip to Content
avatar image
Former Member

workitem is not sending to substitute..

Hello Friends,

when i assign substitute for a approver.. Workitem is not sending to substitute..

i am using standard workflow WS14000133..

thanks.

john.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • avatar image
    Former Member
    Apr 09, 2007 at 01:21 PM

    Hi

    Which SRM server are you using ?

    Couple of reasons can be possible for this ->

    1) Some configuration settings might be missing

    2) Some OSS note applied incorrectly

    3) BADI code is not implemented correctly

    Refer to these links, which might help.

    <b>

    resend-email-for-sc-approval

    reject-change-delete-emails

    http://help.sap.com/saphelp_srm50/helpdata/en/67/ec7b20d15411d2b465006094b92d37/content.htm

    http://help.sap.com/saphelp_srm50/helpdata/en/ee/8804050393ea4596330fe181092003/content.htm

    http://help.sap.com/saphelp_srm50/helpdata/en/6b/eca441eea7ef0be10000000a1550b0/frameset.htm>

    On the safer side, also raise an OSS message with SAP as well.

    Regards

    - Atul

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi

      You need to make the configuration settings here accordingly as per your business requirements.

      <u>Here is the SRM SPRO configuration path. (use Transaction - SPRO)

      SAP Implementation Guide -> Supplier Relationship Management -> SRM Server -> Cross-Application Basic Settings -> SAP Business Workflow -> Define Recipient of Notifications</u>

      <u><b>Define Recipient of Notifications</b></u>

      Use
      
      In this IMG activity you define which users (determined by their workflow functions) receive workflow notifications in which application scenarios.
      
      The workflow notification arrives in the receiver's (for example, the initiator) inbox in the EBP online system and informs him that a specific object (for example, a shopping cart) has been processed (for example, rejected) and by whom (for example, the approver).
      To display the workflow notification, the variables for processor, scenario etc. are determined dynamically during the runtime. One of the sources consists of the settings you make in this IMG activity.
      
      Application scenarios include:
      
      Process Shopping Cart
      Shopping carts may be rejected, approved, changed or deleted
      Relates to Business Object: BUS2121   Shopping Cart EC (SC)
      Called-up notification workflow: WS10400026   SCSendMail
      Triggered standard task: TS10407929   SCMAILSEND
      Confirm Goods Receipt
      Confirmations may be rejected, approved, changed or deleted
      Relates to Business Object: BUS2203   Confirmation of goods/service EC (CF)
      Called-up notification workflow: WS10400025   CFSendMail
      Triggered standard task: TS10407928   CFMAILSEND
      Process Invoice and Credit Memo
      Invoices may be rejected, approved, changed or deleted
      Relates to Business Object: BUS2205   Eingangsrechnung EC (IV)
      Called-up notification workflow: WS10400024   IVSendMail
      Triggered standard task: TS10407927   IVMAILSEND
      Possible recipients include:
      
      Initiator of the workflow (called the requester in the case of a shopping cart)
      Reviewer
      Approver
      If you do not make any settings for a specific application scenario, then no notification is sent.
      
      The standard default settings have been made in such a way that, as far as workflow notifications are concerned, there are no changes in functions at application level compared to the EBP Releases prior to 3.5.
      
      The delivery class of this IMG activity has been set to G (Customizing table, protected against SAP UPD, only INS permitted), and this prevents the settings you make from being overwritten in the event of a Release update.
      
      By making appropriate settings in Shared Office Settings (Transaction SO16) and in Administration of Automatic Forwarding (Transaction SO36), you can determine that the workflow notifications are forwarded by the system to external e-mail addresses.
      
      
      
      
      Activities
      
      To generate a new entry:
      
      On the initial screen (Determination of mail recipients in the event of specific workflow situations) choose New entries
      This takes you to the detail view.
      In the field Scenario, use the dropdown box to choose the appropriate application scenario.
      In the field User role, use the dropdown box to select the role of the user who is to receive a notification in the scenario.
      In the screen area "The user with the role defined above receives an e-mail in the event of", set the indicators for the triggering situations that are to lead to a notification being sent.
      
      Example
      
      The settings
      
      Scenario:
      
      Process shopping cart
      
      User role:
      
      Initiator of the workflow
      
      Indicator:
      
      Rejection of the application object
      
      Changes to the application object
      
      Deletion of the application object
      
      Have as a consequence in the system that the requester of a shopping cart receives a workflow notification if the shopping cart is rejected, changed or deleted.

      Regards

      - Atul