http idoc pskb ad default aspx

Автор admin На чтение 5 мин. Просмотров 33 Опубликовано

Содержание

  1. Наши услуги, опыт и специализация
  2. Symptom
  3. Environment
  4. Product
  5. Keywords

Наши услуги, опыт и специализация

Компания iDoc оказывает услуги по внедрению и разработке решений по автоматизации документооборота и бизнес-процессов на платформе Docsvision.

Компания iDoc обладает большим опытом по выполнению проектов любого уровня сложности и масштаба c полным циклом работ — от анализа до ввода в промышленную эксплуатацию.

Компания iDoc специализируется на автоматизации в основном крупных и очень крупных предприятий, реже средних и малых во всех отраслях деятельности, включая нефтегазовую, металлургическую, финансовую, банковскую, строительную, транспортную и другие.

Symptom

  • In an IDoc_AAE scenario, an SM59 destination has been configured in a sender Business System for the connection with Process Integration (PI).
  • The connection test for the SM59 destination fails with the error message:
    • Error when opening an RFC connection
    • «Transaction program not registered», or «Program XI_IDOC_DEFAULT_PID not registered»
  • This error also occurs in transaction SM58 in the sender Business System.

Environment

  • SAP NetWeaver 7.3
  • SAP enhancement package 1 for SAP NetWeaver 7.3
  • SAP NetWeaver 7.4
  • SAP NetWeaver 7.5

Product

Keywords

XI_IDOC_DEFAULT_DESTINATION, 679, ThSAPOCMINIT, Java, Process Integration 7.30, PI 7.30, Process Integration 7.31, PI 7.31, Process Orchestration 7.4, PI 7.4, PO 7.4, Process Orchestration 7.5, PI 7.5, PO 7.5, XI, AEX , KBA , BC-XI-CON-IDO , Problem

There are quite some and detailed posts on emulating the process to post IDoc xml over HTTP and also posting IDoc using SOAP protocol. However, there are times where we want to test these scenarios ourselves using some kind of tools/ Applications. This document details on some of the various tools which we could use to post IDoc XML to sap.

IDoc xml over HTTP

You could follow the blog here from Grzegorz Glowacki for detailed step-by-step procedure to set up the configuration.

In nutshell these are the steps to post IDoc xml to SAP over HTTP:

  1. Maintain distribution model in BD64 & generate Inbound Partner Profiles. Use WE20 to set up partner profiles manually.
  2. Check HTTP is enabled ( which is true in almost every case ) . Tcode SMICM è GoTo è Services (Shift +f1).
  3. Activate the idoc_xml service in SICF . Path /sap/bc/idoc_xml/ Virtaual Host is usually the default one.
  4. Ping http://[server]:[port]/sap/public/ping?sap-client=[client] to get response “Server reached successfully”.

Tools to post Idoc XML :

  • Mozilla Firefox browser with RESTClient addon by Chao ZHOU.

The UI is simple and straightforward. One could click and add additional custom headers & Authentication for the message easily.

Once you install the add on, click on the RESTCLIENT add on to trigger the below screen. Select Method “POST” and enter the url as http:// :

Click on the header and add the header as text/xml and click on Authentication to add the basic authentication as below.

Once you enter the above details and press “SEND” to post the XML to SAP. You should get response as “IDoc-XML-inbound ok”.

IDoc is successfully posted as shown below.

WE05 / WE09 in SAP:

  • Google Chrome with Postman addon by www.getpostman.com with better UI and more features like the possibility to run scripts before request is called and save test cases etc. I like this personally because of the ease of the UI and the possibility to see the History. The working of this tool is similar to REST CLIENT add-on on Mozilla.

Enter the URL/ Endpoint along with selecting basic authorization. Select the format as text/xml in the headers and press SEND to post the IDoc to SAP. Status code 200 represents a successful posting to SAP.

SoapUI is a free and open source cross-platform for testing SOAP and REST services. It has got easy-to-use graphical interface , enterprise-class features and has multiple options when it comes to creating test scenarios. More about SOAP UI here. Download latest version of SOAP UI from here

First step would to create a new REST project as shown below. Click on new REST project and input the endpoint/URL where the IDoc needs to be posted to:

Enter the URL and press enter.

Choose the authentication as Basic and select the Authenticate pre-emptively option.

Now choose the method as “POST” along with selecting the media type as text/xml as shown below. Copy paste the IDoc xml with out any whitespaces and paragraph breaks into the REQUEST /INPUT window as shown below and press on submit.

When the IDoc is successfully received at the recipient SAP system, following success message is shown in SOAPUI.

Important points:

  • Use textfixer to remove the white spaces between the tags and paragraphs in the xml. Formatted XML should like the one below:
  • Always use the addition encoding=”UTF-8″ in the xml message.
  • Some times you get error “IDoc ‘0000000000000000’ has already been received, therefore reception is refused”. To over come this error message, you need to put an external break-point in the include LEDINF10 after the select statement on SRRELROLES. Now make the retrun code to “1” after the select on SRRELROLES , to post the Idoc with out any error. The cause of the error (“I think”) could be due to inconsistency in buffer refresh. Every time an IDoc is posted from one of the above tools, SAP tries to select an IDoc with number 0000000000000000 from SRRELROLES, which seems to always exist and eventually the error.

    No related posts.