Skip to main content

VIEWING PENDING TRANSACTIONS (Resolving Period Close Pending Transaction R12 or Inventory Closing Steps in Oracle Apps R12 )
















VIEWING PENDING TRANSACTIONS


You can view the number of pending transactions by navigating to the Inventory Accounting Periods form.


Navigate > Cost > Accounting Close Cycle > Inventory Accounting Periods






The Resolution Required displays the number of Unprocessed material, Uncosted material/WSM, Pending WIP Costing, Pending WSM interface and Pending LCM Interface transactions existing in this period. 



The Resolution Recommended zone displays the number of Pending Receiving, Pending Material and Pending Shop Floor Move transactions existing in this period. However, once the accounting period is closed, unresolved transactions in this zone cannot be processed because they have a transaction date for a closed period.



Resolution Required Transactions:



"Uncosted Material/WSM" indicates there are transactions in the MTL_MATERIAL_TRANSACTIONS table with unprocessed accounting entries. 

"Pending WIP Costing" transactions indicate there are unprocessed resource and overhead accounting transactions in the WIP_COST_TXN_INTERFACE table.
"Pending WSM interface" indicate there are pending transactions in the WSM_SPLIT_MERGE_TXN_INTERFACE table. 

"Pending LCM Interface" indicated there are pending transactions in the CST_LC_ADJ_INTERFACE table.

Resolution Recommended Transactions:

"Pending Receiving" transactions indicate there are unprocessed purchasing transactions in the RCV_TRANSACTIONS_INTERFACE table. These transactions include purchase order receipts and returns for inventory. These transactions are not included in your receiving value if they are not resolved prior to closing the period. 

"Pending Material" transactions indicate there are unprocessed material transactions in the MTL_TRANSACTIONS_INTERFACE table. 

"Pending Shop Floor Move" transactions indicate there are unprocessed shop floor move transactions in the WIP_MOVE_TXN_INTERFACE table.

Unprocessed Shipping Transactions:


The Unprocessed Shipping Transactions zone displays the number of Pending Transactions existing in this period. Transactions appearing in this zone must be resolved before the period can be closed, depending if the Resolution 'Required' or 'Recommended' is checked. 

"Unprocessed Material" indicate there are unprocessed material transactions in the MTL_MATERIAL_TRANSACTIONS_TEMP table .

"Pending Transactions" in the Unprocessed Shipping Transactions zone indicate there are transactions in the WSH_DELIVERY_DETAILS table in a status of shipped.


For More Information Visit on www.OracleAppsGuide.comOr Subscribe your email-id on OracleAppsGuide

Ref -: Oracle Doc (Doc ID 1069492.1)

Labels:

Comments

Post a Comment

Popular posts from this blog

Definition of Lookup in Oracle Apps R12 Or What is Lookup in Oracle Apps R12? Or What is the main purpose of lookups in Oracle Apps R12?

Definition of Lookup in Oracle Apps R12 Or What is Lookup in Oracle Apps R12? Or What is the main purpose of lookups in Oracle Apps R12? The main purpose of a lookup is to keep programs flexible and easier to configure. Lookups are an approach of creating a configurable “list of values” in E-Business Suite. One of the simplest examples of a lookup type is gender. A “gender lookup” will have definitions as shown next: Code       Meaning M             Male F              Female U             Unknown Suppose that there is a table for employees named PER_ALL_PEOPLE_F and it has the following columns: FIRST_NAME LAST_NAME DATE_OF_BIRTH GENDER The screen that displays an employee’s gender will display a value of Male, Female, or Unknown. However, the database column PER_ALL_PEOPLE_F table. GENDER will store a value of M, F, or U. Hence, the screen displays the meaning, whereas the dat...
Post a Comment
Read more

AP, AR, GL, INV, PA, FA, PO, TCA, Workflow - Interface and Base table in Oracle Apps R12

Main Interface and Base table in Oracle Apps R12 GL Module (General Ledger Module tables in Oracle Apps R12) Interface Table Base Table gl_interface gl_budget_interface gl_je_batches gl_je_headers gl_je_lines gl_je_sources gl_je_categories gl_sets_of_books gl_daily_rates gl_balances gl_periods gl_period_sets gl_code_conbinations AR Module (Account Receivable Module  tables  in Oracle Apps R12) Interface Table Base Table ra_customers_interface_all   ra_contact_phones_int_all ra_customer_profiles_int_all hz_parties hz_cust_accounts hz_cust_acct_sites_all hz_cust_sit_use_all hz_party_sites hz_locations hz_party_site_uses hz_customer_profiles hz_organization_profiles hz_person_profiles ra_interface_lines_all ra_interface_distributions_all ra_interface_salescredits_all ra_customer_trx_all ra_customer_trx_lines_all ra_cust_trx_line_gl_dist_all ra_cust_trx_types_all ar_payment_schedules_all ra_batch_sources_All ar_vat_tax_all ra_terms ...
2 comments
Read more

Example of $FLEX$ Syntax Used In Value Set

Example of $FLEX$ Syntax Used In Value Set ($flex$ in oracle apps) Example of using “ :$FLEX$.Value_Set_Name” to set up value sets where one segment depends on a prior segment that itself depends on a prior segment. Suppose you have a three-segment flexfield where the first segment is Country , the second segment is State , and the third segment is District . You could limit your third segment's values to only include Districts that are available for the Address specified in the first two segments. Your three value sets might be defined as follows:  Segment Name               Country_Segment Value Set Name              Country_Value_Set Validation Table              Country_Table Value Column                Country_NAME Description Column    ...
5 comments
Read more