Open interface document - MTL_TRANSACTIONS_INTERFACE

Hi,
I'm looking for the open interface document related the MTL_TRANSACTIONS_INTERFACE (on hand quantities)
Regards

http://download.oracle.com/docs/cd/B40089_07/current/acrobat/120scmapi.pdf
Regards
Bilal SARIOZ

Similar Messages

Reg : Open Interface Tables in Oracle Manufacturing Suite

Hi Gurus,
Can anybody help me providing link to get Oracle Open Interface Tables related to Manufacturing ( PO.INV,BOM,WIP,DRP/MRP ) Suire and their usage details ( i know Oracle Documentation has all these details in Open Interface documents ), i am looking for short white papers or brief notes on the Open Interface tables.
Please help
Regards

Sure there is quite good documetation on Open interface tables for the Oracle Manfacturing suite.... You can explore matalink for getting the latest documentation. or you can browse http://oracletimes.blogspot.com which has the resource links for various documetation.
Thanks
Navin

AP error while submitting "Payable Open interface"

Hello,
I am trying to run the request 'Payables open interface'. I got the output once and the error was because the supplier site was invalid. I created a supplier site saved it and ran the request again. Now, I am getting the following error.
Payables: Version : 11.5.0 - Development
Copyright (c) 1979, 1999, Oracle Corporation. All rights reserved.
APXIIMPT module: Payables Open Interface Import
Current system time is 21-JUN-2009 08:15:01
+-----------------------------
| Starting concurrent program execution...
+-----------------------------
Arguments
p_source='SQLLDR'
p_batch_name='N/A'
p_purge_flag='N'
p_trace_switch='N'
p_debug_switch='N'
p_summary_flag='N'
p_commit_batch_size='1000'
p_user_id='1007990'
p_login_id='2532036'
APPLLCSP Environment Variable set to :
XML_REPORTS_XENVIRONMENT is :
/u02/applmgr/lmtestora/8.0.6/guicommon6/tk60/admin/Tk2Motif_UTF8.rgb
XENVIRONMENT is set to: /u02/applmgr/lmtestora/8.0.6/guicommon6/tk60/admin/Tk2Motif_UTF8.rgb
Current NLS_LANG and NLS_NUMERIC_CHARACTERS Environment Variables are :
American_America.UTF8
Spawned Process 1752
MSG-01104: (Before Report) Modified file
MSG-00000: p_purge_flag :N
MSG-00000: c_nls_yes :Yes
MSG-00000: c_nls_no :No
MSG-00000: p_summary_flag :N
MSG-00000: p_nls_summary :No
MSG-00000: p_nls_purge :No
REP-1419: 'beforereport': PL/SQL program aborted.
Report Builder: Release 6.0.8.27.0 - Production on Sun Jun 21 08:15:02 2009
(c) Copyright 1999 Oracle Corporation. All rights reserved.
Enter Username:
Start of log messages from FND_FILE
End of log messages from FND_FILE
Program exited with status 1
Concurrent Manager encountered an error while running Oracle*Report for your concurrent request 2776668.
Review your concurrent request log and/or report output file for more detailed information.
Executing request completion options...
Finished executing request completion options.
Concurrent request completed
I am trying this for first time. Any help is highly appreciated.
Thanks.

Hi,
Please go through the following documents and see if it helps.
Note: 107628.1- Payables Open Interface Invoice Import Troubleshooting Guide (APXIIMPT)
https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=107628.1
Note: 220355.1- APXIIMPT-Payables Open Interface Import Fails Rep-1419:'Beforereport' : Pl/Sql Program Aborted
https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=220355.1
Regards,
Hussein

SAMPLE RECEIVING OPEN INTERFACE SCRIPT(ROI 이용자를 위한 SCRIPT)

