Error Custom Fields MB_MIGO_BADI

[Former Member]

Hi all,

I am implementing MB_MIGO_BADI and calling a screen with an additional fields not standard to migo.

In the method LINE_MODIFY have put:

....

MOVE: ls_extdata_new-zzfield TO cs_goitem-zzfield.

....

In the execution on having modified the field it jumps the following message MIGO049; "BAdI: is not allowed to modify the field content of zzfield".

I have added the field zzfield in the table mseg and goitem, but it do not belong why it jumps this message.

I have seen the method line_modify_badi (include LMIGOKL3) and is called to the method lcl_migo_screenmodification=>get. This one reads of a table of active fields in this execution and the field zzfield is not. Because of this jumps the message.

Not where this table is refilled (probably in the method screen_modify_mode?).

There is a loop where it is said in order that fields to do this checkup but I am not capable of creating an ENHANCEMENT-SECTION in this point. It jumps the message " In this way only can treat implementations of extension " (ED286).

Can you help me, please?

Thanks in adavance.

Regards

Husalban.

[Former Member]

Hi RM ,

Have u seen the sample coding of this Method.

SE18--->badi name ->GOTO(menu)->sample code->display-->double click on the the Interface of Line_ modify , their u can see the sample program , first see how SAP is doing ?

Regards

Prabhu

[Former Member]

Hi Prabhu,

I see the sample code, but use a standard field. The code that I have put is similar but with a custom field.

My problem is in the method LINE_MODIFY, it gives me a mistake on having tried to modify a custom field of the structure cs_goitem.

Not if I have to do something on having inserted a custom field to this structure in order that it works correctly.

Thanks,

[Former Member]

I have seen that calls to the function MIGO_GENERATE_FIELDSELECTION that goes for all the dynpros that there has the program SAPLMIGO.

And inside all the dynpros it takes all the fields that exist and adds them to a table (t_fieldselection).

My custom dynpro it does not take and adds the fields and because of it it fails.

I believe that the BADI should be prepared for this. This way that not if it is that I have skipped some step.

Thank you in advance.

[Former Member]

After putting a note sap. They confirm to me that the badi is not prepared to save customer fields in the structure goitem. I have had to create a table where to save the information, as it is done in the example implementation of the BADI.

Thank you anyhow

[Former Member]

I did it !!!

Doing an EXPORT TO MEMORY from the badi MB_MIGO_BADI and one IMPORT in the exit EXIT_SAPLIE01_007.

[stefan_kolev4]

Hi,

I have probably same problem.

I've added my custom field / zzgroes / into GOITEM and MSEG.I did some coding in PROCESS_ITEM method in my implementation in order to display groes field from mara.But when I put material number and press Enter system returns me a message: BADI: You are not allowed to change the content of the field GOITEM-ZZGROES.

How do you solve your problem ?

Please advice !

Stefan

[Former Member]

Dear Mr Husalban RM

I am also struggling with the similar problem . It will be a great favour incase you can pl guide me about the procedure and syntax to be followed for using "EXPORT TO MEMORY" and "IMPORT" concept .

With Thanks & Rgds

Sonia

[Former Member]

Dear All,

Can anybody help us about this problem? We really need your help. Many thanks.

Regards.

beconxinh

[Prashant4]

Dear All,

I'm also getting same issue in Line Modify.

lcl_migo_screenmodification=>get. giving me status = 8.

Kindly help to resolve this.

Regards,

Prashant Sharma.

[Former Member]

Hi Husalban,

There are some restrictions while using this badi. Please go throught the Badi documentation.

[janewar]

i had to maintain in configuration in SPRO , Material Management->Inventory management->Settings for enjoy transactions->Setting for Goods Movement Type->Field Selection Per Movement type . Execute and Maintained here for the required mvt type with EBELN as optional input field.