Mapping to leads vs. straight to opportunities

client doesn't really convert leads to opportunities, its more opportunity to quote to order (and quote/order are done in external application). I'm thinking the functionality around leads such as qualify, convert, archive, reject is overkill and to map this client 'leads' right to opportunities instead which simply get closed/lost (customer registered for a demo and went live, vs. only registered but no further - salesperson followsup along the way to get them fully live). This way we can reuse some of the stage definitions in the future (e.g. demo stage, vs. partially live vs. fully live stages) and do some analysis. One bad thing is that I'll
have to add some of the standard lead contact fields on the opportunity definition (phone#, email, etc...). There is no real revenue# (more like an account balance potential), so I may have to hide/rename some fields. Is there more functionality lost that
I should consider with this approach?

The approach you described is OK. Some of our CRM On Demand customers do not use Lead object. You can pull in some of the contact information such as work phone # and email into the opportunity object using JoinFieldValue.

Similar Messages

Problem in XSL mapping with leading zero's

Hi ,
i am facing a problem in disigning a XSL mapping where one of the source field (type string ) ,and I need to remove the leading zero's to map it to target.
we have format-numer ,but It is not working in this case ,may be because of type string.
and the replace command is not supported .
So can any one suggest me some way to resolve this xsl problem.
Thanks,
Raju.

I write an example
xsl file:
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:fo="http://www.w3.org/1999/XSL/Format">
 <xsl:template match="/">
 <doc>
 <xsl:apply-templates/>
 </doc>
 </xsl:template>
 <xsl:template match="source_field">
 <source_field>
 <xsl:call-template name="remove_leading_zeros">
 <xsl:with-param name="value" select="."/>
 </xsl:call-template>
 </source_field>
 </xsl:template>
 <xsl:template name="remove_leading_zeros">
 <xsl:param name="value"/>
 <xsl:choose>
 <xsl:when test="starts-with($value, '0')">
 <xsl:call-template name="remove_leading_zeros">
 <xsl:with-param name="value" select="substring($value, 2)"/>
 </xsl:call-template>
 </xsl:when>
 <xsl:otherwise>
 <xsl:value-of select="$value"/>
 </xsl:otherwise>
 </xsl:choose>
 </xsl:template>
</xsl:stylesheet>
to test:
input xml:
<?xml version="1.0" encoding="UTF-8"?>
<doc>
<source_field>000000123456</source_field>
<source_field>0987654</source_field>
</doc>
output xml:
<?xml version="1.0" encoding="UTF-8"?>
<doc xmlns:fo="http://www.w3.org/1999/XSL/Format">
 <source_field>123456</source_field>
 <source_field>987654</source_field>
</doc>
hope can help you.
regards
Bin

I phone maps lead customers to wrong location. We are losing business...How do we fix this?, I phone maps lead customers to wrong location. We are losing business...How do we fix this?

It has come to our attention that the iphone maps are leading guests to another Motel with a similar name to ours. We are Rockhampton Court Motor Inn they are Castle Court Motor Inn...WE ARE LOSING MONEY BY THIS.....How does this happen and how can it be fixed??????

The maps are provided by Google Maps. Contact them.

Follow-up Activities from Leads/Opportunities

HI,
We have configured the follow-up Activities from Leads/Opportunities in CRM. We created a standalone PCUI BSP iView for Activities and assigned ACTIVITYCRM object type to our Role.
Leads to follow-up Opportunities is working but from Leads/Opportunities to follow-up Activities is NOT working. Standalone Activities is working though directly from the menu.
Any input/thought will be appreciated.
Thanks,
Jas

Please check the follow the below points.
1. SPRO -> CRM -> Layout of user Interface -> Navigation (URL generation) -> Assign Object Method to Role. (Check your role and object with Portal Role)
2. Add "CRM_URL_BUFFER_OFF" = "X" Parameter in SU01 for the user.
3. If you assigned many roles to the user in CRM check the Priority.
I hope it will work.
Regards,
Bala.c

Follow-up: From Leads/Opportunities to Activities

HI,
We have configured the follow-up Activities from Leads/Opportunities in CRM. We created a standalone PCUI BSP iView for Activities and assigned ACTIVITYCRM object type to our Role.
Leads to follow-up Opportunities is working but from Leads/Opportunities to follow-up Activities is NOT working. Standalone Activities is working though directly from the menu.
Any input/thought will be appreciated.
Thanks,
Jas

Hi
We have various Forum categories,
Please post your thread in SAP SOLUTIONS (Forum category )
In that we have variuos forums , you can post your thread in
CRM-People centric user interface
Or
CRM-Webapplications forum
Good luck
Regards
Bala

Linking Surveys with Leads and Opportunities

Hi,
We have a survey associated with each lead and opportunity i.e when creating either a lead or an opportunity there is a tab on the GUI in which we can fill up the survey when creating the lead/Opportunity and then save the transaction. The survey goes to a different Infoprovider and leads and opportunity to their respectice Infoproviders.
We now want to link the survey answers to lead and opportunities. I tried infosets and there doesn't seem to be any linkage between these two . Any ideas or has anyone linked surveys to leads and survey to opportunities. Fyi we are on CRM 4.0 and BW 3.5
Thanks.

The CRM Surveys are fed into the cube 0WS_C01. If you have set the correct setting in the transaction CRM_SURVEY_SUITE, the survey results are extracted to the datasource 0SVY_DATA_1. Through the appropriate GUIDs the answers to the survey from the table CRM_SVY_ANSW (do not exactly remember the name) can be linked to the header GUID in CRMD_ORDERADM_H. (May be through the link table CRMD_LINK)
Doniv

Graphical Mapping Vs XSLT mapping Vs Java Mapping Vs ABAP Mapping

Hi Experts,
I have a question regarding different message mapping options available in XI namely
Graphical Mapping
XSLT mapping
Java Mapping
ABAP Mapping
Q1: Which amoung the above mappings is the best and why?
Q2: On what cases Graphical, XSLT, Java and ABAP Mapping should be used?
Q3: Is it true that graphical and XSLT mappings are converted into Java class internally?
Kindly help!
Thanks
Gopal
Message was edited by:
gopalkrishna baliga

Hi,
There is no hard and fast rule for using the mapping techniques.
Graphical Mapping is used for simple mapping cases. When, the logic for your mapping is simple and straight forward and it does not involve mult hiearchical mapping requirement. and context handling.
Java and XSLT mapping are used when graphical mapping cannot help you.
When the choice is between Java And XSLT, XSLT is simpler than java mapping and easier. But, it has its drawbacks. XSLT can lead to a bad perfrormance if the Source XML is huge.
Java Mapping uses 2 types of parsers. DOM and SAX. DOM is easier to use with lots of classes to help you create nodes and elements, but , DOM is very processor intensive.
SAX parser is something that parses your XML one after the other, and so is not processor intensive. But, it is not exaclty easy to develop either.
For further info on each of the mapping, refer to these links,
Graphical Mapping,
http://help.sap.com/saphelp_nw04/helpdata/en/6d/aadd3e6ecb1f39e10000000a114084/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/43/c4cdfc334824478090739c04c4a249/content.htm
XSLT Mapping
http://help.sap.com/saphelp_nw04/helpdata/en/73/f61eea1741453eb8f794e150067930/content.htm
http://www.w3.org/TR/xslt20/
Java Mapping
http://help.sap.com/saphelp_nw04/helpdata/en/e2/e13fcd80fe47768df001a558ed10b6/content.htm
DOM parser API
http://java.sun.com/j2se/1.4.2/docs/api/org/w3c/dom/package-frame.html
Also, check this thread for more info,
Different types of Mapping in XI
Am not sure about XSLT , but , yes graphical mapping is converted into java classes internally and these classes use SAX parsing as well.
Regards,
Bhavesh

Best practise for storing lead information

Hi all
I'm running a qualification process by using a lead assessment script. Via this script our reps ask the potential customer 8 questions and a score is calculated.
Now the reps will begin the process of converting the leads into opportunities - in a prioritized order based on the assessment script score.
Then information which is entered in the assessment script is stored in 8 fields in the lead record and is relevant to a single department in a hospital (fx anesthesia). This information is very valuable to us in the future - because it tells us a lot about the leads potential for buying other products.
Now I want to make sure that this information is passed on in the most appropriate way when leads are converted to opportunities, contacts and accounts. My first thought was to create the 8 new fields in the opportunity record type and contact record type and map the lead conversion to these fields. By second thought this would provide me with a lot of redundant data. Also the data will be updated regularly - which will cause problems with that solution.
Another option is to display the 8 lead fields as related information on the opportunity and contact record detail page. Or I could pass over the data to the contact record and tell the reps that this is where it should be updated in the future.
I'm pretty new to OnDemand so I might not be on the right track here!? Any help will be very much appreciated :-)
Regards,
Allan

Allan, once the lead is converted the lead record (with your 8 fields) is available as a related record under the opportunity and contact records. This allows you to make any updates to these fields without having to do it multiple times if you were to map them during lead conversion.

Java ,abap and XSLT mapping

Hi all,
can any one provide some material on java ,ABA and XSLT mapping(as i got requirement on my current project)..
thanks in advance.
regards
krish..

Hi
All mapping related links
There is no hard and fast rule for using the mapping techniques.
Graphical Mapping is used for simple mapping cases. When, the logic for your mapping is simple and straight forward and it does not involve any complex logic.
Java and XSLT mapping are used when graphical mapping cannot help you and you have multilevel hierarchy structure data.
When the choice is between Java and XSLT, XSLT is simpler than java mapping and easier. But, it has its drawbacks. One among them being that you cannot use Java APIs and Classes in it. There might be cases in your mapping when you will have to perform something like a properties file look up or a DB lookup, such scenarios are not possible in XSLT and so, when you want to use some specific Java API's you will have to go for Java Mapping.
Java Mapping uses 2 types of parsers. DOM and SAX. DOM is easier to use with lots of classes to help you create nodes and elements, but, DOM is very processor intensive.
SAX parser is something that parses your XML one after the other, and so is not processor intensive. But, it is not exactly easy to develop either.
To know more about each of them please go thru the following links. And if you ask me your which is better, it depends basically on the scenario you implementing and the complexity involved. Anyways please go thru the following links:
Graphical mapping
http://help.sap.com/saphelp_nw04/helpdata/en/6d/aadd3e6ecb1f39e10000000a114084/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/43/c4cdfc334824478090739c04c4a249/content.htm
/people/bhanu.thirumala/blog/2006/02/02/graphical-message-mapping-150-text-preview
http://www.sapgenie.com/netweaver/xi/mapping1.htm
/people/alessandro.guarneri/blog/2006/01/26/throwing-smart-exceptions-in-xi-graphical-mapping
XSLT mapping
http://help.sap.com/saphelp_nw04/helpdata/en/73/f61eea1741453eb8f794e150067930/content.htm
http://www.w3.org/TR/xslt20/
JAVA mapping
http://help.sap.com/saphelp_nw04/helpdata/en/e2/e13fcd80fe47768df001a558ed10b6/content.htm
DOM parser API
http://java.sun.com/j2se/1.4.2/docs/api/org/w3c/dom/package-frame.html
ABAP mapping
/people/r.eijpe/blog
To know more about the value mapping tools for the SAP Exchange Infrastructure (XI), please go thru the following link:
http://www.applicon.dk/fileadmin/filer/XI_Tools/ValueMappingTool.pdf
To get an idea as to what value mapping is, please go thru the following links:
http://help.sap.com/saphelp_nw04/helpdata/en/13/ba20dd7beb14438bc7b04b5b6ca300/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/f2/dfae3d47afd652e10000000a114084/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/2a/9d2891cc976549a9ad9f81e9b8db25/content.htm
most of the links that I have provided also helps you get the step by step procedure of doing the same. And also involves the procedure to implement certain advanced features.
And please go through this link which clearly explains the 3 types of mappings.
/people/ravikumar.allampallam/blog/2005/02/10/different-types-of-mapping-in-xi
regards
Prasad

Java Mapping, XSLT Mapping, ABAP Mapping

Hi Experts,
Could any one explain what is the main features of the following Mapping. How to pick the mapping?
Java Mapping - When to use and what is the advantage.
ABAP Mapping - When to use and what is the advantage.
XSLT Mapping - When to use and what is the advantage.
Graphical Mapping - When to use and what is the advantage.
cheers,
Sunee

There are 4 types of mapping in XI
1. Graphical Mapping
2. XSLT Mapping
3. JAVA Mapping
4. ABAP Mapping
When to use Message mapping
1 When the logic for your mapping is simple and straight forward, you can use
Advantages of message mapping
1)Easy to use.
2) has GUI drag and drop.
3) used for simple mapping cases
4) it does not involve any complex logic
Disadvantages of message mapping
1)has limitation in terms of complex hierarchy
When to use Java mapping
1) Java mapping are used when graphical mapping cannot help you.
Advantages of Java Mapping
1)you can use Java APIs and Classes in it.
2) file look up or a DB lookup is possible
3) DOM is easier to use with lots of classes to help you create nodes and elements.
Disadvantages of Java mapping
1)SAX parser is not easy to develop
2)DOM parser is intensive
3) Java knowledge is required
4) bit complexer
XSLT Mapping - When to use
1)When the required output is other than XML like Text, Html or XHTML (html displayed as XML )
2)When default namespace coming from graphical mapping is not required or is to be changed as per requirements.
3)When data is to be filtered based on certain fields (considering File as source)
4)When data is to be sorted based on certain field (considering File as source)
5)When data is to be grouped based on certain field (considering File as source)
Advantages of using XSLT mapping
1)XSLT program itself defines its own target structure.
2)XSLT programs can be imported into SAP XI. Message mapping step can be avoided. One can directly go for interface mapping once message interfaces are created and mapping is imported.
3)XSLT provides use of number of standard XPath functions that can replaces graphical mapping involving user defined java functions easily.
4)File content conversion at receiver side can be avoided in case of text or html output.
5)Multiple occurrences of node within tree (source XML) can be handled easily.
6)XSLT can be used in combination with graphical mapping.
7)Multi-mapping is also possible using xslt.
8)XSLT can be used with ABAP and JAVA Extensions
Disadvantages of using XSLT mapping
1)Resultant XML payload can not be viewed in SXMB_MONI if not in XML format (for service packs < SP14).
2)Interface mapping testing does not show proper error description. So errors in XSLT programs are difficult to trace in XI but can be easily identified outside XI using browser.
3)XSLT mapping requires more memory than mapping classes generated in Java.
4)XSLT program become lengthier as source structure fields grows in numbers.
5)XSLT program sometimes become complex to meet desired functionality.
6)Some XSL functions are dependent on version of browser.
Advantages of Abap Mapping
1) A person comfortable with OOABAP can go for ABAP mapping instead.
Disadvantages of Abap Mapping
1) Abap knowledge is required
2) bit compexer
For further info on each of the mapping, refer to these links,
Graphical Mapping,
http://help.sap.com/saphelp_nw04/helpdata/en/6d/aadd3e6ecb1f39e10000000a114084/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/43/c4cdfc334824478090739c04c4a249/content.htm
XSLT Mapping
http://help.sap.com/saphelp_nw04/helpdata/en/73/f61eea1741453eb8f794e150067930/content.htm
http://www.w3.org/TR/xslt20/
Java Mapping
http://help.sap.com/saphelp_nw04/helpdata/en/e2/e13fcd80fe47768df001a558ed10b6/content.htm
DOM parser API
http://java.sun.com/j2se/1.4.2/docs/api/org/w3c/dom/package-frame.html
Check this blog on Mapping:
/people/ravikumar.allampallam/blog/2005/02/10/different-types-of-mapping-in-xi
Also, check this thread for more info,
Different types of Mapping in XI

