Release strategy tables

Please tell me the tables used for release strategy of PR, PO, service PR, sercice PO, RFQ, contract, and delivery schedules.
Is there a method of finding out the table by some methodology. It is not possible to remember all the tables.
In case of PR item level release is required. Give some guidelines as to how to activate item level guidlines. it is possible both with and without classification.
Regards

HI,
Release strategy tables
Release strategy without classification
T161I as described above.
T161E Release code and Description
T161S Release indicator
T161G Assignment to release indicator
T161F Prerequisites
Release strategy with classification
T16FG, T16FS as described above.
T16FH description of the release group
T16FT description of the release strategy
T16FC Release code
T16FD Description of the release code
T16FV Prerequisites and actions
T16FK Assignment to release indicator
T16FB (purchasing documents), T161S(Purchase requisitions), T16FL(Service Entry sheet) is the release indicator
T161U(requisition), T16FE(purchasing document), T16FM(service entry sheet) are the descriptions of the release indicator
Other tables are
EKBE History per Purchasing Document
EKBZ History per Purchasing Document: Delivery Costs
EKKN Account Assignment in Purchasing Document
EKPA Partner Roles in Purchasing
EKPB "Material Provided" Item in Purchasing Document
EKPV Shipping Data For Stock Transfer of Purchasing Document Item
EKRS ERS Procedure: Goods (Merchandise) Movements to be Invoiced
EKUB Index for Stock Transport Orders for Material
EBAN table has fields for release status and indicator.
To See the tables
goto Transaction SE11, in the field Table click F4, Click on Information system
In the applciation Compnnets enter the following & execute
MM* Materials Management
MM-CBP* Consumption-Based Planning
MM-PUR* Purchasing
MM-SRV* External Services
MM-IM* Inventory Management
MM-IV* Invoice Verification
MM-IS* Information System
MM-EDI* Electronic Data Inter
MM-FT* Foreign trade
OR
goto SE16 Click F4, You have two options Information system & Sap Applications.
Click on SAP Applications & selec the application you wnat to see, for E.g Purchasing you can click on materials managemnt, Purchasing if you drill down you will see the list of tables....
http://help.sap.com/saphelp_47x200/helpdata/en/75/ee1fa755c811d189900000e8322d00/frameset.htm
Check release stratergy with and w/o classification
Thanks & Regards,
Kiran

Similar Messages

Release Strategy - class error

Dear All
I have defined release strategy in my client 100
same i have transport to 101 and checked in the same client
its still working properly
but when i transport the same in client 201, even though all the data is transported strategy is not working
system showing me the following error while i checkiing the strategy in SPRO ( in client 201 - quality client)
while clicking on " Classification "
"Error in classification (Class CLL_PR class type 032)
after double click on above error: Procedure
Please check the specified class or class type in Customizing for the release procedure.
Please sudgest in the matter
Regards
Narendra

Dear Narendra,
We also faced same problem and found that the release strategy was not transported correctly .So my advice is that identify the correct transport and retransport it .Along with this please check all release strategy tables ,there will be some entries missing.
Thanks,
AMIT

Upload Release strategy into T16FW table

Hi Guys
I am trying to uplad data into T16FW table for release strategy but this program is not working , I would be thankful if anyone correct it please.
*& Report Z_UPLOAD                                    *
REPORT ZUPLOAD.
INCLUDES                                            *
*INCLUDE ole2incl.
*&   TYPES                                            *
TYPES: BEGIN OF ty_t16fw,
       frggr TYPE T16fw-FRGGR,
       frgco TYPE T16fw-frgco,
       WERKS TYPE T16fw-werks,
       otype TYPE T16fw-otype,
       objid TYPE T16fw-objid,
       END of ty_t16fw.
TYPES: BEGIN OF ty_titles,
       title(20) TYPE c,
       field(20) TYPE c,
       END OF ty_titles.
*&   INTERNAL TABLES                                  *
DATA: t_t16fw TYPE STANDARD TABLE OF ty_t16fw,
      t_titles TYPE STANDARD TABLE OF ty_titles.
*&   FIELD-SYMBOLS                                    *
FIELD-SYMBOLS: <fs_t16fw> LIKE LINE OF t_t16fw,
               <fs_titles> LIKE LINE OF t_titles,
               <fs> TYPE ANY.
