Skip to main content

Pending WIP Costing transactions (Resolving Period Close Pending Transaction R12 or Inventory Closing Steps in Oracle Apps R12 )














Pending WIP Costing transactions


Resolving Pending WIP Cost transactions is a process of determining and fixing what is preventing a record form being processed through the WIP_COST_TXN_INTERFACE table. Details of pending transactions can be viewed through the applications by navigating to the pending resource transaction form.



WIP > Resource Transactions > Pending Resource Transactions






In the Pending Resource Transaction window, you can view, update and resubmit resource transactions that have failed validation and remain in the WIP_COST_TXN_INTERFACE table. You can also resubmit and delete transactions whose concurrent process has failed and have a processing phase of Complete and a process status of Error. There are seven tabs to select the type of information: Processing, Source, Concurrent Request, Job or Schedule Name, Operation, Resource, Transaction, Comments and Project Information which provide detailed information to help in resolving pending resource transactions.

Erred transactions will have the Transaction Id And Group ID populated and the Status will be "Error". Pending transactions will have the Transaction ID and Group ID fields blank and the Status will be "Pending".


To view error details for failed resource transactions, select the transaction and click on the [Error] button. The Pending Resource Transaction error window appears. Column indicates the name of the column in the resource transaction interface table (WIP_COST_TXN_INTERFACE) THAT FAILED VALIDATION. 



Transaction ID, Transaction Identifier


Fields in Processing Tab:

Group Id, Transaction group identifier

Phase, the Transaction processing phase

Status, Transaction processing status

Fields in Source Tab:

Source Code, Code of the shop floor control system that generated the transaction record 

Source Line, Identifier used by source shop floor control system 

Created By, Username of person that created the record

Fields in Concurrent Request Tab:

Request ID, Request Id

Phase, the Transaction processing phase

Status, Transaction processing status

Message, Concurrent Message

Fields in Job or Schedule Name Tab:

Organization, Organization identifier

Job or Schedule Name, WIP job or repetitive assembly name

Line, WIP line identifier

Assembly, Inventory item identifier of assembly that job or schedule creates

Fields in Operation Name Tab:

Op Seq, Operation sequence number within a routing

Dept, Department Identifier

Res Seq, Resource sequence number

Name, Resource code

Type, Resource type

Employee Number, Employee number


Fields in Resource Tab:

Activity, Activity name

Charge Type, Method of charging the resource

PO Number, Purchase order Identifier that the receipt is against

Currency, Unique Identifier for the currency

Actual Rate, Actual rate of the resource

Fields in Transaction Tab:

UOM, Unit of measure used for the transaction

Quantity, Transaction quantity

Date, Date transaction was performed

Type, Transaction type

Fields in Comments Tab:

Reason, Standard transaction reason name

Reference, Transaction reference descriptive text

Fields in Project Information Tab:

Project Number, Project Identifier

Task Number, Project task Identifier

Resubmitting Failed or Pending Resource Transactions 

In the Pending Resource Transactions window either check the transaction's Resubmit checkbox to resubmit one record or chose Select All for Resubmit from the Special Menu and selectively deselect individual transaction you do not want to resubmit, save your work. Erred transactions can also be resubmitted via the following SQL statement:

Update WIP_COST_TXN_INTERFACE
Set GROUP_ID = NULL,
TRANSACTION_ID = NULL,
REQUEST_ID = NULL,
PROCESS_STATUS = 1
Where PROCESS_STATUS = 3;

This will resubmit records in PROCESS_STATUS = 3 (Error), nulling out the transaction id, group id, and concurrent request id and change the process status to pending. 

The "Cost Manager" is the manager that will launch the "Resource Cost Worker" (short name CMCCTW) or the "Overhead Cost Worker" (short name CMCOCW) to process the resource or resource overhead transactions in the WIP_COST_TXN_INTERFACE table.





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

Ref -: Oracle Doc (Doc ID 1069492.1)

Comments

Post a Comment

Popular posts from this blog

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 ar_periods ar_perio

Error: - APP-PER-50022: Oracle Human Resource Could Not Retrieve a Value For The User Type Profile Option. Please ensure it is set property for your responsibility

Error: - APP-PER-50022: Oracle Human Resource Could Not Retrieve a Value For The User Type Profile Option. Please ensure it is set the property for your responsibility. Solution-:      (1)  Go to System administrator > Profile > System       (2) Now Search “ HR: User Type ” Profile option at Responsibility level with Respective Responsibility. And Click On FIND Button. Now Select HR: User Type Value “HR with Payroll User” (you can choose another option as well accordingly). And SAVE. Now check your responsibility, error removed. Go ahead with your next step and enjoy Oracle Apps. For More Information Visit on www.OracleAppsGuide.com Or Subscribe your email-id on OracleAppsGuide.

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 database columns reference the lookup via a lookup code. If in the future your organization wants the users to s