XI 3.0 Which mapping to used when ? If choice is given to me...

Hi
 Out of all mappings (Graphical message mapping ,Java Mapping,XSLT mapping,
 ABAP mapping).
 If choice is given which mapping i need to use? What are the conditions to
 go any specific mapping ?
 Pls...expalin me all in detail
Adv thanx to all res...
Regards
Prasad

Hi Prasad,
There is no hard and fast rule for using the mapping techniques.

Graphical Mapping is used for simple mapping cases. When, the logic for your mapping is simple and straight forward and it does not involve any complex logic.

Java and XSLT mapping are used when graphical mapping cannot help you and you have multilevel hierarchy structure data.
When the choice is between Java and XSLT, XSLT is simpler than java mapping and easier. But, it has its drawbacks. One among them being that you cannot use Java APIs and Classes in it. There might be cases in your mapping when you will have to perform something like a properties file look up or a DB lookup, such scenarios are not possible in XSLT and so, when you want to use some specific Java API's you will have to go for Java Mapping.
Java Mapping uses 2 types of parsers. DOM and SAX. DOM is easier to use with lots of classes to help you create nodes and elements, but, DOM is very processor intensive.
SAX parser is something that parses your XML one after the other, and so is not processor intensive. But, it is not exactly easy to develop either.
To know more about each of them please go thru the following links. And if you ask me your which is better, it depends basically on the scenario you implementing and the complexity involved. Anyways please go thru the following links:
Graphical mapping
http://help.sap.com/saphelp_nw04/helpdata/en/6d/aadd3e6ecb1f39e10000000a114084/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/43/c4cdfc334824478090739c04c4a249/content.htm
/people/bhanu.thirumala/blog/2006/02/02/graphical-message-mapping-150-text-preview
http://www.sapgenie.com/netweaver/xi/mapping1.htm
/people/alessandro.guarneri/blog/2006/01/26/throwing-smart-exceptions-in-xi-graphical-mapping
XSLT mapping
http://help.sap.com/saphelp_nw04/helpdata/en/73/f61eea1741453eb8f794e150067930/content.htm
http://www.w3.org/TR/xslt20/
JAVA mapping
http://help.sap.com/saphelp_nw04/helpdata/en/e2/e13fcd80fe47768df001a558ed10b6/content.htm
DOM parser API
http://java.sun.com/j2se/1.4.2/docs/api/org/w3c/dom/package-frame.html
ABAP mapping
/people/r.eijpe/blog
To know more about the value mapping tools for the SAP Exchange Infrastructure (XI), please go thru the following link:
http://www.applicon.dk/fileadmin/filer/XI_Tools/ValueMappingTool.pdf
To get an idea as to what value mapping is, please go thru the following links:
http://help.sap.com/saphelp_nw04/helpdata/en/13/ba20dd7beb14438bc7b04b5b6ca300/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/f2/dfae3d47afd652e10000000a114084/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/2a/9d2891cc976549a9ad9f81e9b8db25/content.htm
most of the links that I have provided also helps you get the step by step procedure of doing the same. And also involves the procedure to implement certain advanced features.
And please go through this link which clearly explains the 3 types of mappings.
/people/ravikumar.allampallam/blog/2005/02/10/different-types-of-mapping-in-xi
Regards,
Pooja

