cancel
Showing results for 
Search instead for 
Did you mean: 

Reg: Error G/L account cannot be used !

rajesh_rajendran2
Participant
0 Kudos
235

Hi ,

I have an issue with one of the Purchase orders which though got generated from the EB system did not get transferred to the backend system due to some errors.

The backend application error for the PO is : G/L account X1 cannot be used

G/L account X2 cannot be used. & PO contains errors.

I have debugged the transfer function module of this Purchase order and find that the I get this error message from the BAPI return parameters.

The message number in the backend system is from message class ME 045 -"G/L accout cannot be used".

I have checked and found that this message comes from a form FELDAUSWAHL_FEHLER. Now the perform is called in the program LMEXFU02.

A sample code of the same which will call the perform is enclosed for your reference.

CHECK COUNT GE 9. "Materialnummer (Stelle 9) bewußt mit reingenommen

UNPACK COUNT TO MODIF.

IF L1 = '+'

AND L2 = '-'.

TMODP-MODIF = MODIF.

PERFORM FELDAUSWAHL_FEHLER.

ENDIF.

IF L1 = '-'

AND L2 = '+'.

TMODP-MODIF = MODIF.

  • PERFORM FELDAUSWAHL_FEHLER. "nicht mehr ab 4.0B TK 89897

ENDIF.

  • CHECK COUNT NE 20. "Finanzposition "173298

  • CHECK COUNT NE 49. "Finanzstelle "173298

  • CHECK COUNT NE 50. "Geldgeber "173298

IF L1 = '.' "ab Release 2.1

AND L2 = '-'.

TMODP-MODIF = MODIF.

perform check_t162x using tmodp-modif. "4.6A TK

if sy-subrc eq 0. "4.6A TK

PERFORM FELDAUSWAHL_FEHLER.

endif. "4.6A TK

ENDIF.

IF L1 = '.' OR

L1 = SPACE.

L3 = L2.

ELSE.

L3 = L1.

ENDIF.

ENDDO.

Now can any one tell me why does this perform get triggered. What is the relevance of L1 & L2. i.e which fields it validates etc and why do I receive any error that the G/L account cannot be used when the they are maintained for the company.

Awaiting yor expert comments.

With Regards,

Rajesh

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi

We have faced the similar issue earlier.

We raised the issue with SAP long back, but no reply yet.

We can avoid this by either trying to suppress the error message either in SRM or R/3 for the particular GL Account.

<u>Meanwhile, look at the following SAP OSS Notes, which talks about the same issue, but are quite old (might not be applicable to you ) -></u>

<u>Anyways, please cross-check</u>

Note 95545 ME21 w.new accnt assigmnt category:error mess.ME045

89897 ME21 EME045 G/L account cannot be used

78322 ME21, ME51: Field selection G/L acct. (position 1-8)

82258 PO with accnt assgnmnt: functional area w.req.entry

Note 731791 - Source determination: Test report for checking

Will update you soon on this.

Regards

- Atul

yann_bouillut
Active Contributor
0 Kudos

Hi,

Do you have this error message while creating the PR or PO directly in MM (without SRM) ?

Kind regards,

Yann