BAPI_MATERIAL_SAVEDATA with custom field

Former Member — Mon, 04 Jan 2010 23:29:28 GMT

Colleagues,

We have added custom fields to MARA and MARC, is it possible to update them with this bapi? We are on an ECC 6.0 system and would prefer not to do a BDC/Call Transaction.

Thank you.

Re: BAPI_MATERIAL_SAVEDATA with custom field

Former Member — Tue, 05 Jan 2010 03:24:34 GMT

Hi Ted ,

We have added custom fields to MARA and MARC, is it possible to update them with this bapi?

Yes , it is possible to update it . You should find the bapi and you need to check that parameters are based on MARA and MARC. So , your field will be included in the parameters .Hence, you can update it with other fields.

Hope this helps you.

Re: BAPI_MATERIAL_SAVEDATA with custom field

Former Member — Tue, 05 Jan 2010 03:26:28 GMT

chk this thread..may be useful.

Re: BAPI_MATERIAL_SAVEDATA with custom field

Former Member — Tue, 05 Jan 2010 06:39:29 GMT

Hi,

use extensionin and extensioninx table in BAPI(check the documentation of BAPI).

wa_extensionin-STRUCTURE = 'BAPI_TE_<NAME>'.

wa_extension-VALUEPART1 = wa_ext.

wa_ext has the 'BAPI_TE_<NAME> structure.

Besides the table fields already defined, customer-defined table fields can also be supplied with data. Since these fields are created by the customer, they are known only during the runtime and must therefore be determined dynamically.

The structures BAPI_TE_<NAME> (<NAME> = MARA, MARC, MARD, MBEW, MLGN, MLGT, MVKE) and the relevant checkbox structures BAPI_TE_<NAME> (<NAME> = MARAX, etc.) must first be extended by the customer to include the fields required. The standard structures contain only the corresponding key fields. When including new fields in these structures, make sure that the field has the same name as the field in the database table. In addition, the fields in the structures BAPI_TE_<NAME> may only be of the type CHARACTER. The data element BAPIUPDATE must be used for the fields in the checkbox structure (except for key fields).

The two parameters EXTENSIONIN and EXTENSIONINX are used to transfer the data to the method. The field STRUCTURE contains the name of the structure (for example, BAPI_TE_MARA or BAPI_TE_MARAX) used to identify the work area (for example, WA_BAPI_TE_MARA or WA_BAPI_TE_MARAX) to which the data is transferred. The remaining fields for the parameter EXTENSIONIN or EXTENSIONINX contain the data for the key fields (for example, the material number) and the data for the customer-defined fields. The number of characters reserved in the two parameters for the content of a customer-defined field must be the same as the number of characters for the corresponding work area field. If the number of characters required is smaller, the remaining characters in the two parameters must be filled with blanks. Only then may the content of another field be transferred. Here too, remember that the data is written to the database only if the corresponding indicator has been set in the work area.

Regards,

Manesh.R

topic BAPI_MATERIAL_SAVEDATA with custom field in Application Development and Automation Discussions

BAPI_MATERIAL_SAVEDATA with custom field

Re: BAPI_MATERIAL_SAVEDATA with custom field

Re: BAPI_MATERIAL_SAVEDATA with custom field

Re: BAPI_MATERIAL_SAVEDATA with custom field