This document describes the enhancements that are introduced and the Access Service Ordering Guidelines (ASOG) issues that have been implemented in Oracle Communications MetaSolv Solution Access Service Request (ASR) 68.

This document consists of the following sections:

See ASR Installation Guide for instructions about installing ASR 68.

Data Conversions

The ASR68BD.sql file is included in this release. The installer provides all upgrades to MetaSolv Solution executable files and stored procedure files (Procs directory).

Software Support

MetaSolv Solution 6.3.1 supports ASR 68 on the following software versions:

  • Oracle Enterprise Linux Server 7.1 (or later), 8 (or later), and 9 (or later)

  • Red Hat Enterprise Linux Server 7.1 (or later), 8 (or later), and 9 (or later)

  • Oracle Solaris 11.4

  • IBM AIX 7.1 Update 1

  • HP-UX Itanium 11.31 Update 7

  • Windows Server 2012 R2, Windows Server 2016, Windows Server 2019, and Windows Server 2022

  • Oracle WebLogic Server 12.2.1.4

  • Oracle Database 19c (19.3.0.0.0)

ASR CORBA APIs Desupported

CORBA APIs are no longer supported from ASR 60. Oracle recommends that you use ASR Web Services to integrate ASR with other Oracle products or with external applications. See ASR Web Services Developer's Guide for more information about the ASR Web Services.

ASOG Issues Implemented

The following table describes the Access Service Ordering Guidelines (ASOG) issues that have been implemented in this release.

Table 1-1 ASOG Issues Implemented

Issue Number Description

3663

The existing EVC QTY field is deleted from EVC form and is added in the Admin2 form.

The validation changes are implemented in the UI and the API for the EVC QTY field in the Admin form.

Fixes in This Release

The following table lists the customer-reported bugs that have been fixed in this release.

Table 1-2 Fixes in This Release

Bug Number Description

35840019

Issue

When an order was sent from the upstream system with EVCNUM value as 1 or 2 instead of 0001 and 0002, the MSS application does not display information in EVC UNI MAPPING Details page.

Resolution

The user can now see the EVC UNI MAPPING Details in the ASR order when the EVCNUM value is sent with or without leading zeros in API.

34350760

Issue

When clicking Service Request Detail in the Connection Design window, the users received an invalid service request type error for the ASR orders with the request type as D- DIS.

Resolution

The user can now open Service Request Detail from the Connection Design window for the ASR orders with the request type as D- DIS.

35823427

Issue

When previewing the ASR order, the data for some of the fields such as BDW in the EVC UNI Mapping Detail section are displayed incorrectly.

Resolution

The user can now preview ASR orders and the data in the EVC UNI Mapping Detail section are displayed correctly for all the fields.

36007871

Issue

When installing ASR67, the logger entry cmm.Integration.ASRversionAPI is not added to the loggingconfig.xml automatically.

Resolution

When installing ASR version greater than 67, the logger entry cmm.Integration.ASRversionAPI is added to the loggingconfig.xml automatically.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.