Release Notes

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

This document consists of the following sections:

See ASR Installation Guide for instructions about installing ASR 62.

Data Conversions

The ASR62BD.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 62 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.

Issue Number Description

3647

The UI and API usage validation changes have been implemented for the following fields in the ADMIN form:
  • Design Facsimile Number (DSG FAX NO)
  • Design Electronic Mail Address (DSG EMAIL)
  • Design Routing Code (DRC)
  • Facility Design Routing Code (FDRC)

3650

Added the following new field in the ADMIN form:
  • Implementation Contact Electronic Mail Address (IMPCON EMAIL)

3651

Added the following new field in the ADMIN form and MEC form:
  • Variable Term Agreement Indicator (VTAI)

Implemented UI and API usage validation changes for the Variable Term Agreement Indicator (VTAI) field in the ADMIN and MEC form.

3652

The definition note for the existing Site Contact (SITE CON) field has been modified in the ADMIN form.

Fixes in This Release

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

Bug Number Description

32111743

Issue

When users execute the ImportPTA Web Service API with one circuit mentioned in the PTA Circuit detail section but without the REFNUM value, the API responds with the below error:

ORA-01400: cannot insert NULL into ("ASAP"."PTA_CIRCUIT"."REFERENCE_NUMBER")

Resolution

Code has been modified and now when users execute the importPTA Web Service API with one circuit mentioned in the PTA Circuit detail section but without the REFNUM value, the application will import the order successfully.

32111396

Issue

When users execute the ImportPTA Web Service API for an EVC order, with the PTA Virtual Circuit detail section, but both VCID and VCNUM not populated, the API responds with the below error:

Form: PTAVC_DETAIL | VC Number: null | Field: VCNUM | Value |:: is required

Resolution

Code has been modified and now when users execute the importPTA Web Service API for an EVC order, with the PTA Virtual Circuit detail section, but both VCID and VCNUM not populated, the application will import the order successfully.

32025252

Issue

When importing an ASR order via API, the API errors out if the value provided for the CLLI code fields does not exist in the MSS database.

Resolution

This resolution addresses only the ACTL (Admin), EVCSP (EVC) and ESP (SES & CN) fields.

A new preference “Template CLLI code for API when passed in CLLI does not exist” has been added under Service Request --> Access Service Request. This preference has two text fields, viz. 8 char CLLI code and 11 char CLLI code which will only accept a CLLI code that exist in the MSS database.

When a CLLI value that does not exist in the MSS database is passed in the above mentioned fields, the application will create a new Network Location using the CLLI code given in the preference as reference.

If the provided input is an 8 char CLLI for EVCSP and ESP fields, the application will create a new 8 char CLLI Network Location using the 8 char Template CLLI as reference.

If the provided input is an 11 char CLLI, then the application creates a new CLLI based on the 11 char Template CLLI as reference.
  • If the first 8 char CLLI does not exist in the database, an 8 char building is also created using the same data as the 11 char CLLI that has been created.

  • If the first 8 char CLLI exists in the database, the address from the existing 8 char CLLI will be used, for the new CLLI instead of the address used by the 11 char Template CLLI.

For both 8 and 11 char CLLIs that is created by the application, the CLLI code and location name fields will be same as the input CLLI. The User Data and Custom Attribute sections of the Template CLLI will not be copied over.

Note: This ASR patch would need MSS 6.3.1.74 b23 and above for the preference to be available.

32255861

Issue

When users attempt to supplement cancel a DD completed ASR through the API, the application responds with a “Matching order not found for PON and IC (CCNA)” message.

Resolution

Code has been modified and now when users attempt to supplement cancel a DD completed ASR order through the API, application will respond with the following error message:

This Service Request has a completed Due Date Task or has been Cancelled and will not accept a Supplement Order.

32255859

Issue

When users supplement an ASR order through the API, and if there are any changes on the SALI form fields, the changes are not captured in the Audit history.

Resolution

Code has been modified and now when supplementing an ASR order and if there are any changes to the SALI form fields, the application will capture the changes in the Audit History.

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.