| Parameter Name | Data Item | Data Type | Req/Opt | I/O/Both |
|---|
| szObjectName | OBNM | char | NONE | NONE |
The name that identifies a system object. J.D. Edwards ERP 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:
o Batch Applications (such as reports)
o Interactive Applications
o Business Views
o Business Functions
o
Business Functions Data Structures
o Event Rules
o Media Object Data Structures
|
| szFromDataSource | DATS | char | NONE | NONE |
OneWorld uses this data source if the primary data source or the data item in the primary data source cannot be located. |
| szToDataSource | DATS | char | NONE | NONE |
OneWorld uses this data source if the primary data source or the data item in the primary data source cannot be located. |
| cAddsOnlyObject | ADDC | char | NONE | NONE |
The Add/Change flags determines if the form is in add or change mode. |
| szFromEnvironment | LL | char | NONE | NONE |
The name associated with a specific list of libraries. The J98INITA initial program uses these library list names to control environments that
a user can sign on to. These configurations of library lists are maintained in the Library List Master File table (F0094).
This field represents a
valid environment that can be used to run in PeopleSoft EnterpriseOne. The environment encompasses both a path code (objects), and a
data source (data). When put together, users have a valid workplace within the system.
|
| szToEnvironment | LL | char | NONE | NONE |
The name associated with a specific list of libraries. The J98INITA initial program uses these library list names to control environments that
a user can sign on to. These configurations of library lists are maintained in the Library List Master File table (F0094).
This field represents a
valid environment that can be used to run in PeopleSoft EnterpriseOne. The environment encompasses both a path code (objects), and a
data source (data). When put together, users have a valid workplace within the system.
|
| szUBEName | PID | char | NONE | NONE |
The number that identifies the batch or interactive program (batch or interactive object). For example, the number of the Sales Order Entry
interactive program is P4210, and the number of the Print Invoices batch process report is R42565.
The program ID is a variable length value.
It is assigned according to a structured syntax in the form TSSXXX, where:
T
The first character of the number is alphabetic and identifies the
type, such as P for Program, R for Report, and so on. For example, the value P in the number P4210 indicates that the object is a
program.
SS
The second and third characters of the number are numeric and identify the system code. For example, the value 42 in the number P4210
indicates that this program belongs to system 42, which is the Sales Order Processing system.
XXX
The remaining characters of the numer are
numeric and identify a unique program or report. For example, the value 10 in the number P4210 indicates that this is the Sales Order Entry
program.
|
| szUBEVersion | VERS | char | NONE | NONE |
A user-defined set of specifications that control how applications and reports run. You use versions to group and save a set of user-defined
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 choose a version. |