The authorization check for accessing trip data corresponds with the general SAP authorization checks.
The term authorization object is of fundamental importance for the SAP authorization check. An authorization object is a list with a maximum of ten authorization fields. The authorization objects are listed in table TOBJ.
All of the authorization fields existing in any authorization object are defined with their attributes in table AUTHA in the repository.
An authorization for an authorization object is an assignment of values to the object’s fields.
Several authorizations for an object can be collected in one composite profile.
A user’s authorizations for the various authorization objects in the SAP system depend on the profiles that are assigned to the user in the user master record.
Authorization object Travel Expenses (P_TRAVL)
The authorization object for Travel Expenses is called
P_TRAVL
and consists of the following authorization fields:
Name of authorization field |
Meaning of field |
AUTHF |
HR-TRIP: Operation and
|
AUTHP |
HR-TRIP: Personnel number check |
AUTHS |
HR-TRIP:
|
BUKRS |
Company code |
KOSTL |
Cost center |
PERSA |
Personnel area |
PERSG |
Employee group |
PERSK |
Employee subgroup |
PTZUO |
Employee grouping for Travel Management |
VDSK1 |
Organizational key |
The values of the AUTHC, AUTHP and AUTHS fields are explained in more detail in the following section
Values of the individual authorization fields
.
The values for the authorization fields BUKRS, KOSTL, PERSA, PERSG, PERSK and VDSK1 originate from Infotype 0001 (
Organizational Assignment
), the value for the field PTZUO is filled from the specifications in Infotype 0017 (
Travel Privileges
).
For more information about authorizations, see the SAP Library under
.Values of the individual authorization fields:
The authorization field AUTHF
In the field AUTHF the values for the operation and the status of the relevant trip must be defined. The field has three positions. The first position defines the relevant operation, the second defines the status of the request and the third defines the settlement status of the relevant trip.
Characteristics for 1st position |
Result |
R |
Read trip data |
W |
Write trip data (Create, change, copy) |
D |
Delete trip data |
X |
Settle trip data |
S |
Analyze statistics database |
Operations |
Characteristics for 2nd position |
Result |
Blank |
New trip |
1 |
Request |
2 |
Request approved |
3 |
Trip data |
4 |
Trip approved |
5 |
Request on hold |
6 |
Trip on hold |
All statuses |
Characteristics for 3rd position |
Result |
Blank |
New trip |
0 |
Open |
1 |
To be settled |
2 |
Settled |
3 |
Canceled |
4 |
Posted (FI, payroll or DME) |
All statuses |
Examples of the values for authorization field AUTHF:
R41 |
Read an approved trip that is to be settled |
W |
Create a new trip |
W22 |
Change an approved request that is settled |
D1 |
Delete a request |
X41 |
Settle an approved trip that is to be settled |
S** |
Display statistics data for all trips |
The authorization field AUTHP
In the field AUTHP the value for the personnel number check must be defined.
Value |
Meaning |
O |
Own personnel number only |
E |
All personnel numbers except own |
All personnel numbers |
Examples of the values for the authorization field AUTHP:
The value O reproduces a decentralized concept. Users with this value can only carry out processing for their own personnel numbers.
The value E reproduces the department office concept of decentralized processing of trip data, but central for this department. Users with this value can process for all personnel numbers for the department except their own.
The valuereproduces a centralized concept. Users with this value can process trip data for all personnel numbers.
AUTHS: Status new when trip is saved
The field AUTHS is used to define the values for the status given when trip data is saved. The field has two positions. The first position defines the travel request status and the second defines the settlement status of the relevant trip.
Characteristics for 1st position |
Result |
1 |
Request |
2 |
Request approved |
3 |
Trip data |
4 |
Trip approved |
5 |
Request on hold |
6 |
Trip on hold |
All statuses |
Characteristics for 2nd position |
Result |
0 |
Open |
1 |
To be settled |
3 |
Canceled |
All statuses |
|
Examples of characteristics for authorization field AUTHS:
21 |
Request approved, to be settled |
3 |
Trip data |