Preparation of Oracle EBS - docs.plm.automation.siemens.com · • Oracle E-Business Suite 12.2.x (further referenced as EBS 12.2) Detailed information about the exact sub-versions

Preparation ofOracle EBS

Contents

Preface 5

Introduction 1-1

Oracle EBS Software Requirements to Run T4OSupported Oracle EBS Environment ────────────────────────── 2-1T4O Communication with Oracle EBS ───────────────────────── 2-1

Java Database Connectivity (JDBC) ────────────────────────────── 2-2Integrated SOA Gateway (ISG) ──────────────────────────────── 2-2

Required Patches ────────────────────────────────────── 2-4Required Patches for EBS 12.1 ───────────────────────────────── 2-5Required Patches for EBS 12.2 ──────────────────────────────── 2-13

T4O Application - Installation InstructionsIntroduction ───────────────────────────────────────── 3-1T4O Application Installation Package Content ─────────────────── 3-2Overview of Oracle EBS 12.2 Specifics ──────────────────────── 3-5T4O Application Installation Steps ─────────────────────────── 3-6

Common Installation Steps for JDBC and ISG ──────────────────────── 3-7JDBC Specific Installation Steps ─────────────────────────────── 3-21ISG Specific Installation Steps ──────────────────────────────── 3-27Post Installation Steps ───────────────────────────────────── 3-35

T4O Application Upgrade Steps ──────────────────────────── 3-36Common Upgrade Steps for JDBC and ISG ───────────────────────── 3-37JDBC Specific Upgrade Steps ───────────────────────────────── 3-40ISG Specific Upgrade Steps ────────────────────────────────── 3-41

PL/SQL Functions Called by T4OOracle EBS PL/SQL APIs Called by T4O ───────────────────────── 4-1T4O Extended PL/SQL Functions Called by T4O ─────────────────── 4-2

Required Permissions 5-1

Requirements for System Items Key Flexfield 6-1

Requirements for Module Document Attachments 7-1

Requirements for Module Collection Plans (Quality) 8-1

Set-up for Triggering Data Transfer from Oracle EBS

Preparation of Oracle EBS 2© 2018 Siemens Product Lifecycle Management Software, Inc.

The Z-Table ───────────────────────────────────────── 9-1PL/SQL Package T4O_ZPTC_1140 ──────────────────────────── 9-5T4O Database Trigger Templates ──────────────────────────── 9-9

Glossary A-1

Contents


4 Preparation of Oracle EBS© 2018 Siemens Product Lifecycle Management Software, Inc.

PrefaceThis documentation cannot be used as a substitute for consulting advice, because it can never considerthe individual business processes and configuration. Despite our best efforts it is probable that someinformation about functionality and coherence may be incomplete.

Issue: July 2018

Legal notice:

All rights reserved. No part of this documentation may be copied by any means or made available toentities or persons other than employees of the licensee of the Teamcenter Gateway for Oracle E-Business Suite or those that have a legitimate right to use this documentation as part of theirassignment on behalf of the licensee to enable or support usage of the software for use within theboundaries of the license agreement.

© 2010-2018 Siemens Product Lifecycle Management Software Inc.

Trademark notice:

Siemens, the Siemens logo and SIMATIC IT are registered trademarks of Siemens AG.

Camstar and Teamcenter are trademarks or registered trademarks of Siemens Product LifecycleManagement Software Inc. or its subsidiaries in the United States and in other countries.

Oracle is a registered trademark of Oracle Corporation.

SAP, R/3, SAP S/4HANA®, SAP Business Suite® and mySAP are trademarks or registered trademarks of SAPor its affiliates in Germany and other countries.

TESIS is a registered trademark of TESIS GmbH.

All other trademarks, registered trademarks or service marks belong to their respective holders.


6 Preparation of Oracle EBS© 2018 Siemens Product Lifecycle Management Software, Inc.

1. IntroductionThe Teamcenter Gateway Oracle E-Business Suite (T4O) software solution is a general purposeintegration software that provides data and process integration between Teamcenter® by Siemens PLMand ORACLE® E-Business Suite by Oracle Corporation.

T4O provides a wide range of interactive and workflow functions to transfer and synchronize databetween Teamcenter and Oracle EBS.

Preparation of Oracle EBS 1-1© 2018 Siemens Product Lifecycle Management Software, Inc.

1. Introduction

1-2 Preparation of Oracle EBS© 2018 Siemens Product Lifecycle Management Software, Inc.

2. Oracle EBS Software Requirements toRun T4O

2.1 Supported Oracle EBS Environment

In general, the following Oracle EBS main versions are supported:

• Oracle E-Business Suite 12.1.x (further referenced as EBS 12.1)

• Oracle E-Business Suite 12.2.x (further referenced as EBS 12.2)

Detailed information about the exact sub-versions supported and the tested versions is available in thereadme file Teamcenter_Gateway_for_Oracle_EBS_18.1_README_for_Teamcenter_*.txt. It can bedownloaded from GTAC from the same directory as the T4O software packages.

Caution:

• An Oracle EBS release system must meet the requirements defined by Oracle in thefollowing support notes (keep in mind that those notes are continuously updated by OracleSupport):

• EBS 12.1: Consult the Oracle Support note "Oracle E-Business Suite Release 12.1 ReleaseUpdate Packs (RUPs) (Doc ID 1203734.1)"

• EBS 12.2: Consult the Oracle Support note "Oracle E-Business Suite Release Notes, Release12.2 (Doc ID 1320300.1)"

• With the help of the support notes above, identify the latest Oracle EBS RUPs (Release UpdatePacks) that were available with the release date of this T4O version (July 2018)

→ There is no guarantee that newer versions will work correctly with T4O!

• The minimum supported DB version for an EBS 12.2 is 11.2.0.4 (see Oracle Support note"Database Preparation Guidelines for an E-Business Suite Release 12.2 Upgrade (Doc ID1349240.1)" for details).

2.2 T4O Communication with Oracle EBS

T4O supports two methods of how to communicate with an Oracle EBS system. It's your choice whichtechnology to configure for communication:

• Java Database Connectivity (JDBC)

• Integrated SOA Gateway (ISG)


http://www.siemens.com/gtac

https://support.oracle.com





For instructions on how to configure T4O using the preferred communication method with an OracleEBS system, please refer to chapter T4O Connectivity to Oracle EBS in the Teamcenter Gateway -Installation Guide .

2.2.1 Java Database Connectivity (JDBC)

Please ensure the following before using JDBC with T4O:

• In order to get a connection to an Oracle database via JDBC, the Oracle configuration file sqlnet.ora(usually located at $ORACLE_HOME/network/admin) has to be adapted by choosing one of thefollowing options:

• Deactivate the verification of valid nodes by setting variable TCP.VALIDNODE_CHECKING to NO.This would enable any host to connect to the database.

• Restrict the number of hosts that are allowed to connect to the database by activating theverification of valid nodes: Set variable TCP.VALIDNODE_CHECKING to YES and unlock respectivehosts explicitly in variable TCP.INVITED_NODES, e.g.:

TCP.INVITED_NODES=(host1.company.de, host2.company.de)

In that list, be sure to include the host where T4O is running.

Once you've finished the modifications to sqlnet.ora, bounce the listener.

Caution:

Keep the following in mind when performing any Oracle EBS maintenance tasks:

With JDBC, T4O directly connects to the database. Therefore, T4O is independent of any OracleEBS processes. This means that T4O still works as long as the Oracle DB is up and no maintenancemode was activated. Only after the maintenance mode has been activated, T4O will return withan error message.

→ If you expect T4O to stop working during Oracle EBS maintenance activities, make surethat T4O processes are shut down and that the Oracle EBS maintenance mode is enabled(using the adadmin utility)!

2.2.2 Integrated SOA Gateway (ISG)

The ISG is officially shipped by Oracle with Oracle EBS 12.1.1.

Caution:

Up to now, T4O only supports communication via ISG using SOAP web services. REST webservices are not yet supported.

2. Oracle EBS Software Requirements to Run T4O


https://docs.plm.automation.siemens.com/tdoc/pl4x/18.1/T4O/#uid:index_xid1340292


Prerequisites

Please ensure the following before using ISG with T4O:

• ISG must be successfully installed following the instructions of following Oracle Support notes,depending on your Oracle EBS version:

• “Installing Oracle E-Business Suite Integrated SOA Gateway, Release 12.1.3 (Doc ID 556540.1)” →that document includes references to documents for versions 12.1.1 and 12.1.2

• “Installing Oracle E-Business Suite Integrated SOA Gateway, Release 12.2 (Doc ID 1311068.1)”

• The following Oracle PL/SQL API packages must be available through web service calls (wrapped asservices using ISG):

• User - FND_WEB_SEC

• Concurrent Request - FND_REQUEST

• Make sure that ISG is working properly, e.g. by doing the following:Test any web service (e.g. FND_REQUEST) using a web service testing tool like SoapUI.

For more information on the Integrated SOA Gateway, refer to the following Oracle Support notes,depending on your Oracle EBS version.

Oracle Support notes for ISG with EBS 12.1

Basic Oracle Support notes for ISG setup:

• 556540.1: "Installing Oracle E-Business Suite Integrated SOA Gateway, Release 12.1.3"

• 726414.1: "Oracle E-Business Suite Integrated SOA Gateway Troubleshooting Guide, Release 12"

• 755069.1: "EBS R12 Packager and Adapters for External Application Servers"

• 782455.1: "How Can I Expose E-Business Suite Integration Interfaces as Web Services?"

Additional Oracle Support note for ISG setup with Oracle EBS 12.1.1:

• 565922.1: "Oracle E-Business Suite Integrated SOA Gateway Release Notes, Release 12.1.1"

Additional Oracle Support note for ISG setup with Oracle EBS 12.1.3:

• 1096553.1: "Oracle E-Business Suite Integrated SOA Gateway Release Notes for Release 12.1.3"

Integrated SOA Gateway (ISG)







Oracle Support notes for ISG with EBS 12.2

Oracle Support notes for ISG release information:





Oracle Support notes for ISG troubleshooting:

• 1317697.1: "Oracle E-Business Suite Integrated SOA Gateway Troubleshooting Guide, Release 12.2"

2.3 Required Patches

Running T4O requires the installation of some Oracle patches, depending on your Oracle EBS version.

Caution:

• Depending on your exact Oracle EBS subversion and patchset level you may not need to installall patches as listed in the following. Please review the readme file of respective patch forgetting the applicable product version.

• The following patch list only includes patches for known issues and makes no claim tocompleteness. Furthermore, the list doesn’t comprise any dependencies.

In general, you may want to apply only those patches that are relevant for the functionality you areactually using. However, we recommend installing all of the below patches which are applicable for yourproduct version, even though they might not be relevant for your current use cases.

For each Oracle EBS version (EBS 12.1 and EBS 12.2), the patches are divided into two separate lists: Thefirst one including all patches to be installed independently of the configured Oracle EBS connector type,and the second one including the patches to be installed additionally for the ISG connector.

More information about the listed patches can be found on Oracle Support websites.

Depending on your Oracle EBS version, refer to one of the following chapters:

• Required Patches for EBS 12.1

• Required Patches for EBS 12.2






2.3.1 Required Patches for EBS 12.1

Patch list, irrespective of configured Oracle EBS connector type

Caution:

Please make sure that the patch for item cross references support (see below) is applied beforeinstalling the T4O application (as the patch loads the new package MTL_CROSS_REFERENCES_PUBwhich is referenced by T4O). Otherwise, you would get the following error message whileinstalling T4O PL/SQL packages:

**** ERROR: Cross References Patch is not installed in your system!

**** Please install this patch before continuing with the installation!

**** For details see the T4O documentation.

Patch Number Known Issue/Patch Description

Required /Recommended

(depending onfunctionality)

8550561

(for Oracle EBS12.1.1)

14329926


“(FP:11I10-12.1.2)TRACKING BUG - ITEM CROSS REFERENCEPUBLIC API”

“Patch to support Cross Ref and related items through API andCP in 12.1.3”

Generally required

Patch is alsorequired if you'renot using itemcross references!

10360252

Known issue:

“EGO_ITEM_PUB.Process_items Does Not Return All ErrorMessages (Doc ID 858283.1)”

Patch description:

“EGO_ITEM_PUB.PROCESS_ITEMS DOES NOT RETURN ERRORMESSAGES FOR ALL ITEMS PASSED IN”

Required for ITEMtransfers

8660792


9852661


Known issue:

“API EGO_ITM_PVT Returns Error: ORA-01403: No Data Found(Doc ID 1173413.1)”

Patch description:

“Upon applying this patch, postItemCreate business event logsproper values for item_number and organization_id”

“This patch is applicable for all 12.1.2 Customers, Afterapplying the patch EGO_ITEM_PUB.process_items supportscreation of SKU Items.”


Required Patches for EBS 12.1


→ Also check if you need to apply solution “B. Fixing theSecurity Issue” of Doc ID 1173413.1

8373378“This patch is applicable for all 12.1.2 Customers, Afterapplying this patch UDA values are displayed correctly whenusing EGO_ITEM_PUB.process_item”


13881020

“ITEM UPDATE ERROR AFTER APPLYING PATCH 13489639”

Important post installation steps:

• Unfreeze and freeze the System Items Flexfield (-> uncheckand check again the “Freeze Flexfield Definition” flag)

• Compile the System Items Flexfield definition (-> Save)

• If using ISG: Regenerate and redeploy the WSDL forEGO_ITEM_PUB API and recreate the grants

If you don’t perform those post installation steps, you mayobserve the following problem when T4O tries to read anOracle EBS item: Thefunction ::TPEBS::ITEM::getItemInfo returns withNOT_FOUND even though the requested item exists in EBS.


13721297

“This patch is applicable on 12.1.1 and above.After applyingthis patch,there will be default value forassignee,priority,requestor when create NIR through Excel andAPI”


18161814

Known issue:

“EGO_ITEM_PUB.PROCESS_ITEM API Creates Item Without ItemRevision when only one segment defined in "System Items"Key flexfield (Doc ID 1645685.1)”

Patch description:

“PROCESS_ITEM CREATES ITEM WITHOUT ITEM REVISION”


9681771

Known issue:

“Item Template Values Do Not Override MTL_SYSTEM_ITEMS_BUsing API And Web-Adi (Doc ID 1119093.1)”

Patch description:

“After applying this patch template values will be effected foran Item, when created using EGO_ITEM_PUB.PROCESS_ITEMAPI”

Required for ITEMcreation usingtemplates