Types of Mapping

Hi Masters,
I have Small Dought..
We have 4 Type of Mappings,
Genera Message Mapping, JAVA Mapping, XSLP Mapping and ABAP Mapping...

My Dought is ...In which Scenarios we are using this all mappings....
Please give me Clear Idea...
Regards,
SReddy

Hi,
I thought i will start of from scratch.Mapping is basically done to convert one form of xml into another form. This can be done using either of them mentioned below.
- Graphical mapping
- XSLT mapping
- JAVA mapping
- ABAP mapping
There is no hard and fast rule for using the mapping techniques. But, I will try to put things in the right perspective for you.
Graphical Mapping is used for simple mapping cases. When, the logic for your mapping is simple and straight forward and it does not involve any complex logic.
Java and XSLT mapping are used when graphical mapping cannot help you.
When the choice is between Java And XSLT, XSLT is simpler than java mapping and easier. But, it has its drawbacks. One among them being that you cannot use Java APIs and Classes in it. There might be cases in your mapping when you will have to perfrom something like a properties file look up or a DB lookup, such scenarios are not possible in XSLT and so, when you want to use some specific Java API's you will have to go for Java Mapping.
Java Mapping uses 2 types of parsers. DOM and SAX. DOM is easier to use with lots of classes to help you create nodes and elements, but , DOM is very processor intensive.
SAX parser is something that parses your XML one after the other, and so is not processor intensive. But, it is not exaclty easy to develop either.
To know more about each of them please go thru the following links. And if you ask me your which is better, it depends basically on the scenario you implementing and the complexity involved. Anyways please go thru the following links:
Graphical mapping
http://help.sap.com/saphelp_nw04/helpdata/en/6d/aadd3e6ecb1f39e10000000a114084/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/43/c4cdfc334824478090739c04c4a249/content.htm
/people/bhanu.thirumala/blog/2006/02/02/graphical-message-mapping-150-text-preview
http://www.sapgenie.com/netweaver/xi/mapping1.htm
/people/alessandro.guarneri/blog/2006/01/26/throwing-smart-exceptions-in-xi-graphical-mapping
XSLT mapping
http://help.sap.com/saphelp_nw04/helpdata/en/73/f61eea1741453eb8f794e150067930/content.htm
http://www.w3.org/TR/xslt20/
JAVA mapping
http://help.sap.com/saphelp_nw04/helpdata/en/e2/e13fcd80fe47768df001a558ed10b6/content.htm
http://java.sun.com/j2se/1.4.2/docs/api/org/w3c/dom/package-frame.html
ABAP mapping
/people/r.eijpe/blog
To know more about the value mapping tools for the SAP Exchange Infrastructure (XI), please go thru the following link:
http://www.applicon.dk/fileadmin/filer/XI_Tools/ValueMappingTool.pdf
To get an idea as to what value mapping is, please go thru the following links:
http://help.sap.com/saphelp_nw04/helpdata/en/13/ba20dd7beb14438bc7b04b5b6ca300/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/f2/dfae3d47afd652e10000000a114084/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/2a/9d2891cc976549a9ad9f81e9b8db25/content.htm
most of the links that I have provided also helps you get the step by step procedure of doing the same. And also involves the procedure to implement certain advanced features.
Hope this clears your doubt fully.
Regards,
Abhy

