on 04-30-2008 1:44 PM
hi xi experts,
can u explain what is
meant by ehancenent data type and fault data type and when they are used
Hi,
Ehancenent data type : 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.
Fault data type : These are designed for some specific application errors, if any error ocuur then this structure return back to the sender.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Data Type Enhancements
SAP applications enable customers to enhance application source code without making modifications and thus meet customer-specific requirements that are not provided for in the standard shipment.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
Features
You can make the following enhancements to a data type:
· You can add elements and structures at the top hierarchy level as subelements of the root element.
· You can define attributes for the root element or its inserted elements.
· You can create elements and attributes at the top hierarchy level as optional fields only. You can create all other elements and attributes as often as you like.
· You can define your own facets for newly inserted elements or attributes in the Details column. This is not possible for SAP data type fields.
Activities
... 1. Create a data type enhancement.
2. Assign a data type from a subordinate software component version to the data type enhancement. These data types are shown in the navigation tree of your software component version, in the Basis Objects branch.
3. The Integration Builder automatically enters the namespace of your data type enhancement in the XML Namespace field. You can enter a different XML namespace in this field if you want. The XML namespace avoids naming conflicts between customer fields and fields that are added later by SAP.
4. Enter the fields and attributes that you want to add at the top level on the Enhancement Definition tab page. The functions that are available in the XSD editor are also available here, but with the restrictions described above. You can look at the XSD representation on the XSD Definition tab page.
/people/michal.krawczyk2/blog/2006/11/14/xipi-data-type-enhancements-standard-business-partner
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Vijaya,
1. message Interfaces
ou use a message interface to describe a platform-independent or programming-language-independent interface, which you want to use to exchange messages between application components using SAP Exchange Infrastructure.
Please go through this link for further reference:
http://help.sap.com/saphelp_nw04/helpdata/en/55/c5633c3a892251e10000000a114084/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/06/1522417c22f323e10000000a155106/frameset.htm
2. message type
A message type comprises a data type that describes the structure of a message. At the following points in SAP Exchange Infrastructure you can refer to the message to be exchanged at runtime by using the message type
Please go through this link for further reference:
http://help.sap.com/saphelp_nw04/helpdata/en/2d/c0633c3a892251e10000000a114084/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/e7/7356405aff1e24e10000000a1550b0/frameset.htm
3. fault message types
Fault message types are designed for application-specific errors that occur on the inbound side and that are reported back to the sender or persisted in monitoring.
Please go through this link for further reference:
http://help.sap.com/saphelp_nw04/helpdata/en/dd/b7623c6369f454e10000000a114084/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/5d/a45c3cff8ca92be10000000a114084/frameset.htm
4. data types
A data type is a basic unit for defining the structure of the data for a message type and, as a result, for the message to be exchanged.
Please go through this link for further reference:
http://help.sap.com/saphelp_nw04/helpdata/en/a5/04623c4f69b712e10000000a114084/frameset.htm
exchangefaultdata and exchangeLogData
All fault message types reference the data type ExchangeFaultData for this part and, indirectly, the data type ExchangeLogData. These data types are automatically created in a namespace when you create the first fault message type there.
5. Datatype Enhancements
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.
Please go through this link for further reference:
http://help.sap.com/saphelp_nw04/helpdata/en/a8/bfc6373c8fea43bdb3541535bcbd43/frameset.htm
6. Context Objects
Context objects are a simple alternative to XPath expressions for accessing the contents of a message.
Please go through this link for further reference:
http://help.sap.com/saphelp_nw04/helpdata/en/d6/e44fcf98baa24a9686a7643a33f26f/frameset.htm
7. External Definitions
External definitions enable you to import WSDL, XSD, and DTD documents to the Integration Repository so that you can access the message definitions they contain as external messages.
Please go through this link for further reference:
http://help.sap.com/saphelp_nw04/helpdata/en/43/ce49ef1019087ae10000000a1553f6/frameset.htm
Mapping Objects
Interface Mapping
Interface mappings register your mapping program for an interface pair in the Integration Repository.
Please go through this link for further reference:
http://help.sap.com/saphelp_nw04/helpdata/en/4f/ef761a5ecfb1418b79896e10fe4c57/frameset.htm
Message Mapping
Please go through this link for further reference:
http://help.sap.com/saphelp_nw04/helpdata/en/d9/cea942ad920c31e10000000a1550b0/frameset.htm
Mapping Templates
Just like you can reuse data types in different message types, you can also save parts of message mappings as Mapping Templates and reuse them elsewhere. Once you have saved a mapping template it serves as a copy template that you can then load into other message mappings and modify to fit your requirements.
Please go through this link for further reference:
http://help.sap.com/saphelp_nw04/helpdata/en/79/2835b7848c458bb42cf8de0bcc1ace/frameset.htm
Adapter Objects
Adapter Metadata
With adapter metadata you can define configuration data needed for a certain type of adapter at design time. Adapter metadata define the part of a communication channel that is specific to the adapter type.
Please go through this link for further reference:
http://help.sap.com/saphelp_nw04/helpdata/en/12/f9bb2fe604a94cbcb4c50dc510b799/frameset.htm
Communication Channel Template
You can preconfigure a communication channel with a communication channel template. You can use the communication channel template as a template to define a communication channel at configuration time.
Please go through this link for further reference:
http://help.sap.com/saphelp_nw04/helpdata/en/bd/6af766076e384ebdce621d25161184/frameset.htm
I hope i have helped you clear your doubts.
Reward points if this helps...
Regards
Vani.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
80 | |
24 | |
12 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.