Oracle Shooter

Structure of metadata and how to use metadata structure in Oracle database —-How to Use the Data Dictionary (Metadata) —- The views of the data dictionary serve as a reference for all database users.  Access the data dictionary views with SQL statements.  Some views are accessible to all Oracle users, and others are intended for database administrators only. The data dictionary consists of sets of views. In many cases, a set consists of three views  containing similar information and distinguished from each other by their prefixes: Prefix Scope USER :- User’s view (what is in the user’s schema) ALL  :- Expanded user’s view (what the user can access) DBA  :- Database administrator’s view (what is in all users’ schemas) 1. Views with the Prefix USER ——— The views most likely to be of interest to typical database users are those with the prefix USER. These views: Refer to the user’s own private environment in the database,  including information about schema o...

Metadata What is Metadata in Oracle and What is Data Dictionary | Oracle Shooter –Definition —  The Oracle data dictionary is one of the most important components of the Oracle DBMS.  It contains all information about the structures and objects of the database  such as. • tables, • columns, • users, • data files etc.  The data stored in the data dictionary are also often called metadata. –Introduction to the Data Dictionary One of the most important parts of an Oracle database is its data dictionary, which is a read-only set of tables that provides information about the database. A data dictionary contains: The definitions of all schema objects in the database (tables, views, indexes, clusters, synonyms, sequences, procedures, functions, packages, triggers, and so on) How much space has been allocated for, and is currently used by, the schema objects Default values for columns Integrity constraint information The names of Oracle users Privileges and roles each user h...

Import Journals ImportJournals method in SOAP web service with request and response PAYLOAD Service WSDL URL:  https://servername/fscmService/JournalImportService?WSDL Code: REQUEST PAYLOAD REQUEST PAYLOAD:- <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:typ="http://xmlns.oracle.com/apps/financials/generalLedger/journals/desktopEntry/journalImportService/types/" xmlns:jour="http://xmlns.oracle.com/apps/financials/generalLedger/journals/desktopEntry/journalImportService/" xmlns:jour1="http://xmlns.oracle.com/apps/flex/financials/generalLedger/journals/desktopEntry/journalLineGdf/"> <soapenv:Header/> <soapenv:Body> <typ:importJournals> <typ:interfaceRows> <!--Optional:--> <jour:BatchName>SOAP JV 90001</jour:BatchName> <!--Optional:--> <jour:BatchDescription>TESTING</jour:BatchDescr...

Submit Invoice Import submitInvoiceImport  and  submitInvoiceImportWithSource  Operations in SOAP web service Service WSDL URL:  https://servername/fscmService/InvoiceInterfaceService?WSDL Code for submitInvoiceImport PAYLOAD :-  <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:typ="http://xmlns.oracle.com/apps/financials/payables/invoices/quickInvoices/invoiceInterfaceService/types/"> <soapenv:Header/> <soapenv:Body> <typ:submitInvoiceImport> <typ:ledgerId>300000001520052</typ:ledgerId> <typ:orgId>300000001534054</typ:orgId> <typ:summarizeReport>No</typ:summarizeReport> </typ:submitInvoiceImport> </soapenv:Body> </soapenv:Envelope> Code for submitInvoiceImportWithSource PAYLOAD :-  <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:typ="http:/...

Create Invoice Interface createInvoiceInterface Operations in Payables Invoice in SOAP web service (createInvoiceInterface payload with Response) Service WSDL URL:  https://servername/fscmService/InvoiceInterfaceService?WSDL Code for REQUEST PAYLOAD :- “ STANDARD INVOICE “ <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:typ="http://xmlns.oracle.com/apps/financials/payables/invoices/quickInvoices/invoiceInterfaceService/types/" xmlns:inv="http://xmlns.oracle.com/apps/financials/payables/invoices/quickInvoices/invoiceInterfaceService/"> <soapenv:Header/> <soapenv:Body> <typ:createInvoiceInterface> <typ:invoiceInterfaceHeader> <inv:Source>ELECTRONIC INVOICE</inv:Source> <inv:OperatingUnit>Snapdeal Private Limited</inv:OperatingUnit> <inv:VendorName>Test Supplier App99</inv:VendorName> <in...

Find Invoice Interface findInvoiceInterface Operation in Payables Invoice in SOAP web service (FIND_INVOICE_INTERACE payload with Response)  Service WSDL URL:  https://servername/fscmService/InvoiceInterfaceService?WSDL Code for REQUEST Payload <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:typ="http://xmlns.oracle.com/apps/financials/payables/invoices/quickInvoices/invoiceInterfaceService/types/" xmlns:typ1="http://xmlns.oracle.com/adf/svc/types/"> <soapenv:Header/> <soapenv:Body> <typ:findInvoiceInterface> <typ:findCriteria> <typ1:fetchStart>0</typ1:fetchStart> <typ1:fetchSize>10</typ1:fetchSize> <!--Optional:--> <typ1:filter> <typ1:group> <typ1:item> <typ1:attribute>InvoiceTypeLookupCode</typ1:attribute> ...

Supplier Contact Supplier Contact, Address and Site Creation and Updation by using SOAP Web Service or WSDL in cloud fusion Service WSDL URL:   https://servername/fscmService/SupplierServiceV2?WSDL   Create Supplier Contact <soapenv:Body> <typ:createSupplier> <typ:supplierRow> <!--Optional:--> <sup:Supplier>Test Supplier App9011</sup:Supplier> <sup:AlternateName>App9011</sup:AlternateName> <sup:TaxOrganizationType>CORPORATION</sup:TaxOrganizationType> <sup:SupplierType>SUPPLIER</sup:SupplierType> <sup:BusinessRelationship>SPEND_AUTHORIZED</sup:BusinessRelationship> <sup:SupplierAddresses> <sup:Operation>CREATE</sup:Operation> <sup:AddressName>Main_add</sup:AddressName> <sup:Country>IN</sup:Country> <sup:AddressLine1>123 Old railway Line</sup:AddressLine1> ...