Create an inbound interface framework: Guidelines needed

Hi ,
I need to create an bespoke interface framework monitor (and data processing logic) using file transfers (Not using XI ).
Plan is to make the legacy system dump data files on some SAP server(I guess AL11 can show me the files). Then I need to pick the file and process the data and produce an error log. All the incoming, processed or errorred file details need to be displayed on some bespoke interface monitor
What I am looking for is some guidance and helpful tips which could guide me about how to create a bespoke interface monitor.
I would really appreciate if you have any documentation with table structure details, functon modules etc details or just some plan advise on how to start the design of this interface monitor.
Thanks
Shirin

I had to use one like that once. Had no access to codes though, but I can remember more or less how it works.
I remember there were four Z tables. One was the master, where every interface (inbound or outbound) should be registered before being able to be executed (this check were done under the incapsulated code of the functions). Second was responsible for registering processing data (each time an inferface was processed), like how many records were processed, valid processed transactions, etc. Third was to record history data, which user executed the interface, etc.
The last one were used to record restart data, in case some problem happened when processing interfaces.
Interface processings where identified by timestamp. So the generated files where named like INTNAME.<timestamp>, so that the file names not be too confused, or could not be overwritten.
There were function modules resposible for the actions: Init interface, Load Datafiles, Insert BDCData, Call Bapi, Move Datafiles, Done Inteface.
Also there were an include you could use in some programs, containing some macros that would help on log creation / messaging.
This was some of the framework's architecture.

