Continuation Account logic on GLCP

Comments

10 comments

  • Official comment
    Avatar
    Kymber Taylor

    Hi Tammy, found this: 

    If the uploaded file includes an expired account and the origination code is NOT in the CONTINUATION_ACCOUNT_BYPASS_ORIGINATIONS, post the transaction to the continuation account, unless the document type is in parameter CONTINUATION_ACCOUNT_BYPASS_DOCUMENT_TYPES.

    So, possibly for these transactions you might want to use a different Origination Code and make sure the doc type you're using is not in the 2nd parameter. 

    I'll make sure the articles and parameters are clearer about what's going on. 

    Thanks, Kymber

     

     

    Comment actions Permalink
  • Avatar
    Kymber Taylor

    Hi Tammy, does this only happen when using the GLCP? If the entries are loaded via EnterpriseFeed do they also demerge when closed accounts are present - or do they use continuation account logic? I'll do some testing in a few days, but wondered if you already knew. 

    Thanks, Kymber

    0
    Comment actions Permalink
  • Avatar
    Tammy-Lu Vandevender

    Kymber,

    We don't use the Enterprise Feed so I don't know.  I think non-01 origin codes use the continuation logic, but since the GLCP uses origin code 01, it doesn't.  I'm also wondering if there is a reason we shouldn't automatically post to the continuation account.

    0
    Comment actions Permalink
  • Avatar
    Kymber Taylor

    Hi Tammy, I'm wondering if there's something in the early processing of GLCP - they go through pre-scrubber - I think. GLCP can also be non-01 entries - you can specify the origin code of the accounting lines - and since documents processed in KFS will post to continuation accounts, I don't think it's restricted to non-01. Anyway, I'll let you know what I find out. 

    Thanks, Kymber

     

     

    0
    Comment actions Permalink
  • Avatar
    Kymber Taylor

    Hi Tammy, I closed account BL-4131410 and loaded the following entries via GLCP, ran scrubber/poster and the closed account entry posted to the continuation account. Am I missing something? 

    Thanks, Kymber

    2023BL4131410-----5000   ACEX01DI  MFPRJQ-1283          Research Expenses  80072                 +0000000000000411.00D2021-12-14          ---------- 
    2023BL0211403-----5000   ACEX01DI  MFPRJQ-1284          Research Expenses  80072                 +0000000000001000.00D2021-12-14          ---------- 
    0
    Comment actions Permalink
  • Avatar
    Tammy-Lu Vandevender

    Kymber,

    We get the following error message with the closed account in brackets:

    Origin Code Cannot Have Closed Account.

    Is there a parm we have to set in order for the closed account to use the continuation logic?  I thought perhaps it was this one:

    CONTINUATION_ACCOUNT_BYPASS_ORIGINATIONS

    But that parm determines which origin codes will post to the expired accounts.  We have '01' in that parm.

    Or maybe there is a bug in our version...

    0
    Comment actions Permalink
  • Avatar
    Kymber Taylor

    Thanks Tammy - I noticed my origin code was MF - I changed to 01 and got the same error. Looking into where that's coming from... 

    0
    Comment actions Permalink
  • Avatar
    Tammy-Lu Vandevender

    Kymber,

    Thanks.  I think our issue is that we have 01 in the parm.  Do we need to have 01 in the parm to allow online KFS eDocs to post to the expired accounts?  We do not have GLCP in the 2nd parm

    CONTINUATION_ACCOUNT_BYPASS_DOCUMENT_TYPES

    0
    Comment actions Permalink
  • Avatar
    Kymber Taylor

    GLCP isn't a document type that is processed by the scrubber - when you load a file into GLCP, the Doc Type is loaded as part of the transactions, so unless you put GLCP into the file of transactions, it will not process as a GLCP doc type. 

    Let me do some more testing - the behavior might also be different based on whether the account is expired vs closed. 

    I'm worried that removing 01 from the parm will post all entries to the continuation account and never to the expired account. Entries will post to expired accounts, if CG accounts are used within the grace period and the override box is checked, otherwise, they will post to continuation accounts - unless the account is closed. And I think that's where we're running into the issue - I think you want to change the origin entry on the accural entries loaded via GLCP to be something other than 01 - 01 means it was created in KFS and has a document behind it. Changing the origin code to something else will always post the entries to the continuation account, unless the doc type is in the bypass doc type parameter - which I doubt it will be. At least in base, the values in the bypass doc type parm come from PDP. 

    Anyway - more info tomorrow after I do more testing. 

     

    0
    Comment actions Permalink
  • Avatar
    Tammy-Lu Vandevender

    Kymber,

    Thanks for the added testing.  I forgot about the GLCP including the doc type for the individual transactions.  I'll suggest to our Accounting group that they use a different origin code.  It will be helpful to see how the rest of your testing goes.

    0
    Comment actions Permalink

Please sign in to leave a comment.