An unposted batch will not post in GL Post Transactions.

Article translations Article translations
Article ID: 864408 - View products that this article applies to.
Expand all | Collapse all

TechKnowledge Content

POTENTIAL CAUSES:
1. The Period to Post of the Batch is greater than the Current Fiscal Period in General Ledger. See resolution 2546.
2. GLTRAN records may not exist. See resolution 5618.
3. Detail lines are missing the Account, Subaccount and/or Amount. These lines must be deleted in GL Journal Transactions (01.010) using Initialize Mode. See resolution 467.
4. The Total fields in the BATCH table are incorrect. See resolution 13087.

Resolution 467 - Use Initialize Mode to access the Module field in General Ledger Journal Transactions to edit or delete any Unposted batches.

CORRECTION STEPS:
1. Access Options | Initialize Mode to enable Initialize Mode.
2. Access Journal Transactions and change Module field to indicate the two letter abbreviation of the module for the batch to edit or delete.

>> To DELETE the batch:

A. Select the appropriate batch in the Batch Number field.

B. Click the Delete button on the Dynamics SL toolbar.

C. Respond Yes to System Message 12 'Are you sure you want to delete?'

>> To EDIT the batch:

A. Select the appropriate batch in the Batch Number field.

B. Make appropriate changes and click the Save button on the Dynamics SL toolbar.

Resolution 2546 - Compare the Period to Post for the batch to the Current Fiscal Period in General Ledger GL Setup (01.950) - Fiscal Info.

NOTES:

1. If the batch's Period to Post is the same as or less than the General Ledger Current Fiscal Period, the batch should post when the GL Post Transactions process is run.

2. Any batch posted to a future fiscal period remains unposted until the General Ledger Current Fiscal Period equals the Period to Post for that batch.

Resolution 5618 - Verify GLTRAN records were created for the batch.

VERIFICATION STEPS:

1. Turn Initialization Mode ON in the Options menu.

2. Access GL Journal Transactions.

3. Change the Module field to the specific module (i.e. AP).

4. F3 in the Batch Number field and select the batch in question.

5. Review the detail lines that display in the grid.

CORRECTION STEPS:

1. If detail lines do not display in the grid, add the detail lines if necessary. However, the batch status should be reviewed to verify the batch released successfully.

2. If detail lines display in the grid, verify the total debits sum to the total credits.

Resolution 13087 - Update the Total fields with the correct amounts in the BATCH table using Query Analyzer.

NOTES:

1. There are 6 Total fields in the Accounts Receivable batch that must match: CrTot, CtrlTot, CuryCrTot, CuryCtrlTot, CuryDrTot, and DrTot.

2. DrTot and CuryDrTot fields are populated once the batch is released. (for a normal AR Invoice batch). This field may be 0 and the rest populated with the same total.

CORRECTION STEPS:

1. Using Query Analyzer, access the appropriate Application database and execute the following statement for each batch to determine the correct batch Totals:

SELECT SUM(OrigDocAmt) from ARDOC where BatNbr = 'XXXXXX'
(where XXXXXX = the Batch Number that needs to be corrected).

2. Execute the following statement for each batch to view the current values in the Total fields:

SELECT CrTot, CtrlTot, CuryCrTot, CuryCtrlTot, CuryDrTot, DrTot from BATCH where BatNbr = 'XXXXXX'
(where XXXXXX = the Batch Number that needs to be corrected).

3. Review the 6 Total fields and note which fields that are populated and which ones that are set to 0. For DrTot and CuryDrTot fields set to 0 - DO NOT UPDATE. Total fields that are populated with amounts, should match the Total given from the query statement in step 1. If one or more of the Total fields do not match the Total from step 1, proceed with the Correction Steps.

4. Execute the following statement for those batches where the Total fields are incorrect:

UPDATE BATCH SET YYYY = #####.## where BatNbr = 'XXXXXX'
(where YYYY = the Total field that needs to be corrected, #####.## = the amount the Total should be and XXXXXX = the Batch Number that needs to be corrected).

5. Perform step 2 again to verify the Total fields are now correct.

6. Once all Total fields are correct, try to release the batch again.



This article was TechKnowledge Document ID: 45922

Properties

Article ID: 864408 - Last Review: October 2, 2012 - Revision: 2.1
Applies to
  • Microsoft Dynamics SL 2011
  • Microsoft Dynamics SL 2011 Service Pack 1
  • Microsoft Dynamics SL 6.5
  • Microsoft Dynamics SL 6.5 Service Pack 3
  • Microsoft Dynamics SL 7.0
  • Microsoft Dynamics SL 7.0 Service Pack 2
  • Microsoft Dynamics SL 7.0 Service Pack 3
  • Microsoft Dynamics SL 7.0 Service Pack 4
Keywords: 
kbmbsmigrate KB864408

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com