PR changes after PO Creation

Dear All,
How is it possible not to allow a PR to be changed in case a PO has been created for it? I do not want this to be related to release (changeability) but only to the PR processing status. Can it be done through creating or changing an error / warning message?
Thanks,
Hisham

Hi,
There is no standard erroe message that you can use for this.
If you really need to do this then you will need to use a user exit to check the status when a req is changed.
Most people stop all changes once the requisition has been approved and so no changes can be made after the PO has been created (due to the release strategy, not to the creation of the PO).
Steve B

Similar Messages

Sale order 'value changes' after invoice creation

Experts,
A sale order was created / shipped / invoiced. The invoice did not go to accounting because of credit auth error. We have a procedure to fix it and then release it to accounting (transaction VFX3). All OK until this point.
While fixing the auth error, an user changed the freight condition value in the sale order. Then invoice is released to accounting. Now, the value of freight in order and invoice match. How is it possible to change the value of an invoice after its creation?
Any input would be appreciated.
UV

when the value is changed in the sale order, it would automatically transfer
the new pricing to the existing open SD invoice pending accounting entry??
Certainly not. The control is in VTFL where if you select the billing item category for the combination of your delivery type and billing type, you can see a field "Pricing Type". If you maintain any value other than "B", system will copy the price from sale order to billing and you can, as I said above, can change manually in billing. On the other hand, if you have maintained "B" in the above field, system will not consider sale order price but will check your pricing condition maintained in VK11 which you can check in VK12 or VK13.
thanks
G. Lakshmipathi

PR should not change after PO Creation without Unrelease

Hi,
We want that User cann't change the PR after PO Creation.
For Ex.:- We create a PR with 10 Qty., release it and also create PO with 10 Qty.. Now after PO creation with same qty, no one can change PR (Qty, Purchase Group etc...)..
If User Un-release the PO and PR, then user should be able to change in PR...
Please guide...

Thanks a lot dear..
After doing this, i create a new PR and PO with 10 qty... After PO, i unrelease the PR and change the Qty from 10 to 15 nos..then system shows an error message Requisition already converted into purchase order...
But when we change 10 qty to 5 qty, PR allow the same... I want to insert another check here, that user cann't insert less than qty there... There should also be a Message there in system...
Please guide...

Baseline date change after the creation of invoice list

When I create invoice document, the invoice date (vbrk-fkdat) is the end of the month and the invoice list date (VBRK-FKDAT_RL) is the next business day after the invoice date, the baseline date of the accounting document (bseg-zfbdt) is the document creation date and this is what I wanted.
However, when I start to create the invoice list, the baseline date on the accounting document (field bseg-ZFBDT) is changed to the invoice list date. Does anyone know why and how to fix and where to look in the configuration to see how invoice list date (vbrk-fkdat_rl) is populated? It seems to me that the baseline date default back to the invoice list date when invoice list document is created. Thanks for your help. I also posted this question in the ERP Financial thread.

Hi Valerie,
do you recall the User Exit?
Thanks

Enhancement in IDOC_INPUT_ORDERS not saving changes after order creation

I have an enhancement at the beginning of the IDOC_INPUT_ORDERS function module used to create sales orders via EDI. In the enhancement, I take the data records and make some changes to some quantities and units of measure. After making these changes, I let the function module continue on as normal. The order does get created with my changes in them, however, the IDoc doesn't reflect my changes.
Here's an example: An EDI order comes in with 6 EAs of a material. In my enhancement, I change it from 6 EAs to 2 3PK. I then let it go on its way. The order gets created fine with 2 3PKs, however the IDoc after its a ll done still says 6 EAs.
The enhancement runs before the FM puts the data into the tables it uses. I tried using the last user exit to open the IDoc and editing it there using the EDI_DOCUMENT_OPEN_FOR_EDIT FM but it says its open.
Can anyone give me any clues on how to make my changes stick to the IDoc?
Thanks,
Curtis

