ERIC KB Articles

OEB-CM Processing: Found duplicate CM Number! Please re-process

2011-08-31T02:59:00.000-07:00

Issue:
User encounters error (Found duplicate CM Number! Please re-process) when updating CM.

Cause:
The CM number to be used already exists.

Solution:

Take note of last CM number in A/R System tailoring
Check cm_number in a_sales_rtn_header for last cm_number
Update last CM number in A/R System tailoring
Run queries below to check tables:

-- a_sales_rtn_header
select *
from a_sales_rtn_header with (nolock)
where cm_number = 'Put CM Number with issue here'

-- a_sales_rtn-detail
select *
from a_sales_rtn_detail with (nolock)
where sales_rtn_no in ('Affected SR No. from above query')

-- a_open_payment
select *
from a_open_payment with (nolock)
where payment_doc_no = 'Put CM Number with issue here'

-- a_open_item
select *
from a_open_item with (nolock)
where doc_no = 'Put CM Number with issue here'

-- a_output_tax
select *
from a_output_tax with (nolock)
where doc_no = 'Put CM Number with issue here'

-- a_doc_reg
select *
from a_doc_reg with (nolock)
where doc_no_fr = 'Put CM Number with issue here'

-- a_gl_oeb_trans
select *
from a_gl_oeb_trans with (nolock)
where doc_no = 'Put CM Number with issue here'

-- a_open_acr_appl_to
select *
from a_open_acr_appl_to with (nolock)
where payment_doc_no = 'Put CM Number with issue here'

-- a_bilhst_header
select *
from a_bilhst_header with (nolock)
where doc_no in ('Affected SR No. Refer to query for a_sales_rtn_header')

-- a_bilhst_detail
select *
from a_bilhst_detail with (nolock)
where doc_no in ('Affected SR No. Refer to query for a_sales_rtn_header')

Run script below to update cm status of sales return and delete CM number with issue on a_output_tax.

UPDATE a_sales_rtn_header
SET cm_status = 'N',
cm_number = NULL,
cm_by = NULL
WHERE sales_rtn_no IN ('Affected SR No. Refer to query for a_sales_rtn_header')
DELETE
FROM a_output_tax
WHERE doc_no = 'Put CM Number with issue here'

Receiving: XR Transaction – Error inserting G/L – I.M. record…

2011-08-22T02:07:00.000-07:00

Issue:
Initially, the user receives error ‘No Contra Account Code maintained for item <item number>’. Upon maintaining Contra Account Code and doing transaction again, the user receives another message ‘Error inserting G/L – I.M. record for item <item number> in site <site code>. — INSERT statement conflicted with COLUMN FOREIGN KEY constraint ‘FK42a_valid_accts’. The conflict occured in database’getzdb’, table ‘a_valid_accts’, column’gl_acct”.

Cause:
IM Transaction Contra Account maintained is not valid or is not found in a_valid_accts table.

Solution:
Update Contra Account with Issue and perform transaction again.

AR Batch CM Processing: Balance cannot be adjusted in Batch CM Processing

2011-08-11T01:44:00.000-07:00

Issue:
User is unable to perform CM Processing for particular document number due to amount is zero. When checking Customer A/R Status, there is still balance for the invoice.

Cause:
Column amt_allocated in table a_open_item is not equal to zero. Possible cause is network fluctuation during last transaction.

Solution:
1. Check the following tables if transaction exists:

a_doc_reg
a_open_item
a_open_itm_hist
a_output_tax
a_ar_gl_trans

Criteria would be customer code and document number.
2. Check amt_allocated in a_open_item table if not equal to zero.
2.1. If amt_allocated is not zero, perform update statement below
declare @cust_code as char(8),
@doc_no as char(8)
set @cust_code = 'cust_code w/ issue'
set @doc_no = 'doc_no w/ issue'
update a_open_item
set amt_allocated = 0
where cust_code = @cust_code
and doc_no = @doc_no
2.2. Else, notify JSI for issue

