Object-Dependent Documentation with Maintenance Transaction

Use

Documentation with a separate maintenance transaction is stored in an object-dependent documentation class and can be maintained using the corresponding maintenance transaction, or the HR Documentation Maintenance transaction (PDSY).

Example Example

The documentation for an object-dependent personnel calculation schema is stored in documentation class SCHE and maintained using the schema editor transaction (PE01).

End of the example.

The HR Documentation Maintenance transaction (PDSY) is integrated in the following maintenance transactions. You use the corresponding transaction to maintain the documentation.

Example of documentation classes	Description	Transaction	Name
SCHE	Personnel Calculation Schema	PE01	Schema editor
CYCL	Personnel calculation rule	PE02	Rule editor
549B	Feature	PE03	Features editor
FUNT, FUNC, OPET, OPEC	Payroll and Time Management functionsPayroll and Time Management operations	PE04	Editor for functions and operations
FORM	Forms in Payroll and Statements	PE51	Form editor

Note Note

You enter the documentation for your customer form ZF01 using the maintenance transaction for the HR Form Editor (PE51)

When using each maintenance transaction, note the relevant naming conventions for the object names.

End of the note.

Features

Documentation that is stored in object-dependent documentation classes and has a separate maintenance transaction can be

displayed
changed

You cannot use the HR Documentation Maintenance transaction (PDSY) to

create
delete
transport

In the SAP System, no object should exist without documentation and no documentation should exist if the accompanying object does not exist.

To create, delete, or transport documentation on an HR object, you must create, delete, or transport the accompanying object. To do this, use the appropriate maintenance transaction for the object.