Ok, I figured out why it's not saving. Not realizing it, but the tables are passed into the FM by reference, so what I'm changing is only a copy. So what I tried to do is use the 004 (I've also tried the 005) user exits to try to update the actual DB. I used the following FMs (EDI_DOCUMENT_OPEN_FOR_EDIT, EDI_CHANGE_DATA_SEGMENTS, and EDI_DOCUMENT_CLOSE_EDIT). The problem is that I can't change them because the IDoc is still open.
Does anyone have any ideas on how I can achieve my goal of changing the IDoc?
Thanks,
Curtis

'Inverted Threshold' error on 'Activate Changes' after queue creation

Hi,
In Weblogic Server Administration Console I am trying to create a new Queue by first clicking 'Lock & Edit' and thereafter creating the Queue. When I do this I get an expected: 'The JMS Queue was created successfully' message but, when I then try to click 'Activate Changes', I get an: 'Inverted threshold' error message.
Log file shows: <Failure occurred in the execution of deployment request with ID '1368101884686' for task 'weblogic.deploy.configChangeTask.2'. Error is: 'java.lang.IllegalArgumentException: Inverted threshold' java.lang.IllegalArgumentException: Inverted threshold
Any ideas what this error actually means?
Thanks in advance.

Hi Vijaya,
Thanks for the response but I don't think this error has anything to do with a queue's Message Threshold values. The weblogic server has a number of JMS modules and on one JMS module, Queues can be created and activated successfully but not on the other JMS module. I am not too familiar with Weblogic AS so I am not sure how to track down the source of the error. The best error info I get from the logs is the following:
*<May 9, 2013 4:39:40 PM BST> <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating redeploy task for application 'CommerceJmsModule'.>*
*<May 9, 2013 4:39:40 PM BST> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004*
java.lang.IllegalArgumentException: Inverted threshold
at weblogic.messaging.kernel.internal.StatisticsImpl.addThreshold(StatisticsImpl.java:190)
at weblogic.messaging.kernel.internal.StatisticsImpl.addByteThreshold(StatisticsImpl.java:179)
at weblogic.messaging.common.ThresholdHandler.replaceBytesThreshold(ThresholdHandler.java:115)
at weblogic.jms.backend.BEThresholdHandler.setTarget(BEThresholdHandler.java:59)
at weblogic.jms.backend.BEDestinationImpl.open(BEDestinationImpl.java:267)
Truncated. see log file for complete stacktrace
java.lang.IllegalArgumentException: Inverted threshold
at weblogic.messaging.kernel.internal.StatisticsImpl.addThreshold(StatisticsImpl.java:190)
at weblogic.messaging.kernel.internal.StatisticsImpl.addByteThreshold(StatisticsImpl.java:179)
at weblogic.messaging.common.ThresholdHandler.replaceBytesThreshold(ThresholdHandler.java:115)
at weblogic.jms.backend.BEThresholdHandler.setTarget(BEThresholdHandler.java:59)
at weblogic.jms.backend.BEDestinationImpl.open(BEDestinationImpl.java:267)
Truncated. see log file for complete stacktrace
*>*
*<May 9, 2013 4:39:40 PM BST> <Error> <Console> <BEA-240003> <Console encountered the following error weblogic.application.WrappedDeploymentException: Inverted threshold*
at weblogic.messaging.kernel.internal.StatisticsImpl.addThreshold(StatisticsImpl.java:190)
at weblogic.messaging.kernel.internal.StatisticsImpl.addByteThreshold(StatisticsImpl.java:179)
at weblogic.messaging.common.ThresholdHandler.replaceBytesThreshold(ThresholdHandler.java:115)
at weblogic.jms.backend.BEThresholdHandler.setTarget(BEThresholdHandler.java:59)
at weblogic.jms.backend.BEDestinationImpl.open(BEDestinationImpl.java:267)
at weblogic.jms.backend.BEQueueImpl.open(BEQueueImpl.java:99)
at weblogic.jms.backend.BEDestinationRuntimeDelegate.initialize(BEDestinationRuntimeDelegate.java:163)
at weblogic.jms.backend.BEQueueRuntimeDelegate.initialize(BEQueueRuntimeDelegate.java:59)
at weblogic.jms.backend.BEDestinationRuntimeDelegate.prepare(BEDestinationRuntimeDelegate.java:187)
at weblogic.jms.module.JMSModule$EntityState.setState(JMSModule.java:1704)
at weblogic.jms.module.JMSModule$EntityState.setState(JMSModule.java:1667)
at weblogic.jms.module.JMSModule$EntityState.access$100(JMSModule.java:1608)
at weblogic.jms.module.JMSModule.prepare(JMSModule.java:277)
at weblogic.jms.module.ModuleCoordinator.prepare(ModuleCoordinator.java:185)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:42)
at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
at weblogic.application.internal.SingleModuleDeployment.prepare(SingleModuleDeployment.java:16)
at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:155)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
at weblogic.deploy.internal.targetserver.operations.RedeployOperation.createAndPrepareContainer(RedeployOperation.java:98)
at weblogic.deploy.internal.targetserver.operations.RedeployOperation.doPrepare(RedeployOperation.java:122)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:723)
at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1190)
at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.
java:157)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
*>*
Any other thoughts would be much appreciated!

Contract Total value change after PO creation & GR

Hi,
I would like to understand whether the below mentioned behaviour is a standard one of SAP.
Value contract (WK) is created for 10,000 INR. And PO created for 5,000 INR and GR&IR also done
for 5000 INR.
Now I am able to reduce the target value of contract below 5000 INR in ME32K.
I feel system should not allow to do the same.
Please throw your opinion.
Regards,
Partha

Hi Jurgen,
Thanks for your input.
As we go with your example with the assumption that procurement
has happened fully for 1 million kg and vendor was also paid
for 1 million kg, Then I feel system should atleast warn the user
when he is trying to reduce the quantity in contract header.
I would be happy to receive your comments on the above.
Regards,
Partha

Purchase order rate change after creation of gr.

In t- code ME22N PO line item Rate change is possible after creation of GR against that line item.
We want to restrict the po line item rate change after creation of goods receipt against that line item.
Please suggest.

solution 1 : Do not give authorization for ME22
solution 2 : Grey out price chage , it should only be possible thru info records, and give authorization of info records in secured hands.
You should not totally restrict price change after GR because there are possibilities that you might require to change rate after goods receipt also. In that case you have to change rate and then have to give restrospective effect to GR.
try above 2 solutions which are simple

How to block changes in pr after po creation

We have set up the system messages (06 76 as error). However still it is possible that the user can change the description or add new line item after after the release/po creation. How to prevent this. how to block changes in pr after po creation
do i have to create new system messages if yes then hoe kindly suggest
Thanks.
regards

Dear Goel,
When setting the message 06076 and 06400 as described in the note 385002
to error it is no more possible to create a second purchase order with
reference to the purchase requisition.
See SAP note
315448     ME21N: Referencing a purchase requisition
Regards
V V

Schedule line date changes after each MRP run

Dear Experts,
Clarification needed on how the system plans the MM schedule lines.
Setting: Start in the past not allowed.
3 days for processing of order
The issue is after each MRP run the system is moving the schedule line to the current date + 3 days for processing + the planned delivery time.
If the schedule line is not firmed, after each MRP run ( which happens everyday) the system is moving the schedule line and then giving an alert saying the " order has to be rescheduled to the previous day"
on the second day after the mrp run the system moves the schedule line again by one more day and gives the rescheduling date as " -2 days from today"
this change is happening every day after the planning run. - because of this there are really no backorders ( schedule line in the past ) in the system. we were not able to know if the vendor is actually delayed in this case.
can you kindly suggest what went wrong here ??
we are using strategy 10 for the planning of procured parts. Let me know if more info is needed.
Note: we are also using stock transfer process for some procured parts. there too the PR date gets changed after each MRP run. There there is no lead time in this case. the order is placed on the same day as the requirement as both plants are nearby. There the PR date is changing everyday to the current date.
your advice would be of great help
thanks
Nagendra Kumar

Hi Caetano,
thanks for your suggestion
Yes, we use firm zone for few of the vendors. there the system don't change the schedule lines.
Also for the stock transfer PR's there is no firm zone and the lead time is one day. in this case it changes everyday after the MRP run.
the stock transfer PR's leads to the creation of Schedule lines from the source plant. Since this PR gets changed everyday. the alerts coming out of MD07 gets changed and we really did not know if this order is delayed or not. In the source plant we use the firm zone to avoid moving the schedule line. But then the alerts are always not correct.
is there any setting which helps in not moving the PR everyday without using " start in the past"
thanks
Nagendra Kumar

Address data changed after invoice is created