제품: MFG_PO
작성날짜 : 2006-05-11
SAMPLE RECEIVING OPEN INTERFACE SCRIPT(ROI 이용자를 위한 SCRIPT)
================================================================
PURPOSE
Receiving Open Interface(ROI)를 좀더 쉽게 사용할 수 있도록 만들어진
tool이라고 할 수 있다. 이 script를 이용을 통해 user는 PO no, user id,
Org id를 입력하면 script는 PO에서 최소한의 data를 가져와 receiving
transaction을 생성하기 위해 ROI에 data를 입력한다.
Receiving Transaction Processor는 insert 된 data를 실행한다.
Explanation
Instructions:
1.Script exroi.sql을 local computer에 copy 하거나 sqlplus 환경의 text
edior에 script 내용을 cut&paste 한다.
2.사용가능한 PO no, User id, Org id를 결정한다.
3.sqlplus prompt에서 아래와 같이 입력한다.
SQL> @ezroi.sql
4.PO no, User id, Org id를 입력하라는 prompt를 볼 수 있을 것이다.
5.exroi.sql script를 관련된 PO data를 가져와 rcv_headers_interface 및
rcv_transactions_interface tables에 insert 한다.
만일 PO shipment lind이 closed, cancelled, fully received 되었다면
ROI table에 data를 insert 하지 않는다.
Note: 이 script가 data를 validate 하진 않으며,ROI API 자체 validation
이 실행될 뿐이다.
6.Script가 끝나면 Receiving Transaction Processor를 실행하여 insert 된
lines을 처리할 수 있다. Transaction Status Summary 화면을 통해 실행된
line이 pending 인지 error 상태인지 확인할 수 있다.
Notes:
1.Org_id parameter 값을 찾는법:
a) Application에 접속, Help> Diagnostics> Examine으로 이동.
Block:$Profile$, Field: ORG_ID 를 선택한다.
b) ORG_ID 값을 note 해 놓고 ORG_ID prompt시 이 값을 입력한다.
2.User_Name parameter 값을 찾는법:
a) Application에 접속, Help> Diagnostics> Examine으로 이동.
Block:$Profile$, Field: USER_NAME 를 선택한다.
b) USER_NAME 값을 note 해 놓고 USER_NAME prompt시 이 값을 입력한다.
Example
"eZROI.sql' script...
--*** eZROI ***
--*** by ***
--*** Preston D. Davenport ***
--*** Oracle Premium Applications Support ***
--*** Oracle Worldwide Global Support Services ***
--*** Date: 23-JUL-2003 - Beta release ***
--*** Date: 09-SEP-2003 - Rev A Added multi- ***
--*** shipment line capability ***
--*** Parameters: ***
--*** ORG_ID Organization ID ***
--*** USER_NAME FND User Name ***
--*** PO_NUMBER Purchase Order Number ***
--*** This script intended for a standard Purchase ***
--*** Order document to be inserted into the Oracle ***
--*** Receiving Open Interface (ROI) via the standard ***
--*** Oracle open interface api for a simple Receive ***
--*** transaction. ***
--*** Note: This script only considers open Purchase ***
--*** Orders. This script will not allow over- ***
--*** receipt, cancelled or closed PO's to be ***
--*** inserted into the ROI and received ***
CLEAR BUFFER
SET VERIFY OFF
SET LINESIZE 140
SET PAGESIZE 60
SET ARRAYSIZE 1
SET SERVEROUTPUT ON SIZE 100000
SET FEEDBACK OFF
SET ECHO OFF
DECLARE
X_USER_ID NUMBER;
X_PO_HEADER_ID NUMBER;
X_VENDOR_ID NUMBER;
X_SEGMENT1 NUMBER;
X_ORG_ID NUMBER;
X_LINE_NUM NUMBER;
BEGIN
DBMS_OUTPUT.PUT_LINE('***ezROI RCV API Insert Script***');
SELECT PO_HEADER_ID , VENDOR_ID , SEGMENT1 , ORG_ID
INTO X_PO_HEADER_ID , X_VENDOR_ID , X_SEGMENT1 , X_ORG_ID
FROM PO_HEADERS_ALL
WHERE SEGMENT1 = '&PO_NUMBER'
AND ORG_ID = &ORG_ID;
SELECT USER_ID INTO X_USER_ID
FROM FND_USER
WHERE USER_NAME = UPPER('&USER_NAME');
INSERT INTO RCV_HEADERS_INTERFACE
HEADER_INTERFACE_ID ,
GROUP_ID ,
PROCESSING_STATUS_CODE ,
RECEIPT_SOURCE_CODE ,
TRANSACTION_TYPE ,
LAST_UPDATE_DATE ,
LAST_UPDATED_BY ,
LAST_UPDATE_LOGIN ,
VENDOR_ID ,
EXPECTED_RECEIPT_DATE ,
VALIDATION_FLAG
SELECT
RCV_HEADERS_INTERFACE_S.NEXTVAL ,
RCV_INTERFACE_GROUPS_S.NEXTVAL ,
'PENDING' ,
'VENDOR' ,
'NEW' ,
SYSDATE ,
X_USER_ID ,
0 ,
X_VENDOR_ID ,
SYSDATE ,
'Y'
FROM DUAL;
DECLARE
CURSOR PO_LINE IS
SELECT PL.ITEM_ID , PL.PO_LINE_ID , PL.LINE_NUM ,
PLL.QUANTITY , PL.UNIT_MEAS_LOOKUP_CODE ,
MP.ORGANIZATION_CODE , PLL.LINE_LOCATION_ID ,
PLL.CLOSED_CODE , PLL.QUANTITY_RECEIVED ,
PLL.CANCEL_FLAG, PLL.SHIPMENT_NUM
FROM PO_LINES_ALL PL ,
PO_LINE_LOCATIONS_ALL PLL ,
MTL_PARAMETERS MP
WHERE PL.PO_HEADER_ID = X_PO_HEADER_ID
AND PL.PO_LINE_ID = PLL.PO_LINE_ID
AND PLL.SHIP_TO_ORGANIZATION_ID = MP.ORGANIZATION_ID;
BEGIN
FOR CURSOR1 IN PO_LINE LOOP
IF CURSOR1.CLOSED_CODE IN ('APPROVED','OPEN')
AND CURSOR1.QUANTITY_RECEIVED < CURSOR1.QUANTITY
AND NVL(CURSOR1.CANCEL_FLAG,'N') = 'N'
THEN
INSERT INTO RCV_TRANSACTIONS_INTERFACE
INTERFACE_TRANSACTION_ID ,
GROUP_ID ,
LAST_UPDATE_DATE ,
LAST_UPDATED_BY ,
CREATION_DATE ,
CREATED_BY ,
LAST_UPDATE_LOGIN ,
TRANSACTION_TYPE ,
TRANSACTION_DATE ,
PROCESSING_STATUS_CODE ,
PROCESSING_MODE_CODE ,
TRANSACTION_STATUS_CODE ,
PO_LINE_ID ,
ITEM_ID ,
QUANTITY ,
UNIT_OF_MEASURE ,
PO_LINE_LOCATION_ID ,
AUTO_TRANSACT_CODE ,
RECEIPT_SOURCE_CODE ,
TO_ORGANIZATION_CODE ,
SOURCE_DOCUMENT_CODE ,
DOCUMENT_NUM ,
HEADER_INTERFACE_ID ,
VALIDATION_FLAG
SELECT
RCV_TRANSACTIONS_INTERFACE_S.NEXTVAL ,
RCV_INTERFACE_GROUPS_S.CURRVAL ,
SYSDATE ,
X_USER_ID ,
SYSDATE ,
X_USER_ID ,
0 ,
'RECEIVE' ,
SYSDATE ,
'PENDING' ,
'BATCH' ,
'PENDING' ,
CURSOR1.PO_LINE_ID ,
CURSOR1.ITEM_ID ,
CURSOR1.QUANTITY ,
CURSOR1.UNIT_MEAS_LOOKUP_CODE ,
CURSOR1.LINE_LOCATION_ID ,
'RECEIVE' ,
'VENDOR' ,
CURSOR1.ORGANIZATION_CODE ,
'PO' ,
X_SEGMENT1 ,
RCV_HEADERS_INTERFACE_S.CURRVAL ,
'Y'
FROM DUAL;
DBMS_OUTPUT.PUT_LINE('PO line: '||CURSOR1.LINE_NUM||' Shipment: '||CURSOR1.SHIPMENT_NUM||' has been inserted into ROI.');
ELSE
DBMS_OUTPUT.PUT_LINE('PO line '||CURSOR1.LINE_NUM||' is either closed, cancelled, received.');
END IF;
END LOOP;
DBMS_OUTPUT.PUT_LINE('*** ezROI COMPLETE - End ***');
END;
COMMIT;
END;
SET VERIFY ON
Reference Documents
Note 245334.1

