The report RSBCS_ADDRESS_REFERENCE is used to release references to an address so that it can be deleted. This is executable from transaction code SE38.
Background
You get an error message when attempting to delete a business partner or contact person. This states that the address cannot be deleted because there are other references (for example, AM 266 # Personal Address Not Deleted (Other Reference)).
The address can possibly not be deleted because it was previously used as sender or recipient for e-mails, faxes, and so on.
If an address is used in the Business Communication Services (BCS) (for example, as the recipient of an e-mail), then a where-used list is written for this address. This reference establishes a connection between the address and the document that was sent. The address can only be deleted when the connection no longer exists.
Selection
On the selection screen of the report you can select either a business partner or another address of your choice. The latter can either be specified using the name or directly using the key of the Business Address Services (address number, person number).
Output
During execution the report determines all uses in the BCS and displays them. Choosing ‘Release References…# on the result screen takes you to a window with a security question. Depending on the uses, there are different options available for releasing the references.
Notes
Release References…# always refers to all objects displayed. It is irrelevant which object the cursor is on.
After using a report it is possible that an address cannot be deleted. In this case it is likely that the address was used outside the BCS. The report does not find references of this type.
Further Details on Releasing Address References:
The following uses of an address in the BCS are possible and are found and listed by the report:
- Use in documents (as sender or recipient)
- Use in business object RECIPIENT. Objects of this type are, for example, used for batch jobs with spool list recipients. But only those are listed for which there is not yet a related document. For spool list recipients, these objects are those for which the job has not yet run.
- Use in distribution lists
- Use in automatic forwards that users can set up in their personal office settings (transaction SO12). In addition to these uses the report also lists the where-used lists that are contained in table ADRVP or ADRV, depending on the address type.
The report proceeds differently when releasing references. To avoid inconsistencies, the address is replaced with a direct address for documents. This means that the recipient of a document can be determined even after the address has been deleted. Direct addresses are used only by BCS.
The report also makes it possible to reorganize the documents found directly. The same criteria are used here as for report RSBCS_REORG, that is, a document is deleted when it is no longer used.
RECIPIENT objects are used in the application to save communication addresses with send attributes in the database for use later as recipients. Since a RECIPIENT object should not be usable after deleting an address, the report replaces the address in RECIPIENT objects with an invalid, direct address that contains the name of the original address. In this way, for example, the spool list recipient of a scheduled job is still visible but sending to this address will result in an error. The objects themselves are not deleted by the report, to avoid inconsistencies in the application.
The report can remove addresses from distribution lists and automatic forwards. This does not produce any inconsistencies.
It is possible that only where-used lists and no related objects are found because they have already been deleted. Previous versions of SAPoffice Reorganization (of obsolete report RSSORE00) ignored the where-used lists inadvertently. These where-used lists are also deleted by the report.
