× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: RE: Standard Interface to Invoice Log
  • From: Ram Hari <ramhari@xxxxxxxxxxxxxxx>
  • Date: Tue, 10 Oct 2000 10:02:46 -0400

We have the same problem here, If I try to populate the log indicator then I
get an error report.
On investigating the program, there is no code in the program to populate
the Invoice dissections file PLP17. We are right now in the process of
changing the program to populate the dissections file and also remove the
code that validates the log indicator, but we are still in the early stages
of programming.
I do not know what other hurdles we might face, any input is highly
appreciated.
We are on V351. I have the same V2.1 documentation and it is true in V351, I
do not know about the later versions, if it is changed please let me know
Thanks

Ram S. Hari
Sr. Programmer/Analyst
ramhari@wasserstrom.com <mailto:ramhari@wasserstrom.com> 
Voice 614.228.6525 Ext. 8392
Fax    253.484.5806


                -----Original Message-----
                From:   DAhKow@ibl.intnet.mu [mailto:DAhKow@ibl.intnet.mu]
                Sent:   Tuesday, October 10, 2000 2:26 AM
                To:     JBAUSERS-L@midrange.com
                Subject:        Standard Interface to Invoice Log


                We are required to do some automatic posting of transactions
into the
                Accounts Payable Invoice log. To do this we are considering
using the
                Standard Interface To Accounts payable i.e write to
transaction work files
                PLPI0 & PLPI1 and then calling  program PLPI00CLP as
explained in the
                technical documentation. However that documentation mentions
that the Log
                Indicator field and the Location code field (used for
invoice log
                transactions) should be left blank as these fields are not
used at
                'present' time. Since the documentation we have dates back
to 1995 and
                relates to version 2.1, and we are currently running version
3.5.2b Service
                Pack 3, we are wondering if this note is still pertinent. Or
has someone
                tried doing something similar  and could indicate us how we
can achieve
                this?

                Regards

                +---
                | 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 thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.