14739246

Known issue:

“New Items Getting Created With Chr(0) In Segments 2-20 OfMtl_system_items_b [VIDEO] (Doc ID 1508645.1)”

Patch description:

Required for ITEMtransfers; onlyrequired if multiplesegments areconfigured for



“After application of this patch, EGO_ITEM_PUB.process_itemAPI will not stamp the unused segments inMTL_SYSTEM_ITEMS_B with chr(0) for UPDATE transaction”

System Items KeyFlexfield

16757608

“After applying this patch, Users will be able to null outoptional Item segments by passing exclamation('!') throughImport Catalog Items Concurrent program, Import ItemsConcurrent program, public API flows.”

Required for ITEMtransfers; onlyrequired if multiplesegments areconfigured forSystem Items KeyFlexfield

10630273

Known issue:

“Cross Reference API For Items Errors When Width Of'CROSS_REFERENCE' Is Greater Than 25 Characters (Doc ID1337510.1)”

Patch description:

“TO CHANGE THE WIDTH OF PARAMETER 'CROSS_REFERENCE'IN CROSS REFERENCE API”

Required for ItemCross ReferencesAssignment

8874286

Known issue:

“ENG_ECO_PUB.Process_Eco Fails With Error:BOM_Validate_Bom_Component : (Entity Validation)ORA-01403: no data found (Doc ID 956813.1)”

Patch description:

“After applying patch, creating a new bill throughEng_Eco_PUB.Process_Eco API does not error.”

Required for ECOtransfers

13619324

Known issue:

“OVERLAPPING DATES ERROR WHEN RUNNING ENG PUBLIC APIAFTER RUNNING BOM PUBLIC API (Doc ID 1435356.1)”

Patch description

“OVERLAPPING DATES ERROR WHEN USER RUNS ENG PUBLICAPI AFTER RUNNING BOM PUBLIC API”


13905125“After applying this path, user can insert future revisions evenif there exists revisions more recent than the inserted one.”


9780939

Known issue:

“The Effectivity Dates You Have Entered Are Overlapping ErrorWhile Disabling Component On ECO (Doc ID 553249.1)”

Patch description:

“After applying patch, user will only get a warning aboutoverlapping effectivity date and not an error while trying tosave a change in revised component in an ECO.”




12627502

Known issue:

“Revised Item Components Are Created With The Same ItemNumber, OpSeqNo And Effectivity (Doc ID 1607565.1)”

Patch description:

“ABLE TO ADD SAME ITEM AS COMPONENT TO BOM MULTIPLETIMES VIA API”


17275108

Known issue:

“API PROCESS_ECO - How To Clean Attributes (Doc ID1602824.1)”

Patch description

“After applying this patch, ECO API can be used to nullifyvarious attributes in ECO Header.”


18472502

Known issue:

“Eng_eco_pub.process_eco For Copy (new) Functionality. (DocID 1585958.1)”

Patch description:

“After applying this patch, copy and transfer functionality viaeco api works correctly.”


(also required if nocopy and transferfunctionality via ECOis used!)

18710762

Known issue:

“PROCESS_ECO Implements Revised Item Operations Directly(Doc ID 1905686.1)”

Patch description:

“After applying this patch, eco api will not implement revisedoperations immediately without a call to eco implementationconcurrent program.”

Required forhandling revisedoperations on anECO

20198432

Known issue:

“Unable to Update Change Order (ECO) Status ThroughENG_ECO_PUB.Process_Eco API (Doc ID 1960283.1)”

Patch description:

“API FOR PROMOTING CR PROMOTES TO SCHEDULED BUTWHEN REQUREY-CR IS BACK TO OPEN”

Required forcontrolling thestatus on an ECO

16305221

Known issue:

“Not All Errors From Eng_Eco_Pub.Process_Eco Returned AfterPatch 13777030:R12.ENG.C (Doc ID 1543239.1)”

Patch description:

“After applying this patch, error messages will be shown ifthere is any error happen when usingENG_ECO_PUB.PROCESS_ECO”

Required for ECOtransfers only ifpatch 13777030 isinstalled on yoursystem



12602782“ENCACNC WARNING ENDS WITH ORA-913: TOO MANYVALUES”

Recommended forECO transfers

23091813

Known issue:

“Bug 23091813 : ENG_ECO_PUB.PROCESS_ECO DOES NOTRETURN IF THE ECO IS OPEN IN EDIT MODE”

Patch description:

“ECO API does not throw error message when user tries toupdate an ECO that is simultaneously being modified in ECOform.”


22134406

Known issue:

“Bug 25306832 : PROCESS_ECO CLEARS VALUE FORCHANGE_DESCRIPTION SITTING ON REVISED ITEM”

Patch description:

“After applying the patch, ECO Open Interface populates'Change Description' of a revised item in an ECO.”


15945201“This patch resolves the issue of BOM Mass Change notdefaulting the list price of a non stockable item from ItemMaster”

Required for BOMtransfers

16971204

Known issue:

"API PROCESS_BOM - How To Clean Up Attributes (Doc ID1589034.1)"

Patch description:

“After applying this patch, BOM API can be used to null variousattributes in bom component.”

Required for BOMtransfers

17750170

Known issue:

“BOM API is Creating NEW_OPERATION_SEQUENCE_ID ValueEven if There is No Corresponding Routing Operation. (Doc ID1669987.1)”

Patch description:

“After applying this patch BOM API will create and update billcomponents with valid operation sequence ids”

Required for BOMtransfers andRouting transfers

17774427

Known issue:

“Duplicate Components Created When Use API To Create AndUpdate Bill of Material (Doc ID 1607639.1)”

Patch description:

“BOM API process_bom is creating duplicate components incommon bills”

Required forCommon BillTransfers



16813763“After applying this patch, when editable common bill iscreated, the new created child bill components WHO columnswill be pointed to current process data.”

Required forCommon BillTransfers

21538392

Known issue:

“BOM_BO_PUB.PROCESS_BOM API Does not Set Locators onComponents (Doc ID 2078778.1)”

Patch description:

“After applying the patch, BOM API'bom_bo_pub.process_bom' allows to set locators forcomponents even if the respective sub-inventory is of 'NoLocator' type. It throws a warning message'BOM_NO_LOCATOR_CONTROL' similar to BOM form.”

Recommended forBOM transfers



Patch list for ISG connector

Caution:

Applying the Patch 15889703:R12.OWF.B will disable auditing from SOA Monitor for APIFND_WEB_SEC. You should also disable this for T4O API T4O_WEB_SEC_1140 by adding it to theXML file $JAVA_TOP/oracle/apps/fnd/soa/util/SecurityRisks.xml (delivered with the patch):

Original Content:

<?xml version="1.0"?><Security> <SecurityRisk> <PasswordSecurityRisk> <ListOfAPIS>FND_WEB_SEC</ListOfAPIS> </PasswordSecurityRisk> </SecurityRisk></Security>

Change it to:

<?xml version="1.0"?><Security> <SecurityRisk> <PasswordSecurityRisk> <ListOfAPIS>FND_WEB_SEC</ListOfAPIS> <ListOfAPIS>T4O_WEB_SEC_1140</ListOfAPIS> </PasswordSecurityRisk> </SecurityRisk></Security>

Patch Number Patch Description

Required /Recommended for

ISG

8459663“MANDATORY CONSOLIDATED ONE-OFF FIXES FOR ISG ON TOPOF 12.1.1” (see note “Oracle E-Business Suite Integrated SOAGateway 12.1.1 Consolidated One-Off (Doc ID 815196.1)”)

Required

14659883“OTA (OAFM) IS USING OJDBC14DMS.JAR INSTEAD OFAPPSBORG.ZIP FOR JDBC CONNECTIONS”

Required

18855074“MERGE REQUEST ON TOP OF 10.1.3.5.1 FOR BUGS 1830176213000723 18710285”

Required

8407693“ISG: SERVICE GENERATION FAILURE - JAVA COMPILER COULDNOT BE FOUND”

Required





ISG

8916358“SERVICE TIMEOUT WHEN INVOKING SERVICES DEPLOYED TOINTEGRATED SOA GATEWAY”

Required

8607523“MERGE LABEL REQUEST ON TOP OF 10.1.3.4 FOR BUGS7393405 7027175 6862461”

Required

9905933“PLSQL INTERFACE : CREATE,ADD OR UPDATE BOM BUSINESSENTITIES (BOM_BO_PUB) CANNOT”

Required

11688301“1OFF: CONSOLIDATED ISG PATCH FOR 12.1.X” (-> Pre-req forPatch 15889703)

Required

15889703 “PASSWORD IS DISPLAYED ON THE SERVICE PAYLOAD” Required

15914125“MERGE REQUEST ON TOP OF 10.1.3.5.1 FOR BUGS 91871899668283 13248533”

Required

11831517“WHEN WSDL IS GENERATED THE CLASS CREATED SHOWS UPWITH A NUMBER OR _”

Required

9349321“ISSUE WITH ITEM BULK LOAD IN ORACLE PRODUCT HUB PIP2.4”

Recommended

9446625“1OFF:8995921:12.1.1:12.1.1:PERF : LOGINMODULESPERFORMANCE ISSUE”

Recommended

9070077“1OFF:9045280:12.1.1:INVOKING A WEB SERVICE REQUIRESNLS LANG WHEN IT SHOULD BE OPTIONAL”

Recommended

9153106“IREP_PARSER.PL EXITS WITH GETPWUID FUNCTION ISUNIMPLEMENTED IN PARSER.PM”

Recommended

9004712“ONE-OFF FOR IREP PARSER ON TOP OF EBS R12.1.1 (see note“Oracle E-Business Suite Integrated SOA Gateway 12.1.1Integration Repository Parser One-Off (Doc ID 946192.1)”)”

Recommended

Toubleshooting

• If you're getting one of the following error messages when connecting to Oracle EBS via ISG, pleasefollow the instructions in Oracle Support note “SAML Authentication on EBS R12 Gateway is Failingwith ORABPEL-11622 (Doc ID 1506467.1)”:"ORABPEL-11622""Missing class: oracle.tip.adapter.fw.log.ISGLogObjectPerRequest"




2.3.2 Required Patches for EBS 12.2

Patch list, irrespective of configured Oracle EBS connector type

Caution:

• We strongly recommend installing the latest available AD and TXK Release Update Packs onyour system; please consult the Oracle Support note "Applying the Latest AD and TXK ReleaseUpdate Packs to Oracle E-Business Suite Release 12.2 (Doc ID 1617461.1)".

Minimum required AD and TXK Release Update Packs:

• R12.AD.C.Delta.4

• R12.TXK.C.Delta.4

Patch Number Known Issue/Patch Description

Required /Recommended

(depending onfunctionality)

18710762 Known issue:

“PROCESS_ECO Implements Revised Item Operations Directly(Doc ID 1905686.1)”

Patch description:

“After applying this patch, eco api will not implement revisedoperations immediately without a call to eco implementation

concurrent program.”

Required forhandling revisedoperations on an

ECO


“BOM_BO_PUB.PROCESS_BOM API Does Not Return /CompleteIf The Bill of Materials BOM Is Open In Oracle Forms

BOMFDBOM.fmb (Doc ID 2032248.1)”

Patch description:

„After applying this patch, BOM form will not create locks onBOM_STRUCTURES_B table.”

Required for BOMtransfers and

Routing transfers


“Bug 25306832 : PROCESS_ECO CLEARS VALUE FORCHANGE_DESCRIPTION SITTING ON REVISED ITEM”

Patch description:

“After applying the patch, ECO Open Interface populates'Change Description' of a revised item in an ECO.”





Patch list for ISG connector



ISG


ISG cannot generate and deploy package FND_WEB_SEC dueto wrong annotations.

Patch description:

“Post 12.2.3 HASH PROJECT Rollup”

Recommended

Troubleshooting

• If you get the error message "INV_IOI_NON_REL_CATG" when trying to delete the catalog group (bypassing NULL to parameter P_ITEM_CATALOG_GROUP_ID in call ofEGO_ITEM_PUB.PROCESS_ITEM), this probably occurs due to an incorrect setup of profile optionEnable PIM for Telco Features. In order to solve this, change the value of profile optionEnable PIM for Telco Features from Yes to No. See the Oracle Support note "Get ErrorINV_IOI_NON_REL_CATG When Try To Create Item (Doc ID 1595998.1)" for details.

• Patch 17694742: If you already tried to generate the WSDL for package FND_WEB_SEC before thepatch has been installed, there may be a corrupt state of this package in ISG. In this case, you need toperform the following steps after the patch has been installed:

• Execute the following commands in order to undeploy and reset the package FND_WEB_SEC in ISGvia script:

ant -f $JAVA_TOP/oracle/apps/fnd/isg/ant/isgDesigner.xml -DdbcFile=/opt/oracle/VIS/fs1/inst/apps/VIS_ebs5/appl/fnd/12.0.0/secure/VIS.dbc -Dactions="undeploy" -DirepNames="FND_WEB_SEC"

ant -f $JAVA_TOP/oracle/apps/fnd/isg/ant/isgDesigner.xml -DdbcFile=/opt/oracle/VIS/fs1/inst/apps/VIS_ebs5/appl/fnd/12.0.0/secure/VIS.dbc -Dactions="reset" -DirepNames="FND_WEB_SEC"

• Regenerate and deploy package FND_WEB_SEC.




3. T4O Application - InstallationInstructions

3.1 Introduction

Caution:

Before proceeding with the following chapters, make sure that your Oracle EBS system meets therequirements described in chapter Oracle EBS Software Requirements to Run T4O.

The T4O software delivery contains a T4O Application Installation Package that comprises the followingOracle EBS extensions:

• A series of extended PL/SQL functions, e.g. for object read/write purposes

• Language dependent messages, e.g. for error handling

• T4O scripts for setting up own configured schema XXTO:

• The T4O Z-Table enhancement is loaded into XXTO schema.

• For JDBC, T4O connects to own XXTO schema instead of connecting to the generic APPS schema.

• ISG specific extensions:

• Integration Repository loader (iLDT) files for integration of T4O interfaces into the OracleIntegration Repository

• JDBC specific extensions:

• T4O responsibility and menu templates for setting up function security

• Database objects for T4O Z-Table enhancement that is used to import objects from Oracle EBS toTeamcenter (see chapter Set-up for Triggering Data Transfer from Oracle EBS)

In order to integrate those parts of the T4O Application, please find the appropriate installation package(t4o_apps_install_<ebs_vers>.zip) for one of the supported Oracle EBS versions in directory:

<T4O_ROOT>/var/template/t4oebs/EBS

For more information about the content of the installation package, see chapter T4O ApplicationInstallation Package Content .


Since V10.1.3, T4O provides support for EBS 12.2. For an overview of EBS 12.2 specifics in respect to theinstallation process, refer to chapter Overview of Oracle EBS 12.2 Specifics. Anyhow, the followingchapters will highlight any differences between the two Oracle EBS versions 12.1 and 12.2 whereappropriate.

For a new T4O Application installation, find the required installation steps in the following chapter:

T4O Application Installation Steps

If you need to upgrade to T4O 18.1 from an older version, proceed with the following chapter instead:

T4O Application Upgrade Steps

3.2 T4O Application Installation Package Content

The T4O Application Installation Package has the following directory and file structure:

Caution:

T4O V18.1 introduces new PL/SQL package versions with a new version suffix _1140 (e.g.T4O_ITEM_1140).

• Subdirectory xxto/<ebs_vers>/patch/115/fndload/jdbc:Contains all loader files (LDT) for uploading T4O responsibility and menu templates that are necessaryfor the JDBC connector:

• t4o_usr_menu.ldt

• t4o_usr_resp.ldt

• t4o_read_only_usr_menu.ldt

• t4o_read_only_usr_resp.ldt

• Subdirectory xxto/<ebs_vers>/patch/115/fndload/isg:Contains all T4O Integration Repository loader files (iLDT) that are necessary for ISG connector, e.g.(list is not complete!):

• T4OBASEUTILS_pls.ildt

• T4OWEBSECS_pls.ildt

• T4OITEMS_pls.ildt

• T4OBOMS_pls.ildt

3. T4O Application - Installation Instructions


• ...

• Subdirectory xxto/<ebs_vers>/patch/115/sql:Contains all scripts for loading and dropping T4O database objects:

• Generic installation scripts:

■ T4O_XXTO_Install.sql

■ T4O_XXTO_Pkg_Load.sql

• Script for creating the custom XXTO schema:

■ T4O_XXTO_Schema_Create.sql

• Scripts for setting up required grants and synonyms:

■ T4O_XXTO_Grants_Load.sql

■ T4O_XXTO_Synonyms_Load.sql

■ T4O_XXTO_BASE_GRANTS.sql

■ T4O_XXTO_BASE_SYNONYMS.sql

■ T4O_XXTO_MODEL_GRANTS.sql

■ T4O_XXTO_MODEL_SYNONYMS.sql

■ T4O_APPS_Grants.sql

■ T4O_APPS_Synonyms.sql

• Generic cleanup script:

■ T4O_XXTO_Cleanup.sql

• PL/SQL source files for loading T4O PL/SQL packages, e.g. (list is not complete!):

■ T4OBASEUTILS.pls

■ T4OBASEUTILB.pls

■ T4OWEBSECS.pls

■ T4OWEBSECB.pls

T4O Application Installation Package Content


■ T4OITEMS.pls

■ T4OITEMB.pls

■ T4OBOMS.pls

■ T4OBOMB.pls

■ ...

• SQL scripts for loading and removing T4O Wrappers for JDBC:

■ T4O_BASE_WRAPPERS.sql

■ T4O_BASE_DROPPERS.sql

■ T4O_MODEL_WRAPPERS.sql

■ T4O_MODEL_DROPPERS.sql

• SQL scripts for loading Z-Table and trigger templates:

■ T4O_ZPTC_TBL.sql

■ T4O_ZPTC_ITEM_TRG_TMPL.sql

■ T4O_ZPTC_BOM_TRG_TMPL.sql

■ T4O_ZPTC_ECO_TRG_TMPL.sql

• SQL scripts for installation error handling:

■ T4O_Cross_Ref_Not_Exists.sql

■ T4O_App_Short_Name_Not_Exists.sql

• Script for removing T4O language dependent messages:

■ T4O_Mesg_Delete.sql

• Subdirectory lang contains all SQL scripts for loading language dependent messages:

■ T4O_Mesg_Load_<lang>.sql (e.g. T4O_Mesg_Load_en_US.sql)



• Subdirectory doc contains all SQL scripts for loading the DB objects of the module DocumentAttachments. This module is part of the T4O 18.1 base installation (when executing the T4Oinstallation script T4O_XXTO_Install.sql).

• Subdirectory quality contains all SQL scripts for loading the DB objects of the module Quality/Collection Plans. This module is part of the T4O 18.1 base installation (when executing the T4Oinstallation script T4O_XXTO_Install.sql).

• EBS 12.2 specific scripts for online patching capability

■ T4O_Prepare_Seed_Tables.sql

■ T4O_XXTO_Enable_Editions.sql

3.3 Overview of Oracle EBS 12.2 Specifics

The T4O Application installation process takes the following EBS 12.2 key features into account:

• Online Patching/Edition-based redefinition

• Application registration via AD Splicer (adsplice) utility

To conform to those EBS 12.2 features, the following main components of the T4O Applicationinstallation process needed to be adapted:

• For a production environment, most of the T4O installation process is performed during an onlinepatching cycle.

• The application is registered via adsplice instead of using the Applications window as in olderversions.

A full list of changes of the T4O Application for EBS 12.2 introduced with T4O V10.1.3 can be foundhere:

• The application name has been changed from T4O to XXTO according to the recommendation in themanual “Oracle E-Business Suite Developer’s Guide Release 12.2”.

• The schema name has been changed from T4O_RST to XXTO (for adsplice reasons; needs to be equalto the application name).

• Schema XXTO is created by adsplice instead of T4O install script.

• Schema XXTO is edition enabled in order to support EBS 12.2 Online Patching.

Overview of Oracle EBS 12.2 Specifics


http://docs.oracle.com/cd/E26401_01/doc.122/e22961/T302934T303723.htm

• The XXTO application is registered via adsplice instead of using the Applications window as in olderversions. This is necessary in order to comply with EBS 12.2 standards; see the following OracleSupport note:"Developing and Deploying Customizations in Oracle E-Business Suite Release 12.2 (Doc ID1577661.1)"

• Editioning view T4O_ZPTC_TBL_1140# is added to XXTO schema for Online Patching reasons.

• Schema XXTO has same privileges as the old T4O_RST schema plus grant for CREATE VIEW (this isnecessary to create the editioning view T4O_ZPTC_TBL_1140# for the Z-Table enhancement, seeabove).

• For a production environment, the whole T4O installation scenario is performed within an onlinepatching cycle.

• T4O entries have to be added to the custom synchronization driver file for file synchronizationreasons.

3.4 T4O Application Installation Steps

Please follow the installation steps described in the following chapters in order to get the T4OApplication integrated into Oracle Applications (in that order):

1. Perform the installation steps that are necessary regardless of the used Oracle EBS connector type(JDBC or ISG), as described in chapter Common Installation Steps for JDBC and ISG

2. Afterwards, switch to one of the following chapters, depending on your configured databaseconnector:

• Chapter JDBC Specific Installation Steps for JDBC

• Chapter ISG Specific Installation Steps for ISG

If you need to install T4O for both connector types, as you want to be able to switch between theboth, follow the instructions of both chapters (the order doesn’t matter).

3. In order to complete the installation, follow the post installation steps, as described in chapter PostInstallation Steps





https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=178214936198885&id=1577661.1&_adf.ctrl-state=amwnzbff5_203#S3

https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=178214936198885&id=1577661.1&_adf.ctrl-state=amwnzbff5_203#S3

3.4.1 Common Installation Steps for JDBC and ISG

Caution:

EBS 12.2 only:

The following steps for registering the T4O application (running the adsplice utility) and uploadingT4O database objects will be executed within an online patching cycle. We recommendfollowing this procedure when installing T4O into a production environment; see the followingsections in Oracle Support note “Developing and Deploying Customizations in Oracle E-BusinessSuite Release 12.2 (Doc ID 1577661.1)”for details:

“Section 5.1: Setting Up a Production Environment”

“Section 5.2: Deploying Customizations on a Production Environment”

When installing T4O into a development environment, you may prefer to perform all of thefollowing steps in the run edition file system instead of the patch edition file system.

Perform the following basic installation steps (JDBC + ISG):

1. EBS 12.2 only:Prepare an online patching cycle; see chapter: Prepare Online Patching Cycle (EBS 12.2)The following steps for loading the T4O application into the database are executed in the patchenvironment.

2. Register the T4O application:

• EBS 12.1:Register the T4O application using the Applications window; see chapter: Register T4OApplication (EBS 12.1)

• EBS 12.2:Register the T4O application using the Oracle AD Splicer (adsplice) utility; see chapter: RegisterT4O Application (EBS 12.2)

3. Extract the content of the T4O Application installation package; see chapter: Extract InstallationPackage Content

4. Execute the T4O installation script; see chapter: Execute the T4O Installation Script

5. EBS 12.2 only:Adapt the custom synchronization driver file; see chapter: Adapt the Custom SynchronizationDriver File (EBS 12.2)

6. EBS 12.2 only:Complete the online patching cycle; see chapter: Complete Online Patching Cycle (EBS 12.2)

7. Assign a person to all T4O users; see chapter: Assign Person to FND User

Common Installation Steps for JDBC and ISG



3.4.1.1 Prepare Online Patching Cycle (EBS 12.2)

Perform the following steps in order to prepare an online patching cycle for an EBS 12.2:

• Run the adop prepare phase.Example:

<INSTALL_BASE>/fs_ne/EBSapps/appl/ad/bin/adop phase=prepare

Remember that the adop utility always runs from the run file system.For more information about the adop utility, consult the “Oracle E-Business Suite Maintenance Guide”.

• Connect to the patch file system.Example:

. <INSTALL_BASE>/EBSapps.env patch

Return to common installation steps

3.4.1.2 Register T4O Application (EBS 12.1)

Register the T4O Application (default: XXTO) via the Applications window (e.g. System Administrator ->Application -> Register) using the following attribute values:

Caution:

The following values for attributes Application and Short Name need to be unique in yoursystem!

If in your system, the above values are already in use for any none T4O application, please useother values that are available. Also consider the recommendation below concerning install scriptT4O_XXTO_Install.sql, in that case!

• Application: Teamcenter Gateway For Oracle EBS

• Short Name: XXTOWe strongly recommend specifying the default value XXTO here.However, if for some reasons you need to adapt that default value to any custom name, this ispossible since V11.2.3. But in that case, be aware you need to specify the same value when beingprompted for the T4O application short name during execution of the install scriptT4O_XXTO_Install.sql (see step Execute the T4O Installation Script).

• Basepath: XXTO_TOP

• Description: Integration Solution between Teamcenter and Oracle EBS




3.4.1.3 Register T4O Application (EBS 12.2)

Register the T4O application using the Oracle AD Splicer (adsplice) utility as described in Oracle Supportnote “Creating a Custom Application in Oracle E-Business Suite Release 12.2 (Doc ID 1577707.1)” (inpatch environment).

Follow the steps described in “Section 1: Create A Custom Application Using adsplice”

After a successful run of adsplice, the T4O schema XXTO is created and corresponding T4O applicationXXTO is registered.

When editing the three text files izuprod.txt, izuterr.txt and newprods.txt, please stick to the followingT4O specific instructions:

• Be aware to copy the three text files to the $APPL_TOP/admin directory on the patch file system andalso invoke adsplice from the patch environment.

• Generally, for T4O application registration, adsplice should be run with the following input data:Oracle User/Schema Name: XXTOApplication Short Name: XXTOApplication Name: Teamcenter Gateway for Oracle EBSApplication ID: 50440We strongly recommend using the default value XXTO for the application short name!However, if for some special reasons you need to adapt that default value to any custom name, this ispossible since T4O V11.2.3. But in that case, you need to take care of the following:

Register T4O Application (EBS 12.2)



• You need to specify the same value when being prompted for the T4O application short nameduring execution of the install script T4O_XXTO_Install.sql (see step Execute the T4O InstallationScript).

• You need to distinguish between schema name and application short name when editing the threetext files below.

Caution:

The schema name needs to be XXTO and can’t be changed!



Caution:

The values listed above need to be unique in your system!

Therefore, before running adsplice with adapted text files, you need to make sure that thosevalues are not yet in use by executing the following SQL queries:

• Check if there already exists a schema XXTO:

SELECT DECODE(COUNT ,0, 'AVAILABLE', 'IN USE') StatusFROM(SELECT COUNT(*) AS COUNTFROM FND_ORACLE_USERIDWHERE ORACLE_USERNAME= 'XXTO');

→ Query should return AVAILABLE!

→ If the schema XXTO is in use for any none T4O application, please contact our hotline!Don’t proceed with running adsplice in that case!

• Check if there already exists an application short name XXTO:

SELECT DECODE(COUNT ,0, 'AVAILABLE', 'IN USE') StatusFROM(SELECT COUNT(*) AS COUNTFROM FND_APPLICATIONWHERE APPLICATION_SHORT_NAME = 'XXTO');


→ If the application short name XXTO is in use for any none T4O application, please useanother name which is available when editing below text files. But also consider the aboverecommendation!

• Check if application name Teamcenter Gateway for Oracle EBS already exists:

SELECT DECODE(COUNT ,0, 'AVAILABLE', 'IN USE') StatusFROM(SELECT COUNT(*) AS COUNTFROM FND_APPLICATION_TLWHERE APPLICATION_NAME = 'Teamcenter Gateway for Oracle EBS');


→ If the application name Teamcenter Gateway for Oracle EBS is in use for any noneT4O application, please use another name which is available when editing below text files.

• Check if application ID 55440 already exists:

SELECT DECODE(COUNT ,0, 'AVAILABLE', 'IN USE') StatusFROM(SELECT COUNT(*) AS COUNT FROM(SELECT 'x' FROM FND_ORACLE_USERIDWHERE ORACLE_ID= 50440UNIONSELECT 'x' FROM FND_APPLICATIONWHERE APPLICATION_ID= 50440unionSELECT 'x' FROM FND_PRODUCT_INSTALLATIONSWHERE APPLICATION_ID = 50440));


→ If the application ID 55440 is in use for any none T4O application, please use another IDwhich is available when editing below text files.



• When renaming text files izuprod.txt and izuterr.txt, use the T4O application short name xxto for<CUSTOM MODULE>:xxtoprod.txtxxtoterr.txt

Caution:

If using a custom application short name (other than XXTO, which is not recommended), youalso need to specify that custom value for <CUSTOM MODULE> in the file names.

• When editing the file newprods.txt, consider the following (see above caution!):

• Set the product (application short name) to XXTO:product=xxto

• Set the oracle_schema to xxto:oracle_schema=xxto

Example of adapted file newprods.txt:

product=xxtobase_product_top=*APPL_TOP*oracle_schema=xxtosizing_factor=100main_tspace=USER_DATAindex_tspace=USER_IDXtemp_tspace=TEMPdefault_tspace=USER_DATA

Caution:

• If using a custom application short name (other than XXTO, which is not recommended), youalso need to specify that custom value for the setting product here (but the settingoracle_schema needs to be XXTO!)

• If you’re using the new OATM tablespace model (as you initially installed your system withRapid Install 11.5.10 or later), leave the tablespace settings in newprods.txt unchanged!

• If you’re still using the old OFA tablespace model (as your system was upgraded to release11.5.10 from a previous version of release 11i), you need to consider the following:

Create two tablespaces for the T4O product XXTO, one for the product tables and another forthe product indexes (see “Applications DBA System Maintenance Tasks and Tools” in “OracleE-Business Suite Maintenance Guide” and “Tablespace Management” in “Oracle E-BusinessSuite Concepts”).

Set respective tablespace names for main_tspace and index_tspace in file newprods.txt.



• When editing the file xxtoprod.txt, consider the following (see above caution!):

• Replace all occurrences of izu by xxto and all occurrences of IZU by XXTO (case sensitive!).

• Use 50440 for T4O application ID.

Caution:

If using a custom application short name (other than XXTO, which is not recommended), youalso need to specify that custom value for the following settings (but the settings defaultORACLE username and default ORACLE password need to be xxto!):

• Setting after the comment: Product specific Product ID's

• abbreviation plus shortname

• Setting after the comment: list of products and versions

• When editing the file xxtoterr.txt, consider the following (see above caution!):

• Replace all occurences of izu by xxto and all occurrences of IZU by XXTO (case sensitive!).

• Adapt the text Oracle_Support_Diagnostic_Tools to T4O application name:Teamcenter_Gateway_For_Oracle_EBS

Caution:

If using a custom application short name (other than XXTO, which is not recommended), youalso need to specify that custom value for the following setting:

• Setting after the comment: product names in this language

Follow the steps described in “Section 2: Verify Creation of Custom Product in theDatabase”

Verify if the T4O application XXTO was registered successfully by following the steps described in thatsection.

Make sure to execute the verification queries in the patch edition (e.g. using the alter session setedition statement before executing the queries)!




3.4.1.4 Extract Installation Package Content

Extract the content of the T4O Application installation package t4o_apps_install_<EBS_version>.zip tothe Oracle applications basepath $APPL_TOP (e.g. $ORACLE_BASE/VIS/apps/apps_st/appl).

Caution:

EBS 12.2 only:

Extract the content on the patch file system!


3.4.1.5 Execute the T4O Installation Script

Please check the prerequisites, before executing the T4O installation script: T4O Installation Script -Prerequisites

Then execute the installation script: T4O Installation Script - Execute

Refer to the following sections in order to get advanced information about the installation process:

• For details about the steps performed by the T4O installation script: T4O Installation Script -Performed Steps

• For information about how to handle any issues occurring during the execution of the T4Oinstallation script: T4O Installation Script - Troubleshooting

• For validating the T4O DB objects that were uploaded by the T4O installation script: T4O InstallationScript - Validation

T4O Installation Script - Prerequisites

Before executing the script, please ensure the following:

• EBS 12.1 only:Make sure that the patch for item cross references support (see chapter Required Patches) is applied,before running the installation script. The patch is also required if you’re not using item crossreferences, as it loads the new package MTL_CROSS_REFERENCES_PUB referenced by T4O.Therefore, if not applied, you would get the following error message while loading T4O PL/SQLpackages:**** ERROR: Cross References Patch is not installed in your system!**** Please install this patch before continuing with the installation!**** For details see the T4O documentation.



• All previously described steps must be completed successfully.

• Make sure that you have added T4O Application Installation directory to the SQLPATH parameterbefore executing this script. Alternatively, start sqlplus directly in the directory where this script islocated (e.g. $XXTO_TOP/patch/115/sql).

• Make sure that you have already set the Oracle E-Business Suite application environment in yourcommand shell, before executing this script. Otherwise set the connection identifiers explicitly inscript T4O_XXTO_Install.sql:

connect <DB_user>@<connection_identifier>

Examples:

connect system@VISconnect xxto@VIS/&xxto_passwordconnect apps@VIS

• By default, T4O only loads English error messages into the database. If you need to load errormessages in any other language(s) supported by T4O, you have to uncomment respective line(s) inscript T4O_XXTO_Pkg_Load.sql before running the installation script, e.g.:

@./lang/T4O_Mesg_Load_de_DE.sql

T4O Installation Script - Execute

Using an interactive tool such as SQL*Plus, execute the T4O SQL installation scriptT4O_XXTO_Install.sql.

Example:

@T4O_XXTO_Install.sql

Caution:

EBS 12.2 only:

Execute the installation script in the patch environment!

The T4O install script can be run as any user (e.g. as APPS user), as it will automatically connect torequired schemas. The script creates the custom schema XXTO and loads all T4O objects into APPS andXXTO schemas respectively.

If you want to write the script output into a log file, use the SPOOL command, before executing the T4Oinstallation script.

Execute the T4O Installation Script


Example::

SPOOL T4O_XXTO_Install.log@T4O_XXTO_Install.sql

During script execution the user is prompted for the following input:

• T4O application short name: Usually, you should leave the default value XXTO unchanged by justpressing enter. But if for some reasons you adapted the T4O application short name to any customvalue when registering the T4O application (Register T4O Application (EBS 12.1) or Register T4OApplication (EBS 12.2)), you need to enter the same value here (upper case!).Example:

• Password for SYSTEM schema: Enter the password for DB user SYSTEM. This is necessary as thescript needs to connect to the SYSTEM schema for creating (EBS 12.1 only!) and configuring the XXTOschema and granting some privileges to the XXTO user.Example:

• Tablespace name: Enter the tablespace name where T4O should install the XXTO schema includingthe T4O Z-table enhancement. As with EBS 12.1 and EBS 12.2, usually the Oracle ApplicationsTablespace Model (OATM) is used, the script should be executed with the default value “-” by justpressing enter. The value ‘-’ means that T4O will apply the default tablespace APPS_TS_TX_DATA.Example:



Caution:

If you’re still using the old OFA tablespace model instead of the new OATM tablespace model (asyour system was upgraded to Release 11.5.10 from a previous version of Release 11i), you needto consider the following:

• EBS 12.1:

Create two tablespaces for the T4O product XXTO, one for the product tables and another forthe product indexes (see “Applications DBA System Maintenance Tasks and Tools” in “OracleE-Business Suite Maintenance Guide” and “Tablespace Management” in “Oracle E-BusinessSuite Concepts”).

Pass the name of the newly created tablespace for product tables to the T4O install scriptT4O_XXTO_Install.sql when being prompted (instead of just pressing enter).

• EBS 12.2:

Pass the same tablespace name you specified for main_tspace in file newprods.txt (seeprevious step Register T4O Application (EBS 12.2)) to the T4O JDBC install scriptT4O_XXTO_Install.sql when being prompted (instead of just pressing enter).

• Password for new XXTO schema: Leave the default password “XXTO” unchanged by just pressingenter, or change the password by typing in any desired value.Example:

• Password for APPS schema: Enter the password for DB user APPS. This is necessary as the scriptneeds to connect to the APPS schema for loading T4O code objects.Example:

The T4O installation script will recompile all T4O JDBC wrapper packages (including all older versionwrappers) at the end! That way the old T4O packages won't get invalid. → This will take a few minutes!

The script only creates the XXTO schema, if it doesn’t exist yet:

• As with EBS 12.2 it is required to register an application using the AD Splicer utility (see previous stepRegister T4O Application (EBS 12.2)), the XXTO schema has already been created by AD Splicerutility when running the install script.



• However, with EBS 12.1,the XXTO schema has not been created yet when running the installationscript. Thus the installation script will create the XXTO schema in that case.


T4O Installation Script - Performed Steps

The following steps are performed by the T4O installation script:

• Connect to SYSTEM schema (prompting for password):

• EBS 12.1 only: Create the XXTO schema with default password “XXTO”

• Create basic grants for XXTO schema

• Create some additional grants for XXTO schema needed for metafile generation

• Reset the XXTO password (prompting for a new password):

• Reset the XXTO password to the value entered by the user or reset it to the default password“XXTO” if no value is entered.

Caution:

Due to the following adsplice issue, the XXTO password is reset by the T4O install script inany case (either to the default value “XXTO” or to the user’s input value):

In some cases adsplice doesn't apply the default password as specified in xxtoprod.txt, butuses an own unknown password.

• Connect to the new XXTO schema (using either the default password “XXTO” or the onespecified by the user):

• Create the Z-Table (T4O_ZPTC_TBL_1140).

• Connect to APPS schema (prompting for password):

• Create APPS synonym for Z-Table (XXTO.T4O_ZPTC_TBL_1140).

• Load T4O PL/SQL packages (T4O_BASE_UTIL_1140, T4O_WEB_SEC_1140, T4O_ITEM_1140 …)including all T4O JDBC wrapper packages.

• Load T4O types and language dependent error messages.

• Grant access on just created T4O PL/SQL packages and types in APPS schema to XXTO schema.



• Connect to XXTO schema (second time – again using either the default password “XXTO” or theone specified by the user):

• Create XXTO synonyms for T4O packages and types in APPS schema.

• Grant access on Z-Table (XXTO.T4O_ZPTC_TBL_1140) to APPS schema.

Be aware of the following difference between JDBC and ISG when connecting to an Oracle EBS system:

• With JDBC, no direct connection from T4O to the APPS schema is established for security reasons.Therefore, T4O uses its own custom XXTO schema to connect to.

• With ISG, T4O doesn’t connect to the XXTO schema. However, no direct connection from T4O to theAPPS schema is established either: The connection to the APPS schema is established via an OracleEBS user with the “Apps Schema Connect Role” assigned (see the Oracle manual “Integrated SOAGateway Implementation Guide” for details).


T4O Installation Script - Troubleshooting

If any error occurs during script execution, consider the following:

• Please ignore any SQL error messages for drop statements, complaining about non existing objects,e.g.:ORA-01434: private synonym to be dropped does not exist

• If an error occurred during script execution, resolve the problem and rerun the script.

• EBS 12.1 only: If you get compilation errors for package T4O_ITEM_1140, check if you have alreadyapplied the patch for item cross references support, see chapter Required Patches.


T4O Installation Script - Validation

In order to check if the just loaded T4O objects are valid, execute the following query with APPS user:

SELECT object_name, object_type, statusFROM dba_objectsWHERE owner = 'APPS' AND object_name LIKE 'T4O%_1140%';




3.4.1.6 Adapt the Custom Synchronization Driver File (EBS 12.2)

For an EBS 12.2, add entries for the T4O files to the custom synchronization driver file, in order toensure that the adop utility synchronizes those files between the run file system and the patch filesystem the next time you run the prepare phase.

Edit the custom synchronization driver file adop_sync.drv located at $APPL_TOP_NE/ad/custom byadding the following entry in the section marked by the #Begin Customization and #EndCustomization comments:

Caution:

If you want to directly copy&paste the following examples to your text editor, please remove theline breaks and make sure that there is a white space in between!

• For Unix:

rsync -zr %s_current_base%/EBSapps/appl/xxto/12.0.0/patch %s_other_base%/EBSapps/appl/xxto/12.0.0

• For Windows:

xcopy /dieqy %s_current_base%\EBSapps\appl\xxto\12.0.0\patch %s_other_base%\EBSapps\appl\xxto\12.0.0


3.4.1.7 Complete Online Patching Cycle (EBS 12.2)

In order to complete the current online patching cycle for an EBS 12.2, perform the following steps:

• Run the adop finalize phase.Example:

<INSTALL_BASE>/fs_ne/EBSapps/appl/ad/bin/adop phase=finalize

• Run the adop cutover phase.Example:

<INSTALL_BASE>/fs_ne/EBSapps/appl/ad/bin/adop phase=cutover

Remember that the adop utility always runs from the run file system.

For more information about the adop utility, consult the “Oracle E-Business Suite Maintenance Guide”.



After a successful execution of the adop cutover phase, the T4O application will be available in the runsystem.


3.4.1.8 Assign Person to FND User

Make sure that all FND users using T4O have a person assigned like in the following screenshot:

Otherwise, T4O would return an error message like the following while transferring an object (error isreturned by Oracle PL/SQL APIs, e.g. EGO_ITEM_PUB.Process_Item):

“The following user ID does not have a person ID assigned to it: 9726”

Usually, the assigned person should be an employee.

The above error will be returned, if the following query doesn’t return any rows:

SELECT party_idFROM EGO_USER_VWHERE user_id = <FND user ID>;

An example for a not allowed person assigned to the user, would be an external person. In that case thequery won’t return any rows.


3.4.2 JDBC Specific Installation Steps

Please perform the following installation steps for JDBC connector:

1. Upload the T4O responsibility and menu templates into APPS schema: Upload Responsibility andMenu Templates

2. Assign the T4O responsibilities created in previous step to all FND users who should be allowed toaccess the T4O functionality: Assign T4O Responsibilities to FND Users

Assign Person to FND User


3.4.2.1 Upload Responsibility and Menu Templates

In order to set up function security for JDBC, upload T4O responsibility and menu templates and/or yourown custom ones into APPS schema (e.g. by using the FNDLOAD utility).

For FNDLOAD utility, ensure the following, before executing the commands below:

• Change to the directory where T4O menu and responsibility templates are located (e.g. $XXTO_TOP/patch/115/fndload/jdbc).

• Make sure that you have read, write and execute permissions in the directory where you executethose commands.

• Make sure that you have already set the Oracle E-Business Suite Applications Environment in yourcommand shell, before executing those commands:

• EBS 12.1:Navigate to the Oracle $APPL_TOP directory and source the file <CONTEXT_NAME>.env/<CONTEXT_NAME>.cmd.

• EBS 12.2:Connect to the run file system:Example:

. <INSTALL_BASE>/EBSapps.env run

• EBS 12.1 only:Make sure you have already set the Java Technology Stack Environment in your command shell,before executing those commands:Navigate to the <OracleAS 10.1.3 ORACLE_HOME> directory and source the file<CONTEXT_NAME>.env/<CONTEXT_NAME>.cmd.



Caution:

• The FNDLOAD utility uses different configuration (.lct) files for menus and responsibilities:

• afsload.lct for menus

• afscursp.lct for responsibilities

• Use exactly the same FNDLOAD options as in the examples below:

• UPLOAD_MODE = REPLACE

• CUSTOM_MODE = FORCE

Be aware that the REPLACE mode for menus will clean-up any old menu entries andcompletely replace them by the ones specified in the data file (*.ldt).

T4O delivered responsibility and menu templates are only examples for setting up responsibilities/menusthat allow users/user groups to access T4O functionality. You are free to create your own responsibilities/menus that fit your specific needs.

Perform the following steps, in order to set up function security for JDBC:

• Required: Upload T4O OOTB menu templates delivered with that release.

• Optional: Set up your own custom menus.

• Required: Set up responsibilities used with T4O, choosing one of the following options:

• Upload T4O OOTB responsibility templates delivered with that release.

• Alternatively you may prefer setting up your own custom responsibilities.

In order to get feedback if any error occurred during the upload with FNDLOD utility, check the log filesin current directory.

For more details on FNDLOAD utility, consult the Oracle Support note “Tips and Examples UsingFNDLOAD (Doc ID 735338.1)”.

Upload Responsibility and Menu Templates



Upload T4O OOTB menu templates (required)

You need to upload the OOTB T4O menu templates, regardless whether you use your own customresponsibilities and menus or not! This is required as the menu templates also upload the T4O menufunctions (additionally to the T4O menus).

For each T4O menu template, execute the following command in a command shell:

$FND_TOP/bin/FNDLOAD <db_user>/<password>@<instance_name> 0 Y\UPLOAD $FND_TOP/patch/115/import/afsload.lct <menu_ldt_file>\WARNING=YES UPLOAD_MODE=REPLACE CUSTOM_MODE=FORCE

Example for T4O menus upload:

$FND_TOP/bin/FNDLOAD apps/apps@VIS 0 Y UPLOAD\$FND_TOP/patch/115/import/afsload.lct t4o_usr_menu.ldt WARNING=YES\UPLOAD_MODE=REPLACE CUSTOM_MODE=FORCE

$FND_TOP/bin/FNDLOAD apps/apps@VIS 0 Y UPLOAD\$FND_TOP/patch/115/import/afsload.lct t4o_read_only_usr_menu.ldt\WARNING=YES UPLOAD_MODE=REPLACE CUSTOM_MODE=FORCE

Once T4O menus have been uploaded successfully, you should find them in Oracle Forms UI:



Set up your own custom menus (optional)

Instead of using the OOTB T4O menu templates, you may prefer setting up your own custom menus andincluding T4O menu functions as needed for your specific use cases.

In that case, please make sure to add the required functions (see chapters T4O Extended PL/SQLFunctions Called by T4O and Oracle EBS PL/SQL APIs Called by T4O) to respective menus.

Depending on what T4O should do in your installation, you do not need to make all those functionsavailable to T4O menus and responsibilities. Permissions need to be set according to the object typesand functions that are to be handled via T4O.

In order to set up your own custom menus, choose one of the following options:

• Create your own menu loader files (*.ldt) and upload them via the FNDLOAD utility (executing thecommand above). You may use the T4O OOTB templates as a guideline.

• Manually create your menus using form “Menus” in Oracle Forms UI.Add the T4O menu functions that were uploaded with previous step (e.g. search for functions startingwith "TP").

Upload T4O OOTB responsibility templates (optional)

If not using your own custom responsibilities, upload the OOTB T4O responsibility templates.

For each T4O responsibility template, execute the following command in a command shell:

$FND_TOP/bin/FNDLOAD <db_user>/<password>@<instance_name> 0 Y\UPLOAD $FND_TOP/patch/115/import/afscursp.lct <resp_ldt_file>\WARNING=YES UPLOAD_MODE=REPLACE CUSTOM_MODE=FORCE

Example for T4O responsibilities upload:

$FND_TOP/bin/FNDLOAD apps/apps@VIS 0 Y UPLOAD\$FND_TOP/patch/115/import/afscursp.lct t4o_usr_resp.ldt WARNING=YES\UPLOAD_MODE=REPLACE CUSTOM_MODE=FORCE

$FND_TOP/bin/FNDLOAD apps/apps@VIS 0 Y UPLOAD\$FND_TOP/patch/115/import/afscursp.lct t4o_read_only_usr_resp.ldt\WARNING=YES UPLOAD_MODE=REPLACE CUSTOM_MODE=FORCE

Once T4O responsibilities have been uploaded successfully, you should find them in Oracle Forms UI:

Upload Responsibility and Menu Templates


Set up your own custom responsibilities (optional)

Instead of using the OOTB T4O responsibility templates, you may prefer setting up your own customresponsibilities and including your own custom menus as needed for your specific use cases.

In order to set up your own custom responsibilities, choose one of the following options:

• Create your own responsibility loader files (*.ldt) and upload them via the FNDLOAD utility (executingthe command above). You may use the T4O OOTB templates as a guideline.

• Manually create your responsibilities using form “Responsibilities” in Oracle Forms UI.Add your custom menus to those responsibilities.

Return to JDBC specific installation steps

3.4.2.2 Assign T4O Responsibilities to FND Users

Using the Users window (e.g. System Administrator -> Security -> User -> Define), assign the T4Oresponsibilities created in previous step to all FND users who should be allowed to access the T4Ofunctionality, e.g.:



Return to JDBC specific installation steps

3.4.3 ISG Specific Installation Steps

Please perform the following installation steps for ISG connector:

1. Publish T4O integration interfaces to the Oracle Integration Repository: Publish T4O IntegrationInterfaces

2. EBS 12.2 only:Specify interaction patterns: Specify Interaction Patterns (EBS 12.2)

3. Generate SOAP web services for all T4O Integration Interfaces: Generate Web Services

4. EBS 12.2 only:Select an authentication type: Select an Authentication Type (EBS 12.2)

5. Deploy all generated T4O web services: Deploy Web Services

6. Create security grants for all T4O extended PL/SQL functions: Create Security Grants

ISG Specific Installation Steps


7. Restart the application server: Restart the Application Server

8. Clear the Oracle EBS cache: Clear the Oracle EBS Cache

3.4.3.1 Publish T4O Integration Interfaces

Publish T4O integration interfaces by uploading all T4O iLDT files to the Oracle Integration Repository.

Before executing the commands below, ensure the following:

• Change to the directory where T4O iLDT files are located (e.g. $XXTO_TOP/patch/115/fndload/isg).

• Make sure that you have read, write and execute permissions in the directory where you execute thiscommand.

• Make sure that you have already set the Oracle E-Business Suite Applications Environment in yourcommand shell, before executing this command:

• EBS 12.1:Navigate to the Oracle $APPL_TOP directory and source the file <CONTEXT_NAME>.env/<CONTEXT_NAME>.cmd.

• EBS 12.2:Connect to the run file system:Example:

. <INSTALL_BASE>/EBSapps.env run

• EBS 12.1 only:Make sure you have already set the Java Technology Stack Environment in your command shell,before executing those commands:Navigate to the <OracleAS 10.1.3 ORACLE_HOME> directory and source the file<CONTEXT_NAME>.env/<CONTEXT_NAME>.cmd.

• If you adapted the T4O application short name in previous steps to a custom value (instead of usingthe recommended default value XXTO), you need to consider the following:Before executing the following command, edit each T4O iLDT file by replacing all occurrences of XXTOby your custom application short name (same as specified in previous steps, but lower case)



Caution:

Use exactly the same FNDLOAD options as in the examples above:

• UPLOAD_MODE = REPLACE

• CUSTOM_MODE = FORCE

For each T4O iLDT file, execute the following command in a command shell:

$FND_TOP/bin/FNDLOAD <db_user>/<password>@<instance_name> 0 Y\UPLOAD $FND_TOP/patch/115/import/wfirep.lct <ildt_file>\WARNING=YES UPLOAD_MODE=REPLACE CUSTOM_MODE=FORCE

Example:

$FND_TOP/bin/FNDLOAD apps/apps@VIS 0 Y UPLOAD\$FND_TOP/patch/115/import/wfirep.lct T4OBASEUTILS_pls.ildt\WARNING=YES UPLOAD_MODE=REPLACE CUSTOM_MODE=FORCE

Once all T4O source files have been uploaded successfully, they will be displayed in the SOA IntegrationRepository user interface like the following:

• EBS 12.1:

Publish T4O Integration Interfaces


• EBS 12.2:

Return to ISG specific installation steps

3.4.3.2 Specify Interaction Patterns (EBS 12.2)

On the “SOAP Web Service” tab in Integration Repository user interface, specify interaction patterns(synchronous!) for desired methods to be exposed as services.

An interaction pattern can be specified at method level for one or more methods, or at the interfacelevel for all methods:


3.4.3.3 Generate Web Services

In Integration Repository user interface, generate SOAP web services for all T4O Integration Interfaces:



EBS 12.1:

EBS 12.2:

Instead of generating the web services in the Integration Repository user interface as described above,you may prefer to use the following scripts in order to generate the web services from back end:

• EBS 12.1:soagenerate.sh or soagenerate.cmd respectivelySee Oracle Support note “How Can One Batch Deploy Or Generate SOA Webservices From Backend?(Doc ID 1495551.1)”

• EBS 12.2:isgDesigner.xmlSee Oracle Support note “How To Perform Actions On API's From Backend in R12.2? (Doc ID1664395.1)”


3.4.3.4 Select an Authentication Type (EBS 12.2)

Before deploying the web service, select an authentication type:

Select an Authentication Type (EBS 12.2)





3.4.3.5 Deploy Web Services

In Integration Repository user interface, deploy all generated T4O web services by clicking the “Deploy”button:

EBS 12.1:

EBS 12.1:

Instead of deploying the web services in the Integration Repository user interface as described above,you may prefer to use script soadeploy.sh (or soadeploy.cmd respectively) in order to deploy the webservices from back end. Please consult the following Oracle Support note in that case:

“How Can One Batch Deploy Or Generate SOA Webservices From Backend? (Doc ID 1495551.1)”


3.4.3.6 Create Security Grants

Create security grants, by authorizing an appropriate user, a user group or all users to access permissionsfor all T4O extended PL/SQL functions (see chapter T4O Extended PL/SQL Functions Called by T4O).Select respective PL/SQL functions and click the “Create Grant” button:




EBS 12.1:

EBS 12.2:

Create Security Grants


Caution:

• The following functions are called by T4O, before the Oracle EBS login has been established –thus they are never called with the normal Oracle EBS user (logged in via T4O):

• Check if provided user and password are valid

(FND_WEB_SEC.VALIDATE_LOGIN, T4O_WEB_SEC_1140.TP_VALIDATE_LOGIN)

• Obtain the responsibilities for a user trying to logon to the Oracle EBS system

(T4O_BASE_UTIL_1140.TP_GET_USER_RESPLTS)

• Retrieve information about all installed system languages

(T4O_BASE_UTIL_1140.TP_CHECK_INSTALLED_LANGUAGES)

• Get the current Oracle EBS system timestamp including time zone

(T4O_BASE_UTIL_1140.TP_GET_SYSTIMESTAMP)

• Check if a sent date is a valid G_MISS_DATE value

(T4O_BASE_UTIL_1140.TP_VALIDATE_G_MISS_DATE)

Instead of the user currently logged in, they are called with the special T4O userISG:CHECK_USER, as defined by the following mapping entry (file t4o_mapping_config_<ebssystem id>.sd; see chapter T4O Connectivity to Oracle EBS in the Teamcenter Gateway -Installation Guide for details):

set ::T4O_Defaults(ISG:CHECK_USER:$strSystemId) "sysadmin"

Therefore, for those functions, you should only grant rights to the T4O ISG:CHECK_USER,as defined in the mapping.

• EBS 12.2 only:

The “Select All” on the “Grants” tab will select the currently displayed functions only (up to tenfunctions). The “Create Grant” action then refers to only the selected functions currentlydisplayed. Therefore, if more than ten functions exist, it is necessary to navigate through allfunctions and invoke the “Create Grant” each time (-> a “Create Grant” for all functions isn’tpossible any more with EBS 12.2).






3.4.3.7 Restart the Application Server

Before the generated web services can be invoked, the application server needs to be restarted like thefollowing:

Example for EBS 12.1:

cd $INST_TOP/admin/scriptsadoafmctl.sh stopadoacorectl.sh stopadoafmctl.sh startadoacorectl.sh start

Example for EBS 12.2:

cd $ADMIN_SCRIPTS_HOMEadstpall.shadstrtal.sh


3.4.3.8 Clear the Oracle EBS Cache

Clear the Oracle EBS cache by selecting responsibility “Functional Administrator” and navigating to: CoreServices -> Caching Framework -> Global Configuration -> Clear all cache.


3.4.4 Post Installation Steps

Once you have finished the steps described in previous chapters, perform the following (in that order):

1. Required: Set up the required T4O permissions by following the steps described in chapterRequired Permissions

2. Optional: If using multi key flexfields for inventory items, ensure that your system meets therequirements as described in chapter Requirements for System Items Key Flexfield

3. Optional: If using the Z-Table functionality, upload T4O database trigger templates as described inchapter T4O Database Trigger Templates.

4. Optional: If using the Document Attachments functionality, ensure that your system meets therequirements as described in chapter Requirements for Module Document Attachments.

Restart the Application Server


5. Required: You need to configure the Oracle EBS connectivity for T4O by following the instructionsin chapter T4O Connectivity to Oracle EBS in the Teamcenter Gateway - Installation Guide.

3.5 T4O Application Upgrade Steps

Caution:

If you’re upgrading to T4O 18.1 from an older version than V10.1.3, you need to be aware of thefollowing major changes in respect of the T4O Application installation package:

• The application name has been changed from T4O to XXTO due to EBS 12.2 consistencyreasons.

• The schema name has been changed from T4O_RST to XXTO due to EBS 12.2 consistencyreasons.

• The T4O install script is no longer divided into two scripts (one for JDBC and one for ISG). Onlyone script for both connector types is shipped since T4O 10.1.3: T4O_XXTO_Install.sql

• The following new T4O responsibilities were introduced:

Teamcenter Gateway Read-Only User:

• Restricted Responsibility with access to read-only functionality

• Responsibility Key: T4O_READ_ONLY_USER

• Replaces old Tesis Inventory User (TESIS_INVENTORY_USER)

Teamcenter Gateway User::

• Comprehensive Responsibility with access to all available T4O functions

• Responsibility Key: T4O_USER

• Replaces old Tesis Inventory Super User (TESIS_INVENTORY_SUPER_USER)

Please follow the steps described in the following chapters in order to upgrade an older version of theT4O Application to version 18.1 (in that order):

1. Perform the upgrade steps that are necessary regardless of the used Oracle EBS connector type(JDBC or ISG), as described in chapter Common Upgrade Steps for JDBC and ISG

2. Afterwards switch to one of the following chapters, depending on your configured databaseconnector:




• Chapter JDBC Specific Upgrade Steps for JDBC

• Chapter ISG Specific Upgrade Steps for ISG

If you need to upgrade T4O for both connector types, as you want to be able to switch between theboth, follow the instructions of both chapters (the order doesn’t matter).

The following installation steps will highlight any differences between the two Oracle EBS versions 12.1and 12.2 where appropriate.

3.5.1 Common Upgrade Steps for JDBC and ISG

Caution:

• Any older T4O version may not work properly during the upgrade process. Thus, make sure toshut down any old T4O processes, before performing the steps described in the followingchapters!

• EBS 12.2 only:

The following steps for registering the T4O application (running the adsplice utility) anduploading T4O database objects will be executed within an online patching cycle. Werecommend following this procedure when upgrading T4O in a production environment; seethe following sections in Oracle Support note “Developing and Deploying Customizations inOracle E-Business Suite Release 12.2 (Doc ID 1577661.1)”for details:

“Section 5.1: Setting Up a Production Environment”

“Section 5.2: Deploying Customizations on a Production Environment”

When upgrading T4O into a development environment, you may prefer to perform all of thefollowing steps in the run edition file system instead of the patch edition file system.

If you are upgrading to T4O 18.1 from an older version, please perform the following steps, regardlessof the Oracle EBS connector type (JDBC or ISG):

1. EBS 12.2 only:Prepare an online patching cycle; see chapter: Prepare Online Patching Cycle (EBS 12.2)The following steps for loading the T4O application into the database are executed in the patchenvironment.

2. If you’re upgrading to T4O 18.1 from an older version than V10.1.3, you need to newly register theXXTO schema:

• EBS 12.1:Register the T4O application using the Applications window; see chapter: Register T4OApplication (EBS 12.1)

Common Upgrade Steps for JDBC and ISG



• EBS 12.2:Register the T4O application using the Oracle AD Splicer (adsplice) utility; see chapter: RegisterT4O Application (EBS 12.2)

Otherwise, if upgrading from a version >= V10.1.3, the XXTO schema should have already beenregistered with that older installation:

• EBS 12.1:This step can be skipped!

• EBS 12.2:If you need to re-register the XXTO application in that case, depends on whether you formerlyregistered it using adsplice or not:

• If not registered via adsplice (using the Applications window instead), as the old T4O versionwas originally installed on an Oracle EBS system < V12.2, you need to reregister the XXTOapplication. Re-register the XXTO application via adsplice using the same application ID(50440) and application name (XXTO). Follow the instructions described in chapter RegisterT4O Application (EBS 12.2), ignoring the fact that the validation queries return IN USE.

• If already registered via adsplice, as the old T4O version was originally installed on an EBS12.2, it’s not necessary to re-register the XXTO application. Thus skip this step in that case.

Caution:

With a T4O installation on an EBS 12.2, the XXTO application needs to be registered viaadsplice. If not yet done from an older T4O installation, you need to re-register the XXTOapplication using adsplice!

3. If you already have a subdirectory XXTO in directory $APPL_TOP from an older T4O installation,keep a backup copy of the old version files by renaming the old $APPL_TOP/xxto directory.Afterwards, extract the content of the T4O V18.1 Application installation package, as described inchapter Extract Installation Package Content.

4. Execute the T4O 18.1 base installation script (T4O_XXTO_Install.sql), as described in chapterExecute the T4O Installation Script. But consider the following for an upgrade:Before running the T4O install script, verify the following:

• Check if all patches required for T4O 18.1 are already installed (see chapter Required Patches).

• EBS 12.1 only:Make sure that the patch for item cross references support (see chapter Required Patches) isapplied, before running the installation script. The patch is also required if you're not using itemcross references, as it loads the new package MTL_CROSS_REFERENCES_PUB which isreferenced by T4O.



T4O V18.1 introduces new PL/SQL package versions (with version string “_1140”, e.g.T4O_ITEM_1140).When upgrading to T4O V18.1, the old T4O PL/SQL packages (with another version string than“_1140”) will remain in the database. Therefore, it’s possible to use T4O V18.1 and any of the olderversions in parallel.

5. Only if using ZPTC trigger templates: You need to manually rerun the T4O database triggertemplate scripts of new T4O 18.1 installation package, as described in chapter T4O DatabaseTrigger Templates.

Caution:

Be aware that the new T4O V18.1 trigger template scripts will overwrite any older versionT4O triggers in the DB, by default. Thus, when uploading the new T4O V18.1 triggertemplate scripts to the DB, you need to consider the following, depending on whether youwant to use the older T4O version(s) (< V18.1) in parallel or not:

• If using the new T4O version V18.1 alone:

• Export your existing older version trigger to a file (e.g. using SQL Developer) and mergethe content with the new V18.1 trigger template script (referencing new V18.1 PL/SQLpackage T4O_ZPTC_1140).

• Execute the (adapted) V18.1 trigger template script. Just press enter when beingprompted for the trigger version. This will replace any older version trigger (as only onetrigger should be active when using only one T4O version)!

• If using T4O version V18.1 in parallel with any older T4O version(s):

• Export your existing older version trigger to a file (e.g. using SQL Developer) and mergethe content with the new V18.1 trigger template script (referencing new V18.1 PL/SQLpackage T4O_ZPTC_1140).

• Make sure that each version specific trigger (old version(s) plus new V18.1) has aversion specific condition. Thus, adapt at least the condition of the trigger in new V18.1trigger template script, so that the trigger is initiated only for objects dedicated for thenew T4O version V18.1 (e.g. objects belonging to the organization used with new T4Oversion). Also make sure that the condition from your older version trigger in the DBonly filters objects dedicated for that older T4O version.

• Execute the (adapted) V18.1 trigger template script. Specify a version suffix like _1140when being prompted for the trigger version. This won’t replace any older versiontrigger, but upload a new “revised” trigger to the DB (trigger name including suffix_1140)!

If you're using multiple T4O versions in parallel, consider the following: For a T4O version that isn’tused any longer, make sure to deactivate corresponding “revised” trigger!

Common Upgrade Steps for JDBC and ISG


If using only one T4O version, make sure that only one trigger for the current T4O version is active!Since version V11.2.3, T4O provides a revised Z-Table. Thus, the Z-Table entries for that version aremaintained separately and are not mixed up with any older version Z-Table entries!

6. EBS 12.2 only:Make sure that the entries for the T4O files are included in the custom synchronization driver file,as described in chapter Adapt the Custom Synchronization Driver File (EBS 12.2).

7. EBS 12.2 only:Complete the online patching cycle, as described in chapter Complete Online Patching Cycle (EBS12.2).

8. Make sure that all FND users using T4O have a person assigned.

3.5.2 JDBC Specific Upgrade Steps

1. Upload the T4O 18.1 responsibility and menu templates (t4o_usr_resp.ldt,t4o_read_only_usr_resp.ldt, t4o_usr_menu.ldt and t4o_read_only_usr_menu.ldt) or your owncustom ones into APPS schema, as described in chapter Upload Responsibility and MenuTemplates.

Caution:

When uploading the menu templates, we recommend using the same upload modeREPLACE as described in that chapter. But keep in mind that this will replace the alreadyexisting T4O (“Teamcenter Gateway*”) menus. If you have done any manual changes to theold T4O menus (e.g. added some custom menu entries) in the past, consider one of thefollowing options, in order to make sure that your adaptions don’t get lost:

• Use upload mode MERGE instead of REPLACE.

• Use upload mode REPLACE and repeat the manual changes afterwards.

2. Only if upgrading from a T4O version < V10.1.3:As with T4O 10.1.3, new T4O responsibilities Teamcenter Gateway Read-Only User andTeamcenter Gateway Read-Only User were introduced, you need to assign those to all FND userswho should be allowed to access T4O functionality, see chapter Assign T4O Responsibilities toFND Users.

3. Only if upgrading from a T4O version < V10.1.3:As with T4O 10.1.3, new T4O responsibilities Teamcenter Gateway Read-Only User andTeamcenter Gateway Read-Only User were introduced, you need to newly set up organizationaccess for those new responsibilities as described in chapter Required Permissions.Otherwise, the organization access for those T4O responsibilities should have already been set upfrom an older installation, thus nothing needs to be done therefor.



4. For Oracle EBS connectivity setup, the following steps have to be repeated for your new T4Oinstallation (see chapter T4O Connectivity to Oracle EBS in the Teamcenter Gateway -Installation Guide):

• Install a JDBC driver for T4O.

• Create the stored procedure metafile.

3.5.3 ISG Specific Upgrade Steps

For ISG, perform all the steps described in chapter ISG Specific Installation Steps.

ISG Specific Upgrade Steps






4. PL/SQL Functions Called by T4O

4.1 Oracle EBS PL/SQL APIs Called by T4O

Some of the Oracle EBS PL/SQL APIs are directly called by T4O (without calling any T4O wrapper).

In general, T4O calls the following Oracle EBS PL/SQL APIs:

• FND_REQUEST.SUBMIT_REQUEST

• FND_WEB_SEC.VALIDATE_LOGIN

If you already have installed T4O (BGS + GS) following the instructions in the Teamcenter Gateway -Installation Guide, you can also use test script "MISC get PLSQL function names", in order to get an up-to-date list of all Oracle EBS PL/SQL APIs directly called by T4O. In the output refer to section "OraclePLSQL APIs":




4.2 T4O Extended PL/SQL Functions Called by T4O

With the installation of the T4O Application, several PL/SQL functions are added to the database.

For setting up function security for T4O with JDBC or ISG, you can use respective template files (*.ldt forJDBC or *.ildt for ISG), in order to get an overview of all functions T4O requires.

If you already have installed T4O (BGS + GS) following the instructions in the Teamcenter Gateway -Installation Guide, you can also use test script "MISC get PLSQL function names", in order to get a list ofall T4O extended PL/SQL functions called by T4O. In the script output refer to section "T4O extendedPLSQL functions":





T4O Extended PL/SQL Functions Called by T4O




5. Required PermissionsIn order to run T4O the following permissions need to be set up:

1. T4O access to required PL/SQL functions

2. Profile options for controlling user access rights

3. Organization access for responsibilities used with T4O

T4O access to required PL/SQL functions

T4O access to required PL/SQL functions has to be enabled. What needs to be done depends on whetheryou are using JDBC or ISG for connecting to the Oracle EBS (see chapter T4O Communication withOracle EBS):

• JDBC:If using JDBC, it is necessary to set up one or more T4O responsibilities that arrange T4O requiredfunctions into menus. Those responsibilities determine which users or groups have permissions toaccess respective functions. T4O providestemplates for loading two responsibilities:Teamcenter Gateway Read-Only User (T4O_READ_ONLY_USER): Users assigned to thisresponsibility have limited T4O permissions to only access T4O required read functions.Teamcenter Gateway User (T4O_USER): Users assigned to this responsibility have comprehensivepermissions to access all T4O required functions.Loading those templates is part of the T4O Application installation, so please see chapter UploadResponsibility and Menu Templates.Once you have set up T4O responsibilities, assign them to all FND users who should be allowed toaccess the T4O functionality (see chapter Assign T4O Responsibilities to FND Users).Depending on what T4O should do in this installation, you will not need to make all T4O requiredfunctions (see chapters T4O Extended PL/SQL Functions Called by T4O and Oracle EBS PL/SQL APIsCalled by T4O) available to T4O responsibilities. Permissions need to be set according to the objecttypes that are to be handled via T4O.T4O delivered responsibility templates are only examples for setting up responsibilities that allowusers/groups to access T4O functionality. You are free to create your own responsibilities that fit yourspecific needs.

• ISG:If using ISG, it is necessary to set grant details for each function according to the users or groups whoshould be able to access the requested functionality. Those security grants can be performed onrespective interface details page of Oracle ISG Integration Repository.Setting grant details for T4O extended PL/SQL functions (see chapter T4O Extended PL/SQLFunctions Called by T4O) is part of the T4O Application installation, so please refer to chapter CreateSecurity Grants. Additionally, you have to grant privileges for Oracle EBSPL/SQL APIs directly called byT4O (see chapter Oracle EBS PL/SQL APIs Called by T4O).


Profile options for controlling user access rights

For some of the Oracle EBS functional areas supported by T4O, you have to set up corresponding profileoptions for controlling user access rights. In order to activate those rights for T4O, set the followingprofile options to Yes for respective T4O users/user groups:

• Profile options for Oracle EBS Bills of Material and Routings:

• BOM: Standard Item Access

• BOM: Model Item Access

• BOM: Planning Item Access

• Profile options for Oracle EBS Engineering Change Orders:

• ENG: Engineering Item Change Order Access

• ENG: Standard Item Change Order Access

• ENG: Model Item Change Order Access

• ENG: Planning Item Change Order Access

Depending on what T4O should do in this installation, you will not need to set each of those profileoptions. Profile options need to be set according to the object types that are to be handled via T4O.

We recommend setting up one or more T4O user groups/responsibilities and setting respective profileoptions for those groups/responsibilities.

Organization access for responsibilities used with T4O

In order to establish organization access for responsibilities used with T4O (e.g. “Teamcenter GatewayRead-Only User” or “Teamcenter Gateway User” or any other one used with T4O), you have to linkrespective responsibilities to all those inventory organizations which should be accessible. For doing so,navigate to “Setup -> Organizations -> Organization Access” in the Inventory responsibility and add anew line for each organization:

5. Required Permissions


Remember that in Oracle EBS, if there are no assigned responsibilities for an organization, this meansthat all responsibilities can access it. In this case, don’t add such an organization to responsibilities usedwith T4O.

After you have uploaded T4O responsibilities for JDBC, those have OOTB access to only thoseorganizations that are available for all responsibilities.

If organization access is not established for responsibilities used with T4O, an error message like thefollowing will be returned:

List of used function calls

T4O provides a logfile that lists all actually used Oracle EBS function calls after they have been used.Ideally you get all permissions for the T4O user(s) during development. Then after development iscomplete, you can extract a list of functions from the log and give it to your Oracle EBS administrator tolimit the permissions for the testing phase.

In the BGS Admin GUI you will find the logfile sys/ebs_function_calls.log. It contains a list off all calledSAP functions. Please see Configure T4x BGS Using BGS Admin GUI in the Teamcenter Gateway -



Installation Guide on how to login to the Admin GUI. Please use the help function of the Admin GUI formore details.

5. Required Permissions



6. Requirements for System Items KeyFlexfieldIf you have configured multiple segments for your System Items Key Flexfield, you need to consider thefollowing:

• If you have configured more than one segment for item number in your Oracle EBS system and you’reusing an index for improving Item Interface performance, it is strongly recommended to use thenon-unique index MTL_SYSTEM_ITEMS_INTERFACE_NC1 instead of the unique indexMTL_SYSTEM_ITEMS_INTERFACE_UC1!

• Anyhow, if for any reason you need to use the unique index MTL_SYSTEM_ITEMS_INTERFACE_UC1(but see caution box below!), you would get an error like the following when trying to re-transfer anitem after an already failed transfer:“INV_ITEM_GRP.Insert_MSII_Row: Unexpexted error: ORA-00001: unique constraint(APPS.MTL_SYSTEM_ITEMS_INTERFACE_UC1) violated”In order to eliminate this error, you have to turn on the T4O rollback mechanism for item transfers bydoing the following (if using the non-unique index or no index at all, skip this!):

• Edit the package body of PL/SQL package T4O_ITEM_1140: Change the value of global constantg_Commit_On_Error_ITEM from g_TRUE to g_FALSE:

g_Commit_On_Error_ITEM VARCHAR2(1) := g_FALSE;

• Save the changes

• Recompile all T4O PL/SQL packages

With this configuration T4O will do a rollback instead of a commit in an error case. But keep in mindthat in this way, no error history will be kept in table MTL_SYSTEM_ITEMS_INTERFACE for created/updated items via T4O!

• For more information on those indexes, please visit:http://download.oracle.com/appsnet/115mfgapi.pdf - Page 439http://docs.oracle.com/cd/B40089_10/current/acrobat/120scmapi.pdf - Page 1178

• If using the unique index MTL_SYSTEM_ITEMS_INTERFACE_UC1, you need to define the structureof System Items Key Flexfield in file t4o_mapping_config_<ebs systemid>.sd, see chapter The Filet4o_mapping_config.sd in the Teamcenter Gateway for Oracle EBS - Configuration Guide fordetails.

• Regardless of the index you are using, you need to consider the following in the item data mapping:The attribute P_ITEM_NUMBER needs to be specified in correct form, comprising all segmentsseparated by the delimiter, see chapter Set Key Flex Fields for Item in the Teamcenter Gateway forOracle EBS - Configuration Guide for details.


http://download.oracle.com/appsnet/115mfgapi.pdf

http://docs.oracle.com/cd/B40089_10/current/acrobat/120scmapi.pdf




Caution:

EBS 12.1 only:

If the unique index MTL_SYSTEM_ITEMS_INTERFACE_UC1 is set up in your system, T4O needsto invoke the EGO_ITEM_PUB.PROCESS_ITEM API via segments (otherwise, the API would becalled via item number). This is why the use of unique indexMTL_SYSTEM_ITEMS_INTERFACE_UC1 together with T4O requires the installation of thefollowing patches (if not using the unique index, skip the following):

• Due to bug 14739246 in the Oracle API EGO_ITEM_PUB.PROCESS_ITEM, the following patchneeds to be applied (see chapter Required Patches):

• 14739246 (minimum 12.1.2)

As for 12.1.1 no patch is available yet, it’s not possible to use the unique indexMTL_SYSTEM_ITEMS_INTERFACE_UC1 for this version! Instead, use the nonunique indexMTL_SYSTEM_ITEMS_INTERFACE_NC1 or contact the Oracle Support in order to requestrespective patch for 12.1.1.

• Due to bug 16757608 in the Oracle API EGO_ITEM_PUB.PROCESS_ITEM, clearing optionalitem segments via T4O is only possible, if the following patch is applied (see chapter RequiredPatches):

• 16757608

6. Requirements for System Items Key Flexfield



7. Requirements for Module DocumentAttachmentsThe Document Attachments functionality is a module of T4O which supports the Oracle E-Business Suitefeature “Attachments”. The attachments feature enables users to relate unstructured data to almost anybusiness object (Item, BOM, ECO and Routing) in the Oracle EBS. With T4O it is possible to maintainthose attachments from within TC. The following Oracle EBS datatypes are supported by the T4Ofeature:

• Short Text (DATATYPE_ID=1 in table FND_DOCUMENTS):Text stored in the database containing less than 2000 characters.

• Long Text (DATATYPE_ID=2 in table FND_DOCUMENTS):Text stored in the database containing 2000 characters or more.

• Web Page (DATATYPE_ID=5 in table FND_DOCUMENTS):An URL reference to a web page which you can view with your web browser.

• File (DATATYPE_ID=6 in table FND_DOCUMENTS):Any file like an Image, PDF, MSWord …

Caution:

• T4O automatically saves files in the database in table FND_LOBS. The storage type "file system"is not yet supported.

• T4O only supports the above listed datatypes. Datatypes like Image (DATATYPE_ID=3 in tableFND_DOCUMENTS) and OLE Object (DATATYPE_ID=4 in table FND_DOCUMENTS) are not yetsupported, as they are stored in table FND_DOCUMENTS_LONG_RAW instead of tableFND_LOBS as for datatype File.

The module Document Attachments is part of the T4O 18.1 base installation.

Please consider the following for module Document Attachments:

• The profile option “Upload File Size Limit” that specifies the maximum allowable file size in KB foruploaded attachments, should be adapted to fit your specific needs. If you get an error message likethe following during an attachment transfer via T4O, review the value of this profile option:“The file length exceeds the maximum value set in profile option Upload File Size Limit.”Also have a look at the Oracle Support note “How to Limit The Attachment File Size? (Doc ID604458.1)” for more details on profile option “Upload File Size Limit”.



7. Requirements for Module Document Attachments


8. Requirements for Module CollectionPlans (Quality)The Collection Plans (Quality) functionality is a T4O module which supports parts of the Oracle E-Business Suite module "Quality (QA)". With that functionality it is possible to create, update and read EBSquality result records via T4O.

This module is implemented using the official approach via interface table plus concurrent program"Collection Import Manager". Using that approach implies the following restrictions:

• Create/Update transactions are asynchronous (a concurrent request is submitted).

• The COLLECTION_ID must be unique (getting next sequence value when creating a new qualityresult record). Thus it's not possible to create a series of quality result records for the sameCOLLECTION_ID.Explanation: Usually, for an update transaction a record of table QA_RESULTS can be uniquelyidentified by the following attributes (-> unique index):

• Collection_ID

• Plan_ID

• Occurrence

But since there is no attribute OCCURRENCE in interface table QA_RESULTS_INTERFACE, we needthe COLLECTION_ID to be unique!

• Deleting a quality result record isn't supported by the EBS (also not supported in Oracle Forms UI).

• For an update transaction it's not possible to clear a column value! If specifying NULL, it means thatthis column will be ignored.

The module Collection Plans (Quality) is part of the T4O 18.1 base installation.


8. Requirements for Module Collection Plans (Quality)


9. Set-up for Triggering Data Transfer fromOracle EBS

9.1 The Z-Table

The Z-Table functionality is an enhancement for T4O that is used to import objects from Oracle EBS to ,i.e. create new in Teamcenter or update existing ones. This functionality is only necessary if the datatransfer should be initiated from Oracle EBS.

Except for T4O trigger templates, all T4O Z-Table relevant database objects were already loaded withexecution of SQL script T4O_XXTO_Install.sql (see chapter T4O Application Installation Steps). Forinformation on how to load T4O trigger templates, please see chapter T4O Database TriggerTemplates.

For an explanation on the whole process of initiating a data transfer from Oracle EBS to Teamcenter, seechapter Configure the Data Import in the Teamcenter Gateway for Oracle EBS - ConfigurationGuide.

The Z-Table is a transparent table in the Oracle Database and is used to store information about certainOracle EBS objects which are changed by users interactively, by workflow or by using external softwareconnected via ISG or JDBC. Whenever an object is saved in Oracle EBS, one line will be added to the Z-Table with its corresponding information. To make this possible, it is necessary to create Oracle DatabaseTriggers which are initiated while saving the Oracle EBS object. Within those triggers it is possible to addcertain conditions, for example whether the saved object should be added to the Z-Table or not. Usingthis table, the T4O software is able to grab the stored information by polling against it within a definedtime period (e.g. 5 minutes). It then checks if there are new entries in the table. If so, each new entry isread by T4O and an action is triggered like creating or updating a corresponding object/item inTeamcenter. After this, a status is written back to the table so that the line will not be processed again.

Please refer to the following sections, in order to get some technical information about the Z-TableT4O_ZPTC_TBL_1140.

For details about the SQL code itself, have a look into file T4O_ZPTC_TBL.sql.




Z-Table Fields

Column Name Data Type Nullable Key DataDefault

ColumnId

Comments

ID NUMBER No X 1 UniqueIdentifier

OBJECT_TYP VARCHAR2(10 CHAR) Yes 2 EBS ObjectType

OBJECT_ID VARCHAR2(80 CHAR) Yes 3 EBS Object ID

OBJECT_DESC VARCHAR2(255CHAR)

Yes 4 EBS ObjectDescription

REASON1 VARCHAR2(255CHAR)

Yes 5 char255

REASON2 VARCHAR2(255CHAR)

Yes 6 char255

STATUS VARCHAR2(1 CHAR) Yes 7 ZPTC Status

ERROR_MSG1 VARCHAR2(255CHAR)

Yes 8 Error Message1





DELETED VARCHAR2(1 CHAR) Yes 11 Deleted Flag

CREATED_DATE DATE Yes 12 ZPTC EntryCreation Date

CREATED_TIME TIMESTAMP(6) Yes 13 ZPTC EntryCreation Time

CREATED_USER VARCHAR2(100CHAR)

Yes 14 User whocreated theZPTC Entry

CHANGED_DATE DATE Yes 15 ZPTC EntryChange Date

CHANGED_TIME TIMESTAMP(6) Yes 16 ZPTC EntryChange Time

CHANGED_USER VARCHAR2(100CHAR)

Yes 17 who changedthe ZPTC Entry

Z-Table Metadata (Entry for Z-Table in System View ALL_TABLES)

TABLE_NAME Name of the table T4O_ZPTC_TBL_1140

TABLESPACE_NAME Name of the tablespacecontaining the table

APPS_TS_TX_DATA

9. Set-up for Triggering Data Transfer from Oracle EBS


CLUSTER_NAME Name of the cluster, if any, towhich the table belongs

IOT_NAME Name of the index-only table, ifany, to which the overflow ormapping table entry belongs

STATUS "Status of the table will beUNUSABLE if a previous DROPTABLE operation failed, VALIDotherwise"

VALID

PCT_FREE Minimum percentage of freespace in a block

10

PCT_USED Minimum percentage of usedspace in a block

INI_TRANS Initial number of transactions 1

MAX_TRANS Maximum number oftransactions

255

INITIAL_EXTENT Size of the initial extent in bytes 131072

NEXT_EXTENT Size of secondary extents inbytes

131072

MIN_EXTENTS Minimum number of extentsallowed in the segment

1

MAX_EXTENTS Maximum number of extentsallowed in the segment

2147483645

PCT_INCREASE Percentage increase in extentsize

0

FREELISTS Number of process freelistsallocated in this segment

FREELIST_GROUPS Number of freelist groupsallocated in this segment

LOGGING Logging attribute YES

BACKED_UP Has table been backed up sincelast modification?

N

NUM_ROWS The number of rows in the table

BLOCKS The number of used blocks in thetable

EMPTY_BLOCKS The number of empty (neverused) blocks in the table

AVG_SPACE The average available free spacein the table

CHAIN_CNT The number of chained rows inthe table

AVG_ROW_LEN The average row length,including row overhead

The Z-Table


AVG_SPACE_FREELIST_BLOCKS The average freespace of allblocks on a freelist

NUM_FREELIST_BLOCKS The number of blocks on thefreelist

DEGREE The number of threads perinstance for scanning the table

1

INSTANCES The number of instances acrosswhich the table is to be scanned

1

CACHE Whether the table is to be cachedin the buffer cache

N

TABLE_LOCK Whether table locking is enabledor disabled

ENABLED

SAMPLE_SIZE The sample size used in analyzingthis table

LAST_ANALYZED The date of the most recent timethis table was analyzed

PARTITIONED Is this table partitioned? YES orNO

NO

IOT_TYPE If index-only table, thenIOT_TYPE is IOT orIOT_OVERFLOW or IOT_MAPPINGelse NULL

TEMPORARY Can the current session only seedata that it place in this objectitself?

N

SECONDARY Is this table object created as partof icreate for domain indexes?

N

NESTED Is the table a nested table? NO

BUFFER_POOL The default buffer pool to beused for table blocks

DEFAULT

ROW_MOVEMENT Whether partitioned rowmovement is enabled or disabled

DISABLED

GLOBAL_STATS Are the statistics calculatedwithout merging underlyingpartitions?

NO

USER_STATS Were the statistics entereddirectly by the user?

NO

DURATION If temporary table, then durationis sys$session or sys$transactionelse NULL

SKIP_CORRUPT Whether skip corrupt blocks isenabled or disabled

DISABLED



MONITORING Should we keep track of theamount of modification?

YES

CLUSTER_OWNER Owner of the cluster, if any, towhich the table belongs

DEPENDENCIES Should we keep track of row leveldependencies?

DISABLED

COMPRESSION Whether table compression isenabled or not

DISABLED

COMPRESS_FOR Compress what kind ofoperations

DROPPED Whether table is dropped and isin Recycle Bin

NO

READ_ONLY Whether table is read only or not NO

Sequence T4O_ZPTC_TBL_1140_SEQ

Description: Custom sequence that supports the primary keycolumn “ID” of the Z-Table.

Editioning View T4O_ZPTC_TBL_1140# for EBS 12.2

Description: Editioning view for table T4O_ZPTC_TBL_1140 (EBS12.2 only!)

Trigger T4O_ZPTC_TBL_1140_TRG

Trigger Type: BEFORE EACH ROW

Triggering Event: INSERT

Table: T4O_ZPTC_TBL_1140 for EBS 12.1

T4O_ZPTC_TBL_1140# for EBS 12.2

Description: Initiated before a new entry is inserted to Z-Table.

Determines next free value for unique identifier“ID” by fetching NEXTVAL of sequence.

9.2 PL/SQL Package T4O_ZPTC_1140

The following PL/SQL procedures are provided with package T4O_ZPTC_1140 in order to use the Z-Table functionality:

• TP_ZPTC_Get_DetailRetrieve the information for an entry in the Z-Table

PL/SQL Package T4O_ZPTC_1140


• TP_ZPTC_InsertInsert a record into the Z-Table

• TP_ZPTC_UpdateUpdate a record in the Z-Table

• TP_ZPTC_DeleteDelete a record from the Z-Table

• TP_ZPTC_Dyn_SearchSearch for records in the Z-Table that fulfil a given pattern

• TP_ZPTC_Dyn_DeleteDelete several records from the Z-Table that fulfil a given pattern

For testing those functions, T4O provides the following test scripts:

• EBS ZPTC get detail

• EBS ZPTC insert

• EBS ZPTC update

• EBS ZPTC delete

• EBS ZPTC dyn search

• EBS ZPTC dyn delete

It is possible to run such a script like any other T4O test script.

Please refer to the following sections, in order to get details about the Z-Table functionality providedwith package T4O_ZPTC_1140.

For more details about the provided procedures and their used PL/SQL types, have a look into fileT4OZPTCS.pls which includes the T4O_ZPTC_1140 package specification.

TP_ZPTC_Get_Detail

Description: Retrieves the information for an entry in the ZPTC table.

Scope: Public

Arguments:



Argument Description IN/OUT Type

p_Api_Version API version IN NUMBER

p_Init_Msg_List Boolean whether toinitialize message list

IN VARCHAR2

p_ID ZPTC ID of entry to beretrieved

IN NUMBER

x_ZPTC_Rec Retrieved entry in the ZPTCtable

OUT NOCOPY TP_ZPTC_rec_type

x_Return_Status Return Status OUT NOCOPY VARCHAR2

x_Return_Err Return Error OUT NOCOPY VARCHAR2

TP_ZPTC_Insert

Description: Inserts a record into ZPTC table; sets fields CREATED_USER, CREATED_DATEand CREATED_TIME to the current system user, date and time.

Scope: Public

Arguments:




IN VARCHAR2

p_ZPTC_Rec Record to be inserted intoZPTC table

IN TP_ZPTC_rec_type

x_ID ID of inserted record OUT NUMBER



TP_ZPTC_Update

Description: Updates a record in ZPTC table. Updates only non-empty (not NULL) fieldsspecified in p_ZPTC_Rec. String ‘!leer!’ means that respective field should bereset to default value (NULL). If p_Reset is set to ‘T’, all “change fields” (seeabove) are reset to default values, otherwise they’re set to the current systemvalues.

Scope: Public

Arguments:

PL/SQL Package T4O_ZPTC_1140





IN VARCHAR2

p_ZPTC_Rec Record to be updated inZPTC table

IN TP_ZPTC_rec_type

p_Reset Flag whether to reset“change fields”CHANGED_DATE,CHANGED_TIME,CHANGED_USER and fieldsSTATUS and DELETED

IN VARCHAR2



TP_ZPTC_Delete

Description: Deletes the record with specified ID from ZPTC table. If p_Tagged is set to ‘T’,only marks the record as deleted (assigns value ‘T’ to field DELETED),otherwise really removes the specified entry from table.

Scope: Public

Arguments:




IN VARCHAR2

p_Tagged Flag if a real 'delete' shouldbe performed

IN VARCHAR2

p_ID ID of record to be deleted IN NUMBER



TP_ZPTC_Dyn_Search

Description: Searches for records in ZPTC table that satisfy the defined conditions inp_Where parameter.

Scope: Public

Arguments:






IN VARCHAR2

p_Where Where clause for dynamicSQL to specify the records tobe retrieved

IN VARCHAR2

p_Max_Rows Maximum number ofreturned rows

IN NUMBER

x_Count Number of found records OUT NUMBER

x_ZPTC_Tbl Found records OUT TP_ZPTC_tbl_type



TP_ZPTC_Dyn_Delete

Description: Deletes those records from ZPTC table that satisfy the defined conditions inp_Where parameter. If p_Tagged is set to ‘T’, only marks the records asdeleted (assigns value ‘T’ to field DELETED), otherwise really removes thespecified entries from table.

Scope: Public

Arguments:




IN VARCHAR2

p_Tagged Flag if a real 'delete' shouldbe performed

IN VARCHAR2

p_Where Where clause for dynamicSQL to specify the records tobe deleted

IN VARCHAR2

x_Count Number of deleted records OUT NUMBER



9.3 T4O Database Trigger Templates

For the Oracle EBS target types ITEM, BOM and ECO, T4O provides database trigger templates that caneither be used as defined or as a guideline for own customized database triggers that apply ZPTCprocedures:

T4O Database Trigger Templates


• Trigger T4O_ZPTC_ITEM_TRG_TMPL: T4O_ZPTC_ITEM_TRG_TMPL.sql

• Trigger T4O_ZPTC_BOM_TRG_TMPL: T4O_ZPTC_BOM_TRG_TMPL.sql

• Trigger T4O_ZPTC_ECO_TRG_TMPL: T4O_ZPTC_ECO_TRG_TMPL.sql

To make those T4O database trigger templates available, the scripts have to be executed in APPSschema.

Each of the SQL scripts for loading a T4O database trigger template contains following line at the end ofthe file:

ALTER TRIGGER "T4O_ZPTC_<EBS_Object_Type>_TRG_TMPL" ENABLE;

This will activate respective trigger.

Each trigger template script will prompt for a trigger version. For a first T4O installation (no other T4Oversion is installed on your system yet) and a real upgrade (only one T4O version is used), you just canpress enter – this won’t append a version string to the trigger name. But when upgrading T4O and usingmultiple versions in parallel, you probably need to specify a version string here (have a look into chapterCommon Upgrade Steps for JDBC and ISG.)



Caution:

EBS 12.2 only:

You may need to install those triggers into a patch edition. This can be done by the following:

• Run the adop prepare phase, e.g.:

<INSTALL_BASE>/fs_ne/EBSapps/appl/ad/bin/adop phase=prepare

• Connect to the patch file system, e.g.:

. <INSTALL_BASE>/EBSapps.env patch

• Upload the T4O triggers to the APPS schema using an interactive tool such as SQL*Plus.

• Run the adop finalize phase, e.g.:

<INSTALL_BASE>/fs_ne/EBSapps/appl/ad/bin/adop phase=finalize

• Run the adop cutover phase (prerequisite: shut down T4O GS), e.g.:

<INSTALL_BASE>/fs_ne/EBSapps/appl/ad/bin/adop phase=cutover

Trigger T4O_ZPTC_ITEM_TRG_TMPL


Triggering Event: INSERT OR UPDATE

Table: MTL_SYSTEM_ITEMS_B

Description: Initiated before either a new entry is inserted toMTL_SYSTEM_ITEMS_B table or an already existingentry is updated. Checks if a Z-Table entry of objecttype ‘ITEM’ with same OBJECT_ID as Oracle EBSItem ID already exists, but which does not have anystatus and was not marked as deleted. If so theentry is updated, otherwise a new entry is createdin the Z-Table for current Oracle EBS Item.

Condition for triggering: The description of the created/updated Oracle EBSitem needs to contain string ‘ZPTC TEST’

For details about the SQL code, see file T4O_ZPTC_ITEM_TRG_TMPL.sql.

T4O Database Trigger Templates


Trigger T4O_ZPTC_BOM_TRG_TMPL



Table: BOM_STRUCTURES_B

Description: Initiated before either a new entry is inserted toBOM_STRUCTURES_B table or an already existingentry is updated. Checks if a Z-Table entry of objecttype ‘BOM’ with same OBJECT_ID as Oracle EBSBOM ID already exists, but which does not have anystatus and was not marked as deleted. If so theentry is updated, otherwise a new entry is createdin the Z-Table for current Oracle EBS BOM.

Condition for triggering: The description of the created/updated Oracle EBSBOM needs to contain string ‘ZPTC TEST’

For details about the SQL code, see file T4O_ZPTC_BOM_TRG_TMPL.sql.

Trigger T4O_ZPTC_ECO_TRG_TMPL



Table: ENG_ENGINEERING_CHANGES

Description: Initiated before either a new entry is inserted toENG_ENGINEERING_CHANGES table or an alreadyexisting entry is updated. Checks if a Z-Table entryof object type ‘ECO’ with same OBJECT_ID as OracleEBS ECO ID already exists, but which does not haveany status and was not marked as deleted. If so theentry is updated, otherwise a new entry is createdin the Z-Table for current Oracle EBS ECO.

Condition for triggering: The description of the created/updated Oracle EBSECO needs to contain string ‘ZPTC TEST’

For details about the SQL code, see file T4O_ZPTC_ECO_TRG_TMPL.sql.



A. Glossary

A

Adminis the term used in this document for people who install and configure Teamcenter and its components.This is in contrast to the “user” role.

AppsSee "GS".

B

BGSBasic Gateway Service.

BMIDETeamcenter Business Modeler IDE (Integrated Development Environment).

BOMA Bill Of Materials is a list of the parts or components and their quantities that are required to build aproduct.

BOPThe Bill Of Process describes a manufacturing process and lists the operations and steps with all theirinstructions, consumed materials, resources, work places and machines.

D

Dataview mark-upis the language understood by the Dataview. The Dataview receives messages written in this languagefrom the T4x server. Such messages can be formatted as XML or JSON. Normally users do not see suchmessages. They may however appear in log files or error messages. The so called prop mapping (e.g.t4s_prop_mapping_template.sd) contains TCL commands that compose messages in the Data Viewmark-up.

E

EAstands for Enterprise Application, any software or set of computer programs used by business users toperform various business functions in context of current integration's portfolio with Teamcenter.

Preparation of Oracle EBS A-1© 2018 Siemens Product Lifecycle Management Software, Inc.

ECNThe Engineering Change Notice can also be called an Engineering Change Note, Engineering ChangeOrder (ECO), or just an Engineering Change (EC).

EPMEnterprise Process Modeling.

G

GRMThe Generic Relationship Management provides a general way in which two objects can be associatedvia a relationship.

GSGateway Service, manages the communication between Teamcenter and the Enterprise Application.

GUIGraphical user interface.

I

IDGENThe IDGEN is a mechanism to get an external ID from the ERP system when assigning a Teamcenter ID.

ITKThe Integration Toolkit (ITK) is a set of software tools provided by Siemens PLM Software that you canuse to integrate third-party or user-developed applications with Teamcenter.

J

JDBCJava Database Connectivity is an application programming interface (API) for the programming languageJava, which defines how a client may access a database.

L

LOVList of Values.

A. Glossary

A-2 Preparation of Oracle EBS© 2018 Siemens Product Lifecycle Management Software, Inc.

M

MFKMulti-key functionality in Teamcenter.

O

OOTBOut of the box.

R

RACstands for Rich Application Client also referred to as rich client or portal.

S

SSLSecure Sockets Layer.

T

T4O_ROOTThe installation directory of the T4O Gateway Service (e.g. similar to C:\Siemens\T4O_GS or C:\UGS\T4O_Apps)

T4xThe entire Teamcenter Gateway product family.

TCTeamcenter

TCLis a high-level, general-purpose, interpreted, dynamic programming language.

TEMTeamcenter Environment Manager.

Preparation of Oracle EBS A-3© 2018 Siemens Product Lifecycle Management Software, Inc.

U

UOMUOM stands for Unit of Measure.

URIUnified Resource Identifier: a generalized from of a resource locator (URL) and resource name (URN),which just identifies a resource, but is not necessarily sufficient to locate (find) the resource. URIs areoften used to identify configurations in Java and other languages. See https://en.wikipedia.org/wiki/Uniform_Resource_Identifier for more details.

URLUnified Resource Locator: a string with a certain format, allowing to load a resource from a network.URLs are a specific form or URNs.

X

XMLExtensible Markup Language is designed to store and transport data in a format that is both human- andmachine-readable.

XRTstands for XML Rendering Template, also known as XML Rendering Stylesheet. These are XMLdocuments stored in datasets that define how parts of the Teamcenter user interface are rendered. Theyare used for the Rich Client as well as the Active Workspace.

Z

Z-Table"Z" is the prefix name for custom tables well-known in SAP world.

A. Glossary

A-4 Preparation of Oracle EBS© 2018 Siemens Product Lifecycle Management Software, Inc.

https://en.wikipedia.org/wiki/Uniform_Resource_Identifier

https://en.wikipedia.org/wiki/Uniform_Resource_Identifier

Siemens Industry Software

HeadquartersGranite Park One5800 Granite ParkwaySuite 600Plano, TX 75024USA+1 972 987 3000

AmericasGranite Park One5800 Granite ParkwaySuite 600Plano, TX 75024USA+1 314 264 8499

EuropeStephenson HouseSir William Siemens SquareFrimley, CamberleySurrey, GU16 8QD+44 (0) 1276 413200

Asia-PacificSuites 4301-4302, 43/FAIA Kowloon Tower, Landmark East100 How Ming StreetKwun Tong, KowloonHong Kong+852 2230 3308

About Siemens PLM SoftwareSiemens PLM Software, a business unit ofthe Siemens Industry Automation Division,is a leading global provider of productlifecycle management (PLM) software andservices with 7 million licensed seats and71,000 customers worldwide.Headquartered in Plano, Texas, SiemensPLM Software works collaboratively withcompanies to deliver open solutions thathelp them turn more ideas into successfulproducts. For more information onSiemens PLM Software products andservices, visit www.siemens.com/plm.

© 2018 Siemens Product LifecycleManagement Software Inc. Siemens, theSiemens logo and SIMATIC IT are registeredtrademarks of Siemens AG. Camstar, D-Cubed, Femap, Fibersim, Geolus, I-deas, JT,NX, Omneo, Parasolid, Solid Edge,Syncrofit, Teamcenter and Tecnomatix aretrademarks or registered trademarks ofSiemens Product Lifecycle ManagementSoftware Inc. or its subsidiaries in theUnited States and in other countries. Allother trademarks, registered trademarks orservice marks belong to their respectiveholders.

Documents

Preparation of Oracle EBS - docs.plm.automation.siemens.com · • Oracle E-Business Suite 12.2.x (further referenced as EBS 12.2) Detailed information about the exact sub-versions