topic Re: BAPI_EQUI_CHANGE, customer fields in Application Development and Automation Discussions

BAPI_EQUI_CHANGE, customer fields

Former Member — Thu, 26 Mar 2009 10:43:33 GMT

Hello,

we are using the screen exit and the EQUI Include CI_EQUI in order to show our customer fields in the equipment. I would like to change the equipment with BAPI_EQUI_CHANGE but I can not find our custumer fields in the BAPI. Is there any way to change the customer fields with this BAPI?

Any help is very much appreciated.

regards

stefan

Re: BAPI_EQUI_CHANGE, customer fields

Former Member — Thu, 26 Mar 2009 10:45:52 GMT

use fm

EQUIPMENT_UPDATE

Re: BAPI_EQUI_CHANGE, customer fields

Former Member — Thu, 26 Mar 2009 10:47:38 GMT

i dont think this is possible since input sturctures to bapi do not have these fileds enabled.

Re: BAPI_EQUI_CHANGE, customer fields

Former Member — Thu, 26 Mar 2009 10:50:16 GMT

Hi use below FM:


CALL FUNCTION 'EQUIPMENT_UPDATE'
  EXPORTING
    *heqkt                =
    *hequi                =
    *hequz                =
    *hiloa                =
*   *HEQBS                =
*   *HFLEET               =
*   HAKTYP                = ' '
    heqkt                 =
    hequi                 =                        "Customer include fileds will be available in header structure.
    hequz                 =
    hiloa                 =
*   HEQBS                 =
*   HFLEET                =
    hx_xreftp             =
*   HX_XZEITS             = ' '
*   INHB_COUNTER          = 0
*   INHB_DELETE           = ' '
*   DATE                  = SY-DATUM
*   TIME                  = SY-UZEIT
*   HX_XAEBKZ             = ' '
*   HX_XWFKNZ             =
*   ADD_REMAINDER         = ' '
*   IND_DIRECT_POST       = ' '
* IMPORTING
*   E_ILOAN               =

Re: BAPI_EQUI_CHANGE, customer fields

Former Member — Thu, 26 Mar 2009 11:48:03 GMT

Kishan and Santosh,

thanks for your help.

Stefan

Re: BAPI_EQUI_CHANGE, customer fields

RobynCouch — Fri, 06 May 2016 03:29:33 GMT

Just in case anybody else finds this thread.

SAP have addressed the issue. See note http://service.sap.com/sap/support/notes/2146575