MATMAS IDOC

Hello all,
Iam working on Material master Data Upload using the IDOCs.
-There are about 3K records.
-I have collected the IDOCs and executing the RBDAPP01
-in background with Parallel processing and with Packet size as 5.
All the IDOCs processed these way are going to in to an Error :
IDoc included in IDoc packet containing an error: transfer it separately
Regards
GangaPrasad

HI,
Inorder to package or bundle IDOC u can go for two methods.
Idoc Packaging:
Consider a file to IDOC scenario, where 1 file will contain multiple IDOCs. So, you need to send these multiple IDOC s to R3 system.
Now, one way would be to use a BPM, but a better way is to use the PACKAGINg where these multiple IDOCs are packaged as one IDOC and then on R3 , there are unpacked into multiple IDOCs.
1) In XI where u need to do a configuration
Please find weblog link on Idoc Packaging
/people/sravya.talanki2/blog/2005/12/09/xiidoc-message-packages
2) U can collect the IDOC in R3 and put the IDOC XML file into R3 server and use the file adapter communication channel to pull that file.
FOr more information please go through the below weblog:
1)Collecting IDocs without using BPM By Stefan grube's
/people/stefan.grube/blog/2006/09/18/collecting-idocs-without-using-bpm
I think u have the same requirement.
Thnx
Chirag

