Tag Archives: Oracle

Oracle Inventory Reservation Transfer between Different Sources

Creating reservation for inventory items is one of most common actions regarding business requirements in Oracle E-Business Suite platform. In this example, we transfer existing reservation quantity between different transaction source types/organizations/uom’s in R12 version of EBS.

For each three item-organization-transaction source type , there should be only one unique row in INV.MTL_RESERVATIONS table. So following loop is for a better code review and look. (using cursor depends on you).  We use standart Oracle Inventory API’s and table/record types in this procedure. Here is the PL/SQL script;

procedure transfer_reservation  (  p_rsv_rec in  inv_reservation_global.mtl_reservation_rec_type,
								   x_msg_count out nocopy number,
								   x_msg_data  out nocopy varchar2,
								   x_return_status out varchar2,
								   x_reservation_id out number ) is

x_serial_number   inv_reservation_global.serial_number_tbl_type;
v_rsv_from_rec    inv_reservation_global.mtl_reservation_rec_type ;
v_rsv_to_rec      inv_reservation_global.mtl_reservation_rec_type ;
ln_total_res_qty number:=0 ;

cursor c_res(p_inv_item_id number , p_organization_id number , p_uom varchar2)  is
		select	re.reservation_id,
		        /*you can use a your conversion functions if your source 
				and destination for different UOM's*/
				xxln_inv_pkg.UOM_CONVERSION(p_inventory_item_id =>p_inv_item_id,
					  			       pcur_qty =>re.reservation_quantity,
								       pcur_uom =>re.reservation_uom_code,
								       pnew_uom =>p_uom) as reservation_quantity,
		   from mtl_reservations re
		  where organization_id = p_organization_id
			and inventory_item_id = p_inv_item_id
			and demand_source_type_id = (select transaction_source_type_id
										   from mtl_txn_source_types														
									      where transaction_source_type_name = 'SOME-TRANSACTION-SOURCE')
	   order by re.creation_date;

		v_rsv_to_rec.demand_source_type_id  := p_rsv_rec.demand_source_type_id; 
		v_rsv_to_rec.demand_source_name     := to_char(sysdate);

		for crec in c_res(p_rsv_rec.inventory_item_id,p_rsv_rec.organization_id, p_rsv_rec.reservation_uom_code)  loop

			v_rsv_from_rec.reservation_id  := crec.reservation_id;
			/*Here I use each remaining quantity from source until it equals to demand amount.
			 After process , we could have still remaining amount in our quota*/
			if( p_rsv_rec.reservation_quantity-ln_total_res_qty<crec.reservation_quantity ) then

				v_rsv_to_rec.reservation_quantity :=p_rsv_rec.reservation_quantity-ln_total_res_qty;
				v_rsv_to_rec.reservation_uom_code :=p_rsv_rec.reservation_uom_code;
				ln_total_res_qty:=ln_total_res_qty+v_rsv_to_rec.reservation_quantity ;


				v_rsv_to_rec.reservation_quantity := crec.reservation_quantity;
				v_rsv_to_rec.reservation_uom_code := p_rsv_rec.reservation_uom_code;

			end if;

			inv_reservation_pub.transfer_reservation(p_api_version_number        => 1.0,
													 p_init_msg_lst              => FND_API.G_TRUE,
													 x_return_status             => x_return_status,
													 x_msg_count                 => x_msg_count,
													 x_msg_data                  => x_msg_data,
												   --p_is_transfer_supply       IN  VARCHAR2 DEFAULT fnd_api.g_true
													 p_original_rsv_rec          =>  v_rsv_from_rec,
													 p_to_rsv_rec                =>  v_rsv_to_rec ,
													 p_original_serial_number    =>  x_serial_number ,
													 p_to_serial_number          =>  x_serial_number ,
												   --p_validation_flag          IN  VARCHAR2 DEFAULT fnd_api.g_true
		   										   --p_over_reservation_flag    IN  NUMBER DEFAULT 0
													 x_to_reservation_id         =>x_reservation_id);

			if (x_return_status<>'S') then

				return  ;

			end if ;

		end loop ;

end ;

That’s it !

