Functionality
This function module is used for creating and changing equipment. Itsfunction corresponds to the function modules BAPI_EQUI_CREATE andBAPI_EQUI_CHANGE.
A multilingual processing of short and long texts(create/change/delete) is also possible.
The function module can be used for mass processing and works on the"all-or-nothing principle". This means that either all equipment can becreated/changed, or no equipment can be created/changed.

Notes
The data for a piece of equipment is in the following tables:

• CT_DATA


• CT_DATAX


• IT_DESCRIPT


• IT_LONGTEXT

All the tables contain a field TA_GUID. The data for a piece ofequipment can be determined using this field. Each piece of equipmenthas exactly one CT_DATA and CT_DATAX record. However, it can haveseveral IT_DESCRIPT and IT_LONGTEXT records.

Description
This structure contains all the master data of a piece of equipment. Itunites the import parameters of the function modules BAPI_EQUI_CREATEand BAPI_EQUI_CHANGE.
It includes the following structures:


• BAPI_ITOB


• BAPI_ITOB_EQ_ONLY


• BAPI_ITOB_EQ_INSTALL

For more information, see the documentation of the corresponding importparameters in the function modules BAPI_EQUI_CREATE andBAPI_EQUI_CHANGE.
The following fields are also included:

• TA_GUID


• EQUIPMENT_EXT


• EQUIPMENT_INT


• MDM_FLAG


• VALID_DATE


• WORK_CTR_EXTERN


• WORK_CTR_PLANT

With the TA_GUID field you can determine the data for a piece ofequipment using the various tables.
The EQUIPMENT_EXT field contains the key of the equipment. If thisfield is initial, the system tries to create a new piece of equipment.If this field is not initial, the system checks whether there is apiece of equipment with this key. If so, then the equipment isupdated. If not, the system creates a piece of equipment.
The EQUIPMENT_INT field contains the key of the piece of equipment thatwas created/changed.
If the MDM_FLAG field is set, special MDM coding is run.
The VALID_DATE field is only relevant for creating a piece ofequipment. It contains the valid from date for the equipment to becreated.
The external description and the plant of the responsible work centeris stored in the WRK_CTR_EXTERN and WRK_CTR_PLANT fields. The systemuses this data to determine the internal description of the responsiblework center (WORK_CTR field). If it cannot determine an internaldescription from the external description, then the internaldescription is initialized. This means that the WORK_CTR field must notbe filled before being called up.

Description
This structure corresponds to the BAPI_ITOBX and BAPI_ITOB_EQ_ONLYstructures.
Every parameter in CT_DATA has a corresponding "selection parameter".Only the fields marked here with "X" are used for changing the data.
You can use the EQUIPMENT_X field to control whether a possibleexternally-specified number should be used for the creation. IfEQUIPMENT_X is initial, the number is assigned internally at creation.If none is specified, then number assignment is always internal.

Example
You want to update a piece of equipment with data from a source system.However, field NN cannot be maintained in the source system. Field NNis maintained in the target system (R/3).
Field NN is always delivered in an initial state from the source systemand this initial value should not overwrite the value maintained in thetarget system. This is achieved by setting the corresponding "selectionparameter" to initial.

Description
For a piece of equipment, short texts/long texts can becreated/changed/ deleted in several languages:


• The field DELETE_DESCRIPT specifies whether the short text should be
deleted.

• The field DELETE_LONGTEXT specifies whether the long text belonging to
the short text should be deleted.
In R/3, a long text cannot exist without a short text. If the fieldDELETE_DESCRIPT is set, but the field DELETE_LONGTEXT is not set, thenthe short text is just reset to its initial value but not deleted.
If you want to delete the long text belonging to a short text, you justhave to set the field IT_DESCRIPT-DELETE_LONGTEXT. You do not have toenter the long text using the structure IT_LONGTEXT as well.

Description
Short texts / long texts can be created/changed/deleted in multiplelanguages for a piece of equipment.
Individual lines of existing long texts cannot be changed. Changing along text means replacing the existing long text with the specifiedlong text.
Equipment can have two different long texts: the long text for theequipment header and an internal comment. The system uses the TEXT_IDfield to distinguish between the two long texts. The long text for theequipment header has the ID LTXT. The internal comment has theID INTV. At present it is only possible to copy the long textfor the equipment header.
The DELTE_LONGTEXT field specifies whether the long text should bedeleted. The field value for the first line of the long text determineswhether or not the long text is deleted. If you want to delete the longtext for the equipment header, you just have to set the fieldIT_DESCRIPT_DELETE_LONGTEXT. You do not have to specify the long textas well.
The internal comment only has a long text, but no short text. For suchlong texts, the deletion is controlled by the fieldIT_LONGTEXT-DELETE_LONGTEXT of the first long text line.
INCLUDE BAPI_RETURN OBJECT DOKU ID TX LANGUAGE EN