XDOLoader command to migrate XML/BI publisher reports

XDOLoader command to migrate XML publisher reports

• To load XML file to data definition:

java oracle.apps.xdo.oa.util.XDOLoader UPLOAD -DB_USERNAME $apps_user -DB_PASSWORD $apps_pwd -JDBC_CONNECTION $host:$port:$sid  -LOB_TYPE TEMPLATE -APPS_SHORT_NAME PO -LOB_CODE "XXTEST BLANKET PO" -LANGUAGE en -TERRITORY US -XDO_FILE_TYPE XSL-FO -NLS_LANG AMERICAN -FILE_CONTENT_TYPE 'text/xml' -FILE_NAME $NCUST_TOP/reports/US/UTF-8en-usXXTEST_Blanket.xsl -OWNER ORACLE -CUSTOM_MODE FORCE

•  To load RTF file

 java oracle.apps.xdo.oa.util.XDOLoader UPLOAD -DB_USERNAME $apps_user -DB_PASSWORD $apps_pwd -JDBC_CONNECTION $host:$port:$sid  -LOB_TYPE TEMPLATE -APPS_SHORT_NAME NCUST -LOB_CODE XXTEST_REP -LANGUAGE en -TERRITORY US -XDO_FILE_TYPE RTF -NLS_LANG AMERICAN -FILE_CONTENT_TYPE 'application/rtf' -FILE_NAME $NCUST_TOP/reports/US/XXTEST_REP.rtf -OWNER ORACLE -CUSTOM_MODE FORCE

Introduction to AIA PIP

What is AIA
Application Integration Architecture is an open, standards-based platform that is designed to ease integration of disparate applications into a unified enterprise architecture using service-oriented architecture (SOA). AIA provides an integration framework for enabling cross-application business processes, which spares organizations the effort of having to customize their applications to achieve the same end within a single, common application suite, such as Oracle E-Business Suite or Oracle Siebel applications. It can be used to link together Oracle applications, custom applications or any combination of enterprise legacy applications.

AIA Components

AIA consists of three components:

1. The Foundation Pack, 
2. Process Integration Packs and
3. Direct Integrations.

All of which use Oracle Fusion Middleware as the technology platform. The Foundation Pack sits on top of the Oracle SOA Suite to provide the common framework and object models; the Process Integration Packs are built on top of the Foundation Pack to facilitate composite business process integrations of two or more Oracle applications. Direct Integrations are a prebuilt tightly coupled data integration solution between two applications

Starting lot number prefix is required when Lot Control = Full lot control

While releasing a part from Agile getting below error.

Error: Starting lot number prefix is required when Lot Control = Full lot control

Cause You have to specify Lot Prefix in the  template when you have Lot Control=Full Lot Control.

Resolution Please correct the Item Templates in Oracle EBS and resubmit the ECO from AIA queue.

Err Msg INV INV_INVALID_ARG_NULL_VALUE

Error INV INV_INVALID_ARG_NULL_VALUE 

When an ECO being released from Agile PLM, getting below error in AIA PIP

Org Code MST ECO Name ECO00018 Err Msg INV INV_INVALID_ARG_NULL_VALUE


This could be because, category set which is being sent from Agile is not valid Oracle EBS.
You need check, if the category set is valid in Oracle EBS or not.

Use below code for the same,


SELECT    (segment1)|| '.'
       || (segment2)|| '.'
       || (segment3)|| '.'
       || (segment4)|| '.'
       || (segment5)|| '.'
       || (segment6)|| '.'
       || (segment7) cat_set,
       mc.segment1,
       mc.segment2,
       mc.segment3,
       mc.segment4,
       mc.segment5,
       mc.segment6,
       mc.segment7
  FROM mtl_categories_b mc
 WHERE     enabled_flag = 'Y'
       AND NVL (end_date_active, SYSDATE) >= SYSDATE
       AND    (segment1)
           || '.'|| (segment2)
           || '.'|| (segment3)
           || '.'|| (segment4)
           || '.'|| (segment5)
           || '.'|| (segment6)
           || '.'|| (segment7) LIKE     '&p_cat_set';


Make sure you have the category defined in Oracle and try to resubmit the ECO from AIA queue.

How to update PO document type to refer workflow custom process.

How to update PO document type to refer workflow custom process.

1. Go Purchasing%Super%User responsibility
2. Setup-->Purchasing-->Document type
3. It will open new OAF page
4. If MOAC enabled, it would ask to select the Operating unit for which the settings needs to be applied.
5. Select the appropriate responsibility
6. In the webpage, we need to update following document types in order to refer custom process by PO approval workflow engine.
   ·         Purchase Order Standard
   ·         Purchase Agreement Blanket
   ·         Release Blanket

SCA vs SOA

Service Component Architecture VS Service Oriented Architecture

It's a set of specifications that defines an assembly model for composite services and also provides a programming model to build applications which are SOA-based.

A composite service can have several business processes, bindings, properties, human workflows, etc. all put together. We define a Composite and once the Composite is ready it's for you to be treated as a single component and can easily be exposed as a composite service the way you expose a web service.

SCA makes the deployment design very easy. Suppose your application have n business processes and let's say BP-1 is the entry point to the application then you can define a composite by specifying the navigation details among the various business processes and/or human workflows and then you can expose BP-1 as a composite service. Now, the composite service is having a well-defined assembly of all the components involved in your application and ready to be deployed. You don't need to deploy the individual components separately. All will be handled by SCA. All the assembly information is stored in an SCA Descriptor.




SCA vs SOA 
SCA focuses on the assembly of various components to provide an easier design and deployment while SOA provides an architecture or style to design and develop the individual components. SCA comes into pictures only when you're ready with all the components. So, you create components with SOA and assemble them using SCA mainly to make the deployment easier.

SOA is an architectural style or approach.

SCA is an assembly model for SOA-style applications.

SOA

SOA is all about BPEL and Mediator

·         WSDL - Web Services Description Language

·         A sample WSDL document

·         Ways of combining Web Services. Orchestration vs Choreography

·         What all Request Response Patterns do we have in SOA?

·         Service Component Architecture (SCA). SCA vs SOA

·         Web Services - What, Why, How, and Shortcomings







SCA:

• An assembly model described by a set of specifications that define how to compose applications from components
• A definition of a design and deployment model for composite services

You can also read http://www.erptimes.com/2013/10/service-component-architecture-sca-and.html