DEBMAS Error

Hello Friends,
While I am sending DEBMAS IDOC thru BD12 I am getting Error.
When I go to the WE05 , we got Outbound IDOCs->DEBMAS->Status 29 in segment 26
How to rectify it
Please advise me.
With Regards,
Sunil

hi,
ceheck the ALE configutations..
PLEASE have a look at below of the tcodes for ALE configurations...
        For distributing master data like material master, vendor master, customer master we have standard transaction codes that are provided by sap.
Bd10(send material master)
Bd12(send customer master)
Bd14(send vendor master)
Bd30(boms)
The order of Tcodes are:
           Bd54 (creating logical systems)
           Scc4 (assigning logical systems )
           Sm59 (rfc destination)
           We81 ( message type)
           We30 ( idoc type)
           We31 ( segment type)
           We82 (linking message type and idoc type)
           We21 (creating port)
           We20 (partner profiles)
           Bd64 (Distribution model)
           Bd10 (material master)
Ex: material master.
     Message type: matmas.
     Idoc type: matmas05.
Regards,
Nagaraj

Similar Messages

Document RFC Error in DEBMAS IDoc?

Hi Experts,
we use RFC to transfer DEBMAS-Idocs to a JCo-System.
Is it possible to set an Outgoing Idoc to a red/error state if the RFC transfer fails?
Thanks in advance & best regards,
Alex

Hi,
>>>Is it possible to set an Outgoing Idoc to a red/error state if the RFC transfer fails?
sure it's possible - the IDOC is called ALEAUD and it can tell you the status of the IDOCs in ERP (red etc.)
Regards,
Michal Krawczyk

Error in extended idoc DEBMAS

Hi Gurus,
I have extended DEBMAS message type to ZDEB.....
in which there is one segment ZKBALID and it is released to version 700.
but when i populate that segment in my application program, the idoc is not being generated with status message 02.
Which says
'Segment ZKBALID is unknown in Release 46C /'
Can anyone help me in finding out the exact reason behind the error and how i can rectify the same...
Thanks in advance.....

Hello Chandra,
Check if ur Z Segment is released?
If this helps, plz reward.
Rgds,
Raghu.

DEBMAS IDoc import error

I am trying to import the IDOC DEBMAS06 into XI in the IR. I am trying to import from an ECC 6.0 system. When I try this import I get the following error:
   DEBMAS.DEBMAS06: Error
    + Error: IDoc type DEBMAS06 contains errors (unable to read segments)
   Import failed with 1 error
I am able to import other Idocs, such as ADRMAS03, SERDAT01, and even DEBMAS04 just fine. DEBMAS05 and DEBMAS06 fail though.
I have looked in WE60 and WE30 at the IDoc, and the check is ok, everything seems released.
Any ideas on what this may be?
thanks
Jake

hi,
try loading metadata dor debmas06
from IDX2
if this will work you can get debmas06
from any other sap ERP system in your company
Regards,
michal

Error when posting debmas idoc

i have test run the debmas idoc, when iexecute it i got an an error ' NO BATCH INPUT FOR SAPMF02D 0340 SCREEN' is displayed.. please help me..i have used debmas06 as basic type

Hi,
usually this is due to a field which is either in display only, either suppressed in the online transaction XD01 or XD02.
Try to figure out which field is the one by looking at the data in the idoc in comparison to the fields ready for input in the online transaction.
Alternatively, you can try to process the idoc using the idoc test tool transaction WE19.
Process it using function module IDOC_INPUT_DEBITOR and process the customer master data transaction in order that it jumps online at the first error.
This should help to investigate.
For the fields settings transaction look into OVT0 and OB20
BR
Alain

Error while loading customer master data through Idoc (DEBMAS) from BODS

Hi All,
I am trying to load customer master data from BODS to SAP ECC through IDOC(DEBMAS). The jobs run successfully but IDOC is not getting posted. Please find the error below.
I checked in TSKD table the entry 0 is present. Please help me to resolve this issue.
Thanks & Regards,
Balamurugan G

