Skip to main content

iProcurement Checkout - GL Date field and Finance Options for Encumbrance

GL Date on iProcurement Requisitions is dependant upon the settings for encumbrance in the Finance Options form, Encumbrance tab. If the options are not checked in this form, the date field does not render.



Here are the definitions and the probable logic:

REF: Doc ID 1496106.1
Automatic Updates to General Ledger (GL) DateRequesters can specify the GL date (encumbrance date) for each distribution against a line at the time of creating purchase orders. If the value of the GL Date is invalid, for example, the date is in a closed GL period, or in a period that is not yet open, then the application automatically defaults the GL date to the system date if the current period is open. To use this feature, the value of the PO: Validate GL Date Period profile option must be set to the newly introduced Redefault value.

Encumbrance:
An Encumbrance is the name given to funds that have been reserved when a purchase requisition is finalized and encumbered. When a requisition is processed, funds are placed aside for that transaction. 

Those funds are no longer available for use in other transactions, but also have not been included in the Actual Funds balance because a payment has not yet been generated and the funds have not physically left. The purpose and main benefit of encumbrance accounting is avoiding budget overspending.

So if the Encumbrance for requisition is not enabled then there would be no meaning of specifying a real GL Date as there will be no reserved funds when system is going to take up the entries of the REQ->PO to accounting and it might end up in over budget too.



Comments

Post a Comment

Popular posts from this blog

SQL Query to extract Oracle Purchase Order Information

SELECT   poh.po_header_id,    poh.type_lookup_code PO_TYPE,   poh.authorization_status PO_STATUS,   poh.segment1 PO_NUMBER,   pov.vendor_name SUPPLIER_NAME,   povs.vendor_site_code Location,   hrls.location_code Ship_To,   hrlb.location_code Bill_to,   pol.line_num ,   msib.segment1 Item,   pol.unit_price,   pol.quantity,   pod.amount_billed Amount,   pod.destination_subinventory,   ppf.full_name Buyer_Name,   poh.closed_Code  FROM   PO_HEADERS_ALL poh,   PO_LINES_ALL pol,   mtl_system_items_b msib,   PO_LINE_LOCATIONS_ALL poll,   PO_DISTRIBUTIONS_ALL pod,   po_vendors pov,   po_vendor_sites_All povs,   hr_locations_all hrls,   hr_locations_all hrlb,   per_all_people_f ppf,   po_line_types polt WHERE   1                         =1 AND polt.line...
Post a Comment
Read more

Query to find Operating Unit, Business Group and Legal Entity Information

SELECT   DISTINCT   hrl . country ,                  hroutl_bg . name              bg ,                  hroutl_bg . organization_id ,                  lep . legal_entity_id ,                  lep . name                    legal_entity ,                  hroutl_ou . name              ou_name ,               ...
Post a Comment
Read more

List of iExpenses Tables

List of iExpenses Tables  Table Name Description AP_EXPENSE_REPORT_HEADERS_ALL Expense report header information AP_EXPENSE_REPORT_LINES_ALL Expense report lines information AP_EXP_REPORT_DISTS_ALL Expense report distribution information. It contains the accounts against each expense report line. AP_CREDIT_CARD_TRXNS_ALL Table to store the corporate credit card transactions that are sent by the banks. These lines are saved as expense lines when the user creates the expense lines for credit cards AP_NOTES Table to store the comments entered by approvers and auditors     Setup tables   AP_EXPENSE_REPORTS_ALL This table contains the header level information about the expense templates AP_EXPENSE_REPORT_PARAMS_ALL This table contains the detail level information about the expense templates AP_POL_CAT_OPTIONS_ALL Table to store the policy options AP_POL_CONTEXT Table to store the policy context     ...
Post a Comment
Read more