Context Mapping for Non-Singleton Node

Hi ,
I have following context structure
Node_A
| attr 1
|________ Node_B
 attr2
 attr3
Node_B is the child of Node_A. NOde_B has attributes attr2 and attr3.
Node_B is a Non SIngleton Node.
Node_B is mapped to Node_View of the View Controller.
Node_A had 2 elements. Initially Element 1 is the Lead selection Element for Node A. I get the reference for Node_B using the Lead Selection Path
NodeA_element1 = Node_A->GET_ELEMENT( ).
Node_B = NodeA_element1->GET_CHILD_NODE( 'NODE_B' ).
Node_B is filled with elements, lets say attr2 = 'Dallas', attr3 = 'Detroit'
Node_View shows the values Dallas and Detrait since its mapped to Node_B
Now the Lead selection of Node_A changes to 2.
I again gett he reference for NOde_B usign the Lead Selection Path (index 2)
NodeA_element2 = Node_A->GET_ELEMENT( ).
Node_B = NodeA_element2->GET_CHILD_NODE( 'NODE_B' ).
Node_B is now filled with, lets say attr2 = 'Mexico', attr3 = 'Canada'
Since element 2 is Lead selection for Node A, now, and NodeB is mapped to Node_View, I expect the contents of Node_View to be attr2 = 'Mexico', attr3 = 'Canada' since this is along the Lead Selection of Node_A
But it stays attr2 = 'Dallas', attr3 = 'Detroit'
So in a nut shell, the Context Mapping of the Non Singleton Node DOES NOT map the Lead selection Path when its parent , changes in Lead Selection.
Is this a BUG ?
Thanks

