BAPI_REQUISITION_DELETE (Clears Release Strategy)

Hi guys,
Hoping you can help with a query. I'm using BAPI_REQUISITION_DELETE to delete a line item off a Stock Transport Requisition. The bapi is clearing the following fields in Table EBAN:
- EBAN-FRGKZ (Release ind.)
- EBAN-FRGZU (Release status )
- EBAN-FRGST (Rel. strategy)
I don't want this to happen as deleting one item from the STR should not clear the release strategy.
Has anyone encountered this before? I can't see an option in the BADI to prevent this from happening.
Many Thanks,
Philip Johannesen

Hi Philip,
we have the same issue.
Which the OSS Note?
Thank you in advance.
Regards

Similar Messages

Clear release strategy

We have implemented a workflow solution for approving purchase requisitions. When a user changes a partially approved req, we want the the current workflow to be cancelled and a new one started with a new cleared release strategy.
I think I can use the ME_UPDATE_REQUISITION_RELEASE to update eban-frgzu to null, which will reset the release strategy. However, all of the user exits that I've found up to this point get overwritten.
My questions:
Is there a good place to add this function? EXIT_SAPLEBND_004 seems like the place but the frgzu field get's overwritten later in the process.
Is there an easier way of resetting the release strategy?
Thanks
Travis

Hi,
Check the following link:
http://www.sap-img.com/workflow/sap-workflow.htm
Regards,
Bhaskar

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,
2tea

Please 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,.
Vikas

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

Release strategy of contract disappeared after using of MEMASSCONTRACT

Hi All,
May be some one can help me?
I have next problem it tr. MEMASSCONTRACT(ECC6)
Release strategy of contract disappeared after using of tr. MEMASSCONTRACT. I know why it happened, but I don't know how to correct it. Some time ago IN ECC5 we added a field to a table EKKO and used this field as one of characteristics in the release strategy of contracts. In order to transfer value of this field to field CEKKO-USRC1 we used User Exit EXIT_SAPLEBND_002. This User Exit is suitable only for online transactions (ME31K, ME32K). How can I feel field CEKKO-USRC1 in transaction MEMASSCONTRACT?
Regards, Liza

Thank you. Probably I didn't explain my problem clearly. It's section of code from User Exit EXIT_SAPLEBND_002:
ATA: reference(20) TYPE c VALUE '(SAPMM06E)EKKO'.
DATA: it_ekko TYPE ekko.
FIELD-SYMBOLS: <ymm_icl> TYPE ANY.
e_cekko = i_cekko.
*THE "ICL Contract" FIELD IS ONLY RELEVENT IN THESE TRANSACTIONS
IF sy-tcode EQ 'ME31K' OR sy-tcode EQ 'ME32K'
OR sy-tcode EQ 'ME33K' .
ASSIGN (reference) TO <ymm_icl>.
it_ekko = <ymm_icl>.
e_cekko-usrc1 = it_ekko-ymm_icl.
ENDIF.
Program SAPMM06E can only be reffered while using online transactions. Mass transactions does not use these program and it is completely class based. So, may be someone know how can i do the same , but for tr. MASS in ECC6.

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

hi
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

Purchase order release strategy with multiple characteristics

Hi All,
We have Purchase order release strategy based on the following characteristics:
Total Net Order Value
Purchasing Organization
Release strategy Type
a few other custom fields
We would like to have PO's with release strategy based on a particular Material Group [say X]. I have created a new Characteristic with respect to CEKKO-MATKL and added this characteristic to the same class.
I have created a new release code [HR] [we need a different person to sign off] and a new release strategy [TR] for which I have assigned the release code HR. In this release strategy, I have set it to get activated for a particular Material Group that does seem to work, but the remaining PO's are not getting triggered for other material groups. For other release strategies, I have left the material group field blank, because they need to be triggered for any material groups except X.
Could you please let me know if I am missing something or is there an alternate approach to this ?
Thank you,
Satish

