IDoc/ALE Data Transfer-Scenario

Dear All,
I want to transfer data from Master/Header table(Client 1) to the ZTable(Client 2)
with the help of ALE plz suggest how.
Thanks,
RP

Hi RP,
I guess this is the wrong forum.
Try it elsewhere; i hope you will get a quicker response.
Regards Mario

Similar Messages

  • Errors in ALE data transfer to E-Recruiting.

    Hello,
    I need help with my ALE for E-Recruiting.
    We are on E-Rec 604 with seperated standlone e-rec system.
    We have set up ALE Data transfer for object type P from ECC QA to E-Rec QA system but unfortunately the I-Doc is always gettign posted with status 52.
    Those are the messages:
    Object 01 ,P ,01012021 does not exist: infotype 0105 cannot be created
    Object 01 ,P ,01012021 does not exist: infotype 0009 cannot be created
    Object 01 ,P ,01012021 does not exist: infotype 0006 cannot be created
    Diagnosis:
    You have tried to create infotype 0105 for plan version 01,object type P,object ID 01012021. However,the object does not exist.
    PA objects exist if infotypes 0000, 0001, and 0003 have been created.
    PB objects exist if infotypes 4000, 0001, and 0002 have been created.
    PD objects exist if infotype 1000 has been created.
    I followed the setting of "standalone" attachment to note 997181:
    HRSYNC_P                                    CONV_HR_DATA_TO_EREC (active as of Release 604)
    HRALE00INBOUND_IDOC             HRRCF00_INBD_NEWMOD (active as of Release 604)
    HRALE00SPLIT_INBOUND            HR_INB_PROCESS_IDOC (inactive as of Release 604)
    HRALE00INBOUND_IDOC             HRRCF00_DELETE_SPREL (inactive as of Release
    604)
    HRALE00SPLIT_INBOUND            HR_INB_PROCESS_IDOC (active up to Release 603)
    HRALE00INBOUND_IDOC             HRRCF00_DELETE_SPREL (active up to Release 603)
    So we have activated only the CONV_HR_DATA_TO_EREC and HRRCF00_INBD_NEWMOD because we are on 604.
    We have distributed Infotypes 0000, 0001, 0002, 0105 (Subtypes 0001 and 0010), 0006, and 0009 and I have to distribute the P - CP relation with 1001 A209.
    Somebody could help me please?.
    Thanks,
    Esther

    Hi Esther,
    Can you share you inputs how you have fixed the issue.
    Currently we are following I2 A Scenario according to the link
    http://help.sap.com/erp2005_ehp_05/helpdata/en/49/46037f06971ec6e10000000a42189b/frameset.htm
    DO we need activate the swiches  in HR System or Erec System.I believe it has to be in HR
    HRALX HRAC - X
    HRALX PBPHR ON
    HRALX USRAC X
    RECFA HRRFC
    RECFA RECCE
    RECFA DTCBA
    BADI do i need to activate only below one's
    HRSYNC_P
    CONV_HR_DATA_TO_EREC (active as of Release 604)   HR system
    HRALE00INBOUND_IDOC
    HRRCF00_INBD_NEWMOD (active as of Release 604)   Erec System.
    Correct me if im wrong.

  • ALE Data Transfer Issue--Needs Immediate Attention

    Hello Gurus
    I am hoping somebody can guide me here--
    We are on E-Rec 603 with seperated standlone e-rec system.
    we have set up ALE Data transfer for object type P from ECC QA to E-Rec QA system but unfortunately the I-Doc is always gettign posted with status 52 ( application document not fully posted).
    The infotypes 0000,0001,0002,0006 and 0105 are being transferred. The report HRALXYSNC refuses to recognise the 'P' object transferred and says=='data not found for search condition'.
    We debugged HRALXSYNC and found that IT 0003 needs to be included but we tried transferring that too--however, the ALE still fails to transfer the data.
    Not sure why the data transfer is not happening--what is the best alternative?
    Would really reallly appreciate some light....!!
    Thanks
    Tania

    Hello Tania,
    first of all we should have a look on your system landscape. If you have e-recruiting on an standalone server, the server installation should only include basis components (BASIS, ABA, PI, ...) and the e-recruiting component. Running e-recruiting standalone on a server with a complete ERP installation is not officially supported up to EhP3.
    Could you please check that you either have the first landscape situation or if you have installed a full ERP implemented note 1147882.
    Before running some ALE at all ensure that the system works well and w/o any SLG1 entries for external candidates and internal candidates created using report RCF_CREATE_USER.
    Then make sure the BAdI implemtations are set accorting to note 997181:
    BAdI                    Implementation
    HRALE00SPLIT_INBOUND    HR_INB_PROCESS_IDOC -> activated
    HRALE00INBOUND_IDOC     HRRCF00_DELETE_SPREL -> activated
    HRSYNC_P                CONV_HR_DATA_TO_EREC -> deactivated (if existing)
    HRALE00INBOUND_IDOC     HRRCF00_INBD_NEWMOD -> deactivated (if existing)
    For the distribution model define a filter restriction the infotypes / subtypes destributed for P to:
    Infotype 0000
    Infotype 0001
    Infotype 0002
    Infotype 0006 Subtype 0001
    Infotype 0105 Subtyoes 0001, 0010
    If you want to include the OM in E-rec (use positions in requisition maintenance, etc.) add a filter for Infotypes 1000 and 1001 for objects P, S, O and C (you can use the subtype to restrict relations and avoid unnecessary relations in the IDoc. P->CP relation is only necessary for EhP 4 and higher.
    Make sure you use the best practise step by step descripion for the intial data transfere for EhP 3 documented in note 997181 document Two_Instance_E-REC_Integr_ERP_EN.pdf page 4, add the processing for type C after each object type S step.
    Hope that helps.
    Kind regards
    Roman

  • ALE data transfer in E-recruiting

    hi All,
    We are Implementing E-recruitment in HCM.
                I have following 2 requirements
    Case 1). Distribute data of infotypes 0000,0001,0002,0006,0022,0023,,0024,1000 and 1001 into ER(E-recruiting) from my HCM (ECC) system. This i have achieved using message type HRMD_A and setting up ALE as per standard guidelines.
    Case 2) i have to transfer Candidate data which gets created in E-recruitment server back into HCM(ECC) server(reverse of case 1) and stored them in infotypes 0000,0001,0002,0006,0022,0023 and 0024. How this can be achieved ??
      is there any standard way i mean IMG configuration or ALE setup to transfer this data back into HCM (ESS)  server?? or any BAdis or BAPIss??
        kindly suggest me some solution if anyone  of you have encountered the same situation in past. The final solution i m thinking is of creating custom basic IDOC type, message type and custom programs  for inbound and outbound processing but before  doing this i just  wan to have a confirmation that there is no standard way of doing this...
    Thanks in advance..

    Hi.
         There is a standard  activity in e-Recruiting  "Data Transfer for New Employee"  which transfer the Candidate data from e-Recruiting to HCM system in temprary table T752F. when  you hire this candidate from PA48 all transfer data will get stored in respective Infotype of SAP HCM system.. 
    Thanks,
    Madhu

  • ALE data transfer from E-recruitment to HCM

    hi All,
    We are Implementing E-recruitment in HCM.
                I have following 2 requirements
    Case 1). Distribute data of infotypes 0000,0001,0002,0006,0022,0023,,0024,1000 and 1001 into ER(E-recruiting) from my HCM (ECC) system. This i have achieved using message type HRMD_A and setting up ALE as per standard guidelines.
    Case 2) i have to transfer Candidate data which gets created in E-recruitment server back into HCM(ECC) server(reverse of case 1) and stored them in infotypes 0000,0001,0002,0006,0022,0023 and 0024. How this can be achieved ??
      is there any standard way i mean IMG configuration or ALE setup to transfer this data back into HCM (ESS)  server?? or any BAdis??
        kindly suggest me some solution if anyone  of you have encountered the same situation in past. The final solution i m thinking is of creating custom basic IDOC type, message type and custom programs  for inbound and outbound processing but before  doing this i just  wan to have a confirmation that there is no standard way of doing this...
    Thanks in advance..

    Hi Michell,
    For this purpose, you will have to repair in three places.
    1. One is the FM: HR_PREPARE_NEW_EE
    Fro example you want to add something for infotype  008 you need to add this code ( level being the value you want to pass. ) : 
    PERFORM ppv USING email 'P0105-USRID' '03'.
    Add the this in the import parameter as well.
    2. You need to change include MP000040 under form: process_infogr. The internal table : proposed_values is carrying all the values.
    You can insert your code right after this SAP's loop :
    LOOP AT proposed_values WHERE infty EQ infogr-infty   "XDPK139847
                                    AND seqnr IS INITIAL .      "XDPK139847
            IF proposed_values-fname EQ 'PSPAR-SUPDG'.          "QNUK74530
              pspar-supdg = proposed_values-fval.               "QNUK74530
            ELSE.                                               "QNUK74530
              MOVE proposed_values-fname                        "QNUK74530
                TO initial_values-field_name.                   "QNUK74530
              MOVE proposed_values-fval                         "QNUK74530
                TO initial_values-field_value.                  "QNUK74530
              APPEND initial_values.                            "QNUK74530
            ENDIF.                                              "QNUK74530
            DELETE proposed_values.                             "QNUK74530
          ENDLOOP.                                              "QNUK74530
    For example for e mail it will be :
          if infogr-INFTY = '0105' and infogr-subty = 'U006'.
            infogr-subty = 'U009'.
            clear wa_infogr.
            loop at infogr into wa_infogr
              where INFTY = '0105' and subty = 'U006'.
                    wa_infogr-subty = 'U009'.
            modify infogr from wa_infogr.
            endloop.
          if infogr-INFTY = '0105' and infogr-subty = 'U009'.
         LOOP AT proposed_values WHERE infty EQ infogr-infty   "XDPK139847
                                    AND seqnr = '03' .         "XDPK139847
            IF proposed_values-fname EQ 'PSPAR-SUPDG'.          "QNUK74530
              pspar-supdg = proposed_values-fval.               "QNUK74530
            ELSE.                                               "QNUK74530
              MOVE proposed_values-fname                        "QNUK74530
                TO initial_values-field_name.                   "QNUK74530
              MOVE proposed_values-fval                         "QNUK74530
                TO initial_values-field_value.                  "QNUK74530
              APPEND initial_values.                            "QNUK74530
            ENDIF.                                              "QNUK74530
            DELETE proposed_values.                             "QNUK74530
          ENDLOOP.
          endif.
          endif.
    3. You also need to change on the E -rec side in class:
    CL_HRRCF_ACT_DATA_TRANS_RECORD
    and method: TRANSFER_DATA.
    Hope this is helpful.
    Thanks
    Amina

  • ALE Data Transfer - Urgent help needed

    I am trying to set up an ALE interface from a SAP ECC 6 system to another SAP ECC 6 system using HRMD_A idocs.  The complication I have is in the receiving system, I need to generate a new PERNR for all employees transferred. 
    Can anybody advise how to go about doing this?
    Many thanks
    Jez

    Hi you can send the employees from sender system to reciever system.
    With the help of transaction pfal you can send the personnel number.
    You have to choose the ploan version 01
    object type will be p
    in object id write the employee number which will be transferred to the reciever system
    Then push the run button.
    But you have to configure HRMD_A in ALE implementation.

  • IDOC bad data transfer to XI

    hi. I have a problem.
    sender system send an IDOC to XI.
    when I check the IDOC in WE02 found that one of fields of the idoc have a "#" (Torre B1 - B#Unimev). When XI recive the IDOC with XML format the "#" character is transformer to " "(Torre B1 - B Unimev). any ideas why it can be?
    repeat, when i check in sxi_monitor> inbound message> payloads>MainDocument> I  see  <ZZAD_STREET_CO>Torre B1 - B Unimev</ZZAD_STREET_CO>.
    Who must resolve it, R/3 team or XI??
    another doubt i have is: who create XML document:  R/3 or XI??
    Thanks & Regards,
    Rodrigo
    Message was edited by: Rodrigo Pertierra

    Hi Rodrigo,
    I would ask your question in the XI forum (Exchange Infrastructure), and not in the SAP GUI forum.
    Regards
    Rolf

  • How to load hierarchie with IDOC as data transfer method

    hi ,this is balaji, i have doubt.
    can any one please explain, how to up load hierarchies  using IDOCs. If any material provided could be helpful.And also give me what are the pros and cons.
    regards
    balaji.p

    HI Balaji,
    Check out the following link to load hierarchies:
    http://help.sap.com/saphelp_bw33/helpdata/en/fa/e92637c2cbf357e10000009b38f936/content.htm
    regards

  • Condition record data transfer

    I have a scenario where condition record data from ECC needs to be transferred to MDM.
    I can see COND_A01,COND_A02 idocs in ECC .Pl can you tell me which one is relevant for ALE data transfer.
    Is there any transaction/report (For example BD10 is used for material data transfer) which can generate idoc of condition record and distribute it to receiver
    Pl can you suggest on this.
    thanks,
    Sharada

    I think there is no standard program for distributing Condition records.
    As suggested by Eshwar use COND_A02.
    u are distributing only Condition records to MDM that means u have condition record repository over there.
    i don't know what is the mian program to create Condition Records .
    see is a way to attach output types to that and NACE configurations to distribute it.
    Suresh

  • Data Transfer Between HR and Erec

    Hi all,
    We are using having 2 backend systems 1 for HR other than Erec and another one for erec.
    Now we have setup the ALE data transfer using Message type HRMD_ABA.
    In erec we have only ERECRUIT Component deployed in backend,no EA HR or SAP HR component deployed.
    MEaning no PA* tables.
    Now when Transfer personnel number(HR!001-A008 with Position) to erec box,it says no pernr exist.
    Howver i cannot tranfer the pernr from ECC to Erec as we dont have PA* tables in Erec.
    Can you share me the object types that are transferred from ECC to EREc and EREC and ECC.
    What are the components to be deployed in backend Erec box.
    In Portal for requistions application which should backend(System Object) and for recruiter and recruitment admin applications which should be the backend system(System Object).
    Thanks,
    Nachy

    Hi ,
    1) First get your users created with roles in your Erec system
    Example recruiter ,Manager ,Recruitment Admin
    2) Get your Structure created in your HR back end system .
    3)Make sure you maintain your basic Infotypes with 0105 miantained (System user name /Email id )
    Assign the user to 0105 subtype 0001
    4)ALE that you have setup first move Org structure moved
      next move the person (Pers no ) .
    ALE chose the insert mode and goto WE10 if yoru IDOCS are clean without errors .
    Make sure all the personal data including address ,postal code is all maintained .
    Let me knwo if it helps
    Regards
    Santosh

  • Data Transfer Erec and ECC HR

    Hi all,
    We are using having 2 backend systems 1 for HR other than Erec and another one for erec.
    Now we have setup the ALE data transfer using Message type HRMD_ABA.
    In erec we have only ERECRUIT Component deployed in backend,no EA HR or SAP HR component deployed.
    MEaning no PA* tables.
    Now when Transfer personnel number(HR!001-A008 with Position) to erec box,it says no pernr exist.
    Howver i cannot tranfer the pernr from ECC to Erec as we dont have PA* tables in Erec.
    Can you share me the object types that are transferred from ECC to EREc and EREC and ECC.
    What are the components to be deployed in backend Erec box.
    In Portal for requistions application which should backend(System Object) and for recruiter and recruitment admin applications which should be the backend system(System Object).
    Thanks,
    Nachy

    Hi,
    Check the link :
    http://help.sap.com/saphelp_erp2005/helpdata/en/45/8150635e9c40c1e10000000a1553f7/frameset.htm
    Supported infotypes for transfering data from the E-Recruiting to the HR-System are the PA infotypes 0,1,2 and 6. There are 15 fields sent to pa48 if they were filled in the E-Recruiting system, which are
    - forename, initials, surname
    - gender
    - birth date
    - correspondance language
    - address (street, city, streetcode, region, country)
    - hiring date
    - organisation unit
    - position
    - personel number (for internal candidates)
    So these are the infotypes which can be transfered automatically and cause no problems. If you want the "title" to be transferred additionally, you have to adjust the  system behaviour accordingly.
    To set up data transfer,
    In E-Rec System, use Tcode - BD64 Partner Type LS - Generate partner profile for the ECC System
    Use Tcode - WE20 for the Partner profiles checking
    For ECC Partner Profile, Give Outbound parameters - Messahge type HRMD_ABA and SYNCH. Give Inbound parameters- Message Type HRMD_ABA
    In ECC system, use BD64 for the Partner Type LS. Partner Type LS - Generate partner profile for theCreate Erec System(
    Use Tcode - WE20 for the Partner profiles checking
    For E-Rec Partner Profile  , Give Outbound parameters - Messahge type HRMD_ABA and SYNCH. Give Inbound parameters- Message Type HRMD_ABA
    After doing data transfer using RHALEINI, use transaction SM58 to check whether the data has been transferred or not.
    Hope it helps!
    Arpita

  • Data transfer from E-recruitment to PA

    Dear All,
    we are Implementing E-recruitment. while transferinf the data from E-recruitment to Personnel administraion, I am getting the error, No data available from the partner system table T752F). We are using the same server for E-rec and PA.
    While doing the data transfer activity in E-recruitment i m getting succfulll. In R/3 while going to the Tcode PA48 i m getting the error.
    Please help me on this.
    Thanks and Regards,
    Revathi.

    An integrated hiring (data transfer) scenario with SAP e-recruitment
    and R/3 starts with creating a "Data Transfer for New Employees"
    activity within e-recruiting for the candidate selected to be hired.
    Data from e-recruitment is transferred to the target HR (via an RFC
    call) and stored there in a holding table (T572F) for processing
    by an appropriate action.  Within the HR system, execute transaction
    PA48 to access the holding table.  Select the candidate you want to
    process and then click the "Hire" button, and continue with the
    appropriate action.
    This message occurs, if you execute PA42 or PA48, in order to perform
    the personnel action RA (Integration with Recruitment in Partner
    Systems) and no data exists on the R/3  or external system.
    You will find all the relevant information in the IMG documents
    available. Please check;
    - Set Up Data transfer from SAP ECC
    - Set Up Data Transfer for New Employees

  • DTPs - Delta Init without Data transfer.

    Hi All,
    I am implementing the DTPs in my project where we replicate the old 3.x extractions with the bw7x functioanlity;
    Can anyone tell me if their is way to implement the "Delta Init without Data transfer" scenario with DTPs for
    both R/3 to BW(ODS) extraction or for the Datamarts - ODS to Cube within BW??
    Thanks in advance!
    Cheers
    Rao

    Hi Rao,
    Yes u can achieve Initialization without data in BI 7 DTPs.
    Goto ur DTp's Execute Tab, and Processing mode there drop down the list and select No Data Transfer,Delta Status in Source: Fetched.
    Assign points if helpful.

  • ALE/iDoc for Work Center data transfer

    Hello, community.
    I am working on several interfaces for the PP and PM modules using iDocs/ALE.
    One of the requirements is that only created and modified data must be distributed from R/3.
    For Work Centers, we are using basic type LOIWCS02 and message type LOIWCS. We are generating iDocs through transaction POIM, which has two transfer modes: Complete (data for all Work Centers etc.) and Change (only new and updated data).
    The Change Transfer Mode assumes you have set both Change Pointers and Change Documents for the objects to be transfered. Otherwise, it'll work just like the Complete Transfer Mode.
    Our PP consultant told me there is no configuration to generate Change Documents for Work Center data modifications.
    Can anybody give me other opinions? I'll resort to Z-table solutions only if I have no other options.

    Hi Danilo,
    Do you know what the process codes are for
    LOIWCS and LOIROU ?
    Appreciate your help.
    Thanks,
    Gopi.

  • Data Fir  IDOC  ALE  and EDI

    Hello All,
        I am newly join in IT company (Name don't want to specify) .  They have putted me in a consolidate project in which I do have to work on IDOC,ALE and EDI object.
    yet in my career with SAP ABAP I haven't work on the above mention terms of SAP. Can some One please guide me and provide me some material to prepare my self best for the things.
    Regards
    Swati Namdev

    Some use full Tcodes:
    ALE / EDI/ IDOCS TRANSACTION CODES
    Transaction Code     Description
    WE02     List Of All Idocs Created. (Default, Additional, EDI)
    WE05     List Of  Idocs Created.    (Standard, Additional)
    WE06     Active Monitoring For Idoc Processing.
    WE07     Idoc Statistics.
    WE08     Display View u201CFile Statusu201D:Overview-Path Name.
    WE09     Idoc Search For Business Contents (Database).
    WE10     Idoc Search For Business Contents (Archive).
    WE12     Modification Of Outbound File, Triggering Inbound Processing.
    WE14     Process All Selected Idocs.
    WE15     Selection Program For Issuing Output.
    WE16     Trigger Inbound Processing.
    WE17     Trigger Status Processing.
    WE18     Generate Test Status File For Outbound Idocs.
    WE19     Test Tool For Idoc Processing
    WE20     Partner Profile.
    WE21     Ports In Idoc Processing.
    WE23     Display Test Catalog Test Idoc Interface.
    WE24     Maintain Table View. Direction-1.(Outbound)
    WE27     Maintain Table View. Direction-2.(Inbound)
    WE30     Develop Idoc Type.
    WE31     Develop Idoc Segments.
    WE32     View Development.
    WE33     Maintain Table Views.
    WE34     Change View u201CTable Of Style Ids With The Objects To Be Loadedu201D
    WE40     Display System Process Code.
    WE41     Display View: Logical Msg Overview. For Outbund.
    WE42     Display View: Logical Msg Overview. For Inbound.
    WE43     Display Status Records.
    WE44     Display Partner Types
    WE45     Maintenance Interface: Forwarding Inbound/EDILOGADR For Application
    WE46     Global Parameter For Idoc Interface.
    WE47     Status Maintenance.
    WE50     Display Text For Process Code System.
    WE54     Idoc Function Module For File Name
    WE56     Display Status Process Code
    WE57     Idoc Assignment Of FM To Log. Message And Idoc Type.
    WE58     Text For Process Code Status.
    WE60     Documentation For Idoc Type.
    WE61     Documentation For Idoc Record Type.
    WE62     Documentation For Idoc Segment Type.
    WE63     Documentation For Idoc Record Types And Idoc Types (Parser).
    WE64     Process Code In Idoc Inbound And Outbound.
    WE70     Conversion Table For Basic Types.
    WE71     Conversion Table For Extensions.
    WE72     Conversion Table For Field DOCTYP.
    WE73     Conversion Table For Logical Message Type.
    WE81          EDI:Logical Message Type.
    WE82     Message Types And Assignment To Idoc Types.
    WE84     Assignment Table Between Idoc And Application Field.
    ALE / EDI/ IDOCS TRANSACTION CODES
    Transaction Code     Description
    BD10     Send Material (Matmas)
    BD11     Get Material.
    BD12     Send Customer.
    BD13     Get Customers
    BD14     Send Vendor.
    BD15     Get Vendor.
    BD16     Send Cost Center. (Cosmas)
    BD17     Request Cost Center.
    BD18     Send G/L Accounts.
    BD19     Get Master Data G/L Accounts.
    BD20     Inbound Processing Of Idocs Ready For Transfer.
    BD21     Creating Idoc Types For Change Pointers.
    BD22     Delete Change Pointers.
    BD23     Serialization Using Time Stamp: Deletion Of Old Time Stamp.
    BD24     Send Cost Elements.
    BD25     Send Activity Type (COAMAS)
    BD26     Request  Activity Type
    BD27     Cost Center/Activity Types: Transmit Plan Quantities And Acty Prices.
    BD28     Cost Center/ Cost Elements: Send Control Records.
    BD30     Material Bom Distribution. (Bommat).
    BD31     Document Structure Distribution. (Bomdoc)
    BD32     Plant Allocation To Material Boms Distribution.
    BD33     Distribution Of Material Variants. (STTMAT)
    BD34     Distribution Of Boms (BOMORD)
    BD35     ALE: Send Business Process Group.
    BD36     ALE: Send Business Process.
    BD37     ALE: Send Business Process Price.
    BD40     Generate Idocs For Serialization Group From Change Pointers.
    BD41     Dispatch Of Idocs  Of Serialization Group.
    BD42     Check Dispatch Status Of Idocs Of Serialization Group.
    BD43     Processing Inbound Idocs Of Serialization Group.
    BD44     Change View u201CSerialization Groupu201D.
    BD47     Dependence Between Methods.
    BD48     Dependence Between Methods And Message Type.
    BD50     Activate Change Pointers For Message Type.
    BD51     Characteristics Of Inbound Function Module.
    BD52     Determine Work Area.
    BD53     Reduce Message Type.
    BD54     Change View: Logical Systems
    BD55     Idoc Conversion.
    BD56     Maintain Idoc Segment Filters.
    BD57     Link Type And Serialization Type Of Message Type.
    BD58     Convert Organizational Unit.
    BD59     Allocation Of Object Type.
    BD60     Additional Data For Message Type.
    BD61     Activate Change Pointers Generally.
    BD62     Display Conversion Rule.
    BD63     Transport Of Ale Tables For A Message Type.
    BD64     Display Distribution Model.
    BD65     Maintain Idoc Type Required Fields.
    BD66     Change Idoc Fields.
    BD67     Function Module For ALE/EDI Overview.
    BD68     Maintain List.
    BD69     Assignment Of Idoc Type To Message Type.
    BD70     Cross-System Comparison Of Number Range Objects.
    BD71     Attributes For Receiver Determination.
    BD72     Active Events For ALE/EDI
    BD73     Start Error Handling For Non-Posted Idocs.
    BD75     Status Conversion With Trfc Execution.
    BD77     Generate Transport Requests For Distributing ALE Customizing Data.
    BD78     Monitoring Ale Customizing Data Transport
    BD79     ALE IDOC Segments - Conversion Rule
    BD81     Filter Objects For BAPI Parameter Filtering
    BD82     Generating Partner Profile
    BD83     Re-Processing Incorrect Outbound Odocs.
    BD84     Re-Processing Of Idocs After ALE Input Error.
    BD85     Consistency Check: Reassignment Between Two System.
    BD86     ALE Consistency Check: Create Purchase Order From Sales Order.
    BD87     Select Idocs
    BD89     Customizing Data Modeling For Distribution Model.
    BD91     Distribute All Characteristics Via ALE.
    BD92     Distribute Class Via ALE: Send Direct.
    BD93     Distribution Of Classification Data Via ALE.
    BD95     Ale Object View
    BD96     Filter Object For Receiver Determination Of Methods.
    BD97     Assign RFC Destination For Synchronous Method Calls.
    BD98     Consistency Check With Workflow Link
    BD99     Dependencies Between Message Types.
    BD100     Display Serialized Idocs. (Serialization Using Object Types)
    BD101     Serialization Using Object Types: Consistency Check.
    BD102     Ale: Outbound Channel Registry.

Maybe you are looking for