Kontakt

Ansicht
Dokumentation

/PM0/ABQ_EXTENSION_CONVERSION - Convert Migration Files with Partner Entities and Fields

/PM0/ABQ_EXTENSION_CONVERSION - Convert Migration Files with Partner Entities and Fields

ROGBILLS - Synchronize billing plans   Vendor Master (General Section)  
This documentation is copyright by SAP AG.
SAP E-Book

Purpose

If you want to migrate data for partner entities through the migration interface, you can use this program to convert them to generic enhancement parameters for the data import (ExtensionIn parameter).

You can also use this program to convert partner and customer fields of standard entities to ExtensionIn parameters. You can then import the resulting file with transaction LSMW.

You can find more information about BAPI enhancements under this key word in the documentation of SAP NetWeaver under http://help.sap.com/nw.

Integration

Prerequisites

  • You have created migration structures for partner entities that adhere to the FS-PM naming conventions:
/[Namespace/A[LoB]QA[Entity Code]
  • Field 1: BO_ID type /PM0/ABD_BO_ID

  • Field 2: PARENT_ID type /PM0/ABD_PARENT_ID

  • Field 3: VERSION_ID type /PM0/ABD_MIGVERSION_ID

  • Field 4: TODELETE_FG type /PM0/ABQ_TODELETE

  • This is followed by the data fields of the entity.

  • If you wish to convert partner and customer entities to ExtensionIn parameters, you must have fulfilled the following prerequisites:
  • Add the partner and customer fields to the migration structure (for instance /PM0/ABQAPOLICY) in the same order as you added them to the entity (for instance /PM0/ABDAPOLICY) by customer include or append.

  • Create a migration file that contains all of the fields of the enhanced entity in one line, and store this file in a folder.

Features

Selection

Migration File Folder: All of the migration files in the specified folder will be converted.

Separator: Specify the separator used in the migration file.

Standard Variants

Output

The converted files are stored with the extension _converted in the migration file folder.

Partner entities are converted to structure BAPIPAREX. The fields of BAPIPAREX are filled as follows:

  • STRUCTURE: Name of migration structure
  • VALUEPART1: Concatenated fields of key structure /PM0/ABQ_XKEY
  • VALUEPART2: Concatenated fields of migration structure (max. 240 characters)
  • VALUEPART3: Concatenated fields of migration structure (max. 240 characters)
  • VALUEPART4: Concatenated fields of migration structure (max. 240 characters)

If the migration structure is longer than 720 characters, the fields of the structure do not fit on one line. In this case, a second line is created for this object. The COUNTER_ID field of the key structure /PM0/ABQ_XKEY is increased by 1, and VALUEPART2-4 receive the other characters of the migration data.

Partner and customer fields are then added as lines of the type BAPIPAREX;[enhanced_entity] (for instance BAPIPAREX;/PM0/ABQAPOLICY).

Activities

  1. Create a migration file that lists the partner entities according to the above prerequisites.
  2. Store the file in a folder.
  3. Enter this folder in the Migration File Folder field of the program.
  4. Specify the Separator used in the migration file.
  5. Choose Execute to convert the files stored in the specified folder.

Example






TXBHW - Original Tax Base Amount in Local Currency   Addresses (Business Address Services)  
This documentation is copyright by SAP AG.

Length: 5394 Date: 20240418 Time: 082109     sap01-206 ( 55 ms )