Group Requistion Lines during Requisition Import

When Importing requisitions from the Requisition Interface : po_requisitions_interface_all via Requisition import . Oracle will group the requisitions into 1 or multiple headers  based on Oracle grouping process Which is provided as an Input parameter in the requisition import process


This solution is desirable for Drop ship Process where business many a times needs separate requisitions for individual sales orders. This solution can be achieved by using one of the below changes , which will need a customization to populate the required fields.

• Requisitions Interface has a GROUP_CODE column for the lines which we want to be populated under the same header , same value for group code can be populated for the requisition lines which are intended to be grouped together
• If you specify the value for : REQ_NUMBER_SEGMENT1 in the PO_REQUISITIONS_INTERFACE table then the records with same value will be grouped under the same requisition header
• there is a column of batch_id in requisition interface , you can specify the batch id for the group of records you want to be grouped under same header and then Run requisition import for individual group Id's --> this will also prevent processing of any new records which might have been populated in the requisition interface between the custom code processing and submission of Requisition Import

Requistion Import

Oracle Provides an Interface through which requisition data can be imported into Oracle. this interface is widely used when implementing Drop Ship functionality but can also be used when businesses integrate different systems where requisition is raised in another system but needs to be imported into Oracle.
Depending on business need the INTERFACE_SOURCE_CODE can be populated for each data source.
Further more to control specific data sets to be processed during any run , users can give a combination of INTERFACE_SOURCE_CODE and batch_id , This will ensure only specifc data is picked up
this is helpful in the below scenario :

• Business provides data in the interface , Preprocessing need to be performed on the data and only the processed data should be imported
• the Pre-processing program should update the batch id for the processed records  and submit requisition import with the specific batch id. this will ensure only relevant records are processed

The solution prevents a scenario where due to timing issue unprocessed data get picked up for processed by standard import program

Item Unassignment and Delete Items

There can be scenarios where an Item is mistakenly assigned to a warehouse but we need to un-assign the item from the warehouse , We have 2 options available for this operation depending on the number of items and the number of warehouses from when there items have to be unassigned.


However note that item un-assignment can only be performed provided no material transactions have been booked for the item.


If the data volume is less users can query the items from Item master and uncheck the check boxes of item assignment to the specific warehouses and then save the changes.


For large data volumes we can have follow the step by step approach as below :

1. Delete Item Costs --> Any cost for the item needs to be deleted. This can be achieved by running DELETE scripts on the tables :
1. cst_item_costs
2. cst_item_cost_details
3. CST_COST_UPDATES
4. CST_STANDARD_COSTS

Once the item costs have been cleared we need to group the items into Deletion Groups.
For this an entry needs to be made in the Table :

1. BOM_DELETE_GROUPS --> 1 Entry is made for each Organization (warehouse) from which the item has to be un-assigned
2. BOM_DELETE_ENTITIES --> Entry for individual item is made

Once the data insert is complete the user needs to navigate the screen for Delete Items , Search the BOM Deletion group , review and delete it to complete item un-assignment