, , , ,

Key Flexfields in Oracle E-Business Suite

The Oracle E-Business Suite products provide many key flexfields as integral parts of the products.

Note: Do not modify the registration of any key flexfield supplied with Oracle E-Business Suite. Doing so can cause serious application errors.

Key Flexfields by Flexfield Name

Here is a table listing many of the key flexfields in Oracle E-Business Suite, ordered by the name of the key flexfield.

Name Code Owning Application
Account Aliases MDSP Oracle Inventory
Accounting Flexfield GL# Oracle General Ledger
Activity Flexfield FEAC Enterprise Performance Foundation
AHL Route AHLR Complex Maintenance, Repair, and Overhaul
Asset Key Flexfield KEY# Oracle Assets
Bank Details KeyFlexField BANK Oracle Payroll
CAGR Flexfield CAGR Oracle Human Resources
Category Flexfield CAT# Oracle Assets
Competence Flexfield CMP Oracle Human Resources
Cost Allocation Flexfield COST Oracle Payroll
Grade Flexfield GRD Oracle Human Resources
Item Catalogs MICG Oracle Inventory
Item Categories MCAT Oracle Inventory
Job Flexfield JOB Oracle Human Resources
Location Flexfield LOC# Oracle Assets
Oracle Service Item Flexfield SERV Oracle Inventory
People Group Flexfield GRP Oracle Payroll
Personal Analysis Flexfield PEA Oracle Human Resources
Position Flexfield POS Oracle Human Resources
Public Sector Budgeting BPS Oracle Public Sector Budgeting
Sales Orders MKTS Oracle Inventory
Sales Tax Location Flexfield RLOC Oracle Receivables
Soft Coded KeyFlexfield SCL Oracle Human Resources
Stock Locators MTLL Oracle Inventory
System Items MSTK Oracle Inventory
Territory Flexfield CT# Oracle Receivables
Training Resources RES Oracle Learning Management

You use the flexfield code and the owning application to identify a flexfield when you call it from a custom form.

Note: that the following flexfields are single-structure seeded key flexfields: Account Aliases, Item Catalogs, Oracle Service Item Flexfield, Stock Locators, and System Items.

Key Flexfields by Owning Application

Here is a table listing many of the key flexfields in Oracle E-Business Suite, ordered by the application that “owns” the key flexfield. Note that other applications may also use a particular flexfield.

Owner Name Code
Oracle Assets Asset Key Flexfield KEY#
Oracle Assets Category Flexfield CAT#
Oracle Assets Location Flexfield LOC#
Oracle Complex Maintenance, Repair, and Overhaul AHL Route AHLR
Oracle Enterprise Performance Foundation Activity Flexfield FEAC
Oracle General Ledger Accounting Flexfield GL#
Oracle Human Resources CAGR Flexfield CAGR
Oracle Human Resources Competence Flexfield CMP
Oracle Human Resources Grade Flexfield GRD
Oracle Human Resources Job Flexfield JOB
Oracle Human Resources Personal Analysis Flexfield PEA
Oracle Human Resources Position Flexfield POS
Oracle Human Resources Soft Coded KeyFlexfield SCL
Oracle Inventory Account Aliases MDSP
Oracle Inventory Item Catalogs MICG
Oracle Inventory Item Categories MCAT
Oracle Inventory Sales Orders MKTS
Oracle Inventory Stock Locators MTLL
Oracle Inventory Oracle Service Item Flexfield SERV
Oracle Inventory System Items MSTK
Oracle Learning Management Training Resources RES
Oracle Payroll Bank Details KeyFlexField BANK
Oracle Payroll Cost Allocation Flexfield COST
Oracle Payroll People Group Flexfield GRP
Oracle Public Sectory Budgeting PSB Position Flexfield BPS
Oracle Receivables Sales Tax Location Flexfield RLOC
Oracle Receivables Territory Flexfield CT#

Tables of Individual Key Flexfields in Oracle E-Business Suite

