This project default determines the use of the extended expediting module. It works as an indicator of whether you want to work with basic or extended expediting.
This decision must be made before you start working in Requisitions and Procurement modules. Once you have:
-
created a planned requisition for purchase,
-
or released a requisition for purchase to procurement,
-
or created an agreement of either type Purchase Order or Notice of Commitment, you can no longer change the project default setting.
-
If you have must switch from basic to extended expediting (not vice versa), you can use the package m_pck_mig_exp. This package should be executed either from a SQL*Plus session as user m_sys or by using a DBMS job on Administration > DBMS Jobs page.
-
You should always look at your routing method on Setup > Routing Methods page before running the above mentioned package.
-
For proper migration and better work, you should set the date types and the destinations which are representing the delivery date and main destination for all the routing methods of the affected project(s) (and product groups).
-
You can use the package to either migrate a specific project or to migrate all the projects that are currently working with basic expediting.
-
If you run the package using the command exec m_pck_mig_exp.migrate_exp (MY_PROJECT); only the data of project MY_PROJECT are migrated.
-
If you run the package using the command exec m_pck_mig_exp.migrate_exp (NULL); the data of all projects working with basic expediting are migrated.
-
The package does not only migrate the data but also sets the project default to Y.
This project default cannot be set at discipline level.
-
Module(s) affected by this setting: Inquiry > Requisition Workload, Agreement > Agreements Overview, Expediting, Planning, Open Procurement Interface.
-
List of Values: Y and N (default).