Skip to Content

Sender File Adapter Scenario - Optimization

Hello All,

We have a scenario File - PI - ECC. We have 13 different sender file communication channels (13 different schema's file schemas used). Our goal is to create the scenario with minimal objects i.e least number of Receiver Agreements ,Sender Agreements,Receiver Determination & Interface Determination.

We tried the following :

1) One sender interface with 13 operations. But on the sender agreement side the object is not allowing us to create Sender agreement since we are using :- Same Party : Same Service : Same Interface (The multiple operations are ignored here) and they can only be tied to a single comm channel. Other option is creating seperate communication components but the problem is that we will have to create 13 RD and 13 ID & 13 RA & 13 SA.

Is there a way around this issue ?

The feature of multiple operations is not helping us in reducing the number of objects on the configuration side. Any recommendations on it ?

Thanks,

Kiran

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

4 Answers

  • Best Answer
    Posted on Aug 15, 2012 at 05:56 PM

    I dont think you can avoind Configurtaion to few objects but you can create only one service interface with multiple operations but it does not give any fleaxibility in your case.

    The solution is create one XML schema and it should support 13 message structures then write a conditiopn in interface determniantion to differentiate mapping.

    This case one Sender agreement/Receiver determiantion/interface determiantion but you required 13 receiver agreements.

    But this is not a right design.

    I prefer keep your design as it is.

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Aug 16, 2012 at 04:40 AM

    Hello Kiran,

    You can actually reuse the same sender agreement (still requires one sender cc/agreement) by checking the Sender Uses Virtual Receiver Option, so in your case, it would be 13 sender agreements with different virtual receivers.

    http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/40cb67f7-6464-2b10-bcb9-8edb9a3569f9

    Then after that, it should be possible to just use one RD and ID, and then 13 receiver agreements.

    Hope this helps,
    Mark

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Aug 16, 2012 at 06:21 AM

    Hi Kiran,

    On the sender side. we have to use seperate sender agreements. Each File communication channel should have a unique sender agreement.

    go through obligatiory sender agreements below

    http://help.sap.com/saphelp_nw04/helpdata/en/b1/f29e7a56e18a439984a3c6630951d2/frameset.htm

    On the receiver ECC side what is the adapter is used?

    Is the receiver ECC structure same in all the cases/ is this different structure?

    Reagrds,

    Venu R

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Aug 16, 2012 at 09:02 AM

    Hi Kiran,

    on sender side you cannot reduce the number of your ib directory objects. Each channel needs an agreement and it doesn't matter if you use interfaces or operations. Sending with one Business System would be possible, but not really helping.

    You did not describe the receiver side, therefore we cant support you there.

    I dont think that 13 channels/Business Systems/Interfaces/Agreements are too difficult to maintain. Most PI implementations handle with much more objects. If the scenario is too confusing, just create 13 scenarios inside one folder.

    Regards,

    Udo

    Add a comment
    10|10000 characters needed characters exceeded

    • Thanks Udo,Venu, Mark and Raja for all your valuable inputs.

      We finally went with a scenario with 13 different comm channels for each of the files. Since it is an async scenario.On the outbound side we used one interface with 13 different operations and on the reciever side we have an ECC system and since we used a proxy adapter we had one interface with one operation and one message type and 13 different sub structures for each file type.

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.