Sequence and Summarization Rules for JD Edwards EnterpriseOne Service Billing Transactions

When you generate a batch of invoices from the transactions in the Billing Detail Workfile (F4812), the system automatically creates a new invoice for each customer. You must further define how you want the system to sequence and summarize the transaction information that appears on the invoices. To do this, you define a sequence and summarization key.

The sequence and summarization key that you define indicates divisions within generated batches of invoices and the individual invoices within a batch. You must define these divisions at these levels:

• Invoice level (I)

  When the sequence and summarization key that you define changes at the invoice level, the system creates a new invoice with a unique invoice number.

• Pay item level (P)

  When the sequence and summarization key that you define changes at the pay item level, the system creates a new line of billing detail for the invoice. The system assigns the new line of billing detail a unique pay item number.

The system uses the sequence and summarization key that you define to:

• Assign invoice numbers.

• Summarize transactions by invoice and pay item.

• Control how the transactions appear in the Customer Ledger table (F03B11) when you create the A/R entries.

• Update the workfile transaction with the applicable key invoice information.

  For example, you can define a sequence and summarization key with jobs (business units) at the invoice level and with work orders (subledgers) at the pay item level. During invoice generation, the system uses the key to:

• Create a new invoice number when the job (business unit) changes.

• Create a new pay item number when the work order (subledger) changes for a job (business unit).

You can have only one customer number per invoice. If the customer number changes, the system creates a new invoice number, regardless of how you set up the sequence and summarization key.