| Implementing sourcing rules for copied requisitions in iProcurement [message #569336] |
Wed, 24 October 2012 22:11 |
 |
purnimabh
Messages: 2
Registered: October 2012
|
Junior Member |
|
|
Business requirement:
Users in the Field like technicians copy internal requisitions more often than creating new ones in iProcurement as it saves time.
Expectation for the copied requisition to have correct source Org that is reflective of the current sourcing rule.
Issue Description:
When the requisitions are copied it copies over the source organization instead of deriving source Org based on sourcing rules.
We have multiple primary distribution centers and the sourcing rules keep changing often based on business needs.
When old requisitions are copied they are likely to have source org which is not reflective of the current sourcing rule.
This was causing a major issue for fulfilling on time since the orders used to have incorrect source Org (Ship from Org on internal sales Orders) which had to be updated if the planners happen to catch this on time or cancel the line.
Resolution:
For all requisitions entered in iProcurement we are applying sourcing rules after they are submitted in iProcurement and are created as internal orders but still are in the order interface.
We have developed a custom program that calls the seeded program for sourcing rules and derive the source org for by passing the item and destination org for the orders in the order interface and apply the source org derived on these orders. After this we call order import.
For errored records in Order import due to item not assigned in the destination org etc. we fix the errors and then run the custom program to apply correct sourcing rule.
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
