In this Document

Applies to:

Symptoms

When running Create Accounting - Cost Management process, the following error is generated at the Subledger Accounting Program Report:

Error
------  

Steps to Reproduce
------------------------
1. Connect to General Ledger Super User Responsibility.
2. Go to General Ledger>Create a primary and secondary ledger.
3. Go to General Ledger>Create mapping of accounts between primary and secondary ledgers.
4. Review Doc ID 788666.1 for setting up PLA.
5. Connect to Purchasing Super User Responsibility.
6. Go to Purchasing>Enter a PO and receive and deliver to Inventory.
7. Connect to Cost Management - SLA Responsibility.
8. Go to Request>Submit Request>Run Create Accounting - Cost Management Process.
9. Error is generated at the Subledger Accounting Program Report.

Changes

Cause

Several causes might generate this situation:

  1- Invalid Account due to setup issue
        The invalid account is due to user setup to use standard costing in PJM organization which is not supported by AX in 11i, the ER being considered is
        described in Bug 4443605 and Bug 9651648
 
        Bug 9651648 - EVALUATION TO ENABLE PROJECT COST CATEGORY ACCOUNT IN STANDARD COSTING
        Bug 9668596 - ERR 95353 CREATE ACCOUNTING WAS UNABLE TO DERIVE ACCOUNTING CODE COMBINATION
        Bug 9651648 - EVALUATION TO ENABLE PROJECT COST CATEGORY ACCOUNT IN STANDARD COSTING

   2- For WIP Transactions, rate_variance Account is not defined for Resource (Data Fix required)
        For the resources, rate_variance account is not defined. As a result against purchase variance or Rate variance A/C, the reference account value is -1

        This is explained in the following bug:
        BUG 10212729 - DATAFIX FOR ERROR NUMBER 95353

   3- For WIP Cost_Update_Adjustments Transactions, Standard Cost Variance account was missing
        Standard Cost Variance account was missing in the setup in WIP Accounting Classes Form. In wip_transaction_accounts the REFERENCE_ACCOUNT='-1' for  ACCOUNTING_LINE_TYPE=2;

Solution

  Please proceed in a Test Instance first, where this situation is replicated

1. Invalid Account due to setup issue

  To implement the solution, please execute the following steps:

        1. Download and review the readme and pre-requisites for Patch.10244514:R12.BOM.C.

        2. Ensure that you have taken a backup of your system before applying the recommended patch.

        3. Apply the patch in a test environment.

        4. Confirm the following file versions:

               bom patch/115/odf cstcxla.odf 120.67.12010000.23
               bom patch/115/sql CSTACDPB.pls 120.64.12010000.13
               bom patch/115/sql CSTAPBRB.pls 120.48.12010000.9
               bom patch/115/sql CSTPEACB.pls 120.32.12010000.18
               bom patch/115/sql CSTPPCCB.pls 120.17.12010000.11
               bom patch/115/sql CSTSCHKB.pls 120.1.12010000.2
               bom patch/115/sql CSTVXLAB.pls 120.43.12010000.13
              
               You can use a command like the following:
               strings -a $BOM_TOP/patch/115/sql/filename |grep '$Header'

        5. Retest the issue.

        6. Migrate the solution as appropriate to other environments.

2. For WIP Transactions, rate_variance Account is not defined for Resource (Data Fix required)

  Please log a Service Request in order to provide a datafix for resolving this situation. Upload the following information in a xls file with column names:

        1.
               SELECT *
               FROM wip_transaction_accounts wta
               WHERE wta.reference_account < 0;

        2.
               SELECT *
               FROM wip_transaction_accounts wta,
               cst_organization_definitions cod
               WHERE wta.organization_id = cod.organization_id
               AND wta.organization_id = &org_id
               AND NOT EXISTS
               (SELECT code_combination_id
               FROM gl_code_combinations gcc
               WHERE gcc.chart_of_accounts_id = cod.chart_of_accounts_id
               AND wta.reference_account = gcc.code_combination_id);

       

3. For WIP Cost_Update_Adjustments Transactions, Standard Cost Variance account was missing

  To implement the solution, please execute the following steps:

  Run the following datafx in a TEST instance where issue is replicated:
 
        1. Make a backup of wip_transaction_accounts

        2. Run datafix itself:

               UPDATE wip_transaction_accounts
               set REFERENCE_ACCOUNT=&correct_COST_UPDATE_ADJUSTMENT_account
               where transaction_id = &affected transaction
               and ACCOUNTING_LINE_TYPE=2
               and REFERENCE_ACCOUNT=-1;

               commit;

                  To Identify the account, Review (Doc ID 400088.1) How To Determine The DISTRIBUTION_ACCOUNT_ID For Inventory Datafix Scripts
                  Also, Run
                    
                  SELECT mta.organization_id organization_id,
                  mta.reference_account acct,
                  mta.accounting_line_type alt,
                  ml.meaning accounting_line_type, sum(mta.base_transaction_value)
                  FROM wip_transaction_accounts mta, mfg_lookups ml
                  WHERE reference_account = &&acct_id
                  and ml.lookup_type = 'CST_ACCOUNTING_LINE_TYPE'
                  and ml.lookup_code = mta.accounting_line_type
                  GROUP BY mta.organization_id , mta.reference_account , mta.accounting_line_type , ml.meaning

                  To identify the "affected transaction", run and review the Subledger Period Close Exceptions Report output

        3. Make sure customer populates the Standard Cost Variance Account in the setup in WIP Accounting Classes Form (for the future transactions)

        4. Then re-run Create Accounting - Cost Management program.