I have the same problem on ESXI 5.5 for over a month now, tried the patches, tried the LTS kernel which others say results in an immediate result without patches, nothing seems to work and nobody seems to be able to offer a solution.
Did you make any progress ??
Error! Build of vmblock.ko failed for: 3.10.25-1-lts (x86_64)
Consult the make.log in the build directory
/var/lib/dkms/open-vm-tools/2013.09.16/build/ for more information.
make[2]: *** No rule to make target '/var/lib/dkms/open-vm-tools/2013.09.16/build/vmblock/linux/inode', needed by '/var/lib/dkms/open-vm-tools/2013.09.16/build/vmblock/vmblock.o'. Stop.
Makefile:1224: recipe for target '_module_/var/lib/dkms/open-vm-tools/2013.09.16/build/vmblock' failed
make[1]: *** [_module_/var/lib/dkms/open-vm-tools/2013.09.16/build/vmblock] Error 2
make[1]: Leaving directory '/usr/src/linux-3.10.25-1-lts'
Makefile:120: recipe for target 'vmblock.ko' failed
Last edited by crankshaft (2014-01-10 11:32:32)

Material Transaction Open Interface Error

Hi,
I'm getting following Error in Cost Manager after running the Transaction Open Interface,
Interface work well to update the stocks, but it returns error Layer Cost Worker Concurrent.
Error1
Bills of Material: Version : 12.0.0
Copyright (c) 1979, 1999, Oracle Corporation. All rights reserved.
CMCLCW module: Layer Cost Worker
Current system time is 10-OCT-2012 14:16:32
debug_level = 0
CM_EXTENDED_DEBUG = 2
CSTPLCIN.COST_INV_TXN:CSTPLVCP.interorg (160): ORA-00001: unique constraint (INV.MTL_CST_TXN_COST_DETAILS_U1) violated
Failing Transaction ID is 28227
Start of log messages from FND_FILE
Standard costing org : -1
Interorg transfer send org: (consume layers) ...
84:5
28227:1
Entering get_layers_consumed for transaction 28227 and a required quantity of 2 with a consumption mode of NORMAL
Trying custom layers
There are 0 custom layers
General consumption
Using SQL SELECT inv_layer_id,layer_quantity FROM cst_inv_layers WHERE layer_id = :i AND inv_layer_id <> :j AND NVL(transaction_source_id,-2) <> :k AND layer_quantity > 0 ORDER BY creation_date, inv_layer_id with 1,-1,-1
End of log messages from FND_FILE
No completion options were requested.
Output is not being printed because:
The print option has been disabled for this report.
Deleting output file.
Concurrent request completed
Current system time is 10-OCT-2012 14:16:32
Error2
Bills of Material: Version : 12.0.0
Copyright (c) 1979, 1999, Oracle Corporation. All rights reserved.
CMCLCW module: Layer Cost Worker
Current system time is 10-OCT-2012 14:16:32
debug_level = 0
CM_EXTENDED_DEBUG = 2
CSTPLCIN.COST_INV_TXN:CSTPACDP.insert_account (10) ORA-01400: cannot insert NULL into ("INV"."MTL_TRANSACTION_ACCOUNTS"."BASE_TRANSACTION_VALUE")
Failing Transaction ID is 28228
Start of log messages from FND_FILE
Standard costing org : -1
----------l_to_method---------
=5
Interorg transfer receiving org: (create layers) ...
90:5
28228:2
i_txn_id 28228
1 records updated in mclacd for 15005
1 records copied from mclacd for 15005
interorg_cost_txn(..)
transaction_id:28228
org_id:90
i_txn_org_id:90
i_txf_org_id:84
i_txf_txn_id:28227
i_exp_item:0
i_fob_point:0
l_snd_rcv:2
l_from_org:84
l_to_org:90
Sending org distributions
Receiving org distributions
l_intransit:0
Calling Inventory acct
In Inventory_accounts
In insert accounts
l_ussgl_tc :
Payable amount(l_value): acct: 414240
In insert accounts
l_ussgl_tc :
DS - others Exception, sqlcode = -1400
End of log messages from FND_FILE
No completion options were requested.
Output is not being printed because:
The print option has been disabled for this report.
Deleting output file.
Concurrent request completed
Current system time is 10-OCT-2012 14:16:32
My Coding
insert into mtl_transactions_interface
(transaction_type_id, --------------1
transaction_uom, --------------2
transaction_date, --------------3
organization_id, --------------4
transaction_quantity, --------------5
last_update_date, --------------6
last_updated_by, --------------7
creation_date, --------------8
created_by, --------------9
transaction_mode, --------------10
process_flag, --------------11
source_header_id, --------------12
source_line_id, --------------13
source_code, --------------14
transaction_header_id, --------------15
inventory_item_id, --------------16
transaction_interface_id, --------------17
subinventory_code, --------------18
distribution_account_id, --------------19
transaction_cost, --------------20
transaction_reference, --------------21
transfer_organization, --------------22
transfer_subinventory, --------------23
-- transfer_cost, --------------24
primary_quantity, --------------25
lock_flag,
transaction_action_id,
transaction_source_type_id,
dst_segment1,
dst_segment2,
dst_segment3,
dst_segment4,
dst_segment5,
dst_segment6)
values
(v_trx_type_id, --------------1 ------transaction type id
i.uom_code, --------------2 ------transaction_UoM
sysdate, i.creation_date, ------------3 ------trasnsaction date
i.from_organization_id, --------------4 ------org id
nvl(i.quantity_delivered, i.quantity), --------------5 ------quantity
sysdate, --------------6 ------Last update date
-1, --------------7 ------last updated by
sysdate, --------------8 ------creation date
-1, --------------9 ------creation by
3, --------------10 ------transactio mode
1, --------------11 ------process flag
1, --------------12 ------source_header_id
1, --------------13 ------source_line_id
i.mrn_trx_number, --'MRN Interface', --------------14 ------source code
'999999', --------------15 ------transaction header id
v_item_id, --------------16 ------inventory item id
xx_mrn_mtl_trx_int_seq.nextval, --------------17 ------transaction_interface_id
i.from_subinventory_code, --------------18 ------sub inventory
v_code_id, --------------19 ------code compbination
v_item_cost, --------------20 ------cost
'MRN Interface', --------------21 ------reference
i.organization_id, --------------22
i.to_subinventory_code, --------------23
-- (nvl(i.quantity_delivered, i.quantity) * v_item_cost) --------------24
nvl(i.quantity_delivered, i.quantity),
2,
v_trx_action_id,
v_trx_source_type_id,
               '01',
               '00',
               '000',
               '141013',
               '000000',
               '00000');
