Skip to main content

Balance Control Options

Amount Type: Defines the types of values to include in a row or column. General Ledger provides numerous amount types, such as actual, end-of-day, average-to-date, budget, or encumbrance; or calculated amounts, such as variances, for single or multiple periods. The amount type is typically assigned to column definitions.
Notes:
If you enter a budget, encumbrance, or variance amount type, you should enter a Control Value to assign budgets and encumbrance types to the report definition.
Amount Type, Period Offset, Control Value, and Currency must all share the same column or row.
If you assign an amount type to a row or column, you must also assign an offset.
Suggestion: Use the amount type, YTD-Actual (FY End) to report on fiscal year-end actual balances. Calculate the offset in relation to your accounting calendar and enter the offset value in the Balance Control Region (for example, -12 for a 12 period calendar). Label the column directly (for example, June-1999) instead of using the Period of Interest (&POI) token. Re-use this column set definition indefinitely. Update the column label when your fiscal year changes.
Currency: To report translated account balances for a specific currency, enter the currency. If you want to report on amounts entered in a foreign currency rather than translated amounts, enter a control value number. Then when you define your report, assign the currency and a currency type of Entered to that control value number.
The currency you enter when you define or request a report serves as the default currency for columns without a currency in the column set definition.
Suggestion: For column sets, if you assign a different currency to each of your columns, put the currency code in each column heading so you can correctly identify the currencies on your report.
Control Value: Used to include budgets, encumbrance types, and currencies in a report.
Offset: Enter the relative Offset if you want to report on a period or effective date before or after your runtime period or effective date. If your specified Amount Type refers to a period, such as PTD-Actual, then the Offset will be in number of periods. However, if your specified Amount Type refers to days, such as PATD, then the Offset will be in number of days.
FSG determines the amounts to display based on the offset and the period or effective date you enter at runtime. For example, enter 0 (zero) to display amounts for the runtime effective date or enter -1 to display amounts one day before the runtime effective date.
Note: You must specify offsets at the same level (row or column) at which you specified amount types and control value numbers.

Comments

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