Ansicht
Dokumentation

OHIX0017 - Set up change document

ABAP Short Reference   CPI1466 during Backup  
This documentation is copyright by SAP AG.

In the step Infotypes to be Logged you must enter the infotypes that are to automatically logged when a change is made (Deletion, change, insertion).

You have the following options:

• The changes made to an infotype are logged per field. You are free to choose which fields are to be logged.

• You can group fields together in Field groups that are always logged, i.e. even if you only make a change to one of the fields in the group.

• You can define dependencies between the field groups, i.e. you can specify a supplementary field group for each field group, that is always logged at the same time as the field group. (If, however, you only change one field in the supplementary field group, this change will not be logged).

• There are two document types:
  
  

• Long-term document

Long-term documents are used for revision purposes. Changes made to the infotype are stored in the database or can be archived. Long texts are stored until they are deleted. The archiving object is called PA_LDOC.

• Short-term document

Short-terms documents are stored in the database. Short-term documents are evaluated differently to long-term documents - short-term documents are evaluated according to date and time.

• Determine the infotypes to be logged

A change made to an infotype defined as "to be logged" causes an infotype log to be created. Infotypes that have not been defined as "to be logged", are not logged. Transaction class A is used for documents in HR Master Data Management, transaction class B is used for the documents in Recruitment.

• Determine field groups

Within any one infotype, you must specify all the fields that are to be logged. By using the field list you can display all the fields that belong to an infotype and choose them directly. In adddition to this, you can group the fields into different field groups within any one infotype. When the infotype log is created, all the fields belonging to a field group will be treated as one entity and will, therefore, be logged together.

• Determine the characteristics of the field group

In this step, you tell the system which field groups are to be logged. In addition to this, supplementary field groups (SFG) can be defined for every field group. Supplementary field groups are always logged if a field within this "triggering" field group (TFG) is changed. Here, you must also determine whether the document is to be recorded as a long-term document (L) or a short-term document (S).

The standard SAP system does not contain any documents, i.e. the control tables that are necessary to carry out this step are empty.

Consider carefully which infotpyes and, if necessary, which infotype fields you want to create an infotype log for, as each document causes an entry to be made to the database.

1. Determine the infotypes to be logged.
2. Define the field groups.
3. Determine the characteristics of the field groups and, if necessary, define the supplementary field groups.

Additional notes

You can display any changes made to infotype records with report Logged Changes in Infotype Data (RPUAUD00).

If you are evaluating documents in customer-specific reports, you can use the following function modules provided by SAP:
List of All Logged Infotype Records (HR_INFOTYPE_LOG_GET_LIST)
Read Logged Infotype Record (HR_INFOTYPE_LOG_GET_DETAIL).

The function modules return the logged fields to an infotype structure.

RFUMSV00 - Advance Return for Tax on Sales/Purchases   CPI1466 during Backup  
This documentation is copyright by SAP AG.

Length: 4506 Date: 20240523 Time: 152909     sap01-206 ( 81 ms )