During PO creation system should not allow to create more than contract val

Hi,
System is allowing to create the PO more than the contract value so I want to stop it please explain the required config settings.
always system should allow to create the PO with in the contract value only.
thanks.

Hi,
GOto IMG>MM>Purchasing>Environ Data>define attrib of system messages
change Msg.No:042 in Appl Area:06 & Version:00.. to Error Message...
This will solve your problem
Edited by: Antony anburaj on May 5, 2010 9:41 AM

Similar Messages

During PO creation system should not allow to save if it cross the PR value

Hi,
As I said in above subject line while creating the PO system should not allow to create more than the PR value and Quantity.
Always system should allow the person to create the Po with in PR value as well quantity in order to set up please let me know the configuration settings.
thanks in advance.

Hi,
Please search the forum first for your queries for existance and then post queries., coz, the same question has been answered so many times before.

Delivery is invoiced fully so system should not allow to create 2nd invoic

hi Expert,
my issue is, once invoice is created for delivery.
system should not allow user to create
second invoice for same delivery number.
where to check the confiurtion to stop such
behaviour
waiting for your reply
thanks
Alicia

Hi Alicia
In the copy control from delivery to invoice - T code VTFL
you can maintain the copy routines. try maintaining routine
3-- which is delivery reatled header
4-- which is delivery related item
also at item level copy control you may add the check in billign quantites
this would stop formc reating another invocie
Hope this helps
Thanks
Akasha

After creation of PO system should not allow to change the price in PO

Hi There,
In my scenario once PO is created then after send to vendor PO print document,Users are changing the price in PO.so system should not allow to change the price in PO once PO got saved.
So please advice.

Hi,
you could set in customizing for field selection keys the net price
to display for ME22N so that changes can not be made
(transaction OLME -> purchase order -> Define Screen Layout at Document Level).
Please check that you have set all the relevant field selection
groups to display: AKTV, ME22, ME22N... (read and apply note 30316)
Other workaround is try to do by yourself with the badi
ME_PROCESS_PO_CUST and send your own error message.
Regards,
Edit

System should not allow to delete PO line Item after GR/IR

Hi,
I am working on a SAP Retail Implementation project.
Currently the system is allowing us to delete the PO line items after doing GR or IR against that PO line item. But the clients requirement is that the system should not allow to delete PO line item after doing GR/IR.
We are using Account Assignment Category-N, Item Category-S.
Please let me know if you have the solution for this requirement.
Thanks in advance
Thanks & Regards,
Suresh

Hi,
Standard SAP will not allowed the PO to be deleted once it was GR done. The controlled is on the attributes of message to set as "E"
Message no. 06115
But if invoiced takes place, the is the point that PO can be deleted.
You have to do have a Enhancement using MM06E005, insert you logic here to check PO history tables like EKBE, then check if invoice " Q" (BEWTP) exist, the PO cannot be deleted once the user delete the PO line and SAVE it. Ask you developer to help you on the following coding.
Use MM06E005 and EXIT_SAPMM06E_012
IF SY-TCODE = 'ME22N'.
IF sy-ucomm = 'MESAVE' OR SY-UCOMM = 'YES'..
LOOP AT TEKPO.
IF TEKPO-LOEKZ = 'L'.
SELECT SINGLE BELNR FROM EKBE INTO BELNR1 WHERE EBELN = TEKPO-EBELN AND EBELP = TEKPO-EBELP AND BEWTP = 'E'.
IF SY-SUBRC = 0.
SELECT SINGLE BELNR FROM EKBE INTO BELNR2 WHERE EBELN = TEKPO-EBELN AND EBELP = TEKPO-EBELP AND BEWTP = 'Q'.
IF SY-SUBRC = 0.
Regards,

System should not allow to do the changes in PO once the ID created.

Hi All,
Once the Inbound Delivery is Created based on the Purchse Order, System should not allow to do the changes in the Purchase Order like Deletion of Item, etc..
Any Configuration Changes is avaliable. ?
Regards,
Sudhakar

Dear,
Please check the staus in order
Current order status xxxx does not allow goods receipt (Message no. C6009)? is this the message?
This will not allow you to do GR for production order when you activate status profile "SAT1" in the production order. After that when you confirm order it will automatically assign next user status i.e. "SAT2" (if not assign it manually in CO02) it will allow you to do GR for that production order.
Regards,
R.Brahmankar

System should not allow to add line items in delivery

Hi,
1) system should not allow to add line items in delivery( in reference to sales order or STO)
2) sales order/STO should not be changed if delivery exists
how to control the above
Alec

Hi Lakxmi,
I found answer for 1st point from you are old answers.
can you throw somelight on 2nd point.
Thanks
Anil

QA32: Without going in Inspection lot stock screen system should not allow for UD

Hi
At the time of UD "without going in Inspection lot stock screen system should not allow to save the UD".
Please suggest how to restrict.
Regards
Ashish

