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.

Similar Messages

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

Release status of a function module

Hello,
how can I find out (where) the release status of a function module (if a function module has a status "released for customer")?
regards
zeno

- start SE37
- click on the "attribute" tab
- check on the right section in the bottom area
Markus

Include the Content Released status flag in default WC data control

Hi,
We have integrated custom webcenter portal application with UCM for documents integration. The integration was done using default data control.When we change the document which is getting displayed in the portal from UCM and check it into the system, wokflow gets triggered properly and the content status shows review status. But when we access the document in the portal, at that point of time new document is visible even though the content is still not released from the system.
Can anyone of you let me know how to include the released status of the content in the default data control so that we can avoid this situation
Regards,
Boopathy

First of all, I think this is more a question to WebCenter Portal, because it is how WebCenter Portal components are written.
Another thing is, that this is probably 'works as designed' and there might be good reasons for that. Since PS3, WebCenter (Portal) exposes some of UCM's functionality, among them ability to approve items in a workflow. This is the reason why it makes a good sense that items are available. Of course, they should be available only to approvers; also unapproved items should not appear if an item is displayed via Content Presenter (compare to a document published on a website via WCM). If you found such a behaviour, please, report it to MetaLink as it might be a bug.

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

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

How to get informed when PO / Contract changed to ordered / released status

Hi,
I am working on a program which sends SRM PO and Contract data to a non-SAP system, one of the requirements is to send SRM data immediately after PO / Contract's status changed to Ordered / Released ( workflow is used here ).
I tried to used BBP_DOC_CHANGE_BADI, but noticed throuhg debugger that the last time this BADI get called, I still didn't see Ordered / Released status in the Status table.
Is any way to know status change for PO / Contract ?
Thanks a lot,
Wayne Liu

Hello Wayne,
Solution 1:
You can use the SRM Alert Mangament to know when a contract was released, specifically the following events RELEASED_AGAIN
RELEASED_NEWLY.
Check IMG Cross-Application Basic Settings-> Event and Event Schema for Alert Management
For PO I could not find a similar event, but there is a APPROVAL_PROCESS_DOC_APPROVED event which can be used if the PO was approved after ordering.
In any case you can create your own events and event handlers using the SRM Alert Management BAdi BBP_ALERTING.
Solution 2: Only for Contracts
You can use the existing Distribution mechanism to distribute contracts to Non-SAP systems.
Distribution of contracts is triggered whenever significant changes are done to the Contract (like Release, Lock, Unlock).
Implement function module NOR3_CTR_TRANSFER for this purpose.
Edited by: Sushil Kumar on Mar 22, 2010 9:41 AM

ME_PROCESS_PO_CUST method PROCESS_HEADER to reset release status of doc

Hi Everyone,
I have read lots of threads regarding the implementation of BAdI ME_PROCESS_PO_CUST. However, I could not find one which fits our requirement which is the resetting/ restart of the release status of a PO whenever a released/approved PO has been changed not only in the quantity field but also in the other details of the document.
I believe that the method to be used in this sense is the PROCESS_HEADER. Would you know any logic which could help me restart an already released PO document whenever any changes have been made to the document?
Kindly send your recommendations.
Thanks and regards,
Reymar

Hi,
I used this code:
CALL METHOD im_header->get_data
RECEIVING
re_data = lmpoheader.
IF lmpoheader-frgke = 1 AND
lmpoheader-frgzu IS NOT INITIAL.
lmpoheader-frgke = 2.
lmpoheader-frgzu = ''.
CALL METHOD im_header->set_data
EXPORTING
im_data = lmpoheader.
ENDIF.
After saving the PO document, the fields FRGKE and FRGZU were not changed. When I debugged the code, the values of the fields were changed. I just don't know if the last CALL METHOD has been properly executed so that IM_DATA may contain the changed values.
Thank you and regards,
RE
Edited by: Reymar Ellazo on Apr 21, 2009 6:19 PM

Cash Management : PO release status in Liquidty Forecast Report

Hi,
Can anybody know how to setting :
PO only links to Liquidity Report in TR-CM (FF7B) only if PO has been release completely ?
Thanks

Hi,
You can the desired report through t/code: ME2L / ME2M , after executing the report go the change layout & select the Release code / release status field. Release staus field will be appear like , if first release is done , the status will come as X or if second release done, the it will come XX. And from release indicator field , you can get the code release code .
Regards,
Raghunath

Release Status of PR

Dear All,
How to check a PR is fully released ?
Thanks in advance.

