Populating the INTFC_BI Table
This topic provides an overview of the INTFC_BI table and discusses how to populate the INTFC_BI table.
The following four attributes comprise the key to the Billing Interface table (INTFC_BI):
Term |
Definition |
|---|---|
INTFC_ID (interface ID) |
Represents a batch of billing activity, that is, a collection of billing activity that may be produced by a billing source system. Some systems may generate a batch each night. Other systems may produce a batch for a certain kind of billing activity. When assigning a new INTFC_ID for a batch of data, the Last BI Interface ID field (INSTALLATION_BI.LAST_INTFC_ID) on the Installation Options – Billing General page can be used to ensure that a unique number is assigned. The source system can increase this number by one and use that number for the new batch of data. |
INTFC_LINE_NUM (interface line number) |
Represents a bill line charge. For each interface ID (batch of billing activity), there may be multiple interface line numbers, one for each bill line charge in the group. |
TRANS_TYPE_BI (transaction type billing) |
Transaction type. Characterizes the type of data being stored. Options are LINE, NOTE, and AHDR:
|
TRANS_TYPE_BI_SEQ (transaction type billing sequence) |
Transaction type sequence. Part of the key used to provide uniqueness in the event that there are multiple notes or comments for a bill line charge. For a LINE transaction, set this attribute to 0 (zero). |
Populate the INTFC_BI table for LINE, NOTE, and AHDR transactions only. For each bill line charge added as a bill line to the bill data structure, the Billing Interface table contains one row of data with a transaction type of LINE. For each bill line charge row with a transaction type of LINE, the Billing Interface table can contain one or more notes or comments (NOTES).
Note: To ensure VAT data integrity, you must run the VAT Defaulting process after the Billing Interface process when importing bills with VAT data.
The following table demonstrates how to populate the INTFC_BI fields for LINE transactions:
|
Field Number |
Field Name |
Required for LINE Transaction? |
Remarks |
|---|---|---|---|
|
1 |
INTFC_ID (interface ID) |
Required. |
Used to group or batch a collection of Billing interface activity. |
|
2 |
INTFC_LINE_NUM (interface line number) |
Required. |
Each unique interface line number for an interface ID represents a separate bill line charge. |
|
3 |
TRANS_TYPE_BI (transaction type) |
Required. |
Value must be LINE. |
|
4 |
TRANS_TYPE_BI_SEQ (transaction type sequence) |
Required. |
Initialize to zero for LINE transaction type. |
|
5 |
HDR_FIELDS_KEY |
Populate whenever a record is inserted into the INTFC_BI_HDR table. |
Populate whenever a record is inserted into the INTFC_BI_HDR table. |
|
6 |
HDR_FIELDS_BILL_BY |
Leave blank. |
Leave blank. |
|
7 |
ADJ_TRANS_TYPE (adjustment transaction type) |
Required if the line is part of an adjustment. |
Must be RBALL if line is a delta line for a Rebill Entire Bill. Select CRLIN for Credit Line, RBLIN for Rebill Line, and NTLIN for Net Line. |
|
8 |
CREATE_NEW_BILL |
Optional. |
N is the default value. |
|
9 |
TMP_BILL_FLG (temporary bill flag) |
Optional. |
N is the default value. Bills with this set to Y are created in TMR status. |
|
10 |
ENTRY_TYPE |
Optional. |
Optional. |
|
11 |
ENTRY_REASON |
Optional. |
Optional. |
|
12 |
ENTRY_EVENT |
Conditional |
If provided, it must be valid and included in the bill-by definition. If not provided, the Billing Interface process obtains a default value from the setup tables, based on the PeopleSoft Billing default hierarchy. |
|
13 |
LOAD_STATUS_BI |
Optional. |
May initialize to NEW or leave blank. |
|
14 |
ERROR_STATUS_BI |
Leave blank. |
Leave blank. |
|
15 |
BUSINESS_UNIT (billing business unit) |
Required. |
Must be a valid billing business unit. Required for determining India GST using Billing Interface. |
|
16 |
BUSINESS_UNIT_GL |
Leave blank. |
Leave blank. |
|
17 |
BILL_TO_CUST_ ID (bill-to customer) |
Required. |
Must be a valid bill-to customer. Required for determining India GST using Billing Interface. |
|
18 |
ADDRESS_SEQ_NUM (address sequence number) |
Required for India tax transactions populated by PeopleSoft Order Management. |
If provided, it must be valid and included in the bill-by definition. If not provided, the Billing Interface process obtains a default value from the setup tables, based on the PeopleSoft Billing default hierarchy. Required for determining India GST using Billing Interface. |
|
19 |
BILL_TO_COPIES |
Leave blank. |
Leave blank. |
|
20 |
CNTCT_SEQ_NUM (contact sequence number) |
Conditional. |
If provided, it must be valid and included in the bill-by definition. If not provided, the Billing Interface process obtains a default value from the setup tables, based on the PeopleSoft Billing default hierarchy. |
|
21 |
NAME1 (customer name) |
Leave blank. |
Leave blank. |
|
22 |
INTERUNIT_FLG |
Leave blank. |
Leave blank. |
|
23 |
BUSINESS_UNIT_TO |
Required if an InterUnit flag is active and the customer default does not provide a value. |
If not populated and if the customer is an InterUnit customer, the system uses the BUSINESS_UNIT_GL value from the CUST_OPTION table, based on the customer ID. If the system cannot obtain this value, it marks the transaction in error. |
|
24 |
DIRECT_INVOICING |
Optional. |
Bills set to Y are created in RDY bill status. If provided, it must be valid and included in the bill-by definition. If not provided, defaults to N. |
|
25 |
RANGE_SELECTION_ID |
Optional. |
Used in range selection options and with direct invoicing. |
|
26 |
BILL_SOURCE_ID |
Required only if invoice numbering by bill source. |
Must be a valid bill source if provided. |
|
27 |
BILL_TYPE_ID |
Required. |
Must be a valid bill type. |
|
28 |
BILL_CYCLE_ID |
Optional. |
If provided, it must be valid and included in the bill-by definition. If not provided, the Billing Interface process obtains a default value from the setup tables, based on the PeopleSoft Billing default hierarchy. |
|
29 |
BILL_BY_ID (bill-by identifier) |
Optional. |
Must be valid if provided. Defaults if left blank. |
|
30 |
PAYMENT_METHOD (payment method) |
Optional. |
If provided, it must be valid and included in the bill-by definition. If not provided, the Billing Interface process obtains a default value from the setup tables, based on the PeopleSoft Billing default hierarchy. |
|
31 |
PYMNT_TERMS_CD (payment terms code) |
Optional. |
If provided, it must be valid and included in the bill-by definition. If not provided, the Billing Interface process obtains a default value from the setup tables, based on the PeopleSoft Billing default hierarchy. |
|
32 |
BANK_CD (bank code) |
Optional. |
If provided, it must be valid and included in the bill-by definition. If not provided, the Billing Interface process obtains a default value from the setup tables, based on the PeopleSoft Billing default hierarchy. |
|
33 |
BANK_ACCT_KEY |
Optional. |
If provided, it must be valid and included in the bill-by definition. If not provided, the Billing Interface process obtains a default value from the setup tables, based on the PeopleSoft Billing default hierarchy. |
|
34 |
BI_CURRENCY_CD (billing transaction currency) |
Required. |
It must be a valid currency Required for determining India GST using Billing Interface. |
|
35 |
BASE_CURRENCY |
Leave blank. |
Leave blank. |
|
36 |
CUR_RT_TYPE (currency rate type) |
Optional. |
Must be valid if provided. Defaults if left blank. |
|
37 |
RATE_MULT (rate multiplier) |
Required if CUR_RT_SOURCE is U (user defined). |
If provided, it must be valid and included in the bill-by definition. If not provided, the Billing Interface process sets it to 0 (zero) |
|
38 |
RATE_DIV (rate divisor) |
Required if CUR_RT_SOURCE is U (user defined). |
If provided, it must be valid and included in the bill-by definition. If not provided, the Billing Interface process sets it to 1. |
|
39 |
CUR_RT_SOURCE (currency rate source) |
Optional. |
Defaults to T (from tables) if blank. If provided, it must be valid and included in the bill-by definition. If not provided, the Billing Interface process obtains a default value from the setup tables, based on the PeopleSoft Billing default hierarchy. |
|
40 |
INVOICE_DT (invoice date) |
Optional. |
Optional. Required for determining India GST using Billing Interface. |
|
41 |
ACCOUNTING_DT (accounting date) |
Optional. |
Optional. |
|
42 |
ACCRUE_UNBILLED |
Leave blank. |
Leave blank. |
|
43 |
TARGET_INVOICE |
Optional. |
If passed, target invoice becomes the invoice number. Note: Non-Contracts or Project Costing invoices should not be used as the target for Contracts or Project Costing lines. |
|
44 |
INVOICE |
Leave blank. |
Use the TARGET_INVOICE field to specify an invoice number. |
|
45 |
DOC_TYPE (document type) |
Optional. |
Optional. |
|
46 |
CONSOL_SETID (consolidation customer SetID) |
Populate if generating consolidated bill headers across bill-to customers through the Billing interface. |
If provided, it must be valid and included in the bill-by definition. If not provided, the Billing Interface process obtains a default value from the setup tables, based on the PeopleSoft Billing default hierarchy. |
|
47 |
CONSOL_CUST_ID (consolidation customer ID) |
Populate if generating consolidated bill headers across bill-to customers through the Billing interface. |
If provided, it must be valid and included in the bill-by definition. If not provided, the Billing Interface process obtains a default value from the setup tables, based on the PeopleSoft Billing default hierarchy. |
|
48 |
CONSOL_KEY (consolidation key) |
Populate if generating consolidated bill headers through the Billing interface. |
If provided, it must be valid and included in the bill-by definition. If not provided, the Billing Interface process obtains a default value from the setup tables, based on the PeopleSoft Billing default hierarchy. |
|
49 |
INVOICE_TO_ADJ |
Required for ADJ_TRANS_TYPES of CRLIN, RBLIN, NTLIN, and RBALL. |
Must be a valid invoice. |
|
50 |
ADJ_DELTA_ACTION |
Required for ADJ_TRANS_TYPES of RBALL. |
Must be ADD for new lines, RPL for lines to be replaced, and DEL for lines to be deleted. |
|
51 |
LINE_SEQ_TO_ADJ |
Required for ADJ_TRANS_TYPES of CRLIN, RBLIN, and NTLIN. Also required for RBALL except when ADJ_DELTA_ACTION is DEL. |
Must be a valid line sequence. |
|
52 |
LINE_SEQ_NUM |
Leave blank. |
Leave blank. |
|
53 |
LINE_DST_SEQ_NUM |
Leave blank. |
Leave blank. |
|
54 |
LINE_DFR_SEQ_NUM |
Leave blank. |
Leave blank. |
|
55 |
LINE__SEQ_NUM |
Leave blank. |
Leave blank. |
|
56 |
LAST_NOTE_SEQ_NUM |
Leave blank. |
Leave blank. |
|
57 |
NOTES_SEQ_NUM |
Leave blank. |
Leave blank. |
|
58 |
LINE_TYPE |
Required. |
Must be a valid translate value. |
|
59 |
IDENTIFIER (bill charge identifier) |
Optional. |
Required for determining India GST using Billing Interface. |
|
60 |
DESCR (bill charge description) |
Optional. |
For lines from PeopleSoft feeder systems, use the base language description. Required for determining India GST using Billing Interface. |
|
61 |
UNIT_OF_MEASURE |
Optional. |
Must be valid if provided. |
|
62 |
QTY (quantity) |
Required. |
Line charge quantity. |
|
63 |
ORIG_QTY (original quantity) |
Optional. |
Used only with PeopleSoft Project Costing integration. |
|
64 |
UNIT_AMT (unit amount) |
Required. |
|
|
65 |
LIST_PRICE |
Optional. |
Optional. |
|
66 |
PPRC_PROMO_CD (promotion code) |
Optional. |
Optional. |
|
67 |
MERCH_TYPE (merchant type) |
Optional. |
Optional. |
|
68 |
TAX_CD (tax code) |
Must be valid if provided. |
If not populated and ship-to customer exists, the system defaults the tax code from the ship-to customer address for non third-party supplier tax transactions. |
|
69 |
TAX_EXEMPT_CERT (tax exempt certificate) |
Optional. |
Optional. |
|
70 |
TAX_EXEMPT_FLG (tax exempt flag) |
Optional. |
If not provided, the system uses N (no) as the default value. |
|
71 |
TAX_EXEMPT_RC (tax exempt reason code) |
Optional. |
Used only with Taxware tax option. |
|
72 |
TAX_JOB_NUM (tax job number) |
Optional. |
Used only with Taxware tax option. |
|
73 |
BI_TAX_TIMING |
Optional. |
Optional. |
|
74 |
CUSTOMER_GROUP |
Optional. |
Used with Vertex tax option. |
|
75 |
VAT_TXN_TYPE_CD (value-added tax transaction type code) |
Optional. |
Applies to VAT transactions only. If not provided, the system populates with a default value through the VAT Defaulting process. |
|
76 |
TAX_CD_VAT (tax code value-added tax) |
Conditional. |
Applies to VAT transactions only. If not provided, the system populates with a default value through the VAT Defaulting process. Must be populated if VAT applicability is provided and equals T (taxable), X (exonerated), or S (suspended). Must be blank if VAT applicability is provided and equals E (exempt) or O (outside of scope). |
|
77 |
VAT_APPLICABILITY |
Optional. |
Applies to VAT transactions only. If not provided, the system populates with a default value through the VAT Defaulting process. |
|
78 |
VAT_PRODUCT_GROUP |
Optional if IDENTIFIER_TBL = SVC, LAB, ITM, ID, G, PRD, or PDA. Otherwise, leave blank. |
Applies to VAT transactions only. |
|
79 |
PROD_GRP_SETID (product group SetID) |
Optional. |
Identifies the SetID to use with the VAT_PRODUCT_GROUP. If left blank when VAT_PRODUCT_GROUP is provided, defaults from the most relevant business unit. Applies to VAT transactions only. |
|
80 |
IST_TXN_FLG (intrastat transaction flag) |
Leave blank. |
Applies to VAT transactions only. |
|
81 |
IDENTIFIER_TBL (identifier table) |
Required if IDENTIFIER is populated. Values are ID, D, S, PRD, PDA, CON, ITM, PRM, A, LAB, SVC, G. |
The value entered in the IDENTIFIER and IDENTIFIER_TBL fields must be a valid combination. If the IDENTIFIER field is populated, and the IDENTIFIER_TBL field is not populated, the system uses G as the default value in the IDENTIFIER_TBL field. |
|
82 |
SHIP_FROM_LOC (ship-from location) |
Optional. |
Must be a valid location if provided. Used in conjunction with Taxware or Vertex tax options. Note: For third-party tax transactions with no ship-to address override, you must populate either the SHIP_FROM_LOC field or the ORD_ACCEPT_LOC field for the system to insert a row into the BI_LINE_TAX table. Required for determining India GST using Billing Interface. |
|
83 |
ORD_ACCEPT_LOC (order acceptance location) |
Optional. |
Must be a valid location if provided. Used in conjunction with Taxware or Vertex tax options. If not provided, the system retrieves as a default value the order acceptance location from the Billing business unit definition. Note: For third-party tax transactions with no ship-to address override, you must populate either the SHIP_FROM_LOC field or the ORD_ACCEPT_LOC field for the system to insert a row into the BI_LINE_TAX table. |
|
84 |
ORD_ORIGIN_LOC (order origin location) |
Optional. |
Must be a valid location if provided. Used in conjunction with Taxware tax options. If not provided, the system retrieves as a default value the order origin location from the Billing business unit definition. |
|
85 |
STORE_LOC (store location) |
Optional. |
Must be a valid location if provided. Used in conjunction with Taxware or Vertex tax options. |
|
86 |
TITLE_PASSAGE |
Optional. |
Must be valid if provided. Used in conjunction with Taxware tax options. |
|
87 |
TAX_GROUP |
Optional. |
Used in conjunction with Taxware or Vertex tax options. |
|
88 |
TAX_USER_AREA |
Optional. |
Used in conjunction with Vertex tax options. |
|
89 |
TAX_TRANS_TYPE (transaction type) |
Optional. |
Used in conjunction with Taxware or Vertex tax options. |
|
90 |
TAX_TRANS_SUB_TYPE (transaction subtype) |
Optional. |
Used in conjunction with Vertex tax options. |
|
91 |
NET_EXTENDED_AMT (net extended amount) |
Leave blank. |
Calculated by interface process, depending on gross extended amount, discounts, and surcharges. |
|
92 |
GROSS_EXTENDED_AMT (gross extended amount) |
Required. |
Net extended amount, discounts, and surcharges are calculated based on this amount. |
|
93 |
REV_RECOG_BASIS |
Required for contract liability recognition. |
Defaults from Bill Type definition for contract liability transactions. Values are defined by translate table. If set to a value other than blank or INV, indicates whether the line can have deferred accounting entries created. |
|
94 |
PROJECT_ID |
Optional. |
You may assign a project reference value here. This value is not automatically associated with the PROJECT_ID. This is not used as a ChartField. |
|
95 |
BUSINESS_UNIT_OM (PeopleSoft Order Management business unit) |
Required if PRODUCT_ID is populated or when India tax transactions are populated by PeopleSoft Order Management. |
Identifies Order Management business unit. |
|
96 |
ORDER_NO (order number) |
Optional. |
Optional. |
|
97 |
ORDER_INT_LINE_NO (order line number) |
Optional. |
Optional. |
|
98 |
SCHED_LINE_NBR (schedule line number) |
Optional. |
Optional. |
|
99 |
DEMAND_SOURCE |
Optional. |
Optional. |
|
100 |
DEMAND_LINE_NO (demand line number) |
Optional. |
Optional. |
|
101 |
BUSINESS_UNIT_RMA (PeopleSoft Order Management business unit for RMA) |
Optional. |
Optional. |
|
102 |
RMA_ID (RMA identifier) |
Optional. |
Optional. |
|
103 |
RMA_LINE_NBR (RMA line number) |
Optional. |
Optional. |
|
104 |
PRODUCT_ID (product identifier) |
Required when PeopleSoft applications populate the IDENITIFIER_TBL with PRD or PDA. |
Required for determining India GST using Billing Interface. |
|
105 |
ORDER_DATE |
Conditional. |
Required for contract liability if recognition basis is ORD (order date). |
|
106 |
PO_REF (purchase order number) |
Optional. |
Optional. |
|
107 |
PO_LINE (purchase order line) |
Optional. |
Optional. |
|
108 |
CONTRACT_NUM (contract number) |
Optional. |
Optional. |
|
109 |
CONTRACT_DT |
Conditional. |
Required for contract liability if recognition basis is CON (contact date). |
|
110 |
CONTRACT_TYPE |
Optional. |
Optional. |
|
111 |
CONTRACT_LINE_NUM (contract line number) |
Optional. |
Optional. |
|
112 |
FREIGHT_TERMS |
Optional. |
Optional. |
|
113 |
BILL_OF_LADING |
Optional. |
Optional. |
|
114 |
COUNTRY_SHIP_FROM |
Required for India tax transactions populated by PeopleSoft Order Management. |
If not provided, the system obtains a default value from the ship-from business unit, then from the billing business unit location for VAT transactions. Required for determining India GST using Billing Interface. |
|
115 |
COUNTRY_SHIP_TO |
Optional. |
If not provided, the system obtains a default value from the ship-to customer location for VAT transactions. Required for determining India GST using Billing Interface. |
|
116 |
SHIP_TO_CUST_ID (ship-to customer) |
Required when third-party tax software is associated with a billing business unit, and for India tax transactions populated by PeopleSoft Order Management. |
For VAT transactions, if you do not provide a value, the Billing Interface process attempts to provide a default value in this manner:
Required for determining India GST using Billing Interface. |
|
117 |
SHIP_TO_ADDR_NUM (ship-to address) |
Required when third-party tax software is associated with a billing business unit and for India tax transactions populated by PeopleSoft Order Management. |
For VAT transactions, if you do not provide a value, the Billing Interface process attempts to provide a default value in this manner:
Required for determining India GST using Billing Interface. |
|
118 |
SHIP_ID (shipment ID) |
Optional. |
Optional. |
|
119 |
SHIP_TYPE_ID (shipment type) |
Optional. |
Optional. |
|
120 |
SHIP_FROM_BU (ship-from business unit) |
Required when PeopleSoft applications populate IDENTIFIER with INV_ITEM_ID from MASTER_ITEM_TBL |
Identifies shipping business unit. |
|
121 |
SHIP_DATE |
Required for contract liability if recognition basis is SHP (ship date). |
The date an order is shipped. |
|
122 |
SHIP_TIME |
Optional. |
Optional. |
|
123 |
PACKSLIP_NO (packing slip number) |
Optional. |
Optional. |
|
124 |
LC_ID (letter of credit ID) |
Optional. |
Optional. |
|
125 |
LOC_DOC_ID (location document ID) |
Optional. |
Optional. |
|
126 |
SEQUENCE_NBR (shipment sequence number) |
Optional. |
Optional. |
|
127 |
SOLD_TO_CUST_ID (sold to customer) |
Optional. |
Optional. Required for determining India GST using Billing Interface. |
|
128 |
SOLD_TO_ADDR_NUM (sold to address number) |
Optional. |
Optional. Required for determining India GST using Billing Interface. |
|
129 |
BUSINESS_UNIT_PC (PeopleSoft Project Costing business unit) |
Optional. |
Optional. |
|
130 |
BUSINESS_UNIT_CA (PeopleSoft Contracts business unit) |
Required if PRODUCT_ID from PROD_ITEM table is populated by PeopleSoft Contracts. |
Identifies Contracts business unit. |
|
131 |
RT_EFFDT (rate effective date) |
Leave Blank. |
Not currently used. |
|
132 |
BILL_PLAN_ID |
Optional. |
Optional. |
|
133 |
PC_DISTRIB_STATUS |
Leave blank. |
N is the default value if Contract Number and Bill Plan ID are present. If they are not present, I is the default value. Controls integration with PeopleSoft Project Costing. |
|
134 |
BPLAN_LN_NBR (bill plan line number) |
Optional. |
Optional. |
|
135 |
EVENT_OCCURRENCE |
Optional. |
Optional. |
|
136 |
XREF_SEQ_NUM (cross-reference sequence number) |
Optional. |
Optional. |
|
137 |
CONTRACT_PPD_SEQ (prepaid add sequence) |
Optional. |
Optional. |
|
138 |
ANALYSIS_TYPE |
Optional. |
Optional. |
|
139 |
RESOURCE_ID |
Optional. |
Optional. |
|
140 |
RESOURCE_TYPE |
Optional. |
Optional. |
|
141 |
RESOURCE_CATEGORY |
Optional. |
Optional. |
|
142 |
RESOURCE_SUB_CAT (resource subcategory) |
Optional. |
Optional. |
|
143 |
ACTIVITY_ID |
Optional. |
Optional. |
|
144 |
ACTIVITY_TYPE |
Optional. |
Optional. |
|
145 |
DIST_CFG_FLAG |
Required. |
Set to either Y or N. When an item is configurable, set to Y. |
|
146 |
PRODUCT_KIT_ID |
Optional. |
Optional. |
|
147 |
SYSTEM_SOURCE |
Optional. |
For PeopleSoft Order Management sales orders: OBI. For PeopleSoft Order Management and Inventory returns: OBI. For PeopleSoft Inventory: IBI. For PeopleSoft Contracts: CBI. For PeopleSoft Project Costing: PBI. For PeopleSoft Asset Managements: ABI. If left blank, the Billing Interface process uses BBI as the default value. Required for determining India GST using Billing Interface. |
|
148 |
EMPLID (employee ID) |
Optional. |
Optional. |
|
149 |
EMPL_RCD (number of employee record) |
Optional. |
Optional. |
|
150 |
START_DT |
Required for contract liability if recognition basis is STE (start and end date range). |
Use START_DT with END_DT to specify the period over which revenue should be recognized. |
|
151 |
END_DT |
Required for contract liability if recognition basis is STE (start and end date range). |
Use START_DT with END_DT to specify the period over which revenue should be recognized. |
|
152 |
FROM_DT |
Optional. |
Optional. |
|
153 |
TO_DT |
Optional. |
Optional. |
|
154 |
SERVICE_CUST_ID (service customer) |
Optional. |
Optional. |
|
155 |
SERVICE_ADDR_NUM (service address) |
Optional. |
Optional. |
|
156 |
NOTE_TYPE |
Leave blank. |
Used for NOTE transactions only. |
|
157 |
STD_NOTE_FLAG (standard note flag) |
Leave blank. |
Used for NOTE transactions only. |
|
158 |
INTERNAL_FLAG |
Leave blank. |
Used for NOTE transactions only. |
|
159 |
HDR_OR_LINE_NOTE (header or line note flag) |
Leave blank. |
Used for NOTE transactions only. |
|
160 |
AR_LVL |
Leave blank. |
Leave blank. |
|
161 |
AR_DST_OPT |
Leave blank. |
Leave blank. |
|
162 |
GL_LVL |
Leave blank. |
Leave blank. |
|
163 |
ENABLE_DFR_REV_FLG |
Leave blank. |
Leave blank. |
|
164 |
BILLING_SPECIALIST |
Optional. |
If provided, it must be valid and included in the bill-by definition. If not provided, the Billing Interface process obtains a default value from the setup tables, based on the PeopleSoft Billing default hierarchy. |
|
165 |
BILLING_AUTHORITY |
Optional. |
If provided, it must be valid and included in the bill-by definition. If not provided, the Billing Interface process obtains a default value from the setup tables, based on the PeopleSoft Billing default hierarchy. |
|
166 |
BILLING_FREQUENCY |
Optional. |
ONC (once) is the default value, if left blank. |
|
167 |
BILL_INQUIRY_PHONE |
Optional. |
If provided, it must be valid and included in the bill-by definition. If not provided, the Billing Interface process obtains a default value from the setup tables, based on the PeopleSoft Billing default hierarchy. |
|
168 |
SALES_PERSON |
Optional. |
If provided, it must be valid and included in the bill-by definition. If not provided, the Billing Interface process obtains a default value from the setup tables, based on the PeopleSoft Billing default hierarchy. |
|
169 |
COLLECTOR |
Optional. |
If provided, it must be valid and included in the bill-by definition. If not provided, the Billing Interface process obtains a default value from the setup tables, based on the PeopleSoft Billing default hierarchy. |
|
170 |
CR_ANALYST |
Optional. |
If provided, it must be valid and included in the bill-by definition. If not provided, the Billing Interface process obtains a default value from the setup tables, based on the PeopleSoft Billing default hierarchy. |
|
171 |
INVOICE_FORM_ID |
Optional. |
If provided, it must be valid and included in the bill-by definition. If not provided, the Billing Interface process obtains a default value from the setup tables, based on the PeopleSoft Billing default hierarchy. |
|
172 |
STD_NOTE_CD (standard note code) |
Leave blank. |
Used for NOTE transactions only. |
|
173 |
TOT_LINE_DST_AMT |
Leave blank. |
Leave blank. |
|
174 |
TOT_LINE_DST_PCT |
Leave blank. |
Leave blank. |
|
175 |
TOT_LINE_DFR_PCT |
Leave blank. |
Leave blank. |
|
176 |
TOT_LINE_DFR_AMT |
Leave blank. |
Leave blank. |
|
177 |
TOT_LINE__AMT |
Leave blank. |
Leave blank. |
|
178 |
TOT_LINE__PCT |
Leave blank. |
Leave blank. |
|
179 |
SSN (social security number) |
Optional. |
Optional. |
|
180 |
CHARGE_FROM_DT (charge from date) |
Required for contract liability if recognition basis is CHG. |
Use CHARGE_FROM_DT with CHARGE_TO_DATE to set the revenue recognition period. |
|
181 |
CHARGE_TO_DT (charge to date) |
Required for contract liability if recognition basis is CHG. |
Use CHARGE_FROM_DT with CHARGE_TO_DATE to set the revenue recognition period. |
|
182 |
SUBCUST_QUAL1 (subcustomer qualifier 1) |
Optional. |
If not populated, the system defaults subcustomer1 from bill-to customer setup. |
|
183 |
SUBCUST_QUAL2 (subcustomer qualifier 2) |
Optional. |
If not populated, the system defaults subcustomer2 from bill-to customer setup. |
|
184 |
REIMB_AGREEMENT |
Optional. |
Optional. |
|
185 |
TOT_DISCOUNT_AMT |
Leave blank. |
Leave blank. |
|
186 |
TOT_SURCHARGE_AMT |
Leave blank. |
Leave blank. |
|
187 |
ACCUMULATE |
Optional. |
Include in cumulative balance (Y/N). If not provided, the system uses Y as the default value. |
|
188 |
VAT_TREATMENT_GRP |
Optional. |
Applies to VAT transactions only. If provided, it must be a valid VAT treatment group. If not provided, the system populates with a default value through the VAT Defaulting process. |
|
189 |
COUNTRY_VAT_BILLFR |
Optional. |
Applies to VAT transactions only. If provided, it must be a valid VAT country. If not provided, the system populates with a default value through the VAT Defaulting process. |
|
190 |
COUNTRY_VAT_BILLTO |
Optional. |
Applies to VAT transactions only. If provided, it must be a valid VAT country. If not provided, the system populates with a default value through the VAT Defaulting process. |
|
191 |
VAT_TREATMENT |
Optional. |
Applies to VAT transactions only. If provided, it must be a valid VAT treatment. If not provided, the system populates with a default value through the VAT defaulting process. |
|
192 |
PHYSICAL_NATURE |
Optional. |
Use G for goods; S for services. Applies to VAT transactions only. If not provided, the Billing Interface process obtains a default value from the PeopleSoft Billing VAT drivers hierarchy for transactions that are liable for VAT. |
|
193 |
COUNTRY_LOC_BUYER |
Optional. |
Applies only to VAT transactions where the physical nature is S (services). If provided, it must a valid country. If not provided, the system obtains a default value from the customer's bill-to location. |
|
194 |
STATE_LOC_BUYER |
Optional. |
Applies only to VAT transactions where the physical nature is S (services). If provided, it must be a valid state associated with the buyer's location country. If not provided, the system obtains a default value from the customer's bill-to location. Leave blank when the buyer's location country does not track VAT by state or province. |
|
195 |
COUNTRY_LOC_SELLER |
Optional. |
Applies only to VAT transactions where the physical nature is S (services). If provided, it must be a valid country. If not provided, the system obtains a default value from the appropriate business unit location according to the source of the transaction. |
|
196 |
STATE_LOC_SELLER |
Optional. |
Applies only to VAT transactions where the physical nature is S (services). If provided, it must be a valid state associated with the seller's location country. If not provided, the system obtains a default value from a business unit location, as described for COUNTRY_LOC_SELLER. Leave blank when the seller's location country does not track VAT by state or province. |
|
197 |
VAT_SVC_SUPPLY_FLG |
Optional. |
Applies only to VAT transactions where the physical nature is S (services). If provided, it must be valid. If not provided, the system populates with a default value through the VAT Defaulting process. |
|
198 |
VAT_SERVICE_TYPE |
Optional. |
Applies only to VAT transactions where the physical nature is S (services). If provided, it must be a valid VAT service type. If not provided, the system populates with a default value through the VAT Defaulting process. |
|
199 |
COUNTRY_VAT_PERFRM |
Optional. |
Applies only to VAT transactions where the physical nature is S (services). If provided it must be a valid country. If not provided, the system populates with a default value from the PeopleSoft Billing VAT drivers hierarchy. |
|
200 |
STATE_VAT_PERFRM |
Optional. |
Applies only to VAT transactions where the physical nature is S (services). If provided, it must be a valid state associated with the COUNTRY_VAT_PERFRM value. If not provided, the system populates with a default value from the PeopleSoft Billing VAT drivers. Leave blank when the COUNTRY_VAT_PERFRM does not track VAT by state or province. |
|
201 |
COUNTRY_VAT_SUPPLY |
Optional. |
Applies only to VAT transactions where the physical nature is S (services). If provided it must be a valid country. If not provided, the system populates with a default value through the VAT Defaulting process. |
|
202 |
STATE_VAT_SUPPLY |
Leave blank. |
Leave blank. |
|
203 |
STATE_SHIP_FROM |
Optional. |
If provided, it must be a valid state associated with the ship-from country. If not provided, the system obtains a default value as described for COUNTRY_SHIP_FROM. Leave blank when the ship-from country does not track VAT by state or province. Required for determining India GST using Billing Interface. |
|
204 |
STATE_SHIP_TO |
Optional. |
If provided, it must be a valid state. If not provided, the system obtains a default value from the ship-to customer location for VAT transactions. Leave blank when the ship-to country does not track VAT by state or province. Required for determining India GST using Billing Interface. |
|
205 |
MAST_CONTR_ID |
Optional. |
Optional. |
|
206 |
TAX_CUST_ID |
Optional. |
Used in conjunction with Taxware or Vertex tax options. Populate with customer number defined in Vertex or Taxware to determine tax exemptions. (If blank, tax calculation in PeopleSoft Billing sends ship-to customer to Vertex or Taxware). |
|
207 |
BUSINESS_UNIT_AM |
Required for Asset Management transactions. |
Populated by the asset management system only. |
|
208 |
BUSINESS_UNIT_AMTO |
Required for InterUnit transactions. |
Populated by the asset management system only. |
|
209 |
ASSET_ID |
Required for InterUnit transactions. |
Populated by asset management system only. |
|
210 |
PROFILE_ID |
Required for InterUnit transactions. |
Populated by the asset management system only. |
|
211 |
COST_TYPE |
Required for InterUnit transactions. |
Populated by the asset management system only. |
|
212 |
STATE_VAT_DEFAULT |
Optional. |
Applies to VAT transactions only. If not provided, the system populates with a default value through the VAT Defaulting process. Leave blank when the VAT reporting country does not track VAT by state or province. |
|
213 |
SO_ID |
Optional. |
Optional. |
|
214 |
BUSINESS_UNIT_RF |
Optional. |
If populated, use the CRM services business unit value associated with the SO_ID. |
|
215 |
SOURCE_REF_TYPE |
Optional. |
Populate if the SOURCE_REF_NO is populated, and use a value that describes the type of generic reference used in the SOURCE_REF_NO field. |
|
216 |
SOURCE_REF_NO |
Optional. |
If populated, use a unique generic reference number (that does not already exist on the INTFC_BI table), such as the CRM agreement or CRM case ID. |
|
217 |
SOURCE_REF_KEY |
Optional. |
Populate only when SOURCE_REF_NO is also populated, and use a key to the generic reference number. For example, you might use the business unit or SetID. |
|
218 |
ACCEPTGIRO_IND |
Leave blank. |
Leave blank. |
|
219 |
CA_PGP_SEQ |
Conditional. |
Required for progress payment transactions. Populate with the value in the CA_PGP_SEQ field for the row on the CA_PGP_TERMS table corresponding to the progress payment term entry for this transaction. Leave blank for other transactions. |
|
220 |
SUM_TEMPLATE_ID |
Optional. |
Populate with an ID value from the BI_SUM_TEMPLATE table. |
|
221 |
SUM_GROUP_TYPE |
Optional. |
If the summarization template identified in the SUM_TEMPLATE_ID field includes the summarization group type, populate with an ID from the BI_SGRP_TYP_TBL. |
|
222 |
SUM_GROUP_ID |
Optional. |
If the summarization template identified in the SUM_TEMPLATE_ID field includes the summarization group, populate with an ID from the BI_S_GRP_ID_TBL. Important! The Billing Interface process does not check that the summarization group is a member of the summarization group type. |
|
223 |
CUST_DEPOSIT_ID |
Required when line references a customer deposit. |
Must be blank if not used. Otherwise, must match the DEPOSIT_ID on the DEPOSIT_CONTROL table corresponding to the customer's deposit entry. |
|
224 |
TAX_DATE |
Optional. |
Enter a date that third-party tax software should use to determine effective tax rates, if this date is different from the invoice date or transaction date. |
|
225 |
GROUP_CODE |
Leave blank. |
Leave blank. |
|
226 |
SRV_PERFORM_LOC |
Optional. |
If used must correspond to a value in the LOCATION field on LOCATION_TBL. Enter the location where the service will be performed. |
|
227 |
TAX_DIVISION |
Optional. |
Defaults from Billing Business Unit. |
|
228 |
TAX_DEPARTMENT |
Optional. |
Defaults from Billing Business Unit. |
|
229 |
PT_SALE_FLG |
Optional. |
Y or N, defaults to N. Used in tax calculation, this indicates that the customer visited the seller's office for part of the transaction. |
|
231 |
CUST_PICKUP |
Optional. |
Indicates that the customer picked up the goods, and the ship-to address is equivalent to the ship-from address. |
|
232 |
CUSTOMER_PO_SCHED |
Leave blank. |
Leave blank. |
|
233 |
PUBLIC_VOUCHER_NBR |
Optional |
Leave blank to have the Billing Interface assign a PVN number when PVN_GEN_LVL is not blank. |
|
234 |
PVN_GEN_LVL |
Optional |
Required for Public Voucher Number assignment. Populated by PeopleSoft Contracts module for PVN processing. |
|
235 |
USER_AMT1 (user amount 1) |
Optional. |
User-defined field. |
|
236 |
USER_AMT2 (user amount 2) |
Optional. |
User-defined field. |
|
237 |
USER_DT1 (user date 1) |
Optional. |
User-defined field. |
|
238 |
USER_DT2 (user date 1) |
Optional. |
User-defined field. |
|
239 |
USER1 (user field 1) |
Optional. |
User-defined field. |
|
240 |
USER2 (user field 2) |
Optional. |
User-defined field. |
|
241 |
USER3 (user field 3) |
Optional. |
User-defined field. |
|
242 |
USER4 (user field 4) |
Optional. |
User-defined field. |
|
243 |
USER5 (user field 5) |
Optional. |
User-defined field. |
|
244 |
USER6 (user field 6) |
Optional. |
User-defined field. |
|
245 |
USER7 (user field 7) |
Optional. |
User-defined field. |
|
246 |
USER8 (user field 8) |
Optional. |
User-defined field. |
|
247 |
USER9 (user field 9) |
Optional. |
User-defined field. |
|
248 |
SETID |
Leave blank. |
Leave blank. |
|
249 |
PROCESS_INSTANCE |
Leave blank. |
The Process Instance ID is set by the Billing Interface process. |
|
250 |
ADD_DTTM (add date and time) |
Optional. |
Allows accurate reporting on interface activity. Used by interface workflow functions. |
|
251 |
LAST_UPDATE_DTTM (last update date and time) |
Leave blank. |
The last update date and time field is set by the Billing Interface process. |
|
252 |
VAT_RVRSE_CHG_GDS |
Leave blank. |
Leave blank. |
|
253 |
TAX_CD_VAT_RVC |
Leave blank. |
Leave blank. |
The following table demonstrates how to populate the INTFC_BI fields for NOTE transactions:
|
Field Number |
Field Name |
Required for NOTE Transactions? |
Remarks |
|---|---|---|---|
|
1 |
INTFC_ID (interface ID) |
Required. |
Used to group or batch a collection of Billing interface activity. |
|
2 |
INTFC_LINE_NUM (interface line number) |
Required. |
Each unique interface line number for an interface ID represents a separate bill line charge. |
|
3 |
TRANS_TYPE_BI (transaction type) |
Required. |
Value must be NOTE. |
|
4 |
TRANS_TYPE_BI_SEQ (transaction type sequence) |
Required. |
If more than one note is populated for a particular LINE transaction, the transaction type sequence must be used for uniqueness. Note: Do not initialize to zero, for note transactions, TRANS_TYPE_BI_SEQ must begin with 1. |
|
13 |
LOAD_STATUS_BI |
Optional. |
May initialize to NEW or leave blank. |
|
15 |
BUSINESS_UNIT (billing business unit) |
Required. |
Must be a valid billing business unit. |
|
156 |
NOTE_TYPE |
Optional. |
|
|
157 |
STD_NOTE_FLAG (standard note flag) |
Optional. |
Y is the default value if a standard note code (STD_NOTE_CD) exists and the note text (TEXT254) is blank. N is the default value if note text (TEXT254) is populated and standard note code (STD_NOTE_CD) is blank. |
|
158 |
INTERNAL_FLAG |
Required. |
Must be Y or N. |
|
159 |
HDR_OR_LINE_NOTE (header or line note flag) |
Optional. |
Values are: H (header note) and L (line note). L appears as the default value, if left blank. |
|
184 |
REIMB_AGREEMENT |
Optional. |
|
|
246 |
ADD_DTTM |
Optional. |
Allows accurate reporting on interface activity. Used by interface workflow functions. |
The following table demonstrates how to populate the INTFC_BI fields for AHDR transactions:
|
Field Number |
Field Name |
Required for AHDR Transactions? |
Remarks |
|---|---|---|---|
|
1 |
INTFC_ID (interface ID) |
Required. |
Used to group or batch a collection of Billing interface activity. |
|
2 |
INTFC_LINE_NUM (interface line number) |
Required. |
Each unique interface line number for an interface ID with AHDR transaction guarantees uniqueness. |
|
3 |
TRANS_TYPE_BI (transaction type) |
Required. |
Value must be AHDR. |
|
4 |
TRANS_TYPE_BI_SEQ (transaction type sequence) |
Required. |
Initialize to zero for AHDR transaction type. |
|
7 |
ADJ_TRANS_TYPE (adjustment transaction type) |
Required. |
Must be CRALL for Credit Entire Bill or RBALL for Rebill Entire Bill. |
|
9 |
TMP_BILL_FLG (temporary bill flag) |
Leave blank. |
Temporary bills are not supported for adjustments. |
|
10 |
ENTRY_TYPE |
Optional. |
|
|
11 |
ENTRY_REASON |
Optional. |
|
|
12 |
ENTRY_EVENT |
Conditional. |
Leave blank for CRALL. If provided for RBALL, it must be valid and included in the bill-by definition. If not provided, the Billing Interface process obtains a default value from the setup tables, based on the PeopleSoft Billing default hierarchy. |
|
13 |
LOAD_STATUS_BI |
Optional. |
May initialize to NEW or leave blank. |
|
15 |
BUSINESS_UNIT (billing business unit) |
Required. |
Must be a valid billing business unit. |
|
17 |
BILL_TO_CUST_ID (bill-to customer) |
Required. |
Must be a valid bill-to customer. Leave blank for India tax transactions populated by PeopleSoft Order Management. AHDR is not supported for India transactions. |
|
18 |
ADDRESS_SEQ_NUM (address sequence number) |
Conditional. |
Leave blank for CRALL. If provided for RBALL, it must be valid and included in the bill-by definition. If not provided, the Billing Interface process obtains a default value from the setup tables, based on the PeopleSoft Billing default hierarchy. Leave blank for India tax transactions populated by PeopleSoft Order Management. |
|
20 |
CNTCT_SEQ_NUM (contact sequence number) |
Conditional. |
Leave blank for CRALL. If provided for RBALL, it must be valid and included in the bill-by definition. If not provided, the Billing Interface process obtains a default value from the setup tables, based on the PeopleSoft Billing default hierarchy. |
|
23 |
BUSINESS_UNIT_TO |
Conditional. |
Leave blank for CRALL For RBALL, if not populated and if the customer is an InterUnit customer, the system uses the BUSINESS_UNIT_GL value from the CUST_OPTION table, based on the customer ID. If the system cannot obtain this value, it marks the transaction in error. |
|
24 |
DIRECT_INVOICING |
Optional. |
Bills set to Y are created in RDY bill status. If provided, it must be valid and included in the bill-by definition. If not provided, defaults to N. |
|
25 |
RANGE_SELECTION_ID |
Optional. |
Used in range selection options and with direct invoicing. |
|
26 |
BILL_SOURCE_ID |
Required only if invoice numbering by bill source. |
Must be a valid bill source if provided. |
|
27 |
BILL_TYPE_ID |
Required. |
Must be a valid bill type. |
|
28 |
BILL_CYCLE_ID |
Conditional. |
Leave blank for CRALL. If provided for RBALL, it must be valid and included in the bill-by definition. If not provided, the Billing Interface process obtains a default value from the setup tables, based on the PeopleSoft Billing default hierarchy. |
|
29 |
BILL_BY_ID (bill-by identifier) |
Conditional. |
Leave blank for CRALL. Must be valid if provided for RBALL. Defaults if left blank. |
|
30 |
PAYMENT_METHOD (payment method) |
Conditional. |
Leave blank for CRALL. If provided for RBALL, it must be valid and included in the bill-by definition. If not provided, the Billing Interface process obtains a default value from the setup tables, based on the PeopleSoft Billing default hierarchy. |
|
31 |
PYMNT_TERMS_CD (payment terms code) |
Conditional. |
Leave blank for CRALL. If provided for RBALL, it must be valid and included in the bill-by definition. If not provided, the Billing Interface process obtains a default value from the setup tables, based on the PeopleSoft Billing default hierarchy. |
|
32 |
BANK_CD (bank code) |
Conditional. |
Leave blank for CRALL. If provided for RBALL, it must be valid and included in the bill-by definition. If not provided, the Billing Interface process obtains a default value from the setup tables, based on the PeopleSoft Billing default hierarchy. |
|
33 |
BANK_ACCT_KEY |
Conditional. |
Leave blank for CRALL. If provided for RBALL, it must be valid and included in the bill-by definition. If not provided, the Billing Interface process obtains a default value from the setup tables, based on the PeopleSoft Billing default hierarchy. |
|
34 |
BI_CURRENCY_CD (billing transaction currency) |
Conditional. |
Leave blank for CRALL. For RBALL, must be the same currency as the bill being adjusted. |
|
36 |
CUR_RT_TYPE (currency rate type) |
Conditional. |
Leave blank for CRALL. Must be valid if provided for RBALL. Defaults if left blank. |
|
37 |
RATE_MULT (rate multiplier) |
Conditional. |
Leave blank for CRALL. If provided for RBALL, it must be valid and included in the bill-by definition. If not provided, the Billing Interface process sets it to 0 (zero) |
|
38 |
RATE_DIV (rate divisor) |
Conditional. |
Leave blank for CRALL. If provided for RBALL, it must be valid and included in the bill-by definition. If not provided, the Billing Interface process sets it to 1. |
|
39 |
CUR_RT_SOURCE (currency rate source) |
Conditional. |
Leave blank for CRALL. If provided for RBALL, it must be valid and included in the bill-by definition. If not provided, the Billing Interface process obtains a default value from the setup tables, based on the PeopleSoft Billing default hierarchy. |
|
40 |
INVOICE_DT (invoice date) |
Optional. |
|
|
41 |
ACCOUNTING_DT (accounting date) |
Optional. |
|
|
43 |
TARGET_INVOICE |
Optional. |
If passed, target invoice becomes the invoice number. |
|
45 |
DOC_TYPE (document type) |
Optional. |
|
|
46 |
CONSOL_SETID (consolidation customer SetID) |
Leave blank. |
Not supported for adjustments. |
|
47 |
CONSOL_CUST_ID (consolidation customer ID) |
Leave blank. |
Not supported for adjustments. |
|
48 |
CONSOL_KEY (consolidation key) |
Leave blank. |
Not supported for adjustments. |
|
49 |
INVOICE_TO_ADJ |
Required. |
Invoice to be adjusted must be a valid invoice. |
|
95 |
BUSINESS_UNIT_OM (PeopleSoft Order Management business unit) |
Conditional. |
Leave blank for CRALL. Required for RBALL if PRODUCT_ID is populated or when India tax transactions are populated by PeopleSoft Order Management. |
|
96 |
ORDER_NO (order number) |
Optional. |
Leave blank for CRALL. Optional for RBALL. |
|
102 |
RMA_ID (RMA identifier) |
Optional. |
Leave blank for CRALL. Optional for RBALL. |
|
103 |
RMA_LINE_NBR (RMA line number) |
Optional. |
Leave blank for CRALL. Optional for RBALL. |
|
105 |
ORDER_DATE |
Conditional. |
Leave blank for CRALL. For RBALL, required for contract liability if recognition basis is ORD (order date). |
|
106 |
PO_REF (purchase order number) |
Optional. |
Leave blank for CRALL. Optional for RBALL. |
|
114 |
COUNTRY_SHIP_FROM |
Conditional. |
Leave blank for CRALL and India tax transactions populated by PeopleSoft Order Management. If not provided for RBALL, the system obtains a default value from the ship-from business unit, then from the billing business unit location for VAT transactions. |
|
115 |
COUNTRY_SHIP_TO |
Conditional. |
Leave blank for CRALL and India tax transactions populated by PeopleSoft Order Management. If not provided for RBALL, the system obtains a default value from the ship-to customer location for VAT transactions. |
|
116 |
SHIP_TO_CUST_ID (ship-to customer) |
Conditional. |
Leave blank for CRALL and India tax transactions populated by PeopleSoft Order Management. For RBALL VAT transactions, if you do not provide a value, the Billing Interface process attempts to provide a default value in this manner:
|
|
117 |
SHIP_TO_ADDR_NUM (ship-to address) |
Conditional. |
Leave blank for CRALL and India tax transactions populated by PeopleSoft Order Management. For RBALL VAT transactions, if you do not provide a value, the Billing Interface process attempts to provide a default value in this manner:
|
|
118 |
SHIP_ID (shipment ID) |
Conditional. |
Leave blank for CRALL and India tax transactions populated by PeopleSoft Order Management. Optional for RBALL. |
|
119 |
SHIP_TYPE_ID (shipment type) |
Conditional. |
Leave blank for CRALL and India tax transactions populated by PeopleSoft Order Management. Optional for RBALL. |
|
120 |
SHIP_FROM_BU (ship-from business unit) |
Optional. |
Leave blank for CRALL. Optional for RBALL. |
|
123 |
PACKSLIP_NO (packing slip number) |
Optional. |
Leave blank for CRALL. Optional for RBALL. |
|
124 |
LC_ID (letter of credit ID) |
Optional. |
Leave blank for CRALL. Optional for RBALL. |
|
125 |
LOC_DOC_ID (location document ID) |
Optional. |
Leave blank for CRALL. Optional for RBALL. |
|
127 |
SOLD_TO_CUST_ID (sold to customer) |
Optional. |
Leave blank for CRALL. Optional for RBALL. |
|
128 |
SOLD_TO_ADDR_NUM (sold to address number) |
Optional. |
Leave blank for CRALL. Optional for RBALL. |
|
129 |
BUSINESS_UNIT_PC (PeopleSoft Project Costing business unit) |
Optional. |
Leave blank for CRALL. Optional for RBALL. |
|
130 |
BUSINESS_UNIT_CA (PeopleSoft Contracts business unit) |
Conditional. |
Leave blank for CRALL. Required for RBALL if PRODUCT_ID from PROD_ITEM table is populated by PeopleSoft Contracts. |
|
132 |
BILL_PLAN_ID |
Optional. |
Leave blank for CRALL. Optional for RBALL. |
|
134 |
BPLAN_LN_NBR (bill plan line number) |
Optional. |
Leave blank for CRALL. Optional for RBALL. |
|
135 |
EVENT_OCCURRENCE |
Optional. |
Leave blank for CRALL. Optional for RBALL. |
|
137 |
CONTRACT_PPD_SEQ (prepaid add sequence) |
Optional. |
Leave blank for CRALL. Optional for RBALL. |
|
138 |
ANALYSIS_TYPE |
Optional. |
Leave blank for CRALL. Optional for RBALL. |
|
140 |
RESOURCE_TYPE |
Optional. |
Leave blank for CRALL. Optional for RBALL. |
|
141 |
RESOURCE_CATEGORY |
Optional. |
Leave blank for CRALL. Optional for RBALL. |
|
142 |
RESOURCE_SUB_CAT (resource subcategory) |
Optional. |
Leave blank for CRALL. Optional for RBALL. |
|
143 |
ACTIVITY_ID |
Optional. |
Leave blank for CRALL. Optional for RBALL. |
|
144 |
ACTIVITY_TYPE |
Optional. |
Leave blank for CRALL. Optional for RBALL. |
|
145 |
DIST_CFG_FLAG |
Conditional. |
Leave blank for CRALL. For RBALL, set to either Y or N. When an item is configurable, set to Y. |
|
146 |
PRODUCT_KIT_ID |
Conditional. |
Leave blank for CRALL and India tax transactions populated by PeopleSoft Order Management. Optional for RBALL. |
|
147 |
SYSTEM_SOURCE |
Same as LINE for RBALL. See Understanding Guidelines for Creating Adjustments. |
Leave blank for CRALL. For RBALL of PeopleSoft Order Management sales orders: OBI. For RBALL of PeopleSoft Order Management and Inventory returns: OBI. For RBALL of PeopleSoft Inventory: IBI. For PeopleSoft Contracts: CBI. For RBALL of PeopleSoft Project Costing: PBI. For RBALL of PeopleSoft Asset Managements: ABI. If left blank, the Billing Interface process uses BBI as the default value. |
|
148 |
EMPLID (employee ID) |
Optional. |
Leave blank for CRALL. Optional for RBALL. |
|
150 |
START_DT |
Conditional. |
Leave blank for CRALL. Required for RBALL with contract liability if recognition basis is STE (start and end date range). |
|
151 |
END_DT |
Conditional. |
Leave blank for CRALL. Required for RBALL with contract liability if recognition basis is STE (start and end date range). |
|
152 |
FROM_DT |
Optional. |
Leave blank for CRALL. Optional for RBALL. |
|
153 |
TO_DT |
Optional. |
Leave blank for CRALL. Optional for RBALL. |
|
154 |
SERVICE_CUST_ID (service customer) |
Optional. |
Leave blank for CRALL. Optional for RBALL. |
|
155 |
SERVICE_ADDR_NUM (service address) |
Optional. |
Leave blank for CRALL. Optional for RBALL. |
|
164 |
BILLING_SPECIALIST |
Conditional. |
Leave blank for CRALL. If provided for RBALL, it must be valid and included in the bill-by definition. If not provided, the Billing Interface process obtains a default value from the setup tables, based on the PeopleSoft Billing default hierarchy. |
|
165 |
BILLING_AUTHORITY |
Conditional. |
Leave blank for CRALL. If provided for RBALL, it must be valid and included in the bill-by definition. If not provided, the Billing Interface process obtains a default value from the setup tables, based on the PeopleSoft Billing default hierarchy. |
|
166 |
BILLING_FREQUENCY |
Conditional. |
Leave blank for CRALL. For RBALL, ONC (once) is the default value, if left blank. |
|
167 |
BILL_INQUIRY_PHONE |
Conditional. |
Leave blank for CRALL. If provided for RBALL, it must be valid and included in the bill-by definition. If not provided, the Billing Interface process obtains a default value from the setup tables, based on the PeopleSoft Billing default hierarchy. |
|
168 |
SALES_PERSON |
Conditional. |
Leave blank for CRALL. If provided for RBALL, it must be valid and included in the bill-by definition. If not provided, the Billing Interface process obtains a default value from the setup tables, based on the PeopleSoft Billing default hierarchy. |
|
169 |
COLLECTOR |
Conditional. |
Leave blank for CRALL. If provided for RBALL, it must be valid and included in the bill-by definition. If not provided, the Billing Interface process obtains a default value from the setup tables, based on the PeopleSoft Billing default hierarchy. |
|
170 |
CR_ANALYST |
Conditional. |
Leave blank for CRALL. If provided for RBALL, it must be valid and included in the bill-by definition. If not provided, the Billing Interface process obtains a default value from the setup tables, based on the PeopleSoft Billing default hierarchy. |
|
171 |
INVOICE_FORM_ID |
Conditional. |
Leave blank for CRALL. If provided for RBALL, it must be valid and included in the bill-by definition. If not provided, the Billing Interface process obtains a default value from the setup tables, based on the PeopleSoft Billing default hierarchy. |
|
179 |
SSN (social security number) |
Optional. |
Leave blank for CRALL. Optional for RBALL. |
|
182 |
SUBCUST_QUAL1 (subcustomer qualifier 1) |
Conditional. |
Leave blank for CRALL. If not populated for RBALL, the system defaults subcustomer1 from bill-to customer setup. |
|
183 |
SUBCUST_QUAL2 (subcustomer qualifier 2) |
Conditional. |
Leave blank for CRALL. If not populated for RBALL, the system defaults subcustomer2 from bill-to customer setup. |
|
184 |
REIMB_AGREEMENT |
Optional. |
|
|
231 |
USER_AMT1 (user amount 1) |
Optional. |
Leave blank for CRALL. Optional for RBALL. |
|
232 |
USER_AMT2 (user amount 2) |
Optional. |
Leave blank for CRALL. Optional for RBALL. |
|
233 |
USER_DT1 (user date 1) |
Optional. |
Leave blank for CRALL. Optional for RBALL. |
|
234 |
USER_DT2 (user date 1) |
Optional. |
Leave blank for CRALL. Optional for RBALL. |
|
235 |
USER1 (user field 1) |
Optional. |
Leave blank for CRALL. Optional for RBALL. |
|
236 |
USER2 (user field 2) |
Optional. |
Leave blank for CRALL. Optional for RBALL. |
|
237 |
USER3 (user field 3) |
Optional. |
Leave blank for CRALL. Optional for RBALL. |
|
238 |
USER4 (user field 4) |
Optional. |
Leave blank for CRALL. Optional for RBALL. |
|
239 |
USER5 (user field 5) |
Optional. |
Leave blank for CRALL. Optional for RBALL. |
|
240 |
USER6 (user field 6) |
Optional. |
Leave blank for CRALL. Optional for RBALL. |
|
241 |
USER7 (user field 7) |
Optional. |
Leave blank for CRALL. Optional for RBALL. |
|
242 |
USER8 (user field 8) |
Optional. |
Leave blank for CRALL. Optional for RBALL. |
|
243 |
USER9 (user field 9) |
Optional. |
Leave blank for CRALL. Optional for RBALL. |
|
246 |
ADD_DTTM |
Optional. |
Allows accurate reporting on interface activity. Used by interface workflow functions. |