Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

BAPI_MATERIAL_SAVEDATA Question....

Former Member
0 Likes
642

Hi,

I want to save more than one material unit conversion in BAPI. How can I add multiple unit conversion and additional value (like definition in other languages) when I Use BAPI_MATERIAL_SAVEDATA BAPI.

Thanks

1 ACCEPTED SOLUTION
Read only

Former Member
0 Likes
597

hi

good

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.

thanks

mrutyun^

5 REPLIES 5
Read only

Former Member
0 Likes
597

For example

EN - A4 Paper

TR - A4 Kagidi

Can I add multi value in BAPI?

Read only

0 Likes
597

My question lost in the unanswered questions

I need this information. Can I add multi value for unit conversition and translation?

Read only

Former Member
0 Likes
598

hi

good

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.

thanks

mrutyun^

Read only

0 Likes
597

I don't understand. Can anyone give me an example?

Read only

Former Member
0 Likes
597

This message was moderated.