0% found this document useful (0 votes)
11 views4 pages

Oracle Integration Table Structures Guide

Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
11 views4 pages

Oracle Integration Table Structures Guide

Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd

Table Structures

-----------------------------

1. UCM -- Universal Content Management

2. Interface Tables -- Middle Tables -- Error supplier not valid -- Success

3. Stagging Tables -- Real data

Integration Steps

----------------------------------------

Inbound

--------------

1. REST API Integration

2. FBDI Integration

Oubound

--------------

[Link] Push Integration

[Link] Triggered Integration

Call back event --> ess name --> job id ->

Inound

1. REST API create/update -- sample json payload -- less volume -- less dificulty --

2. FBDI bulk upload -- Create/update -- higher volume -- higher difficulty -- FBDI Oracle Standard
Template
1. REST API Integration

--------------------------------------------------------------

--> Get source file FTP - > ftp list files -> each file

-- > each file --> download file -> read file -> each record -> validation report run -> required
columns -> ERP push to create/update -> status success/error -> email status file

test faces

CRP1

CRP2 -->

SIT -- >

UAT --> Errorss Item wrong org lot qyt

PREPROD

PROD

3. BIP Push

-------------------
Custom Report Items Status report active/inactive -->

==================================================================================
====================================================

4. Integration will handle the below scenarios while processing shipment file.

a. Errors while Issuing the Wafer.

b. Errors after Wafer Issue and before creating the candidates. (Ex: If wafer doesn’t have the
Candidtes)

c. Errors while creating the candidates.

d. Errors after candidates creation and before shipment creation.

(Ex: Candidate don’t’ have open TO, Open TO quantity less then the candidates qty)

-----------------------------------------------------------------

Integrations can fail for reasons such as the following:

-----------------------------------------------------------------------

• A call to a target system fails because the target system is down (for a short or long time

period).

• A source-to-target transformation or target-to-source transformation fails because of

faulty XSL coding, an invalid lookup call, or other system issue.

• A target system call results in a business failure for the following possible reasons:

– Incorrect target application configuration

– Invalid lookup data


– Invalid business data

• A call to a trigger system (with a response message) fails because the trigger system is

down.

• Any other Oracle Integration system failure.

You might also like