RE: Pr release , it should not be editalble like qty, material.

Dear Sap experts,
In Pr , After the release Pr , it should not be editable like material & Qty.
Thanks
Mohit

Hi Mohit,
as you have Written
please advise me that where is the option of R in release indicators... there is only 1,2,3,4,b & X
Do following settings during designing of release procedure and then your design release strategies,which result once PR released,it can not be changed.
ReleaseIndicator ....Released....Changeability ....Value change % ....Description
B .........................................................................................................PR Blocked
R.................................X.....................1..................................................PR Release
in front of B (Blocked) you have not given Changeability option......................PLease please give in that also.
Rgeards,
yawar Khan

Similar Messages

Without standard release confirmation should not allow in process order

Our clients need is that without standard release confirmation should not allow in process order.
We are using CORK,cor6 and MB31 My need is to apply user exit in all cases.
I got input from sdn User exit:-PPCO0006 Function module Exit_SAPLCOZF_003
INCLUDE ZXCO1U06
I need to activate this only during confirmation.ie confirmation to be avoided if cost is not released.
Regards,
Pert

Hi,
You are right. For preventing confirmation in case std cost estimate release is not available you need to do enhancement. You can check for following exit along with exit which you mentioned in your post :
Enhancement CONFPI05
EXIT_SAPLCORF_405 - Process Ord. Conf.: Cust.-Specific Enhancements when Saving
INCLUDE ZXCOFU10
Check either of the enhancements which may fulfill your business requirement.
Regards,
Tejas

New release strategy should not trgger for PO released with old Rel Strategy

Hi All,
Please suggest. Po has been fully released with Release Strtgy V1 XX. Now I m replacing release strategy XX with ZZ. If I change any po which has old rel str XX , system will reset new release strategy as in config changeability indicator 4 maintained.
But requirement is if there is any change or value decreasing in fully released Pos with old strategy it should not retrigger new release strategy. If value Increases then New strategy should retrigger.
Please help me on this.
regards,
Rohit

HI Rohit
A reset of the release strategy only takes place if
       - the changeability of the release indicator is set to '4' in
          case of a purchase requisition and '4' or '6' in case of
          another purchasing document (purchase order, request for
          quotation, contract, scheduling agreement),
       - the document is still subject to the previous release
          strategy,
       - the new TOTAL NET ORDER VALUE is higher than the old one.
The most important thing to consider in to avoid changes to release strategy customizing once the release strategy is used.
The commom steps are:
1- make sure all of the old POs should have been released.
2- don't delete/change the original release strategy. create a new release strategy with copy function, then the old release strategy will not be replaced.
3- if you delete the original release strategy and add a new release strategy which the characteristics in classification is same as old release strategy then the PO (have been approved) will be replaced with the new release strategy.
Kind regards,
Lorraine

PO RELEASED IT SHOULD NOT BE ALLOWED TO AMMEND

Sir,
once po is released it is should not be allowed to edit.
how can i configure this
regards
amey

Hi Amey,
Once PO is released it cant be Changed it can be done by doing the following setting in SPRO.
SPRO>Material Management>Purcahsing->Purchase order->Release procedure for purchase order--->Define release Procedure for the PO
In this Release Stategy config there is option called Release indicator
where in we have to define a release ID and this release ID ( Eg A ) has to be given 1 cannot changeable in the feild in chagble--for the allowing no changes in PO after release and then we have to go to release Strategy option we can select the release strategy we want the change and in the Strategy
click on the release status and in this status we can give the ID defined earlier ( at which level what effect should come)
hope so it helps
regards
Anjanna.

Delivery Qty. should not Exceed the PO Qty.

Hi All
My requirement is that just like Sales Order, incase of STO the delivery Quantity (delivery creayed through VL04) should not exceed the Balance Quantity PO quantity (where PO Quantity less Already delivered Qty = Balance Qty). Is there any standard customisation or Exit is available for this??
Regards
AA

Dear AA
I have searched in MM forum and found this thread which is relevant to your requirement
Forum post in ERP - Logistics Materials Management (MM): STO - How to control Over delivery ?
STO - How to control Over delivery ?
Hope this helps you
SAP has a logic for not controlling the over delivery in STO in standard (unlike sales order to delivery we have the controls in Zero VLP or 0VLP for this) because STO happens between plants of a same company code or different company codes .The movement of stocks are between plants But in a normal sales the delivery happens to a customer who is actually a third person and hence a user can misuse the delivery quantity
A plant and an external customer cannot be treated as same
Hence in SAP standards over delivery is not controlled in standard settings like item category etc
Regards
Raja