*&   VARIABLES                                        *
DATA: w_tabix TYPE sy-tabix,
      w_titles TYPE sy-tabix,
      w_line TYPE sy-tabix,
      w_field TYPE string,
      filename TYPE string,
      path TYPE string,
      fullpath TYPE string.
DATA: data_titles TYPE REF TO data.
*DATA: e_sheet TYPE ole2_object,
     e_activesheet TYPE ole2_object,
     e_newsheet TYPE ole2_object,
     e_appl TYPE ole2_object,
     e_work TYPE ole2_object,
     e_cell TYPE ole2_object,
     e_color TYPE ole2_object,
     e_bold TYPE ole2_object.
*&   SELECTION-SCREEN                                 *
SELECTION-SCREEN BEGIN OF BLOCK b1.
PARAMETERS: p_file TYPE rlgrap-filename,
p_objid TYPE t16fw-objid. "no-extension no intervals OBLIGATORY,
SELECTION-SCREEN END OF BLOCK b1.
*& START-OF-SELECTION                                *
START-OF-SELECTION.
PERFORM get_titles.
PERFORM get_data.
*& AT SELECTION-SCREEN                                *
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_file.
CALL METHOD cl_gui_frontend_services=>file_save_dialog
    EXPORTING
      window_title      = 'Select archivo'
      default_extension = 'xls'
      file_filter       = '*.xls'
    CHANGING
      filename          = filename
      path              = path
      fullpath          = fullpath.
IF sy-subrc EQ 0.
    p_file = fullpath.
ENDIF.
*&      Form get_titles                              *
FORM get_titles.
CREATE DATA data_titles TYPE ty_titles.
ASSIGN data_titles->* TO <fs_titles>.
<fs_titles>-title = 'Grp'.
<fs_titles>-field = 'FRGGR'.
APPEND <fs_titles> TO t_titles.
<fs_titles>-title = 'Code'.
<fs_titles>-field = 'FRGCO'.
APPEND <fs_titles> TO t_titles.
<fs_titles>-title = 'Plnt'.
<fs_titles>-field = 'WERKS'.
APPEND <fs_titles> TO t_titles.
<fs_titles>-title = 'Ob'.
<fs_titles>-field = 'OTYPE'.
APPEND <fs_titles> TO t_titles.
<fs_titles>-title = 'AGENT ID'.
<fs_titles>-field = 'objid'.
ENDFORM.                    "get_titles
*&      Form get_data                                *
FORM get_data.
SELECT frggr frgco werks otype objid
INTO TABLE t_t16fw
FROM t16fw
WHERE OBJID EQ 'GAIW'.
objid eq p_objid.
ENDFORM.                    " get_data
Regards
Chris

Hi paedro,
I think coresponding events are triggered by SAP automatically when you release/create a PR. What you need to do is just do Event Type Linkage of those events with your Workflow .
For this you can use transaction SWETYPV
Also see
Please check the configuration for Release groups (Path SPRO->Materials Management->Purchasing->Purchase Requisition->Release Procedure->Procedure with Classification->Set up Procedure with Classification->Release Groups). In this, you should check 'OverReqRel'.
Check if you are using workflow template WS20000077 (Workflow for overall release of requisition) with object type 'BUS2105'.
Workflow template WS00000038 (Workflow for requisition release) with object type 'BUS2009', is used for releasing at the item level.
regards,
Hareesha k

Table name for release strategy

Hi
In which place i need to take table name for purchase requisition and purchase order release strategy configurartion,plz suggest
Regards
Sam

HI
While defining characteristics you required table name in po & pr

Purchase requsitions into table EPRTRANS when using release strategy

Hi,
We are working with release strategy.
It is not passible to insert purchase requsitions into the table EPRTRANS when I choose e.g.a material group which
has been declared as a relevant criteria for release strategy. How can this problem be achived ?
Regards
Alexander
Edited by: AlexanderZiegler on Sep 23, 2009 11:25 AM

pls. comment out this perform
     PERFORM bbp_release_check USING l_xeban
                                     l_yeban
                            CHANGING no_update
                                     now_released.
     IF no_update = 'X'.                   " preq not yet released
       CONTINUE.
     ENDIF.

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

Release strategy: Tx CL20N Error: Entry 01 does not exist in table T16FS

