Clarification neded on extended RCVR Determination

Hi Experts,
Plz clarify me here:
1.we can send mesages to multiple receivers based on condition in conditional editor......when exactly we should go for extended rcvr determination?
2.why we need to use a seperate mapping for extended rcvr determination using basis object"receiver determination"? wat is the use of this mapping?
3.do we need to go for enhanced interface face determination everytime when we r gong for extended rcvr determination?
4.Plz let me know what is the sequence of processing steps that takes place in IE/IS...
Thaks in advance.

Hi,
1.we can send mesages to multiple receivers based on condition in conditional editor......when exactly we should go for extended rcvr determination?
Depending upon your requirement like, for same BS you want to send some data to other customers if some field changes. lets say for Cust A , if X fields changes you wanna send some different amount of data ie payload 1, else if X field have diff data which behaves in different way , and sends some other payload to Cust B.
If X = "M"
     Send Payload P1 to Cust A
else if
   X = "N"
     Send Payload P2 to Cust B
else
     Send Default Payload Z1
This is one of the general scenario.
2.why we need to use a seperate mapping for extended rcvr determination using basis object"receiver determination"? wat is the use of this mapping?
As you can see using the above scenario, you must use other or you can resuse the same mapping for different purposes, depending upon your requirement. You can use graphical mapping for conditional values to be fix in target. Also You can provide the context objects depending upon your requirement and then you can refer this to determine conditional receiver in XPATH.
3.do we need to go for enhanced interface face determination everytime when we r gong for extended rcvr determination?
I guess above answers will clarify you why we do this for all receiver determination. in simple way, all receiver needs a Interface mapping, as you know in interface mapping we define the actual path like Source to target with some message mapping X. So for every receiver we should provide the Interface detemination that which mapping program its gonna use.
4.Plz let me know what is the sequence of processing steps that takes place in IE/IS...
To view Pipe line execution steps(You should have access to SXMB_ADM:
1.Go to SXMB_ADM.
2.select Display Pipeline defination option.
3.Select PipeLine Id as (SAP_CENTRAL).
4.Click on Pipelineelement tab.
Then u can see the pipe line steps exactly.
Also in SXMB_moni, take any successful or error message double click and in left hand side you will se the sequence of processing steps.
like
Interface Determination----
ID
Message Split----
Runtime
Message Mapping -
IR
Technical Routing----
ID
Call Adaptor----
ID
Hope this will clarify you.
regards
Aashish Sinha
PS : reward points if helpful

Similar Messages

  • Extended rcvr determination mapping problem...

    Hi experts,
    I am using extended recv determination to achive a functionality.....
    We r creating 2 mappings one for the main mapping( transforming source to target) 2nd mapping is for extended rcvr determination  using receivers message type from BASIS components to determine my target based on conditions...
    the problem is already 2 receivers nodes are there which will trigger 2 receivers based on their own conditions....but now i need to duplicate the subtree and add my conditions to that new subtree...but  after creating the mapping after saving the mapping i am unable to see the newly created subtree...( i guess this problem is with occurence...but i have no idea how to proceed...)
    Plz help me out....
    Thanx in advance...

    the problem is already 2 receivers nodes are there which will trigger 2 receivers based on their own conditions.
    --->
    You can generate these receiver nodes dynamically by checking condition in UDF.
    For more on mapping and UDF refer
    /people/venkataramanan.parameswaran/blog/2006/03/17/illustration-of-enhanced-receiver-determination--sp16

  • Extended Interface determination

    I have a outbound scenario
    R/3 (PO from different vendors)--> Mapping A(or)Mapping B(or)Mapping C-->multiple Partners
    when a puchase order comes to  XI it should be able to recognise either of the mappingsA,B orC.
    Can i use extended Interface determination in this case giving the vendor number(unique) so that the appropriate mapping is selected.
    -Sudhansu

    Hi Sudhanshu,
    As Mark says, YOu can use extended interface determination when you use multi mapping and no need to define BPM for the same.
    But for your requirement, under Standard Interface determination , Give multiple Interface mapping and give Xpath conditions for Vendor number  for every Mapping.
    Let us know if you require more clarifications.
    Best Regards,
    Divyesh

  • Extended receiver determination and Dynamic attributes

    Hello,
    is it possible to access dynamic attributes within an extended receiver determination? Can I modify / set dynamic attributes of an XI message within an UDF in the extended receiver determination mapping?
    In detail: In my scenario I want to use an extended rec. determination, make a lookup in a DB inside the determination in order to define the receiver, and based on the lookup result I want to add some information as dynamic attributes to the XI message, which then can be accessed in the interface determination as conditions.
    Thanks,
    Chris

    Hi,
    In my scenario I want to use an extended rec. determination, make a lookup in a DB inside the determination in order to define the receiver, and based on the lookup result I want to add some information as dynamic attributes to the XI message, which then can be accessed in the interface determination as conditions - See you can do a DB lookup in a msg mapping........but by the time you have reached msg mapping your receiver determination will be done......so  your receiver is already decided............Extended recever determination is for dynamically choosing a recever based on source msg's data.........
    Regards,
    Rajeev Gupta

  • Interface Mapping not listing in the Extended Reciever Determination

    Hi,
    The Interface Mapping is not shown in my Extended receiver determination. I have created and activated the IM & MM using the MT - Receivers within the SAP Basis.
    Regards
    Unni

    Hi,
    You can only choose the Interface mapping for the Enhanced recevier determination in the extended tab of Receiver determination. & I dont see the Interface mapping in the select list.
    Where do I have to check for the proper outbound message???
    Regards

  • Error in Extended Receiver Determination

    Hello Experts,
    We are working on a scenario where, we are using Extended Receiver Determination.
    In this reveiver determination mapping we are doing JDBC lookup and some receivers are determined on that basis.
    Also, we have a default receiver in mapping.
    We are using: SAP PO 7.4 SP 7
    We are getting below error while testing from WSnavigator/SOAP UI, but mapping works when we test it in ESR.
    Error:
    <s:SystemError xmlns:s='http://sap.com/xi/WebService/xi2.0'>
              <context>XIAdapter</context>
              <code>ADAPTER.JAVA_EXCEPTION</code>
              <text><![CDATA[
    com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.aii.adapter.xi.routing.RoutingException: Error while executing receiver determination mapping.
    at com.sap.aii.adapter.soap.web.SOAPHandler.processSOAPtoXMB(SOAPHandler.java:773)
    at com.sap.aii.adapter.soap.web.MessageServlet.doPost(MessageServlet.java:530)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
    at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:202)
    Kindly help.

    hi,
    you r trying to impliment Lookup for the file adapter which is not synch in nature and hance u r not getting the responce back.
    please find the link which deals with how to impliment lookup for file adapter.
    https://www.sdn.sap.com/irj/scn/wiki?path=/display/xi/file%252blookup%252bin%252budf.
    now once u get rhe runtime receiver u can perform enhanced receiver determination (write a simple UDF)
    regards,
    navneet.

  • Want to Use Extended Receiver Determination

    Dear All,
    As my last post I came to know that i was using invaild data in input payload so i now have tested with proper data.
    i am getting lot of invaild things in my input like space ,# and all from ECC side in first step of pipeline(Receiver Determination). so thinking to use extended reciver determination so that there i can validate the input paylaod there only..........is this possible
    Plz suggset.....
    Regards
    Abhay Agarwal

    Hi Abhay,
    As i read the all the posts in this thread.. and ur error status is..
    <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
    <SAP:Category>XIServer</SAP:Category>
    <SAP:Code area="RCVR_DETERMINATION">NO_RECEIVER_CASE_ASYNC</SAP:Code>
    <SAP:P1 />
    <SAP:P2 />
    <SAP:P3 />
    <SAP:P4 />
    <SAP:AdditionalText />
    <SAP:ApplicationFaultMessage namespace="" />
    <SAP:Stack>No receiver could be determined</SAP:Stack>
    <SAP:Retry>M</SAP:Retry>
    </SAP:Error>
    This problem is not from the mapping which will be in interface determination... also,
    the mapping(interface determination) comes only after the receiver determination...
    So the problem lies in the receiver determination configuration....
    please delete the receiver determination once and recreate it once more(some times due to cache problem's)
    For ur requirement dont create the extended receiver determination...(it's required only when u want to determine the receivers in run time)
    To delete the spaces and special chars...
    u can solve these in mapping,using the stringReplace and trim functions....
    Also i doubt if at all the incoming source XML is proper structure or not... please check once in the SXMB_MONI.. the incoming payload.
    Still some problem... please post the problem in detail .. so that others can also understand..
    Babu

  • Extended Receiver Determination in 7.31 IDApi

    Hi,
    I'm using the 7.31 IDApi to create\change an ICO in 7.31 AEX. Currently this is working fine. However, I also need to create an ICO using the Extended receiver determination but I do not see ay function for this in the existing wsdls that SAP has provided.
    I have also referred to William Li's blogs for IDAPi for this.
    Using PI 7.3’s Directory API
    Could you please let me know if creating an ICO with Extended receviver determination from IDApi is possible and any pointers as to how it can be done would be very helpful.
    Regards

    Hi Shiladitya
    I can see that there is a option for dynamic receiver rule in the receiver determination of ICO.
    You can find the same in
    IntegratedConfigurationCreateChangeIn----> IntegratedConfiguration--->Receivers--->DynamicReceiverRule
    I am in 7.31 dual stack SP 07.

  • Extended Receiver Determination

    Hi
    I have scenario like this.
    Sending order file into SAP through XI
    If the order is there in SAP it needs to be send mail along with details of
    order else if this is new order then it needs to posted into SAP and create IDOC .I need to use RFC function module which is developed in SAP that returns 0 or 4
    If SUBRC=0 then need to send mail as I mentioned above
    If SUBRC=4 then need to create Idoc in SAP system.
    Note : without BPM - Need a solution
    Let me know how to use extened Receiver determination.
    Till now I have designed like this:
    In the IR :
    I have created 3 message mappings for this.
    1st one is to decide receiver.
               Source - file
               Target -  Receiver determination (structure - which available in SAP
    Basis software componenet)
    2nd one is to create IDOc
                Source - file
                 Target - Idoc
    3rd one is to create mail
                Source - file
                Target - Mail ( External defination)
    In ID:
    I am using extended receiver determination , their i have given the mapping program which ti determine the receiver.
    Next i have created 2 Interface Determinations,Sender as well as Receiver agreements.
    Finally Activated all .
    While testing i am getting message in the MONI No Receiver agreement found
    Could pls help this case.
    Cheers
    MMV

    Hi Mrutynjaya,
    Rest all seems to be fine, but are you using 2 sender agreements??? You need only 1 sender agreement,as you have only 1 sender. Correct me if i am wrong.
    Regards,
    Sanjeev.

  • Extended Receiver Determination problem

    Hi,
    I am making use of extended receiver determination to send 1 source to multiple target systems. When I was testing so that the interface would just send to 1 target system while still making use of the extended receiver determination, I got the following error CO_TXT_OUTBINDING_NOT_FOUND and "No receiver agreement found". The red flag error occurs during Technical Routing and when I checked the details SOAP Header -> Main, I found that the following:
    Sender Service: ServiceA (correct)
    Sender Interface: InterfaceA (correct)
    Sender namespace: NamespaceA (correct)
    Receiver Service: ServiceB (correct)
    Receiver Interface: InterfaceA (wrong)
    Receiver namespace: InterfaceA (wrong)
    It seems that extended receiver determination was able to successfully determine the receiver service but fail in determining the correct receiver interface and receiver namespace. Does anybody know why this happen and how to correct the problem?
    Some investigation that I already done:
    1.) I temporarily changed the extended receiver determination to a standard receiver determination and specifying the 1 target system explicity without changing any other object in both IR and ID as well as using the same test file. The result is that this worked and the file was sent succefully to my intended target system. This tells me that the problem might either be in the extended receiver determination or in the message mapping or message interface Receivers. Also, this means that all the other objects in ID for this interface is configured correctly.
    2.) I tried hard coding the target system as a constant in the message mapping for the Receivers message type and still make use of the extended receiver determination and I got the same problem mentioned above.
    3.) I tried deleting the receiver determination, activating the changes, re-create the object and activate it and I still got the problem
    4.) I tried checking sxi_cache and everything is up to date and correct
    Any suggestions is highly appreciated.

    Elbert,
    I you are doing only standard receiver determination only and using certain condition you are sending to different targets. If yes check this url:
    /people/prasadbabu.nemalikanti3/blog/2006/09/20/receiver-determination-based-on-the-payload-of-input-dataextended-xpathcontext-object
    Can you please put the payload after message mapping and the xpath condition you mentioned. or if you are doing enhanced receiver determination please check this:
    Re: Error in enhanced receiver determination
    ---Satish
    Edited by: Satish Reddy on Jun 23, 2009 9:08 AM

  • Extended Receiver & Extended  Interface Determination

    Hi Experts,
    Can any tell me what is Extended Receiver & Extended  Interface Determination.
    And the Difference between Standard Receiver & Standard Interface Determination.
    were to use Extended Receiver & Extended  Interface Determination.
    Thanks in advance
    Shakif

    Hi,
    Standard Receiver Determination Features
    Specifying Receivers
    You can specify receiver parties and receiver services. To specify the receiver in more detail, you have the following options:
    &#9679;     Select the receiver from the Integration Directory
    &#9679;     Specify a constant value for the receiver
    &#9679;     Determine the receiver dynamically from the message content
    To enter the necessary details, use the following:
    &#9679;     The party editor for specifying the receiver party
    &#9679;     The service editor for specifying the receiver service
    To call the relevant editor, in the Display/Edit Receiver Determination editor in the Configured Receivers frame, call the Input Help ( ) in either the Party or Service column.
    Defining Conditions
    You also have the option of specifying the conditions to be applied when forwarding a message to the receiver(s) in a receiver determination.
    Generally, a condition relates to the contents of a message; if a specified condition is fulfilled for a particular payload element (the corresponding element has a certain value, for example), then the message is forwarded to the specified receiver(s).
    &#9679;     If you want to specify a new condition for forwarding the message to a receiver, in the table in the Display/Edit Receiver Determination editor in the Configured Receivers frame, choose Insert New Condition () and call the condition editor by using the input help ().
    &#9679;     If you want to specify a new condition for forwarding the message to multiple receivers, in the table in the Display/Edit Receiver Determination editor in the Configured Receivers frame, choose Insert Line After Selection ( ) and call the condition editor  by using the input help (). 
    In the condition editor, you can select an element from the message payload and specify a value with which the value of this element is to be compared at runtime.
    Enhanced Receiver Determination
    Use
    You use an enhanced receiver determination to have a mapping program determine the receivers of the message dynamically at runtime. Instead of creating the receivers in the receiver determination manually, you assign a mapping to the receiver determination and this returns a list of receivers at runtime.
    A typical usage case is if you do not yet know the names of the receivers at configuration time. In this case, you can define a mapping program, for example, which reads a list of receivers from a table or from the payload of the message at runtime.
    You can of course formulate conditions in a standard receiver determination that relate to the content of the message. However, you have to specify the names of the receivers (to which the message is sent under the formulated condition) explicitly in the receiver determination. If you create an enhanced receiver determination, you do not have to specify receiver names at this stage. 
    Integration
    During the definition of the interface mapping, you assign the abstract message interface ReceiverDetermination as the target interface. The message interface ReceiverDetermination is in the Integration Repository in the software component SAP BASIS (namespace http://sap.com/xi/XI/System).
    The message interface uses the message type Receivers and the data type Receivers. The data type Receivers describes a list of receivers and has the following structure:
    The following instance of the data type Receivers contains two receivers. The first receiver comprises a party and service and is identified by a DUNS number; the second receiver comprises a service without a party.
    <Receivers>
    <Receiver>
        <Party agency=“016“ scheme=“DUNS“>123456789</Party>
        <Service>MyService</Service>
    </Receiver>
    <Receiver>
        <Party agency=“http://sap.com/xi/XI“ scheme=“XIParty“></Party>
        <Service>ABC_200</Service>
    </Receiver>
    </Receivers>
    You can specify party and service for each receiver.
    Activities
           1.      Integration Repository: Define the interface mapping. Assign the message interface ReceiverDetermination as the target interface (see above).
           2.      Integration Repository: Define the message mapping or mapping program that is to determine the receivers at runtime. Assign the message mapping or mapping program to the interface mapping.
           3.      Integration Directory: Define an (enhanced) receiver determination.
    &#9675;     Enter the outbound interface of the interface mapping from step 1 in the key of the receiver determination as the outbound interface.
    &#9675;     Assign the interface mapping created in step 1 to the receiver determination.
    Standard Interface Determination
    Use
    You can specify to which inbound interfaces at the receiver the message is to be sent at runtime. You also have the option of specifying a mapping and (when multiple inbound interfaces are defined) a condition for each inbound interface.
    Note the following fundamental cases when assigning multiple inbound interfaces:
    Multiple Different Inbound Interfaces
    Imagine you enter the following interface assignment.
    Inbound Interface
    Condition
    Interface Mapping
    IF_1
    M_1
    IF_2
    M_2
    After the interface determination is evaluated, this results in two messages with the same payload at runtime. A different mapping (either M1 or M_2) is executed for both messages and then they are forwarded to the two interfaces (either IF_1 or IF_2) at the receiver. 
    Multiple Identical Inbound Interfaces with Conditions
    Imagine you enter the following interface assignment.
    Inbound Interface
    Condition
    Interface Mapping
    IF_1
    B_1
    M_1
    IF_1
    B_2
    M_2
    In this case, the conditions are evaluated during the interface determination step. If condition B_1 is true, then mapping M_1 is executed; if condition B_2 is true, then mapping M_2 is executed. The message is forwarded to the same inbound interface at the receiver in both cases. Unlike in the case described above, this does not result in multiple messages with the same payload because only one condition can ever be true at runtime.
    Features
    You enter the assignment between the outbound interface and the inbound interface(s) in a table. Each table line represents exactly one assignment between the outbound interface and an inbound interface. To insert or delete lines, choose Insert One Line After Selection () or Delete Selected Line ().
    Enhanced (Mapping-Based) Interface Determination
    Use
    In an enhanced interface determination you do not enter the inbound interfaces manually, but instead first select a multi-mapping. You get the inbound interfaces from the target interfaces of the multi-mapping. The inbound interfaces are determined at runtime during the mapping step.
    You typically use an enhanced interface determination if the source message has an element with occurrence 0 ... unbounded (for multiple items of a data record) and you want multiple messages (for the individual items) to be generated at runtime.
    For example, you want to split an overall booking for a trip comprising connecting flights into individual booking orders (for each leg of the trip).
    You cannot realize this usage case with a standard interface determination (without using an integration process). A standard interface determination does allow you to specify multiple (N) inbound interfaces (with different mapping).  In this case, N messages with the same payload and different receiver interfaces are generated from the source message before the mapping step; these are then transformed differently depending on the receiver interface. Therefore it is conceivable to write the mappings in such a way that the first mapping from the source message generates a message that only contains the first item, the second mapping generates a messages that only contains the second item, and so on. However, this no longer works if the number of items can vary with each new source message.
    You can use an enhanced interface determination to configure a mapping-based message split for this usage case. You assign the interface determination a multi-mapping that has a target interface with an element with occurrence 0...unbounded. At runtime, the individual messages (for the individual items) are calculated in the mapping step. First, the individual messages are grouped into a bulk message. Then, the bulk message is transferred to the Adapter Engine. The Adapter Engine then splits the bulk message up into the individual messages (see figure).
    Procedure at Runtime During Message Split
    Note that both the bulk message and all individual messages each have a message header with a receiver interface (see figure).
    Receiver Interfaces of Bulk Messages and Individual Messages
    The header of the individual messages contains the relevant receiver interface. It is based on the definition of the multi-mapping. Note that the receiver interfaces of the individual messages may be different. The receiver interface of the bulk message is always InterfaceCollection (namespace http://sap.com/xi/XI/System).
    If the message split only results in one message, the original message structure remains the same. In this case, a bulk message containing just one individual message is not created.
    You can also assign a multi-mapping with multiple different target interfaces to an enhanced interface determination (1:n transformation). Each target interface can contain elements with occurrence 0 ... unbounded.
    Messages cannot be sent by using different Adapter Engines in a mapping-based message split. This affects configuration thus: All receiver agreements that have a receiver interface from the mapping entered in the key must only be assigned communication channels with the following adapter types: 
    -          RFC Adapter
    -          SAP Business Connector Adapter
    -          File/FTP Adapter
    -          JDBC Adapter
    -          JMS Adapter
    -          SOAP adapter
    -          Marketplace adapter
    -          Mail Adapter
    -          RNIF adapter
    -          CIDX Adapter
    The adapters also have to all run on the same Adapter Engine.
    Adapters developed by partners also support a mapping-based message split if they run on the same Adapter Engine.
    Attachments from the original message are not appended to the messages resulting from the message split.
    Activities
    To execute a mapping-based message split, perform the following steps:
           1.      Integration Repository: Define the multi-mapping (see Developing Multi-Mappings for Message Splits).
           2.      Integration Directory: Define the interface determination.
    Note the following:
    &#9675;     The outbound interface of the multi-mapping must be entered as the sender interface in the key of the interface determination.
    &#9675;     The interface determination type must be set to Enhanced.
    &#9675;     Select the multi-mapping you defined previously from the Integration Repository.
    To do so, call input help ().
    The target interfaces of the interface mapping are displayed in the Inbound Interfaces frame.
    The number of messages (for an inbound interface) created in the mapping step is displayed in the Occurrence column.
    Regards,
    Phani
    Reward points if Helpful

  • Extended Receiver Determination option missing

    Hi All,
    In the Receiver Determination the extended receiver determination option is missing. We are on PI 7.0. I would like to know as to which patch level i need to upgrade it to see this option.
    Thanx for all your help in advance
    Regards,
    Abhy

    hi,
    you need to go for: SPS07 which is SP16 in 3.0
    Regards,
    michal
    <a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

  • Multiple targets using extended receiver determination

    Hello,
    One quick question related to extended receiver determination
    for same receiver 4 conditions exists.
    at the same time 3 can become true.
    will the extended receiver determination has the capability to create 3 records for the same receiver depending on the condition?
    if cond1 -->> target1
    if cond2 -->> target1
    if cond3 -->> target1
    if cond4 -->> target1
    ( I am using ext interface determination so that my message inputs to receiver determination is also many )
    but now when  I execute, its executing only first condition n generating records generated with the first condition only.
    regards,
    nikhil.

    im using extended receiver determination n giving 4 diff conditions as inputs to the receiver.
    however, thanks...
    answer is you can do it
    its working

  • Rcvr Determination problem

    Hi All,
    In my scenario there is rcvr determination in ID , but it is throwing an error no Rcvr determination found. What can i do?
    Regards
    Sai

    HI
    this is a common error and relate to a wrong configuration. if you have the rights try a test configuration under tools menu
    please check the service interface (enterprice services in PI7.1)configured in the receiver determiantion and sender agreement.
    take a look to these thread:
    u0093RCVR_DETERMINATION.NO_RECEIVER_CASE_BE No receiver could be determineu0094
    No receiver could be determined - ERROR
    No Receiver could not be determined ?
    Edited by: Rodrigo Alejandro Pertierra on Sep 17, 2010 10:54 AM

  • Standard Vs Extended Interface Determination

    Can someone tell me what is the difference between extended and standard interface determination

    Extended receiver determination is used when you want to decide which receiver's to send the message to based on the content of the input message or some other condition at runtime.
    Here, first you define mapping to figure out the receivers of the msg and then you call this mapping in your receiver determination. the "receiver" message type which is present in sap basis -->... XI/system namespance i think.
    The whole idea behind enhanced receiver determination is that during normal receiver determination the pipe line step for receiver determination is executed before the mapping step this resulted in a limitation in XI that you could not change your receivers based on the mesg content at runtime.
    Now, in enhanced receiver determination XI will first execute this receiver determination mapping and figure out the receivers at runtime and then call the individual mappings.
    Cheer's

Maybe you are looking for

  • Problem with persistence across scenes

    I have a student who has created some code- see below. At the moment this code is in Scene 5 - but the blocks also appear on other scenes. How does he limit this code to just one scene? Can he replicate this to be used on other scenes, but starting o

  • Problem in Crystal Report Viewer 2008

    Dear all, I found that the crystal report viewer 2008  (Windows XP) could not display report properly when the file extension is in upper case. (report.RPT). In order to view this report, I must launch the viewer and click file --> open --> select fi

  • Security question; HELP!

    So, I changed the email and password to my apple account, the only thing left to do is change my security questions, The problem is I can't send a security question reset because it's only giving me the option to send a reset message to my old email

  • Add music to my ipad from second iTunes library

    Hi everyone For syncing, backups, etc I use my iTunes library on my mac for my iPhone and ipad. This includes CDs I have ripped in mp3 I have been reripping my CDs using AIFF. I have these an external hard drive. I also have imported these into MY se

  • How to send pdf files from local dir through emails attachments

    I have some pdf documents in some directory, I want to send those pdf's as an attachment throu emails to the concerned person. Please let me know how to attach the files and send through email. Thanks.