|
 



 



 
 


Prior to Oracle EBS Release 11.5.10, Functional Companions were
used for custom functionalities in Configurator
Oracle has introduced Configurator Extensions in Release 11.5.10
which replaced Functional Companions
Configurator Extensions are referred with short name CX
CX definitions are stored in the database

   



 

 
 
 
|n short, Configurator Extensions are Java code that you write to
perform functions that go beyond the functionality and Configurator
Rules that Oracle Configurator Developer provides out of the box

|
 

|
 
 
 



Configurator Extensions extend the runtime Oracle Configurator with

custom code through established interfaces
Configurator Extension includes the following:


  



    
   
 


 

 


 
 



|


 
 





 
 

 
 
 ! "#
 




 





! "
|
 

 
 



1.

Write and Compile Java Classes

2.

|n Configurator Developer, Create Configurator Extension Archive and

upload the compiled Java Classes with Z|P format

3.

Add Archive to Configurator Models Archive Path

4.

Create Configurator Extension Rule:

!  
 




 

$
! 

! 


5.

Test the functionality in Model Debugger and Runtime User |nterface

6.

Publish the Configurator Model

|
 

 
 



Configurator Extension Archive

|
%
 





 

  
 
 

 

!   ! &
 
  
 
 

 

! 

 

! &
|
! 

! 

'
 

( )| *
|
 

 
 

*


|
 

 
 



Configurator Extension Archive Path is


!  
 



   
 


  
 
! 
  

 

 





 
 


+, 
 


 
 
! 
-!  

! .

  
! .
|
 

 
 

/! 0

|
 

 
 

/! 0 
 "

|
 

 
 





Configurator Extension Rule associates

$ 
! 


 


 
 



|


*






1








  




|
 

 
 





*


Rule Name Write Attributes Soft Options

Event postCX|nit, postConfigSave
Java Class oracle.apps.cz.ext.SoftOptions.WriteAttributes.java
Method initialize, afterSave
Description
 

 






  !"


#


$!%
!&

|
 

^^

 
 





|
 

*
 
 "

 
 




An event is something that occurs during a runtime configuration session, such a

change in the value of a node. Events have names, such as postValueChange

Every Configurator Extension Rule is triggered by an event in the runtime

configuration session





 
 

 



 


 
 2
 2 










 

 










!  23

$

4

At runtime, Oracle Configurator signals configuration events. When one occurs,

this runs all methods bound to that event if the binding is in scope

|
 

 
 





  


  




 





  





   



 




 


 


 

 




 


  
 






 
 
 

 



 
 



 














  


 


  
  










 


 
  

 



 


|
 

 
 


*

Scope is used to control when an extension is invoked
Every Event Binding has one of three possible Scopes

/




 

 


0
$ /1


 


 

 0
$ 
*  /1

 

 
 

 



0
The scope on an event binding specifies if it should be interested in a
specific event being signaled by the Configurator

|
 

 
 




$


There are four types of Bindings

*

/""$ 

 
 
0

 2



/""
 
 
   
0
!  /"" 
 ! 
0
+/"" 
0

|
 

^*

 
 



56
Desired Functionality: Trigger a calculation when a custom button is clicked
Rule Name Query Data Extension
Event onCommand (This automatically creates a Button in Configurator U|
Java Class oracle.apps.cz.ext.SoftOptions.CustomData
Method QueryData
Description-
 '

 !

$!
$!
%


Code : !
( !!


 

|
 

^]

 
 



57
Desired Functionality: Clear selections in certain node(s based on selection
change in one or more node(s
Rule Name - Clear Field For Frame Field Changes
Node - UC27 MODEL.Page 1.Frame
Event - postValueChange
Java Class oracle.apps.cz.ext.SoftOptions.CustomData
Method clearFields
Description
 !
%
 ")*&


! 

Code : !
( !!



 


|
 

 
 

5#

Bind all the CZ nodes used in JAVA method as parameters to the
method for getting or setting data on the nodes
Use class ConfigTransaction to begin a transaction for modifying
value or state of CZ Nodes
Always commit or rollback the ConfigTransaction to refresh the state
of CZ nodes after completion of CX Rule.
Handle the exceptions and use class |nformationalMessage to show
messages on Configurator U|
Use Jdeveloper to write the JAVA class and make a jar file of
oracle.apps.cz.* and attach it through the Project Setting Option.

|