BAPI_MATERIAL_SAVEDATA to update mara append fields

[Former Member]

Hi All ,

i want to use the BAPI_MATERIAL_SAVEDATA to update the Z-fields of tables MARA and MARM, but I don't know how to use the tables EXTENSIONIN and EXTENSIONINX.

If anyone can give me a sample.

thanks

[former_member181962]

Hi Fabrice ,

This is what the FM documenytation says:

<i><b>Reference Structure for BAPI Parameters EXTENSIONIN/EXTENSIONINX

Description

You use this structure to transfer the material's customer-defined

fields. For information on transferring these fields, see the function

module documentation.

Note

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. </b></i>

[former_member188685]

Hi,

check thsi documentation on extension.

Reference Structure for BAPI Parameters EXTENSIONIN/EXTENSIO

Description

You use this structure to transfer the material's customer-defined fields. For information on transferring these fields, see the function module documentation.

Note

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

vijay

[Former Member]

Hello

Thanks, but I've already read the documentation, but I don't understand what they mean.

Do you have an abap sample ?

Thanks for your answers

Fabrice

[Former Member]

see the sample code I had posted long back.

I had posted it on wiki too

http://wiki.sdn.sap.com/wiki/pages/viewpage.action?pageId=71368708&decorator=printable

[Joerg_S]

both links lead to a "dead end"