Similar Messages

  • FILE  to  IDOC  SCENARIO   NEED  MANDATORY FIELDS IN  MATMAS IDOC

    Hi
       I'm  learning a scenario like File to Idoc  which is i need some what are the mandatory fields for  creting the message mapping.. between source file and MATMAS IDOC...  because it was showing several fields.
    is there any way to find out the  fields we need to map compulsory...  for sending IDOC successfully.
    Thanks
    Babu

    Hi Babu !
    Log into the R/3 system, transaction WE60, enter the idoc type MATMAS01 or 02, 03, 04, then press F8 or go to Documentation menu, HTML Format.
    It will display a document, telling you which fields are optional and which mandatory.
    Regards,
    Matias
    PS: please award points if helpful.

  • MATMAS idoc with classification details - reg

    Hi,
    I am working in a project related to the transfer of Material Master from one system to another ( Both are R/3 systems).
    I am currently  using the message type MATMAS with basic type MATMAS05. With the above message type i am able to generate an idoc from source system with all of the details except for the classification details.
    For classification i have configured the message type CLFMAS and CHRMAS, in the CLFMAS i am able to successfully generate an idoc with BD91/BD92 tcodes. But when the idoc is generated, the idoc gives the list of charactersistics managed in the class at each segment level but not able to retrieve the values maintained by me during the material master creation. In order the target values for each of the characteristics in the class is empty.
    Please clarify me with the following queries:-
    a) Is that really required to push both CLFMAS and CHRMAS for a material master classification related field values ?
    b) How to get the characteristics values maintained in the material master at the idoc level ?
    c) How to link the CLFMAS generated idoc and the MATMAS idoc to link the relationship?
    Thanks for the understanding.
    Thanks and Regards,

    Classification of a material has to be send with CLFMAS IDOC separate from the material.
    Usually you first distribute all characteristics and classes, then the materials, finally the classification.
    You have to enter the  new material number in segment E1OCLFM field OBJEK of your classification Idoc.

  • Multiple MATMAS IDoc getting created through RBDMIDOC program

    Hello All,
    I am creating MATMAS Idocs by RBDMIDOC proram, but as MATMAS message type is used in multiple distribution models ( i.e. MATAMAS is being sent to multiple partners), its creating multiple IDocs.
    I want my IDoc to get triggered only for a particular partner. How can i acheive this ?
    Searched on SDN but did not found solution.

    As the standard settings, IDOCs will be transmitted to all the Partners which are maintained in WE20 (Partner Configuration).  You can restrict the triggering of IDOC based on some condition using the Business transaction event MGV00100 (Publish & Subscribe).  This event is called from Function module MASTERIDOC_CREATE_MATMAS (Line number 2074).  Documentation of Standard FM SAMPLE_INTERFACE_MGV00100  reads
    * Event rissen by the ALE outbound process for MATMAS.
    * It allows to modify the idoc's control header the idoc data aswell
    * as serialization information created by the standard SAP outbound
    * process.
    * Raising the EXCEPTION ERROR will prevent the IDOC from being
    * submitted to the ALE layer.
    * BE CAREFUL WITH ANY CHANGES TO IDOC_CONTROL. IT MAY EFFECT YOUR WHOLE
    * ALE-SCENARIO
    You have to copy the Standard FM SAMPLE_INTERFACE_MGV00100 to a Z function module and assign it using transaction code FIBF.  Search SCN to get more details about configuring Business transaction events using FIBF.

  • Create a matmas idoc based on PIR information

    Hello friends,
    can you please help me on the following points please :-) ?
    I need to create matmas idocs and these idocs should be sent on a web portal identified on our SAP system as a logical system. The vendors will have access only to the materials they supply. For this reason, I need to send in the matmas the GLN code corresponding to the vendor for which we have created a purchase information record. This way, on the web portal the display of matmas information will be organised according to GLN codes.
    Question :
    how can we create the MATMAS idocs according to purchase information records? I mean how can I create matmas idocs selecting the materials supplied by specific vendors???
    is there any standard way to do it on SAP? or has it got to be done a specific way. and if so, do you have any idea on how to do it?
    Thanks in advance for your very precious help,
    Kind regards,
    Karenn

    are you thinking about manual creation in BD10, or something automatic?
    BD10 has the standard F4 material search help.
    If you need to do it regular and manually, then you may consider creation of a new included search help where you can search based on info records.

  • Filtering out MATMAS IDoc based on a condition

    Hi All,
           We are distributing a Material Master IDoc (Message Type MATMAS / IDoc Type MATMAS05) from an ECC 6.0 (WebAS 700) system to an external Non-SAP system via SAP XI.
           Now our requirement is that the users will maintain a Z-table with all the SAP plants that are relevant for the external system. They can add or delete plants from this table in the future
           If the MATMAS Idoc is created/extended for a plant which is not in the Z-Table then it should not get distributed.
    E.g. If MATMAS IDoc contains plant 5000 and 5000 is not in the Z-Table then the Idoc should not even be created
    We Tried a lot of enhancements: -
    SMOD Enhancement - MGV00001
    Enhancement Spot - ES_SAPLMV01 at different call up points
    But none of them give the required exact result.
    If we implement the enhancement spot inside the function module MASTERIDOC_CREATE_MATMAS, we get a message "1 Master IDoc created, 0 Communication IDocs created". So something is getting created and that's incomplete anyway.
    So I am not sure how reliable this is
    <b>One last approach I have is</b>: -
    1) Send the IDoc to XI (without filtering)
    2) Let XI look at the Plant code and compare with the Z-Table in ECC (via a Z-RFC function module) and then decide whether to send the IDoc or not send it to external system
    Please let me know if my approch is correct or I am missing something here
    Thanks and Regards,
    Aditya

    Hi Aditya,
    If the Communication Idoc is not created it means that the IDOC is not sent out of the system. The Master Idoc creation does not mean the Idoc is sent to the XI adapter.
    The purpose of Restricting at the Plant level will be satisfied if you delete the Idoc data with in the function module MASTERIDOC_CREATE_MATMAS.
    It will work. Consequently you can add an additional check in XI to do this check, but this will increase the number of connections made to R3.
    Hope it helps.
    Thanks,

  • Creating new material using i/b MATMAS IDOC

    Hi mates,
    I'm trying to create a material in R/3 using an inbound MATMAS IDOC. The material type I use is confiugured for internal number assignment. So, I'm leaving the E1MARAM-MATNR blank.
    But, the IDOC failing saying 'No Material Transfered'.
    I'm using '005' for the field MSGFN in E1MARAM, E1MAKTM, E1MARMM etc. Is this the right value?
    I'm trying to create a material with only the basic view data maintained.
    Whats wrong/missing in my config?
    I appreciate ur inputs.
    thx in adv
    praveen

    Hi Praveen,
    Use WE19 transaction to execute the function module IDOC_INPUT_MATMAS01.
    Use different values for the MSGFN field and check it
    Regards
    Arun

  • ADD FIELD TO MATMAS IDOC

    Hi all
    I need to add a field (LABST) in to the STANDARD MATMAS IDOC structure.
    How can I Do it?
    Can someone help me please.
    Thankyou

    Hi Simon,
    You have to extend the IDoc.
    Transaction code is WE30. Please check these sites to get more info.
    http://help.sap.com/saphelp_470/helpdata/EN/dc/6b7d6243d711d1893e0000e8323c4f/content.htm
    http://sap.ittoolbox.com/documents/document.asp?i=2358
    Kindly reward points for helpful replies.
    Thanks
    Vinod

  • Work scheduling view via MATMAS idoc

    Can somebody tell me which segment and field is used in MATMAS idoc to create Work scheduling view?

    Hi,
    Identify the various Basic Types available for MATMAS and then provide the basic type in transaction WE30 and you can check the various segments being generated.
    Thanks
    Krithika

  • Userexit: Outbound matmas idoc

    Hi Guys,
    I am looking for a suitable userexit for Outbound matmas idoc.
    The requirement is once the idoc number has been generated with idoc status AFTER that only i need a userexit for my own .
    I am using BD10 transaction code to create the MATMAS idoc.
    Will appriciate your help..!
    Thanks,
    Biswajit.

    Hi,
    The flow is like this in BD10....
    CALL FUNCTION 'MASTERIDOC_CREATE_REQ_MATMAS'
       CALL FUNCTION 'MASTERIDOC_CREATE_MATMAS'
          CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE'        " it return the control record with idoc no after execution
              CALL FUNCTION 'IDOC_CREATE_ON_DATABASE'    " it return the control record with idoc no after execution
                  CALL FUNCTION 'EDI_DOCUMENT_CLOSE_CREATE_TAB'     " it return the control record with idoc no after execution
                          PERFORM F09_IDOC_INSERT_WITH_NUMBER USING IDENTIFIER    " idoc no generates here in control record
                                                DOCNUM
                                                IDOC_CONTROL
                                                SYNTAX_RETURN
                                                FREE_RETURN
                                                SYN_ACTIVE.
    So i need a userexit / enhancement point after that with control record data.......

  • MATMAS IDoc - Batch Mgmt Flag Incorrect

    I am trying to link R/3 to our manufacturing system being developed with MII.  I've created a reduced message type for material masters and am attempting to send the MATMAS message type (MATMAS01 basic IDoc type) to a MII logical system. 
    Everything works perfectly except that the material batch management (XCHPF) flags in both the MARA and MARC segments don't contain any value even for batch managed materials. 
    We manage batch uniqueness at the material level and therefore I would expect the MARA-XCHPF field to have the "X" value but no value is being passed to the IDoc.
    Any ideas as to why the field doesn't have a value and what I can do to resolve?
    Thanks in advance.

    Randy,
    Check this notes.
    Note 1393947 - VL60/IDOC Batch indicator not always filled
    Note 481688 - ALE: Error messages while posting IDocs
    Reddy

  • Problem in triggering MATMAS IDOC through BD10 transaction

    Hi,
         My scenario is to trigger an IDOC(MATMAS)in BD10 and store it as an XML file in the physical directory.
    I have created a logical system for this and also created partner profile for the logical system defined.
    Further i've have configured XML Port has my reciever port of the outbound message type(MATMAS). But when i trigger the IDOC, it says that "1 Master IDOC setup for the message type MATMAS" and "0 Communication IDOCs generated" and the outbound IDOC is not recieved at the concerned directory.  Please help me out in solving this issue.

    Hi,
    While doing configuration u must take care of creation of Distribution model. Here you need to give message type,sender & receiver.
    At the same time you need to generate partner profiles. Results should give 'SYNCH' along with all info.
    Check all the inbound/outbound parameters are correct or not.
    If you satisfy with this pls close this issue and allocate some points.
    Regards
    KER.

  • New field in MATMAS Idoc

    I would like to add new field from MARD which was not included in standard MATMAS. There are some MARD fields in MATMAS already and I like to add one more field. Can someone give me step by step procedure in brief please ?. Thank you

    WE30 - create segment
    WE31 - extend you idoc and add your created segment to it.

  • MATMAS IDoc processing error

    Hi all,
    I have an issue while trying to simply ALE a material from one SAP4.6C system to another.  The MATMAS04 IDoc is being received properly by the receiving system, but goes to status 51 when we attempt to post it.
    The error message is:
    <b>"Function module not allowed: AFS_RETAIL_ARTMAS_IDOC_INPUT"</b>
    The inbound partner profile for MATMAS message type is specifying a process code <b>'MAT2'</b> which should call FM <b>IDOC_INPUT_MATMAS_MDM</b>.  Why would the system try to call the FM mentioned in the error?
    I have checked the partner profile, the process code, and the assignment of FM to message type as directed by the error message and they all seem to be correct.
    Thanks!

    Hi Stefan,
    Both sending and receiving system are on 4.6C.
    The cotrol record on the receiving side shows everything to be correct.  Message type is MATMAS and IDoc type is MATMAS04 as expected.
    Incidentally, the IDocs post correctly when pushed through the test tool in the receiving system and specifying the material function module.  It is only posting automatically or manually through BD87 that doesn't work.
    --Jack

  • Triggering MATMAS IDoc

    Hi Folks,
        I have a requirement to send IDocs to the other system on create or change of material. On any create or change of material I want a MATMAS01 IDoc to be triggered and to be sent to the partner system.
    1. I have chceked the Active checkbox for MATMAS in the tcode BD50.
    2. I have saved the Change pointer in the tcode BD61
    3. I have created the partner profile added the message types to it in the outbound parameter.
    4. I have created the distribution channel.
    But the problem is the IDoc is not triggering automatically once the material is created or changed in the source system.
    Kindly let me know how to resolve this.
    Regards,
      Santosh

    Hi,
    Activating the change pointer for the mnessage type wont create the Idoc, you need to manually or schdueld prog to create the idoc against chage pointers.
    Via change pointer, you have to run BD21 transaction or need to schedule RBDMIDOC to create an idoc.
    If its a new material you need to run BD10 transaction.
    Hope you clear, if not pls come back.

  • Reg. Custom MATMAS IDOC

    Hi Gurus,
    I created one custom idoc based on matmas. I want to raise that idoc whenever material created or changed (Changes only send to thirdparty). How can we do this.
    Thanks & Regards
    Krishna

    HI krishna,
    goto WE61 to activate change pointers first.
    then run the program RBDMIDOC.
    Regards,
    Chinna

Maybe you are looking for