We also help companies who need to separate their ERP data when there is an acquisition or disposal of a business unit. There are different approaches to this:

• The carve-out is done on the existing database, and the carved out data is then transferred to a new database for the new entity
• The database is duplicated the carve-out runs on one and its inverse on the other.

Defining the Data to be Carved Out

Generally, the basis for a Company Carve-out will be company number. Many JDE transaction table will contain a company number field (CO or KCO). If a table does not contain a company number, then there are many alternative ways to determine which company the record is associated with. Below are some examples of linking back to company Id from various field types:

• MCMCU (Cost centre)
  If a record contains a cost centre field (MCU) then it can be linked to the cost centre master table (F0006) which in turn contains a company number (MCCO)

• WADOCO (Work order number)
  If a record contains a work order number field (DOCO) then it can be linked to the work order master table (F4801) which in turn contains a company number (WACO). Note: This applies to work orders and not Sales or Purchase orders.

• GMAID (GL Bank A/C number)
  If a record contains a GL Bank a/c (AID) then it can be linked to the GL Account Master table (F0901) which in turn contains a company number (GMCO).

• FANUMB (Fixed Asset item number)
  If a record contains an Asset Item number (NUMB) then it can be linked to the Fixed asset master table (F1201) which in turn contains a company number (FACO).

As you can see from the above list , there are lots of ways of identifying which company a record belongs to. We can also use dependency modules to achieve the same goal. So, for instance, if we carve out all Item branch records (F4102) for company 00123 then subsequent to this we can carve out all Item Master records (F4101) where there are no F4102 records.

Which Tables Should be Carved Out?

It is up to each site to determine what tables should be targeted in a Carve-out. Generally, we would expect all the transaction tables to be targeted for each module. Alternatively, the site may wish to run a SQL statement across their database to determine the table which have field names ending in CO, KCO & MCU.

• select owner,Table_Name,Column_name, Char_Length from all_tab_columns where
• column_name like '%KCO%' and owner='JDEDATA910’ or
• column_name like '%CO' and owner='JDEDATA910’ or
• column_name like '%MCU' and owner='JDEDATA910 or
• column_name like '%AID' and owner='JDEDATA910 or
• column_name like '%NUMB' and owner='JDEDATA910



How Many Modules will be Required?

There will be at least 10 Carve-out modules which will carve-out data based on various master data. Additional modules will be required to cater for any tables that do not conform to the above. The total amount of modules will depend on how thorough the carve-out requirement is.

Learn More

For more details:

• On JD Edwards Data Carve Outs visit our dedicated page - using Datawaire software you can do the carve-out yourself or we can do this as a service. 
• On other functionality of JD Edwards Data Management provided by Datawaire.