Setting up Line Details for Inventory Cost Type
After you have completed the general details for the ledger interface line details, the remaining information required is dependent on the Ledger Interface Value Type. A different set of information is required for each type, and this information is used in different ways. This topic covers the Inventory Costs type of ledger interface.
- Click the Inventory Cost tab only, then the front row of tabs containing Value, Analysis Suppression, and Transfer Data Codes. If you click the Transaction Value or Business Line Import tabs in error, the correct information is not displayed. Click the Inventory Cost tab again to display the correct information.
-
Specify this information:
- Value Label Value Type
-
On the journal lines generated, the value to be transferred can be split into four parts: base, transaction, and reporting values, and a memo value. Financials fourth and fifth currencies are not supported for ledger interfaces between Order Fulfilment and Financials.
The Value Type determines the format of each of the four inventory cost values being transferred. For example, standard cost, weighted average cost and so on. This is required to translate the value into the format required by Financials. You must take care to assign the appropriate value type to each value being transferred.
The valid options are:
- Without Units - a number without a Unit of Measure attached to it. For example, a percentage.
- With Units - a number with a Unit of Measure attached to it. For example, a quantity.
- Corresponds to Base Currency - a number that is the base currency.
- Corresponds to Transaction Currency - a number that is the transaction currency.
- Corresponds to Reporting or 2nd Base Currency - a number that is the reporting or 2nd base currency.
- Cost Indicator
-
Order Fulfillment calculates costs using different costing methods including standard costing, weighted average costing, and latest or actual costing. It also allows user defined costing methods to be defined.
Ledger Interface can transfer values of any of these costing methods. For the chosen costing method, you can transfer either the unit price or a cost value. This choice of costing method and type of value is determined by the cost indicator you choose.
If you select a Unit Cost indicator, the unit cost for the item is transferred, that is, the cost for one item only. For example, if you select Weighted Average Unit Cost as the cost indicator, the weighted average cost for one item is transferred as the value.
If you select either an Extended Cost or Line Cost indicator, a cost value is transferred.
- Line Costs - these are calculated and stored against the issues and receipts when the transaction takes place. The line cost is the total cost of the transaction quantity.
- Extended Costs - these are calculated by multiplying the transaction quantity by a unit cost (the unit cost is the cost of a single item). Unit costs are calculated and stored against the issues and receipts when the transaction takes place (line cost divided by quantity). Unit costs are also stored against the item. When defining the Ledger Interface you can choose which unit cost is used to calculate the Extended Cost.
You should consider the following when setting these indicators:
- The costs on the issue or receipt (line cost and unit cost) are those which are effective at the time of the transaction, or were specific to that transaction.
- Extended costs are calculated using the cost which is effective at the time of the posting. If this is the standard or weighted average cost from the item, this may have changed since the transaction took place.
- The process of calculating extended costs is: (line costs divided by transaction quantity) multiplied by the same transaction quantity. This may result in rounding errors where items have a small unit cost.
- If an organization is dealing with low value goods and latest costs, you should consider using line costs as it is more accurate because it takes the exact value from the transaction. If extended costs are used, rounding errors may have been introduced when calculating the unit cost.
- Cost Source
-
Select Item to use the latest unit cost held for the item in the calculations. Select Inventory to use the unit cost held on the inventory issue or receipt transactions in the cost calculations.
This choice may depend on when the cost values on the Item are updated.
If a Unit Cost Indicator is selected, the Cost Source must be Item.
- Cost Type Code
- The Cost Type Code identifies the type of cost to use on this Ledger Interface Line. This is only required if you wish to split the total cost across different Financials transactions. For example, if you have defined cost types for Materials, Labour and Overhead costs you might want to post these costs individually to separate Financials accounts. If no cost type code is defined, then all cost types are summed together.
- User Defined Cost Def'n Code
- The user defined costing method to be used. This is required if you select a User Defined Cost Indicator, for example, UD Extended Cost.
- Preset Analysis Code
- For each of the ten analysis dimension codes on the journal, you can specify where the analysis code is derived from.
- Suppress OR Replace with
- Select Suppress if no analysis code is to be entered in the journal. Select Replace to enter the value as an analysis code.
- If Suppress or Replace are not entered, the Analysis Mapping to Ledger (ANM) settings which define where the analysis code is derived from, are checked. The system uses the Business Definition Type setting of Issues or Receipts, if this transaction is linked to an issue or receipt.
-
The Transfer Data Code options allow you to transfer selected
field values from the Order Fulfilment source transaction into the Transaction
Date and Transaction Reference fields on the Financials transaction. If you
choose to transfer details into either of these fields and you have chosen to
balance journals by either of these fields, you must ensure that these transfer
options will not prevent the journal balancing. For example, if the Post Balance
By option on the Ledger Interface header is set to Transaction Reference, and
one of the Transfer Data Code options transfers different transaction reference
values onto each journal line, the journal will not balance.
- Transaction Date
- A date from the Order Fulfilment transaction that is to be transferred to the Transaction Date field on the generated journal.
- Journal Source
- A field from the Order Fulfilment transaction that is to be transferred to the Journal Source field on the generated journal.
- Transaction Reference
- A reference number field from the Order Fulfilment transaction that is to be transferred to the Transaction Reference field on the generated journal.
- Description
- A field from the Order Fulfilment transaction that is to be transferred to the Description field on the generated journal.
- Save your changes.