Closing month error

SOLVED

I am trying to close previous months and no one at Sage can seem to help me.  We NEED to get out months closed because voids and such are posting in previous months and changing our #'s and causing confusion. 

When I try to close the period/month via transaction - Common Data- GL Accounting Tables - Fiscal Periods

I get this EXACT error "There is still some subcontract in process that needs to be posted'

We don't do anything with subcontractors or subcontracts in the system.  I have tried everything I can and have had 2 consultants look at it and no one can figure it out thus we now have a whole YEAR of months that cannot be closed and we cannot close & roll our year either. 

Can anyone help??? Please! 

  • 0

    I have seen an issue like that once. I checked all subcontract-related tasks and there was nothing in there that had to do anything with sub contracts. I was able to resolve this by doing the following (Make sure you have a backup and/or create a copy folder to test):

    1. Go to Costing>WIP>In-Process Posting
    2. Run that task and update/post it.
    3. After I updating those transactions, run the FUNSTKACC and then Final validation (CPTVAL)
    4. Try closing the period/year again.

    Hope this helps.

  • 0 in reply to Steffen Urban

    Thank you for the suggestion but when I run the costing-wip-in process posting there is nothing to run/post so it just takes me back to my menu screen.  

    Wish that was the answer.  

  • 0 in reply to Lsharpe

    Sage ERP X3 will only throw that error in one section of code, which is looks like this:

       If clalev([F:MWI]) & ([F:FCY]MFGFLG=2 | [F:FCY]WRHFLG=2 & [F:FCY]PURFLG=2)

           Call PARAM([F:FCY]FCY,"OPEIFA",LOPEIFA) From ADOVAL

           Call PARAM([F:FCY]FCY,"SCOIFA",LSCOIFA) From ADOVAL

           If [F:FCY]MFGFLG=2 & val(LOPEIFA)>1 | val(LSCOIFA)>1

               Filter [MWI] Where MFGFCY=[F:FCY]FCY

    &                            & TXNDAT>=PDATSTR & TXNDAT<=PDATEND

    &                            & ENTCOD<>""

    &                            & GLPSTA<>2

               Look [MWI] First With Nohint

               Filter [MWI]

               If !fstat

                   LRET += (LRET<2)*2

                   Call ECR_TRACE([F:FCY]FCY-":"-mess(96,187,1),1) From GESECRAN

               Endif

           Endif

    This is saying that you must either have OPEIFA or SCOIFA activated in your folder parameters.

    That's the WO WIP accounting interface or the EO subcontract process.

    OPEIFA (WO WIP) has two options:

    Yes: the account posting for the material consumption, production reporting and time consumption transactions will be performed using the WO WIP accounting function, with the automatic journal entered in the general setup ACCWIPENT - WIP automatic journal)

    No: the material consumptions and production reportings can be posted by means of the accounting interface function for the stocks when the setup ACCIFA - Accounting interface is set to Yes. In this case, it is necessary to specify that, in the stock transactions, the automatic journal codes are used. The times will not be posted.

    SCOIFA (EO Subcontract) has two options:

    Yes: The sub-contract WIP posting is carried out via the function WIP posting,with the automatic journal entered in the general setup ACCWIPEOA - sub-contract WIP auto journal.

    No: the posting is carried out via the function of the stockaccounting interface, when the setup ACCIFA - Accounting interface is set to Yes.In this case, it is necessary to specify, in the Receipts entry transaction, the code of the automatic journal used.

    What the code above is saying is:

    If either OPEIFA or SCOIFA are set to true

    THEN read the WIPCOST table (MWI), where these conditions are true:

    1. For this specific production site

    2. The transaction date is greater than or equal to the start production date and end production date range

    3. There must be an automatic journal set up (ENTCOD<> "")

    4. Posted cannot be true (GLPSTA <> 2)

    If any records are found within this table then the call to ECR_TRACE with the message you getting will be shown.

    Hope that helps you.

    Bob

  • 0 in reply to Delamater

    Bob ~ That may help but you could have written in Japanese for as much as I understand what you wrote.  Any chance you could direct me on how to look at these things or what to do?  I am completely lost on even where to start with your suggestion.  

    Thanks

  • 0 in reply to Lsharpe

    Hi LSharpe, just found this error in my folder as well.  I will report back what I find out.

  • 0 in reply to RegularGuy

    RegularGuy ~ Do you use subcontracting/subcontractors?  We do not which is why this error is even more confusing.  

  • 0 in reply to Lsharpe

    No, we don't use S/c either, in our case we had some unposted WIP.  

    I just ran FUNWIPACC and FUNSTKACC manually wide open.

    As soon as I posted all the WIP the error went away.

    Looking back I ran into this same issue last fiscal year and that was also our solution.

    Did that help?

  • 0 in reply to RegularGuy

    Unfortunately we have tried that and it doesn't work either.  Thanks for the reply though.  

  • 0 in reply to Lsharpe

    Do you still need assistance with the issue? It could also be that something is stuck in a table. It might be necessary that we take a look at this a bit more in depth. If you still need help, please contact support so that we can get the issue resolved.

  • 0 in reply to Steffen Urban

    HI, I have the same issue now. Could you help where exactly I should check?

  • 0 in reply to Lsharpe
    Hi Lsharpe

    How did you manage to solve this? We are experiencing the same problem.

    Thank you very much,

    Liesl
  • 0 in reply to Liesl
    verified answer
    We had to have another consultant do something in the background to delete the entry (which changed the books) but it was the only way we could get it closed. We could find the entry but there was nothing we could do to clear it.
    Sorry I don't have a better answer.
  • 0 in reply to Lsharpe
    Thank you very much.
  • 0 in reply to Lsharpe
    I have the same message. is there anyone who has a solution to this