Forms Printing: Unable to Retrieve Document number

2011-08-11T01:27:00.000-07:00

Issue:
User is unable to retrieve some document numbers in Forms Printing. Message ‘No Rows Retrieved’ appears when retrieving rows.

Cause:
APV status is fully paid and period end has been processed.

Solution:
1. Check the following tables:
declare @doc_no1 as char(8),
@doc_no2 as char(8)
set @doc_no1 = '8VP12560'
set @doc_no2 = '8vp12560'
-- a_apy_doc
select printd_flg, trans_code, *
from a_apy_doc
where doc_no_fr = @doc_no1
--a_open_inv_hdr_hst
select *
from a_opn_inv_hdr_hst
where doc_no = @doc_no1
– a_open_pay
select *
from a_open_pay
where pay_doc_no in (@doc_no1, @doc_no2)
-- a_gl_ap_trans
select *
from a_gl_ap_trans
where doc_no_appl = @doc_no1
-- c_apy_ctl
select fiscal_period, *
from c_apy_ctl
2. To determine the particulars needed by the user, run query below:
declare @supplier as char(8),
@ref_no as char(20),
@trans_apv as char(3)
set @supplier = '192043'
set @ref_no = '8VP12-560'
set @trans_apv = 'APV'
-- a_gl_ap_trans
select trans_date, supplier, trans_code, ref_no, trans_amt, doc_no, particulars
from a_gl_ap_trans
where supplier = @supplier
and ref_no = @ref_no
and trans_code = @trans_apv
order by doc_no, trans_code_appl

SO Entry: Unable to Retrieve SO

2011-08-11T00:49:00.000-07:00

Issue:
User is unable to retrieve particular SO.

Cause:
Column so_created_by under a_so_header table is NULL. Why it became NULL remains a mystery.

Solution:

Check if SO is present on the tables (see query below). Also check so_created_by column in a_so_header table if value is NULL.
declare @so_no as char(8)

set @so_no = 'input so number here'

select *
from a_so_header
where so_number = @so_no

select *
from a_so_detail
where so_number = @so_no

select *
from a_so_release
where so_number = @so_no
If value of so_created_by is NULL, perform update statement below. Otherwise, proceed to step 3.
declare @so_creator as char(10),
@so_no as char(8)
set @so_creator = 'input user id here'
set @so_no = 'input so number here'

update a_so_header
set so_created_by = @so_creator
where so_number = @so_no
Notify JSI for issue.

AR Batch PR Processing: Unable to process PR. Message ‘This document is currently being processed…’ appearing when selecting document number.

2011-07-27T18:48:00.000-07:00

Issue:
The user is unable to proceed processing transaction for a customer due to message appearing (‘This document is currently being processed in a different transaction. Please choose another document.’) when selecting document number.

Cause:
This happens when the last transaction done for the document encountered problem during processing causing the document to be locked in t_acr_lock.

Solution:

Perform select statement below to verify locking. Check for the doc_no column. The document number should match the document on which the user is encountering problem.select *
from t_acr_lock
Delete the row that is causing the problem. Refer to delete statement below.
declare @cust_code as char(8),
@doc_no as char(8),
@user_id as char(10)set @cust_code = ‘put customer code here’
set @doc_no = ‘put document number here’
set @user_id = ‘put user id here’
– delete row with locked document
delete
from t_acr_lock
where cust_code = @cust_code
and doc_no = @doc_no
and user_id_chg_by = @user_id

AR Batch CM Processing: User received DBPROCESS Message During Batch CM Processing

2011-07-27T18:39:00.000-07:00

Issue:
The user receives message ‘DBPROCESS is dead or not enabled’ during Batch CM Processing and would like to verify if transaction is successfully processed.

Cause:
This issue is caused by intermittent network connection. The user got disconnected from the network during Batch CM Processing.

Solution:

Check Customer A/R status if transaction exists.

If transaction exists, take note of informations such as transaction type, trans date, doc date, doc no, reference, etc.
Else, notify JSI for issue.

