Profile
|
Description
|
Default
|
Options
|
Recommended
Change Levels
|
GMF: Actual Costing
Maximum Iteration Limit for Circular Reference
|
This sets the
maximum number of iterations
|
200
|
200
|
Site, Applications
|
GMF: Actual Cost
Process Error Limit
|
Defines the number
of AC Process generated errors at which the system aborts.
|
1000
|
Any valid number
|
Site, Applications,
Responsibility, User
|
GMF: Commit Count
in Accounting Pre-Processor
|
This profile option
lets you indicate the frequency of database commits within the Pre-Processor
program. A very large value requires a large Rollback Segment space but performs
a little faster. A small value requires less Rollback Segment space, but performs a little
slower because of frequent commits and memory allocations. The default value
of 1000 suffices for normal processing
|
1000
|
-
|
Site
|
GMF: Copy Item
Costs - Copy Recipe Information to Target
|
Use this profile
option to copy over recipe validity rule information to the target periods using
the copy item costs program. The profile option can have a value of either
Yes or No. If the value is set to Yes, then only the recipe validity rules
are copied. The profile value is set to No at the site level.
|
N
|
Y = Copy item costs
and recipe information to target
N = Do not copy
item costs and recipe information to targetd
|
Site, Application,
Responsibility, User
|
GMF: Cost
Allocation Factor Calculation
|
This profile option
lets you specify the method for the calculation of batch cost allocation. If you
select Static, then the application calculates the batch cost allocations based
on the cost allocation factor defined for each product in the production
batch formula. This is how the costs were allocated before this enhancement.
If you select Dynamic, then the
application calculates the batch cost allocations as a ratio of actual quantity
of each product produced to the total production batch output quantity
|
-
|
Static
Dynamic
|
Site, Application,
Responsibility
|
GMF: Cost Process
Message Level Threshold
|
The Actual Cost
process generates a lot of error and warning messages during
processing and in a
high volume of data environment. The threshold value indicates the type of
error messages to log by the process. The valid values are Diagnostic
Messages, Warnings, Data Setup Errors, Errors impacting Cost, and Fatal or
Internal System errors. It is recommended that you set this to Warnings so
that any mistakes can be corrected before further processing.
|
Diagnostic Messages
|
Diagnostic Messages
Warnings
Data Setup Errors
Errors impacting
Cost
Fatal or Internal
System Errors
|
Site
|
GMF: Costing
Tolerance Percent
|
This profile option is used to specify tolerance percentage for circular reference batches in Actual Costing. It fixes the percentage of the difference in cost between iterations whether or not the costs are converged. For example, if the tolerance percent is set as 0.01%, then during the iterative calculation, if the prior iteration and current iteration produce results that are within 0.01%, then costs are considered as converged. |
0.000001
|
Tolerance percent
value
|
Site, Application,
Responsibility, User
|
GMF: Delete Ingredient
Cost When No Effectivity Found
|
This profile option
lets you specify whether the Cost Rollup process must delete or not delete the
ingredient costs if no valid validity rules are found.
|
Yes
|
No = Does not
delete the ingredient costs.
Yes = Deletes the
ingredient costs when no effectivity is found.
|
Site
|
GMF: Exclude
Invoices Which Have No Receipts
|
If this profile
option is set to 1, then the Actual Cost process ignores invoices that do not
have receipts in the period for which the cost is being calculated. If set to
0, then the Actual Cost process does not exclude invoices that have no
receipts.
|
0
|
1
0
|
Site, Application,
Responsibility, User
|
GMF: Exclude
Negative Inventory Balance
|
Use this profile
option to ignore zero or negative beginning on-hand inventory during PMAC cost
calculations. If the profile value is set to 0, then the actual cost process includes negative
or zero onhand quantity in PMAC cost calculations. If the profile
value is set to 1,
then during the raw material and product cost calculations, the previous period
balance and previous period component costs are considered zero for items having zero
or negative beginning on-hand inventory quantity.
|
0
|
1
0
|
Site, Application,
Responsibility, User
|
GMF: Include Drop
Shipments in Actual Cost
|
This profile option
determines whether drop shipments are included in Actual Cost calculations. The
default is Yes. Set the profile to No to ignore drop shipments and only include other
transactions in actual cost. It is recommended that you set this profile to Yes.
|
Yes
|
Yes
No
|
Site
|
GMF: Include
Inventory Movements in Actual Cost
|
This profile option
lets you control the inclusion of inventory movements in the Actual Cost
calculation process. It can be set to Yes or No. The default is No. If it is
set to Yes, then the Actual
Cost process includes inventory movements in the cost calculation. If it
is set to No, then
inventory movements are not considered in the cost calculation.
|
No
|
Yes
No
|
Site, Applications,
Responsibility
|
GMF: Include
Inventory Transfers in Actual Cost
|
This profile option
determines whether Inventory Transfers are included in Actual Cost calculations. The
default value is Yes. Set the profile to No, if you want to ignore transfers and only
include other transactions in actual cost. It is recommended that you
set this profile to
Yes.
|
Yes
|
Yes
No
|
Site
|
GMF: Include
Invoices in Actual Cost
|
This profile option
controls the inclusion of invoice transactions in the Actual Cost calculation
process. This profile option can have a value of either 1 or 0. The default
value is 1. If the
profile value is set to 1, then the Actual Cost process includes invoice transactions in
cost calculations. If the profile value is set to 0, then the invoice
transactions are
not considered in the cost calculations.
|
1
|
1 = Include
invoices in cost calculation
0 = Exclude
invoices in cost calculation
|
Site
|
GMF: Include
Production Batches in Actual Cost
|
This profile option
indicates whether production batches are considered in actual cost calculations. The
default value is Yes. The profile is for troubleshooting and debugging
purposes only. Set
to No only if requested by the Oracle Support. It is recommended that you set this
profile to Yes.
|
Yes
|
Yes
No
|
Site
|
GMF: Include
Receipts in Actual Cost
|
This profile option
determines whether Receipts are included in Actual Cost
calculations. The
default value is Yes. Set the value to No, only if you want to use invoices and
transfers for actual costs. It is recommended that you set this value to Yes.
|
Yes
|
Yes
No
|
Site
|
GMF: Log All
Subledger Variances
|
This profile option
calculates variances for all of the three variance types (Scale to Plan, Scale to Actual,
Aggregate) and stores them in a separate table for analysis. Refer to
"Accounting
Setup and Account Processes and Distribution" topics in this guide for more details.
|
No
|
No = The subledger variances are not logged to the separate table and only one variance type is calculated as specified in the profile option, GMF: Subledger Variance Type.
Yes = The Subledger
process calculates variances for all of the three variance types
(Scale to Plan,
Scale to Actual, Aggregate) and stores them in a separate table.
|
Site
|
GMF: Log Frozen
Error Messages in Cost Rollup
|
If an Item's cost
is already frozen by a final cost update, then Cost Rollup does not rollup the cost of
this item if run again, even if any of the ingredients or routing costs have changed. If
you set the profile to Yes, then the application logs a message that an item's cost was not
recalculated when it is frozen. The default value is No.
|
No
|
No
Yes
|
Site
|
GMF: Standard Cost
Rollup Error Limit
|
Defines the number
of Rollup generated errors at which the system aborts.
|
1000
|
Any valid number
|
Site, Applications,
Responsibility, User
|
GMF: Subledger
Variance Type
|
This profile option
contains the variance type which the Subledger process uses to calculate and post
variances for the production transactions. Specify any of the above
mentioned variance
types as a value. Refer to "Accounting Setup and Account Processes and
Distribution" topics in this guide for more details.
|
Scale to Plan
|
Scale to Plan =
Scale the costing formula to planned quantity of the primary product in the
batch and compare with the actual batch.
Scale to Actual =
Scale the costing formula to actual quantity of the primary product in the
batch and compare with the actual batch.
Aggregate =
Calculates Aggregate type variances.
|
Site
|
GMF: Use Cost Alloc
Factor in Lot Costing
|
The Lot Cost
Process uses the actual quantities yielded or transferred at each
production setup to
arrive at the cost allocations for co-products. Set this profile to Yes,
if you want to use
the default cost allocation factor set up for the batch products. The
default value is
No.
|
No
|
No
Yes
|
Site
|
GMF: Use Only
Costing Validity Rules for Cost Rollup
|
Determines what
validity rules to use during the Cost Rollup process. This affects cost calculations. If
the profile value is set to 0, then costing validity rules are used if available.
Otherwise, the Cost Rollup process uses production validity rules. If the profile value is
set to 1, then only costing validity rules are used.
|
0
|
0 or 1
|
Site
|
GMF: Use PO
Acquisition Costs for Invoice
|
It is not possible
to enter the actual freight and other costs at the time of invoicing. If the profile
is set to Yes, then Actual Cost picks up the estimated freight and other
charges entered at the time of creating a purchase order as applicable to the
invoice as well. The default value is No. If the value is set to No, then the
Actual Cost does not include these charges.
|
No
|
No
Yes
|
Site
|
GMF: Use Substitute
Items in Standard Costing
|
This profile option
lets you specify whether to use the original formula item or the substitute item in
the product cost calculations. If you select No, then the application uses
the original item for cost calculations. This is the default value. If you
select Yes, use period start date as effective date, then the application
uses the substitute item. The most appropriate substitute item is determined
using the costing period start date as the effective date. The
costing period start date must be within the item substitution's
effective start and
end date as set up in the OPM Product Development application. If you select Yes, use
period end date as effective date, then the application uses the substitute
item. The most appropriate substitute item is determined using the costing period
end date as the effective date. The costing period end date must be within
the item substitution's effective start and end date as set up in the OPM
Product Development
application.
|
No
|
No
Yes, use period
start date as effective date
Yes, use period end
date as effective date
|
Site, Application,
Responsibility
|
Oracle Financials Management Handbook. A comprehensive guide which contains functional and technical information: documents, articles, notes, SQL scripts and references in Oracle e-Business Suite Financial modules.
Setting Profile Options
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment