Re: Shipped Qty Problem

It could be as simple as the user thinking that they have to key the right 3
decimals (forgetting to key in the decimal point).   You also may want to
look at the MAPICS UE/API that does not allow overshipments.  This would not
be useful if you company allows overshipments on some orders, however...

Eric

----- Original Message -----
From: "Nandagopal Padmanabhan" <npadmanabhan@xxxxxxxxxxxxxx>
To: "MAPICS ERP System Discussion" <mapics-l@xxxxxxxxxxxx>
Sent: Tuesday, June 01, 2004 10:06 AM
Subject: RE: Shipped Qty Problem


> We have had that problem too. But these transactions came in via an
> offline load. We have an external application for creating service
> orders and these are brought into MAPICS as customer orders. So
> basically, it is an automated processes and this is the first time we
> are having this problem.
>
> -----Original Message-----
> From: Trudie Cook [mailto:trudie.cook@xxxxxxxxxxxxxxx]
> Sent: Tuesday, June 01, 2004 10:02 AM
> To: MAPICS ERP System Discussion
> Subject: RE: Shipped Qty Problem
>
> Was it a possible a keying error?   That someone did not use the field
> exit key?  We have had the problem that sometimes someone tabs out of
> the field instead of using the right adjust.
>
> -----Original Message-----
> From: mapics-l-bounces@xxxxxxxxxxxx
> [mailto:mapics-l-bounces@xxxxxxxxxxxx]On Behalf Of Nandagopal
> Padmanabhan
> Sent: Tuesday, June 01, 2004 12:55 PM
> To: mapics-l@xxxxxxxxxxxx
> Subject: Shipped Qty Problem
>
>
> Hello All,
>
> We had some SA transactions (customer orders) go through MAPICS where
> there was a discrepancy between the original order quantity and the
> shipped quantity. Basically, the shipped quantity was multiplied by a
> factor of 1000 i.e. if the original qty was 2, the shipped qty was 2000.
> This problem has caused a major misstatement in our month-to-date
> financials to the tune of tens of millions of dollars.
>
>
>
> Fixing this problem is one thing and figuring out why this happened is
> another thing. We may do journal entries to correct the situation, but
> any thoughts on why this problem may have occurred. We use XA6. Look
> forward to responses.
>
>
>
> Thanks,
>
> Nandu
>
>
>
>
>
>
>
> _______________________________________________
> 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.
>
>
> _______________________________________________
> 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.
>
>