|
midrange.com
WAD. Working as Designed.
This is definetely an argument that I have had for many years and have lost
each time. I do see some of the logic not to move it by default, but never
is not the correct answer either. This is especially true in situations
where a user exit might not be available to move it.
The one that is even more frustruating:
I had COM add user fields into the offline load files (MBG8CPP & MBG9CPP)
since I had to write so many programs to back-fill user fields. They added
those fields, but the off-line load doesn't move them. In speaking to COM,
they said that they don't move user fields from one file to another: for
example, from on-line to shipment orders. I do understand that an order is
different from a shipment and that some people might be using them
differently, but an off-line order is an order and should be loaded.
Good luck.
Michael Franchino
Custom Systems Corporation
www.cussys.com
(973) 726-0202 X214 (Phone)
(973) 726-4552 (Fax)
|---------+---------------------------->
| | "Dave Shaw" |
| | <daveshaw@bellsou|
| | th.net> |
| | Sent by: |
| | mapics-l-admin@mi|
| | drange.com |
| | |
| | |
| | 06/21/2002 08:20 |
| | PM |
| | Please respond to|
| | mapics-l |
| | |
|---------+---------------------------->
>------------------------------------------------------------------------------------------------------------------------------|
|
|
| To: "MAPICS-L" <mapics-l@midrange.com>
|
| cc:
|
| Subject: Fw: User-defined fields in MAPICS
|
>------------------------------------------------------------------------------------------------------------------------------|
Forwarded for Dale:
----- Original Message -----
From: <DaleGindlesperger@fft-inc.com>
To: <mapics-l-admin@midrange.com>
Sent: Friday, June 21, 2002 10:54 AM
Subject: User-defined fields in MAPICS
> This is a general question/comment for the thread members.
>
> We use "user-defined fields" in the product structure files and other
> files to help support non-MAPICS functionality, such as union information
> requirements (labor standard type, etc). When orders are released, the
> user-defined fields don't go over from the master files to the order
files
> (ie., User Code A in PSTDTL doesn't go to MODATA). It seems odd to me
> that we are forced to write blaster programs to load the user fields to
> the "work" files from the "master" files and either have them as triggers
> or insert them into the CLs.
>
> Here's where it is a question as well as a comment. Have I been missing
> something in MAPICS that you can tell the system to copy the user fields
> over in order release and such? Or is this a "functioning as designed"?
> If so, does it seem odd to you good people on the thread that they don't
> go over?
>
> I was going to write this up as an enhancement request, but if I am the
> only person that wants user fields to copy from the "master" to the
"work"
> files, or if it will mess up other people's enhancements, I probably
won't
> bother.
>
> Any comments one way or the other are welcome....
>
> Dale @ Fleetwood
>
_______________________________________________
This is the MAPICS ERP System Discussion (MAPICS-L) mailing list
To post a message email: MAPICS-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/mapics-l
or email: MAPICS-L-request@midrange.com
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.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
