Use this function to view and delete configuration history records. 

Prerequisites

SEEREFERTTO Refer to documentation Implementation

Screen management

The Configuration history function contains a header information section and one tab per feature of the function:

  • Header information. Use the header information to select a specific configuration run.
  • Characteristics. This tab identifies key data such as the product code and the Business Partner (BP) the configuration was initiated for.
  • Responses. This tab lists responses to questions presented when configuration was run.
  • Variables. This tab lists variables referenced by the configuration run.

Header

Use the header information to select a specific configuration run. You can select a specific run date, the configuration scenario code and a configuration document number. 

Tab Characteristics

This tab identifies key data such as the product code and the Business Partner (BP) the selected configuration was initiated for.

Tab Responses

This tab lists responses to questions presented when configuration was run.

Tab Variables

This tab lists variables referenced by the selected configuration run.

Reports

By default, the following reports are associated with this function :

  PRTSCR : Screen print

This can be changed using a different setup.

Action panel

Delete

Click the Delete action to delete this configuration history.

 

Comments

Deleting a configuration with history results in all data created during the selected configuration run being deleted.

Deletion is not possible if data for the selected configuration exists in other configuration records.

Error messages

In addition to the generic error messages, the following messages can appear during the entry :

Key present in the XXXXX file

This message is displayed if an attempt is made to delete data present in the work files.

Stock records exist for this product

This message is displayed if an attempt is made to delete a configured product present in the stock records.

Tables used

SEEREFERTTO Refer to documentation Implementation