AP does not balance to GL

Source: Internet
Author: User
Tags metalink

Doc id:ag0967<?xml:namespace prefix = o ns = "Urn:schemas-microsoft-com:office:office"/>

SUBJECT:PH payment done by May but still appeared as unrecorded transaction of reconciling

Type:problem

Creation date:11-aug-08

Last Revision date:02-sep-08

Status:open

Owner:kevin

Symptom

PH FIN said that there are unrecorded payments this appeared as reconciling when in fact the payment is done in the month of May 2008. (Refer to Ag0967_01 ag0967_02)

cause

Solutions

1. [11-aug-08] Kevin checked the problem and found so many records were at Gl_interface table. And the status of some of records is ' EC12 '. (Refer to ag0967_03)

2. [12-aug-08] Kevin found note:344367.1 about that AP does not balance to GL in Metalink.

How to check this kind of problem:

The There is no data in the GL Interface this has yet to be processed.

If The following query returns any rows this data must is imported and posted into

The GL before following through with the rest of the action plan.

Select x.group_id

, X.batch_name

, x.gl_transfer_run_id

, G.status

, User_je_source_name

, SUM (G.ACCOUNTED_DR)

, SUM (G.ACCOUNTED_CR)

From Xla_gl_transfer_batches_all X

, Gl_interface G

where x.group_id = g.group_id

and x.application_id = 200

and g.gl_sl_link_table = ' apecl '

GROUP BY x.group_id

, X.batch_name

, x.gl_transfer_run_id

, G.status

, User_je_source_name

(Refer to Ag0967_04)

3. [13-aug-08] Kevin found this kind of ' EC12 ' problem maybe be Bug 4585089 of Oracle EBS.

4. [14-aug-08] Kevin asked Ren to the Apply Patch 4569370 in a test environment. (ag0967_05)

5. [15-aug-08] Kevin checked this problem and run ' Journal Import ' into GL on TEST Server. But the error ' EC12 ' still existed. (Refer to Ag0967_06)

6. [18-aug-08] Kevin is still checking this problem.

7. [21-aug-08] Kevin found account [210.212.5901002000.0000.0000.0000.000.0000] in accounting of payment [Document num:29 A. and Kevin confirmed with PH FIN, that, [210.212.5901002000.0000.0000.0000.000.0000] should not appear here. (Refer to ag0967_07)

8. [21-aug-08] Kevin wanted to create SR for this problem but didn ' t succeed because the status of support identifier is ' NO VALID CSI FOUND '.

9. [25-aug-08] Kevin found payment [2971] and [2972] those were not balance.

[25-aug-08] Kevin ran the SQL script on TEST Server (erpdb). (SQL script:ag0967_08)

[25-aug-08] opened period ' May-08 ' in AP module. (Refer to ag0967_09)

[25-aug-08] Then ran the ' Payables Transfer to General Ledger '. (Refer to Ag0967_10)

[25-aug-08] Then ran the ' Journal Import '. (Refer to Ag0967_11)

[25-AUG-08] inquired journal. (Refer to Ag0967_12)

[26-aug-08] Kevin asked PH FIN to check this problem on TEST Server (erpdb) carefully. (Refer to Ag0967_13)

[26-aug-08] PH FIN confirmed that this problem is solved on TEST Server (erpdb). (Refer to Ag0967_14)

[26-aug-08] Awaiting for PH FIN confirms entry AG0968 this is OK. We need to confirm so AG0967 and AG0968 are all OK before we apply the solution on PROD Server, because entry AG0967 The same kind of problem as AG0968, and they have the same one solution.

18. [02-SEP-08] Kevin applied the solution on TEST Server again, and found there were journal entry are unbalanced.

There were Batch name[34985 Payables 5231237:a 371476], Batch name[36288 Payables 5231237:a 396269]

[03-sep-08] PH FIN Myles checked them and found some abnormal. (Refer to Ag0967_15 ag0967_15a)

[03-sep-08] Kevin found what caused these abnormal entries. The cause needed to be checked. (Refer to Ag0967_16)

[04-sep-08] PH FIN Myles confirmed these entries were abnormal. (Refer to Ag0967_17 ag0967_17a)

[05-sep-08] Ren restored ERPAPP backup dated 2008-08-30 on the TEST server for my testing. (Refer to Ag0967_18)

[05-sep-08] Kevin ran the SQL script to correct the abnormal data. (Refer to ag0967_19)

[05-sep-08] Ran ' Payables Transfer to General Ledger ' & ' Journal Import '. (Refer to Slide #8 & #9 in ag0967_20)

[05-SEP-08] This problem is solved on TEST Server (erpdb). Awaiting for end user ' s confirmation.

Doc id:ag0968

subject:voided transactions still showed in bank recon items

Type:problem

Creation date:11-aug-08

Last Revision date:02-sep-08

Status:open

Owner:kevin

Symptom

PH FIN said that there were several "voided transactions" made which should not appear as reconciling but the system read or included those in downloading of bank recon items. (Refer to Ag0968_01 ag0968_02)

cause

Solutions

1. [11-aug-08] Kevin checked the problem and found so many records were at Gl_interface table. And the status of some of records is ' EC12 '. (Refer to ag0968_03)

2. [12-aug-08] Kevin found note:344367.1 about that AP does not balance to GL in Metalink.

How to check this kind of problem:

The There is no data in the GL Interface this has yet to be processed.

If The following query returns any rows this data must is imported and posted into

The GL before following through with the rest of the action plan.

Select x.group_id

, X.batch_name

, x.gl_transfer_run_id

, G.status

, User_je_source_name

, SUM (G.ACCOUNTED_DR)

, SUM (G.ACCOUNTED_CR)

From Xla_gl_transfer_batches_all X

, Gl_interface G

where x.group_id = g.group_id

and x.application_id = 200

and g.gl_sl_link_table = ' apecl '

GROUP BY x.group_id

, X.batch_name

, x.gl_transfer_run_id

, G.status

, User_je_source_name

(Refer to Ag0968_04)

3. [13-aug-08] Kevin found this kind of ' EC12 ' problem The maybe caused by Bug 4585089 of Oracle EBS.

4. [14-aug-08] Kevin asked Ren to the Apply Patch 4569370 in a test environment. (ag0968_05)

5. [15-aug-08] Kevin checked this problem and run ' Journal Import ' into GL on TEST Server. But the error ' EC12 ' still existed. (Refer to Ag0968_06)

6. [18-aug-08] Kevin is still checking this problem.

7. [21-aug-08] Kevin found account [210.212.5901002000.0000.0000.0000.000.0000] in accounting of payment [Document num:29 A. and Kevin confirmed with PH FIN, that, [210.212.5901002000.0000.0000.0000.000.0000] should not appear here. (Refer to ag0968_07)

8. [21-aug-08] Kevin wanted to create SR for this problem but didn ' t succeed because the status of support identifier is ' NO VALID CSI FOUND '.

9. [25-aug-08] Kevin found payment [2971] and [2972] those were not balance.

[25-aug-08] Kevin ran the SQL script on TEST Server (erpdb). (SQL script:ag0968_08)

[25-aug-08] opened period ' May-08 ' in AP module. (Refer to ag0968_09)

[25-aug-08] Then ran the ' Payables Transfer to General Ledger '. (Refer to Ag0968_10)

[25-aug-08] Then ran the ' Journal Import '. (Refer to Ag0968_11)

[25-AUG-08] inquired journal. (Refer to Ag0968_12)

[26-aug-08] Kevin asked PH FIN to check this problem on TEST Server (erpdb) carefully. (Refer to Ag0968_13)

[26-aug-08] PH FIN said that they didn ' t to the solution on TEST Server (erpdb). (Refer to Ag0968_14)

[27-aug-08] Kevin told them to check this problem. (Refer to Ag0968_15 ag0968_15a)

[28-aug-08] PH FIN said that there were payments do in 2007, and there payments were-reversed in 2008. (Refer to Ag0968_16)

[28-aug-08] Awaiting for the "end confirmation of PH FIN.

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.