SAP Accounting Consulting

Symptom

This note tries to answer questions on the SAP business partner that may have come-up on an upgrade to SAP_ABA 5.0A and higher releases:
1. Is table BUT001 obsolete?
The table BUT001 is obsolete from SAP_ABA release 5.0A and higher. It is now possible to maintain multiple identification and industry sector information for a business partner. The identification data is maintained in table BUT0ID and the industry sector information is maintained in table BUT0IS.

2. Is there a standard conversion report available to move data from BUT001 to tables BUT0ID and BUT0IS?
Schedule and execute report BUPXPRA13 to migrate data from BUT001 to BUT0ID. More information is available in the release note for SAP WebAS 610
Schedule and execute report BUPXPRA12 to migrate data from BUT001 to BUT0IS

3. Can the reports BUPXPRA12 and BUPXPRA13 be re-run?
The BUPXPRA12 and BUPXPRA13 are one-time conversion programs. They must be executed once on the whole partner range.

4. There are customer defined fields in BUT001. What happens to this data in 5.0A and higher?
The table BUT000 can be used for appending customer defined fields. The data in BUT001 must be migrated by an own program to BUT000. In release 700 (ERP2004, CRM 5.0) and above, the tool Easy Enhancement Workbench is available to create customer defined fields.

5. Is there any report to be run on upgrade to SAP_ABA release 7.0 and above?
There is no need for a report on upgrade to SAP_ABA 7.0 and above as there is a mechanism of gradual conversion of BPs which is in place to make the older data compatible with release 7.0 and above. This conversion happens on the first access of the partner in either transaction BP or in a BAPI read functionality.
The side effect of the conversion in transaction BP (or in an equivalent dialog transaction) is a pop-up informing that ‘Data is changed. Do you want to SAVE the changes?’ – requesting a SAVE of data even though nothing was changed in the transaction. This is not an error but is designed to happen only on the first access to the BP.
Mass conversion of BPs to SAP_ABA 7.0 release and above: There is a possibility to run report BP_TD_SWITCH as parallel batch jobs scheduled at non-critical times to ensure that the data is converted and is compatible with the SAP_ABA 7.0 format.
BPs that have been converted and compatible with the SAP_ABA 7.0 release format will have the indicator TD_SWITCH set in table BUT000.

6. Does running BP_TD_SWITCH mean that the system becomes time dependent?
Running report BP_TD_SWITCH does not mean that the system becomes time dependent.It only makes the datasets of BP compatible with the SAP_ABA 7.0 format. The following operations are performed during execution of BP_TD_SWITCH
1. Activation of planned changes as real changes based on past or scheduled activation dates. This implies that planend changes are also now stored in the corresponding master data tables (BUT000_TD, BUT0BK, BUT100, BUT020)
2. Conversion of standard address flag (XDFADR) in table BUT020 to standard address usage (address type XXDEFAULT) in table BUT021_FS.
3. Updation of BUT020 records with validity periods.
4. Migration of address usages from table BUT021 to table BUT021_FS with validity periods. Table BUT021 is no longer used after release SAP_ABA 640
For further details refer to the report documentation of BP_TD_SWITCH in transaction SE38.

7. After upgrade, whenever I open a BP, I get the error mesage R11 349
In the earlier release, planned changes may be maintained or time validity for address usages may have been set while Financial services application was active.
The time dependency settings configured do not match the data that exists on the database. Refer to the Note 810634 to configure the time dependency activation settings in transaction SPRO (table TB056)

8. On upgrade from SAP_ABA 640 to 700 and above, should time dependency be maintained active?
Yes. All datasets must be maintained time dependently, ie. the time dependency activation switch must be set as active for BUT020, BUT100, BUT0BK. Please note that time dependency must be activated on upgrade from SAP_ABA release 640 only

9. Planned change functionality for business partners were used in the lower release. On upgrade from SAP_ABA 46C, 50A, 620 to 700 and above, should time dependency be maintained active?
Set time dependency for the corresponding datasets as active in the following cases:
If planned changes were used in lower release
If FS was active in lower release
In all other cases, the decision to set time dependency or not is left to the customer.
Once decision is made to switch on, the customer is advised NOT to switch off time dependency
For more details, refer note 810634

