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?

Similar Messages

Check duplicate asset number during MIGO

Hi MM/Abap Gurus ,
What user exit can be used to check duplicate asset number during GR. E.g: I have a PO with same asset number for item line 1 and 2. What user exit can be used to set warning msg if duplicate asset number exits during MIGO. Please advise if there any user exit can be used for my requirement?
Thanks
Mitra

Hi Puspha,
Actually, the scenarios as below:
1. PO created with 1 line item with Acc Assign Cat = A and multiple account assignment. Therefore, under the account assignment tab there are duplicate asset number inputted.
2. Hence, when do GR, the system should prompt warning message " Duplicate asset number exists".
Above are the requirement. I need any user exit that I can use in MIGO, where there is checking on duplicate asset number or during the sving of MIGO, I could inforce a logic on the checking.
Your help appreciated.
Thanks

Need API for EAM Active Association - Asset number and Asset Group

Hi
I am working in R12 and need api for EAM Active Association - Asset number and Asset Group to insert the new records.
If any one is aware please let me know API with sample script.
Regards
Suresh P

All APIs are listed in Oracle Integration Repository
http://irep.oracle.com/index.html
API User Notes - HTML Format [ID 236937.1]
R12.0.[3-4] : Oracle Install Base Api / Open Interface Setup Test [ID 427566.1]
Oracle Trading Community Architecture API User Notes, June 2003 [ID 241320.1]
Technical Uses of Customer Interface and TCA-API [ID 269121.1]
Pelase also check below:
Api's in EBS
Re: Api's in EBS
http://sairamgoudmalla.blogspot.com/2009/05/script-to-find-oracle-apis-for-any.html
API
Fixed Asset API
List of API
Re: List of APIs
Oracle Common Application Components API Reference Guide
download.oracle.com/docs/cd/B25284_01/current/acrobat/jta115api.pdf
List of APIs and open interface R12
Re: List of APIs and open interface R12
Regard
Helios

Payable Open Interface Import---Asset Book name is being generated

Hi,
I am working on Payables Open Interface Import in R12.
I am not generating the 'Track as Asset Flag' and 'Asset Book Type Code' fields in Ap_invoice_lines_nterface table.
And the distribution account is also an Expense account.
But after the payables open interface import is completed, the asset book name is being populated in ap_invoice_lines_all table.
and as a result, recoverable and non recoverable tax lines are being created in the ap_invoice_distributions_all table making the invoice total and line total unequal.
Did any body faced a similar issue?
Please help....
this is really very urgent.
Any queries, please ask me [email protected]
Thanks in advance,
Sharmila

Hi,
I have raised a SR with Oracle and got following suggestion:
=== ODM Solution /Action Plan ===
To implement the solution, please execute the following steps:
1. Download and review the readme and pre-requisites for Patch.9577089:R12.AP.B.
2. Ensure that you have taken a backup of your system before applying
the recommended patch.
3. Apply the patch in a test environment.
4. Confirm the following file versions:
120.67.12010000.27 of apiimutb.pls
You can use the commands like the following:
strings -a $XX_TOP/filename |grep '$Header'
5. Retest the issue.
6. Migrate the solution as appropriate to other environments.
Will keep you all posted.
Regards,
Sharmila

CM Open Interface - reference back to original bank statement line

we are using Open Interface for our bank reconciliation. we found that, the API APPS.CE_999_PKG.clear always send us the Open Interface Transaction amount as the cleared amount, and we have no visibility to the amount in the bank statement line.
eg:
bank statement line is $100
if a user manually reconcile this line with an open interface transaction line with amount $200, the status will changed to reconciled and the cleared amount is $200.
the cleared amount passed through the API to our customize program also $200.
how can we get the amount $100?
we are doing some GL posting for the cleared amount. getting $200 will caused us to do over post, as the amount we received only $100 (bank statement line amount)

Hi All,
I found this article, which explains about the bank statement mappings.
*Mapping BAI2, SWIFT Bank Statement Format Masking: BANK_ACCOUNT_NUM, BANK_TRX_NUMBER, BANK_ACCOUNT_TEXT, Agent Bank account number And Others [ID 752532.1]*
Based on this I defined a new bank statment mapping by coping the existing BAI2 mapping.
The only change I had to do was to change the position of the BANK_TRX_NUMBER to -2 and my problem got resolved.
Below is the question and answer as per the document.
Q2: Why following BAI2 datafile needs bank statement mapping as:
BANK_TRX_NUMBER 16 -2 and not -1?
16,581,156500,Z,813009392186700,000000002004/
A2:
The bank statement mapping you give to populate depends on where the BANK_TRX_NUMBER is in the data file: Example:
Rec 16 structure is as follows:
16,<transaction code>,<amount>,<funds type>,<bank ref #>,<customer ref #>,<text>/
In the rec:16,581,156500,Z,813009392186700,000000002004/
while the NUMBER appears to be -1 position however the text is assumed missing here and hence the
BANK_TRX_NUMBER 16 -2 will work.
Thanks and Regards,
MPH

