Understanding Blend Transaction Processing

You create journal entries, detailed or summarized, periodically to account for transactions when you close an operation. Operational transactions can include:

  • Operations for receipt, crush, drain, move, and so forth.

  • Gains/losses for survey, operation, and casualty.

  • EUR changes.

As you close operations, the system stores transactions in the Blend Transactions table (F31B66). Blend automatic accounting instructions (AAIs) contain the accounts to which journal entries are written. The system creates journal entries for inventory if the operation includes consumables or additives. To create journal entries for Before and After lot costs, you run the Blend Cost Accounting Journal Entries program (R31B802).

If you use operational costing, the system captures lot costs in the journal entries. When the system creates journal entries for After lot amounts, it reverses the journal entries, not the costs, of the Before lot amounts. If you use standard costing, the system multiplies the lot quantity with the EUR standard cost in the journal entries.

After you create journal entries, you must review the journal entry batch, approve the batch, and then post the batch to the general ledger. When you run the General Ledger Post program (R09801), it updates all account balances in the Account Balances table (F0902). After posting, the system provides several reports that you can use to review the posted journal entries. You can run only one post at a time. You must ensure that all post menu selections are routed to the same job queue and that the job queue allows only one job to process at a time.

Note: Oracle strongly recommends that you not configure the post program. You should not change the accounts, AAIs, constants, or processing options when you run the post.

See "Posting Financial Transactions" in the JD Edwards EnterpriseOne Applications Financial Management Fundamentals Implementation Guide.