Last Login: October 3, 2023 11:20 AM CST Switch to Cloud Support MEIHUA (Available) (0) Contact Us Help

Dashboard Knowledge Service Requests

Give Feedback...
Copyright (c) 2023, Oracle. All rights reserved. Oracle Confidential.

Fusion CST: Costing Period Close Processing - Troubleshooting Periods Close Exceptions Report To Bottom
(Doc ID 2285213.1)

In this Document Was this document helpfu

Purpose Yes
Troubleshooting Steps No

Overview
Document Details
Managing Cost Accounting Periods
Documentation Type:
Status: TROUBLESHOOT
Troubleshooting
Last PUBLISHED
Cannot view validations-> Page shows blank Major
15-May-2020
Validation: Cost Accounting Pending Update:
15-Jun-2023
Validation : Pending Revenue Recognition : Last
Update:
Pending Cost Processing
List of Validations
Related Products

How to Close Costing Period with Pending Validations Oracle Fusion Cost
Management
Logging Service Request with Oracle for period close issues
References
Information Centers
Information Center:
APPLIES TO: Fusion Applications
Supply Chain
Oracle Fusion Cost Management - Version 11.1.11.1.0 and later Management [108.2]
Information in this document applies to any platform.

Document References
PURPOSE
No References available
for this document.
The Purpose of this document is to troubleshoot and latest track issues related to period end process for Fusion Cost
Management
Recently Viewed
This document was last reviewed on 8th March 2018
FUSION: CST: Manage
Latest changes in one line : List of Validations are revised from Release 11.13.11.0 or Release 1317D , find more details on latest Period End [1302747.1]
changes section on this note.
Fusion Global Financials:
Latest Major Update Date : August 2018 ERP Period Close
Technical Brief with
Runbook Considerations
TROUBLESHOOTING STEPS [2506148.1]
Information Center:
Overview Fusion Financials
Troubleshooting
Oracle Fusion Cost Management's period-end functionality is incorporated into the Manage Period End activity. This activity [1368842.2]
allows cost accountants to configure period-end validations, review any validation exceptions, and open/close cost periods Information Center:
accordingly. Period-end processing is meant to ensure statutory compliance and provide a good perspective of a company's Fusion Receivables
financial situation. Troubleshooting Guide
[1381399.2]
While based on a fiscal calender, costing periods in Fusion are separate from those in General Ledger. These periods primarily
Close
providePending:
a referencePeriod can be marked
for perpetual averageascosting
Close pending by thePeriods
calculations. users. are
Themaintained
period would be closed
at the for all new transactions
Cost Organization / Cost Book level, Common Problems and
(similar to Closed
and multiple status).
periods No open
may be validations would
for each be performed when
Organization/Book a period Cost
combination. is marked as Close
accountants Pending.
may The user validations
use period-end can then to Solutions Fusion
make
resolveallopen
necessary corrections
transactions, and adjustments
providing and then
a more efficient markprocess
reporting the period as Closed
before closingor Permanently
the period. Closed. Receivables
Closed: All the validations defined at the cost organization-cost book level are checked when the period status is set to close. Troubleshooting Guide
Period is closed
Configuring for processing
Period-End transactions. Status can be reverted to ‘Open’ or changed to ‘Permanently Closed’.
Validations Month End [1390469.1]
Permanently Closed: Period is closed for processing of new transactions. This is an irreversible process and the period status Show More
Period-End
cannot validations are set at the Cost Organization / Cost Book level. The Manage Cost Organization Relationships UI (as
be changed.
shown below). Cost accountants can choose to perform each validation at initial or final period close, and they may also choose
to ignore errors from one or more validation types.

Maintaining Cost accounting period status enable you to monitor the timing of transaction processing in costing, and to perform
validations in preparation for period close.
Managing Cost Accounting Periods
Cost periods are associated with combination of cost organization and cost book. When you associate a cost organization with a
Cost accountants
cost book, can
you also execute
define the period-end validation
cost accounting periodand open/close
calendar periods
and other through the Manage Cost Accounting Periods UI
attributes.

