Shuhail,
OK, you have a mess and will need to do a little more investigating.  Quite 
likely, you don't want to mess with anything below status 40 - your facility 
probably has those in process. Here's a suggested method to determine what you 
want to do, assuming that your company has some rules and cares about 
profitability and such.  This is NOT something you want to do as a regular 
procedure, but it will clean up your current mess.  I'm assuming you can write 
some very simply programs.....
Step 1:  Run a query to determine order quantity completed vs. qty ordered on 
all orders at status 40 or higher.  That will give you a list of the orders that 
MAY be done.  Make that a file.
Step 2:  Write a program that will take the file from step 1 and run through 
MODATA for each order.  Check to see if the quantity issued matches the quantity 
required.  For each MODATA component where the quantities don't match, extend 
the difference between ((quantity required - quantity issued) * UCDEF) (Get 
UCDEF from ITMRVA).  Create an output file with Order#, Order Due Date, Order 
status, and extended variance price.
Step 3.  Print the file, show it to your accounting person responsible for 
factory variances and profitability.  Have that person give you a dollar limit 
for allowable variances (I'm assuming your company cares about profitability).  
It is also quite likely the person will also give you a cut-off date where the 
company doesn't care about orders older than a certain date.
Step 4.  Write a program that will read the file created in Step 2, and apply 
the selection logic given to you by the accounting person in Step 3.  For all 
orders that match that criteria, set the MOMAST order status to "55".  (An 
alternative would be to generate an "RM" transaction with the Order Completion 
set to "C", but in reality, all that will do is give you an audit trail in 
IMHIST - it was important to my former employer, but if you guys aren't 
concerned about that, which seems likely based on what's going on....).
Step 5.  Run the normal IM Order Close and Purge, also select the option to 
purge canceled orders.  That will properly clean up everything in the system.  
Keep the close audit summary report and give it to your accounting person, along 
with the print out from Step 3 (and his/her/their instructions).   I'd keep a 
copy for myself for a while, strictly as a CMA in case someone questions what 
happened in the future.
---------------------------------------
INITIATE PROCEDURES TO START CHECKING AND PROPERLY CLOSING ORDERS FROM HERE 
ON!!!!  You really DON'T want this to be a common methodology!!!  This is a 
crude method of getting you out of the hole you are in.
Good luck!
 Dale (Cork) Gindlesperger, CPIM 
________________________________
From: Shuhail Mohamed <shuhail.mohamed@xxxxxxxxxxxxxxxxxxx>
To: MAPICS ERP System Discussion <mapics-l@xxxxxxxxxxxx>
Sent: Thu, December 16, 2010 7:15:58 AM
Subject: Re: [MAPICS-L] Closing MOs
Count is as below by Status:
Blank   =        80
10      =       347
40      =    3928
45      =      28
99      =      59
-Shuhail
-----Original Message-----
From: mapics-l-bounces@xxxxxxxxxxxx [mailto:mapics-l-bounces@xxxxxxxxxxxx] On 
Behalf Of Dale Gindlesperger
Sent: Thursday, December 16, 2010 5:23 PM
To: MAPICS ERP System Discussion
Subject: Re: [MAPICS-L] Closing MOs
Shuhail,
What is the status of the orders in question?   Are they at 40 or 50?  (Check
Order Status in MOMAST)
Dale (Cork) Gindlesperger, CPIM
________________________________
From: Shuhail Mohamed <shuhail.mohamed@xxxxxxxxxxxxxxxxxxx>
To: MAPICS ERP System Discussion <mapics-l@xxxxxxxxxxxx>
Sent: Thu, December 16, 2010 6:43:56 AM
Subject: Re: [MAPICS-L] Closing MOs
Forgot to mention one thing earlier. IM & PCC not interfaced to IFM. We want to
re-implement (re-map) XA.
-----Original Message-----
From: mapics-l-bounces@xxxxxxxxxxxx [mailto:mapics-l-bounces@xxxxxxxxxxxx] On
Behalf Of Shuhail Mohamed
Sent: Thursday, December 16, 2010 4:52 PM
To: MAPICS ERP System Discussion
Subject: [MAPICS-L] Closing MOs
Hi to all,
In one of our environment MOs have been never closed after the initial closings
(Number of open MOs = 4400). Now closing them one by one is not on the cards due
to the time and effort needed.
What is the best proven way to Set the MOs to close stage or forced close stage
using a SQL or some other program? What I need is the all the files/fields that
needs to be updated with the values need to be set. I can manage to write the
SQL statement. After that we will take the Purge option thru the XA system. Pls
advice.
Rgds
Shuhail
Confidentiality and Disclaimer
* This email has been scanned by Hayleys PLC  Group IT Risk Management Services
*
This email and any files transmitted with it are confidential and intended
solely for the use of the individual or entity to whom they are addressed. If
you have received this email in error please notify the Hayleys PLC system
manager. This message contains confidential information and is intended only for
the individual named. If you are not the named addressee you should not
disseminate, distribute or copy this e-mail. Please notify the sender
immediately by e-mail if you have received this e-mail by mistake and delete
this e-mail from your system. If you are not the intended recipient you are
notified that disclosing, copying, distributing or taking any action in reliance
on the contents of this information is strictly prohibited.
_______________________________________________
This is the MAPICS ERP System Discussion (MAPICS-L) mailing list
To post a message email: MAPICS-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: 
http://lists.midrange.com/mailman/listinfo/mapics-l
or email: MAPICS-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at 
http://archive.midrange.com/mapics-l.
Confidentiality and Disclaimer
* This email has been scanned by Hayleys PLC  Group IT Risk Management Services
*
This email and any files transmitted with it are confidential and intended
solely for the use of the individual or entity to whom they are addressed. If
you have received this email in error please notify the Hayleys PLC system
manager. This message contains confidential information and is intended only for
the individual named. If you are not the named addressee you should not
disseminate, distribute or copy this e-mail. Please notify the sender
immediately by e-mail if you have received this e-mail by mistake and delete
this e-mail from your system. If you are not the intended recipient you are
notified that disclosing, copying, distributing or taking any action in reliance
on the contents of this information is strictly prohibited.
_______________________________________________
This is the MAPICS ERP System Discussion (MAPICS-L) mailing list
To post a message email: MAPICS-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: 
http://lists.midrange.com/mailman/listinfo/mapics-l
or email: MAPICS-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at 
http://archive.midrange.com/mapics-l.
_______________________________________________
This is the MAPICS ERP System Discussion (MAPICS-L) mailing list
To post a message email: MAPICS-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: 
http://lists.midrange.com/mailman/listinfo/mapics-l
or email: MAPICS-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at 
http://archive.midrange.com/mapics-l.
Confidentiality and Disclaimer
* This email has been scanned by Hayleys PLC  Group IT Risk Management Services 
*
This email and any files transmitted with it are confidential and intended 
solely for the use of the individual or entity to whom they are addressed. If 
you have received this email in error please notify the Hayleys PLC system 
manager. This message contains confidential information and is intended only for 
the individual named. If you are not the named addressee you should not 
disseminate, distribute or copy this e-mail. Please notify the sender 
immediately by e-mail if you have received this e-mail by mistake and delete 
this e-mail from your system. If you are not the intended recipient you are 
notified that disclosing, copying, distributing or taking any action in reliance 
on the contents of this information is strictly prohibited.
_______________________________________________
This is the MAPICS ERP System Discussion (MAPICS-L) mailing list
To post a message email: MAPICS-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: 
http://lists.midrange.com/mailman/listinfo/mapics-l
or email: MAPICS-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at 
http://archive.midrange.com/mapics-l.
      
As an Amazon Associate we earn from qualifying purchases.