How to create KMX OM Sales Order Interface

Responsibility Name: KMX Order Management Super User

Concurrent Program: KMX OM Sales Order Interface
Parameters:

Debug Flag = To display log messages in log file. (Yes/No) (will be disabled , not for users)
Load Data = To load data file into the staging table mentioned in the control file. (Yes/No)
Validate Data= To validate staging area against the standard Oracle setups. (Yes/No)
Process Data= To process the data from staging area to oracle base tables. User can view the
standard forms after hitting process data as Yes. This will process the Sales Order into the sales
order form.
Control File= Name of the control file for conversion. (will be disabled , not for users)
Data File= Name of the data file to be uploaded for process.
Request ID=Request ID for which records need to process. (will be disabled , not for users)

Step by step procedure of converting data.

Step1) This step will load data into the staging table and validate against Oracle setups and dumps the
records to the Staging area for Sales Order validation and processing.
Load, validate as Y.
File to be uploaded by IT person to the BSDM_TOP/data/in. Cherie does that for Koyo US.

KMX_OM_Open_Sales
_Order_ Interface_Template SO Sample(Developer Comments).xlsx

Please contact Deepak.khosla@in.fujitsu.com

After concurrent program KMX OM Sales Order Interface has been completed normal, click on the view
output report.(attached below). This report will display the validation and process error and status.

If results looks desired to you please submit the KMX OM Sales Order Interface to import Sales Order
into Oracle with the parameters as mentioned in Step2. If found errors in Step1. Please fix the file and
re-submit as Step1 before proceeding to Step2.

Please contact Deepak.khosla@in.fujitsu.com

Step2)
Submit the concurrent program: KMX OM Sales Order Interface
Responsibility: KMX Order Management Super User
User should select the following parameter to see the correct results.
Process as Y, rest of the parameters input as N.
Control file and data file to leave as default.

View Output after KMX OM Sales Order Interface is completed normal, It displays if records are loaded
succesfully ot nor.

Please contact Deepak.khosla@in.fujitsu.com

2) Go to Sales Order form and verify if sales order is created or not.

Sales Order Header

Sales Order Lines

Please contact Deepak.khosla@in.fujitsu.com

Post Query:
select distinct stg.order_number, ooh.orig_sys_document_ref,
stg.operating_unit, stg.customer_name, stg.customer_number,
stg.account_name, stg.order_type, stg.price_list, stg.sales_rep,
stg.warehouse,
stg.payment_terms, stg.freight_term, stg.item_identifier_type,
stg.ordered_quantity, stg.unit_selling_price, stg.gpr_number,
stg.customer_account_id, stg.ship_to_id, stg.bill_to_id,
stg.price_list_id,
stg.header_warehouse_id, stg.salesrep_id, stg.pay_term_id,
stg.inventory_item_id, stg.oracle_item, stg.oracle_item_id,
ooh.order_number, ooh.org_id, ooh.cust_po_number,
ooh.flow_status_code,
ooh.sold_from_org_id, ooh.sold_to_org_id, ooh.ship_from_org_id,
ooh.ship_to_org_id, ooh.invoice_to_org_id, ooh.salesrep_id,
ool.line_number, ool.ordered_item, ool.ordered_quantity,
ool.inventory_item_id, ool.price_list_id, ool.freight_terms_code,
ool.fob_point_code, ool.unit_selling_price, ool.unit_list_price,
ool.ordered_item_id, ool.flow_status_code, ool.calculate_price_flag
from oe_order_headers_all ooh,
oe_order_lines_all ool,
bsdm_om_sales_order_intf_stg stg
where ooh.header_id = ool.header_id
and ooh.orig_sys_document_ref = stg.org_id||'_'||stg.order_number
and ool.orig_sys_line_ref =
stg.order_number||'_'||stg.org_id||'_'||stg.seq_id
and ool.ORDERED_ITEM = stg.ORACLE_ITEM
and stg.process_flag = '7'
and stg.request_id = 4620600

Please contact Deepak.khosla@in.fujitsu.com