| Parameter Name | Data Item | Data Type | Req/Opt | I/O/Both |
|---|
| szOMWProjectName | OMWPRJID | char | OPT | NONE |
An identifier for a OneWorld project. A OneWorld project is composed of a group of OneWorld objects that have been modified or created
by a developer to complete a task. All work with objects within OneWorld must occur within the context of a project. |
| szOMWProjectUser | OMWUSER | char | OPT | NONE |
A value that indicates the user or group for which the To status is valid. If the user is not set up for a valid To status, then the user may not
advance a project to that status.
*PUBLIC is a valid value for this field. |
| szOMWObjectName | OMWOBJID | char | OPT | NONE |
A 200-character field that serves as an identifier for a OneWorld object. When used in conjunction with an Object Management Workbench
Object Type (OMWOT),it uniquely identifies any OneWorld object. See the H92/OT UDC for a list of object types that can use this field to
store their identifiers. |
| szOMWObjectType | OMWOT | char | OPT | NONE |
In OneWorld, an object has traditionally been a reusable entity based on software specification created by the OneWorld Tools. These
objects included Object Librarian Objects, such as interactive applications (APPL), as well as batch applications (UBE), and data structure
(DSTR) objects. In OMW, we have expanded this definition to include other Non Object Librarian type objects or data source based rather than
path code based objects. These include User Defined Controls (UDC), Workflow, ActivEra, Menus, and Data Items. OL Objects:
o Batch
Applications
o Business functions
o Business views
o Data structures
o Event rules
o Interactive applications
o Media Objects
o
Tables Non-OL Objects
o Data dictionary items
o UDC items
o Workflow items
o Menus |
| szObjectRelease | SRCRLS | char | OPT | NONE |
The transfer rule only applies to objects in the project for this release (objects are always tied to a release within a project). The From and
To Release fields should always be equal. |
| szMachineKey | MKEY | char | OPT | NONE |
The Location or Machine Key indicates the name of the machine on the network (server or workstation).
|
| szNameObject | OBNM | char | OPT | 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
|
| szVersion | VERS | char | OPT | 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. |
| cOMWProofOrFinalMode | OMWPOF | char | OPT | NONE |
|
| szOMWUserRole | OMWUR | char | OPT | NONE |
A definition of the user's function within a project. Project managers generally assign a user to a project. When they do so, they indicate
what role that user will be playing. Examples of User Roles are:
01 Originator: Person who originated the project or the need for the project.
02 Developer: Person who modifies project objects.
03 Manager: Person who manages the project.
04 Quality Assurance:
Person who checks the project's functionality.
06 Administrator: Person who configure project status, user roles, objects, etc. |