LS NAV - Autopost Statements

• Create Job to run C99001460 Automatic Statement Posting
• • Retail Setup
  • Set Default Store, Enter Store Name
  • Store Setup
  • Calculation Type: Terminal or staff
  • One statement per day: True
  • Tender Type
  • Counting Required (False) (Not required)
  • Job Setup
  • Create Job to run C99001460
  • Select Stores to run against
  • Modification to Codeunit 99001460 Automatic Statement Posting to automatically post statement after job ran
  • Add Code “StatementPost.RUN(Statement);”
  • Comment/Remove code “StatementPost.RunItemPosting(Statement,FALSE);”
  • If any warnings exist on the statement pertaining to missing transactions, it should be cleared and recalculated or the statement will not post
  • Check the Trans. Sales Entry Status 99001494 table to ensure that records exist for all transactions on a statement. If any are missing, the statement will not post.
  • This is happening because all of the transactions have not been uploaded to the HO as yet. The statement has been prematurely calculated
  • You must clear and recalculate the statement.
  • The problem that happens is that when the automated statement calculate runs, and hits this specific error, it breaks the job itself preventing any other records from being processed, and putting the job and statement into error states
  • When the job runs again, the same thing happens, causing the job to permanently stick on a bad statement
  • Prior to running the job, ensure all transactions are at HO with a full trans pull
  • You must add code to auto clear and recalculate the statement if the job or the statement are in error states (or you could auto clear and recalculate ALL the statements)