Tim,

Yes that’s helped a lot.

But i need some approve about:

An issue I see is that only one instance of the Generic Text Message Service Provider integration is currently possible

It’s strange, cause we haven’t any restrictions on using the second GTMSP in our TEST system. Ok, it’s clear.

If you do the routing on CPI using some logic, you could create the corresponding interaction via an API call back into SAP Marketing Cloud.

It’s not clear, because standard response from text provider (or SCPI in our case) don’t support different interaction types.

https://help.sap.com/viewer/0f9408e4921e4ba3bb4a7a1f75f837a7/1902.500/en-US/929b31776e0040dfbd1a553913c88756.html

For example if i send PUSH, i get the messageId only

Response:  
Success Code 202  
Content-Type: application/json  
 
 
{
    "messageId": "33fds34534r4"
}

or

{
    "page": 2,
    "lastPage": false,
    "status": [
                    {
                         "messageId"   : "12343243243413",
                         "recipient"   : "+49123456789",
                         "statusCode"  : "10",
                         "statusText"  : "Number does not exist",
                         "type"        : "Permanent",
                         "timestamp"   : "20170913144813"
                    }
         ]
}

and this automatically creates interaction type “sms delivered” or “not” in SAP MKT.

So there will be only SMS send (delivered or not). Am i wrong? Or we can import interaction from sCPI and ignore this messages?

It's looks like solution!

Do this BAdI can change SMS_DELIVERED as interaction type? It's creating automatically, but not after import from any external systems.

Or do you suggest create 2 interaction after all the text messages (like sms_delivered and push_delivered also)?

Thank you very much, Tim! This really helped a lot!