Release Status Indicator table in SPRO

Hi,
I am a abaper and one of collegue is facing a customizing problem in which he wants to know whether the release indicator has been changed or not by anyone?
Please provide some knowledge about it i.e. how it is to be checked or which table is to be used for it?
Edited by: nav009 on Feb 9, 2010 12:14 PM

Hi
Th list below show the tables used for Rel stg., pls use the appropriate one
Release strategy tables
Ans: T16FG - Release Groups
T16FC - Release Codes
T16FB - Release Indicator: Purchasing documents
T161S - Release Indicator, Purchase Requisition
T16FE - Description of Release Indicators: Purchasing Documents
T16FS - Release Strategies
T16FV - Release Prerequisites
T16FK - Release Statuses

Similar Messages

How to maintain SAP Release status in table COTPL

Hi All,
We have upgraded our system from ECC EHP4 TO ECC EHP 5. Now our SAP Release is 702 but in table COTPL
still the SAP Release status is 701 becuase of which there is error in some of our sap jobs.
Request you all to help us. How we can maintained SAP Release in table COTPL?
Thanks

Hi,
You can try using priority field in the rule. Please check this.
Priority for Responsibilities
If you are using responsibilities for role resolution in Workflow, you can provide individual responsibilities with priorities.
Example: There are various responsibilities for a standard role for processing orders, grouped, for example according to order value (one responsibility for orders up to a certain value, another for orders with a greater order value).
Assuming that orders for a particular customer are always to be processed with the same responsibility (and therefore by the same agent), you can access it via another responsibility with a higher priority that contains the customer name as the only criterion. The responsibility (-ies) with lower priority, and therefore the order value, is then no longer taken into account during agent determination.
Use only numeric values here, and note that, logically, the responsibility with the highest numberic value in this field has the highest priority.
Procedure
1. Sequence Priority of Objects
In Create mode, assign a priority to the objects you wish to rank.
To do so, assign an alphanumeric value (1, 2, 3... or A, B, C...) to each object.
In Change mode, overwrite the value in the field.
2. Priority When Defining Evaluation Paths
In the Priority field, enter the priority or priorities for objects that should be considered in evaluation paths. Enter "*" if you want to have no restriction.
3. Priority for Responsibilities
Maintain the priority directly in the detail screen for the responsibility or in the overview screen for the responsibilities for the rule. Note that you must use numeric values here. On the overview screen, the system sorts the responsibilities in descending order of priority.
Hope this helps.
Feel free to revert back.
-=-Ragu

PO Printing Status Indicator - Table

Hi Guys,
We are developing one report for PO Printing Status.
In which table PO Printing status updated after user Prints PO.
Regards,
Jackie

Hi Jackie
The PO Print status will not be updated in table. Its from a Structure TSP01_SP0R, Print status field name RQSTATUS_V
Regards
Shantha Kumar

Condition Tables with Release status

When we create condition tables, we have the option of creating them with release status or without release status. What is the difference? What is release status?
Thanks,
Venkat

hi,
The release status for condition records in a sales deal enables you to limit the use of records that have already been created.
Release status has the following characteristics:
no entry: released
A: blocked
B: released for price simulation
C: released for price simulation and planning
The amount and significance of individual characteristics is defined using domain fixed values and can not be maintained.
Maintenance of the release status is carried out in the sales deal itself (in the proposed values block), is transferred over to the condition records concerned and can then not be changed for these records.
When setting up a new sales deal (with copy), a proposed value is suggested for the release status, which can be set up in Customizing for the agreement type.
A record blocked for an application is treated in the access, as though it has been identified with a deletion indicator. It can however be recognized and displayed as such via the log functionality in Pricing.
The characteristic Pricing Simulation is only used in the report SDNETPRO, which gives a net price list.
If when maintaining individual condition records a sales deal is assigned to the condition record using the transaction VK12, the release status from the sales deal is used for this record. When changing the release status using this sales deal or changes to the sales deal, the user will be notified of any changes to the status.
The release status of conditions in an agreement can only be changed, if
the condition record has release status in the key
the agreement has the release status released
Otherwise the condition record always has the release status of the agreement.
The processing status is always directly assigned to a release status. If conditions are assigned to an agreement, the agreement passes the release status on to all related conditions. The related processing status is then set accordingly.
If you have several processing statuses assigned to a release status, the condition record receives the first (alphabetical) suitable entry as a processing status.
The processing status, which the conditions have received indirectly from an agreement via the release status, can only be changed in the case of released agreements.
source : Library.
regards

Table for PO release status

hi,
im developing PO Smartform.in that i have to display PO release status ie; whether it is released or not released(ME22N----->click on HEADER--
>click on RELEASE STRATEGY).from which tables i can fetch this data .please help.

Hi
Take the fields from EKKO that are related to PO release startegy
FRGGR
FRGSX
FRGKE
FRGZU
and check the tables
T16FG
T16FS
T16FB
for the release codes
Reward points for useful Answers
Regards
Anji

