1I want to enter default sub inventory and stock locators for some of the inventory items.

So
that at the time of inspection (if applicable), it will populate sub inventory and stock locators and
will directly deliver the qty in that particular default stock locators.

The It will avoid the work of stores person to check and deliver the material.

Ans:- Please set up the Default material Transaction in INV module.

You need to perform this step :

1. Sub-Inventory : In which Default Locator is existing
2. Locator : which is to be default once material get delivered.
3. Item : Whose Location is to be defaulted.

Navigation Path : Oracle Inv--->Setup----> Transaction---> Item Transaction Defaults

Select New & Enter Item Name.

Then Default Type : Shipping or Receiving.
Then Assign Sub-Inventory & Locator in Both the Tabs Provided to you.

Constraint : Material will be moved to default Sub-Inv & Locator irrespective of Inspection result at
QC level. It will be moved to same location whether it is accepted or rejected. If Quality / WMS
modules are not present.

2I have problem regarding to uploading data in master item through import item.
data is in MTL_SYSTEM_ITEMS_INTERFACE and import item pick nothing
and showing no error in mtl_interface_errors. can anyone help me out please.

Ans:- i went through the following and uploaded up to 120000 items

A table is created on apps schema to import the following from delivered data excel sheets; item
number , short description and long description

? The table created named INV_PREUPLOAD and is created as follows:

o CREATE TABLE INV_PREUPLOAD

(
SEGMENT1 VARCHAR2(40 BYTE),
DESCRIPTION VARCHAR2(240 BYTE),
LONG_DESCRIPTION VARCHAR2(4000 BYTE)
)

? Using the toad tool or any other tool you can import the INV_PREUPLOAD table with data from
delivered excel sheets

? The table used by the import status is named MTL_SYSTEM_ITEMS_INTERFACE under the
apps schema

? Run the following query:

o INSERT INTO MTL_SYSTEM_ITEMS_INTERFACE

(SEGMENT1,DESCRIPTION,LONG_DESCRIPTION)

select segment1,description,long_description
from inv_preupload
? Then update mtl_system_items_interface with the following update statement
update MTL_SYSTEM_ITEMS_INTERFACE

set