Hi Anand,
There is no bug. See when you are saying
"Node_B is now filled with, lets say attr2 = 'Mexico', attr3 = 'Canada' "
I am just not sure how you have filled the data in node B. Because the way u populate node data that way only you can get the data. The way you want to get data you must populate data in this way:
1. Get Node A instance let say in lv_node_A.
2. Get Node A element instance (lead selection) in your case lets say in lv_elem_A.
3. Now get node B instance by lv_elem_A->get_child_node( 'B' ) lets say in lv_node_B.
4. Create element of lv_node_B and bind it to the node B and also populate the value of attributes.
Repeat the steps as per your requirement. Also Singleton and Non singleton has nothing to do with this it is all about how the instances will be manged in the memory.
Look at this sample code and will help you while populating data in nested nodes:
 DATA lo_nd_a TYPE REF TO if_wd_context_node.
 DATA lo_el_a TYPE REF TO if_wd_context_element.
 DATA lo_nd_b TYPE REF TO if_wd_context_node.
 DATA lo_el_b TYPE REF TO if_wd_context_element.
 DATA ls_a TYPE wd_this->element_a.
 DATA lv_test LIKE ls_a-test.
 data lv_btest type string.
navigate from <CONTEXT> to <A> via lead selection
 lo_nd_a = wd_context->get_child_node( name = wd_this->wdctx_a ).