Document number and reference doc number

Hi All,
When i post a invoice through F-22 i get a document number.
1: Is this doc. number also called invoice number
2: What is reference document number (XBLNR field). From where does it get its value
What's the use of this reference doc. number and how different it is from doc. number
Thanks in advance,
Prashanth

hey,
1. It is the invoice no.
2. The reference document number is used as a search criterion when displaying or changing documents. In correspondence, the reference document number is sometimes printed in place of the document number.
Ex; Vendor send the invoice and it has a no. on it. You can use that no as document no and/or reference no when posting in the system. So when you do a search it is easy to pull the invoice based in this no.
Hope this helps.
Assign points if helpful

Limits on number of invoices put through AP Open Interface Tables

Hi,
a quick question.
We have multiple AP systems which we are thinking of interfacing directly with eBusiness Suite. With a potential of approximately 20,000 invoices per night/batch (each invoice will have on average two distribution lines). All invoices are going into a single organisation.
Does anyone have experience of this number of invoices (or greater) going through the AP Open Interface tables?
Steve
nb

This should certainly be possible - we process about 15000 invoices every night in under 2 hours.
HTH
Srini

Oracle Open interface- Error in Item Import (INCOIN)

Hi,
I am migrating items to oracle using oracle open interface.
I am getting the follwing errors.
1. The TEMPLATE_ID or TEMPLATE_NAME specified is not valid for this Organization
2. The revision entered is for an item that does not exist in MTL_SYSTEM_ITEMS nor MTL_SYSTEM_ITEMS_INTERFACE (No Revision Is Used)
3. Expense Account is required when Inventory Asset Value is "No" and Inventory Item is "Yes"
4. Item number is invalid.
EBS: 11.5.10
The Migratin was working fine in the previous instance. Pls let me know if you have any information on this.
Thanks
AM

Hi,
Please see these docs.
INCOIN: Error Message Template_ID or Template Name Specified is not a Valid Template When Item Catalog ID is NULL during Item Import in UPDATE Mode [ID 1076193.1]
Item Import: What Does "Sync" Items Do? [ID 417887.1]
INCOIN Gets INV_TEMPLATE_ERROR After Patch Applied [ID 141579.1]
Item Open Interface (INCOIN/IOI) Setup and How-To [ID 115557.1]
Understanding Item Import and Debugging Problems with Item Import [ID 268968.1]
Thanks,
Hussein

CE Bank Statement Open Interface

Hi,
I have successfully run the Bank Statement Loader for Open Interface.
Then I run the 2nd step > Bank Statement Import:
The docs said:
2. Bank Statement Import
The required parameters to this job are the following:
Bank Branch Name - Provide the bank branch name that you setup in the Bank
Account Setup section.
GL Date - Although this parameter is not marked as required, the import will
often fail if you do not provide a value for this parameter. The date must in
an open period in both AP and AR.
Note: If you have multiple files loaded, but only want to import one of them,
use the Statement Date or Statement Number range parameters to limit the import
job.
If successful, this program moves records from the
CE_STATEMENT_HEADERS_INTERFACE and CE_STATEMENT_LINES_INTERFACE tables into
the CE_STATEMENT_HEADERS and CE_STATEMENT_LINES tables.May run request was successful, and I got this logs
Output log
                                                               Execution Report                       Report Date   26-MAR-09 20:28
                                                                                                             Page     1 of      1
Statement Number        -
Statement Date          -
Bank Branch Name       Rufino                                       Bank Name            Asia United Bank
Bank Account Number     -                                           Bank Account Currency    -
Bank Account Name       -
                          ******* Program Ran Successfully, No Error Found. ********View Log
+---------------------------------------------------------------------------+
Cash Management: Version : 12.0.0
Copyright (c) 1979, 1999, Oracle Corporation. All rights reserved.
CEIMPERR module: Bank Statement Import Execution Report
+---------------------------------------------------------------------------+
Current system time is 26-MAR-2009 20:28:57
+---------------------------------------------------------------------------+
+-----------------------------
| Starting concurrent program execution...
+-----------------------------
Arguments
P_BANK_BRANCH_ID='3104'
P_SQL_TRACE='N'
P_DISPLAY_DEBUG='N'
Current NLS_LANG and NLS_NUMERIC_CHARACTERS Environment Variables are :
American_America.US7ASCII
Enter Password:
Report Builder: Release 10.1.2.2.0 - Production on Thu Mar 26 20:28:58 2009
Copyright (c) 1982, 2005, Oracle. All rights reserved.
+---------------------------------------------------------------------------+
Start of log messages from FND_FILE
+---------------------------------------------------------------------------+
+---------------------------------------------------------------------------+
End of log messages from FND_FILE
+---------------------------------------------------------------------------+
+---------------------------------------------------------------------------+
Executing request completion options...
+------------- 1) PRINT   -------------+
Printing output file.
               Request ID : 328310
         Number of copies : 0
                  Printer : noprint