Thanks

Can you get the following for the errored transaction?
SELECT   transaction_id txnid, transfer_transaction_id txfrtxnid
       , organization_id orgid, transfer_organization_id txfrorgid, subinventory_code subinv
       , transfer_subinventory txfrsubinv, cost_group_id cgid
       , transfer_cost_group_id txfrcgid       , prior_costed_quantity
       , transfer_prior_costed_quantity       , rcv_transaction_id rcvtxnid
       , transaction_action_id txnactid       , transaction_source_type_id txnsrctypid
       , transaction_type_id txntypid       , costed_flag cstdflg
       , transaction_group_id       , inventory_item_id invitmid
       , transaction_source_id wip_entity_id       , transaction_cost txncst
       , shipment_number shipnum       , new_cost       , prior_cost
       , actual_cost       , project_id       , transaction_uom txnuom
       , transaction_quantity txnqty       , primary_quantity priqty       , prior_costed_quantity priorqty
       , currency_code altcurr       , currency_conversion_rate currconvrt       , currency_conversion_date currconvdt
       , TO_CHAR (mmt.creation_date, 'dd-mm-yyyy hh24:mi:ss') creation_date
       , TO_CHAR (mmt.last_update_date, 'dd-mm-yyyy hh24:mi:ss')last_upd_date
       , ERROR_CODE errcode
       , error_explanation errexpl
    FROM mtl_material_transactions mmt
   WHERE transaction_id IN (&Trx_Id)   -- Error transaction_id
ORDER BY transaction_id DESC

EAM Asset Number Open Interface - Technical Reference docs required

Hello,
I'm developing a migration of EAM assets.
I have no issue by filling the interface tables MTL_EAM_ASSET_NUM_INTERFACE and MTL_EAM_ATTR_VAL_INTERFACE and then running the "Import Asset Number" standard functionallity.
But, I need to work with genealogy information. The table MTL_OBJECT_GENEALOGY_INTERFACE is used to relate parent and child assets .. but when I run "Import Asset Number" nothing happens .. I mean, if I query the asset in the application, I can see it without the parent asset association.
Now, I'm trying to use the API's for EAM, but until now without success ...
I saw that there exist a "Technical Reference" document for EAM .. but I can't find it ...
Do you know from where I can download it ? ...
or, if the mentioned document does not exist anymore
Do you know where I can find documents about eAM Open Interface, more detailed than the information of the "Implementation Guide" ?
Thanks in advance,
Sergio Maestri

Did the original poster ever find a resolution to this issue? I'm seeing the same behavior. I examined all of the documentation listed in the post already (though I can't find doc 256410.1).
In my example, my child asset is a rebuildable asset, but that won't always be the case. Even though I see that the Import Asset Genealogy request has run successfully, my record doesn't change. I should get an error as I'm deliberately trying to create a new parent-child relationship with a child that currently has a parent. This gives me an error message in the Maintenance Super User -> Asset -> Configuration History page.
Here's what I did to create the import record:
insert into MTL_OBJECT_GENEALOGY_INTERFACE
(INTERFACE_HEADER_ID, LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, BATCH_ID, GROUP_ID, OBJECT_TYPE, PARENT_OBJECT_TYPE, GENEALOGY_ORIGIN, GENEALOGY_TYPE, PROCESS_STATUS, IMPORT_MODE,
ORGANIZATION_CODE, INVENTORY_ITEM_ID, SERIAL_NUMBER, PARENT_ORGANIZATION_CODE, PARENT_INVENTORY_ITEM_ID, PARENT_SERIAL_NUMBER, START_DATE_ACTIVE) VALUES
(MTL_OBJECT_GEN_INTERFACE_S.NEXTVAL, sysdate, 1068, sysdate, 1068, 100, 100, 2, 2, 3, 5, 'P', 0,
'EM1', 8319, 'Battery1000', 'EM1', 7885, 'FL1020', sysdate);
The only way I could get this to work was to set the MTL_OBJECT_GENEALOGY_INTERFACE.PROCESS_STATUS = 'R' and then call EAM_GENEALOGY_IMPORT_PUB.import_genealogy via PL/SQL. If I did that, I didn't get an error back from the PL/SQL call, but I did get a decent message in the ERROR_MESSAGE field of the interface table: "Child Battery1000 already has a parent FL1030 from 15-DEC-2006 10:43:50; the open period from 16-AUG-2013 15:55:52 overlaps with it."
The Parameters dialog for the Import Asset Genealogy request only works if PROCESS_STATUS = 'P' and the EAM API only works if PROCESS_STATUS = 'R'.
Is it me or does this seem poorly thought out or at the very least poorly documented?

Move transaction open interface

I import move transaction through Move transaction open interface.
The 11i open interface user guide tells that for WIP transaction completion, I need to insert a row into WIP_MOVE_TXN_INTERFACE, and also a line into CST_COMP_SNAP_INTERFACE.
What is the purpose of the table CST_COMP_SNAP_INTERFACE ?
I have tried a scrap transaction through Oracle Applications screen. I have compared the result when I insert the same transaction in WIP_MOVE_TXN_INTERFACE (no line is inserted into CST_COMP_SNAP_INTERFACE table).
And the result seem to be the same (data in table CST_COMP_SNAPSHOT are the same with the 2 method). So , why should I also insert a line into the CST_COMP_SNAP_INTERFACE table ?
Thank in advance.

Hi,
What is the application release?
Was this working before? If yes, any changes have been done since then?
Please see if these documents help.
Note: 141685.1 - Unable to Close WIP Discrete Jobs
Note: 460061.1 - How To Check the Inventory Interface Manager's Status Programmatically
Note: 735186.1 - Outside Processing Transactions Occasionally Get Stuck In Pending Status.
Thanks,
Hussein

FI Open Interface vs FQEVENTS

Hi,
My understanding is that FQEVENTS transaction is only active for FICA (contract account). Please correct. Is this also available for FI-AP?
If FQEVENTS is not available for FI-AP, we then need to use BTE (Business Transaction Evetnts-FIBF). I have checked events 1025 and 1030, assigned custom function modules for these events and inserted break-points. But when I create posting (F-53 outgoing payment for vendor), the above events are not triggered and thus function modules are not triggered. Is there anything missing?
Also, the requirement is to read the cleared(paid) amount for given vendors and store to a Z table. Is there any user exit/BTE which gets triggered before SAVE of clearing document in FI-AP?
Thanks in advance.
Kamal

Chandrasekar,
as i know, the main thing you should consider is, that starting from R12 you will
be able to import invoices only through the Payables Open Interface.
basically, Invoice Import is used by OA to create invoice (from expense reports or from Oracle Projects). for standard invoice import, i've ever used Payables Open Interface.
Milan
<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by Chandrasekara Kayamboo ([email protected]):
I would like to know which is the best way to import invoice and what are the advantages and disadvange in each.
Regards
Chandrasekar<HR></BLOCKQUOTE>
null

Receiving Open Interface related doubt

Hi All,
We are currently on Oracle Release 12.0.4 and need some help/information regards Receiving Open Interface tables : rcv_headers_interface & rcv_transactions_interface tables.
We import the ASN which is being sent across from the Supplier via EDI directly into the Receiving Open Interface tables and then RTP program ( Receiving Transaction Processor ) program processes these into the base tables
to complete the receipt process..
Now for some reason or the other lets say because of EDI data issues or some other system issue with the RTP program , the Interface records end up in error status & the users have to manually complete the Receipt in Oracle Forms directly..
Now this Interface data over a period in time keeps accumulating while the corresponding PO Document would already have been Received manually in Oracle.
Because of this errored interface records the Interface tables keep growing in size in terms of data volume..
Now is there a way script or a program which validates these interface records and purges these automatically based on some validations on its own..
For Example : for a po if the records are stuck in the interface table but the po shipment has already been received in manually and in Closed Status, then it would automatically purge these records from interface tables.
Could someone please help us with this as soon as possible with any suggestions or workarounds..
Thanks

Currently there is no purge program available to purge the records in RTI. Further the oracle support wont be able to provide a delete script to delete the records in RTI (The reason being, the records are populated by the customer and customers are the best persons to validate the records and delete them on their own).
However, for ASN's
You may write a query based on the RTI.po_distribution_id and then check, whether the corresponding po shipment\distribution is already received \ closed for receiving and then you may delete.

PAYABLES OPEN INTERFACE INVOICE IMPORT 시 REQUIRED FIELD 정보

제품 : FIN_AP
작성날짜 : 2005-05-10
PAYABLES OPEN INTERFACE INVOICE IMPORT 시 REQUIRED FIELD 정보
==========================================================
PURPOSE
AP Open Interface Invoice Import 를 통해 Invoice 를 생성 코자 할 경우 반드시 필요한 Field 에 대한 정보이다.
Explanation
1. PO 나 Project 과 Match 하지 않는 Invoice Case
Table : AP_INVOICE_INTERFACE
==============================
Required Columns
================
-INVOICE_ID : AP_INVOICES_INTERFACE_S.NEXTVAL를 이용하여 생성됨
-INVOICE_NUM : 특정 Supplier 내에서는 unique 해야함
-VENDOR_ID/VENDOR_NUM/VENDOR_NAME : Active 하여야 하며 PO_VENDORS과 Mapping
-VENDOR_SITE_ID/VENDOR_SITE_CODE : Active 한 Site 여야 하며 PO_VENDOR_SITES table과 mapping
-INVOICE_AMOUNT : 'STANDARD' type인 경우에는 양수, 'CREDIT' type인 경우는 음수를 입력
-ORG_ID : AP_SYSTEM_PARAMETERS.ORG_ID
-SOURCE : select lookup_code from ap_lookup_codes where lookup_type='SOURCE' 중 하나
Table : AP_INVOICE_LINES_INTERFACE
==================================
Required Columns for LINE_TYPE_LOOKUP_CODE = 'ITEM'
===================================================
-INVOICE_ID : AP_INVOICES_INTERFACE.INVOICE_ID
-INVOICE_LINE_ID : AP_INVOICE_LINES_INTERFACE_S.NEXTVAL
-LINE_NUMBER : 해당 invoice 내에서 unique 해야함.
-LINE_TYPE_LOOKUP_CODE :'ITEM'
-AMOUNT
-ACCOUNTING_DATE: Optional. Defaulted from INVOICE_DATE or SYSDATE
- DIST_CODE_CONCATENATED / DIST_CODE_COMBINATION_ID
: select code_combination_id from gl_code_combinations
where account_type = 'E' and enabled_flag = 'Y'
and summary_flag = 'N'
and sysdate between nvl(start_date_active, sysdate-1)
and nvl(end_date_active, sysdate+1))
Required Columns for LINE_TYPE_LOOKUP_CODE = 'TAX'
===================================================
-INVOICE_ID : AP_INVOICES_INTERFACE.INVOICE_ID
-INVOICE_LINE_ID : AP_INVOICE_LINES_INTERFACE_S.NEXTVAL
-LINE_NUMBER : 해당 invoice 내에서 unique 해야함.
-LINE_TYPE_LOOKUP_CODE : 'TAX'
-TAX_CODE / TAX_CODE_ID : AP_TAX_CODES_ALL table에서 mapping
-AMOUNT
-ACCOUNTING_DATE : Optional. Defaulted from INVOICE_DATE or SYSDATE
-DIST_CODE_CONCATENATED or DIST_CODE_COMBINATION_ID
: select code_combination_id from gl_code_combinations
where account_type = 'E' and enabled_flag = 'Y'
and summary_flag = 'N'
and sysdate between nvl(start_date_active, sysdate-1)
and nvl(end_date_active, sysdate+1))
2. PO Matched Invoice 의 경우 Table: AP_INVOICE_INTERFACE
============================
Required Columns
================
-INVOICE_ID : AP_INVOICES_INTERFACE_S.NEXTVAL를 이용하여 생성됨
-INVOICE_NUM : 특정 Supplier 내에서는 unique 해야함
-PO_NUMBER : approved 된 PO 여야 하며 cancelled, closed 혹은 final closed 된 PO NUMBER 는 안됨. PO_HEADERS Table 과 mapping
-INVOICE_AMOUNT : 'STANDARD' type인 경우에는 양수, 'CREDIT' type인 경우는 음수를 입력
-SOURCE : select lookup_code from ap_lookup_codes where lookup_type='SOURCE'
-ORG_ID : AP_SYSTEM_PARAMETERS_ALL.ORG_ID
Table: AP_INVOICE_LINES_INTERFACE
=================================
Required Columns for PO Matched Lines
=====================================
-INVOICE_ID : AP_INVOICES_INTERFACE.INVOICE_ID
-INVOICE_LINE_ID : AP_INVOICE_LINES_INTERFACE_S.NEXTVAL
-LINE_NUMBER : 해당 invoice 내에서 unique 해야함.
-LINE_TYPE_LOOKUP_CODE : 'ITEM'
-AMOUNT : QUANTITY_INVOICED * UNIT_PRICE
If MATCH_OPTION is 'P', then populate:
-RELEASE_NUM or PO_RELEASE_ID : Blanket Release only, validated against PO_RELEASES_ALL
-PO_NUMBER or PO_HEADER_ID : Validated against PO_HEADER_ALL
-PO_LINE_NUMBER or PO_LINE_ID : Validated against PO_LINES_ALL
-PO_SHIPMENT_NUM or PO_LINE_LOCATION_ID : Validated against PO_LINE_LOCATIONS_ALL
If MATCH_OPTION is 'R', then populate:
-RECEIPT_NUMBER : RCV_SHIPMENT_HEADERS.RECEIPT_NUM
-RCV_TRANSACTION_ID or PO_LINE_LOCATION_ID : RCV_TRANSACTIONS과 Mapping
Example
Reference Documents
Note 205331.1

Chandrasekar,
as i know, the main thing you should consider is, that starting from R12 you will
be able to import invoices only through the Payables Open Interface.
basically, Invoice Import is used by OA to create invoice (from expense reports or from Oracle Projects). for standard invoice import, i've ever used Payables Open Interface.
Milan
<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by Chandrasekara Kayamboo ([email protected]):
I would like to know which is the best way to import invoice and what are the advantages and disadvange in each.
Regards
Chandrasekar<HR></BLOCKQUOTE>
null

Payables Open Interface Pgm fails without any error(Very urgent)

All,
I'm into an integration project where in I'm pushing Invoice doc from a third party appln to Oracle apps (11.5.10.2) thru payables open interface. The integration is smooth till today. We pushed a record today, but the concurrent neither picks up the data but failed with 'completed error' status. When I delete the same record from the interface, the concurrent runs fine. So we are sure there is some issue with the data in my record. Since concurrent is failed without any reason, from where I can get the log to know what is the actual problem with that record? Pls help me with your inputs.
Thanks,
Sen

Sen,
To enable trace, please refer to this document (skip the part about generating TKPROF, just check the concurrent request output file if more details about the error are logged after enabling trace and setting the profile option).
Note: 453527.1 - How To Trace a Concurrent Request And Generate TKPROF File
https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=453527.1
The database log file can be usually found under $ORACLE_HOME/admin/<SID>_<hostname>/bdump directory (or from SQL*Plus, issue "show parameter background_dump_dest").
Regards,
Hussein

Open Interface or Public/Private API for Blanket Release

Hi All,
I am on Oracle Apps 11.5.10.2
Is there any open interface available to import the blanket releases in Oracle system. I have searched the meta link and found the doc 160781.1. According to the document there has been a future enhancement request logged by Oracle for this functionality but I am interest if any one know about some private API available to do same job. I will also appreciate if someone can share his project experience in migrating the blanket release to the Oracle.
Thanks
Vishalaksha

I do not think it is available in 11i -- Please see (HOW TO IMPORT BLANKET SALES AGREEMENT AND BLANKET RELEASE. (Doc ID 336086.1)) for details.
You may log a SR and confirm this with Oracle support.
Thanks,
Hussein

Open Interface for Approved Supplier Lists and Sourcing Rules

Hi All,
Is there an open interface or an API available for Appeoved Supplier Lists and Sourcing Rules.
Thanks and Regards,
MPH

Hi sandeep,
I prefer to use the API mentioned.
However this is in Oracle Manufactirung and we dont use that module instead I want to define them in Oracle Purchasing.
can I still do it in Purchasing using the same API.
Further as per the document there are 3 entities
01) Sourcing Rule/Bill of Distribution
02) Receiving Organization
03) Shipping Organization
Do I need to define all 3 in order to make it work?
Thanks and Regards,
MPH

Open interface error ...Preventing us from closing May-11

Hi All
we are running ERP 12.0.6 on solaris machines. IT was not allowing us to close MAY-11. Reason was there were some 22 error records in TRANSACTION OPEN INTERFACE.
I cloned the PRODUCTION INSTANCE to TES to reproduce the problem and deleted all records from backend table (mtl_transactions_interface ) in test. Now its all fine in TEST and we can successfully close the month.
1) Is it the right way of doing it.
2) If not please suggest how wud i do the same in proper way.
Regards
Musaddaq

