The BASIS of SAP

Operating System TP / TMS / CTS unconditional modes

The TMS / CTS functions are  a front end to the TP commands at the operating system level. If you use the operating system commands, you face the challenge of replicating the options available via the SAP GUI front end.  These options are controlled by using the Unconditional mode. An example of how to use these is shown below. 

host:prdadm 2> tp import L6BK162625 PA1  U client=100
This is tp version 340.16.38 (release 640)
This is R3trans version 6.13 (release 640 – 07.01.08 – 14:25:00).
2EETW000 T5QTM table class is ‘C’. Entries are only imported to client ’000′.
2EETW000 T5QTX table class is ‘C’. Entries are only imported to client ’000′.
R3trans finished (0008).
tp finished with return code: 8
meaning:
  A tool used by tp produced errors
host:prdadm 3> tp addtobuffer  L6BK162625 PA1
This is tp version 340.16.38 (release 640)
Addtobuffer successful for L6BK162625
tp finished with return code: 0
meaning:
  Everything OK
host:prdadm 4> tp import L6BK162625 PA1  U128 client=100
This is tp version 340.16.38 (release 640)
This is R3trans version 6.13 (release 640 – 07.01.08 – 14:25:00).
R3trans finished (0000).
tp finished with return code: 0
meaning:
  Everything OK
host:prdadm 5>

The U stands for unconditional force, similar to the options that you can select when importing via the SAP GUI.

0: Overtaker – change requests can be imported without deleting it from the buffer. Usually, this is followed sooner or later by an import using unconditional mode 1 to import another transport in the correct sequence.

1: Import the transport again.

2: Allow transport to overwrite SAP or System originals.

3: Allow transport to overwrite system-dependant objects.

5: Allow transport to contain source systems other than the integration system (usually used only when importing into Development or Consolidation system).

6: Allow transport to overwrite objects in unconfirmed repairs.

8: Allow transport to ignore limitations caused by the table classification (see the example above).

9: Allow transport to ignore that the system is locked for this kind of transport.

Remember that the location to run the tp addtobuffer and / or tp import from is operating system dependent:
(Windows): \\$(SAPTRANSHOST)\sapmnt\trans\bin
(UNIX): /usr/sap/trans/bin

SAP HR/PY Structural Authorisations

I had added a new developer to the customer’s HR/PY landscape, but they couldn’t see any of the Employee Data in the Development or QA system. According to SU01, the roles and profiles were identical to a developer who could see the data.

After hunting around my disks (because it has happened to me before !!), I found a note about Table T77UA, which has prompted this reminder to both myself and any one else who has to work with HR/PY Developers.

HR Security

HR Security comprises the General Authorisation Profiles as managed by Role Maintenance (transaction PFCG), plus Structural Profiles.  To assign Structural Profiles, you use table T77UA (User Authorizations = Assignment of Profile to User).  The Structural Authorisation’s themselves are specified in the T77PR table (Definition of Authorization Profiles).  You protect structures (or substructures) of the Organisational Chart by making relevant entries in this table.

1. When you use both Structural and General Authorisations , a user’s Overall Profile is determined from the intersection of the two.
2. The structural profile determines which object in the hierarchical structure the user has
   access to;
3. The general profile determines which object data (infotype, subtype) and which type of
   authorization (Read, Write, …) the user has for these objects.
4. The access mode for authorization objects in HR Master Data is determined in the AUTHC field (Authorization Level).

Steps to do Structural Authorisation:

1. Use transaction OOAC (updates table T77S0) to Activate the Structural Authorisation switch
2. Use transaction  OOSP (updates table T77PR) to Create Structural Authorisation profiles. You protect (sub)structures by making relevant entries in this table.
3. Assign regular Role Authorisation via PFCG.
4. Assign Structural Authorisation profile to User Id. Apparently, some releases have a report RHRPROFL0 that you can use to assign the object id. However, I use transaction SM30 to update Table – T77UA (User Authorizations = Assignment of Profile to User).
5. Organizational Plans are created using PPOCE

SAP Enterprise Portal 7 – Modify Default Ports

An SAP portal installation, by default, selects a port for http and https access based on your system number. For example, if your system number is ##, then the default port for portal access would be

* 5##00 for http access
* 5##01 for https access ( aka SSL )

Many Project teams wish to shorten this long url (http://yourserver.yourdomain.com:5##00\irj\portal). Fortunately, there is an easy way to modify the portal http and https ports and keep it to 80 and 81 ( or anything you wish).

Follow the below given steps to achieve this.
1. Start the j2ee visual administrator tool
2. navigate to cluster -> dispatcher -> HTTP Provider
3. Choose Ports
4. Change the port number to 80 for http and 81 for https
5. Thats it – You’re done!!!!

One extra step that’s required if you’re also running IIS (for example, if you’re using an ITS to communicate with an older R3 system or running TREX), you need to make sure that your J2EE ports do not conflict with any of the IIS ports (including the default web server). The best way of doing that is to ensure that the IIS default web server is pointing at different ports AND is stopped.

SAP Enterprise Portal 5 – Modify Logon Page

The logon page is FormLogon.asp found in the SAPPortal  directory of the Default Web Site under IIS 

For those familiar with later releases of Enterprise Portal, you need to remember that when EP5 was released, the Web Application Server release of SAP had yet to be released.  This meant that the portal server had to provide its own web server.