ML81N user exit

[Former Member]

While revoking service entry sheet through ML81N transaction for service purchase order ,

it accepts the posting date before the date of creation of service document date.

We want any user exit or BADI to trigger error message that 'Posting date can not be in past'

We already tried for customer exit SRVDET and other customer exits for MM-Service entry exits

in smod. But issue is not resolved. Please help.

[Former Member]

Try exits

EXIT_SAPLMLSR_020

EXIT_SAPLMLSR_021

under enhancement SRVEUSCR

[Former Member]

No these customer exits do not work.When i added break point it did not stop there.

I want to display error message when we edit service entry and Posting date is entered in past.

[Former Member]

Hi Manjusha,

Try the following user exit for MLN81N:

Exit Name Description

INTERFAC Interface for data transfer

SRVDET User screen on tab strip of service detail screen

SRVEDIT Service list control (maintenance/display)

SRVENTRY Unplanned part of entry sheet (obsolete since Rel. 3.1G)

SRVESI Data conversion entry sheet interface

SRVESKN Set account assignment in service line

SRVESLL Service line checks

SRVESSR Set entry sheet header data

SRVEUSCR User screen on entry sheet tabstrip

SRVKNTTP Setting the account assgnmt category when reading in, if "U"

SRVLIMIT Limit check

SRVMAIL1 Processing of mail before generation of sheet

SRVMSTLV Conversion of data during importing of standard service cat.

SRVPOWEB Purchase order for service entry in Web

SRVQUOT Service export/import for inquiry/quotations

SRVREL Changes to comm. structure for release of entry sheet

SRVSEL Service selection from non-SAP systems

SRV_FRM SRV: Formula calculation (obsolete since 4.0A!)

Hope this will help you...

[Former Member]

Hello Rajeev,

I worked on these user exits. But these user exits do not solve the problem of raising the message.

Now i am working on FI realted BTE and FI Validations.

[Former Member]

Hi SAP guru,

I also have the same requirement.

Please suggest any solution for this.

Thanks in advance.

[Former Member]

We can use MB_CHECK_LINE_BADI for this purpose

[Former Member]

We can use MB_CHECK_LINE_BADI badi for this purpose. We can write the required logic at method check_line.