Application Development 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: 

Change DMBTR field in MIGO

Former Member
0 Kudos
2,422

Hi Gurus,

I'm trying to change the DMBTR field with the BADI MB_MIGO_BADI, method LINE_MODIFY, but i'm receiving the warning message saying that the field isn't available for update.

I've already seen some topics, but unfortunately without any luck.

Please, i really have to solve this.

Thanks and Regards.

Marco Costa

7 REPLIES 7

raymond_giuseppi
Active Contributor
1,079

For what kind of movement? Usually for output the value comes from stock valuation rules, check you Customizing. However, if you able to change the amount transferred to FI/CO, you would certainly generate discrepancies between FI and MM stock valuation, did you ask accountant functional?

Regards,
Raymond

0 Kudos
1,079

Raymond,

I need it for the movement 803, which the field DMBTR is not shown on screen.

Thanks,

Marco Costa.

1,079

I agree with Raymond. Such fields should not require ABAP to be populated. It seems to me that either configuration or process is incorrect here. Ask the MM/FI consultant to review this requirement and provide an explanation why this can't be accomplished without ABAP.

0 Kudos
1,079

Jelena,

I've already talked to the consultant, and she told me that the process isn't wrong.

I really need a Z development.

Thanks.

Marco Costa

1,079

Seems the 803 movement type (OMJJ) is specific to Brazil, so I wont be able to help much.

I can only suggest you and functional/consultant to look for Best Practives availbale for Brazil (104_BB_ConfigGuide_EN_BR, there are data to insert in table MIGO_CUST_FIELDS during Customizing)

Regards,
Raymond

Jelena_Perfiljeva
Active Contributor
1,079

Well, I'm not sure what other answers are expected... If the field is not available for update then you can't update it. Some fields are not available for input for a reason. Usually it's because by updating them you could cause some problems. Even if the process is not wrong per se it still may not be best practice.

I'd suggest for the functional consultant to ask in the MM forum for alternative solutions to whatever business requirement is here.

Former Member
1,079

i agree with Jelena here, DMBTR is a (local) currency (amount) field. does anybody remember Deutsche Mark? so, any updates out of controlled process are not allowed for many good reasons, auditability being the most important one.