Skip to main content

Including Budgets, Encumbrances, and Currencies in an FSG Report

To include budgets, encumbrance types, and currencies in a report, your report definition must specify a row set or column set that has control values specified in the Balance Control options. When you use such row sets or column sets in a report definition, you assign the control values to specific budgets, encumbrances, or currencies.
When you assign a Budget to a control value number, FSG automatically prints the appropriate budget amounts in the budget-related rows or columns that are assigned that control value number. For example, if you assigned the number 1 to a column with the PTD-Budget amount type and the number 3 to a column with the PTD-Encumbrance amount type, you must assign a budget to the control value number 1 and an encumbrance to the control value number 3. This same logic applies to currency types.
Notes:
You must assign the same budget, encumbrance type, or currency to intersecting row and column control values.
You cannot enter currencies in the report definition if the report does not contain a row and/or column set with a currency control value.
You must specify a budget or encumbrance when your report includes rows or columns which use related amount types, such as PTD-Budget or PTD-Encumbrance.
To assign a budget, encumbrance, or currency to a financial report:
1. Assign a budget, encumbrance, or currency control value to the row set or column set you will use for your report.
2. Define a financial report using the row set or column set from step 1.
3. From the Define Financial Report window, choose Control Values.
4. Enter the Control Value number you assigned to the related rows or columns when you defined the row set and/or column set.
5. Enter the Budget name, Encumbrance Type, or Currency to associate with the control value number.
6. (Currency only) Select the Currency Type (Entered or Translated) for the accounts referenced in the rows and/or columns in the report.
7. Save your work.

Comments

  1. fusionscmtraininginhyderabadJanuary 5, 2024 at 5:00 AM

    As someone interested in Fusion Cloud SCM online training, your expertise in architecture, technical leadership, and Oracle Fusion Cloud applications consultancy is particularly appealing. I'm eager to explore more content from you, especially if it delves into how your experiences and skills intersect with the realm of online training for Fusion Cloud SCM.

    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
1 comment
Read more

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
1 comment
Read more

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
Post a Comment
Read more