CL_EXM_IM_PLM_AUDIT_IDENTIFIER - Example Implementation for BAdI Definition PLM_AUDIT_IDENT

RFUMSV00 - Advance Return for Tax on Sales/Purchases   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.

Functionality

In the standard system, the user must specify the identification for an audit component.

This example implementation is an example of the way that the system automatically sets the component identification for the higher-level component.

The example implementation contains the following functions:

• The system does not assign the 'root' identification. Example: You create an audit with lower-level questions. The system does not assign the identification for the audit.

• The identification for a lower-level component is allocated using the logic described below. Example:You create an audit with identification 4711. Two audit question lists are assigned to this audit. Twoaudit questions are assigned to each of these question lists. The question lists and questions contain the following identifications:

Question list 1: 4711-I-1

Questions for question list 1: 4711-I-1-1 and 4711-I-1-2

Question list 2: 4711-I-2

Questions for question list 2: 4711-I-2-1 and 4711-I-2-2

• The object is prefixed by a letter (for example, P for audit plan, A for audit, I for audit question list, C for preventive/corrective action).

• A maximum of 99 components can be assigned for each hierarchy level.

• The increment for a new assigned component is 1.

• If the system determines the identification, the identification is not determined again in this example implementation. Example: assignment of a question list to an audit.

• If the identification determined in the example implementation is longer than 24 characters, an identification is not suggested.

Relationships

Example

Notes

Further information

PERFORM Short Reference   Vendor Master (General Section)  
This documentation is copyright by SAP AG.


Length: 1965 Date: 20120526 Time: 122059     triton ( 83 ms )