Otro Estado

3
7/30/2019 Otro Estado http://slidepdf.com/reader/full/otro-estado 1/3 Definir esquema de status Utilización This section explains how to adapt general SAP status management to your requirements. General information on status management Management of the different statuses in the SAP System is divided up according to system status and user status System status The SAP System contains in a central table a basic store of statuses that are valid for all applications and can be used by all applications. These statuses are maintained by SAP and cannot be changed. They are referred to as system statuses. Business transactions The SAP System contains in a central table a basic store of business transactions that are valid for all applications and can be used by all applications. These business transactions are maintained by SAP and cannot be changed. Business transaction - system status A further central table, also predefined by SAP, defines a system status for every business transaction and indicates whether or not the corresponding system status is deleted or set during the business transaction. Objects - business transactions Another table defines the business transactions that are allowed for each SAP object (order, equipment and so on). This allocation is also predefined by SAP. Result The allocations listed above defines Which system statuses are the maximum possible for an object Which system statuses can be set for the different individual business transactions Status profile You can define your own statusprofiles in the IMG activity DefineStatusProfiles . Every status profile must be allocated to at least one object. Every status profile contains one or more statuses allowed.

Transcript of Otro Estado

Page 1: Otro Estado

7/30/2019 Otro Estado

http://slidepdf.com/reader/full/otro-estado 1/3

Definir esquema de status

Utilización

This section explains how to adapt general SAP status management to your requirements.

General information on status management

Management of the different statuses in the SAP System is divided up according to

system status and

user status

System status

The SAP System contains in a central table a basic store of statuses that are valid for all applications

and can be used by all applications.

These statuses are maintained by SAP and cannot be changed. They are referred to as systemstatuses.

Business transactions

The SAP System contains in a central table a basic store of business transactions that are valid for all applications and can be used by all applications.

These business transactions are maintained by SAP and cannot be changed.

Business transaction - system status

A further central table, also predefined by SAP, defines a system status for every businesstransaction and indicates whether or not the corresponding system status is deleted or set during thebusiness transaction.

Objects - business transactions

Another table defines the business transactions that are allowed for each SAP object (order,equipment and so on). This allocation is also predefined by SAP.

Result

The allocations listed above defines

Which system statuses are the maximum possible for an object

Which system statuses can be set for the different individual business transactions

Status profile

You can define your own statusprofiles in the IMG activity Def i ne S t a tu s P ro f i l e s . Every statusprofile must be allocated to at least one object.

Every status profile contains one or more statuses allowed.

Page 2: Otro Estado

7/30/2019 Otro Estado

http://slidepdf.com/reader/full/otro-estado 2/3

For each of these statuses, you can determine the system response within the business transactionspredefined by SAP.

In the status profile you can

define your own statuses (user statuses) and document their function in a respective longtext

determine the statusnumbers for user statuses which predefine the possible sequence for processing user statuses

define an initial status which is activated automatically when creating the object

determine which user status is automatically activated when carrying out a businesstransaction

define which operations are allowed or prohibited if a certain status is active

Status number

You can define a status number for every user status.

The status number determines the sequence in which the user statuses can be activated.

If you do not assign a status number to a user status, the user status can always be set. However,there can only be one user status with a status number active at any one time.

If you assign a status number to a user status, you must also specify a lowest and a highest statusnumber for the status. These limit the status number interval from which the following user status canbe chosen.

Example of status number

Example of equipment status

SAP supplies the following business transactions for equipment:

Set deletion indicator (From release 3.0B)

Cancel deletion indicator (From release 3.0B)

Install equipment

Dismantle equipment

When maintaining the status profile, you can determine for every status within the profile whether equipment of this status can be installed or dismantled and whether a deletion indicator can be set or not.

You can also determine in status maintenance whether, for example, the deletion indicator is setautomatically and whether the system should respond with a warning or an error message when adeletion indicator is set.

Maintenance objects for which status profiles can be maintained:

o Equipment

Page 3: Otro Estado

7/30/2019 Otro Estado

http://slidepdf.com/reader/full/otro-estado 3/3

o Functional locations

o Maintenance notifications

o Service notifications

o Maintenance orders

o Service orders

Notas

In the menu for the configuration of equipment, you can specify a status profile as a default value for each equipment category.

For maintenance notifications, only a single status profile is allowed.

Actions

Define the user statuses for the individual maintenance objects.

Crear clave de autorización para status de usuario

In this step you define authorization keys which you can use to set up authorization checks when youmanually set or delete a user status. When the system sets a user status as a reaction to businesstransaction, it does not perform an authorization check.

When you set or delete a user status , the system checks whether the user is authorized for thisaction. In addition to the status profile and the object type, the system also checks the authorizationkey assigned to the user status in question.

Example

You want to define that certain user statuses can be changed only by a specified employee group .

To do this, create an authorization key and assign it to the relevant user statuses.

In the general authorization maintenance you can then assign authorizations for this key via theauthorization object B_USERSTAT.

Actividades

1. Check whether you want to define authorizations for your user statuses.

2. If necessary, create authorization keys as follows:

a) Choose "New entries".

b) Enter a key and an explanatory text in the appropriate fields and choose "Save".

You have now created the authorization key.

3. Assign the authorization key to one or more user statuses in your status profile.

4. Define corresponding authorizations and include them in the relevant authorization

profiles.