|
Functionality
This BAPI changes a change order or creates it if it does not yet exist.
- The complete new state of the change order must be transferred. If a
field is not filled, this means that the current content of the fieldis deleted, so it is not possible to transfer changes only.
- The following data can be changed with this BAPI:
Basic data (including the status) of the change order
Language-dependent descriptions
Validity
Texts and object management records are processed by their own BAPIs.There are no BAPIs for change tasks.Description
This structure contains the administrative data for the change order,such as the user who created and last changed it, and the respectivetime stamps.
This information is only processed during a distribution process (calledfrom BAPI_ECMORDER_INBOUND).
Otherwise it is ignored. The user who last changed the record is thenalways the system user. Description
Basic data of the change order.
The following fields must be filled:
- Change type (CHANGE_KIND 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 for the changeorder. Description
If a context is to have 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 intervals are 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 settings in Customizing, multiple statuses may be active inparallel. 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).
|