Delivery qty should not exceede Sales order qty

Dera Friends,
System is allowing to create delivery for a higher quantity than in sales order. For eg. The sales order is created for 10 pieces and delivery is created for 20 pieces.
We want to have a check on this. Pls guide where we can configure this. Our requiremnt is that Delivery qty should not exceede the sales order qty.
points assured
Krishna>C

hi,
Go to VTLA, select your order type and delivery type and select item category and see whether you have maintained the following:-
Order requirements:::::101
Item Data:::::::::::::::::::101
Updata Document flow:::X
Pos./neg.quantity::::::::::+

Release PR Should not get deleted in md51,planning mode 3

Hi all,
We are facing a problem in MRP run taken through transaction code MD51. This Problem (as explained below) will occur when MRP control parameter for Planning Mode will be set to u20183u2019 (Delete and recreate planning data).
During normal course, if MRP control parameter for Planning mode is set to u20183u2019, system deletes all open PR & Planned orders & creates new PR & new planned orders.
But in our business scenario, where we have release strategy for MRP generated PR, even these released PR get deleted. This results in re-analysis & releasing of MRP generated PR which itself is a tedious & time consuming task.
We are looking for a solution where PR will not get deleted during MRP.
Thanks
Sukumar
Edited by: skumar kalame on Nov 10, 2008 1:59 PM

Hi,
The planing time fence is maintained in MRP-1 view of the material in workdays. You can also have this defined in the MRP group. But the value in material master takes precedence over MRP group.
Use - It is a kind of safety fence which is used to protect any automatic changes to take place for firm order proposals during MRP run.
Depends on - Firming indicator needs to be maintained for the MRP type. This can be set in customizing for the MRP Type. This basically specifies how you want to firm the order proposals. Please note there are 5 types of firming
The SAP help for firming type reads as below:
firming type 0
The system does not firm procurement proposals automatically.
firming type 1
Procurement proposals that move into the planning time fence are firmed automatically, as soon as their date lies at least one day before the end date of the planning time fence. The date of new procurement proposals that are created in the planning time fence is displaced to the end of the planning time fence. These new procurement proposals are not firmed.
firming type 2
Procurement proposals that move into the planning time fence are firmed automatically, as soon as their date lies at least one day before the end date of the planning time fence. The system does not create any new procurement proposals within the planning time fence; that means, the system does not balance the shortage situation in the planning time fence.
firming type 3
Procurement proposals that move into the planning time fence are not firmed automatically by the system. All procurement proposals that are necessary for requirements coverage are displaced to the end of the planning time fence.
firming type 4
Procurement proposals that move into the planning time fence are not firmed automatically by the system. The system does not create any new procurement proposals within the planning time fence; that means, the system does not balance the shortage situation in the planning time fence.
If helpful award points
Regards,
Vivek

Cost Run should not be getting executed on Material with Price Control V

Raw & Packing materials are with price control V in MM as company wants to keep them on moving average cost. Somehow finance users executed cost run on one such material and cost run was executed and the difference was posted in price difference. As far as I know, system shouldn't be allowing cost run on materials other than those having S as price control.
Question is: How to ensure system sends error if cost run is attempted to be executed on materials with Price Control V?

Hi
If you are executing cost run using CK40N, it releases the cost for all the materials i.e. both for the header and the components
the components may be usually valuated at V. So, the std price update for these will be only for information purposes and it wont revaluate your inventory for sure... This cant post to price difference.... Price diff upon std cost release will apply only to those materials which have price control S
However, if you dont want to release the cost for V items, you can specify them in the exclusion list... In Ck40N selection parameters you specify your plant/material, etc... While specifying the materials to be costed in the multiple selection screen, , you can also specify the ones not to be. Then std cost wont be released in those cases
Regards
Ajay M

PO qty Should not more than PR qty

we Have configured For controlling Multiple Pos for same PR, error message 06-076.
It is working fine for Materials PR/PO. But for service PO, Item Qty is AU always and
item detail screen having Service tab having Multiple services.In this case even though
less qty is converted to Po,for remaining qty conversion to Po, system giving this error message. can any body give idea?
thanks
ramitreddy

When it comes to service you need to make message number 438 and application area SE error in the below config
spro>MM>external service management-->define attributes of system messages
Regards
Antony

Delivery Qty should not be greater then po qty