Similar Messages

  • Need information on how to create Idoc Inbound Interfaces for Business Sys

    Hi,
    I'm losing it.
    Can anyone point me to some documentation or an example of how to create inbound interfaces for Business Systems in PI 7.1.
    Here's the scenario
    I'm working on a B2B integration process which sends inbound idocs to an ECC 6.0 system.
    I've created the Business System communication component  but under the Inbound Interfaces it is blank.
    I want to have MBGMCR.MGBMCR03 as an inbound interface.
    But I forget how to get it there.
    For Business components you can just add the inbound interface.
    I've already defined the Business System in the SLD pointed it to the correct Tech System, imported the idoc definitions in the Enterprise Service Builder and set up IDX1, IDX2 to ensure the metadata exists in PI.
    But for Business systems the hep says that it's got to come from the SLD.
    Outbound/Inbound Interfaces
    For each business system, the interfaces that are installed on the business system are also entered in the SLD. These interfaces are displayed in this frame. You cannot add any other interfaces.
    I know I've done this before, but I can't remember how.
    Cheers,
    John

    Hi John ,
    Please have a look at the following links which might be of help to you
    PI 7.1 IDocs interfaces act as operations
    http://www.sdn.sap.com/irj/scn/weblogs;?blog=/pub/wlg/7933
    /people/peter.gutsche/blog/2008/10/27/what146s-new-in-sap-netweaver-pi-71
    There is a section in the following link on IDOC , have a look at the links in that section
    https://wiki.sdn.sap.com/wiki/display/XI/ImportantBlogsand+Notes
    Best Regards

  • Inbound interface with multiple IDOC processing

    Hi,
    I have to create an inbound interface which has to be triggered only when a batch job is completed in the middleware. The batch job will create 2000 records and 1 IDOC for each record. I have to get all the 2000 IDOCs and then process them together. I have to manipulate the data in these 2000 IDOCs and update them in a SAP table.
    Please let me know how do I proceed with this.
    Should I go with a custom func module or a custom program?
    Thanks,
    Abhishek

    Hi,
    Custom function module with standard parameters : For details refer to the topic Implementing Inbound Processing on page 85 of the
    [ALE Programming Guide|http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf]
    regards,
    Advait

  • LIS inbound interface & mystics

    Hi All! Can anybody explain me what is matter? I was creating LIS inbound interface. The system suggested me event and function group. I generated the interface and pointed out the place for saving in request - personal Z-package. Function module was created too. I could find my new function group through SE84. However when I tried to look own package through SE80, I didn't see new group in it. Whole day I struggled against the problem but all my efforts were without result. And I was very surprised when 3 days later the new function group suddenly appeared in my z-package.
    Can anybody explain me what is matter? What is reason 3-day lag?

    This has nothing to do with LIS or even SD. Check with your Basis admin. Maybe there was something wrong with the object directory entry of the function group or with the package. Normally Basis creates the packages and makes sure they have all the right settings. It is possible that your Basis admin ran something within those 3 days that adjusted the object directory.
    Also sometimes there are just plain glitches in SE80. Most of the time log off / log on helps.

  • Inbound Plug in standard SAP (create as an interface)

    Hi All- I have a standard SAP component that I create an Inbound PLUG at the window level, I'm using that component (standard SAP) in another component (custom) but I don't have access to the inbound plug that I just create in the standard SAP because the check-box for interface is not "CHECKED".
    When I try to enhanced the standard SAP the interface check-box disappear, how can I check that check-box interface box?
    How I can make my custom inbound plug accessible globally?
    thanks!
    Jason PV

    You Can not enhance that.( creating interface  inbound plug) according to the sap enhancement documentation.

  • I continue to recieve the error message "Could not create key: Verify that you have sufficient access to that key" when I am try to down Akamai NetSession Interface that's needed to download the adobe photoshop elements 13 software that I purchased.

    I continue to receive the error message "Could not create key: Verify that you have sufficient access to that key" when I am try to down Akamai NetSession Interface that's needed to download the adobe Photoshop elements 13 software that I purchased.

    cancel the akamai download and download files 1 of 2 and 2 of 2 directly.  put both in the same directory and double click the exe to start installation.
    Downloadable installation files available:
    Suites and Programs:  CC 2014 | CC | CS6 | CS5.5 | CS5 | CS4, CS4 Web Standard | CS3
    Acrobat:  XI, X | 9,8 | 9 standard
    Premiere Elements:  13 | 12 | 11, 10 | 9, 8, 7 win | 8 mac | 7 mac
    Photoshop Elements:  13 |12 | 11, 10 | 9,8,7 win | 8 mac | 7 mac
    Lightroom:  5.7.1| 5 | 4 | 3
    Captivate:  8 | 7 | 6 | 5.5, 5
    Contribute:  CS5 | CS4, CS3
    FrameMaker:  12, 11, 10, 9, 8, 7.2
    Download and installation help for Adobe links
    Download and installation help for Prodesigntools links are listed on most linked pages.  They are critical; especially steps 1, 2 and 3.  If you click a link that does not have those steps listed, open a second window using the Lightroom 3 link to see those 'Important Instructions'.

  • How to connect to third party using PI for outbound and inbound interfaces

    Hello,
    I have scenarios where I have data coming in from third party EDI subsystem and sent to SAP. And also from SAP to EDI subsystem. We need to send the XMLs to the EDI subsystema nd also receive XMLs.
    Can someone please suggest the ways I can connect to EDI subsytem for both Outbound and Inbound interfaces.
    Thanks

    Hi Prabhu,
    EDI file is different from the normal flat or xml file. Hope you understand the difference.
    Now if your EDI subsytem has the capability of converting the xml file to edi file viceversa then create and receive the xml file from the EDI subsystem. For the xml file you may use the file adapter as an option.
    If it doesnot have the capability then seeburger adapter needs to  be used. This is not an inbuilt adapter. So your company needs to purchase it.
    Regards,
    ---Satish

  • A more successful experiment in creating compositable user interfaces for Config Dialogs

    A couple weeks ago I posted an experiment in creating compositable user interfaces using transparent subpanels. The approach might best be described as, "It at least was notable for being novel."
    Today, I'm posting another attempt, this one along more traditional lines, and far more successful. Particularly notable: this one can do all the arbitrary composition of the last one AND it solves the TAB order problem.
    This solution uses a picture control and renders N copies of a control. When the user tabs to a control or moves the mouse over the control, a real control slides into that position to be able to catch the events (update mouse over draw state, highlight for keyboard focus, handle typing, etc). When the Value Change occurs, a master array of data is updated and the picture control is updated.
    This is something that has been attempted in various forms in the past, but there are two aspects of this particular implementation that make it nice:
    its programmatic interface for specifying the behavior of the various objects should make it fairly easy for a user of the framework to programmatically generate their dialogs
    it handles the TAB problem without flickering, something I haven't seen in other attemps
    This idea spawns out of conversation about the previous experiment -- thanks to those of you who posted on various forums, e-mailed me, or, in a couple cases, showed up at my desk. That last one is not something I'm encouraging unless you work at NI... just saying. :-)
    Now, this experiement has already yeilded some interesting conversation. We note that as long as controls are instantiated independent of each other -- that is, no property of one control depends upon the property of another control -- this dialog system scales nicely. But in this experiment, I implemented Radio Buttons, which interact with each other -- when one is set True, the others go False. As soon as controls start interacting with each other (such as graying out one control when a checkbox is toggled, or having expandable sections, or really complex cases like updating a graph as some options change, like happens in some Express VI config dialogs) then we start needing ways to refer to the other controls. This rapidly moves us in one of two directions: naming controls or creating references. The naming approach is definitely my preference as it fits better with dataflow and I can do some interesting effects with breaking apart some of the tree. But all of this quickly starts sounding like "Please implement a XAML parser in LabVIEW." For those of you unfamiliar with XAML, in the world of UI design, it might very well be the coolest thing since sliced bread. A XAML string would indeed fit with dataflow, and we could start building that up. I hesitate to head down this road for two reasons. One, as many have noted, there's really not a good XML parsing library written in LabVIEW that can give me a useful DOM tree. Two, that's a huge project and my gut sense is that you'd have to complete a fairly large chunk of it before you'd start seeing any return on investment. But it is worth thinking about -- I might be wrong. Wouldn't be the first time. This code that I've posted today can at least get you started on the generation side if one of you decides to become industrious.
    I'm turning my attention away from this project for now... coding in G is lots of fun, and I wish I could spend more days doing it, but this has been a side project and it's time to get back to my assigned projects in text programming. Building a powerful platform for automatic UI generation in LabVIEW would be really useful -- I see lots of requests for this sort of thing, and other languages are pulling ahead of us in this domain.
    [UPDATE 5/17/2012 - There is an improved version.]
    Solved!
    Go to Solution.
    Attachments:
    ConfighThroughCtrlCreation.zip ‏558 KB

    Elijah K wrote:
    Thanks for posting this Aristos.  I would normally be one of those to go bug you at your desk, but in case I'm not the only one with this question... which particular flickering problem are you referring to?  The act of switching tabs?  In all honesty, I've never noticed...
    When you move controls around on the screen, normally you try to Defer Panel Updates while you do that. But Defer Panel Updates has an effect on control's abilities to catch certain mouse clicks, so when you're trying to move a control to catch the mouse, you have to work a lot without Defer Panel Updates, so if you're adjusting captions, etc, to match the new location, you can see flicker as properties adjust. You can move the control off-screen, as long as you have already updated the picture control to reflect the changes. It took a while to catch all the ways that the flickering can crop up. I think I got 'em all.
    Attached are the VIs saved for LV 2009. Actually, they're saved for LV 8.6, but it doesn't work in 8.6 because of a bug in the picture control that existed back then.
    Attachments:
    ComposableUI_LV2009.zip ‏391 KB

  • 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.

  • Error when determining the inbound interface

    Hi Experts,
    I have a Scenario, where i am using Multi mapping Scenario in DEBMDM IDOC from ECC to Xml_File-1(DEBMAS) and Xml_File-2(ADRMAS).
    When i Execute the Scenario by sending the IDOC from ECC , i am getting the below error.
    Runtime error
    Error when determining the inbound interface: Inbound interface found several times (for same sender and receiver) for the outbound interface urn:sap-com:document:sap:idoc:messages.DEBMDM.DEBMDM06
    Scenario Steps
    1) No Condition in Interface Determination
    2) 0..unbounded in Message Mapping and Operational Mapping.
    3) E1KNA1 is mapped to E1KNA1
    4) E1ADRMAS is mapped to E1ADRMAS
    5) One Message Mapping and 1 Operational Mapping.
    Thanks in Advance.
    Sriram.

    Hello,
    I have a Scenario, where i am using Multi mapping Scenario in DEBMDM IDOC from ECC to Xml_File-1(DEBMAS) and Xml_File-2(ADRMAS).
    Since your scenario makes sure that the 2 files are created, there is no need to use multi-mapping. Rather, you can use an interface determination split. To do this:
    1. declare xml_file1 as service interface 1, xml_file2 as service interface 2
    2. do not change target occurrence in message mapping and operation mapping, maintain it as 1..1
    ( 2 operation mappings)
    3. in ID, add the two service interfaces in your interface determination
    At runtime, it will split into two inbound interfaces.
    When i Execute the Scenario by sending the IDOC from ECC , i am getting the below error.
    Runtime error
    Error when determining the inbound interface: Inbound interface found several times (for same sender and receiver) for the outbound interface urn:sap-com:document:sap:idoc:messages.DEBMDM.DEBMDM06
    Were you able to declare the 2 xml_files as two separate service interface(different names) in your operation mapping?
    Hope this helps,
    Mark

  • Inbound interface found more than once for outbound interface

    Hello everybody,
    i have a simple problem.
    I build a interface with XI3.0
    File to idoc
    for each file i need crate 2 idoc.
    It's not a problem when Idoc type is different, but in my case i need crate 2 idoc of same type but with a different mapping.
    so when i upload the file i have this error:
    Inbound interface found more than once for outbound interface
    how can i solve this problem? can i force this step?
    i thought to create a different idoc type or create the 2 idoc in same mapping , but there is not my favourite solution because in case of error , both idoc will be not created.
    any suggestion?
    thanks in advance
    alex

    Hi,
    Instead of exporting and changing the occurrence as suggested by Ravi,
    use the same Idoc twice in mapping as well as Interface mapping.
    Coming to ID part, do every thing as usual.
    The only thing to note is instead of using normal Interface determination, use extended Interface Determination.
    This will solve your problem. The error will not come again. I'm sure.
    Try out and update the thread.
    Regards,
    Jeevan.

  • Several inbound interfaces in intagrated configuration

    Hi all,
    I want to use an intagrated cnfiguration object for scenario with several inbound interfaces on a receiver side. As for now, I have a usual condition-based interface determination for my receiver system. I've studied all features of "Revceiver Interfaces" tab in IC object as well as corresponding documentation, but found no way to use 2-3 inbound interfaces with conditions for same receiver.
    So the question is: how can we use IC object to have several interfaces on receiver system? I'm talking not about message split, since it's impossible for IC, but about interface determination based on message content.
    Thanks!
    Dmitriy

    Hello
    So the question is: how can we use IC object to have several interfaces on receiver system? I'm talking not about message split, since it's impossible for IC, but about interface determination based on message content.
    Yes, it is possible to use several interfaces on a receiver system. The key here is to group your message types/ed/wsdl under a single outbound interface. You can do this by:
    1.) In your outbound service interface, use Stateless as your interface pattern
    2.) Then under the operations tab, add as many operations as you need. For example, operation1 uses mestype, operation2 uses xsd, and operation 3 uses wsdl and so on...
    3.) Configure your inbound service interface, you can separate them or group them as you like (it depends if they will be using different comm channels) For example, operation 1 can use inbound service interface 1, operations 2 and 3 can use inbound service interface 2
    4.) Configure operation mappings (per operation).
    5.) After cofiguring your comm channels, create the integrated configuration
    6.) Make sure you have a value under the Select Component Version of Sender Interface.
    7.) Your created operation mappings will appear under the receiver interfaces
    8.) And under outbound processing, there will appear the inbound service interfaces
    I hope I have explained this clearly.
    Regards,
    Mark
    Edited by: Mark Dihiansan on Aug 23, 2011 9:15 AM

  • Multiple inbound interfaces (xml) but one target (idoc)

    Hi Experts,
    I am trying to setup in ID four inbound interfaces (eg. MessageType1-MesageType4) and each has an interface mapping having the same target idoc (eg. Shpmnt05).
    Also, there is a condition set per interface mapping. 
    Should I create four sender agreements that is one per message type? If so, how many interface determination is needed? Any advise please.
    IR
    Message Interfaces:
    OA_MessageType1
    OA_MessageType2
    OA_MessageType3
    OA_MessageType4
    Interface Mappings:
    OA_MessageType1_to_Shpmnt05
    OA_MessageType2_to_Shpmnt05
    OA_MessageType3_to_Shpmnt05
    OA_MessageType4_to_Shpmnt05
    ID
    Receiver Determination:
    |Party1|Shpmnt05
    Interface Determination:
    Sender Agreement:

    However, how are we going to handle the interface determination?  I believe in the interface determination setup it asks for the message interface suppose MessageType1.
    Now, I need to set-up the condition (eg. operationtype=Create)  for that message interface and set interface mapping.  For this one the interface mapping to be used is OA_MessageType1_to_Shpmnt05. 
    But in this case, i need to add another condition (eg. operationtype=dummy) so that the first condition will be saved, correct? I think if I only have one condition in the interface determination, once activated the condition is gone.
    Having said, are you suggesting that i need four interface determinations?
    Or is it possible to just have one int. det.?

  • Objects required when publishing inbound interface

    Hi
    We are publishing an inbound interface in SAP PI SR, and implementing proxy in ECC.
    What all objects do we need to create in PI.
    In ESR we will just need one inbound service interface, with request/response messages.
    - Do we need to have any other objects in ESR??
    - Do we need to create any objects in Integration Directory??
    One more thing, when publishing Outbound interface from Sender agreement, we will configure the end points, is it possible to configure endpoints when publishing inbound interface?

    Dear Osman,
    Concerning the issue, kindly go through the following link :
      - http://help.sap.com/saphelp_nwpi71/helpdata/EN/02/265c3cf311070ae10000000a114084/content.htm
    which might help you.
    Best Regards
    Nishwanth

  • Sales order change Inbound interface

    Hi all,
    This is regarding sales order change inbound interface,
    we are using new Z function module for sales order posting(exteded idoc ORDERS05), for this shall i use standard message type,standard process code or custom message and custom process code?
    Regards,
    Suresh.D

    Hi,
    If you are having a custom function then its better you create a custom process code, you need not create a custom message type and also never change any of the standard process codes.
    Thansk,
    Mahesh.

Maybe you are looking for