Administración de la empresa > Implementación de Windchill ESI > Implementing Windchill ESI in an ORACLE Applications Environment > Oracle Applications API and OIT Structures > Create and Change Process Plans
  
Create and Change Process Plans
* 
Windchill MPMLink Process Plans are referred to as Routings in Oracle Applications.
The following API structure tables list all the APIs and the respective API fields that are required to create routings within the current version of Oracle Applicationsdistribution targets.
API Name = Routings Business Object Interface
The Routings Business Object Interface (BOI) is invoked to create and change Routings in Oracle. The Routing API is designed so that objects within one Routing are entered into the API by referencing each other through the common business relationships. The following are the main areas of the BOM API:
1. Routing Header
2. Routing Revision's
3. Operations
4. Resources
All calls to the Routing API require the Routing Header to be populated. Operations, Operation Resources, are repeating structures, whereas you may only have one Routing Header.
Windchill Attribute Name
API Segment/ API Structure
API field
API field description
Value if Default
Source
Transform
Transaction ID
Routing Header/P tc_Int_rtg _api_hdr
TIBCO_ KEY
Tibco_Key
Transaction ID +time Stamp
Windchill/ TIBCO
Concatenate Transaction ID with date and time
Distribution Target
Routing Header/ Ptc_Int_r tg_api_h dr
ORGANI ZATION _CODE
Organization
N/A
Windchill
Substring
ProcessPlan PartLink- ProcessPl anPartNu mber
Routing Header/ Ptc_Int_r tg_api_h dr
ASSEM BLY_IT EM_NA ME
Assembly item Name
N/A
Windchill
N/A
N/A
Routing Header/ Ptc_Int_r tg_api_h dr
ENG_RO UTING_ FLAG
Eng routing flag
2
N/A
N/A
(Action flag)
Routing Header/ Ptc_Int_r tg_api_h dr
TRANS ACTION _TYPE
Transaction Type
"CREATE" "UPDATE
" Windchill/ TIBCO
N/A
Transaction ID
Routing Revision/ Ptc_Int_r tg_api_re v
TIBCO_ KEY
Tibco_Key
Transaction ID +time Stamp
Windchill/ TIBCO
Concat Transacti on Id with date/time
Distribution Target
Routing Revision/ Ptc_Int_r tg_api_re v
ORGANI ZATION _CODE
Organization
N/A
Windchill
Substring
Assembly Part Number
Routing Revision/ Ptc_Int_r tg_api_rev
ASSEM BLY_IT EM_NAME
Assembly item Name
N/A
Windchill
N/A
Assembly Part Number
Routing Revision/ Ptc_Int_r tg_api_re v
ASSEM BLY_IT EM_NA ME
Assembly item Name
N/A
Windchill
N/A
ProcessPlan Revision
Routing Revision/ Ptc_Int_r tg_api_re v
REVISION
Revision
N/A
Windchill
Front pad with --
ProcessPlan -Start Effective Date
Routing Revision/ Ptc_Int_r tg_api_re v
START_ EFFECTI VE_DAT E
Start Effective date
TIBCO's system date/time
Windchill/ TIBCO
Date-format
(Action flag)
Routing Revision/ Ptc_Int_r tg_api_re v
TRANS ACTION _TYPE
Transaction Type
"CREATE
"Windchill
N/A
Transacti on ID
Routing Operations/ Ptc_Int_r tg_api_o pr
TIBCO_ KEY
Tibco_Key
Transaction ID +Time Stamp
Windchill/ TIBCO
Concat Transacti on Id with date/time
Distributi on Target
Routing Operations/ Ptc_Int_r tg_api_o pr
ORGANI ZATION _CODE
Organization
N/A
Windchill
Substring
Assembl y Part Number
Routing Operations/ Ptc_Int_r tg_api_o pr
ASSEM BLY_IT EM_NA ME
Assembly item Name
N/A
(Action flag)
Routing Operations/ Ptc_Int_r tg_api_o pr
TRANS ACTION _TYPE
Transaction Type
"CREATE" "UPDATE"
Distribution Target
Routing Operations/ Ptc_Int_r tg_api_o pr
ORGANI ZATION _CODE
Organization
N/A
ProcessPlan-Start Effective Date
Routing Operations/ Ptc_Int_r tg_api_o pr
START_ EFFECTI VE_DAT E
Start effective date
N/A
Old Operation Label
Routing Operations/ Ptc_Int_r tg_api_o pr
OPERAT ION_SE QUENC E_NUM BER
Operation Sequence Number
N/A
Windchill
N/A
New Operation Label
Routing Operations/ Ptc_Int_r tg_api_o pr
NEW_O PERATI ON_SEQ UENCE_ NUMBE R
New Operation Sequence Number
N/A
Windchill
N/A
N/A
Routing Operations/ Ptc_Int_r tg_api_o pr
OPERAT ION_TYPE
Operation type
1
TIBCO
N/A
Operation Workcenter Link- Department
Routing Operations/ Ptc_Int_r tg_api_o pr
DEPART MENT_ CODE
Department Code
N/A
Windchill
N/A
* 
The Associated Bills of Material is also processed while the Routing is processed. When the data is passed for a Routing, the associated Bills of Material data is also passed in the API structure. The API structure is the same as the BOM API structure. Thus the Routing and its associated BOM get processed atomically by the API APPS.PTC_RTG_API.main_adb.