EXIT

[Former Member]

HI,

I AM CREATING A EXIT FOR MIRO . IN Enhancements LMR1M001 I AM CREATING ONE SCREEN 400. IN 400 I AM DISPLAYING SOME SCREEN FIELD . NOW IN 6000 (INITIAL SCREEN IN MIRO ) WHENEVE I AM ENTERING

SOME BLDAT LIKE 09.07.2007 THIS SCREEN MUST TRIGGER . SO IN PBO I WROTE LIKE THIS WAY

DATA: BLDAT LIKE INVFO-BLDAT.

MODULE CHECK_BLDAT OUTPUT.

BREAK-POINT.

IF BLDAT = '09.07.2007'.

CALL SCREEN 400.

ENDIF.

ENDMODULE. " CHECK_BLDAT OUTPUT

IN PAI

MODULE USER_COMMAND_0400 INPUT.

CASE OK_CODE.

WHEN 'BACK'.

LEAVE PROGRAM .

ENDCASE.

ENDMODULE. " USER_COMMAND_0400 INPUT

BUT AM NOT GETING ANY THING. PLEASE CORRECT IT

THANK YOU

ASHOK KUMAR

[Former Member]

Hi Ashok,

According to note: 165635 - Documentation: Enhancement LMR1M001 (MM-IV)

this enhacement is obsolete:

"(...) Functions

In the header screen (screen SAPLMR1M 0400) you can define a customer-specific subscreen.With this customer-specific function module you can determine the default values for the subscreen.

As the basis, the fields of structure RBKPV (header data) are available.

Remark

As of Release 4.6C, Transaction MR1M is no longer supported. Thus this customer exit and its functions are also obsolete.(...)"

Additional information:

To use screen exit pls refer the below link:

http://wiki.ittoolbox.com/index.php/Implement_a_screen_exit_to_a_standard_SAP_transaction

To resolve this issue :

So use Badi Invoice_Update and call FM

I am not sure if method CHANGE_BEFORE_UPDATE is the right one because it does contain neither an "error flag" parameter nor an exception.

I assume that method CHANGE_AT_SAVE will be more useful to you because it has an exception (ERROR_WITH_MESSAGE) that you can raise.

You can also use the METHOD CHANGE_BEFORE_UPDATE or CHANGE_IN_UPDATE..

Which will be called when saving the invoice..

like Update the structure MRMRBTX of the paramter TI_MRMRBTX in the method

CHANGE_IN_UPDATE.

<b>Reward pts if found usefull :)</b>

Regards

Sathish