Reprint CM. Go to AR > Activity > Custom Activity > AR Forms Printing.

Customer A/R Status: CM Transaction for SR with Reference Reflected in Customer AR as UNC

2011-07-27T18:33:00.000-07:00

Issue:
The user is wondering why the CM (Credit Memo) transaction for SR (Sales Return) with Reference went to Customer A/R status as UNC instead of applying it under the reference invoice in SR.

Cause:
The Invoice connected with the Sales Return transaction done is already paid in full which is why the entry created in Customer AR reflected as UNC during CM Processing because there is nothing left to be applied for the Invoice.

Solution:
No solution to be done here because this is the normal behavior of the program. However, you can do the following actions below to validate the cause.

Go to AR > Inquiry > Customer A/R Status
Inquire for the customer with issue and search for the invoice number. You should notice under Net Balance that it is already zero.

Issuing: Item Suspended

2011-07-21T18:56:00.000-07:00

Issue:
User receives 'All items were suspended due to insufficient stock.' message upon performing Issuing transaction. After clicking OK, user Processed Suspended transaction then another message appeared 'There's no suspended item that has been processed because there's no available qty. on hand.'

Cause:
UM balance in a_item_balance (BT) is different from SKU (PC).

Solution:
1. Run query to check tables:
declare @item_no as varchar(20),
@site as char(8)
set @item_no = 'CL0504022'
set @site = 'MLA-D/S'
-- a_item_balance
select qty_alloc_mfg,
qty_alloc_sales,
qty_on_hand,
*
from a_item_balance
where item_number = @item_no
and site = @site
-- a_item_um
select *
from a_item_um
where item_number = @item_no
-- a_item_master
select *
from a_item_master
where item_number = @item_no
2. Below is the update statement to fix issue:
declare @um as char(3),
@item_no as varchar(20),
@ref1 as varchar(15),
@ref2 as varchar(15),
@site as char(8),
@lot_serial1 as varchar(20),
@lot_serial2 as varchar(20)
set @um = 'PC'
@item_no = 'CL0504022'
@ref1 = 'RS044739'
@ref2 = 'RS044744'
@site = 'MLA-D/S'
@lot_serial1 = 'CM143086-SR36734'
@lot_serial2 = 'CM143091-SR36738'
-- update a_item_balance table
update a_item_balance
set um = @um
where item_number = @item_no
and ref in (@ref1, @ref2)
and site = @site
and lot_serial_no in (@lot_serial1, @lot_serial2)

AR-DM Interface: Not balanced

2011-07-21T18:08:00.000-07:00

Issue:
Debit and Credit is not balanced in AR-DM Interface.

Cause:
The trans amount of debit entry DM No. 00000321 for GL Account Code 1230-0011000 is zero.

Solution:
1. Below are the select queries sent by JSI:
declare @doc_no as char(8)
set @doc_no = ’00000321′
– a_open_item
select *
from a_open_item
where doc_no = @doc_no
– a_open_itm_hist
select *
from a_open_itm_hist
where doc_no = @doc_no
– a_doc_reg
select *
from a_doc_reg
where doc_no_fr = @doc_no
– a_ar_gl_trans
select *
from a_ar_gl_trans
where doc_no = @doc_no
2. Below is the 2nd set of query sent:
declare @trans_amt as decimal (12, 2),
@trans_dm as char(3),
@reverse_flg as varchar(1),
@cust_code as char(8),
@doc_no as char(8)
set @trans_amt = 38.83
set @trans_dm = ‘DM’
set @reverse_flg = ‘Y’
set @cust_code = ’10GM1360′
set @doc_no = ’00003092′
– a_open_item
select *
from a_open_item
where trans_amt = @trans_amt
and trans_code = @trans_dm
– a_open_itm_hist
select *
from a_open_itm_hist
where trans_amt = @trans_amt
and trans_code = @trans_dm
– a_tax_schedule
select *
from a_tax_schedule
where tax_amt = @trans_amt
and reverse_flg = @reverse_flg
and cust_code = @cust_code
– a_tax_schedule
select *
from a_tax_schedule
where doc_no = @doc_no
3. See below for the data fix script:
declare @doc_no as char(8),
@trans_dm as char(3),
@cust_code as char(8)
set @doc_no = ’00000321′
set @trans_dm = ‘DM’
set @cust_code = ’10GM1360′
– a_ar_gl_trans
delete
from a_ar_gl_trans
where doc_no = @doc_no
and trans_code = @trans_dm
and cust_code = @cust_code

