Skip to main content

Pending WSM interface (Resolving Period Close Pending Transaction R12 or Inventory Closing Steps in Oracle Apps R12 )






Pending WSM interface


To resolve transactions in the WSM interface, you need to determine and fix what is preventing a record from being processed through the WSM_SPLIT_MERGE_TXN_INTERFACE table.



The user inserts rows into WSM_SPLIT_MERGE_TXN_INTERFACE (WSMTI), WSM_STARTING_JOBS_INTERFACE (WSJI), and WSM_RESULTING_JOBS_INTERFACE (WRJI) tables. Transactions in WSMTI are joined with the transactions in WSJI and WRJI by the HEADER_ID column in these tables.



Errors and Validations:



Whenever any one-row errors out within a given group, the PROCESS_STATUS of the entire group is set to ERROR. But only the transactions that actually erred out will have the
ERROR_MESSAGE column containing the error message.

Errors and warnings, if any, will be written into the WSM_INTERFACE_ERRORS table. Appropriate messages will be given in the parent and child

interface tables to refer to WSM_INTERFACE_ERRORS table when there is an error.


Resubmitting Pending WSM Interface transactions:

To resubmit the erred transactions for processing, the user has to rectify the error and change the PROCESS_STATUS of the required transactions from 3
(ERROR) to 1 (PENDING). Launching the concurrent process Import WIP Lot Transactions (Navigation path; Responsibility, Shop Floor Management > Run Request > Import WIP Lot Transactions) will process the records in the WSM_SPLIT_MERGE_TXN_INTERFACE table by Group_id.




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

Ref -: Oracle Doc (Doc ID 1069492.1)

Comments

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