Fonction SAP BAPI_ECMORD_CREATE - Create Engineering Change Order

Paramètre Reférence Type Long. Valeur par déf. Facultatif Description
DETAILS BAPI_ECM_ORDER_DETAIL u 102 Details of Engineering Change Order
ORDER_NEW BAPI_ECMORD_FIELDS-ORDER C 12 Engineering Change Order

Paramètre Reférence Long. Facultatif Description
IT_DESCRIPTIONS BAPI_ECM_ORDER_DESCR 43 X Descriptions
IT_PARAMETER BAPI_ECM_PARAMETER 158 X Parameter Effectivity
IT_STATUS BAPI_ECM_STATUS 40 X Status
IT_VALIDITY BAPI_ECM_VALIDITY 58 X Validity
RETURN BAPIRET2 548 X Return Parameters

Functionality
This BAPI creates a change order.

  • It checks whether the change order already exists.

  • Then the change BAPI is called, which can both create and change.

    • This means that you only need to use this BAPI if you want to ensurethat you are not changing an existing change order. Otherwise, use thechange BAPI only. For more information, see the documentation of thechange BAPI.

    Description
    Basic data of the change order.
    The following fields must be filled:

    • CHANGE_KIND (change type from Customizing)

    • ORDER_TYPE (order type)

      • The domain ECMTYP defines the possible values (N, V, C, and L).

      Description
      Name of the change order.

      Description
      This table contains all language-dependent descriptions of the changeorder.

      Description
      If a context is to have a parameter effectivity (in which case it musthave an effectivity type entered in Customizing), this table contains aline for each context with the parameter names and values. If intervalsare maintained, there is more than one line for a context.

      Description
      In this table, the new status is specified in the required format.Depending on Customizing, multiple statuses may be active in parallel.This applies to system status distributable.

      Description
      This table contains the complete validity of the change order, with theexception of parameter effectivity.

      • First, the contexts that are to get a validity are specified. The
        • contexts must be defined in the change type of the change order.
        • Each context gets a status. The time stamp for release is irrelevant. It
          • is only filled when outputting the validity.
          • For each context, a time interval can also be specified, within which
            • the context is to be valid.
            If parameter effectivity is required, it must be specified for eachcontext in a separate table, because BAPI interfaces do not allow nestedtables.

            Description
            Log messages of the BAPI.