Functionality
Application interface for updating task lists in the buffer table. Thisfunction module enables you to update the components of a single tasklist, including all alternatives. The function module can also be calledrepeatedly in order to update changes in buffer tables withoutcommitting them to the database. Important to note is that after anunsuccessful update attempt, the buffer tables are reset with the datafrom the database. Previously altered data in the buffer tables isoverwritten with the records from the database.
Supported task list types are:

• Equipment task lists


• Functional location task lists


• General task lists

In order to update a task list, enter the changed or new records intothe TABLES parameters. The tables with ending _DEL are for the recordswhich should be deleted, the tables with ending _INS create new recordsin the buffer table, whereas the _UPD tables are for changing thecorresponding records.
The import parameters define the task list to be changed, the date thechanges are to be made and the change number. The changeable objects ofthe task list are:

• Task list header - update only


• Operations - update and insert


• Production resource/tools- update, delete and insert


• Material components - update, delete and insert


• Operation relations - update, delete and insert


• Service packages - update, delete and insert


• Maintenance packages - insert and delete only

Each of the changeable objects provides an update flag table (ending_UPDX), which contains the detailed information on which data fields ofthe corresponding update table have to be changed. The field names inthe update flag tables are the same as in the update tables, an 'X' inthe update flag table indicates a change of the field's value. To mapthe records to each other, it is required to set the key values for eachrecord in the update flag table.
Additionally, long texts can be maintained for the following objects:

• Task list header


• Task list operations


• Task list production resource/tools

Example
CALL FUNCTION 'EAM_TASKLIST_CHANGE'
EXPORTING
IV_PLNTY = 'T' " Functional Location Task List
IV_TPLNR = 'FLOC'
IV_DATE = SY-DATUM
TABLES
IT_HEADER_DEL = LT_HEADER_DEL " Headers fordeletion
IT_HEADER_UPD = LT_HEADER_UPD " Headers forupdate
IT_HEADER_UPDX = LT_HEADER_UPDX " Header updateflag table
IT_OPERATIONS_INS = LT_OPERATIONS_INS " Operations tobe created
IT_OPERATIONS_DEL = LT_OPERATIONS_DEL " Operations fordeletion
IT_OPERATIONS_UPD = LT_OPERATIONS_UPD " Operations forupdate
IT_OPERATIONS_UPDX = LT_OPERATIONS_UPDX " Operationsupdate flag table
IT_COMPONENTS_INS = LT_COMPONENTS_INS " Components tobe created
IT_COMPONENTS_DEL = LT_COMPONENTS_DEL " Components fordeletion
IT_COMPONENTS_UPD = LT_COMPONENTS_UPD " Components forupdate
IT_COMPONENTS_UPDX = LT_COMPONENTS_UPDX " Componentsupdate flag table
IT_PRTS_INS = LT_PRTS_INS " Productionresource/tools to be created
IT_PRTS_DEL = LT_PRTS_DEL " Productionresource/tools for deletion
IT_PRTS_UPD = LT_PRTS_UPD " Productionresource/tools for update
IT_PRTS_UPDX = LT_PRTS_UPDX " PRTs updateflag table
IT_RELATIONS_INS = LT_RELATIONS_INS " Relations to be
created
IT_RELATIONS_DEL = LT_RELATIONS_DEL " Relations fordeletion
IT_RELATIONS_UPD = LT_RELATIONS_UPD " Relations forupdate
IT_RELATIONS_UPDX = LT_RELATIONS_UPDX " Relationsupdate flag table
IT_SPACKAGES_INS = LT_SPACKAGES_INS " Servicepackages to be created
IT_SPACKAGES_DEL = LT_SPACKAGES_DEL " Servicepackages for deletion
IT_SPACKAGES_UPD = LT_SPACKAGES_UPD " Servicepackages for update
IT_SPACKAGES_UPDX =LT_SPACKAGES_UPDX " Servicepackages update flag table
IT_MPACKAGES_INS = LT_MPACKAGES_INS " Maintenancepackages to be created
IT_MPACKAGES_DEL = LT_MPACKAGES_DEL " Maintenancepackages for deletion
IT_TEXT_INS = LT_TEXT_INS " Long textheaders to be created
IT_TEXT_LINES_INS = LT_TEXT_LINES_INS " Long text lines
to be created
IT_TEXT_DEL = LT_TEXT_DEL " Long textheader lines for deletion
IT_TEXT_UPD = LT_TEXT_UPD " Long textheaders for update
IT_TEXT_LINES_UPD = LT_TEXT_LINES_UPD " Long text lines
for update
ET_RETURN = LT_RETURN " BAPI returntable containing messages
.

Notes
To finalize the update and to write the data into the database, callfunction module EAM_TASKLIST_POST.
If an update fails due to inconsistent values, ALL buffer tables aredeleted and all unsaved data (no call of EAM_TASKLIST_POST) is lost.
Fields STLTY, STLNR, STLAL and STLKN of parameter IT_COMPONENTS_INS areoptional input parameters, representing keys of a non standard BOM item.Keys of a non standard BOM item should only be given for the case, whena certain existing non standard BOM item with a category other than "S"is to be used for a new component being created.

Description
This structure contains the full key of the top hierarchy task list(level 0). The top hierarchy task list has to be provided if a hierarchyelement is to be updated.

Description
Date on which the task list is edited or displayed. All objects, forexample header or operation, that are valid on this key date aredisplayed.

Default
The default value for the key date is the current date.

Description
Equipment ID to which task list is assigned to. This parameter shouldonly be set, if the task list type is Equipment Task List.

Description
This key field indicates the task list group. Each task list is assignedto a group, therefore this ID serves as a main identifier, besidesfunctional location number and equipment number. If a function callrequests a general task list, this field is mandatory. In case of arequest for equipment task lists or functional location task lists, thisfield may be initial.

Description
Determines the task list type of the task lists to be read.

Value range
'E' - Equipment task list
'T' - Functional location task list
'A' - General task list

Default
The task list type is required for all function module calls and istherefore not defaulted.

Description
Functional location ID to which task lists are assigned to. Parametershould only be set if task list type is a functional location task list.

Description
Table with all the messages sent by the API.

Description
Dialogue table for task list header containing header records to bedeleted. It is only possible to delete selected alternatives of a tasklist, therefore field PLNAL is required in the header records.

Description
Dialogue table for task list header containing header records forupdate. It is only possible to update selected alternatives of a tasklist, therefore field PLNAL is required in the header records. Forunique identification of the record, the following fields have to be set:


• PLNNR


• PLNTY


• PLNAL

Description
Update flag table for task list headers. If a field of tableIT_HEADER_UPD should be used for update, the corresponding flag has tobe set in this structure. The records are mapped to each other by usingthe unique key of the update table, therefore entries are required for:


• PLNNR


• PLNTY


• PLNAL

Description
Deletion table for task list maintenance packages. All fields ofstructure EAM_S_TL_MPACK are mandatory.


• PLNTY,,Task List Type


• PLNNR,,Key for Task List Group


• PLNAL,,Group Counter


• AOBAR,,Type of relationship


• PAKET,,Maintenance package number


• VORNR,,Operation/Activity Number


• STRAT,,Maintenance strategy

Description
Insert table for task list maintenance packages. All fields of structureEAM_S_TL_MPACK are mandatory.


• PLNTY,,Task List Type


• PLNNR,,Key for Task List Group


• PLNAL,,Group Counter


• AOBAR,,Type of relationship


• PAKET,,Maintenance package number


• VORNR,,Operation/Activity Number


• STRAT,,Maintenance strategy

Description
Table containing operations to be deleted. The entered operations willbe deleted from the buffer tables. For unique identification of therecord, it is required to set fields:


• PLNTY


• PLNNR


• PLNAL


• VORNR


• UVORN (only required for suboperations)

Description
Table containing task list operations to be inserted. Theoperations will be created in the buffer tables with the external keyVORNR.

Description
Table containing operations to be updated. In case of theoperations, it is possible to update the external key VORNR/UVORN. Inthis case the internal key PLNKN has to be transferred unchanged. Theoperations are identified with the following unique keys:


• PLNTY


• PLNNR


• PLNAL


• PLNKN (only required if VORNR or UVORN changed)


• VORNR


• UVORN (only required for sub operations)

Description
Update flag table for task list operations. If a field of tableIT_OPERATIONS_UPD should be considered for update, the correspondingflag has to be set in this structure. The records are mapped to eachother by using the unique key of the update table, therefore entries arerequired for:


• PLNNR


• PLNTY


• PLNAL


• PLNKN (only required if VORNR changed)


• VORNR_OLD (containing only unchanged VORNR)


• UVORN_OLD (containing only unchanged UVRORN)

Description
Table with production resource/tools for insert in buffer table.

Description
Deletion table for relations. To Delete entry, all key fields have to beset:
PLNTY
PLNNR
PLNAL
AOBAR
VORN1
VORN2

Description
Insert table for operation relationships. Mandatory fields of structureEAM_S_TL_REL are:


• PLNTY,,Task List Type


• PLNNR,,Key for Task List Group


• PLNAL,,Group Counter


