GL_BC_PACKETS表说明

GL_BC_PACKETS是跟预算控制有关的主要的表，对于一个账户来说有三种余额类型：A,E,B－最专业的ERP社区，帮助你在ERP行业实现价值！
表中ACTUAL_FLAG主要表示影响的是账户的那种类型的余额
资金保留流程在表gl_bc_packets中插入记录，并且ACTUAL_FLAG，过账程序把这条记录删掉。
举个例子：在应付模块定义一张发票，包含一个分配行，金额为100，下面是这些信息在gl_bc_packets表中的变化：
a 输入一张发票，并且分配行金额为100
b 验证这张发票。资金保留流程会在gl_bc_packets表中创建一条记录，并且ACTUAL_FLAG='E'
c.执行传送至总帐的程序，这个过程在gl_interface创建了一条日记帐的记录(actual_flag=A),并且je_bach_id= null. 这个时候，保留款余额就为0了，实际余额就是100。实际的余额在gl_bc_packets中登记，不单单是在gl_balances表中
d.执行日记帐导入过程，这个过程会创建一个实际的日记帐输入，金额为100
执行日记帐过账，删除了gl_bc_packets表中的相应的内容

关于GL_BC_PACKETS中的数据，有17种情况：
1. A need to make a correction on a journal that has been created from a sub ledger. These transactions cannot be updated in the Journal form because the funds reservation was done in the sub ledger. These journals cannot be updated without some SQL updates and deletes to be performed. The purpose is that if any correction needs to be done it should come from the source. This keeps your sub ledger and General Ledger in balance. However, there is from time to time a need to have a correction made in the General Ledger for one of these types of journals.

2. Transactions are stuck in the GL_BC_PACKETS table with a JE_BATCH_ID –1 From time to time there may be records in the gl_bc_packets table that have a je_batch_id = -1. There are a few reasons why this condition could happen. Records from payables were stuck in gl_bc_packets during Payables transfer to GL. Sometimes it is all related to a certain transaction date. All rows for detail accounts had je_batch_id = -1 and je_batch_id = null for summary accounts. This can happen if a user had created GL batch after correcting stuck rows in gl_interface.

3. Orphan lines left in the GL_BC_PACKETS table after a user has deleted a manual journal from the form. This will leave the rows in the GL_BC_PACKETS table causing an orphan record. The correct procedure would be to post the journal. Reverse the journal and then post the reversal. If a journal is deleted the rows in the GL_BC_PACKETS and GL_BC_PACKET_ARRIVAL_ORDER table are orphaned. The deletion process does not clear the table of the matching rows.

4. Very old records from very old periods are left in the GL_BC_PACKETS and GL_BC_PACKET_ARRIVAL_ORDER table that have not been deleted for some reason and the records are too old to complete a root cause. This can happen because of some customization or custom triggers that might have been in place at some time.

5. Journal posting process has gotten hung up on a journal that has funds reservations completed. Usually this type of problem is cause by a disruption in the concurrent manager.

6. Funds reservations have gotten hung up during the reservation process. This can happen if there is a disconnection from the applications while funds reservation process is being performed.

7. Encumbrance lines remain in the GL_BC_PACKETS table with an account_type of ‘E’ and the customer is a Federal Customer.

8. Encumbrance lines remain in the GL_BC_PACKETS table with an account_type of ‘A’ and the customer is using encumbrance accounting and should not have any account_types of ‘A’ left in the table.

9. Users have turn encumbrance accounting on and off which should NOT be done once encumbrance accounting is turn on. This causes negative encumbrances in the General Ledger.

10. If a user has made any corrections to a journal in the applications through the Journals->Import->Correct. This may leave corrupted rows in the gl_bc_packets table.

11. Program – Create Journals created journals for encumbrances and actual.

12. ERROR12 in journal entry posting form.

13. An account that was used in a sub ledger while entering in transactions has been disabled or end dated and journal import or the posting fails because of this end dated/disabled account combination or end dated/disabled segment value.

14. Grant Management System (GMS) Funds Checking (GMSFCUPB) NOT POPULATING THE GL_BC_PACKETS TABLE CORRECTLY FROM GMS

15. JOURNAL COMING FROM AP ARE CHECKING FUNDS AGAIN IN GL. The packet_id that is in the gl_je_batches does not match the packet_id in gl_bc_packets table for the same transactions.

16. FUNDS RESERVATION DOES NOT FAIL WHEN TWO INVOICES WERE VALIDATED AT SAME TIME - Creates duplicate rows in the gl_bc_packets table. The source of the transactions is from the inventory sub ledger.

17. BUDGETARY CONTROLS CREATED JOURNALS ENCUMBRANCES AND ACTUAL. The issue was that Auto Post running for multiple sources, such as Payables and Purchasing, etc., while the Create Journals was starting to submit for both Actual and Encumbrance journals in Auto Posted. Actual and Encumbrance journals should not be set up to be ran through Auto Post at the same time