PR derelease should not be allowed after PO creation

Dear Friends
I have created a PR, released , then PO is created with reference to PR. After that I came back to me54n and cancel the PR release. As per our Business Practice it should not allow to cancel the PR release after PO creation.
I have maintained message 06 076/06 400 and 06 608 as error message.
The changeability indicator is also maintained as '1' against the release indicator'2'.
I don't want to go for any Badi implementation or user exit. Is there any solution in standard SAP
Thanking you
Tapan

Even I tried this testing but it seems like not working. I this is standard SAp behaviour.
Check this OSS notes 493900
1. Question :
Why can I modify a purchase requisition although I set the changeability of
the release indicator to '1' ('Cannot be changed')?
Answer :
The purchase requisition is not modifiable via a purchasing transaction
like ME52 or ME52N. But it is possible to change the purchase requisition
from any other external application like sales order, planned order,
maintenance order or network.
The Changeability functionality only concerns the purchasing transactions.
This is intended and a new release strategy determination takes place if
there is a modification of the data in the external application.
But logically why the user is cancelling the PR after PO creation? Even if they cancel the PR it doesnt impact the PO which is already created. Even if they cancel and re release the PR and try to create a new PO, system wont allow you to create new PO stating that PR is already ordered. Even though it looks strange but it doesnt harm the procurement.

Similar Messages

Production Order Usage Probability should not be allowed to change after GI

Dear Gurus,
pls tell me how to do this ,Production Order Usage Probability should not be allowed to change after Goods Issue (GI) done against Prod Order . pls tell me procedure or any UserEXit for this.
Thanks in Advance,
Regards,
Dev

Hi,
Can you elaborate little bit more?
Regards,
Sankaran

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.

Billing document should not be cancelled after creating return sales order

Hi All,
Billing document should not be cancelled after creating return sales order with reference to billing document. Please suggest configuration settings on the same.
Sudheer.

Hi,
In SAP, when the sub-sequent document is existing , we can not cancel the preceeding document. Therefore if you want to cancel the billing document you need to calcel the documents which are created with reference to that.
Check and confirm.
Regards,
Ravi Duggirala

Inventory in storage bins should not be allowed to go negative

Hi
Inventory in storage bins should not be allowed to go negative?
Regards
Vivek

you can uncheck the "Allow negative stock" for the combination of warehouse and the storage type.
Path is-
SPRO > Logistics execution > Warehouse management > Stock removal startegies.
Then select your strategy.
Check out if it helps.
Regards,
nilesh

Zero quantity should not be allowed for STO delivery

Hi,
     zero quantity should not be allowed for STO delivery.
     when i create a delivery for a STO it should not allow zero quantity
     can someone throw some light.
Alec

Hi,
Please maintain the "B - Create Delivery with qty greater than Zero" in Part.dlv./item in shipping tab page of the customer of site.
more briefly: in WB02 --> click on the customer of the site --> Shipping Tab page --> Maintain B (Create Delivery with qty greater than Zero)
Regards,
Srini

Excise amounts should not be changed after IEI

Once Incoming excise invoice is completed, one should not be allowed to change excise amounts in the A/P Invoice. This creates to a lot of problems. This posts different amounts in the cenvat clearing amount at the time of IEI and then at the time of A/P Invoice, thus creating reconciliation problems...

done using query...

User should not be allowed to login 2 times to an application from same m/c

Hi Everyone,
I have to find all possible solutions to below problem:
Problem: User should not be allowed to login 2 times to an application from same machine.
Steps to produce the problem:
1) User 1 logins to application.
2) User 1 tries to login with different credentials from same machine.
3) User 1 should be presented with a message that he cannot login from same machine using 2 browsers.
4) User 2 tries to login to application with credentials of user 1. System should now display an alert to both users on System 1 and System 2 of this conflict.
Please share your thoughts regarding above problem.
Thank you
Edited by: rishab.garg on Feb 25, 2009 10:53 PM

When a user logs in to application flag it in database. Irrespective of client machine and browser when another user tries to login using same user id you will be able to identify that easily using stored flag against the user id.
If you want to distinguish between client machine for displaying different messages you can easily do this by comparing client IP address. To obtain client IP address use:
request.getRemoteAddr();Note that getRemoteAddr() might return last proxy machine's IP address (in case proxy is used) instead of client's machine. In that case you may consider using cookie (though using cookie is not a great idea).
Thanks,
Mrityunjoy
Edited by: mrityunjoy on 28 Feb, 2009 11:43 PM

BOM editing should not be allowed while creating P.O./ Scheduling agreement

BOM editing should not be allowed while creating P.O. / Scheduling agreement

