Hi @serhat.gulsen1

In terms of length of RICs please see this existing post for detailed explanation What is the maximum length of a RIC - Forum | Refinitiv Developer Community

UPDATE on 01/02/21

Just to clarify -

• a RIC code is an official Reuters/Refinitiv Instrument code - as used by our data feeds and data sources/products.
• an item name/code, is the equivalent code/name used by clients for their internally published + consumed data.

Whitespace is not allowed in RICs on our realtime Refinitiv Real-Time (Elektron) Feed nor for item names on our ATS (Advanced Transformation Server) system, list of illegal characters:

The following are considered illegal characters anywhere within RICs / ATS item names.

· '(', ')', ';', '@', '~', '&'

· Underscore, Space, Single & double quotes

· Any non-printing characters.

· Characters above 7F

Also, for the DACS entitlement system, any type of white space etc will not work end-to-end e.g. RIC Codes/item names with white-spaces will not appear correctly in DACs reports and spaces are not allowed in Subject Based entitlements rules.

However, in terms of general Refinitiv Real-Time ADS, ADH and OMM APIs, they should allow whitespace within Item names.

Having said all that, unless there is an incredibly strong reason for using any of the above illegal characters in an item Name (i.e. for internal publication/consumption), it is strongly advised not to do so.

In terms of your 1st question, you were asking if you need to predefine RIC codes on the ADH etc before you can publish?

The answer is no, you can publish records using new (or existing) RIC codes as and when required.

There are two types of Provider applications - Interactive Provider or Non-Interactive Provider. You can a fuller description of each type in the API-ConceptsGuide.pdf that is packaged with most of our real-time SDKs (in the Docs folder). In a quick summary:

• Interactive Providers (IP) receive requests from the infrastructure and must respond interactively to these requests. Via these requests, the infrastructure may ask for information about the provided services and capabilities of the provider. The infrastructure also forwards consumer requests demanding for specific data items. For all these requests, the Interactive Provider must respond interactively by either providing the requested information or by rejecting the demand.
• Non-Interactive Providers (NIP) are not solicited by infrastructure requests but instead, they publish information (e.g. Available services, data items…) following their own timing. In this model, the infrastructure caches the published information and serves it to the demanding consumer applications.

If you only wish to publish records that a downstream consumer is interested in, then you would use an Interactive Provider. If you wish to publish records regardless of downstream interest, you would use a Non-interactive provider.

A tutorial for EMA Java NIProvider Tutorials | Refinitiv Developers

An article which focuses on IProvider Publish Custom Data via Refinitiv Real-Time Distribution System by EMA | Refinitiv Developers