Enhancement M06E0004 P.O. Release strategy

Hi ALL,
How to correct the below error message.
*********SAP log** tcode :OMGSCK
You must maintain a customer exit for characteristic Z_COSTCENTER
Diagnosis
You have linked the characteristic Z_COSTCENTER with field USRN1 of the communication structure CEKKO. In the standard system, this field is not populated. The data must therefor be determined in a customer exit.
Example
The person responsible for a cost center in a purchase requisition is to be determined. The name of this person is read from the cost center master record, placed in the field USRC1, and passed on to communication structure CEBAN.
The following customer exits are available to you:
Purchase requisition M06B0002
PO, RFQ, contract,
scheduling agreement M06E0004
Procedure
Check that you have maintained the relevant customer exit.
if any one has work on I_CEKKO this structure and used USRN1 field to validate some condition.
Please write me ..
Thanks ,
Shravan

Similar Messages

ML81N Enhancement to trigger the 'Release Strategy'..very urgent !!

Hi Guys,
ML81N work in a manner such that if the net amount for any PO/Service entry is less than $2500 then its 'Release Strategy' tab is not active, because the minimum value should be 5000$ to trigger the 'Release Strategy'.
I have a requirement where i have to make that tab active and select the Lowest Release Strategy (the one for 5000$) even when the amount is less than $2500.
I have already tried with the ser exit EXIT_SAPLEBND_003, its a blank user exit and the structure available is CESSR.
Can any one tell me how to activate the 'Release Strategy' tab and the lowest Release stratedy should be selected ????
What i have investigated is that once i will set the Release Strategy to the lowest Release stratedy then that tab will automatically become active.
Please tell me how to select the lowest Release strategy using the CESSR structure ?
Points will be awarded...
Thanks
Rahul

Use this exit.
MM06E005

User exit (To change the PO Release Strategy): M06E0004

Dear Experts,
         I am trying to implement the enhancement for changing the PO release strategy, using exit M06E0004 for following situation.
If PO is already released and then if any changes made to it affects the net amount which makes it less than previous net amount. We have to change the PO Release indicator to 'Blocked'.
We have tried to change the value of USRC1 USRC2 USRN1 USRN2 of structure E_CEKKO but it is not workingu2026
Please help me *how / what to change in the E_CEKKO structure*.
I am new to User Exit.

Hi Nagarajun,
I am able to solve this problem.!
All u have to do is follwoing two step.
1.maintained a flag in ur enhacement part (FM to Z_FIND_PO_RELEASE_STRATEGY)
inorder to know whether the current PO is without PR or not then export its value to memory.
2.Do enhancement in standard FM ME_REL_STRATEGIE_EKKO
(which is used to reset release strategy and indicator).
Inside this fm u can find below code
if xchange ne space.
*- Strategie geändert --------------------------------------------------
    if e_frgst ne i_frgst or
       e_frggr ne i_frggr.
      perform reset
         using e_frgst e_frggr
               e_frgzu e_frgkz e_frgrl.
      e_reset = 'X'.
*- Wertänderung prüfen -------------------------------------------------
    else.
      if t16fb-kzfae eq '4' or
         t16fb-kzfae eq '6' .
         perform currency_conversion using *cekko-waers
                                          bwkurs_old
                                          hwaers
                                          fwaers
                                          bwkurs
                                    changing *cekko-gnetw.
        f1 = *cekko-gnetw * t16fb-tlfae / 1000.
        f1 = f1 + *cekko-gnetw.
        if cekko-gnetw gt f1.
          perform reset
            using e_frgst e_frggr
                  e_frgzu e_frgkz e_frgrl.
          e_reset = 'X'.
        endif.
      endif.
    endif.
else.
    perform reset
       using e_frgst e_frggr
             e_frgzu e_frgkz e_frgrl.
endif.....
above code is use to check the PO amount and with old net amount,Since normally code is done to reset indicator only when amount is greater than old one, u can copy above code and modify with ur condition(i.e flag) and paste in last line.
Please check & reward is useful.

Enhancement for Release strategy PO

Hi,
Is there any User Exit or Enhancement Section available for sending an email to buyer after releasing the PO in case of release strategy PO ??
Thanks
Nishad

Hi
You can you the BADI ME_PROCESS_PO_CUST for this process and try to implement the method close.
It triggers when the user leaves the transaction after transacation commit triggers. So here you can retrieve the header data using the method of get_data.
In the retrieved structure you can see the release strategy and you can do what ever you want to implement.
Please let me know, if any details requried.
Thanks
Praveen

How to Use User Exit M06E0004 for RElease Strategy

Hi All,
MY client is currently having release strategy based on Net order value. Now they want that release order should be based on Net order value plus other charges (Frieght).
I have to write logic that this will be done through User exit M06E0004.
BUt I have no idea that how to carry out user Exit.
Please let me know that what logic shoul I mention in the functional design to change this Release strategy.
Thanks

create a prohect.
assign component
activate project

User Exit for Purchase Order Release Strategy

Hi,
I am a little new to this, how do I search for a user exit for purchase order release strategy (TCode ME29N).
Thanks in advance.
Mick

Hi
Check the following Exits and BADI for Pur Requisition
Enhancement
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
AMPL0001 User subscreen for additional data on AMPL
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
MEQUERY1 Enhancement to Document Overview ME21N/ME51N
MELAB001 Gen. forecast delivery schedules: Transfer schedule implem.
MEFLD004 Determine earliest delivery date f. check w. GR (only PO)
MEETA001 Define schedule line type (backlog, immed. req., preview)
ME590001 Grouping of requsitions for PO split in ME59
M06E0005 Role determination for release of purchasing documents
M06E0004 Changes to communication structure for release purch. doc.
M06B0005 Changes to comm. structure for overall release of requisn.
M06B0004 Number range and document number
Business Add-in
ME_PROCESS_REQ_CUST Enhancements for Processing Enjoy PReqs: Customer
ME_PROCESS_REQ Enhancements for Processing Enjoy PReqs: Internal
ME_PROCESS_PO_CUST Enhancements for Processing Enjoy Purchase Order: Customer
ME_PROCESS_PO Enhancements for Processing Enjoy Purchase Order: Intern.
ME_PROCESS_COMP Processing of Component Default Data at Time of GR: Custome
ME_PO_SC_SRV BAdI: Service Tab Page for Subcontracting
ME_PO_PRICING_CUST Enhancements to Price Determination: Customer
ME_PO_PRICING Enhancements to Price Determination: Internal
ME_INFOREC_SEND Capture/Send Purchase Info Record Changes - Internal Use
ME_HOLD_PO Hold Enjoy Purchase Orders: Activation/Deactivation
ME_GUI_PO_CUST Customer's Own Screens in Enjoy Purchase Order
ME_FIELDSTATUS_STOCK FM Account Assignment Behavior for Stock PR/PO
ME_DP_CLEARING Clearing (Offsetting) of Down Payments and Payment Requests
ME_PURCHDOC_POSTED Purchasing Document Posted
SMOD_MRFLB001 Control Items for Contract Release Order
EXTENSION_US_TAXES Extended Tax Calculation with Additional Data
ARC_MM_EKKO_WRITE BAdI: Enhancement of Scope of Archiving (MM_EKKO)
ARC_MM_EKKO_CHECK BAdI: Enhancement of Archivability Check (MM_EKKO)
MM_EDI_DESADV_IN Supplementation of Delivery Interface from Purchase Order
MM_DELIVERY_ADDR_SAP Determination of Delivery Address
ME_WRF_STD_DNG PO Controlling Reminder: Extension to Standard Reminder
ME_TRIGGER_ATP Triggers New ATP for Changes in EKKO, EKPO, EKPV
ME_TRF_RULE_CUST_OFF BADI for Deactivation of Field T161V-REVFE
ME_TAX_FROM_ADDRESS Tax jurisdiction code taken from address
ME_REQ_POSTED Purchase Requisition Posted
ME_REQ_OI_EXT Commitment Update in the Case of External Requisitions
ME_RELEASE_CREATE BAdI: Release Creation for Sched.Agrmts with Release Docu.
ME_DEFINE_CALCTYPE Control of Pricing Type: Additional Fields
ME_CHANGE_OUTTAB Enrich ALV Output Table in Purchasing
ME_CHANGE_CHARACTER Customer-Specific Characteristics for Product Allocation
ME_CCP_DEL_DURATION Calc. of Delivery Duration in CCP Process (Not in Standard)
ME_CCP_BESWK_AUTH_CH BAdI for authorization checks for procuring plant
ME_CCP_ACTIVE_CHECK BAdI to check whether CCP process is active
ME_BSART_DET Change document type for automatically generated POs
ME_BAPI_PR_CREATE_02
ME_BAPI_PR_CREATE_01
ME_BAPI_PO_CREATE_02
ME_BAPI_PO_CREATE_01
ME_BADI_DISPLAY_DOC BAdI for Internal Control of Transaction to be Invoked
ME_ACTV_CANCEL_PO BAdI for Activating the Cancel Function at Header Level
MEGUI_LAYOUT BAdI for Enjoy Purchasing GUI
ME_CHECK_ALL_ITEMS Run Through Items Again in the Event of Changes in EKKO
ME_COMMTMNT_REQ_RE_C Check of Commitment Relevance of Purchase Requisitions
ME_COMMTMNT_REQ_RELE Check of Commitment Relevance of Purchase Requisitions
ME_COMMTMNT_PO_REL_C Check for Commitment-Relevance of Purchase Orders
ME_COMMTMNT_PO_RELEV Check for Commitment-Relevance of Purchase Orders
ME_COMMITMENT_STO_CH BadI for checking if commitments for STOs are active
ME_COMMITMENT_RETURN Commitment for return item
ME_CIP_REF_CHAR Enables Reference Characteristics in Purchasing
ME_CIP_ALLOW_CHANGE Configuration in Purchasing: Changeability Control
ME_CIN_MM06EFKO Copy PO data for use by Country version India
ME_CIN_LEINRF2V BADI for LEINRF03 excise_invoice_details
ME_CIN_LEINRF2R BADI for CIN India - Delivery charges
ME_CHECK_SOURCES Additional Checks in Source Determination/Checking
ME_CHECK_OA Check BAdI for Contracts
Reward points if useful
Rgds,
Naren

