Taking Over and Forwarding BP Changes
If you make changes to certain master data of a business partner in the business partner-managing system, the system flags this data for forwarding to the processor. These changes are managed in Account Management
as the card process Master Change Change (0007)
.
Features
The system first takes over the changes from the business partner application using an internal BAdI. Two implementations of the BAdI are available to you for this. For the settings and other information, see Customizing for Account Management under 
Contract Management
Card
Use of Events for Business Partner Changes.
Note
If the business partner data is located in a remote instance, you must use the implementation V1
(proxy BAdI for events that were caused by the business partner changes). Some changes are only forwarded by means of this implementation (see the following table).
Then the changes are forwarded online or via batch report to the processor.
The changes to data that is relevant for cards is forwarded for each business partner role for the following roles for a contract:
Card holder
Authorized card user
Business partner roles that you have defined in the Customizing activity
Define BP Roles Relevant to Card Management
For these settings, see Customizing for Account Management under
Card
Contract Management
Define BP Changes Relevant to Card Management
.
Note
The system only takes account of changes to natural persons. The data is only forwarded if there are valid cards or card pools for the changed business partner.
Result
Forwarded data
The following table shows which changes to a business partner result in forwarding master data and which data the system transfers to the processor, depending on the forwarding mode.
Type of Change |
Batch Forwarding |
Online Forwarding |
|---|---|---|
Change to parts of names (such as first or last name, title) of a natural person |
Current parts of names and date of birth In addition, the data for the current standard address (present) is transferred. |
Current parts of names and date of birth |
Add an address |
Current data of the address added* |
|
Delete an address |
Deleted address number |
|
Change the postal address in an address |
Current data of the changed address* |
|
Change a telephone number in an address |
Current data of the changed address* |
Current standard telephone number of the address number in question, as well as the address number and validity |
Change a fax number in an address |
Current data of the changed address* |
Current standard fax number of the address number in question, as well as the address number and validity |
Insert a relocation (move) address in a certain address |
Current data of the changed address*
The system can only forward this type of change if you have chosen the implementation End of the note. |
|
Reversal of a relocation (move) address in a certain address |
Current data of the changed address*
The system can only forward this type of change if you have chosen the implementation End of the note. |
|
Change the use of address for a certain address |
Current data of the changed address*
The system can only forward this type of change if you have chosen the implementation End of the note. |
|
*Current address data = address number, postal address, standard telephone number, standard fax number, validity
Forwarding for different dispatch address
For cards, there is the correspondence type BA29
(Different Dispatch Address
) in the system. For card contracts, you can assign this correspondence type to a card in the contract element Correspondence Recipient
by specifying an address number.
In the BAdIs for batch or online forwarding, you can check the existence of this correspondence type (in the contract present) using a customer implementation. If there are master data changes, you can forward data for the different dispatch address to the processor. For this, you use the address number stored in the contract.
More Information
For general information about the forwarding process, see Forwarding Master Data Changes.