Ansicht
Dokumentation

/PICM/FM_ISSUE_CR_UPDATE_API - Update API for Issue

/PICM/FM_ISSUE_CR_UPDATE_API - Update API for Issue

Fill RESBD Structure from EBP Component Structure   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.
SAP E-Book

Functionality

You use this function module to:

  • Update issues and change requests of master projects
The function module allows you to modify issue or change request details, alternatives, impact, and solutions. You can add new business partners, object references, and attachments. However, you cannot modify existing entries.
  • Update activities of issues and change requests in a flat or hierarchical format, including the addition of new activities
The function module allows you to modify activity overviews. You can add new business partners, object references, and attachments. However, you cannot modify existing entries.

When you use this function module, you must note the following:

  • In IS_ISSUE_ROOT_DATA, issue ID is a mandatory entry.
  • Use SORT_NUMBER to define the sequence for fields related to dates, description, description text, partners, object reference, and attachments.
  • You can modify the Datesand Description fields.
  • You can add new object references, partners, and attachments; you cannot, however, modify existing entries in these fields.
  • Entries in the IT_ISSUE_CHANGE_FIELD table are mandatory. This table is used to define the field names that need to be modified. In this table, use SORT_NUMBER1 to map the relevant fields to their corresponding records.
Example
To edit TEXT and LONG_TEXT_FORMATTED for one description and only LONG_TEXT_FORMATTED for another description, you must add LONG_TEXT_FORMATTED two times with different sort numbers and these sort numbers must belong to the description data.
  • The activity ID is a mandatory entry if you want to modify activities.
  • The application, activity type (or activity template), and category are mandatory entries if you want to add a new activity as a flat structure.
  • If you want to add a new activity as the child of another activity, the first record must be the parent record with a mandatory entry for activity ID and SORT_NUMBER1 as, for example, 0001. In this case, the second record must have SORT_NUMBER1 as 0002and SORT_NUMBER2 as 0001.
  • The use of the sort number feature, in activities, has the following rules:
  • In Activity List, use SORT_NUMBER1 to provide the activity sequence and SORT_NUMBER2 to set the parent activity, if required

  • Use SORT_NUMBER1 in a sequence, for fields related to dates, description, description text, partners, object reference, and attachments

  • SORT_NUMBER2 must contain the corresponding SORT_NUMBER1 of the activity to which it belongs

  • The entries for IT_ACT_CHANGE_FIELDS are mandatory if you want to add or modify activities
  • Use SORT_NUMBER1 to define the record sequence and SORT_NUMBER2 to specify the activity to which it belongs
  • If EV_RESULT is X it reflects that the records have been successfully updated; if not, ET_MESSAGES displays the error details.

Example

Notes

Further information





Parameters

ET_MESSAGES
EV_RESULT
IS_ISSUE_ROOT_DATA
IT_ACT_ATT
IT_ACT_CHANGE_FIELDS
IT_ACT_DATES
IT_ACT_DESC
IT_ACT_DESC_TXT
IT_ACT_OBJ_REF
IT_ACT_PARTY
IT_ACT_ROOT
IT_DATES
IT_DESC
IT_DESC_TXT
IT_ISSUE_ATT
IT_ISSUE_CHANGE_FIELD
IT_OBJ_REF
IT_PARTNERS

Exceptions

Function Group

M/SAPLISSUE_API

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   ABAP Short Reference  
This documentation is copyright by SAP AG.

Length: 5906 Date: 20240419 Time: 024908     sap01-206 ( 110 ms )