/IWNGW/CM_BEP_COS -

The following messages are stored in message class /IWNGW/CM_BEP_COS: .
It is part of development package /IWNGW/BEP_COS_MESSAGES in software component OPU-GW-NOT. This development package consists of objects that can be grouped under "Notification Channel - BEP - Messages - Fully translated".
Message Nr
Message Text
000DB Error: Registration for provider '&1' failed.
001Class '&1' for provider '&2' not found
002Interface '&1' not implemented in class '&2' (provider '&3')
003Syntax error in class '&1'
004Action cancelled by user
005Transport error for provider '&1'
006DB Error: Registration for service '&1' not deleted
007Notification type '&2' version '&3' not resolved (provider '&1')
008Provider with id '&1' is not registered
009Provider with id '&1' is registered but not active
010Notif type '&2' vers. '&3' text not resolved for lang &4 (provider '&1')
011Client Productive, maintenance not allowed
012Transport error with provider '&1'
013Provider registration - Create failed with provider ID '&1'
014Provider registration - Update failed with provider ID '&1'
015Provider registration - Delete failed with provider ID '&1'
016Action canceled by user
017Provider '&1' already registered
018&1&2&3&4
019Error in provider
020Callback in the provider system started to resolve '&1' for RFC
021Processing of action on notification(s) started in the provider
022Notification provider '&1' found active.
023Notification provider '&1' activated successfully.
024'&1' fetched
025'&1' not fetched
026User does not have authorization to invoke the RFC
027Method '&1' not implemented in provider id '&2'
028Processing in provider completed
029Notification provider '&1' deactivated successfully.
030No authorization to read '&1'.
031No authorization to maintain/delete '&1'.
032Destination '&1' retrieved successfully.
033Destination '&1' maintained successfully.
034Destination '&1' deleted successfully.
Privacy Policy