Cannot find intf mapping in interface determination

Hi all,
I have these bpm steps 1. Trasnformation followed by send sync. i am trying to do a receiver JDBC sync call to oracle db.
1. in my transformation i have my:
1. Request message : messageA mapped to
2.Response message JDBC request and in my sync send step i have specifed,
1.Request Message : JDBC Request
2. Response Message :JDBC response
I have the following MI defined:
1. Abstract Async - Message A
2. Abstract Async  - JDBC Request
3. Abstract Async  - JDBC Response
4. Abstract Sync  - JDBC Request
                  - JDBC Response
in my ID , when i configure for my interface determination, i cannot slect my inbound interface nor my interface mapping...It says no object found!
Although i activated them in my IR. I did Cache refresh,SLD cache..No Luck
Pls advice

Hi,
><i>in my ID , when i configure for my interface determination, i cannot slect my inbound interface nor my interface mapping...It says no object found!</i>
Are you using a Business Service for your JDBC? if yes, did you assign the Message Interface to the Inbound of your Business Service.
As you are doing the transformation inside the BPM, there will be no need to select the Interface Mappuing in Interface Determinaytion.
Also, in your Intefrace/ Receiver Determination, the Sender message Interface will be <i>4. Abstract Sync - JDBC Request - JDBC Response</i> . You also should have created an <b>Inbound Synch Message Interace with JDBC request and JDBC Response</b> and this should have been assigned to the Inbound Message Interface of your JDBC service.
Regards,
Bhavesh

