IDOC DEBMAS05

Hello,
we are trying to send Customer master data from R/3 to an external system. We were supposed to use DEBMAS05 for this, but realized that the customer data is not in table KNA1, but in BUT000 (the customer is originally created in CRM, and then transferred to R/3). Does anyone know if there is a corresponding IDOC for table BUT000? (Alternatively, an IDOC for sending business partner data directly from CRM)
Any help appreciated,
Henrik

Hi,
As you are not passing the LIFNR field, system is overwriting the existing vendor with the blank value.
To avoid this, please pass the existing vendor which is related to the customer which is being chaned through the IDOC.
Regards,
Vijaymadhur
Edited by: vijaymadhur papabathini on Aug 27, 2010 7:34 AM

Similar Messages

Find Idoc extension type for Basic Idoc type

Hi all,
Is there any way to find existing extesions for Idoc given by SAP? For example, for basic idoc DEBMAS05 for version 4.7 , Idoc extension is DEBMASEXT.
In similar way I want to know what is Idoc extension for Idoc basic type PREQCR02 [Create Purchase Requisition].
Thanks in advance.
Madhura

The reason is preqcr02 is a generated idoc type and matmas05 and debmas05 are not generated idoc types .
You can search in table EDBAS for this . If you go for dynamic debuggin , message comes from form
create_ext_structure in include MSED5F02
data: l_edbas type edbas.
select single * from edbas into l_edbas
     where idoctyp eq edi_iapi01-idoctyp.
if l_edbas-generated eq 'X'.
   message e099(b1) with
      'Action is not possible for generated idoctypes'.
endif.
Edited by: anil sasidharan on Feb 25, 2009 12:51 PM
Edited by: anil sasidharan on Feb 25, 2009 12:59 PM

Idoc texting without any EDI or EAI

Hello,
I have a text file to test in SAP with the following IDOC DEBMAS05.
Does somebody the méthodology to run the test without any middleware...
thanks
Roger

Use test tool (transaction WE19) for inbound IDOC test.

Auto trigger outbound IDOC

Hi, everyone:
I just want to know how to auto trigger outbound IDOC to non-SAP system. For example, Customer Master IDOC DEBMAS05, Masterial Master MATMAS05.
I know we can use changer pointer, But we need run the program 'RBDMIDOC'. I want the system will create IDOC when we click 'SAVE' icon.
Does somebody have any idea? Thanks.
cdspi

cdspi cdspi,
if the IDOC / Message type is set for immediate processing, it will be procesed immediately.
Regards,
Clemens

Idoc Extension...Access Key

Hi Guru
Require your suggestion.
I have to extend the standard idoc DEBMAS05 but when i am doing it asking for Access Key.
Now i don't want to use access key. So what is other option for it,
Can i copy the all DEBMAS05 idoc as ZDEBMAS05 and then do the extension....
If yes then in that case do i need to to make ZDEBMAS Message Type or i can use the same DEBMAS Message for ZDEBMAS05.
Please give me Steps how to procees for Copy the Besic type.
Rgz
SA

Hi
here is my scenario
Can you help me on following.
I am working on DEBMAS05 Idoc.
Sender system sending DEBMAS05 Idoc which is an Idoc Extension with two Z segment.
Now here is my problem.
In Receving system if i am extending the DEBMAS05 its asking for Access key.Which i don't want. Is any other alternative of doing this?
I have two below option but not much clear about it.
1. If i copy the DEBMAS05 to ZDEBMAS05 and then do idoc extension.In this case do i need to also make ZDEBMAS.
or i can using DEBMAS as Message type for ZDEBMAS05?
2. I found one function-exit 'EXIT_SAPLVV02_001' in (user-exit VSV00001) which has description 'Read and Post Additional Export Customer Master Segments'.
can i use above function-exit in DEBMAS05 without extending the Idoc for Z fields in reciver side.
i am just evaluating above option so that i do not use Access Key.If above option is not valid then i may use Access Key,
Please suggest.
Regards
RJ

Structure of basic type

Hi Friends,
How i can know the Structure of basic type of the following idocs: DEBMAS05, CREMAS05, MATMAS05, ARTMAS and INVOIC02. Any documents or link would be more helpful.
Any help will be appreciated. Thank you all.

This you can find the IDOC Interfaces (Debmas, Cremas, etc) for Business Partner:
http://help.sap.com/saphelp_mdm300/helpdata/en/06/c5567cff4370448bc381ab39739199/frameset.htm

Update Dunning level on Customer(KNB5-MAHNS)

Hi experts,
I have request to update dunning level of customer (field KNB5-MAHNS) from another system using BAPI or something.
I can't find any BAPI for this purpose.
Anybody have some ideas or solutions for this problem?
Thanks,
Drazen

