BD10 & BD12

HI!!!
I need to create a IDOC with BD10 and BD12 but I obtain the error:
1 master IDocs set up for message type DEBMAS......    then .....  0 communication IDoc(s) generated for message type  DEBMAS.
1 master IDocs set up for message type MATMAS......    then .....  0 communication IDoc(s) generated for message type  MATMAS.
Somebody help me, please... step by step.
Thanks you!!!
Best Regards

Hi
Basic Configuration settings necessary for successful ALE process are as follows.
1)     Define Logical Systems
2)     Define RFC destination
3)     Define Ports
4)     Create Partner Profiles
5)             Maintain Distribution Model
Logical systems
Logical Systems should be defined for both the sending and the receiving systems using the transaction u2018SALEu2019. Assign these logical systems with the necessary clients and role.
RFC Destination
The recipient system should be configured in the RFC destination using Transaction u2018SM59u2019. Check for the type of the connection to be used for and create an rfc destination. Test if the connection is working fine and try remote logon. If it everything works fine then the user should be able to login to the recipient system.
Ports
Depending on the type of the destination system, ports can be created using Tcode u2018WE21u2019. If the destination is of type RFC then using Transactional RFC to create a port and assign the rfc destination created for the recipient system.
Partner Profiles
Identify the Idoc type and Message Type to be sent and go to Transaction u2018WE20u2019 to create partner profiles. Partner profiles can be created under logical systems tab. Assign the partner number and partner type. In the sending system give the outbound parameters as Message Type, port and the Idoc type along with the mode of output. In the recipient system give the inbound parameters as Message type and process code assigned with the message type.
Maintain Distribution Model
Go to Transaction u2018BD64u2019 and create a customer distribution model with the sending and the recipient logical systems. Add Message type to the model which needs to be sent. Now distribute the model and check for the successful distribution of the same. If an error occurs go to the particular transaction and make the necessary changes and follow the same process to replicate the changes.
Also make sure that the IDOC types are being assigned to  the message types for your SAP Version in transaction WE82.

