DEBMAS!

[Former Member]

I am sending customer IDOCS (DEBMAS) to middleware (XI). I configured it (XI as logical system) in partner profile to receive customer IDOCS.

In the outbound parameters, I configured for DEBMAS with receiver port and other information.

My question is should I have to maintain outbound parameters or inbound parameters for XI logical system?

When I am generating DEBMAS IDOCS, using BD12 tcode, I am getting the following messages.

"1 Master IDOC is created" and

"0 communication IDOCS are created"

I know communication IDOCS are created after looking at the partner profiles. What am I doing wrong here?

Any ideas?

Thanks,

[Former Member]

Absolutely you have to maintain the Inbound Parameters

[Former Member]

Hi Somen,

Yes, you need to maintain outbound parameters (R/3) and inbound parameters (XI) for XI logical system (WE20).

But prior to above activities, you need to setup the distribution model (BD64) in R/3 for R/3 -> XI. Once it is done then generate partner profile (menubar: Environmnet -> Generate Partner Profile). As a result of this, SAP will generate message type SYNCH with basic type SYNCHRON for communication purposes between R/3 to XI.

Now you should be able to generate and send DEBMAS IDoc(s).

Hope this will help.

Regards,

Ferry Lianto

[Former Member]

You will need both: partner profile WE20 and distribution model BD64! Your partner profile config is correct! Once you set up the distribution model you will see the communication idocs being generated!

[Former Member]

Thanks for the replies.

I completed the configuration as suggested. Now I am able to generate the IDOC. But the idoc status is 02.

Here is the error message.

<i>Could not find code page for receiving system

Message no. E0266

Diagnosis

For the logical destination MIDDLEWARE-TEST, you want to determine the code page in which the data is sent with RFC. However, this is not currently possible, and the IDoc cannot yet be dispatched.

Procedure for System Administration

Possible causes are:

1. The entry no longer exists in the table of logical destinations.

2. The target system could not be accessed.

3. The logon language is not installed in the target system.</i>

What am I missing here? Please suggest.

Thanks,

[sridhar_k1]

Make sure the RFC destination assigned to the port is defined properly, Click on test connection and check test is ok.

Regards

Sridhar

[Former Member]

When I click on 'test connection' for this RFC destination, I got the below error message.

ERROR program ES1RFC not registered

LOCATION SAP-Gateway on host ed1db01 / sapgw01

DETAIL TP ES1RFC not registered

COMPONENT SAP-Gateway

COUNTER 151090

MODULE gwr3cpic.c

LINE 1599

RETURN CODE 679

SUBRC 0

RELEASE 640

TIME Tue Oct 3 17:17:15 2006

VERSION 2

Thanks,

[Former Member]

Also, check if you have given the correct name of the registered server program (in SM59). And if you need more info on connectors, take a look at: <a href="https://websmp210.sap-ag.de/connectors">SAP Service - Connectors</a>

[Former Member]

Hi Somen,

It seems there is an issue on gateway connection between R/3 and XI.

Please check with BASIS folk. He/She should be able to figure out quickly.

Regards,

Ferry Lianto

[Former Member]

Thanks for the replies. Its working now.