| Parameter Name | Data Item | Data Type | Req/Opt | I/O/Both |
|---|
| szTableName | OBNM | char | OPT | INPUT |
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
|
| szObjectName | OBNM | char | OPT | INPUT |
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
|
| idCursor | GENLNG | ID | OPT | BOTH |
General purpose ID variable. |
| szGenericTextKey | CDCDES | char | OPT | OUTPUT |
This field is dynamic and its name and function depends upon the build step highlighted. The possible names and functions are as follows:
o Description - A short description of the highlighted build step.
o Target Folder - A relative path where the output of the build step will be
placed.
o Executable - A Microsoft Windows executable program. You can use this field to display the path and name of this program. |