The following sections contain a table for individual key flexfields in the Oracle E-Business Suite. These tables provide you with useful information, including:

  • Which application owns the key flexfield
  • The flexfield code (used by forms and routines that call a flexfield)
  • The name of the code combinations table
  • How many segment columns it has
  • The width of the segment columns
  • The name of the unique ID column (the CCID column)
  • The name of the structure ID column
  • Whether it is possible to use dynamic insertion with this key flexfield

Many of these key flexfield sections also contain information on the uses and purpose of the flexfield, as well as suggestions for how you might want to implement it at your site.

Account Aliases

The following table lists details for this key flexfield.

Owner Oracle Inventory
Flexfield Code MDSP
Table Name MTL_GENERIC_DISPOSITIONS
Number of Columns 20
Width of Columns 40
Dynamic Inserts Possible No
Unique ID Column DISPOSITION_ID
Structure Column ORGANIZATION_ID

This key flexfield supports only one structure.

Accounting Flexfield

The following table lists details for this key flexfield.

Owner Oracle General Ledger
Flexfield Code GL#
Table Name GL_CODE_COMBINATIONS
Number of Columns 30
Width of Columns 25
Dynamic Inserts Possible Yes
Unique ID Column CODE_COMBINATION_ID
Structure Column CHART_OF_ACCOUNTS_ID

The Accounting Flexfield is fully described in the Oracle General Ledger documentation.

Asset Key Flexfield

The following table lists details for this key flexfield.

Owner Oracle Assets
Flexfield Code KEY#
Table Name FA_ASSET_KEYWORDS
Number of Columns 10
Width of Columns 30
Dynamic Inserts Possible Yes
Unique ID Column CODE_COMBINATION_ID
Structure Column None

Oracle Assets uses the asset key flexfield to group your assets by non-financial information. You design your asset key flexfield to record the information you want. Then you group your assets by asset key so you can find them without an asset number.

Warning: Plan your flexfield carefully. Once you have started entering assets using the flexfield, you cannot change it.

Bank Details KeyFlexField

The following table lists details for this key flexfield.

Owner Oracle Payroll
Flexfield Code BANK
Table Name PAY_EXTERNAL_ACCOUNTS
Number of Columns 30
Width of Columns 60
Dynamic Inserts Possible Yes
Unique ID Column EXTERNAL_ACCOUNT_ID
Structure Column ID_FLEX_NUM

The Bank Details KeyFlexfield [sic] holds legislation specific bank account information. The Bank Details structure that you see is determined by the legislation of your Business Group.
Localization teams determine the data that is held in this flexfield. Each localization team defines a flexfield structure that allows you to record the bank account information relevant to each legislation.
If you are using a legislation for which a Bank KeyFlexfield structure has been defined you should not modify the predefined structure.

Warning: You should not attempt to alter the definitions of the Bank Details Flexfield which are supplied. These definitions are a fundamental part of the package. Any change to these definitions may lead to errors in the operating of the system.
It is possible that Oracle Human Resources will use the other segments of this flexfield in the future. Therefore, you should not try to add other segments to this Flexfield. This may affect your ability to upgrade the system in the future.
Consult your Oracle Human Resources National Supplement for the full definition of your Bank Details Flexfield.

Category Flexfield

The following table lists details for this key flexfield.

Owner Oracle Assets
Flexfield Code CAT#
Table Name FA_CATEGORIES
Number of Columns 7
Width of Columns 30
Dynamic Inserts Possible No
Unique ID Column CATEGORY_ID
Structure Column None

Oracle Assets uses the category flexfield to group your assets by financial information. You design your category flexfield to record the information you want. Then you group your assets by category and provide default information that is usually the same for assets in that category.

Warning: Plan your flexfield carefully. Once you have started entering assets using the flexfield, you cannot change it.

Cost Allocation Flexfield

The following table lists details for this key flexfield.

