Ansicht
Dokumentation
FSBP_IDNUM_MIGRATION_START - Update Additional Partner Numbers to Identification Numbers
Addresses (Business Address Services) BAL Application Log DocumentationThis documentation is copyright by SAP AG.
Purpose
As of Release SAP_ABA 7.10, the additional partner numbers will be replaced by identification numbers. This means that you can now process identification numbers for a business partner centrally and consistently.
If you have already entered additional partner numbers in table BPID001 (Additional Partner Numbers), then you have to transfer this dataset to table BUT0ID (BP: Identification Numbers) after the upgrade and convert the corresponding change documents.
You use this report to convert the additional partner numbers into identification numbers.
The report uses the SAP Framework for Parallel Processing of Mass Data (CA-GTF-TS-PPM).
Integration
Prerequisites
- There are additional partner numbers in table BPID001 that have to be converted to identification numbers after the upgrade to Release SAP_ABA 7.10.
- You have made all the Customizing assignments between the additional partner numbers and the identification numbers that are required for the conversion using the report FSBP_MAINTAIN_IDTYPE_MAPPING ( Assign Identification Number Categories to Identification Categories and Types).
- If you have enhanced the additional partner numbers with customer-defined fields, then you have also created an active implementation of the enhancement spot FSBP_IDNUM_MIGRATION (BAdI: Convert Additional Partner Numbers).
- You have activated the business function CA_FSBP_MIGRATION_ID (FS-BP: Migration of Additional Partner Numbers).
Features
Before the report converts the data, it checks whether all prerequisites are met. If the required prerequisites are not met, then the system displays the appropriate error messages and the report terminates processing. If the prerequisites are met, then the report schedules the jobs to convert the additional partner numbers in accordance with the settings made.
If errors occur during job processing (if a business partner to be processed is locked, for example), then the system leaves the corresponding entries in table BPID001. Once you have removed the cause of this error, then you can start the report again, either with the same start conditions or you can limit processing to the business partners that still have to be processed.
The processing status is not tracked for individual business partners. The system does not automatically restart the report. You must run the report as often as you need to convert all the data.
When all identification numbers have been converted and there are no more entries in table BPID001, the system sets the status of the migration to Completed. The system then writes a corresponding entry to table FSBP_ID_STATUS (Status Information for Conversion of Identification Numbers).
Selection
- Unique run ID
- Define a unique run ID each time you start the report. You can use this ID to find the processing log in the application log (transaction SLG1).
- Package size
- If you want to determine the number of identification numbers that are converted in one step, then you can define a package size.
- Business partner number
- If you want to limit the business partners that are to be converted, then you can define which business partner numbers are to be included in the conversion.
Standard Variants
Output
If errors occur during processing, the system writes them to an application log.
Activities
Define a unique run ID, make settings for the report, and run the report as often as you need to convert all the additional partner numbers from table BPID001.
Example
Addresses (Business Address Services) CPI1466 during Backup
This documentation is copyright by SAP AG.
Length: 4346 Date: 20240531 Time: 113850 sap01-206 ( 76 ms )
