OracleFree referencePDF, Excel, Word exportOracle JD Edwards EnterpriseOneAll JD Edwards EnterpriseOne tools

JD Edwards Document Types Reference (OP, SO, OV, PV)

Every transaction in JD Edwards EnterpriseOne carries a two character document type next to its document number and company, and reading those pairs quickly is a core skill for support staff and developers. This lookup lists the common ones such as OP, SO, OV and PV with the module and the table they normally sit in.

Download:

Doc type	Typical meaning	Module	Typical table	Note
OP	Purchase order	Procurement (43)	F4301 / F4311	Standard order type for purchase orders
OV	Purchase order receipt	Procurement (43)	F43121	Receipt against a purchase order line
SO	Sales order	Sales Order Management (42)	F4201 / F4211	Standard sales order document type
PV	Standard voucher	Accounts Payable (04)	F0411	Created by voucher entry or voucher match
RI	Standard invoice	Accounts Receivable (03B)	F03B11	Customer invoice from invoice entry
RC	Receipt	Accounts Receivable (03B)	F03B13	Customer payment applied to invoices
JE	Journal entry	General Accounting (09)	F0911	Manual journal entry
WO	Work order	Shop Floor Management (31)	F4801	Manufacturing and maintenance work orders
II	Inventory issues	Inventory Management (41)	F4111	Material issued from stock
IA	Inventory adjustments	Inventory Management (41)	F4111	Quantity adjustment transactions
IC	Inventory cycle count	Inventory Management (41)	F4111	Cycle count update transactions
IT	Inventory transfers	Inventory Management (41)	F4111	Transfers between locations or branches

Document types are user defined codes (UDC system 00, type DT) and sites can add their own, so check your own table. Many sites also use extra order types such as for blanket orders, returns or interbranch work. The table column shows where the document normally lands, not every table it touches.

Trace a JDE document chain without SQL

Optional: see how a read-only assistant can follow an order to receipt to voucher in your own data.

Optional. The tool and every export work without this. No spam.

Was this tool useful?

How to use the lookup

Type a code or a keyword such as voucher or receipt into the search box and the table filters. Use the module and table columns to know where to look when you trace a transaction. Export the filtered rows to Excel when you need to hand a quick legend to a new analyst or add it to a runbook for the support team.

Document number, type and company

A JDE document is identified by three values together: document number, document type and document company (key company). The same number can legitimately exist under different types, so searching by number alone returns the wrong record more often than people expect. In SQL, always join on all three, for example on voucher number, document type and key company in the accounts payable ledger.

OP and OV: the purchase order and its receipt are different types
PV: the voucher that the payable ledger carries
SO: the sales order header and detail share the type
JE: general ledger entries from manual journals

Why codes differ by site

The delivered values are a starting point. Because the list is user defined, you may find sites that use separate types for rush orders, intercompany orders or credit memos. Some behaviour such as the next status, the GL class or approval route is tied to the order type in setup, so the same transaction can behave differently across sites. Treat this table as a quick orientation guide and confirm any value in your own UDC table.

Common mistakes

Mixing up order type and document type is frequent: sales and purchase orders use an order type field that carries the document type value, while journal and voucher entries use the document type directly. Another mistake is assuming OV exists only as a receipt, when in some implementations receipts are also reversed with their own types.

Searching by number without the type and company
Assuming delivered codes are unchanged at your site
Joining header and detail tables on number only
Forgetting that archived documents may sit in history tables

Frequently Asked Questions

What does OV mean in JD Edwards?

In the standard delivered setup OV is the document type for a purchase order receipt, stored in the purchase order receiver table F43121. As with all document types it is a user defined code, so confirm the meaning in your own UDC table.

What is the difference between OP and PV?

OP is the purchase order, a commitment to a supplier. PV is the standard voucher, the payable created from invoice entry or voucher match. They sit in different modules and tables, and a voucher can reference one or many orders.

Where are document types defined?

They are user defined codes in system 00, type DT, maintained through the UDC programs. Order types for sales and purchasing have their own related setup that references the code.

Can I add my own document type?

Yes, by adding a UDC value and any required related setup such as next numbers and order activity rules. Test in a development path first and check any custom reports that filter on document type.

If you often trace documents across modules, Netray can add a read-only natural language layer on top of your JDE database so staff can ask for a voucher or receipt chain without writing joins.

Talk to an Expert Explore More Free Tools