Ansicht
Dokumentation

RSPOXPRA - Obsolete

General Material Data   General Data in Customer Master  
This documentation is copyright by SAP AG.

Description

With R/3 Release 4.0 some changes to the spool system tables are necessary. New table fields must be filled with feasible values or new tables given entries. This report executes all the required actions.

If it fails it can be restarted without problems. Adaptations not made in the previous run are carried out in this case.

The following adaptations are necessary in R/3 Release 4.0:

1. Introduction of attributes for format types

Until now the attributes for a format type have been determined from the name of a format type, according to a naming convention (e.g. lines and column no. of a list format X_65_80). However, particularly in a customer namespace, these attributes cannot always be taken uniquely from a name (e.g. differentiation of list and SAPscript formats).

For this reason the corresponding table (TSP1D) was extended by a type and additional attributes. Initially these had to be taken from the name and extended in the table entries.

Without the extension these values can no longer be printed since they are used by the function modules to select formats. The naming convention is no longer used.

1. Introduction of an attribute table for implemented formats

Until now only one table existed for the inclusion of the data lines for the format actions of a device type. The attributes were stored as text within a pseudo action. To check whether a device type supports a format type, a search must always be made for suitable entries in this data table.

The fact that a device type of a format is implemented is noted in a separate table (TSP06A) as of Release 4.0. The attributes of this implementation are also stored here.

Initially this table does not have an entry. However, as it is now being used to search for implemented formats, the status in which it arrives at the moment of the upgrade in the existing format actions must be analyzed and converted into entries in the attribute table.

Without the generation of these entries no printing can take place, since they are used by the function modules to select formats. The action table is no longer used for searching.

Requirements

The report can run repeatedly. The status of 3.X is, therefore, not a precondition.

Output

The report issues a list of the actual status and the manipulations that have been carried out. Entries are indicated as follows:

* Converted entry

Entry already updated

M Entry modified according to naming convention

X Inconsistent entry (ignored)

Incorrect conversions are underlined in red.

Example

General Data in Customer Master   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.

Length: 3012 Date: 20240601 Time: 103326     sap01-206 ( 56 ms )