Invoice Printing: There are no more orders ready for invoicing

2011-07-20T19:53:00.000-07:00

Issue:
User receives message ‘There are no more orders ready for invoicing.’ when performing invoice printing.

Cause:
Table is locked to another user. This type of issue is fixed in the current patch for Invoice printing (External Exe). There are also other reasons for this error. Please see solution to verify.

Solution:
1. Go to SO Tracking (OEB > Inquiry > SO Tracking) to check what transactions the SO had passed thru. Should there be no error here, proceed to next step.
2. Go to SO Entry and retrieve SO with issue. Take note of the SO Type.
3. Go to SO Types (OEB > Tables > Sales Order Types) and check particular SO Type if Print Invoice is checked and also what Invoice format number it uses. If not checked, then this is the cause of the error. Otherwise, proceed to next step.
4. From previous window (Sales Order Types), check if Format is not 1. If Format is not 1 then perform Invoice printing again for the SO then select correct Format. If issue persists, proceed to next step.
5. Check t_oeb_lock table and see if SO Number is locked. Should the SO number exist, take note of the user_id using the SO and proceed to next step. Otherwise, contact JSI for assistance.
6. Check pc_user_def table and filter by user_id noted on previous step in order to get the name of the other user using the SO.
7. Notify user with issue that the error is caused by other user using the same SO and corrective action is to have the other user logout of ERIC then log back in.
8. Once other user logs out of ERIC, user can now perform Invoice printing. Should issue persist, notify JSI for assistance.

A/P Aging: Discrepancy with Aging Report (Current vs Last Year)

2011-07-20T19:43:00.000-07:00

Issue:
User reported discrepancy for Aged payables (A/P Aging) report printed last May 30, 2010 for supplier P11001A and same report printed currently as of July 2011.

Cause:
This happens when DM has been applied and when period end has been processed. As a result, transaction will be removed from the main table and put to the history table. Ergo it will no longer be seen in the AP Aging report.

Solution:
For the issue above. Below are corresponding DM entries:

APV 10IPR506 – DM F0800629
CM 12M154A – DM 11JV610C

You can check for the above document number via Document Register report. To access report, go to Accounts Payable module > Reports > Document Register.

Inventory Management: Error in Receiving

2011-07-19T05:09:00.000-07:00

Issue:
User encountered error in Receiving Transaction. See below for error received:

Error: GEN000033
What Happened: You have an interrupted process that must be continued.
What to Do: Please press the OK button to proceed.

Cause:
This is usually due to connection error or illegal termination of ERIC.

Solution:
Check the following table:

a_inv_trans_top
t_inv_lock

Verify with user if ok to remove record then remove record.

Inventory Management: Blocking/Hanging

2011-07-19T05:05:00.000-07:00

Issue:
User experienced hanging when performing Stock Transfer Location (STL).

Cause:
For some reason, user is blocked by another user logged in to ERIC. The strange part is that the blocking user is just logged in under Inventory Module and is not performing any activity in ERIC.

Solution:
1. Open SQL Enterprise Manager
2. Connect to ERIC server
3. Go to Management > Current Activity > Locks / Process ID
4. Look for the user icon with exclamation mark (This is the blocking user) and take note of its spid.
5. Open u_audit_trail_users to determine blocking users activity (user_id, module_name, program)
6. Check pc_user_def table to determine blocking users identity (first_name, last_name, etc)
7. Contact blocking user and advice to logout then log back in to ERIC.

