What exactly does “Program Not Registered Mean”?

Many times we come accross RFC connections of type TCP/IP connection which are not working or suddenly stop working with most infamous error “Program no registered”

Logon Connection Error
Error Details Error when opening an RFC connection
Error Details ERROR: program <program id> not registered
Error Details LOCATION: SAP-Gateway on host xxxxx / sapgwxx
Error Details DETAIL: TP xxxxx not registered
Error Details COMPONENT: SAP-Gateway

External program should always regsiter on the Gateway of the SAP application to be able to establish connectivity like SLD registers itself using RFC’s SLD_UC or SLD_NUC.

For example a ESB program like WSO2 should register on the gateway using connectors (.jar files normally). While registering, it will use details of the application/server like, gateway host, gateway service, Program ID, user name, password etc..

Once this program is registered you should be able to see this under the logged on clients in transaction SMGW:

You should see the program you registered under TP name. Once this is done, you are ready to create the required TCP/IP RFC using the same program ID under TP name.

smgw

smgw2

If you are not able to see this TP Name registered, check the connectivity from you third party server to SAP gateways host by doing a telnet to gateway port.

If this works, it could be your gateway ACL parameters are blocking the connection.

Check you profile parameters for gw/acl_mode, gw/sec_info and gw/reg_info etc and adjust them accordingly,

2104408 – Checklist for “program <program ID> not registered” errors

 

Advertisements

Usage and Procedure logging (UPL/SCMON) on Solution Manager 7.2

Usage and Procedure logging (UPL) also know as SCMON enables you to monitor you custom code usage and make informed decisions on the same.

You can either enable it either from the managed system directly or from SAP Solution Manager.

On the managed system the data is by default available only for 14 days after which it is overwritten.

Of course this is not enough data when you are looking at long term decision making.

In such case Solution Manager can be used to store the data in BW objects for longer duration.

Below are some points for configuring the UPL with Solution Manager 7.2.

System Preparation, Infrastructure Preparation and Basic Configuration has to be finished successfully.

Among these most import steps are:

1. Solution manager central note is applied in System Preparation

2. Infrastructure Preparation (Set up SAP BW)

3. Basic Configuration (BW Content activation (UPL) under configure basic functions)

It is very important that this step is complete.

4. Managed System Configuration (Maintain RFC’s)

All the required RFC’s (Especially read RFC to the Managed system of required client ) have to be maintained.

5. Custom Code management.

cc1

Steps 1, 2 and 3 are automatic activities and required to be completed successfully.

Under step 3 be careful to select the granularity of the data required while scheduling the house keeping jobs.

Most important steps are 4, 5 and 6 where you select the scope (SID, Client of Managed system) and enable the extractors and jobs to collect data.

If your Managed system setup is completed successfully, the system and client should be available here.

This completes all the actions required to activate UPL on Managed system and collect data on Solution Manager.

Now to verify that UPL is activated successfully, flowing can be done.

On the Managed system:

Execute Program /SDF/SHOW_UPL. This should show you data and available from date (Which is by default 14 days)

If available from data is empty, its time to recheck your configuration.


On Solution Manager:

Check if the extractor framework is is running fine.

SOLMAN_WORKCENTER

 

Check data in UPL Day DSO (0SM_UPLDD). You should find more than 14 days of data here for your managed system.

Note that from Solution Manager 7.2 SCMON extractor will not be filling the UPL day cube (0SM_UPL).

Important SAP Notes:

2546841 – Custom Code: Usage Logging – SCMON extractor failing with error “Environment key is missing”

2662295 – Benefits of using SCMON in Solution Manager 7.2

2569292 – UPL Data in Usage Cockpit instead of SCMON

2541488 – Poor performance of SCMON extractor ( AGS_CC_SCMON_EXTRACTOR ) in SAP Solution Manager 7.2

2434255 – How To: Stop & Remove UPL/SCMON Data from Solution Manager

2682315 – SCMON collection job ” ABAP Call Monitor: Collect ” is been activated via Solution Manager with no active SCMON data collection configured

2570468 – How to check the SCMON settings for a root flag

2558437 – Data access error: To many Coverage Analyzer job are scheduled on the system * – Error in SCMON extractor

2623917 – Custom Code Management Migration Task 4.2 Fails