Hi, did you referred this link : Error during customer master mass update through XD99

Error while posting Customer with Multiple sales areas using DEBMAS05.

Dear experts,
We are generating IDOCS vis SAP DS for posting Customer master. The message type used is DEBMAS and basic type is DEBMAS05. we have a requirement to create 1 customer with multiple sales areas. However, we are ending up with a strange error: "Fill all required fields SAPMF02D 0111 ADDR1_DATA-NAME1". Despite the IDOC going into status 51, the customer gets created and the 1st sales area too. the 2nd sales area however is not created! The IDOC data definitely contains Name1, otherwise the customer would not have been created in the first place.
As the error message is related to the Address data, I also explored upon exploring this erorr further on the lines of Central Address management where in the ADRMAS and DEBMAS have to be passed together(IDOC Serialiization). OSS Note (384462) provides further details about this. One Important point from the note is:
"As you have to specify the logical name of the sending system among other things, SAP is not able to make any default settings in the standard systems. When you use the serialization groups delivered as a standard by SAP, the address objects are imported before the master objects.Thus the sequence address data before master objects must only be adhered to if one of the following points applies to your application:
Such fields are set as required entry fields that are only provided by the BAS in the Customizing of the customer or vendor master.
For your customers, contact persons exist to which a private address or a different business address is assigned.".
This is not the case in our situation, as we do not have required entry fields in customizing that are only provided by the BAS, so the error is all the more confusing and I am not too sure what the cause is.
If someone have experienced the same issue before and have found a solution to it, kindly help out.

I have found the cause and solution to this problem.
This error ”Fill all required fields SAPMF02D 0111 ADDR1_DATA-NAME1” and other similar errors like “Fill all required fields SAPMF02D 0111 ADDR1_DATA-SORT1“ which occurrs during the IDOC posting when there are more than one sales area or company code occurs when the customer number range is set up for Internal numbering. This means, that the number gets generated only at the time of save and upon debugging the IDOC, we found out that after creating the customer and the first sales area/company code record, the segment E1KNA1M is cleared completely! This is the reason, it throws an error which points to a mandatory KNA1 field as missing. (Like NAME1, SORT1 etc.)
This was resolved by splitting the IDOC into 2.
The solution is to First post only the KNA1 segment and create the customer.
In the second step, pass the IDOC with all other segments along with E1KNA1M, but pass only KUNNR in E1KNA1M and the rest of the fields in E1KNA1M as “/”: you would have got the KUNNR after the first step.
Important note: This requirement to split the IDOCs does not occur when the customer number is known upfront. (Meaning cases where the customer number is externally generated) I also tested this and created a customer with external numbering and I was able to post more than 1 sales area with the same IDOC.
I noticed multiple threads with the same issue, but none of it had a concrete answer. I hope this information will be useful for anyone facing similar problems.
Cheers
Venkat

Error when exporting IDOC from one XI system to another

Hi all,
When I do an export for an IDOC from my one XI server to be able to import it into another I get the error below. The funny thing is that it works perfectly for my COND_A idoc but not at all for DEBMAS and MATMAS idoc.
Any ideas?
<b>Error during export. Internal error during pvc call: SAP DBTech JDBC: Result set is positioned after last row.</b>
Regards,
Liesel

Hey,
I guess you are using MAXDB,
please read note number 1055246
(Inconsistent XI content caused by bug in MAX DB)
Good luck!

Activation error in message mapping

Hi,
while activating Message mapping i am getting the error like this.
how to get rid of this error?
error:
Activation of the change list canceled Check result for Message Mapping MM_XXXXXX | http://www.xyerxd.com/mm
Imported source message has invalid reference IDoc
DEBMAS.DEBMAS06 | urn:sap-com:document:sap:idoc:messages
Imported target message has invalid reference Message Type MT_Receiver | http://www.xyerxd.com/mm

hi
Hope you are using the inactive versions of message/Idoc types for mapping.
First activate the message/Idoc types used in the message mapping.
Then open the message mapping, from the menu choose refresh.
Complete the mapping and test.
Now do the activation.
rgds,
Arun

