Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
KC (Package) Cost Accounting Controlling EIS
IMG Activity
| ID | SIMG_CFOKCMKCF0 | Import File |
| Transaction Code | S_ALR_87000283 | IMG Activity: SIMG_CFOKCMKCF0 |
| Created on | 19981222 | |
| Customizing Attributes | SIMG_CFOKCMKCF0 | Import File |
| Customizing Activity | SIMG_CFOKCMKCF0 | Import File |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_CFOKCMKCF0 |
Description
Using this function, you import data from a file. In order to import larger datasets periodically, you can schedule program RKCFILE0 in the background.
Requirements
You must have maintained the sender structure and the transfer rules and if applicable the Sender structure package.
Parameters
Program parameters
You need to enter either a physical file name or a logical file name.
File system
Under 'File system', you define whether the file is on the presentation server or application server. Make sure that the process which is to read the data has the right access authorization for the file. The path must also have been entered correctly. If you wish to read data from the application server, make sure that you enter the path from the point of view of the user who started the application server. You should enter an absolute path. Note that only files from the application server can be imported in the background.
Options
Under 'Options', you can choose whether you wish to
- execute a data transfer,
- display the file and
- display the assignment of fields from the sender record to field contents.
If you check off 'Display fld assignment for sender rec.', the system displays a list of which value is contained in which sender record. Using this list, you can see whether the sender structure is correct or not. Note that the output list is stored in the main memory and can require a lot of space with large files.
File type
Under 'File type', you determine whether you wish to import a text file. With this type of file, there is a Newline at the end of each line. For the binary file, you need to choose SAP binary format. Caution: Binary files cannot be read from the presentation server. For TXT format, the fields in the lines must be separated by tabs. For CSV format, the fields must be separated by semicolons. For MC format, the file to be imported is split into two parts: Lines at the beginning with characteristic values which are valid for the rest of the record and individual records. The fields in these individual records are separated by a field separator (either a comma or a semicolon).
Example
Here is an example of a file in MC format, in which all the records are for fiscal year 1994 and period 002:
1994
002
00000001;PROFITC;00004543000 ;000000004534500 ;000000004000430
00000001;PROFITC;00004555000 ;000000004523000 ;000000004800000
The field separator in this file is the semicolon.
In a text file with field separators, the individual fields in the file are assumed to be separated by the sign which you entered as the field separator.
Number format
If you wish to import numbers of type 'P', you can define whether these numbers are to be stored in the file in double length as characters '0123456789+- ' or in the SAP format (packed). Internally, the system usually works with packed numbers during a data transfer. If the numbers are stored in single length in the file, the system assumes that the numbers do not need to be packed into SAP internal format. If the numbers are stored in double length on the file, the system converts the numbers into packed format. The minus sign can be placed before or after the numbers. Apart from binary and text files, the default defines that packed numbers are always stored in double length in the file and therefore need to be converted. You can choose whether the numbers have no editing character or have a decimal point (or comma).
- If the numbers have a decimal point, it is assumed that the points are only present for display purposes. If you have indicated that there are no editing characters in the file, the number of places after the decimal point is determined from the specification of the decimal place in the sender structure.
If you are importing master data or comments for master data, this option is not valid and is therefore not offered.
Integer and floating point numbers must have 12 or 16 bytes in the file.
Date format
Under 'Date format', you decide which format the date is to be in: YYYYMMDD or DD.MM.YYYY. You only have this choice for TXT / CSV / MC format. For all other formats, the date must be in format YYYYMMDD.
Other settings
Under 'Data format', you can check off whether the data is in ASCII or EBCDIC format. In EBCDIC format, all fields apart from packed fields (type P) and hexadecimal fields (type X) are converted from EBCDIC to ASCII. If your file has comment lines that are not to be imported you can indicate them as such here. Enter the character with which the comment lines begin. The system will ignore these lines when importing the file.
Settings for repeat fields
In many information systems, the period is locked for transaction data. In such cases, the period is not contained in the key of the transaction data record, however, key figures are then stored n times in the non-key portion, where n is the number of periods. During data transfer, records in such structures cannot be transformed into transaction data records in which the period is stored in the key and the key figure only once in the non-key portion of the record.
Example
The records in an example file have the following structure:
Field Description
GJAHR Fiscal year
BUKRS Company code
WERKS Plant
KOSTL Cost center
WTA01 Value A Period 1
WTA02 Value A Period 2
WTA03 Value A Period 3
WTA04 Value A Period 4
WTA05 Value A Period 5
WTA06 Value A Period 6
WTA07 Value A Period 7
WTA08 Value A Period 8
WTA09 Value A Period 9
WTA10 Value A Period 10
WTA11 Value A Period 11
WTA12 Value A Period 12
WTB01 Value B Period 1
WTB02 Value B Period 2
WTB03 Value B Period 3
WTB04 Value B Period 4
WTB05 Value B Period 5
WTB06 Value B Period 6
WTB07 Value B Period 7
WTB08 Value B Period 8
WTB09 Value B Period 9
WTB10 Value B Period 10
WTB11 Value B Period 11
WTB12 Value B Period 12
This record must be transformed into 12 records with the following structure:
Field Description
GJAHR Fiscal year
PERDE Period
BUKRS Company code
WERKS Plant
KOSTL Cost center
WTA Value A
WTB Value B
The second record differs from the first in two ways:
- It contains the field PERDE. You enter this field in parameter 'Index field' on the selection screen.
- Instead of 24 fields WTA01, ..., WTA12, WTB01, ..., WTB12, it contains two fields WTA and WTB.
In order to carry out the data transfer, the structure of the second record must be defined. To transform the first record into 12 records of the second structure, you must make the following entries on the selection screen:
Parameter Entry
Index field PERDE
Repetition factor 12
Start value for index field 1
Increment for index field 1
Repeat fields WTA
WTB
The result of the transformation of the first record into the second can be described as follows:
- Twelve records are created. The number of records corresponds to the repetition factor.
- The index field of the first record is the start index. The following records are calculated from the <start index> + <increment for index field> * m. m is the following number of the record. The following number of the first record is zero. The following number of the twelfth record is eleven. In this example, the field PERDE is numbered from 1 to 12.
- In the first record, field WTA is filled with the value of WTA01 and field WTB with the value of WTB01. In the second record, field WTA is filled with the value of WTA02 and WTB with the value of WTB02. In the twelfth record, field WTA is filled with the value of WTA12 and WTB with the value of WTB12.
Note
Note that in TXT, CSV and MC format, fields of type 'C' which are not text fields are automatically converted into capital letters.
Output
If you checked off 'Display file', the system displays a list of transferred records. If you checked off 'Display fld assignment for sender rec.', the system displays additional information about how the individual fields of the sender record were filled. If you have transferred the data, you receive a message informing you of the success of the operation. You will find more detailed information about the update
Business Attributes
| ASAP Roadmap ID | 254 | Transfer Data |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-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_CFOKCMKCF0 | 0 | HLA0009491 | Data Collection |
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 | KCF0 | 285 | Import File |
History
| Last changed by/on | SAP | 19981222 |
| SAP Release Created in |