Can you get the following for the errored transaction?
SELECT   transaction_id txnid, transfer_transaction_id txfrtxnid
       , organization_id orgid, transfer_organization_id txfrorgid, subinventory_code subinv
       , transfer_subinventory txfrsubinv, cost_group_id cgid
       , transfer_cost_group_id txfrcgid       , prior_costed_quantity
       , transfer_prior_costed_quantity       , rcv_transaction_id rcvtxnid
       , transaction_action_id txnactid       , transaction_source_type_id txnsrctypid
       , transaction_type_id txntypid       , costed_flag cstdflg
       , transaction_group_id       , inventory_item_id invitmid
       , transaction_source_id wip_entity_id       , transaction_cost txncst
       , shipment_number shipnum       , new_cost       , prior_cost
       , actual_cost       , project_id       , transaction_uom txnuom
       , transaction_quantity txnqty       , primary_quantity priqty       , prior_costed_quantity priorqty
       , currency_code altcurr       , currency_conversion_rate currconvrt       , currency_conversion_date currconvdt
       , TO_CHAR (mmt.creation_date, 'dd-mm-yyyy hh24:mi:ss') creation_date
       , TO_CHAR (mmt.last_update_date, 'dd-mm-yyyy hh24:mi:ss')last_upd_date
       , ERROR_CODE errcode
       , error_explanation errexpl
    FROM mtl_material_transactions mmt
   WHERE transaction_id IN (&Trx_Id)   -- Error transaction_id
ORDER BY transaction_id DESC

RECEIVING OPEN INTERFACE TABLE의 STRUCK RECORDS 정보 취합 SCRIPT

제품 : MFG_PO
작성날짜 : 2005-01-27
RECEIVING OPEN INTERFACE TABLE의 STRUCK RECORDS 정보 취합 SCRIPT
=================================================================
PURPOSE
RCV_TRANSACTIONS_INTERFACE table에 있는 struck receipt records의 정보를
취합하여, struck 원인 및 해결에 도움을 줄 수 있다.
(Oracle Purchasing - Version: 11.5.2 to 11.5.9)
Explanation
Receiving Open Interface Tables에 걸려 있는 receipt struck의 source
document의 추가 정보를 어떻게 취합할 수 있을것인가?
(RCV_TRANSACTIONS_INTERFACE)
Source document는 아래 중 하나가 될 수 있다.
* Purchase Order
* Return Material Authorization (RMA)
* Internal Requisition
아래에 소개하는 scripts는 interface tables에 많은 수의 records가 있을때,
많은 수의 records의 정보를 한 번에 취합하길 원할때 사용하면 유용하다.
만약 interface tables에 단지 몇 개의 records만 있다면 Note: 171257.1
- Oracle Procurement (Purchasing)/iProcurement Diagnostic Tests 에 소개
되어져 있는 적당한 diagnostic script를 이용하는편이 낫다.
Example
1.Error가 발생한 Purchase Order receipts의 추가 정보를 취합하는 script:
SELECT SUBSTR(POH.SEGMENT1,1,10) "PO Number",
POR.RELEASE_NUM "Release Num",
POL.LINE_NUM "Line Num",
RTI.INTERFACE_TRANSACTION_ID "Intf Trx Id",
RTI.TRANSACTION_DATE "Trx Date",
RTI.PROCESSING_MODE_CODE "Proc Mode",
RTI.TRANSACTION_STATUS_CODE "Trx Status",
RTI.PROCESSING_STATUS_CODE "Proc Status",
SUBSTR(PIE.ERROR_MESSAGE,1,75) "Error Message",
POH.ORG_ID "Op Unit Id",
RTI.PO_HEADER_ID "PO Hdr Id",
RTI.PO_RELEASE_ID "Rel Id",
RTI.PO_LINE_ID "PO Line Id",
RTI.PO_LINE_LOCATION_ID "Line Loc Id",
RTI.QUANTITY "Intf Qty",
POLL.QUANTITY "Order Qty",
POLL.QUANTITY_RECEIVED "Qty recvd",
POD.QUANTITY_DELIVERED "Qty Delv",
NVL(POLL.CLOSED_CODE,'OPEN') "Closed Code",
OOD.ORGANIZATION_CODE "To Inv Org",
RTI.DESTINATION_TYPE_CODE "Dest Type",
RTI.TRANSACTION_TYPE "Intf Trx Type",
NVL(POLL.QTY_RCV_EXCEPTION_CODE,'NONE') "Qty Exception",
POLL.QTY_RCV_TOLERANCE "Qty Tolerance",
POLL.RECEIVE_CLOSE_TOLERANCE "Receipt Tolerance"
FROM RCV_TRANSACTIONS_INTERFACE RTI,
PO_HEADERS_ALL POH,
PO_RELEASES_ALL POR,
PO_LINES_ALL POL,
PO_LINE_LOCATIONS_ALL POLL,
ORG_ORGANIZATION_DEFINITIONS OOD,
PO_DISTRIBUTIONS_ALL POD,
PO_INTERFACE_ERRORS PIE
WHERE POH.PO_HEADER_ID = RTI.PO_HEADER_ID
AND POR.PO_RELEASE_ID(+) = RTI.PO_RELEASE_ID
AND POL.PO_LINE_ID = RTI.PO_LINE_ID
AND OOD.ORGANIZATION_ID(+) = RTI.TO_ORGANIZATION_ID
AND POLL.LINE_LOCATION_ID = RTI.PO_LINE_LOCATION_ID
AND POD.LINE_LOCATION_ID = POLL.LINE_LOCATION_ID
AND RTI.INTERFACE_TRANSACTION_ID = PIE.INTERFACE_TRANSACTION_ID(+);
2.Error가 발생한 RMA receipts의 추가 정보를 취합하는 script:
SELECT RTI.INTERFACE_TRANSACTION_ID "Interface Transaction ID",
RTI.PROCESSING_STATUS_CODE "Processing Status",
RTI.PROCESSING_MODE_CODE "Processing Mode",
RTI.TRANSACTION_STATUS_CODE "Transaction Status",
RTI.TRANSACTION_TYPE "Transaction Type",
RTI.TRANSACTION_DATE "Transaction Date",
RTI.OE_ORDER_HEADER_ID "Order header Id",
OOH.ORDER_NUMBER "Order Number",
OOH.ORG_ID "Oper Unit Id",
RTI.OE_ORDER_LINE_ID "Order Line Id",
OOL.INVENTORY_ITEM_ID "Order Item",
OOL.FLOW_STATUS_CODE "Line Flow Status Code",
RTI.QUANTITY "Intf Qty",
RTI.UNIT_OF_MEASURE "Intf UOM",
OOL.ORDERED_QUANTITY "Qty Ordered",
OOL.SHIPPED_QUANTITY "Qty Shipped",
OOL.FULFILLED_QUANTITY "Qty Fulfilled",
OOL.OPEN_FLAG "Open Flag",
OOL.CANCELLED_FLAG "Cancelled",
WH.ORGANIZATION_CODE||' - '||WH.ORGANIZATION_NAME
"Ship To Organization",
WH1.ORGANIZATION_CODE||' - '||WH1.ORGANIZATION_NAME
"Ship From Organization",
OOL.BOOKED_FLAG "Booked",
SUBSTR(PIE.ERROR_MESSAGE,1,75) "Error Message"
FROM RCV_TRANSACTIONS_INTERFACE RTI,
OE_ORDER_LINES_ALL OOL,
OE_ORDER_HEADERS_ALL OOH,
ORG_ORGANIZATION_DEFINITIONS WH,
ORG_ORGANIZATION_DEFINITIONS WH1,
PO_INTERFACE_ERRORS PIE
WHERE OOL.HEADER_ID = RTI.OE_ORDER_HEADER_ID
AND OOL.LINE_CATEGORY_CODE = 'RETURN'
AND OOL.LINE_ID = RTI.OE_ORDER_LINE_ID
AND OOH.HEADER_ID = RTI.OE_ORDER_HEADER_ID
AND OOL.SHIP_TO_ORG_ID = WH.ORGANIZATION_ID(+)
AND OOL.SHIP_FROM_ORG_ID = WH1.ORGANIZATION_ID(+)
AND RTI.INTERFACE_TRANSACTION_ID = PIE.INTERFACE_TRANSACTION_ID(+)
ORDER BY RTI.INTERFACE_TRANSACTION_ID;
3.Error가 발생한 Internal Requisition receipts의 추가 정보를 취합하는
script:
SELECT RTI.RECEIPT_SOURCE_CODE "Receipt Source Code",
RTI.REQUISITION_LINE_ID "Intf Req Line Id",
RTI.SHIPMENT_HEADER_ID "Ship Hdr Id",
RTI.SHIPMENT_LINE_ID "Ship Line Id",
RTI.ITEM_ID "Item Id",
RTI.QUANTITY "Intf Qty",
RTI.UNIT_OF_MEASURE "UOM",
RTI.FROM_ORGANIZATION_ID "From Org Id",
RTI.TO_ORGANIZATION_ID "To Org id",
PRH.REQUISITION_HEADER_ID "Req Hdr Id",
PRH.SEGMENT1 "Req Num",
PRL.REQUISITION_LINE_ID "Req Line Id",
NVL(PRL.QUANTITY_DELIVERED,0) "Qty Delv",
NVL(PRL.QUANTITY_CANCELLED,0) "Qty Canc",
PRL.QUANTITY "Qty Ordered",
PRL.QUANTITY - (nvl(PRL.QUANTITY_CANCELLED,0) +
NVL(PRL.QUANTITY_DELIVERED,0))"Qty Remaining",
PRL.SOURCE_TYPE_CODE "Source Type",
PRH.TRANSFERRED_TO_OE_FLAG "XFR to OE Flag",
NVL(PRL.CANCEL_FLAG,'N') "Cancelled",
NVL(PRL.CLOSED_CODE,'OPEN') "Closed Code",
LIN.LINE_ID "ISO Line Id",
NVL(LIN.ORDERED_QUANTITY,0) "ISO Line Qty",
NVL(LIN.SHIPPED_QUANTITY,0) "ISO Ship Qty",
NVL(FULFILLED_QUANTITY,0) "ISO Fulfilled Qty",
NVL(LIN.CANCELLED_QUANTITY,0) "ISO Cancelled Qty",
NVL(LIN.OPEN_FLAG,'N') "ISO Line Open",
NVL(LIN.BOOKED_FLAG,'N') "ISO Line Booked",
NVL(LIN.CANCELLED_FLAG,'N') "ISO Line Cancelled",
OOH.ORDER_NUMBER "ISO Order Number",
PIE.COLUMN_NAME "Intf Column",
SUBSTR(PIE.ERROR_MESSAGE,1,75) "Error Message"
FROM RCV_TRANSACTIONS_INTERFACE RTI,
PO_REQUISITION_HEADERS_ALL PRH,
PO_REQUISITION_LINES_ALL PRL,
PO_INTERFACE_ERRORS PIE,
OE_ORDER_LINES_ALL LIN,
OE_ORDER_HEADERS_ALL OOH
WHERE PRL.REQUISITION_HEADER_ID = PRH.REQUISITION_HEADER_ID
AND RTI.REQUISITION_LINE_ID = PRL.REQUISITION_LINE_ID
AND LIN.SOURCE_DOCUMENT_ID = PRH.REQUISITION_HEADER_ID
AND LIN.SOURCE_DOCUMENT_LINE_ID = PRL.REQUISITION_LINE_ID
AND LIN.SOURCE_DOCUMENT_TYPE_ID = 10 --Internal Requisition
AND OOH.HEADER_ID = LIN.HEADER_ID
AND PIE.INTERFACE_TRANSACTION_ID(+) = RTI.INTERFACE_TRANSACTION_ID
ORDER by PRH.SEGMENT1;
Reference Documents
Note 263368.1

Any suggestion/advise please!
Thanks,
Genoo

Open interface document - MTL_TRANSACTIONS_INTERFACE

Similar Messages

Maybe you are looking for