Skip to Content
author's profile photo Former Member
Former Member

Urgent Suggestion on better apporach..!! Multi mappings or normal Mappigs.

Hi All,

1) My Client requirement is that they want all the PO's interfaces into one namespace ( http:/xxx.com/PO> ).So that they can create all the PO's which belongs to different customers by different mappings under one namespace.The reason for this is in future if they want to add any new customer .Then it will be easy for them to do the same.

Can we do this by multi mapping?

or

Since the mappings are different for each customer.

Ex: for 3 customers(Colgate,Closeup,pepsodent)

So there will be three separate mappings i need to do.

<b>2)</b> But i suggested to create the namespace according to there customers like

http:/xxx.com/colgate>

Under this we can create <b>PO,Invoice,REMDEV</b> etc for each customer... i think it will be a good method because it will be easy for the maintaince and support.

NOw i need to explain to my client which is the better approach and why??

I need to give the Pros and Cons on the two methods.. like there performance and If they want to add a new customer in future which will be the easy and better option.

Pls share some suggestions on this.

Its a bit urgent.

Thank you.

Regards

Seema.

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

5 Answers

  • Best Answer
    Posted on Nov 21, 2007 at 05:59 AM

    Hi,

    As far as i understand your question, you need to dynamically determine the mapping based on the Customer field sent in Source Message Type. So there cant be Multi-mapping implementation( Multi-mapping can be done when at Source message has to be mapped to all the target messages at a time)

    So you need to have 3 Msg mappings.You can determine the required mapping at runtime by specifying conditions in Receiver Determination.

    Regards

    Arpil

    • Please award useful answers.

    So that they can create all the PO's which belongs to different customers by different mappings under one namespace.The reason for this is in future if they want to add any new customer .Then it will be easy for them to do the same.

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Nov 21, 2007 at 04:18 AM

    <i>Can we do this by multi mapping?

    or

    Since the mappings are different for each customer.

    Ex: for 3 customers(Colgate,Closeup,pepsodent)

    So there will be three separate mappings i need to do.</i>

    >>>

    go for 3 different mappings.

    <i>

    NOw i need to explain to my client which is the better approach and why??</i>

    >>>

    my suggestion is make a SWCV . eg. SWCV_PO

    and then under the same create different namespaces according to the customers

    eg.

    http:/xxx.com/colgate

    http:/xxx.com/ge

    etc.

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi Vijay,

      Thanks for your reply.I think thats a good approach.

      One more point is since the structure is same for PO(orders.orders05) for all the customers.Cant i acheive it through Multi mapping instead of normal mapping??

      1. Performance wise which one wil be good? Pls give me with reason.

      2. Maintainence wise which one will be good? (I think normal mapping would be good i feel.)

      Waiting for reply.

      Thank You.

      Regards

      Seema.

  • author's profile photo Former Member
    Former Member
    Posted on Nov 21, 2007 at 04:50 AM

    Seema,

    I would suggest you to go for different mappings for different vendors under the same name space.

    You can create one data type and use them for all the vendors (In case you are mapping to the same BAPI or IDOC structure). This will reduce the burden of creating separate data types for different vendors.

    Thanks,

    Sudhir

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      hi seema,

      you can go for one Namespace , you can go for any no. of mapping for your vendors in one interface , you can add or delete any mapping which is required or not depands on you<b> ,if you want to chng vendor so just asssign this new mapping to your scenario in inteface mapping, no need to chng in ID part.</b>

      hope this will help

      regards

      HONEY

  • author's profile photo Former Member
    Former Member
    Posted on Nov 21, 2007 at 05:44 AM

    Hi

    I would suggest you to create one Software Component Version.Underneath that one name space with the you interface.As you say that the interfaces are same.

    Now you can go for Enhanced Receiver Determination.

    /people/venkataramanan.parameswaran/blog/2006/03/17/illustration-of-enhanced-receiver-determination--sp16

    Here you will create different CC for different receivers.Different mappings for different receivers.And one reciever Agreement to determine the receiver.

    When a new receiver comes , create a CC, mapping etc for it in the same name space..

    Thanks

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi Seema,

      R u using the same mapping for all the customers with the same functionality.

      Does your input file contains any customer number from which you can identify this input file is belongs to which customer.

      Pls give your inputs for the above question so that i can give you the solutions.

      Thnx,

      Chirag Gohil

  • author's profile photo Former Member
    Former Member
    Posted on Nov 21, 2007 at 05:26 AM

    Seema,

    Yes, you can achieve this by creating the mappings under the same name space. If you want to add a new vendor you can directly add them under the same name space created.

    Similarly, you can create different Business scenarios for different vendors under the same CS, so that you have a dedicated communication channel for each vendor. Let me know if this helps you.

    Thanks,

    Sudhir

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.