Fonction SAP BAPI_BUS2002_ACTELEM_CREATE_M - List: Create Activity Elements

Paramètre Reférence Type Long. Valeur par déf. Facultatif Description
I_NUMBER BAPI_NETWORK_LIST-NETWORK C 12 Network Number

Paramètre Reférence Long. Facultatif Description
ET_RETURN BAPIRET2 548 X Return Parameter
EXTENSIONIN BAPIPAREX 990 X Ref. Structure for BAPI Parameters EXTENSIONIN/EXTENSIONOUT
EXTENSIONOUT BAPIPAREX 990 X Ref. Structure for BAPI Parameters EXTENSIONIN/EXTENSIONOUT
IT_ACT_ELEMENT BAPI_BUS2002_ACTELEM_NEW 647 Data Structure: Create Activity Element

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

Example

  • Parameter I_NUMBER

    • Specify the network for which the activity elements are to be createdin parameter 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 network number for internalassignment of the network number for parameter I_NUMBER.
    • Table IT_ACT_ELEMENT

      • Transfer the data for each new activity element to be created in aseparate row in table IT_ACT_ELEMENT.
      The activity number in field ACTIVITY to which the new activity elementis to be assigned, as well as the activity element number in fieldELEMENT are required-entry fields. Note that the activity in thenetwork must already exist and that the new activity element numbermust be unique for all activities and activity elements of the network.
      An activity element can be assigned to an activity that was created inthe current processing unit via BAPI BAPI_BUS2002_ACT_CREATE_MULTI.
      • Parameter CONTROL_KEY

        • Initially the CONTROL_KEY field for the control key is not arequired-entry field.
        If you do not transfer a value in the CONTROL_KEY field, an internallyprocessed activity element is created with the control key from thenetwork profile for the activity type "internal". However, if acorresponding control key is not defined in the network profile, theCONTROL_KEY becomes a required-entry field.
        INCLUDE CNIF_PI_NOT_MRP_APPLICABLE OBJECT DOKU ID TX
        • Messages from the application and a success or error message are
          • returned by the BAPI to the caller in the return table ET_RETURN. InET_RETURN, the messages are collected 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

          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 detail data for the activity elements that are to be createdfor the specified network instance.

611507Personnel number for activity element
595484Create activity via BAPI, control key: MESSAGE_TYPE_X
586151PI-BAPIs Create/change network: CORE corrections II
580136PI-BAPIs create/change network: CORE corrections