Hi,
Obviously system will not trigger release strategy in ur case since in the classification data for other strategies u have left it blank excepting X for one strategy.
Since u have added a new characteristic Material group and assigned it to class then system expects an input for Material group for triggering release tab.If this is left blank then system by default will not trigger release strategy tab.
Solution:
First add all existing material groups in values tab of mat group characteristic then maintain the required set of material groups except X in other strategies in classification data.
Hope this is clear to you.
Regards,
Uzair

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

Release Strategy vs. Delete (Purchase Requisition)

When my Purchase Requisition hasn't got a Release Strategy I can mark it as deleted using BapiDelete from the Purchase Requisition business object. But when is has got a Release Strategy I can not. Is it right? Am I missing something? Or maybe haven't I got the privileges to delete an Item?

I am assuming that you are using the BAPI_REQUISITION_DELETE. If I look at the code, there is a comment that says 'Requisitions with dependent reservations won't be processed'.
So if your requisition item creates a reservation then you will not be able to delete the item. It doesn't give you any error message but gives a warning message 'Subcontracting item & & not processed due to reservations'for that. Here is the condition that it is checking.
IF xeban-pstyp EQ 3 AND xeban-rsnum NE space.
So if you are deleting more than one item at the same time and one of them meets that above criteria, then it will not be processed for deletion, but you will see a success message because the other items are processed correctly. If you look at the entire return messages, you might find a warning message in there for the item that didn't get deleted.
Srinivas

Po Release Strategy Change

Hi Gurus
I am changing the release strategy for po.
Same characterstics and value also same.
only change is release codes. so that, what i can do. if i add new release codes in same old strategies ?
Otherwise i can create new release strategies ?
if i create new what i have to take steps ?
if i use same old release strategy and in that i can chage release codes what about previous documents ?
client side cl24n here we can block old stratiges what about the documents created on old ?
If any body answer right rewarded full.
Thanks in advance
Regards
Laxman

Hi
we have also did some changes to relase codes after once in use & we had encountered some problems in the PO.
For E.g. If you have the previous repease codes as L1 & L2 , & if you are removeing the L2 form the release codes then All the PO's whcih are approved by L1 & awaiting tobe approed by L2 will be in hanging status. You need to go into each PO 7 click on revoke acceptance & Click on check then The new relase codes will appear.
If you can clearly explain what you are planning to do on the relase codes , then we can advise you in the right manner.
Thanks & Regards
Kishore

To avoid deleted item of P.O in release Strategy

Dear all
We are facing a problem. our user deleting the line item of a P.O and this is routed through release strategy. Is there any configuration that , any deleted item in P.O can by pass release strategy. Shall be grateful, if you could kindly urgently help me,
Kind Regards - P.L.dey

Thanks ....I have seen the structure for the PO release.I have gone thouogh the parameters of the function module of the user exit...But to me it is not clear how to incorporate the Deletion indicator of the PO item in the code...
Hope to hear from you.......
Regards

EXIT_SAPLEBND_002 -- user exit for release strategy

Hi,
This is regarding help on user exit for release strategy, ref: note no. 365604, however after going through all the config part given in the given note we activate the fm in cmod.... but after activating the release tab goes off from me29n.
That is after you activate in cmod and then if u create po and go to me29n the relese tab is not there.
if u deactivate and create po and then relese the release tab in me29 would appear.
All we are trying is that the po in me29n should be open to release again if we change the delivery date. However what coding and how is still a second step , first is as soon as the exit is active the tab goes off.
New to user exit . plz help.

Hi Again,
I guess I have solved the issue temporarily, however Am not sure if this is the best which cld be doen to the issue.
I didnt make any new characteristics in ct04, for the delivery dats since i didn't want to restrict the delivery date. All I did i yje coding below in the exit :
DATA wa_eket TYPE LINE OF mmpur_beket.
DATA wa_eket1 TYPE LINE OF mmpur_beket.
data: c type i.
 data: p type i.
