Email functionality for PO Release Strategy:

Email functionality for PO Release Strategy:
>When PO is blocked an email must be sent out to the first approver.
>If there is a second approver there should be sent out an e-mail after the first level is approved and soon.
>When a PO is released by last approver an e-mail must be sent to the creator of the PO
I need develop this demand without workflow.
I found an Exit 'EXIT_SAPMM06E_013' which is triggering when 'ME21N' is executed.
But i'm unable to update the table EKKO before my code is executed.
Here i need Rel. gr(FRGGR),
            Rel Str.(FRGSX),
            Rel Indicator(FRGKE),
            subject to release(FRGRL) AND
            Rel Status(FRGZU) from table EKKO to check whether the PO is Blocked or Released.
Based on the values got from the table EKKO, i need pick email ids from ZTable which stores Email Ids.
I'm able to get the PO no which is currently genereated and i need to pass this PO no. to table EKKO to get the above fields.
But Table EKKO is updating in the database after the execution of my code.
What do i need to do to get table EKKO updated in the database before my code is executed.

Similar Messages

Email functionality for delivery release via VKM3

Dear All,
My question is -
When a delivery is being released by the credit department by transaction VKM4 a message should be automatically send to the responsible person in the sales office with the confirmation that the delivery has been released.
The message will be send to the @ mail (Lotus Notes) address.
The correct person will be identified via the partner function VW Customer Service which is defined at header level and should be available in the sales order.
I found the user exit Include RVKREFZ2 to be used for this.
Can anyone guide how to use this email functionality and from where the relevant data can be picked up from?
If any further clarifications are needed pls let me know.
Would greatly appreciate your useful feedback.
Thanks.
Regards,
Saurabh.

hello Saurabh,
You can use the following code to send an email.
DATA : l_message(100) TYPE c.
DATA : l_subject(50) TYPE c.
DATA : g_email(50) type c value '[email protected]'.
DATA : objheader LIKE solisti1 OCCURS 0 WITH HEADER LINE.
DATA object_id LIKE soodk.
DATA : docdata LIKE sodocchgi1 OCCURS 0 WITH HEADER LINE.
DATA : objcontents LIKE solisti1 OCCURS 0 WITH HEADER LINE.
DATA : receivers LIKE somlreci1 OCCURS 0 WITH HEADER LINE.
receivers-receiver = g_email.
MOVE : 'X'      TO receivers-express,
          'U'      TO receivers-rec_type.
APPEND receivers.
CONCATENATE 'Please note that your cheque numbered' p_cheque ' has been dishonoured' INTO l_message SEPARATED BY space.
CONCATENATE 'Cheque numbered' p_cheque 'dishonoured' INTO l_subject SEPARATED BY space.
objheader-line = 'Cheque Dishonoured!'.
APPEND objheader.
mail contents
objcontents-line = l_message.
APPEND objcontents.
objcontents-line = 'You are requested to contact the nearest Regional Office immediately'.
APPEND objcontents.
mail subject
docdata-obj_descr = l_subject.
APPEND docdata.
CALL FUNCTION 'SO_NEW_DOCUMENT_SEND_API1'
    EXPORTING
      document_data                    = docdata
DOCUMENT_TYPE                    = 'RAW'
     put_in_outbox                     = 'X'
   commit_work                      = 'X'
   IMPORTING
SENT_TO_ALL                      =
     new_object_id                    = object_id
    TABLES
     object_header                    = objheader
     object_content                   = objcontents
CONTENTS_HEX                     =
OBJECT_PARA                      =
OBJECT_PARB                      =
      receivers                        = receivers
   EXCEPTIONS
     too_many_receivers               = 1
     document_not_sent                = 2
     document_type_not_exist          = 3
     operation_no_authorization       = 4
     parameter_error                  = 5
     x_error                          = 6
     enqueue_error                    = 7
     OTHERS                           = 8
Moreover the email address can be found from the ADR6 table by giving the address number from KNA1 - the customer master.
Happy Programming
Zankruti

User exit for triggering release strategy

