|
SELECT C.SETID , C.CUST_ID , O.EFFDT , O.EFF_STATUS , C.SUBCUST_QUAL1 , C.SUBCUST_QUAL2 , O.PYMNT_TERMS_CD , O.PAYMENT_METHOD , O.DST_ID_AR , O.CR_ANALYST , O.COLLECTOR , ' ' AS SALES_PERSON , C.CUST_STATUS , C.BILL_TO_FLG , C.CUST_LEVEL , C.SUBCUST_USE , I.SUBCUST_USE_SW , C.CUR_RT_TYPE , C.IPAC_INTERFACE , C.FEDERAL_INDICATOR , O.DRAFT_TYPE , O.DRAFT_APPROVAL , O.DRAFT_DOC , O.DD_PROFILE_ID , C.EMPLID , C.ADDRESS_SEQ_NUM FROM %Table(CUSTOMER) C , %Table(CUST_OPTION) O , %Table(INSTALLATION_FS) I WHERE O.SETID = C.SETID AND O.CUST_ID = C.CUST_ID
|
| # |
PeopleSoft Field Name |
PeopleSoft Field Type |
Database Column Type |
Description |
| 1 |
 SETID |
Character(5) |
VARCHAR2(5) NOT NULL |
SetID
Prompt Table:
SP_SETID_NONVW
|
| 2 |
CUST_ID |
Character(15) |
VARCHAR2(15) NOT NULL |
Uniquely identifies an organizational entity that purchases goods or services from the enterprise. Represents the sold-to customer which is the customer organization that places orders. The CUST_ID may or may not be the same as the identifiers for the bill-to and ship-to locations.
Prompt Table:
CUSTOMER
|
| 3 |
EFFDT |
Date(10) |
DATE NOT NULL |
Effective Date
|
| 4 |
EFF_STATUS |
Character(1) |
VARCHAR2(1) NOT NULL |
Effective Status
A=Active
I=Inactive
|
| 5 |
SUBCUST_QUAL1 |
Character(15) |
VARCHAR2(15) NOT NULL |
Specifies a user-defined grouping of customer receivables activity. A subcustomer qualifier provides the ability to record and report receivables activity across multiple business units and/or multiple customers. For example a subcustomer qualifier could represent a sales region or a geographic area. There are two possible subcustomer qualifiers: SUBCUST_QUAL1 and SUBCUST_QUAL2.
|
| 6 |
SUBCUST_QUAL2 |
Character(15) |
VARCHAR2(15) NOT NULL |
Specifies a user-defined grouping of customer receivables activity. A subcustomer qualifier provides the ability to record and report receivables activity across multiple business units and/or multiple customers. For example a subcustomer qualifier could represent a sales region or a geographic area. There are two possible subcustomer qualifiers: SUBCUST_QUAL1 and SUBCUST_QUAL2.
|
| 7 |
PYMNT_TERMS_CD |
Character(5) |
VARCHAR2(5) NOT NULL |
Specifies how the payment due date and discount due date are calculated. A payment terms code is associated with various business units bill-to customers vendors as well as sales orders purchase orders and vouchers.
Prompt Table:
OM_TRMS_VW
|
| 8 |
PAYMENT_METHOD |
Character(3) |
VARCHAR2(3) NOT NULL |
Specifies the preferred method of payment by a customer. Examples of payment method are check direct debit and draft.
10/28/2003 edw 655070000 - Removed LTC and CSH xlats.
ACH=ACH
CC=Credit Card
CHK=Check
CSH=Cash
DD=Direct Debit
DR=Draft
EC=Electronic Check
EFT=Electronic Fund Transfer
GE=Giro - EFT
PL=PayPal
WIR=Wire Report
|
| 9 |
DST_ID_AR |
Character(10) |
VARCHAR2(10) NOT NULL |
Specifies the general ledger ChartField combination that is affected when subsequent activity such as a payment occurs for the item.
Prompt Table:
DST_CODE_AR_VW
|
| 10 |
CR_ANALYST |
Character(8) |
VARCHAR2(8) NOT NULL |
Specifies the personnel code for the person who works with a customer to establish credit limits and payment terms. This field is required for a bill-to customer.
Prompt Table:
CR_ANALYST_VW
|
| 11 |
COLLECTOR |
Character(8) |
VARCHAR2(8) NOT NULL |
Specifies the personnel code for the person who works with a customer to collect overdue payments.
Prompt Table:
COLLECTOR_VW
|
| 12 |
SALES_PERSON |
Character(8) |
VARCHAR2(8) NOT NULL |
Specifies the personnel code for the person who works with a customer as a sales representative. This field is required for a customer that functions as a bill-to customer.
|
| 13 |
CUST_STATUS |
Character(1) |
VARCHAR2(1) NOT NULL |
Customer Status
A=Active
I=Inactive
T=Template
|
| 14 |
BILL_TO_FLG |
Character(1) |
VARCHAR2(1) NOT NULL |
Bill To Customer
N=No
Y=Yes
|
| 15 |
CUST_LEVEL |
Character(1) |
VARCHAR2(1) NOT NULL |
Customer Level
N=New
P=Prospect
R=Regular
S=Short-Term
T=Temporary
|
| 16 |
SUBCUST_USE |
Character(1) |
VARCHAR2(1) NOT NULL |
SubCustomer
|
| 17 |
SUBCUST_USE_SW |
Character(1) |
VARCHAR2(1) NOT NULL |
SubCustomer Usage
1=Use First SubCustomer Field
B=Use Both SubCustomer Fields
N=Do Not Use SubCustomer Fields
|
| 18 |
CUR_RT_TYPE |
Character(5) |
VARCHAR2(5) NOT NULL |
Currency Rate Type
|
| 19 |
IPAC_INTERFACE |
Character(1) |
VARCHAR2(1) NOT NULL |
IPAC Interface
|
| 20 |
FEDERAL_INDICATOR |
Character(1) |
VARCHAR2(1) NOT NULL |
Federal Vendor Information
|
| 21 |
DRAFT_TYPE |
Character(10) |
VARCHAR2(10) NOT NULL |
A flag that indicates whether a draft is initiated by the vendor (1) or by the customer (2).
|
| 22 |
DRAFT_APPROVAL |
Character(1) |
VARCHAR2(1) NOT NULL |
"Indicates whether or not a draft is pre-approved for payment by a bill-to customer. If the draft is pre-approved then it can be submitted to the customer's bank without the customer's sign-off. Otherwise the draft must be reviewed and approved by the customer before the enterprise can submit it to the bank for payment. This field is used only if the preferred payment method is ""Draft""."
P=Preapproved
R=Approval Required
|
| 23 |
DRAFT_DOC |
Character(1) |
VARCHAR2(1) NOT NULL |
"A flag that indicates whether or not (C or N) a draft document should be created for a Receivables item when the payment method is ""draft"". If the value is N then the system prints only a draft statement. If the value is C then the system creates a draft document. "
C=Create Document
N=Do Not Create Document
|
| 24 |
DD_PROFILE_ID |
Character(5) |
VARCHAR2(5) NOT NULL |
Specifies the Profile ID for a Direct Debit
|
| 25 |
EMPLID |
Character(11) |
VARCHAR2(11) NOT NULL |
Employee ID
|
| 26 |
ADDRESS_SEQ_NUM |
Number(5,0) |
INTEGER NOT NULL |
Address Sequence Number
|