Receiving ALEAUD as acknowledgment in ccBPM

[former_member8655]

 

In SAP PI world, getting acknowledgement and processing on the basis of that acknowledgement is a very common scenario. During different use cases, I was required to get response from R/3 system and process it further on the basis of acknowledgement received. The way I found initially, to get the acknowledgement from R/3 system, was to use event and call proxy from the IDOC receiving system.

Blog by Rene Klumberg, Code free dispatch confirmation from ERP to MDM using PI, helps to move ahead it that direction.

Code free dispatch confirmation from ERP to MDM using PI

But what if we don't have the required event as in case with Vendor Business object where we don't have event for Vendor create/change. Then we can schedule report RBDSTATE with variants configured that help to generate acknowledgments ALEAUD for inbound Vendor Create IDOCs. In general, this acknowledgement message, ALEAUD, appears as below image in SXMB_MONI.

To get a separate message entry in SXMB_MONI for ALEAUD, make the configuration mentioned in this link.

http://help.sap.com/saphelp_nw04/helpdata/en/44/a1b46c4c686341e10000000a114a6b/content.htm

So after configuration done based on above link, a separate message appears in the SXMB_MONI.

Now after this configuration with a defined scenario in Integration Directory, these messages can be collected and dumped into any file server for further usage. With the scenario discussed above, we don't have a clear picture of a particular acknowledgment is for which IDOC number till we have a manual check on that.  Now if you have defined a correlation on the basis of field element in messages then we can use these ALEAUDIT for further processing in ccBPM, but again if we don't have any field which can be used for defining correlation then what to do? Can we use IDOC number? but that is generated in adapter, so we don't have IDOC number readily available to compare with ALEAUDIT message received.

So lets start, in this blog I will talk about the scenario, Vendor master create, where after sending an IDOC from SAP PI to a SAP ERP system I want to get an ALEAUD message back and process further based on that message. We need a ccBPM process that will send the IDOC message and then will pick the correct ALEAUD based on the correlation.

But again the question remains the same, what will be the condition in our correlation? I would say IDOC number. Yes, we will have our correlation based on IDOC number. We will have an ABAP mapping program to retrieve IDOC number generated in XI system and then on the basis of the retrieved IDOC number and E1STATE-DOCNUM field of ALEAUDIT message, our correlation will work and get correct acknowledgement and process further.

Let us first start with the scenario we are going to discuss.

I won't go through the development of all the design objects. I will just provide a reference to the objects that are required and a note for the special interface objects and mapping objects to be created for this scenario.

Object	Name/details	Used By
Data Type	Vendor, Address	Sender Interface
Message Type	Vendor	Sender Interface
Message Interface	Vendor_OB	Sender Interface
	ALEAUD_AB	ccBPM
	CREMAS_AB	ccBPM
	ZALEAUD4XI_AB	ccBPM
Imported Objects	RFC: ZALEAUDIT4XI	ccBPM
	IDOC: ALEAUD.ALEAUD01	ccBPM
	IDOC: CREMAS.CREMAS03	ccBPM, Receiver Interface
Message Mapping/ Interface mapping	Between Vendor and CREMAS	Between source and ccBPM
	An ABAP mapping between CREMAS and RFC: ZALEAUDIT4XI	ccBPM, to retrieve IDOC number

Here is the mapping program; I have highlighted the section in this mapping program that is responsible to get IDOC number based on PI system tables SWFRXIHDR and IDXRCVPOR and then push it into the RFC request message ZALEAUDIT4XI.