Please go through the below link & with small changes you can fulfill your requirement using user profile
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/601c82e3-b743-2c10-dbb6-ed4c00167157?QuickLink=index&…

With out goods issue for order system should not allow for order confirmati

Dear all
with out goods issue system should not allow for order/operation confirmation.
how it is possible.
Regrads
Srinivas

Dear ,
In some cases we required to do confirmation or TECO without GI .
We can change it as per req using user exit
Regards,
Ishwar

Without result recording closing system should not allow for usage decesion

Hi
without result recording closing system should not allow for usage decision.I think it is possible through user status. Please tell the procedure .
Thanks and regards,
vairavan

Dear vairavan,
You can check for the authorisation object.I can't remember that authoriation object right now.But surely you can restrict that with authorisation object.
Anyone knows the authoristaion object.
Regards,
Sunil Patil

System should not allow PO beyond Maximum price.

Gurus,
My requirement is as follows:
I have a material which has a Max Purchase price of 100.Now whenever I create a PO system should not allow me to create a PO beyond 100.
Pl suggest a way out
SN

Hi,
According your rquirement while creating PO , material price ( that should be a condition based) does not cross your price limits,
In PO we have number of conditions like
Gross price
Discounts
Surcharge
etc........so on
for each condition type we can give upper limit while maintaining Material-Vendor info record(vendor -material specific).for this combination only it's works.
Regards,
Venkat

Is it true that iPhone 4s does not allow to take more than 1000 photos?

Hi!
Is it true that iPhone 4s does not allow to take more than 1000 photos?
http://dolboeb.livejournal.com/2299939.html

Not true.
Only Photostream is allowed to take a max of 1000 photos, then they will be removed from server/icloud.

NTLM Authentication : why is it not possible to create more than one NTLM realm ?

Hello,
I'm wondering why it is not possible to create more than one NTLM realm on a wsa.
Can you explain exactly what is the blocking point ?
Thanks in advance
Regards

Well, at this point (pre 7.5), there isn't an agent, the WSA is joined to the domain, just like a Windows box, it authenticates via that trust relationship. From that point it is all based on how NT/Active Directory domains work. As long as there is a trust between the domains, you can can auth users from as many domains as you like.
There is an agent in the works. The ADAgent will be released with 7.5. The code is already available, it was released with the ASA ver 8.4, and it will be used to pass authentication info to the WSA. At this point, current versions still require trust relationships between all of the domains touched.
Taken from the setup guide: http://www.cisco.com/en/US/docs/security/ibf/setup_guide/ibf10_install.html#wp1054011
Before you configure even a single domain controller machine using the
adacfg dc create
command, ensure that the AD Agent machine is first joined to a domain (for example, domain
J
) that has a trust relationship with each and every domain (for example, domain
D[i]
) that it will monitor for user authentications (through the domain controller machines that you will be configuring on the AD Agent machine).
Depending on your Active Directory domain structure, the following scenarios are possible:
1. Single Forest, Single Domain—There is only one domain, D[i] for all domain controller machines, which is one and the same as domain J. The AD Agent machine must first be joined to this single domain, and since no other domains are involved, there is no need to configure any trust relationship with any other domain.
2. Single Forest, Multiple Domains—All the domains in a single forest already have an inherent two-way trust relationship with each other. Thus, the AD Agent must first be joined to one of the domains, J, in this forest, with this domain J not necessarily being identical to any of the domains D[i] corresponding to the domain controller machines. Because of the inherent trust relationship between domain J and each of the domains D[i], there is no need to explicitly configure any trust relationships.
3. Multiple Forests, Multiple Domains—It is possible that domain J might belong to a forest that is different than the forest to which one or more of the domains D[i] corresponding to the domain controller machines belong. In this case, you must explicitly ensure that each of the domains D[i] has an effective trust relationship with domain J, in at least one of the following two ways:
a. A two-way external trust relationship can be established between the two domains, D[i] and J
b. A two-way forest trust relationship can be established between the the forest corresponding to domain D[i] and the forest corresponding to domain J

Once payment received for bill system should not allow to cancel

Hi Experts ,
we have created commercial invoice and posted to fi document and payment received from party.but when we try to cancel the same billing document system allowing to cancel the document.So Client requirement is once payment received from party system it should not allow to cancel the billing document.
Please give your valuable suggestions on the same ...
regards...
MM

Hello,
In the Tx VOFA for the billing type to be cancelled(Ex F2), please
fill the field Copying Requirements(V_TVFK-GRBED_S) with '29'.
This routine prevents the cancellation of the billing documents which
have been cleared.
Regards,
Raghavendra YN

System should not allow overlapping trips

How to restrict the sytem - overlapping trips should not be allowed in R3 as well as ESS. Error message should be displayed.

That is a standard functionality.
Say you have created a trip from 01.01.2009 to 05.01.2009 and created an expense report for it.
Now you try to create another travel request from 03.01.2009 to 07.01.2009, system will give error

During PO creation system should not allow to create more than contract val

Similar Messages

Maybe you are looking for