+--------------------------------------+
Finished executing request completion options.
+---------------------------------------------------------------------------+
Concurrent request completed successfully
Current system time is 26-MAR-2009 20:29:00
+---------------------------------------------------------------------------+Why is that my
CE_STATEMENT_HEADERS
and
CE_STATEMENT_LINES
have no rows?
Thanks a lot

The error tables has no contents either :(
The trace files does not help much , I want to know the program part that inserts into the target tables, but its just showing other reports process :((
trace file
PARSING IN CURSOR #2 len=11462 dep=0 uid=173 oct=3 lid=173 tim=1209109154828460 hv=1080153458 ad='436471d8'
SELECT /* Created Miscellaneous Receipt */
        l1.meaning                              error_type,
        'D'                             break_group,
        sh.statement_number                     statement_no,
        sh.doc_sequence_value                                   doc_sequence_value,
        sl.line_number                  line_no,
        sh.statement_date                       statement_date,
        sl.trx_date                             trx_date,
        ba.bank_account_num                     bank_acc,
        ba.bank_account_name            bank_account_name,
        ba.currency_code                        acc_currency,
        NULL                            message_name,
        nvl(sl.amount,0)                        amount,
        acr.currency_code                       C_CURRENCY_CODE,
        l2.meaning                              trx_type,
        acr.receipt_number                      trx_no,
        'CE'                            application_short_name,
        bb.branch_party_id                      bank_branch_id
FROM        ce_lookups                  l1,
        ce_lookups                      l2,
        ce_bank_accts_gt_v                      ba,
        ce_bank_branches_v                      bb,
                   ce_statement_headers         sh,
                   ce_statement_lines                   sl,
        ar_cash_receipts_all    acr,
                   ce_222_reconciled_v cr
WHERE l1.lookup_type = 'ABR_REPORT_EXCEPTIONS' AND l1.lookup_code = 'MISC_RECEIPT_CREATED' AND l2.lookup_type = 'BANK_TRX_TYPE' AND l2.lookup_code = sl.trx_type AND bb.branch_party_id = ba.bank_branch_id AND bb.branch_party_id = : P_BANK_BRANCH_ID AND ba.bank_account_id = sh.bank_account_id AND sh.statement_header_id = sl.statement_header_id AND ba.bank_account_id = DECODE ( : P_BANK_ACCOUNT_ID , NULL , ba.bank_account_id , : P_BANK_ACCOUNT_ID ) AND to_char ( sh.statement_date , 'YYYY/MM/DD' ) >= nvl ( to_char ( : P_STAT_DATE_FROM , 'YYYY/MM/DD' ) , to_char ( sh.statement_date , 'YYYY/MM/DD' ) ) AND to_char ( sh.statement_date , 'YYYY/MM/DD' ) <= nvl ( to_char ( : P_STAT_DATE_TO , 'YYYY/MM/DD' ) , to_char ( sh.statement_date , 'YYYY/MM/DD' ) ) AND sh.statement_number >= nvl ( : P_STAT_NUMBER_FROM , sh.statement_number ) AND sh.statement_number <= nvl ( : P_STAT_NUMBER_TO , sh.statement_number ) and acr.cash_receipt_id = cr.cash_receipt_id and cr.statement_line_id = sl.statement_line_id and acr.comments = 'Created by Auto Bank Rec' UNION ALL SELECT    /* Reconciliation errors */
        l1.description                  error_type,
        'C'                             break_group,
        sh.statement_number                     statement_no,
        sh.doc_sequence_value                                   doc_sequence_value,
        sl.line_number                  line_no,
        sh.statement_date                       statement_date,
        sl.trx_date                             trx_date,
        ba.bank_account_num                             ba.bank_account_name            bank_account_name,
        ba.currency_code                        acc_currency,
        e.message_name                          message_name,
        to_number(NULL)                 amount,
        ba.currency_code                        C_CURRENCY_CODE,
        NULL                            trx_type,
        NULL                            trx_no,
        NVL(e.application_short_name,'CE')      application_short_name,
        bb.branch_party_id                      bank_branch_id
FROM        ce_lookups                          l1,
        ce_bank_accts_gt_v                      ba,
        ce_bank_branches_v                      bb,
                   ce_statement_headers         sh,
        ce_reconciliation_errors                e
WHERE l1.lookup_type = 'ABR_REPORT_EXCEPTIONS' AND l1.lookup_code = 'RECONCILIATION' AND bb.branch_party_id = ba.bank_branch_id AND bb.branch_party_id = : P_BANK_BRANCH_ID AND ba.bank_account_id = sh.bank_account_id AND ba.account_classification = 'INTERNAL' AND sh.statement_header_id = e.statement_header_id AND e.statement_line_id is null AND ba.bank_account_id = DECODE ( : P_BANK_ACCOUNT_ID , NULL , ba.bank_account_id , : P_BANK_ACCOUNT_ID ) AND to_char ( sh.statement_date , 'YYYY/MM/DD' ) >= nvl ( to_char ( : P_STAT_DATE_FROM , 'YYYY/MM/DD' ) , to_char ( sh.statement_date , 'YYYY/MM/DD' ) ) AND to_char ( sh.statement_date , 'YYYY/MM/DD' ) <= nvl ( to_char ( : P_STAT_DATE_TO , 'YYYY/MM/DD' ) , to_char ( sh.statement_date , 'YYYY/MM/DD' ) ) AND sh.statement_number >= nvl ( : P_STAT_NUMBER_FROM , sh.statement_number ) AND sh.statement_number <= nvl ( : P_STAT_NUMBER_TO , sh.statement_number ) UNION ALL ( SELECT     /* Header interface errors */
        l.description                   error_type,
        'A'                             break_group,
        e.statement_number                      statement_no,
                  to_number(NULL)                       doc_sequence_value,
        1                               line_no,
        sh.statement_date                       statement_date,
        sh.statement_date                       trx_date,
        e.bank_account_num                      bank_acc,
        ba.bank_account_name            bank_account_name,
        ba.currency_code                        acc_currency,
        e.message_name                  message_name,
        0                               amount,
        ' '                             C_CURRENCY_CODE,
        ' '                             trx_type,
        ' '                             trx_no,
        NVL(e.application_short_name,'CE')      application_short_name,
        bb.branch_party_id                      bank_branch_id
FROM         ce_lookups                 l,
                   ce_statement_headers_int     sh,
                   ce_header_interface_errors   e,
        ce_bank_branches_v              bb,
        ce_bank_accts_gt_v              ba
bank_acc,   WHERE l.lookup_type = 'ABR_REPORT_EXCEPTIONS' AND l.lookup_code = 'STATEMENT' AND sh.bank_account_num = e.bank_account_num AND sh.statement_number = e.statement_number AND sh.bank_branch_name = bb.bank_branch_name AND e.bank_account_num = NVL ( ba.bank_account_num , e.bank_account_num ) AND ba.bank_branch_id = bb.branch_party_id AND bb.bank_branch_name = DECODE ( : C_BANK_BRANCH_NAME_DSP , : C_ALL_TRANSLATION , bb.bank_branch_name , : C_BANK_BRANCH_NAME_DSP ) AND ba.bank_account_id = NVL ( : P_BANK_ACCOUNT_ID , ba.bank_account_id ) AND ba.account_classification = 'INTERNAL' AND to_char ( sh.statement_date , 'YYYY/MM/DD' ) >= nvl ( to_char ( : P_STAT_DATE_FROM , 'YYYY/MM/DD' ) , to_char ( sh.statement_date , 'YYYY/MM/DD' ) ) AND to_char ( sh.statement_date , 'YYYY/MM/DD' ) <= nvl ( to_char ( : P_STAT_DATE_TO , 'YYYY/MM/DD' ) , to_char ( sh.statement_date , 'YYYY/MM/DD' ) ) AND sh.statement_number >= nvl ( : P_STAT_NUMBER_FROM , sh.statement_number ) AND sh.statement_number <= nvl ( : P_STAT_NUMBER_TO , sh.statement_number )thanks

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)

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

Customer Item Open Interface Validation

Hi Folks,
I have to write package for customer item open interface ,
can anyone let me know what are the validation required or if any one have package written ,please share it with me .[email protected]
Waiting for your kind response.
Thanks in advance....
Regards
RP

Hi
Please find the code below for Customer Item Interface
HTH
Dinesh
declare
     ex_not_ok     exception          ;
     Cursor      cur_cust_item is
     select     b.*,rowid from btl_cust_item b      ;
     rec_cur_cust_item     cur_cust_item%rowtype;
     vc_rowid          varchar2(50);
     vc_error_desc          varchar2(2000);
     vc_org_code          varchar2(20)     :='F02';
     vc_org_id          varchar2(20)     ;
     vc_inv_item          number          ;
     vc_cust_id          varchar2(50)     ;
     vc_create_by          number;
     vc_last_updated_by     number;
     vc_user_name          varchar2(100);
     vc_login_name          varchar2(30)     := '&1';
     vc_master               number;
begin
     vc_org_id := &2 ;
vc_master := &3;
     begin
          select      user_id          ,last_updated_by      ,user_name
          into     vc_create_by     ,vc_last_updated_by     , vc_user_name
          from      fnd_user
          where      user_name = vc_login_name;
     end;
     open     cur_cust_item;          -- open cursor
     loop
          begin
          fetch     cur_cust_item
          INTO     rec_cur_cust_item;
          vc_rowid     := rec_cur_cust_item.rowid;
          exit when cur_cust_item%NOTFOUND;
          -- perform the mandatory validations
          -- 1. Check the validity of the customer
          begin
               select      count(*)
               into     vc_cust_id
               from      ra_customers
               where     upper(customer_number) = upper(rec_cur_cust_item.customer_number);
               if      vc_cust_id > 0 then
                    null;
               else
                    vc_error_desc := rec_cur_cust_item.customer_number||' '|| rec_cur_cust_item.customer_name ||' - Customer Number Does not Exist in Ra_customers';
                    raise     ex_not_ok;
               end if;
               exception
                    when no_data_found then
                    update      btl_cust_item
                    set     process_flag = 'E',
                         error_message = 'XREF- Customer Does not exist '||vc_error_desc
                    where     rowid     = vc_rowid;
          end ;
          -- 2. Check that the Customer Item Is not Null
          begin
               if     rec_cur_cust_item.customer_item_number is not null then
                    null;
               else
                    vc_error_desc := rec_cur_cust_item.Customer_Number ||' - '|| rec_cur_cust_item.customer_item_number || ' - Customer Item has no value    ';
                    raise ex_not_ok;
               end if;
          end;
          -- 3. Validate the Inventory Item
          begin
               select      count(*)
               into     vc_inv_item
               from      mtl_system_items a, org_organization_definitions b
               where     a.organization_id            = b.organization_id
               and     rec_cur_cust_item.inventory_item = segment1
               and     a.organization_id             = vc_org_id;
               if     vc_inv_item != 0 then
                    null;
               else
                    vc_error_desc := 'Inventory Item '|| rec_cur_cust_item.inventory_item ||' is not valid/exist in mtl_system_item ';
                    raise ex_not_ok;
               end if;
          end;
    rec_cur_cust_item.commodity_code := 'MISC';
          insert into mtl_ci_interface (
                    PROCESS_FLAG          ,
                    PROCESS_MODE          ,
                    TRANSACTION_TYPE     ,
                    CUSTOMER_NUMBER          ,
                    CUSTOMER_NAME          ,
                    CUSTOMER_ITEM_NUMBER     ,
                    ITEM_DEFINITION_LEVEL     ,
                    COMMODITY_CODE          ,
                    INACTIVE_FLAG          ,
                    LOCK_FLAG          ,
                    LAST_UPDATE_DATE     ,
                    LAST_UPDATED_BY          ,
                    CREATION_DATE          ,
                    CREATED_BY          ,
                    --LAST_UPDATE_LOGIN     ,
                    ERROR_CODE          ,
                    ERROR_EXPLANATION
          values
                    '1'                                ,     --PROCESS_FLAG
                    '1'                                ,     --PROCESS_MODE
                    'CREATE'                     , -- TRNASACTION_TYPE
                    rec_cur_cust_item.customer_number     ,     --CUSTOMER_NUMBER
                    rec_cur_cust_item.customer_name           , --CUSTOMER_NAME
                    rec_cur_cust_item.customer_item_number, --CUSTOMER_ITEM_NUMBER
                    '1'                          , --ITEM_DEFINATION_LEVEL
                    rec_cur_cust_item.commodity_code      , --COMMODITY_CODE
                    '2'                          , --INACTIVE_FLAG
                    'N'                          ,     --LOCK_FLAG
                    sysdate                      , --LAST_UPDATE_DATE
                    vc_last_updated_by                    , --LAST_UPDATED_BY
                    sysdate                          , --CREATION_DATE
                    vc_create_by                     , --CREATED_BY
                    --'10'                          , --LAST_UPDATE_LOGIN
                    'N'                          , --ERROR_CODE
                    ' '                             --ERROR_EXPLANATION
          Insert into mtl_ci_xrefs_interface (
                    PROCESS_FLAG          ,
                    PROCESS_MODE          ,
                    TRANSACTION_TYPE     ,
                    CUSTOMER_NUMBER          ,
                    CUSTOMER_NAME          ,
                    CUSTOMER_ITEM_NUMBER     ,
                    ITEM_DEFINITION_LEVEL     ,
                    INVENTORY_ITEM          ,
                    MASTER_ORGANIzATION_ID     ,
                    PREFERENCE_NUMBER     ,
                    INACTIVE_FLAG          ,
                    LOCK_FLAG          ,
                    LAST_UPDATE_DATE     ,
                    LAST_UPDATED_BY          ,
                    CREATION_DATE          ,
                    CREATED_BY          ,
                    --LAST_UPDATE_LOGIN     ,
                    ERROR_CODE          ,
                    ERROR_EXPLANATION
          Values
                    '1'                    ,      --PROCESS_FLAG
                    '1'                    ,      --PROCESS_MODE
                    'CREATE'               ,      --TRNSACTION_TYPE
                    rec_cur_cust_item.customer_number,     --CUSTOMER_NUMBER
                    rec_cur_cust_item.customer_name     ,      --CUSTOMER_NAME
                    rec_cur_cust_item.customer_item_number, --CUSTOMER_ITEM_NUMBER
                    '1'                    ,     --ITEM_DEFINATION_LEVEL
                    rec_cur_cust_item.inventory_item,     --INVENTORY_ITEM
                    vc_master               ,      --MASTER_ORGANISATION_ID
                    '1'                    ,     --PREFERENCE_NUMBER
                    '2'                    ,     --INACTIVE_FLAG
                    'N'                    ,     --LOCK_FLAG
                    sysdate                    ,     --LAST_UPDATE_DATE
                    vc_last_updated_by          ,     --LAST_UPDATED_BY
                    sysdate                    ,     --CREATION_DATE
                    vc_create_by               ,     --CREATED_BY
                    --'10'                    ,     --LAST_UPDATE_LOGIN
                    'N'                    ,     --ERROR_CODE
                    ' '                         --ERROR_EXPLANATION
--dbms_output.put_line( ' Inserting into reference table - done');
          exception
               when ex_not_ok then
                    update      btl_cust_item
                    set     process_flag = 'E',
                         error_message = 'XREF-'||vc_error_desc
                    where     rowid     = vc_rowid;
          end ;
     end loop;
     commit;
     begin
           dbms_application_info.set_client_info(' ');
     end;
     dbms_output.put_line ( ' End time ' || to_char( sysdate, 'DD-MON-YYYY HH24:MI:SS'));
     exception
          when others then
               dbms_output.put_line( Sqlcode || ' ' || Sqlerrm );
end ;
/

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

What else can be loaded through AP Open Interface

Hi All,
Its a functional query from one who has experience in AP Open Interfaces.
Actually I'm looking it technically but want to know it at high level, that other than Invoices, what else can be populated or loaded through AP Open Interfaces ?
Your earliest response will be highly appreciated.
Regards,

Hi;
Please check below which could be helpful for your issue:
http://docs.oracle.com/cd/A60725_05/html/comnls/us/ap/openimpt.htm
http://www.shareoracleapps.com/2010/05/payables-open-interface-import-basics.html
Regard
Helios

11.5.10 RECEIVING OPEN INTERFACE를 통해 RETURN처리하는 방법

제품 : MFG_PO
작성날짜 : 2006-05-30
11.5.10 RECEIVING OPEN INTERFACE를 통해 RETURN처리하는 방법
==================================================
PURPOSE
11.5.10에서 Receiving Open Interface를 통해 Return처리하는 방법을 기술함.
Explanation
11.5.10 is ROI supports for Standard Purchase Order
. RETURN to RECEIVING transactions
. RETURN to VENDOR transactions
1. Receipt routing = Standard Receipt일 경우
A) perform a "RETURN to RECEIVING" for a standard Purchase Order
through ROI
TRANSACTION_TYPE = RETURN TO RECEIVING
PARENT_TRANSACTION_ID = (Transaction Id for DELIVER transaction)
B) perform a "RETURN to VENDOR" for a standard Purchase Order
through ROI
TRANSACTION_TYPE = RETURN TO VENDOR
PARENT_TRANSACTION_ID = (Transaction Id for RECEIVE transaction)
2. Receipt routing = Direct Receipt일 경우,
==> only 1 step return is needed,
TRANSACTION_TYPE = RETURN TO VENDOR
TRANSACTION_ID = (Transaction Id for DELIVER transaction)
3. a Lot and Serial Controlled Item의 경우,
다음 table들에 data를 Insert해 주어야 합니다.
RCV_TRANSACTIONS_INTERFACE,
MTL_TRANSACTIONS_LOTS_INTERFACE,
MTL_SERIAL_NUMBERS_INTERFACE.
TEST
step1> PO등록
1) Standard Purchase Order number: # 8415
Inventory Item = Lot-Serial-Controlled-1
Receipt Routing = Standard Receipt
Destination Type Code = Inventory
step2) Receipt처리
Receipt number :# 7970
The deliver transaction's quantity=1
item=Lot-Serial-Controlled-1
Lot Number=S336
Serial Number = SN0021
step3> Return처리
A) "RETURN to RECEIVING" for PURCHASE ORDER Example
SQL>
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,
QUANTITY,
UNIT_OF_MEASURE,
ITEM_ID,
EMPLOYEE_ID,
SHIPMENT_HEADER_ID,
SHIPMENT_LINE_ID,
RECEIPT_SOURCE_CODE,
VENDOR_ID,
FROM_ORGANIZATION_ID,
FROM_SUBINVENTORY,
FROM_LOCATOR_ID,
SOURCE_DOCUMENT_CODE,
PARENT_TRANSACTION_ID,
PO_HEADER_ID,
PO_LINE_ID,
PO_LINE_LOCATION_ID,
PO_DISTRIBUTION_ID,
DESTINATION_TYPE_CODE,
DELIVER_TO_PERSON_ID,
LOCATION_ID,
DELIVER_TO_LOCATION_ID,
VALIDATION_FLAG
VALUES
(rcv_transactions_interface_s.nextval, --INTERFACE_TRANSACTION_ID
rcv_interface_groups_s.nextval, --GROUP_ID
SYSDATE, --LAST_UPDATE_DATE
0, --LAST_UPDATE_BY
SYSDATE, --CREATION_DATE
0, --CREATED_BY
0, --LAST_UPDATE_LOGIN
'RETURN TO RECEIVING', --TRANSACTION_TYPE
SYSDATE, --TRANSACTION_DATE
'PENDING', --PROCESSING_STATUS_CODE
'BATCH', --PROCESSING_MODE_CODE
'PENDING', --TRANSACTION_STATUS_CODE
1, --QUANTITY
'Each', --UNIT_OF_MEASURE
169845, --ITEM_ID
13706, --EMPLOYEE_ID
477550, --SHIPMENT_HEADER_ID
484510, --SHIPMENT_LINE_ID
'VENDOR', --RECEIPT_SOURCE_CODE
7927, --VENDOR_ID
204, --FROM_ORGANIZATION_ID
'Stores', --FROM_SUBINVENTORY
null, --FROM_LOCATOR_ID
'PO', --SOURCE_DOCUMENT_CODE
524018, --PARENT_TRANSACTION_ID
40924, --PO_HEADER_ID
46915, --PO_LINE_ID
81963, --PO_LINE_LOCATION_ID
84349, --PO_DISTRIBUTION_ID
'INVENTORY', --DESTINATION_TYPE_CODE
null, --DELIVER_TO_PERSON_ID
null, --LOCATION_ID
null, --DELIVER_TO_LOCATION_ID
'Y' --VALIDATION_FLAG
INSERT INTO MTL_TRANSACTION_LOTS_INTERFACE
( TRANSACTION_INTERFACE_ID,
LAST_UPDATE_DATE,
LAST_UPDATED_BY,
CREATION_DATE,
CREATED_BY,
LAST_UPDATE_LOGIN,
LOT_NUMBER,
TRANSACTION_QUANTITY,
PRIMARY_QUANTITY,
SERIAL_TRANSACTION_TEMP_ID,
PRODUCT_CODE,
PRODUCT_TRANSACTION_ID
VALUES
( MTL_MATERIAL_TRANSACTIONS_S.NEXTVAL,--
TRANSACTION_INTERFACE_ID
SYSDATE, --LAST_UPDATE_DATE
0, --LAST_UPDATED_BY
SYSDATE, --CREATION_DATE
0, --CREATED_BY
0, --LAST_UPDATE_LOGIN
'S366', --LOT_NUMBER
1, --TRANSACTION_QUANTITY
1, --PRIMARY_QUANTITY
MTL_MATERIAL_TRANSACTIONS_S.NEXTVAL, --
SERIAL_TRANSACTION_TEMP_ID
'RCV', --PRODUCT_CODE
RCV_TRANSACTIONS_INTERFACE_S.CURRVAL --
PRODUCT_TRANSACTION_ID
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,--
TRANSACTION_INTERFACE_ID
SYSDATE, --LAST_UPDATE_DATE
0, --LAST_UPDATED_BY
SYSDATE, --CREATION_DATE
0, --CREATED_BY
0, --LAST_UPDATE_LOGIN
'SN0021', --FM_SERIAL_NUMBER
'SN0021', --TO_SERIAL_NUMBER
'RCV', --PRODUCT_CODE
RCV_TRANSACTIONS_INTERFACE_S.CURRVAL --
PRODUCT_TRANSACTION_ID
Commit;
B) "RETURN to VENDOR" Transaction for PURCHASE ORDER
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,
QUANTITY,
UNIT_OF_MEASURE,
ITEM_ID,
EMPLOYEE_ID,
SHIPMENT_HEADER_ID,
SHIPMENT_LINE_ID,
RECEIPT_SOURCE_CODE,
VENDOR_ID,
FROM_ORGANIZATION_ID,
FROM_SUBINVENTORY,
FROM_LOCATOR_ID,
SOURCE_DOCUMENT_CODE,
PARENT_TRANSACTION_ID,
PO_HEADER_ID,
PO_LINE_ID,
PO_LINE_LOCATION_ID,
PO_DISTRIBUTION_ID,
DESTINATION_TYPE_CODE,
DELIVER_TO_PERSON_ID,
LOCATION_ID,
DELIVER_TO_LOCATION_ID,
VALIDATION_FLAG
VALUES
(rcv_transactions_interface_s.nextval, --INTERFACE_TRANSACTION_ID
rcv_interface_groups_s.nextval, --GROUP_ID
SYSDATE, --LAST_UPDATE_DATE
0, --LAST_UPDATE_BY
SYSDATE, --CREATION_DATE
0, --CREATED_BY
0, --LAST_UPDATE_LOGIN
'RETURN TO VENDOR', --TRANSACTION_TYPE
SYSDATE, --TRANSACTION_DATE
'PENDING', --PROCESSING_STATUS_CODE
'BATCH', --PROCESSING_MODE_CODE
'PENDING', --TRANSACTION_STATUS_CODE
1, --QUANTITY
'Each', --UNIT_OF_MEASURE
169845, --ITEM_ID
13706, --EMPLOYEE_ID
477550, --SHIPMENT_HEADER_ID
484510, --SHIPMENT_LINE_ID
'VENDOR', --RECEIPT_SOURCE_CODE
7927, --VENDOR_ID
204, --FROM_ORGANIZATION_ID
'Stores', --FROM_SUBINVENTORY
null, --FROM_LOCATOR_ID
'PO', --SOURCE_DOCUMENT_CODE
524017, --PARENT_TRANSACTION_ID
40924, --PO_HEADER_ID
46915, --PO_LINE_ID
81963, --PO_LINE_LOCATION_ID
84349, --PO_DISTRIBUTION_ID
'RECEIVING', --DESTINATION_TYPE_CODE
null, --DELIVER_TO_PERSON_ID
null, --LOCATION_ID
null, --DELIVER_TO_LOCATION_ID
'Y' --VALIDATION_FLAG
INSERT INTO MTL_TRANSACTION_LOTS_INTERFACE
( TRANSACTION_INTERFACE_ID,
LAST_UPDATE_DATE,
LAST_UPDATED_BY,
CREATION_DATE,
CREATED_BY,
LAST_UPDATE_LOGIN,
LOT_NUMBER,
TRANSACTION_QUANTITY,
PRIMARY_QUANTITY,
SERIAL_TRANSACTION_TEMP_ID,
PRODUCT_CODE,
PRODUCT_TRANSACTION_ID
VALUES
( MTL_MATERIAL_TRANSACTIONS_S.NEXTVAL,--
TRANSACTION_INTERFACE_ID
SYSDATE, --LAST_UPDATE_DATE
0, --LAST_UPDATED_BY
SYSDATE, --CREATION_DATE
0, --CREATED_BY
0, --LAST_UPDATE_LOGIN
'S366', --LOT_NUMBER
1, --TRANSACTION_QUANTITY
1, --PRIMARY_QUANTITY
MTL_MATERIAL_TRANSACTIONS_S.NEXTVAL, --
SERIAL_TRANSACTION_TEMP_ID
'RCV', --PRODUCT_CODE
RCV_TRANSACTIONS_INTERFACE_S.CURRVAL --
PRODUCT_TRANSACTION_ID
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,--
TRANSACTION_INTERFACE_ID
SYSDATE, --LAST_UPDATE_DATE
0, --LAST_UPDATED_BY
SYSDATE, --CREATION_DATE
0, --CREATED_BY
0, --LAST_UPDATE_LOGIN
'SN0021', --FM_SERIAL_NUMBER
'SN0021', --TO_SERIAL_NUMBER
'RCV', --PRODUCT_CODE
RCV_TRANSACTIONS_INTERFACE_S.CURRVAL --
PRODUCT_TRANSACTION_ID
Commit;
step4) RUN the Receiving Transaction Processor with (GROUP_ID=30053)
step5) Check a data
Navigate to Receiving / Receiving Transactions Summary form
Example
Reference Documents
Note#360340.1

I have done this by a direct insert.
I had loaded a table called xx_eam_msii. It holds the item id , org id and locator id.
The following works.
INSERT
INTO MTL_ITEM_LOC_DEFAULTS (INVENTORY_ITEM_ID ,ORGANIZATION_ID ,locator_id,DEFAULT_TYPE,subinventory_code
,LAST_UPDATE_DATE ,LAST_UPDATED_BY ,CREATION_DATE ,CREATED_BY )
(select msi.inventory_item_id,msi.organization_id ,x.inventory_location_id,2,x.receiving_subinventory
,sysdate,11531,sysdate,11531
from mtl_system_items_b msi, xx_eam_msii x
where x.segment1 = msi.segment1 and msi.organization_id = x.organization_id
and not exists (select 1 from MTL_ITEM_LOC_DEFAULTS misd
where misd.inventory_item_id = msi.inventory_item_id and misd.organization_id = msi.organization_id
and DEFAULT_TYPE = 2)
Hope this helps,
Sandeep Gandhi

EAM Asset Number Open Interface - Technical Reference docs required

Similar Messages

Maybe you are looking for