How to handle SBI IDs when there is no SBI

There is an issue in situations where it is desired to carry out a form of end to end, or integrated, testing which does not involve the execution of an SBI. The issue is that outside the context of am SBI execution there is no meaning to the SBI ID value that is currently required in the resource allocation JSON documents.

In the absence of an SBI these tests are often carried out by loading the resource allocation JSON from a file. In gthat file the SBI ID value is fixed. As a consequence repeated tests using the same (or similar) file will result in the use of a duplicate SBI ID, causing a "duplicate SBI ID error" to be raised. SKB-37 is a good example of the problem.

This ADR should identify a good approach to resolving this problem.

Why Now? Testing of the above type is being carried out, both in the context of CI and use of the PSI.

Scope: Integrated testing involving OMC and SDP

Quality: Testability.