• AOBAR,,Type of relationship


• VORN1,,Operation number to which relationship is applied to


• VORN2,,Operation number from which relationship originates

Description
Update table for operation relations. Mandatory fields of structureEAM_S_TL_REL are:
PLNTY,,Task List Type
PLNNR,,Key for Task List Group
PLNAL,,Group Counter
AOBAR,,Type of relationship
VORN1,,Operation number to which relation is applied to
VORN2,,Operation number from which relation originates

Description
Contains flags for update. To identify corresponding line of updatetable, following key fields have to be maintained:
PLNTY,,Task List Type
PLNNR,,Key for Task List Group
PLNAL,,Group Counter
AOBAR,,Type of relationship
VORN1,,Operation number to which relation is applied to
VORN2,,Operation number from which relation originates

Description
Deletion table for MM service package contract limits. Mandatory fieldsof structure EAM_S_TL_SPACK_CONTR_LIMIT are:


• PLNTY ,,,,Task List Type


• PLNNR ,,,,Key for Task List Group


• PLNAL ,,,,,,Group Counter


• VORNR ,,,,,,Operation/Activity Number


• CONTRACT,,,,,,,,Purchasing Document Number


• CONTRACT_ITEM,,,,,,Item Number of Purchasing Document

Description
Insert table for MM service package contract limits. Mandatory fields ofstructure EAM_S_TL_SPACK_CONTR_LIMIT are:


• PLNTY ,,,,Task List Type


• PLNNR ,,,,Key for Task List Group


• PLNAL ,,,,,,Group Counter


• VORNR ,,,,,,Operation/Activity Number


• CONTRACT,,,,,,,,Purchasing Document Number


• CONTRACT_ITEM,,,,,,Item Number of Purchasing Document

Description
Update table for MM service package contract limits. Mandatory fields ofstructure EAM_S_TL_SPACK_CONTR_LIMIT are:


• PLNTY ,,,,Task List Type


• PLNNR ,,,,Key for Task List Group


• PLNAL ,,,,,,Group Counter


• VORNR ,,,,,,Operation/Activity Number


• CONTRACT,,,,,,,,Purchasing Document Number


• CONTRACT_ITEM,,,,,,Item Number of Purchasing Document

Description
Table containing update flags for MM service package contract limits.Mandatory fields used for identification of the respective line in tableIT_SPACK_CONTR_LIMITS_UPD are:


• PLNTY ,,,,,,Task List Type


• PLNNR ,,,,,,Key for Task List Group


• PLNAL ,,,,,,Group Counter


• VORNR ,,,,,,Operation/Activity Number


• CONTRACT,,,,,,Purchasing Document Number


• CONTRACT_ITEM,,,,Item Number of Purchasing Document

Description
Deletion table for MM service package lines. Mandatory fields ofstructure EAM_S_TL_SPACK are:
PLNTY,,Task List Type
PLNNR,,Key for Task List Group
PLNAL,,Group Counter
VORNR,,Operation/Activity Number
SRV_LINE Line Number
OUTLINE,,Outline Number

Description
Deletion table for MM service package limits. Mandatory fields ofstructure EAM_S_TL_SPACK_LIMITS are:


• PLNTY ,,,,Task List Type


• PLNNR ,,,,Key for Task List Group


• PLNAL ,,,,,,Group Counter


• VORNR ,,,,,,Operation/Activity Number

Insert table for MM service package limits. Mandatory fields ofstructure EAM_S_TL_SPACK_LIMIT are:

• PLNTY ,,,,Task List Type


• PLNNR ,,,,Key for Task List Group


• PLNAL ,,,,,,Group Counter


• VORNR ,,,,,,Operation/Activity Number


• OVERALL_LIMIT,,,,,,Overall Limit

Description
Update table for MM service package limits. Mandatory fields ofstructure EAM_S_TL_SPACK_LIMIT are:


• PLNTY ,,,,Task List Type


• PLNNR ,,,,Key for Task List Group


• PLNAL ,,,,,,Group Counter


• VORNR ,,,,,,Operation/Activity Number

Description
Table containing update flags for MM service package limits. Mandatoryfields used for identification of the respective line in tableIT_SPACK_LIMITS_UPD are:


• PLNTY Task List Type


• PLNNR Key for Task List Group


• PLNAL Group Counter


• VORNR Operation/Activity Number

Description
Insert table for MM service package lines. Mandatory fields of structureEAM_S_TL_SPACK are:


• PLNTY Task List Type


• PLNNR Key for Task List Group


• PLNAL Group Counter


• VORNR Operation/Activity Number


• SRV_LINE Line Number