Every period
Only Cost will that
Books haveare
onelinked
of thetofollowing
a Primarystatuses:
Ledger are eligible to be closed.

Never Opened:
Period Close No transaction
Exceptions Report Cancanbebesubmitted
processedanyin this
timeperiod
duringstatus. Statusincan
the period be changed
preparation to ‘Open’. This
for upcoming would
period closebeevent.
the You
default
can runstatus for all periods
this program as soon
for specific as a Book
validations is associated
or all validations with a Cost Organization.
enabled.
Open: All transactions are allowed in this status. Status can be changed to ‘Closed’ or ‘Permanently Closed’. The system should
To helpthe
check with the list
setting foroftherecords failing
maximum under of
number a specific validation,
concurrent periodsuse theand
open number hyperlink.
if its within The list of allow
the threshold, records
thecan be exported
period to be
for further analysis. ensure to select all columns when exporting via view->all columns under actions.
opened.
While based on a fiscal calender, costing periods in Fusion are separate from those in General Ledger. These periods primarily
Close
providePending:
a referencePeriod can be marked
for perpetual averageascosting
Close pending by thePeriods
calculations. users. are
Themaintained
period would be closed
at the for all new transactions
Cost Organization / Cost Book level, Common Problems and
(similar
and to Closed
multiple status).
periods No open
may be validations would
for each be performed when
Organization/Book a period Cost
combination. is marked as Close
accountants Pending.
may The user validations
use period-end can then to Solutions Fusion
make
resolveallopen
necessary corrections
transactions, and adjustments
providing and then
a more efficient markprocess
reporting the period as Closed
before closingor Permanently
the period. Closed. Receivables
Closed: All the validations defined at the cost organization-cost book level are checked when the period status is set to close. Troubleshooting Guide
Period is closed
Configuring for processing
Period-End transactions. Status can be reverted to ‘Open’ or changed to ‘Permanently Closed’.
Validations Month End [1390469.1]
Permanently Closed: Period is closed for processing of new transactions. This is an irreversible process and the period status Show More
Period-End
cannot validations are set at the Cost Organization / Cost Book level. The Manage Cost Organization Relationships UI (as
be changed.
shown below). Cost accountants can choose to perform each validation at initial or final period close, and they may also choose
to ignore errors from one or more validation types.

Maintaining Cost accounting period status enable you to monitor the timing of transaction processing in costing, and to perform
validations in preparation for period close.
Managing Cost Accounting Periods
Cost periods are associated with combination of cost organization and cost book. When you associate a cost organization with a
Cost accountants
cost book, can
you also execute
define the period-end validation
cost accounting periodand open/close
calendar periods
and other through the Manage Cost Accounting Periods UI
attributes.
Every period
Only Cost will that
Books haveare
onelinked
of thetofollowing
a Primarystatuses:
Ledger are eligible to be closed.
Never Opened:
Period Close No transaction
Exceptions Report Cancanbebesubmitted
processedanyin this
timeperiod
duringstatus. Statusincan
the period be changed
preparation to ‘Open’. This
for upcoming would
period closebeevent.
the You
default
can runstatus for all periods
this program as soon
for specific as a Book
validations is associated
or all validations with a Cost Organization.
enabled.
Open: All transactions are allowed in this status. Status can be changed to ‘Closed’ or ‘Permanently Closed’. The system should
check
To helpthe setting
with forofthe
the list maximum
records number
failing under of concurrent
a specific periodsuse
validation, open
theand if its within
number the threshold,
hyperlink. The list of allow thecan
records period to be
be exported
opened.
for further analysis. ensure to select all columns when exporting via view->all columns under actions.

Documentation

Please find reports related documentation here @ docs.oracle.com for SCM

Troubleshooting

Most of the issues with Period Close validations are resolved when appropriate expected actions are taken care when closing a
costing period.

