Release strategy control fields
I am doing release strategy in my project for P.O. Please answer follow question
a) by what fields we can control release strategy, and how we know can use only those particular fields control by these field
b) What is the difference between EKKO and CEKKO? Why CEKKO should use? Is that should use always C before EKKO? If yes, why?
Hi,
a) by what fields we can control release strategy, and how we know can use only those particular fields control by these field
--> You can use the fields to configure release startegy which are available in communication structure CEKKO. All fields in communication structure can be used to control release strategy.
b) What is the difference between EKKO and CEKKO? Why CEKKO should use? Is that should use always C before EKKO? If yes, why?
---> As said by Indranil, it is a communication structure and it is copied from the table EKKO to enable the release strategy.
System follows the below described procedure to apply release strategy. This will understand you more clearly.
When you process a purchase order (PO), the system passes on the data from the PO document to the communication structure CEKKO.
After the data has been passed on to the communication structure, the system initiates an object search:
1. The system checks which class is defined in Customizing for the release procedure.
Note
There can be only one class for all purchasing documents (POs, contracts, scheduling agreements, etc.). This one class (032)then constitutes the basis for the release procedures for all purchasing documents.
2. The system assigns the values from the communication structure CEKKO to the characteristics of this class.
3. Via the object search function, the system then identifies a release strategy whose characteristics accord with the values from the communication structure or lie within the specified interval.
The following search results are possible:
Just one release strategy is found.
The system assigns this release strategy to the purchasing document.
Several release strategies are found.
The system assigns the first release strategy found to the purchasing document.
No release strategy is found.
The system does not assign a release strategy to the purchasing document.
Hope above explaination helps you.
Deepak.
Similar Messages
-
PO release strategy is not triggering if Quantity pre.Qty
Standard SAP design will trigger the 'PO release strategy' if Total net order value (GNETW) is more than set. Lets take if PO created with Qty 100 and Price 50 then first time 'PO release strategy' is triggering when you save the PO. Next time when you change Qty less than the previous value like 80 from 100 then 'PO release strategy' is not triggering but if you enter more than previous value as 120 then its triggering. Ofcourse it makes sense but our user wants to trigger if any changes happened to QTY or PRICE. Is there anyway to trigger?
Found user exit - EXIT_SAPLEBND_002 but not sure what needs to be changed. Can one let me know the solution, if you have any.Hi.
According to note 493900, question 4, release strategy is reset only
for some specific case. Alternatively, please question 5 from this note
release strategy might be redetermined. However in order to determine a
new release strategy the field that is changed in PO must be included
as one of the fields in the strategy. Thus there is no standard way
for resetting/redermining release strategy for a change of e.g. text
on header or item level.
Please also kindly refer to other 2 useful notes for this area:
662993 Resetting an already occurred release
365604 FAQ: Release strategies in purchasing
BR
Nadia Orlandi -
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.
RDHello,
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 -
PR Release Strategy tab processor field is not getting displayed
Hi Experts,
While creating Purchase Requisition, In the Release Strategy tab processor field is not getting displayed which should be showing the name of the user id which has been configured in the SPRO.
SPRO--> Rel Proc for PR > Rel Group> Rel Code--> Object type (US) and --> Agent (User id who has to approve the PR).
release strategy - Release code -work flow 1
That processer name is not displaying
Thanks
chandooThis is the workflow forum.
-
Item category control the release strategy?
Hi,
Currently the purchase of a material needs to be released.
My issue is that as soon as I change the item category in the sales order,
the material does not need to be released.
How does item category control the release strategy?
Sincerely,
KetanHi Ketan,
You can set item category in the characteristic of a release strategy.
In your case, I guess the item category characteristic is already created. So you can just add the desire value into the characteristic.
Go to SPRO > IMG > Material Management > Purchasing > Purchase Requisition > Release Procedure > Procedure With Classification > Set Up Procedure With Classification > Release Strategies
Select the related release strategy, double click to view the detail. You will see there are 4 buttons in the bottom of the screen. Choose 'Classification' and enter you value of item category.
Thanks & regards,
JT -
How to control PO Release strategy using WorkFlow
please tell me how to control PO Release strategy using WorkFlow.
Moderator message: please search for available information/documentation.
Edited by: Thomas Zloch on May 31, 2011 9:35 AMHi,
Yes they are same unless you differentiate by using
1> Purchasing Document Category i.e CEKKO -BSTYP
A..... Request for Quotation
F......Purchase Order
K......Contract
L......Scheduling Agreement
So if you just create a characteristics for CEKKO-BSTYP then maintain its values only for F so it will not be applied to RFQ -
PO Release Strategy, include new field.
Hi,
What are the steps involved to include a new field ( for e.g Account Assignment Category ) which is not there in the standard structure CEKKO.
Shall I have to change the structure CEKKOZZ or from the user exit 'M06E0004'?
Thanks in advance,
Regards,
Madhu.Hi Arif,
Thanks for your reply. My requirement is to exclude a material group from PO release strategy.
If I include the characteristic related to material group in PO rlease class, and subsequently change the PO release startegy below is the problem.
Suppose PO contains one item or multiple with same material group, then only it is picking release strategy ( let us say all materials belong to mat group: 101)
If PO contains multiple items with different mat groups ( for e.g: 101, 102 & 103 ), then it is not picking up the Release strategy.
classification data is perfect and release strategy is ok for all material groups ( if PO contains only one material group)
I have checked in the program : MM06EF0S_STRATEGIE_CEKKO , the logic written in the program is such a way that, if two values exist for a doc field, then blank is passed to CEEKO structure.
I will try with user exit, and please let me know if you have any other idea.
Many Thanks,
Madhu. -
Contract Release Strategy - field Requisitioner
Hello,
I will start to use the Contract release strategy and I need the field Requisitioner (EKPO-AFNAM), because this field is part of my PO release strategy.
This field isn't available in the transactions ME31K and ME32K.
Can you tell me, if it's possible to show it in these transactions?
In other case, where can I fill this field? How is the BAPI, BADI, etc?
Thank you,
MeireHi,
Please, be so kind to refer to note 373361. This field was only
available in purchase requisitions and due to requirements of
SRM (formerly BBP business tons business procurement ), it has
been added into the new enjoy transaction
ME21N/22N/23N for purchase orders.
It is not available for contracts.
The contract is not the last document in the procurement.In bussiness
process the requirement of requisitioner in contract is less important.
It is enough if you don't know the requisitioner at the time of contract but
you know it at the time of PO creation.
This is the standard SAP design. Please do not use this field in the contract release strategy: create a new release group for the contract release strategy, delete the value entry for EKPO-AFNAM in the "Change view - release strategies - classificaion". The characteristic for EKPO-AFNAM should appear as black and not as blue on the screen. Save your strategy.
Regards,
Edit -
Issue with retriggering Release Strategy
Hi all,
We have a one off situation here. We had already 10 release staragies in our system. We added 2 more release strategies with a new characteristic. We updated the characteristic value only for the new 2 release strategues and did not update the rest 10. Although now we had updated the characteristic value for remaiining strategies, the purchase documents created in the mean tme is not subjected to release strategy. To ensure business control we need to retrigger back the release strategy for almost 1000's of documents.
As any change to purcahsing document will retrigger it when done manually, but given the number of documents and as per Note 493900 we cannot trigger it by any backgoriund job to modify as below:
16. Question :
Why is there no release strategy determination when a program changes in
background a purchasing document which corresponds to the classification of
a release strategy ?
Answer :
This is the system design that a release strategy determination can only be
triggered through a user action and not by changes made in background
process.
If you create a document (e.g. PO, Contract, etc), the determination of the
release strategy takes place only in case of a user event like checking or
saving the document.
Kindly suggest any best practise to retrigger release strategy for the missing documents to ensure business control. Any easy and time savig measure to get it resolved will be appreciated.
Regards,
Anand SampathHi Arnand,
After investigation by searching customer messages database ,I found
other customer has similar problem as the release strategy has changed
after creation of the SES please review the explanation from developer
:(whose release code is 03 )
When you try to revoke the acceptance of the service entry sheets
in ML81N or ML81, the 'Enter release code' pop up window appears, but
entering the code that is determined via the menu path Goto -> Entry
Sheet -> Release Strategy (which is the 03), the SES remains the same.
Nothing changes. The status does not vary and no error or warning
message is issued.
Checking the customizing for the release strategy, the release code
03 should have never been assigned to the SES 800024272 as the values
for the relevant characteristics were not included under that code.
I do not know how it was managed to accept the SES.
Now, when you try to revoke it, it seems that no release
strategy can be determined, not even including the values RCARESANO
and 012 between the valid values for the characteristics of the release
code 03 (RCARESANO as valid value for SUPERVISOR_SERVICIOS
(CESSR-ERNAM)and 012 as valid value for GRUPO_COMPRAS (CESSR-EKGRP)).
The only Possibility is to change now the SES so that the release
strategy can be re-determined by the system.This is the Only possible
way that the system can redetermine the Release Strategy , but it will
not be possible to do so as the SES is already accepted with the Old
strategy and it does not admit any further changes.
To be able to change it you would need to revoke the SES first,
but this Will also not be possible as the Release Strategy was changed
and the system still applies the old rules for determining the Release.
Solution to our Problem
The Only way to revoke the SES is to Restore back the Old Strategy that
was prior to 03 in the customizing.So now what will happen is that by
applying the Old Rules the System will be able to revoke the SES that#s
using the Old one. Once the necessary SES are revoked then go back to
customizing and apply the new strategy as it was did now, and
Change the SES and save , the new value of the Release Strategy will get
updated in the table ESSR and the field frgsx will now have 03.
Problems associated if the Release strategy is changed
Actually the release strategy is not supposed to be changed when there
are some documents in the System that uses it and even if you change the
Strategy the Old records will not get AUTOMATICALLY UPDATED by the
system.The Release Strategy routine has to run again to update the
values. This is Possible by changing the document SES ,
This change will happen only if the SES is not accepted and if its
accepted then you need to revoke and to revoke you need to restore the
old strategy , revoke and then change the SES , and have to go back to
customizing and Start using the New strategy from now on by doing so the
Routine will update the old record with the new strategy.
b) You may want to use CEKKO-BADAT(Requisition Date) or any other
structure in CEBAN or CEKKO and create a new release strategy
to differentiate the old release strategy.
Hope this helps,
Kind Regards,
Matthew -
How to setup a release strategy for store generated purchase order
Hi there,
Does anybody know how to setup a release strategy for store/plant generated purchase order? I have a request from our client, but I never cross this before. Please help and let me know the step with every single detail.
Greatly thank for your help.
Kind Regards,
2teaPlease go thru the below Release Procedure and check whether you have maintained all the settings properly.
PO RELEASE STRATEGY
The release code is a two-character ID allowing a person to release (clear, or approve) a requisition or an external purchasing document. The release codes is basically controlled via a system of authorizations (authorization object M_EINK_FRG).
Use SE12, structure CEKKO to check all the fields available for controlling the Purchase Order.
e.g. If the total value for the Purchase Order exceeds 10,000, release strategy 01 is assigned to the Purchase Order. There is only one characteristic created in this example. For controlling the Purchase Order type, create characteristic for CEKKO-BSTYP and the value NB.
CT04 - Create Characteristic e.g. NETVALUE
Click Additional data Table name CEKKO Field name GNETW and press enter
(for currency dependent field, you are prompt to enter the currency which the system then converts the currency of the Purchasing document into this currency)
In the Basic data (X refers to tick),
X Mutliple values
X Interval values
In the Value data, in the Char. value column, type >10000 and press enter
Save your data
CL02 - Class
Class - Create REL_PUR
Class type - 032
Click Create
Description - Release Procedure for Purchase Order
In the Same Classification section, click Check with error
In the Char. (characteristic) tab, type NETVALUE to assign your characteristics to the class
OMGS - Define Release Procedure for Purchase Order Type
Release Group - New entries
Rel.group Rel. Object Class Description
02 REL_PUR Rel. Strategy for PO
Release codes - New entries
Grp Code
02 01
Release indicators
Release indicators Release Description
0 Blocked
1 X Release
Release Strategy
Release group 02
Rel.strategy 01
Release codes 01
Release status 01
Classification Choose your check values
OMGSCK - Check Release Strategies
(make sure there are no error messages)
Once the Purchase Order is not release, buyers will not be able to print the Purchase Order.
Goods Receipts will be shown with Message no. ME 390 - Purchasing document XXXXXXX not yet released.
In 4.6c, Purchase Order with Release Strategy have a tabs at the end of the Header. This allowed the buyers to check the release status of the Purchase Order.
The person with the release authorization have to use ME28 to release the Purchase Order.
Regards,
Ashok -
New Release Strategy in case of PO amendment
Dear All,
We have the release strategy at PO level on 3 parameters,
Purchasing Group, Value and Document type.. for each parameter we have created the characteristics EKKO- EKGRP, EKKO-BSART, EKKO-GNETW. Till date system is working ok and trigreeeing the release strategy as per it should.
When ever users edit the PO, again system sets the release strategy as per above logic.
Now our requiremet is, when ever user edite the PO value or PO quantity, system should trigger a new release strategy.I come to know that, SAP have a provision to maintain the release strategy on "Version level also", I have tried the same but i facing one problem, when we try to create the characteristic based on Version , system creates it and put field name "REVNO", data types is coming "CHAR".
Can any one send me a user manual and steps for this.
Thanks in advance,.
VikasHi,
You can set a control within Config. there is a parameter called as release indicator.
Follow this IMG path:
SPRO> Materials Management>Purchasing>Purchase Order>Release Procedure for Purchase Orders>Define Release Procedure for Purchase Orders>Release indicator
1 Cannot be changed
2 Changeable, no new determination of strategy
3 Changeable, new release in case of new strategy
4 Changeable, new release in case of new strat. or val. change
5 Changeable, new release if new strategy/outputted
6 Changeable, new rel. if new strat. or value change/outputted
Changeable, new release in case of new strategy
Changeability of purchasing document during/after release which means how the system reacts if an internal or external purchasing document is changed after the start of the release procedure.
Note that the values 1 to 4 apply to internal purchasing documents (purchase requisitions) and the values 1 bis6 to external purchasing documents.
So you would need to set this Indicator for the specific release Id. which specifies whether the purchasing document can be processed in or is blocked for follow-on functions.
Hope this explanation was clear.
Prashant Rathore. -
Purchase Order not subject to release strategy
Good day everyone!
I've created one release strategy for all my purchasing documents. The characteristic is net value, and the value of this characteristic is >=0.00. Meaning, ALL purchase orders are subject to release strategy.
After I did the release strategy in SPRO, I created a few PO and when I tried to release them, I got this message: "Purchasing document 45xxxxxxxx not subject to release strategy".
My question is: How to assign purchasing document to release strategy?
Please help. Thank you in advance.
Anisahhi
yes you have to use table CEKKO for PO release strategy , now , in PO you can't create without clasification so it will be applicabe for whole PO not for line items ,
now below i am giving u one by one steps , follow and let me know .
The release code is a two-character ID allowing a person to release (clear, or approve) a requisition or an external purchasing document. The release codes is basically controlled via a system of authorizations (authorization object M_EINK_FRG).
Use SE12, structure CEKKO to check all the fields available for controlling the Purchase Order.
e.g. If the total value for the Purchase Order exceeds 10,000, release strategy 01 is assigned to the Purchase Order. There is only one characteristic created in this example. For controlling the Purchase Order type, create characteristic for CEKKO-BSTYP and the value NB.
CT04 - Create Characteristic e.g. NETVALUE
Click Additional data Table name CEKKO Field name GNETW and press enter
(for currency dependent field, you are prompt to enter the currency which the system then converts the currency of the Purchasing document into this currency)
In the Basic data (X refers to tick),
X Mutliple values
X Interval values
In the Value data, in the Char. value column, type >10000 and press enter
Save your data
CL02 - Class
Class - Create REL_PUR
Class type - 032
Click Create
Description - Release Procedure for Purchase Order
In the Same Classification section, click Check with error
In the Char. (characteristic) tab, type NETVALUE to assign your characteristics to the class
OMGS - Define Release Procedure for Purchase Order Type
Release Group - New entries
Rel.group Rel. Object Class Description
02 REL_PUR Rel. Strategy for PO
Release codes - New entries
Grp Code
02 01
Release indicators
Release indicators Release Description
0 Blocked
1 X Release
Release Strategy
Release group 02
Rel.strategy 01
Release codes 01
Release status 0
1
Classification Choose your check values
OMGSCK - Check Release Strategies
(make sure there are no error messages)
Once the Purchase Order is not release, buyers will not be able to print the Purchase Order.
Goods Receipts will be shown with Message no. ME 390 - Purchasing document XXXXXXX not yet released.
In 4.6c, Purchase Order with Release Strategy have a tabs at the end of the Header. This allowed the buyers to check the release status of the Purchase Order.
The person with the release authorization have to use ME28 to release the Purchase Order.
regards
ravikant dewangan -
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.
MickHi
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 -
Types of release strategy's?
Hi Guys
what are the types of release strategy?
other than value based what else criteria does the release strategy can be made?
could you please share some of your real time strategy's followed by your company.
Any answers would be greatly appreciated.
cheerswhat are the types of release strategy?
Ther is no types but based on the requirements you can create the release strategy
It's not neccesary that you can creta only value based but you can use for any purpose as long as you want to control your PO or PR or any purchase document go out without any supervision in this case you can create based on the field avilabe for release strategy
e.g. for PO you can use any field from CEKKO table and for PR - CEBAN table
i have scenario in one of my project is i don;t want my PR should directly go to purchasing without label approvla in this case the price was not creiteria but the material group was the criteri like wise you can use any criteria to hold the document go without approval -
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
Maybe you are looking for
-
PLEASE HELP!!!!!!! i have had this problem for 2 months!
-
Graduated method in financial statement version
Hi, Can anyone explain me what is graduated total method in financial statement version creation in simple words. Thanks Mona
-
Itunes says I have 7 app updates but only 6 show
For the past couple weeks my itunes window displays that i have 1 more update then actually displays. For instance tonight in the top left "Library" section of iTunes besides Apps the number 8 is displayed (meaning there are 8 updates to apps). Howev
-
Hi, I am using the following query to get customer listing. When I run the statement for one party_id in the first select statement, it works but if I remove that condition I get Ora-01427 error... select distinct ( select hl.address1 from hz_cust_ac
-
Hi, I want to purchase a subscription for Lightroom 5. I am looking in investing in a better laptop in a few months. I plan on initially downloading LR5 to my desktop but hope to download it to my new laptop later on. Will this be possible? Also,