ME21N - in which table saved the release status for specific release code ?

and for the specific po number.

Hi
You will find all Release codes in T16FS
Release procedures are used in condition tables to control whether the condition types for these condition tables have to be read during pricing condition determination or not.
If the condition table status is released then only the condition types will be read during pricing determination. If the status is not released, then they can be used for information purposes or for simulation of pricing.
The release status is controlled by processing status too, which can be seen in condition record creation screen.
So in crux, the processing status with Release status help in simulation of pricing, blockign the condition records from being read during pricing etc.
For more information an F1 help on the following path will give you some more information.
SPROSD-BF-PRICING-DEFINE PROCESSING STATUS----Here read the documentation meant for this link. You will get some more clarity on this.
Reward points
Regards

Processing and Released Status when we create a new Condition table

Hi all
I created a new condition table in M/03, and assigned one field to it, Generated and saved. Then added the condition table in the access sequence. There appeared two more lines below the field that i have assigned. One is Processing status and the other is released status, both are having green lights. what are these and what is its impact.
inputs will be highly appreciated
thanks

I myself could find the answer

Activate Release Status in condition table

HI,
Some has created a pricing condition table and it is being used since 5 years.
Now client had a requirement where he wants release mechanism for any new condition records created.
For this SAP provided a standard functionality of release status.
In our case release status button is not checked while creation of condition table.
Now how to reactivate the release button in the condition table.
Regards,

Hi Uday
We can't activate release function in old tables just like that. You have to create new table with same fields but with release status activate. For copying old condition records in this new table you can use
SD_MOVE_A004_TO_A304 report. As you can see with its name this report is for tables 004 and 304. If you want to copy records from 004 to 304 you can use this report. In your case you must have some other tables but if you show this report to your ABAPer he would be able to generate a new report using your tables.
You can take a look on following document provided by SAP and see the conversion section at the end of this document.
http://help.sap.com/saphelp_46c/helpdata/en/9b/3b1a2bc925d311b60f0060b03c2bff/content.htm
Thank$

What is the purpose of the release status in creating condition table

hi gurus,
can you please tell me the purpose of the release status and validity date in creating condition table for pricing?
thanks,
Paul

Dear John
The release status controls in which scenarios the condition records are found.
If the status is set at 'B', for example, then the corresponding records are taken into account during a pricing simulation, but are not used in current documents.
The release status can only be maintained directly for agreements (sales deals). For condition records, this is done via the processing status.
thanks
G. Lakshmipathi

Hai release status

what is this release status in the condition table creation what does it indicate
In pricing procedure det we found condition type field what is the purpose of this
thanks

Hi Kishore,
The release status for condition records in a sales deal enables you to limit the use of records that have already been created.
Release status has the following characteristics:
no entry: released
A: blocked
B: released for price simulation
C: released for price simulation and planning
The amount and significance of individual characteristics is defined using domain fixed values and can not be maintained.
Maintenance of the release status is carried out in the sales deal itself (in the proposed values block), is transferred over to the condition records concerned and can then not be changed for these records.
When setting up a new sales deal (with copy), a proposed value is suggested for the release status, which can be set up in Customizing for the agreement type.
A record blocked for an application is treated in the access, as though it has been identified with a deletion indicator. It can however be recognized and displayed as such via the log functionality in Pricing.
The characteristic Pricing Simulation is only used in the report SDNETPRO, which gives a net price list.
If when maintaining individual condition records a sales deal is assigned to the condition record using the transaction VK12, the release status from the sales deal is used for this record. When changing the release status using this sales deal or changes to the sales deal, the user will be notified of any changes to the status.
The release status of conditions in an agreement can only be changed, if
the condition record has release status in the key
the agreement has the release status released
Otherwise the condition record always has the release status of the agreement.
The processing status is always directly assigned to a release status. If conditions are assigned to an agreement, the agreement passes the release status on to all related conditions. The related processing status is then set accordingly.
If you have several processing statuses assigned to a release status, the condition record receives the first (alphabetical) suitable entry as a processing status.
The processing status, which the conditions have received indirectly from an agreement via the release status, can only be changed in the case of released agreements.
In pricing, only those conditions are used, those have the release status 'released'.
Reward points if it helpful
Cheers,
Govind.

Processing status & release status

Hi,
There is a configuration which says: DEFINE processing status.
Can somebody expalin in details the use of it .
In short i would like to know about the processing status & release status.
thanks,
prithika

Prithika,
Processing Status and Release status work closely both are interlinked. you can define processing status and assign it to condition record. Release status controls in which scenarios the condition record are found.
The release status can only be maintained directly for agreements. For condition records, this is done via the processing status.
Configuration for Processing status can carried out using
IMG --> SD --> Basic Functions --> Pricing --> Define Processing status
Here you can create processing status and Release status will be assigned according to the scenarios if it were "B", "Release for pricing simulation" will be assigned to the processing status.
Using Tcode SM30, choose Table/View: "/BEV3/CHA_KOND".
Activate Enter Conditions Indicator
Click maintain and use the options provided.
Regards
Sathya