10. In case there is a need to establish data-exchange with another system or set up master-data-synchronization with customer or vendor in the system immediately after an upgrade, are there any precautions to be followed?
First, ensure that the data in the database is compatible with the SAP_ABA 700 and above format. Mass conversion of business partner data after upgrade may be performed using the report BP_TD_SWITCH.
Run report BP_TD_SWITCH during non critical times in parallel batches. If there are planned changes, BUT020, BUT021_FS, BUT100 and BUT0BK will carry the scheduled changes as active as on run date.
If there are no planned changes, only BUT020 and BUT021_Fs will be adjusted for address and usages from the old address usage table BUT021
Next, if the FS was active in the older release, ensure that reports run in the order
1. note 889788 and
2. note 931355 (only execute this report on upgrade from 640 to higher release)
Thirdly, run report in note 941186 to add missing validity periods to the datasets BUT0BK and BUT100. Note that this will add default validity as 01.01.0001 to 31.12.9999.

11. When the Master data synchronization is in place, adding sales area (or datasets other than bank details) to the Business Partner results in deletion of bank details. Similar deletion of bank details happen on updating datasets other than bank details. Is there a solution?
Refer to the note 941186. Consult SAP to verify the case.

12. Are there any precautions to take while using the master data synchronization framework for synchronizing the Business Partner master data with customer or vendor master and vice versa?
If the master data synchronization is in place before the validity periods are updated to the existing bank details in table BUT0BK, the data exchange may ignore the bank details as they are not considered currently valid. Refer to the note 941186 for a solution.

13. There is a performance problem with respect to the execution time of report BP_TD_SWITCH. Is there anyway to improve performance?
Ensure that the below notes are applied in the system before
running the report BP_TD_SWITCH:
867862 : SAP BP: duplicate record – BUA_ADDRESS_XPRA_TD
852263 : Deactivating the buffer in BP_TD_SWITCH
858868 : Error in Max Time Calculation for report
808815 : BP_TD_SWITCH does not convert all partner data
911201 : SAP_BP:Problems updating table TB009 in BUA_ADDRESS_XPRA_TD
956454 : SAP BP: Endless loop in business partner TD switch.

14. The standard address indicator is not set in table BUT020 after upgrade to SAP_ABA release 640 and above.
From release 640 and above, the standard address is represented via the Standard address usage (XXDEFAULT address kind in table BUT021_FS).
Refer note 761663 for more details
More details:
The conversion automatically happens on accessing the partner via transaction BP or via a BAPI read functionality.
In order to do a mass conversion for all partners, report BP_TD_SWITCH may be used. Run report BP_TD_SWITCH during non critical times and in parallel batches.

15. After an upgrade, error message R11 117 or R11 118 is thrown saying there is no standard internal or external grouping.
Refer to note 917825 for a solution.

16. After an upgrade, all address usages stored in table BUT021 are lost.
If the older release had maintained no financial services (FS) address usages (address usages were stored in table BUT021), then the system after upgrade must be configured similarly (FS must not be active after upgrade until the conversion of all partners to SAP_ABA 700 format or above is completed) This is necessary so that the gradual conversion or report BP_TD_SWITCH picks usages from BUT021 table. Otherwise (if FS is active), the system would pick the address usages from table BUT021_FS and DELETES the usages in BUT021 table.
Check if the system has FS as active. To do this: Execute the Function module FSBP_CHECK_FS_CRITERIA in transaction SE37. If the result is ‘X’ -> FS application is active. If so, deactivate the FS application until the conversion is completed for all partners.

17. You want to upgrade to SAP_ABA 700 release and you want to activate FS as well, when upto now FS has been inactive.
In what sequence this has to be carried out?
You should first upgrade, then activate FS. Do NOT activate FS and then upgrade.The reason for this is that the report BP_TD_SWITCH checks whether FS is active and based on the value it will take the entries from BUT021 or BUT021_FS.
If FS is active, the entries in BUT021_FS are considered, thus deleting the entries from BUT021. This might result in loss of required data.
So it is preferred that the upgrade must be done first and then the activation for FS.

Other terms

SAP_BP BP_DIALOG BP_TD_SWITCH XXDEFAULT BUT001 BUPXPRA12 BUPXPRA13
R11117 R11118 BUA_ADDRESS_XPRA_TD BUPA_TD_PARTNER_SWITCH TB009 TB001 TB038 TB039 TB023 BUT000 BUT0BK BUT020 BUT021_FS BUT021 FSBP_CHECK_FS_CRITERIA R11 349 BP_TD activation TB056 SAP_ABA 640 6.4 7.0 7.1
Reason and Prerequisites

This note serves as a supplement for SAP Notes and release notes. The note attempts to answer most frequently asked questions on upgrade to SAP_ABA release 5.0A, 640, 700 and above

Solution

For further information please check the release note of the corresponding release