Data Migration via Advanced PL/SQL – Using Bulk Processing

Data Migration/Manuplation operations are common in projects, in this case we will use “Bulk Processing” for fastest UPDATE operations in Oracle Databases. We have two staging tables; xxln.xxln_bom_operational_routings xbor and xxln.xxln_bom_operation_sequences . We are moving old sequence values on our production tables in E-Business Suite BOM (Bill of materials) schema .

This PL/SQL code shows how it works ;


cursor c1 is 
      select /*+ FIRST_ROWS
             bos.rowid as main_comp_rowid, 
            from xxln.xxln_bom_operational_routings xbor, 
                 xxln.xxln_bom_operation_sequences xbos ,   
                 mtl_system_items_b msib, 
                 bom_operational_routings bor,
                 bom_operation_sequences bos ,
                 mtl_parameters mp  
            where xbor.assembly_item_code = msib.segment1
              and xbor.organization_code = mp.organization_code
              and bor.organization_id=mp.organization_id
              and msib.organization_id = mp.organization_id
              and bor.assembly_item_id = msib.inventory_item_id
              and bor.organization_id = mp.organization_id
              and bos.routing_sequence_id = bor.routing_sequence_id
              and xbos.routing_sequence_id= xbor.routing_Sequence_id
              and nvl(bor.alternate_routing_designator ,'-99') = nvl(xbor.alternate_routing_designator,'-99')
              and nvl(bos.disable_date,sysdate-1000) = nvl(xbos.disable_date,sysdate-1000)  
              and bos.operation_seq_num = xbos.operation_seq_num ;              
type crec_type is table of c1%rowtype index by binary_integer; 
crec crec_type ; 


        open c1 ; 
        fetch c1 bulk collect into crec limit 2000000 ; 
            forall i in crec.first..crec.last 
                     update bom_operation_sequences set 
                            attribute14 = crec(i).routing_sequence_id,
                            attribute15 = crec(i).operation_sequence_id,
                            where rowid =crec(i).main_comp_rowid ; 
        exit when c1%notfound ; 
        end loop ; 
end ;

We use main tables rowid on UPDATE operation , FIRST_ROWS hint and combine it fetching data with BULK COLLECT INTO and FORALL LOOP for best result. You can also divide the query by adding a condition and execute it in different times , this helps cleaning rollback segments (caused by commit) if you are working on VLDB ‘s .


Oracle E-Business Suite – Bill of Materials ATO Configurations Migration via SQL Loader

In this case,  we are going to create scripts for migrating data from 11i Oracle EBS to version R12.  This process is including generating “meaningful” data with SQL , creation of custom staging table of bom.bom_ato_configurations , a bulk insert via SQL Loader using single control(.ctl) file and finally runing it in Linux. Let’s start ;

First of all we are creating custom staging table and indexes for ATO Configurations in R12 on custom schema  ;

  config_item_id number, 
  organization_id number, 
  base_model_id number, 
  component_item_id number,  
  component_code varchar2(240 BYTE), 
  creation_date date,  
  component_quantity number, 
  last_referenced_date date, 
  cfm_routing_flag number, 
  organization_code varchar2(3 byte),
  config_item_code varchar2(150 byte),
  base_model_code varchar2(150 byte),
  component_item_code varchar2 (150 byte),
  component_code_name varchar2(2000 byte)
            INITIAL          128K
            NEXT             128K
            MINEXTENTS       1
            MAXEXTENTS       UNLIMITED
            PCTINCREASE      0
            BUFFER_POOL      DEFAULT

            INITIAL          64K
            NEXT             1M
            MINEXTENTS       1
            MAXEXTENTS       UNLIMITED
            PCTINCREASE      0
            BUFFER_POOL      DEFAULT


Then we generate our more “meaningful” hierarchical material – item data associated with components via following SQL script;

select b.config_item_id, 
       msib.segment1 as config_item_code,
       msib2.segment1 as base_model_code,
       msib3.segment1 as component_item_code,
             x3.segment1 ,'--') as component_code_name 
  from bom.bom_ato_configurations b , 
       mtl_system_items_b msib ,
       mtl_system_items_b msib2, 
       mtl_system_items_b msib3,
       mtl_parameters mp ,
       mtl_system_items_b x1,
       mtl_system_items_b x2,
       mtl_system_items_b x3
 where b.organization_id = mp.organization_id 
   and mp.organization_id = msib.organization_id 
   and b.config_item_id = msib.inventory_item_id
   and mp.organization_id = msib2.organization_id 
   and b.base_model_id = msib2.inventory_item_id
   and mp.organization_id = msib3.organization_id 
   and b.component_item_id = msib3.inventory_item_id 
   and x1.inventory_item_id(+) = rtrim(ltrim( substr(b.component_code, 0,
                                    decode(instr (b.component_code,'-',1,1), 0,
                                       length(b.component_code),instr (b.component_code,'-',1,1))),'-') ,'-' )  
   and x1.organization_id(+)  = b.organization_id 
   and x2.inventory_item_id(+) =  rtrim(ltrim( substr(b.component_code,
                                    decode( instr(b.component_code,'-',1,1),0,1000, instr(b.component_code,'-',1,1)) ,
                                    decode(instr (b.component_code,'-',1,2),0,length(b.component_code)+1,
                                     instr(b.component_code,'-',1,2)) - instr (b.component_code,'-',1,1)),'-'))
   and x2.organization_id(+)   = b.organization_id 
   and x3.inventory_item_id(+) =  rtrim(ltrim( substr(b.component_code,
                                    decode(instr (b.component_code,'-',1,2),0,1000,instr (b.component_code,'-',1,2)),
                                    length(b.component_code)+1- instr (b.component_code,'-',1,2)),'-'))
   and x3.organization_id(+)  = b.organization_id

Now we need to export this data to SQL Loader control file , i use TOAD’s sqlloader extension in this case , it can directly write output results to single .ctl file . But you can also manually create your own control file by refencing a exported .csv sheet.


I use EBS Vision Database so item and component names don’t look like a material! but your in production DB should not look like this . This script also creates .bad and .dsc file in the same directory that you can check if there is any error . SQL Loader control file is that one  ;

Fields terminated by ";" Optionally enclosed by '|'
4524;207;143;1492;|143-1490-1492|;|03/29/2001 10:49:56|;1;|03/29/2001 10:49:56|;NULL;|M1|;|CN97444*4523|;|CN97444|;|CM55243|;|CN97444-OC42556-CM55243|
4524;207;143;251;|143-299-251|;|03/29/2001 10:49:56|;1;|03/29/2001 10:49:56|;NULL;|M1|;|CN97444*4523|;|CN97444|;|CM08830|;|CN97444-OC29315-CM08830|
4524;207;143;197;|143-313-197|;|03/29/2001 10:49:56|;1;|03/29/2001 10:49:56|;NULL;|M1|;|CN97444*4523|;|CN97444|;|CM94043|;|CN97444-OC55449-CM94043|
4524;207;143;185;|143-297-185|;|03/29/2001 10:49:56|;1;|03/29/2001 10:49:56|;NULL;|M1|;|CN97444*4523|;|CN97444|;|CM41684|;|CN97444-OC68020-CM41684|
4524;207;143;217;|143-347-217|;|03/29/2001 10:49:56|;1;|03/29/2001 10:49:56|;NULL;|M1|;|CN97444*4523|;|CN97444|;|CM56560|;|CN97444-OC55437-CM56560|
4524;207;143;257;|143-347-257|;|03/29/2001 10:49:56|;1;|03/29/2001 10:49:56|;NULL;|M1|;|CN97444*4523|;|CN97444|;|CM49954|;|CN97444-OC55437-CM49954|
4524;207;143;219;|143-347-219|;|03/29/2001 10:49:56|;1;|03/29/2001 10:49:56|;NULL;|M1|;|CN97444*4523|;|CN97444|;|CM59311|;|CN97444-OC55437-CM59311|
4524;207;143;215;|143-347-215|;|03/29/2001 10:49:56|;1;|03/29/2001 10:49:56|;NULL;|M1|;|CN97444*4523|;|CN97444|;|CM54321|;|CN97444-OC55437-CM54321|
4524;207;143;1490;|143-1490|;|03/29/2001 10:49:56|;1;|03/29/2001 10:49:56|;NULL;|M1|;|CN97444*4523|;|CN97444|;|OC42556|;|CN97444-OC42556|
4524;207;143;299;|143-299|;|03/29/2001 10:49:56|;1;|03/29/2001 10:49:56|;NULL;|M1|;|CN97444*4523|;|CN97444|;|OC29315|;|CN97444-OC29315|
4524;207;143;313;|143-313|;|03/29/2001 10:49:56|;1;|03/29/2001 10:49:56|;NULL;|M1|;|CN97444*4523|;|CN97444|;|OC55449|;|CN97444-OC55449|
4524;207;143;297;|143-297|;|03/29/2001 10:49:56|;1;|03/29/2001 10:49:56|;NULL;|M1|;|CN97444*4523|;|CN97444|;|OC68020|;|CN97444-OC68020|
4524;207;143;347;|143-347|;|03/29/2001 10:49:56|;1;|03/29/2001 10:49:56|;NULL;|M1|;|CN97444*4523|;|CN97444|;|OC55437|;|CN97444-OC55437|
4524;207;143;143;|143|;|03/29/2001 10:49:56|;1;|03/29/2001 10:49:56|;NULL;|M1|;|CN97444*4523|;|CN97444|;|CN97444|;|CN97444|
221170;209;220028;220035;|220028-220035|;|10/23/2009 13:22:02|;1;|10/23/2009 13:22:02|;NULL;|M2|;|HFAT001-Computer-Controlled|;|HFAT001|;|HFOC006|;|HFAT001-HFOC006|
221170;209;220028;220061;|220028-220035-220061|;|10/23/2009 13:22:02|;1;|10/23/2009 13:22:02|;NULL;|M2|;|HFAT001-Computer-Controlled|;|HFAT001|;|HF55004|;|HFAT001-HFOC006-HF55004|
221170;209;220028;220028;|220028|;|10/23/2009 13:22:02|;1;|10/23/2009 13:22:02|;NULL;|M2|;|HFAT001-Computer-Controlled|;|HFAT001|;|HFAT001|;|HFAT001|
221168;209;220080;220030;|220080-220030|;|10/23/2009 13:22:02|;1;|10/23/2009 13:22:02|;NULL;|M2|;|HFAT002-375HP|;|HFAT002|;|HFOC001|;|HFAT002-HFOC001|
221168;209;220080;220037;|220080-220030-220037|;|10/23/2009 13:22:02|;1;|10/23/2009 13:22:02|;NULL;|M2|;|HFAT002-375HP|;|HFAT002|;|HF50001|;|HFAT002-HFOC001-HF50001|
221168;209;220080;220075;|220080-220075|;|10/23/2009 13:22:02|;1;|10/23/2009 13:22:02|;NULL;|M2|;|HFAT002-375HP|;|HFAT002|;|HFOC008|;|HFAT002-HFOC008|
221168;209;220080;220077;|220080-220075-220077|;|10/23/2009 13:22:02|;1;|10/23/2009 13:22:02|;NULL;|M2|;|HFAT002-375HP|;|HFAT002|;|HF57001|;|HFAT002-HFOC008-HF57001|
221168;209;220080;220080;|220080|;|10/23/2009 13:22:02|;1;|10/23/2009 13:22:02|;NULL;|M2|;|HFAT002-375HP|;|HFAT002|;|HFAT002|;|HFAT002|
10541;1884;7033;7113;|7033-7047-7113|;|07/31/2003 12:46:34|;1;|07/31/2003 12:46:34|;NULL;|W1|;|WDAT001*10540|;|WDAT001|;|WD50152|;|WDAT001-WDOC104-WD50152|
10541;1884;7033;7107;|7033-7045-7107|;|07/31/2003 12:46:34|;1;|07/31/2003 12:46:34|;NULL;|W1|;|WDAT001*10540|;|WDAT001|;|WD50100|;|WDAT001-WDOC102-WD50100|
10541;1884;7033;7099;|7033-7041-7099|;|07/31/2003 12:46:34|;1;|07/31/2003 12:46:34|;NULL;|W1|;|WDAT001*10540|;|WDAT001|;|WD50007|;|WDAT001-WDOC100-WD50007|
10541;1884;7033;7047;|7033-7047|;|07/31/2003 12:46:34|;1;|07/31/2003 12:46:34|;NULL;|W1|;|WDAT001*10540|;|WDAT001|;|WDOC104|;|WDAT001-WDOC104|
10541;1884;7033;7045;|7033-7045|;|07/31/2003 12:46:34|;1;|07/31/2003 12:46:34|;NULL;|W1|;|WDAT001*10540|;|WDAT001|;|WDOC102|;|WDAT001-WDOC102|
10541;1884;7033;7041;|7033-7041|;|07/31/2003 12:46:34|;1;|07/31/2003 12:46:34|;NULL;|W1|;|WDAT001*10540|;|WDAT001|;|WDOC100|;|WDAT001-WDOC100|
10541;1884;7033;10539;|7033-7039|;|07/31/2003 12:46:34|;1;|07/31/2003 12:46:34|;NULL;|W1|;|WDAT001*10540|;|WDAT001|;|WDAT004*10538|;|WDAT001-WDAT004|
10541;1884;7033;10537;|7033-7037|;|07/31/2003 12:46:34|;1;|07/31/2003 12:46:34|;NULL;|W1|;|WDAT001*10540|;|WDAT001|;|WDAT003*10536|;|WDAT001-WDAT003|
10541;1884;7033;10535;|7033-7035|;|07/31/2003 12:46:34|;2;|07/31/2003 12:46:34|;NULL;|W1|;|WDAT001*10540|;|WDAT001|;|WDAT002*10534|;|WDAT001-WDAT002|
10541;1884;7033;7033;|7033|;|07/31/2003 12:46:34|;1;|07/31/2003 12:46:34|;NULL;|W1|;|WDAT001*10540|;|WDAT001|;|WDAT001|;|WDAT001|
10539;1884;7039;7397;|7039-7071-7397|;|07/31/2003 12:46:33|;1;|07/31/2003 12:46:33|;NULL;|W1|;|WDAT004*10538|;|WDAT004|;|WD51301|;|WDAT004-WDOC114-WD51301|
10539;1884;7039;7389;|7039-7069-7389|;|07/31/2003 12:46:33|;1;|07/31/2003 12:46:33|;NULL;|W1|;|WDAT004*10538|;|WDAT004|;|WD51205|;|WDAT004-WDOC115-WD51205|
10539;1884;7039;7377;|7039-7067-7377|;|07/31/2003 12:46:33|;1;|07/31/2003 12:46:33|;NULL;|W1|;|WDAT004*10538|;|WDAT004|;|WD51111|;|WDAT004-WDOC113-WD51111|
10539;1884;7039;7327;|7039-7063-7327|;|07/31/2003 12:46:33|;1;|07/31/2003 12:46:33|;NULL;|W1|;|WDAT004*10538|;|WDAT004|;|WD50910|;|WDAT004-WDOC111-WD50910|
10539;1884;7039;7303;|7039-7061-7303|;|07/31/2003 12:46:33|;1;|07/31/2003 12:46:33|;NULL;|W1|;|WDAT004*10538|;|WDAT004|;|WD50810|;|WDAT004-WDOC116-WD50810|
10539;1884;7039;7237;|7039-7057-7237|;|07/31/2003 12:46:33|;1;|07/31/2003 12:46:33|;NULL;|W1|;|WDAT004*10538|;|WDAT004|;|WD50610|;|WDAT004-WDOC109-WD50610|
10539;1884;7039;7189;|7039-7053-7189|;|07/31/2003 12:46:33|;1;|07/31/2003 12:46:33|;NULL;|W1|;|WDAT004*10538|;|WDAT004|;|WD50410|;|WDAT004-WDOC107-WD50410|
10539;1884;7039;7129;|7039-7049-7129|;|07/31/2003 12:46:33|;1;|07/31/2003 12:46:33|;NULL;|W1|;|WDAT004*10538|;|WDAT004|;|WD50207|;|WDAT004-WDOC105-WD50207|
10539;1884;7039;7109;|7039-7047-7109|;|07/31/2003 12:46:33|;1;|07/31/2003 12:46:33|;NULL;|W1|;|WDAT004*10538|;|WDAT004|;|WD50150|;|WDAT004-WDOC104-WD50150|
10539;1884;7039;7107;|7039-7045-7107|;|07/31/2003 12:46:33|;1;|07/31/2003 12:46:33|;NULL;|W1|;|WDAT004*10538|;|WDAT004|;|WD50100|;|WDAT004-WDOC102-WD50100|
10539;1884;7039;7101;|7039-7041-7101|;|07/31/2003 12:46:33|;1;|07/31/2003 12:46:33|;NULL;|W1|;|WDAT004*10538|;|WDAT004|;|WD50008|;|WDAT004-WDOC100-WD50008|

Now , bom_ato_configurations.ctl file generated from 11i enviroment is ready to migrate with R12 . After deploying our .ctl file to database server , we use this shell script on Redhat Linux to run sqlloader , you should change the directories on this script with your deployment directory :

sqlldr   apps/$AppsPWD control=./files/ctl/bom_ato_configurations.ctl

Finally , we finished Bill of Materials ATO Configurations Migration via SQL Loader process . We have a “meaningful” ATO Configuration data in our custom XXTH.XXTH_BOM_ATO_CONFIGURATIONS staging  table that we can use in Reports and API’s in R12 . Enjoy!

End to End Virtualization E-Business Suite 12.2.3 on a Windows host


What’s Our Expectations In This Process?

We will create a guest Oracle Linux virtual machine on Oracle VM VirtualBox with a Single Node Vision VM Template Appliance. And we will configure it as EBS rapid-express installation standarts for version 12.2. In this process we will also exercise basic Unix Shell Scripting skills on Oracle Linux 6 for less system administrator more “developer” “mates”. After Installation/configuration process will have a 12.2.3 version R12 EBS enviroment that helps us to examine differences between older versions of EBS on particular areas such as http/servlet services on application tier (Weblogic Server) and file system structure.Before we start this virtualization process, we need some requirements ;

  • Virtual Disk Space : 500 GB
  • Actual Disk Space Used on File System : 256 GB
  • RAM : 6 GB
  • A post modern CPU
  • An Oracle E-Delivery account
  • Totally around 18 hours (Depends on your network connection) to Finish End to End process including downloading and post-configuration.
  • Cups of coffees!

First of all, we are starting this flow by loging in the https://edelivery.oracle.com/linux side and selecting Oracle VM Templates as product pack and x86 64bit as Platform. Then we download releated files as follows ;


  • V43683-01  Oracle EBS 12.2.3 Single Node Vision Install X86 (64 bit) Linux x86-64
  • V43684-01  Oracle EBS 12.2.3 Single Node Vision Install X86 (64 bit) Linux x86-64
  • V43685-01  Oracle EBS 12.2.3 Single Node Vision Install X86 (64 bit) Linux x86-64
  • V43686-01  Oracle EBS 12.2.3 Single Node Vision Install X86 (64 bit) Linux x86-64
  • V43687-01  Oracle EBS 12.2.3 Single Node Vision Install X86 (64 bit) Linux x86-64
  • V43688-01  Oracle EBS 12.2.3 Single Node Vision Install X86 (64 bit) Linux x86-64
  • V43689-01  Oracle EBS 12.2.3 Single Node Vision Install X86 (64 bit) Linux x86-64
  • V43690-01  Oracle EBS 12.2.3 Single Node Vision Install X86 (64 bit) Linux x86-64

We need to download 16 zip files from E-delivery. Sum of these files cost 53 GB . Also it is important to verify files after download, i do this with Digest (SHA-1) for each file using DownloadManager (Mozilla). We can find SHA list on edelivery download page.


After finishing download we need to unzip all files then we need assemble all .ova files in a single .ova file . Oracle gives us a assemble script on this document 1620448.1 . But i wrote my own .bat file on windows its simple ..

ECHO “Starting Assemble…”
Copy /B Oracle-E-Business-Suite-12.2.3-VISION-INSTALL.ova.00+Oracle-E-Business-Suite-12.2.3-VISION-INSTALL.ova.01+Oracle-E-Business-Suite-12.2.3-VISION-INSTALL.ova.02+Oracle-E-Business-Suite-12.2.3-VISION-INSTALL.ova.03+Oracle-E-Business-Suite-12.2.3-VISION-INSTALL.ova.04+Oracle-E-Business-Suite-12.2.3-VISION-INSTALL.ova.05+Oracle-E-Business-Suite-12.2.3-VISION-INSTALL.ova.06+Oracle-E-Business-Suite-12.2.3-VISION-INSTALL.ova.07+Oracle-E-Business-Suite-12.2.3-VISION-INSTALL.ova.08+Oracle-E-Business-Suite-12.2.3-VISION-INSTALL.ova.09+Oracle-E-Business-Suite-12.2.3-VISION-INSTALL.ova.10+Oracle-E-Business-Suite-12.2.3-VISION-INSTALL.ova.11+Oracle-E-Business-Suite-12.2.3-VISION-INSTALL.ova.12+Oracle-E-Business-Suite-12.2.3-VISION-INSTALL.ova.13+Oracle-E-Business-Suite-12.2.3-VISION-INSTALL.ova.14 Oracle-E-Business-Suite-12.2.3-VISION-INSTALL.ova
ECHO “Assemble finished”

Then we need to import single .ova file to Oracle VM Virtual Box from file>import appliance menu;


Then we need to change network adapter to Host-Only Adapter from VM Manager, if you are using public networks like British Library, it is possible to have new problems with types like Bridged Adapter and that would costs your hours 🙂


After ending the VM appliance, we boot it. In first boot VM comes with pre-configured linux version , so we don’t need to do any changes for starting SSH protocols or any necessary services for OS. We need to enter new passwords for root in boot screen, applmgr, oracle users .After that patch 18545803 is necassary for last version of appliance scripts, this will update .sh files which is using in installment process . then when patching is finished , we run /u01/install/scripts/configdhcp.sh to configure host and domain names (default values are ebs.example.com , ebs as host ,example.com as domain , i gave ebs.lonict.com for that process. ) . Then we run /u01/install/scripts/cleanup.sh to force force configuring next boot.Finally we boot the machine with reboot command. after reboot we need to check network configurations as follows  ;


After finishing network configurations we run vision configuration scripts , these are asking you db host-domain names and SID while processing .  ;

  • /u01/install/VISION/scripts/visiondbconfig.sh script with root user , this script refines db config files for autoconfig then automatically starts db tier services.
  • /u01/install/VISION/scripts/visionappsconfig.sh script with root user , this script refine application config files for autoconfig then automatically starts all application tier services . Before running this script we should check that database services is up(TNS listener).

Then we need to run autoconfig for all db and application tier . before running autoconfig we must set enviroments (.env)  . We should check doc 387859.1 from support.oracle.com , this document includes detailed information about autoconfig process. I run both autoconfig process with oracle user. And don’t logout! After finishing both db and application autoconfig we need to check enviroment variables as oracle user ;


Now we have an EBS platform with these default passwords ;

  • weblogic/welcome1
  • root-oracle-applmgr / <user defined passwords>
  • sysadmin/sysadmin

Then we must change ~/.bashrc for both oracle and applmgr users .This initializes enviroment variables in every login for each session ;

  • For oracle user /home/oracle/.bashrc
  • For applmgr user /home/applmgr/.bashrc

After adding last two line both must look like that ;


Also we need to append our <host> .<domain> (ebs.lonict.com) with to c:windowssystem32driversetchosts file to connect our VM guest machine from Windows .Now Check ! EBS 12.2.3 Platform and Weblogic Console from these URLs 😉 ;

  • EBS :    <host> .<domain>:8000/OA_HTML/AppsLogin
  • Weblogic Console :    <host> .<domain>:7001/console/




Now we finished configuration , there are some key administration scripts that we need to check while shutting down the VM. these are under $ADMIN_SCRIPTS_HOME directory , and we must always run some of these scripts before shutdown ;


  • $ADMIN_SCRIPTS_HOME/adstpall.sh (this stops all application tier services)
  • $ADMIN_SCRIPTS_HOME/adstrtal.sh (this starts all application tier services )

Before shutting down VM we need to shutdown all db and application services as follows ;




On every boot of VM , db and application services are being started so we don’t need to start these services manually.We completed End to End Virtualization E-Business Suite 12.2.3 process .

Enjoy R12 – 12.2.3 now your VM is ready for development!!!

Refereced Oracle Documents ;

  • Doc ID 1620448.1  : General installation process for Virtual Box
  • Doc ID 387859.1    : document that includes Autoconfig details
  • Doc ID e22950-17  : Installation Guide: Using Rapid Install

What’s that holy WebLogic “thing” in Oracle E-Business Suite 12.2 ?

First version of Oracle E-Business Suite 12.2 was released about one year ago at September 2013. As a result of Oracle Sales Managers hard work, it’s planing to start implementations of this new version to clients/partners probably will be at the end of this year. In Release 12.2, Web and Forms services are provided by Oracle Application Server and Oracle Fusion Middleware. They are no longer servers in the sense of being a single process, as was the case in previous releases. There is no other spesific changes on client or database tiers.

We can figure this changes and current EBS 12.2 Architecture as follows ;


Association between Client and Application Tiers are different then other R12 versions. It seems Forms and Web Services are integrated with Fusion Middleware services  ;


When we also want to check the “new” Application Tier ,we are still seeing that there are two ORACLE_HOMEs like other older R12 versions. Oracle documents are writing that enabling this two ORACLE_HOMEs are about advantages of lasted Oracle Technologies.


In EBS 12.2 Web Service components of Oracle Application Server processes requests are mainly includes two components. These are  ;

  • Web Listener : Our old friend Oracle HTTP Listener Apache
  • Java Servlet Engine : Our new crush(!) Oracle Weblogic Server .

Web listener(Apache) basicly gives information by accepting HTTP requests from client browsers and gives to integrated Weblogic Service-WLS for security and context . And also Apache still can supply HTML content for basic requests, it only routes to Servlet if requested content is advanced level. If HTTP request(url) is including technologies like ADF and OAF or hybrid of ADF/OAF, Weblogic takes responsibilty by obtaining data from database and making the meal with the context from metadata dictionary (constructs HTML page), then sends back HTML page to our precious end user browsers with the help of Apache(Listener). This figure shows how it works ;


What kind of holy product is this Weblogic Server and what is its real occupation in these old sustainable/traditional EBS Architecture?

Yes we can answer this question in an easy simple way; Weblogic services are replaced with OC4J (Oracle Container for Java) as new Servlet Engine. All HTML-Based Applications and Oracle Application Framework (OAF) is still using Java servlets provided by Apache Jserv module and BC4J patterns (Business Components for Java) but Oracle Weblogic provides connection to database and application-specific functionality such as flexfields via WLS service. Weblogic is integrated with this tier planning to create hybrid applications using OAF-ADF and optimizing clustring performances . I think possible further requirements in the future for EBS to Fusion evolution is also key reason for Oracle’s decision on this change.

In 12.2 , OA Framework Architecture includes Weblogic services such as WLS,UIX,Java Controller, Metadata UI. And it looks like this ;


When we compare 12.2 with other R12 versions we can’t not see any changes for Forms Services . There is no change in Form Listener Servlet .They are still connecting database with Oracle Net networking infrastructure.But! Weblogic manages this processes ;


 Summary  ;

A server is an instance of WebLogic Server that runs in its own Java Virtual Machine (JVM) and has its own configuration. And there five WebLogic instances these are ;

  • Admin(Server)
  • oacore (also cluster)
  • oafm (also cluster)
  • forms (also cluster)
  • formsc4ws  (also cluster)


Referenced Oracle Documents about Weblogic thing in Oracle E-Business Suite:

  •  Part No. E12841-04
  •  Part No. E22949-09