E1: PKG: Package Assembly - Building Update Packages With Objects Based On a Project Name in Object Management Workbench (OMW) (Doc ID 626382.1)

Last updated on JULY 17, 2017

Applies to:

JD Edwards EnterpriseOne Tools - Version SP24 and later
Information in this document applies to any platform.

Goal

This document describes how to build update packages with objects based on project names.
Building Update Packages With Objects Based On a Project Name in Object Management Workbench (OMW).

When in Package Assembly there could be problems when searching on versions that have been included in a Project in OMW. In Package Assembly when a search is done on an OMW Project Name, the application looks at the F9861 table in the Modification Comment (SIMODCMT) field and finds all the records it has based on the Project Name. This field gets updated after an object in the Project is checked in. When OMW is delivered the default activity rules are set to allow check-in and check-out rules from DV900.

Before building an update package with objects (including UBE templates/versions) based on the search by "OMW Project Name" field, the objects should already be included in the OMW Project and checked in through the same Project. In the case of UBEs the templates and it's versions should be included in the Project and checked in.

When the objects are not included as part of the OMW Project, objects can still be selected by doing a search based on the "Object Name" field in Package Assembly. If a UBE is selected, the user will be directed to the versions selection screen. However, the specs for the package that is being built are going to be based on what is currently in Central Objects for the objects selected.

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms