Need to ALE only 2 fields through a reduced message type copied from MATMAS

Hi,
Only the Authorization group fields MARA-BEGRU and MARC-QMATA need to be transferred through ALE from one system to another one.  A new reduced message type has been created from MATMAS.
The fields BEGRU and QMATA have been selected through the BD53 transaction to be part of the segments.
Result: 3 segments are part of the new Message type: E1MARAM and its 2 children E1MAKTM and E1MARCM.
Problem:  Even the BD53 (Reduced message type) transaction has been used, too many unnecessary fields are transferred through the ALE. 
The following fields in the E1MARAM segment must not been updated (transferred) in the receiving system:
          -  PSTAT,
          -  LVORM
          -  MTART
          -  MBRSH,
          -  MATKL,
          -  MEINS,
          -  GROES,
          -  WRKST,
          -  SPART,
          -  VPSTA.
They should disappear from the segment.
The E1MAKTM segment must not been transferred to the receiving system because the user does not want to modifiy the Material description.  But the BD53 (reduce message type) seems to consider that segment as mandatory.
Only few 1EMARCM segments with specific Plants (WERKS) should be sent on the receiving system.  Not all the Plants.  That segment should not include the PSTAT field.  I have no control on which Plants to transfer.
<u>Revision</u>:
Only 2 segments must be ALE'd with only the following fields:
          1-  <b>E1MARAM</b>:
                    a)  MATNR (Material number)
                    b)  BEGRU (Authorization group)
          2-  <b>E1MARCM:</b>
                    a)  WERKS (Plant)
                    b)  QMATA (Material Authorization Group for Activities in QM).
What should I do to ALE only those 2 segments and only those specific fields?
Thanks a lot.
Diane.

Thanks Ferry for the previous answer,
I have a problem with the E1MARCM segment.
My sending and receiving systems do not have always the same Plant numbers.
If a Plant exists on the sending system and it does not on the receiving system, the Plant must not be created on the receiving system. But from the sending system, I do not know which Plants the receiving system has. This is why the IDoc contains all the Plants. But I added some logic in the  <b>inbound</b> customer-function, EXIT_SAPLMV02_002, to ignore the Plants that do not exist on the receiving system in doing a SELECT on the MARC table in the receiving system.
But that customer-function is called from the IDOC_INPUT_MATMAS01 function module, in the " WHEN  E1MARCM " section:
          PERFORM CHECK_USER_EXIT TABLES T_EDIDD
                                                                        USER_SEGMENTS
                                                           USING CURRENT TABIX.
          LOOP AT USER_SEGMENTS.
                     CALL CUSTOMER-FUNCTION '002'
                               EXPORTING
                                            MESSAGE_TYPE    = IDOC_CONTRL-MESTYP
                                            F_CUST_SEGMENT = USER_SEGMENTS
          ENDLOOP.
In the perform check_user_exit, no record is created in the user_segments table because all the segments in my IDoc start with ' E1 ' :
          LOOP AT IDOC_DATA INTO USER_SEGMENTS FROM CURRENT_TABIX.
                    IF USER_SEGMENTS-SEGNAM(2) = ' E1 '.
                        EXIT.
                    ENDIF.
                    APPEND USER_SEGMENTS.
          ENDLOOP.
The customer-function is called within the ' loop at user_segments '. This is why the customer-function is never executed and my code is ignored. So, all the IDocs in the receiving system are in the status 51 (red light).
Do you have any idea how to resolve my problem.
Thanks.
Diane.

Similar Messages

  • What's the difference between segment filtering and reduced message type

    Hi gurus,
    What's the difference between segment filtering and reduced message type? It seems they have the same functionality: Reduce the segment while idoc is generated.
    Thanks in advance.

    Hi,
    BD53 is for IDoc Reduction.
    this allows you to create a reduced message based upon a standard message type.If you want see mandatory fields. go to T-coe BD53 and give one standard messege type name and eg: matmas
    there mandatory fields will be in Green color..
    And BD56- This transaction is used to filter out segments of IDocs for combination of sender and receiver. This is usefull in scenarios where a standard IDoc with many segments is used but the receiving partner is only interested in some of the segments
    the table related to this transation is TBD20
      please go through below blog you have an idea abt that,
    http://wiki.sdn.sap.com/wiki/display/ABAP/ReducedMessageTypes
    http://saptotal.com/IDoc%20Segment%20Filtering.html
    regards,
    ganesh.

  • Reduced message type - Idoc without conversion rules

    Hi Friends,
    Am facing a strange situation while converting the Material Master data from 4.7b to ECC using BD21 transaction with reduced custom message type. I have reduced the standard msg type MATMAS05 using BD53 for the required field mapping both systems and I written the code using the exit EXIT_SAPLMV01_002 based on client req.
    The situation is that sometimes IDocs are failing and the error shows that some fields which I have not selected in E1MARAM segment of the reduced msg type are populated with some values(ex: zeroes-0, slash-/,spaces)
    Note: Conversion rules are not needed for this scenario.
    Please help me out how to get rid of this '/ ' or spaces which appear for unselected fields in outbound Idoc using reduced message type ?
    Thanks
    Saravanan

    Hi,
    Please check the documentation in WE60 tcode and see if the fields are required to be passed...
    Regards,
    Nagaraj

  • How can I add an extention to a reduced message type?

    We want to create change pointens for a subset of the HRMD messagetype.
    So we created a reduced message type (based on HRMD_A07) and activated only those segment we need.
    This works fine.
    Now we need to add information of IT2006, this is not available in the HRMD. Therefore we made a Z segment and an extention to HRMD_A7. We added the extention to the partnerport and to the infotype (T777D).
    The new segment is not send with PFAL, what do we need to do to make this work?

    You need to make sure the new Z segments are populated with the data. You can check that by putting a break point in function module MASTER_IDOC_DISTRIBUTE and check the EDIDD parameter MASTER_IDOC_DATA. Check whether your Z segment is populated there. And check in parameter COMMUNICATION_IDOC, whether your extension is there. If your Z segment is not populated, you may have to check how that can be populated.
    Regards,
    Gokul

  • Issue with the change pointer  for the reduced message type ZMATMAS

    Hi All,
    I have created reduced message type ZMATMAS for the MATMAS to create a Idoc when change or insert material master data fields( MARA-LAENG, MARA-BREIT, MARA-HOEHE) . My Problem is that the Idoc is generated with the status (03) but the fields(LAENG, BREIT,HOEHE)  are not getting fill with the values. They are always filling with the values  '/'). I have done the following steps to create idoc for the change pointer. Please check whether i have missed some steps.
    1.     Create reduction maintenance ZMATMAS  (Tcode BD53)
    keep the default selected segments E1MARAM, E1MAKTM
    2.     Add following data to maintain table view for the message type ZMATMAS  (Tcode BD52)
    Object      Table Name     Field Name
    MATERIAL       MARA      KEY
    MATERIAL     MARA     LAENG
    MATERIAL     MARA     BREIT
    MATERIAL     MARA     HOEHE
    3.     Activate particular change pointer in BD50
    Message Type       Active
    ZMATMAS         yes
    4.     Activate change pointers u2013 Generally (Tcode BD61).
    5.     Assign Segment fields to change document fields (Tcode BD66 )
    Segment Type     Field Name     Object     Table Name     Field Name
    E1MARAM     BREIT     MATERIAL     MARA     BREIT
    E1MARAM     HOEHE     MATERIAL     MARA     HOEHE
    E1MARAM     LAENG     MATERIAL     MARA     LAENG
    6. I have done the distribution model settings (BD64) and  the idoc configurations
    1.     Logical System
    2.     RFC destination
    3.     Create port
    4.     Create partner profile
    7. I changed the fields in material master data(Tcode MM02)  and I executed the Tcode BD21.
    Idoc is generated but the fields are not getting fill with the values
    (Note: some fields  are filled with values e. g material number, material description)
    I checked the Idoc data segment E1MARAM (WE02)
    Fld name   Fld cont.
    LAENG       /
    BREIT       /
    HOEHE      /
    Can you please let me know the issue
    Prad

    Issue is solved when I select the segments and the fields in the segments (Tcode :BD53)
    Prad

  • ALE-IDocs: Issue on COGRP1 & COGRP6 Message Types

    Dear Experts,
    I need to send the Cost center groups data and Profit Center groups data from one system to other, I had sent this for one time using the tcodes, from now on I need to send only the changed data, so configured the ALE for this.
    I activated change pointers generally in BD61 and then activated change pointers for message types in BD50. Cost Center Group (COGRP1), Profit Center Group (COGRP6).
    Why is RBDMIDOC program not showing any output when executed with standard message types COGRP1 and COGRP6 ?
    It is working fine with other message types like MATMAS, DEBMAS, COSMAS, PRCMAS, CREMAS.
    Tcode: BD59: Assignment of Object Type to Message
    Tcode: WE30: Develop IDoc Types
    Tcode: BD52: Change document items for message type
    So, COGRP1 does not have assignment of all the segments that are displayed for the IDoc Type: COGRP01 in WE30. Do we need to assign all these segments and fields to the message type in BD59? If so, how to create this ALE Object Types and what are these table names and fields in BD52., any user exits kind of thing for populating the fields if we do this way?
    I am really having trouble and great confusion with this.
    I would really appreciate you if you could provide me an answer or a hint.
    Thanks in advance for the time you spent on this.
    RV

    Hi,
    You need to follow following steps for the activation of change pointer.
    1) Enable change pointer globally <b>(BD61)</b>
    2) Enable Change Pointers for a Message Type <b>(BD50)</b>
    3) Specify the Fields for Which Change Pointers Are to Be Written <b>(BD52).</b>
    <b>BD59</b> is used to Assign Filter Object Type to IDoc Field. Then you can add filter while creating distribution model.This is used when you have to filter the Idoc at distribution stage. It has nothing to do with the change pointer technique.
    In BD52 , you have to assign the change pointer object(this you can find using <b>T.code SCDO</b>), table name and field.In your case change doc object is <b>ALESETS</b>
    Just make sure that you are making changes in Cost center groups data and Profit Center groups and then execute program RBDMIDOC.
    Regards,
    Monika

  • ALE - Status 52 Idocs for HRMD_A message type

    HRMD_A Idocs in target system are not completely posted, turning into status '52'. Most of the times the infotype 1001 idoc with relations ship P->S arrives before the idoc which has the actual objects(P, S) causing 'Relationship imposible because the object does not exist". We use program RBDAPP01 for inbound processing of Idoc which should take care of Serialization based on the time stamp of idoc creation in source system.
    Change pointors for Message type HRMD_A are processed using program RBDMIDOC in source system.
    It is unlikely that relationship P->S is created without object P being created in the source system. So the change pointors should create the idocs in the same sequence. But it is not happening.
    Any help on this appreciated.

    Hi Santosh,
    If you haven't found by now the .... here is the Solution:
    First change the size of table T77S0  check out note 305688
    Then process the IDOCS again - check out note 363187
    Regards
    Luis

  • To reduce a miror copy from high redundancy ASM configuration to normal?

    If we have configured "high redundancy ASM disk group", then late on, wanted to change it to "normal redundancy", then it becomes 2-mirror copies.
    Can I achive that, and what steps ?
    Thanks for your inputs in advance.

    backup database (someplace other than ASM)
    shut down database
    drop diskgroup
    recreate diskgroup with normal redundancy
    restore database
    or
    create new diskgroup with normal redundancy
    migrate all datafiles to new diskgroup
    (look at RMAN backup datafilecopy and switch datafile)
    you must shut down the database in order to move the system datafile etc... Which, if the database is small enough, it may be faster to do option 1.

  • Message type PRCMAS cannot be reduced

    Hi friends,
    Our company are running on multiple sap systems and now we want to process profit center master data on a single sap system and pass the data over to the other sap systems. I've found the standard message type PRCMAS which can realize profit center master data synchronization. But the issue is our controlling area is different between those SAP systems.
    client
    controlling area
    100
    1000
    200
    2000
    300
    3000
    So, i must create a new reduced message type copy from PRCMAS. But the system pop-up a message:
    Message type PRCMAS cannot be reduced
    Message no. B1144
    Diagnosis
    There are different message types for different applications in the R/3 System.  However, reduction is not possible for all message types depending on their business function and technical aspects.
    Procedure
    Please choose a message type that allows reduction
    What should i do? I only want to set the conversion rule for the message type PRCMAS to set the controlling area as constant and assign to different client. But unfortunately, i cannot go ahead.
    If someone could help me!
    Thanks in advance
    Jessie

    For the message SERDAT processing in the inbound partner profiles should be set to 'immediate processing'.

  • Query for Inbound processing for ALE IDOC & Outbound through Change Pointer

    Hi,
    I have a scenario, in which I have reduced Message Type for HRMD_A as Inbound and Outbound both.
    The Problem that I am facing is , whenver the inbound Idoc processing takes place, it updates the Infotypes and at the same time, as updation is done, Change Pointers write entries for the same in BDCP2. So, again the same changes are tracked for Outbound Message type and creates the idoc and post it again.
    This need to be avoided. The requirement is to stop such processing of the data from sending again.
    Any help for this would be appreciated.
    Regards,
    Heena

    Hi Heena...
    please check the fields present corresponding to the messagetype "HRMD_A" in trnsaction BD52. keep only the reuired fields and delete the remaining fields in BD52 trnsaction. if any changes happened in the required fields then change pointers will trigger an idoc. So, please check the fields present in BD52 transaction.
    please let me know if you need any clarifications further.
    Regards,
    Lokeswari.

  • Need of ALE settings to connect 4.7 to 5.0 to send IDOc

    Hi
    I have two servers 4.7 and 5.0 .
    Now I want to send Idoc from 4.7 client 800 to 5.0 client 800.
    Can anybody provide me the steps to create ALE settings and to send IDOC.
    creating logical systems in source and destination and creating RFC and partner profile and port.
    Thanks in Advance

    Hi,
    For ALE senerion for sending the material from one system there are three methods are there
    1) Executable program only for Master Data
    2) Message type Master As well as Transcation Data
    2) Change Pointers Master As well as Transcation Data
    1) SCC4 Create the Logical systems.
    ALG800 for 800
    ALG810 for 810
    2) Assign the Logical systems to the Client using SCC4> selecting the Client and Double click> maintain the logical system name which you had created in the step 1
    3) Main RFC destination SM59---> use the same Logical system name as the Logical system name
    log on to 800 and goto SM59 --> create
      ALG810 --> provide the 810 logon details and save
    test with remote logon...it will open the client 810..
    logon to client 810 goto--> sm59 --> create
       ALG800 --> provide the 800 logon details and save
    test with remote logon...it will open the client 800..
    logon to 800 goto BD64 maintain CDM-->change
    create CDM
    ZCDM01  CDM
    ALG800 sender
    ALG810 Reciever
    MATMAS Message type
    ZCDM01  CDM
    ALG810 sender
    ALG800 Reciever
    MATMAS Message type
    save
    Environment ---> Generate partner porfile.
    edit --> distribute CDM
    Logon to 810
    goto BD64---> select CDM ZCDM01 ---> Environment ---> Generate Pratner Profile.
    Edit --> distribute.
    ALE Setting are compleated.
    Logon to sender system 800.
    create material in MM01
    Material   10001
    Industry sector mechanical engee
    Material Type finished
    enter
    Base Unit of Measure KG
    Weight unit         KG
    Gross Weight         100
    Net Weight           100
    save
    Execute BD10 in client 800
    Check the Idoc in WE05.
    Log on to Client 810
    Execute BD11
    check the IDOC status in WE05
    goto MM03 provide the material numer enter...
    Thansk,
    Nelson

  • ALE: setting up reduced IDoc type for use in 4.7 and ERP 2005 problem

    I need to set up a reduced HRMD_A message type and then use it to send HR data from a 4.7 system to an ERP 2005 system.
    To define the reduced type in both systems I use transaction BD53 (Idoc reduction maintenance).
    The problem is that the transaction offers HRMD_A06 as the basic type on a 4.7 system and HRMD_A07 on ERP 2005. Thus i cannot  set up identical definitions.
    I suppose I should  'step back' to A06 at the ERP 2005 system somehow, but where to look for?..
    Thank you in advance!

    The table is maintained with BD69 - Assignment of message type to IDOC type.
    In my case I added one line with values:
    Message type: {my reduced message type}
    Basic type: HRMD_A06
    Extension: {my HRMD_A06 extension}
    Also it looks like there is another (better?) way of making the assignment. It is done with WE82, described in sap help here http://help.sap.com/saphelp_erp2005vp/helpdata/en/dc/6b7db043d711d1893e0000e8323c4f/frameset.htm and also discussed in this topic.
    SAP ERP Human Capital Management (SAP ERP HCM)

  • ALE: reduced IDOC type

    I have 4 systems, i.e.: PLM and R3-1, R3-2, R3-3
    I want to send a reduced IDOC for material master (MATMAS) from the R3 instances to PLM
    I created a reduced IDOC type for MATMAS and created a transport  request of ALE tables of reduced message type in PLM.
    However, I am unable to import the transport request from PLM to the R3 instance, because PLM is unicode and R3 is non-unicode.
    As a workaround until I resolve the unicode issue, I re-create the reduced IDOC in the R3 instance and I am able to send the material master data correctly.
    Is there a simpler workaround than re-creating the reduced idoc in each R3 instance?
    Also, when I send material master data from R3 using BD10, it does not send associated material class even though, I specify 'send material in full'. Where does that association take place?
    Any thoughts?

    The table is maintained with BD69 - Assignment of message type to IDOC type.
    In my case I added one line with values:
    Message type: {my reduced message type}
    Basic type: HRMD_A06
    Extension: {my HRMD_A06 extension}
    Also it looks like there is another (better?) way of making the assignment. It is done with WE82, described in sap help here http://help.sap.com/saphelp_erp2005vp/helpdata/en/dc/6b7db043d711d1893e0000e8323c4f/frameset.htm and also discussed in this topic.
    SAP ERP Human Capital Management (SAP ERP HCM)

  • Copying from client through se71 is getting saved as local object only?

    hi.
    i am copying the form from std to z form through se71.but after doing copy from client,it is getting saved automatically s a local objct $tmp.
    Also,there is no option enabled to save it to transportable object.
    in se80,in the object list also that object is not reflecting.

    check it
    Re: local object to transport request for a form
    just go to SE03  > object  Directory > change object directory entries

  • Distributing message type MATQM using ALE

    Hi everybody!
    I am using ALE to distribute material data. This already works. Now I also want to distribute material data for quality management.
    When I try to distribute materials using BD10 I get this message:
    Could not determine recipients for message type MATQM
    So I tried to create a new distribution model for MATQM using BD64. Unfortunately I could not choose MATQM or MATQM01 as the message type. (Error: Message type MATQM01 unknown)
    However, in transaction WE60 I can display message type MATQM01.
    What is the problem?
    best regards
    Roland

    Hi Roland,
    BD10 only can be used with message type MATMAS.
    If you want to send message type MATQM and IDoc type, please use this FM <b>MASTERIDOC_CREATE_SMD_MATQM</b>. You still need to maintain partner profile (WE20) and IDoc Port (WE21).
    Other you can use <b>Change Pointer</b> (BD21) to send out and ensure you have activated the change pointer for message type MATQM (BD50).
    Hope this will help.
    Regards,
    Ferry Lianto
    Please reward points if helpful.

Maybe you are looking for