Change append fields in customer master via BAPI?

[jrgkraus]

I need to update append fields of KNA1 and KNVV (via IDOC). Since we need change pointers for those changes, I should have change documents for these changes.

BAPI_CUSTOMER_CHANGEFROMDATA1 doesn't seem to have a mechanism for updating append fields. Is there a possibility to update those fields with creation of change documents?

[jrgkraus]

I need to update append fields of KNA1 and KNVV (via IDOC). Since we need change pointers for those changes, I should have change documents for these changes.

BAPI_CUSTOMER_CHANGEFROMDATA1 doesn't seem to have a mechanism for updating append fields. Is there a possibility to update those fields with creation of change documents?

[Nawanandana]

what do you mean by " append fields"? Do you mean that you need add custom fields or what?

[chaouki_akir]

A minima, change document flag, for the data elements of the appended fields, should be checked.

This BAPI is calling a "WRITE Document" function. Then Change pointers should be inserted (for each field with a DTEL having "change document" checked).

  OBJECTID = XKUNNR.                                        "mi/45B
  CALL FUNCTION 'DEBI_WRITE_DOCUMENT           ' IN UPDATE TASK
       EXPORTING
*           objectid                = xkunnr            "mi/45B
            OBJECTID                = OBJECTID              "mi/45B
            TCODE                   = CODE
            UTIME                   = UTIME
            UDATE                   = UDATE
            USERNAME                = USERNAME
            PLANNED_CHANGE_NUMBER   = PLANNED_CHANGE_NUMBER
            OBJECT_CHANGE_INDICATOR = CDOC_UPD_OBJECT
            PLANNED_OR_REAL_CHANGES = CDOC_PLANNED_OR_REAL
            O_YKNA1                 = YKNA1
            N_KNA1                  = KNA1
            UPD_KNA1                = VKZ-KNA1
....

[ThangaPrakash]

Hi Jörg Krause

Did you try with SE18 Enhancement spot 'CUSTOMER_ADD_DATA_BI' (Additional Data at Customers (Batch Input and ALE)), try with below two methods.

FILL_BI_TABLE_WITH_OWN_SEGMENT - Fill Batch Input Table from Own Segment (ALE Inbound Proc.)

PASS_NON_STANDARD_SEGMENT - Pass On Customer-Defined Segments (ALE Inbound Processing)

[jrgkraus]

Yes, we have an append structure on KNA1 and KNVV with own fields in it. Actually, we are doing a db update to maintain them because I did not find a way to maintain them via BAPI

[srikanthnalluri]

@Jörg Krause Not sure this is wise way - I would create a new function module and keep all the BAPI - BAPI_CUSTOMER_CHANGEFROMDATA1 import, export and tables along with custom fields in the created FM. Then in the FM i would update custom fields if the BAPI call is success.

[jrgkraus]

In this case I will not have change documents as well....

[srikanthnalluri]

You can maintain change log as well, please check below link which explains how to maintain change log for custom fields.

https://wiki.scn.sap.com/wiki/display/ABAP/Maintaining+Change+Log+for+Database+Tables?original_fqdn=...

[jrgkraus]

I need an application log (cdhdr, cdpos), not a database log.

[chaouki_akir]

Are, the data elements of your append fields, have "change document" checked ?

[jrgkraus]

Yes, this flag is set. But since I do a DB update, there is no effect.