Similar Messages

  • Cannot find the maps stored in import manager during port creation

    Hi All,
    I am unable to find any maps that i saved in import manager during port creation ,the maps are not showing in dropdown list during port creation in console.Do i need to store the maps that i have in import manager in specific place under mdm server,so that i can see them during port creation.
    All i need to do is assign my import map during inbound port creation,but i cannot find any maps in console.
    Could I know whether i am storing my maps some where other than default location.
    Thanks
    Aravind

    Hi Aravind,
    First of all check the remote system assigned to ur Port. After that go to import manager. When u logon to the import manager, u get a window "Connect to source". Mention the same remote system over there.Select the file type.Browse the file and map the fields,values,field matching and save the map. then unload the repo and assign the map to the port.
    Second way is, u create the port first and give any particular remote system to it. Put the file (u want to use for mapping) in the ready folder of that port and in connect to source window select the type as port, remote system(ame as used port port) and port.then map and save. unload the repo and assign the map to port. Ready folder will be in ur server at location: C drive or D drive->SAP MDM 5.5 ->server->distributions->repo name->inbound->port code->ready. For this option, Ur port type should be manual. After assigning the map u can change it to automatic or keep it manual as per ur requirement.
    Hope this solves ur problem.
    Regards,
    Dheeraj.
    Edited by: Dheeraj Kumar on May 6, 2008 9:16 AM

  • P67-C43 "cannot find required map name"

    Hello
    Specs:
    P67-C43
    RAM: Gskill DDR3 1333 8GB
    Video card: 4870 XFX 1GB
    PSU: Antec 620W
    CPU: i5 2500k @ stock 3.3ghz
    DVD drive: Sony (don't know exactly)
    HD: 1TB Samsung
    & A Hyper 212+
    I'm getting this message
    EFI Shell version 2.00[4.640]
    Current running mode 1.1.2
    map: cannot find required map name.
    Press ESC in _ seconds to skip startup.nsh, any other key to continue.
    Shell>
    I don't get that message when I take out or put in a new stick of RAM. Instead, I can go the BIOS and change settings or load default settings. If I choose default settings/boot then I get the message.
    Any help please. Please don't tell me it's DOA :(

    Quote from: petersonx on 14-May-11, 23:52:55
    I don't get that message when I take out or put in a new stick of RAM. Instead, I can go the BIOS and change settings or load default settings. If I choose default settings/boot then I get the message.
    Can you further explain on this part?
    Do you already have an OS installed to the system? If you do, does the message pops up when you do the OS installation?

  • MSI Z77A-GD65 Cannot Find Required Map Name

    Hello, I am trying to do my first build ever and ran into an error with the MSI 7ZZA-GD65 motherboard. I tried to do a build outside of the case to make sure everything was running and I got an error when booting up my system. It states.
    EFI Shell version 2.31 [4.6530
    Current running mode 1.1.2
    map: cannot find required map name.
    Press esc in 1 seconds to skip startup.nsh, any other key to continue.
    Shell> _
    There isn't much plugged into the board right now I have.
    CPU: Intel i5-3570k
    RAM: 1 stick Billistix in slot DIMM 1
    GPU: Asus Gtx 660ti
    PSU: Seasonic M12 II 620w Bronze
    I couldn't find anyone else getting the error so I posted here. Please help if you can.

    Quote
    RAM: 1 stick Billistix in slot DIMM 1
    Is that the second slot from the CPU ? If not, then insert it into that second slot. Afterwards do a full CMOS clear, and then retest.
    Also remove that GPU card for now and test with only the onboard graphics.

  • No interface mapping in interface determination.

    Hi ALL,
    I am doing a simple File to File scenario. i have created all repository elements and activated them.
    Now while configuring them in Directory at interface determination level I can enter
    inbound Interface but in interface mapping i can´t see my Interface mapping object so i am getting error while testing scenario in Directory. 
    Can anybody tell me where exactly can be problem_
    Please note that i have created interface mapping object in repository.
    Thanks,
    Atul

    Hi Atul,
    After creating your business system or business service, click on your BS and include  the sender and receiver interfaces.
    Regards,
    Ramesh P

  • Interface mapping in Interface Determination??

    Hi friends..
    iam doing IDOC to File..
    in message mapping ,i changed the occurance of IDOC to unbounded and did the same in interface mapping also..
    but in intrerface determination i am not getting Interface mapping ,i tried Extended interface mapping also..
    please suggest me..
    thanks and regards
    Ram

    Hi,
    MultiMapping will not work for IDoc's.You need to use Idoc packaging for this,
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/877c0d53-0801-0010-3bb0-e38d5ecd352c
    Is this what you have done?
    Regards
    Bhavesh

  • Calling web service from MBean weblogic cannot find type mapping file

    When calling web service from custom MBean i get java.io.IOException.
    java.io.IOException: unable to find the type mapping resource file for:
    net.msl.sfx.ebooking.client.BookingPartiesServiceService
    at weblogic.webservice.core.encoding.DefaultRegistry.<init>(DefaultRegis
    try.java:67)
    at weblogic.webservice.core.rpc.ServiceImpl.<init>(ServiceImpl.java:83)
    at net.msl.sfx.ebooking.client.BookingPartiesServiceService_Impl.<init>(
    BookingPartiesServiceService_Impl.java:22)
    at net.msl.sfx.ebooking.service.EBookingService.getBookingParties(EBooki
    ngService.java:59)
    The types.xml file is placed in same jar file as the classes such as net.msl.sfx.ebooking.client.BookingPartiesServiceService_Impl.
    When calling the same class/method from a EJB, everything works fine and the web service is called.

    i am having the same problem.
    Do you have a solution now?
    Thanks

  • On running labview cannot find Scaling & mapping or Amp & level measurement VI's

    I am trying to run through the exercises in the getting started book, and in the first few pages it is asking for VI's that I can not find. Using a 1600, 1100 in the 1000 slot chassis. I used all the five disks when installing the software.
    Did I miss something?

    As explained in the on-line help for those functions, they are not available in the base version of LabVIEW. Check to see which version you have.

  • When we  will go for Ectended Interface Determination

    extended interface determination example give me any one...
    Regards,
    Vinay

    Enhanced (Mapping-Based) Interface Determination 
    Use
    In an enhanced interface determination, you do not enter the inbound interfaces manually, but 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:
    ○     The outbound interface of the multi-mapping must be entered as the sender interface in the key of the interface determination.
    ○     The interface determination type must be set to Enhanced.
    ○     Select the multi-mapping you defined previously from the Integration Repository.
    To select the interface mapping, use the 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,
    Raj

  • Problem in Interface Determination

    Hi All,
        While trying to do webservices using webdynpro i was able to do the repository part without any errors but while trying to do configuration i'm facing a problem in interface determination.
    I'm unable to find my interface mapping in the interface determination.
    While trying to search for the interface mapping its showing me as "no objects found".
    Could anyone help me out in this regard.
    Thanks in Advance
    Madhu

    Hi,
    As said by Moorthy, you should able to see interface mapping.You just Copy the interface mapping name from IR and insert at Interface Mapping in interface determination.To insert Interface mapping , right click choose Insert option from context.Save & activate Interface determination.If it is activated successfully every thing is ok.Otherwise once you should check as said by Moorthy and check Namespace of Interface too.Hope this will solve your problem.
    Cheers
    Tiger Woods
    Note:Give the points for helpful answers

  • 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

  • Error when trying multiple inbound interface determination for IDOC

    Hi !
    I have this scenario: File -> XI -> IDOC. 
    For each source file, I need to send multiple idoc packages, all to the same business system, but each package should be the result of different interface mappings.
    All mappings have same source and target message types...e.g. source: MT_MyFile, target: CREMAS04.
    To avoid creating a generic mapping program, we need to duplicate the current mapping program, make it handle the new case, and then add it as second interface mapping in Interface Determination, with same inbound interface, but different interface mapping, without conditions. All interface mapping should execute.
    We are receving this error:
      <SAP:Code area="IF_DETERMINATION">CX_ID_PLSRV</SAP:Code>
      <SAP:P1>Inbound interface was found more than once (for same sender and receiver) for outbound interface urn:xxxxx/xxxx:.MI_xx_xxxxxxxx_xxx_xx</SAP:P1>
      <SAP:Stack>Error when determining the inbound interface: Inbound interface was found more than once (for same sender and receiver) for outbound interface urn:xxxxx/xxxx:.MI_xx_xxxxxxxx_xxx_xx Inbound interface was found more than once (for same sender and receiver) for outbound interface urn:xxxxx/xxxx:.MI_xx_xxxxxxxx_xxx_xx</SAP:Stack>
    Any clues?
    Regards,
    Matias.

    Hi Satish !
    Thanks.
    I need to send different IDOCs to SAME business system.
    In Interface determination I need this:
    Inbound Interface -
    Condition -
    Interface Mapping
    <b>IF_1</b>                     no condition                   <b>M_1</b>
    <b>IF_1</b>                     no condition                   <b>M_2</b>
    I need to send BOTH IDOC packages to same business system.
    But it keeps throwing the posted error.
    Regards,
    Matias.

  • Extended receiver and enhanced interface determination

    Hi,
    Can somebody list me the business cases when we use the extended receiver and enhanced interface determination.In which scenarios we have to use them?
    Where we can use these features and whom they can replace?
    Regards,
    Anoop

    Hi Anoop
    have alook at thses URl's also
    http://help.sap.com/saphelp_nw04/helpdata/en/43/01322a7af25285e10000000a1553f7/frameset.htm
    :Dynamic file and variable substitution
    Similarly Extended Receiver determination is used to determine the receiver at runtime.
    Refer my reply:Re: Condition In Receiver Determination Not Working
    enhancement in ID
    Enhanced Receiver Determination:
    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.
    http://help.sap.com/saphelp_nw04/helpdata/en/43/a5f2066340332de10000000a11466f/content.htm
    Enhanced (Mapping-Based) Interface Determination
    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.
    http://help.sap.com/saphelp_nw04/helpdata/en/42/ed364cf8593eebe10000000a1553f7/frameset.htm
    <b>enhanced interface determination</b>
    /people/robin.schroeder/blog/2006/11/15/using-dynamic-receiver-determination-with-sync-interface
    /people/venkataramanan.parameswaran/blog/2006/03/17/illustration-of-enhanced-receiver-determination--sp16
    List of receivers can be dyamically determined and assigned at runtime using enhanced receiver determination .
    http://help.sap.com/saphelp_nw04/helpdata/en/43/a5f2066340332de10000000a11466f/content.htm
    Thanks
    Pls reward if useful

  • How to find the mapping between External Object Name and Business Obj.

    Hello Gurus
      Anyone who can help me? I would like to know is there any way to know Business Object is behind object associated to Context Node, it seems that for some cases is easy but for instance for object BuilHeader is not the case, at least for me.  View BP_ADDR/StandardAddress, which belongs to UI Component BP_ADDR, has context node HEADER which is associated to BuilHeader. In case to enhance that object (to add new attributes), using EEWB, I need to know what is the business object behind that external name. Somehow I cannot find the mapping between external name BuilHeader and Business Object. 
      Kind regards
    Aleksandar

    Hi Aleks,
    If you want to enhance Business Partner, the object you are looking at should be "BUPA" in EEWB. To my knowledge, there is no place where this kind of mapping is maintained.
    Note 484597 describes where to find the Cookbook  which describes the enhanceable objects and the enhancement process.
    In case your requirement is to add table attributes, you can also  take a look at the wiki link:
    http://wiki.sdn.sap.com/wiki/display/CRM/EEWB-AddingTableattribute
    Regards,
    Nisha

  • Non BPM process - no mapping object found in interface determination

    I'm working on a non BPM synchronous process of kind HTTP=>XI=>RFC
    I completed my design and onto config now. I created receiver determination for HTTP (no sender agreement) and receiver determination for RFC. In my interface determination I cannot find mapping objects.
    I included in HTTP service, the request, sync and response message and RFC shows up naturally with RFC objects.
    Any ideas. I've been struggling with this for over a day now.
    Thanks.

    Hi Parimala -
    Just to clarify, for this scenario, here's what you need:
    <b>Design</b>
    1. One Message Interface (outbound/synchronous) corresponding to your HTTP request/response.  You don't need a Message Interface nor Message Type for your inbound/synchronous RFC.
    2. Request Mapping corresponding to request
    - HTTP request Message Type to imported RFC (request)
    3. Response Mapping corresponding to response
    - RFC.response to some Message Type for the response
    4. Interface Mapping
    - interfaces: your outbound/sync Message Interface corresponding to HTTP request to imported RFC
    - at bottom request tab, select your Request mapping (#2 above)
    - at bottom response tab, select your Response mapping (#3 above)
    <b>Config</b>
    When you say the following:
    >>><i>I completed my design and onto config now. I created receiver determination for HTTP (no sender agreement) and receiver determination for RFC.</i>
    Don't know if that's a typo, but there should only be one receiver determination based on your sending system/service, sending interface (HTTP one), and interface namespace.
    Confirm the above steps and see if that helps.
    Regards,
    Jin

Maybe you are looking for

  • Can't repair disk permissions on OSX snow leopard

    Hello i have some problem with repairing the disk permissions. I tried repairing them twice but they just keep coming back and i tried to do a clean install but after i updated everything they came back again, anyone have a solution to fix this? Here

  • Error: Javax.mail does not exist, please help

    I have copies mail.jar and activation.jar in the classpath directory as instructed, then try to compile but got the below error: package javax.mail does not exist please help. G:\CRD>javac SendMailBean.java SendMailBean.java:22: package javax.mail do

  • How to defer constraint of one schema from another schema

    Hi All, I am having a requirement of migrating data from one schema(SCHEMA_A) to another schema(SCHEMA_B). So I tried to implement the same using PL/SQL. Because of foreign key contraint while migrating child table, Oracle throws an error message lik

  • Field labels for Radio Buttons

    when creating radio button form fields in Acrobat, I'd like to also put a label next to the radio button  that correspond to the value when the specific radio button is clicked (like "Yes", "No" "Maybe")

  • How do i reference a div on html page with php?

    This question is an extension to a topic I asked last week... I am programming a form within a div on the page..   <div id="contact_form">   <form name="contact" action="showEntry()">     <fieldset>       <p>         <input type="text" name="name" id