Go to ME53, Select the Line item, and click the Flag Icon,
You will have Pop up of Release strategy.
Check release code of "release to date" against the release codes "Final release" they should be same,
Check the Release ID : RFQ/Purchase order is allowed or it comes as Block for Processing.
You can also check the PR Release status through Report MB5A, with required criteria of the check boxes.
Regards
Vikrant

Settlement of WBS with Partially Released status

Hi colleagues,
We are encountering problems during our settlement to AUC. Although the settlement rule is maintained, the system does not allow us to post the settlement to a WBS with "PREL" (partially released) status. Is this really the standard of the system? When can we release the WBS?
Thank you.

Ask your FICO consultants to create a separate Asset class for AUCs.
They can maintain such class in OAOA, where ask them to maintain status of Auc as Investment Measure.
Now you can use this class in OITA - Investment Profile.
And assign this Investment Profile to Project Profile in OPSA.
Assign this Profile to capital project.
Now all your assets which are AUC stage will come to this asset class.
You can create completed asset in the other class by full settlement.
Rewards for helpful answer.
Thanks,
RIYA

Grt release status on backend to SC on SRM

Dear all,
We would like to see the process Release Status of Purchase requisition or Purchase order on backend system R/3 , in the Shopping Cart on SRM side.
Does SRM 5 Support this issue?
Does anybody has implement this case?
Best Regards,
Moshe

Hi
I have seen your requirement. It's some what similar to this problem asked in the thread. Anyways, i paste your requirement here.
once SC is created in SRM system,pr or po will be created in R/3 system.
now client requirment is
1)PR release status has to be updated,
2)untill PR is approved in R/3 SC has to be allowed to change !
3)RFQ and quotation have to be update the status.
4)backend Po release status have to updated
finally price details should not be dispalyed in follow on documents overview as well as detail screen.
Regards,
Mani
From SRM system, the BAPI - BAPI_REQ_CREATE is called in R/3 system which creates the Back-end Purchase Requisition in the R/3 system.
From SRM BAPI - BAPI_PO_CREATE / BAPI_PO_CREATE1 is called in R/3 system which creates the Back-end purchase order in the R/3 system.
Similarly, In our case, we need to read the R/3 data into SRM using any of the BAPIs which will bring up the Status and then update the same to the Shopping cart custom field.
I am still looking for alternative approaches.
Wl update you soon on this.
Hope this will help.
Please reward suitable points, incase it suits your requirement.
Regards
- Atul

PO Release status with date

Hi Guys,
I have a requirement where in I need to list out the POs with the Release status based on
date range. Any pointers on this is appreciated.
Thanks.
Rgds,
Senthil GR

hi
go to me2n then select the date range and then press shift+F4 (dynamic selection )here in header u can select the release indicator and dates
regards
kunal
award if helpful

PO Release Status

How can we check the release status of Purchase Orders - pending release at different levels
Regards,
Param

Dear Param,
Transaction ME2N:
Click the dynamic selection button
Expand "Purchasing document Header" folder
=> Here you can find release group, release strategy,
release status, subject to release field based on your
requirement.
Hope this will help,
ian Wong

Digital Signature only Release Status with 3(Approver) Signer

Hello SDN Folks
I have done all the basic settings for Digital Signature which is sawn in following link
http://wiki.sdn.sap.com/wiki/display/PLM/Digitalsignaturein+DMS
it is work fine with 1 RE (Release) status and 1 Signer
We have in process to implement Digital Signature with only two Status
our scenario is
Document Creator Create Document With Status CR
Document Approver Approve Document With Status RE
now we have scenario that For 1 Document we have 3 Approver and 3 approver must digitally sign on DIR
our status is
only CR(create)---->RE(release)
so how i can attached 3 digital signer with only 1 RE(Release) Status
is it possible to go with 3 digital signer with only 1 RE (Release) Status ????
Regards
Tushar Dave

Hi Tushar,
Your requirement of utilizing 3 different approvers for a single 'Release' status in a document type/s can be addressed via the approach proposed below:
1.Define 3 individual authorization groups
2.Define 3 individual signatures
3.Define a common signature strategy
4.Assign the above 3 individual signatures to the common signature strategy
5.Define the signature sequence(the order in which the 3 approvers must approve)
6.Define users and restrictions(signature assigned to relevant approvers/users)
7.For the document type in question for the 'Release' status,assign the above signature strategy and test.
For more detailed information on using digital signature effectively,refer the below link
http://help.sap.com/saphelp_470/helpdata/en/9f/857f3a1c7b11d294d200a0c92f024a/frameset.htm
Regards,
Pradeepkumar Haragoldavar

Hai release status

Similar Messages

Maybe you are looking for