Report for Service Eetry Sheet Release Status

I have created a Service Entry Sheet which has 4 Levels of approval. How will I come to know which level is completed and which one is pending?
Is there any standard report available?

Hi,
then create z report
use
     ESSR-FRGGR - release group
     ESSR-FRGSX - release strategy
     ESSR-FRGZU - release status
     ESSR-FRGKL - release indicator
     ESSR-FRGRL - release not yet completely effected
Regards
Kailas Ugale

Network Connectivity Status Indicator for IPv6 works wrong in Windows 7 and Windows 8

Hi Folks,
I am working on testing Network Connectivity Status Indicator for IPv6 in Windows 7 and 8.
Waht is "Network Connectivity Status Indicator(NCSI)" you can refer to https://technet.microsoft.com/en-us/library/ee126135%28v=ws.10%29.aspx?f=255&MSPPError=-2147217396
I found that even if Network Connectivity Status Indicator detect IPv6 connection to http://ipv6.msftncsi.com/ncsi.txt failed.
Windows IE still use IPv6 to connect to website first, rather than stop using IPv6 and to use IPv4.
It will cause IPv6 fallback to IPv4 problem, that's 21 secs and 7 secs delay for fallback in Windows 7 and 8.
Does anyone suffer the same problem?
Or someone know how this works?
Thanks!

Hi Roger_Wang0214,
"Windows IE still use IPv6 to connect to website first, rather than stop using IPv6 and to use IPv4."
By default Windows prefers IPv6 over IPv4,we can manually configure the IPv4 prefer over IPv6 if it has result in any troubles.
Here is a link for reference :
Resolving Internet connectivity issues after World IPv6 Launch (June 6, 2012)
https://support.microsoft.com/en-us/kb/2533454
"The "Prefer IPv4 over IPv6" Fix it solution will configure your computer to prefer IPv4, instead of IPv6. By default, Windows prefers IPv6 over IPv4. If you are having problems using IPv6 to connect to some websites, this may resolve the
problem."
For a Windows 7 machine ,we can try the following fixit tool to configure IPv4 prefer over IPv6 .For a Windows 8.1 machine ,we can configure it referring to the manual part .
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters\DisabledComponents
If the DisabledComponents entry is unavailable, we can create it (DWORD (32-bit) Value).Then set a value with "0x20"to prefer IPv4 over IPv6 by changing entries in the prefix policy table.
Here is a link for reference :
How to disable IPv6 or its components in Windows
https://support.microsoft.com/en-us/kb/929852
Best regards
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Demand on Demand Board even if ticket is not saved in release status.

All
I am currently on CRM 5.0 SP 8 and I am using the RPA Tool. I believe this is a bug but would like validation.
When I create a Service Ticket and change the status code from in process to release and than to customer action but i do not save it, it still moves the demand to the board.
I believe it should only show up in the demand list if you have changed the status to released and than saved it.
Can someone confirm this theory so I can create a OSS Message?
Regards
Julie Hayashi

Hi Julie
did you receive and reply on this from SAP? I'm facing a similar issue (actually in CRM 2007 SP5): when I save an order as released, and then cancel it, the demand does not get canceled, but is still available in the demand search.
There is a demand cancellation status in table WFDSD_DEMAND, however this status never gets set to "03" = cancelled.
Thanks in advance!
Christian
Edited by: Christian Böhm on Dec 21, 2009 1:43 PM

PO release status is not updated.

Dear Expert,
Configuration of PO Release Strategy:
Release Indicator B & R.
Indicator B : Changble field is 4
Indicator R : Changble field is 1 ( Cann't be changed)
Note : For PR , Business case is same , Upon final release users are not allowed to change the PR & PO.
Transaction:
1. PR Creation & Release --- Working fine.
1. PO w.r.t PR Creation & Release --- PO release ( ME29N)status is getting changed from B to R, But release status of PO getting reset from R to B when I am trying to View/Change/cancel Release ME23N/ME22N/ME29N.
When I am using the above said T-Code, there I am seeing that PO is un-release, Though I ahve released the PO.
I am not able to understand why system is behaviing such way.
Help me out to resolve this issue.
Rgds,
Manoj

Hi,
Keep Changeability Indicator BLANK in Indicator B & for Indicator R , you can keep Changeability Indicator 1 ( Cann't be changed) as your business required in configuration of PO Release Strategy:
For Example:
Release Indicator B & R.
Release ID..........Released.........Changeability Indicator.........Description
Indicator B ........{ }..........................{ }......................................Blocked
Indicator R ........................................................................Released
Now try creating PO & then release, sure it will work.
Regards,
Biju K

Release Status Indicator table in SPRO

Similar Messages

Maybe you are looking for