Generate Extensions Report

The Generate Extensions Report (GEXTRPT) page allows you to generate reports on page extensions. There is a separate GEXTRPT page for each application, which allows you to generate reports for pages specific to each application as well as common pages.

You can generate reports for pages that have file-based extensions, migrated extensions, or extensions that are pending migration or under development on DESIGNER. If a page is registered on Application Page Registration (APGS or ERPAPGS), you can specify the page code(s) to generate reports for specific pages. Leave the page code blank to generate a report for all pages with extensions, including those that are not registered.

The report generates as a .csv file and is deposited in the extension_report folder within the Export/Import directory corresponding to the application. The file name includes the user ID that performed the Generate Report action and follows the format: extension_report_userID.csv. After report generation, you can download the report. Each time you generate the report, the file is overwritten. If you need to generate multiple reports, please generate the report one at a time, and download the file before generating the next report. You can use the File Transfer Maintenance (FUD) page to download the report if you have access to the Export/Import directory extension_report folder on FUD.

Report generation uses PalDb and the ADV_EXT_ONLN table in the Common schema as input. After applying file-based extensions or running the Designer Sync to XML job to migrate DESIGNER extensions to xml, make sure to follow up with the post_cd process to deploy the extensions in the environment and bounce the application. Refer to the Extract Deploy Extension Metadata Guide for more information.

ActionsActions

Generate Report - This action generates the extension report. You can continue using the application while the report generates in the background.
Reset - This action clears the Page Code(s) field.

Example Report UsageExample Report Usage

Compare extensions between different environments - For example, after extensions have been migrated from a staging environment to a testing environment, you can run the report in both environments and then compare them to verify that the extensions have been migrated successfully.
Research extensions for a specific page - If the page is registered, you can run the report for the specific page to see all page extensions.

How to Interpret the ReportHow to Interpret the Report

The report is intended to be used by users who are familiar with extension metadata. The generated .csv file contains a header row indicating the field names, followed by one or more rows where each row shows one property of the changed element within the specified page under global or conditional extension.

The rows appear in the order that the extensions are processed while generating the report. If desired, you can open the .csv file as a spreadsheet and group related entries together by sorting the non-header rows by Page Key, Condition, Condition Value, View/Pick, Section, Card, Component, Parent, Changed Element, Name, and Property.

Field InformationField Information

Field Name	Description
Page Key	Page that the extension is applicable to. The value is a technical name identifying the page metadata.
Pages(s)	Page code(s) associated with the page. If the page is registered, then the value shows the associated page code(s); otherwise, there is no value.
Condition	Type of extension (global or conditional): Global Role Type Business Role Business Process Transaction Department
Condiition Value	For a global extension, the value is ALL. For a conditional extension, the value varies based on Condition: Role Type - Value indicates the Role Type that the extension is applicable to. Extension applies to all Business Roles (BUSROLE) with this Role Type. Business Role - Value indicates the Business Role Name and ID the extension is applicable to. Business Process - Value indicates the Business Process Name and ID that the extension is applicable to. Transaction - Value indicates the Transaction that the extension is applicable to. Department - Value indicates the Department to which the extension is applicable.
The following fields pinpoint where an extension is located: View/Pick, Section, Card, Component, Parent, Changed Element, Name, and Property.
View/Pick	What you see on a page is located within a hierarchical structure. The View/Pick, Section, Card, and Component fields identify where the Changed Element is located. The value consists of the functional title if available as well as the technical name in the page metadata.
Section
Card
Component
Parent	Sometimes the Changed Element is in a menu or wizard or is in a deeper hierarchy beyond View/Pick-Section-Card-Component, such as a PB field with an associated rule, condition, or parameter. The Parent field identifies any additional hierarchical structure leading to the Changed Element. If Parent = viewMenu.Additional Actions(viewActionGroup1), then the Changed Element is located inside viewMenu > Additional Actions (viewActionGroup1). The functional title, if available, is shown with the technical name in parentheses. If the functional title is not available, the technical name is shown without parenthesis. The Parent value shows one or more levels separated by a period (.) depending on the hierarchy to reach the Changed Element. Examples: Identifies the menu and sub-menu if the Changed Element is located within a menu. Identifies the wizard defining the tabs on a multi-tab page or steps of a wizard-style page. Identifies the action that a confirmation is associated with. For a PB page field associated with a rule, condition, or parameter, identifies the location of the rule, condition, or parameter propertiesextended.
Changed Element	Element being extended.
New?	Value is Yes if the Changed Element is added via extensions; otherwise, the value is No.
Name	Identifies the element with this name that is being extended. Example: Extend the Rank of the Department field - Changed Element = field, Name = DEPT_CD.
Property	Identifies the property that is being extended. Many properties are self-explanatory. The report can show properties that are more technical in nature, used in the background but not shown on DESIGNER, or only available via file-based extensions. This information is helpful when researching extension issues. Notes: active - This is the same as Displayed on DESIGNER. data - This is used for extensions that display text, such as view-level text or action confirmation message. hidden - This is usually used with a complex grid to control whether a field appears in the complex grid instead of a scalar or vice versa. visible - This is used when system logic determines when to display an element, usually based on data populated in other fields or parameter settings.
Delivered	Property value appears under Delivered, FBE Value, Designer Migrated Value, or Designer Pending Value based on the source of the property value: Notes: Delivered - Indicates the delivered baseline global property value. If a value refers to a business object or attribute title, Delivered includes any extension to the business object or attribute title in PalDb. If the named changed element is added via extension, or if the named change element exists in the delivered baseline but does not have this property defined, then there is no value under Delivered. FBE Value - Indicates the property value coming from file-based extensions if it is different from the delivered baseline property value. If the property value is blanked out by FBE, then <no value> is shown. Designer Migrated Value - Indicates the property value coming from migrated DESIGNER extensions. Designer Pending Value - Indicates the property value that is pending synchronization or under development on DESIGNER. Notes: If a property has a value under Delivered but <No Value> under FBE Value, this means that the FBE removed the property value. If a property has a value under Designer Migrated Value, but no value under Designer Pending Value and the User ID and Last Update Date values are populated, this means that particular extension has been removed or reverted using DESIGNER but has not migrated yet. The report represents certain property values using the translated functional value shown on DESIGNER rather than the actual technical value in the page metadata. These include: Boolean fields (report shows Yes or No) Priority (report shows Primary, Secondary, or Tertiary) Button template (report shows Solid filled or No fill)
FBE Value
Designer Migrated Value
Designer Pending Value
User ID	Indicates the user ID that last updated this page on DESIGNER and when the update occurred if pending extensions exist on DESIGNER.
Last Updated Date

Report Generation NotificationReport Generation Notification

The system sends you an alert after generating the report on the Admin, Financial, HRM, or Performance Budgeting application. There is no alert on the VSS application.

Report LimitationsReport Limitations

The report covers page extensions. Business object extensions are not reported.

The report does not report delivered file-based extensions to pageView. For example, if there is an extension to the posting line layout in the Financial application via file-based extensions to the fin.pageView.Common.AbstractTransactionPostingLine page, these extensions are not reported.

The report presents a snapshot of the extensions currently in place.

Titles defined using replaceable text can appear as is on the report. These can include:

Referencing a dynamically-configured title in Performance Budgeting
Examples: {COACONFIGURATION:field.fieldLabel}, {PROJECTCONFIGURATION.field.fieldLabel}
referencing a business object name {BO:table_name.title}
referencing a typedefinition {TYPE:global_attr.title}

On the report, extensions such as view-level text with formatted text values can appear as text with technical encoding rather than nicely formatted text.