Hi,
I've a problem to solve and it's related with data changed after invoice is created.
The scenario is the follow:
1º - create a complete and standard sales process - order => delivery => invoice, with the standard partner scheme and without edit the address data, for any kind of partner
2ª after the invoice is created, I change the address data on Client Master Data, for the same client that I've used on previous process
3º I'll go to the VF03 transaction and take a look at the partner data on header level. Here I can see that the changes on the Client Master Data ar updated to the invoice document wich is already created and printed when I maked the changes
I think that could be a program error because, once the documento is created, you only can change texts and accounts if this document is not yet created.
And, I can't edit this kind of data on invoice creation because it must be done at order level.
So I don't understand why it happen, but it happen on more than one client.
I'll hope that anyone can help me to solve this issue.
Kind regards,
Nuno Rodrigues

Hi Nuno,
the adresses of all Clients are stored in table adrc. If there are no changes in the order, the system takes the standard adress of the client. That is made for not having an extra adress for each order.
If you change the adress - the system will create a new adressnumber ( 999........ - see in VBPA ).
If you have different adressnumbers in your orders, you are not able th collect several orders into one delivery note - for the adressnumber ist normally a split-criteria.
Ich you will have an extra Adress for each Order, change the adress - for example by an user exit.
But if you have different adressnumbers - the delivery and the invoice will split the different orders - if you dont do something against in an user-exit.
Hans

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.

Detail changes for release creation on schedule aggreements

Hi Experts,
Landscape:
-we have a standard ERP 6.0 system with an external EDI converter
-IDoc data exchange via RFC connection
-IDoc SAP standard (without modifications or add ons): message type: DELINS, basic type: DELFOR01
If we create a release on a schedule aggrement, all schedule lines in forecast comes out as expected.
When we delete some schedule lines, these lines exported to IDoc with quantity 0 and have an aggregation per week. So we have the following structure in IDoc:
E1EDK09 (head data)
|-E1EDP10 (pos data)
      |-E1EDP16 (schedule line): aggregation per week (IDoc field PRGRS = W), quantity 0
      |-E1EDP16 (schedule line): aggregation per day (IDoc field PRGRS = ' '), quantity 10
      |-E1EDP16 (schedule line): aggregation per week (IDoc field PRGRS = W), quantity 200
      |-E1EDP16 (schedule line): aggregation per week (IDoc field PRGRS = W), quantity 200
      |-E1EDP16 (schedule line): aggregation per month (IDoc field PRGRS = M), quantity 9000
So far so good. This looks fine.
But our standard EDI converter expect the IDoc data starting with days, weeks, months aggregation. If the first schedule line with aggregation weeks are send, the converter expect all other schedule lines with aggregation per week or per month.
It is possible to change the release creation in the IDoc without coding in User-Exits, just with customizing?
regards,
Steffen
Edited by: Steffen Froehlich on May 3, 2010 1:31 PM (accidentally clicked on Post than Save button)

Hi,
   Go to MN04 transaction and maintain the "Date/Time" as 3 for the specific output type condition record as shown below:
   Test the scenario again with a new PO. Now, system wont generate the spool immediately after release and save in ME29N and the output will be "in process" mode (yellow signal). You can process the output in ME9F transaction to display and print.
Regards,
AKPT

When creating a new window in safari, using command T, the marker have not activated the search field. It means you have to click there every time. Changed after upgrading to Mavericks. Anyone knows how to change this?

When creating a new window in safari, using command T, the marker have not activated the search field. It means you have to click there every time. Changed after upgrading to Mavericks. Anyone knows how to change this?

Yes, you can do something like that. What you would do is create a button for each image and then hide them. When I do this type of thing I place all of the buttons on a template page and then hide the template.
You can then use JavaScript to copy the icon from any of the hidden buttons to the main button that you've set up to display the image. For example, suppose you set up 10 buttons named b1, b2, b3, ...b10. The code to copy the icon from one of them to the button used to display the image (b0) would be something like this:
// Get the icon from the b3 button
var oIcon = getField("b3").buttonGetIcon();
// Get reference to the b0 button
var f = getField("b0");
// Set the icon of the b0 button to the icon retrieved from the hidden button
f.buttonSetIcon(oIcon);
// Show the b0 button
f.display = display.visible;
This code would go in the Mouse Up event of the smaller button.

Account of the opportunity is not populated after the creation of a task

Hi,
In our project, we are using the Opportunity Object after the creation of a task. Our tasks are always related to an existing account.
I was wondering why when I create an opportunity from a task, the field "Account Name" is not populated by default with the account name related to the task.
Any ideas?
Regards,
Dara
Edited by: user6469826 on 2 août 2011 11:40

Contact an electronics repair shop.

PR changes after PO Creation

Similar Messages

Maybe you are looking for