Known Issues
Following is a list of known issues at the time of this integration release:
• The following fields in Oracle Utilities Work and Asset Cloud Service Assets Extract do not have data for the 23A release. These will be populated in the subsequent releases.
• Account Segment 1 to Account Segment 10
• GEN_PROC_ID
• MAINT_OBJ_CD
• PK_VALUE1
• The Fixed Assets Mass Addition process to add non project assets will add the assets in NEW queue of mass addition lines. Users will validate the records and move them to POST queue. After the records are in POST queue and ready to be posted, users should run the Post Mass Additions process.
• Due to the unavailability of Account Segment 1 to Account Segment 10 data (issue # 1), users will have to manually enter expense account in mass addition lines after the integration uploads the non-project assets data to NEW queue of mass addition lines. Users can then further validate and post the assets.
• Tax Jurisdiction field in Oracle Utilities Work and Asset Cloud Service Assets Extract will be delivered as a blank field. The customer is expected to implement customization to Oracle Utilities Work and Asset Cloud Service Assets Extract to populate the Tax Jurisdiction field for the asset as per their implementation. Along with this, all valid Tax Jurisdiction values from Oracle Utilities Work and Asset Cloud Service will have to be mapped to valid location segments of Oracle Fusion Cloud ERP as described in the Oracle Utilities Work and Asset Cloud Service Integration to Oracle Assets Configuration Guide included in this release.
• The Fusion ERP Project Number for project-based assets is currently derived from ERP Reference Number of parent Oracle Utilities Work and Asset Cloud Service Project of project assigned to the Oracle Utilities Work and Asset Cloud Service Activity. The Fusion ERP Task Number is derived from ERP Reference Number of the Oracle Utilities Work and Asset Cloud Service project assigned to Oracle Utilities Work and Asset Cloud Service activity. This logic will be further refined in the upcoming releases.
• Make sure the Project ID created in Oracle Fusion Cloud ERP is not more than 14 characters as the Oracle Utilities Work and Asset Cloud Service Project BO is currently accepting 14 characters for the ERP Reference Number field.
• Make sure the Asset Badge Number entered in Oracle Utilities Work and Asset Cloud Service is not more than 15 characters as the ERP Tag Number field accepts a maximum of 15 characters.
• Non-tracked asset retirement from Oracle Utilities Work and Asset Cloud Service that should be sent as an adjustment to Oracle Fusion Cloud ERP will be available in upcoming release.