Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM-MD-BP (Application Component) Business Partners⤷
FB0C (Package) Financial Accounting customers
IMG Activity
| ID | SIMG_CFORFBSXDABLG | Data Transfer Workbench for Accounting Documents |
| Transaction Code | S_ALR_87003390 | IMG Activity: SIMG_CFORFBSXDABLG |
| Created on | 19981222 | |
| Customizing Attributes | SIMG_CFORFBSXDABLG | Data Transfer Workbench for Accounting Documents |
| Customizing Activity | SIMG_CFORFBSXDABLG | Tools for Initial Data Transfer |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_CFORFBSXDABLG |
Step 1: Identify relevant fields
In this activity you determine the info record fields which are relevant to the data transfer. You decide online which fields are important for your application.
Example
You find the Company code field on the first data screen. This is a required field and you must therefore make an entry in it when transferring legacy data. By calling up the F1 help and pressing the Technical info button, you see that the field under Field name is called BKPF-BUKRS.
Activities
- Identify all the fields which are relevant to you as described above.
- Compare your legacy data with the R/3 System data fields.
- Determine which fields from the legacy data can be transferred directly into the R/3 System.
- Set up rules for fields which cannot be filled directly from the legacy data as to how you can still fill the R/3 System data fields.
- Decide whether you want to transfer your legacy data automatically or manually.
- If you want to transfer the legacy data automatically, you can use the batch input procedure.
Step 2: Edit transfer structure
In this activity you create the data structures for the data transfer. Here you can use your own data structures ZBSEG (for the BBSEG document segment data) and ZSELP (for the BSELP selection items (transaction FB05 only)) (see further on).
The activity consists of the following activities:
- Extract the data which is to be transferred from the source system using a program which you write yourself and write the data into a sequential file.
- You can run a record layout generator to use the SAP data structure definitions in your legacy system. This generates an include in the programming languages COBOL, C, PL/1 or ASSEMBLER, if you require this.
Record layout
The following table structures exist for the record layout:
BGR00 Session record
BBKPF BTCI header data
BBSEG Document segment data (including one-time account data, COBL
data)
BBTAX Document controls
BSELK Selection header data (FB05 only)
BSELP Selection items (FB05 only)
The following user-defined structures are possible:
ZBSEG Record type 2 Document segment data
ZSELP Record type 2 Selection items (FB05 only)
Your own structures beginning with "Z" are only allowed to differ from the standard structures beginning with "B" in as far as a number of the fields are not contained in them. The record type (-STYPE) and table name (-TBNAM) fields are not, however, allowed to be left out. Your own structures must be available in the Repository and be active. If you include fields in your own structure which are not available in the standard structure, then the transfer program for batch input terminates when you run it.
The data which is to be transferred is expected in the following sequence in the sequential file:
- A session record per session (BGR00, record type 0)
All further records up to the next session record are assigned to the last session read.
- A header record per transaction (BBKPF, record type 1)
All further records up to the next header record are assigned to the last transaction read.
In addition to the tranaction code, the header record contains all document header data.
- A record with the document segment data (BBSEG, record type 2) for each line item.
- The option of a record (BBTAX, record type 2) for each tax code.
- The selection header data (BSELK) and the selection items (BSELP) must be transferred per document for transaction FB05. The data for BBSEG must be transferred before BSELK and BSELP for technical reasons.
Up to 18 selection items can be transferred in a BSELP structure. If this is not sufficient, then further BSELP structures can be transferred.
If the length of a batch input structure is extended at a later stage, then the end of the structure is marked by a special field (SENDE). If you are already working with the new, extended structure, then fill this field with the NODATA special character when initializing the structure. This way the system can recognize when importing the structure whether the old or the new structure forms the basis of the data.
Note
Note the following:
- You can select extensive preliminary checks per parameter.
- You must define an entry for each field. This can be:
- A field value entered specifically (to transfer a particular value)
- A special character (not to transfer a value)
The special character must be defined in the session record in the "BGR00-NODATA" field.
- You must predefine all fields in the output format.
- Special G/L transactions are not supported.
- The direct input procedure does not support transaction FB05.
- After creating or changing a batch input structure, you must run the RFBIBLG0 generation program and then check the RFBIBL00 main program for syntax errors.
- Note the following authorizations when processing the sessions:
- If a session is processed online, the user who processes it must have the corresponding authorizations.
- If a session is processed in the background, the user who is entered in the session record under "USNAM" must have the corresponding authorizations.
Step 3: Carry out data transfer
Here you start the program for generating accounting documents. You have the choice between the following types of data transfer:
- Batch input
- Direct posting using a call transaction
- Direct input
For the advantages and disadvantages of the individual procedures, read the section "Accounting Document Data Transfer".
Requirements
You must have extracted your data from the legacy system and have made the file available to the R/3 System.
Activities
- Create a variant for the program for generating accounting documents.
- If you have selected batch input, make sure that the sessions generated are processed.
- If you choose "Call transaction" or "Direct input", you may have to restart the program after a program termination. Therefore also carry out the activities "Create job for document data transfer" and "Start job for document data transfer".
Additional information
You can find additional information batch input sessions in the "BC System Administration" manual. You can find more information on the program in the RFBIBL00 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_CFORFBSXDABLG | 0 | HLA0006511 O HLA0006520 O HLA0006500 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 | 0100 | Data Transfer Workbench: Accounting Document |
History
| Last changed by/on | SAP | 19981222 |
| SAP Release Created in |
