Customization Manager 14-41
• File comparison to report missing files or version differences.
• Technology Stack Details - For each given property, this table lists the value for the
package and the Oracle E-Business Suite instance, and how they compare to each
other.
Searching for a Report
You can search for a report by its name on the main Package Report page, or click the
Advanced Search link to search based on additional criteria, including:
E-Business Suite Mapping - The E-Business Suite mapping used for the report
generation or comparison.
• Primary Package - The primary package for the report.
• Secondary Package - The secondary package, if any. The secondary package would
be used in Comparison Reports.
• Type - The type of report; either Standard, Comparison, or Instance Comparison.
• Report Format - The format chosen for the report; either PDF, RTF, or XLS.
Releasing and Sharing a Package
After a package is released, it is implicitly shared with other users to deploy. Use the
Update Package Metadata page to release a package. See: Updating Package Metadata,
page 14-33.
Note: With the Change Approval Framework, once an approver
approves a request to release a customization package from a user, the
package is released. The user does not need to release the package
explicitly after the approval.
Before you deploy a custom package in Patch Manager, you should run the Instance
Comparison Report to compare the technology stack properties of the package with
those of the instance to which the package is being deployed. Patch Manager does not
stop the deployment of a patch if the technology stack properties are not compatible, so
you should make your best judgement based on the Instance Comparison Reports.
Comentarios a estos manuales