Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Implementation at PAVCI
PAVCI Working process for New Models:
Engg Arrg Receive from KM -------->Converted as Per PAVCI
Structure into Excel format and issued to all the Departments in
PAVCI------> Parts List is uploaded to Oracle Apps as per our
standard Program------> Change Notes Received from KM and
implemented, Change Notes issued to Every Dept and
implemented in Oracle Apps----> Engg Release received from
KM--------> Parts List are compared and differences are reconciled
and change notes are issued for discrepancies-----> After Model
launch, Change Notes are received continuously and implemented
in Oracle apps and issued to every Dept.
After Web Portal Implementation
Engg Arrg Receive from KM----> New project defined and Inserted
for every Model and base Parts List as KM Parts list with levelling
Structure----> Parts List is Uploaded to Web-Portal from TOPS
System-----> Local Parts Conversion shall be done for Parts List
Conversion----> BOM is pushed to Oracle Apps PAVCI from Web
Portal-------> New Items Inserted as per the Items from Oracle
APPS-------> Change Notes received from KM shall be mapped to
our Naming Convention--------> Change Notes pushed from Web
Portal to Oracle and Implemented--------> Engg Release
Downloaded from TOPS and Oracle Parts List compared with and
differences reconciled--------> After Model launch, Change Notes
are received continuously and implemented in Oracle apps and
issued to every Dept. as standard from Web-Portal.
Problem Points to be discussed with Alvin San during Web Portal
Implementation:
issues we face during our implementation with Azura San and ask
for the Same Scenario solution in PAVCKM.
Thank You very Much Azura San and Kuan San for all the help
during this discussion.