Customer Master using Appended structure KNA1

[Former Member]

Hi

We have to update few ZZ description fields in ZAKNA1, which are not part of user interface in XD01/02/03. The available options are such as LSMW, Batch input require code addition through user exit ZXF04U01/ EXIT_SAPMF02D_001.

I would like to use BAPI as we have a plan to use web services. Any idea how to extend the BAPI's such as BAPI_CUSTOMER_CHANGEFROMDATA1 or BAPI_CUSTOMER_CREATEFROMDATA1 using best practice? I donu2019t find any extension structures like other BAPIu2019s have. Without ExtensionIn and ExtensionOut parameters, a BAPI can not be enhanced correct?

The version we are using is ECC 5.0. Any ideas with customer master BAPI will be greatly appreciated.

Bala

[Former Member]

Hi

We have to update few ZZ description fields in ZAKNA1, which are not part of user interface in XD01/02/03. The available options are such as LSMW, Batch input require code addition through user exit ZXF04U01/ EXIT_SAPMF02D_001.

I would like to use BAPI as we have a plan to use web services. Any idea how to extend the BAPI's such as BAPI_CUSTOMER_CHANGEFROMDATA1 or BAPI_CUSTOMER_CREATEFROMDATA1 using best practice? I donu2019t find any extension structures like other BAPIu2019s have. Without ExtensionIn and ExtensionOut parameters, a BAPI can not be enhanced correct?

The version we are using is ECC 5.0. Any ideas with customer master BAPI will be greatly appreciated.

Bala

[former_member194669]

You cannot able use said bapi's in your post. they are all ONLINE bapis. You need to try with fm SD_CUSTOMER_MAINTAIN_ALL. ( I think if you extend your KNAI the same structure will be available in function module also)

a®

[Former Member]

Thanks. But SD_CUSTOMER_MAINTAIN_ALL is not a RFC enabled FM as we would like to use as webservice too?

Bala

[Former Member]

Please create a Z_ RFC, with the same interface as the BAPI, then call BAPI in side the RFC.

Cheers,