Sunteți pe pagina 1din 3

PowerView is On [My Core Products] Product Line: Internal ...

ERP (Available) (0) Contact Us Help

Dashboard Knowledge Service Requests Patches & Updates Community

Give Feedback...

Copyright (c) 2018, Oracle. All rights reserved.

Receiving Error: Cust_Trx_Type_id is required for Invoice Interface. (Doc ID 1951706.1) To Bottom

In this Document Was this document helpful?

Symptoms Yes
No
Cause
Solution
Document Details

APPLIES TO: Type:


PROBLEM
Status:
PUBLISHED
Oracle Order Management - Version 11.5 and later Last Major
Jan 9, 2017
Information in this document applies to any platform. Update:
Apr 25, 2018
Last Update:

SYMPTOMS
Related Products
A sales order has been entered and shipped, yet will not invoice. Oracle Order Management
The sales order line status is Awaiting Invoice Interface - Incomplete Data.
The following processing error message occurs:
Information Centers
ERROR Information Center: Oracle Order
Order Line Processing messages Management [1395754.2]
Cust_Trx_Type_id is required for Invoice Interface.

STEPS Document References


1. Responsibility: Order Management Super User No References available for this
2. Navigation: Orders, Returns > Sales Orders document.
3. Enter and Book sales order
4. Navigation: Shipping > Release Sales Orders > Release Sales Orders
Recently Viewed
5. Pick release order
6. Navigation: Inventory > Move Orders > Transact Move Orders Interoperability Notes Oracle EBS
7. Complete move transaction 12.2 with Oracle Database 12c
Release 1 [1926201.1]
8. Navigation: Shipping > Transactions INV DEBUG: How to get Debug
9. Ship sales order Information for Inventory Material
Transactions [148651.1]
This case can happen with Return Order [Reference or Non-Reference ] as well. For this, some sample steps are: Progressing SO Line Displays
"Cust_trx_type_id Is Required For
Invoice Interface" Message
1. Order Management Super Users>Orders, Returns> Sales Order>
[1367912.1]
2. Use Reference field to map to Sales Order.
Complete Checklist for Manual
3. Select the Book button . Upgrades to Oracle Database 12c
4. Sales Order is approved and then items are successfully receipted in. Release 1 (12.1) [1503653.1]
5. When attempt to progress RMA, you will get the following error message: Transactions Stuck In Table
Cust_trx_type_id is required for Invoice Interface MTL_TRANSACTIONS_INTERFACE
Failing With Error Invalid
Distribution Account [2132578.1]
BUSINESS IMPACT Show More
Due to this issue, users cannot invoice for this sales order.

CAUSE

The issue is caused by the following setup: customer transaction type/credit memo type is not assigned to the line and/or header
transaction type.

SOLUTION

Please perform the following steps to resolve the issue by your own:

1. Login to SQLPLUS using user APPS.

2. Execute the attached script cust_trx_type.sql. This script will take the Line_Id as input parameter. Please pass the Line_Id of one of the
problematic Line. You can get the Line_Id of the Sales Order Line through front end via following navigation:

A. Query the Sales Order from Sales Order form.

B. Go to Line Items tab. Place your cursor on problematic Sales Order Line and then, go to Help > Diagnostics > Examine

For Block = LINE, Select the Field as LINE_ID and note down the value.

3. If this script finds the issue as your selected option, It will print the following as the output

Please refer to file /XX/YY/ZZ/l4369569.dbg to overcome this issue.


OR
To retrieve the Action Plan, navigate to Order Management > Run Requests. Then choose: Diagnostics: OM Debug File Retrieval.
Parameters: Give the name of the debug file as l4369569.dbg ( Please make sure to include the .dbg extension of the file name).
To view and save the Solution Action Plan, navigate to View > Requests > Relevant Request_id (button). Click View Output > Save file
as "filename.txt".

Please note: A. Here, XX/YY/ZZ is a directory path taken for an example. It will be same as the the value for profile options "OM: Debug Log
Directory"

B. l1269559.dbg will be different in your case. Here, l4369569.dbg, it is taken as an example.

In this case, action plan in the file will guide you with the missing setup and what needs to be setup and where needs to be setup.

Attachment l4369569.dbg is a sample output file [Action Plan to resolve this issue] generated for a similar case.

Didn't find what you are looking for? Ask in Community...

Attachments
cust_trx_type script (42.31 KB)
Sample Output of Script [l4369569.dbg] (6.68 KB)

Related
Products

Oracle E-Business Suite > Order Management > Order Management > Oracle Order Management > Finance & Accounting > Invoicing and Credit Issues (includes 11.5.x Interface to AR issues)

Back to Top
Copyright (c) 2018, Oracle. All rights reserved. Legal Notices and Terms of Use Privacy Statement

S-ar putea să vă placă și