Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
FBZ (Package) Payments
Basic Data
| Data Element | FORDNAMD |
| Short Description | File Name in File System or Name Proposal for Download |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | TEXT38 | |
| Data Type | CHAR | Character String |
| Length | 38 | |
| Decimal Places | 0 | |
| Output Length | 38 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | File |
| Medium | 15 | File name |
| Long | 20 | File name |
| Heading | 38 | File name |
Documentation
Definition
Complete name of the sequential file to be created.
Use
Output in the file system
If required, the file can be written into the file system. The file created can be copied onto a PC via the DME manager. When doing this, you should search for files by download since the data medium is not managed within the SAP System but has already been stored in the file system by means of the payment medium program.
If the file name is not to be specified by parameter, then it is generated by the program. It then consists of the disk format, date and time of creation as well as a consecutive number so that the file name in the file system is unique.
If the file name is specified by the user, then a consecutive number is likewise added for each program run. From an organizational point of view, however, you should make sure that already existing files are not overwritten.
Note: If you cannot find the file via the DME manager, then this can be due to the following reason: the directory which was written to when the payment medium program was started (for example, in background processing), cannot be read online. Therefore you should choose a directory which can be written to and read by different machines.
Due to the above-mentioned problems and the affect this has an data security, it is advisable not to write data to the file system. It may be advisable to use this method in cases where the data medium file is 'picked up' from the file system by an external program to be passed on to the bank.
Output in the TemSe
If required, the file created can be stored within the SAP System (stored in the TemSe and not in the file system), thus protecting it from unauthorized external access. You can download the file into the user's file system via DME management.
The name of the file to be created during the download can be determined when running the payment medium program; the contents of the file name parameter are stored in the management data and defaulted when running the download.
Example
/usr/sap/dta/<file name> or C:\DTA\<file name>
Note
Depending on the operating system used (for example, Unix), you should be aware of the differentiation between lower and upper case when specifying the file name.
History
| Last changed by/on | SAP | 19950401 |
| SAP Release Created in |