break1.
break2.
e_cekko = i_cekko.
loop at it_beket into wa_eket . " for comparing previous and the current del date
e_cekko-usrc1 = wa_eket-eindt.
SELECT SINGLE * FROM eket INTO wa_eket1 WHERE ebeln = wa_eket-ebeln
AND ebelp = wa_eket-ebelp.
if wa_eket1-eindt <> wa_eket-eindt.
import c from memory id 'CID'.
c = c + 1.
clear p.
p = c mod 2.
if p is not initial. " adding 0.01 to the characteristic value for p.o amt.
e_cekko-GNETW = e_cekko-GNETW + '0.01'.
else.
e_cekko-GNETW = e_cekko-GNETW - '0.01'.
export c to memory id 'CID'.
endif.
endif.
endloop.
The logic I tried using is since the relese gets reset incase of p.o amnt and hence indirectly po amnt so i changed the value of p.o value by 0.01 incase of change in delivery date. cekok-gnetw doesnt reflect anywhere in the p.o as amnt, I guess its for defing range for relese stragey's amont in ct04 characteristics.
However anything better incase u know plz let me know, or do u think this can cause any problems later....new to exits.
Rgds,
Anu.

Release Strategy with New Class and Char.

Dear All,
I have facing problem when creating the new release strategy for different country. i have create new Characteristic and class for new Release streategy.
when i going to add in Release group.. system giving the error.
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.
My existing Characteristic for india :
ZP0_GNETW     Total net order value     CURR     15     2     INR
ZPO_BSART     Order type (Purchasing)     CHAR     4     0
ZPO_EKORG     Purchasing Organization     CHAR     4     0
ZPO_EKGRP     Purchasing group     CHAR     3     0
New Characteristic for South africa :
ZPOSA_BSART     PO Order Type ATSA     CHAR     4     0
ZPOSA_EKGRP     Purchasing Group ATSA     CHAR     3     0
ZPOSA_EKORG     Purchasing Organization ATSA     CHAR     4     0
ZPOSA_GNETW     Total net PO value ATSA     CURR     15     2     ZAR
ZPOSA_WERKS     Plant     CHAR     4     0
Please help me how do configure 2 release strategy for 2 country.
I will be very thankfull to u.
Regards,
Vishal Garg

HI Biju K,
I can use exising Characteristic Like Purchasing Organization & Purchasing Group & Plant etc. But in the case of Net order value : ZPO_GNETW Total net PO value for my indian company Currency is INR and for My SA company currency is ZAR. What will i do in that case.
Please explain..
And aslo clear the concept of creation of new Characteristic as Company Code & design different release strategies based on company code. How i can do that..??
Please explain in details.
I will be highly thankfull to u.
Regards,
Vishal Garg
9810402156

PO Release Strategy Issue

HI,
We have created a PO release strategy workflow.All scenarios are working fine except 1 scenario.
That is,when a PO is created and rejected by a user in user decision step.The workflow will end.If the PO is changed(amount) again,the release strategy is triggered for the same user.But the workflow is not triggering.
If the release strategy is for a different user,its triggering the workflow.
I have used a fork inside which 1 parallel branch contains a wait for significantly changed event & another branch contains the user decision step,po release step & rejection reason scenario.
Can anyone tell the solution for why the workflow is not triggering for only this scenario?
Thanks,
Aparna.

Feddie wrote:>
> Kjetil, I am not clear still, could you explain me a bit clear. I have not seen any tool tip in my release tab.
Don't you see any buttons in the subscreen? The tooltip is not for the tab (title) it is for the button. I am quite sure there is a button there for cancelling the rejection, but without access to a system where this has been set up I can't check it. I just had the same issue before Christmas, where the users said the solution didn't work for the same reason mentioned here - no workflow was sent after changes where made. In fact the solution did work flawlessly as soon as they cancelled the rejection.
See also [documentation at help.sap.com|http://help.sap.com/erp2005_ehp_02/helpdata/en/4c/16443c4a089537e10000000a114084/frameset.htm|ERP release ECC 6.0] for the workflow for rejected purchase orders.

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.

BAPI_REQUISITION_DELETE (Clears Release Strategy)

Similar Messages

Maybe you are looking for