New Transaction code in S/4 HANA for Business Partner to Set

Deletion/Archiving flag. Garbage collection ☺

Tcode:BUPA_PRE_DA

Documentation

This program allows you to transfer business partners to archiving or deletion. A prerequisite is that these
business partners are no longer actively used in business processes.

Warning
Note that the physical deletion of business partners in the productive system can be critical due to legal
regulations. Before you execute the report you should therefore check whether the business partner in your
industry can actually be deleted or whether it should be deleted and archived due to a legal storage obligation.

Integration
Plan one of the following steps once this program has run:
 • After flagging for archiving: Archiving run for archiving object CA_BUPA, transaction SARA.

• After flagging for deletion: Deletion run using the report BUPA_TEST_DELETE

Requirements
Before this program is used, an application-specific check/selection logic must be programmed and defined as
the implementation of the BAdI BUPA_DA_PREPARE.

When the flag Deletion/Archivability Check or the filter value DEFAULT is used, it should be checked before the
program is started whether all the necessary check modules in the Customizing are defined and also activated.
(transaction BUS7, events ARCH1 or DELE1).

Selection
The business partner is determined as follows:
If you fill the input field Business Partner, a selection is first carried out for all flagged business partners.

After this, you can choose a freely-definable application function using the input field Filter. New application
functions are added by implementing the BAdI BUPA_DA_PREPARE. The value corresponds to the filter value
of a relevant BAdI implementation.

If you have set the flag Deletion/Archivability Check, the now reduced hit list is also transferred to a standard
check function that anticipates checks taking place in the context of archiving or deletion. In this way no records
are flagged for archiving or deletion that would fail the subsequent checks.
The standard check function is the same as the filter value DEFAULT.

The transfer to the subsequent processes takes place

• In the case of flagging for archiving, by setting the archiving flag (radio button To Be Archived) for the
reduced hit list of business partners in each case.

At the same time you can also set the indicators System Status 'Can Be Archived' and System Status
Can Be Deleted.
The archiving flag is meant to prevent the business partner being used in new application objects.
The system status "Can Be Archived" ensures that a business partner can no longer be changed.

• In the case of flagging for deletion, by setting the system status "Deleted" (radio button To Be Deleted)
for the reduced hit list of business partners in each case.

The system status "Deleted" ensures that a business partner can no longer be changed. In addition, it
also serves as a characteristic for the selection of the records to be deleted by the subsequent
process.

The above-mentioned flags (archiving flag, system status) can be set by means of the radio button Set Flag
and, if this was a mistake, it can be canceled by means of the radio button Reset Flag.

The field Further Differentiation is not used by the program, but is instead transferred to the application-specific
BAdIs. It makes further differentiation possible within the application logic.

If the indicator Test Run, Check Only has been set, no changes are carried out on the database. The selected
business partners can, however, be displayed in the application log.
Standard Variants
None. However, a DEFAULT implementation of the BAdI BUPA_DA_PREPARE is supplied.

Output
You can store the results of the report in the application log (transaction SLG1). Set the flag With Application
Log for this purpose.

When the program is started in the dialog processing, the log is displayed immediately. In the case of
background processing the application log can be saved and displayed later. Set the flag Save Application Log
for this purpose.