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

Similar Messages

MIGO should not create after PO Delivery Date

Hi,
We have a PO with multiple line items and diff. Delivery Dates...
We want that during MIGO Process, Posting Date should not exceed to PO Delivery Date.
Means, if PO Delivery Date is 05.07.2014, then MIGO should not created after this date...
Please suggest.

If you want to achieve the scenario with standard settings, then you can use the field "Latest GR date".
Just put the same date as delivery date in this field. Then system will not allow to do GR if the Posting date is exceed with compare this date in MIGO.
You can find the latest GR date in Delivery tab in PO. Also you can maintain the field as mandatory in PO to avoid the field value blank as per your requirement.
Also if you want to change Latest GR date along with delivery date, just take the steps which is explained in this document Mass changes from one field to another field.
**Edited by: Dëv Päträ

Outlook 2013 Clients certificate has expired warning or not yet valid

Hello,
We had been through a migration from exchange 2010 to 2013 in the last year but have had an ongoing issue with
some Outlook clients getting a certificate warning after they launch the client. Not all Outlook clients experience this. We've just recently uninstalled exchange from our 2010 servers and shut them
down. What we have left are two 2013 servers in a DAG. The certificate these Outlook clients are complaining about had expired in 2012. Here is the warning they are getting:
"Certificate has expired warning or not yet valid"
I've been through numerous threads/sites regarding this error but it always ends up that there was an expired cert hanging out somewhere. I cannot seem to find an expired cert anywhere...
I've ran the 'Get-ExchangeCertificate | fl' cmdlet and I see 7 certs listed, none of which match the thumbprint on the Cert Warning on Outlook.
When I check the registry of the Exchange servers here: HKLM>Software>Microsoft>SystemCertificates>My>Certificates
I can see 7 certificate entries listed there and the thumbprint matches those of the cmdlet ran from
EMS.
OWA shows the correct cert expiring in 2015 and Outlook clients are pointed to the 2013 servers. We do have a load balancer that AutoDiscover, OWA, SMTP are going through.
It seems like some of these Outlook clients are still looking at the decommissioned 2010 Exchange servers' old certificate. Any ideas on how I can get outlook to point to the new certificate/server?
Thanks.
Rory
Rory Schmitz

Hi Rory,
If possible, could you please post the Get-ExchangeCertificate | FL results about the certificate which is assigned with IIS service here?
If the issue only happens for some users instead of all users, please create a new Outlook profile for the problematic user to check whether the issue persists. Please make sure the certificate name which is reported as expired or not valid is included
in the IIS service certificate in your Exchange 2013.
In Exchange server side, please restart IIS service by running IISReset /noforce from a command prompt window to have a try.
Regards,
Winnie Liang
TechNet Community Support

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.

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

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

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

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

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 orders with expired dates should not consider in MRP

Hi,
My requirement is that when i m running MRP for sales order for which expiry date has already been lapsed or over.sysyem should not create any mrp elements(Planned order) for such Sales orders.
We have maintained one Z table which gives the validity period(Expiry date) for sales order according to their respective division.
if MRP running date lies after the date of expiry of sales order, system shoul not allow to run MRP for that sales order or it should pop some message while executing MRP run before saving it.
How we can achieve this?
Pls suggest.....
Rgds,
Yogesh Thorat..

Since as per standard, there is no concept called validity period for sale order and you are maintaining in a zee table, definitely your requirement has to be met with user exit or function module or some enhancements.
Perhaps, you can try with MRP Enhancements
a) LMDR2001 or
b) LMDZU001
to meet your requirement.
thanks
G. Lakshmipathi

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

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

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.

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,

System has power but will not load up to bios.

system will not load to bios after i just installed the mother board. power and ever thing else seems to be working, but it still will not boot; even to bios. i have a neo pt8 can any one help me give me hints of what might be worng once i get it to bios i can take it from their. my aim is caperneoignis
my system specs are
p4 1.6ghz 256 cache 400mhz 478 pin
samsung 512 ram ddr 266
singel IDE 100 7,000 rpm westren digtal hd
nvida geforce 4 128mb couldnt rember the exat make
sound blaster auidgy gamer
450 watt turbolink switching power supply
+3.3/28A +5/40A +12/18A
mother board is a pt8 neo
if you need any more info let me know

Read and post all the info asked for in this Moan Guide

QM system has expired, MIGO should not be allowed

Similar Messages

Maybe you are looking for