• SHORT_TEXT Short text


• QUANTITY Quantity


• UOM Unit of measure

Hints:
OUTLINE field is only required if different from default outline 1.

Description
Update table for MM service package lines. Mandatory fields of structureEAM_S_TL_SPACK are:


• PLNTY,,,,Task List Type


• PLNNR,,,,Key for Task List Group


• PLNAL,,,,Group Counter


• VORNR,,,,Operation/Activity Number


• SRV_LINE ,,Line Number


• OUTLINE,,,,Outline Number


• SHORT_TEXT,,Short text


• QUANTITY,,,,Quantity


• UOM,,,,,,Unit of measure

Description
Table containing update flags for MM service package lines. Mandatoryfields used for identification of the respective line in tableIT_SPACK_LINES_UPD are:
PLNTY,,Task List Type
PLNNR,,Key for Task List Group
PLNAL,,Group Counter
VORNR,,Operation/Activity Number
SRV_LINE Line Number
OUTLINE,,Outline Number

Description
Deletion table for MM service package outlines. Mandatory fields ofstructure EAM_S_TL_SPACK_OUTLINE are:


• PLNTY ,,,,Task List Type


• PLNNR ,,,,Key for Task List Group


• PLNAL ,,,,,,Group Counter


• VORNR ,,,,,,Operation/Activity Number


• OUTLINE_LEVEL_NAME,,,,Outline Level


• PARENT_OUTLINE,,,,Parent's Outline Number

Description
Insert table for MM service package outlines. Mandatory fields ofstructure EAM_S_TL_SPACK_OUTLINE are:


• PLNTY ,,,,Task List Type


• PLNNR ,,,,Key for Task List Group


• PLNAL ,,,,,,Group Counter


• VORNR ,,,,,,Operation/Activity Number


• SHORT_TEXT ,,,,Short text


• OUTLINE_LEVEL_NAME,, Outline Level


• PARENT_OUTLINE,,,,Parent's Outline Number ( if not set 1 is used )

Description
Insert table for MM service package outlines. Mandatory fields ofstructure EAM_S_TL_SPACK_OUTLINE are:


• PLNTY ,,,,Task List Type


• PLNNR ,,,,Key for Task List Group


• PLNAL ,,,,,,Group Counter


• VORNR ,,,,,,Operation/Activity Number


• SHORT_TEXT ,,,,Short text


• OUTLINE_LEVEL_NAME,,,,Outline Level


• PARENT_OUTLINE,,,,Parent's Outline Number

Description
Table containing update flags for MM service package lines. Mandatoryfields used for identification of the respective line in tableIT_SPACK_OUTLINES_UPD are:


• PLNTY ,,,,,,Task List Type


• PLNNR ,,,,,,Key for Task List Group


• PLNAL ,,,,,,Group Counter


• VORNR ,,,,,,Operation/Activity Number


• OUTLINE,,,,,,Outline Number


• PARENT_OUTLINE,,Parent's Outline Number

Description
Import table containing header data for long texts to be deleted for asubobject of a task list alternative. The subobject key where the newlong text is supposed to be deleted must be specified in each tableline. Prerequisite for changing the long text assigned to a task listsubobject is that the short text and the language key of this subobjectare marked for update. The reason is that the first line of long textoverwrites the short text of the corresponding task list subobject.
Mandatory fields of structure IT_TEXT_DEL are:
·,,PLNTY Task list type
·,,PLNNR Key for task list group
·,,PLNAL Group counter
Optional fields of parameter IT_TEXT_DEL are:
·,,VORNR ,,External identifier for operation/activity (mandatory foroperations, PRT and service packages)
·,,PZLFH ,,External item counter for production resources/tools(mandatory for PRT)
Optional fields for service packages:
·,,OUTLINE External identifier for outline number
·,,SERVICE_LINE External identifier for service line assigned to aboveoutline number
·,,TEXT_ID If equals to 'LTEXT', this refers to an 'outline longtext' ora 'line text' of a service line
If equals to 'LLTXT', this refers to a'service text' of a service line

