Functionality
Change one or more activities (subobject of the BOR object typeBUS2002001). Activities of one network only can be changed each timethis BAPI is called.

Example

• Parameter I_NUMBER

Specify the network for which the activities are to be changed inparameter I_NUMBER.
The network can already exist in the database, or have been createdpreviously in the current processing unit via BAPI"BAPI_BUS2002_CREATE". In the second case, use the temporary networknumber for internal assignment of the network number for parameterI_NUMBER.

• Tables IT_ACTIVITY und IT_UPDATE_ACTIVITY

Transfer a separate row in the tables IT_ACTIVITY andIT_UPDATE_ACTIVITY for each activity to be changed. The mapping of bothtable entries takes place via the activity number field (ACTIVITY)
Fill the table entry in IT_ACTIVITY with the data that is to be changedfor the activity.
In the table entry in IT_UPDATE_ACTIVITY flag all fields that are to beupated with the values from IT_ACTIVITY with an "X".
All other fields remain unchanged even if values were assigned to themin IT_ACTIVITY. This BAPI works therefore according to the "change byflagging" principle (refer also to the programming guide in the BAPItransaction).
Entries in table IT_UPDATE_ACTIVITY that do not have a corresopndingrecord in IT_ACTIVITY are ignored.
Entries in table IT_ACTIVITY that do not have a corresponding record intable IT_UPDATE_ACTIVITY generate an error.
If the tables IT_ACTIVITY and/or IT_UPDATE_ACTIVITY contain severalentries with the same key ACTIVITY, system behaviour is undefinedbecause unique mapping is not possible.
INCLUDE CNIF_PI_NOT_MRP_APPLICABLE OBJECT DOKU ID TX
INCLUDE CNIF_PI_LTXA1_KTSCH OBJECT DOKU ID TX

• Temporary activity

An activity to be changed can already exist in the database or havebeen created previously in the current processing unit viaBAPI_BUS2002_ACT_CREATE_MULTI. You can change an activity within aprocessing unit several times via BAPI BAPI_BUS2002_ACT_CHANGE_MULTI.

• Return table ET_RETURN

Messages from the application and a success or error message arereturned by the BAPI to the caller in the return table ET_RETURN. InET_RETURN, the messages are collected together in blocks per activity.Each message block refers therefore to an activity and starts with asummarized success or error message.

Notes
INCLUDE CNIF_PI_BAPI_HINTS OBJECT DOKU ID TX

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. Procurementof the data takes place in the relevant BAdI.