topic Re: BAPI_MATERIAL_SAVEDATA - Extending table in Application Development and Automation Discussions

BAPI_MATERIAL_SAVEDATA - Extending table

Former Member — Tue, 06 Jun 2006 10:37:49 GMT

Hi,

I have to populate EXTWEB using BAPI_MATERIAL_SAVEDATA.

This field is not present in the BAPI_MARA.

Any solutions?

Thanks

Salvatore

Message was edited by: Salvatore Volpe

Re: BAPI_MATERIAL_SAVEDATA - Extending table

Former Member — Tue, 06 Jun 2006 10:42:41 GMT

Hi,

Is it a custom field added to the mara table?

If yes, you have to use the EXTENSIONIN and EXTENSIONINX tables parameters of the bapi.

Read the following documentation for EXTENSIONIN :

<b>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>

Regards,

Ravi

Re: BAPI_MATERIAL_SAVEDATA - Extending table

Former Member — Tue, 06 Jun 2006 10:57:37 GMT

No, it's a standard field.

It's the same solution?

Thanks

Salvatore

Re: BAPI_MATERIAL_SAVEDATA - Extending table

Former Member — Tue, 06 Jun 2006 11:35:59 GMT

You may use, if it's possible, MATERIAL_MAINTAIN_DARK for the same purposes. I believe, that this function should apply your needs.

Re: BAPI_MATERIAL_SAVEDATA - Extending table

Former Member — Tue, 06 Jun 2006 11:39:39 GMT

What is the description of EXTWEB??

Re: BAPI_MATERIAL_SAVEDATA - Extending table

Former Member — Tue, 06 Jun 2006 11:55:27 GMT

EXTWG

CHAR 18

External material group

Re: BAPI_MATERIAL_SAVEDATA - Extending table

Former Member — Tue, 06 Jun 2006 12:00:39 GMT

Do you have some example to how use this function?

Can you use this FM instead of BAPI_MATERIAL_SAVEDATA to create and modify material?

Message was edited by: Salvatore Volpe

Re: BAPI_MATERIAL_SAVEDATA - Extending table

Former Member — Wed, 25 Jul 2007 13:55:19 GMT

Yes. Some standard fields have to be transferred with EXTENSIONIN. See note 211815.