HI
SAP Guru's
Delivery quantity should not greater then po qty.
my problem is they are rising mulitiple devliveries for one PO
Code written in MV50AFZ1 is not working because it is checking only if Delivery Qty more then PO qty, I tries to sum qty from LIPS table using VBGLN Cust po no but VBGLN is non key field in LIPS table. It is giving perfomance problem.
Please suggest if any other tables to SUM the delivery quantity.
regards
ravi N
9866595994

Hello Experts..
Need ur expertise advice on above issue...

Schedule lines should not be maintained with out release

schedule lines should not be maintained with out release of schedule agreement......but system accepting to maintain the schedule lines.Please say how.
regards,
Sridhar kumar.a

Hello,
I have the same problem as you. Someone know something about it?
kanyadhara, did yo solve this problem?
Thanks a lot

Purchase Requisition Attachement Should not be Modified when it is released

Hi Experts,
I've a requirement that, In ME52N, if the Purchase Requisition is Released then, the user should not add or delete or change the Attachments. Pl help me in this how to do.
Regards
Rajiv.

Thanks giri.
For the following reasons, the billing documents are not released to accounting.
1. If the user wrongly chosen the billing type for the delivery.
2. After creating condition type, it has to be assigned in COPA. If we forgot to do it, billing doc will not released.
Our requirement is that if the billing document is not able create accounting document, the billing document itself should not be generated.
Hope this will be suffice to understand my issue and suggest a suitable solution.
Points will be rewarded.
Regards,
Kumar.

This method should not be called anymore. The client was already released i

Hi,
while configuring Business Packager for Projects 50.3 fo, we made few changes in R/3 side as per the documentation. after that we are getting following error in portal
"This method should not be called anymore. The client was already released into the pool or the pool entry was deleted"
all the chages were reverted in R/3 system still we are getting the same error.
Can any one help on this issue....
Thanks in advance and for early responce higher marks would be awarded!!!..
Regards
Ravi Sankar Karri

Hi,
Well there were errors in how stop works:
"Stopping a thread with Thread.stop causes it to
unlock all of the monitors that it has locked (as a
natural consequence of the unchecked ThreadDeath
exception propagating up the stack). If any of the
objects previously protected by these monitors were in
an inconsistent state, the damaged objects become
visible to other threads, potentially resulting in
arbitrary behavior. "
I do understand that you want to have something like
killTheTreadIDontCareAboutConcequences-method, but
it's better to let all your methods that you want to
be able to terminate take a timeout argument, and deal
with the termination in the method. (Close the
sockets/streams etc that you are blocking on).
/KajThe point is, it is not always possible to make those blocking methods stop, via some magic "timeout" thingamabob. The bottom line is still that the blocking methods were written incorrectly to begin with (to possibly block indefinitely), so one cannot come up with an across-the-board solution, other than getting the root cause fixed in the first place. However, one is not always in control of fixing the root cause.

Purchase Requisition attachments should not be modified when it is released

Hi Gurus,
I've requirement that i should restrict the Users not to modify, delete, and add any attachments when PR is released. pl help me in this
-Rajiv.

Thanks giri.
For the following reasons, the billing documents are not released to accounting.
1. If the user wrongly chosen the billing type for the delivery.
2. After creating condition type, it has to be assigned in COPA. If we forgot to do it, billing doc will not released.
Our requirement is that if the billing document is not able create accounting document, the billing document itself should not be generated.
Hope this will be suffice to understand my issue and suggest a suitable solution.
Points will be rewarded.
Regards,
Kumar.

Billing documents should not be created when it is not released to accounti

Hi SD gurus,
In some situation, billing documents are generated but it is not released to accounting which results in mismatch between FI value and SD value. We go to VFX3 and see the list of billing documents and take corrective action.
Our requirement is that the billing document should not be generated when system is not releasing this billing document to accounting.
Please suggest a solution for this.
Regards,
Senthil.

Thanks giri.
For the following reasons, the billing documents are not released to accounting.
1. If the user wrongly chosen the billing type for the delivery.
2. After creating condition type, it has to be assigned in COPA. If we forgot to do it, billing doc will not released.
Our requirement is that if the billing document is not able create accounting document, the billing document itself should not be generated.
Hope this will be suffice to understand my issue and suggest a suitable solution.
Points will be rewarded.
Regards,
Kumar.

RE: Pr release , it should not be editalble like qty, material.

Similar Messages

Maybe you are looking for