Setting Up Bill By Identifiers for External Sources
To set up bill by identifiers, use the Bill-By Identifier (BI_BILL_BY) component.
PeopleSoft Billing uses the bill by ID to define how to group billing activity on invoices when it is added to a bill through the Billing Interface. A bill by ID that you define can appear as the default at the customer, bill source, bill type, and business unit levels.
Note: If you define any one of the following fields as yes, the Billing Interface creates a new bill: CREATE_NEW_BILL, DIRECT_INVOICING, or TMP_BILL_FLG.
|
Page Name |
Definition Name |
Usage |
|---|---|---|
|
BI_BILL_BY |
Enter a new bill by field or review existing bill by fields. |
Use the Bill-by Identifier page (BI_BILL_BY) to enter a new bill by field or review existing bill by fields.
Navigation:
Field or Control |
Description |
|---|---|
New Bill Status |
Select the status that the system assigns to a new bill header. This value determines the status of new bills generated by the Billing Interface process (BIIF0001). |
Add to Bills With Status |
Displays the valid status of bill headers to which the system can add billing activity in the interface staging area. |
Bill-By Fields |
When you add bill by fields to the bill by definition, you are instructing the Billing Interface to use those fields to determine which noninvoiced bills are subject to interface activity. For example, if you define a bill by ID with the fields ORDER_NO and SHIP_TO_ADDR_NUM, the interface process generates a new bill for each combination of order number and ship to location for each customer. For each line of activity in the interface staging area, the interface process verifies that a noninvoiced bill exists for that business unit, bill to customer, order number, and ship to location. If a bill exists, the process adds the interface line of activity to the bill as another bill line. If no bill exists, the interface process generates a new bill header and adds the interface line activity to the new bill. |
Bill By Example
The following example demonstrates how five lines of billable activity are populated in the interface staging area for customer 5001:
|
Line |
Business Unit |
Customer |
Order Number |
Ship-To Location |
Amount |
|---|---|---|---|---|---|
|
1 |
US001 |
5001 |
5550122 |
1 |
500 USD |
|
2 |
US001 |
5001 |
5550122 |
1 |
2000 USD |
|
3 |
US001 |
5001 |
5554095 |
1 |
45 USD |
|
4 |
US001 |
5001 |
5554095 |
2 |
4700 USD |
|
5 |
US001 |
5001 |
5554095 |
1 |
16000 USD |
When the Billing Interface processes this activity, it establishes whether any noninvoiced bill headers exist for each business unit, customer, order number, and ship to location combination. If any noninvoiced bill headers exist, it adds the interface lines to the appropriate bills. If none exist, it generates new bill headers and adds the interface lines to the new bills.
Suppose that before the interface process was run for the preceding activity, one noninvoiced bill existed for business unit US001, customer 5001, order 550122, and ship to location 1, and no existing bills existed for order number 5554095. The interface process determines that a bill exists for order number 5550122 and ship to location 1, so it adds lines 1 and 2 to that bill. It then generates two new bill headers, one for order 5554095 and ship to location 1, and one for order 5554095 and ship to location 2. It adds lines 3 and 5 to the first of these two new bills. It adds line 4 to the second of these two new bill headers.
Note: If the Billing Interface process is run as a part of a job, such as IN Indirect Invoicing, that gets initiated by an upstream product, such as OM, the RANGE_SELECTION_ID field should be added to the Bill By identifier. This enables the billing processes to identify what transaction needs to be processed.