As far as i know there is no "actual" BAPI to update Customer (AR) master data so you may look at IDoc [DEBMAS05|https://www.sdn.sap.com/irj/sdn/advancedsearch?cat=sdn_all&query=debmas05&adv=false&sortby=cm_rnd_rankvalue] and write a program to use it or use [LSMW|https://www.sdn.sap.com/irj/sdn/advancedsearch?cat=sdn_all&query=lsmwCustomermaster+data&adv=false&sortby=cm_rnd_rankvalue] and direct input/batch input.
Regards

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

Issue with the configuration of http xml port for sending the idoc

Hello,
      I am planning to send multiple idocs in a single file using http xml port.
Presently I am trying to send a single idoc, but am having the issue.
I am trying to create a RFC for HTTP XML port of type H i.e. HTTP Connection to ABAP System
In the how to guide for - How Tou2026 Send Multiple IDocs Within One XI Message
( https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/30ea2fdf-f047-2a10-d3a2-955a634bde6b )
the following parameters are defined for the path prefix -
RFC destination of type H (HTTP Connection to R/3 System).
Specify the path prefix as follows:
/sap/xi/adapter_plain/
?namespace=< your namespace>
&interface=<IDoc_Type>
&service=<Sender System>
&qos=EO (or EOIO).
I am trying to use the following prefix -
/sap/xi/adapter_plain/
?namespace=urn:sap-com:document:sap:idoc:messages ( this is the standard namespace of SAP for all the idocs)
&interface=DEBMAS05 (Idoc type )
&service=SNDLS100 ( ECC system name )
&qos=EOIO
On testing the RFC connection, I am getting the error of page not found.
Can anyone please give me pointers for the issue.
Regards,
Mayank

Thanks Barry!!!
Now I am getting a different message.
In RFC...it is giving me the following message ->
Status HTTP Response     204
Status Text     Body is empty
In case of Idoc, the status is till 02...
the error description for the idoc is --
"When transferring the IDoc by HTTP, the return code with the message '500<SAP:Error><SAP:Category>XIServer</SAP:Category><S' has occurred.
The target address was: http://emgeccsnd1:8001/sap/xi/adapter_plain/?namespace=urn:sap-com:document:sap:idoc:messages&interf
Check whether the IDoc can be sent again.
It is unfortunately not possible to determine automatically whether the IDoc has in fact arrived in the target system and the error occurred afterwards"
I am still not able to resolve the issue.
Regards,
Mayank

Func. Mod's, BAPI's, IDoc's Related to Customer Master

Hi,
I need Func. Mod's, BAPI's, IDoc's Related to Customer Master. For creation, modification, Deletion, Updation of master data records.
Regards,
Sudheer

Hi,
Bapi to create customer master
BAPI_CUSTOMER_CREATEFROMDATA
BAPI_CUSTOMER_CREATEFROMDATA1
Or you can use FM SD_CUSTOMER_MAINTAIN_ALL
customer master idoc is DEBMAS05
Hope this helps
Please reward points if useful.
Regards
Rose

How to fill the KNBW Customer master record (withholding tax types) in IDOC

Hi experts,
The creation of a new customer (intern) with idoc has status 51 with error : No batch input data for screen SAPMF02D 0610. When à use the WE19 transaction, in background step by step, the batch-input stops in withholding tax types. But those informations aren't compulsory and not filled!
1 - Why did the idoc stops in this step of the batch?
2 - If i had to fill those informations, i don't find a segment in the DEBMAS01 or DEBMAS05 to fill the informations. Should i create an new segment?
Thanks à lot for you responses.
Wail

Hi
Step 1: Take help of a FI guy and:
The fields can be suppressed by configuring through Financial accounting > Business Partners > Customers > Account groups.
Step2 : The challenge inyou project is to have a single tab with the allowed fields
A technical guy can only help you out on this . Again This would be a huge effort since first you need to change the code for customer master. As customer master is a source of data for various documents in SD , at each place you will have to do changes in th code...I don't think it is feasible.
Instead of doing this , create an external interface for transferring the value to SAP through BAPI. this would involve integration and may be as per defined SAP standards you can use CSV files or XML files for the integration process.
This would be a better option than fiddling with SAP system
Regards
Nikhil

ORDERS05 Idoc Type Extension

Hello,
I am extending the segment E2EDKA3 in ORDERS05. Please let me know any user exit or any other way to populate the values in the extended segments.
I am adding these fields: VBPA-KUNNR,VBPA-ADRNR,VBPA-XCPDK & VBPA-ADRNP                         .
Thanks in advance,
Suresh

Hi Suresh,
Go through this info ucan able to do.
Enhancement of IDoc Type
Usually enhancement takes place when the content in IDocs provided by SAP are not sufficient for the business process. IDoc extension can take place whenever dictionary table has a new structure appended required by the business process.
In brief IDoc extension takes place when extra fields are required for the business process.
Let us take a scenario and understand the process of IDoc extension.
In this scenario say visitor is different from the actual customer who has came to the sales office in behalf of the customer to obtain the quotation or inquiry etc. Or an authorized agent qualified by the actual customer to order for items. So a field by name NAMEVI (Visitor) is added to Customer master data. As there is no provision given by SAP to handle this, we need to extend an IDoc.
The standard message type and IDoc type provided by SAP are DEBMAS and DEBMAS05.
Consider the data in the table below for extending the IDoc. These details can be understood in different sections in the process of extending it.
Basic IDoc type      DEBMAS05
Version      4.7
IDoc extension      DEBMASEXT
Custom segment      Z1KNA1
Fields in Custom Segment      Visitor
Parent of Custom Segment      E1KNA11
Outbound process
Step1. Customize kna1 table by appending a structure provided by SAP (ZAKNA1)
Component                Component Type
VISITOR                     NAMEVI
Step2: Write a module pool program to update some existing customers to add data for Visitor.
Step3: Create a custom segment
Transaction Code: WE31
Segment type: Z1KNA11   Click (create). Provide short text
Field Name                Data element
VISITOR                NAMEVI
Save
Step4: Create IDoc extension
Transaction      WE30
Object Name      DEBMASEXT
Choose Extension
Click   and it leads to next screen.
Linked basic type: DEBMAS05
Provide description and enter
Observe all the segments to be copied into your IDoc extension from linked basic
type.
Select E1KNA11 and click (create segment) to obtain a popup window
Provide the required values and observe child segment Z1KNA11 to be added to
parent segment E1KNA11.
Step5: Release segment and IDoc extension
Transaction: WE31
Segment type: Z1KNA11
Path: Edit à Set release
Step6: Assign Basic type to extension / messages
Transaction: WE82
Click , then
Select DEBMAS message type against DEBMAS06 basic type
Click   provide the information
Message Type      Basic Type      Extension      Version
DEBMAS      DEBMAS06      DEBMASEXT           4.7
Delete the earlier one from which it was copied.
Save.
Observe the result as follows
Step 7: Check and Transport IDoc extension
Transaction: WE30
Object name: DEBMASEXT
Path: Development object à Check
Ensure that there are no errors or warnings
Now transport
Path: Development à Transport
Step8: Find suitable user exit for writing code to support IDoc extension
Transaction: SE84.
Click Enhancements
In short text provide customer
Find suitable enhancement to be VSV00001
                         Alternative way
Transaction: SMOD
Click F4 help for Enhancement
Path: F4help à SAP Applications à Logistics general à Logistics Basic Data à
Business partners à Vendor Master.
Find the enhancement as VSV00002, which is an approximate user exit.
Now search for different extensions like VSV00001. Then see for its components.
Identify the appropriate user exit to be EXIT_SAPLVV01_001 (Create Export of
Additional Customer Master Segments). This user exit can be used in outbound ALE
process, meant for filling the data into custom segments.
You have to identify here another user exit as EXIT_SAPLVV02_001, which is
helpful for inbound ALE process. This user exit can be used to read the segments
and post it to Application repository.
Step9: Develop a project to encapsulate enhancements and components.
Transaction: CMOD.
Enhancement: custex and click Create to provide attributes.
Click Enhancement Assignments.
Provide VSV00001, short text and save.
From the initial screen of the transaction, select components and click change.
Find 4 components to be added.
Activate them.
Select user exit EXIT_SAPLVV01_001 for outbound process and double click it. It leads to function builder.
Double click on provided include program ZXVSVU01 and press enter.
Now, write supporting code for IDoc extension, i.e., populating custom segments in IDoc.
Check the code and activate.
Code in ZXVSVU01
*& Include           ZXVSVU01                                         *
*In this scenario, the E1KNA11 has been extended to accommodate
*User-defined fields in the customer table kna1. The name of the
*extended
*segment is z1kna11. There is one custom field: visitor
*Data declarations
DATA: kna1m like e1kna1m,
      kna11 like e1kna11,
      z1kna11 like z1kna11,
      w_kna1 like kna1.
make sure you are processing correct message type
check message_type eq 'DEBMAS'.
make sure data is added after the correct segment
check segment_name eq 'E1KNA1M'.
since customer number is not passed in this user exit, you need to go
through the data records to find the customer number
loop at idoc_data.
case idoc_data-segnam.
     when 'E1KNA1M'.
       move idoc_data-sdata to kna1m.
     when 'E1KNA11'.
       move idoc_data-sdata to kna11.
endcase.                             " case idoc_data-segname.
endloop.                               " loop at idoc_data.
select data from the user-defined fields in kna11.
select single *
from kna1                            " Customer master table
into w_kna1
where kunnr = kna1m-kunnr.
if sy-subrc eq 0.
set the idoc extension name for control record
idoc_cimtype = 'DEBMASEX'.
clear custom fields from kna1 to extended segment
clear z1kna11.
copy custom fields from kna1 to extended segment
move-corresponding w_kna1 to z1kna11. " field name must be same
condense all fields of extended segment
condense: z1kna11-visitor.
populate segment name in the data record, copy data contents into it
and append the data record to existing data records in
move 'Z1KNA11' TO IDOC_data-segnam.    " administrative section
move z1kna11 to idoc_data-sdata.       " data section
append idoc_data.
endif.                                 " if sy-subrc eq 0.
Step 10:
Define Logical System
Assign client to Logical System
Maintain RFC Destination
Maintain Customer Distribution Model
Generate Partner Profiles
Distribute Customer Distribution Model
INBOUND PROCESS
Step 11: Append the custom structure to the table KNA1 similar to the process done
        in outbound process.
Step 12.
Define Logical System
Assign client to Logical System
Generate Partner Profiles
Step 13. Execute the transaction to Send Customers from Outbound system.
Step 14. Now in the Inbound system, create the project in the similar way as done at
        outbound side.
In the user exit EXIT_SAPLVV02_001, find include ZXVSVU02. Write the code to
support IDoc extension.
Code in ZXVSVU02
*& Include           ZXVSVU02                                         *
data: kna1m like e1kna1m,
      kna11 like e1kna11,
      z1kna11 like z1kna11.
data fs_kna1 type kna1.
message i000(0) with 'INBOUND PROCESS CALLED'.
LOOP AT IDOC_data.
case idoc_data-segnam.
    when 'E1KNA1M'.
      kna1m = idoc_data-sdata.
    when 'E1KNA11'.
      kna11 = idoc_data-sdata.
    when 'Z1KNA11'.
      z1kna11 = idoc_data-sdata.
      select single *
        from kna1
        into fs_kna1
       where kunnr = kna1m-kunnr.
      if sy-subrc eq 0.
        update kna1
           set visitor = z1kna11-visitor
         where kunnr = kna1m-kunnr.
      else.
        idoc_status-docnum = idoc_control-docnum.
        idoc_status-status = '51'.
        idoc_status-msgty = 'E'.
        idoc_status-msgid = 'ZE'.
        idoc_status-msgno = '005'.
        idoc_status-msgv1 = kna1m-kunnr.
     append idoc_status.
      endif.                           " if sy-subrc eq 0.
endcase.                             " case idoc_data-segnam.
endloop.                               " LOOP AT IDOC_data.
Step 15. Assign FM to extension/Message type
Transaction:      WE57
Path: Change à New Entries
Select IDOC_INPUT_DEBITOR against DEBMAS06 basic type, to fill extra
information as shown below.
Function Module          Basic Type     Message Type          Extension
IDOC_INPUT_DEBITOR     DEBMAS06     DEBMAS          DEBMASEXT
Step 16. Execute the transaction to Get Customers.
And observe that records with extra data are saved in database.
Rewards some points.
Rgds,
P.Nag

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

Idoc creation - Different Message types

Hi All,
Is there an efficient way of to create both DEBMAS and ORDERS message type idocs within the same same ABAP program?
Please advise.
Regards,
Meghna

Thanks for your reply.
We have lot of custom development and we have to go with an ABAP program to create these Idocs.
Here's what I am planning to do:
fill DEBMAS05 idoc type.
append EDIDD.
fill ORDERS05 idoc type.
append EDIDD.
I'm planning to use INBOUND IDOC Process function module to create these idocs.
For performance reasons do you want me to call this FM twice or only once for both ( by appending EDIDD both debmas and orders records ).
Please advise.
Meghna

Idoc type extension

Hi Experts ,
I have created an extesnion for standrad message type DEBMAS and Idoc type DEBMAS05 . In devlopment system it is working fine . when transported to other system it is not working and after analsys it is found that EDISYN table has differnt values for differnt systems .Please let me know how can solve this , is any customization need to be mainatined or how it can be done .
Regards
Arun .

Hi,
You have to transport the idoc Extension object to fix this issue. It is not related to customization and it is more of IDOC development related. Try to find out the request under which the idoc extn is saved and retransport the request or include the extn related objects into new request and move it to target system. This should solve your problem.
Cheers,
Prasanna

IDOC DEBMAS05

Similar Messages

Maybe you are looking for