Solution : https://service.sap.com/sap/support/notes/517102 (SAP Service marketplace login required)
Summary :
This SAP Note addresses issues with time-dependent address usages affecting SAP Business Partner for Financial Services during upgrades to specific Banking or R/3 Enterprise releases. Problems include maintenance online, external data transfer, and conversion between SAP BP and TR BP, with impacted address determination modules. Key components also encompass function extension, error corrections, and procedural updates. Users are advised to review all associated notes meticulously for crucial support package-level information and implement recommended changes to resolve noted discrepancies and enhance program functionality.
Key words :
bckgrnd maintnnce time-depndnt address usages, - release-independent note short text 724492 - bp_dia, 677526 - report rfsbpbut020 deletes external partner number, time-dependent address usages financial services 727528 - bp_adu, time-dependent address usages financial services, sap + tr bp standard address type, /3 enterprise extension ea-fs 504734 - sap bp, time-dependent address usages created, 636199 - edt sap bp fs address usages, time-dependent address usages occur
Related Notes :
767427 | BP_ADU: Error R1614 in report RFSBPBUT021 |
766567 | BP_ADU: Termination when displaying change documents |
764550 | BP_ADU: R1612 "There is no address for business partner &" |
755612 | BP_ADU: Error in reading address usages |
750491 | BP_ADU: Error while reading address data |
749316 | BP_ADU: Report RFSBPBUT021, error in log |
747754 | BP_ADU: Performance of report RFSBPBUT021 |
738298 | BP_ADU: Performance improvement for report RFSBPBUT021 |
729592 | BP_ADU: Time-dependent address usages Financial Services |
727528 | BP_ADU: Error in the address uses (BANK/CFM 463_20) |
725889 | BP_ADU: Update termination for report RFSBPBUT021 |
725887 | BP_ADU: Error in the address determination |
724492 | BP_DIA: Correspondence language for SAP business partner |
724144 | BP_TR1: Standard indicator not set in table BUT020 |
724023 | BP_ADU: FSBP_READ_ADDRESS_DATA FM not rfc-enabled |
721721 | BP_ADU: Performance problem with report RFSBPBUT021 |
717945 | BP_ADU: Address usages not transferred to loans |
717833 | BP_ADU: R1 856: "Error when updating table BUT021" |
717831 | BP_ADU: Various corrections for report RFSBPBUT021 |
708117 | BP_ZZZ: City name is only output in upper case |
705841 | BP_ADU: Communication data is selected incompletely |
704768 | GP_ADU: Incorrect traffic lights with WUL for addresses |
704767 | BP_ADU: Address usages not active in some roles |
703393 | BP_ADU: Same usage more then once in the menu tree |
700524 | BP_ADU: External data transfer of address usages |
695812 | BP_POT: Display of address types for loans FNVS |
693547 | BP_TR1: Correspondence language for persons is missing |
691847 | BP_ADU: Short dump when creating/changing a loan |
691327 | BP_ADU: Various corrections to FS read modules |
689957 | BP_TR2: Correction report adjustment for table ADRC |
686087 | BP_ADU: Error when editing a special arrangement |
684664 | BP_PAR: Error in parallel maintenance and address conversion |
679126 | SAP BP: Various corrections for FS address read modules |
677526 | Report RFSBPBUT020 deletes external partner number |
677462 | SAP BP address usages: Start date after end date possible |
677237 | SI: Error when creating an alternative address |
670406 | Incorrect scroll bar in BP address overview |
670034 | BP_ZZZ: Incorrect formatting of addresses |
666801 | SAP BP: Error AM053 after RFSBP_CUST_ADDRESS_UPDATE |
663280 | SAP BP address usages: Multiple assignment of same address |
656796 | BP_CVI: Bckgrnd maintnnce time-depndnt address usages in CVI |
652599 | SAP BP address usages: Changes in display mode possible |
652049 | SAP BP:Problems while scrollg in time-dependent addr.usages |
651195 | BP_ADU: Addr.usages lost in loan during partner maintenance |
648464 | BP_ADU: Incorrect read logic in FSBP_DBREAD_BUT021_FS |
647973 | BP_ADU: Address info in addr.usage overview not updated |
645872 | BP_TR1: Conversion of form of addr:Corr report for tab. ADRC |
643033 | SAP BP ADVW: Description 'SDSD' for address usage XXDEFAULT |
642884 | BP_ADV: Incorrect fields in EDT filled by addr.usage |
642420 | SAP BP: Where-used list for addresses incorrect |
636199 | EDT SAP BP FS address usages: Overlaps possible |
635397 | SAP BP: No change documents for address usage date |
634554 | SAP BP: Read module FSBP_DBREAD_BUT021_FS incorrect |
633843 | BP_ADU: Error in address formatting (form of addr, language) |
632530 | SAP BP ADVW: Various corrections "Address usage conflicts" |
629569 | BP_BAP:2 New BAPIs for addresses with time-depend. usages |
623450 | SAP BP: Problems using PS and FS applications in one client |
621959 | PAR: Parallel update of address usages: incorrect transfer |
619636 | SAP BP: Various corrections for read modules of SAP BP FS |
618291 | C_ADR: Redundant update BUT021 from BUT021_FS |
617414 | SAP BP: Adjustments in report RFTBP030 |
617220 | BP_POT: Address transfer to loan contract |
617172 | BP_BAP: New BAPIs for addresses with time-depent. usages |
617052 | SAP BP: Various adjustments for report RFSBP21FS |
616625 | SAP BP: Report RFSBPBUT020 not complete |
616044 | BP_ADU: Limited use of the BAPIs for SAP FS BPs |
615194 | SAP BP: Transfer of current standard address to customer |
615131 | FS BP: c/o address not transferred |
614663 | BP_ADU: Addresses in overview indistinguishable |
607007 | SAP BP: Report RFSBPBUT021 does not change table BUT020 |
605368 | BP_ADU: FM FS04_BUPA_MEMORY_GET returns incorrect data |
603007 | BP_ADU: E-mail address not found (error FTRO263) |
601008 | BP_ADU: Read logic in FS04_BUPA_MEMORY_GET not correct |
598142 | BP_ADU: Incorrect data transfer from BUT021_FS to BUT021 |
594871 | BP_BDT: Address usage and "Company code data" button |
591721 | SAP BP: Deletion report for time-dependent address usages |
590392 | BP_TR1: Incorrect report RFTBP030 (convert BP addresses) |
588916 | BP_ADU: Address usage conflicts for business partner |
588851 | SAP BP address usages: Various corrections |
581758 | SAP BP ADVW:Buttons active in display mode |
573969 | BP_CDC: Incorrect generation change docs for address usage |
572257 | BP_CDC: Short dump change docmts of time-depend.addr.usages |
569561 | SAP BP ADVW: Incorrect error because of overlap, short dump |
566432 | SAP BP ADVW: Sorting in tree, overlaps, short dump |
564976 | SAPBP: Addrs Mangmt: update termin (CML) & delete address |
564339 | BP_CDC: Validity date is missing in the change documents |
563077 | SAP BP: Short dump with report RFSBP21FS (memory overflow) |
560753 | SAP BP: Address read modules find no/incorrect address type |
559617 | SAP BP address uses:Various corrections |
557372 | BP_ADU: Switch for time-dependent address usage |
555558 | Address uses: Different corrections |
555138 | SAP BP: Address uses (dialog and conversion) |
550854 | SAP BP: SAP + TR BP standard address type in parallel maint. |
550547 | FS BP:EDT:Termination if internal address number not filled |
550153 | SAP BP: Address modules always generate default address |
547299 | SAP BP: Address usages (conversion, parallel maint., dialog) |
544759 | SAP BP: Conversion/maintenance of address uses (XXDEFAULT) |
538748 | PAR: Dialog box (missing postal code) when saving SAP BP |
536636 | BP_XDT: Error FSBP519 with Modify/Delete of address usage |
536249 | SAP BP: PAR: House number not transferred to TR BP |
535351 | BP_XDT: MODIFY always uses number of standard address |
532705 | BP_CDC: Validity date is missing in the change documents |
532670 | Activating the R/3 Enterprise Extension EA-FS |
532246 | BP_XDT: Missing address number for the EDT address usages |
532191 | BP_XDT: Error in DI of the time-dependent address uses |
531424 | BP_XDT:Incorrect Modify of the address usages for DI |
513762 | PAR:Standard address transferred incorrectly into BP030 |
505977 | SAP BP conversion Customizing: View V_TP14 and standard flag |
504734 | SAP BP: Time-dependent address usages of SAP BP for FS |
398888 | BP_TR1: Composite note and FAQs about bus partner conversion |