Changing Activity Elements under the WBS in Project Systems

Question

I have added additional fields to the AFVU structure and need to update the fields.
I created a sub-screen using enhancement CNEX0008. This subscreen contains my added fields.  I wanted to use tcode CN22 to perform the updates.
When i record a BDC for Tcode CN22 to preform the update, I find the screen numbers change. I am trying to update the internal activity entries.  I can not see a pattern as to why this is happening so i thought i would look for a bapi to perform my updates. But i don't know how to use the bapi's to update my added fields. or which one to use.
Can anyone give me ideas as to which way to go - and how?
Please and Thanks,

Answer 1

Hi,
Use BAPI BAPI_INTERNALORDER_CREATE. To add custom field, you have to user the table EXTENSIONIN of this BAPI. But before that you will have to <b>extend AUFK using append structure CI_AUFK ( enhancement COOPA003 )</b>
This what SAP says about this table.
You can use this parameter to transfer user-defined fields from  order master records. However, no fields are supported that are updated in user-defined tables. Only the user-defined fields created within the framework of the SAP enhancement COOPA003 that are updated automatically in table AUFK are supported. This means you must use the table extension BAPI_TE_AUFK
The enhancement COOPA_01 includes the function module EXIT_SAPLRKIO_001, in which checks of the user-defined fields can be implemented.
The documentation to the structure BAPIPAREX that this parameter is based on contains more information about the use of this parameter.
<b>This is how you populate this table.</b> Check this code
DATA: gt_ci_aufk     LIKE bapi_te_aufk
                         OCCURS 0 WITH HEADER LINE.
DATA: gt_extensionin LIKE bapiparex
                         OCCURS 0 WITH HEADER LINE.
DATA: lst_ci_aufk LIKE ci_aufk.
** Five variables used to handle the structure length changes
DATA: lv_length    TYPE i,
      lv_length1   TYPE i,
      lv_length2   TYPE i,
      lv_length3   TYPE i,
      lv_length4   TYPE i.
FIELD-SYMBOLS <f> LIKE bapi_te_aufk.
DESCRIBE FIELD <f> LENGTH lv_length.
IF lv_length > 720.
  lv_length4 = lv_length - 720.
  lv_length3 = 240.
  lv_length2 = 240.
  lv_length1 = 240.
ELSEIF lv_length > 480 AND lv_length <= 720.
  lv_length3 = lv_length - 480.
  lv_length2 = 240.
  lv_length1 = 240.
ELSEIF lv_length > 240 AND lv_length <= 480.
  lv_length2 = lv_length - 240.
  lv_length1 = 240.
ELSEIF lv_length <= 240.
  lv_length1 = lv_length.
ENDIF.
* move custom field
lst_ci_aufk-field1 = 'field1 data'.
lst_ci_aufk-field2 = 'field2 data'.
lst_ci_aufk-field3 = 'field3 data'.
lst_ci_aufk-field4 = 'field4 data'.
* move order number
gt_ci_aufk-orderid = 'iternal order no'. "In create node keep this blank
* move custom fields
MOVE-CORRESPONDING lst_ci_aufk TO gt_ci_aufk.
* This is for the EXTENSIONIN (Custom fields structiure - CI_AUFK)
LOOP AT gt_ci_aufk.
  gt_extensionin-structure = 'BAPI_TE_AUFK'.
  IF lv_length1 > 0.
    MOVE gt_ci_aufk+0(lv_length1)   TO gt_extensionin-valuepart1.
  ENDIF.
  IF lv_length2 > 0.
    MOVE gt_ci_aufk+240(lv_length2) TO gt_extensionin-valuepart2.
  ENDIF.
  IF lv_length3 > 0.
    MOVE gt_ci_aufk+480(lv_length3) TO gt_extensionin-valuepart3.
  ENDIF.
  IF lv_length4 > 0.
    MOVE gt_ci_aufk+720(lv_length4) TO gt_extensionin-valuepart4.
  ENDIF.
  APPEND  gt_extensionin.
ENDLOOP.
Let me know if you have any question.
Regards,
RS