In industry, a transaction is a transformation of state which has the properties of atomicity (all or nothing), durability (effects survive failures) and consistency (a correct transformation). The transaction concept is key to the structuring of data management applications. The concept may have applicability to programming systems in general.
More commonly, ACID (Atomicity, Consistency, Isolation, Durability) is known as database transaction properties. That is, All or Nothing for critical commitment. So it is important to understand what is a Transaction not only in EnterpriseOne but also industry common. This document contains some possible questions you may have when getting errors such as the ones described here.
Example of Error Message:
In industry, a transaction is a transformation of state which has the properties of atomicity (all or nothing), durability (effects survive failures) and consistency (a correct transformation). The transaction concept is key to the structuring of data management applications. The concept may have applicability to programming systems in general.
More commonly, ACID (Atomicity, Consistency, Isolation, Durability) is known as database transaction properties. That is, All or Nothing for critical commitment. So it is important to understand what is Transaction not only in EnterpriseOne but also industry common.
Transaction Processing is designed to maintain a computer system (typically a database or some modern file system) in a known, consistent state, by ensuring that any operations carried out on the system that are interdependent are either all completed successfully or all canceled successfully.
Transaction processing allows multiple individual operations to be linked together automatically as a single, individual transaction. The transaction-processing system ensures that either all operations in a transaction are completed without error, or none of them are. If some of the operations are completed but errors occur when the others are attempted, the transaction-processing system rolls back all of the operations of the transaction (including the successful ones), thereby erasing all traces of the transaction and restoring the system to the consistent, known state that it was in before processing of the transaction began. If all operations of a transaction are completed successfully, the transaction is committed by the system, and all changes to the database are made permanent; the transaction cannot be rolled back once this is done.
To have full list of transaction processing in EnterpriseOne refer to <Document 1320968.1> E1: DB: Listing of Applications with Transaction Processing by EnterpriseOne Release. For instance, P4114 commits data as below,
1. Calling Business Function F4114EndDocument Ref #1
2. Calling Business Function F0911FSEditDoc Ref #2
2. Return Value is 0 for for F0911FSEditDoc
2. Calling Business Function F0911FSSummarizeDoc Ref #3
2. Return Value is 0 for for F0911FSSummarizeDoc
2. Calling Business Function F4111EndDocument Ref #4
3. Calling Business Function F0911FSEndDoc Ref #5
sql> INSERT INTO PRODDTA.F0911 *** Write Credit ***
sql> INSERT INTO PRODDTA.F0911 *** Write Debit ***
4. Calling Business Function BatchReviseOnTransactionCommit
sql> UPDATE PRODDTA.F0011 Ref #6
4. Return Value is 0 for for BatchReviseOnTransactionCommit
3. Return Value is 0 for for F0911FSEndDoc
sql> UPDATE PRODDTA.F41021 Ref #7
sql> INSERT INTO PRODDTA.F41021WF *** To enables rollback data from F41021 in the event commit fails ***
3. Calling Business Function InventoryCardexShell
4. Calling Business Function WriteCardexRecord
sql> INSERT INTO PRODDTA.F4111 *** Insert Cardex Information so long as inventory is involved ***
4. Return Value is 0 for for WriteCardexRecord
3. Return Value is 0 for for InventoryCardexShell
3. Calling Business Function AverageCostUpdate
4. Calling Business Function UpdateItemCost
sql> UPDATE PRODDTA.F4105 *** Update relevant cost if needed ***
4. Return Value is 0 for for UpdateItemCost
3. Return Value is 0 for for AverageCostUpdate
sql> DELETE FROM PRODDTA.F41021WF Ref #8
3. Calling Business Function BatchReviseOnExit
sql> UPDATE PRODDTA.F0011 *** to release reserved batch ***
3. Return Value is 0 for for BatchReviseOnExit
2. Return Value is 0 for for F4111EndDocument
1. Return Value is 0 for for F4114EndDocument
For this example, the actual transaction will be:
sql> INSERT INTO PRODDTA.F0911
sql> INSERT INTO PRODDTA.F0911
sql> UPDATE PRODDTA.F0011
sql> UPDATE PRODDTA.F41021
sql> INSERT INTO PRODDTA.F41021WF
sql> INSERT INTO PRODDTA.F4111
sql> UPDATE PRODDTA.F4105
Listed applications from <Document 625535.1> handles commit as below:
Why it is needed? In case there is an Excel file in a shared area that multiple users can modify, the user modifying may not have the result they want. So grant the author read/write and grant others read only option. If this document is not locked the information referenced by other users will be not accurate (so called, dirty read (against update) or phantom read (against delete).)
In EnterpriseOne the first purpose of locking is when a user modifies data through transaction A, which gets locked by same data till transaction A gets committed or rolled back. In other words, a certain transaction A has to be locked till this transaction is completed (Data Concurrency).
Another purpose is that by blocking a certain data modified by other transaction, the original data can be handled within transaction A (Read Concurrency).
These two attributes (Data Concurrency and Read Concurrency) can be understood better by removing locking in a certain transaction.
Example of an SQL Server:
Example of an Oracle database server:
and commonly in Oracle database server:
Then to detect deadlock in Oracle:
| Type | When | How long? | Details |
|---|---|---|---|
| Shared Lock, Read Lock | SELECT | It ends once SELECT is over | It shares locking with other locking methods. Exclusive Locking cannot be locked together |
| Exclusive Lock, Write Lock | INSERT, UPDATE, DELETE | In the end of Transaction | It cannot be locked together with other locking as it is exclusive |
Blocking:
tx1(transaction1) locks certain data and tx2(transaction2) is waiting to lock the same data. In case tx1 did not COMMIT or ROLLBACK for long long time then it can impact performance seriously. But BLOCKING is different from "dead lock" rather BLOCKING is "live lock". For example, you have issued update statement sql> update proddta.f0101 set abalpha = 'Alpha Name' where aban8 = 4245; through sqlPlus then table F0101 gets locked for designated time and/or till sql> commit; issued.
Deadlock:
More than 2 transactions keep on locking a certain table in turn, so it ends in infinite loop. For example, Tx1 tries to update table A and Table B and at the same time tx2 tries to update table B and table A. when tx2 tries to update table A, txt2 is not allowed to do so as table A is locked by tx1 till tx1 COMMIT table B. But in same manner table B is locked by tx2 so it has to wait till it gets unlocked. In case deadlock occurs the error code 1205 (in SQL database server for example) will be returned.
Deadlocks can also occur between/among three or more transactions. The more transactions involved, the more difficult they are to detect, to the point that transaction processing systems find there is a practical limit to the deadlocks they can detect.
Transaction-processing systems ensure database integrity by recording intermediate states of the database as it is modified, then using these records to restore the database to a known state if a transaction cannot be committed. For example, copies of information on the database prior to its modification by a transaction are set aside by the system before the transaction can make any modifications (this is sometimes called a before image). If any part of the transaction fails before it is committed, these copies are used to restore the database to the state it was in before the transaction began.
In this scenario the result can be vary depends on where memory violation/error has occurred. In general, commit won't take place as we have defined above actual commitment will take place only when sql> COMMIT TRANS gets issued at the end of Transaction Processing routine. However blocking may be observed for a specific amount of time as both 'rollback transaction' and 'commit transaction' or simply 'commit' may not take place
In computer science, ACID (atomicity, consistency, isolation, durability) is a set of properties/characteristics that guarantee database transactions are processed reliably. In the context of databases, a single logical operation on the data is called a transaction. For example, during Purchase Order receipt, which involves multiple changes (such as item cost change, inventory increase, monetary changes and so on), is a single transaction.
| Criteria | Description |
|---|---|
| Atomicity | Atomicity requires that database modifications must follow an "all or nothing" rule. Each transaction is said to be atomic if when one part of the transaction fails, the entire transaction fails and database state is left unchanged. It is critical that the database management system maintains the atomic nature of transactions in spite of any application, DBMS, operating system or hardware failure. An atomic transaction cannot be subdivided, and must be processed in its entirety or not at all. Atomicity means that users do not have to worry about the effect of incomplete transactions. |
| Consistency | The consistency property ensures that the database remains in a consistent state; more precisely, it says that any transaction will take the database from one consistent state to another consistent state. To maintain consistency;
|
| Isolation | Isolation refers to the requirement that other operations cannot access data that has been modified during a transaction that has not yet completed. The question of isolation occurs in case of concurrent transactions (multiple transactions occurring at the same time). Each transaction must remain unaware of other concurrently executing transactions, except that one transaction may be forced to wait for the completion of another transaction that has modified data that the waiting transaction requires. If the isolation system does not exist, then the data could be put into an inconsistent state. This could happen if one transaction is in the process of modifying data but has not yet completed, and then a second transaction reads and modifies that uncommitted data from the first transaction. If the first transaction fails and the second one succeeds, that violation of transactional isolation will cause data inconsistency. Due to performance and deadlocking concerns with multiple competing transactions, many modern databases allow dirty reads which is a way to bypass some of the restrictions of the isolation system. A dirty read means that a transaction is allowed to read, but not modify, the uncommitted data from another transaction. |
| Durability | Durability is the ability of the DBMS to recover the committed transaction updates against any kind of system failure (hardware or software). Durability is the DBMS's guarantee that once the user has been notified of a transaction's success the transaction will not be lost, the transaction's data changes will survive system failure, and that all integrity constraints have been satisfied, so the DBMS won't need to reverse the transaction. Many DBMSs implement durability by writing transactions into a transaction log that can be reprocessed to recreate the system state right before any later failure. A transaction is deemed committed only after it is entered in the log. Durability does not imply a permanent state of the database. A subsequent transaction may modify data changed by a prior transaction without violating the durability principle. |
Commonly:
A. JDE.INI
[JDENET]
enterpriseServerTimeout=60000
- This parameter is the max time when certain logic (BSFN) can be running. So this is time limit between client (which requests) and server (which responds). If it fails to return within this time error will be issued on client with return value 99. This business function is not specific to xxxEndDoc
[NETWORK QUEUE SETTINGS]
JDENETTimeout=60
- This is parameter which is related with the Commit Fail error. In case you do not have this parameter in jde.ini it is considered default settings which is 60 seconds and the max value for this parameter is 360 seconds. For the problematic BSFN XT4311Z1 - F4311EndDoc is to be called with option as below,
- Transaction Processing ON (At once Transaction Processing is on, which is MANUAL commit) F4311EndDoc can consume to commit cache to DB same amount of time.
- Asynchronously
[PERFMON]
jdenetTimeout=120
transactionTimeout=60000
- This option is only valid when using a Transaction server
B. JAS.INI
[JDENET]
# Time out value for requests sent to the Enterprise Server
enterpriseServerTimeout=90000
- When the JAS Server is calling a certain BSFN, it has to return to the calling routine within this amount of time. This affects not only xxxEndDoc but also any type of BSFN even when 'Transaction Processing' is OFF. So this value has to be equal to or greater than JDENETTimeout settings in server.
C. JDBJ.INI
# transactionTimeout=120000
- This parameter is only valid when using a Transaction server
| Object | Description | Type | Xe | 8.0 | 8.9 | 8.10 | 8.11 | 8.11 SP1 | 8.12 | 9.0 |
|---|---|---|---|---|---|---|---|---|---|---|
| P01301 | Edit Activity | APPL | N | N | N | N | N | N | Y | Y |
| P01302 | Edit Activity Lite | APPL | N | N | N | N | N | N | Y | Y |
| P03B102 | Standard Receipt Entry | APPL | Y | Y | Y | Y | Y | Y | Y | Y |
| P03B11 | Standard Invoice Entry | APPL | Y | Y | Y | Y | Y | Y | Y | Y |
| P03B11SI | Speed Invoice Entry | APPL | Y | Y | Y | Y | Y | Y | Y | Y |
| P03B41Z1 | Deductions Interop Revision | APPL | N | N | N | N | N | N | N | Y |
| P03B41Z2 | Deductions Interop Revision | APPL | N | N | N | N | N | N | N | Y |
| P041016 | Multi Company - Single Supplier | APPL | N | N | N | N | Y | Y | Y | Y |
| P041017 | Multi-Voucher Entry | APPL | N | N | N | N | Y | Y | Y | Y |
| P0411 | A/P Standard Voucher Entry | APPL | N | N | N | N | Y | Y | Y | Y |
| P0411SV | A/P Speed Voucher Entry | APPL | N | N | N | N | Y | Y | Y | Y |
| P0411Z1 | A/P Batch Voucher Entry | APPL | N | N | N | N | Y | Y | Y | Y |
| P0413M | A/P Manual Payments | APPL | N | N | N | N | Y | Y | Y | Y |
| P0413V | A/P Void Payment | APPL | Y | Y | Y | Y | Y | Y | Y | Y |
| P05601 | Revise Component Instructionss | APPL | N | N | N | N | N | N | N | Y |
| P059022 | Revise Pay Calculation Tables | APPL | N | N | N | N | N | N | N | Y |
| P073111 | Associate Pay Types with Activity Types | APPL | N | N | N | N | N | Y | Y | Y |
| P07315 | Manage Schedules for Employee Groups | APPL | N | N | N | N | N | Y | Y | Y |
| P076311 | Manager Self Service Leave Review | APPL | N | N | N | N | N | N | Y | Y |
| P07916 | Item Master | APPL | N | N | N | N | Y | Y | Y | Y |
| P07918 | Item Piece Rate Revisions | APPL | N | N | N | N | Y | Y | Y | Y |
| P09106 | Journal Entries with VAT | APPL | Y | Y | Y | Y | Y | Y | Y | Y |
| P0911 | Journal Entries | APPL | Y | Y | Y | Y | Y | Y | Y | Y |
| P09631 | Manual Bank Statement Reconciliation | APPL | N | N | N | N | Y | Y | Y | Y |
| P3002 | Bill of Material Maintenance | APPL | N | N | N | N | N | N | Y | Y |
| P3003 | Routing Maintenance | APPL | N | N | N | N | N | N | Y | Y |
| P311221 | WO Time Entry | APPL | N | N | N | N | N | N | Y | Y |
| P31B317B | Speed Advanced Comment | APPL | N | N | N | N | Y | Y | Y | Y |
| P31B65A | Create/Edit Operations | APPL | N | N | N | N | Y | Y | Y | Y |
| P31B67 | Speed Actuals Update | APPL | N | N | N | N | Y | Y | Y | Y |
| P31B76 | Speed Quality Results | APPL | N | N | N | N | Y | Y | Y | Y |
| P31B78 | Create Operations From Vessel List | APPL | N | N | N | N | Y | Y | Y | Y |
| P31B94 | Search for Operations | APPL | N | N | N | N | Y | Y | Y | Y |
| P31B95 | Search for Work Order | APPL | N | N | N | N | Y | Y | Y | Y |
| P31B96 | Speed Operation Update | APPL | N | N | N | N | Y | Y | Y | Y |
| P3411 | MRP/MPS Detail Message Revisions | APPL | N | N | N | N | N | N | Y | Y |
| P3460 | Forecast Revisions | APPL | Y | Y | Y | Y | Y | Y | Y | Y |
| P40G003 | Harvest Period Patterns | APPL | N | N | N | N | N | N | Y | Y |
| P40G01 | Grower Farm Maintenance | APPL | N | N | N | N | N | N | Y | Y |
| P40G02 | Grower Block Maintenance | APPL | N | N | N | N | N | N | Y | Y |
| P40G020 | Speed Block Update | APPL | N | N | N | N | N | N | Y | Y |
| P40G021 | Block Descriptors Maintenance | APPL | N | N | N | N | N | N | Y | Y |
| P40G022 | Block Styles Maintenance | APPL | N | N | N | N | N | N | Y | Y |
| P40G023 | Block Coordinates Maintenance | APPL | N | N | N | N | N | N | Y | Y |
| P40G03 | Grower Harvest Maintenance | APPL | N | N | N | N | N | N | Y | Y |
| P40G030 | Speed Harvest Update | APPL | N | N | N | N | N | N | Y | Y |
| P40G100 | Advance Voucher | APPL | N | N | N | N | N | N | Y | Y |
| P40G101 | Manage Ownership Distribution | APPL | N | N | N | N | N | N | Y | Y |
| P40G102 | Manage Contacts Info | APPL | N | N | N | N | N | N | Y | Y |
| P40G103 | Manage EUR - Intended Use Distribution | APPL | N | N | N | N | N | N | Y | Y |
| P40G104 | Action Dates Maintenance | APPL | N | N | N | N | N | N | Y | Y |
| P40G10A | Operation Edit Create - Farming Activity | APPL | N | N | N | N | N | N | Y | Y |
| P40G10C | Farming Activities - Multiple Harvest Assignments | APPL | N | N | N | N | N | N | Y | Y |
| P40G11A | Speed Actuals - Spray Activity | APPL | N | N | N | N | N | N | Y | Y |
| P40G20 | Harvest Estimate | APPL | N | N | N | N | N | N | Y | Y |
| P40G200 | Price Review | APPL | N | N | N | N | N | N | Y | Y |
| P40G21 | Frozen Harvest Estimate | APPL | N | N | N | N | N | N | Y | Y |
| P40G23 | Continuous Harvest Estimate | APPL | N | N | N | N | N | N | Y | Y |
| P40G30 | Grower Harvest and Weigh Tag Receipt Operations | APPL | N | N | N | N | N | N | Y | Y |
| P40G300 | Final Setllement | APPL | N | N | N | N | N | N | Y | Y |
| P40G40A | Operation Edit Create - Spray Activity | APPL | N | N | N | N | N | N | Y | Y |
| P40G40C | Farming Activities - Single Harvest Assignment | APPL | N | N | N | N | N | N | Y | Y |
| P40G41A | Speed Actuals - Farming Activity | APPL | N | N | N | N | N | N | Y | Y |
| P40R10 | Demand Maintenance | APPL | N | N | N | N | Y | Y | Y | Y |
| P4112 | Inventory Issues | APPL | N | N | N | N | Y | Y | Y | Y |
| P4113 | Inventory Transfers | APPL | N | N | N | N | Y | Y | Y | Y |
| P4114 | Inventory Adjustments | APPL | N | N | N | N | Y | Y | Y | Y |
| P4116 | Item Reclassifications | APPL | N | N | N | N | Y | Y | Y | Y |
| P4205 | Shipment Confirmation | APPL | N | N | N | N | Y | Y | Y | Y |
| P4210 | Sales Order Entry | APPL | N | N | Y | Y | Y | Y | Y | Y |
| P42101 | Sales Order Entry | APPL | N | N | N | N | Y | Y | Y | Y |
| P42117 | Backorder Release | APPL | Y | Y | Y | Y | Y | Y | Y | Y |
| P4310 | Purchase Orders | APPL | Y | Y | Y | Y | Y | Y | Y | Y |
| P4312 | PO Receipts | APPL | Y | Y | Y | Y | Y | Y | Y | Y |
| P4314 | Voucher Match | APPL | N | N | N | N | Y | Y | Y | Y |
| P43291 | Landed Cost Selection | APPL | N | N | N | N | Y | Y | Y | Y |
| P43C00 | Search for Contracts | APPL | N | N | N | N | N | N | Y | Y |
| P43C00C | Copy Contract | APPL | N | N | N | N | N | N | Y | Y |
| P43C01 | Edit Header Contract | APPL | N | N | N | N | N | N | Y | Y |
| P43C05 | Contract Action Dates | APPL | N | N | N | N | N | N | Y | Y |
| P43C10 | Contract Block | APPL | N | N | N | N | N | N | Y | Y |
| P43C10S | Block Subform | APPL | N | N | N | N | N | N | Y | Y |
| P43C11 | Contracts Detail | APPL | N | N | N | N | N | N | Y | Y |
| P43C20 | Payee SubForm | APPL | N | N | N | N | N | N | Y | Y |
| P43C40 | Contract Assessment and Donation | APPL | N | N | N | N | N | N | Y | Y |
| P43C50 | Push from Header to Blk/Harvest Dtl | APPL | N | N | N | N | N | N | Y | Y |
| P43C60 | Contract Clauses SubForm | APPL | N | N | N | N | N | N | Y | Y |
| P43C70 | Harvests for Block | APPL | N | N | N | N | N | N | Y | Y |
| P43C80 | Push from Block to Harvest detail | APPL | N | N | N | N | N | N | Y | Y |
| P43E060 | Requisition Expeditor | APPL | N | N | N | N | Y | Y | Y | Y |
| P43E22 | Direct Connect Setup Application | APPL | N | N | N | N | Y | Y | Y | Y |
| P43Q411 | Bidder Response Detail Questions | APPL | N | N | N | N | N | N | Y | Y |
| P43Q51 | SRM - Score Text Questions | APPL | N | N | N | N | N | N | Y | Y |
| P43Q52 | View/Edit Question Responses | APPL | N | N | N | N | N | N | Y | Y |
| P48013 | Manufacturing Work Order Processing | APPL | N | N | N | N | N | N | Y | Y |
| P76CCIC | Input Tax Setup - COL - 00 - 76C | APPL | N | N | N | N | Y | Y | Y | Y |
| P76H001 | Legal Document Next Number - CHI - 03B - 76H | APPL | N | N | N | N | Y | Y | Y | Y |
| P76H3B20 | Invoices not Printed - CHI - 03B - 76H | APPL | N | N | N | N | Y | Y | Y | Y |
| P76H3B50 | Lot of Printing Review - CHI - 03B - 76H | APPL | N | N | N | N | Y | Y | Y | Y |
| PF30L201 | Volume Design | APPL | N | N | N | N | N | Y | Y | Y |
| PF30L702 | Product Synch | APPL | N | N | N | N | N | Y | Y | Y |
| PF30L901 | Process Maps | APPL | N | N | N | N | N | Y | Y | Y |
| PF30L912 | Line Design | APPL | N | N | N | N | N | Y | Y | Y |
| PF30L950 | Operational Def | APPL | N | N | N | N | N | Y | Y | Y |
| PF31010B | Daily Planning | APPL | N | N | N | N | N | Y | Y | Y |
| PF31K10 | Kanban Demand | APPL | N | N | N | N | Y | Y | Y | Y |
| PF31K21 | Assign Comp to Pull Chain | APPL | N | N | N | N | Y | Y | Y | Y |
| PF34S001 | Daily Sequencing | APPL | N | N | N | N | N | Y | Y | Y |
| PF34S002 | Daily Planning | APPL | N | N | N | N | N | Y | Y | Y |
| R03B41Z2 | Interop Deduction Dispositions | UBE | N | N | N | N | N | N | Y | Y |
| R03B50A | Invoice Selection Match | UBE | Y | Y | Y | Y | Y | Y | Y | Y |
| R03B50B | Balance Forward Match | UBE | Y | Y | Y | Y | Y | Y | Y | Y |
| R03B50D | Known Invoice Match With Amount | UBE | Y | Y | Y | Y | Y | Y | Y | Y |
| R03B50E | Known Invoice Match Without Amount | UBE | Y | Y | Y | Y | Y | Y | Y | Y |
| R03B50F | Combination Invoice Match | UBE | Y | Y | Y | Y | Y | Y | Y | Y |
| R04110ZB | Inbound AP Claims | UBE | N | N | N | N | N | N | Y | Y |
| R04110ZC | AP Confirmation | UBE | N | N | N | N | N | N | Y | Y |
| R04586 | Generate Positive Pay Text File | UBE | N | N | N | Y | Y | Y | Y | Y |
| R05601 | Component Pay Generation - Driver Section | UBE | N | N | N | N | N | N | N | Y |
| R07311 | Generate Timecards from Schedule | UBE | N | N | N | N | N | Y | Y | Y |
| R083800 | Batch Enrollment | UBE | Y | Y | Y | Y | Y | Y | Y | Y |
| R09110Z | Journal Entry Batch Processor | UBE | Y | Y | Y | Y | Y | Y | Y | Y |
| R09110ZS | Store and Forward JE Batch Processor | UBE | Y | Y | Y | Y | Y | Y | Y | Y |
| R09801 | General Ledger Post | UBE | N | N | N | N | N | N | N | Y |
| R30510 | ECO Change Population | UBE | N | N | N | N | N | N | Y | Y |
| R30835 | Frozen Cost Update | UBE | Y | Y | Y | Y | Y | Y | Y | Y |
| R31422 | Hrs & Qty Update | UBE | N | N | N | N | N | N | Y | Y |
| R31802A | Manufacturing Accounting | UBE | N | N | Y | Y | Y | Y | Y | Y |
| R31B65AZ | Operations Inbound Processor | UBE | N | N | N | N | Y | Y | Y | Y |
| R42800 | Sales Update | UBE | N | N | N | Y | Y | Y | Y | Y |
| R42800G | Sales Update Summarized COGS-Inv Recovery | UBE | N | N | N | N | Y | Y | Y | Y |
| R45640 | Inbound Promotional Pricing | UBE | N | N | N | N | N | N | Y | Y |
| R45720ZB | Live Promotions Update | UBE | N | N | N | N | N | N | Y | Y |
| R46151 | Carton Recommendations Report | UBE | N | N | N | N | N | N | Y | Y |
| R46474 | Generated Sequenced Carton Packing Recommendations | UBE | N | N | N | N | N | N | Y | Y |
| R48132 | G/L Journal Generation | UBE | N | N | N | N | Y | Y | Y | Y |
| R48S781 | Create Retroactive Adjustments | UBE | N | N | N | N | Y | Y | Y | Y |
| R49500 | Batch Transportation Shipment Confirmation | UBE | N | N | Y | Y | Y | Y | Y | Y |
| RF31011A | Multi Level Item Completions | UBE | N | N | N | N | N | Y | Y | Y |
| RF31011B | Multi Level Item Completions | UBE | N | N | N | N | N | Y | Y | Y |
| RF31011C | Multi Level Item Completions | UBE | N | N | N | N | N | Y | Y | Y |
| RF31011L | Multi Level Item Completions | UBE | N | N | N | N | N | Y | Y | Y |
| RF31012 | BOM and Routing Detail Generation - Item/Branch | UBE | N | N | N | N | N | Y | Y | Y |
| RF31200 | Lean MFG Accounting | UBE | N | N | N | N | Y | Y | Y | Y |
| RF31210 | Lean MFG Variance Acctg | UBE | N | N | N | N | Y | Y | Y | Y |
| RF31220 | Lean WIP Revaluation | UBE | N | N | N | N | Y | Y | Y | Y |