Error on creation of customer classification processing with IDOC CLFMAS

Hy everybody,
I create customer in 4.6c system.
So I use IDOC DEBMAS for customer data and CLFMAS for classification.
But when processing the classification IDOC,after customer integration, i have the following message return by IDOC.
==>   "Vendor & does not exist".
But IDOC status is set to 53.
I have filled the structure E1OCLFM with the following values:
     - MSGFN = 009 for creation
     - OBTAB = KNA1 (for customer)
     - OBJEK = Customer number created previously
     - KLART = 011 (Customer Class)
     - MAFID = 0
     - OBJECT_TABLE = KNA1
So i don't understand why i have this message.
Does anyone help me on this problem?
Thank in advance.

Hi Ludovic,
How did you resolve your earlier issue with correction of parther profile? I am getting teh same error while posting CLFMAS for a customer i.e. OBJEK 1100000215 ( KNA1) not found, where 1100000215 is my customer number ( KUNNR).
Could you please advise me how to resolve this?
Many thanks in advance
Regards
Dev

Error during the configuration of communication channel

Hi ,
I am trying to create a senario where XI will send the DEBMAS Idocs to the SAP system.
Can you please help me as to how sould i go about configuring this senarion.
The error i am getting is -
Communication channel is not configured correctly. Choose a different communication channel----- when i am trying to assign the communication channel to the receiver.
Thanks for the help
Nikhil

Hi,
1. at first you can take a look at:
http://server:port/mdt/amtServlet
find you channnel type and your channel and see if there's any error over there
2.tell us all of the channel parameters that you've configured so far
Regards,
michal

IDOC - Web Service scenario gives errors when processing multiple IDocs

Hi,
I have an integration process defined in PI 7.1 that contains four major steps :
-     Receive DEBMAS IDoc
-     Call a RFC to get additional information
-     Call a MS Dynamics web service to retrieve the MS Dynamics customer account number via the SAP customer number (synchronous call)
-     Call a MS Dynamics web service to update customer info (asynchronous call)
This process works well when one IDoc is processed.
If however 10 Idocs are submitted, some updates are processed correctly, most of them are not (the find service call works perfectly fine). Sometimes 3 work fine, sometimes 1 (for the same 10 IDocs submitted)
I did a test with SOAP UI where in a test script I submitted the 10 update service calls and this works fine.
The error that is given in the adapter engine SOAP communication channel is :
Message processing failed. Cause: (415)Cannot process the message because the content type 'multipart/related; type="text/xml"; start="<45504935B855BA3ACA0EA2FD503BC60F>"; boundary="----=_Part_20_1319086528.1239082062538"' was not the expected type 'text/xml; charset=utf-8'.
I noticed in the message content that the SOAP calls that go wrong have two payloads attached, one for the Main Document and one for the XI Context.. The ones that are processed correctly only have one payload, the Main Document
Anyone an idea what the cause can be ?
Thanks,
Jan

Hi,
Please check the transaction idx5 in PI system and see whether the IDOC status by double clicking on the corresponding Transaction ID.
I think this might be due to some invalid data coming from the source system
Thanks,
Tiny

How to serialize the IDoc of DEBMAS by time sequence?

Hi experts,
We want to transfer customer master data from one client to the other.
We have carried out the serialization distribution for message type DEBMAS
and actived the change point.
Scenario:
time 1 : We created one "NEW" customer 100436.
time 2 : We assigned the Head Office of "existed" customer100435 as 100436
The time of the distribution job was arrived,
the job started to run and failed to change "existed" customer 100435
even though "NEW" customer 100436 has created sucessfully.
We think the IDoc should be processed by time sequence,
but it seems not.
Did you think it is processed by customer key ascendence ?
How do we define the process sequence of the IDoc?
Any advice will be appreciated.
Regards,

