Important BI_EXTRCT Table Fields

The primary extract table, BI_EXTRCT, contains the following important fields used by invoices:

Term Definition

PRINT_SEQ_NBR

Printing sequence number that is calculated by the Billing extract process based on Print Invoice Sort By information specified by the run control. The query should order by this field to take advantage of this run control feature.

LANGUAGE_CD

The language code is usually specified by the run control. When it is not specified in the run control, the system looks it up either from user preferences or the PeopleSoft general options table.

SQR and BI Publisher invoices can be printed in any supported languages. If the PeopleSoft environment is configured to support multiple languages, the definitional data in the transaction, such as the description of a project, will be extracted from the related language tables in the desired language for all forms. However, there is a difference in handling predefined labels on SQR and BI Publisher forms. SQR uses the related language Strings table.

The report definition does not include any language-specific text. Each portion of text uses a formula called @langlookup, resembling the following:

StringVar RptLang := {BIXPRNT00.LANGUAGE_CD};
if stringVar RptLang = "USA" then 1
Else
if RptLang = "ENG" then 1
Else
 if RptLang = "FRA" then 2
Else
 if RptLang = "ESP" then 3
Else
 if RptLang = "CFR" then 4
else
 if RptLang = "GER" then 5
else
 if RptLang = "JPN" then 6

else
		if RptLang = "INE" then 7 
else
		 if RptLang = "DUT" then 8
else 
		 if RptLang = "POR" then 9 
else
		 if RptLang = "ITA" then 10 
else 
		 if RptLang = "ZHS" then 11
else 1

Each text field prints a different text string of an array, indexing it with the @langlookup formula.

The BI Publisher report definitions contain language-specific text for the labels in the main template file. Each template file has associated XLIFF (XML Localization Interchange File Format) files which will contain the translated report labels. A separate XLIFF file can be created for each language. These XLIFF files are used when the report is run to produce the output of report labels in the appropriate language.

Note: If BI Publisher is used as the invoice form and a batch of invoices contains multiple language codes, then one output report is generated for each language code.

XEU_PARTICIPATING

Indicates whether the billing currency is a euro-participating currency. If the currency is euro-participating, the invoice prints the euro invoice amount. Otherwise, it does not.

DECIMAL_POSITIONS

Indicates how many decimal places to print for the billing currency. Reports are set up to print any number of decimal places. The field format must be set up accordingly. The edit formula on the decimals uses DECIMAL_POSITIONS to define how many places to print.

INVOICE_DT

The invoice date that is printed on the invoice uses this field from the extract table. There is also an INVOICE_DT on the table BI_HDR, but depending on where the bill is in the invoice process, that field may not contain a value. BI_IVCEXT calculates the invoice date, if needed, and populates INVOICE_DT on the extract table.

PYMNT_TERMS_ CD_DSC (Payment Terms Code Description)

Use this field to print the description, and not the code that is stored on BI_HDR.

DISC_AMT, DISC_DT

The discount amount and discount date.

DUE_DT

Due date.

ADDR_LN1 thru 8

These lines contain the customer name, customer contact (attention to), and address lines formatted appropriately for the country. The country-dependent formatting is done in BI_IVCEXT. If all address lines are used in an address, there are eight printed lines. If all address lines are not used, there are fewer than eight lines, and the ADDR_LN fields are filled out from top to bottom with blank lines at the bottom.

REMIT_ADDR_LN1 thru 8

These lines contain the remit to description and address. They are handled the same as Customer address lines.

INV_LABEL

Invoice label is the text that is printed at the top of the invoice. It is a language-specific version of invoice, pro forma, temporary, credit invoice, and so on.

CUSTOM_LABEL

Contains printed text. For example, it may contain the label that is specified on the run control, or a language-specific version of original, duplicate, courtesy copy, original sent using electronic data interchange.

CONFIG_DTL_FLAG

Equals Y if the invoice form specifies the printing of order management configuration detail. This field is used in the example query BIPRNCONFGDTL, which is used in a subreport on the order management invoice example.

CONFIG_CD_FLAG

Equals Y if the invoice form specifies the printing of order management configuration code. This field is used in the example query BIPRNCONFGCD, which is used in a sub report of the order management invoice example.

CR_CARD_FLG

Determines whether a bill has credit card information.

AMOUNT

Stores a credit card amount.

AMOUNT_XEU

Stores a credit card amount in euros.

NET_AMOUNT

Contains a net amount.

NET_AMOUNT_XEU

Stores a net amount in euros.

TEMPLATE_INVOICE

Used with installment bills, and contains the installment template invoice number.

BILLING_FREQUENCY

Used to identify billing frequency for processing.

PRINT_INST_DETAIL

Controls printing of installment bill details.

PRINT_INST_SUMMARY

Controls printing of the installment bill summary.

PRINT_VAT_ANAL_FLG

Controls printing of VAT analysis

PRINT_TAX_FLG

Controls printing of sales tax

PRINT_UTL_PPD_FLG

Controls printing of contract utilization prepaid information.

PROJECT_ID

Stores the project ID from the bill header.

PROJ_DESCR

Stores project description that is derived from the Project table corresponding to the project ID on the bill header.

CONTRACT_NUM

Stores the contract number from the bill header.

PO_REF

Stores the purchase order reference number from the bill header.