Skip to main content

Posts

Showing posts from June, 2015

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

Resolving Period Close Pending Transaction R12 or Inventory Closing Steps in Oracle Apps R12

Resolving Period Close Pending Transaction R12 (Doc ID 1069492.1) APPLIED ON:- Oracle Cost Management - Version 12.0.0 and later Oracle Shipping Execution - Version 12.0.0 and later Oracle Purchasing - Version 12.0.0 and later Oracle Work in Process - Version 12.0.0 and later Oracle Inventory Management - Version 12.0.0 and later PURPOSE:- Troubleshooting Pending Transactions TROUBLESHOOTING STEPS:- 1 -: VIEWING PENDING TRANSACTIONS 2-:  UNPROCESSED MATERIAL TRANSACTIONS 3-:  Uncosted Material/WSM Transactions 4-:  Pending WIP Costing transactions 5-:  Pending WSM interface 6-:  Pending LCM Interface Transactions Resolution Recommended Transactions 1-:  Pending Receiving Transactions 2-:  Pending Material Transactions 3-:  Pending Shop Floor Move 4-:  UNPROCESSED SHIPPING TRANSACTIONS Conclusion: The key steps to resolving pending transactions are: -Locate the transactions -Find the error message to determine what is preventing the transactions from processing. -Resolve the err

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

UNPROCESSED SHIPPING TRANSACTIONS To resolve unprocessed shipping transactions, you need to determine and fix the shipping transactions that are in a status of shipped, BUT not interface to Order Management or Inventory, in the WSH_DELIVERY_DETAILS table. Details of the Shipping transactions in a status of shipped can be viewed through the application by navigating to the Transaction screen through Order Management and quarrying on the status 'Shipped' and the Date of a period: Order Management > Shipping > Transactions The Shipping Transactions window provides a consolidated workbench for three major shipping functions: planning, pick releasing, and ship confirming. It enables you to plan and manage trips, stops, deliveries, delivery lines, and LPNs. There are four tabs to select they type of information: Trips, Stops, Contents by Delivery, Contents by Line/Lpn. Transactions that are in a in a status of 'Shipped' have been shipped confirmed but have not y

Pending Shop Floor Move(Resolving Period Close Pending Transaction R12 or Inventory Closing Steps in Oracle Apps R12)

Pending Shop Floor Move Resolving unprocessed Move Transactions is a process of determining and fixing what is preventing a record from being processed through the WIP_MOVE_TXN_INTERFACE table. Details of pending move transactions can be viewed through the applications by navigating to the pending move transactions form: WIP > Move Transactions > Pending Move Transactions Through the Pending Move Transactions window, you can view, update, delete, and resubmit Move transaction records that have failed validation and remain in the Open Move Transaction Interface table (WIP_MOVE_TXN_INTERFACE). You can also resubmit transactions whose concurrent process has failed and had a processing phase of Complete and process status of Error. You can view error messages associated with failed records. Error messages can assist you in updating failed records before resubmission. There are seven tabs to select information on the move transaction; Processing, Source, Concurrent Request, Job or

Pending Material Transactions(Resolving Period Close Pending Transaction R12 or Inventory Closing Steps in Oracle Apps R12)

Pending Material Transactions Resolving Pending Material Transactions is a process of determining and fixing what is preventing a record from being processed through the MTL_TRANSACTIONS_INTERFACE table. Details of pending transactions can be viewed through the application by navigating to the Transaction Open Interface form: Inventory > Transactions > Transaction Open Interface Using the Transaction Open Interface window, you can view, edit, correct and resubmit transactions received through the open interface. There are four tabs to view information: Error, Location, Source, Intransit and Other which provide detailed information to help you resolved pending transactions. Select a tabbed region to display a type of information: Error: Interface transaction error information. Location : Interface transaction location information. Source : Interface source information Intransit: Interface in the transit shipping information. Others : Miscellaneous header and costing inform

Pending Receiving Transactions (Resolving Period Close Pending Transaction R12 or Inventory Closing Steps in Oracle Apps R12)

Pending Receiving Transactions Pending Receiving Transactions are transactions that have not processed through the RCV_TRANSACTIONS_INTERFACE table. These transactions can be viewed and deleted through the "Transaction Status Summary" form: Purchasing > Receiving > Transactions Status Summary A Find window will appear and to query all of the unprocessed transactions for that period select from the field Source Type 'All', from the Transactions Details tab input the start and completion dates of the period in question and click 'Find': Using the Transaction Statuses window, pending transactions can be viewed and deleted. There are four tabs to select: Transactions, Details, Order Information and Outside Services . The Main Descriptive fields give detailed information on the type of transaction that the cursor is on : Receipt, Receipt number Supplier , Source of the receipt Description , Item description Errors , Error message Order , Order Number Paren

Pending LCM Interface Transactions (Resolving Period Close Pending Transaction R12 or Inventory Closing Steps in Oracle Apps R12 )

Pending LCM Interface Transactions To resolve pending Landed Cost Management (LCM) transactions you need to determine and fix what is preventing a record from being processed through the CST_LC_ADJ_INTERFACE table. Details of transactions can be viewed through the Applications by navigating to the Pending Landed Cost Adjustment form. Cost Responsibility > View Transactions > Pending Landed Cost Adjustments The Pending Landed Cost Adjustment Transactions window can be used to view pending landed cost adjustment transactions. You can also use this window to resubmit any erred pending adjustment transactions. There are three tabs; Processing, Transaction,  and Source, to view information on the pending records and an Errors button to view the error if the transactions are in error; Fields common to all tabs ; Transaction Id , Unique landed cost transaction identifier Fields in the Processing TAB: Group Id , Landed cost adjustment processor group id Phase, Process phase: 1-Pe

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

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. E