Re: LTPUR not recalculated after changing ITEMBL with SQL

Kevin Fox <[email protected]>
Newsgroups gmane.comp.systems.as400.mapics
Message-ID <26010664.1328555913720.JavaMail.root@mswamui-cedar.atl.sa.earthlink.net>
Bryan

While you can update XA database using SQL, it is not recommended for several reasons.  One of which you just discovered.  Whenever you update XA database directly, you run the risk of failing to edit the data correctly.  For example, all number fields do not have the same number of digits.  Date fields are in a unique, non-ISO format.  This list is long.

If you are going to create programs to write directly to the database, you must understand the logic and edit requirements before doing so.  Trial and error method will most likely result in corruption.  Test everything, all variables in a test environment.  However, not understanding XA logic can lead you to false test rests.  For example, if the lead time fields are not updated correctly, what are the effects on receiving, MRP or month end close?  Unless you know, it is a wild risk.

R5.5 is circa 1998.  The current versions since 2006 have incorporated web services that allow you to update the database and incorporate all the logic and edits required  The current version also allows you to update using XML forms.

To answer your specific question.  The database does not contain triggers to recalculated lead times.  This is in the logic programs from the screen entry.  For your version (R5.5) you should always update with the data entry screens, or the offline load processes that are built into R5.5 for this purpose.

Thanks

Kevin Fox




-----Original Message-----
>From: Bryan Burns <[email protected]>
>Sent: Feb 6, 2012 6:02 AM
>To: mapics-l-Zwy7GipZuJhWk0Htik3J/[email protected]
>Subject: [MAPICS-L] LTPUR not recalculated after changing ITEMBL with SQL
>
>In an XA5.5 test environment, I updated LTVEN and LTSAF using SQL; but
>LTPUR has not been re-calculated for those items I updated.
>
>I went into ITEMBL file maintenace on a record and I was able to get it
>re-calculated that way.


>
>Two questions:
>
>1. This was my first accomplishment using SQL to do an update and I'd like
>to know if I did any damage, and what other file/fields can be damaged with
>even the most careful use of SQL?
>
>2. How can I automagically get the LTPUR recalculated for about 130 records?
>_______________________________________________
>This is the MAPICS ERP System Discussion (MAPICS-L) mailing list
>To post a message email: MAPICS-L-Zwy7GipZuJhWk0Htik3J/[email protected]
>To subscribe, unsubscribe, or change list options,
>visit: http://lists.midrange.com/mailman/listinfo/mapics-l
>or email: MAPICS-L-request-Zwy7GipZuJhWk0Htik3J/[email protected]
>Before posting, please take a moment to review the archives
>at http://archive.midrange.com/mapics-l.
>


Kevin Fox
(909) 762-1384 mobile
_______________________________________________
This is the MAPICS ERP System Discussion (MAPICS-L) mailing list
To post a message email: MAPICS-L-Zwy7GipZuJhWk0Htik3J/[email protected]
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/mapics-l
or email: MAPICS-L-request-Zwy7GipZuJhWk0Htik3J/[email protected]
Before posting, please take a moment to review the archives
at http://archive.midrange.com/mapics-l.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.