Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

DEBMAS iDoc Contact Persons Issue

Former Member
0 Kudos
881

Hi Folks,

I have a DEBMAS06 iDoc that is creating a customer. In the main everything is perfect however there has just been an issue raised by the business.

We use contact persons to determine where to send differnt output types, however in small companies, that person would be the same for all output types.

When creating a customer in XD01, if you enter a contact person with the same name, SAP will issue a warning message that you can ignore, however, when using my iDoc, the first contact person entry is added but none of the rest of them are.

Is there a way that I can add the same contact name for multiple contact types in my iDoc?

4 REPLIES 4

Former Member
0 Kudos
286

Hi,

In standard IDOC its working fine, I have maintained the duplicate contact persions while creating the customer, we are getting all the contact persons in the IDOC.

Regards

Praveen

0 Kudos
286

Praveen,

My iDoc has this format

E1KNA1M

--E1KNA11

--E1KNA1H

--E1KNVVM

--E1KNB1M

--E1KNVKM

--E1KNVKM

--E1KNVKM

--E1KNVKM

--E1KNKKM

My four E1KNVKM segments look like this (I have deleted the number for privacy)::

MSGFN 005

NAMEV Nezire

NAME1 Turk

TELF1 99999999

PAFKT ZA

MSGFN 005

NAMEV Nezire

NAME1 Turk

TELF1 999999999

PAFKT ZB

MSGFN 005

NAMEV Nezire

NAME1 Turk

TELF1 9999999999

PAFKT ZD

MSGFN 005

NAMEV Nezire

NAME1 Turk

ABTNR 0007

TELF1 99999999

Yet it is only the 0007 segment that is created even though the entire iDoc has a success message.

Former Member
0 Kudos
286

Anyone else with any other suggestions?

Former Member
0 Kudos
286

I logged a SAP call and after much work by me and my analyst we determined that this issue is unsolvable without changing standard SAP.

There is a SAP standard error message that is hard-coded into the XD01 transaction and the iDoc is coded to ignore this message within the iDoc (i.e. do not change the status to fail) but also to not pass save the information.

I will now need to arrange a suitable work around for our users.