Fonction SAP BAPI_ECMORD_INBOUND - Engineering Change Order: Inbound Distribution

Paramètre Reférence Type Long. Valeur par déf. Facultatif Description
ADMIN BAPI_ECM_ORDER_ADMIN u 50 X Administrative Data: For Distribution Only
DETAILS BAPI_ECM_ORDER_DETAIL u 102 Engineering Change Management: BAPI Structure for Engineering Change Order
ORDER BAPI_ECMORD_FIELDS-ORDER C 12 Engineering Change Management: BAPI Element 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 serves as an interface when distributing change orders.Internally, the change BAPI is called after an indicator that controlsthe distribution logic is set.
The scope of functions for distribution is identical to the scope offunctions for the change BAPI.

Description
This structure contains administrative data for the change order, suchas the user who created and changed the order and their time stamps.
In distribution, unlike other uses of the BAPI, the administrative datais copied from the source system unchanged.

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 the language-dependent descriptions of thechange order.

    Description
    If a context is to have a parameter effectivity (in which case it musthave an effectivity type entered in Customizing), this table gets a linefor each context with the parameter names and values. If intervals aremaintained, there are multiple lines for a context.

    Description
    In this table, in field STATUS_SYSTEM, the new status is specified.

    • Depending on Customizing, more than one status may be active in
      • parallel. This applies to system status distributable.
      • The fields with the short and long description of the status are
        • ignored.

        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
            • here. It is only filled when the validity is displayed.
            • For each context, a time interval can 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.