BADI for PO release strategy

Hi,
If PO is released than automatically mail should be sent to authorized person.
How i can achieve this using BADI.Please suggest.And where i have to write the code.

Hello Priyank
If you are already working on ERP 6.0 the the BAdI of choice is ME_PROCESS_PO_CUST. Below I describe schematically how you implement your requirement:
METHOD IF_EX_ME_PROCESS_PO_CUST~OPEN.
me->md_trtyp = id_trtyp. " NOTE: Define MD_TRTYP as instance attribute
" NOTE: Presumably IF ( id_trtyp = 'H' ). => means PO is created
ENDMETHOD.
" Closing Processing
METHOD IF_EX_ME_PROCESS_PO_CUST~CLOSE.
CHECK ( me->md_trtyp = 'H' ). " implies PO has been created
CALL METHOD me->send_email( ).
ENDMETHOD.
Regards
Uwe

Similar Messages

BADI for PO release through ME29n

Hi Experts,
I have to send an IDOC as & when user release the Purchase order from ME29n. I got a user exit 'M06E0004' for release strategy but it sends idoc when i open the Transaction ME29n. Instead of that i have to send it on the click on that release button.
Can anyone please tell me the BADI for this and the method in which i have to write the code for button click to send the IDOC.
Regards,
Manish

that means there is no BADI for PO release.
the problem is i dont no these config steps as i never did any config work.
I will try whatever the thread says.
Again i want 1 more BADI for repeat output functionality. Purchase Order to be automatically re-sent (if changes are made) from the Repeat Output function within ME22n messages. If changes are made the relevant personnel will manually trigger a reprint of the order using the Repeat Output function, this needs to trigger the idoc to be re-sent.
Regards
Manish

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

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

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.

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.

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

User Exit/ BADI for PO release

Hi Experts,
Can anyone please tell me about the User Exit or BADI for Sub contract PO release.Also tel me how to proceed for the following 2 requirement ,
i have to send an IDOC as & when the Sub contract PO releases.
And automatically resent if changes are made in PO with the repeat output function in ME22N.
Regards,
Nik

Hi,
Use trx SE19 to implement your BADI: create an ZME_PROCESS_PO_CUST using ME_PROCESS_PO_CUST as definition.
Now in Interface Tabs you can see the METHODs you can use as "user-exit", in particular there's PROCESS_ITEM to manage items data.
You have to write your code into this method.
This method has IM_ITEM like parameter in its interface, and it's like the type IF_PURCHASE_ORDER_ITEM_MM.
This type has the method IF_LONGTEXTS_MM~SET_TEXT, you can try to use it to set your text in item.
This is code for example:
DATA: TLINE TYPE MMPUR_T_TEXTLINES.
CALL METHOD IM_ITEM->IF_LONGTEXTS_MM~SET_TEXT
EXPORTING
IM_TDID = <YOUR ID>
IM_TEXTLINES = TLINE.
So you should read the text you want to copy and pass it to TLINE.
You can use the METHOD PROCESS_HEADER to read the text you need. This METHOD has IM_HEADER as parameter and it's like the type IF_PURCHASE_ORDER_MM, this type has the method IF_LONGTEXTS_MM~GET_TEXT to read header logn text.
Anyway while you're in implementation of the BADI go to:
GoTo->Sample Code
Here you can try an example how to implement the method you need to use.
Regards

User Exit Or Badi for Framework Release PO

Anyone could tell me about any user exit or BADI for storing the calculated value in Frameork order.
Since it is storing the GNETW in CEKKO and that is used in releasing procedure.
First of all i want to calculate the total price according to srat date and end date and then only for framework order put that value in CEKKO-KTWRT field.
Please Help and suggest some thing about this.
Thanks & Regards,
Nitin Malhotra

Hi,
Check the following PDF .
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/9cd334f3-0a01-0010-d884-f56120039915
May be useful to you.
Regards
Sachin

BADI for PO Release

Hi Experts,
I want to save data of PO after its Release.
Can anbody tell me the BADI which will get triggered after PO Release ???
Regards,
Chaitanya

Hi
Goto Se24 and enter CL_EXITHANDLER
in method GET_INSTANCE
CALL METHOD cl_exithandler=>get_class_name_by_interface
keep break point and check the relevant BADI for you requirement
Regards
Shiva

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

User Exit Or Badi for Framework Release

We have set up Release strategy at PO based on value and Purchase organization. It is working fine for all types of PO except Frame work PO. As per system prospective it is working fine but as per business prospective it is not appropriate.This is beacuse Frame work in our case is created with Invoice plan set up . Ex If PO is created for 5000 USD then with Invoicing plan set up it is assigned for period of 12 months and total invoicing value gets 60000 USD and release strategy gets triggered on the base of header value i.e. 5000 USD.
So business requirement is that PO release strategy should triggered on the basis of total invoicing plan set up of that PO i.e. 60,000 USD.
in release procedure they are using CEKKO-GNETW field.
only for framework PO, i want to calculate the price according to start date and end date and popullate that in CEKKO-KTWRT field so that a new release procedure can be implemented for the same.
I use M06E0004 user exit, but it is not working.
as soon as we click check button or save button this user exit is triggering but values of EKKO is comming null inside user exit.
How to calculate the price since start date and end date is in EKKO table.
please help in USER EXIT.
Thanks & Regards,
Nitin Malhotra

Hi,
Check the following PDF .
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/9cd334f3-0a01-0010-d884-f56120039915
May be useful to you.
Regards
Sachin

Exit / BADI for RFQ Release (ME45)

Hi all,
         I need an exit or badi when an RFQ got released.
Can anybody please help me to find the badi when an RFQ has been released.
Thanks & Regards.
Ranganadh.

Hi,
Exits for RFQ are following-
AMPL0001            User subscreen for additional data on AMPL
ME590001            Grouping of requsitions for PO split in ME59
MEETA001            Define schedule line type (backlog, immed. req., preview)
MEFLD004            Determine earliest delivery date f. check w. GR (only PO)
MELAB001            Gen. forecast delivery schedules: Transfer schedule implem.
MEQUERY1            Enhancement to Document Overview ME21N/ME51N
MEVME001            WE default quantity calc. and over/ underdelivery tolerance
MM06E001            User exits for EDI inbound and outbound purchasing documents
MM06E003            Number range and document number
MM06E004            Control import data screens in purchase order
MM06E005            Customer fields in purchasing document
MM06E007            Change document for requisitions upon conversion into PO
MM06E008            Monitoring of contr. target value in case of release orders
MM06E009            Relevant texts for "Texts exist" indicator
MM06E010            Field selection for vendor address
MM06E011            Activate PReq Block
MMAL0001            ALE source list distribution: Outbound processing
MMAL0002            ALE source list distribution: Inbound processing
MMAL0003            ALE purcasing info record distribution: Outbound processing
MMAL0004            ALE purchasing info record distribution: Inbound processing
MMDA0001            Default delivery addresses
MMFAB001            User exit for generation of release order
MRFLB001            Control Items for Contract Release Order
LMEDR001            Enhancements to print program
LMELA002            Adopt batch no. from shipping notification when posting a GR
LMELA010            Inbound shipping notification: Transfer item data from IDOC
LMEQR001            User exit for source determination
LMEXF001            Conditions in Purchasing Documents Without Invoice Receipt
LWSUS001            Customer-Specific Source Determination in Retail
M06B0001            Role determination for purchase requisition release
M06B0002            Changes to comm. structure for purchase requisition release
M06B0003            Number range and document number
M06B0004            Number range and document number
M06B0005            Changes to comm. structure for overall release of requisn.
M06E0004            Changes to communication structure for release purch. doc.
M06E0005            Role determination for release of purchasing documents
Regards,
Sujit

BADI for PO release strategy

Similar Messages

Maybe you are looking for