Skip to main content

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 yet been interfaced to Oracle Inventory. These must be processed and resolved before the period is closed. The concurrent process "Order Management Interface" and the concurrent process "Inventory Interface" populate Inventory Interface and Order Management Interface and upon completing successfully the status of the line changes to "Invoice Eligible". These concurrent processes can be submitted through the applications by navigating to:



Order Management > Shipping > Interface > Run



Run the Order Management Interface-SRS first then the Inventory Interface-SRS. These concurrent processes can be submitted by Trip Stop. The Trip Stop of the pending shipping transaction can be found in the Shipping Transactions window under the Stops tab in the Trip column. Reviewing the log file will supply an error message if the concurrent process does not complete successfully.





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

Ref -: Oracle Doc (Doc ID 1069492.1)

Labels:

Comments

Post a Comment

Popular posts from this blog

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

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...
Post a Comment
Read more

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.
3 comments
Read more