Skip to Content

AIF Implementation for PI proxies(Outbound)- Part 4

A new AIF structure has to be created similar to the proxy structure that was generated while generating the proxy class.

The structure for  ZAIF_REPAIR_SALES_AND_SERVICEO   shall be used in AIF customizings.

The details of the AIF structure is described below.

Fig 1.

 

Table type  ZAIF_REPAIR_SALE_RECORD_TAB  for component RECORD in Fig 1.

Fig 2.

Main record structure of the outbound with case a header and case lines as the line items for a single case.

Fig 3.

 

ZAIF_NOTIF_CASELN_ITEMS_TAB – Case lines

Fig 4.

Case line structure details.

Fig 5.

Go to part1 for AIF configuration

https://blogs.sap.com/?p=710949&preview=true&preview_id=710949

 

 

 

2 Comments
You must be Logged on to comment or reply to a post.
  • Hi

    apart from handling errors and restarting what other advantages does implementing a outbound Proxy in AIF have over just calling in the regular way ?.   I am particularly interested to know if AIF offers the same ability that a DRF Change Pointer does ?  – A DRF Change pointer can simply be set at the pointing of saving a Master or Transactional record and so that a loosely coupled from the actual Framework that sends / calls the Proxy interface.  Does AIF offer the same advantage ?

    • AIF is mainly used for interfaces error handling and monitoring.

      So there is only way a data change can happen in an inbound interface , is to resend the data again via the interface and then a new message can be seen in the AIF monitoring.

      But if there is any error happening due to the incoming data issue , then appropriate messages can be sent to AIF monitoring screen. Now a business user can check the messages and take corrective action to update the data and restart the interface again. The user can change the data directly from the AIF monitoring in the corresponding data structure.

      Hope this helps.

      Thanks and regards,

      Kangkana deb