Chek budget in PO with release strategy

Hi
When i created a PO with a release strategy and the comand need it, the budget are not checking at the save, only when i release the PO.
Is it possible to check the budget (on a PM order or on WBS element) at the PO save.
Thank's
serge

Normally checks like those happen once the PO is released ( example - output is not allowed etc)...
You may need to add something in the PO release strategy user exit to do the check before release (after save), Look into the below to see if this works.
Name of the Enhancement: - M06E0004
Name of the function module: - EXIT_SAPLEBND_002
Hope this helps

PO release strategy based on Account Assignment Cat (CEKKO - KNTTP)

Hi Experts,
I want to configure the release strategy for PO on account assignment category.when i maintaining a characteristic for account assignment cat by inputing CEKKO- KNTTP , sys throughs error message. I looked in to CEKKO but I could not find the field .Kindly tel how maintain teh same .
Regards,
Kumar.

Hi Kumar,
Account Assignment Category and Item Category belong to the item level and not to the header level of a purchase order (table EKPO). Therefore,   neither Account Assignment Category nor Item Category are available in CEKKO.As work-around you can use the following user-exit:
MM06EF0S_STRATEGIE_CEKKO
(enhancement M06E0004, EXIT_SAPLEBND_002, ZXM06U22).
In this user-exit the data are available in structure I_CEKKO.   The hand-over from I_CEKKO to the calling program is via structure E_CEKKO.   In the user-exit I_CEKKO has to be copied to E_CEKKO , e.g.
E_CEKKO = I_CEKKO.
Please also see our FAQ note 365604, it is worth reading.
Regards,
Mauro

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

Release strategy complex customer specific checks

Hi MM guys,
does anybody knows whether there are UserExits for the release strategy functionality in 46C? We´re already using this strategy functionality via classification. But now we´ve got further request concerning the checks which have to be processed to determine wether a PO will be released or locked. These checks cannot be implemented over the classification system cause they´re more complex.
Thx, for any tips.
Andy

Hi,
The Enhancement for this purpose is M06E0004 and the user exit is EXIT_SAPLEBND_002.
You can use this user exit to pass values in user defined fields (e.g. USRC1, USRC2 etc) in structure CEKKO. If the user fields given in the structure not enough then this structure can be expanded and new fields can be added.
While using this user exit, please keep in mind that the user exit gets called while you start the transaction (e.g. ME29N) and you check or save the document. So when you want to pass values, you will do so only at the time of saving the document.
Regards.

PR Release strategy

Dear All,
We want that if any user change account assignment(Cost center,G/L.Order etc..) in PR the release should reset and need reapprovals.
Please let me know how we can achieve this.
Thanks.

Hi ,
           In standard design system only considers characteristics from
CEKKO structure for release strategy consideration. But it will not
stop us in selecting the other characteristics.
Please go through the IMG help of release strategy, will give good
information.
I think you have already read the note:
The characteristics of the class used must all be linked to the
       corresponding fields of structure CEBAN or CEKKO (for purchase
       orders)...."
Characteristics which are created for the release strategy with
classification MUST access communication structures CEBAN or CEKKO since
during the strategy determination, the system cannot access any other
tables or structures.
If the characteristics refer to fields which are not contained in
structures CEBAN or CEKKO, the corresponding fields can be added to
communication structure CEKKOZZ or CEBANZZ, or an append structure can
be created for CEKKO or CEBAN in which new fields can be included.
If you want to use new defined fields as part of the
release strategy clasification, you should use enhancement M06E0004
(User exit "exit_saplebnd_002").This user exit allows you to use the
user fields in strucure CEKKO to include additional data.
Use the user fields of this structure: USRC1, USRC2, USRN1 or USRN2 and
control them through user exit "EXIT_SAPLEBND_002. Otherwise new field
will not work.
As you very well know SAP has provided the following customer exits
which allow us to change the communication structure for determining
the release strategy
Purchase requisition
                       M06E0002 - for item wise release
                       M06E0005 - for overall release
