Functionality
Change one or more activity elements (subobject of the BOR object typeBUS2002001). Each time this BAPI is called, only the activity elementsfor one network can be changed.

Example

• Parameter I_NUMBER

Specify the network for which the activity elements are to be changedin parameter I_NUMBER.
The network can already exist in the database or have been createdpreviously in the current processing unit via BAPIBAPI_BUS2002_CREATE. In the second case, use the temporary networknumber for internal assignment of the network number for parameterI_NUMBER.

• Tables IT_ACT_ELEMENT and IT_UPDATE_ACT_ELEMENT

Transfer a row for each activity element to be changed in the tablesIT_ACT_ELEMENT and IT_UPDATE_ACT_ELEMENT. The mapping of both tableentries takes place via the activity element number field (ELEMENT).
Fill the table entry in IT_ACT_ELEMENT with the data of the activityelement that is to be changed.
In the table entry in IT_UPDATE_ACT_ELEMENT, flag all fields that areto be updated with the values from IT_ACT_ELEMENT with an "X".
All other fields remain unchanged, even if new values have beenassigned to them in IT_ACT_ELEMENT. This BAPI therefore works accordingto the "change by flagging" principle (refer also to the programmingguide in transaction BAPI).
Entries in table IT_UPDATE_ACT_ELEMENT that do not have a correspondingrecord in table IT_ACT_ELEMENT are ignored.
Entries in table IT_ACT_ELEMENT that do not have a corresponding recordin table IT_UPDATE_ACT_ELEMENT generate an error.
If the tables IT_ACT_ELEMENT and/or IT_UPDATE_ACT_ELEMENT each containseveral entries with the same key ELEMENT, system behaviour isundefined because unique mapping is not possible.

• Temporary activity element

An activity element to be changed can already exist in the database orhave been created previously in the current processing unit via BAPIBAPI_BUS2002_ACTELEM_CREATE_M. You can change an activity elementseveral times within a processing unit via BAPIBAPI_BUS2002_ACTELEM_CHANGE_M.
INCLUDE CNIF_PI_NOT_MRP_APPLICABLE OBJECT DOKU ID TX

• Messages from the application and a success or error message are
returned to the caller by the BAPI in the return table ET_RETURN. InET_RETURN, the messages are grouped together in blocks per activityelement. Each message block refers therefore to an activity element andstarts with a summarized success or error message.

Notes
INCLUDE CNIF_PI_BAPI_HINTS OBJECT DOKU ID TX LANGUAGE EN

Description
Data for customer enhancements is imported using the container"ExtensionIn", as described in the BAPI programming guide. Furtherprocessing of the data is carried out in the relevant BAdI.

Description
Customer enhancement data is exported using the container"ExtensionOut", as described in the BAPI programming guide. Theprocurement of the data occurs in the relevant BAdI.

Description
A list of the detail data of the records to be changed. Data fields ofthe activity element of the specified network instance are overwrittenwith these values, provided they are flagged in the update structure.

Description
Update structure of the records to be changed. Only the flagged fieldsof the activity element are overwritten in the data structure.