process_flag = 1
, PRIMARY_UOM_CODE = 'x'
, PRIMARY_UNIT_OF_MEASURE = 'x'
, set_process_id =1
, transaction_type = 'CREATE'
, ORGANIZATION_ID = org id
, SUMMARY_FLAG = 'N'
, ENABLED_FLAG = 'Y'
, PURCHASING_ITEM_FLAG = 'Y'
, SHIPPABLE_ITEM_FLAG = 'Y'
, CUSTOMER_ORDER_FLAG = 'Y'
, INTERNAL_ORDER_FLAG = 'N'
, SERVICE_ITEM_FLAG = 'N'
, INVENTORY_ITEM_FLAG = 'Y'
, ENG_ITEM_FLAG = 'N'
, INVENTORY_ASSET_FLAG = 'Y'
, PURCHASING_ENABLED_FLAG = 'Y'
, CUSTOMER_ORDER_ENABLED_FLAG = 'Y'
, INTERNAL_ORDER_ENABLED_FLAG = 'N'
, SO_TRANSACTIONS_FLAG = 'Y'
, MTL_TRANSACTIONS_ENABLED_FLAG = 'Y'
, STOCK_ENABLED_FLAG = 'Y'
, BOM_ENABLED_FLAG = 'Y'
, BUILD_IN_WIP_FLAG = 'Y'
, CATALOG_STATUS_FLAG = 'N'
, CHECK_SHORTAGES_FLAG = 'N'
, RETURNABLE_FLAG = 'Y'
, TAXABLE_FLAG = 'N'
, ALLOW_ITEM_DESC_UPDATE_FLAG = 'Y'
, RECEIPT_REQUIRED_FLAG = 'Y'
, RFQ_REQUIRED_FLAG = 'N'
, PRICE_TOLERANCE_PERCENT = 0
, LOT_CONTROL_CODE = 1
, SHELF_LIFE_CODE = 1
, SHELF_LIFE_DAYS = 0
, SERIAL_NUMBER_CONTROL_CODE = 1
, EXPENSE_ACCOUNT = 46306
, RESTRICT_SUBINVENTORIES_CODE = 2
, RESTRICT_LOCATORS_CODE = 2
, LOCATION_CONTROL_CODE = 1
, PLANNING_TIME_FENCE_CODE = 4
, LEAD_TIME_LOT_SIZE = 1
, ACCEPTABLE_RATE_INCREASE = 0
, ACCEPTABLE_RATE_DECREASE = 0
, PLANNING_TIME_FENCE_DAYS = 1
, END_ASSEMBLY_PEGGING_FLAG = 'N'
, REPETITIVE_PLANNING_FLAG ='N'
, BOM_ITEM_TYPE = 4
, PICK_COMPONENTS_FLAG = 'N'
, REPLENISH_TO_ORDER_FLAG = 'N'
, ATP_COMPONENTS_FLAG = 'N'
, ATP_FLAG = 'N'
, WIP_SUPPLY_TYPE = 2
, ALLOWED_UNITS_LOOKUP_CODE = 3
, COST_OF_SALES_ACCOUNT = 46306
, SALES_ACCOUNT = 46306
, DEFAULT_INCLUDE_IN_ROLLUP_FLAG = 'Y'
, INVENTORY_ITEM_STATUS_CODE = 'Active'
, INVENTORY_PLANNING_CODE = 6
, PLANNING_MAKE_BUY_CODE = 2
, ROUNDING_CONTROL_TYPE = 1
, POSTPROCESSING_LEAD_TIME = 0
, MRP_SAFETY_STOCK_CODE = 1
, RESERVABLE_TYPE = 1
, VENDOR_WARRANTY_FLAG = 'N'
, SERVICEABLE_COMPONENT_FLAG = 'N'
, SERVICEABLE_PRODUCT_FLAG = 'N'
, PREVENTIVE_MAINTENANCE_FLAG = 'N'
, PRORATE_SERVICE_FLAG = 'N'
, INVOICEABLE_ITEM_FLAG = 'Y'
, INVOICE_ENABLED_FLAG = 'Y'
, MUST_USE_APPROVED_VENDOR_FLAG = 'N'
, OUTSIDE_OPERATION_FLAG = 'N'
, COSTING_ENABLED_FLAG = 'Y'
, CYCLE_COUNT_ENABLED_FLAG = 'N'
, AUTO_CREATED_CONFIG_FLAG = 'N'
, ITEM_TYPE = 'P'
, SHIP_MODEL_COMPLETE_FLAG = 'N'
, MRP_PLANNING_CODE = 3
, RETURN_INSPECTION_REQUIREMENT = 2
, ATO_FORECAST_CONTROL = 2
, EFFECTIVITY_CONTROL = 1
, EQUIPMENT_TYPE = 2
, WEB_STATUS = 'UNPUBLISHED'
, BULK_PICKED_FLAG = 'N'
, LOT_STATUS_ENABLED = 'N'
, SERIAL_STATUS_ENABLED = 'N'
, LOT_SPLIT_ENABLED = 'N'
, LOT_MERGE_ENABLED = 'N'
, DUAL_UOM_CONTROL = 1
, DUAL_UOM_DEVIATION_HIGH = 0
, DUAL_UOM_DEVIATION_LOW = 0
, SERV_BILLING_ENABLED_FLAG = 'N'
, LOT_TRANSLATE_ENABLED = 'N'
, DEFAULT_SO_SOURCE_TYPE = 'INTERNAL'
, CREATE_SUPPLY_FLAG = 'Y'
, TRACKING_QUANTITY_IND = 'P'
, ONT_PRICING_QTY_SOURCE = 'P'
, SO_AUTHORIZATION_FLAG = 1
, CONSIGNED_FLAG = 2
, ASN_AUTOEXPIRE_FLAG = 2
, VMI_FORECAST_TYPE = 1
, EXCLUDE_FROM_BUDGET_FLAG = 2
, DRP_PLANNED_FLAG = 2
, CRITICAL_COMPONENT_FLAG = 2
, CONTINOUS_TRANSFER = 3
, CONVERGENCE = 3
, DIVERGENCE = 3
and of course set the above update values according to your setup of items

3Can we prevent Oracle Sourcing from grouping similar Requisition?

When creating a RFQ from some Requisitions in Oracle Sourcing, if these PORs have same
item, Sourcing combines the lines to make only one line, changing the quantity.
This is an issue if PORs have different need dates because supplier will not see this detail.
Can we prevent Oracle sourcing from doing so ?

Ans
The point is that this issue seem to work ONLY if you have 2 (or more) different lines of SAME
requisition# . in this case you can choose to split them and it works. BUT if – as very often
happens - you have multiple DIFFERENT requisitions with same items and you try to ungroup
them , you get a strange error that prevents you from doing that “because you don’t have the
same requisition” , which doesn’t make mush sense to me …

They way out is, we if we have the existing PO of same supplier then we can add all different
lines from Different requisitions at single PO. Also due date is same or different , it will create
different line in PO creation. Then existing PO go to re-approval process if it is already approved.