5 Replies Latest reply: Apr 28, 2006 8:37 PM by Ferry Lianto RSS

ALE Error For GLMAST

Shelina Chamadia
Currently Being Moderated

While processing inbound IDoc's for GLMAST, we get the following error:

 

Message No. FH 511 - The data contains error, you cannot save.

 

It has error ststus 51 - Application document not posted.

 

We are on my SAP ERP 2004

 

Any help !!

  • Re: ALE Error For GLMAST
    Ferry Lianto
    Currently Being Moderated

    Hi Shelina,

     

    Welcome to SDN.

     

    The error was due to G/L master check in function module <b>GL_ACCT_MASTER_SAVE</b>.

     

    The following are possible errors by:

     

    - Check chart of account

    - Check if changes in chart of accounts data are allowed

    - Check names

    - Check keyword

    - Check company code

    - Check cost element

    - Check custom user exit

     

     

    Hope this will help.

     

    Regards,

    Ferry Lianto

  • Re: ALE Error For GLMAST
    Shelina Chamadia
    Currently Being Moderated

    Hi Ferry Lianto,

     

    Thank you for the response.

     

    Can you please elaborate as to what exactly we have to check for in that function module. I am fairly new to this whole ALE topic.

     

    Shelina

  • Re: ALE Error For GLMAST
    Ferry Lianto
    Currently Being Moderated

    Hi Shelina,

     

    If you go to t/code <b>SE37</b> -> Enter FM <b>GL_ACCT_MASTER_SAVE</b> -> Display.

     

    Then scroll down until you hit line with statement <b>PERFORM gl_acct_master_check TABLES</b>. Double click on the gl_acct_master_check, the system will then take you to include program <b>LGL_ACCOUNT_MASTERFX2</b>.

     

    In this include program, system will perfom validation such chart account, company code and etc. If one of the validation is incorrect, the system will then raise an error as you see in IDoc error message with status 51.

     

    Hope this will help.

     

    Regards,

    Ferry Lianto

  • Re: ALE Error For GLMAST
    Shelina Chamadia
    Currently Being Moderated

    Hi Ferry,

     

    I checked for

    - Check chart of account

    - Check if changes in chart of accounts data are allowed

    - Check names

    - Check keyword

    - Check company code

    - Check cost element

    - Check custom user exit

     

    All of these are there in the include.

     

    Dont know what to do next.

  • Re: ALE Error For GLMAST
    Ferry Lianto
    Currently Being Moderated

    Hi Shelina,

     

    Yes ... all the checking logics are inside the include program.

     

    Is this production issue?

    If it is, the best way is to simulate in QA using <b>WE19</b> - Test tool for IDoc processing. Populate all segments and process via the function module but with debug mode on.

     

    In this case, you will be able to step through the code and find out exactly what is causing error status 51.

    You can place break point at the include program LGL_ACCOUNT_MASTERFX2 as mentioned earlier.

     

    If you are not familiar with debugging process, perhaps you can work with ABAPer.

     

    Again, hope this will help.

     

    Regarsd,

    Ferry Lianto

Actions