This chapter provides overviews of the invoicing processes, the delivered invoicing jobs that contain these processes, direct invoicing jobs, and discusses how to configure and optimize invoicing jobs.
This section provides an overview of invoice processing and discusses:
Preprocessing steps.
Print processing steps.
Email processes (paperless invoices).
Retaining Invoice Image.
Processing Invoice Bursting
Post-invoicing processing steps.
PeopleSoft Billing generates invoices from the data stored in the Billing tables when an invoicing job is run. The components of an invoicing job can include AE, SQR, and Crystal processes, as well as subjobs. You can configure the invoicing jobs so that all the processes needed to generate an invoice are part of a single job, or you can use separate jobs to divide the invoicing process into logical steps. Likewise, you can configure a single job to generate all types of invoice forms or you can use different jobs for different types of invoice forms.
The typical steps required to generate an invoice are:
Complete the preprocessing steps:
Import billing data through the Billing interface.
Set value-added tax (VAT) and tax defaults.
Finalize invoice data and set status.
Extract invoice data and complete the print processing steps:
Extract data to temporary tables.
Run print processes for each invoice form.
Complete physical printing, email notification, and electronic data interchange (EDI) transmittal.
Complete the post-processing steps:
Process credit card payments.
Convert currency (if needed).
Create accounting entries.
When configuring invoice jobs, you must maintain the proper processing order. The processes and subjobs within a job can be configured to run in series or in parallel. In general, pre- and post-process steps must be run in series, while the processes that print the different types of invoice can be run in parallel.
Before invoices can be printed, the billing data must be imported (for Interface bills), validated, and finalized.
This table lists the processes, in alphabetical order, used to prepare billing data for invoicing:
Process Name |
Type |
Prerequisites |
Notes |
BIIF0001 |
AE |
External sources of billing data must load the Billing interface tables. |
Transfer data from the interface tables to the standard Billing tables. BIIF0001 can be run on its own, or as part of a larger job such as in direct or streamlined invoicing. See Understanding the Billing Interface Process Main Processing Logic. |
BIIVC000 |
AE |
BIPVAT00 must be run before BIIVC000, if VAT defaulting is required. |
Prepare bills for invoicing. No further changes can be made to billing data after the BIIVC000 process is run. |
BIPVAT00 |
AE |
Must be run before BIIVC000 for those transactions that are subject to VAT taxation. |
Set VAT defaults. See Understanding the Process VAT Defaults Process (BIPVAT00). |
BIRMAADJ |
AE |
NA |
Load RMA (return material authorization) adjustments into the billing interface tables. |
IN_FUL_CONF |
AE |
NA |
Confirm inventory picking. See Picking Inventory. |
IN_PUB_MSG |
AE |
NA |
Publish inventory outbound message. |
INS6300 |
SQR |
NA |
Load interunit transfer bills into the billing interface tables. |
INS6500 |
SQR |
NA |
Generate inventory packing slips. |
OM_BILL |
AE |
NA |
Load PeopleSoft Order Management bills into the billing interface tables. See Populating Billing. |
Finalization Process (BIIVC000)
The Finalization process selects bills that are ready for invoicing and validates and transforms the bill data. The process works in two modes. In pro forma mode, the process performs data validations and transformations that are necessary to preview the invoice. In finalization mode, the process carries out the same tasks as in pro forma mode and also performs final processing, such as setting the invoice date and status, and processing credit cards. Any number of pro formas can be created for a single bill; however, a bill can be finalized only once.
The Finalization process performs the following tasks (the tasks performed only in finalization mode are noted):
Sequences bill lines by the user-defined sort by option, or according to the invoice line numbers that you define manually during bill entry.
Calculates taxes by line according to current line values and tax rates.
Updates the bill header invoice amount to include currently calculated taxes.
Note. The system does not calculate taxes or VAT for a bill line when the tax timing option for the bill line (populated by PeopleSoft Contracts) is defined as S (taxes on services rendered).
Calculates due date and updates the bill header with this value.
Changes bill status from RDY (ready) to INV (Finalization mode only).
Updates the invoice date with the appropriate value for the bill, the run control, or the current date (Finalization mode only).
If you define the invoice date on the run control request page, the system checks if the date is in an open accounting period and issues a warning on the run control request page if the date falls outside of the period that is currently open in PeopleSoft General Ledger.
Updates the invoice print setting with a status of Printed for bills where the invoice form ID specifies a nonprinting form (Finalization mode only).
(If no printing is expected on this bill, the print status is Complete upon finalization).
For credit card bills, generates credit card authorization requests and changes the status of the bill to FNL (final) instead of INV (invoiced) (Finalization mode only).
Updates the last maintenance user ID and last updated date and time fields (Finalization mode only).
For invoices in euro-participating currencies, converts the invoice amount to the euro currency so that the amount appears on printed invoices in both currencies.
Creates EDI request entries for bills by EDI using XML technology (Finalization mode only).
Performs the Screen for Denied Parties process (SCM_FSS) as a secondary process if the Financial Sanctions Screening (FSS) is configured to be performed for the Order to Cash.
See Enabling PeopleSoft Billing Business Units for VAT and FSS.
Note. Use the Message Log page to review the results of this process online.
Platform-Specific Statements in BIIVC000
The ROUND and DATETIME functions differ from platform to platform; therefore, the system creates the following platform-specific sections:
DBSPEC |
DAY-related statement. |
DBSPEC05, 06, 07, 08 |
Due date calculation. |
DBSPEC10, 11 |
ROUND function for tax calculation without VAT. |
DBSPEC25, 26 |
ROUND function for tax calculation with VAT. |
BIBIIVC000_UPD |
Bill Header multi-column update. |
BIBIIVC000_UPD |
Bill Header VAT multi-column update. |
BIBIIVC000_UPD |
Bill Line multi-column update. |
BIBIIVC000_UPD |
Bill Line Tax multi-column update. |
BIBIIVC000_UPD |
Bill Line Excise and Sales Tax multi-column update. |
BIIVC000 validates bill data during pro forma and finalization processing. The following error codes are issued to BI_HDR and BI_LINE for validation and processing errors:
0120 |
Invalid Tax Code. |
0233 |
Missing or invalid bill currency. |
0900 |
Missing Remit To / Bank Code. |
0901 |
Invalid Invoice Form for Accepgiro. |
0902 |
Invalid Bank CD for Accepgiro. |
0903 |
Invalid Bank Account for Accepgiro. |
1000 |
AVP Error. |
1050 |
Ship To Geocode Not Numeric. |
1055 |
Ship From Geocode Not Numeric. |
1060 |
Order Acc Geocode Not Numeric. |
1110 |
Missing Ship To Cust ID (missing ship-to customer ID). |
1111 |
Invalid Ship To Cust Addr (invalid ship-to customer address). |
1112 |
Invalid HDR Ship To Cust Addr (invalid header ship-to customer address). |
1120 |
Invalid Ship From Bus Unit (invalid ship-from business unit). |
1121 |
Invalid Ship From Bus Unit Loc (invalid ship-from business unit location). |
1122 |
Invalid Ship From Location. |
1123 |
Missing Inventory BU Location (missing Inventory business unit location). |
1130 |
Missing Order Mgmt Bus Unit (missing Order Management business unit). |
1131 |
Invalid Ord Mgmt Bus Unit Loc (invalid Order Management business unit location). |
1132 |
Invalid Business Unit Loc (invalid business unit location). |
1140 |
Order Accept Address not found. |
1141 |
Order Origin Address not found. |
1142 |
Location Address is incomplete. |
1143 |
Original BU/INV does not exist. |
1200 |
Line(s) contain error. |
1210 |
Attached Bill(s) contain error. |
1220 |
Consolidation group has error. |
1300 |
Missing active Remit To Address. |
1310 |
Missing active Bill To Address. |
1350 |
Missing active Payment Terms. |
1360 |
Missing active Distribution CD. (missing active distribution code). |
1370 |
Missing Invoice Date. Rerun the program. |
1380 |
Error calculating Due Dates. |
1400 |
Missing Email ID for Contact. |
1410 |
Contact Not Set up for eBill Payment. |
1420 |
Contact has no row-level security on the Bill-To Customer of the bill. |
1430 |
Email Notification Failed. |
2033 |
Financial sanctions list match. |
2040 |
Invalid Tax Vendor Supplied. |
2041 |
Invalid action supplied. |
2042 |
Ship To address required. |
2043 |
No Geocode found - ShipTo ZIP (no geocode found – ship-to zip code). |
2044 |
Invalid ShipTo Geocode. |
2045 |
No Geocode found - ShipFr ZIP (no geocode found – ship-from zip code). |
2046 |
Invalid Ship From Geocode. |
2047 |
No Geocode found - Ord Acc ZIP (no geocode found - order acceptance address zip code). |
2048 |
Invalid Ord Accept Geocode (invalid order acceptance geocode). |
2050 |
Error calculating tax. |
2051 |
No Tax Provider Install data. |
2052 |
Tax Vendor Error. |
2053 |
No Tax Vendor Application. |
2054 |
Tax Upgrade Not Run. |
2100 |
Invalid Tax Code. |
2110 |
Interlink Tax Error. |
2111 |
Integration Gateway Error. |
2150 |
Invalid Tax Authority Code. |
2160 |
Incomplete Header VAT Defaults. |
2170 |
Incomplete Line VAT Defaults. |
2500 |
Missing Intrastat NatureOfTxn1 (missing intrastat nature-of-taxation one). |
2510 |
Missing Intrastat NatureOfTxn2 (missing intrastat nature-of-taxation two). |
2520 |
Missing Intrastat Fiscal Regm (missing intrastat fiscal regime). |
2600 |
Missing VAT Reporting Country. |
2650 |
Missing Supply State. |
2800 |
Excise and Sales Tax Defaulting Not Applied. |
2810 |
No Excise, Sales Tax, or VAT Rate Code. |
2820 |
No Excise Tax Rate Details. |
2830 |
No Sales Tax or VAT Rate Details. |
2840 |
Excise and/or Sales Tax Calculation Error. |
2850 |
No Tax Transaction Type. |
2860 |
Missing Excise Tax Parameter(s). |
2870 |
Missing Sales Tax or VAT Parameter(s). |
2880 |
No Excise Conversion Rate. |
3000 |
Missing EDI Profile. |
3100 |
Document Sequence Error. |
3110 |
Missing DOC TYPE on Billing BU (missing document type on billing business unit). |
3500 |
Missing Currency Rate Type. |
3530 |
Missing Euro exchange rates. |
The print processes consist of the data extract process, which copies bill data to temporary extract tables and print processes for generating each type of invoice. There are three types of print processes, which are SQR, Crystal and BI Publisher reports. Each printing process selects bills from the extract tables that meet the requirements for the type of invoice it generates.
The delivered SQR programs combine invoice selection, layout, and formatting in a single, modular program. Most of the SQR programs can generate several forms of invoice within a given layout; however, separate SQR programs are used for consolidated versus nonconsolidated invoices, portrait versus landscape invoices, and summarized versus detailed invoices. Thus one SQR program prints consolidated, portrait, and detailed invoices, while another prints consolidated, landscape, and detailed invoices. Not every combination is available in the delivered SQR programs. For example, summarized invoices are only provided in landscape format.
BI Publisher invoices have two parts:
An Application Engine program which selects the invoices to process.
Report definitions, or templates, which define the format and the layout of the invoice
The print processes and queries can be modified to produce tailored invoice forms.
See Understanding Invoice Forms.
This table lists the print process options:
Process Name |
Type |
Layout |
Prerequisites |
Notes |
BI_IVCEXT |
AE |
BIIVC000 |
Extracts billing data to the temporary extract tables. BI_IVCEXT must be run before any of the other print processes. |
|
BICA |
Crystal |
Portrait |
BI_IVCEXT |
PS/CA Contracts invoice. |
BICAA |
Crystal |
Portrait |
BI_IVCEXT |
PS/CA Contracts invoice with acceptgiro. |
BICLSUM |
Crystal |
Landscape |
BI_IVCEXT |
Summarization invoice. |
BICLSUMC |
Crystal |
Landscape |
BI_IVCEXT |
Consolidated summarization invoice. |
BIGIVCPN |
SQR |
Portrait |
BI_IVCEXT |
Grants invoices. |
BIIVCLC |
SQR |
Landscape |
BI_IVCEXT |
Consolidated invoices. |
BIIVCLN |
SQR |
Landscape |
BI_IVCEXT |
Nonconsolidated invoices. |
BIIVCPC |
SQR |
Portrait |
BI_IVCEXT |
Consolidated invoices. |
BIIVCPCA |
SQR |
Portrait |
BI_IVCEXT |
Consolidated acceptgiro invoices. |
BIIVCPN |
SQR |
Portrait |
BI_IVCEXT |
Nonconsolidated invoices. |
BIIVCPNA |
SQR |
Portrait |
BI_IVCEXT |
Nonconsolidated acceptgiro invoices. |
BIPRNC00 |
Crystal |
Landscape |
BI_IVCEXT |
Generic consolidated invoice. |
BIPRNC02 |
Crystal |
Landscape |
BI_IVCEXT |
PS/OM Order Management invoice. |
BIPRNCA0 |
Crystal |
Portrait |
BI_IVCEXT |
Generic consolidated acceptgiro invoice. |
BIPRNCA2 |
Crystal |
Portrait |
BI_IVCEXT |
Consolidated PS/OM Order Management acceptgiro invoice. |
BIPRNT00 |
Crystal |
Portrait |
BI_IVCEXT |
Generic invoice. Prints header notes at the bottom of the invoice. Prints line notes after the line. |
BIPRNT01 |
Crystal |
Landscape |
BI_IVCEXT |
PS/PC - Project Costing invoice. |
BIPRNT02 |
Crystal |
Landscape |
BI_IVCEXT |
PS/OM - Order Management invoice. This query subtotals (on LINE_TYPE), prints configuration detail, and prints product kit description. |
BIPRNTA0 |
Crystal |
Portrait |
BI_IVCEXT |
Generic acceptgiro invoice. |
BIPRNTA2 |
Crystal |
Portrait |
BI_IVCEXT |
Order Management acceptgiro invoice. |
BIPSA01 |
Crystal |
Portrait |
BI_IVCEXT |
PS/PSA01 - Projects By Employee invoice. |
BIPSA02 |
Crystal |
Portrait |
BI_IVCEXT |
PS/PSA02 - Projects By Activity invoice. |
BIPSA03 |
Crystal |
Portrait |
BI_IVCEXT |
PS/PSA03 - Project Detail invoice. |
BIPSAA1 |
Crystal |
Portrait |
BI_IVCEXT |
PS/PSA01 - Projects By Employee acceptgiro invoice. |
BIPSAA2 |
Crystal |
Portrait |
BI_IVCEXT |
PS/PSA02 - Projects By Activity acceptgiro invoice. |
BIPSAA3 |
Crystal |
Portrait |
BI_IVCEXT |
PS/PSA03 - Project Detail acceptgiro invoice. |
BISF108X |
SQR |
Portrait |
BI_IVCEXT |
Standard Forms 1080 and 1081. |
BISLSUM |
SQR |
Landscape |
BI_IVCEXT |
Summarization invoices. |
BISLSUMC |
SQR |
Landscape |
BI_IVCEXT |
Consolidated summarization invoices. |
BI_PRNXPN01 |
Application Engine (BI Publisher) |
Portrait |
BI_IVCEXT |
Sample BI Publisher invoice. |
BIPRNXPC01 |
Application Engine (BI Publisher) |
Portrait |
BI_IVCEXT |
Sample BI Publisher consolidated invoice. |
BI_XPSF103X |
Application Engine (BI Publisher) |
Portrait |
BI_IVCEXT |
Standard form 1034/1035 BI Publisher invoice. |
BIXCA |
BI Publisher |
Portrait |
BI_IVCEXT |
BI Publisher contracts invoice. |
BIXCLSUM |
BI Publisher |
Landscape |
BI_IVCEXT |
BI Publisher summarization invoice. |
BIXCLSUMC |
BI Publisher |
Landscape |
BI_IVCEXT |
BI Publisher consolidated summarization invoice. |
BIXPRNT00 |
BI Publisher |
Portrait |
BI_IVCEXT |
BI Publisher generic invoice. |
BIXPRNC00 |
BI Publisher |
Landscape |
BI_IVCEXT |
BI Publisher generic consolidated invoice. |
BIXPRNT01 |
BI Publisher |
Landscape |
BI_IVCEXT |
PS/PC - BI Publisher projects invoice. |
BIXPRNT02 |
BI Publisher |
Landscape |
BI_IVCEXT |
BI Publisher Order Management invoice. |
BIXPRNC02 |
BI Publisher |
Landscape |
BI_IVCEXT |
BI Publisher Order Management consolidated invoice. |
BIXPSA01 |
BI Publisher |
Portrait |
BI_IVCEXT |
BI Publisher project by employee invoice. |
BIXPSA02 |
BI Publisher |
Portrait |
BI_IVCEXT |
PS/PSA02 - BI Publisher projects by activity invoice. |
BIXPSA03 |
BI Publisher |
Portrait |
BI_IVCEXT |
PS/PSA03 - BI Publisher project detail invoice. |
PeopleSoft Billing supports two ways of paperless invoicing, Email Notification and Email invoice as attachment. You can specify the type to use on the invoice media field of the invoice.
The BIIVCEMAIL Email Notification process sends an email to billed customers for invoices that were finalized with an Invoice Media setting of Email Notification. You must have the eBill Payment product installed in order to choose this option. The process can be run independently from its own run control page, or it can be incorporated into one or more of the invoicing jobs. If incorporated, the Email Notification process must follow the BIIVC000 finalization process. This process will send an email to the billing contact on the bill. The email will contain a link to the eBill Payment application. When the customer clicks the link, they will be directed to the eBill Payment log in screen. Once logged in, the customer will be able to view and pay the invoice.
Alternatively, you can choose the Email invoice as attachment feature to accomplish paperless invoicing. The BI_XMLPBURST process sends an email to the customer with the invoice attached as a PDF. This feature is available only for BI Publisher invoices. The Review Email Invoice Log component can be used to review the processing results of the email attempts.
See Also
Running the Email Notification Process
During the invoice print processing, the system can generate an image of the formatted invoice for permanent storage. The image that is generated is in a PDF file format and is automatically attached to the bill header. The image is viewable from the Bill Summary or Supporting Documentation components. If the eBill Payment product is installed, the image can also be viewed by your customers from the self-service Bill Summary page.
The invoice image is produced by the BI_XMLPBURST program when the invoice is finalized. An image is not retained when a pro forma or a reprint is run for the invoice. This feature is available only for invoices that specify a BI Publisher invoice format. This feature is not available for invoices marked for the following Invoice Media delivery options: Invoice Notification, EDI and Federal Highway File because a formatted invoice is not produced for these media types.
The PeopleSoft Billing system is able to achieve batch emailing of invoices and retaining invoice images via the bursting feature of BI Publisher. During the Finalize and Print processing of invoices, the BI_XMLPBURST program is run which will generate a PDF file which contains multiple invoices, and break it up into smaller PDF files of one file per invoice. This means that for each distinct invoice, a separate PDF file will be generated.
The name of the PDF will be a concatenation of Business Unit, Invoice and sequence number. These bursted files are stored in a temporary working directory which is deleted once the processing completes. For Windows, the working directory is specified in the TMP environment variable of the process scheduler. For UNIX environments, the working directory is specified in the PS_FILEDIR environment variable.
The burst program will loop through each bursted file and either email the PDF file, attach the PDF file or both depending on your system settings. If the invoice file is to be emailed, then a row is inserted into an email log table to track the email attempt and the results.
Note. The email invoice as attachment and retain invoice image features do not support the SF1034/1035 BI Publisher invoice.
After you generate a set of invoices, several processes can be run to create accounting entries.
This table lists the Billing post-invoice processes in alphabetical order:
Note. Processes not listed here may be required when finalized invoice data is sent back to integrated applications such as Project Costing and Contracts.
Process Name |
Type |
Prerequisites |
Notes |
BICRC000 |
AE |
BIIVC000 |
Credit card processing. |
BICURCNV |
AE |
BIIVC000 and BICRC000 (when credit card payments are accepted). |
Billing currency conversion. Warning! Do not run the Currency Conversion process concurrently. If you run two Currency Conversion processes at the same time, one or both processes may fail. See Understanding the Currency Conversion Process (BICURCNV). |
BIGNAP01 |
SQR |
BIPRELD |
Generate AP vouchers. |
BILDAR01 |
SQR |
BIPRELD |
Load AR pending items. |
BILDGL01 |
SQR |
BIPRELD |
Load GL interface. |
BIPCC000 |
AE |
Billing to PC/CA Interface. |
|
BIPRELD |
AE |
BICURCNV |
Billing preload process. |
FS_BP |
AE |
BILDGL01 |
Commitment Control Budget Check. |
The delivered invoicing jobs combine invoicing processes and subjobs to provide a range of options for generating invoices. You should reconfigure the delivered jobs to suit the business needs of your company.
Note. If the Billing Interface process is run as a part of a job, such as Indirect Invoicing, that is initiated by an upstream product, such as OM, then the RANGE_SELECTION_ID field should be added to the Bill By identifier. This field allows the billing processes to identify which transaction needs to be processed.
Note. Subjobs in the Components column are indicated by emphasized text.
This table lists the jobs that are provided:
Job Name |
Classification |
Description |
Components |
BICPJ00 |
Print subjob |
Print nonconsolidated Crystal invoices |
|
BICPJ00C |
Print subjob |
Print consolidated Crystal invoices |
|
BICPJ10C |
|
Print consolidated SQR invoices |
|
BICPJ11C |
|
Print portrait SQR invoices |
|
BICPJ40C |
|
Print consolidated Crystal invoices |
|
BICPJA00 |
Print subjob |
Print Crystal acceptgiro invoices |
|
BICPJA0C |
Print subjob |
Print consolidated Crystal acceptgiro invoices |
|
BIDIRIV2 |
Interface, preprocess, finalize, and print |
Direct invoicing (no post processes) See The BIDIRIVC Jobs. |
|
BIDIRIVC |
Interface, preprocess, finalize, print, and post process |
Direct invoicing See The BIDIRIVC Jobs. |
|
BIINIU |
Interface, preprocess, finalize, print, and post process |
InterUnit inventory transfer See The BIINIU Job. |
|
BIINIU2 |
Interface, preprocess, finalize, and print |
InterUnit inventory transfer (no Crystal or post processes) See The BIINIU Job. |
|
BIINIU3 |
Interface, preprocess, finalize, print SQR, and post process |
InterUnit inventory transfer (No Crystal processes) See The BIINIU Job. |
|
BIJOB01 |
Finalize and print |
Finalize and print SQR, BI Publisher, and Crystal invoices |
|
BIJOB02 |
Finalize and print |
Finalize and print consolidated SQR, BI Publisher, and Crystal invoices |
|
BIJOB03 |
Finalize, print, and post-process |
Single action. Print SQR, BI Publisher, Crystal, and acceptgiro invoices |
|
BIJOB03K |
Finalize, print, and post-process |
Single action. Print SQR, BI Publisher, Crystal, and acceptgiro invoices with commitment control |
|
BIJOB04 |
Finalize, print, and post-process |
Single Action. Print consolidated SQR, BI Publisher, Crystal, and acceptgiro invoices |
|
BIJOB04K |
Finalize, print, and post-process |
Single Action. Print consolidated SQR, BI Publisher, Crystal, and acceptgiro invoices with commitment control |
|
BIJOB05 |
Post-process |
Currency conversion, preload accounting entries, and load AR |
|
BIJOB06 |
Post-process |
Currency conversion, preload accounting entries, and load GL |
|
BIJOB06K |
Post-process |
Currency conversion, preload accounting entries, and load GL with commitment control |
|
BIJOB07 |
Interface and preprocess |
Process RMA adjustments through the Billing interface and VAT defaults |
|
BIJOB08 |
Finalize and print |
Single Action. Print SQR, Crystal, and acceptgiro invoices without post-processes |
|
BIJOB09 |
|
Extract and print generic Crystal invoices |
|
BIJOB10 |
|
Extract and print Crystal PS/PC invoices |
|
BIJOB11 |
|
Extract and print Crystal PS/OM invoices |
|
BIJOB12 |
|
Extract and print consolidated Crystal invoices |
|
BIJOB13 |
|
Extract and print consolidated PS/OM invoices |
|
BIJOB14 |
|
Extract and print Crystal PS/CA invoices |
|
BIJOB15 |
|
Extract and print Crystal PS/PSA01 invoices |
|
BIJOB16 |
|
Extract and print Crystal PS/PSA02 invoices |
|
BIJOB17 |
|
Extract and print Crystal PS/PSA03 invoices |
|
BIJOB18 |
Postprocess |
Currency conversion and preload accounting entries |
|
BIJOB19 |
Reprint |
Reprint invoices |
|
BIJOB20 |
|
Print portrait SQR invoices |
|
BIJOB21 |
|
Print portrait consolidated SQR invoices |
|
BIJOB22 |
|
Print landscape SQR invoices |
|
BIJOB23 |
|
Print landscape consolidated SQR invoices |
|
BIJOB24 |
|
Print BI Publisher invoices for eBill Payment |
|
BIJOB25 |
|
Print BI Publisher consolidated invoices for eBill Payment |
|
BIJOB26 |
|
Print SF 1034/1035 BI Publisher invoices for eBill Payment |
|
BIJOB27 |
|
Print BI Publisher PS/CA invoice |
|
BIJOB30 |
|
Print BI Publisher invoice |
|
BIJOB31 |
|
Print BI Publisher consolidated invoice |
|
BIJOB32 |
|
Print BI Publisher PS/PC invoice |
|
BIJOB33 |
|
Print BI Publisher PS/OM invoice |
|
BIJOB34 |
|
Print BI Publisher PS/OM consolidated invoice |
|
BIJOB35 |
|
Print BI Publisher PSA01 invoice |
|
BIJOB36 |
|
Print BI Publisher PSA02 invoice |
|
BIJOB37 |
|
Print BI Publisher PSA03 Invoice |
|
BIJOB50 |
Finalize, print, and post-process |
Single Action. Print Project Costing and Contracts invoices |
|
BIJOB51 |
Finalize and print |
Finalize and print Crystal invoices |
|
BIJOB52 |
Finalize and print |
Finalize and print consolidated Crystal invoices |
|
BIJOBI01 |
Interface and preprocess |
Process Billing interface and VAT Defaults |
|
BIJOBP01 |
Pro forma |
Print pro formas |
|
BIJOBP02 |
Pro forma |
Print consolidated pro formas |
|
BIJOBP03 |
Pro forma |
Print pro forma Note. To run BIPJOB03, click the Proforma button on the online bill entry pages. |
|
BIJOBP51 |
Pro forma |
Print Crystal pro formas |
|
BIJOBP52 |
Pro forma |
Print consolidated Crystal pro formas |
|
BIPJ10 |
|
Print/SQR invoices |
|
BIPJ11 |
|
Print portrait SQR invoices |
|
BIPJ20 |
|
Print Grants SQR invoices |
|
BIPJ30 |
|
Print SQR SF1080/81 forms |
|
BIPJ40 |
|
Print Crystal invoices |
|
BIPJ50 |
|
Print BI Publisher invoices |
|
BISPJ00 |
Print subjob |
Print SQR invoices |
|
BISPJ00C |
Print subjob |
Print SQR invoices |
|
BIXPJ00C |
|
Print BI Publisher consolidated invoices |
|
DIRAUTO |
Interface, preprocess, finalize, print, and post-process |
Print Order Management Direct Invoicing invoices with automatic approval See The DIRAUTO Job. |
|
DIRCTIV2 |
Interface, preprocess, finalize, and print |
Print Order Management Direct Invoicing invoices (no post-processes) See The DIRCTIVC Job. |
|
DIRCTIV3 |
Interface, preprocess, finalize, print SQR, and post-process |
Print Order Management Direct Invoicing invoices (no Crystal processes) See The DIRCTIVC Job. |
|
DIRCTIVC |
Interface, preprocess, finalize, print, and post-process |
Print Order Management Direct Invoicing invoices See The DIRCTIVC Job. |
|
Direct invoicing jobs streamline the billing process by combining several steps in the collection and processing of billing activity from other source systems. The PeopleSoft Billing user preferences that you set up on the User Preferences - Billing page as well as where you initiate direct invoicing determine which jobs are initiated.
This section discusses the details of:
The DIRCTIVC job.
The BIDIRIVC jobs.
The BIINIU job.
The DIRAUTO job.
Use the DIRCTIVC job (initiated by clicking the Run Process button on the Shipping/Issues - Order Summary page), to create invoices for sales orders originating from PeopleSoft Order Management. The DIRCTIV2 job is similar to DIRCTIVC, but it contains no Crystal or post-invoicing processes. Likewise, the DIRCTIV3 job contains no Crystal processes, but it does contain post-invoicing processes.
This table lists all of the processes that are part of the DIRCTIVC job used in PeopleSoft Inventory:
Process |
What Is Selected Now? |
What Should Be Processed Later? |
OM Billing Interface (OM_BILL) |
All activity for Ship ID. |
Nothing. |
Billing Interface (BIIF0001) |
All activity for INTFC ID. To process direct invoicing through the Billing Interface process, the Range Selection ID and Direct Invoicing fields must be part of the explicit bill-by criteria and must be populated on the interface transaction lines. Direct invoicing bills are created with a status of RDY (ready). |
All activity for INTFC ID with errors. |
VAT Defaulting (value-added tax) (BIPVAT00) |
Applies defaults at the bill header and line levels for VAT fields. Selects all VAT bills with range selection ID specified by the direct invoicing job and with Defaults Applied = No. Status changes from RDY to HLD if defaulting fails. Defaults applied change to Yes if defaulting succeeds. If your business never processes VAT invoices, you can remove this step from the BIDIRIVC job. |
All VAT bills with VAT defaulting errors. |
Invoice Finalization (BIIVC000) |
All bills for range selection ID with direct invoice option On. Status changes to:
|
All bills for range selection ID with direct invoice option Off. The status of activity not selected remains RDY. Any bills for the range selection ID that were found to have errors. Any pending credit card transactions that were created. |
Invoice Extract Process (BI_IVCEXT) |
Selects all printable bills with range selection ID specified by the direct invoicing job. All printable bills will be extracted into the billing extract tables. This process also prepares the run control records for the SQR, Crystal and BI Publisher invoice print process. |
|
Invoice Printing (BISPJ00, BIXPJ00, BICPJ00, BICPJA00, BISLSUM, BICLSUM) |
All printable bills extracted by the Invoice Extract process. The system prints these bills using one of several processes, depending on the invoice form. All bills get marked as printed and get assigned a print date. All bills that are marked for Email invoice as attachment will be emailed by the BI_XMLPBURST process and will get marked as email sent. Also, the invoice image is attached to the bill header by the BI_XMLPBURST process for bills that are marked for retain invoice image. |
|
Billing Currency Conversion (BICURCNV) |
All bills for range selection ID with a status of FNL or INV. Your business practices may dictate different timing for running currency conversion. However, currency conversion must be completed before billing activity can be interfaced to PeopleSoft Receivables or General Ledger. |
All bills for range selection ID with direct invoice option Off. |
Pre-Load (BIPRELD) |
All bills for range selection ID with a status INV and which have completed currency conversion. |
All bills for range selection ID with status RDY or FNL. All bills for ship ID with invoice and currency conversion errors. |
Load Receivables (BILDAR01) |
All bills for range selection ID with a status INV and which have completed currency conversion. Your business practices may dictate different timing for loading to PeopleSoft Receivables. You can remove this processes from the DIRCTIVC job. |
All bills for range selection ID with status RDY or FNL. All bills for ship ID with invoice and currency conversion errors. |
Load General Ledger (BILDGL01) |
All bills for range selection ID with status INV and which have completed currency conversion. Your business practices may dictate different timing for loading to PeopleSoft General Ledger. You can remove this process from the DIRCTIVC job. |
All bills for range selection ID with status RDY or FNL. All bills for ship ID with invoice and currency conversion errors. |
Generate AP Voucher (BIGNAP01) |
All bills for range selection ID with status INV and which have completed currency conversion. |
All bills for range selection ID with status RDY or FNL. All bills for ship ID with invoice and currency conversion errors. |
Warning! If you do not click the Run button on the Shipping/Issues - Order Summary page, you must run all of the processes individually.
See Also
The BIDIRIVC and BIDIRIV2 jobs carry out the Billing portion of the Projects and Contracts to Billing interface process. These jobs are normally called from the CA_BI_INTFC job as part of the larger process of moving bill data from Projects and Contracts to Billing and back. The BIDIRV2 job is identical to the BIDIRIVC job, except that it contains no post-invoicing processes.
This table lists all of the processes that are part of the BIDIRIVC and BIDIRIV2 jobs used in Contracts and Project Costing:
Process |
What Is Selected Now? |
What Should Be Processed Later? |
Billing Interface (BIIF0001) |
All activity for INTFC ID. To process direct invoicing through the Billing Interface process, the Range Selection ID and Direct Invoicing fields must be part of the explicit bill-by criteria and must be populated on the interface transaction lines. Direct invoicing bills are created with a status of RDY (ready). |
All activity for INTFC ID with errors. |
VAT Defaulting (BIPVAT00) |
Applies defaults at the bill header and line levels for VAT fields. Selects all of the VAT bills with Defaults Applied = No. Status changes from RDY to HLD if defaulting fails. Defaults applied changes to Yes if defaulting succeeds. If your business never processes VAT invoices, you can remove this step from the BIDIRIVC job. |
All VAT bills with VAT defaulting errors. |
Invoice Finalization (BIIVC000) |
All bills for range selection ID with direct invoice option On. Status is changes to:
|
All bills for range selection ID with direct invoice option Off. The status of activity not selected remains RDY. Any bills for the range selection ID that were found to have errors. Need to process any pending credit card transactions that were created. |
Invoice Extract Process (BI_IVCEXT) |
Selects all printable bills with range selection ID specified by the direct invoicing job. All printable bills will be extracted into the Billing extract tables. This process also prepares the run control records for the SQR, Crystal, and BI Publisher invoice print processes. |
|
Invoice Printing (BISPJ00, BICPJ00, BICPJA00, BISLSUM, BICLSUM, BIGIVCPN, BIXPJ00) |
All printed bills extracted by the Invoice Extract process. The system prints these bills using one of several processes, depending on the invoice form. All bills get marked as printed and get assigned a print date. All bills that are marked for Email invoice as attachment will be emailed by the BI_XMLPBURST process and will get marked as email sent. Also, the invoice image is attached to the bill header by the BI_XMLPBURST process for bills that are marked for retain invoice image. |
|
Billing Currency Conversion (BICURCNV) |
All bills for range selection ID with a status of FNL or INV. Your business practices may dictate different timing for running currency conversion. However, currency conversion must be completed before billing activity can be interfaced to PeopleSoft Receivables or General Ledger. |
All bills for range selection ID with direct invoice option Off. |
Pre-Load (BIPRELD) |
All bills for range selection ID with a status INV and which have completed currency conversion. |
All bills for range selection ID with status RDY or FNL. All bills for ship ID with invoice and currency conversion errors. |
Load Receivables (BILDAR01) |
All bills for range selection ID with a status INV and which have completed currency conversion. Your business practices may dictate different timing for loading to PeopleSoft Receivables. You can remove this process from the BIDIRIVC job. |
All bills for range selection ID with status RDY or FNL. All bills for range selection ID with invoice and currency conversion errors. |
Load General Ledger (BILDGL01) |
All bills for range selection ID with status INV and which have completed currency conversion. Your business practices may dictate different timing for loading to PeopleSoft General Ledger. You can remove this process from the BIDIRIVC job. |
All bills for range selection ID with status RDY or FNL. All bills for range selection ID with invoice and currency conversion errors. |
BISF108X |
Print Standard forms 1080 and 1080X. |
|
Generate AP Voucher (BIGNAP01) |
All bills for range selection ID with status INV and which have completed currency conversion. |
All bills for range selection ID with status RDY or FNL. All bills for range selection ID with invoice and currency conversion errors. |
See Also
Integrating with PeopleSoft Contracts, Project Costing, Grants, and Pay/Bill Management
You can initiate the BIINIU job from the Express Issue and Shipping/Issues - Order Summary page to create invoices for intercompany transfers.
The first process the system runs for this job is the Transfer Order Billing Load process (INS6300), which extracts all intercompany transfer order information with the same shipping identifier from the inventory shipping table (IN_DEMAND) and loads that information into the PeopleSoft Billing Interface table (INTFC_BI). Once this information is within PeopleSoft Billing, it is ready for subsequent processing. The BIINIU2 job is similar to BIINIU, but contains only SQR print processing and no post-invoicing processes. Likewise, the BIINIU3 job contains only SQR print processes, but does contain the post-invoicing processes.
You initiate the Transfer Order Billing Load process from the PeopleSoft Inventory Express Issue and Shipping/Issues components, as well as from the InterUnit Bill Load Process page.
Note. All shipment activity for a shipping identifier is loaded to PeopleSoft Billing even if the direct invoice option is not selected.
This table lists all of the processes that are part of the BIINIU job used in PeopleSoft Inventory:
Process |
What Is Selected Now? |
What Should Be Processed Later? |
Transfer Order Billing Load (INS6300) |
All activity for ship ID. |
Nothing. |
Billing Interface (BIIF0001) |
All activity for INTFC ID. For intercompany transfers with direct invoicing selected at the customer level, the Billing Interface process creates bills in RDY status, unless there are errors. For intercompany transfers without direct invoicing selected, the Billing Interface process creates bills according to the status that you defined on the Billing Bill By Identifier page: New, Pending, or Hold. |
All activity for INTFC ID with errors. |
VAT Defaulting (BIPVAT00) |
Applies defaults at the bill header and line levels for VAT fields. Selects all VAT bills with Defaults Applied = No. Status changes from RDY to HLD if defaulting fails. Defaults applied change to Yes if defaulting succeeds. If your business never processes VAT invoices, you can remove this step from the BIINIU job. |
All VAT bills with VAT defaulting errors. |
Invoice Finalization (BIIVC000) |
All bills for range selection ID with direct invoice option On. Status is changes to:
|
All bills for range selection ID with direct invoice option Off. The status of activity is RDY. Any bills for the range selection ID that were found to have errors. Any pending credit card transactions that were created. |
Invoice Extract Process (BI_IVCEXT) |
Selects all printable bills with range selection ID specified by the direct invoicing job. All printable bills will be extracted into the Billing extract tables. This process also prepares the run control records for the SQR, Crystal, and BI Publisher invoice print processes. |
|
Invoice Printing (BISPJ00, BICPJ00, BICPJA00, BISLSUM, BICLSUM, BIXPJ00) |
All printed bills extracted by the Invoice Extract process. The system prints these bills using one of several processes, depending on the invoice form. All bills get marked as printed and get assigned a print date. All bills that are marked for Email invoice as attachment will be emailed by the BI_XMLPBURST process and will get marked as email sent. Also, the invoice image is attached to the bill header by the BI_XMLPBURST process for bills that are marked for retain invoice image. |
|
Billing Currency Conversion (BICURCNV) |
All bills for range selection ID with a status of FNL or INV. Your business practices may dictate different timing for running currency conversion. However, currency conversion must be completed before billing activity can be interfaced to PeopleSoft Receivables or General Ledger. |
All bills for range selection ID with direct invoice option Off. |
Pre-Load (BIPRELD) |
All bills for range selection ID with a status INV and which have completed currency conversion. |
All bills for range selection ID with status RDY or FNL. All bills for ship ID with invoice and currency conversion errors. |
Load Receivables (BILDAR01) |
All bills for range selection ID with a status INV and which have completed currency conversion. Your business practices may dictate different timing for loading to PeopleSoft Receivables. You can remove this process from the BIINIU job. |
All bills for range selection ID with status RDY or FNL. All bills for ship ID with invoice and currency conversion errors. |
Load General Ledger (BILDGL01) |
All bills for range selection ID with status INV and which have completed currency conversion. Your business practices may dictate different timing for loading to PeopleSoft General Ledger. You can remove this process from the BIINIU job. |
All bills for range selection ID with status RDY or FNL. All bills for ship ID with invoice and currency conversion errors. |
Generate AP Voucher (BIGNAP01) |
All bills for range selection ID with status INV and which have completed currency conversion. |
All bills for range selection ID with status RDY or FNL. All bills for ship ID with invoice and currency conversion errors. |
See Also
Transferring Stock Between Business Units
Creating Orders for Fulfillment
You can initiate the DIRAUTO job from the Ship and Invoice Process page to create invoices for sales orders (originating from PeopleSoft Order Management) and intercompany transfers. DIRAUTO takes stock requests that are confirmed on the Material Picking Feedback page and runs all of the remaining processes to invoicing. You must select the autoship option for any stock requests that you want to process.
This table lists all of the processes that are part of the DIRAUTO job used in PeopleSoft Inventory:
Process |
What IS Selected Now? |
What Should Be Processed Later? |
Picking Confirmation (IN_FUL_CONF) |
All lines that match the selection criteria on the Ship and Invoice Process page. |
All lines not marked as autoship, as well as any lines that could not be shipped automatically. |
Packing Slip (INS6500) |
All lines that were shipped in the picking confirmation step. |
Nothing. |
Depletion (INPDDEPL) |
All lines that were shipped in the picking confirmation step. |
Nothing. |
Advanced Shipping Notices (IN_PUB_MSG) |
All lines that were shipped in the picking confirmation step. |
Nothing. |
OM Billing Interface (OM_BILL) |
All lines originating from the PeopleSoft Order Management system that were depleted in the depletion step. |
Nothing. |
Transfer Order Billing Load (INS6300) |
All activity for ship ID. |
Nothing. |
Billing Interface (BIIF0001) |
All activity for INTFC ID. To process direct invoicing through the Billing Interface process, the Range Selection ID and Direct Invoicing fields must be part of the explicit bill-by criteria and must be populated on the interface transaction lines. Direct invoicing bills are created with a status of RDY (ready). |
All activity for INTFC_ID with errors. |
VAT Defaulting (BIPVAT00) |
Applies defaults at the bill header and line levels for VAT fields. Selects all VAT bills with Defaults Applied = No. Status changes from RDY to HLD if defaulting fails. Defaults applied change to Yes if defaulting succeeds. If your business never processes VAT invoices, you can remove this step from the DIRAUTO job. |
All VAT bills with VAT defaulting errors. |
Invoice Finalization (BIIVC000) |
All bills for range selection ID with direct invoice option On. Status changes to:
|
All bills for range selection ID with direct invoice option Off. The status of activity is RDY. Any bills for the range selection ID that were found to have errors. Any pending credit card transactions that were created. |
Invoice Extract Process (BI_IVCEXT) |
Selects all printable bills with range selection ID specified by the direct invoicing job. All printable bills will be extracted into the Billing extract tables. This process also prepares the run control records for the SQR, Crystal, and BI Publisher invoice print processes. |
|
Invoice Printing (BISPJ00, BICPJ00, BISLSUM, BICLSUM, BIXPJ00) |
All printed bills extracted by the Invoice Extract process. The system prints these bills using one of several processes, depending on the invoice form. All bills get marked as printed and get assigned a print date. All bills that are marked for Email invoice as attachment will be emailed by the BI_XMLPBURST process and will get marked as email sent. Also, the invoice image is attached to the bill header by the BI_XMLPBURST process for bills that are marked for retain invoice image. |
|
Billing Currency Conversion (BICURCNV) |
All bills for range selection ID with a status of FNL or INV. Your business practices may dictate different timing for running currency conversion. However, currency conversion must be completed before billing activity can be interfaced to PeopleSoft Receivables or General Ledger. |
All bills for range selection ID with direct invoice option Off. |
Pre-Load (BIPRELD) |
All bills for range selection ID with a status INV and which have completed currency conversion. |
All bills for range selection ID with status RDY or FNL. All bills for ship ID with invoice and currency conversion errors. |
Load Receivables (BILDAR01) |
All bills for range selection ID with a status INV and which have completed currency conversion. Your business practices may dictate different timing for loading to PeopleSoft Receivables. You can remove this process from the DIRAUTO job. |
All bills for range selection ID with status RDY or FNL. All bills for ship ID with invoice and currency conversion errors. |
Load General Ledger (BILDGL01) |
All bills for range selection ID with status INV and which have completed currency conversion. Your business practices may dictate different timing for loading to PeopleSoft General Ledger. You can remove this process from the DIRAUTO job. |
All bills for range selection ID with status RDY or FNL. All bills for ship ID with invoice and currency conversion errors. |
Generate AP Voucher (BIGNAP01) |
All bills for range selection ID with status INV and which have completed currency conversion. |
All bills for range selection ID with status RDY or FNL. All bills for Ship ID with invoice and currency conversion errors. |
See Also
Creating Shipping Documentation
Configuration of Order Fulfillment
This section provides an overview of spreadsheet invoice import, lists prerequisites, and discusses how to:
Configure spreadsheet invoices.
Set up spreadsheet invoice import.
Enter spreadsheet invoices.
Post an invoice.
Review the posted data.
Run the billing interface process.
Correct data errors.
The Spreadsheet Import to Billing Interface is used to enter invoice data in a worksheet format and have an xml file generated automatically. The xml file can be posted into the PeopleSoft Billing Interface tables via Integration Broker or it can be used with a third-party application.
The worksheet can be personalized to display only the specific fields needed for data entry.
Process Flow
The following diagram illustrates the process flow to create an invoice:
Before you can enter and import spreadsheet invoice, you must:
Copy the Excel workbook to a folder on your workstation.
Set up your Microsoft Excel to accept macros.
Configure Integration Broker and Excel workbook.
Use Microsoft Office Excel 2007 version or higher.
Page Name |
Definition Name |
Navigation |
Usage |
Quick Configuration |
PTIB_ADMIN |
PeopleTools, Integration Broker, Configuration, Quick Configuration |
Displays the information on the gateway and the domains. |
Nodes |
IB_NODE |
PeopleTools, Integration Broker, Integration Setup, Nodes |
Displays the information on the nodes. |
Routings |
IB_ROUTINGDEFN |
PeopleTools, Integration Broker, Integration Setup, Routings |
Displays the routing information. |
Service Operations |
IB_SERVICE |
PeopleTools, Integration Broker, Integration Setup, Service Operations |
Displays information on the service operations. |
Queues |
IB_QUEUEDEFN |
PeopleTools, Integration Broker, Integration Setup, Queues |
Displays information on the queue definitions. |
Review Pending Transactions |
INTFC_BI |
Billing, Interface Transactions, Review Pending Transactions |
Display data for interface transactions in the INTFC_BI table. |
Correct Interface Errors |
INTFC_BI |
Billing, Interface Transaction, Correct Interface Errors |
Display data for interface transactions in the INTFC_BI table. |
This section discusses the configurations required for the Excel workbook and the PeopleSoft Integration Broker to communicate with each other.
Configuring the Integration Broker
Follow the given steps to set up the Integration Broker:
Access the Quick Configuration page (PeopleTools, Integration Broker, Configuration, Quick Configuration). This page displays the information on the gateway and the domains. Verify a ping is successful by clicking the Ping Gateway button. Ensure that the domains to be used are in the Active status.
Access the Nodes page (PeopleTools, Integration Broker, Integration Setup, Nodes). Display node PSFT_BI_INTFC_XML. Click the Connectors tab. Ping the external and the local node to verify the connection is successful.
Access the Routings page (PeopleTools, Integration Broker, Integration Setup, Routings) to activate the BI_INTFC_UPLOAD routing.
Access the Service Operations page (PeopleTools, Integration Broker, Integration Setup, Service Operations). Select the Active checkbox on the General tab to activate the Service Operation BI_INTFC_UPLOAD. Set the status as Active on the Handlers tab and verify that the status for the BI_INTFC_UPLOAD service operation is active on the Routings tab.
Access the Queues page (PeopleTools, Integration Broker, Integration Setup, Queues). Set the Queue Status to Run for the queue BILLING_INTERFACE_UPLOAD and the save the page.
Configuring the Excel Workbook
An Excel workbook is used for the generation of the XML file that is passed to the Integration Broker. The Excel book is comprised of three worksheets: Template, Data Sheet and Example.
Follow the given steps to set up the Excel workbook:
Access the Template sheet in the Excel workbook. Enter the Machine Name and the Integration Gateway. Use PSIGW as the Integration Gateway.
Enter PSFT_BI_INTFC_XML as the From Node.
Enter the local node of the database as the To Node value.
The generated URL field will be automatically populated.
Access the Spreadsheet Invoice - Template worksheet by clicking the BillingInterfaceExcelUpload.xlsm file delivered with your PeopleSoft products. You set the defaults and set up your invoice spreadsheets for importing into PeopleSoft Billing on the Template worksheet.
The Template worksheet in the Spreadsheet Invoice workbook contains all of the available fields that you can use on the Data Sheet worksheet to enter invoice data. However, since customers typically require a subset of fields based on the business requirements and the user role, this sheet can be customized to restrict the visibility of certain fields.
Machine Name, Integration Gateway, From Node, and To Node |
Enter machine name, integration gateway, from node, and to node. The data entered in these fields creates a URL string. Note. Oracle delivers the From Node as PSFT_BI_INTFC_XML. The Integration Broker subscribes only to a single default local node. The To Node is the URL for the database that you want to receive the invoice. |
Generated URL |
Displays the URL generated from the host name, integration gateway, routing alias and node entered. The XML file created is posted to the defined URL. |
Record |
Displays the Billing Interface table name associated with the field. |
Record Type |
Displays the record type associated with the field. Values are:
|
Field |
Displays the name of the field. |
Label |
Displays the label of the field. |
Field Type |
Displays the type of the field. Types include Character, Date, and Number. |
Field Length |
Displays the length of the field. |
Field Visibility on Data Sheet |
Selected fields will be visible on the Data Sheet worksheet. |
Select All |
Click this button to select all the fields on the Template sheet. All the check boxes on the Field Visibility on Data Sheet row will be selected. |
Deselect All |
Click this button to deselect all the fields on the Template sheet. All the check boxes on the Field Visibility on Data Sheet row will be deselected. You can also manually select or deselect individual fields based on the requirement. |
Update Data Sheet |
Click to update the Data Sheet worksheet with the selected fields. |
Hide Template |
Select to hide the Template worksheet. The Template Visibility Button also acts in union with the Hide Template button. |
Template Visibility |
If the Template Visibility Button option is Visible, clicking Hide Template button will hide the template and only the data sheet will be visible. The user can click Display Template from the Data Sheet to redisplay the template. If the Template Visibility Button option is Hidden, clicking Hide Template button will hide the template and only the data sheet will be visible. The user does not have an option to redisplay the template. If the template is visible to the users, they can make changes to the fields available on the data sheet. An administrator should determine which fields are to be available and whether users should be granted access to change those fields if required. |
Access the Spreadsheet Invoice - Data Sheet worksheet by clicking the BillingInterfaceExcelUpload.xlsm file delivered with your PeopleSoft products. You use the Data Sheet worksheet to create and import invoice data.
Each row on the sheet can contain an entry for only one table.
Generate XML |
Click to create an XML file. This XML file can be edited and transferred to the PeopleSoft system via a third-party application. The Excel Save As window appears when you click the Generate XML button. Indicate the file name and the location where you want to save it. For example, you can write the data to an FTP site and create another process to post the XML file to the URL. When Integration Broker is active, it posts the XML data to the system making the data available for processing by the batch Billing Interface Excel Upload process. |
Generate XML & Post |
Click to create an XML file and post the file to the URL defined in the Template worksheet. The Excel Save As window appears when you click the Generate XML and Post button. Save the XML file to a folder to instantly post the XML file to the URL. |
Display Template |
Click to display the Template sheet if it is hidden. This button is displayed only if the administrator has set the Template Visibility Button option to Visible on the template. |
Access the Spreadsheet Invoice - Example worksheet by clicking the BillingInterfaceExcelUpload.xlsm file delivered with your PeopleSoft products. The Example worksheet acts as a guideline for the user on how to enter data.
Follow the given steps to post an invoice:
Enter data for parent record and the child record on the respective rows on the data sheet.
If data is entered in an incorrect location, the entire row will be highlighted to indicate the problem.
Click Generate XML & Post button to populate the Billing Interface tables.
Click OK to the message displayed.
Save the XML file. Each time a new file is saved, the previous file is overwritten.
You will receive a confirmation message that the data has posted after the xml file is saved.
The data is processed via the Integration Broker. The BILLING_INTERFACE_UPLOAD message and its associated subscription contract must be in Done status for the data to be updated into the interface tables. Check the application message monitor to verify that the Status is Done.
Access the Review Pending Transactions page (Billing, Interface Transactions, Review Pending Transactions). Review the data posted by either querying the tables or viewing it online.
Access the Process Billing Interface page (Billing, Interface Transactions, Process Billing Interface).
Create the invoice by running the Billing Interface to post the data.
Access the Message Log page (PeopleTools, Process Scheduler, Process Monitor) to check if any of the data returned an error for the particular process instance.
Access the Correct Interface Errors page (Billing, Interface Transaction, Correct Interface Errors) to rectify any errors. Update the data and rerun the Billing Interface.
An alternate method to rectify errors is to update the Data Sheet on the workbook with correct data and repost the XML file.
Note. This method should be used during testing phase only as a new interface ID will be generated and data for the previous interface ID will remain in the tables.
Consider both the human and the machine factors when configuring and optimizing invoicing jobs. Optimizing for the human factor requires matching the job definitions to natural work practices. Removing unwanted jobs can make the system easier to operate and reduce user errors. Optimizing for the machine factor requires configuring the jobs to make efficient use of system resources. To improve the performance of the Billing jobs, consider the following:
The delivered invoicing jobs typically include processes to print a range of invoice types. If you never print some of the invoice types, remove those print processes from the job.
As invoices are extracted, printed, and reprinted, the invoice extract tables and print process run control tables will grow in size. Over time, these tables can become large enough to degrade the performance of the extract and print processes. To maintain performance, the Billing Delete Data process (BIDELDATA) should be run regularly. It is also helpful to recompute the database statistics on these tables on a regular basis.
While most of the steps in generating an invoice must be carried out in sequence, the invoice printing processes can be run in parallel.
See PeopleTools PeopleBook: Process Scheduler, Defining Jobs and JobSets.
In some cases, you can decrease the processing time of jobs containing many processes by reducing the Process Scheduler sleep time.
See PeopleTools PeopleBook: PeopleSoft Process Scheduler, Setting Server Definitions.
Review the document, Performance Recommendations for PeopleSoft Billing, and implement the recommendations appropriate for your PeopleSoft implementation.
Invoice Job Configuration Example
In this example, we will configure the BIJOB01 job to print only Project Costing and Contracts invoices. As delivered, the BIJOB01 job has the following components:
BIIVC000 (Finalization)
BI_IVCEXT (Extract)
BISPJ00 (SQR invoices)
BIXPJ00 (BI Publisher invoices)
BICPJ00 (Crystal invoices)
BISLSUM (Summarized SQR invoices)
BICLSUM (Summarized Crystal invoices)
BIGIVCPN (Grants invoices)
Summarized, Grants, and BI Publisher invoices are not needed, so these can be removed from the job definition. When properly configured, the BIJOB01 definition should look like this:
BIIVC000
BI_IVCEXT
BISPJ00
BICPJ00
BICPJ00 and BISPJ00 are subjobs that contain a number of print processes, so they must also be modified. These jobs contain the following components:
BICPJ00 (Crystal invoices) |
BICSPJ00 (SQR invoices) |
|
|
The BIPRNT00, BIPRNT02, and BIIVCPNA processes create invoices that are not used, so they should be removed:
BICPJ00 |
BICSPJ00 |
|
|