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

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.

Script to insert on hand quantity in to MTL_TRANSACTIONS_INTERFACE

Script to insert on hand quantity into MTL_TRANSACTIONS_INTERFACE To insert on hand quantity into MTL_TRANSACTIONS_INTERFACE INSERT INTO MTL_TRANSACTIONS_INTERFACE ( TRANSACTION_INTERFACE_ID, SOURCE_CODE, SOURCE_LINE_ID, SOURCE_HEADER_ID, PROCESS_FLAG, VALIDATION_REQUIRED, TRANSACTI...

Error "You have exceeded the transaction quantity". Precision Restriction for Quantity Field Up To 6 Decimal Places Performing Lot Receipts (Doc ID 464983.1)

Error "You have exceeded the transaction quantity". Applies to: Information in this document applies to any platform. FORM:RCVRCERC.FMB - Enter Receipts GUI FORM:RCVTXERT.FMB - Enter Receiving Transactions GUI FORM:RCVTXERE.FMB - Enter Returns GUI FORM:RCVTXECO.FMB - Enter Corrections GUI "You have exceeded the transaction quantity" Symptoms: "You have exceeded the transaction quantity" Note: Internal error message may indicate this message: INV_QUANTITY_TOO_BIG Steps: Go to Receiving Screen Enter the qty like 7200.00000489 (6 digits restriction makes it 7200.000005) Go to Lot/Serial form Enter lot number and qty as 7200.00001 (which was rounded to 5 digits) The message "you have exceeded the transaction quantity " Cause Can Be-: a) Restriction of precision support up to 6 decimal places was added for the quantity field b) Comparing the transaction qty entered in receiving forms and the lot quantity entered in lot-entry form after rounding to...

testoag

Search This Blog