Description:
Symptoms:
--------------
If the program id say “TIBCO.Program.Id” is created and registered at SAP end and adapter is using this Id to publish the IDOC/RFC from the SAP end. It has been seen that “TIBCO.Program.Id” is trimmed to “TIBCO” while creating the  connection with SAP at SAP end.
This can be seen by executing the transaction code SMGW.

Cause:
--------
The cause of this issue is under investigation.  On analysis and testings performed on the issue, it has been found that issue could be specific to  the SAP libraries and not to the adapter. Adapter is able read the program Id  appropriately.


Impact:
--------
a functional loss as Idocs/RFC calls cannot be made to the adapter if the programID is not registered.

Workaround:
---------------
Please configure the adapter to work in multithreaded mode, set the adr3.maxconnection to a value greater that one. In this case one of the connections will appear as "TIBCO" but the other connections will be valid and appear as "TIBCO.Program.Id". If you want to use the adapter in single threaded mode set the adr3.maxconnection as 2, so that one connection will appear as "TIBCO.Program.Id" and will be valid.

Resolution:
-------------
Resolution for this issue is under investigation
Symptoms:

Cause:

If the ProgramId is defined as “TIBCO.Program.Id” while configuring outbound adapter, the ProgramId will visible as “TIBCO” only at SAP end.