Functionality
This Business ApplicationProgramming Interface (BAPI) is used to change maintenance or serviceorders and their subobjects. The following objects of an order can beprocessed (restrictions are listed at the end of the documentation):

• Order header


• Partner


• User status


• Order operations


• Relationships


• Components


• Long text for order header, operations, and components


• Settlement rules


• Object list


• Object list links


• Production resources/tools

Function
Calling this BAPI once allows you to perform all the operations. Forthis the system supplies the function module with a method tablecontaining the methods to be performed. The entries in the method tablerefer to data records in the optionally filled-out data tables. All themethods from the method table are performed. Alternatively, justsubobjects of existing orders can be changed, without changing theheader.
You can process the transferred data with theBusiness Add-In (BAdI)IBAPI_ALM_ORD_MODIFY to, for example, merge data from the externalsystem with data from the SAP system. The BAdI is called as soon as thetransferred data is converted to the internal formats. The checks thentake place after this.
INCLUDE BAPI_COMMIT OBJECT DOKU ID TX

Structure of Method Table


• REFNUMBER,,Reference number for linking object method to attributes

The reference number is the line of the database which contains thecorresponding data. The data table is determined by the object type.

• OBJECTTYPE,,Object type

The object category specifies which object from the order should beprocessed. The key words listed here are not language-dependent and mustbe transferred exactly as they are. The following objects exist:
HEADER,,,,Order header
PARTNER,,,,Partner data
USERSTATUS,,User status
OPERATION,,,,Operation data
RELATION,,,,Relationships
COMPONENT,,Component
TEXT,,,,Long texts
SRULE,,,,Settlement rule
OBJECTLIST,,,,Object list
OLISTRELATION,,,,Object list links
TASKLIST,,,,General maintenance task list
PRT,,,,,,Production resources/tools
(Blank),,,,,,General BAPI functions (Save)

• METHOD,,,,Method

The methods with which the data is to be processed. The followingfunctions exist:
CREATE,,,,,,Create objects
CREATETONOTIF,,,,,,Create notifications
CHANGE,,,,,,Change objects
DELETE,,,,,,Delete objects
RELEASE,,,,,,Release
TECHNICALCOMPLETE,,Technically complete
ATPCHECK,,,,,,Availability check
CALCULATE,,,,,,Estimate costs
SCHEDULE,,,,,,Schedule
DELELTEDSEX,,,,Delete the status for external scheduling at operationlevel
ADD,,,,,,Add (only possible for object TASKLIST)
SAVE,,,,,,Save all data
DIALOG,,,,,,Dialog call. See explanation below.
TRACE,,,,,,Write trace file to the specified file at the front end

• OBJECTKEY,,,,SAP-external object key

This key is for assigning the lower-level objects correctly to thecorresponding objects, as there is always just one key in the datatable. The key must have the following structure:
1-12,,,,Order number
When creating orders with internal number assignment, a reference numberbeginning with % must be entered here. The BAPI then returns this numberand the number actually assigned.
13-16,,Operation number
17-20,,Suboperation number
For relationships, the key is structured as follows:
1-12,,,,Order number from
13-16,,Operation number from
17-28,,Order number to
29-32,,Operation number to
INCLUDE BAPI_ALM_ORDER_MAINTAIN OBJECT DOKU ID TX

Data Tables and Update Tables
The objects have one or more data tables. For some objects you canspecify which of the fields specified in the structure should bechanged. For this you must set the field in the corresponding table toX as in the data table. If no update table is transferred, thenonly those fields are set that have a value that is not initial.This simplifies the transfer data. However, this means it is notpossible to delete fields. If an update structure should only bespecified for some data records, the table with the update fields mustnonetheless have the same number of lines as the data table. The emptylines are then treated as if no update structure was transferred. Theobjects "Partner", "User Status", "Text", and "Task List" have no updatetables. The whole data record is always copied here.

References
The objects use the field REFNUMBER from the method table torefer to the lines in the data table. Counting always begins with 1. Indoing this, REFNUMBER also refers to the update table. However,in the method table there is a second reference to the higher-levelobject for subobjects. The field OBJECTKEY must be filled withorder number, operation number, and suboperation number, as specifiedabove. If subobjects of a newly created order should be changed, thenyou must enter a temporary order number that must begin with %. Severalorders can be numbered consecutively, for example, with %00000000001,%00000000002. For external number assignment, the external order numbermust be used here.
The following objects have special handling for REFNUMBER:


• Partner

Partners have an order number in the data table. During processing ofthe method table, all those entries in the data table are processed thathave an order number that is the same as that in the line to which themethod refers. Thus, through just one entry in the method table, severalpartners can be changed.

• Texts

Texts are composed of two tables. The first table (IT_TEXT) is made upof the header data of the text. Here you must specify the object and thefirst and last line of the text table (both inclusive, counting from 1).This specifies a line segment in the text line table (IT_TEXT_LINES).

Special Features in Processing
The BAPI processes the transferred methods in a particular sequence
, which need not correspond to the sequence in the methods table.


• Write trace file


• Change user status time 1


• Delete objects (dependent first)


• Create new objects


• Change existing or newly created objects


• Change user status time 2


• Status change of order


• Save data

The methods are performed such that subobjects can also be assigned tonewly created objects. For example, first the operations are created,and then the components. Long texts can also be created for the objects.
Components have an exceptional position. Components are createdthrough the assignment to an operation, that is, using the "key" order/operation (item number). However, as this is not the unique componentkey, you can only access the components to change them, delete them, oradd long texts by using the reservation number/item, which is only givenafter saving. This means that, for example, you cannot create a longtext when you create the component.
For settlement rules the following account assignment types aresupported:

• Cost center


• Order


• WBS element


• Asset


• G/L account


• Sales document

User status changes can take place at two different time points.Time point 1 is before the object changes, time point 2 is after theobject changes and before the status change of the system. These timepoints should be defined in the transfer table in the CHANGE_EVENT
field. The field documentation contains the possible values.
The external scheduling is offered by the BAPI as a specialfunction. The BAPI can set the date field directly at the operationlevel, and select the operation with the status DSEX (Date set byexternal system). This status prevents any further scheduling of theoperation. The transferred dates are retained. For this, set thecategory X in the restriction categories. When reading theoperation, this category is also returned, independent of the categoryof restriction set in the dialog. To delete the status, you can call upthe method DELETEDSEX for the object operation. The external schedulingcannot be influenced in dialog. All changes to the schedulingrestrictions in the dialog are saved, but they are not relevant forscheduling as long as the status DSEX is active.
A SAVE or DIALOG method must be transferred in every callof the BAPI. Usually, the BAPI call is thought of as a transaction. Alldata that is changed in the BAPI should also be saved immediately to thedatabase. The BAPI checks whether a SAVE method exists. Otherwise, itterminates processing. A test run of the BAPI consists of a standardcall with SAVE method, followed by a BAPI_TRANSACTION_ROLLBACK. To callthe BAPI without the SAVE method, for example, to realize dialogtransactions, the BAPI can be called with the DIALOG method. Thisswitches off the check for the SAVE method. The caller must then ensurethat later either a SAVE method or a BAPI_TRANSACTION_ROLLBACK iscalled.
A BAPI_TRANSACTION_COMMIT without SAVE method terminates processing inthe update to ensure that no inconsistent data is written to thedatabase. The caller that called the BAPI does not receive anyconfirmation of the termination of the update in the target system. Thislogic is necessary as the order data was flagged for updating withBAPI_TRANSACTION_COMMIT through the SAVE method. However, the statusinformation was already flagged for updating when the BAPI was called. ABAPI_TRANSACTION_COMMIT without SAVE method then just saves the statusinformation and would generate inconsistent orders, if the updating wasnot terminated.
The TRACE method is used to save an XML trace file on the frontend under the file name specified in the OBJECTKEY field. Thisfile can only be written if the BAPI is called from the dialog, that is,from the SAP GUI. The file is not written if background processing isused, nor is it written if the call originates in a different system.This file can be used by SAP for analysis purposes. SAP does not intendto use this data productively.

Customer Enhancement
The BAdI IBAPI_ALM_ORD_MODIFY can be used to change thetransferred data. The BAdI is called up after the conversion of thetransfer structure into the structures used internally. Additional datacan be transferred using the table EXTENSION_IN. Only then is the datachecked.

Refurbishment Order
BAPI BAPI_ALM_ORDER_MAINTAIN also supports the creation and change ofrefurbishment orders.
Refurbishment-order-specific header data, item (component) data, andserial number data is always created and updated together with the orderheader data even though it is passed to the BAPI separately.
In order to support refurbishment-order-specific data, the interface ofthe BAPI has been enhanced by the following table parameters:


• IT_REFORDER_ITEM (BAPI_REFORDER_ITEM_I)


• IT_REFORDER_ITEM_UP (BAPI_REFORDER_ITEM_UP)


• IT_REFORDER_SERNO_OLIST_INS (BAPI_REFORDER_SERNO_OLIST_I)


• IT_REFORDER_SERNO_OLIST_DEL (BAPI_REFORDER_SERNO_OLIST_I)

Refurbishment order item data (IT_REFORDER_ITEM) is mandatory for thecreation of refurbishment orders. A refurbishment order cannot becreated without this data. If serial numbers are to be assigned to therefurbishment order (object HEADER, method CREATE/CHANGE), they mustalso be passed using the parameter IT_REFORDER_SERNO_OLIST_INS. If aserial number is to be unassigned from the order during an update of theorder (object HEADER, method CHANGE), the parameterIT_REFORDER_SERNO_OLIST_DEL must be passed to the BAPI. Only existingserial numbers can be assigned to the refurbishment order.
Refurbishment-order-specific parameters are always processed togetherwith the order header data. This means that if the refurbishment orderis created or updated, the order header data structures must be providedby the calling application. Even if the header data itself must not beupdated, at least the order number of the refurbishment order beingupdated must be provided in the order header structures:

• IT_HEADER (BAPI_ALM_ORDER_HEADERS_I)


• IT_HEADER_UP (BAPI_ALM_ORDER_HEADERS_I_UP)

In all cases, the update and creation of the data of the first componentin the refurbishment order (the refurbishment order item), as well asthe assignment and unassignment of serial numbers, is triggered byproviding the HEADER object with the corresponding method CREATE orCHANGE in the method table
The HEADER object for a refurbishment order is also responsible forcreating and updating the refurbishment-order-specific data, forexample, plant from/to; storage location from/to, batch from/to,valuation type from/to). There may be several serial numbers assigned toa single refurbishment order, so the parameter table must always containthe order number to which the serial number is assigned.
The data of the first component (refurbishment order item) is alwayscreated with the order header data. In order to be able to create thisdata, the HEADER function must be specified in the method table.
The data of the first component can be updated either with the headerdata (object HEADER, method CHANGE) or separately by specifying thefunction component update (object COMPONENT, method CHANGE) in themethod table. If the data of the first component is updated with theorder header data, then the structures for the header data must also bepassed to the BAPI interface (the order number at least must bespecified). If both methods of updating the component data are usedsimultaneously in the method table, then the refurbishment order itemdata is updated with the header data.
When the refurbishment order is created, the first operation isgenerated automatically. If this generated data needs to be changed, anupdate must be triggered in the method table. The first operation mustbe generated for refurbishment orders (unlike standard orders) in orderto make it possible to create the data of the first component with therefurbishment order header data.
The BAdI BADI_REFORDER_BAPI_MESG allows the user to suppress somemessages that are raised during the creation or update of arefurbishment order. These messages are shown as warning messages whenthe back-end transaction is executed, so this BAdI provides the userwith the flexibility to control the message type of these messages inthe BAPI.

Restrictions and Limitations


• The first operation cannot be created as an external operation.


• The first refurbishment order operation must not be created manually by
passing the relevant data trough the method table.

• When more than one order is processed at once, the same serial number
must not be assigned to several orders.

• The same serial number can be assigned to another order only if the
first order has been successfully committed to the database table.

• Only existing serial numbers can be assigned to the refurbishment order.


• The first generated refurbishment order component cannot be updated
within the execution of the same BAPI call.

DIMP-Specific Features


• An order can be created from a notification using the CREATETONOTIF
method for the object type HEADER.

• A notification can be created for the order.


• The notification type has to passed within the parameter IT_HEADER
(BAPI_ALM_ORDER_HEADER_I-NOTIF_TYPE)

• A notification can be separated from the order.


• The notification type (NOTIF_TYPE) must be empty in the IT_HEADER, and
the corresponding update flag (NOTIF_TYPE) must be set in the updateparameter IT_HEADER_UP.

• An object list can be maintained for the refurbishment order.


• DIMP-specific fields can be maintained at the header level:

Special stock is determined automatically from the equipment ormaterial/serial number stock data if the refurbishment order is beingcreated for a piece of equipment (BAPI_ALM_ORDER_HEADER_I-EQUIPMENT) ora material/serial number (BAPI_ALM_ORDER_HEADER_I-SERIALNO andBAPI_ALM_ORDER_HEADER_I-MATERIAL have to be specified in tableIT_HEADER)
Sales order, sales item (BAPI_ALM_ORDER_HEADER_I-SALES_ORD andBAPI_ALM_ORDER_HEADER_I-S_ORD_ITEM must be specified in the tableIT_HEADER)