Owner Oracle Payroll
Flexfield Code COST
Table Name PAY_COST_ALLOCATION_KEYFLEX
Number of Columns 30
Width of Columns 60
Dynamic Inserts Possible Yes
Unique ID Column COST_ALLOCATION_KEYFLEX_ID
Structure Column ID_FLEX_NUM

You must be able to get information on labor costs from your payrolls, and send this information to other systems. Payroll costs must of course go to the general ledger. Additionally, you may need to send them to labor distribution or project management systems.
The Cost Allocation Flexfield lets you record, accumulate and report your payroll costs in a way which meets the needs of your enterprise.

Grade Flexfield

The following table lists details for this key flexfield.

Owner Oracle Human Resources
Flexfield Code GRD
Table Name PER_GRADE_DEFINITIONS
Number of Columns 30
Width of Columns 60
Dynamic Inserts Possible Yes
Unique ID Column GRADE_DEFINITION_ID
Structure Column ID_FLEX_NUM

Grades are used to represent relative status of employees within an enterprise, or work group. They are also used as the basis of many Compensation and Benefit policies.

Item Catalogs

The following table lists details for this key flexfield.

Owner Oracle Inventory
Flexfield Code MICG
Table Name MTL_ITEM_CATALOG_GROUPS
Number of Columns 15
Width of Columns 40
Dynamic Inserts Possible No
Unique ID Column ITEM_CATALOG_GROUP_ID
Structure Column None

This key flexfield supports only one structure.

Item Categories

The following table lists details for this key flexfield.

Owner Oracle Inventory
Flexfield Code MCAT
Table Name MTL_CATEGORIES
Number of Columns 20
Width of Columns 40
Dynamic Inserts Possible No
Unique ID Column CATEGORY_ID
Structure Column STRUCTURE_ID

You must design and configure your Item Categories Flexfield before you can start defining items since all items must be assigned to categories.
You can define multiple structures for your Item Categories Flexfield, each structure corresponding to a different category grouping scheme. You can then associate these structures with the categories and category sets you define.

Job Flexfield

The following table lists details for this key flexfield.

Owner Oracle Human Resources
Flexfield Code JOB
Table Name PER_JOB_DEFINITIONS
Number of Columns 30
Width of Columns 60
Dynamic Inserts Possible Yes
Unique ID Column JOB_DEFINITION_ID
Structure Column ID_FLEX_NUM

The Job is one possible component of the Employee Assignment in Oracle Human Resources. The Job is used to define the working roles which are performed by your employees. Jobs are independent of Organizations. With Organizations and Jobs you can manage employee assignments in which employees commonly move between Organizations but keep the same Job.
You use the Job Flexfield to create Job Names which are a unique combination of segments. You can identify employee groups using the individual segments of the Job whenever you run a report or define a QuickPaint.

Location Flexfield

The following table lists details for this key flexfield.

Owner Oracle Assets
Flexfield Code LOC#
Table Name FA_LOCATIONS
Number of Columns 7
Width of Columns 30
Dynamic Inserts Possible Yes
Unique ID Column LOCATION_ID
Structure Column None

Oracle Assets uses the location flexfield to group your assets by physical location. You design your location flexfield to record the information you want. Then you can report on your assets by location. You can also transfer assets that share location information as a group, such as when you move an office to a new location.

Warning: Plan your flexfield carefully. Once you have started entering assets using the flexfield, you cannot change it.

People Group Flexfield

The following table lists details for this key flexfield.

Owner Oracle Payroll
Flexfield Code GRP
Table Name PAY_PEOPLE_GROUPS
Number of Columns 30
Width of Columns 60
Dynamic Inserts Possible Yes
Unique ID Column PEOPLE_GROUP_ID
Structure Column ID_FLEX_NUM

The People Group flexfield lets you add your own key information to the Employee Assignment. You use each segment to define the different groups of employees which exist within your own enterprise. These may be groups which are not identified by your definitions of other Work Structures.

Personal Analysis Flexfield

The following table lists details for this key flexfield.

Owner Oracle Human Resources
Flexfield Code PEA
Table Name PER_ANALYSIS_CRITERIA
Number of Columns 30
Width of Columns 60
Dynamic Inserts Possible Yes
Unique ID Column ANALYSIS_CRITERIA_ID
Structure Column ID_FLEX_NUM

The Personal Analysis Key Flexfield lets you add any number of Special Information Types for people. Each Special Information Type is defined as a separate flexfield structure for the Personal Analysis Flexfield.
Some common types of information you might want to hold are:

  • Qualifications
  • Language Skills
  • Medical Details
  • Performance Reviews
  • Training Records

Each structure can have up to 30 different segments of information.

Position Flexfield

The following table lists details for this key flexfield.

Owner Oracle Human Resources
Flexfield Code POS
Table Name PER_POSITION_DEFINITIONS
Number of Columns 30
Width of Columns 60
Dynamic Inserts Possible Yes
Unique ID Column POSITION_DEFINITION_ID
Structure Column ID_FLEX_NUM

Positions, like Jobs, are used to define employee roles within Oracle Human Resources. Like Jobs, a Position is an optional component of the Employee Assignment. However, unlike Jobs, a Position is defined within a single Organization and belongs to it.
Positions are independent of the employees who are assigned to those positions. You can record and report on information which is directly related to a specific position rather than to the employee.

Sales Orders

The following table lists details for this key flexfield.

Owner Oracle Inventory
Flexfield Code MKTS
Table Name MTL_SALES_ORDERS
Number of Columns 20
Width of Columns 40
Dynamic Inserts Possible Yes
Unique ID Column SALES_ORDER_ID
Structure Column None

The Sales Orders Flexfield is a key flexfield used by Oracle Inventory to uniquely identify sales order transactions Oracle Order Management interfaces to Oracle Inventory.
Your Sales Orders Flexfield should be defined as Order Number, Order Type, and Order Source. This combination guarantees each transaction to Inventory is unique.
You must define this flexfield before placing demand or making reservations in Oracle Order Management.

Sales Tax Location Flexfield

The following table lists details for this key flexfield.

Owner Oracle Receivables
Flexfield Code RLOC
Table Name AR_LOCATION_COMBINATIONS
Number of Columns 10
Width of Columns 22
Dynamic Inserts Possible Yes
Unique ID Column LOCATION_ID
Structure Column LOCATION_STRUCTURE_ID

The Sales Tax Location Flexfield is used to calculate tax based on different components of your customers’ shipping addresses for all addresses in your home country.

Oracle Service Item Flexfield

The following table lists details for this key flexfield.

Owner Oracle Service
Flexfield Code SERV
Table Name MTL_SYSTEM_ITEMS
Number of Columns 20
Width of Columns 40
Dynamic Inserts Possible No
Unique ID Column INVENTORY_ITEM_ID
Structure Column ORGANIZATION_ID

The Service Item flexfield uses the same table as the System Item Flexfield. However, you can set up your segments differently with the Service Item Flexfield.

Soft Coded KeyFlexfield

The following table lists details for this key flexfield.

Owner Oracle Human Resources
Flexfield Code SCL
Table Name HR_SOFT_CODING_KEYFLEX
Number of Columns 30
Width of Columns 60
Dynamic Inserts Possible Yes
Unique ID Column SOFT_CODING_KEYFLEX_ID
Structure Column ID_FLEX_NUM

The Soft Coded KeyFlexfield holds legislation specific information. The Soft Coded KeyFlexfield structure that a user will see is determined by the legislation of the Business Group.
Localization teams determine the data that is held in this flexfield. Each localization team defines a flexfield structure and uses qualifiers to define the level at which each segment is visible. Segments can be seen at business group, payroll or assignment level. The type of information that is held in this key flexfield varies from legislation to legislation.
If you are using a legislation for which a Soft Coded KeyFlexfield structure has been defined you should not modify the predefined structure.

