• Subject: RE: Default Reason Codes
  • From: "George Sagen" <gsagen@xxxxxxxxxxxxxxxxxxx>
  • Date: Sun, 18 Jul 1999 09:46:11 -0700
  • Importance: Normal

Here is some general info re default reason codes:
SYS180 is the program. The settings are stored in the ZOM table.
If you're on full client server one place the icon can be found within Accounts Receivable => Accounts Receivable Maintenance.
The settings you put in here determine the reason code to which each subsystem program that uses a reason codes will automatically default.
Each subsystem uses these settings differently. For A/P mode 0=Payment, 1=Invoice... You can look at the ones SSA provided in the priming database or refer to the "System Reference Manual".
A quirky thing to note regarding default reason codes for order entry: You put the order class in the mode field, however in the case of custom order classes, BPCS actually seems to look at the default reason code for the BASE order class (the order class upon which your custom order class is based). I've seen this in 6.0.02 and 6.04, but haven't tested it in 6.1.
George Sagen
BPCS Application Consultant
PrimeSource Technologies, L.L.C.
7373 East Doubletree Ranch Road
Suite 150
Scottsdale, AZ 85258
(801)360-6360 Direct & VM 
-----Original Message-----
From: uucp@Uucp1.mcs.net [mailto:uucp@Uucp1.mcs.net]On Behalf Of Mike Young
Sent: Saturday, July 17, 1999 5:19 PM
To: BPCS-L@midrange.com
Subject: Default Reason Codes

We are trying to remember how to create Default Reason Codes in BPCS. We are on Version 6.0.04 Mixed Mode. We need to add some additional information. The format of information to be entered is the PROGRAM NAME, DESCRIPTION, MODE,
MODE DESCRIPTION, AND G/L REASON CODE. Thanks in advance for your help
M. Young
ITW Shakeproof Assembly Components

This thread ...


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

This mailing list archive is Copyright 1997-2020 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].