• DIMP-specific fields can be changed at the component level. In
particular, the special stock indicator can be set for the component.

Example
The following examples illustrate usage:

Creating an order
OBJECTKEY should be filled with a temporary key. The BAPI returnsthis key together with the assigned order number in the return tableET_NUMBERS. The order number in the HEADER table should also befilled with the number. For external number assignment, the externalnumber should be specified. The update structure can be transferred ifnecessary.
Methods table
REFNUMBER,,OBJECTTYPE,,METHOD,,OBJECTKEY
1,,HEADER,,CREATE,,%00000000001
IT_HEADER
ORDERID,,ORDER_TYPE,,PLANPLANT,,...
%00000000001,,PM01,,1000,,...

Creation of an order with operation and long text
Methods table
REFNUMBER,,OBJECTTYPE,,METHOD,,OBJECTKEY
1,,HEADER,,CREATE,,%00000000001
1,,OPERATION,,CREATE,,%00000000001
1,,TEXT,,CREATE,,%000000000010010
IT_HEADER
ORDERID,,ORDER_TYPE,,PLANPLANT,,...
%00000000001,,PM01,,1000,,...
IT_OPERATION
ACTIVITY,,SUB_ACTIVITY,,CONTROL_KEY,,WRK_CNTR,,...
10,,,,PM01,,MECHANIK,,...
IT_TEXT
ACTIVITY,,...,,TEXTSTART,,TEXTEND
10,,...,,1,,2
IT_TEXT_LINES
TDFORMAT,,TDLINE
*,,Long text for operation 10, line 1
*,,Line 2 of the long text

Creation of the refurbishment order header data with one serial numberassigned (operation and first component are created automatically):
Methods table
REFNUMBER,,OBJECTTYPE,,METHOD,,OBJECTKEY
1,,HEADER,,CREATE,,%00000000001
1,, ,,SAVE,,
IT_HEADER
ORDERID,,ORDER_TYPE,,PLANPLANT,,...
%00000000001,,PM04,,0001,,...
IT_REFORDER_ITEM
ORDERID,,REQUIREMENT_QUANTITY,,PLANT_TO,,PLANT_FROM,,...
%00000000001,,3,,0001,,0002,,...
IT_ REFORDER_SERNO_OLIST_INS
ORDERID,,SERIALNO,,UII
%00000000001,,SN01,,

Creation of the refurbishment order data, changing the first operationdata, adding the second operation and second component:
Methods table
REFNUMBER,,OBJECTTYPE,,METHOD,,OBJECTKEY
1,,HEADER,,CREATE,,%00000000001
1,,OPERATION,,CHANGE,,%000000000010010
2,,OPERATION,,CREATE,,%00000000001
1,,COMPONENT,,CREATE,,%00000000001
1,, ,,SAVE,,
IT_HEADER
ORDERID,,ORDER_TYPE,,PLANPLANT,,...
%00000000001,,PM04,,0001,,...
IT_REFORDER_ITEM
ORDERID,,REQUIREMENT_QUANTITY,,PLANT_TO,,PLANT_FROM,,...
%00000000001,,3,,0001,,0002,,...
IT_OPERATION
ACTIVITY,,SUB_ACTIVITY,,...,,DESCRIPTION,,..
0009,, ,,...,,Update of 1st Operation,,..
0020,, ,,...,,New 2nd Operation,,..
IT_OPERATION_UP
ACTIVITY,,SUB_ACTIVITY,,...,,DESCRIPTION,,..
X,, ,,...,,X,,..
IT_COMPONENT
RESERV_NO,,RES_ITEM,,PLANT,,MATERIAL,,...
,, ,,0001,,MN_01,,...

Update of the data of the refurbishment order#s first component fromheader data (recommended):
Methods table
REFNUMBER,,OBJECTTYPE,,METHOD,,OBJECTKEY
1,,HEADER,,CHANGE,,000004000001
1,, ,,SAVE,,
IT_HEADER
ORDERID,,ORDER_TYPE,,PLANPLANT,,...
000004000001,, ,, ,, ...
IT_HEADER_UP
ORDERID,,ORDER_TYPE,,PLANPLANT,,...
000004000001,, ,, ,, ...
IT_REFORDER_ITEM
ORDERID,,REQUIREMENT_QUANTITY,,PLANT_TO,,PLANT_FROM,,...
000004000001,,6,,9999,, ,,...
IT_REFORDER_ITEM_UP
ORDERID,,REQUIREMENT_QUANTITY,,PLANT_TO,,PLANT_FROM,,...
000004000001,,X,,X,, ,,...
IT_REFORDER_SERNO_OLIST_DEL
ORDERID,,SERIALNO,,UII
000004000001,,SN01,,

