× 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.



If I remember correctly.
To backtrack the journal source(AP,AR,...)to the BPCS program you can do the
following steps.

1) In the CEA Models file GHM you find the journal source(HMJNSC). You find
the associated model in field HMJNMD and a description in field HMLDES.

2) This model is linked with an event. You can find this in GTD(Event
definition). TDJNMD=model TDTRMD=event

3) Knowing the event, you can determine the reasoncode with the help of the
subsystem event determination table(GED). EDEVNT =event EDREAS=reason code

4) With the reason code, you can find the default reason code for a BPCS
program in the ZOM file. (or SYS180)

I hope this helps you a little bit further.


Met vriendelijke groeten,
With best regards,


Patrick Rigole
SOLAR-IT

Tel. +32(0)3 544 49 78
Fax. +32(0)3 544 49 71
Mail: P.Rigole@Solar-it.com
Helpdesk: Help@Solar-it.com


CONFIDENTIAL
The contents of this email and any attachments may be confidential. It is
intended for the named recipient(s) only. If you are not the named
recipient, please notify the sender immediately and do not disclose the
contents to any other person or make any copies.
---------------------
Message: 3
From: Dennis Munro <DMunro@badgerminingcorp.com>
To: "BPCS-L Mailing List (E-mail)" <BPCS-L@midrange.com>
Subject: GLH Journal Entry Codes
Date: Fri, 5 Apr 2002 11:42:54 -0600
Reply-To: bpcs-l@midrange.com

Ver. 6.0.02 plf, Mar'98n cume, full client/server

Trying to come up with a VARPG inquiry program using data in the GLH file &
I seem to be running into a mental road block. Preparing for a sales tax
audit & trying to use the VIxxx & VRxxx record types to list the dollars &
account numbers recorded for a given invoice number.  The A/P accrual
account is eliminated from the inquiry but I seem to be getting invalid
data.  I've created two new logical views over the GLH to help but still I
seem to be missing something.  That is why I'm wondering about codes listed
below that to see what I might be missing.  Some of the results from the
Inquiry program are right on & some are way out in left field.  It's down to
displaying all the data records & figuring out what I'm
missing/misunderstanding.  I also am wondering if it might be a "data entry'
problem, i.e. not entering the complete invoice & receiver info?

The following are the various 2 character codes that start the contents of
the Journal Entry/LHJNEN column in our version of the GLH file:

AC
AL
AP  =  Accounts Payable
AR  =  Accounts Receivable
BL
IN  =  Inventory
MJ  =  Manual Journal Entry
MR
RV
VI  =  Vendor Invoice
VR  =  Vendor Receipt

Some are guessable but some I don't have a clue.  Could you fill in what I
have missed or incorrectly guessed at?

Thanks - Dennis.

Dennis Munro

"I love deadlines.  I especially like the whooshing sound they make as they
go flying by."  Dilbert's Words Of Wisdom:

Badger Mining Corporation
www.badgerminingcorp.com
dmunro@badgerminingcorp.com
(920) 361-2388



--__--__--

_______________________________________________
This is the SSA's BPCS ERP System (BPCS-L) digest list
To post a message email: BPCS-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/bpcs-l
or email: BPCS-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/bpcs-l.



End of BPCS-L Digest



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.