Some of the issues of Period Close Exceptions process is with validations not showing correct records. If this is the case, the
general resolution to unblock period close is to ignore these validations on the cost book setup.

For valid validation failures as well , the validations can be ignored on the cost book and the transactions can be swept to next
periods if the business is okay with this approach.

Below discussed are some of the popular issues reported with Period Close Processing in Costing.

Cannot view validations-> Page shows blank

This is a known issue and is being worked by development as low priority bug.
Workaround for this is to go to "period Details" page by clicking the period details button and view exceptions from there.

Validation: Cost Accounting Pending

Navigate to Review Cost Accounting Distributions UI, search for the transaction reported as validation failure and check the
following things

1) what is the status of the "Accounting Status" column

2) What is the status of the Cost Status column

3) Go to the "Journal Entries" tab and check if journals are visible and no error is reported

If any of these validations fail, refer to the Note 2274517.1 Troubleshooting Sub-ledger Create Accounting program for Cost
Management Application

Validation : Pending Revenue Recognition :

Navigate to Review Cost Accounting Distributions UI, search for the transaction reported as validation failure and check the
following things
Generic Queries for Validation Program:
1) what is cost status for the transaction related to the sales orders and the corresponding Sales Order Ship Transaction type

2)1.For
In thedetails of check
distributions errored transactions:
if COGS distributions are created and successfully transferred to GL
select * from cst_transaction_errors where cp_error_id in (
3)SELECT
Refer tocp_error_id FROM cst_cp_errors
the note and confirm if this is not the WHERE request_id
issue Costing Period =
Close Exceptions Shows Pending Cogs Events Validation
&periodclosevalidationprogram_Request_ID))
Failure Note 2284784.1
2.For list of errors for the run :
4)SELECT
Check the Transaction Date of the Validations by exporting the list of rows with this validation failure and view -> all columns.
* FROM cst_cp_errors WHERE request_id =
Check if the transaction date is within the period end date you are trying to close. If it is beyond, ignore the validation.
&periodclosevalidationprogram_Request_ID';

The followingClose
3.Period query Actions
can be used
: to identify Cogs pending Sales Orders that are stopping from period close :
select * from cst_period_close_actions order by creation_date desc;
Query to run for cogs validation :
4. Transaction details for the errors, depends on the validation type:
select
For Cogs* from cst_transactions
validation error : ct, cst_transaction_errors
cte where
select cte.transaction_id=ct.transaction_id
* from and cte.cp_error_id=
cst_cogs_transactions where transaction_id
&periodclosevalidationprogram_Request_ID';
in ( select TRANSACTION_ID from cst_transaction_errors where cp_error_id
in (
select * from cst_cogs_transactions cct , cst_transaction_errors
SELECT cp_error_id FROM cst_cp_errors WHERE request_id =
cte where cte.transaction_id=cct.transaction_id and cte.cp_error_id=
&periodclosevalidationprogram_Request_ID))
&periodclosevalidationprogram_Request_ID';

select * from cst_inv_transactions cct , cst_transaction_errors

cte where cte.transaction_id=ct.transaction_id and cte.cp_error_id=
Generic Queries for Validation Program:
1) what is cost status for the transaction related to the sales orders and the corresponding Sales Order Ship Transaction type

2)1.For
In thedetails of check
distributions errored transactions:
if COGS distributions are created and successfully transferred to GL
select * from cst_transaction_errors where cp_error_id in (
3)SELECT
Refer tocp_error_id FROM cst_cp_errors
the note and confirm if this is not the WHERE request_id
issue Costing Period =
Close Exceptions Shows Pending Cogs Events Validation
&periodclosevalidationprogram_Request_ID))
Failure Note 2284784.1
2.For list of errors for the run :
4)SELECT
Check the Transaction Date of the Validations by exporting the list of rows with this validation failure and view -> all columns.
* FROM cst_cp_errors WHERE request_id =
Check if the transaction date is within the period end date you are trying to close. If it is beyond, ignore the validation.
&periodclosevalidationprogram_Request_ID';