Notes

Using the BAPI to process the order data cannot support all thefunctions of the transaction. This applies in particular to thefollowing functions:
Order header data


• The estimated costs cannot be processed - only the estimated overall
costs of the order.

• Notification data cannot be processed with the order BAPI, even if the
settings in Customizing are such that the orders and notifications canbe maintained on one screen. However, the system will create anotification with the order if this is specified in the Customizingsettings.

• Permits cannot be processed.


• The order addresses cannot be processed.


• Individual partner addresses cannot be maintained.

Order functions

• Printing the papers is not possible.


• Locking and unlocking the order is not possible.


• Accepting and rejecting quotations is not possible.


• Business completion is not possible.


• Flagging for deletion is not possible.


• The log cannot be displayed.


• User default values are not used.


• The field selection is not checked.


• The Customer Exits/BAdIs are not executed completely.


• Joint ventures are not supported.


• Funds Management is not supported.


• Investment orders are not supported.


• No integration of service products with task lists is possible if
configuration data has to be maintained.

• No integration of configurable service products is possible if
configuration data has to be manually maintained.

• Assignment of sales document items with service products in accordance
with the aforementioned conditions.
Operation data

• A change of the control key in the operation is not possible, if this
leads to a change of the processing type (internal/external processing).

• User status change not possible.


• Production resources and tools cannot be processed.


• Service lines cannot be processed.


• Integration of task lists with configurations is not supported, since
manual maintenance of the characteristic valuations would be performedin the dialog.

• Automatic linking of operations with object list is not
supported. If a new operation is to be generated for a new object listentry, you must do this by creating a new operation in the correspondingBAPI method and linking to the object list entry using the objectOLISTRELATION.
Component data

• User status change not possible.


• BOM data cannot be processed.


• The delivery address cannot be processed.

Further information
See also the documentation for the individual transfer tables.

Description
Table with the order numbers issued by the system. The temporary numbercopied to the function module and the number assigned by the system areassigned with this.

Value range
The temporary number begins with % z.B. %00000000001

Description
Option of transferring customer-specific fields to the BAPI andanalyzing the fields in the BAdIIBAPI_ALM_ORD_MODIFY or transferringthem to internal structures.

Procedure
The following enhancement structure exists for using the Customer Exit:


• BAPI_TE_ALM_ORDER_MAINTAIN

The structure has the fields of the method table as key fields. Thus thecorresponding methods and thereby the referenced data structure can beassigned uniquely.
The structure should be enhanced with the desired fields using appendtechnology.
For further information see the BAPI documentation on Customer Exits.

Description
Table with the component data

Description
The update structure for IT_COMPONENT

Value range
' '= Do not update field
'X' = Update field

Default
If the structure is left empty, then all the filled values (the valuesthat are not initial) are updated.

Description
Header data of the order.

Description
Service data of the order. This data must only be specified for serviceorders. The same index as for IT_HEADER is used.

Description
The update structure for IT_HEADER

Value range
' '= Do not update field
'X' = Update field

Default
If the structure is left empty, then all filled values (that is, valuesthat are not initial) are updated.

Description
The update structure for IT_HEADER

Value range
' '= Do no update field
'X' = Update field

Default
If the structure is left empty, then all filled values (that is, valuesthat are not initial) are updated.

Description
The methods table specifies which methods the BAPI executes. For thisthe following data is always required:


• REFNUMBER,,A reference number for a data table line,


• OBJECTTYPE,,An object type, which specifies which data table(s) is
referenced

• METHOD,,,,A method which specifies what should be done to the object


• OBJECTKEY,,A key as a reference to the corresponding higher-level object

Value range
The following values are allowed:
OBJECTTYPE


• HEADER,,,,Order header


• PARTNER,,,,Partner data


• OPERATION,,Operation data


• RELATION,,,,Relationships


• COMPONENT,,Components


• TEXT,,,,,,Long texts


• PRT,,,,,,Production resource/tool


• (empty),,,,,,General BAPI functions (Save)

METHOD,,,,

• CREATE,,,,Create objects


• CREATETONOTIF,,Create with reference to a notification


• CHANGE,,,,Change objects


• DELETE,,,,Delete objects


• RELEASE,,,,Release


• ATPCHECK,,,,Availability check


• CALCULATE,,,,Calculate


