You are on page 1of 45

Test_INV

Project Documentation

This document was generated by Designer 7.6.1


May 25, 2019

1
Table of Contents

1. Project Description.................................................................................................................................................2
2. All Parameters in Project....................................................................................................................................... 3
3. Project Business Flows and Cartridges................................................................................................................. 6
3.1. Business Flow InventoryTransArchive 7.60.1.12.115.115.................................................................................6
3.1.1. Business Flow Description..............................................................................................................................6
3.1.1.1. Business Flow Diagram............................................................................................................................... 10
3.1.1.2. Parameters used in Business Flow Actvities (and Model Compatibilities)....................................................12
3.1.1.3. Order of Parameters for Business Flow Activities.........................................................................................12
3.1.2. Business Flow Activities..................................................................................................................................12
3.1.2.1. Script Activity "PeriodCheck" Description..................................................................................................... 12
3.1.2.2. Cartridge Activity "TransactionSchedule" Description.................................................................................. 14
3.1.2.3. Cartridge Activity "TransactionAccounts" Description...................................................................................14
3.1.2.4. Cartridge Activity "TransactionLotNumbe" Description.................................................................................14
3.1.2.5. Cartridge Activity "SerialTransactionsA" Description.................................................................................... 14
3.1.2.6. Cartridge Activity "TransactionsArchive" Description....................................................................................14
3.1.2.7. Interrupt Activity: "Pause"............................................................................................................................. 14
3.1.2.8. Cartridge Activity "TransactionSchedule" Description.................................................................................. 15
3.1.2.9. Cartridge Activity "TransactionAccounts" Description...................................................................................15
3.1.2.10. Cartridge Activity "TransactionLotNumbe" Description...............................................................................15
3.1.2.11. Cartridge Activity "SerialTransactionsA" Description.................................................................................. 15
3.1.2.12. Cartridge Activity "TransactionsArchive" Description..................................................................................15
3.2. Business Flow InventoryTransReload 7.60.1.12.115.115................................................................................. 15
3.2.1. Business Flow Description..............................................................................................................................16
3.2.1.1. Business Flow Diagram............................................................................................................................... 16
3.2.1.2. Parameters used in Business Flow Actvities (and Model Compatibilities)....................................................17
3.2.1.3. Order of Parameters for Business Flow Activities.........................................................................................17
3.2.2. Business Flow Activities..................................................................................................................................17
3.2.2.1. Cartridge Activity "TransactionSchedulesReload" Description..................................................................... 18
3.2.2.2. Cartridge Activity "TransactionAccountsReload" Description....................................................................... 18
3.2.2.3. Cartridge Activity "TransactionLotNumbersReload" Description.................................................................. 18
3.2.2.4. Cartridge Activity "SerialTransactionsReload" Description........................................................................... 18
3.2.2.5. Cartridge Activity "TransactionsReload" Description.................................................................................... 18
3.3. Undo Business Flow InventoryTransUndo 7.60.1.12.115.115............................................................................18
3.3.1. Undo Business Flow Description..................................................................................................................... 18
3.3.1.1. Undo Business Flow Diagram.......................................................................................................................19
3.3.2. Undo Business Flow Activities......................................................................................................................... 20
3.3.2.1. Cartridge Activity "TransactionsArchive" Description....................................................................................20
3.3.2.2. Cartridge Activity "SerialTransactionsA" Description.................................................................................... 20
3.3.2.3. Cartridge Activity "TransactionLotNumbe" Description.................................................................................21
3.3.2.4. Cartridge Activity "TransactionAccounts" Description...................................................................................21
3.3.2.5. Cartridge Activity "TransactionSchedule" Description.................................................................................. 21
3.4. Database to Database Cartridge SerialTransactionsArchive 7.60.1.12.115.115................................................21
3.4.1. Cartridge SerialTransactionsArchive............................................................................................................... 21
3.4.1.1. Cartridge operations..................................................................................................................................... 21
3.4.1.2. Cartridge-specific data movement key warnings.......................................................................................... 21
3.4.1.3. Parameters used in the Source Model and Cartridge...................................................................................22
3.4.1.4. Rules in Cartridge......................................................................................................................................... 22
3.5. Database to Database Cartridge SerialTransactionsReload 7.60.1.12.115.115................................................ 22
3.5.1. Cartridge SerialTransactionsReload................................................................................................................ 22
3.5.1.1. Cartridge operations..................................................................................................................................... 22
3.5.1.2. Cartridge-specific data movement key warnings.......................................................................................... 22
3.5.1.3. Data Sources................................................................................................................................................ 22
3.5.1.4. Parameters used in the Source Model and Cartridge...................................................................................23
3.5.1.5. Rules in Cartridge......................................................................................................................................... 23
3.6. Database to Database Cartridge TransactionAccountsArchive 7.60.1.12.115.115............................................23
3.6.1. Cartridge TransactionAccountsArchive............................................................................................................23
3.6.1.1. Cartridge operations..................................................................................................................................... 23
3.6.1.2. Cartridge-specific data movement key warnings.......................................................................................... 23
3.6.1.3. Parameters used in the Source Model and Cartridge...................................................................................23
3.6.1.4. Rules in Cartridge......................................................................................................................................... 23
3.7. Database to Database Cartridge TransactionAccountsReload 7.60.1.12.115.115............................................ 24
3.7.1. Cartridge TransactionAccountsReload............................................................................................................ 24
3.7.1.1. Cartridge operations..................................................................................................................................... 24
3.7.1.2. Cartridge-specific data movement key warnings.......................................................................................... 24
3.7.1.3. Data Sources................................................................................................................................................ 24
3.7.1.4. Parameters used in the Source Model and Cartridge...................................................................................24
3.7.1.5. Rules in Cartridge......................................................................................................................................... 24
3.8. Database to Database Cartridge TransactionLotNumbersArchive 7.60.1.12.115.115....................................... 25
3.8.1. Cartridge TransactionLotNumbersArchive.......................................................................................................25
3.8.1.1. Cartridge operations..................................................................................................................................... 25
3.8.1.2. Cartridge-specific data movement key warnings.......................................................................................... 25
3.8.1.3. Parameters used in the Source Model and Cartridge...................................................................................25
3.8.1.4. Rules in Cartridge......................................................................................................................................... 25
3.9. Database to Database Cartridge TransactionLotNumbersReload 7.60.1.12.115.115........................................25
3.9.1. Cartridge TransactionLotNumbersReload....................................................................................................... 26
3.9.1.1. Cartridge operations..................................................................................................................................... 26
3.9.1.2. Cartridge-specific data movement key warnings.......................................................................................... 26
3.9.1.3. Data Sources................................................................................................................................................ 26
3.9.1.4. Parameters used in the Source Model and Cartridge...................................................................................26
3.9.1.5. Rules in Cartridge......................................................................................................................................... 26
3.10. Database to Database Cartridge TransactionSchedulesArchive 7.60.1.12.115.115........................................26
3.10.1. Cartridge TransactionSchedulesArchive........................................................................................................27
3.10.1.1. Cartridge operations................................................................................................................................... 27
3.10.1.2. Cartridge-specific data movement key warnings........................................................................................ 27
3.10.1.3. Parameters used in the Source Model and Cartridge.................................................................................27
3.10.1.4. Rules in Cartridge....................................................................................................................................... 27
3.11. Database to Database Cartridge TransactionSchedulesReload 7.60.1.12.115.115........................................ 27
3.11.1. Cartridge TransactionSchedulesReload........................................................................................................ 27
3.11.1.1. Cartridge operations................................................................................................................................... 28
3.11.1.2. Cartridge-specific data movement key warnings........................................................................................ 28
3.11.1.3. Data Sources.............................................................................................................................................. 28
3.11.1.4. Parameters used in the Source Model and Cartridge.................................................................................28
3.11.1.5. Rules in Cartridge....................................................................................................................................... 28
3.12. Database to Database Cartridge TransactionsArchive 7.60.1.12.115.115.......................................................28
3.12.1. Cartridge TransactionsArchive.......................................................................................................................28
3.12.1.1. Cartridge operations................................................................................................................................... 29
3.12.1.2. Cartridge-specific data movement key warnings........................................................................................ 29
3.12.1.3. Parameters used in the Source Model and Cartridge.................................................................................29
3.12.1.4. Rules in Cartridge....................................................................................................................................... 29
3.13. Database to Database Cartridge TransactionsReload 7.60.1.12.115.115....................................................... 29
3.13.1. Cartridge TransactionsReload....................................................................................................................... 29
3.13.1.1. Cartridge operations................................................................................................................................... 30
3.13.1.2. Cartridge-specific data movement key warnings........................................................................................ 30
3.13.1.3. Data Sources.............................................................................................................................................. 30
3.13.1.4. Parameters used in the Source Model and Cartridge.................................................................................30
3.13.1.5. Rules in Cartridge....................................................................................................................................... 30
4. Source Models....................................................................................................................................................... 32
4.1. Source Model SerialTransactions...................................................................................................................... 32
4.1.1. ER Diagram..................................................................................................................................................... 32
4.1.2. Table use List...................................................................................................................................................32
4.1.2.1. Table use MTL_UNIT_TRANSACTIONS..................................................................................................... 32
4.2. Source Model TransactionAccounts.................................................................................................................. 33
4.2.1. ER Diagram..................................................................................................................................................... 33
4.2.2. Table use List...................................................................................................................................................34
4.2.2.1. Table use MTL_TRANSACTION_ACCOUNTS............................................................................................ 34
4.3. Source Model TransactionLotNumbers............................................................................................................. 35
4.3.1. ER Diagram..................................................................................................................................................... 35
4.3.2. Table use List...................................................................................................................................................35
4.3.2.1. Table use MTL_TRANSACTION_LOT_NUMBERS..................................................................................... 35
4.4. Source Model TransactionSchedules................................................................................................................ 36
4.4.1. ER Diagram..................................................................................................................................................... 37
4.4.2. Table use List...................................................................................................................................................37
4.4.2.1. Table use MTL_MATERIAL_TXN_ALLOCATIONS......................................................................................37
4.5. Source Model Transactions............................................................................................................................... 38
4.5.1. ER Diagram..................................................................................................................................................... 38
4.5.2. Table use List...................................................................................................................................................39
4.5.2.1. Table use MTL_MATERIAL_TRANSACTIONS............................................................................................39
4.5.2.2. Table use WIP_SCRAP_VALUES................................................................................................................40
4.5.2.3. Table use MTL_CST_ACTUAL_COST_DETAILS........................................................................................41
4.5.2.4. Table use MTL_CST_TXN_COST_DETAILS...............................................................................................41
4.5.2.5. Table use MTL_ACTUAL_COST_SUBELEMENT....................................................................................... 42
1. Project Description
Project Info
Annotation

