ERROR: program XMIIIDOC01 not registered

[yasin_kurtulus]

Hello Experts,

I'm a Basis guy.

We have MII 15.3 and S/4 Hana 1809 systems. Two systems are Production.

The S/4 Hana distributed system, ASCS App1, PAS App2.

The MII distributed system too, SCS App1, PAS App2.

Two systems' instance number 00

We would like to connect these two systems via Idoc. that's what I mean.

I have maintained XMIIIDOC01 Resource Adapter on MII Application Resources.

ServerName entry is PAS hostname so app2.company.com

acl mode = 0 on S/4. (I know the risk, I will maintain acl list later)

I create an XMIIIDOC01 RFC and test it, error occurs.

Kernel release 773 SP 201

I added sapmsSID 3600/tcp entry for S/4 services file on MII.

No restriction between two systems.(Firewall etc.) Ping or telnet successful.

So what should I do for this issue?

Thank you.

[former_member185280]

In addition to Mikes suggestions I would check the logs on the NW/MII side as well. There can sometimes be useful clues about where the connection is going wrong in there. From you pics I can see that your Gateway Options is not set and I think it has to be for MII to connect properly but I am not sure. Go thru the docs Mike provided I think it will help find the issue.

Regards,
Christian

[agentry_src]

Hi Yasin,

80-90% of the time there is an issue with an IDoc Listener, it is because the Program ID is not unique. Since the MIIIDOC01 is already defined in NW as an IDoc Listener and you used the same name as your program ID, this is most likely the issue. Check out these two documents for more details, although both are quite old. HANA does have some differences in configuration (like no need for SYNCH), but the general gist is still there.

How to Send an IDoc from SAP ECC to the SAP MII IDoc Listener (MII 12.1 to ECC 6.0)

Troubleshoot issues with MII-ECC connectivity

Best first step is to come up with a different ProgramID. If you are in Production, something like MII_Prod1 is recommended. If you are working in Dev then MII_Dev1. And no you can't use the same Program ID in Dev and QA and Prod.

Cheers, Mike

[former_member788389]

Hi,

Make sure that Gateway Options in SM59 has been set correctly, then check the NetWeaver AS Java logs. Probably the root cause is that the Program ID hasn't been registered on S4 side because of DENIED PERMISSION of gateway security. If so, edit these two files: reginfo and secinfo located on /usr/sap/SID/SYS/profile path in the ABAP server and add permission for registering external program from AS Java host. Refer to note 2348099 for more info.

Regards,

SedraPro

[former_member610632]

After repeated tests, you need to change the value of maxreaderthreadcount of xmiiidoc01 from 0 to 1 (tested) or other (not tested)

[Private_Member_221638]

Can you check the netweaver logs? Usually when I get this message, it's something on the S3/S4 side. Are you sure the programID has been registered correctly on S4?

[yasin_kurtulus]

In addition, I run the command as below

It works but this is temporary solution because when I exit the cmd it does not work again.