This document contains answers to common questions about working with objects and packages in Oracle Manufacturing Objects Warehouse (OMW) projects. It explains why an object removed from a project may still show up when assembling a package, how to verify the object's project assignment and remove incorrect assignments. It also describes that only versions added to a project along with the base UBE will be included in package assembly, and provides several methods to view the contents of an assembled update package, including package reports, database tables, and the package manifest file.
This document contains answers to common questions about working with objects and packages in Oracle Manufacturing Objects Warehouse (OMW) projects. It explains why an object removed from a project may still show up when assembling a package, how to verify the object's project assignment and remove incorrect assignments. It also describes that only versions added to a project along with the base UBE will be included in package assembly, and provides several methods to view the contents of an assembled update package, including package reports, database tables, and the package manifest file.
This document contains answers to common questions about working with objects and packages in Oracle Manufacturing Objects Warehouse (OMW) projects. It explains why an object removed from a project may still show up when assembling a package, how to verify the object's project assignment and remove incorrect assignments. It also describes that only versions added to a project along with the base UBE will be included in package assembly, and provides several methods to view the contents of an assembled update package, including package reports, database tables, and the package manifest file.
3. Why would an object that has been removed from a OMW
Project stillshow in the same project when assembling a package by project? Answer: User is assembling an update package. When selecting objects to be included in the package based upon project name,an object (for example UBE R770631D) is included when this object is no longer part of that project. It was once insidethe project, but it has since been removed from the project. Why is it still showing up? First verify which project has the token for the object(s); and in this example there were no tokens assigned to object inquestion R770631D at the token queue. Next, open UTB, and then open F9861 table in "Object Librarian - 910" DataSource. Search for the relevant object, in this case R770631D. Make sure for the pathcode you are assembling apackage, the SIMODCMT column for the record is NOT populated. If it is, remove the value and retest if it shows upin Package Assembly. It will fix this issue. Note that there is not an application to update the F9861 table. This willneed to be done by your DBA. 4. How to get OMW projects with versions only to show in PackageAssembly? How to get OMW projects with versions only to show in Package Assembly application (P9601) without base UBE inprojects. Answer: The question is whether or not there is a way to add a version to a project and have only that version addedwhen using Package Assembly. This has been tested and there is NO alternative - the template or base UBE must alsobe included in the OMW project. This is true whether you add the version to a project and add the project to thepackage or just select the object individually using the 'Browse' in Package Assembly. 5. How to get the list of objects in an update package? Answer: Methods available: 1. The pdf(s) generated by either Client Package UBE R9621 or Server Package UBE R9622 (Package Build). 2. Assemble Package or Package History and look at the information for the package. As you expand the + to see thesublistings, there will be one for Objects. 3. Table F9631. You can use UTB to open the table. Package name is in column PDPKGNAME and object is in columnPDOBNM. If the same package was built multiple times, then you can retrieve the list by adding DATE and TIME to5/11/2021 Note: 2258067.2 https://support.oracle.com/epmos/faces/DocumentDisplay? _afrLoop=214690228802991&id=2258067.2&_afrWindowMode=0&_adf.ctrl-state=1bcbpg… 4/36 Classification: Internal
the search criteria;
4. Over the file manifest.xml. It is located in: \<Release>\<Pathcode> \PACKAGE\<package> \spec\MANIFEST.zip NOTE: Method 4 is applicable for EnterpriseOne