2
2. All Parameters in Project
Parameter: pcMonthsToRetain
Label Inventory: Number of Months to Retain
UID DFC9-BE20-D47B-FFC0
Parameter Type Configuration
Data Type NUMBER
Length 9
Default 6
Validation Mandatory
List of Values <None>
Parameter Annotation This configuration parameter is used by the user to give the retention
period in months.This is taken in to account
for validating the purgable Update Parameter value.

Parameter: pcPauseAfterSelectionINVTRX
Label InventoryTrans:Pause after the Selection Step?
UID 2E71-5792-4136-0DCF
Parameter Type Configuration
Data Type STRING
Length 30
Default No
Validation Mandatory
Static List of Values Id Label
Yes Yes
No No
Parameter Annotation This parameter will facilitate the PAUSE between the selection and
archive/cleanup subjobs
during an archive job.

Parameter: prCutoffDate
Label Archive CutOff Date(YYYY.MM.DD)
UID E3E9-F873-2909-8BCE
Parameter Type Runtime
Data Type DATE
Length
Default
Validation Mandatory
List of Values <None>
Parameter Annotation This is the parameter for the archive cut-off date.The inventory
transactions created before the cut
-off date will be archived during archive job.This is mandatory parameter
for the archive job.

Parameter: prOrganization
Label Archive Organization Name
UID EA4A-50E4-9962-BA06
Parameter Type Runtime
Data Type STRING
Length 30

3
Parameter: prOrganization
Default
Validation <None>
Dynamic List Definition
Query Expression
DB Connection Annotation
Connection Query
Source This list provides all ansi SELECT mp.ORGANIZATION_ID,
the Inventory upper(haotl.name) organization_name
Organizations FROM
defined in the ${SOURCE.INV.MTL_PARAMETERS} mp
application. ,
${SOURCE.HR.HR_ALL_ORGANIZATION
_UNITS_TL} haotl
WHERE mp.organization_id =
haotl.organization_id
AND haotl.language = USERENV('lang')
order by upper(haotl.name)

Parameter Annotation Organization is one of the parameter user selects while running the
archive.
Only inventory transactions created in this organizations would be eligible
for archiving.
User will select the organization from the LOV attached to the parameters.

Parameter: prReloadFromTransaction
Label Low Transaction Number to Reload
UID 14B1-8EA3-34B7-748C
Parameter Type Runtime
Data Type NUMBER
Length 9
Default
Validation Mandatory
Dynamic List Definition
Query Expression
DB Connection Annotation
Connection Query
History This sql query ansi select mmt.transaction_id td1,
provides with all the mmt.transaction_id td2 from
transaction id values ${HIST.INV.MTL_MATERIAL_TRANSACTI
stored in the history ONS} mmt
database. where mmt.transaction_id like
'%'||:FilterPattern||'%'
order by td1

Parameter Annotation Low Transaction Number to Reload.This is mandatory parameter.

Parameter: prReloadToTransaction
Label High Transaction Number to Reload
UID 14B1-8E99-80E3-0B70
Parameter Type Runtime
Data Type NUMBER
Length 9
Default
Validation <None>

4
Parameter: prReloadToTransaction
Dynamic List Definition
Query Expression
DB Connection Annotation
Connection Query
History This sql query ansi select mmt.transaction_id td1,
provides with all the mmt.transaction_id td2 from
transaction id values ${HIST.INV.MTL_MATERIAL_TRANSACTI
stored in the history ONS} mmt
database. where mmt.transaction_id like
'%'||:FilterPattern||'%'
order by td1

Parameter Annotation High Transaction Number to Reload.This is optional paramete.If this


parameter
is not selected, then only one transaction number (low transaction number
)
will be purged.

5
3. Project Business Flows and Cartridges
3.1. Business Flow InventoryTransArchive 7.60.1.12.115.115
3.1.1. Business Flow Description

Business Flow Info


Version 7.60.1.12.115.115
UID D65B-73B7-566D-F67C
Annotation Business flow of Inventory transactions module for Oracle Apps Version: 11.5.10.2
This business flow is used to archive inventory transactions information for a particular
organization.The organization for which transactions are archived is passed by user
as a parameter at runtime.User also passes the cutoff date.The cutoff date should be
in the closed inventory period.All transactions which are created for the organization
(passed as parameter)
before the cutoff date ,gets archived through this business flow.If the cutoff date lies in
an open inventory period, businness flow will be errored out without archiving any data.
This business flow executes the following Cartidges:
1. TxnSchedulesArchive
2. TxnAccountsArchive
3. TxnLotNumberArchive
4. SerialTxnArchive
5. TransactionsArchive

6
Business Flow Info
Install script import com.outerbay.api.*;
import groovy.sql.*
import groovy.lang.GroovyClassLoader;
/* utils = new oebsUtils();*/
def utils;
l_inv_owner = "INV";
try
{
def gcl = new GroovyClassLoader()
Class sst = gcl.parseClass(new File("${PRODUCT_HOME}/lib/oebsUtils.groovy")) ;
utils = sst.newInstance();
}

