Receiving Transactions and Debugging Techniques 20112012

1 2009 Oracle Corporation Proprietary and Confidential


The following is intended to outline our general

product direction. It is intended for information

purposes only, and may not be incorporated into

any contract. It is not a commitment to deliver any

material, code, or functionality, and should not be

relied upon in making purchasing decision. The

development, release, and timing of any features

or functionality described for Oracles products

remains at the sole discretion of Oracle.

Safe Harbor Statement

Receiving Transactions and Debugging Techniques

Pallavi Vutharkar \ Senior Software Engineer \ Oracle Global Customer Support

Paarthasarathy Kanjamalai \ Senior Software Engineer\ Oracle Global Customer Support

4

AGENDA

Receiving Introduction

Concepts Routing, Destination types, Receiving tolerance, Receiving Options

Processing Modes

Transaction Types - Demo

Data flow for various document types (PO,ISO\IOT)

Troubleshooting commonly reported issues

Overview of Gathering Debug Logs

2012 Oracle Corporation Proprietary and Confidential

5

What is Receiving?

Inventory

Order Entry

Internal shipment Inspect

Transfer

Shop floor

Inventory

Supplier

Shipment

Expense

Receive Deliver

(Sample PO based receiving)

6

Various Procure to Pay Cycles involving Receiving

PO Receipt created against Purchase Orders\ Releases

Internal Sales Order (ISO) - are sourced from your inventory rather than from outside suppliers

Inter-org shipment receipt - Transfers between two inventory orgs

Return Material Authorization (RMA) - to receive goods returned by your customers.

Centralized Procurement - User will create a purchase order in one operating unit, and receives the shipment in a different operating unit.

Dropship Sales Order Receipt - for items that your supplier ships directly to the customer either because you don't stock or currently don't have the items in inventory, or because it's more cost effective for the supplier to ship the item to the customer directly. Drop Shipment was introduced in R11.

Back to Back sales order Receipt Same as above, except the material physically goes to inventory and the tracking is explicitly done on the SO.

7

AGENDA


Concepts Routing, Destination types, Tolerance

and Receiving Options

Major Setups Processing Mode






8

Receiving Concept - Receipt Routing Receipt Routing - Direct Delivery , Inspection Required and Standard Receipt

9

Destination Types Receiving,(Shop floor, Inventory, Expense)

Receiving Concept - Destination Type

10

Tolerance at PO RECEIVING CONTROLS page

Receiving Tolerance Defined at

organization,

supplier,

item, and

order level, with the lowest level overriding previous levels.

Tolerances are defined for

1)On-time delivery

2)Receipt quantity, and

3)Receiving location.

Enforcement options :

ignore,

warn the user or

reject

11

Receiving Options Setup

12

AGENDA


Concepts Routing, Destination types, Receiving tolerance

Receiving Transaction Processor and Processing Modes






13

Receiving Transaction Processor and Processing Modes

Profile option RCV: Processing Mode - determines how the Receiving

Transaction Processor concurrent program is called to process the receipt

entered via Receiving forms

In Online processing mode most commonly used processing mode.When the user saves a transaction, no other

application activity can be performed

until the process completes

In Immediate processing mode When the user saves a transaction, the RTP is called in

the background. User who may then perform

other application activity.

In Batch processing mode, the receiving forms

insert transaction information into the receiving

interface tables. These transactions remain in

the interface table until you run the Receiving

Transaction Processor.

14

AGENDA




Transaction Types Demo (Receive, Inspect, Deliver, Correct, Return)




Q & A Session


15

Transaction Types

Demo Receiving Transactions

16

AGENDA









17

Tables and Processors Involved

RHI - Rcv_Headers_Interface

RTI Rcv_Transactions_Interface

RSH Rcv_Shipment_Headers

RSL Rcv_Shipment_Lines

RT Rcv_Transactions

RLT Rcv_Lot_Transactions

MS -- MTL_SUPPLY

RS -- RCV_SUPPLY

RLS Rcv_Lots_Supply

RSS Rcv_Serials_Supply

Processes involved:

RTP Receiving Transaction Processor

Inventory Transaction Manager

MTLI Mtl_Transactions_Lot_Interface

MSNI Mtl_Serial_Numbers_Interface

MTLT Mtl_Transaction_Lots_Temp

MSNT Mtl_Serial_Number_Temp

MTLN Mtl_Transaction_Lot_Numbers

MUT Mtl_Unit_Transactions

MSN Mtl_Serial_Numbers

MMT Mtl_Material_Transactions

MMTT Mtl_Material_Transactions_Temp

Dataflow charts:

PO receipt for Expense Destination

PO Receipt for Inventory destination

PO receipt for lot controlled items

PO receipt for serial controlled items

ISO /IOT receipt

18

Dataflow : PO Receipt for Expense destination(Standard routing)

RHI

RTI with

receive

Approve the PO

Save receipt

RTP

RSL RT with RECEIVE RCV_SUPPLY

MTL_SUPPLY

Save delivery

RT with DELIVER

RECEIVE

Data inserted in RHI only

in case of ROI RSH

RTI with deliver

Modifyies supply type

code to RECEIVING

deletes record

creates PO Supply type

deletes record

DELIVER

RTP

19

Dataflow: PO Receipt for Inventory destination

RHI

RTI

Approve the PO`

RTP

RSH RSL RT

MTL_SUPPLY

Save receipts

&delivery

(direct routing)

MMTT

MMT INV worker

Data goes to RHI only

in case of ROI creates PO Supply type

deletes record

Receive and Deliver

records saved at same time

20

Dataflow : PO Receipt for Serial controlled items

RHI RTI

Approve the PO

RTP

RSL RT RST

MTL_SUPPLY

Save receipts

&delivery

MMTT

MMT

INV worker

MSNT RSH

MUT


in case of ROI

Delete record

Create record

MSN

21

Dataflow : PO Receipt for lot controlled items

RHI RTI

Approve the PO

RTP

RSL RT RLT

MTL_SUPPLY

Save receipts

&delivery

MMTT

MMT

INV worker

MTLT RSH

MTLN


in case of ROI

Delete record

Create record


Dataflow : ISO /IOT dataflow

Create IOT

OR

Ship confirm ISO

Populate Interface table and call

Inventory Transaction Processor

MTI

MTLI/MSNI

INV worker

MMT

MSN\MUT

MLN\MTLN

Populates Receiving Interface and Calls

Receiving Manager

RTI

MSNI\MTLI

RTP

RSH

RSL

MTL_SUPPLY

RSS\RST

RLS\RLT

Issue Txn in the Source Inv Org

Expected Shipment Transaction in the Destination Inventory Org

Create receipt

RT

RTP INV worker

MMT

MSN\MUT

MLN\MTLN

Receive Txn in the destination Inv

Org MMTT

Delete mtl supply

23

AGENDA







- Type of issues in receiving

- Gathering Debug Logs

- Types of Trace


24

Find form issues/ Form errors :

-- Not able to find receipt, PO is not searchable in find form etc

-- See errors on the form like APP PO 14094 errors or FRM errors.

Data corruption issues Rcv11i

ROI errors - sample resolution

Processor related errors RVTII-060 or RVTTH-115f or other errors in Receiving transaction processor log or Transaction Status Summary form.

Over view of debug log collection

-Various types of debugs

- how to collect

- how / what to read in debug

Types of trace collection

- Concurrent request trace

- Form level SQL trace

- Event trace.

- when to use what.



Typical issues in Receiving

25

Troubleshooting -- Form issues

Typical problem SYMPTOMS in

Find form :

a) Quantity to be received appears

as Zero in the Enter Receipts form

- Although there are quantities yet to

be received, Receiving Transaction

Summary form does not show

quantity has been received.

b) Trying to enter or view Receipts,

find form throws error,

APP-PO-14094 - No records meet

your search criteria.


POSSIBLE CAUSES :

1) This may occur because a previous attempt at the transaction has failed or is incompelte and is stuck in Transaction Status Summary (rcv_transactions_interface) as Pending. Delete the stuck record and redo the transaction.


27

POSSIBLE CAUSES Continued:

2) This error might mean that no eligible records are found for transaction based on

the search criteria provided, verify search criteria is valid.

3) Verify correct receiving inventory organization is chosen - Inventory organization

chosen at the time of receipt should be the same as that on the PO Shipment.

4) PO Shipment is in Approved status - Only open and approved shipments are

eligible for receiving transactions.

5) Verify for any corruption on the PO/Receipt tables using the RCV11i script to

view data at the table level. Shipment_header_id corruption at RCV tables

has been a common issue for the error



References:

RCVRCERC Form Shows Line with Quantity 0 Zero although on PO or Req Summary form Quantity Received is not 0 (Doc ID 1075852.1)

Allow Blind Receiving option is checked for the destination organization.(Doc ID 1448999.1)

How To Troubleshoot APP-PO-14094 When Performing Receiving Related Transactions (Doc ID 444771.1)

How To Remove Pending and Errored Transactions from Transaction Status Summary (Doc ID Note.303544.1 )

RCVTXERT APP-PO-14094 FRM-40212 Multiple Receipt For Intransit Shipment Gives Corrupted Shipment_Header_ID (Doc ID 1198144.1)

28


Demo How To Run RCV11i from Application

Demo- How to use RCV11i

Troubleshooting - Data corruption issues Rcv11i

29

Troubleshooting ROI transactions

Verify the Data Populated in the interface table

Try to Reprocess the Data after resetting the

recommended fields

If Reprocess fails, Review the

Debug Files to find the reason

for failure.

30

VERIFY if the fields are correctly populated according to the transaction

and document type.



31


Transaction type : SHIP

RTI.header_interface_id has to be populated and there must be a corresponding record in RHI

RTI - request_id=null,

processing_request_id=null

order_transaction_id=null,

primary_quantity=null

primary_unit_of_measure=null,

interface_transaction_qty=null

validation_flag = 'Y'

processing_status_code = 'PENDING'

transaction_status_code = 'PENDING

shipment_header_id=null

RHI - processing_request_id=null

receipt_header_id=null



receipt_num=null

REPROCESS

32


Transaction type : RECEIVE

RTI.header_interface_id has to be populated and there must be a corresponding record in RHI










shipment_header_id=null

RHI - processing_request_id=null




receipt_num=null


33

Other Transaction types ACCEPT, REJECT, TRANSFER, DELIVER, RETURN TO RECEIVING, RETURN TO VENDOR, CORRECT

RTI.header_interface_id has to be null and there must be no corresponding record in RHI.












34

For SHIP and RECEIVE transactions :

Reset the RHI record to pending

For exmple, Assume there is 1 RHI and correspondingly 5 RTI records.

During the RTP run, RHI is successfully processed.

4 RTIs successfully processed.

However the 5th RTI failed during the RTP run.

Now to re-process the 5th RTI alone, update 5th RTI to PENDING status and also update RHI

to PENDING (from SUCCESS).

For all other transactions :

As there won't be any RHI, there is no question of resetting RHI record to PENDING status

when RTI is reset for re-processing when it failed in the first RTP run.

References:

Receiving Open Interface (ROI): Features and Links to Useful ROI Documents (Doc ID 559956.1)

How Are Failed Receiving Open Interface (ROI) Transactions Reset? (Doc ID 605300.1)

What Form Functionality Is Available to Delete Or Reprocess ROI Transactions? (Doc ID 726045.1)


Partially Processed ROI records



Debug for further Investigation


36

AGENDA



Major Setups Processing Mode, Receiving Options






- Types of Trace


37

Gathering Debug Logs


Set the Suggested

profiles depending

on the transaction

Perform the Erroring

Transaction

Reset the

Profiles

Collect the Debug

information

Process Flow for collecting debug logs:

38

Receiving interacts with other products like Inventory, Order Management, WMS, OPM, WIP etc. When the receiving process interacts with another product and the error occurs in that product, entire receiving process errors as well.

To diagnose receiving issues across products, debug profiles need to be enabled for receiving as well as the other product.

ENSURE :

a) Profile values should ONLY be set at User Level.

b) Transact minimum number of lines while gathering logs.

c) After replicating - Reset the Profiles immediately.

d) It is easier to gather logs in Immediate\Batch mode than on-line.


Important points to note Debug Logs:

39

:[12-SEP-07 14:19:01] INV_RCV_INTEGRATION_PVT: VALIDATE_LOT_SERIAL_INFO: RTI_ID = : 1811335 [12-SEP-07 14:19:01] INV_RCV_INTEGRATION_PVT: move_lot_serial_info - Number of MTLT Inserted =: 0 with product transaction_id = 1811335 [12-SEP-07 14:19:01] INV_RCV_INTEGRATION_PVT: move_lot_serial_info - Number of MSNT Inserted =: 0 with product transaction_id =1811335 [12-SEP-07 14:19:01] INV_RCV_INTEGRATION_PVT: VALIDATE_LOT_SERIAL_INFO: MOVE_LOT_SERIAL_INFO done :WMSINB-21949 [12-SEP-07 14:19:01] INV_RCV_INTEGRATION_PVT: VALIDATE_LOT_SERIAL_INFO: RTI query done :WMSINB-21964 [12-SEP-07 14:19:01] INV_RCV_INTEGRATION_PVT: VALIDATE_LOT_SERIAL_INFO: TRANSACTION TYPE: RECEIVE: WMSINB-21964 [12-SEP-07 14:19:01] INV_RCV_INTEGRATION_PVT: VALIDATE_LOT_SERIAL_INFO: MTL_SYSTEM_ITEMS query done :WMSINB-22021 [12-SEP-07 14:19:01] INV_RCV_INTEGRATION_PVT: VALIDATE_LOT_SERIAL_INFO: Lot Control Code:1 [12-SEP-07 14:19:01] INV_RCV_INTEGRATION_PVT: VALIDATE_LOT_SERIAL_INFO: Serial Number Control Code:5 [12-SEP-07 14:19:01] INV_RCV_INTEGRATION_PVT: VALIDATE_LOT_SERIAL_INFO: Lot Status Enabled: [12-SEP-07 14:19:01] INV_RCV_INTEGRATION_PVT: VALIDATE_LOT_SERIAL_INFO: SERIAL CONTROLLED: WMSINB-22076 [12-SEP-07 14:19:01] INV_RCV_INTEGRATION_PVT: VALIDATE_LOT_SERIAL_INFO: SERIAL CONTROL CODE: 5 : WMSINB-22076 [12-SEP-07 14:19:01] INV_RCV_INTEGRATION_PVT: VALIDATE_LOT_SERIAL_INFO: SOURCE DOCUMENT CODE: INVENTORY : WMSINB-22076 [12-SEP-07 14:19:01] INV_TRX_MGR: *** Initializing log *** [12-SEP-07 14:19:02] INV_RCV_INTEGRATION_PVT: VALIDATE_LOT_SERIAL_INFO: SERIAL QUANTITY: 1 : WMSINB-23198 [12-SEP-07 14:19:02] INV_RCV_INTEGRATION_PVT: VALIDATE_LOT_SERIAL_INFO: SERIAL EXISTS: 1 : WMSINB-23233 [12-SEP-07 14:19:02] INV_RCV_INTEGRATION_PVT: VALIDATE_LOT_SERIAL_INFO: SERIAL NUMBER: RCV001 : WMSINB-23233 [12-SEP-07 14:19:02] INV_RCV_INTEGRATION_PVT: VALIDATE_LOT_SERIAL_INFO: CURR STATUS: 5 : WMSINB-23233 [12-SEP-07 14:19:02] INV_RCV_INTEGRATION_PVT: VALIDATE_LOT_SERIAL_INFO: CURR ORG ID: 209 : WMSINB-23233 [12-SEP-07 14:19:02] INV_RCV_INTEGRATION_PVT: VALIDATE_LOT_SERIAL_INFO: CURR LPN ID: : WMSINB-23233 [12-SEP-07 14:19:02] INV_RCV_INTEGRATION_PVT: VALIDATE_LOT_SERIAL_INFO: CURR LOT NUM: : WMSINB-23233 [12-SEP-07 14:19:02] INV_RCV_INTEGRATION_PVT: VALIDATE_LOT_SERIAL_INFO: INSPECT STS: : WMSINB-23233 [12-SEP-07 14:19:02] INV_RCV_INTEGRATION_PVT: VALIDATE_LOT_SERIAL_INFO: GROUP MARK ID: 56702 : WMSINB-23233 [12-SEP-07 14:19:02] INV_RCV_INTEGRATION_PVT: VALIDATE_LOT_SERIAL_INFO: RESTRICT RCPT SER: 2 : WMSINB-23233 [12-SEP-07 14:19:02] INV_RCV_INTEGRATION_PVT: VALIDATE_LOT_SERIAL_INFO: ASN LINE FLAG: N : WMSINB-23276 [12-SEP-07 14:19:02] INV_RCV_INTEGRATION_PVT: VALIDATE_LOT_SERIAL_INFO: SERIAL NOT ENTERED ON PARENT: WMSINB-23287 [12-SEP-07 14:19:02] INV_RCV_INTEGRATION_PVT: For Intransit receipt the serial number org does not match the sending org! [12-SEP-07 14:19:02] INV_RCV_INTEGRATION_PVT: Exitting VALIDATE_LOT_SERIAL_INFO - execution error:2007-09-12 02:12:02:WMSINB-23435 [12-SEP-07 14:19:02] INV_RCV_INTEGRATION_PVT: STACKED ERROR MESSAGES : Fail to validate serials [12-SEP-07 14:19:02] inv_receiving_transaction: TXN_COMPLETE - Enter txn_complete : 10: 2007-09-12 02:12:02 [12-SEP-07 14:19:02] inv_receiving_transaction: TXN_COMPLETE - Parameters passed : 10.1: p_group_id - 1811335 [12-SEP-07 14:19:02] inv_receiving_transaction: TXN_COMPLETE - Parameters passed : 10.2: p_txn_status - FALSE [12-SEP-07 14:19:02] inv_receiving_transaction: TXN_COMPLETE - Parameters passed : 10.3: p_txn_mode - PROCESSOR

Date / Time

Package: Procedur

e

Variable

Value

Error

Sample Outputs - Inventory Debug log

Stored in inventory debug log file , full file name and patch mentioned on profile option INV: Debug File


TIMESTAMP MODULE MESSAGE_TEXT

13-MAY-08 15:45:21 po.plsql.RCV_ROI_PREPROCESSOR. Entering preprocessor. Request_id = 3388603,Group_id=514

13-MAY-08 15:45:21 po.plsql.RCV_ROI_PREPROCESSOR. RCV_FAIL_IF_LINE_FAILS profile option =N

13-MAY-08 15:45:21 po.plsql.RCV_ROI_PREPROCESSOR. Calling the Garbage collector

13-MAY-08 15:45:21 po.plsql.RCV_ROI_PREPROCESSOR. Calling explode_lpn

13-MAY-08 15:45:21 po.plsql.RCV_ROI_PREPROCESSOR. After explode_lpn

13-MAY-08 15:45:21 po.plsql.RCV_ROI_PREPROCESSOR. After update to order_transaction_id

13-MAY-08 15:45:21 po.plsql.RCV_ROI_PREPROCESSOR. Opening transactions cursor. x_request_id=3388603

x_group_id=514

13-MAY-08 15:45:21 po.plsql.RCV_ROI_PREPROCESSOR. Opened transactions cursor.

13-MAY-08 15:45:21 po.plsql.RCV_ROI_PREPROCESSOR. enter loop

13-MAY-08 15:45:21 po.plsql.RCV_ROI_PREPROCESSOR. after loop

13-MAY-08 15:45:21 po.plsql.RCV_ROI_PREPROCESSOR. Exit preprocessor

13-MAY-08 15:45:22 po.plsql.RCV_ERROR_PKG.RCV_ERR logging error on column INTERFACE_TRANSACTION_ID

13-MAY-08 15:45:22 po.plsql.RCV_ERROR_PKG.RCV_ERR error stack from call to po_interface_call





Sample Outputs - FND Debug log

Stored in table FND_DEBUG_MESSAGES controlled by profile option FND: Debug Log

41


Important points to note - Debug Logs:

Online Immediate Batch

FND debug log is collected with max log sequence number saved before and after the transaction

Only event trace is possible using profile initialize custom Applicable for ISO, IOT and receipts made in online mode.

FND log and trace can be gathered from request id as

well as with max log

sequence number collected

before and after

Event trace for binds or concurrent trace enabled at

sysadmin-> Define ->Program

Applicable for receipts made with processing mode

Immediate

FND log and trace can be gathered from request id as

well as with max log

sequence number collected

before and after .

Debug options on request submission can be used for

tracing.

Applicable for receitps made in processing mode Batch

and ROI transactions.

Its easier to collect debug in batch - immediate - online in that order

References:

How to Generate Receiving Transaction Debug Statements in 11.5.10 and R12 (Doc ID 299497.1) for details. How to Generate Receiving Transaction Debug Statements in 11.5.6 11.5.9 (Doc ID 431053.1) How to Trace the Receiving Transactions (Doc ID 372432.1) Simple Debug Setup For Receiving Transaction Activity (Doc ID 1063222.1)

42

Troubleshooting -- Processor related errors sample debugging

RTP error: RVTII-060: Subroutine INV_TXN_MANAGER_PUB.Process_Transactions() returned error

43


RTP error: RVTII-060: Subroutine INV_TXN_MANAGER_PUB.Process_Transactions() returned error

44


Inventory debug log for the error shows the following detailed error: no data found mtl_material_transactions

P.S: All the debug messages are pre-coded by development to capture possible errors, some errors might evade this capturing and hence may not be reported on the log. In such cases, there is no way to know the possible cause without going through the underlying code. In this case you may drill down further in the package INV_LPN_TRX_PUB and investigate by creating new debug messages .

45


46

AGENDA



Major Setups Processing Mode, Receiving Options






- Types of Trace


47

1)FORM trace


TroubleshootingTypes of Trace Form Trace

References :

Steps To Take FRD Trace in 11.5.10 & R12 (Doc ID 867943.1)

How To Create Forms And Database Level Trace (Doc ID 564817.1)

48

Trace using profile option : Initialization SQL Statement Custom


Troubleshooting Types of Trace Event Trace

Reference - Note.135389.1 - Using profile option 'Initialization SQL Statement - Custom

49

Enable trace from Sysadmin -> define


Troubleshooting Types of Trace concurrent Trace

50

Concurrent request trace for Batch mode.


Troubleshooting Types of Trace


Start using the procurement community instead of raising new SR

https://communities.oracle.com/portal/server.pt/community/procurement/230

For Next Webcasts

Please Review Procurement Advisor Webcast Calendar [ID 1456150.1]

New Features and enhancements

Incorporated in the Procurement

Rollup Patch

14254641:R12.PRC_PF.B

Tuesday,

December 4,

2012 at 14:00

London

Document 1501064.1

Approval Management Engine

(AME) New Features, Setup and

Use for Purchase Orders

Thursday,

December 6, 2012

at 14:00 London

Document 1501063.1

How to Solve Approval Errors in

Procurement

Tuesday,

December 18,

2012 at 14:00

London

Document 1504425.1

53

Are You Ready

To Get

Proactive?

Avoid the unexpected

Dont leave value on the table

Lower overall organizational costs through preventative

maintenance

Reduce risks and maximize uptime

Achieve resolution faster

Streamline and simplify your daily operations

Get even more through connection

Discover more about Get Proactive https://support.oracle.com/CSP/main/article?cmd=show

&type=ATT&id=1385165.1:DISCOVER

ACT Get Proactive Access proactive capabilities available for your products

by visiting the product pages at My Oracle Support;

Article ID 432.1

Contact the Get Proactive team today for help getting started

[email protected]



THANK YOU