method IF_MAPPING~EXECUTE.* initialize iXMLtype-pools: ixml.class cl_ixml definition load.data irc type i.* create main factorydata: ixmlfactory type ref to if_ixml.ixmlfactory = cl_ixml=>create( ).* create stream factorydata: streamfactory type ref to if_ixml_stream_factory.streamfactory = ixmlfactory->create_stream_factory( ).* create input streamdata: istream type ref to if_ixml_istream.istream = streamfactory->create_istream_xstring( source ).* initialize input documentdata: idocument type ref to if_ixml_document.idocument = ixmlfactory->create_document( ).data: ele type ref to if_ixml_element.data: iparser type ref to if_ixml_parser.iparser = ixmlfactory->create_parser( stream_factory =streamfactoryistream = istreamdocument = idocument ).iparser->parse( ).*--------------------------------------------------- ---*----Data declarationdata : oref TYPE REF TO cx_root,l_msgid_ref TYPE string,wa_SWFRXIHDR type SWFRXIHDR,l_msgid type string,l_v_idocnumber type string,l_v_sendersys type string,l_v_msgtyp type string,l_v_createdate type string,wa_IDXRCVPOR type IDXRCVPOR.*---Getting the messageIDTRY.l_msgid_ref = param->get( IF_MAPPING_PARAM=>MESSAGE_ID ).catch CX_SY_REF_IS_INITIAL into oref.endtry.*---Get the Guid for SEND stepselect single guid from SWFRXIHDR into l_msgid where REFGUID = l_msgid_ref and CREA_POINT = 'SEND'.*---Wait so that all the commits are donewait up to 30 seconds.*---Get IdocNumber from this table based on GUIDSELECT single * from IDXRCVPOR into wa_IDXRCVPOR where GUID = l_msgid.l_v_idocnumber = wa_IDXRCVPOR-IDOCNUMBER.l_v_msgtyp = wa_IDXRCVPOR-IDOCTYP.l_v_sendersys = wa_IDXRCVPOR-SNDPRN.l_v_createdate = wa_IDXRCVPOR-CREDATE.*--------------------------------------------------- ---* build up output document =============================================* create output documentdata: odocument type ref to if_ixml_document.odocument = ixmlfactory->create_document( ).data: msgtype type ref to if_ixml_element.msgtype = odocument->create_simple_element(name = 'ns0:ZALEAUDIT4XI'parent = odocument ).irc = msgtype->set_attribute( name = 'xmlns:ns0' value = 'urn:sap-com:document:sap:rfc:functions' ).data: l_idocnumber type ref to if_ixml_element.l_idocnumber = odocument->create_simple_element(name = 'S_DOCNUM'value = l_V_idocnumberparent = msgtype ).data: l_msgtyp type ref to if_ixml_element.l_msgtyp = odocument->create_simple_element(name = 'S_MESTYP'value = l_v_msgtypparent = msgtype ).data: l_sndsys type ref to if_ixml_element.l_sndsys = odocument->create_simple_element(name = 'S_SNDSYS'value = l_v_sendersysparent = msgtype ).data: l_credate type ref to if_ixml_element.l_credate = odocument->create_simple_element(name = 'S_UPDDAT'value = l_v_createdateparent = msgtype ).* render document ==================================================== ==* create output streamdata: ostream type ref to if_ixml_ostream.ostream = streamfactory->create_ostream_xstring( result ).* create rendererdata: renderer type ref to if_ixml_renderer.renderer = ixmlfactory->create_renderer( ostream = ostreamdocument = odocument ).irc = renderer->render( ).endmethod.

ABAP Mapping to retrive IDOC Number. 

Talking about integration process, it will look like this:

Correlation in this integration process is defined based on:

1) IDOC number (generated in XI system and is retrieved in a RFC request message ZALEAUDIT4XI through ABAP mapping) and

2) Field E1STATE-DOCNUM of response ALEAUD (to be received from target SAP ERP by ccBPM).

Step 4 in the ccBPM, which is an RFC call, will trigger an ALEAUD message for the inbound IDOC Vendor Create message. Here the RFC that will trigger the acknowledgement:

FUNCTION ZALEAUDIT4XI.*"----------------------------------------------------------------------*"*"Local Interface:*" IMPORTING*" VALUE(S_DOCNUM) TYPE EDI_DOCNUM*" VALUE(S_MESTYP) LIKE BDAUDSTATE-MESS_TYPE*" VALUE(S_SNDSYS) LIKE BDAUDSTATE-RCV_SYSTEM*" VALUE(S_RCVSYS) LIKE BDAUDSTATE-RCV_SYSTEM*" VALUE(S_UPDDAT) LIKE EDIDC-UPDDAT*"----------------------------------------------------------------------INCLUDE mbdconst.INCLUDE bdcstaud.CONSTANTS:c_max_idocs TYPE i VALUE '500'.TABLES: edidc, sscrfields, bdaudstate.DATA: NEIGHBORS LIKE NEIGHBOR OCCURS 0 WITH HEADER LINE.ranges:s_r_upddat FOR edidc-upddat.DATA:t_idoc_control TYPE audit_idoc_control_tab,t_idoc_control_all TYPE audit_idoc_control_tab,s_idoc_control TYPE AUDIT_IDOC_CONTROL_T ,nothing_to_do,resulting_idocs LIKE bdidocs OCCURS 0 WITH HEADER LINE,g_IDOC_OBJECT like BORIDENT.DATA: paket TYPE i,t_idoc_control_all_max TYPE i,t_idoc_control_all_anz TYPE i.g_IDOC_OBJECt-OBJKEY = S_DOCNUM.g_IDOC_OBJECt-OBJTYPE = 'IDOC'.g_IDOC_OBJECt-LOGSYS = s_sndsys.s_r_upddat-low = s_upddat .s_r_upddat-high = s_upddat .s_r_upddat-option = 'BT'.s_r_upddat-sign = 'I'.append s_r_upddat .* Source IDocCALL FUNCTION 'SREL_GET_NEXT_NEIGHBORS'EXPORTINGOBJECT = g_IDOC_OBJECTROLETYPE = 'OUTIDOC'RELATIONTYPE = 'IDC4'* MAX_HOPS = 1TABLESNEIGHBORS = NEIGHBORS.LOOP AT NEIGHBORS.EXIT.ENDLOOP.SELECT sndprn mestyp mescod mesfct credat cretim docnum statusFROM edidc INTO TABLE t_idoc_control_allWHERE* upddat IN s_r_upddat anddocnum = NEIGHBORS-OBJKEY* AND sndprt = c_prt_logical_system* AND sndprn eq s_sndsys* AND mestyp eQ s_mestyp* AND status <> c_status_in_archive_reload* AND status <> c_status_in_archived* AND status <> c_status_in_orig_of_edited* ORDER BY sndprn mestyp mesfct mescod credat cretim.*IF sy-subrc <> 0.nothing_to_do = 'X'.ELSE.DESCRIBE TABLE t_idoc_control_all LINES t_idoc_control_all_max.LOOP AT t_idoc_control_all into s_idoc_control.APPEND s_idoc_control to t_idoc_control.t_idoc_control_all_anz = t_idoc_control_all_anz + 1.paket = paket + 1.IF paket = c_max_idocs ORt_idoc_control_all_anz = t_idoc_control_all_max.PERFORM idocs_createTABLESresulting_idocsUSINGt_idoc_control.CLEAR paket.REFRESH t_idoc_control.ENDIF.ENDLOOP.ENDIF.IF NOT nothing_to_do IS INITIAL.MESSAGE i139(B1).* Es wurden keine auditrelevanten Daten selektiert.ELSEIF NOT resulting_idocs[] IS INITIAL.COMMIT WORK.CALL FUNCTION 'DEQUEUE_ALL'.* exporting* _SYNCHRON = ' '* exceptions* others = 1.ELSE.MESSAGE i158(B1).* Für die selektierten Daten gibt es keine InteressentenENDIF.ENDFUNCTION.*&---------------------------------------------------------------------**& Form IDOCS_CREATE*&---------------------------------------------------------------------** text*----------------------------------------------------------------------** --> p1 text* <-- p2 text*----------------------------------------------------------------------*FORM idocs_createTABLESresulting_idocs STRUCTURE bdidocsUSINGidoc_controls TYPE audit_idoc_control_tab.INCLUDE mbdconst.INCLUDE bdcstaud.CONSTANTS:c_filter_mestyp LIKE tbd10-objtype VALUE 'MESTYP'.DATA: idoc_control TYPE audit_idoc_control_t,receiver_input LIKE bdi_logsys OCCURS 0 WITH HEADER LINE,receiver_output LIKE bdi_logsys OCCURS 0 WITH HEADER LINE,filter_objects LIKE bdi_fltval OCCURS 0 WITH HEADER LINE,to_send TYPE c,idoc_info TYPE audit_idoc,control_package TYPE audit_idoc_tab.LOOP AT idoc_controls INTO idoc_control.AT NEW mestyp.REFRESH receiver_input.receiver_input-logsys = idoc_control-sndprn.APPEND receiver_input.REFRESH filter_objects.* append entry for filter object MESTYPfilter_objects-objtype = c_filter_mestyp.filter_objects-objvalue = idoc_control-mestyp.APPEND filter_objects.CALL FUNCTION 'ALE_MESTYPE_GET_RECEIVER'EXPORTINGmessage_type = c_mestyp_aleaudTABLESreceiver_input = receiver_inputreceivers = receiver_outputfilterobject_values = filter_objects.* exceptions* mestype_not_found = 1* error_in_filterobjects = 2* error_in_ale_customizing = 3* others = 4.IF NOT receiver_output[] IS INITIAL.to_send = 'X'.ELSE.CLEAR to_send.ENDIF.ENDAT.IF NOT to_send IS INITIAL.MOVE-CORRESPONDING idoc_control TO idoc_info.APPEND idoc_info TO control_package.ENDIF.AT END OF sndprn.IF NOT control_package[] IS INITIAL.CALL FUNCTION 'AUDIT_IDOC_CREATE'EXPORTINGrcv_system = idoc_control-sndprnIMPORTINGidoc_number = resulting_idocs-docnumCHANGINGidoc_info_records = control_package.* exceptions* others = 1.REFRESH control_package.IF NOT resulting_idocs IS INITIAL.APPEND resulting_idocs.ENDIF.ENDIF.ENDAT.ENDLOOP.ENDFORM. " IDOCS_CREATE

RFC ZALEAUDIT4XI to trigger ALEAUD. 

I assume that all the required ALE setting are already done in the target system to receive the CREMAS IDOC and send ALEAUD message as a response back to XI system.

Based on the above correlation correct ALEAUD message will be picked and further processing can be done. There are different fields in ALEAUD which can be helpful like field ALEAUD01.IDOC.E1ADHDR.E1STATE.STAPA1 contains the Document number created in the target system, field ALEAUD01.IDOC.E1ADHDR.E1STATE.STATYP contains the status of the IDOC message which can be used for error processing.

The scenario I have taken gives just a idea on how correct ALEAUD message can be gather in SAP PI. One can add more steps as per requirement too process further on the basis of ALEAUD.