Hi,
I think that when you create a subcontracting PO it READS the valid BOM, so there's no locking. From a business point of view you need to question such a requirement, since in SAP you can have many kinds and types of BOMs. Then what if one of the BOMs is open in change mode (edited) exactly when you try to create the order? It should not allow you to create the order? Why?
Regards,
Mario

Sales Order item should not be allowed to modify after doing PGI.

Dear all SAP experts,
When i create a sales order say for 10 pieces. Now I have created the delivery for all the 10 pieces & also created the invoice.
My requirement is when i create a delivery for all 10 pieces then after doing the PGI the system should make the sales order line item & qty "grey" - I should not be able to change the sales order item in any respects.
If not from delivery then when i save the invoice for that sales order then I should not be able to modify the sales order item & qty.
With best regards,
Allabaqsh G. Patil

Hi
I think there can be a problem in copy control
In copy control at item level, in teh item category, ensure that the field "Update document flow" and the Pos/neg quantity are properly updated.
Update document flow shoudl be ticked on
Pos/neg quantity should be positive.
Before doing this , check teh document flow of the sales order. Do the same after doign this configuration. Note the difference.
This will solve your problem

QM system has expired, MIGO should not be allowed

HI All,
If the vendor QM Sytem has expired ,then the sytem should not allow posting of goods receipt (MIGO) by using the functionality of Quality Info record or any other methods of control like vendor master or purchasing info record.
Please provide your valuable suggestions
Thanks & regards,
rajesh

The QM system is only designed to control the creation of the PO against vendors with the specifiied QM system.
If you want to block receipt at the time of MIGO, you will need to use a MIGO user exit to do a check against the vendor's QM system to verifiy it ihas not expired since the purchase order was created.
FF

User should not be allowed to change plant in SO once PR/PO is created

Hi SAP Gurus,
User has created the Purchase Request & Purchase Order for a sales order line item. After PR/PO creation user is able to change the plant. We need to stop that is there any standard configuration or setting by which i can stop the user to change the plant.
System is giving the error if i am trying to delete the item since the PO exist but not stoping me to change the plant.
Thanks
Surender

Hi,
Standard setting is not available.You need to write the specific code in Sales order change exist by checking the VBEP -schedule line table where the PR exists.so for the line item the Plant should not be changeable.
Sales Order Change exit the following requirement has to be incorporated.
You can find the user exits in SPRO-Sales and DistributionSystem ModificationsUser Exits--User Exits for Order Processing.
Regards,
Saju.S

Re-extraction should not be allowed in J2i5

Hi friends,
I have this business requirement that data should not be re-extracted once the extraction is done
in J2I5 .
I did not find any User_exit or BADI for the same .
Can anybody suggest me how can i go about it.?

You can copy the program to a Z program and check whether the excise registers are already extracted with the given date or not.
You can make use of Last extraction date button on the input screen to validate the data on the input screen.
Regards,

Purchase org. field entry should not be Mandatory for PR creation/release

Dear Experts,
When we are creating PR (ME51N), Purchase organization field entry is mandatory for few user id & in few user id this field is not mandatory. While we are creating PR by which user id, where purchase org. field entry is not mandatory (not fill purchase org. field) & release PR (ME54N) than system ask purchase org no.
Purchase organization field entry should not be mandatory for us when we are creating & release the PR for all user ID's. How can be maintain this things on all user ID's.
Please help us regarding this issue.
Thanks & Regards,
Shatrughan

Hi dear,
Do the following settings in SPRO,
SPRO->MATERIALS MANAGEMENT->PURCHASING->PURCHASE REQUISITION->DEFINE DOCUMENT TYPES.
Here check the Field selection Key for your document type.
Now go to
SPRO->MATERIALS MANAGEMENT->PURCHASING->PURCHASE REQUISITION->DEFINE SCREEN LAYOUT AT DOCUMENT LEVEL
Now double click on the field selection key which you have found earlier and now double click on Reference data,item and set the indocator as optional for Purchasing Organisation key.

Deletion of Delivery after confirm of Pick and WM TO, should not be allowe

The system will allow a delivery to be deleted after confirmation of Picking and WM TO. This creates all kinds of issues in WM for tracebility. Is there any way to prevent this from happening through config in WM or SD?
Edited by: Daryl Dellinger on Jan 30, 2008 3:51 PM

Try OSS notes 567666 - stock inconsistencies after deletion of delivery items
Regards
Edited by: Shiva Ram on Jan 30, 2008 8:32 PM

PR derelease should not be allowed after PO creation

Similar Messages

Maybe you are looking for