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) 63.

This document consists of the following sections:

See ASR Installation Guide for instructions about installing ASR 63.

Data Conversions

The ASR63BD.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 63 on the following software versions:

  • Oracle Enterprise Linux Server 6.6 (or later) and 7.1 (or later)

  • Red Hat Enterprise Linux Server 6.6 (or later) and 7.1 (or later)

  • Oracle Solaris 11.2 or later

  • IBM AIX 7.1 Update 1

  • HP-UX Itanium 11.31 Update 7

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

  • Oracle WebLogic Server 12c (12.2.1.3 and 12.2.1.4)

  • Oracle Database 12cR2 (12.2.0.1), 18c (18.3.0.0.0), and 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

3654

Addition of allowable special characters.

3655

The valid entry changes have been implemented for the Clarification/Notification Type (CNT) field in the Clarification/Notification Request (C/NR) Details section 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

32750029

Issue

When executing the ImportExternalDLR ASR Web Service API with the UNIT field value length more than 6, the API returns the error “The value '1234567' of element 'UNIT' is not valid.”. As per the DLR-ISI guidelines, the length of the UNIT field is 25 characters.

Resolution

The code has been modified and now when executing the ImportExternalDLR Web Service API with UNIT field length up to 25 characters, the API will successfully create the external DLR.

After importing the External DLR via API, when the user views the external DLR in the application, the UNIT field value that exceeds 6 characters will be split into multiple lines in the Design Lines tab.

The length of the IC field has been increased from 20 to 25 characters to match the DLR-ISI guidelines. This change will be reflected in the External DLR API and also in the Connection Design and External DLR windows in the GUI.

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.