AR Batch CM Processing: Invalid Login

2011-07-19T05:00:00.000-07:00

Issue:
The user encounters error when opening custom activity AR Batch CM Processing. The error only appears on the users machine. Copying of ERIC 5.2 folder from other machine still does not fix the issue.

Cause:
This is usually due to the access rights for the ERIC folder.

Solution:
1. Right click on ERIC 5.2 folder (usually in c:\eric 5.2) and select properties.
2. Go to Security tab and check if user has access to the folder.
3. Provide access for the user then apply to subfolders.

Stock Transfer: Error when Saving Stock Transfer Location

2011-07-15T19:22:00.000-07:00

Issue:
User receives error message ‘Error generating document number.’ after clicking save when performing Stock Transfer Location.

Cause:
Temporary table a_inv_trans_top contains record of the user. This might be due to problem during his last transaction. Problem may be due to abnormal program termination or network connection.

Solution:

Backup a_inv_trans_top table
Remove record of user with issue in a_inv_trans_top

Disbursement Selection: Error in Disbursement - Amount Doubled

2011-07-15T18:50:00.000-07:00

Issue:
User receives error when performing Disbursement Selection. He is unable to generate screenshot of the error but upon checking again in Disbursement Selection, the amounts got doubled.

Cause:
One of the table that holds the amount paid in disbursement process was already updated after the error appeared. Upon performing disbursement process again, it summed up the value currently on the second disbursement batch created.

Solution:
Run script below to fix issue:
declare @doc_no  as char(8),
@supplier as char(8),
@trans_apv as char(3)
set @doc_no  = ’11AB3SK1′
set @supplier = ‘P11042A’
set @trans_apv = ‘APV’
– Update a_open_inv_hdr table
update a_open_inv_hdr
set amt_allocated = 0.00
where doc_no  = @doc_no
and supplier = @supplier
and trans_code = @trans_amt
Note: Run this for all document numbers affected.

AR Batch PR Processing: Database Error - Row changed between retrieve and update...

2011-07-13T19:23:00.000-07:00

Issue:
User encountered error upon performing AR Batch PR Processing.

Cause:
Suspending a batch while it is still in use by other user. This error can be replicated given scenario below:

User 1, create invoice. Enter user calculated batch and entry no. Close the window then open it again.
User 2, suspend transactions made by user 1, create another invoice. Click ok. Enter calculated batch and entry no.
User 1, open the first invoice, then ok. Update the batch. The error message will
prompt.

Fix:
1. Check the following tables to verify if transaction is successfully saved.

a_open_payment
a_open_pymt_hist
a_open_payment_check
a_open_pymt_check_hist
a_doc_reg
a_open_acr_appl_to
a_open_acr_appl_hist
a_open_item
a_open_itm_hist

Use script below in checking the above tables.
declare @doc_no1 as char(8),
@doc_no2 as char(8),
@doc_no3 as char(8),
@trans_pr as char(3),
@trans_unp as char(3)
– Continue adding @doc_no if more than 3. Hence, if less then remove excess declaration of @doc_no.
set @doc_no1 = ’428154′
set @doc_no2 = ’427739′
set @doc_no3 = ’426030′
set @trans_pr = ‘PR’
set @trans_unp = ‘UNP’
– a_open_payment
select *
from a_open_payment with (nolock)
where payment_doc_no in
(@doc_no1, @doc_no2, @doc_no3)
and payment_trans_code = @trans_pr
– a_open_pymt_hist
select *
from a_open_pymt_hist with (nolock)
where payment_doc_no in
(@doc_no1, @doc_no2, @doc_no3)
and payment_trans_code = @trans_pr
– a_open_payment_check
select *
from a_open_payment_check with (nolock)
where payment_doc_no in
(@doc_no1, @doc_no2, @doc_no3)
and payment_trans_code = @trans_pr
– a_open_pymt_chk_hist
select *
from a_open_pymt_chk_hist with (nolock)
where payment_doc_no in
(@doc_no1, @doc_no2, @doc_no3)
and payment_trans_code = @trans_pr
– a_doc_reg
select *
from a_doc_reg with (nolock)
where doc_no_fr in
(@doc_no1, @doc_no2, @doc_no3)
and trans_code = @trans_pr
– a_open_acr_appl_to
select *
from a_open_acr_appl_to with (nolock)
where payment_doc_no in
(@doc_no1, @doc_no2, @doc_no3)
and payment_trans_code = @trans_pr
– a_open_acr_appl_hst
select *
from a_opn_acr_appl_hst with (nolock)
where payment_doc_no in
(@doc_no1, @doc_no2, @doc_no3)
and payment_trans_code = @trans_pr
– a_open_item
select *
from a_open_item with (nolock)
where doc_no in
(@doc_no1, @doc_no2, @doc_no3)
and trans_code = @trans_unp
– a_open_itm_hist
select *
from a_open_itm_hist with (nolock)
where doc_no in
(@doc_no1, @doc_no2, @doc_no3)
and trans_code = @trans_unp