Description
Import table containing header data for long texts to be created for asubobject of a task list alternative. The subobject key where the newlong text is supposed to be created must be specified in each tableline. In case a subobject should not have any long text the table mustremain empty. Prerequisite for changing the long text assigned to a tasklist subobject is that the short text and the language key of thissubobject are marked for update. The reason is that the first line oflong text overwrites the short text of the corresponding task listsubobject.
Mandatory fields of structure IT_TEXT_INS are:
·,,PLNTY Task list type, mandatory if this was specified in parameterIS_HEADER
·,,PLNNR Key for task list group, mandatory if this was specified inparameter IS_HEADER
·,,PLNAL Group counter, mandatory if this was specified in parameterIS_HEADER
·,,TEXTSTART First table line within API parameter IT_TEXT_LINES_INS
that refers to current line ofIT_TEXT_INS
·,,TEXTEND Last table line within API parameter IT_TEXT_LINES_INS
Optional fields of parameter IT_TEXT_INS are:
·,,LANGU ,,Language in which the long text is to be created. If leftempty the logon language is used.
·,,VORNR ,,External identifier for operation/activity (mandatory foroperations, PRT and service packages)
·,,PZLFH ,,External item counter for production resources/tools
Optional fields for service packages:
·,,OUTLINE External identifier for outline number
·,,SERVICE_LINE External identifier for service line assigned to aboveoutline number
·,,TEXT_ID If equals to 'LTEXT', this refers to an 'outline longtext' ora 'line text' of a service line
If equals to 'LLTXT', this refers to a'service text' of a service line

Description
Import table containing all text lines for long texts to be created forall related subobjects of a task list alternative. The subobject keywhere the new long text is supposed to be created must be specified inAPI parameter IT_TEXT_INS. The first line of this parameterIT_TEXT_LINES_INS will overwrite the short text of the correspondingtask list subobject.
Mandatory fields of structure IT_TEXT_LINES_INS are:
·,,TDFORMAT Style element name (paragraph, character string) inSAPscript format
·,,TDLINE SAPscript text line with a length of 132 characters
The line index of API Parameter IT_TEXT_LINES_INS refers to followingthree fields of API parameter IT_TEXT_INS:
·,,TEXTSTART First table line within API parameter IT_TEXT_LINES_INS
that refers to a single (header) line ofIT_TEXT_INS
·,,TEXTEND Last table line within API parameter IT_TEXT_LINES_INS
that refers to the same single (header)line of IT_TEXT_INS
·,,LANGU ,,Language in which the long text is to be created. If leftempty the logon language is used.

Description
Import table containing all text lines for long texts to be updated forall related subobjects of a task list alternative. The subobject keywhere the new long text is supposed to be updated must be specified inAPI parameter IT_TEXT_UPD. The first line of this parameterIT_TEXT_LINES_UPD will overwrite the short text of the correspondingtask list subobject. The text lines of parameter IT_TEX_LINES_UPD willcompletely replace any existing text lines.
Mandatory fields of structure IT_TEXT_LINES_UPD are:
·,,TDFORMAT Style element name (paragraph, character string) inSAPscript format
·,,TDLINE SAPscript text line with a length of 132 characters
The line index of API Parameter IT_TEXT_LINES_UPD refers to followingthree fields of API parameter IT_TEXT_UPD:
·,,TEXTSTART First table line within API parameter IT_TEXT_LINES_UPD
that refers to a single (header) line ofIT_TEXT_UPD
·,,TEXTEND Last table line within API parameter IT_TEXT_LINES_UPD
that refers to the same single (header)line of IT_TEXT_UPD

Description
Import table containing header data for long texts to be updated for asubobject of a task list alternative. The subobject key where the newlong text is supposed to be updated must be specified in each tableline. If the long text of a subobject should remain unchanged<(>,<)> thetable must remain empty. Prerequisite for changing the long textassigned to a task list subobject is that the short text and thelanguage key of this subobject are marked for update. The reason is thatthe first line of long text overwrites the short text of thecorresponding task list subobject.
Mandatory fields of structure IT_TEXT_UPD are:
·,,PLNTY Task list type, mandatory if this was specified in parameterIS_HEADER
·,,PLNNR Key for task list group, mandatory if this was specified inparameter IS_HEADER
·,,PLNAL Group counter, mandatory if this was specified in parameterIS_HEADER
·,,TEXTSTART First table line within API parameter IT_TEXT_LINES_UPD
that refers to current line ofIT_TEXT_UPD
·,,TEXTEND Last table line within API parameter IT_TEXT_LINES_UPD
Optional fields of parameter IT_TEXT_UPD are:
·,,LANGU ,,Language in which the long text is to be created. If leftempty the logon language is used.
·,,VORNR ,,External identifier for operation/activity (mandatory foroperations, PRT and service packages)
·,,PZLFH ,,External item counter for production resources/tools
Optional fields for service packages:
·,,OUTLINE External identifier for outline number
·,,SERVICE_LINE External identifier for service line assigned to aboveoutline number
·,,TEXT_ID If equals to 'LTEXT', this refers to an 'outline long text'or a 'line text' of a service line
If equals to 'LLTXT', this refers to a'service text' of a service line