The followingClose
3.Period query Actions
can be used
: to identify Cogs pending Sales Orders that are stopping from period close :
select * from cst_period_close_actions order by creation_date desc;
Query to run for cogs validation :
4. Transaction details for the errors, depends on the validation type:
select
For Cogs* from cst_transactions
validation error : ct, cst_transaction_errors
cte where
select cte.transaction_id=ct.transaction_id
* from and cte.cp_error_id=
cst_cogs_transactions where transaction_id
&periodclosevalidationprogram_Request_ID';
in ( select TRANSACTION_ID from cst_transaction_errors where cp_error_id
in (
select * from cst_cogs_transactions cct , cst_transaction_errors
SELECT cp_error_id FROM cst_cp_errors WHERE request_id =
cte where cte.transaction_id=cct.transaction_id and cte.cp_error_id=
&periodclosevalidationprogram_Request_ID))
&periodclosevalidationprogram_Request_ID';

select * from cst_inv_transactions cct , cst_transaction_errors

cte where cte.transaction_id=ct.transaction_id and cte.cp_error_id=
&periodclosevalidationprogram_Request_ID';

5. CST SQL TIMINGS:

select * from cst_sql_timings where request_id =

&periodclosevalidationprogram_Request_ID order
by creation_date desc;

6. period status for costing :

select * from cst_period_statuses where period_name='&period_name'

7. All pending transactions :

8. SELECT t.* FROM cst_transactions t,CST_INV_TRANSACTIONS cit

WHERE NVL( t.cost_date, t.transaction_date) <= to_timestamp('2018-01-31
23:59:59.0','YYYY-MM-DD HH24.mi.SS.FF')
AND t.cost_org_id = &from program log
AND t.cst_inv_transaction_id
= cit.cst_inv_transaction_id
AND t.cost_book_id = &from program log
AND ( (t.posted_flag NOT
IN ('Y', 'E', 'X'))
OR (t.transaction_id IN
(SELECT transaction_id
FROM cst_transaction_overheads
WHERE posted_flag = 'N'
)) );

Sample period end date given on this query is : '2018-01-31 23:59:59.0',

you can change this according to your period end date for the period.

In above SQLs the request id input is the period close program request id that is submitted when you click on 'Run Validations'
in Manage Cost Accounting Periods UI or when you attempt to close cost period this job is submitted automatically .

Pending Cost Processing

1) Subinventory Transfers as Pending

Pick transactions within same validation unit are not stamped correct and hence show up as pending. Bug 26757286 -
POSTED FLAG FOR SUB INVENTORY TRANSFERS IS STAMPING INCORRECTLY

SQL to identify such transactions :

and ct1.cost_status=''X''
and
select(ct1.base_txn_source_type_id, ct1.base_txn_action_id) in
ct.*, ''Y'' process_flag, to_char(sysdate,''YYYYMMDDHH24MISS'') RUN_ID
(select base_txn_source_type_id,
from cst_transactions base_txn_action_id
ct, cst_transactions ct1 from cst_txn_source_actions
where
where additional_processing_code
ct.cost_org_id = ct1.cost_org_id = ''TRANSFER'' and transfer_ship_rcpt_coeval =
''Y'')
and ct.cost_book_id = ct1.cost_book_id
and
and ct1.cost_transaction_type=''RECEIPT''
ct.base_txn_source_type_id=0 and ct.base_txn_action_id =16
';
and ct.cost_transaction_type=''ISSUE''
and ct.cost_status<>''X''
and ct.transfer_transaction_group_id =ct1.transaction_group_id
and ct1.cost_status=''X''
and (ct1.base_txn_source_type_id, ct1.base_txn_action_id) in
2) TIR TII chaining issue : Bug 28823583 - REVIEW COST ACCOUNTING DISTRIBUTIONS SHOWS "NOT PROCESSED" FOR
(select base_txn_source_type_id, base_txn_action_id from cst_txn_source_actions
SOME
whereTRANSACTIONS
additional_processing_code = ''TRANSFER'' and transfer_ship_rcpt_coeval =
''Y'')
Due to this bug Trade Intransit Issue transactions are stuck as not processed and show up on period validation failures.
and ct1.cost_transaction_type=''ISSUE''
union
select ct.*, ''Y'' process_flag, to_char(sysdate,''YYYYMMDDHH24MISS'') RUN_ID
from cst_transactions ct, cst_transactions ct1
where ct.cost_org_id = ct1.cost_org_id
List of Validations
and ct.cost_book_id = ct1.cost_book_id
and ct.base_txn_source_type_id=0 and ct.base_txn_action_id =15
The
andlist of validations have changed from Release 13 17D version. The changed validations are :
ct.cost_transaction_type=''RECEIPT''
and ct.cost_status<>''X''
List
andofct1.transfer_transaction_group_id
Period end Validations ( R13 + ) =ct.transaction_group_id Actions to Resolve these
 and ct1.cost_status=''X''
