My Oracle Support Banner

Invalid SALI Validation Error For Disconnect Orders - "No SALI data found on order when QSA field is populated" (Doc ID 1447555.1)

Last updated on APRIL 09, 2012

Applies to:

Oracle Communications MetaSolv Solution Module - ASR - Version: 44.0.0 and later   [Release: 44.0 and later ]
Information in this document applies to any platform.


Getting validation errors from MetaSolv Solution Software MSS) ASR code for disconnect orders where SALI address is not populated.

Executing the import TRANSPORT ASR API with ACT=D, QSA=1 and SALI form EUNAME="XXX" is successful, but it throws an error "No SALI data found on order when QSA field is populated" when the imported ASR order is opened through GUI.

Per ASOG rules:
By strictest interpretation of the ASOG the address fields on the SALI Form are not required for a disconnect order.

Using the Transport Form as an example, the SECLOC field itself is not required for a disconnect but if the customer elects to populate it with an “E” (end user designation in lieu of an established CLLI code) the the SALI Form is required but only for the purposes of specifying the end user’s name in the EUNAME field. The SASN field (Street Name) which is the trigger point for all the other address-related fields is optional for disconnects. Therefore, the only “required” field on the SALI would be for the specification of the end user’s name….


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.