BAdI: Maintenance of Extenral Detail Subscreens for Transact

Use

Application component: MM-IM-GR; MM-IM-GI

With the Business Add-In (BAdI) MB_MIGO_BADI, you can extend the interface of the goods movements transaction
( MIGO) with additional tabstrip controls for the detailed information (detail tabstrips) and header information (header
tabstrips). It is possible for an external application

to display an additional detail tabstrip with own subscreen (max. 10 lines) in MIGO
to display an additional header tabstrip with own subscreen (max. 3 lines) in MIGO
The program name, screen number and tab page text can be determined dynamically. Different screens can
therefore be controlled according to the mode (for example, change mode, display mode, goods receipt, goods
issue).

Pushbuttons
It is not possible to implement pushbuttons in the MIGO menu, but you can, however, implement pushbuttons directly
on the external subscreen. The OK code from MIGO is forwarded to the external application so it can react.

Cursor Control
So that the cursor stays on the same subscreen after you press Continue, if it was positioned there before, the
external application in the own PAI must hold the cursor positioning (on the same screen 'yes'/'no'; if 'yes', on which
field), to set the cursor in PBO again.

Requirements

If you use the BAdI MB_MIGO_BADI in MIGO to update customer-own data, in addition to the material document, to
the database, you should note the following:

The BAdI MB_MIGO_BADI is only active in transaction MIGO.

If you post goods movements with other transactions (for example, with MB01, MB1C, VL02N), you must ensure that
customer data is also updated, if necessary.
You can do this by using the BAdI MB_DOCUMENT_BADI (Creating a material document) to post the goods
movements with the transactions mentioned above.
Note that otherwise, posting the goods movements will lead to inconsistencies between SAP system data (for
example, in stocks, material documents, FI documents) and customer data.
To avoid these inconsistencies, we recommend posting all goods movements with transaction MIGO.

Standard settings

In the standard system, the Business Add-In is not active.

There is no default code.
The Business Add-In is not filter-dependent.
The Business Add-In can be used more than once.
Activities

To activate the Business Add-In, you must create an active implementation. Do this in Inventory Management and
Physical Inventory Customizing and choose the relevant activity under Maintain Customer-Exits and Business AddIns.

For more information about this procedure, see the SAP Library under

Basis Components -> ABAP Workbench -> Changing the SAP Standard -> Business Add-Ins -> Implementing
Business Add-Ins.
Note that the Business Add-In can be used multiple times and therefore all active implementations are called and run
through.

Create Implementations

BAdI definition MB_MIGO_BADI was created with transaction SE18.

Using transaction SE19, you can create an implementation for this BAdI. You can provide the methods with customerdefined code.

The BAdI definition can be used several times. In MIGO, five additional tabstrip control were defined for the detail
screen, and five additional tabstrip controls for the header information. In other words, up to five different
implementations can be created.

Recommendation
We recommend that you do not install the external application data directly in the implementation, but enclose it in
function modules. You assign the screen with the subscreens to the corresponding function group; see the example
implementation.

Example

For easier comprehension, an example code has been created for the BAdI MB_MIGO_BADI. The example
implementation class isCL_EXM_IM_MB_MIGO_BADI.

To activate the example implementation, use transaction SE19 to create a new implementation and then activate it.
Copy the example code with Goto -> Sample Code -> Copy.

The tabstrip controls MIGO BAdI Example are then displayed in MIGO for the header and detail information.

On the tabstrip control for the detail information, you can enter an additional quantity (and unit of measure). Both are
saved in table MIGO_BADI_EXAMPL.

The text field SGTXT can also be changed. An example shows how an external application can change the data from
the GOITEM (item data in MIGO) structure.

On the tabstrip control for the header information, you can enter an additional number. This is saved in table
MIGO_BADI_EXAMP2.

Further notes

Documentation for BAdI methods:

Initialization and registration of external detail screens:

INIT

PBO of detail screen

PBO_DETAIL

PAI of detail screen

PAI_DETAIL

Insert / change line (GOITEM)

LINE_MODIFY

Delete line (GOITEM)

LINE_DELETE

MIGO reset (delete all internal data)

RESET

Post a goods movement

POST_DOCUMENT

Check item data for goods movement

CHECK_ITEM

Mode of transaction MIGO (action, reference document, etc.)

MODE_SET

Status information and header data

STATUS_AND_HEADER

Save held data

HOLD_DATA_SAVE

Load held data

HOLD_DATA_LOAD

Delete held data

HOLD_DATA_DELETE

PBO of header screen

PBO_HEADER

PAI of header screen

PAI_HEADER

Check item data for goods movement

CHECK_HEADER

You can also call the documentation on the BAdI method via the menu, by carrying out the following steps:

1. Choose the tab page Interface.

2. Double-click on the relevant method.
3. Click on the right mouse button and choose Component documentation.

<b>Kindly reward points if you found the reply helpful.<b>