Regarding Interface Objects

[Former Member]

Hello,

In the Integration Repository we can see

Data type Enhancement

Context Objects

External Definations.

How to use these things in Integration Scenario.

What its purpose?

What are the steps to design it.

Thank you

[Former Member]

HI

External Definitions: If a definition of the message structure exists in wsdl, xsd, dtd formats, we can use it in the integration repository by importing it as an external definition.

Context-Object is like an Alias (a pointer).

You can define it into IR (e.g myContext) with "Create a new Context-Object" and then always in IR, you can use it into your Interface Message (see the tab called "Context") in order to affect this alias to a specific field.

(e.g myContext <-> /myMessage/myRow/myAddress/myField)

And then,(for instance) in the Integration Directory, for the Receiver Determination you can define a condition (filter) DIRECTLY by using this Context name, WITHOUT to display the whole XML tree. By this way, you can simplify the configuration of your flow, because it's easier to use a Context name (e.g myContext) compare to deployed the structure tree in order to find your field (e.g /myMessage/myRow/myAddress/myField).

Moreover, as you associate the field to the Context only ONCE (in the IR, interface message), you decrease the posibility to do an error in the ID config, especially if fieldname are quasi-similar: addressName, adrName, addressSupplierName, AddressClientName.

Note: x-path and Context can also be used in BPM for a condition a branch (for instance).

Technical Context Objects :

http://help.sap.com/saphelp_nw04/helpdata/en/d6/e44fcf98baa24a9686a7643a33f26f/frameset.htm

A list of the Technical Context Objects names can be found here:

http://help.sap.com/saphelp_nw04/helpdata/en/6e/ff0bf75772457b863ef5d99bc92404/content.htm

Difference between context object and x-path:

cheers

reward points if found useful

[aashish_sinha]

Hi,

Data type Enhancement

SAP applications enable customers to enhance application source code without making modifications and thus to meet customer-specific requirements that are not provided for in the standard shipment. The applications can use Business Add-Ins (BAdIs) for this purpose. Furthermore, if customers use applications that exchange messages by using XI, they can define data type enhancements for Integration Repository data types. Customers can use these enhancements to send additional data with a message and can access this data by using BAdIs, for example.

Refer http://help.sap.com/saphelp_nw04/helpdata/en/a8/bfc6373c8fea43bdb3541535bcbd43/content.htm

Context Objects

To improve access to message content in a message exchange system, a context object is defined for the message as an abstraction of the message content. The context object can be assigned to many different message communication interfaces, thereby allowing context objects to be reused across various interfaces. The context object provides access both to a message payload, and parts of a message other than the payload, such as technical data. Accordingly, access to message content for various tasks and applicability to a number of different message interfaces is improved.

External Definations

There is a series of standard schema for describing the message structure at runtime. WSDL (Web Service Description Language), XSD (XML Schema Definition Language), or DTDs (Document Type Definitions) are often used to describe message schema. If a description of the message structure already exists in one of the above formats, you can use it in the Integration Repository by importing it as an external definition rather than re-entering it manually using the data type editor.

Refer http://help.sap.com/saphelp_nw04/helpdata/en/26/9e97b0f525d743882936c2d6f375c7/content.htm

Regards

Aashish Sinha

[Former Member]

Hi,

Refer the below link:

Data enhancement:

http://help.sap.com/saphelp_nw70/helpdata/EN/a8/bfc6373c8fea43bdb3541535bcbd43/frameset.htm

Context object:

http://help.sap.com/saphelp_nw04/helpdata/en/d6/e44fcf98baa24a9686a7643a33f26f/frameset.htm

/people/prasadbabu.nemalikanti3/blog/2006/09/20/receiver-determination-based-on-the-payload-of-input-dataextended-xpathcontext-object

External definition:

http://help.sap.com/saphelp_nw2004s/helpdata/en/d6/e44fcf98baa24a9686a7643a33f26f/frameset.htm

It is used when u ahve a std strucutre file of type WSDL,XSD.

chirag

[Former Member]

Hi,

Data type Enhancement

If you have a standard message type that you are reusing and then you just need to modify it a bit and rest of the strcutre remains the same.

You can make extensions to this exisiting message type and this will help you reusing the existing Data type and the change will not effect any exisiting interface thats using the same data type.

Check Michal's Blog and you got it!!!!!!!!!

/people/michal.krawczyk2/blog/2006/11/14/xipi-data-type-enhancements-standard-business-partner

Context Objects

context objects are like variables in any programming language

say we declare String A = "context objects are like variables in any programming language"

So instead of the whole string "context objects are like variables in any programming language" we can ref. it as A anywhere in the program.

Similarly Context objects acts on XPATH. Suppose we have a xpath like /a/aa/aaa/aaaa/b/bb/bbb we can define it as a BBB = /a/aa/aaa/aaaa/b/bb/bbb using a context object.

this lik explains how to access context objects.

External Definations.

An external definition enables you to import a local WSDL, XSD, or DTD file to the Integration Repository and specify which parts of the schema to extract as the description for a message. You can use these extracted message schema as:

Output or input messages in message interfaces

Source or target structures for message mappings

Have a look at

http://help.sap.com/saphelp_nw04/helpdata/en/43/ce49ef1019087ae10000000a1553f6/content.htm

http://help.sap.com/saphelp_nw04/helpdata/en/ba/d4c23b95c8466ce10000000a114084/content.ht

Thanks

Vikranth

[Former Member]

hi,

Data type Enhancement:

this is to enable developers to add some additional fields to standard SAP messages .

check this for clea understanding.

/people/michal.krawczyk2/blog/2006/11/14/xipi-data-type-enhancements-standard-business-partner

Context Objects:

Context objects are alternative to XPATH expressions. It is like macros in other programming langugage. If you define this , you can use this object in the receiver determination while doing conditional receiver determination

Check out these

http://help.sap.com/saphelp_nw2004s/helpdata/en/d6/e44fcf98baa24a9686a7643a33f26f/content.htm

/people/prasadbabu.nemalikanti3/blog/2006/09/20/receiver-determination-based-on-the-payload-of-input-dataextended-xpathcontext-object

Here is a scenario where context objects were used for BPM

External Definations:

An external definition enables you to import a local WSDL, XSD, or DTD file to the Integration Repository and specify which parts of the schema to extract as the description for a message. You can use these extracted message schema as:

Output or input messages in message interfaces

Source or target structures for message mappings

Have a look at

http://help.sap.com/saphelp_nw04/helpdata/en/43/ce49ef1019087ae10000000a1553f6/content.htm

http://help.sap.com/saphelp_nw04/helpdata/en/ba/d4c23b95c8466ce10000000a114084/content.htm

this should be helpful:

What are the steps to design it

/people/venkat.donela/blog/2006/02/17/companion-guide-to-integration-scenario

/people/siva.maranani/blog/2005/08/27/modeling-integration-scenario146s-in-xi

http://help.sap.com/saphelp_nw04/helpdata/en/ec/21ee117a909f44a8b69794b9ed6221/frameset.htm

Thanks,

Vijaya.