Stock Locators

The following table lists details for this key flexfield.

Owner Oracle Inventory
Flexfield Code MTLL
Table Name MTL_ITEM_LOCATIONS
Number of Columns 20
Width of Columns 40
Dynamic Inserts Possible Yes
Unique ID Column INVENTORY_LOCATION_ID
Structure Column ORGANIZATION_ID

You can use the Stock Locators Flexfield to capture more information about stock locators in inventory. If you do not have Oracle Inventory installed, or none of your items have locator control, it is not necessary to set up this flexfield.
If you keep track of specific locators such as aisle, row, bin indicators for your items, you need to configure your Stock Locators Flexfield and implement locator control in your organization.
This key flexfield supports only one structure.

System Items (Item Flexfield)

The following table lists details for this key flexfield.

Owner Oracle Inventory
Flexfield Code MSTK
Table Name MTL_SYSTEM_ITEMS
Number of Columns 20
Width of Columns 40
Dynamic Inserts Possible No
Unique ID Column INVENTORY_ITEM_ID
Structure Column ORGANIZATION_ID

You can use the System Items Flexfield (also called the Item Flexfield) for recording and reporting your item information. You must design and configure your Item Flexfield before you can start defining items.
All Oracle E-Business Suite products that reference items share the Item Flexfield and support multiple-segment implementations. However, this flexfield supports only one structure.

Territory Flexfield

The following table lists details for this key flexfield.

Owner Oracle Receivables
Flexfield Code CT#
Table Name RA_TERRITORIES
Number of Columns 20
Width of Columns 25
Dynamic Inserts Possible Yes
Unique ID Column TERRITORY_ID
Structure Column None

You can use the Territory Flexfield for recording and customized reporting on your territory information. Territory Flexfields are also displayed in the Transaction Detail and Customer Detail reports in Oracle Receivables.

/by
, , , , , ,

Defining Unit of Measure Conversions

Unit of measure conversions are numerical factors that enable you to perform transactions in units other than the primary unit of the item being transacted. You can define:
A conversion common to any item (Standard)
A conversion for a specific item within a unit of measure class (Intra-class)
A conversion for a specific item between unit of measure classes (Inter-class)
  • Unit of measure conversions are not organization-specific.
  • You must define a conversion between a non-base unit of measure and the base unit of measure before you can assign the non-base unit of measure to an item

Specifying Which Conversion to Use
When you define an item you decide which type of unit of measure conversion to use:

  1. Itemspecific: Only uses unit of measure conversions unique to this item. If none exist, you can only transact this item in its primary unit of measure.
  2. Standard: Uses standard unit of measure conversions for this item if an item-specific conversion is not available.
  3. Both: Uses both item-specific and standard unit of measure conversions. If both exist for the same unit of measure and item combination, the item-specific conversion is used.

 
Unit of Measure Conversions During Transactions
Whenever you enter an item’s quantity, the default is the primary unit of measure for the item. The list of values for the unit of measure field displays all units of measure for which you have defined standard and/or item-specific conversions from the primary unit of measure.
Transactions are performed in the unit of measure you specify. The conversion happens automatically and item quantities are updated in the primary unit of measure of the item.