and
select(ct1.base_txn_source_type_id, ct1.base_txn_action_id) in
ct.*, ''Y'' process_flag, to_char(sysdate,''YYYYMMDDHH24MISS'') RUN_ID
(select base_txn_source_type_id,
from cst_transactions base_txn_action_id
ct, cst_transactions ct1 from cst_txn_source_actions
where
where additional_processing_code
ct.cost_org_id = ct1.cost_org_id = ''TRANSFER'' and transfer_ship_rcpt_coeval =
''Y'')
and ct.cost_book_id = ct1.cost_book_id
and
and ct1.cost_transaction_type=''RECEIPT''
ct.base_txn_source_type_id=0 and ct.base_txn_action_id =16
';
and ct.cost_transaction_type=''ISSUE''
and ct.cost_status<>''X''
and ct.transfer_transaction_group_id =ct1.transaction_group_id
and ct1.cost_status=''X''
and (ct1.base_txn_source_type_id, ct1.base_txn_action_id) in
2) TIR TII chaining issue : Bug 28823583 - REVIEW COST ACCOUNTING DISTRIBUTIONS SHOWS "NOT PROCESSED" FOR
(select base_txn_source_type_id, base_txn_action_id from cst_txn_source_actions
SOME
whereTRANSACTIONS
additional_processing_code = ''TRANSFER'' and transfer_ship_rcpt_coeval =
''Y'')
Due to this bug Trade Intransit Issue transactions are stuck as not processed and show up on period validation failures.
and ct1.cost_transaction_type=''ISSUE''
union
select ct.*, ''Y'' process_flag, to_char(sysdate,''YYYYMMDDHH24MISS'') RUN_ID
from cst_transactions ct, cst_transactions ct1
where ct.cost_org_id = ct1.cost_org_id
List of Validations
and ct.cost_book_id = ct1.cost_book_id
and ct.base_txn_source_type_id=0 and ct.base_txn_action_id =15
The
andlist of validations have changed from Release 13 17D version. The changed validations are :
ct.cost_transaction_type=''RECEIPT''
and ct.cost_status<>''X''
List
andofct1.transfer_transaction_group_id
Period end Validations ( R13 + ) =ct.transaction_group_id Actions to Resolve these

1. Pending Interface
- Records stuck in Costing Interface Tables - Look fo

2. Pending Pre-processing - Records are staged in Costing Interface but are not

- Look for Cost Processor logs for Errors

3. Pending Cost Processing

- Records in Error, transactions are staged, but canno

4. Pending Create Accounting

in Final Mode - Records are waiting to be processed to SLA by runn

5. Pending Revenue Recognition

- Records are pending to be interfaced from AR for
Events Import
Sales Order related Revenue transactions

- Work Orders are not closed or not WIP Close transa

6. Completed Work Orders
- Run Transfer Transactions from Production to Costi
Not Closed
- Look for WIP related errors for Close in Review Cos