Transaction Processing: Error on Batch Update [batch no.]

2011-07-13T00:04:00.000-07:00

Issue:
User encountered error messsage ’3902 The COMMIT TRANSACTION request has no corresponding BEGIN TRANSACTION.’ when performing Batch Update of DM under Transaction Processing.

Cause:
This is caused due to network fluctuation.

Fix:
Check the following tables

a_open_item
a_open_itm_hist
a_doc_reg
a_ar_gl_trans

See below for sample query:
-- a_open_item
select *
from a_open_item with (nolock)
where trans_code = ‘DM’
and ref_no in (’11V6-156′, ’11V6-157′, ’11V6-158′, ’11V6-159′, ’11V6-160′, ’11V6-161′, ’11V-162′, ’11V6-163′, ’11V6-164′, ’11V6-165′)

-- a_open_itm_hist
select *
from a_open_itm_hist with (nolock)
where trans_code = ‘DM’
and ref_no in (’11V6-156′, ’11V6-157′, ’11V6-158′, ’11V6-159′, ’11V6-160′, ’11V6-161′, ’11V-162′, ’11V6-163′, ’11V6-164′, ’11V6-165′)

-- a_doc_reg
select *
from a_doc_reg with (nolock)
where trans_code = ‘DM’
and ref_no in (’11V6-156′, ’11V6-157′, ’11V6-158′, ’11V6-159′, ’11V6-160′, ’11V6-161′, ’11V-162′, ’11V6-163′, ’11V6-164′, ’11V6-165′)

-- a_ar_gl_trans
select *
from a_ar_gl_trans with (nolock)
where trans_code = ‘DM’
and batch_no = ’897′

Sales Return: Error retrieving item class record of item [item number]

2011-07-11T17:22:00.000-07:00

Issue:
User receives error message ‘Error retrieving item class record of item YS0101102′. When saving Sales Return transaction.

Cause:
This issue is due to table is not maintained in Sales tab of IM – G/L Account code definition.

Solution:
1. Get the following information:

Item Code
Site used during Sales Return
Item Class
Item Sub-Class

2. Check table IM-G/L Account code definition. Go to Sales tab and lookup Site, Item Class, and Sub-Class if maintained.
2.1. If not maintained, advise user to maintain table.
2.2. Else, contact JSI for assistance.

Customer A/R Status: Issue with Retuned Check (RC)

2011-07-11T17:14:00.000-07:00

Issue:
Customer A/R status is incorrect due to issue with RC transaction. Entry is erroneous due to transaction code UNO is not removed from the report.

Cause:
The cause of this error is due to the old patch being used. This has been corrected on the current patch.

Fix:
1. Run script below to check for other RC issues:
SELECT a.cust_code, a.trans_code, a.doc_no
FROM a_open_item AS a WITH(NOLOCK)
INNER JOIN a_open_itm_hist AS b WITH(NOLOCK)
ON a.company_code = b.company_code
AND a.cust_code = b.cust_code
AND a.trans_code = b.trans_code
AND a.doc_no = b.doc_no
INNER JOIN a_open_payment AS c WITH(NOLOCK)
ON c.company_code = b.company_code
AND c.cust_code = b.cust_code
AND c.payment_doc_no = b.doc_no
WHERE a.trans_code = (‘UNO’)
AND b.trans_code = (‘UNO’)
AND c.payment_trans_code = ‘OR’
AND c.cleared_flg = ‘Y’
AND c.returned_chk_flg = ‘Y’
2. Take note of the document numbers with issue then perform script below:
– Declare variables
declare
@doc_no as char(8),
@trans_uno as char(3),
@trans_unp as char(3),
@trans_or as char(3)
– Initialize values
set @doc_no = ‘doc_no with issue’
set @trans_uno = ‘UNO’
set @trans_unp = ‘UNP’
set @trans_or = ‘OR’
– Delete record from a_open_item
delete from a_open_item
where doc_no = @doc_no and trans_code = @trans_uno
– Delete record from a_open_itm_hist
delete from a_open_itm_hist
where doc_no = @doc_no and trans_code in (@trans_uno, @trans_unp)
– Update record from a_open_payment
update a_open_payment
set unapplied_amt = ’0.00′
where payment_doc_no = @doc_no and payment_trans_code = @trans_or

OEB-CM Processing: Error - 'Customer is currently being processed...'

2011-07-11T02:33:00.000-07:00

Issue:
User receives message ‘Customer is currently being processed in Accounts Receivable. Please wait.’ when saving CM Processing.

Cause:
This issue occurs if there is another user using the same customer in Batch Processing. JSI has released patch to address this issue. The message is still there but it now shows which user_id is currently doing a transaction for the customer. This way, the user performing OEB-CM Processing is aware on who uses the customer and instead of contacting IT, he/she would contact the department.

There are times when user performing Batch processing is complete but the person performing CM Processing is still seeing the message. For some reason, the record for the customer in table t_acr_lock is not cleared. If this is the case, perform fix below.

Fix:

Check t_acr_lock for customer with issue to identify which user uses the customer.
Notify user if he/she is currently doing transaction for the customer.
If user is doing transaction, wait for feedback once done.
If user confirmed that no transactions are done, proceed to step 4.
Update t_acr_lock. Delete record for customer with problem.
Notify requestor that he/she could now perform CM Processing.

AR Batch OR Processing: Transaction Deadlocked

2011-07-10T21:52:00.000-07:00

Issue:
User receives message: ‘Transaction (Process ID ) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.’ when performing AR Batch OR Processing.

Cause:
This issue is caused by intermittent connection of ERIC possibly due to the main ERIC module was terminated abnormally.

Fix:
Have user close/exit all ERIC modules then have him login again to refresh ERIC connection.

DR Printing: Nothing to process!

2011-07-10T04:23:00.000-07:00

Issue:
User is unable to print DR due to error ‘Nothing to Process! Some items might be on hold or not yet delivered.’

Cause:
This is caused when one ERIC user is also accessing the SO or the SO is locked in t_oeb_lock table.

Fix:
1. Check t_oeb_lock table for user using the SO number. Take note of the user_id
2. Determine corresponding first and last name of user_id in pc_user_def.
3. Check s_user_registration if user is logged in.
4.1. If user is logged in, notify user to logoff then log back in to ERIC.
4.2. Else, remove entry for user in t_oeb_lock.

Receiving: Error retrieving IM/GL Account Record of [Item Code]

2011-07-10T03:57:00.000-07:00

Issue:
User encountered error ‘Error retrieving IM/GL account record of <item code w/ issue>’ when saving Stock Transfer transaction.

Cause:
This error appears when the site, item class, and sub-class is not maintained in IM/GL Account code definition table.

Solution:
Advise user to have IM/GL Account code definition table maintained. They could ask Lyn so she could inform accounting for table maintenance.