Important: Inventory transactions and on hand balance supports decimal precision to 5 digits after the decimal point. Oracle Work in Process supports decimal precision to 6 digits. Other Oracle Applications support different decimal precision. As a result of the decimal precision mismatch, transactions another Oracle Application passes may be rounded when processed by Inventory. If the transaction quantity is rounded to zero, Inventory does not process the transaction.
It is therefore suggested that the base unit of measure for an item is set up such that transaction quantities in the base unit of measure not require greater than 5 digits of decimal precision. Define a Standard conversion for any item
In standrad conversion you specify how one unit of mesaure is related to the primary unit of measure in the same class.
In standrad conversion you cant do the following
You cant specify any sort of intra class conversion
Relationship between two UOMs not invloving primary UOM
Navigate to the Unit of Measure Conversions window  & Select the Standard tabbed region.
1 Enter a unit of measure.
2 Enter the conversion factor by which the unit of measure is equivalent to the base unit of measure established for this class.
For example, if one DZ (this unit of measure) is equivalent to 12 EA (base unit), the conversion factor is 12. Or, if EA is equal to one-twelfth of a DZ, the conversion factor is 0.08333. Define a conversion for a specific item within a unit of measure class (Intra-class)
We have seen in standard conversion we can only do convesrion from one UOM to primary UOM.
Suppose we have defined a UOM convsrion rule for a unit of measure UOM_XYZ as UOM_XYZ = 6 x Primary UOM but for a particular item the vonvsrion rate is not 6 in that case we define a intra class convesrion for  a particular item and when ever that item is transacted system ‘ll pick the convesrion rate from either intra class or standrad convesrion depending upon ITEM master set up.
Notes
We can do intra class conversion between two UOMs for a particular item only for a single class which is the UOM class of the primary UOM of the item.
For exampe Suppose ITEM001 has a primary UOM as Ea and UOM Ea belongs to class Quantity then we can define intra class conversion for the item ITEM001 between two UOMs in the class Quantity.
we cant define intra class convesrion between any other UOMs belonging to a differnt UOM class.
Navigate to the Unit of Measure Conversions window.
 
1. Select the Intra-class tabbed region.
2. Enter an item.
3. Enter a unit of measure.
4. Enter the conversion factor by which the unit of measure is equivalent to the base unit of measure established for this class.
For example, if one LB (this unit of measure) is equivalent to 16 OZ (base unit), the conversion factor is 16.
 
Define a conversion for a specific item between unit of measure classes (Inter-class)
Inter class conversion is used to convert an item from one primary UOM in one class to another primary UOM in a differnt class for a particular item. Navigate to the Unit of Measure Conversions window and Select the Inter-class tabbed region.

1. Select an item.
2. Select the destination base unit of measure of the class to which you are converting a unit of measure.
3. Enter the conversion factor by which the source base unit is equivalent to the destination base unit.
For example, if one ML (source base unit) is equivalent to one GR (destination base unit), the conversion factor is one.
/by
, , , , , ,

Closing a Period

1. Enter all transactions.
Be sure you enter all transactions for the period. Perform all issues,receipts, and adjustments. Verify that no hard copy records exist or are waiting for data entry, such as packing slips in receiving.
2. Check Inventory and Work in Process transaction interfaces.You can set up the material and move transaction managers to execute transactions immediately, then submit an immediate concurrent request to execute, or submit a concurrent request periodically at a time interval you specify. If you do not use immediate processing, or interface external transactions, check the Inventory material transaction manager and the Work in Process move transaction manager before closing the period.

3. Check Cost Management cost interfaces.
Cost Management processes your inventory and work in process accounting transactions as a concurrent request, using a specified time interval. Before you close the period, you should check that the Cost Manager is active.

