Community
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
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Read only

Extended Material Master

Former Member

‎2006 Mar 28 9:36 AM

0 Likes
671

Hi, I've extended the material master for MARA with three new fields on the basic data1 tab. In MM01/MM02 I populate them save it down all works fine.

I've now in development to automatically create material masters in the background using BAPI_MATERIAL_SAVEREPLICA. I appended BAPI_TE_E1MARA/X with the new fields and I populate EXTENSIONIN/X with the values as required. I've also done this with BAPI_TE_E1MARC/X for the batch managed flag that isn't in the BAPI.

I kick off the program the material is created without the new MARA fields but with the MARC fields. I've debugged and will carry on doing so until I nail this but there seems to be discrepancies between the structures wmara(populated)/mara(ultimately not)/ymara(populated)/*mara(not) around the FM MATERIAL_UPDATE_ALL. Is there a bit of config I'm missing as everthing else seems to be in place. I'm working in Enterprise 4.7.

Thanks in advance. Mark

Hi, I've extended the material master for MARA with three new fields on the basic data1 tab. In MM01/MM02 I populate them save it down all works fine.

I've now in development to automatically create material masters in the background using BAPI_MATERIAL_SAVEREPLICA. I appended BAPI_TE_E1MARA/X with the new fields and I populate EXTENSIONIN/X with the values as required. I've also done this with BAPI_TE_E1MARC/X for the batch managed flag that isn't in the BAPI.

I kick off the program the material is created without the new MARA fields but with the MARC fields. I've debugged and will carry on doing so until I nail this but there seems to be discrepancies between the structures wmara(populated)/mara(ultimately not)/ymara(populated)/*mara(not) around the FM MATERIAL_UPDATE_ALL. Is there a bit of config I'm missing as everthing else seems to be in place. I'm working in Enterprise 4.7.

Thanks in advance. Mark

Reply
2 REPLIES 2
Read only

Former Member

‎2006 Mar 28 9:46 AM

0 Likes
550

It was config. Needed to assign field selection groups.

Read only

Former Member
In response to Former Member

‎2006 May 05 2:20 PM

0 Likes
550

Hello Mark,

What do you mean by " It was config. Needed to assign field selection groups. " I've the same problem and I don't find the solution

Thanks

Fabrice

PS. are you working in France (I'd met a Mark Walker in France, working for a big blue company, was it you ?)