on 05-03-2008 3:26 PM
Hello Sdners
I am confused about whether to use fixed or value mapping for my scenarios.. do u have idea?
Hi,
Refer the below link for more information:
http://help.sap.com/saphelp_nw04/helpdata/en/43/c4cdfc334824478090739c04c4a249/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/13/ba20dd7beb14438bc7b04b5b6ca300/frameset.htm
Value mapping:
You use the value mapping function to map different representations of an object to each other.
/people/sreekanth.babu2/blog/2005/02/23/value-mapping-replication
/people/sreekanth.babu2/blog/2005/01/05/design-time-value-mappings-in-xslt
Fixed mapping is simple:
in fixed mappping in a table u define the input value and output value.
Example
A->X
B->Y
c-> Z
u maintain the above values in Fixed value and accordingly u will get the output based on the input.
Chirag
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Deepak,
Function Category: Conversions
Function
Use
FixValues
Executes a value mapping using a fixed value table that you complete using the function properties. The table is saved together with the most current message mapping and can only be used once.
Value mapping
Executes a value mapping for the value I entered. In the function attributes, assign the both input value I and source value O to a representation in the value-mapping table. In this way, you can assign source and target structure fields to a representation. You complete the value-mapping table on the configuration maintenance screen in the Integration Builder. Since these entries are not available at design time, the mapping result is just an estimate when you test the message mapping. See also Value Mapping
The runtime interface for value mappings has changed for XI 3.0. However, XI 2.0 message mappings that call the Value Mapping function still function using the old runtime interface. To use the function parameters in the new runtime interface, choose XI 3.0 Interface.
In the function properties for the standard function Value mapping, in the fields Agency and Schema, enter the key for the source or target value. These values can have any values. However, you can also refer to the fields SenderParty, SenderService, ReceiverParty or ReceiverService. The mapping runtime replaces these values at runtime with the values from the corresponding fields in the message header of the message for which a value mapping is being executed.
In the field Agency you can also enter the name of a business system. When transporting value mappings from one Integration Directory to another, the Integration Builder sees if you have entered a business system as the agency and converts it during the transport (see also: Configuring Groups and Transport Targets).
Go through this IMP Links..
Fixed Mapping:
http://help.sap.com/saphelp_nw04/helpdata/en/2f/41e641fb6e3f5de10000000a1550b0/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/43/c4cdfc334824478090739c04c4a249/content.htm
Value Mapping:
http://help.sap.com/saphelp_erp2004/helpdata/en/d3/4017d9b90afe4999dbf8792638b291/content.htm
Thanks,
Satya Kumar..
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I dont know whether I understood your question or not but my interpretation : Fix mapping is declared and defined itself in mapping ,so if you want to use the conversion fix mapping table in many scenarios ,then you should go for value mapping ,which is defined once in the ID.
Later if you make changes also to the value mapping table ,then it will be reflected in all the interfaces ,but for Fix mapping ,you need to go to individual interfaces and change the entries for fix mapping.
Thanks
Kunal
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
93 | |
10 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.