Dear MM Gurus,
I was designing new release strategy for PR and PO, so I deleted all the previous entries(SPRO) available in SAP. I created my new entries but in the transaction CL20N I got the above mentioned error: "Entry 01 does not exist in table T16FS-Check your entry" . I checked the table T16FS, where the entries were available. It also showed the previous entries I deleted from SPRO.
Refering the SAP note 365604 (version 29, valid from 08.10.2008), I created the deleted entries again so that I could delete them in the required sequence
1. release strategies
2. release indicators
3. release codes
4. release groups
5. class
After deleting the entries in the above mentioned sequence also I am getting the same error in CL20N.
I ran report RCCLZUOB, it shows the entries does not exist.
Please help.
Edited by: Akshay Kurhe on Mar 2, 2009 6:02 AM

hi
check this setting
Distribution Using Object Classes -->Maintain Class Types & Maintain Classes

USRC1, USRC2 in CEKKO table for Release Strategy.

Hi all,
Can anybody shed some light on how i can make use of USRC1 and USRC2 in CEKKO table for Release Strategy?
I see it in the table but i have no idea on how to use them.
Thanks all.

Hi,
SAP has given user defined fileds in CEKKO communication structure which you can use by using user exits to fill in CEKKO.
These fileds you can use as characteristics for release strategy.
Details of user exit:
M06E0004 Changes to communication structure for release purch. doc.
EXIT_SAPLEBND_002, Changes to Communication Structure for Release of Purchasing Documents
Description: User exit that control the values in CEKKO for the Release Strategy.
Regards,
Shailesh Mackwan

What is the name of the table where Release Strategy changes are maintained

Dear Friends,
Every time I make the changes in the Release Strategy Codes the Signature of the Approver changes in the Output. The problem is that it even changes for the Older PO's which are already approved by some other approver. Is there any way this problem can be sorted out? or can any one give the name of the table which records the changes made in the Release Strategy along with time and date? I will be really thankful if you guys can help me out!

Hi Chintan,
I hope you are talking about the release codes, which we attach later on to user Ids and signature means its description. I hope followed correctly.
In standard system, as and when you change the description of release code at back end, it gets reflected on front end. No matter whether its old or new PO. There is no way out to stop this. Every time you display the purchase order, the release codes checks for description at back end and displayes the same. Still, it should not bother you, as the already released PO dosent get affected for any changes you do at back end in the entire release strategy.
Beside the tables mentioned by other friends AUSP is the table where all release related entries gets stored.
I hope it clarifies.
Regards
sachin

Release strategy for purchase requisition does not kick in

Hi Gurus!
I've been struggling with this issue for some weeks now.
I have set up the release strategy configuration for purchase requisitions with classifications.
However, if I create a purchase requisition the release functionality is not taken into account by the system.
See below some more information regarding my configuration:
1. I've created a new characteristic "REL_PR_GROUP". Status: released, Multiple values, Number of Chars 3, 7 values (TR1, TR2, TR3....TR7), Table name: CEBAN, Field name: EKGRP, Procedure for value assignment set to not ready for input.
2. I've created a new class: "REL_PR_ANPC". Class type 032, Status: released, Same classification: do not check, Char: "REL_PR_GROUP"
3. I have one release group "T1", Rel. object 1, OverReqRel is marked, Class: "REL_PR_ANPC"
4. I have 5 release codes. Grp: T1, Code: 01....05
5. I have 2 release indicators:
"R = Released", Rel. for ordering is marked, Changeabil: 4, Value chgs. 100,0
"X = Blocked", Changeabil: 4, Value chgs. 100,0
6. I have 1 release strategy:
"T1 with Grp T1"
- one release group, 01 Manager
- release prerequisites not applicable because of only one release group
- release status, nothing marked = blocked, 01 marked = released
- classification, purchasing group is TR1 or TR2 or TR3 or TR4 or TR5 or TR6 or TR7
I intentionally kept the configuration as simple as possible so I can try to get it working first.
Now if I create a purchase requisition for an item with release group T1, I would expect the release strategy to be activated. However, this is not the case. I don't see the "release status" tab in the PR, and if I try to relase via ME54 the system says the PR is not relevant for release.
Could you please assist in getting this working?

