Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-MID-ALE (Application Component) ALE Integration Technology⤷
SALE (Package) Application Link Enabling
Basic Data
| Data Element | BAPIFN |
| Short Description | Function of BAPI |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | BAPIFN | |
| Data Type | CHAR | Character String |
| Length | 3 | |
| Decimal Places | 0 | |
| Output Length | 3 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | FUNCTION | |
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Function |
| Medium | 15 | Function |
| Long | 20 | Function |
| Heading | 3 | Fnc |
Documentation
Definition
In change BAPIs, database changes are made at the data record level or for lists (a group of data records).
Data records can be inserted, updated or deleted. If SaveReplica BAPIs are used, all these options can normally be carried out for objects and for sub-objects. With list operations (e.g. cost center records) new elements can be inserted or existing elements replaced.
The FUNCTION field is used for this.
With SaveReplica BAPIs you can identify what the BAPI call actually does - send, insert, update, or delete an object. The same applies to all the sub-objects. Details of the object are included in the FUNCTION header parameter. The FUNCTION field should be the first field in all structures and in all table parameters. The key fields are the next fields in table parameters.
The FUNCTION field in the header parameter describes what the message (i.e. the BAPI call) does - create, update, delete or refresh the object.
However, in the structures and tables, the FUNCTION field specifies what is to happen with the details of the object contained in it. This makes it possile to insert, change or delete details, when an object is updated (for example, insert/change/delete plant information for a material).
The BAPIFN data element is used with the FUNCTION field.
It contains the following fixed values:
- INS (insert),
- UPD (update),
- DEL (delete),
- REF (refresh) and
- IGN (ignore).
One-to-one mapping can be carried out with the MSGFN data element. (INS = 009, UPD = 004, DEL = 003, REF = 005, IGN = 018).
(Note: the receiving system does not have to be able to distinguish between create and change functions. The semantics of the SaveReplica BAPI specify that, with the functions create/change, an existing object will be changed and, if the object does not exist, it will be created.
FUNCTION as Header Parameter
In the header parameter the FUNCTION field describes the action that is to be carried out on the object:
- INS (insert): the object is to be created (or updated)
- UPD (update): the object is to be updated (or created)
- DEL (delete): the object is to be deleted (or the deletion flag is to be set)
- REF (refresh): the entire object is to be transferred by, for example, "direct dispatch" or realignment. All global information on the object is replaced by the information contained in the BAPI. If there is object data that was maintained decentrally, this must be kept separate from the global data, so that is not deleted when the object is refreshed.
FUNCTION in Structures/Tables
In structures and tables the FUNCTION field describes the action performed on the data contained in the table entry/structure or describes why the action is included in the BAPI:
- INS (insert): the entry is to be inserted
- UPD (update): the entry is to be updated
- DEL (delete): the entry is to be deleted
- REF (refresh): all table entries are to replace the global area of the object. If a structure is involved, the appropriate data record is replaced/ created. IGN (ignore): the entry has not been changed, it is only included because it includes dependent information that is contained in the BAPI call. (e.g. plant details, if changes are transferred to the plant). If check lists are used, the FUNCTION field must have the same value in the corresponding check lists/check tables.
History
| Last changed by/on | SAP | 19990505 |
| SAP Release Created in |
