Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
CV0C (Package) R/3 applications development: Cust. document management sys.
IMG Activity
| ID | SIMG_CFMENUSAPCFILE | Maintain File Names and File Paths Across all Clients |
| Transaction Code | S_ALR_87007752 | IMG Activity: SIMG_CFMENUSAPCFILE |
| Created on | 19981222 | |
| Customizing Attributes | SIMG_CFMENUSAPCFILE | Maintain file names and file paths across all clients |
| Customizing Activity | SIMG_CFMENUSAPCFILE | Maintain file names and file paths across all clients |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_CFMENUSAPCFILE |
Note for document distribution
You require a global directory that is accessible from all platforms (for example, UNIX, Windows NT) for document distribution. The documents that are to be distributed are stored temporarily in this directory.
You require directory DOCUMENT_DISTRIBUTION for document distribution. All the settings that you need for this directory are available in the in the standard system.
General notes
This activity (transaction FILE) is for cross-client maintenance of logical filenames and file paths and includes the following:
- Logical file path definition
- Assignment of physical paths to logical path
- Logical file name definition, cross-client
- Definition of variables
- Syntax group definition
- Assignment of operating system to syntax group
Choose one of these in the navigation area of the screen to see the corresponding view of the values to be maintained. You can examine existing entries and enter new values. Depending on the data you need to maintain, you can either work in the overview or you may need to go to the details view by pressing F2 or the "Details" push button in the application toolbar.
Note
Release 3.0C introduces cross-client logical filename maintenance. In addition to cross-client maintenance you can still choose to maintain filenames for a specific client. You must maintain a logical filename across clients before you can maintain it for one client. Then you can maintain it for particular clients as required.
Use program RSFILE01 to transfer filenames from the client-specific maintenance (available before Release 3.0C) to cross-client maintenance. Client-specific data is not affected.
Activities
- Verify that existing definitions meet your needs.
- Change the definitions (and, if necessary, the structure of your file system).
- If necessary, define additional filenames and paths.
Business Attributes
| ASAP Roadmap ID | 203 | Establish Master 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_CFMENUSAPCFILE | 0 | HLB0100242 | Document Distribution |
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 |
| FILENAME | C - View cluster | FILE | DVS | Logical file name maintenance |
History
| Last changed by/on | SAP | 19981222 |
| SAP Release Created in |
