Build an SAP IDOC Receiver Using the SAP. Net Connector 2. 0. Overview. This blog post describes how to receive an IDOC from an SAP system, using the SAP. Net Connector 2. 0 and Microsoft C. EDITORS NOTE SAP. Net Connector 2. 0 has been replaced by NCo 3. SAP. Net Connector 2. March 3. 1, 2. 01. Introduction. The SAP. Net Connector simplifies creating C programs that can interoperate with an SAP host. The SAP. Net Connector is available from the SAP Service Marketplace. You must have access to the SAP Service Marketplace to be able to download the SAP. Net Connector. The SAP. Register Rfc Program Sap AccountingNet Connector must be installed on your development machine before we begin. An IDOC is an Interface Document that is used to send or receive information to or from an SAP host. An IDOC will consist of a header record and as many detail records as necessary. The header records follow the format of the EDIDC4. EDIDD4. 0 table. Server update in progress. Check back shortly. The exact format of the payload in the detail records depends on the type of IDOC being transmitted. C Code. We will create an application that displays the contents of IDOCs received from an SAP host. Use Visual Studio 2. C console application. Name the new application Idoc. Receive. Add Reference to SAP. Net Connector. In the Solution Explorer,  right click on References and choose Add New Reference. Register Rfc Program Sap ItSelect both SAP. Connector. SAP. Connector. Rfc. Typically, these files will be found in C Program Files. SAPSAP. Net Connector 2. Our program will instantiate a custom class, Idoc. Receiver, that encapsulates the SAP transmit and receive logic. Register Rfc Program Sap' title='Register Rfc Program Sap' />One of the more common challenges related to the SAP NetWeaver BW Accelerator that SAP administrators face is a broken RFC connection between the blades of the BW. The SAP Community is the quickest way for users to solve problems, learn more about SAP solutions, and invent new ways to get things done. Idoc. Receiver inherits from the SAP. Net Connector.   Idoc. Receiver overrides methods from the SAP. Net Connector to manage the flow of IDOCs from the SAP host. Idoc. Receiver also subscribes to two events exposed by the SAP. EAUdmcqEipU/T1-ArIZJMgI/AAAAAAAAAqw/IloTGWJIiEc/s1600/9+file+-+binding.jpg' alt='Register Rfc Program Sap' title='Register Rfc Program Sap' />Net Connector that perform the actual transmission. IDOC Receiver Main Method. Line 5 contains the reference to the SAP. Net Connector that we need. Voodoo Dj Soul Essentials Zip here. The Idoc. Receiver object requires an SAPHost object that is used to configure the connection to the SAP Gateway. Line 9 instantiates the SAPHost object. Line 1. 4 calls the Idoc. Receiver constructor. The first parameter is the SAP Connection String, used to connect to the SAP host. There are three parts of an SAP Connection String a. Program. Name is the program name as it is defined on the SAP Gateway. This value must match the Program ID configured on the SAP Gateway. Use SAP command SM5. SAP Gateway. x. SAPGWnn is the SAP Gateway number to which the IDOC receiver will register. The SAP Gateway listens on a TCPIP port number based on nn value. The actual port number is equal to 3. In this case nn is zero, so port 3. Host. Name is the DNS host name of the SAP server. It is also possible to specify an IP address, like g. Line 1. 6 starts the SAP host, which makes it possible to begin receiving IDOCs. At this point, our program will now be visible to the SAP host, which you can verify using the Test Connection command via SAP transaction SM5. As long as the Idoc. Receiver object remains in scope, it will receive IDOCs. Idoc. Receiver Class. To receive an IDOC, the Idoc. Receiver class inherits from the SAP. Net Connector SAPIdoc. Receiver class. To control the flow of IDOCs, the Idoc. Receiver class overrides certain methods of the SAPIdoc. Receiver class. To actually receive an IDOC, the Idoc. Receiver subscribes to two events exposed by the SAPIdoc. Receiver class. Constructor. Here is the code for the Idoc. Receiver constructor. Idoc. Receiver Constructor. On line 2. 5 we declare our Idoc. Receiver and inherit from the appropriate SAP. Net Connector object. We use the String. Writer on Line 2. IDOC received. The constructor requires two parameters, the SAP Configuration string, and an SAPServer. Host object that is a container for the Idoc. Receiver. Line 3. The transfer of the IDOC raises an event at two times when the transfer begins and when the transfer ends. On lines 3. 2 3. Idoc. Receiver methods to the Begin. Receive and End. Receive events exposed by the SAPIdoc. Receiver class. Our Idoc. Begin. Receive will be called at the start of the IDOC transmission, and our Idoc. End. Receive method will be called at the end of the IDOC transmission. IDOC Flow Control. IDOCs flow out of an SAP system in a transactional way, in that an SAP host will send a particular IDOC once an only once. To accomplish this, the SAP host will put together one or more IDOCs into a transaction and send that off to the Idoc. Receiver that has registered on the SAP Gateway. The transaction is identified by a unique Transaction ID TID that is supplied by the SAP host. The SAP host will communicate with our Idoc. Receiver using the Transaction ID to control the flow of IDOCs from SAP to our program. There are four methods of the base SAPIdoc. Receiver class that we need to override. IDOC Flow Control Methods. In each case, the SAP host expects our code to return a zero if there are no difficulties. The TIDs passed as parameters can be used to verify the state of the transmission. This demonstration code leaves out any processing you may want to use to validate the state of the transaction. The SAP host will first call the Check. Transaction method. If a zero is returned, the SAP host will call Confrim. Transaction. If a zero is then returned, the SAP host will begin transmitting IDOCs. When the transmission is complete, the SAP host will call Commit. Transaction. IDOC Reception. We use two methods to receive the actual IDOCs. At the start of the transmission, we assign a String. Writer to the Event. Arg, which tells the SAP. Net Connector where we want to place the payload of the transmission. When the transmission is complete, we can read from the String. Writer to extract the payload. IDOC Reception. There can be one or more IDOCs transmitted at a time. Adobe After Effects Remove Easy Ease. Your code will need to parse the payload to determine what goes where. If any of your code throws an exception, the SAP. Net Connector will detect that and alert the SAP side. The SAP side will then call your Rollback method. Summary. Using the SAP. Net Connector makes it easy to receive an IDOC from an SAP host. To learn more about IDOCs download the white paper ALE IDOC Leveraging.