Hello Experts,
My requirement is when changes are made in purchase order (ME22N) then once again release strategy will have to get trigger.
is the user exits exists for this purpose,if yes, What is it?. I searched alot but not able to find right exits.

Hello ,
I think you can achieve this via configuration .Basically you want the release strategy to get redetermined based on the changes in the item or if the price of these items increase a certain level .if you have the release startegy as changeble in the SPRO ticked it will automatically go for new release strategy if you have the value of release indicator set .This can be done SPRO->MM->Purchase order->Release procedure for purchase order->Define release procedure->Release indicator.
Set the appropriate value .
Remember you need to know what is that it retrigger that release strategy .
The link below deals with similar requirement ....
[http://sap.ittoolbox.com/groups/technical-functional/sap-log-mm/retrigger-release-strategy-for-purchase-requisition-with-any-change-1858101]
Thanks
Anjaneya .
Edited by: Anjaneya Bhardwaj on Aug 31, 2011 8:21 AM

Tables for PO Release Strategy

Hi,
could you send me the list of tables for "Tables for PO Release Strategy".
Rgs,
Priya.

Hi,
EKKO - FRGGR (Release group)
EKKO - FRGSX (Release Strategy)
EKKO - FRGKE (Release indicator)
EKKO - FRGZU Release status
T16FB                          Release Indicator: Purchasing Document
T16FC                          Release Codes
T16FD                          Description of Release Codes
T16FE                          Descriptions of Release Indicators: Purchasing documents.
T16FG                          Release Groups
T16FH                          Descriptions of Release Groups
T16FK                          Release Statuses
Regards,
Chandra

How to have more than 8 release code for a release strategy

Hi,
In standard only 8 level of release is possible for a release strategy. Our client requires more than 8 levels i.e., more than 8 release codes for a release strategy. How can we achieve this?
Pls provide your views/ideas.
Reards,

Hello,
In case you require more than 8 levels in release strategy , write to SAP, maybe they could give a fitting reply.
By the way , 8 levels of release should be more than enough . Try to incorporate the client business process
within this.
Regards
Anis

Workflow for PO release strategy agent not found

Hi all,
I m beginner in the workflow. i want to create a workflow for the PO. release strategy I have done all the settings in the SPRO for the release strategy. I have copied the standard workflow definition WS20000075 also done the binding with object type BUS2012. in the steps 'Release of purchase order' i have mentioned the task TS20000166 i.e. 'Release of purchase order' and also maintain the AC Rule 20000027 i.e. 'Person responsible for PO release' for agents. But still its not getting the agents. the workflow is getting triggered but its not getting the agent. What else setting I need to do to get this done.
Thanks a lot.
Regards.

Very well put Rick. In my case if i simulate this workflow from swdd transaction then it works fine but the same workflow when initiated from ME21N doesn't work and throws same error.
1. I have copied standard workflow and task 166 is throwing error.
"Resolution of rule AC20000027 for task TS20000166: no agent found"
2. I have recreated the step but still the workflow is throwing error.
3. If I execute the rule individually (PFAC_DIS) with a specific PO then the rule works fine. The rule executes the below mentioned exit successfully.
4. I am using exit to determine the agent, the workflow works fine if I don't use the exit. The exit is EXIT_SAPLEBNF_005. I am just pulling the agent from a ztable.
Please advise if you can help as I have not seen anyone answering.
by the way irrespective of the explicit rule update in the workflow the step executes AC20000027 by default.
Any help on above is appreciated.

Inconsistency for Previous Release Strategy of PO

Dear colleagues,
Is there any standard program to come up with new values and criteriau2019s for new release strategy if pre defined release strategy, with class, is deleted for PO approval.
Best regards,

Hello Metin,
can you please elaborate your question, it is not very clear, as it is not showing the clear picture of your requirement.
regards,
Prashant Rathore.

Fields suitable for PO release strategy

Hi,
I had worked with the PO release strategy in which a characteristic is created with the fields BSART ( Order type ), WERKS ( Plant ), Value ( GNETW ), EKORG ( Purchasing group )
Other than these fields what are the list of fields over which we can have a control through the release strategy.
Pl expedite.
RD

Hello,
Please check the documentation for the activity 'Edit Characteristic' in the IMG:
[...] Requirements
In communication structure CEKKO you will find all the fields that can be used as characteristics for a release condition (e.g. BSART for the order type and GNETW for the total order value).
Check which fields you wish to use as characteristics for your release strategy. To do so, choose Tools -> ABAP Workbench -> Development -> Dictionary, enter CEKKO in the field Database table, and choose "Display".
Note
If you wish to define a separate release strategy for the various document categories (PO, RFQ, etc.), you must create a characteristic for each relevant document category.
So theoretically one can use any field from CEKKO.
For the workflow, customisation is linked to release strategies and codes, not directly with the classification fields.
Regards,
Michal

Workflow for PR Release Strategy

Hi Expert,
   Is there a way the scenario given below will be possible to achieve..
   All the needed config for the PR release strategy has been define... (release code, group,release strategy,class & characteristic)
Parameter : Doc Type,
                  Amount
                  Acct Assignment Cat ( K,A,C)
                  Cost Center
                   Sales Order
The challenge is that when the given
               Doc Type - NB
               Amount - >0
               Acct Assignment Cat = C
               Cost Center - Empty
               Sales Order - 9999
The PR will be subject for release strategy of Project Manager ( Release Code :PM)
The PR should be sent to the approver (through workflow) which can be found in the partner function maintain in the Sales Order
9999..Partner Function   ZM - Proj Manager. which contain Employee No ( from HR)
She

Hi,
Thanks..but i have completed all the setting in PR release strategy .. -
Am looking for alternative/ ways that i can incorporate the partner function from SO using the sales order
as the link from the PR (charge to sales order) to trigger where the notification will flow through...
This is more i think in the workflow or userexit or abap, but i took the libertly of posting it here perhaps some of the member had this requirement before and how it was accomplished..

Error in event receiver in workflow for PO release strategy

Hi Expert,
I am trying to trigger an email through workflow for PO release. I have setup following
In SWETYPV,I have check marked on Type linkage active and Enable event queue. Status no error.
In PFTC, under Triggering events, Object type BUS2012 is green light
When i create the PO in my SAP inbox, i get notification, however, i getting this error u201CERROR IN EVENT RECEIVER".
Also, how can i send the notification to the user's outlook inbox? Your help will be appreciated.

laurarice wrote:
Hi Expert,
>
> I am trying to trigger an email through workflow for PO release. I have setup following
>
> In SWETYPV,I have check marked on Type linkage active and Enable event queue. Status no error.
> In PFTC, under Triggering events, Object type BUS2012 is green light
> When i create the PO in my SAP inbox, i get notification, however, i getting this error u201CERROR IN EVENT RECEIVER".
> Also, how can i send the notification to the user's outlook inbox? Your help will be appreciated.
I suppose, you are using the workflow WS20000075. Add sending email as an additional task to the same workflow in SWDD.

User Exit for Requisition Release Strategy

Hi All,
Is anyone able to provide any guidance on determining the release strategy of a purchase requisition via a user exit? It has become neccessary to do this due to certain shortcomings of the classes and characteristic functionality.
I believe it's possible, I just don't know how.
Thanks.
Richard

go SMOD and enter enhancement M06E0004 it is exit LXM06U13

URGENT: Cutomize Email functionality for Action Items

Experts,
I need to your help for a customization I need to help setup immediately.
Here is the requirement : Client does not currently have an E-mail notification functionality turned on for Action Items. The requirement is to have E-mails sent out when ever an Action Item is Assigned to a User. The email should be sent to both the user who has been AssignedTo and the person who actually assigned.
I believe this need customization to Criteria Workflow email and/or cutomization to the out of the mail templates - reviewr_mail.htm and reject_mail.htm .
I am not sure which workflow is tied to Action Items.
Any expert advise on this would tremendously help .
Thanks in advance.
Rakesh

Old Old (6 years) data that only partly covers this, and on a current server may need some tweaking but this may help.
The following are required and assumed for custom workflow email functionality:
Stellent Content Server 7.x or higher
A working knowledge of CS
A working knowledge of CS workflow step event architecture
A working knowledge of Idoc Script.
Business Problem
You wish to customize the email message, subject, template, or all of the above, sent out by CS Criteria workflow.
Idoc Script Explanation
There are several new or newly exposed Idoc Script variables and functions, as well as old stand-bys, that make customizing 7.x Criteria Workflow emails quick and easy. All the functions and variables described herein may be found in the Idoc Script reference guide.
Emails will be triggered by criteria workflow:
Upon Step Entry
Upon Reject
Upon execution of the <wfNotify()> Idoc Script function
Customizing Email Templates
There are two primary workflow email templates that are used to generate the email messages sent out to recipients. These are: reviewer_mail.htm and reject_mail.htm both of which are located in the default templates directory at:
< Stellent Home Dir >/shared/config/templates
These templates may be modified like any other template according to established component architecture best practices. The templates are Idoc Script enabled and, as such, may evaluate dynamic code and draw dynamic results when the server is creating the mail message. Of course, after the message instance is created from the template and sent off to the mail server, no additional scripting may be done. Email message template modification provides the greatest flexibility and opportunity for truly customized and dynamic workflow emails.
It should be noted that not only may the email templates be modified for universal email changes, but also you may create custom workflow email templates based on the standard templates. Custom templates may be called as desired by adding them as the optional third parameter to <wfNotify()>.
Example:
<wfNotify(userName,"user",templateName)>
or
<wfNotify(aliasName,"alias",templateName)>
If no template is specified, SCS will use the system default template.
Although email template modification is relatively straightforward, such modification requires careful component development. Consequently, some clients prefer to modify the most important portions of the criteria workflow email: the subject and the message.
Customizing the Email Subject Line
Criteria workflow email subject lines may be modified in several ways. The core string resource may be modified according to standard component architecture. Additionally, the wfMailSubject IdocScript variable may be declared in criteria workflow step event scripting to give greater control and flexibility for narrowly targeted customization.
The default criteria workflow email subject lines are defined in the ww_strings.htm file located at:
< Stellent Home Dir >/shared/config/resourced/lang
The string definitions are:
<@wwWfIsNotifyOnly=Workflow notification for content item '{1}' is in step '{2}'.@> {1} = content item title. {2} = name of step in workflow.
<@wwWfReadyForStep=Content item '{1}' is ready for workflow step '{2}'.@> {1} = content item title. {2} = name of step in workflow.
<@wwWfRejected=Content item '{1}' has been rejected.@> {1} = name of content item.
These may be aliased (superceded) in a component resource file. They are typically called with the localization Idoc Script function <$lc()$>. See the <@dynamichtml wf_approve_mail_subject@> include definition in std_page.htm for an example of how email subject line string includes may be implemented.
For simple criteria workflow subject line changes Idoc Script, rather than full-blown components, may be used. The Idoc Script variable <$wfMailSubject="my subject"$> can be placed in step event script. The value of <$wfMailSubject$> can also accept Idoc Script. For example:
<$wfMailSubject="My Custom Subject Line for the content with title <$dDocTitle$>"$>
Note that no eval() function is required for the Idoc Script variable to evaluate when included in the wfMailSubject variable.
If wfMailSubject is place in the entry event of a workflow step, then any email messages triggered by content entering the step will receive the customized subject line. Additionally, wfMailSubject may be declared just prior to a wfNotify() function and the email(s) generated by that function call will receive the custom subject line.
Customizing the Email Message Line
The email message line is not the same thing as the email body. Rather each SCS criteria workflow generated email contains several lines of standard data:
Message: message line
Workflow Name: workflow name line
Workflow Step: workflow step name line
Content Item: content id line
The message line will default to one of two messages depending on whether or not the workflow step is a "notification only" (i.e. 0 required reviewers) step or not. The relevant localized strings are:
Notification only: <@wwWfIsNotifyOnly=Workflow notification for content item '{1}' is in step '{2}'.@> {1} = content item title. {2} = name of step in workflow.
Review Required: <@wwWfReadyForStep=Content item '{1}' is ready for workflow step '{2}'.@> {1} = content item title. {2} = name of step in workflow.
See the <@dynamichtml wf_approve_mail_message@> include definition in std_page.htm for an example of how email message line string includes may be implemented.
For simple criteria workflow message line changes Idoc Script may be leveraged in step event scripts. The Idoc Script variable <$wfMessage="my message"$> may be placed in step events to give the workflow emails custom message lines. Like wfMailSubject, the value of wfMessage can accept tagged Idoc Script variables without requiring an eval() wrapper. If wfMessage is declared in the entry event of a workflow step, workflow generated email messages for that step will use the value assigned to wfMessage. Additionally, wfMessage may be declared prior to a wfNotify() function and the email(s) generated by that function call will receive the custom message line.
These are not the only ways to customize criteria workflow email attributes. However, the SCS 7.x Idoc Script API provides these methods, functions, and variables to make customizing workflow emails simple.
Requirements, Pre-Requisites, and Assumptions
The following are required and assumed for custom workflow email functionality:
Stellent Content Server 7.x or higher
A working knowledge of CS
A working knowledge of CS workflow step event architecture
A working knowledge of Idoc Script.

Release Group for PR Release Strategy

Hi ,
When i am trying to define new "Release Group" AA , with Class "Z_PR" (it has Plant and Item Value as charcteristics ) , I am receiving message "Please Check Release Classes" , Message no. ME492.It doesn't allow me to save this new release group.
Please also note that other two release Groups are already available.
Do u know what I am missing and how can I save my Release group ?
ALSO as per the LONG text of this prompted message
"Diagnosis
Here you can assign release groups to release classes. Only one release class should be used within the release groups for overall release and the release groups without overall release in each case. However, in this instance several release classes have been used."
What does it mean ?
Sandeep

Hi,
The message has explained the problem.
You cannot have two classes for the same document release and you are tryng to break this rule by adding another entry (the fact that you have give it a different release group does not make any difference this is still another class for the same document.)
You should be able to do what you want without the need for a new release group or additional class, after all everyone else that uses SAP is using one class per document.
Why diod you think that you needed another release group / class?
Steve B

Workflow for PO Release Strategy

Hi all Workflow experts
We are on ECC 6.0. We have created a 3 level Rel strategy PO and are creating the workflow for this scenario.
The business object we are using is BUS2012 and WF Template is WS20000075.
Each time a PO is created/changed workitem will be sent order we have defined, ie. L1, L2,L3. Each time mail goes to the inbox of the concerned approver.
The problem is when the final approver cancels the release. Under activity 'Release of PO canceled, Task TS20000167 we have assigned the agent as Originator of PO. However at this instant mail does not go into the originator's mailbox.
Approver is cancelling the release in ME28 as it should be, I presume.
Are we missing something here? Is there any additional settings required to trigger the mail to the originator?
I would be happy if the responses from you all does not point to SAP .htm files! since I have already gone through them but it is very hard to understand some simple things!
Thanks in advance.
Regards,
Raghu

All,
I gather that ver 4.7 onwards, SAP has supported the PO rejection/cancellation feature. Since I am working on client's server which is 4.6 c I am not able to implement this. Unfortunately, in the process of doing R&D within the sandbox I seem to have damaged the template WS000075. Now I am getting an error message at the first approval level saying "relase written to buffer".
Can anyone tell me what does this mean? Also is there a way to retrive the original template form the development clients?
Regards,
raghu

Emailing functionality for billing output

Hello SDN's,
As per requirement, business needs to send invoice output to customer email directly and business needs to validate the invoice before sending to customer email .Can you please suggest how do we implement this process in as per business requirement.
I have checked current functionality, as per that business is validating the invoice before sending to customer(not email).
Please suggest.
Thanks in advance
Regards,
KV

Hello Guru's
Based on the discussion, I do have similar business requirement but with little twist, as it can never be same
I need to configure billing output via ale. which they want in email format to be sent to vistex for further processing.
Secondly this output has to be for some special customers, business will run a batch by the end of the day to push this docs for further processing to vistex.
So for this solution do I control it by output routine or maintain access sequence?
And also which transmission medium should I use?
Please suggest on this.
Thanks
Aman

Email functionality for PO Release Strategy:

Similar Messages

Maybe you are looking for