CTS Status Switch for SAP Enterprise Portal

[ucabazz]

Dear Experts,

In our landscape we use Solman 7.2 SPS14 CHARM functionality to manage transports for SAP Enterprise Portal 750.

We want to restrict users to create transport requests using ChaRM only.

For this we closed status switches in CHARM Administration Cockpit for EP.

However there is still possibility to create transport requests for Portal directly in Transport Organizer WEB UI of communication system (Solman) in respective CTS project.

Here it is possible to create TR for CTS project which status switches are closed.

How do we restrict users to create transport requests for EP using ChaRM only?

--Abay

[Thomas_Winkler]

Hallo Abay,

CTS+ offers two possible scenarios:

1. Loose Coupling: (This is what you're using now)

• No direct integration of CTS+ mechanisms into application
• Additional tool needed to create transport requests, attach files and release transport orders
• Manual attachment of files to transport requests via file upload
• Import only on file system level, manual actions for activation

2. Close Coupling

• CTS+ mechanisms are available via additional buttons, links, and input-fields within the existing export UIs
• Automatic attachment of files to transport requests directly within the application (for example, EP, PI, and so on)
• Get default transport requests
• Automatic creation of transport requests possible
• Automatic release of transport request possible
• Connection from application server to CTS server
• Automatic deployment and activation

Important Parameter for your scenario:

NON_ABAP_WBO_INBOX

• Path to the directory where Transport Organizer searches for files.
• This parameter enables you to choose between a close or loose coupling of your SAP applications and CTS:

Close coupling.

• You need this parameter setting when you attach files to a transport request from a server share/mount.
• The default setting uses file streaming (see parameter WBO_FILE_TRANSFER).
• In the Loose coupling scenario, you need this parameter setting when you attach files to a transport request from a server and not from a desktop (client).

WBO_GET_REQ_STRATEGY

Tagged: Transport Organizer Web UI (or ChaRM) has to be used to create a request for a user and to mark them with a tag. If there is no tagged request found for a given user, the application reacts with an error-

Smart: If there is no tagged request available for a user; the transport backend creates a valid request. The export wizards in the applications are never interrupted, because there is always a valid request

WBO_REL_REQ_STRATEGY

Manual: Transport Requests can only be released using the Transport Organizer Web UI or ChaRM-

Automatic: Transport Requests are automatically released from the Transport API after the objects are attached to the request

https://wiki.scn.sap.com/wiki/pages/viewpage.action?pageId=447468169

https://wiki.scn.sap.com/wiki/pages/viewpage.action?pageId=343933137

Good luck - Thomas

[ucabazz]

Hello tommy_sta,

Thank you for the useful information.

However, it is not clear why the CTS status switches do not work and even with closed switches there is still possibility to create TRs outside of CHARM (in Transport Organizer UI).

Do you mean we need to move to Close Coupling scenario?

Currently we have these parameters for EP in transport tool:

--Abay.

[Thomas_Winkler]

Hallo Abay,

yes - this is the background of Close coupling. With this parameter you force the developers to follow the charm process, because the transport only works when the status switches agree.

Cheers Thomas

[ucabazz]

tommy_sta,

Thank you for reply, I will check and revert back with feedback.

--Abay

[ucabazz]

Hello tommy_sta,

We tried using these parameters, but it did not help. As per note #1413047 - Missing function in CTS+ in comparison with CTS, this is not possible. Excerpt from the note:

"Project status switches for export transactions: CTS+ does not provide the option of maintaining export-side project status switches for pure non-ABAP systems (the system ID of the non-ABAP system is different than the system ID of the communication system). Therefore, these settings are ignored when related transport requests are created or released."

--Abay

[JSULLIVAN]

Hello Abay,

It is also a good idea to set a couple attributes in SE03 -> Display/Change Request Attributes if they apply:

SAP_CTS_PROJECT

SAP_TMWFLOW

[ucabazz]

Hello john_sullivan_68,

Thank you for suggestion.

Will check it.

--Abay