Hierarchy
⤷ CA (Application Component) Cross-Application Components
⤷ CFX_BI_0C (Package) Customizing for cFolders backend integration
Basic Data
Data Element | CFX_BI_LOOK_UP_DEPTH |
Short Description | No.of Document Copies for Tracking Origin in Backend System |
Data Type
Category of Dictionary Type | Direct Type Entry | |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | ||
Data Type | INT1 | 1-byte integer, integer number <= 255 |
Length | 3 | |
Decimal Places | 0 | |
Output Length | 3 | |
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 | L.Up Depth |
Medium | 18 | Look Up Depth |
Long | 40 | Look Up Depth for Document Origin |
Heading | 15 | Look Up Depth |
Documentation
Definition
This field sets how many movements of the document you want traced when reimporting documents.
This field is only used for reimporting documents and their original application files from cFolders after they were exported using backend integration.
When exporting using backend integration the document key is transferred to the cFolders area as an alias. When reimporting to the backend system from cFolders the interface determines the target document in the backend system based on this alias and creates a new document version. This target document appears in the list at the bottom of the screen. The user can change the target document by hand before copying the documents to the backend system. If the interface cannot determine a target document because it does not find an alias it allows the user to determine where the document is stored in the R/3 backend system.
An alias, and therefore a document key, is not found when the document:
- Was not exported using backend integration
Or
- Was created from another source
Or
- Was copied one or more times across areas
When a document is moved (copied) across areas within cFolders the document key is "lost" because aliases and labels are not copied.
Setting Look Up Depth to 1 or higher level (0 for no movement, searches this area only, 1 for 1 movement, 2 for 2 movements and so on) tells the system to search document movement(s) (copying) across areas to find the document key and find the target document in the backend system.
Example
You exported a document and its original application file to the Public Area of a collaboration project using backend integration. The document key from the backend system was copied to cFolders as an alias at this time. A partner then copies the document and its original to another area. The alias and therefore the document key is "lost" during this movement to the partner area.
You then want to copy the document from the partner area to the backend system. You set the Look Up Depth to 1 to ensure that the backend system will look at the document in the partner's area as well as one previous document, therefore finding the alias in the Public Area. The backend system determines the target document in the backend system and creates a new version in the backend system.
History
Last changed by/on | SAP | 20050615 |
SAP Release Created in |