catch(FileNotFoundException cex)
{
println "Please Deploy EBSIntegrationCreateArchiveAccess Businessflow before
module deployment.";
throw new IllegalStateException("Please Deploy EBSIntegrationCreateArchiveAccess
Businessflow before module deployment.");
}
catch(Exception ex)
{
println "Exception while loading oebsUtils class"+ex;
throw new IllegalStateException("Exception while loading oebsUtils class"+ex);
}

if(!utils.checkInstall(INTF_DB,'OEBS_INTG2',null))
throw new IllegalStateException("Please Deploy EBSIntegrationCreateArchiveAccess
Businessflow before module deployment.")

ConfigurationProperties.createSession(" ", ENVIRONMENT_NAME);

ArchiveAccessConfiguration.createSession(" ",ENVIRONMENT_NAME);

def packageOwner = ConfigurationProperties.getProductConfigValue("BusinessFlow",


"pcEBSPackageOwner");

if (utils.objectExists(INTF_DB,packageOwner,"VIEW","CST_INV_DISTRIBUTION_V"))
{
ArchiveAccessConfiguration.addTextReplacer("",packageOwner,"CST_INV_DISTRIBUTI
ON_V","VIEW",1,"(?i)SELECT MMT.","SELECT /*+
use_nl(MTL_MATERIAL_TRANSACTIONS,MTL_TRANSACTION_ACCOUNTS,mtt,mtst
,mtr,br,bd,ca,lu2,lu1) */ MMT.",true,true);
}

// R12.1 related code - Start

try {

if (utils.objectExists(INTF_DB,packageOwner, "PACKAGE
BODY","FTP_IRC_ADI_MIGRATE"))
{
objName = "FTP_IRC_ADI_MIGRATE";
objType = "PACKAGE";
cascadeExclusion = false;
transparencyLayer = null;
utils.addObjAsSynonymAndExclusion(INTF_DB,
packageOwner,
objName,
objType,
cascadeExclusion,
transparencyLayer
);
println("Added object exclusion for FTP_IRC_ADI_MIGRATE");
}

if (utils.objectExists(INTF_DB,packageOwner, "PACKAGE

7
Business Flow Info
BODY","IGF_AW_GEN_004"))
{
objName = "IGF_AW_GEN_004";
objType = "PACKAGE";
cascadeExclusion = false;
transparencyLayer = null;
utils.addObjAsSynonymAndExclusion(INTF_DB,
packageOwner,
objName,
objType,
cascadeExclusion,
transparencyLayer
);
}
if (utils.objectExists(INTF_DB,packageOwner, "PACKAGE
BODY","OE_MASS_CHANGE_PVT"))
{

objName = "OE_MASS_CHANGE_PVT";
objType = "PACKAGE";
cascadeExclusion = false;
transparencyLayer = null;
utils.addObjAsSynonymAndExclusion(INTF_DB,
packageOwner,
objName,
objType,
cascadeExclusion,
transparencyLayer
);
println("Added object exclusion for OE_MASS_CHANGE_PVT");
}

if (utils.objectExists(INTF_DB,packageOwner, "PACKAGE
BODY","AZ_R12_TRANSFORM_CASCADE"))
{

objName = "AZ_R12_TRANSFORM_CASCADE";
objType = "PACKAGE";
cascadeExclusion = false;
transparencyLayer = null;
utils.addObjAsSynonymAndExclusion(INTF_DB,
packageOwner,
objName,
objType,
cascadeExclusion,
transparencyLayer
);
}

if (utils.objectExists(INTF_DB,packageOwner, "PACKAGE
BODY","WMS_PICKING_PKG"))
{

objName = "WMS_PICKING_PKG";
objType = "PACKAGE";
cascadeExclusion = false;
transparencyLayer = null;
utils.addObjAsSynonymAndExclusion(INTF_DB,
packageOwner,
objName,
objType,
cascadeExclusion,
transparencyLayer
);
}

if (utils.objectExists(INTF_DB,packageOwner, "PACKAGE
BODY","PAY_PAYMENT_XML_PKG"))
{

objName = "PAY_PAYMENT_XML_PKG";

8
Business Flow Info
objType = "PACKAGE";
cascadeExclusion = false;
transparencyLayer = null;
utils.addObjAsSynonymAndExclusion(INTF_DB,
packageOwner,
objName,
objType,
cascadeExclusion,
transparencyLayer
);
println("Added object exclusion for PAY_PAYMENT_XML_PKG");
}
}
catch (Exception e)
{
println("Exception occured while calling addObjAsSynonymAndExclusion groovy
function for " + objType + " - " + objName);
e.printStackTrace();
throw new IllegalStateException(println(e.getMessage()));
}

// R12.1 related code - END

ArchiveAccessConfiguration.commit();
ArchiveAccessConfiguration.closeSession();
ConfigurationProperties.closeSession();

LiveArchiveJobManager.createSession(" ",ENVIRONMENT_NAME);
LiveArchiveJobManager.addExcludedIndex(ENVIRONMENT_NAME, NULL,
l_inv_owner, "MTL_MATERIAL_TRANSACTIONS", NULL, l_inv_owner,
"MTL_MATERIAL_TRANSACTIONS_N3");
LiveArchiveJobManager.addExcludedIndex(ENVIRONMENT_NAME, NULL,
l_inv_owner, "MTL_MATERIAL_TRANSACTIONS", NULL, l_inv_owner,
"MTL_MATERIAL_TRANSACTIONS_N10");
LiveArchiveJobManager.addExcludedIndex(ENVIRONMENT_NAME, NULL,
l_inv_owner, "MTL_MATERIAL_TRANSACTIONS", NULL, l_inv_owner,
"MTL_MATERIAL_TRANSACTIONS_N13");
if
(utils.objectExists(INTF_DB,l_inv_owner,"INDEX","MTL_MATERIAL_TRANSACTIONS_
N21"))
{
LiveArchiveJobManager.addExcludedIndex(ENVIRONMENT_NAME, NULL,
l_inv_owner, "MTL_MATERIAL_TRANSACTIONS", NULL, l_inv_owner,
"MTL_MATERIAL_TRANSACTIONS_N21");
}

if
(utils.objectExists(INTF_DB,l_inv_owner,"INDEX","MTL_MATERIAL_TRANSACTIONS_
N22"))
{
LiveArchiveJobManager.addExcludedIndex(ENVIRONMENT_NAME, NULL,
l_inv_owner, "MTL_MATERIAL_TRANSACTIONS", NULL, l_inv_owner,
"MTL_MATERIAL_TRANSACTIONS_N22");
}

if
(utils.objectExists(INTF_DB,l_inv_owner,"INDEX","MTL_MATERIAL_TRANSACTIONS_
N23"))
{
LiveArchiveJobManager.addExcludedIndex(ENVIRONMENT_NAME, NULL,
l_inv_owner, "MTL_MATERIAL_TRANSACTIONS", NULL, l_inv_owner,
"MTL_MATERIAL_TRANSACTIONS_N23");
}

if
(utils.objectExists(INTF_DB,l_inv_owner,"INDEX","MTL_MATERIAL_TRANSACTIONS_
N24"))
{
LiveArchiveJobManager.addExcludedIndex(ENVIRONMENT_NAME, NULL,
l_inv_owner, "MTL_MATERIAL_TRANSACTIONS", NULL, l_inv_owner,

9
Business Flow Info
"MTL_MATERIAL_TRANSACTIONS_N24");
}

if
(utils.objectExists(INTF_DB,l_inv_owner,"INDEX","MTL_MATERIAL_TRANSACTIONS_
N25"))
{
LiveArchiveJobManager.addExcludedIndex(ENVIRONMENT_NAME, NULL,
l_inv_owner, "MTL_MATERIAL_TRANSACTIONS", NULL, l_inv_owner,
"MTL_MATERIAL_TRANSACTIONS_N25");
}

utils.updateInstallStatus(INTF_DB,"INV","Inventory Transactions","1.0.0");
Install annotation Integration Layer has to be installed before installing any other business flow.
This Script checks if the Integration Layer has been instanlled or not before
installing the archive business flow.If it has not been installed, This check will
fail the installation of the archive business flow.

3.1.1.1. Business Flow Diagram

10
11
3.1.1.2. Parameters used in Business Flow Actvities (and Model Compatibilities)

Parameters used
pcMonthsToRetain,
pcPauseAfterSelectionINVTRX,
prCutoffDate,
prOrganization

3.1.1.3. Order of Parameters for Business Flow Activities

Parameter Order
prOrganization,
prCutoffDate,
pcPauseAfterSelectionINVTRX,
pcMonthsToRetain

3.1.2. Business Flow Activities


3.1.2.1. Script Activity "PeriodCheck" Description

12
Code
import groovy.time.*
import groovy.SQL.*
import groovy.sql.*
import groovy.runtime.TimeCategory.*
import java.text.SimpleDateFormat;
import java.lang.Float

oltpSchema3 = "GL"
oltpSchema4 = "APPS"

def format = new SimpleDateFormat( "MM/dd/yyyy" )

p_prCutoffDate = format.format(prCutoffDate)

params = [p_prCutoffDate,p_prCutoffDate]

sql = """SELECT * FROM inv.org_acct_periods WHERE organization_id =


to_number(nvl(${prOrganization},organization_id))
AND period_start_date <= to_date(?,'MM/DD/YYYY') AND schedule_close_date >= to_date(?,'MM/DD/YYYY')
AND open_flag = 'N'""";

if (!INTF_DB.firstRow(sql,params)){
throw new IllegalStateException("cutoff_date does not fall between a closed period.")
}

String Qry1 = """


SELECT organization_id FROM inv.org_acct_periods
WHERE organization_id = to_number(nvl(${prOrganization},organization_id))
AND period_start_date <= to_date(?,'MM/DD/YYYY')
AND schedule_close_date >= to_date(?,'MM/DD/YYYY')
AND open_flag = 'N'
""";

params13 = [p_prCutoffDate,p_prCutoffDate]

INTF_DB.eachRow(Qry1,params13) { row1 ->


l_organization_id = row1.organization_id

if(pcMonthsToRetain > 0)
{
String query3 = """
select count(*) \"COL3\"
from ${oltpSchema4}.gl_periods
where start_date > to_date(?,'MM/DD/YYYY')
and end_date < trunc(sysdate)
and adjustment_period_flag = 'N'
and (period_set_name, period_type) =
(select sob.period_set_name,
sob.accounted_period_type
from ${oltpSchema4}.org_organization_definitions ood,
${oltpSchema4}.gl_sets_of_books sob
where ood.set_of_books_id = sob.set_of_books_id
and ood.organization_id = nvl(?,ood.organization_id))
"""

params3 = [p_prCutoffDate,l_organization_id]

INTF_DB.eachRow(query3, params3) {row ->


l_retention_prd_count = row.COL3
}

println("pcMonthsToRetain " + pcMonthsToRetain + " l_organization_id "+l_organization_id+"


l_retention_prd_count "+l_retention_prd_count);

if (l_retention_prd_count < pcMonthsToRetain)


{
throw new Exception("Purge Date must be at least " + pcMonthsToRetain + " full fiscal periods old for
organization "+l_organization_id+". But it is right now : "+l_retention_prd_count)

13
Code
}
}
}
Annotation
User is supposed to pass the cutoff date as parameter to the achive job in the closed
inventory period.
This groovy check if the cutoff date falls in the closed period. If it does not fall in
the closed period , it aborts the job and gives the message
"cutoff_date does not fall between a closed period."

3.1.2.2. Cartridge Activity "TransactionSchedule" Description

Cartridge Activity Info


Subjobs Selection
Cartridge reference Cartridge "TransactionSchedulesArchive" definition

3.1.2.3. Cartridge Activity "TransactionAccounts" Description

Cartridge Activity Info


Subjobs Selection
Cartridge reference Cartridge "TransactionAccountsArchive" definition

3.1.2.4. Cartridge Activity "TransactionLotNumbe" Description

Cartridge Activity Info


Subjobs Selection
Cartridge reference Cartridge "TransactionLotNumbersArchive" definition

3.1.2.5. Cartridge Activity "SerialTransactionsA" Description

Cartridge Activity Info


Subjobs Selection
Cartridge reference Cartridge "SerialTransactionsArchive" definition

3.1.2.6. Cartridge Activity "TransactionsArchive" Description

Cartridge Activity Info


Subjobs Selection
Cartridge reference Cartridge "TransactionsArchive" definition

3.1.2.7. Interrupt Activity: "Pause"

Interrupt Activity
Type Pause
Message Job Paused

14
Interrupt Activity
Condition
pcPauseAfterSelectionINVTRX == 'Yes'

Annotation
The Pause is inserted in case the user wants to run the Selection and Archive job as two
different steps.

3.1.2.8. Cartridge Activity "TransactionSchedule" Description

Cartridge Activity Info


Subjobs Archive,
Clean Up
Cartridge reference Cartridge "TransactionSchedulesArchive" definition

3.1.2.9. Cartridge Activity "TransactionAccounts" Description

Cartridge Activity Info


Subjobs Archive,
Clean Up
Cartridge reference Cartridge "TransactionAccountsArchive" definition

3.1.2.10. Cartridge Activity "TransactionLotNumbe" Description

Cartridge Activity Info


Subjobs Archive,
Clean Up
Cartridge reference Cartridge "TransactionLotNumbersArchive" definition

3.1.2.11. Cartridge Activity "SerialTransactionsA" Description

Cartridge Activity Info


Subjobs Archive,
Clean Up
Cartridge reference Cartridge "SerialTransactionsArchive" definition

3.1.2.12. Cartridge Activity "TransactionsArchive" Description

Cartridge Activity Info


Subjobs Archive,
Clean Up
Cartridge reference Cartridge "TransactionsArchive" definition

15
3.2. Business Flow InventoryTransReload 7.60.1.12.115.115
3.2.1. Business Flow Description

Business Flow Info


Version 7.60.1.12.115.115
UID 295B-4487-6FA9-5D91
Annotation Business flow of inventory transactions module for Oracle Apps Version: 11.5.10.2
This business flow is used to reload inventory transactions information for a particular
organization.The organization for which transactions arere-loaded is passed by user
as a parameter at runtime.User also passes the cutoff date.
All transactions which are archived for the organization (passed as parameter)
and are created before the cutoff date ,gets re-loaded through this business flow.
This business flow runs the following cartridges:
1. TxnSchedulesArchive
2. TxnAccountsArchive
3. TxnLotNumberArchive
4. SerialTxnArchive
5. TransactionsArchive
Install script import com.outerbay.api.*;
import groovy.sql.*
import groovy.lang.GroovyClassLoader;

def utils;
try
{
def gcl = new GroovyClassLoader()
Class sst = gcl.parseClass(new File("${PRODUCT_HOME}/lib/oebsUtils.groovy")) ;
utils = sst.newInstance();
}

catch(FileNotFoundException cex)
{
println "Please Deploy EBSIntegrationCreateArchiveAccess Businessflow before
module deployment.";
throw new IllegalStateException("Please Deploy EBSIntegrationCreateArchiveAccess
Businessflow before module deployment");
}
catch(Exception ex)
{
println "Exception while loading oebsUtils class"+ex;
throw new IllegalStateException("Exception while loading oebsUtils class"+ex);
}

if(!utils.checkInstall(INTF_DB,'OEBS_INTG2',null))
throw new IllegalStateException("Please Deploy EBSIntegrationCreateArchiveAccess
Businessflow before module deployment.")
Install annotation Integration Layer has to be installed before installing any other business flow.
This Script checks if the Integration Layer has been instanlled or not before
installing the reload business flow.If it has not been installed, This check will
fail the installation of the reload business flow.

3.2.1.1. Business Flow Diagram

16
3.2.1.2. Parameters used in Business Flow Actvities (and Model Compatibilities)

Parameters used
prReloadFromTransaction,
prReloadToTransaction

3.2.1.3. Order of Parameters for Business Flow Activities

Parameter Order
prReloadFromTransaction,
prReloadToTransaction

3.2.2. Business Flow Activities

17
3.2.2.1. Cartridge Activity "TransactionSchedulesReload" Description

Cartridge Activity Info


Subjobs <All SubJobs>
Cartridge reference Cartridge "TransactionSchedulesReload" definition

3.2.2.2. Cartridge Activity "TransactionAccountsReload" Description

Cartridge Activity Info


Subjobs <All SubJobs>
Cartridge reference Cartridge "TransactionAccountsReload" definition

3.2.2.3. Cartridge Activity "TransactionLotNumbersReload" Description

Cartridge Activity Info


Subjobs <All SubJobs>
Cartridge reference Cartridge "TransactionLotNumbersReload" definition

3.2.2.4. Cartridge Activity "SerialTransactionsReload" Description

Cartridge Activity Info


Subjobs <All SubJobs>
Cartridge reference Cartridge "SerialTransactionsReload" definition

3.2.2.5. Cartridge Activity "TransactionsReload" Description

Cartridge Activity Info


Subjobs <All SubJobs>
Cartridge reference Cartridge "TransactionsReload" definition

3.3. Undo Business Flow InventoryTransUndo 7.60.1.12.115.115


3.3.1. Undo Business Flow Description

Undo Business Flow Info


Version 7.60.1.12.115.115
Base Business Flow InventoryTransArchive
UID B191-C531-9581-8BA3
Annotation This business flow reloads the data archived by a particular run of the archive
business flow.

18
Undo Business Flow Info
Install script import com.outerbay.api.*;
import groovy.sql.*
import groovy.lang.GroovyClassLoader;

def utils;
try
{
def gcl = new GroovyClassLoader()
Class sst = gcl.parseClass(new File("${PRODUCT_HOME}/lib/oebsUtils.groovy")) ;
utils = sst.newInstance();
}

catch(FileNotFoundException cex)
{
println "Please Deploy EBSIntegrationCreateArchiveAccess Businessflow before
module deployment.";
throw new IllegalStateException("Please Deploy EBSIntegrationCreateArchiveAccess
Businessflow before module deployment");
}
catch(Exception ex)
{
println "Exception while loading oebsUtils class"+ex;
throw new IllegalStateException("Exception while loading oebsUtils class"+ex);
}

if(!utils.checkInstall(INTF_DB,'OEBS_INTG2',null))
throw new IllegalStateException("Please Deploy EBSIntegrationCreateArchiveAccess
Businessflow before module deployment.")
Install annotation Integration Layer has to be installed before installing any other business flow.
This Script checks if the Integration Layer has been instanlled or not before
installing the undo business flow.If it has not been installed, This check will
fail the installation of the undo business flow.

3.3.1.1. Undo Business Flow Diagram

19
3.3.2. Undo Business Flow Activities
3.3.2.1. Cartridge Activity "TransactionsArchive" Description

Cartridge Activity Info


Subjobs <All SubJobs>
Cartridge reference Cartridge "TransactionsArchive" definition

3.3.2.2. Cartridge Activity "SerialTransactionsA" Description

Cartridge Activity Info


Subjobs <All SubJobs>
Cartridge reference Cartridge "SerialTransactionsArchive" definition

20
3.3.2.3. Cartridge Activity "TransactionLotNumbe" Description

Cartridge Activity Info


Subjobs <All SubJobs>
Cartridge reference Cartridge "TransactionLotNumbersArchive" definition

3.3.2.4. Cartridge Activity "TransactionAccounts" Description

Cartridge Activity Info


Subjobs <All SubJobs>
Cartridge reference Cartridge "TransactionAccountsArchive" definition

3.3.2.5. Cartridge Activity "TransactionSchedule" Description

Cartridge Activity Info


Subjobs <All SubJobs>
Cartridge reference Cartridge "TransactionSchedulesArchive" definition

3.4. Database to Database Cartridge SerialTransactionsArchive


7.60.1.12.115.115
3.4.1. Cartridge SerialTransactionsArchive

Cartridge Info
Source Model SerialTransactions
reference
Version 7.60.1.12.115.115
UID 34DE-0269-0AFE-73BB
Annotation This cartridge uses model SerialTxns(INV.MTL_UNIT_TRANSACTIONS).
This cartridge archives the material transactions of serialized unit in inventory.
The transactions which is archived, are of a specified organization and created before
the
cut-off date.Organization and cut-off date are passed by the user as parameters.

3.4.1.1. Cartridge operations

Table use name Copy Purge Annotation


MTL_UNIT_TRANSACTIONS Yes Yes

3.4.1.2. Cartridge-specific data movement key warnings

Data movement key warnings


Reload could result in duplicate rows. This is because some tables in the cartridge do not have a unique key
set or auto-chosen as the data movement key.

21
3.4.1.3. Parameters used in the Source Model and Cartridge

Parameters used
prCutoffDate,
prOrganization

3.4.1.4. Rules in Cartridge

Included Rules Excluded Rules


OrganizationParam ReloadTransactions
CutoffDateParam

3.5. Database to Database Cartridge SerialTransactionsReload


7.60.1.12.115.115
3.5.1. Cartridge SerialTransactionsReload

Cartridge Info
Source Model SerialTransactions
reference
Version 7.60.1.12.115.115
UID D498-0BF8-F307-CCF5
Annotation This cartridge uses model SerialTxns(INV.MTL_UNIT_TRANSACTIONS).This cartridge
is used for re-load purpose.
This cartridge re-loads the material transactions of serialized unit in inventory.
The transactions which are re-loaded are of a specified organization and created before
the
cut-off date.Organization and cut-off date are passed by the user as parameters.

3.5.1.1. Cartridge operations

Table use name Copy Purge Annotation


MTL_UNIT_TRANSACTIONS Yes Yes

3.5.1.2. Cartridge-specific data movement key warnings

Data movement key warnings


Reload could result in duplicate rows. This is because some tables in the cartridge do not have a unique key
set or auto-chosen as the data movement key.

3.5.1.3. Data Sources

Table use name Data Source Annotation


MTL_UNIT_TRANSACTIONS History

22
3.5.1.4. Parameters used in the Source Model and Cartridge

Parameters used
prReloadFromTransaction,
prReloadToTransaction

3.5.1.5. Rules in Cartridge

Included Rules Excluded Rules


ReloadTransactions OrganizationParam
CutoffDateParam

3.6. Database to Database Cartridge TransactionAccountsArchive


7.60.1.12.115.115
3.6.1. Cartridge TransactionAccountsArchive

Cartridge Info
Source Model TransactionAccounts
reference
Version 7.60.1.12.115.115
UID 222E-0F16-5407-E863
Annotation This cartridge uses model TxnAccounts(INV.MTL_TRANSACTION_ACCOUNTS).
This cartridge archives the accounting information for the material transaction
of an organization ,which falls before the cut-off date.Organization and cut-off date
are passed by the user as parameters.

3.6.1.1. Cartridge operations

Table use name Copy Purge Annotation


MTL_TRANSACTION_ACCOUNTS Yes Yes

3.6.1.2. Cartridge-specific data movement key warnings

Data movement key warnings


Reload could result in duplicate rows. This is because some tables in the cartridge do not have a unique key
set or auto-chosen as the data movement key.

3.6.1.3. Parameters used in the Source Model and Cartridge

Parameters used
prCutoffDate,
prOrganization

3.6.1.4. Rules in Cartridge

23
Included Rules Excluded Rules
OrganizationParam ReloadTransactions
CutoffDateParam

3.7. Database to Database Cartridge TransactionAccountsReload


7.60.1.12.115.115
3.7.1. Cartridge TransactionAccountsReload

Cartridge Info
Source Model TransactionAccounts
reference
Version 7.60.1.12.115.115
UID C1E8-18A6-3C11-419D
Annotation This cartridge uses model TxnAccounts(INV.MTL_TRANSACTION_ACCOUNTS).
This cartridge is used for re-load purpose.
This cartridge re-loads the accounting information for the material transaction
of an organization ,which falls before the cut-off date.Organization and cut-off date
are passed by the user as parameters.

3.7.1.1. Cartridge operations

Table use name Copy Purge Annotation


MTL_TRANSACTION_ACCOUNTS Yes Yes

3.7.1.2. Cartridge-specific data movement key warnings

Data movement key warnings


Reload could result in duplicate rows. This is because some tables in the cartridge do not have a unique key
set or auto-chosen as the data movement key.

3.7.1.3. Data Sources

Table use name Data Source Annotation


MTL_TRANSACTION_ACCOUNTS History

3.7.1.4. Parameters used in the Source Model and Cartridge

Parameters used
prReloadFromTransaction,
prReloadToTransaction

3.7.1.5. Rules in Cartridge

Included Rules Excluded Rules


ReloadTransactions OrganizationParam
CutoffDateParam

24
3.8. Database to Database Cartridge
TransactionLotNumbersArchive 7.60.1.12.115.115
3.8.1. Cartridge TransactionLotNumbersArchive

Cartridge Info
Source Model TransactionLotNumbers
reference
Version 7.60.1.12.115.115
UID 6951-F16A-8FD4-0EBB
Annotation This cartridge uses model TxnLotNumber(INV.MTL_TRANSACTION_LOT_NUMBERS).
This cartridge archives the lot number information for transactions of an organization
,which falls before the cut-off date. Organization and cut-off date
are passed by the user as parameters.

3.8.1.1. Cartridge operations

Table use name Copy Purge Annotation


MTL_TRANSACTION_LOT_NUMBERS Yes Yes

3.8.1.2. Cartridge-specific data movement key warnings

Data movement key warnings


Reload could result in duplicate rows. This is because some tables in the cartridge do not have a unique key
set or auto-chosen as the data movement key.

3.8.1.3. Parameters used in the Source Model and Cartridge

Parameters used
prCutoffDate,
prOrganization

3.8.1.4. Rules in Cartridge

Included Rules Excluded Rules


OrganizationParam ReloadTransactions
CutoffDateParam

3.9. Database to Database Cartridge


TransactionLotNumbersReload 7.60.1.12.115.115

25
3.9.1. Cartridge TransactionLotNumbersReload

Cartridge Info
Source Model TransactionLotNumbers
reference
Version 7.60.1.12.115.115
UID 090B-FAFA-77DD-67F5
Annotation This cartridge uses model TxnLotNumber(INV.MTL_TRANSACTION_LOT_NUMBERS).
This cartridge is used for re-load purpose.
This cartridge re-loads the lot number information for transactions of an organization
,which falls before the cut-off date. Organization and cut-off date
are passed by the user as parameters.

3.9.1.1. Cartridge operations

Table use name Copy Purge Annotation


MTL_TRANSACTION_LOT_NUMBERS Yes Yes

3.9.1.2. Cartridge-specific data movement key warnings

Data movement key warnings


Reload could result in duplicate rows. This is because some tables in the cartridge do not have a unique key
set or auto-chosen as the data movement key.

3.9.1.3. Data Sources

Table use name Data Source Annotation


MTL_TRANSACTION_LOT_NUMBERS History

3.9.1.4. Parameters used in the Source Model and Cartridge

Parameters used
prReloadFromTransaction,
prReloadToTransaction

3.9.1.5. Rules in Cartridge

Included Rules Excluded Rules


ReloadTransactions OrganizationParam
CutoffDateParam

3.10. Database to Database Cartridge


TransactionSchedulesArchive 7.60.1.12.115.115

26
3.10.1. Cartridge TransactionSchedulesArchive

Cartridge Info
Source Model TransactionSchedules
reference
Version 7.60.1.12.115.115
UID A3EA-46D0-BF1A-3588
Annotation This cartridge uses model TxnSchedules(INV.MTL_MATERIAL_TXN_ALLOCATIONS).
This cartridge archives the repetitive schedules charged for the material transactions
of an organization ,which falls before the cut-off date. Organization and cut-off date
are passed by the user as parameters

3.10.1.1. Cartridge operations

Table use name Copy Purge Annotation


MTL_MATERIAL_TXN_ALLOCATIONS Yes Yes

3.10.1.2. Cartridge-specific data movement key warnings

Data movement key warnings


Reload could result in duplicate rows. This is because some tables in the cartridge do not have a unique key
set or auto-chosen as the data movement key.

3.10.1.3. Parameters used in the Source Model and Cartridge

Parameters used
prCutoffDate,
prOrganization

3.10.1.4. Rules in Cartridge

Included Rules Excluded Rules


OrganizationParam ReloadTransactions
CutoffDateParam

3.11. Database to Database Cartridge


TransactionSchedulesReload 7.60.1.12.115.115
3.11.1. Cartridge TransactionSchedulesReload

Cartridge Info
Source Model TransactionSchedules
reference
Version 7.60.1.12.115.115
UID AFB3-F709-9118-800E

27
Cartridge Info
Annotation This cartridge uses model TxnSchedules(INV.MTL_MATERIAL_TXN_ALLOCATIONS).
This cartridge is used for re-load purpose.
This cartridge re-loads the repetitive schedules charged for the material transactions
of an organization ,which falls before the cut-off date. Organization and cut-off date
are passed by the user as parameters.

3.11.1.1. Cartridge operations

Table use name Copy Purge Annotation


MTL_MATERIAL_TXN_ALLOCATIONS Yes Yes

3.11.1.2. Cartridge-specific data movement key warnings

Data movement key warnings


Reload could result in duplicate rows. This is because some tables in the cartridge do not have a unique key
set or auto-chosen as the data movement key.

3.11.1.3. Data Sources

Table use name Data Source Annotation


MTL_MATERIAL_TXN_ALLOCATIONS History

3.11.1.4. Parameters used in the Source Model and Cartridge

Parameters used
prReloadFromTransaction,
prReloadToTransaction

3.11.1.5. Rules in Cartridge

Included Rules Excluded Rules


ReloadTransactions OrganizationParam
CutoffDateParam

3.12. Database to Database Cartridge TransactionsArchive


7.60.1.12.115.115
3.12.1. Cartridge TransactionsArchive

Cartridge Info
Source Model Transactions
reference
Version 7.60.1.12.115.115
UID 5BE5-B5F5-1A57-471D

28
Cartridge Info
Annotation This cartridge uses model Transactions(INV.MTL_ACTUAL_COST_SUBELEMENT,
INV.MTL_CST_ACTUAL_COST_DETAILS,INV.MTL_CST_TXN_COST_DETAILS,
INV.MTL_MATERIAL_TRANSACTIONS,WIP.WIP_SCRAP_VALUES)
This cartridge archives the data of the inventory transactions of an organization ,which
falls before the cut-off date.
It also archives the corresponding cost information,material overhead subelement
information and assembly scrap transaction cost
information.
Organization and cut-off date are passed by the user as parameters.

3.12.1.1. Cartridge operations

Table use name Copy Purge Annotation


MTL_ACTUAL_COST_SUBELEMENT Yes Yes
MTL_CST_ACTUAL_COST_DETAILS Yes Yes
MTL_CST_TXN_COST_DETAILS Yes Yes
MTL_MATERIAL_TRANSACTIONS Yes Yes
WIP_SCRAP_VALUES Yes Yes

3.12.1.2. Cartridge-specific data movement key warnings

Data movement key warnings


Reload could result in duplicate rows. This is because some tables in the cartridge do not have a unique key
set or auto-chosen as the data movement key.

3.12.1.3. Parameters used in the Source Model and Cartridge

Parameters used
prCutoffDate,
prOrganization

3.12.1.4. Rules in Cartridge

Included Rules Excluded Rules


OrganizationParam ReloadTransactions
CutoffDateParam

3.13. Database to Database Cartridge TransactionsReload


7.60.1.12.115.115
3.13.1. Cartridge TransactionsReload

Cartridge Info
Source Model Transactions
reference
Version 7.60.1.12.115.115
UID B260-5AE0-5D61-F657

29
Cartridge Info
Annotation This cartridge uses model Transactions(INV.MTL_ACTUAL_COST_SUBELEMENT,
INV.MTL_CST_ACTUAL_COST_DETAILS,INV.MTL_CST_TXN_COST_DETAILS,
INV.MTL_MATERIAL_TRANSACTIONS,WIP.WIP_SCRAP_VALUES). This cartridge is
used for re-load purpose.
This cartridge re-loads the data of the inventory transactions of an organization ,which
falls before the cut-off date.
It also re-loads the corresponding cost information,material overhead subelement
information and assembly scrap transaction cost
information.
Organization and cut-off date are passed by the user as parameters.

3.13.1.1. Cartridge operations

Table use name Copy Purge Annotation


MTL_ACTUAL_COST_SUBELEMENT Yes Yes
MTL_CST_ACTUAL_COST_DETAILS Yes Yes
MTL_CST_TXN_COST_DETAILS Yes Yes
MTL_MATERIAL_TRANSACTIONS Yes Yes
WIP_SCRAP_VALUES Yes Yes

3.13.1.2. Cartridge-specific data movement key warnings

Data movement key warnings


Reload could result in duplicate rows. This is because some tables in the cartridge do not have a unique key
set or auto-chosen as the data movement key.

3.13.1.3. Data Sources

Table use name Data Source Annotation


MTL_ACTUAL_COST_SUBELEMENT History
MTL_CST_ACTUAL_COST_DETAILS History
MTL_CST_TXN_COST_DETAILS History
MTL_MATERIAL_TRANSACTIONS History
WIP_SCRAP_VALUES History

3.13.1.4. Parameters used in the Source Model and Cartridge

Parameters used
prReloadFromTransaction,
prReloadToTransaction

3.13.1.5. Rules in Cartridge

Included Rules Excluded Rules


ReloadTransactions OrganizationParam
CutoffDateParam

30
31
4. Source Models
4.1. Source Model SerialTransactions
Source Model Info
UID C849-D688-A2F7-9C9F
Annotation This model contain 1 driving table (INV.MTL_UNIT_TRANSACTIONS)

4.1.1. ER Diagram

4.1.2. Table use List


4.1.2.1. Table use MTL_UNIT_TRANSACTIONS

MTL_UNIT_TRANSACTIONS
Table Name INV.MTL_UNIT_TRANSACTIONS
Table Alias MTL_UNIT_TRANSACTIONS
Use Type Transactional
Annotation MTL_UNIT_TRANSACTIONS stores a record of every material
transaction of
a serialized unit in Inventory. Records are inserted into this table
through the transaction processor

Data movement key for MTL_UNIT_TRANSACTIONS


DM Key name <Row ID>
DM Key Info "MTL_UNIT_TRANSACTIONS" is set to have data movement done by
row ID.

Rules on MTL_UNIT_TRANSACTIONS
Name Attributes Annotation
OrganizationParam Category: Data Integrity This rule is based on
Analytics: Disabled MTL_UNIT_TRANSACTIONS table.
Based on the organization selected
Mode: Exclusive by the user as a parameter,
Customization: Optional the eligible data from this table gets
archived.
Query Expression
Database ansi
Query
MTL_UNIT_TRANSACTIONS.ORGANIZATION_ID in (SELECT organization_id from
${SOURCE.INV.ORG_ACCT_PERIODS} oap where oap.period_start_date <= :prCutoffDate and
oap.schedule_close_date >= :prCutoffDate and oap.open_flag = 'N' and
oap.organization_id = nvl(:prOrganization ,oap.organization_id) )
Name Attributes Annotation

32
Rules on MTL_UNIT_TRANSACTIONS
CutoffDateParam Category: Data Integrity This rule is based on
Analytics: Disabled INV.MTL_UNIT_TRANSACTIONS
table.
Mode: Exclusive Based on the user selected cutoff
Customization: Mandatory date and organization, the eligible
data gets
archived from this table.It deletes all
the data for a particular organization
where
transaction date is less than the
cutoff date.
Query Expression
Database ansi
Query
"MTL_UNIT_TRANSACTIONS"."TRANSACTION_DATE" <= :prCutoffDate + 1-(1/(24*3600))
Name Attributes Annotation
ReloadTransactions Category: Data Integrity This rule works only for reload job. It
Analytics: Disabled takes the low transaction id and high
transaction id as input parameters.
Mode: Exclusive Low transaction id value is
Customization: Mandatory mandatory while high transaction id
value is optional.
if user passes both transaction id
values, then the reload job reloads
all the records
ranging from the lower transaction id
to higher transaction id (both
inclusive).
If user passes only lower transcation
id, then the reload job reloads only
the lower
transaction id record.
Query Expression
Database ansi
Query
"MTL_UNIT_TRANSACTIONS"."TRANSACTION_ID" >= :prReloadFromTransaction AND
"MTL_UNIT_TRANSACTIONS"."TRANSACTION_ID" <= nvl(:prReloadToTransaction ,
:prReloadFromTransaction)

4.2. Source Model TransactionAccounts


Source Model Info
UID 1F1C-A299-DDA6-1B47
Annotation This model contain 1 driving table (INV.MTL_TRANSACTION_ACCOUNTS)

4.2.1. ER Diagram

33
4.2.2. Table use List
4.2.2.1. Table use MTL_TRANSACTION_ACCOUNTS

MTL_TRANSACTION_ACCOUNTS
Table Name INV.MTL_TRANSACTION_ACCOUNTS
Table Alias MTL_TRANSACTION_ACCOUNTS
Use Type Transactional
Annotation MTL_TRANSACTION_ACCOUNTS holds the accounting information for
each
material transaction in MTL_MATERIAL_TRANSACTIONS. Oracle
Inventory
uses this information to track the financial impact of your quantity
moves.

Data movement key for MTL_TRANSACTION_ACCOUNTS


DM Key name <Row ID>
DM Key Info "MTL_TRANSACTION_ACCOUNTS" is set to have data movement done
by row ID.

Rules on MTL_TRANSACTION_ACCOUNTS
Name Attributes Annotation
OrganizationParam Category: Data Integrity This rule is based on
Analytics: Disabled MTL_TRANSACTION_ACCOUNTS
table.
Mode: Exclusive Based on the organization selected
Customization: Optional by the user as a parameter,
the eligible data from this table gets
archived.
Query Expression
Database ansi
Query
MTL_TRANSACTION_ACCOUNTS.ORGANIZATION_ID in (SELECT organization_id from
${SOURCE.INV.ORG_ACCT_PERIODS} oap where oap.period_start_date <= :prCutoffDate and
oap.schedule_close_date >= :prCutoffDate and oap.open_flag = 'N' and
oap.organization_id = nvl(:prOrganization ,oap.organization_id) )
Name Attributes Annotation
CutoffDateParam Category: Data Integrity This rule is based on
Analytics: Disabled INV.MTL_TRANSACTION_ACCOU
NTS table.
Mode: Exclusive Based on the user selected cutoff
Customization: Mandatory date and organization, the eligible
data gets
archived from this table.It deletes all
the data for a particular organization
where
transaction date is less than the
cutoff date.
Query Expression
Database ansi
Query
"MTL_TRANSACTION_ACCOUNTS"."TRANSACTION_DATE" <= :prCutoffDate + 1-(1/(24*3600))
Name Attributes Annotation

34
Rules on MTL_TRANSACTION_ACCOUNTS
ReloadTransactions Category: Data Integrity This rule works only for reload job. It
Analytics: Disabled takes the low transaction id and high
transaction id as input parameters.
Mode: Exclusive Low transaction id value is
Customization: Mandatory mandatory while high transaction id
value is optional.
if user passes both transaction id
values, then the reload job reloads
all the records
ranging from the lower transaction id
to higher transaction id (both
inclusive).
If user passes only lower transcation
id, then the reload job reloads only
the lower
transaction id record.
Query Expression
Database ansi
Query
"MTL_TRANSACTION_ACCOUNTS"."TRANSACTION_ID" >= :prReloadFromTransaction AND
"MTL_TRANSACTION_ACCOUNTS"."TRANSACTION_ID" <= nvl(:prReloadToTransaction ,
:prReloadFromTransaction)

4.3. Source Model TransactionLotNumbers


Source Model Info
UID 2FB3-B715-0677-F79F
Annotation This model contain 1 driving table (INV.MTL_TRANSACTION_LOT_NUMBERS)

4.3.1. ER Diagram

4.3.2. Table use List


4.3.2.1. Table use MTL_TRANSACTION_LOT_NUMBERS

MTL_TRANSACTION_LOT_NUMBERS
Table Name INV.MTL_TRANSACTION_LOT_NUMBERS
Table Alias MTL_TRANSACTION_LOT_NUMBERS
Use Type Transactional
Annotation MTL_TRANSACTION_LOT_NUMBERS stores lot number information for
transactions in the MTL_MATERIAL_TRANSACTIONS table.

Data movement key for MTL_TRANSACTION_LOT_NUMBERS


DM Key name <Row ID>
DM Key Info "MTL_TRANSACTION_LOT_NUMBERS" is set to have data movement
done by row ID.

35
Rules on MTL_TRANSACTION_LOT_NUMBERS
Name Attributes Annotation
OrganizationParam Category: Data Integrity This rule is based on
Analytics: Disabled MTL_TRANSACTION_LOT_NUMB
ERS table.
Mode: Exclusive Based on the organization selected
Customization: Optional by the user as a parameter,
the eligible data from this table gets
archived.
Query Expression
Database ansi
Query
MTL_TRANSACTION_LOT_NUMBERS.ORGANIZATION_ID in (SELECT organization_id from
${SOURCE.INV.ORG_ACCT_PERIODS} oap where oap.period_start_date <= :prCutoffDate and
oap.schedule_close_date >= :prCutoffDate and oap.open_flag = 'N' and
oap.organization_id = nvl(:prOrganization ,oap.organization_id) )
Name Attributes Annotation
CutoffDateParam Category: Data Integrity This rule is based on
Analytics: Disabled INV.MTL_TRANSACTION_LOT_NU
MBERS table.
Mode: Exclusive Based on the user selected cutoff
Customization: Mandatory date and organization, the eligible
data gets
archived from this table.It deletes all
the data for a particular organization
where
transaction date is less than the
cutoff date.
Query Expression
Database ansi
Query
"MTL_TRANSACTION_LOT_NUMBERS"."TRANSACTION_DATE" <= :prCutoffDate + 1-(1/(24*3600))
Name Attributes Annotation
ReloadTransactions Category: Data Integrity This rule works only for reload job. It
Analytics: Disabled takes the low transaction id and high
transaction id as input parameters.
Mode: Exclusive Low transaction id value is
Customization: Mandatory mandatory while high transaction id
value is optional.
if user passes both transaction id
values, then the reload job reloads
all the records
ranging from the lower transaction id
to higher transaction id (both
inclusive).
If user passes only lower transcation
id, then the reload job reloads only
the lower
transaction id record.
Query Expression
Database ansi
Query
"MTL_TRANSACTION_LOT_NUMBERS"."TRANSACTION_ID" >= :prReloadFromTransaction AND
"MTL_TRANSACTION_LOT_NUMBERS"."TRANSACTION_ID" <= nvl(:prReloadToTransaction ,
:prReloadFromTransaction)

36
4.4. Source Model TransactionSchedules
Source Model Info
UID E105-9E06-DA34-36EE
Annotation This model contain 1 driving table (INV.MTL_MATERIAL_TXN_ALLOCATIONS)

4.4.1. ER Diagram

4.4.2. Table use List


4.4.2.1. Table use MTL_MATERIAL_TXN_ALLOCATIONS

MTL_MATERIAL_TXN_ALLOCATIONS
Table Name INV.MTL_MATERIAL_TXN_ALLOCATIONS
Table Alias MTL_MATERIAL_TXN_ALLOCATIONS
Use Type Transactional
Annotation MTL_MATERIAL_TXN_ALLOCATIONS stores the repetitive schedules
charged
by a material transaction. Each row contains the quantity transacted
to each schedule for a given transaction. Oracle Work in Process uses
this information to report the changes to individual schedules for
multi-schedule material transactions.

Data movement key for MTL_MATERIAL_TXN_ALLOCATIONS


DM Key name <Row ID>
DM Key Info "MTL_MATERIAL_TXN_ALLOCATIONS" is set to have data movement
done by row ID.

Rules on MTL_MATERIAL_TXN_ALLOCATIONS
Name Attributes Annotation
OrganizationParam Category: Data Integrity This rule is based on
Analytics: Disabled MTL_MATERIAL_TXN_ALLOCATI
ONS table.
Mode: Exclusive Based on the organization selected
Customization: Optional by the user as a parameter,
the eligible data from this table gets
archived.
Query Expression
Database ansi
Query
MTL_MATERIAL_TXN_ALLOCATIONS.ORGANIZATION_ID in (SELECT organization_id from
${SOURCE.INV.ORG_ACCT_PERIODS} oap where oap.period_start_date <= :prCutoffDate and
oap.schedule_close_date >= :prCutoffDate and oap.open_flag = 'N' and
oap.organization_id = nvl(:prOrganization ,oap.organization_id) )
Name Attributes Annotation

37
Rules on MTL_MATERIAL_TXN_ALLOCATIONS
CutoffDateParam Category: Data Integrity This rule is based on
Analytics: Disabled INV.MTL_MATERIAL_TXN_ALLOC
ATIONS table.
Mode: Exclusive Based on the user selected cutoff
Customization: Mandatory date and organization, the eligible
data gets
archived from this table.It deletes all
the data for a particular organization
where
transaction date is less than the
cutoff date.
Query Expression
Database ansi
Query
"MTL_MATERIAL_TXN_ALLOCATIONS"."TRANSACTION_DATE" <= :prCutoffDate + 1-(1/(24*3600))
Name Attributes Annotation
ReloadTransactions Category: Data Integrity This rule works only for reload job. It
Analytics: Disabled takes the low transaction id and high
transaction id as input parameters.
Mode: Exclusive Low transaction id value is
Customization: Mandatory mandatory while high transaction id
value is optional.
if user passes both transaction id
values, then the reload job reloads
all the records
ranging from the lower transaction id
to higher transaction id (both
inclusive).
If user passes only lower transcation
id, then the reload job reloads only
the lower
transaction id record.
Query Expression
Database ansi
Query
"MTL_MATERIAL_TXN_ALLOCATIONS"."TRANSACTION_ID" >= :prReloadFromTransaction AND
"MTL_MATERIAL_TXN_ALLOCATIONS"."TRANSACTION_ID" <= nvl(:prReloadToTransaction ,
:prReloadFromTransaction)

4.5. Source Model Transactions


Source Model Info
UID 46B0-63BD-E5C2-C981
Annotation This model contains 1 driving table (INV.MTL_MATERIAL_TRANSACTIONS) and 4-
transactional table
(WIP.WIP_SCRAP_VALUES,INV.MTL_CST_ACTUAL_COST_DETAILS,INV.MTL_CST
_TXN_COST_DETAILS,INV.MTL_ACTUAL_COST_SUNELEMENT).

4.5.1. ER Diagram

38
4.5.2. Table use List
4.5.2.1. Table use MTL_MATERIAL_TRANSACTIONS

MTL_MATERIAL_TRANSACTIONS
Table Name INV.MTL_MATERIAL_TRANSACTIONS
Table Alias MTL_MATERIAL_TRANSACTIONS
Use Type Transactional
Annotation MTL_MATERIAL_TRANSACTIONS stores a record of every material
transaction or cost update performed in Inventory.

Data movement key for MTL_MATERIAL_TRANSACTIONS


DM Key name <Row ID>
DM Key Info "MTL_MATERIAL_TRANSACTIONS" is set to have data movement done
by row ID.

Rules on MTL_MATERIAL_TRANSACTIONS
Name Attributes Annotation
OrganizationParam Category: Data Integrity This rule is based on
Analytics: Disabled MTL_MATERIAL_TRANSACTIONS
table.
Mode: Exclusive Based on the organization selected
Customization: Optional by the user as a parameter,
the eligible data from this table gets
archived.
Query Expression
Database ansi
Query
MTL_MATERIAL_TRANSACTIONS.ORGANIZATION_ID in (SELECT organization_id from
${SOURCE.INV.ORG_ACCT_PERIODS} oap where oap.period_start_date <= :prCutoffDate and
oap.schedule_close_date >= :prCutoffDate and oap.open_flag = 'N' and
oap.organization_id = nvl(:prOrganization ,oap.organization_id) )
Name Attributes Annotation

39
Rules on MTL_MATERIAL_TRANSACTIONS
CutoffDateParam Category: Data Integrity This rule is based on
Analytics: Disabled INV.MTL_MATERIAL_TRANSACTI
ONS table.
Mode: Exclusive Based on the user selected cutoff
Customization: Mandatory date and organization, the eligible
data gets
archived from this table.It deletes all
the data for a particular organization
where
transaction date
Query Expression
Database ansi
Query
"MTL_MATERIAL_TRANSACTIONS"."TRANSACTION_DATE" <= :prCutoffDate + 1-(1/(24*3600))
Name Attributes Annotation
ReloadTransactions Category: Data Integrity This rule works only for reload job. It
Analytics: Disabled takes the low transaction id and high
transaction id as input parameters.
Mode: Exclusive Low transaction id value is
Customization: Mandatory mandatory while high transaction id
value is optional.
if user passes both transaction id
values, then the reload job reloads
all the records
ranging from the lower transaction id
to higher transaction id (both
inclusive).
If user passes only lower transcation
id, then the reload job reloads only
the lower
transaction id record.
Query Expression
Database ansi
Query
"MTL_MATERIAL_TRANSACTIONS"."TRANSACTION_ID" >= :prReloadFromTransaction AND
"MTL_MATERIAL_TRANSACTIONS"."TRANSACTION_ID" <= nvl(:prReloadToTransaction ,
:prReloadFromTransaction)

4.5.2.2. Table use WIP_SCRAP_VALUES

WIP_SCRAP_VALUES
Table Name WIP.WIP_SCRAP_VALUES
Table Alias WIP_SCRAP_VALUES
Use Type Transactional
Annotation WIP_SCRAP_VALUES stores assembly scrap transaction cost
information for jobs and schedules. Oracle Work in Process calculates
this information as part of scrap transaction processing and
inserts the values in this table. Oracle Work in Process updates
these values as necessary when you perform cost updates. This table
is also used when printing scrap transaction information on the
Discrete Job and Repetitive Schedule Value reports.

Relation between WIP_SCRAP_VALUES and parent MTL_MATERIAL_TRANSACTIONS


Parent Table Name INV.MTL_MATERIAL_TRANSACTIONS
Parent Table Alias MTL_MATERIAL_TRANSACTIONS
Unique Key Name MTL_MATERIAL_TRANSACTIONS_U1
Foreign Key Name MTL_MATERIAL_TRANSACTIONS_WIP_SCRAP_VALUES_FK

40
Relation between WIP_SCRAP_VALUES and parent MTL_MATERIAL_TRANSACTIONS
Foreign Key Annotation Transaction_id is the joining key between the WIP_SCRAP_VALUES and
MTL_MATERIAL_TRANSACTIONS table
UK Columns (UK is on parent) FK Columns
TRANSACTION_ID TRANSACTION_ID

Data movement key for WIP_SCRAP_VALUES


DM Key name <Row ID>
DM Key Info "WIP_SCRAP_VALUES" is set to have data movement done by row ID.

4.5.2.3. Table use MTL_CST_ACTUAL_COST_DETAILS

MTL_CST_ACTUAL_COST_DETAILS
Table Name INV.MTL_CST_ACTUAL_COST_DETAILS
Table Alias MTL_CST_ACTUAL_COST_DETAILS
Use Type Transactional
Annotation MTL_CST_ACTUAL_COST_DETAILS stores actual cost, prior cost, and
new
cost information for a transaction by element and by level.

Relation between MTL_CST_ACTUAL_COST_DETAILS and parent MTL_MATERIAL_TRANSACTIONS


Parent Table Name INV.MTL_MATERIAL_TRANSACTIONS
Parent Table Alias MTL_MATERIAL_TRANSACTIONS
Unique Key Name MTL_MATERIAL_TRANSACTIONS_U1
Foreign Key Name MTL_MATERIAL_TRANSACTIONS_MTL_CST_ACTUAL_COST_DETAI
LS_FK
Foreign Key Annotation Transaction_id is the joining key between the
MTL_CST_ACTUAL_COST_DETAILS and
MTL_MATERIAL_TRANSACTIONS tables
UK Columns (UK is on parent) FK Columns
TRANSACTION_ID TRANSACTION_ID

Data movement key for MTL_CST_ACTUAL_COST_DETAILS


DM Key name <Row ID>
DM Key Info "MTL_CST_ACTUAL_COST_DETAILS" is set to have data movement
done by row ID.

4.5.2.4. Table use MTL_CST_TXN_COST_DETAILS

MTL_CST_TXN_COST_DETAILS
Table Name INV.MTL_CST_TXN_COST_DETAILS
Table Alias MTL_CST_TXN_COST_DETAILS
Use Type Transactional
Annotation MTL_CST_TXN_COST_DETAILS stores the cost of a transaction by
element and level.

Relation between MTL_CST_TXN_COST_DETAILS and parent MTL_MATERIAL_TRANSACTIONS


Parent Table Name INV.MTL_MATERIAL_TRANSACTIONS
Parent Table Alias MTL_MATERIAL_TRANSACTIONS

41
Relation between MTL_CST_TXN_COST_DETAILS and parent MTL_MATERIAL_TRANSACTIONS
Unique Key Name MTL_MATERIAL_TRANSACTIONS_U1
Foreign Key Name MTL_MATERIAL_TRANSACTIONS_MTL_CST_TXN_COST_DETAILS_
FK
Foreign Key Annotation Transaction_id is the joining key between the
MTL_CST_TXN_COST_DETAILS and
MTL_MATERIAL_TRANSACTIONS tables
UK Columns (UK is on parent) FK Columns
TRANSACTION_ID TRANSACTION_ID

Data movement key for MTL_CST_TXN_COST_DETAILS


DM Key name <Row ID>
DM Key Info "MTL_CST_TXN_COST_DETAILS" is set to have data movement done
by row ID.

4.5.2.5. Table use MTL_ACTUAL_COST_SUBELEMENT

MTL_ACTUAL_COST_SUBELEMENT
Table Name INV.MTL_ACTUAL_COST_SUBELEMENT
Table Alias MTL_ACTUAL_COST_SUBELEMENT
Use Type Transactional
Annotation MTL_ACTUAL_COST_SUBELEMENT stores the material overhead
subelements that are charged for a given transaction. This is a child
table of MTL_CST_ACTUAL_COST_DETAILS.

Relation between MTL_ACTUAL_COST_SUBELEMENT and parent MTL_MATERIAL_TRANSACTIONS


Parent Table Name INV.MTL_MATERIAL_TRANSACTIONS
Parent Table Alias MTL_MATERIAL_TRANSACTIONS
Unique Key Name MTL_MATERIAL_TRANSACTIONS_U1
Foreign Key Name MTL_MATERIAL_TRANSACTIONS_MTL_ACTUAL_COST_SUBELEME
NT_FK
Foreign Key Annotation Transaction_id is the joining key between the
MTL_ACTUAL_COST_SUBELEMENT and
MTL_MATERIAL_TRANSACTIONS tables
UK Columns (UK is on parent) FK Columns
TRANSACTION_ID TRANSACTION_ID

Data movement key for MTL_ACTUAL_COST_SUBELEMENT


DM Key name <Row ID>
DM Key Info "MTL_ACTUAL_COST_SUBELEMENT" is set to have data movement
done by row ID.

42

You might also like