"Transactions Errors" tab.

How to Close Costing Period with Pending Validations

1. Navigate to Setup and Maintenance -> Manage Cost Organization Relationships UI -> Cost Book Tab
If the information provided on this Note still does not help resolve log a service request with Oracle by choosing Component as
"Costing"
See on theend
the period Cloud subscription
validations service
section available
that allows to you
users under
to set Supply
validate Chain
action forGroup of Products.
each validation type.
Choose Sub-component
2. Set each as "Reports
of the validation that youand Processes"
want to ignore , change the action value from Error to Ignore.

3.REFERENCES
Save changes

4. Close Costing Period, system should not throw validation error and allow closing period with pending validations ignored.

5. All the ignored transactions will now be swept to new open costing period when Cost Processor is run with Cut of Date in new
open Costing period.

6. Revert
Didn't the
findchanges
what youtoare
Validation
looking Action
for? in the AskManage Cost Organization Relationships UI So these validations alert users in
in Community...
subsequent period close activities until the identified issues are resolved.
Related
7. Repeat the process for all subsequent periods if required and suggested by Support/ Development teams while the identified
Productsare being fixed . Check with the business on the strategy to handle such late processing of transactions and
bugs/issues
sweeping transactions toApplications
Oracle Fusion subsequent > periods
Supplyif Chain
the validations
Managementshown are Valid.
> Cost Management > Oracle Fusion Cost Management > Reports and Processes

Keywords
Logging Service Request with Oracle for period close issues
ACCOUNTING; CLOSED; COSTING; CREATE ACCOUNTING; ERROR; EVENT; MANAGE COST ACCOUNTING PERIODS; MANAGE PERIOD END; PENDING;
PERIOD STATUS; PROCESSING; REPORT; REVIEW COST ACCOUNTING DISTRIBUTIONS; SLA; TROUBLESHOOT; VALIDATE; VALIDATION ERROR; VALIDATIONS
1. Navigate to Setup and Maintenance -> Manage Cost Organization Relationships UI -> Cost Book Tab
If the information provided on this Note still does not help resolve log a service request with Oracle by choosing Component as
"Costing" on theend
See the period Cloud subscription
validations service
section available
that allows to you
users under
to set Supply
validate Chain
action forGroup of Products.
each validation type.
Choose Sub-component
2. Set each as "Reports
of the validation that youand Processes"
want to ignore , change the action value from Error to Ignore.

3.REFERENCES
Save changes

4. Close Costing Period, system should not throw validation error and allow closing period with pending validations ignored.

5. All the ignored transactions will now be swept to new open costing period when Cost Processor is run with Cut of Date in new
open Costing period.

6. Revert
Didn't the
findchanges
what youtoare
Validation
looking Action
for? in the AskManage Cost Organization Relationships UI So these validations alert users in
in Community...
subsequent period close activities until the identified issues are resolved.
Related
7. Repeat the process for all subsequent periods if required and suggested by Support/ Development teams while the identified
Productsare being fixed . Check with the business on the strategy to handle such late processing of transactions and
bugs/issues
sweeping transactions toApplications
Oracle Fusion subsequent > periods
Supplyif Chain
the validations
Managementshown are Valid.
> Cost Management > Oracle Fusion Cost Management > Reports and Processes

Keywords
Logging Service Request with Oracle for period close issues
ACCOUNTING; CLOSED; COSTING; CREATE ACCOUNTING; ERROR; EVENT; MANAGE COST ACCOUNTING PERIODS; MANAGE PERIOD END; PENDING;
PERIOD STATUS; PROCESSING; REPORT; REVIEW COST ACCOUNTING DISTRIBUTIONS; SLA; TROUBLESHOOT; VALIDATE; VALIDATION ERROR; VALIDATIONS

Back to Top
Copyright (c) 2023, Oracle. All rights reserved. Legal Notices and Terms of Use Privacy Statement