Ansicht
Dokumentation
PLMC_AUDIT_A_TYPE - Audit Type
SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up BAL_S_LOG - Application Log: Log header dataThis documentation is copyright by SAP AG.
In this IMG activity you define audit types.
You specify an audit usage (for example, quality audit) and an audit category (for example, system audit,
process audit, product audit) to provide a closer definition of the audit type. Note: The audit usages are defined in a Customizing table. The possible audit categories are predefined in the system.
These specifications only serve to differentiate between audit types. They have no controlling effect.
The following fields assigned to the audit type have a controlling effect:
- Status profile
You can supplement the predefined statuses (system statuses) that an audit runs through with user statuses.
- Input help for audit object
You can define one audit object for each audit type.
You define the audit object related to the audit type by determining a number with a short text for it. In addition, you can assign fields (data elements or objects) from the data dictionary to the audit object.
You can determine value sets in a table for fields that are used to define the audit components.
You can specify audit triggers for the audit type (Audit Trigger for Audit Type). If you do not specify a value, all audit triggers are available for the audit type.
You can specify rating profiles for the audit type (Rating Profiles for Audit Type). If you do not specify a value, all rating profiles are available for the audit type.
The tables of the upper two levels of the view cluster have delivery class G.
For your own entries, use the keys 1* to 4*, and A* to Z*.
Do not delete the entries delivered by SAP.
Reason: It is possible that the evaluation programs delivered by SAP access these keys.
ABAP Short Reference General Data in Customer Master
This documentation is copyright by SAP AG.
Length: 2479 Date: 20240523 Time: 200053 sap01-206 ( 37 ms )
