Ansicht
Dokumentation

ADT_CONFIG_SERV_ENTRIES_CHGS - changes done for data in configuration service tables

RFUMSV00 - Advance Return for Tax on Sales/Purchases   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.

Purpose

Making ADT_CONFIG and ADT_CONFIG_PROPS tables client-dependent

Integration

Prerequisites

Table structure should be changed.

Features

Selection

Standard Variants

Output

Activities

The purpose of the report is to delete the redundant entries in 2 tables i.e.

1) ADT_CONFIG

2) ADT_CONFIG_PROPS

ADT_CONFIG_PROPS borrows a foreign key from ADT_CONFIG table.

The above 2 tables have been changed from client-independent to client-dependent.

A new column 'MANDT' gets added after this change to both the tables. All the rows in both the tables get multiplied for each client.

The logic is as follows:

We already have a field called 'client' in the table ADT_CONFIG. This column value would help to identify the genuine client to which the row belongs to. With the help of client field we try to remove the redundant rows.

Logic :

·,,If mandt is equal to client, then such a row belongs to that client.

·,,If mandt is not equal to client remove the row.

·,,The method remove_redundant_entries would remove such unwanted rows in both the tables ADT_CONFIG and ADT_CONFIG_PROPS.

Example

Let's say there are 5 entries in table ADT_CONFIG when the table is client-independent.

Imagine a system having 5 clients. Making the table ADT_CONFIG client-dependent would make the entries in table 5*5 = 25 entries.

As you see, only 5 rows are actually productive. The remaining 20 are redundant.

The code in the report removes such unwanted rows in both the tables ADT_CONFIG and ADT_CONFIG_PROPS.

PERFORM Short Reference   General Material Data  
This documentation is copyright by SAP AG.

Length: 2003 Date: 20240531 Time: 190459     sap01-206 ( 31 ms )