Error - : ROI Fails with WMSINB-23840: Lot/Serial Validation Failed. Please Check Log for Details Ref Doc ID 352570.1

Error -: ROI Fails with WMSINB-23840: Lot/Serial Validation Failed. Please Check Log for Details (Doc ID 352570.1)

Applies to:

Oracle Inventory Management - Version 11.5.1 to 11.5.10.CU2

And [Release 11.5 to 11.5.10]

Information in this document applies to any platform.

EXECUTABLE: RVCTP - Receiving Transaction Processor

The following tables have been populated:

RCV_HEADERS_INTERFACE

RCV_TRANSACTIONS_INTERFACE

RCV_SERIALS_INTERFACE.

Cause

MTL_SERIAL_NUMBERS_INTERFACE table is not populated in a proper way for Serial Controlled Item.

Solution

If Item is Serial controlled, the following should be used:

INSERT INTO MTL_SERIAL_NUMBERS_INTERFACE (

TRANSACTION_INTERFACE_ID,

LAST_UPDATE_DATE,

LAST_UPDATED_BY,

CREATION_DATE,

CREATED_BY,

LAST_UPDATE_LOGIN,

FM_SERIAL_NUMBER,

TO_SERIAL_NUMBER,

PRODUCT_CODE,

PRODUCT_TRANSACTION_ID) VALUES (

MTL_MATERIAL_TRANSACTIONS_S.CURRVAL, --only for Items that are both Serial and Lot Controlled

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

Comments

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

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

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

testoag

Search This Blog