Hi,
Have you checked in CL30/CL30N if your release strategy is derived successfully?
See section 3 of Note 365604. A small section of it:
You can use transaction CL30 search for an object using the data
of the purchase requisition/purchase order. Here, it is important
that the object search determines exactly one strategy. If this
is not the case, this indicates that there are overlapping
strategies in the system or that the release strategies in
Customizing do not correspond with those from transaction CL24.
See the previous point. If the object search returns more than
one result, the system subsequently determines an incorrect
release strategy or no release strategy at all.
If it is derived successfully, next, check the user exit EXIT_SAPLEBND_001 as per Note 371667:
The following assignment statement has to exist within activated SAP
enhancements M06B0002 (include zxm06u13) and M06B0005 (include zxm06u31)
for purchase requisitions:
E_CEBAN = I_CEBAN.
Regards,
Purnima.

Release strategy for PO and Contract

Hi,
I maintain characteritic for PO
Plant
Doc Type
Net Order Value
Purchasing Group
I maintain characteristic for contract
Company code
Target Value
Doc Type
Purchasing group
My class consist of
Plant
Doc Type
Net Order Value
Purchasing Group
Company code
Target value
Q1: Do i need to maintain ALL characteristic value when i define my release strategy for PO or Contract as some characteristic only apply to PO only or contract only?
Q2: What option do i have if i need to maintain all characteristic value ? leave it blank ? empty
Currently my PO release is working fine but when i try to maintain the contract release inside the class . my PO release is not triggering . I maintained diffrent release group for both PO and Contract .
Thank for your advice

First of all
For purchasing like PO,pr,contract you can able to get in ekko table.No need to maintain separate release unless if it your business requirement.Take Document type as one of the characteristics it will distinguish whether it is PO or contract.
You have to maintain all the characteristic value then only it will trigered release.
Check the release indicator as well.
Hope it will help.

Contract & PO Release Strategy

Hi All,
We are in the process of designing the release strategy for contract and PO. I would like to know whether we can have the different release conditions for contract and different release conditions for PO. For example.
The release conditions for Contract required are
1)Porg
2)Pgroup
3) Value
Also, for quantity contract how can we make the release strategy trigger based on value.
The release conditions for PO required are
1)Porg
2)Pgroup
3)Material Group
4)Value
The release strategy is not getting determined if we create po with two line items which belongs to two different material group. Is there any way out to solve this issue?
Request your help.
Regards,
Kannan

Hi Kannan
Yes your requirement is possible...
While creating Charectristics in CT04 for External Purchase Documents...Create one more Value for your Document Category...ie) Table as :CEKKO and Field as BSTYP and choose the Purchase Doc. Category values K and F.
Then create Charecteris for CEKKO - EKORG, CEKKO - EKGRP and CEKKO - GNETW, CEKKO- MATKL... and assign these all 4 Chareteristices in your release class.
And Configure your release statergy according to your requirement...
Reward if useful
Regards
S.Baskaran

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 Sampath

Hi 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

Purchase order release strategy report

Dear Gurus,
We are using purchase order release strategy with classification.
We have 3-4 level of release. We want to develop a report where we will come to know at which level purchase order is pending for release .
How to get it ?
Please provide ur help for the same
Rgds,
Saurabh

Hi,
Basically in EKKO table there is a field name FRGZU -
Release status based on that we can write a logic take the report.
for example A1,B2,C3 ARE THREE release codes in that if A1 released means with check thable whether A1 released once it is release it will go to next release code it iwll check the status again inthe loop....
Just tell him the logic to ABAP person they will develop
Rehgards
Murugan J

Issue: Purchase order release strategy with storage loaction.

Hi Friends,
I have created release strategy for purchase order considering following characteristics.
1. Plant
2. Purchase organization
3. Purchase group
4. Document type
Hence the release strategy is working fine.
Now the requirement is changed, PO approves should be picked depending on the storage location wise. So i tried to create characteristic for storage location with table name CEKKO and with field LGORT. However system not allowing to create, telling that field LGORT not found in table CEKKO.
Can any one tell me how to maintain this LGORT filed in structure CEKKO.
Thanks in advance
Shashidhar

HI Shashi ,
Thanks for your quick response,
I have Appended a structure to Standard Structure CEKKO with Field LGOBE.
Also we written the code :move: i_cekko = e_cekko, in user User-Exit M06E0004 function exit
FUNCTION EXIT_SAPLEBND_002.
However, the release strategy is not triggering when PO is saved,
also the user-exit is not getting triggered , even though i have included the statement ' Break-Point'
in it.
Kindly reply.
Thanks ,
Shashidhar

Release strategy tables

Similar Messages

Maybe you are looking for