• SCHEDULE,,,,Schedule


• SAVE,,,,,,Save all data

OBJECTKEY,,,,

• 0-12,,,,Order number


• 13-16,,,,Operation number


• 17-20,,,,Suboperation number


• 13-24,,,,Notification number (only for method CREATETONOTIF)

INCLUDE BAPI_ALM_ORDER_MAINTAIN OBJECT DOKU ID TX

Description
Table of object list data

Description
Relationship of object list entry to operation

Description
Table containing the operation data

Description
The update structure for IT_OPERATION

Value range
' '= Do not update field
'X' = Update field

Default
If the structure is left empty, then all filled values (that is, valuesthat are not initial) are updated.

Description
Table for partner data. All entries with the same order number areprocessed and not just the entry which the method table indicates.

Description
Update table for PARTNER

Value range
' ' = Do not update field
'X' = Update field

Description
Input table for production resources/tools in BAPIs for maintenance andservice orders.
The assignment of production resources/tools to orders and operationsuses the method table.

Description
Update table for IT_PRT for changing production resources/tools.
The entry for changing a production resource/tool must be in the sameline as the related entry in IT_PRT.
Only the fields for which the change indicator is set are changed.Fields which have no change indicator (for example, item number) cannotbe changed.

Value range
' ' = Do not update field
'X' = Update field

Description
Table with the first component data of the refurbishment order, which isprocessed together with the header data.
If the table is empty, the refurbishment order cannot be created.
Component ORDERID specifies the order from table IT_HEADER for which therefurbishment component is to be created.

Description
The update structure for IT_REFORDER_ITEM.

Value range
' ' = Do not update field
'X' = Update field

Default
If this structure is left empty, all the filled values (those which arenot initial) are updated.

Description
This parameter is used if the first operation of the refurbishment orderis to be an external operation. It contains the same data as theIT_OPERATION table parameter. All other operations that are requiredmust be transferred with the IT_OPERATION parameter.
IF &[SWITCH]AD_ROTSUB_01_SFWS& = 'X'.
In a subcontracting scenario, the subcontracting flag can be set for theexternal operation using this parameter.
If there is supposed to be at least one external operation with thesubcontracting flag set, the material provision indicator of the maincomponent will be automatically set to Rework Material.
In a planned modification scenario (independent of subcontracting), thematerial provision indicator of the main component will be automaticallyset to Rework Material. The rework component with material provisionindicator set to Rework Material from Subcontr has to be passed manuallyinto the BAPI importing components' table.
ENDIF.

Description
Table with serial number object list data that is to be deleted from therefurbishment order while the refurbishment order is changed.
The order from which the serial numbers are to be deleted is specifiedby component ORDERID.

Description
Table with serial number object list data that is to be assigned to therefurbishment order while the refurbishment order is created or changed.
The order to which the serial numbers are to be assigned is specified bycomponent ORDERID.

Description
Table with the relationships.relationships.

Description
The update structure for IT_RELATION

Value range
' '= Do not update field
'X' = Update field

Default
If the structure is left empty, then all filled values (that is, valuesthat are not initial) are updated.

Description
Table with the allocation rules for the order settlement

Description
The update structure for IT_SRULE.

Value range
' '= Do not update field
'X' = Update field

Default
If you do not enter a value in the structure, the system updates all thefilled values (that is, the values that are not initial).

Description
Table of maintenance task lists or general task lists that are to beincluded.
For each task list, you can define:


• If operations that already exist in the operation are to be deleted


• If only operations for the task list or the general task list are to be
selected with a particular work center

• If the work centers in the task list or general task list are to be
replaced by another work center

Value range
DELETE_OLD_OPERATIONS:
WORKCENTER_SEL, PLANT_SEL: Only the operations that are assigned to thiswork center are selected.
WORKCENTER_USE, PLANT_USE: The work center in the operations of thegeneral task list is replaced with this work center.
USE_WORKCENTER_FROM_HEAD: If this indicator is set, the work center inthe operations from the general task list will be replaced with the workcenter from the order header. This indicator overrides values forWORKCENTER_USE and PLANT_USE.

Description
Table with header data for the texts.
The object must be specified here and the first and the last lines fromthe text table must be specified (inclusive respectively, count from1). This specifies a line segment in the text line table(IT_TEXT_LINES).

Description
Text lines in SAPscript format

Description
Transfer table for the user status.

Description
Return table by BAPI standard with all the notifications that aroseduring processing. If notifications of category E or A areamong them, then the data is not saved.