Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM-MD-BP (Application Component) Business Partners⤷
FB0C (Package) Financial Accounting customers
IMG Activity
| ID | SIMG_CFORFBSXDADB | Data Transfer Workbench for Customer Master Data |
| Transaction Code | S_ALR_87001955 | IMG Activity: SIMG_CFORFBSXDADB |
| Created on | 19981222 | |
| Customizing Attributes | SIMG_CFORFBSXDADB | Data Transfer Workbench for Customer Master Data |
| Customizing Activity | SIMG_CFORFBSXDADB | Data Transfer Workbench for Customer Master Data |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_CFORFBSXDADB |
Step 1: Identify the fields you require
In this activity you determine the fields from the info record that are required for data transfer. You can find out from the online system what fields are important for your application.
Example
On the first data screen, you see the Customer field. This field is a required field. Therefore you have to make an entry for it when transferring old data. By accessing the F1 help for this field and choosing Technical info, you can see that the field is called RF02D-KUNNR in the Field name field.
By connecting the customer and vendor master records and the relevant contact persons to the central address management (CAM), you are provided with additional address fields. This additional address information is not contained in the usual master tables (KNA1 for the customer master, LFA1 for the vendor master, KNVK for the contact person), but is archived in the CAM-specific tables.
You must execute a separate transfer run from the ALE interface in order to transfer this additional address information. You must execute this run before the transfer run for master data.
If you use number ranges with internal number assignment when creating customer and vendor masters, the number by which the master object is uniquely identified in the system must be determined beforehand. This is because the address information and master data are transferred separately.
The following BAPIs can be used to determine the numbers:
- BAPI_VENDOR_GETINTNUMBER (for vendor master)
- BAPI_CUSTOMER_GETINTNUMBER (for customer master)
- BAPI_PARTNEREMPLOYEE_GETINTNUM (for contact person)
Entries continue to be made in the usual master tables for master data fields which have a matching field in the central address management (such as name, street, telephone number). The layout of these fields in the central address management is different from the original setup without a connection to central address management. SAP therefore recommends transferring the data from these fields only when transferring the CAM address information.
Activities
- Identify all the fields you require as descibed above.
- Compare the fields that contained your old date with the date fields in the SAP R/3 System.
- Determine which fields can be transferred directly to the SAP System.
- For fields that cannot be supplied with old data, establish rules on how they should be entered in the SAP System.
- Decide whether you want to transfer your old data automatically or manually. You can use batch input to transfer your old data automatically.
Step 2: Edit the transfer structure
In this activity you create the data structures for data transfer.
- Extract the data you want to transfer from the source system using your own program, and write the data to a sequential file.
- To use the SAP data structure definitions in your existing system, you can run a record layout generator. This generates an INCLUDE in either COBOL, C, PL/1, or ASSEMBLER.
The keys possible for the identifier in TSRCG are:
- FI-DEBI
This key contains all SAP tables that were combined for customer master data that is necessary for Financial Accounting.
- ALL-DEBI
This key contains all SAP tables that were combined for customer master data that is necessary for all applications.
Record layout description
The following table structures are available for the record layout:
BGR00 Batch input structure for session data
BKN00 Header data for customers
BKNA1 General data for customers
BKNB1 Company code data
BKNB5 Dunning data
BKNBK Bank details with new bank master data
BKNEX Foreign trade
BKNKA Central credit limit
BKNKK Credit limit control area data
BKNVA Unloading points
BKNVD Messages
BKNVI Taxes
BKNVK Contact person
BKNVL Licenses
BKNVP Partner functions data
BKNVV Sales data
BKNZA Alternative payer
Country-specific structures:
BKNAT Tax categories (South America)
The system expects the data you want to transfer to be in the following order in the sequential file:
- One session record for each transfer (BGR00, record type 0)
All other records up to the next session record are assigned to the last session to be read.
- One header record for each transaction (BLF00, record type 1)
All other records up to the next header record are assigned to the last transaction to be read.
In addition to the transaction code, the header record contains all data for the initial screen.
Each structure is identified by the record type and table name.
If you later extend a batch input structure, the end of the structure is identified by a special field (SENDE). If you are already using the new extended structure, enter the special NODATA character in this field when initializing the structure. This enables the system to recognize whether the data is based on the old structure or on the new one when importing it.
Transactions supported:
The following central transactions are supported in this version:
- XD01 Create Customer
- XD02 Change Customer
- XD05 Block/Unblock Customer
- XD06 Set/Reset Mark for Deletion - Customer
- FD32 Maintain credit limit
Note
- You can make extensive preliminary checks per parameter.
- You must define an entry for each field. The entry can be
- an explicit field value (to transfer a specific value)
- a special character (to transfer no value)
The special character must be defined in the "BGR00-NODATA" field in the session record.
- You must specify all fields in output format.
- After creating or changing a batch input structure, you must run the generation program RFBIKRG0 and then check the main program RFBIDE00 for syntax errors.
- Note the following authorizations for processing sessions:
- Users who process a session in the foreground must have the appropriate authorizations to do this.
- Users entered in "USNAM" in the session record who process a session in the background must have the appropriate authorizations.
Step 3: Execute the data transfer
In this activity you start the batch input program for customer master data. The program generates batch input sessions which you process in order to transfer the master data to the SAP database.
If you select Check file only, the system does not create a session, but checks whether the sequential file is set up correctly.
Requirements
You have extracted your data from the external or legacy system, and the file is accessible in the SAP System.
Activities
- Specify the name of the sequential file that contains the data from your legacy system.
- Generate the batch input session.
- Process this batch input session.
- Test the transferred data.
Further notes
You can find further information on the subject of batch input sessions in the BC System Administration documentation.
For more information about the program, see the program documentation.
Business Attributes
| ASAP Roadmap ID | 254 | Transfer Data |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 1 | Critical |
| Country-Dependency | A | Valid for all countries |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | SIMG_CFORFBSXDADB | 0 | HLA0001274 O HLB0006314 |
Maintenance Objects
| Maintenance object type | C | Customizing Object |
| Assigned objects | ||||||
|---|---|---|---|---|---|---|
| Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
| IMGDUMMY | D - Dummy object | SXDA | 0050 | Data Transfer Workbench: Customer Master Data |
History
| Last changed by/on | SAP | 19981222 |
| SAP Release Created in |
