A number that the transmitter assigns to the batch.
During batch processing, the system assigns a new batch number to the transactions for each control batch number it finds.
A code that determines whether the batch application is used to process an added or a deleted transaction record. Values are:
1: Use batch application.
0: Do not use batch application.
A code that determines whether the batch application is used to process an inquiry of a transaction record. Values are:
1: Use batch application.
0: Do not use batch application.
A code that determines whether the batch application is used to process an updated transaction record. Values are:
1: Use batch application.
0: Do not use batch application.
A code that determines whether the system exports the transaction record to an external API. Values are:
1: Export
0: Do not export
A code that determines whether the transaction record should be exported to an external database. Values are:
1: Export
0: Do not export
A code that determines whether the transaction record should be exported to a flat file. Values are:
1: Export
0: Do not export
The library for the function. This includes the path for the directory where the library exists.
The name of the function. You can define data export control for either a vendor-specific batch process or function. If you enter information in fields for vendor-specific batch processors or functions, the system uses the batch process.
A value that controls the immediate execution of a batch job. If the field is set to a 1, the job executes immediately.
A code (00/DT) that identifies the type of document.
This code also indicates the origin of the transaction. We have reserved document type codes for vouchers, invoices, receipts, and time sheets, which create automatic offset entries during the post program. (These entries are not self-balancing when you originally enter them.)
We have defined these document types that should not be changed:
P: Accounts Payable
R: Accounts Receivable
T: Payroll
I: Inventory
O: Purchase Order Processing
J: General Accounting and Joint Interest Billing
S: Sales Order Processing
The transaction type. This can be a code from user-defined code (UDC) 00/DT or a transaction type, such as, JDEVOUCH for voucher transactions.
The number that an Electronic Data Interchange (EDI) transmitter assigns to a transaction.
In a non-EDI environment, you can assign any number that is meaningful to you to identify a transaction within a batch. It can be the same as a JD Edwards EnterpriseOne document number.
The name that identifies a system object. JD Edwards EnterpriseOne architecture is object-based.
Discrete software objects are the building blocks for all applications, and developers can reuse the objects in multiple applications. The Object Librarian tracks each object. Examples of system objects include:
Batch Applications (such as reports)
Interactive Applications
Business Views
Business Functions
Business Functions Data Structures
Event Rules
Media Object Data Structures
You can define data export control for either a vendor-specific batch process or function.
If you enter information in fields for vendor-specific batch processors or functions, the system uses the batch process.
The source of the transaction.
This can be an ID, a workstation, the address of an external system, a node on a network, and so on. This field helps identify both the transaction and its point of origin.
A set of specifications that control how applications and reports run.
You use versions to group and save a set of processing option values and data selection and sequencing options. Interactive versions are associated with applications (usually as a menu selection). Batch versions are associated with batch jobs or reports. To run a batch process, you must select a version.