4. Check Order Management transaction processes. If you use Order Management, ensure that all sales order transaction processes complete and transfer successfully to Inventory.
5. Review Inventory transactions.
Before you close a period, review all of the transactions using the Material Account Distribution Report for the period with a high dollar value and/or a high transaction quantity. Check that you charged the proper accounts. Correcting improper account charges before you close a period is easier than creating manual journalentries.
6. Balance perpetual inventory.
Check that your ending perpetual inventory value for the period being closed matches the value you report in the general ledger. Perpetual inventory value normally balances automatically with the general ledger. However, one of the following sources can create a discrepancy:
– Other inventory journal entries. Journal entries from products other than Inventory that affect the inventory accounts.
– Charges to improper accounts: For example, you issued material from a subinventory to a miscellaneous account, but used one of the subinventory accounts as that miscellaneous account.
– Issue to miscellaneous account: For example, the following miscellaneous transaction issue would cause an out of balance situation: debit account specified at transaction 123, credit subinventory valuation account 123. The debit and credit net to zero with no financial charge, but since the inventory quantity decreased, the month–end inventory valuation reports will not equal the general ledger account balance.
– Transactions after period end reports. This occurs when you run the end of month inventory valuation reports before you complete all transactions for the period.
If you do not run the inventory reports at period end, you can also run these Reports:
– Inventory Value Report– Material Account Distribution Detail Report
– Material Account Distribution Summary Report
– Period Close Summary Report– Period Close Reconciliation report– Inventory Subledger Report (Average Costing Only)
In a organization using Project Manufacturing Average Costing, if there is more than one cost group, the following valuation reports should not be used for reconciliation purposes because these reports list the average value across cost groups.
– Transaction historical Summary Report
– Receiving Value Report
– All Inventories Value Report
– Elemental Inventory Value Report
– Subinventory Account Value Report
– Item Cost Report
7. Validate Work in Process inventory.
If you use Work in Process, check work in process inventory balances against transactions with the WIP Account Distribution Report.

8. Transfer transactions in advance of closing period (optional).
If time permits, run the general ledger transfer process up to the period end date before closing the period.
Closing a period executes the general ledger transfer automatically. However, you can also run this process without closing a period using Transfer Transactions to General Ledger. Since you cannot reopen a closed period, running this process before period close allows you to proof the interfaced transactions and make adjustments to the period via new inventory transactions as necessary.
9. Close Oracle Payables and Oracle Purchasing.
If you use Payables and Purchasing, you need to close the accounting periods in the following order:
– Payables
– Purchasing
– Inventory
If you only use Purchasing and Inventory, you need to close Purchasing first. Close Payables before Purchasing, in preparation for accruing expenses on uninvoiced receipts. Doing so ensures that all new payables activity is for the new month and you do not inadvertently match a prior month invoice in payables to a new month receipt. When you close Purchasing or Inventory, you cannot enter a receipt for that period. However, as a manual procedure, close Purchasing before Inventory. This still allows miscellaneous transaction corrections in Inventory.

10. Run the Period Close Reconciliation report.
This report automatically runs in simulation mode for the open period. It is used to match account balances with inventory value at period end.
11. Close the accounting period and automatically transfer transactions to the general ledger.
This sets your Inventory Accounting Period status to Closed not Summarized. If the CST: Period Summary profile option is set to Automatic, no other steps are necessary. The period status is set to Closed when the summarization process has completed.

12. If the CST: Period Summary profile option is set to Manual, create period summarization transactions by generating the Period Close Reconciliation report.
The concurrent program creates summarized transaction records, and displays the differences between account balances and inventory value.
/by
, , , , , ,

Inventory Pending Transaction

Users can see the number of pending transactions by navigating to the Inventory Accounting Periods Form.
Navigate > Cost > Accounting Close Cycle > Inventory Accounting Periods
Place cursor on the appropriate open accounting period and click on the [Pending] Button. There are three zones titled “Resolution Required”, “Resolution Recommended” and “Unprocessed Shipping Transactions”.

