ESYU: Order Import를 통해 간단한 ATO Model을 위한 Order를 생성하는 방법

Purpose
Oracle Order Management - Version: 11.5.9 to 12.0.5
Information in this document applies to any platform.
아래와 같은 구조를 갖는 간단한 ATO model을 위한 order를 order import를 통해 생성하는 방법에 대해 알아본다.
ATO Model (542851)
|- ATO Option Class (542852)
|--Option Item (152840)
Solution
Order Import interface table에 header와 lines을 입력하는 아래 script를 이용한다.
Interface tables에 data insert 후 Order Import concurrent program을 실행한다.
INSERT INTO OE_HEADERS_IFACE_ALL (
order_source_id
,orig_sys_document_ref
,creation_date
,created_by
,last_update_date
,last_updated_by
,operation_code
,sold_to_org_id
VALUES (
1227 --order_source_id
,'12345' --orig_sys_document_ref
,sysdate --creation_date
,-1 --created_by
,sysdate --last_update_date
,-1 --last_updated_by
,'INSERT' --operation_code
,1005 --sold_to_org_id
INSERT INTO OE_LINES_IFACE_ALL (
order_source_id
,orig_sys_document_ref
,orig_sys_line_ref
,inventory_item_id
,ordered_quantity
,operation_code
,created_by
,creation_date
,last_updated_by
,last_update_date
,top_model_line_ref
,item_type_code
VALUES (
1227 --order_source_id
,'12345' --orig_sys_document_ref
,'1' --orig_sys_line_ref
,542851 --inventory_item
,1 --ordered_quantity
,'INSERT' --operation_code
,-1 --created_by
,sysdate --creation_date
,-1 --last_updated_by
,sysdate --last_update_date
,'1' --top_model_line_ref
,'MODEL' --item_type_code
INSERT INTO OE_LINES_IFACE_ALL (
order_source_id
,orig_sys_document_ref
,orig_sys_line_ref
,inventory_item_id
,ordered_quantity
,operation_code
,created_by
,creation_date
,last_updated_by
,last_update_date
,top_model_line_ref
,link_to_line_ref
,item_type_code
VALUES (
1227 --order_source_id
,'12345' --orig_sys_document_ref
,'2' --orig_sys_line_ref
,542852 --inventory_item_id
,1 --ordered_quantity
,'INSERT' --operation_code
,-1 --created_by
,sysdate --creation_date
,-1 --last_updated_by
,sysdate --last_update_date
,'1' --top_model_line_ref
,'1' --link_to_line_ref
,'CLASS' --item_type_code
INSERT INTO OE_LINES_IFACE_ALL (
order_source_id
,orig_sys_document_ref
,orig_sys_line_ref
,inventory_item_id
,ordered_quantity
,operation_code
,created_by
,creation_date
,last_updated_by
,last_update_date
,top_model_line_ref
,link_to_line_ref
,item_type_code
VALUES (
1227 --order_source_id
,'12345' --orig_sys_document_ref
,'3' --orig_sys_line_ref
,152840 --inventory_item_id
,1 --ordered_quantity
,'INSERT' --operation_code
,-1 --created_by
,sysdate --creation_date
,-1 --last_updated_by
,sysdate --last_update_date
,'1' --top_model_line_ref
,'2' --link_to_line_ref
,'OPTION' --item_type_code
); commit;
- Orders, Returns -> Import Orders -> Order Import Request
- Parameter form의 Order Source LOV에서 Order Source를 선택
- Submit the concurrent request.
Reference
Note 746677.1

Similar Messages

Unable to book orders created by Sales Order with ATO Model Items

I am trying to create Orders for Ato Model Items with Option classes and Option using process_order API. The Issue we are facing is when we start booking the order. Although we are passing all the otions that are required for the Model, it says the configuration is incomlete when we try to book it.
DECLARE
v_line_id oe_order_lines_all.line_id%TYPE;
v_api_version_number NUMBER := 1;
l_return_status VARCHAR2(2000) := FND_API.G_FALSE;
l_line_tbl oe_order_pub.line_tbl_type;
l_msg_data VARCHAR2(300);
l_msg_count NUMBER;
l_header_rec oe_order_pub.header_rec_type;
l_new_header_rec oe_order_pub.header_rec_type;
t_header_val_rec oe_order_pub.header_val_rec_type;
t_header_adj_tbl oe_order_pub.header_adj_tbl_type;
t_header_adj_val_tbl oe_order_pub.header_adj_val_tbl_type;
t_header_price_att_tbl oe_order_pub.header_price_att_tbl_type;
t_header_adj_att_tbl oe_order_pub.header_adj_att_tbl_type;
t_header_adj_assoc_tbl oe_order_pub.header_adj_assoc_tbl_type;
t_header_scredit_tbl oe_order_pub.header_scredit_tbl_type;
t_header_scredit_val_tbl oe_order_pub.header_scredit_val_tbl_type;
t_out_line_tbl oe_order_pub.line_tbl_type;
t_line_val_tbl oe_order_pub.line_val_tbl_type;
t_line_adj_tbl oe_order_pub.line_adj_tbl_type;
t_line_adj_val_tbl oe_order_pub.line_adj_val_tbl_type;
t_line_price_att_tbl oe_order_pub.line_price_att_tbl_type;
t_line_adj_att_tbl oe_order_pub.line_adj_att_tbl_type;
t_line_adj_assoc_tbl oe_order_pub.line_adj_assoc_tbl_type;
t_line_scredit_tbl oe_order_pub.line_scredit_tbl_type;
t_line_scredit_val_tbl oe_order_pub.line_scredit_val_tbl_type;
t_lot_serial_tbl oe_order_pub.lot_serial_tbl_type;
t_lot_serial_val_tbl oe_order_pub.lot_serial_val_tbl_type;
t_action_request_tbl oe_order_pub.request_tbl_type;
v_message_index NUMBER;
v_api_message VARCHAR2(300);
v_count NUMBER := 1;
BEGIN
oe_msg_pub.initialize;
fnd_global.apps_initialize(1459,21623,660,NULL);
commit;
mo_global.init('S',82);
--header records
l_header_rec := oe_order_pub.g_miss_header_rec;
-- l_header_rec.shipping_instructions := p_special_instructions;
l_header_rec.ship_to_org_id := 1067;
l_header_rec.cust_po_number     :='9090909090';
l_header_rec.operation := oe_globals.g_opr_create;
l_header_rec.transactional_curr_code := 'USD';
--l_header_rec.org_id := 82;
--l_header_rec.context :=82 ;
--l_header_rec.header_id         := null;
--l_header_rec.order_number      := 100;
-- l_header_rec.version_number := 1;
l_header_rec.open_flag := 'Y';
l_header_rec.booked_flag := 'N';
l_header_rec.order_category_code := 'ORDER';
l_hus,
x_msg_data => l_msg_data,
x_msg_count => l_msg_count,
x_header_rec => l_new_header_rec,
x_header_val_rec => t_header_val_rec,
x_header_adj_tbl => t_header_adj_tbl,
x_header_adj_val_tbl => t_header_adj_val_tbl,
x_header_price_att_tbl => t_header_price_att_tbl,
x_header_adj_att_tbl => t_header_adj_att_tbl,
x_header_adj_assoc_tbl => t_header_adj_assoc_tbl,
x_header_scredit_tbl => t_header_scredit_tbl,
x_header_scredit_val_tbl => t_header_scredit_val_tbl,
x_line_tbl => t_out_line_tbl,
x_line_val_tbl => t_line_val_tbl,
x_line_adj_tbl => t_line_adj_tbl,
x_line_adj_val_tbl => t_line_adj_val_tbl,
x_line_price_att_tbl => t_line_price_att_tbl,
x_line_adj_att_tbl => t_line_adj_att_tbl,
x_line_adj_assoc_tbl => t_line_adj_assoc_tbl,
x_line_scredit_tbl => t_line_scredit_tbl,
x_line_scredit_val_tbl => t_line_scredit_val_tbl,
x_lot_serial_tbl => t_lot_serial_tbl,
x_lot_serial_val_tbl => t_lot_serial_val_tbl,
x_action_request_tbl => t_action_request_tbl
IF l_return_status = FND_API.G_RET_STS_UNEXP_ERROR THEN
RAISE FND_API.G_EXC_UNEXPECTED_ERROR;
ELSIF l_return_status = FND_API.G_RET_STS_ERROR THEN
RAISE FND_API.G_EXC_ERROR;
ELSE
dbms_output.put_line('Order Created'||l_header_rec.order_number||l_return_status );
END IF;
EXCEPTION
WHEN FND_API.G_EXC_ERROR THEN
FOR x_index IN 1..l_msg_count
LOOP
OE_MSG_PUB.GET(p_msg_index => x_index,
p_encoded => FND_API.G_FALSE ,
p_data => v_api_message ,
p_msg_index_out => v_message_index
dbms_output.put_line('Execution'||v_api_message);
l_return_status := FND_API.G_RET_STS_ERROR;
END LOOP;
WHEN FND_API.G_EXC_UNEXPECTED_ERROR THEN
-- To see the errors
FOR x_index in 1..l_msg_count
LOOP
OE_MSG_PUB.GET(p_msg_index => x_index ,
p_encoded => FND_API.G_FALSE,
p_data => v_api_message ,
p_msg_index_out => v_message_index
dbms_output.put_line('Unexpected'||v_api_message);
l_return_status := FND_API.G_RET_STS_UNEXP_ERROR ;
END LOOP;
WHEN OTHERS THEN
dbms_output.put_line('In Others'||SQLERRM);
END;
COMMIT;
END; -- get_process_order
assing all the otions that are required for the Model, it says the configuration is incomlete when we try to book it.
DECLARE
v_line_id oe_order_lines_all.line_id%TYPE;
v_api_version_number NUMBER := 1;
l_return_status VARCHAR2(2000) := FND_API.G_FALSE;
l_line_tbl oe_order_pub.line_tbl_type;
l_msg_data VARCHAR2(300);
l_msg_count NUMBER;
l_header_rec oe_order_pub.header_rec_type;
l_new_header_rec oe_order_pub.header_rec_type;
t_header_val_rec oe_order_pub.header_val_rec_type;
t_header_adj_tbl oe_order_pub.header_adj_tbl_type;
t_header_adj_val_tbl oe_order_pub.header_adj_val_tbl_type;
t_header_price_att_tbl oe_order_pub.header_price_att_tbl_type;
t_header_adj_att_tbl oe_order_pub.header_adj_att_tbl_type;
t_header_adj_assoc_tbl oe_order_pub.header_adj_assoc_tbl_type;
t_header_scredit_tbl oe_order_pub.header_scredit_tbl_type;
t_header_scredit_val_tbl oe_order_pub.header_scredit_val_tbl_type;
t_out_line_tbl oe_order_pub.line_tbl_type;
t_line_val_tbl oe_order_pub.line_val_tbl_type;
t_line_adj_tbl oe_order_pub.line_adj_tbl_type;
t_line_adj_val_tbl oe_order_pub.line_adj_val_tbl_type;
t_line_price_att_tbl oe_order_pub.line_price_att_tbl_type;
t_line_adj_att_tbl oe_order_pub.line_adj_att_tbl_type;
t_line_adj_assoc_tbl oe_order_pub.line_adj_assoc_tbl_type;
t_line_scredit_tbl oe_order_pub.line_scredit_tbl_type;
t_line_scredit_val_tbl oe_order_pub.line_scredit_val_tbl_type;
t_lot_serial_tbl oe_order_pub.lot_serial_tbl_type;
t_lot_serial_val_tbl oe_order_pub.lot_serial_val_tbl_type;
t_action_request_tbl oe_order_pub.request_tbl_type;
v_message_index NUMBER;
v_api_message VARCHAR2(300);
v_count NUMBER := 1;
BEGIN
oe_msg_pub.initialize;
fnd_global.apps_initialize(1459,21623,660,NULL);
commit;
mo_global.init('S',82);
--header records
l_header_rec := oe_order_pub.g_miss_header_rec;
-- l_header_rec.shipping_instructions := p_special_instructions;
l_header_rec.ship_to_org_id := 1067;
l_header_rec.cust_po_number     :='9090909090';
l_header_rec.operation := oe_globals.g_opr_create;
l_header_rec.transactional_curr_code := 'USD';
--l_header_rec.org_id := 82;
--l_header_rec.context :=82 ;
--l_header_rec.header_id         := null;
--l_header_rec.order_number      := 100;
-- l_header_rec.version_number := 1;
l_header_rec.open_flag := 'Y';
l_header_rec.booked_flag := 'N';
l_header_rec.order_category_code := 'ORDER';
l_hus,
x_msg_data => l_msg_data,
x_msg_count => l_msg_count,
x_header_rec => l_new_header_rec,
x_header_val_rec => t_header_val_rec,
x_header_adj_tbl => t_header_adj_tbl,
x_header_adj_val_tbl => t_header_adj_val_tbl,
x_header_price_att_tbl => t_header_price_att_tbl,
x_header_adj_att_tbl => t_header_adj_att_tbl,
x_header_adj_assoc_tbl => t_header_adj_assoc_tbl,
x_he
Message was edited by:
user604069

Are you able to book an order on sales order work bench with same configuartion?

Issue in sales order order import program

Hi all,
I need to create a Sales Order using interface tables.First I inserted the record into the interface table OE_HEADERS_IFACE_ALL.I populated necessary columns in it.
Then I executed Order Import Concurrent program giving value of order source(which I created using order import source setup),order reference(which is origSysDocumentRef column value in the above said interface table).
But the concurrent program is not picking up the records in the interface table and its output shows no order to process.As a result no record is inserted in the OE_ORDER_HEADERS_ALL table.
I dont understand where the problem lies.Please help me out to solve the issue.
Thanks,
goutam

Hi Sandeep Gandhi,
Thanks for your reply.
Now Order Import Concurrent program picks up the header records from the OE_HEADERS_IFACE_ALL interface table successfully for processing.
But during the process some errors are raised, and the error_flag in the header interface table is set to 'Y'.
I want to know where can i find those errors,so that I can correct them.
Is there any error log tables that contains these errors occured during import?
Or we have any other way to identify it?
Please help me..
Thanks,
goutam

How to import order from Interface table using Api Order Import

Hi All
I am using oracle EBus R12.
I was working in Data migration in Order management.
I have manually entered data in Interface table ie (oe_header_iface_all) and (oe_lines_iface_all)
And i have given the order_source_id as 2 and order_source as COPY.
And after that i ran the concurrent program with parameter as COPY but the concurrent program does'nt picks the order in the interface.
Can any one please tell the steps in OM.
Thanks & Regards
Srikkanth.M

Hi;
please check:
http://sureshvaishya.blogspot.com/2009/04/order-import-using-api.html
Also i suggest see:
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]
http://www.google.com.tr/#hl=tr&source=hp&q=Api+Order+Import+&oq=Api+Order+Import+&aq=f&aqi=&aql=&gs_sm=e&gs_upl=469l469l0l1l1l0l0l0l0l0l0ll0&fp=87c57485fd170fd2&biw=1259&bih=793
Regard
Helios

Import quote sales order with 'Pending Internal Approval' status.

Hi,
I’m trying to import a quote sales order using the oracle Order Import request, the order was imported with status 'Draft'.
Is there any way to import the quote sales order with 'Pending Internal Approval'?
or any API to change the Quote Status from 'Draft' to 'Pending Internal Approval'?
Thank You In Advance.
Ali

No in standard, there is no such TCodes. You have to develop a zee report considering the tables VBBE (for open order quantity) and MARD (storage location wise stocks)
thanks
G. Lakshmipathi

Order Import Workflow

Hi All,
Can anyone please let me know the purpose of oracle Order Import workflow.
What exactly is it used for. I would like to understand in detail about what does the order Import workflow do and what does the Oracle Order Import Interface does.
Regards,
Tech D

There is nothing like Order Import Workflow. EBS leverages Oracle Workflow in Oracle Order Management to facilitate Order processing.
For Order Import in EBS you can refet below
[url http://docs.oracle.com/cd/E18727_01/doc.121/e13406/T373258T376579.htm] Order Import in Oracle Order Management
For Workflow in Order Management, please refer below
[url http://docs.oracle.com/cd/E18727_01/doc.121/e16350/T393423T393427.htm]Using Oracle Workflow in Oracle Order Management
Please refer the following MOS notes for further insight into Order Import.
Order Import Functionality In Order Management [ID 746650.1]
FAQ on Order Import [ID 1275116.1]
Importing Sales Orders and/or Returns [ID 199281.1]
HTH
Cheers,
ND
Use the "helpful" or "correct" buttons to award points to replies / Mark the thread as answered, if your question is answered.

How to import qoutations or sale orders using Order Import request?

Hello,
Anyone have document or link to read? I can't find this document.
thank you.

Order Import Functionality In Order Management [ID 746650.1] ---- Metalink Note in Details.
Regards,
Khan.

Oracle Order Import Program

Hello,
Can the Order Import program running concurrently in the concurrent manager. We want to run order import in parallel
Thanks.

Hi,
As far as I know, there are no restrictions but performance. However, as order import works in a master-child basis (11i), maybe, you could submit one order import and use the parameter instances to define how many child order import programs you want to run. This way, order import will split orders to be import among the child requests in parallel.
Regards,
Ketter Ohnes

Collected ATO Model & items with sales orders and forcast not in ASCP plan

PTO/ATO/ATP challenged - need some help understanding this and how it should work or if it can work.
On 11.5.10.2, a customer wants to see the ATO model and options in the ASCP plan
when the ATO configuration item is not created in the Sales Order.
Using the BOMN example below level 2 - ATO item and level 4 - Marketing Code (Forecast at this level)
ALTIX-4700-PTO-Z level 1 PTO Model
ALTIX-4700-ATO-Z level 2 ATO model
--ALTIX4700-SYS-Z level 3
LST-IRU-Z level 4 Ordered item
LST-4700-WC-Z level 4 Ordered item
LST-IRU-WC-SRACK-Z level 4 Ordered item
They are not seeing level 4 items in the plan even though they have Sales Order Demand and forecast at this level.
They see the items in the collection workbench, but they are missing in the ASCP plan.
Any ideas will be appreciated.
Thanks.
Edited by: Bob Marchant on Oct 16, 2008 12:02 PM

Are you able to book an order on sales order work bench with same configuartion?

Order Import not importing ATO items

Order Import not importing ATO items and can see error message in log file SELECT COMP_CODE FAILED , NO DATA FOUND INVALID ITEM TYPE. After research with this error found the API OE_CONFIG_UTIL.Explode not fully exploding the ATO items. Any one come across this kind of issue please let me know.
Thanks,
Uma

>
I launched the Import directly from the Interface screen, it creates the order. But not through the Order Import. >
Go to the OM Super user resp.
Verify that the interface records are there.
Come out of the interface screen.
Go to requests screen.
Submit order import.
Does it process the records?
If it does, then it most likely means that the parameters (or the org_id) associated with the Order Import program you mention above are not correct.
Sandeep Gandhi

ESYU: Importing Standard Purchase Orders에서 문제 발생시 진단 방법

Purpose
Oracle Purchasing - Version: 11.5.10.2 to 12.0.6
Information in this document applies to any platform.
ConcurrentProgram:POXPOPDOI - Import Standard Purchase Orders
이 문서는 reader게 Importing Standard Purchase Orders 실행 중 갑자기 발생하는 issue에 대해 어떻게
대응하는지에 대한 자세한 정보를 제공한다.
Instroduction
Purchase Document Open Interface는 다량의 Standard Purchase Order는 Oracle Purchasing으로 빨리
import 할 수 있게 한다. Import process는 import 되어야 하는 document information을 PO interface tables에
넣어주는 작업을 필요로하며, data를 validate 하고 application에 PO를 생성하거나 error message를 return 하는
Import Standard Purchase Orders concurrent program을 실행한다.
이 문서의 목적은 Importing Standard Purchase Orders에 관련된 process를 이해하거나 갑자기 발생한 문제의
원인을 찾는데 도움을 주기 위함이다. PO import 문제는 일반적으로 interface tables에 입력된 불일치하는 data가
원인이며, 일단 문제가 확인되면 Metalink는 비슷한 문제를 찾아주거나 Oracle Support에 Service Request를 log
할 수 있다.
Test case Information
1. 아래 insert 문장을 이용하여 PO interface tables에 data를 입력:
INSERT INTO po.po_headers_interface
(interface_header_id,
action,
org_id,
document_type_code,
currency_code,
agent_id,
vendor_name,
vendor_site_code,
ship_to_location,
bill_to_location,
reference_num)
VALUES
(apps.po_headers_interface_s.NEXTVAL,
'ORIGINAL',
207, -- Seattle
'STANDARD',
'USD', -- Your currency code
24, -- Your buyer id stock
'Advanced Network Devices',
'FRESNO',
'V1- New York City', -- Your ship to
'V1- New York City', -- Your bill to
'Currency test') -- Any reference num
INSERT INTO po.po_lines_interface
(interface_line_id,
interface_header_id,
line_num,
shipment_num,
line_type,
item,
uom_code,
quantity,
--unit_price,
promised_date,
ship_to_organization_code,
ship_to_location)
VALUES
(po_lines_interface_s.nextval,
po_headers_interface_s.currval,
1,
1,
'Outside processing',
'Flooring OSP',
'Ea',
1,
--17.50,
'10-APR-2009',
'V1',
'V1- New York City' )
INSERT INTO po.po_distributions_interface
(interface_header_id,
interface_line_id,
interface_distribution_id,
distribution_num,
quantity_ordered,
charge_account_id)
VALUES
(po_headers_interface_s.currval,
po.po_lines_interface_s.CURRVAL,
po.po_distributions_interface_s.NEXTVAL,
1,
1,
12975) -- Your Charge Account Id
2. Interface tables에 data가 insert 되었다면 import progra을 실행전 정보를 확인하기 위해 아래 query 문을 이용한다.
a - Select * from PO_HEADERS_INTERFACE where INTERFACE_HEADER_ID=&headerid
b - Select * from PO_LINES_INTERFACE where INTERFACE_HEADER_ID=&headerid
c - Select * from PO_DISTRIBUTIONS_INTERFACE where INTERFACE_HEADER_ID=&headerid
3. Data를 review 했으면 Import Standard Purchase Orders program을 실행한다.
Parameter >>
Default Buyer: Null
Create or Update Items: No
Approval Status: INCOMPLETE
Batch Id: Null
4. 만일 program에 문제가 있어 error가 발생한다면 error의 원인을 제공하기 위해 Purchasing Interface Error Report를
실행할 수 있다.
Parameter >>
Source Program: PO_DOCS_OPEN_INTERFACE
Purge Data: No
만일 PO가 import 되지 않았다면 Puchasing Interface Errors Report와 동일한 정보를 보기 위해 Interface Errors table을
아래 SQL을 이용하여 조회할 수 있다.
SELECT * FROM PO_INTERFACE_ERRORS WHERE INTERFACE_TRANSACTION_ID ='&recordsinterfacetransid';
Diagnostics
Import Standard Purchase ORder process의 troubleshoot 도움을 위해 아래 Diagnostics과 Reports를 이용한다.
1. Diagnostics Tool : Oracle Purchasing Purchasing Documents Open Interface Data Collection Test
(please refer to Note 224887.1 for assistance)
이 Diagnostics는 import program에 의해 import 되는 data를 validate 할 것이며 missing 되거나 맞지않는 정보를 highlight 한다.
이 Tool은 interface tables에 있는 맞지 않거나 불완전한 data의 자세한 정보를 제공할 수 있다.
Error는 PO를 import 할 때 발생한 문제 분석을 시도하는데 매우 유익하므로 SR을 log시 이 Diagnostic output을 upload 하는
것을 권장한다.
2. Purchasing Interface Errors Report
이 report는 Oracle Purchasing에서 사용가능하며 Import Standard Purchase Orders program을 실행시 발생하는
error를 강조한다.
Tracing
11.5.10 이상의 version에서 Import Standard Purchase Orders program의 trace를 생성:
1. Navigate to System Administrator responsibility
2. Navigate to Profiles->System
3. Query the Profile Option Concurrent: Allow Debugging and set it to Yes at User level
4. Navigate to Purchasing responsibility
5. From the Requests form, choose the Import Standard Purchase Orders program and set the required Parameters
6. Click the Debug button
7. Check the SQL Trace checkbox and specify Trace with Binds and Waits
8. Submit the Concurrent program
9. Retrieve the trace file created.
Logging
Import Standard Purchase Orders program의 FND Deug Log 생성:
1. Log_seq를 아래 SQL을 이용하여 확인.
select max(log_sequence) from fnd_log_messages;
2. Set the following profiles at the user level:
FND: Debug Log Enabled = YES
FND: Debug Log Filename = NULL
FND: Debug Log Level = STATEMENT
FND: Debug Log Module = %
3. Run Import Standard Purchase Orders program
4. Using a SQL client run the following query :
Select * from fnd_log_messages
where log_sequence > &log_seq_noted_above
order by log_sequence;
이 query의 output은 Import Standard Purchase Orders program이 실행 중 발생한 error를 표시한다.
Reference
Note 781351.1

ESYU: Order Import를 통해 기존 Order를 reference 하는 RMA Order를 생성하는 방법

Purpose
Oracle Order Management - Version: 11.5.9 to 12.0.5
Information in this document applies to any platform.
Order Import를 통해 기존 존재하는 Order를 reference 하는 RMA Order의 생성 방법을 알아본다.
Solution
Order Import interface의 header와 line에 data를 insert 하기 위해 아래 script를 이용한다.
INSERT INTO OE_HEADERS_IFACE_ALL (
order_source_id
,orig_sys_document_ref
,creation_date
,created_by
,last_update_date
,last_updated_by
,operation_code
,sold_to_org_id
,order_type_id
,booked_flag
VALUES
1227 --order_source_id
,'123456' --orig_sys_document_ref
,sysdate --creation_date
,-1 --created_by
,sysdate --last_update_date
,-1 --last_updated_by
,'INSERT' --operation_code
,1005 --sold_to_org_id
,1436 --order_type_id
,'Y' --booked_flag
INSERT INTO OE_LINES_IFACE_ALL (
order_source_id
,orig_sys_document_ref
,orig_sys_line_ref
,inventory_item_id
,ordered_quantity
,operation_code
,created_by
,creation_date
,last_updated_by
,last_update_date
,return_reason_code
,return_context
,return_attribute1
,return_attribute2
VALUES
1227 --order_source_id
,'123456' --orig_sys_document_ref
,'1' --orig_sys_line_ref
,249 --inventory_item_id
,10 --ordered_quantity
,'INSERT' --operation_code
,-1 --created_by
,sysdate --creation_date
,-1 --last_updated_by
,sysdate --last_update_date
,'CANCELLATION' --return_reason_code
,'ORDER' --referencing a sales order
,'157638' --header_id of referenced order
,'256619' --line_id of referenced line
commit;
API guide와 eTRAM을 참조하여 귀사의 testcase에 알맞게 위 insert script를 수정하거나 다른 columns을 add 한다.
위 모든 interface tables의 order_source_id에는 당신의 order_source_id 값을 입력한다.
위 모든 interface tables의 orig_sys_document_ref에는 각각의 order에 대한 unique 값을 입력한다.
Interface table에 값을 insert 하면 Order Import Concurrent program을 실행한다.
- Navigate to Orders, Returns -> Import Orders -> Order Import Request
- Select your Order Source from the LOV in the parameters form.
- Submit the concurrent request.
Reference
Note 746668.1

ESYU: Order Import를 통해 기존에 있는 Order에 hold를 적용할 수 있는 방법

Purpose
Oracle Order Management - Version: 11.5.10
Information in this document applies to any platform.
Order Import를 통해 기존에 존재하는 Order에 hold를 적용하는 방법에 대해 알아본다.
Solution
아래와 같이 order import interface를 이용하여 기존에 존재하는 order에 hold를 적용할 수 있다.
OE_HEADERS_IFACE_ALL:
ORDER_SOURCE_ID
ORIG_SYS_DOCUMENT_REF
OPERATION_CODE => 'UPDATE'
ORG_ID
ORDER_TYPE_ID
CREATED_BY
CREATION_DATE
LAST_UPDATED_BY
LAST_UPDATE_DATE
OE_ACTIONS_IFACE_ALL:
ORDER_SOURCE_ID,
ORIG_SYS_DOCUMENT_REF,
ORG_ID,
HOLD_ID,
HOLD_TYPE_CODE,
HOLD_TYPE_ID,
OPERATION_CODE => 'APPLY_HOLD'
HOLD_ID는 적용되어야 할 hold type을 의미한다.
(HOLD_ID from OE_HOLD_DEFINITIONS)
HOLD_TYPE_CODE는 생성되어야 하는 hold source에 대한 entity code이다.
C: Customer hold source
S: Bill To or Ship To hold source
I: Item hold source
O: Order hold source
W: Warehouse Hold Source
HOLD_TYPE_ID 값은 입력하는 HOLD_TYPE_CODE에 의존한다.
예를들어 HOLD_TYPE_CODE = 'C' 라면 HOLD_TYPE_ID는 customer_number가 되어야 한다.
Reference
Note 444040.1

Importing configurations via Order Import in R12

Hi All,
We need some help with this issue we are facing while importing configurations ( PTO ) via order import process.
The scenario is like this : we have parent PTO Model Item : A and under this we have 2 Option Classes within the BOM: OC1 & OC2
Each of these option classes have 2 items each : option class - OC1 has ( Item B & Item C) while option class - OC2 has ( Item D & Item E)
Now in the OM interface tables we want to interface : PTO Model Item A and along with it the Item B and Item E ( one item from each of the option classes). Hence we populate the oe_lines_iface_all table the below mentioned fields
inventory_item, item_type_code , orig_sys_line_ref , top_model_line_ref, ship_from_org
A                     MODEL               1.0                        NULL                      S1
B                                                                            1.0                         S1
E                                                                            1.0                         S1
--Now when we run the Order Import we are getting errors : "org_sys_line_ref cannot be NULL" and errors - "item B and E are not found in the BOM of the model A"
--when we try to populate the orig_sys_line_ref columns values for Item B and E as let's say 2.0 and 3.0 , still we get the "items not found in the BOM of the model A error message". But when we check the BOM these component items are present there.
With the same Model Item A and Option class component items B and E we are able to create an order successfully within OM frontend screen and the BOM structure for the PTO Model A is also active and enabled.. This is a Published BOM for the PTO Model Item A
Could someone please help as to what additional columns need to be populated or what needs to be done in order to get this resolved.
Thanks

We referred the Oracle OM related white paper from metalink :
Oracle Order Management Suite White Papers (Doc ID 113492.1) - Importing Configurations

Issue in Batch import of Configuration orders using order Import

Hi All,
I am trying to import Configuration orders into Oracle R12 using Order import. As per Oracle white paper on this, I ahve populated all the required fields like top_model_line_ref,link_to_line_ref, item_type_code etc. But order import is giving error "Item ABC not found in BOM of Model XYZ".
Is there any setup or profile I am missing?
Please help me on this also is there any other approach to import Batch configuration orders?
Thanks!!

you have to customize tha availability check on MM movements in OMCP

ESYU: Order Import를 통해 간단한 ATO Model을 위한 Order를 생성하는 방법

Similar Messages

Maybe you are looking for