## Glossary of JD Edwards EnterpriseOne Terms

Accessor Methods/Assessors | Java methods to “get” and “set” the elements of a value object or other source file.
activity rule | The criteria by which an object progresses from one given point to the next in a flow.
add mode | A condition of a form that enables users to input data.
Advanced Planning Agent (APAg) | A JD Edwards EnterpriseOne tool that can be used to extract, transform, and load enterprise data. APAg supports access to data sources in the form of rational databases, flat file format, and other data or message encoding, such as XML.
alternate currency | A currency that is different from the domestic currency (when dealing with a domestic-only transaction) or the domestic and foreign currency of a transaction. In JD Edwards EnterpriseOne Financial Management, alternate currency processing enables you to enter receipts and payments in a currency other than the one in which they were issued.
Application Server | Software that provides the business logic for an application program in a distributed environment. The servers can be Oracle Application Server (OAS) or WebSphere Application Server (WAS).
as if processing | A process that enables you to view currency amounts as if they were entered in a currency different from the domestic and foreign currency of the transaction.
as of processing | A process that is run as of a specific point in time to summarize transactions up to that date. For example, you can run various JD Edwards EnterpriseOne reports as of a specific date to determine balances and amounts of accounts, units, and so on as of that date.
Auto Commit Transaction | A database connection through which all database operations are immediately written to the database.
back-to-back process | A process in JD Edwards EnterpriseOne Supply Management that contains the same keys that are used in another process.
batch processing | A process of transferring records from a third-party system to JD Edwards EnterpriseOne. In JD Edwards EnterpriseOne Financial Management, batch processing enables you to transfer invoices and vouchers that are entered in a system other than JD Edwards EnterpriseOne to JD Edwards EnterpriseOne Accounts Receivable and JD Edwards EnterpriseOne Accounts Payable, respectively. In addition, you can transfer address book information, including customer and supplier records, to JD Edwards EnterpriseOne.
batch server | A server that is designated for running batch processing requests. A batch server typically does not contain a database nor does it run interactive applications.
batch-of-one immediate | A transaction method that enables a client application to perform work on a client workstation, then submit the work all at once to a server application for further processing. As a batch process is running on the server, the client application can continue performing other tasks. See also direct connect and store-and-forward.
best practices | Non-mandatory guidelines that help the developer make better design decisions.
BPEL | Abbreviation for Business Process Execution Language, a standard web services orchestration language, which enables you to assemble discrete services into an end-to-end process flow.
BPEL PM | Abbreviation for Business Process Execution Language Process Manager, a comprehensive infrastructure for creating, deploying, and managing BPEL business processes.
Build Configuration File | Configurable settings in a text file that are used by a build program to generate ANT scripts. ANT is a software tool used for automating build processes. These scripts build published business services.
build engineer | An actor that is responsible for building, mastering, and packaging artifacts. Some build engineers are responsible for building application artifacts, and some are responsible for building foundation artifacts.
Build Program | A WIN32 executable that reads build configuration files and generates an ANT script for building published business services.
business analyst | An actor that determines if and why an EnterpriseOne business service needs to be developed.
business function | A named set of user-created, reusable business rules and logs that can be called through event rules. Business functions can run a transaction or a subset of a transaction (check inventory, issue work orders, and so on). Business functions also contain the application programming interfaces (APIs) that enable them to be called from a form, a database trigger, or a non-JD Edwards EnterpriseOne application. Business functions can be combined with other business functions, forms, event rules, and other components to make up an application. Business functions can be created through event rules or third-generation languages, such as C. Examples of business functions include Credit Check and Item Availability.
business function event rule | See named event rule (NER).
business service | EnterpriseOne business logic written in Java. A business service is a collection of one or more artifacts. Unless specified otherwise, a business service implies both a published business service and business service.
business service artifacts | Source files, descriptors, and so on that are managed for business service development and are needed for the business service build process.
business service class method | A method that accesses resources provided by the business service framework.
business service configuration files | Configuration files include, but are not limited to, interop.ini, JDBj.ini, and jdelog.properties.
business service cross reference | A key and value data pair used during orchestration. Collectively refers to both the code and the key cross reference in the WSG/XPI based system.
business service cross-reference utilities | Utility services installed in a BPEL/ESB environment that are used to access JD Edwards EnterpriseOne orchestration cross-reference data.
business service development environment | A framework needed by an integration developer to develop and manage business services.
business services development tool | Otherwise known as JDeveloper.
business service EnterpriseOne object | A collection of artifacts managed by EnterpriseOne LCM tools. Named and represented within EnterpriseOne LCM similarly to other EnterpriseOne objects like tables, views, forms, and so on.
business service framework | Parts of the business service foundation that are specifically for supporting business service development.
business service payload | An object that is passed between an enterprise server and a business services server. The business service payload contains the input to the business service when passed to the business services server. The business service payload contains the results from the business service when passed to the Enterprise Server. In the case of notifications, the return business service payload contains the acknowledgement.
business service property | Key value data pairs used to control the behavior or functionality of business services.
Business Service Property Admin Tool | An EnterpriseOne application for developers and administrators to manage business service property records.
business service property business service group | A classification for business service property at the business service level. This is generally a business service name. A business service level contains one or more business service property groups. Each business service property group may contain zero or more business service property records.
business service property categorization | A way to categorize business service properties. These properties are categorized by business service.
business service property key | A unique name that identifies the business service property globally in the system.
business service property utilities | A utility API used in business service development to access EnterpriseOne business service property data.
business service property value | A value for a business service property.
business service repository | A source management system, for example ClearCase, where business service artifacts and build files are stored. Or, a physical directory in network.
business services server | The physical machine where the business services are located. Business services are run on an application server instance.
business services source file or business service class | One type of business service artifact. A text file with the .java file type written to be compiled by a Java compiler.
business service value object template | The structural representation of a business service value object used in a C-business function.
Business Service Value Object Template Utility | A utility used to create a business service value object template from a business service value object.
business services server artifact | The object to be deployed to the business services server.
business view | A means for selecting specific columns from one or more JD Edwards EnterpriseOne application tables whose data is used in an application or report. A business view does not select specific rows, nor does it contain any actual data. It is strictly a view through which you can manipulate data.
central objects merge | A process that blends a customer's modifications to the objects in a current release with objects in a new release.
central server | A server that has been designated to contain the originally installed version of the software (central objects) for deployment to client computers. In a typical JD Edwards EnterpriseOne installation, the software is loaded on to one machine—the central server. Then, copies of the software are pushed out or downloaded to various workstations attached to it. That way, if the software is altered or corrupted through its use on workstations, an original set of objects (central objects) is always available on the central server.
charts | Tables of information in JD Edwards EnterpriseOne that appear on forms in the software.
check-in repository | A repository for developers to check in and check out business service artifacts. There are multiple check-in repositories. Each can be used for a different purpose (for example, development, production, testing, and so on).
connector | Component-based interoperability model that enables third-party applications and JD Edwards EnterpriseOne to share logic and data. The JD Edwards EnterpriseOne connector architecture includes Java and COM connectors.
contra/clearing account | A general ledger account in JD Edwards EnterpriseOne Financial Management that is used by the system to offset (balance) journal entries. For example, you can use a contra/clearing account to balance the entries created by allocations in JD Edwards EnterpriseOne Financial Management.
Control Table Workbench | An application that, during the Installation Workbench processing, runs the batch applications for the planned merges that update the data dictionary, user-defined codes, menus, and user override tables.
control tables merge | A process that blends a customer's modifications to the control tables with the data that accompanies a new release.
correlation data | The data used to tie HTTP responses with requests that consist of business service name and method.
cost assignment | The process in JD Edwards EnterpriseOne Advanced Cost Accounting of tracing or allocating resources to activities or cost objects.
cost component | In JD Edwards EnterpriseOne Manufacturing, an element of an item’s cost (for example, material, labor, or overhead).
credentials | A valid set of JD Edwards EnterpriseOne username/password/environment/role, EnterpriseOne session, or EnterpriseOne token.
cross-reference utility services | Utility services installed in a BPEL/ESB environment that access EnterpriseOne cross-reference data.
cross segment edit | A logic statement that establishes the relationship between configured item segments. Cross segment edits are used to prevent ordering of configurations that cannot be produced.
currency restatement | The process of converting amounts from one currency into another currency, generally for reporting purposes. You can use the currency restatement process, for example, when many currencies must be restated into a single currency for consolidated reporting.
cXML | A protocol used to facilitate communication between business documents and procurement applications, and between e-commerce hubs and suppliers.
database credentials | A valid database username/password.
database server | A server in a local area network that maintains a database and performs searches for client computers.
Data Source Workbench | An application that, during the Installation Workbench process, copies all data sources that are defined in the installation plan from the Data Source Master and Table and Data Source Sizing tables in the Planner data source to the system-release number data source. It also updates the Data Source Plan detail record to reflect completion.
date pattern | A calendar that represents the beginning date for the fiscal year and the ending date for each period in that year in standard and 52-period accounting.
denominated-in currency | The company currency in which financial reports are based.
deployment artifacts | Artifacts that are needed for the deployment process, such as servers, ports, and such.
deployment server | A server that is used to install, maintain, and distribute software to one or more enterprise servers and client workstations.
detail information | Information that relates to individual lines in JD Edwards EnterpriseOne transactions (for example, voucher pay items and sales order detail lines).
direct connect | A transaction method in which a client application communicates interactively and directly with a server application. See also batch-of-one immediate and store-and-forward.
Do Not Translate (DNT) | A type of data source that must exist on the iSeries because of BLOB restrictions.
dual pricing | The process of providing prices for goods and services in two currencies.
duplicate published business services authorization records | Two published business services authorization records with the same user identification information and published business services identification information.
embedded application server instance | An OC4J instance started by and running wholly within JDeveloper.
edit code | A code that indicates how a specific value for a report or a form should appear or be formatted. The default edit codes that pertain to reporting require particular attention because they account for a substantial amount of information.
edit mode | A condition of a form that enables users to change data.
edit rule | A method used for formatting and validating user entries against a predefined rule or set of rules.
Electronic Data Interchange (EDI) | An interoperability model that enables paperless computer-to-computer exchange of business transactions between JD Edwards EnterpriseOne and third-party systems. Companies that use EDI must have translator software to convert data from the EDI standard format to the formats of their computer systems.
embedded event rule | An event rule that is specific to a particular table or application. Examples include form-to-form calls, hiding a field based on a processing option value, and calling a business function. Contrast with the business function event rule.
Employee Work Center | A central location for sending and receiving all JD Edwards EnterpriseOne messages (system and user generated), regardless of the originating application or user. Each user has a mailbox that contains workflow and other messages, including Active Messages.
enterprise server | A server that contains the database and the logic for JD Edwards EnterpriseOne.
Enterprise Service Bus (ESB) | Middleware infrastructure products or technologies based on web services standards that enable a service-oriented architecture using an event-driven and XML-based messaging framework (the bus).
EnterpriseOne administrator | An actor responsible for the EnterpriseOne administration system.
EnterpriseOne credentials | A user ID, password, environment, and role used to validate a user of EnterpriseOne.
EnterpriseOne object | A reusable piece of code that is used to build applications. Object types include tables, forms, business functions, data dictionary items, batch processes, business views, event rules, versions, data structures, and media objects.
EnterpriseOne development client | Historically called “fat client,” a collection of installed EnterpriseOne components required to develop EnterpriseOne artifacts, including the Microsoft Windows client and design tools.
EnterpriseOne extension | A JDeveloper component (plug-in) specific to EnterpriseOne. A JDeveloper wizard is a specific example of an extension.
EnterpriseOne process | A software process that enables JD Edwards EnterpriseOne clients and servers to handle processing requests and run transactions. A client runs one process, and servers can have multiple instances of a process. JD Edwards EnterpriseOne processes can also be dedicated to specific tasks (for example, workflow messages and data replication) to ensure that critical processes don't have to wait if the server is particularly busy.
EnterpriseOne resource | Any EnterpriseOne table, metadata, business function, dictionary information, or other information restricted to authorized users.
Environment Workbench | An application that, during the Installation Workbench process, copies the environment information and Object Configuration Manager tables for each environment from the Planner data source to the system-release number data source. It also updates the Environment Plan detail record to reflect completion.
escalation monitor | A batch process that monitors pending requests or activities and restarts or forwards them to the next step or user after they have been inactive for a specified amount of time.
event rule | A logic statement that instructs the system to perform one or more operations based on an activity that can occur in a specific application, such as entering a form or exiting a field.
explicit transaction | Transaction used by a business service developer to explicitly control the type (auto or manual) and the scope of transaction boundaries within a business service.
exposed method or value object | Published business service source files or parts of published business service source files that are part of the published interface. These are part of the contract with the customer.
facility | An entity within a business for which you want to track costs. For example, a facility might be a warehouse location, job, project, work center, or branch/plant. A facility is sometimes referred to as a “business unit.”
fast path | A command prompt that enables the user to move quickly among menus and applications by using specific commands.
file server | A server that stores files to be accessed by other computers on the network. Unlike a disk server, which appears to the user as a remote disk drive, a file server is a sophisticated device that not only stores files, but also manages them and maintains order as network users request files and make changes to these files.
final mode | The report processing mode of a processing mode of a program that updates or creates data records.
foundation | A framework that must be accessible for execution of business services at runtime. This includes, but is not limited to, the Java Connector and JDBj.
FTP server | A server that responds to requests for files via file transfer protocol.
header information | Information at the beginning of a table or form. Header information is used to identify or provide control information for the group of records that follows.
HTTP Adapter | A generic set of services that are used to do the basic HTTP operations, such as GET, POST, PUT, DELETE, TRACE, HEAD, and OPTIONS with the provided URL.
instantiate | A Java term meaning “to create.” When a class is instantiated, a new instance is created.
integration developer | The user of the system who develops, runs, and debugs the EnterpriseOne business services. The integration developer uses the EnterpriseOne business services to develop these components.
integration point (IP) | The business logic in previous implementations of EnterpriseOne that exposes a document level interface. This type of logic used to be called XBPs. In EnterpriseOne 8.11, IPs are implemented in Web Services Gateway powered by webMethods.
integration server | A server that facilitates interaction between diverse operating systems and applications across internal and external networked computer systems.
integrity test | A process used to supplement a company’s internal balancing procedures by locating and reporting balancing problems and data inconsistencies.
interface table | See Z table.
internal method or value object | Business service source files or parts of business service source files that are not part of the published interface. These could be private or protected methods. These could be value objects not used in published methods.
interoperability model | A method for third-party systems to connect to or access JD Edwards EnterpriseOne.
in-your-face-error | In JD Edwards EnterpriseOne, a form-level property which, when enabled, causes the text of application errors to appear on the form.
IServer service | This internet server service resides on the web server and is used to speed up delivery of the Java class files from the database to the client.
jargon | An alternative data dictionary item description that JD Edwards EnterpriseOne appears based on the product code of the current object.
Java application server | A component-based server that resides in the middle-tier of a server-centric architecture. This server provides middleware services for security and state maintenance, along with data access and persistence.
JDBNET | A database driver that enables heterogeneous servers to access each other's data.
JDEBASE Database Middleware | A JD Edwards EnterpriseOne proprietary database middleware package that provides platform-independent APIs, along with client-to-server access.
JDECallObject | An API used by business functions to invoke other business functions.
jde.ini | A JD Edwards EnterpriseOne file (or member for iSeries) that provides the runtime settings required for JD Edwards EnterpriseOne initialization. Specific versions of the file or member must reside on every machine running JD Edwards EnterpriseOne. This includes workstations and servers.
JDEIPC | Communications programming tools used by server code to regulate access to the same data in multiprocess environments, communicate and coordinate between processes, and create new processes.
jde.log | The main diagnostic log file of JD Edwards EnterpriseOne. This file is always located in the root directory on the primary drive and contains status and error messages from the startup and operation of JD Edwards EnterpriseOne.
JDENET | A JD Edwards EnterpriseOne proprietary communications middleware package. This package is a peer-to-peer, message-based, socket-based, multiprocess communications middleware solution. It handles client-to-server and server-to-server communications for all JD Edwards EnterpriseOne supported platforms.
JDeveloper Project | An artifact that JDeveloper uses to categorize and compile source files.
JDeveloper Workspace | An artifact that JDeveloper uses to organize project files. It contains one or more project files.
JMS Queue | A Java Messaging service queue used for point-to-point messaging.
listener service | A listener that listens for XML messages over HTTP.
local repository | A developer’s local development environment that is used to store business service artifacts.
local standalone BPEL/ESB server | A standalone BPEL/ESB server that is not installed within an application server.
Location Workbench | An application that, during the Installation Workbench process, copies all locations that are defined in the installation plan from the Location Master table in the Planner data source to the system data source.
logic server | A server in a distributed network that provides the business logic for an application program. In a typical configuration, pristine objects are replicated on to the logic server from the central server. The logic server, in conjunction with workstations, actually performs the processing required when JD Edwards EnterpriseOne software runs.
MailMerge Workbench | An application that merges Microsoft Word 6.0 (or higher) word-processing documents with JD Edwards EnterpriseOne records to automatically print business documents. You can use MailMerge Workbench to print documents, such as form letters about verification of employment.
Manual Commit transaction | A database connection where all database operations delay writing to the database until a call to commit is made.
master business function (MBF) | An interactive master file that serves as a central location for adding, changing, and updating information in a database. Master business functions pass information between data entry forms and the appropriate tables. These master functions provide a common set of functions that contain all of the necessary default and editing rules for related programs. MBFs contain logic that ensures the integrity of adding, updating, and deleting information from databases.
master table | See published table.
matching document | A document associated with an original document to complete or change a transaction. For example, in JD Edwards EnterpriseOne Financial Management, a receipt is the matching document of an invoice, and a payment is the matching document of a voucher.
media storage object | Files that use one of the following naming conventions that are not organized into table format: Gxxx, xxxGT, or GTxxx.
message center | A central location for sending and receiving all JD Edwards EnterpriseOne messages (system and user generated), regardless of the originating application or user.
messaging adapter | An interoperability model that enables third-party systems to connect to JD Edwards EnterpriseOne to exchange information through the use of messaging queues.
messaging server | A server that handles messages that are sent for use by other programs using a messaging API. Messaging servers typically employ a middleware program to perform their functions.
Middle-Tier BPEL/ESB Server | A BPEL/ESB server that is installed within an application server.
Monitoring Application | An EnterpriseOne tool provided for an administrator to get statistical information for various EntepriseOne servers, reset statistics, and set notifications.
named event rule (NER) | Encapsulated, reusable business logic created using event rules, rather that C programming. NERs are also called business function event rules. NERs can be reused in multiple places by multiple programs. This modularity lends itself to streamlining, reusability of code, and less work.
nota fiscal | In Brazil, a legal document that must accompany all commercial transactions for tax purposes and that must contain information required by tax regulations.
nota fiscal factura | In Brazil, a nota fiscal with invoice information. See also nota fiscal.
Object Configuration Manager (OCM) | In JD Edwards EnterpriseOne, the object request broker and control center for the runtime environment. OCM keeps track of the runtime locations for business functions, data, and batch applications. When one of these objects is called, OCM directs access to it using defaults and overrides for a given environment and user.
Object Librarian | A repository of all versions, applications, and business functions reusable in building applications. Object Librarian provides check-out and check-in capabilities for developers, and it controls the creation, modification, and use of JD Edwards EnterpriseOne objects. Object Librarian supports multiple environments (such as production and development) and enables objects to be easily moved from one environment to another.
Object Librarian merge | A process that blends any modifications to the Object Librarian in a previous release into the Object Librarian in a new release.
Open Data Access (ODA) | An interoperability model that enables you to use SQL statements to extract JD Edwards EnterpriseOne data for summarization and report generation.
Output Stream Access (OSA) | An interoperability model that enables you to set up an interface for JD Edwards EnterpriseOne to pass data to another software package, such as Microsoft Excel, for processing.
package | JD Edwards EnterpriseOne objects are installed to workstations in packages from the deployment server. A package can be compared to a bill of material or kit that indicates the necessary objects for that workstation and where on the deployment server the installation program can find them. It is point-in-time snapshot of the central objects on the deployment server.
package build | A software application that facilitates the deployment of software changes and new applications to existing users. Additionally, in JD Edwards EnterpriseOne, a package build can be a compiled version of the software. When you upgrade your version of the ERP software, for example, you are said to take a package build. Consider the following context: “Also, do not transfer business functions into the production path code until you are ready to deploy, because a global build of business functions done during a package build will automatically include the new functions.” The process of creating a package build is often referred to, as it is in this example, simply as “a package build.”
package location | The directory structure location for the package and its set of replicated objects. This is usually \\deployment server\release\path_code\package\package name. The subdirectories under this path are where the replicated objects for the package are placed. This is also referred to as where the package is built or stored.
Package Workbench | An application that, during the Installation Workbench process, transfers the package information tables from the Planner data source to the system-release number data source. It also updates the Package Plan detail record to reflect completion.
Pathcode Directory | The specific portion of the file system on the EnterpriseOne development client where EnterpriseOne development artifacts are stored.
patterns | General repeatable solutions to a commonly occurring problem in software design. For business service development, the focus is on the object relationships and interactions. For orchestrations, the focus is on the integration patterns (for example, synchronous and asynchronous request/response, publish, notify, and receive/reply).
planning family | A means of grouping end items whose similarity of design and manufacture facilitates being planned in aggregate.
preference profile | The ability to define default values for specified fields for a user-defined hierarchy of items, item groups, customers, and customer groups.
print server | The interface between a printer and a network that enables network clients to connect to the printer and send their print jobs to it. A print server can be a computer, separate hardware device, or even hardware that resides inside of the printer itself.
pristine environment | A JD Edwards EnterpriseOne environment used to test unaltered objects with JD Edwards EnterpriseOne demonstration data or for training classes. You must have this environment so that you can compare pristine objects that you modify.
processing option | A data structure that enables users to supply parameters that regulate the running of a batch program or report. For example, you can use processing options to specify default values for certain fields, to determine how information appears or is printed, to specify date ranges, to supply runtime values that regulate program execution, and so on.
production environment | A JD Edwards EnterpriseOne environment in which users operate EnterpriseOne software.
production-grade file server | A file server that has been quality assurance tested and commercialized and that is usually provided in conjunction with user support services.
Production Published Business Services Web Service | Published business services web service deployed to a production application server.
program temporary fix (PTF) | A representation of changes to JD Edwards EnterpriseOne software that your organization receives on magnetic tapes or disks.
project | In JD Edwards EnterpriseOne, a virtual container for objects being developed in Object Management Workbench.
promotion path | The designated path for advancing objects or projects in a workflow. The following is the normal promotion cycle (path): 11>21>26>28>38>01 In this path, 11 equals new project pending review, 21 equals programming, 26 equals QA test/review, 28 equals QA test/review complete, 38 equals in production, 01 equals complete. During the normal project promotion cycle, developers check objects out of and into the development path code and then promote them to the prototype path code. The objects are then moved to the productions path code before declaring them complete.
proxy server | A server that acts as a barrier between a workstation and the internet so that the enterprise can ensure security, administrative control, and caching service.
published business service | EnterpriseOne service level logic and interface. A classification of a published business service indicating the intention to be exposed to external (non-EnterpriseOne) systems.
published business service identification information | Information about a published business service used to determine relevant authorization records. Published business services + method name, published business services, or *ALL.
published business service web service | Published business services components packaged as J2EE Web Service (namely, a J2EE EAR file that contains business service classes, business service foundation, configuration files, and web service artifacts).
published table | Also called a master table, this is the central copy to be replicated to other machines. Residing on the publisher machine, the F98DRPUB table identifies all of the published tables and their associated publishers in the enterprise.
publisher | The server that is responsible for the published table. The F98DRPUB table identifies all of the published tables and their associated publishers in the enterprise.
pull replication | One of the JD Edwards EnterpriseOne methods for replicating data to individual workstations. Such machines are set up as pull subscribers using JD Edwards EnterpriseOne data replication tools. The only time that pull subscribers are notified of changes, updates, and deletions is when they request such information. The request is in the form of a message that is sent, usually at startup, from the pull subscriber to the server machine that stores the F98DRPCN table.
QBE | An abbreviation for query by example. In JD Edwards EnterpriseOne, the QBE line is the top line on a detail area that is used for filtering data.
real-time event | A message triggered from EnterpriseOne application logic that is intended for external systems to consume.
refresh | A function used to modify JD Edwards EnterpriseOne software, or subset of it, such as a table or business data, so that it functions at a new release or cumulative update level, such as B73.2 or B73.2.1.
replication server | A server that is responsible for replicating central objects to client machines.
Rt-Addressing | Unique data identifying a browser session that initiates the business services call request host/port user session.
rules | Mandatory guidelines that are not enforced by tooling, but must be followed in order to accomplish the desired results and to meet specified standards.
quote order | In JD Edwards Procurement and Subcontract Management, a request from a supplier for item and price information from which you can create a purchase order. In JD Edwards Sales Order Management, item and price information for a customer who has not yet committed to a sales order.
secure by default | A security model that assumes that a user does not have permission to execute an object unless there is a specific record indicating such permissions.
Secure Socket Layer (SSL) | A security protocol that provides communication privacy. SSL enables client and server applications to communicate in a way that is designed to prevent eavesdropping, tampering, and message forgery.
SEI implementation | A Java class that implements the methods that declare in a Service Endpoint Interface (SEI).
selection | Found on JD Edwards EnterpriseOne menus, a selection represents functions that you can access from a menu. To make a selection, type the associated number in the Selection field and press Enter.
serialize | The process of converting an object or data into a format for storage or transmission across a network connection link with the ability to reconstruct the original data or objects when needed.
Server Workbench | An application that, during the Installation Workbench process, copies the server configuration files from the Planner data source to the system-release number data source. The application also updates the Server Plan detail record to reflect completion.
Service Endpoint Interface (SEI) | A Java interface that declares the methods that a client can invoke on the service.
SOA | Abbreviation for Service Oriented Architecture.
softcoding | A coding technique that enables an administrator to manipulate site-specific variables that affect the execution of a given process.
source repository | A repository for HTTP adapter and listener service development environment artifacts.
spot rate | An exchange rate entered at the transaction level. This rate overrides the exchange rate that is set up between two currencies.
Specification merge | A merge that comprises three merges: Object Librarian merge, Versions List merge, and Central Objects merge. The merges blend customer modifications with data that accompanies a new release.
specification | A complete description of a JD Edwards EnterpriseOne object. Each object has its own specification, or name, which is used to build applications.
Specification Table Merge Workbench | An application that, during the Installation Workbench process, runs the batch applications that update the specification tables.
SSL Certificate | A special message signed by a certificate authority that contains the name of a user and that user's public key in such a way that anyone can "verify" that the message was signed by no one other than the certification authority and thereby develop trust in the user's public key.
store-and-forward | The mode of processing that enables users who are disconnected from a server to enter transactions and then later connect to the server to upload those transactions.
subscriber table | Table F98DRSUB, which is stored on the publisher server with the F98DRPUB table and identifies all of the subscriber machines for each published table.
superclass | An inheritance concept of the Java language where a class is an instance of something, but is also more specific. “Tree” might be the superclass of “Oak” and “Elm,” for example.
supplemental data | Any type of information that is not maintained in a master file. Supplemental data is usually additional information about employees, applicants, requisitions, and jobs (such as an employee's job skills, degrees, or foreign languages spoken). You can track virtually any type of information that your organization needs. For example, in addition to the data in the standard master tables (the Address Book Master, Customer Master, and Supplier Master tables), you can maintain other kinds of data in separate, generic databases. These generic databases enable a standard approach to entering and maintaining supplemental data across JD Edwards EnterpriseOne systems.
table access management (TAM) | The JD Edwards EnterpriseOne component that handles the storage and retrieval of use-defined data. TAM stores information, such as data dictionary definitions; application and report specifications; event rules; table definitions; business function input parameters and library information; and data structure definitions for running applications, reports, and business functions.
Table Conversion Workbench | An interoperability model that enables the exchange of information between JD Edwards EnterpriseOne and third-party systems using non-JD Edwards EnterpriseOne tables.
table conversion | An interoperability model that enables the exchange of information between JD Edwards EnterpriseOne and third-party systems using non-JD Edwards EnterpriseOne tables.
table event rules | Logic that is attached to database triggers that runs whenever the action specified by the trigger occurs against the table. Although JD Edwards EnterpriseOne enables event rules to be attached to application events, this functionality is application specific. Table event rules provide embedded logic at the table level.
terminal server | A server that enables terminals, microcomputers, and other devices to connect to a network or host computer or to devices attached to that particular computer.
three-tier processing | The task of entering, reviewing and approving, and posting batches of transactions in JD Edwards EnterpriseOne.
three-way voucher match | In JD Edwards Procurement and Subcontract Management, the process of comparing receipt information to supplier’s invoices to create vouchers. In a three-way match, you use the receipt records to create vouchers.
transaction processing (TP) monitor | A monitor that controls data transfer between local and remote terminals and the applications that originated them. TP monitors also protect data integrity in the distributed environment and may include programs that validate data and format terminal screens.
transaction processing method | A method related to the management of a manual commit transaction boundary (for example, start, commit, rollback, and cancel).
transaction set | An electronic business transaction (electronic data interchange standard document) made up of segments.
trigger | One of several events specific to data dictionary items. You can attach logic to a data dictionary item that the system processes automatically when the event occurs.
triggering event | A specific workflow event that requires special action or has defined consequences or resulting actions.
two-way authentication | An authentication mechanism in which both client and server authenticate themselves by providing the SSL certificates to each other.
two-way voucher match | In JD Edwards Procurement and Subcontract Management, the process of comparing purchase order detail lines to the suppliers’ invoices to create vouchers. You do not record receipt information.
user identification information | User ID, role, or *public.
User Overrides merge | Adds new user override records into a customer’s user override table.
value object | A specific type of source file that holds input or output data, much like a data structure passes data. Value objects can be exposed (used in a published business service) or internal, and input or output. They are comprised of simple and complex elements and accessories to those elements.
variance | In JD Edwards Capital Asset Management, the difference between revenue generated by a piece of equipment and costs incurred by the equipment. In JD Edwards EnterpriseOne Project Costing and JD Edwards EnterpriseOne Manufacturing, the difference between two methods of costing the same item (for example, the difference between the frozen standard cost and the current cost is an engineering variance). Frozen standard costs come from the Cost Components table, and the current costs are calculated using the current bill of material, routing, and overhead rates.
versioning a published business service | Adding additional functionality/interfaces to the published business services without modifying the existing functionality/interfaces.
Version List merge | The Versions List merge preserves any non-XJDE and non-ZJDE version specifications for objects that are valid in the new release, as well as their processing options data.
visual assist | Forms that can be invoked from a control via a trigger to assist the user in determining what data belongs in the control.
vocabulary override | An alternate description for a data dictionary item that appears on a specific JD Edwards EnterpriseOne form or report.
wchar_t | An internal type of a wide character. It is used for writing portable programs for international markets.
web application server | A web server that enables web applications to exchange data with the back-end systems and databases used in eBusiness transactions.
web server | A server that sends information as requested by a browser, using the TCP/IP set of protocols. A web server can do more than just coordination of requests from browsers; it can do anything a normal server can do, such as house applications or data. Any computer can be turned into a web server by installing server software and connecting the machine to the internet.
Web Service Description Language (WSDL) | An XML format for describing network services.
Web Service Inspection Language (WSIL) | An XML format for assisting in the inspection of a site for available services and a set of rules for how inspection-related information should be made.
web service proxy foundation | Foundation classes for web service proxy that must be included in a business service server artifact for web service consumption on WAS.
web service softcoding record | An XML document that contains values that are used to configure a web service proxy. This document identifies the endpoint and conditionally includes security information.
web service softcoding template | An XML document that provides the structure for a soft coded record.
Where clause | The portion of a database operation that specifies which records the database operation will affect.
Windows terminal server | A multiuser server that enables terminals and minimally configured computers to display Windows applications even if they are not capable of running Windows software themselves. All client processing is performed centrally at the Windows terminal server and only display, keystroke, and mouse commands are transmitted over the network to the client terminal device.
wizard | A type of JDeveloper extension used to walk the user through a series of steps.
workbench | A program that enables users to access a group of related programs from a single entry point. Typically, the programs that you access from a workbench are used to complete a large business process. For example, you use the JD Edwards EnterpriseOne Payroll Cycle Workbench (P07210) to access all of the programs that the system uses to process payroll, print payments, create payroll reports, create journal entries, and update payroll history. Examples of JD Edwards EnterpriseOne workbenches include Service Management Workbench (P90CD020), Line Scheduling Workbench (P3153), Planning Workbench (P13700), Auditor's Workbench (P09E115), and Payroll Cycle Workbench.
work day calendar | In JD Edwards EnterpriseOne Manufacturing, a calendar that is used in planning functions that consecutively lists only working days so that component and work order scheduling can be done based on the actual number of work days available. A work day calendar is sometimes referred to as planning calendar, manufacturing calendar, or shop floor calendar.
workflow | The automation of a business process, in whole or in part, during which documents, information, or tasks are passed from one participant to another for action, according to a set of procedural rules.
workgroup server | A server that usually contains subsets of data replicated from a master network server. A workgroup server does not perform application or batch processing.
XAPI events | A service that uses system calls to capture JD Edwards EnterpriseOne transactions as they occur and then calls third-party software, end users, and other JD Edwards EnterpriseOne systems that have requested notification when the specified transactions occur to return a response.
XML CallObject | An interoperability capability that enables you to call business functions.
XML Dispatch | An interoperability capability that provides a single point of entry for all XML documents coming into JD Edwards EnterpriseOne for responses.
XML List | An interoperability capability that enables you to request and receive JD Edwards EnterpriseOne database information in chunks.
XML Service | An interoperability capability that enables you to request events from one JD Edwards EnterpriseOne system and receive a response from another JD Edwards EnterpriseOne system.
XML Transaction | An interoperability capability that enables you to use a predefined transaction type to send information to or request information from JD Edwards EnterpriseOne. XML transaction uses interface table functionality.
XML Transaction Service (XTS) | Transforms an XML document that is not in the JD Edwards EnterpriseOne format into an XML document that can be processed by JD Edwards EnterpriseOne. XTS then transforms the response back to the request originator XML format.
Z event | A service that uses interface table functionality to capture JD Edwards EnterpriseOne transactions and provide notification to third-party software, end users, and other JD Edwards EnterpriseOne systems that have requested to be notified when certain transactions occur.
Z table | A working table where non-JD Edwards EnterpriseOne information can be stored and then processed into JD Edwards EnterpriseOne. Z tables also can be used to retrieve JD Edwards EnterpriseOne data. Z tables are also known as interface tables.
Z transaction | Third-party data that is properly formatted in interface tables for updating to the JD Edwards EnterpriseOne database.