Similar Messages

  • How to send an Invoice from R/3 using ALE configrations.

    Hii All,
    My object is that I have to send an Invoice, similar to that of sending of an material from R/3, for material the transaction code is BD10. Is there any TCode for invoice ?? If not how can we send the data ..??
    Thanks in Advance,
    Srikanth

    hi
    here we r triggering the idoc by using ALEs.
    BD10 BD12 etc are used for the master data distribution only.
    for transactional data u hv to follow the below process.
    u have to configure the same settings which u hv done for the material posting.
    u have to set the settings in teh message controle tab of the parnter profile, here we r dealing with transactional data so we have tjo use outbound process code and medium as ALE distribution.
    after this u hv to sonfigure the settings in NACE transaction with invoice form or smartform name and print program name.
    so whenever the invoice is created and saved then this process will continue and triggers the IDOC and send to target.
    regards
    sreeni

  • Sending sale order data

    hi,
    how can we send sale order data from sapxisap.
    are there any standard tcode like BD10 BD12 BD14.
    plz help me.
    thanks and regards
    vijender

    For creating sales documents (sales order) through IDOCS you will have to use the T code WE19.  In that click basic type and enter order05(IDOC type) and select via message type then enter ORDERS(message type), click execute.
    You will get to see many fields.here you have to enter the datas that you enter in the VA01 screen in order to create sales order. The datas such as material name, date, qty, P.O no etc.  After entering all the datas, you click standard inbound the IDOC would be created by the system.You can see the created order by going in to VA03 screen.
    Next time when you create the IDOC, in same tcode WE19 screen, click existing IDOC and enter the IDOC which you created in the above step and just change the P.O no.Sytem will create new sales order through new IDOC
    Before doing all you need to maintain the partner profile in T code WE20

  • Importing xml file using standard maps in mdm

    Hi Experts,
    In a scenario of getting the data from ECC system to the MDM system(using MDM standard business contents and standard Maps), we are  two cases.
    Case 1 : Using MDM_CLNT_EXTR, we extract the main table records into the standard IDoc structure and sent to PI and PI converts this standard IDoc in to an XML file and sends it to the inbound folder of MDM and from there using the standard map, it is imported into MDM.(most common method of implementation)
    Case 2: we are using XML File option in Partner Profile to store the XML file in the Global Directory of ECC system and we are generating XML files using the transactions BD10, BD12 and BD14 for the respective business objects.And then copy these XML files from the Global directory and plae it in the inbound folder of MDM manually.
    Now the question is can the xml file in the case 2 be used as a substitute for the xml of case1 and
    can we use the same standard map to import the XML file abtained from case2?
    Please share your experience to solve this issue.
    Thanks and Regards,
    Sravan.

    Hi Sravan,
    this depends on the business content you are using. Some parts of the content use XSLT mappings on PI to change the message content. Please refer to the related SAP content notes for details:
    MDM Business Partner Content (SAP Note 1035773) 
    MDM Customer Content (SAP Note 1252884) 
    MDM Employee Content (SAP Note 1268212) 
    MDM Material Content (SAP Note 1255401) 
    MDM Product Content (SAP Note 1252846) 
    MDM Vendor Content (SAP Note 1252883) 
    Best regards
    Michael

  • Tcode for Global Projects

    Friends,
    Do we have a standard Tcode to create the PROJECT01(Global Projects) idoc similar like BD10,BD12 etc....
    Thks,
    Chandra.

    Hi Chandra,
    I could not find any standard FM and program to generate an outbound IDoc PROJECT01.
    You need to create custom FM to populate EDIDC and EDIDD for the above IDoc type. Once the population segments are done then you can call FM MASTER_IDOC_DISTRIBUTE to generate and send the IDoc.
    Hope this will help ...
    Regards,
    Ferry Lianto

  • TRIGGERING THE IDOC

    Hi
        I have one Zxxx table.. that contain some master data  details... now  i want to send these details to external systems... i created one custom IDoc and  Message type.. every thing... 
      but for triggering the idoc what we need to do.. for  example..  for predefined data we have option   like BD10, BD12, BD14...  these executable programs.. or  Chnage pointers(RBDMIDOC) we can trigger the idoc for predifined data..
    but for user defind  data tables.. what can we do for triggering the idocs..
    thanks
    BABU

    Hi,
    check the below sample code for triggering the idoc..The same thing u can do for ur requirement..slect all then data from ur custom table and finally call the FM
    "MASTER_IDOC_DISTRIBUTE".
    *& Report ZZ_Program_To_Create_Idoc
    report zz_program_to_create_idoc .
    tables: ekko,ekpo.
    selection-screen skip 3.
    selection-screen begin of block b1 with frame title titl.
    selection-screen skip.
    select-options s_ebeln for ekko-ebeln.
    selection-screen skip.
    selection-screen end of block b1.
    data: header_segment_name like edidd-segnam value 'Z1EKKO',
    item_segment_name like edidd-segnam value 'Z1EKPO',
    idoc_name like edidc-idoctp value 'Z19838IDOC1'.
    data: header_segment_data like z1ekko,
    item_segment_data like z1ekpo.
    data: control_record like edidc.
    data: messagetyp like edmsg-msgtyp value 'ZZ9838MESG1'.
    data: i_communication like edidc occurs 0 with header line,
    i_data like edidd occurs 0 with header line.
    data: begin of i_ekko occurs 0,
    ebeln like ekko-ebeln,
    aedat like ekko-aedat,
    bukrs like ekko-bukrs,
    bsart like ekko-bsart,
    lifnr like ekko-lifnr,
    end of i_ekko.
    data: begin of i_ekpo occurs 0,
    ebelp like ekpo-ebelp,
    matnr like ekpo-matnr,
    menge like ekpo-menge,
    meins like ekpo-meins,
    netpr like ekpo-netpr,
    end of i_ekpo.
    start-of-selection.
    select ebeln aedat bukrs bsart lifnr from ekko
    into table i_ekko where ebeln in s_ebeln.
    select ebelp
    matnr
    menge
    meins
    netpr
    from ekpo
    into table i_ekpo
    where ebeln in s_ebeln.
    control_record-mestyp = messagetyp.
    control_record-rcvprt = 'LS'.
    control_record-idoctp = idoc_name.
    control_record-rcvprn = '0MART800'.
    loop at i_ekko.
    header_segment_data-ebeln = i_ekko-ebeln.
    header_segment_data-aedat = i_ekko-aedat.
    header_segment_data-bukrs = i_ekko-bukrs.
    header_segment_data-bsart = i_ekko-bsart.
    header_segment_data-lifnr = i_ekko-lifnr.
    i_data-segnam = header_segment_name.
    i_data-sdata = header_segment_data.
    append i_data.
    select ebelp
    matnr
    menge
    meins
    netpr
    from ekpo
    into table i_ekpo
    where ebeln = i_ekko-ebeln.
    loop at i_ekpo.
    item_segment_data-ebelp = i_ekpo-ebelp.
    item_segment_data-matnr = i_ekpo-matnr.
    item_segment_data-menge = i_ekpo-menge.
    item_segment_data-meins = i_ekpo-meins.
    item_segment_data-netpr = i_ekpo-netpr.
    i_data-segnam = item_segment_name.
    i_data-sdata = item_segment_data.
    append i_data.
    endloop.
    clear i_ekpo.
    refresh i_ekpo.
    endloop.
    call function 'MASTER_IDOC_DISTRIBUTE'
    exporting
    master_idoc_control = control_record
    OBJ_TYPE = ''
    CHNUM = ''
    tables
    communication_idoc_control = i_communication
    master_idoc_data = i_data
    exceptions
    error_in_idoc_control = 1
    error_writing_idoc_status = 2
    error_in_idoc_data = 3
    sending_logical_system_unknown = 4
    others = 5
    if sy-subrc <> 0.
    message id sy-msgid type sy-msgty number sy-msgno
    with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
    else.
    loop at i_communication.
    write: 'IDOC GENERATED', i_communication-docnum.
    endloop.
    commit work.
    endif.
    initialization.
    titl = 'ENTER THE PURCHASE ORDER NUMBER'.
    Reward if hlpful.
    Regards,
    Nagaraj

  • Message Type not visible in BD10

    Hi,
    One of the message types is not visible in BD10. Will this appear if I add it using BD60 transaction. But my doubt is that all the message types visible in BD60 are again not there in the F4 help. Is there some othere place where the message type has to be maintained.
    Regards,
    Deepti

    hi
    If you add required message type in BD60 you can see it. but the thing is BD10 is only for MATERIALS. So material related message types only you can see there. It you want to see customer related message type then you can go to BD12.
    While creating message type in BD60, system should ask reference message type. You have to select one reference message type while selecting dropdown or pressing f4 for reference field in BD60. If you select MATMAS as reference message type there then you can see that message in BD10.
    Reward if it is helpful.
    Thanks
    Siva Kumar

  • ISSUE:regarding production version tab of MRP4 of  data transfer using BD10

    Hi all,
    This is regarding production version tab of MRP4 of  data transfer using ALE idoc (BD10).
    When i transfer the data using BD10 the production version is received at receiving end through segment
    but not created in MRP4 view tab.An error is coming as-
    "You wanted to maintain the master record of the material AB_06.04.09(2). However, it is already being processed by the user EBGABAP and is therefore locked."
    I logged in as-EBGABAP
    Please help me resolve the issue.
    Thanks
    Edited by: sanu debu on May 6, 2009 11:08 AM
    Edited by: sanu debu on May 6, 2009 11:09 AM
    Edited by: sanu debu on May 6, 2009 11:11 AM

    >
    sanu debu wrote:
    > Hi,
    > I have to upload production version tab data of  MRP4 view(MM01).Please suggest a function  moduleor bapi  for the same.
    >
    > Thanks.
    >
    > Edited by: sanu debu on May 6, 2009 3:24 PM
    BAPI_MATERIAL_SAVEDATA can be used, populate the respective fields in input parameter PLANTDATA

  • Creation of communication IDOC's from BD12

    Hi All,
    I am triggering BD12 transaction for few customers.
    For some set of customers i am able to create both Master IDOC & Communication IDOC.
    Ex: For the customers whose Account Group is : 0001
    For other set of customers i am able to create Master IDOC but Communication IDOC i am not able to create.
    Ex: For the customers whose Account Group is: ZCRD
    Customer in account group ZCRD do not have sales area data maintained, where in there is no information maintained for sales, billing, shipping & Partner functions.
    Where as customers in account group 0001 have the sales area data maintained.
    This is the functional analysis of both the Account Groups.
    Can anybody tell the reason why Communication IDOC's are not created for Account Group-ZCRD customers & For Account Group-0001 communication IDOC's are created!
    Can anybody solve this issue!
    I have debugged this issue step-by-step for both Account Group's [ZCRD, 0001] related customers, There is no check in code for Account Group-ZCRD so that communication IDOC's does not get created.
    Also both Account Group's customers went through same piece of code, Only at in F.M call to MASTERIDOC_CREATE_REQ_DEBMAS
    the returned parameter CREATED_COMM_IDOCS is 0 for Account group-ZCRD related customer where as it is 1 for ACcount Group-0001 related customer.
    Can anybody resolve this issue so that Communication IDOC's will also be created for Account Group-ZCRD related customers!
    Thanks in advance.
    Thanks,
    Deep.

    Hi Naveen,
    Thank you for the reply.
    In BD64 i have checked the details.
    There is no checks/filteration against Account Groups-ZCRD/0001.
    One more thing is the customers for Account Group-ZCRD are
    Credit Master accounts.
    Is there any way i can find the resolution for the same!
    Thanks for the reply.
    Thanks,
    Deep.

  • Regarding generating Master/Communication IDOCS's from BD12 forfewcustomers

    Hi All,
    I have one issue when i am using BD12.
    I am inputting some customers and output type/message type and executing the transaction for some customers it is generating both Master & Communication IDOCs, But for some customers it is generating only Master IDOC's but not Communication IDOC's.
    These kind of cases are coming for particular Account Group [Ex: ZCRD etc..],
    Can anybody tell me what is the relation between Account Grooup & Customer & why it is stopping generation of Communication IDOC's for particular Account group related customers.
    How can i solve this issue!
    Can anybody solve this issue!
    Thanks in advance.
    Thanks,
    Deep.

    Hi All,
    Any inputs/Solution for the above posted issue!
    Resolution in this regard will be appreciated.
    Thanks,
    Deep.

  • Logical System field in BD10/BD14 need as a Mandatory Field

    Hi All,
    Good Day,
    We have Logical System field in BD10 or BD14 etc.. TCodes and I would like to make this field as a Mandatory field. The reason for this is, while sending the Materials using BD10, and If I haven't enter any value for this field, IDOCs are getting generated and sending to all the logical systems say Dev, Quality and Production too. I want to avoid this.
    So Is there anyway where we can make the filed "Logical System" as a mandatory field.
    Thanks in Advance.
    Param.

    HI Param,
    try  BAPI_IDOC_INPUT1and check it in WE57 tcode.
    hope this helps
    regards
    Aakash Banga

  • Restricting BD10 field Logical Systems

    Is there an authorization object that can restrict field 'Logical Systems' (LOGSYS) in transaction code BD10?  If not, has anyone implemented an alternative solution?

    nope, there isn't.
    may i ask why you are granting this transaction? would it not be more efficient and less a risk to distribute materials using change-pointers and put the whole thing to batch?

  • Customer master data not replicated to DSD Connector tables - BD12 - Idocs

    Hi experts,
    I have a customer existing in 2 different sales organizations. I need to replicate it to the DSD/ME_CUST_SA table in the DSD Connector.
    The Idoc's segments generated while executing BD12 transaction, include only information for one sales org (VKORG) but I see no records or segments regarding the other Sales Org.
    I think mapping rules are just fine (VKORG field is correctly mapped to DSD/ME_CUST_SA table)
    What I need is to have both data replicated: that is, data from both sales orgs.
    Any thoughts on this?
    Thanks in advance
    Edited by: Jose Barreto on Jun 4, 2008 11:13 PM

    Hi Jose,
    pl. go through note 1015076 and implement it if useful.
    please email your personal ID at my id( given in my profile)
    as I am also trying to implement DSD and need some help.
    Note: reward Points if helpful
    Thanks,
    Akhil

  • Get IDOC number information from BD10 to be displayed

    Hi,
    I want to make a report whr i m calling 'BD10' report by call transaction which is used for sending material master details through IDOCs.(msg type MATMAS). basic type matmas05.
    now user requirement is that we need to show materail number along with success ful created IDOC number. pls let me know hw to get the informayion for idoc as idoc creation is handled by BD10.
    rgds,
    rag

    no rpl

  • BD10 returning all data in segments (MARC, MVKE)inspite of filtered data of BD64

    In BD64, Under MATMAS Data filtration is set on Sales Org and Distribution Channel. When I am sending material from BD10 , I need to get these values ( Sale Org / Distribu Channel ). B'cos on the basis of these values I need to fetch PLANT from MVKE table by passing SOrg and Dchl .
    I got Sale org and Dis Chl but now the issue I am getting  all info from MARA, MVKE and MARC for the material rather I need filtered value only..
    I have attached one image where it shows filtered Sale org and Dist Chl, but when i executing BD10 , it is returning data of respective material of all plant , sale org and distribution channel..
    Ref Post : BD64 Filtering Value (Sale org/ Distri Channel) need to get in EXIT_SAPLMV01_002
    Please suggest.
    Regards
    Ankesh

    Hi,
    if suppose if youb want to replace the earlier segment fields  then update the MARC segment after reading the MVKE segment .
    example code  some thing like below
    tables: ,E1MVKEM,E1MARCM
    loop at  EDIDD INTO WA1 WHERE  SEGNAM = ' E1MVKEM'.
    E1MVKEM = WA1-SDATA.
    READ TABLE EDIDD INTO WA2 WHERE SEGNAM = 'É1MARCM'
    IF SY-SUBRC = 0.
    E1MARCM = WA2-SDATA.
    SELECT SINGLE DWERK FROM MVKE INTO E1MARCM-WERKS WHERE
    MATNR = E1MVKEM-MATNR
    VKORG = E1MVKEM-VKORG
    VTWEG = E1MVKEM-VTWEG.
    WA2-SDATA  = E1MARCM.
    MODIFY   EDIDD FROM WA2 INDEX SY-TABIX transporting sdata.
    ENDIF.
    endloop.
    Regards,
    Venkat

Maybe you are looking for