The Batch workload involves the entire flow from Order to Cash i.e. High Volume Order Processing (HVOP), Pick Release, Process Deliveries, Ship Confirm, Interface Trip Stop (ITS), Autoinvoice, Revenue Recognition, Transfer to GL and GL Autopost.
The Release 11i Order Management HVOP benchmark focuses exclusively on meeting the high order volumes originating from the new electronic channels, such as consumer and business web sites, B2B exchanges, and EDI. The benchmark is designed to represent a core component of the order to cash business flow demonstrating the overall order processing throughput. Oracle Workflow, a high performance process control engine that guides sales order headers and lines through a series of consecutive steps from order creation through Shipping, controls order processing. The HVOP program processes orders by reading the rows from the Order Management Interface tables and converting the interface records into permanent Oracle Applications order headers and their respective order lines. The orders are then booked and advanced to the shipping state.
Pick Release finds and releases eligible delivery lines that meet the release criteria, and creates move orders. Pick release can be executed by order, trip, stop, container,delivery, warehouse, customer, scheduled, or requested dates, shipment priority or combinations of the above criteria. The default release criteria is set up in Shipping Parameters, which can be overridden in the Release Sales Order window at pick release. The process of transacting move orders creates a reservation and determines the inventory source subinventory. Pick Slips can be created after the detailing process completes, and the quantity and source can be manually verified at pick confirm. Detailing and pick confirmation can be manually transacted through Oracle Inventory or set up in Shipping Parameters to occur automatically at pick release. Release criteria can be customized using one of the following rules.
Release Rules to specify your picking criteria and set the default Release Rule through Shipping Parameters Pick Release tab. The batch part of the kit uses this to define Release rule to pick up Items pertaining to a particular Item Category. This way, Pick Release process can be executed in parallel by specifying different Release rules pointing to different Item Categories.
Release Sequence Rules to specify the order in which eligible delivery lines are allocated during pick release.
Pick Slip Grouping Rules to determine how released move order lines are grouped onto pick slips.
Process Deliveries autocreates deliveries with unassigned delivery lines or to auto create trips with delivery groups according to the grouping parameters and compatibility constraints. This process can be limited in the execution of the request to particular delivery lines status, delivery status, date ranges, ship method or customer.
Ship confirm is the process of confirming that items have shipped. When a delivery is shipconfirmed, Shipping Execution confirms that the delivery lines associated with the delivery have shipped.
Interface Trip Stop—SRS has been modified to accept Organization code as a parameter and process the trip stops for the specified organization. Interface Trip Stop—SRS has also been enhanced to spawn multiple child processes to process trip stops in parallel. Two new parameters have been added to support spawn multiple child processes. The parameter Number of Child Processes is used to specify the number of child processes to be spawned by Interface Trip Stop—SRS. The parameter Stops per Batch is used to specify the number of stops to be processed by each thread of the Interface Trip Stop—SRS. Interface Trip Stop—SRS has also been enhanced to defer the Inventory Interface processes. A new profile option Defer Inventory Process Online has been added to support this feature. In the eBS kit, this profile is set to Yes so that the Inventory Interface transactions are processed in the background by the Inventory transaction manager.
INV Material transaction
The material transaction manager is configured to execute material transaction by periodic concurrent request submissions. The execution interval is set to 20 minutes.
AutoInvoice process is used to import invoices, credit memos, debit memos, and on–account credits. Receivables ensures that the data imported is accurate and valid.
Run the Revenue Recognition program to generate the revenue distribution records for the invoices and credit memos that use Invoicing and Accounting Rules. Accounting rules can be assigned to recognize revenue over several accounting periods. The Revenue Recognition program will create distribution records for the invoices and credit memos that are created in Receivables and imported using AutoInvoice.
Running General Ledger Interface/ Journal Import
The General Ledger Interface program transfers Receivables transaction accounting distributions to the general ledger interface table (GL_INTERFACE) and create either detailed or summarized journal batches. Receivables create unposted journal entries in general ledger and executes Journal Import from Oracle General Ledger. It posts journal batches in Oracle General Ledger to update account balances.
The Journal Import program transfers data from the Receivables GL_INTERFACE table and creates unposted journal entry batches in the Oracle General Ledger tables GL_JE_BATCHES, GL_JE_HEADERS, and GL_JE_LINES. To run Journal Import when General Ledger Interface is executed, set Run Journal Import to Yes.
Posting Journal Batches
Post journal batches to update the account balances of the detail and summary accounts. It can post actual, budget, or encumbrance journal batches.