Object Movement

When you perform any of these tasks, objects move between the central objects location and the object destination:

Check in or check out objects.
Add existing objects to a project.
Perform a get object in Oracle's JD Edwards EnterpriseOne Object Management Workbench application (P98220).
Run Oracle's JD Edwards EnterpriseOne Workstation Installation application.
During the workstation installation, all objects and the Supported Local Database, which contains replicated data, are copied from the package to the workstation. The system copies objects in only those packages for which you included specifications. If the package does not include specifications, objects are not replicated; instead, they are installed on the workstation through just-in-time installation.

Unless otherwise noted, object movement is the same when you check objects in or out, add objects to a project, or perform a get object. This table describes the objects and specifications that move when you check in, check out, add, or get each type of object:

Object Type	Movement
Table (object type TBLE)	These objects move: Table specs Table event rule specifications (If the tables have event rules) Source files (.c) Table header files (.h) Object files (.obj) (If the objects have event rules) Table event rule include files (.hxx) (If the tables have event rules) The table header is not the same as the actual table that resides in a database. The table itself is created through Table Design Aid when you generate it. The JD Edwards EnterpriseOne Workstation Installation program copies this table to the workstation if the table is stored in the Supported Local Database.
Business view (object type BSVW)	These objects move: Specifications .h files (if generated)
C business function (object type BSFN, source language C)	These objects move: Specifications Source files (.c) Header files (.h) Object files (*.obj)
NER business functions	Business function event rules (object type BSFN) can be checked out. When business function event rules are checked out, the .h file moves to the include directory, the .c file moves to the source directory, the .obj moves to the obj directory, and the local specifications are updated. These objects move: Specifications Source (.c) Header (.h) Object (*.obj)
Business function data structure (object type DSTR)	Specifications move.
Embedded event rules	You cannot check out embedded event rules. Embedded event rules move when you check out the object in which the event rule is embedded. For example, if embedded event rules are attached to a table, interactive application, or batch application, when you move the table or application, the specifications for the embedded event rules move with it.
Media object data structure (object type GT)	Data structure specifications move.
Interactive application (object type APPL)	These specifications move: Application Form Form data structure Embedded event rules
Batch application (object type UBE)	These objects move: Report and event rule specifications (check in and check out the version separately from the report) .h file (if generated by the developer)
Business Services (object type BSFN, source language Java) These objects are type BSFN except for: F9860.SIPARDLL = " F9860.SISRCLNG = "SBF"	These objects can be checked out and checked back in. The IDE for development of business services objects is JDeveloper. When they are checked out, the <F9860.SIOBNM>.zip file is copied from the path code check-in location on the deployment server (<path code>/java/sbfjars) to the <EnterpriseOne client install>/<path code>/java/source/<F9860.SIOBNM> folder on the Microsoft WIN32 client, and the contents are extracted. When they are checked in, the contents of the <EnterpriseOne client install>/<path code>/java/source/<F9860.SIOBNM> folder are compressed to a <F9860.SIOBNM>.zip file and the file is copied to the path code check-in location.
User Defined Objects (object types E1PAGE, WATCHLIST, QUERY, FORMAT, CAFE1, COMPOSITE PAGE (Release 9.2.0.2), IMAGE (Release 9.2.0.2), and ONEVIEW	User Defined Objects are web-based objects. They are managed with the Web Based Object Management application (P98220W). They can be administered via the Web Based Object Administration application (P9822U). These objects move differently than other objects. On check-in (share/publish), their components are consolidated into a single zip file and inserted as a single record to the F98700R (Object Archive Repository). This replaces the objects' existing repository record if one exists. The single record is also inserted into the F98700H (Object Archive History). This record will coexist with other history records for the same object. All UDO types include the following data in .xml format: One F9860W record. One F9861W record. Zero to many F9860WD records. Zero to many F98700D records. Zero to many F98700H records. Zero or one F952460 record. Additional .xml data included in the .zip file for each type are: E1PAGE (EnterpriseOne Pages) - One F952400 record. COMPOSITE PAGE (Composite Page) - One F952410 record. (Release 9.2.0.2) IMAGE (Image) - One F952415 record. (Release 9.2.0.2) WATCHLIST (One View Watchlists) - One F952420 record. QUERY (Advanced Query) - One F952430 record. FORMAT (Grid Format) - One F952440 record. CAFE1 (Composite Application Framework) - One F952450 record. ONEVIEW (One View Reports) - One F952400 record plus associated artifacts from the BI Publisher server. On transfer, the object's current repository record is transferred from central objects in the source path code to central objects in the target path code (for example, DV910.F98700R to PD910.F9870R). When the UDO is first used in the target path code, its F98700R record is unpacked and moved to the runtime tables (F9860W, F9861W, F9860WD, and associated UDO tables (F9524*). These objects are not included in traditional packages and do not require deployment to the servers. They are created on the servers and reside their immediately.