Ansicht
Dokumentation

BUPTDTRANSMIT - Distribution of time-dependent business partner data

rdisp/max_wprun_time - Maximum work process run time   CPI1466 during Backup  
This documentation is copyright by SAP AG.

Purpose

In Release 6.40, time dependency is partially introduced for the SAP Business Partner, in the form of time constraints for bank details (table BUT0BK), business partner roles (BUT100), addresses (BUT020), and communication data for address usages (ADR2-13, ADRU), as well as full time dependency for address usages (BUT021_FS). In Release 7.0, full time dependency for the central data (BUT000_TD) as well as time dependency for EEW extensions was also introduced for the Business Partner. This could result in problems when business partner data is exchanged with other applications or systems, if they do not support time dependency, or cannot process time-dependent data.

Therefore when business partner data is saved, the data records whose validity start falls in the future or whose validity is restricted and falls in the future, are saved in a separate table BUT_TDTRANS. Thus this data is not distributed to applications that do not support time dependency.

The data records in question may distributed only when the validity actually begins or ends. Distribution takes place by means of the report BUPTDTRANSMIT that distributes all entries from table BUT_TDTRANS that are valid on the current date to applications registered in table TB048. Execute the report daily if possible in order to keep the data up-to-date.

The table BUT_TDTRANS is filled only if at least one active application is registered in table TB048 when the data is saved. However it is always possible to use the program BUPTDTRANSGEN to generate the BUT_TDTRANS entries subsequently.

In addition, it is necessary that an entry exists in table TB058 for every table that is to be distributed. This entails defining for each table, the update structures needed for the interface modules, as well as the modules for distributing and generating the distribution-relevant business partner data.

Caution

No entries are written to the table BUT_TDTRANS for the central data (tables BUT000 and BUT000_TD). However, the central data that will become valid in the future is integrated into the scenario, because when BUPTDTRANSMIT is run, a check is first carried out to determine whether there are records in the table BUT000 that are not valid on the current date. All of these records are exchanged for the relevant records from the table BUT000_TD that are valid on the current date. When the data that has been exchanged is posted, all information on the new BUT000 time slices is then distributed via the regular posting per BAdI. If there was a complete integration of the tables BUT000 and BUT000_TD in the process described above, the data would then be distributed twice. For this reason, integrating the BUT000 data in the table BUT_TDTRANS would not only be unnecessary, it would actually be incorrect.

Integration

The entries in the table BUT_TDTRANS are generated using the report BUPTDTRANSGEN.

Prerequisites

All applications that want to participate in the distribution of time-dependent data using the report BUPTDTRANSMIT must register themselves in table TB048 (maintenance view V_TB048) as active applications. Function modules are defined here for transferring the data.
The standard SAP system contains the function module SAP BWBUPA_DEF_ADDRESS_DELTA_QUEUE_B (with active usage) and the function module BUPA_OUTBOUND_TDTRANSMIT (with active usage), for example, for outbound processing of the SAP Business Partner.

The relevant module is called by the report BUPTDTRANSMIT as follows:

call function lt_tb048-funcname

TABLES

t_but0bk = lt_but0bk

t_but020 = lt_but020

t_but021_fs = lt_but021_fs

t_but100 = lt_but100

t_adr2 = lt_adr2

.....

t_adr10 = lt_adr10

t_adr13 = lt_adr13

t_adru = lt_adru

EXCEPTIONS

others = 1.

The table entries are based on the TB058 entries, whereby not all tables must be contained in the interface (is determined dynamically by the program).

The modules assigned in table TB058 are called by report BUPTDTRANSMIT or BUPTDTRANSGEN with pre-defined interfaces. The modules BUPA_TRANS_SELECT_SINGLE and BUPA_BUTTDTRANS_GENERATE can serve as an example for the central data.

Features

The program BUPTDTRANSMIT can be started for any selection of the applications listed in table TB048. Initially, all the records that have become valid in the meantime are determined from table BUT_TDTRANS and are read subsequently together with the table key of the respective business partner tables. If the record is not found in the table, then this is a case of a deletion operation; meaning that the update indicator of the table record is filled with 'D'. If the record only becomes valid for that date, the indicator 'I' for Insert is transferred. If it is a move that does not coincide with the deletion date or validity start data, a 'U' is transferred.
The table records determined in this way are transferred to the selected applications using the module defined in table TB048.
If a record cannot be processed, the application returns it with the update indicator 'E'. If the transfer module triggers an exception that is marked as containing errors by at least one application, then all the records are treated as containing errors.
All records that are marked as containing errors by at least one application, are recorded application-specifically in the table BUT_TDMISS. Only when a record has been distributed successfully to all applications is it deleted from the table BUT_TDTRANS (and if necessary also from BUT_TDMISS).
The date of the last erroneous and the last successful BUPTDTRANSMIT run is recorded subsequently in table BUT_TDAPPLI for each application.

Selection

Standard Variants

Output

Activities

Example

RFUMSV00 - Advance Return for Tax on Sales/Purchases   PERFORM Short Reference  
This documentation is copyright by SAP AG.

Length: 6570 Date: 20240531 Time: 015909     sap01-206 ( 147 ms )