|
Harry, The Heirarchcy option (36/ARU) does three main functions. 1. Sets the hrriearchy parameters and files 2. Converts all AR transactions for the children (original account and customer account) 3. Rebuilds the AR balance. The parent child relationship exists on another file besides SLP04, and also impacts on the transaction master file (SLP15/20) Having survived a conversion of a customer master and transactions file from another system which included setting up of hierachies, I would not recommend you do it manually. As for breaking the function into components it would be possible and would require a (thoroughly tested) mod to read back in the paramters, convert the data and rebuild. Give me a call to discuss. Michael Harry Young <hyoung@alsafe.com.au> on 18/08/2000 05:42:00 PM Please respond to JBAUSERS-L@midrange.com To: JBAUSERS-L@midrange.com cc: (bcc: Michael Berman/JBA International/AU) Subject AR Hierarchies : We have several thousand customers and come from a business 400 version 2 to version 3.5.1 ish. We ae experiencing difficulties with allocating receipts in AR. It appears that the hierarchies relationships are not properly defined (i.e. SLP04 has no records). Option 36 of the AR utility (Maintain customer hierarchies) solves the problem of retrospectively establishing a relationship with historical data in mind. The problem is this takes minutes per relationship and we have 70 pages of parent/child relationships to set-up. Conceptionally we would like to split this utility into two parts 1 to enter the relationship and 2 to rebuild. Has anyone experienced something similar or can comment on a possible SQL load of SLP04 then an AR rebuild. Thanks in anticipation Harry Young I.T. Manager Alsafe Safety Industries Pty Ltd Phone: 61 3 9556 1234 Fax: 61 3 9555 4691 e-mail: hyoung@alsafe.com.au This transmission or any part of it is intended for the addressee. It is confidential and may contain legally privileged information. The copying or distribution by any person other than the named addressee is prohibited. If you have received this transmission in error please call us or return by e-mail to sender. +--- | This is the JBA Software Users Mailing List! | To submit a new message send your mail to JBAUSERS-L@midrange.com. | To subscribe to this list send email to JBAUSERS-L-SUB@midrange.com. | To unsubscribe from this list send email to JBAUSERS-L-UNSUB@midrange.com. | Questions should be directed to the list owner: doug333@aol.com. +--- +--- | This is the JBA Software Users Mailing List! | To submit a new message send your mail to JBAUSERS-L@midrange.com. | To subscribe to this list send email to JBAUSERS-L-SUB@midrange.com. | To unsubscribe from this list send email to JBAUSERS-L-UNSUB@midrange.com. | Questions should be directed to the list owner: doug333@aol.com. +---
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.