@TODO handle not set lead selection
 IF lo_nd_a IS INITIAL.
 ENDIF.
 data count type c.
 data count_i type i value 1.
 do 2 times.
 lo_el_a = lo_nd_a->create_element( ).
 lo_el_a->set_attribute(
 EXPORTING
 name = `TEST`
 value = count_i ).
 lo_nd_a->bind_element( new_item = lo_el_a
 SET_INITIAL_ELEMENTS = abap_false ).
 lo_nd_b = lo_el_a->get_child_node( 'B' ).
 lo_el_b = lo_nd_b->create_element( ).
 move count_i to count.
 concatenate count 'in node b' into lv_btest.
 lo_el_b->set_attribute(
 EXPORTING
 name = `BTEST`
 value = lv_btest ).
 lo_nd_b->bind_element( new_item = lo_el_b
 SET_INITIAL_ELEMENTS = abap_false ).
 count_i = count_i + 1.
 enddo.
This code will set value 1 and 2 in node A's test attribute. and on change of lead selection between 1 and 2 it will show value of attribute BTEST in node B as 1 in node B and 2 in node B...
Regards,
Neha

Can't show Greate Circle Route (in SRID 8307) in Map Viewer

I've got a task to show flight tracks on the world map in Map Viewer.
I've got a table with appropriate geometry
INSERT INTO USER_SDO_GEOM_METADATA (TABLE_NAME, COLUMN_NAME, DIMINFO, SRID) VALUES (
'TMP_LEG_ARC_001', 'LEG_GEOM',
SDO_DIM_ARRAY(
SDO_DIM_ELEMENT('LONG', -180.0, 180.0, 0.05),
SDO_DIM_ELEMENT('LAT', -90.0, 90.0, 0.05)
8307);
I've got a theme created from this column. It's evident that flights (and any other straight lines on the earth surface) should look like arcs but in MapViwer I can see straight lines.
It looks like Map Viewer just projected ends of line on the map and then draw straight line between them, instead of projecting whole line on the map (which should be converted into arc)
What have I done wrong?!
Edited by: Wishmaster on 08.11.2012 21:38

MapViewer doesn't display them as great circles. This will be fixed in a future release.
Meanwhile you can use Oracle Spatial functions to create the sissified lines which will approximate/be displayed as flight paths/great circles.
That is use something like Dan Geringer's (sample code so usual disclaimers apply) densify_line plsql stored procedure below.
The densify_line function takes two arguments:
• two_pt_line - The line to densify
• arc_tolerance - The interval (in meters) used to densify the line
The first argument calls for a two point line. It ensures the endpoints are included in the densified result.
You can also pass in a linestring with more than two points. The end points are ensured to be part of the densified line, but the intermediate shape points are not. To guarantee shape points, you can call densify_line iteratively with the 2 point line segments of a linestring.
CREATE OR REPLACE FUNCTION densify_line (two_pt_line MDSYS.SDO_GEOMETRY,
arc_tolerance number) RETURN MDSYS.SDO_GEOMETRY
DETERMINISTIC IS
lrs_segment MDSYS.SDO_GEOMETRY;
new_point MDSYS.SDO_GEOMETRY;
densified_line MDSYS.SDO_GEOMETRY := mdsys.sdo_geometry (two_pt_line.sdo_gtype,
two_pt_line.sdo_srid,
null,
mdsys.sdo_elem_info_array (1,2,1),
mdsys.sdo_ordinate_array ());
curr_measure NUMBER;
times_to_loop NUMBER;
BEGIN
IF two_pt_line IS NOT NULL
THEN
densified_line.sdo_ordinates.extend(2);
densified_line.sdo_ordinates(1) := two_pt_line.sdo_ordinates(1);
densified_line.sdo_ordinates(2) := two_pt_line.sdo_ordinates(2);
lrs_segment := SDO_LRS.CONVERT_TO_LRS_GEOM (two_pt_line);
times_to_loop := FLOOR (lrs_segment.sdo_ordinates(lrs_segment.sdo_ordinates.count) / arc_tolerance);
curr_measure := 0;
FOR i IN 1 .. times_to_loop LOOP
curr_measure := curr_measure + arc_tolerance;
densified_line.sdo_ordinates.extend(2);
new_point := sdo_lrs.locate_pt (lrs_segment, curr_measure);
densified_line.sdo_ordinates(densified_line.sdo_ordinates.count-1) := new_point.sdo_ordinates(1);
densified_line.sdo_ordinates(densified_line.sdo_ordinates.count) := new_point.sdo_ordinates(2);
END LOOP;
IF curr_measure < lrs_segment.sdo_ordinates(lrs_segment.sdo_ordinates.count)
THEN
densified_line.sdo_ordinates.extend(2);
densified_line.sdo_ordinates(densified_line.sdo_ordinates.count - 1) :=
two_pt_line.sdo_ordinates(two_pt_line.sdo_ordinates.count - 1);
densified_line.sdo_ordinates(densified_line.sdo_ordinates.count) :=
two_pt_line.sdo_ordinates(two_pt_line.sdo_ordinates.count);
END IF;
END IF;
RETURN densified_line;
END;
/

Extraneous lines in printing a map

On some of our computers, when we send a map to the plotter from Acrobat, we get extraneous long lines across the page. These are always a line symbol that is really on the map, but shoots off straight from a vertex somewhere. These lines do not show up when you view the file in Acrobat, they only appear on the plotter. All the computers are using Acrobat Reader 8.1.2, but only some have the issue. The problem seems to be specific to a login. If I login as myself on a coworker's computer I have the problem, but he does not when he logs in as himself. There must be a setting in Acrobat somewhere that we have changed on some computers and then forgotten about.
These maps are generated in ESRIs ArcMap GIS software and are 36 X 60. Most of the files are about 50 MB. Each map has lots of line contour lines and such. The computers are all running XP SP3 and are printing to an HP Design Jet 4000ps large format plotter. We are not using the Postscript driver.

This problem appears to be caused by checking auto-rotate on the main Print dialog instead of on the plotters Properties dialog. Also, it may be important to select the orientation correctly on the plotters properties dialog.
Uncheck Auto-Rotate and Center on the main Print dialog.
In the plotters Properties window, check Autorotate and set the Roll Size.
On the Finishing tab of the Properties dialog, choose Portrait or Landscape.

Mapping to leads vs. straight to opportunities

Similar Messages

Maybe you are looking for