ProvisioningSequenceNumber incorrectly Modified in Multi Service Orders

(Doc ID 783652.1)

Last updated on FEBRUARY 20, 2009

Applies to:

Oracle Communications ASAP - Version: 5.2.4 to 5.2.4
This problem can occur on any platform.


-- Problem Statement:
On ASAP 5.2.4 Efix 2 (Patch ID 7714278):

The application code was changed to provide a custom translation. This XSLT translation
puts the value of upstream "serviceSequenceNumber" to "provisioningSequenceNumber" before submission
for SRT service bundle processing. The value is then expected to be carried forward for order
processing. During orderCompleteEvent response of ASAP, parameter "serviceSequenceNumber" is
generated with the value provided in "provisioningSequenceNumber". The value is then returned to the

The above logic works well if one service is present in an order. However in the case where multiple
services are within the same order, the behavior is unexpected.

Every work order with multiple services is affected.

Expected behavior :
The value of upstream “serviceSequenceNumber” is passed to "provisioningSequenceNumber". This must
happen for each service within the order. The value is then passed to JSRP with no change. During
ASAP Event of orderCompletion, the same values must be returned. The values must match with the
value of “serviceSequenceNumber” as put in "provisioningSequenceNumber" initially.

Actual behavior :
The custom translation is working correctly to put right value of “serviceSequenceNumber” to
"provisioningSequenceNumber". This happens for each service. Order is passed to SRT and passes
through the normal Service bundle processing. Just before the order gets submitted to JSRP message
queue, the value of "provisioningSequenceNumber" is found to be changed unexpectedly. For various
scenarios these are the modified values of "provisioningSequenceNumber" .

Test Order 1

Service 1 : provisioningSequenceNumber = 8
Service 2 : provisioningSequenceNumber = 9
After Service bundle processing
Service 1 : provisioningSequenceNumber = 8
Service 2 : provisioningSequenceNumber = 9

Test Order 2
Service 1 : provisioningSequenceNumber = 25
Service 2 : provisioningSequenceNumber = 19
After Service bundle processing
Service 1 : provisioningSequenceNumber = 19
Service 2 : provisioningSequenceNumber = 20

-- Steps To Reproduce:
The issue can be reproduced at will with the following steps:
1. An order is submitted to SRT with multiple services. Order should have multiple services with
different service bundle names so as not to make it a bulk order. Parameter value
"provisioningSequenceNumber" must be set for each service.

2. View the output post Service bundle processing and just before order is submitted to JSRP. The
values of provisioningSequenceNumber is found to be changed.


Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms