Skip to main content

Grouping Rules


Define grouping rules that AutoInvoice will use to group revenue and credit transactions into invoices, debit memos, and credit memos. Grouping rules specify attributes that must be identical for lines to appear on the same transaction.
Grouping rules include mandatory attributes which are always included in all grouping rules, and optional attributes which may be included in a grouping rule. Optional attributes may be added to the mandatory attributes to create new grouping rules. To be included in a group a transaction must always match on all of the mandatory attributes as well as on all of the optional attributes included in a grouping rule. For complete lists of the mandatory attributes and the optional attributes see the section titled "Using Grouping Rules to Create Transactions" in the Transactions chapter. All attributes of the Transaction Flexfield are optional within a grouping rule, and you can assign these attributes as optional grouping characteristics in the Grouping Rules window.
Note: The Grouping Rules window only displays the optional attributes included in a grouping rule. This window does not display any mandatory grouping attributes. The mandatory attributes are the same for all grouping rules. Use the Ordering and Grouping Rules Listing report to view all of the mandatory and optional attributes assigned to your grouping rules. See: Ordering and Grouping Rules Listing Report.
In the diagram below, the grouping rule specifies that to appear on the same invoice items must match on all of the mandatory attributes, for example currency (CURRENCY_CODE) and bill-to address (ORIG_SYSTEM_BILL_ADDRESS_ID) and must also match on the optional attribute of order type (SALES_ORDER_SOURCE). For example, in the diagram, assume that all mandatory attributes match other than currency and bill-to address. Items A and B share the same currency and order type, so they appear on the same invoice (Invoice 1). Item C has the same currency as A and B, but it has a different order type, so it appears on its own invoice (Invoice 2). Items D and E share the same currency and Order Type, so they appear on the same invoice (Invoice 3).
To define a grouping rule:
1. Navigate to the Grouping Rules window.
2. Enter a Name for this grouping rule.
3. Enter a Description for this grouping rule (optional).
4. Enter the invoice line ordering rule for this grouping rule (optional). The invoice line ordering rule tells AutoInvoice how to order transaction lines within this grouping rule.
5. Enter a range of Effective Dates for this grouping rule. The default Start Date is today's date, but you can change it. If you do not enter an end date, this grouping rule will be active indefinitely.
6. Enter the Transaction Class to define for this grouping rule. Choose from the following classes: Invoice, Debit Memo, or Credit Memo.
Note: If AutoInvoice uses grouping rules and it is processing a transaction class that is not defined for this grouping rule, AutoInvoice will only use the mandatory grouping transaction attributes.
7. Enter any Optional Grouping Characteristics you want to use to group your transactions. For example, if you enter the transaction flexfield attribute 'Attribute2' (order type), only transactions with the same order type can appear together on a transaction. Use the list of values to review the description and sources of each attribute.
Receivables ensures that you do not assign duplicate transaction class grouping characteristics to your grouping rule.
8. Save your work.

Comments

  1. I wondered upon your blog and wanted to say that I have really enjoyed reading your blog posts. Any way I’ll be subscribing to your feed and I hope you post again soon.
    mobile app developers pune

    ReplyDelete

Post a Comment

Popular posts from this blog

Applying Prepayments to Invoices

You can apply the available amount of Item type distributions from a Temporary type prepayment to one or more invoices to offset the amount you pay on the invoice(s). If you entered the prepayment as a Permanent type and want to apply it, you can query the prepayment in the Invoices window and change the Prepayment Type to Temporary. If you use Automatic Offsets then your setting for the Prevent Prepayment Application Across Balancing Segments Payables option controls whether you can apply a prepayment to an invoice or expense report with a different balancing segment. Prerequisites The invoice type is Standard, Mixed, or Expense Report. Today's date is on or after the Settlement Date of the prepayment. The invoice date is on or after the date of the prepayment. The prepayment is type Temporary, fully paid, validated, not cancelled, has no active holds, and has not already been fully applied. The prepayment has the same supplier, invoice currency and payment currenc

Application Utilities Lookups and Application Object Library Lookups

Maintain existing and define additional Lookups for your shared Lookup types. You can define up to 250 Lookups for each Lookup type. Each Lookup has a code and a meaning. For example, Lookup type YES_NO has a code Y with meaning Yes, and a code N with a meaning No. Note: In Releases 11.0 and earlier, there were two Lookup features, Special Lookups and Common Lookups. These two features have been merged into one. The new consolidated Lookups feature has Lookups maintained in this form. If you make changes to a Lookup, users must log out then log back on before your changes take effect. Lookups Block Type Query the type of your Lookup. You can define a maximum of 250 Lookups for a single type. User Name The user name is used by loader programs. Application Query the application associated with your Lookup type. Description If you use windows specialized for a particular Lookup type, the window uses this description in the window title. Access Level The access level restricts changes that

Matching Prepayments to Purchase Orders

You can match a prepayment to a purchase order or receipt. The accounting entries for Item distributions on a matched prepayment typically debit a prepayment account that Payables provides. However, during prepayment entry you can override any account that Payables defaults or builds. Payables does not create an encumbrance entry for the prepaid amount when a prepayment is matched to a purchase order. The match is treated like a reservation of the quantity billed. Payables does not calculate the invoice price variance or exchange rate variance at this point. Furthermore, you cannot change the unit price during the prepayment match to purchase order. A final match to the purchase order is not allowed either. When the matched prepayment is applied to an invoice, Payables reverses the matched quantity on the prepayment to reflect the balance of the total quantity matched. The following example illustrates a prepayment application to a purchase order: You contract to attend a $5,000 trade