Unprocessed material transactions exist for this period
This message indicates you have unprocessed material transactions in the MTL_MATERIAL_TRANSACTIONS_TEMP table. You are unable to close the period with this condition. Please see your system administrator. Inventory considers entries in this table as part of the quantity movement.
Closing the period in this situation is not allowed because the resultant accounting entries would have a transaction date for a closed period, and never be picked up by the period close or general ledger transfer process.
Uncosted material transactions exist for this period
This message indicates you have material transactions in the MTL_MATERIAL_TRANSACTIONS table with no accounting entries (Standard Costing) and no accounting entries and no costs (Average Costing). You are unable to close the period with this condition. These transactions are part of your inventory value.
Closing the period in this situation is not allowed because the resultant accounting entries would have a transaction date for a closed period, and never be picked up by the period close or general ledger transfer process.
Pending WIP costing transactions exist in this period
This message indicates you have unprocessed resource and overhead accounting transactions in the WIP_COST_TXN_INTERFACE table. You are unable to close the period with this condition. These transactions are in your work in process value, and awaiting further processing.
Closing the period in this situation is not allowed because the resultant accounting entries would have a transaction date for a closed period, and never be picked up by the period close or general ledger transfer process.
Unprocessed Shipping Transactions
“Pending Transactions” in the Unprocessed Shipping Transactions zone indicate there are transactions in the WSH_DELIVERY_DETAILS table in a status of shipped.
Pending receiving transactions for this period
When you use Purchasing, this message indicates you have unprocessed purchasing transactions in the RCV_TRANSACTIONS_ INTERFACE table. These transactions include purchase order receipts and returns for inventory. If this condition exists, you will receive a warning but will be able to close the accounting period. These transactions are not in your receiving value. However, after you close the period, these transactions cannot be processed because they have a transaction date for a closed period.
Pending material transactions for this period
This message indicates you have unprocessed material transactions in the MTL_TRANSACTIONS_INTERFACE table. If this condition exists, you will receive a warning but will be able to close the accounting period. These transactions are not in your inventory value. However, after you close the period, these transactions cannot be processed because they have a transaction date for a closed period.
Pending move transactions for this period
This message indicates you have unprocessed shop floor move transactions in the WIP_MOVE_TXN_INTERFACE table. If this condition exists, you will receive a warning but will be able to close the accounting period. These transactions are not in your work in process value. However, after you close the period, these transactions cannot be processed because they have a transaction date for a closed period.

/by
, , , , , ,

Transfer Transactions to General Ledger

You can perform the general ledger transfer at any time during an open period—not just at period close. Interim transfers allow you to reconcile and transfer information weekly, making the month–end period close process much simpler and
faster.
The general ledger transfer loads summary or detail accounting activity for any open period into the general ledger interface, including both inventory and work in process entries. When more than one period is open, the transfer selects transactions from the first open period, up to the entered transfer date, and passes the correct accounting date and financial information into the general ledger interface.
For example, when you transfer detail entries, the transaction date is the accounting date with a line for line transfer. When you transfer summary entries with two periods open and enter a transfer date in the second period, the transfer process assigns the period one end date for all the summarized transactions in period one and assigns the entered transfer date for the summarized transactions in period two.
For each inventory organization, Cost Management transfers transactions to the general ledger interface table, line for line. If you transfer summary information, Cost Management groups transactions by GL batch, by journal category, by currency code, and by account.
Attention: Transfer in detail only if you have low transaction volumes. Transferring large amounts of detail transactions can
adversely affect General Ledger performance.
For both detail and summary transfers, Cost Management passes the organization code, GL batch number, batch description, and batch date. When you transfer in detail, you also pass the material or work in process transaction number. In General Ledger, you can see the transferred information, as follows:

Cost Management uses the journal source Inventory for both inventory and work in process transactions.
The journal categories Inventory and Work in Process distinguish between inventory and work in process transactions.
Using Journal Import and Post Journals processes in General Ledger, you can then post this information to the general ledger.
Period Summarization Process
Summarization of transaction records for the open period is the last step in period close. You have the option to perform this process automatically or manually using the profile option, CST:Period Summary. If the profile option is set to Automatic, the period is closed and summarized when you change the period status from Open to Closed.
If the profile option is set to Manual, you can delay summarization – but you must summarize these delayed periods in accounting period order. For example, if you delay summarization for a given period, the following period cannot be summarized until the previous period is summarized. In situations where summarization is delayed, the longer the delay – the larger the number of transaction records needed for reconciliation purposes. This situation can cause summarization to take
more time to complete.
If you do not choose to summarize periods, set the period status to Closed not Summarized.
The Period Close Reconciliation report is used to compare account balances with inventory value at period end. You can run the report in simulation mode by generating it for an open period. The report can be generated at any time during the period.

/by