External purchasing document
                       M06E0004
I hope this helps!
Regards
Vijayesh V V

PO release strategy on Overall limit of the PO

HI All,
Presently release strategy in R/3 Purchase order is triggered on Total net order value ( i.e. CEKKO - GNETW ) > 250.
For limit PO it triggered on Expected value but we want to trigger it on Overall Limit value.
( If Overall limit = 1000 and Expected value = 100 release strategy should trigger on Overall limit)
Please help on this.
we have used the enhancement used : M06E0004 , Exit EXIT_SAPLEBND_002.
But I do not find the table or field showing the overall limit of the PO so that I can put the same in my purchase order release stucture.
Thanks in advance, will appreciate any help on this regard,
Anurag Goel

Hi
The expected value is the value that the item is not likely to exeed. in std SAP the expected value serves as a creterian for a possible release procedure for limit p.o
Thanks

PO Release strategy on Overall Limit

HI All,
Presently release strategy in R/3 Purchase order is triggered on Total net order value ( i.e. CEKKO - GNETW ) > 250.
For limit PO it triggered on Exepected value but we want to trigger it on Overall Limit value.
( If Overall limit = 1000 and Expected value = 100 release strategy should trigger on Overall limit)
Please help on this.
Thanks in advance
Vikas

Dear Vikas,
you can use enhancement M06E0004 , Exit EXIT_SAPLEBND_002.
This allows to change values in structure CEKKO based on specific conditions.
First after activating you have to put this line:
e_cekko = i_cekko.
This means that no change will be made to cekko structure. Then if you want to change gnetw value, do something like this:
e_cekko = i_cekko.
If xxxxxxxxxxxxxxx.
e_cekko-gnetw = xxxxxxxxx.
endif.
Maybe you can have multiple items so you will have probably to loop on IT_BEKPO table to get the total Overall Limit for all items in your document and then transfer the total value.
Good luck,
SL

PO release strategy for changes in price ($ and %)

Hello,
I have searched this forum and others to find an answer to my question, but as I was unsuccessful, I decided to post my question here.
I have a requirement for a PO release strategy that involves triggering the release strategy only if the total value of the PO has increased over a certain dollar amount or %. I will need to calculate the difference in the total value between the original PO and the changed PO.
Example:
Original PO total net value is $1000
PO after a price change - total net value is $1500
Total net value has increased by $500 or 50%.
Tolerance for price change is $200 or $20, so tolerance has been exceeded.
I know I will be using the total net order value (CEKKO-GNETW). I will have my tolerances in a custom table, and I will need to take the difference in the total net value from the changed PO and the original PO and check against my custom tolerance table. I also know that I will use a user defined field (CEKKO-USRC1) to indicate if the tolerance has been exceeded or not. I know that I will put this tolerance check code in the M06E0004 enhancement for changes to communication structure for release of PO.
What I don't know is where will I find the previous total net order value once the PO has been changed? Is the only place that information is stored in the change logs? If so, what is the change log table name? Or is there a different table that would contain this information?
Thanks in advance for any help you can provide.
Sincerely,
Angela

Update:
I utilized function module EXIT_SAPLEBND_002 as a solution to this. I got the old PO value from the database table EKPO, and I got the new/changed value from the I_CEKKO structure which is accessible from this FM.
I check to see if my tolerance has been exceeded. If it has, I pass a 'Y' as a tolerance flag via CEKKO-USRC1.
I originally thought about using the change document tables, but I discounted this when I discovered that those tables weren't updated at the time that the function module EXIT_SAPLEBND_002 was being hit.

Enhancement M06E0004, EXIT_SAPLEBND_002, ZXM06U22

Hi Experts,
I am writing some logic while PO creation in the user exist ZXM06U22.
As per my understanding this user exit should trigger for all the company code but its getting triggere for only few company code, I am not able to understand why its not getting trigger for all the company code.
its already in use for some other functionality.
Please suggest.
Sagar.

Hi Sagar,
The Enhancement M06E0004 is basically used to change the communication structure, which can inturn be used to trigger the release strategy if you want to calculate few values in runtime.
If the exit is not getting triggered for few company codes i would suggest you to check the functional configuration steps where characteristics, groups, codes, strategies are defined.. may be there are chances that few company codes are not configured for release strategy.
Regards,
deepak.

Enhancement M06E0004 P.O. Release strategy

Similar Messages

Maybe you are looking for