But what if i want to check the format of date that my
database supports ?
Actually situation is :
I am making a form designer by which user will inset
date to a particular column. okay.
now the format of date must match with the underlying
format of database. Then only query will be
successfull. Is it not so.?No.
Basically you will be doing the following:
Browser -> java.util.Date
java.util.Date -> JDBC -> database
JDBC does the 'conversion' work for you, you just need to put it in the java.util.Date.
suppose database table-> column's format is
YYYY/DD/MM Databases don't store dates like that. They usually (probably always) store it as a signed integer value which is relative to a specific date/time.
When you use a database tool to look at the value the database tool converts it from the number to a format that looks familar to you.
and user enters date in the format
DD/MM/YYYY, then i will have show an error message to
the user that the format of date that he has entered
is wrong. No need for that.
The user does need to put the date in in a form that you understand. So you can convert it to a java.util.Date.
java.text.SimpleDateFormat can help with that.

Error when determining the inbound interface

Hi Experts,
I have a Scenario, where i am using Multi mapping Scenario in DEBMDM IDOC from ECC to Xml_File-1(DEBMAS) and Xml_File-2(ADRMAS).
When i Execute the Scenario by sending the IDOC from ECC , i am getting the below error.
Runtime error
Error when determining the inbound interface: Inbound interface found several times (for same sender and receiver) for the outbound interface urn:sap-com:document:sap:idoc:messages.DEBMDM.DEBMDM06
Scenario Steps
1) No Condition in Interface Determination
2) 0..unbounded in Message Mapping and Operational Mapping.
3) E1KNA1 is mapped to E1KNA1
4) E1ADRMAS is mapped to E1ADRMAS
5) One Message Mapping and 1 Operational Mapping.
Thanks in Advance.
Sriram.

Hello,
I have a Scenario, where i am using Multi mapping Scenario in DEBMDM IDOC from ECC to Xml_File-1(DEBMAS) and Xml_File-2(ADRMAS).
Since your scenario makes sure that the 2 files are created, there is no need to use multi-mapping. Rather, you can use an interface determination split. To do this:
1. declare xml_file1 as service interface 1, xml_file2 as service interface 2
2. do not change target occurrence in message mapping and operation mapping, maintain it as 1..1
( 2 operation mappings)
3. in ID, add the two service interfaces in your interface determination
At runtime, it will split into two inbound interfaces.
When i Execute the Scenario by sending the IDOC from ECC , i am getting the below error.
Runtime error
Error when determining the inbound interface: Inbound interface found several times (for same sender and receiver) for the outbound interface urn:sap-com:document:sap:idoc:messages.DEBMDM.DEBMDM06
Were you able to declare the 2 xml_files as two separate service interface(different names) in your operation mapping?
Hope this helps,
Mark

IDOC Ack from BPM to SAP R3 runs into an error

Hi All,
I have a scenario which sends an DEBMAS IDOC to an Integration Process "IP_SPLIT_Site" which process the IDOC and sends it to multiple systems.
When the IDOC is sent from SAP R3 to the receiving Integration Process "IP_SPLIT_Site" in XI, it is processed successfully.
Since the SAP system is expecting an acknowledgement from the receiver of the IDOC, the integration process "IP_SPLIT_Site" tries to send back an acknowledgement for the IDOC which runs into an error because it is not able to convert "IP_SPLIT_Site" into an ALE logical system.
The error displayed is :
Unable to convert the sender service IP_SPLIT_Site to an ALE logical system
Error code : ATTRIBUTE_INV_SND_SERV
I am getting this error in all my scenarios where an IDOC is sent to an Integration Process.
Is there any solution avoid this error?
Thanks & Regards;
Bbnu

Hi Michal
The 1st approach seems to be helpful.
about the 2nd approach if i am sending the Ack through a separate send step in BPM then i suppose it would show the same error "Unable to convert the sender service IP_SPLIT_Site to an ALE logical system".
OR
Do you mean to say that we could send a separate message of type ALEAUD to the SAP system?
for 3rd approach, i wouldn't wanna handle many partner profiles.
Thanks for your reply,
Rgds;
Bbnu

DEBMAS Error

Similar Messages

Maybe you are looking for