Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-SRV-RM (Application Component) SAP Records Management⤷
SRM_BAPI_RECORD (Package) Business Object Interface for RM Records
Basic Data
| Data Element | BAPIANCHOR |
| Short Description | Anchor |
Data Type
| Category of Dictionary Type | Direct Type Entry | |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | ||
| Data Type | CHAR | Character String |
| Length | 64 | |
| Decimal Places | 0 | |
| Output Length | 64 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ANCHOR | |
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Anchor |
| Medium | 15 | Anchor |
| Long | 20 | Anchor |
| Heading | 32 | Anchor |
Documentation
Definition
Anchor in a record model in SAP Records Management.
For each model node in a record model, you can enter a value for the attribute ANCHOR. You can use this anchor to automatically add new elements to records at a defined position in the record.
Supplementary Documentation - BAPIANCHOR0000
Use
You can use the following methods to assign an anchor:
- Intelligent anchor update: The system automatically enters the infotype number for each infotype at the anchor position. The system finds the correct anchor in the record for each infotype.
Enter an anchor prefix.
Prerequisite: You have created a model node for every infotype in the record model. You have assigned a new value for the attibute ANCHOR to each of these model nodes. The value of the attribute ANCHOR for the model node must have the following structure: <Anchor prefix><Infotype number>.
If an infotype has one or more subtypes, these are added in sequence to the anchor with the same number as the corresponding infotype.
- Simple anchor: All infotypes and subtypes are inserted in sequence for a single model node.
Enter the same anchor that you entered in the record model as the value for the attribute ANCHOR of the model node for infotypes and subtypes.
If you do not enter an anchor, the system first tries to insert the infotype/subtype for a model node with the anchor '*' (in the standard setting, every record model has the model node Worklist element, for which the anchor '*' is entered).
- If you have deleted the model node Worklist element and the system does not find an anchor '*' or any other suitable anchor, the infotype is not inserted into the record.
Note: You can use this mechanism to deliberately prevent some of the infotypes that you specified in the Infotype from/to field from being inserted into the record: For each infotype that is to be entered, create a model node in your record model with the anchor <anchor prefix><infotype number>, and enter the anchor prefix in the report input template (see intelligent anchor update, above). Because the system does not find a suitable anchor for any other infotypes, only the required infotypes are entered in the record.
Dependencies
Example
History
| Last changed by/on | SAP | 20041216 |
| SAP Release Created in | 50A |
