![]() I recommend you run your SQL in a TEST/DEV environment before applying to PRODUCTION, also make a back up of your database and the Maximo Folder before running the above SQL. (NRS 616B.557 590) Contact Jacque Everhart at (702) 486-9089 or everhartbusiness.nv.gov for more information. The costs of any qualified subsequent injury are paid from the appropriate subsequent injury account. Update maxvars set varvalue=0 where varname='INVOICEMGT' and orgid='EAGLENA' Īfter updating any of the above three Maxvar values, you will need to restart the MXserver. The Subsequent Injury Accounts encourage employers to hire workers with a permanent physical impairment. Here is the SQL to run (Please replace "EAGLENA" with your orgid): If you do not use Maximo for invoicing and wish to be able to bulk close PO's from the list tab, you can set another maxvar - "INVOICEMGT". ![]() Update maxvars set varvalue='1' where varname='CLOSENOINVOICEPO' and Update maxvars set varvalue='1' where varname='CLOSENORECEIVEDPO' and Here is the SQL to run to change these values (Please replace "EAGLENA" with your orgid): The CLOSENOINVOICEPO maxvar controls whether PO's can be closed even if they are not completely invoiced. The CLOSENORECEIVEDPO maxvar controls whether PO's can be closed even if they are not completely Consider changing these maxvars to suit your business needs. ![]() Whether Maximo will allow the batch closing of PO's is controlled byīoth maxvars default values are 0 and this default setting causes theīehaviour and messages you are seeing. The error you are receiving can be avoided by changing settings in the maxvars table.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |