ALE Distribution LOIROU Change pointer

Hello
I want to know if it is possible to manage LOIROU idoc with change pointer management in SALE and how ?

Hello Jean,
I think you can manage LOIROU idoc with change pointers.
Steps are as follows:
1. Activae change pointers generally : TC : BD61.
2. Activate change pointer for message type LOIROU using TC : BD50.
3.Create an object for the Change Documents, by transaction SCDO.
4. Maintain Distribution model using BD64.
5. Maintain Partner profile & remaininf basic configuration.
6. After creating / changing document goto transaction BD21 and execute it with  Message type LOIROU.
Thats all!!
Cheers,
Nilesh

Similar Messages

  • Position data not getting ALEd correctly through change pointers

    Hi All,
    When Posiiton is updated in One system, it gets transfers to another systems through ALE/IDOCs using change pointer method.
    when a new holder is assigned to the position in system A,  the updated data is not getting tranfered to system B.
    All the ALE settings are correct, background jobs are scheduled correctly for the change pointers.
    How ever the updated position data is not getting transfered to system B.
    The IDOCs are faling with message " Relationship starting from 01O XXXXX impossible - 01S XXXX does not exist/is not active".
    Please let me know how to over come this error and tranfer the posoition data when ever it is changed.
    Thanks & Regards,
    Preethi G

    hello Sagar,
    u r dynamically generating dropdowns in ur view say VIEW1.U must be generating ur UI dropdowns on click of the button under a trnsparent container with a particular DROP DOWN INDEX ID .
    in ur onActionAdd method if u r generating drop downs with ID say DD101, DD102, DD103 and so on ...
    thn in ur close button , u need to use the method REMOVE_CHILD_NODE and try to remove the dropdowns with same index .
    u cn take reference of this code :
    DATA :
        DATA:
                lr_node_info     TYPE REF TO if_wd_context_node_info ,
                lr_node          TYPE REF TO if_wd_context_node,
                dd_indx_id       TYPE string .
    CONCATENATE lv_node wd_this->count_sysdel INTO lv_node.
            dd_indx_id = 'DD_1'.
            wd_this->count_sysdel = wd_this->count_sysdel + 1.
            wd_this->count_dd_sys = wd_this->count_dd_sys + 1.
            CONCATENATE dd_indx_id wd_this->count_dd_sys INTO dd_indx_id.
            lr_node = wd_context->get_child_node( name = lv_node ).
            lr_node->invalidate( ).
            CALL METHOD lr_node_info->remove_child_node
              EXPORTING
                name = lv_node.
            lo_drdwn = lo_container->remove_child( id = dd_indx_id ).
    here lv_node is the name of ur node , I am using count_sysdel of type NUM and concatenate statement
    to provide unique names to the generated node.
    u cn declare it under the attributes tab .
    u can have dd_indx_id = 'DD_1' and increment count each time using
    wd_this->count_dd_sys  which is another counter .
    do revert back if u need any assitance ,it shud help .
    rgds,
    amit

  • ALE Change pointer setup for master

    Hello everyone,
       When I am extracting data from R/3 some of the changes are not getting extracted.  I want to check if all the proper Message types are turned on or not.  What is the best way to do that?
    I am extracting 0cust_sales.
    thanks

    It is activated there, I checked.  Thats like a master switch which controls change pointers for all message types. 
    But dont I also have to turn on change pointer for each message type ?
    I am refering to customizing in R/3
    SAP Netweaver-> SAP Web Application Server -> IDoc Interface / Application Link Enabling (ALE)->Modelling and Implementing Business Processes->Master Data Distribution->Replication of Modified Data->Activate Change Pointers for Message Types
    Thanks

  • What is the use of change pointer concept in ale?

    what is the use of change pointer concept in ale?
    Edited by: Alvaro Tejada Galindo on Feb 6, 2008 5:10 PM

    ALE Architecture:
    It consists of an Outbound process, an Inbound process, and an Exception – Handling process.
    Outbound Process:
    ALE Outbound Process in SAP sends data to one or more SAP Systems. It involves four steps.
    1. Identify the need of IDoc: This step starts upon creating a application document, can relate to a change to a master data object.
    2. Generate the Master IDoc: The document or master data to be sent is read from the database and formatted into an IDoc format. This IDoc is called as a Master IDoc.
    3. Generate the Communication IDoc: The ALE Service layer generates a separate IDoc from the Master IDoc for each recipient who is interested in the data. Separate IDocs are generated because each recipient might demand a different version or a subset of the Master IDoc. These recipient-specific IDocs are called Communication IDocs and are stored in the database.
    4. Deliver the Communication IDoc: The IDoc is delivered to the recipients using an asynchronous communication method. This allows the sending system to continue its processing without having to wait for the destination system to receiver or process the IDoc.
    Inbound Process:
    The inbound process receives an IDoc and creates a document in the system.
    1. Store the IDoc in the database: The IDoc is received from the sending system and stored in the database. Then the IDoc goes through a basic integrity check and syntax check.
    2. Invoke the Posting Module: The control information in the IDoc and configuration tables are read to determine the posting program. The IDoc is then transferred to its posting program.
    3. Create the Document: The posting program reads the IDoc data and then creates a document in the system. The results are logged in the IDoc.
    Over view of IDocs:
    IDoc is a container that is used to exchange data between any two processes. The document represented in an IDoc is independent of the complex structure SAP uses to store application data. This type of flexibility enables SAP to rearrange its internal structure without affecting the existing interface.
    IDoc interface represents an IDoc Type or IDoc data. IDoc Type represents IDoc’s definition and IDoc Data is an instance of the IDoc Type.
    IDoc Types:
    IDoc type structure can consist of several segments, and each segment can consist of several data fields. The IDoc structure defines the syntax of the data by specifying a list of permitted segments and arrangement of the segments. Segments define a set of fields and their format.
    An IDoc is an instance of an IDoc Type and consists of three types of records.
    i. One Control record: each IDoc has only one control record. The control record contains all the control information about an IDoc, including the IDoc number, the sender and recipient information, and information such as the message type it represents and IDoc type. The control record structure is same for all IDocs.
    ii. One or Many Data records: An IDoc can have multiple data records, as defined by the IDoc structure. Segments translate into data records, which store application data, such as purchase order header information and purchase order detail lines.
    iii. One or Many Status records: An IDoc can have multiple status records. Status record helps to determine whether an IDoc has any error.
    Message in IDoc Type:
    A Message represents a specific type of document transmitted between two partners.
    Outbound Process in IDocs:
    Outbound process used the following components to generate an IDoc. A customer model, and IDoc structure, selection programs, filter objects, conversion rules, a port definition, an RFC destination, a partner profile, service programs, and configuration tables.
    The Customer Model:
    A customer model is used to model a distribution scenario. In a customer model, you identify the systems involved in a distribution scenario and the message exchanged between the systems.
    Message control:
    Message control is a cross application technology used in pricing, account determination, material determination, and output determination. The output determination technique of Message control triggers the ALE for a business document. Message control separates the logic of generating IDocs from the application logic.
    Change Pointers:
    The change pointers technique is based on the change document technique, which tracks changes made to key documents in SAP, such as the material master, customer master and sales order.
    Changes made to a document are recorded in the change document header table CDHDR, and additional change pointers are written in the BDCP table for the changes relevant to ALE.
    IDoc Structure:
    A message is defined for data that is exchanged between two systems. The message type is based on one or more IDoc structures.
    Selection Program:
    Is typically implemented as function modules, are designed to extract application data and create a master IDoc. A selection program exists for each message type. A selection program’s design depends on the triggering mechanism used in the process.
    Filter Objects;
    Filter Objects remove unwanted data for each recipient of the data basing on the recipients requirement.
    Port Definition:
    A port is used in an outbound process to define the medium in which documents are transferred to the destination system. ALE used a Transactional RFC port, which transfers data in memory buffers.
    RFC Destination:
    The RFC destination is a logical name used to define the characteristics of a communication link to a remote system on which a function needs to be executed.
    Partner Profile:
    A partner profile specifies the components used in an outbound process(logical name of the remote SAP system, IDoc Type, message type, TRFC port), an IDoc’s packet size, the mode in which the process sends an IDoc (batch versus immediate), and the person to be notified in case of error.
    Service Programs and Configuration Tables:
    The outbound process, being asynchronous, is essentially a sequence of several processes that work together. SAP provides service programs and configuration tables to link these programs and provide customizing options for an outbound process.
    Creation of IDoc:
    Basic Type:
    Basic IDoc type defines the structure and format of the business document that is to be exchanged between two systems.
    Segments:
    Segments form the basic building blocks of an IDoc type and are used to store the actual datta. A segment type is the name of a segment and is independent of the SAP elease. A segment definition is the release-specific name of a segment.
    Steps in creating Segments:
    T.Code WE31
    Enter the name for your segment type and click on the create icon.
    Type the Short text.
    Enter the variable names and data elements.
    Save and Go back.
    Go to Edit -> Set Release.
    Repeat the steps to create more segments.
    IDOC TYPE:
    Business data is exchanged with an external system using the IDoc Interface.
    IDoc types (Special Structures) An IDoc type is defined through its permitted segments. Segments can be dependent on each other (parent and child segments). The IDoc interface can check for each IDoc whether thhe segments contained are compatible with thhe definitiion of its type. This systax check is activated or deactivated in the Partner Profiles.
    Steps in creating IDoc Type:
    T.Code WE30 to create IDoc Type.
    Enter the Object Name, Select Basic Type and click Create Icon
    Select the create new option and enter a description for your basic IDOC type and press enter
    Select the IDoc name and click Create icon
    The system prompts us to enter a segment type and its attributes
    Choose the appropriate values and press enter
    The system transfers the name of the segment type to the IDoc editor.
    Follow these steps to add more number of segments to Parent or as Parent-child relation.
    Save it and go back.
    Go to Edit -> Set Release.
    Message Type:
    Steps in Creating Message Type:
    T.Code WE81.
    change the details from Display mode to Change mode
    After selection, the system will give this message "The table is cross client (See help for further info)". Press enter.
    Click New Entries to create new Message Type.
    Fill details
    Save it and go back.
    Assign Message Type to IDoc Type:
    T.Code WE82
    Change the details from Display mode to change mode.
    After selection, the system will give this message "The table is cross client (See help for further info)". Press enter.
    Click New Entries to create new Message Type.
    Fill details
    Save it and go back.
    <REMOVED BY MODERATOR>
    Edited by: Alvaro Tejada Galindo on Feb 6, 2008 5:10 PM

  • ALE change pointer error - master data

    Hi friends,
    While loading master data (customer,material and order number) all delta,we faced the error "ALE change pointers are not set correctly".
    In the discussions posted earlier,it was said that the change pointer in BD61 activation would solve the issue.
    If i do that now,whether my other delta loads will be affected or it doesnt have any relation to my other transactional deltas.Pls clarify me.
    Also explain me the reason fot this error.
    Thanks & Regards
    Ragu

    thanks ajay for your input
    regards
    ragu

  • What is change pointer in ALE ?

    Dear Guru,
    1. What is change pointer in ALE and how to configure it ?
           The process of configure please guide me !
    Tanks and Regards,
    Subash.

    Hi,
    Change pointers are R/3 objects that mark changes to SAP master data. Change pointers are managed by mechanisms in a Shared Master Data (SMD) tool and are based on Change Document (CD) objects. CD objects record the changes occurring to master data at a field level. These changes are stored in tables CDHDR (header table) and CDPOS (detail table). ALE configuration provides a link between CD objects and change pointers. Internal mechanisms update tables BDCP and BDCPS, which host the change pointers. While CD objects are application-data-specific, the processing status of change pointers is message-type-specific. Also, the ALE change pointers are activated first at a general level and then at the message-type level.
    ALE provides powerful capabilities to capture changes occurring to master data and to distribute them via the IDOC interface. This feature can be used to keep two or more systems synchronized with respect to master data.
    Steps to configure change Pointers:
    1.Activate the change pointers globally(BD61)
    2.Activate the change pointers for individual message types(BD50)
    3.Schedule the program RBDMIDOC to run periodically on the sending system.
    To Delete Change pointers use transaction BD22 and the standard program is RBDCPCLR
    Remember You can see a check box in Further characteristics tab of the data element ( se11>enter data element>Further characteristics tab) for change document.
    This check box is to bo checked to trigger change pointers.
    please check out the following link for more information it might help you
    http://help.sap.com/saphelp_nw04/helpdata/en/12/83e03c19758e71e10000000a114084/content.htm
    http://help.sap.com/saphelp_470/helpdata/en/dc/eb683c00e8a646e10000000a11402f/frameset.htm
    Regards,
    Satish

  • How to filter change pointer in ALE

    hi,
    i am using message type DEBCOR for transferting customers from client A to B with ALE.
    and i am using the 'change pointer' to transfer changed/added customers.
    BUT: how can i tell the system that only changes for customers with a specific number range (1000-1999) should
    trigger an idoc ? now EVERY change is triggered, i don't want that !
    reg, Martin

    You can filter change pointers using BADI 'BDCP_BEFORE_WRITE'.

  • ALE/Change Pointer Configuration for ZSEGMENTS

    Hello all,
    I have been searching for a few days now trying to obtain my requirement with extending of an idoc.  I am working with the following:
    Message Type: HRMD_A
    BASIC Type: HRMD_A06
    Extension: ZHRMDA06
    I extended the idoc because I wanted to include 2 extra infotypes which are not on that idoc.  Infotypes 77 and 709.
    Here is what I have completed so far.
    WE30...Created ZSEGMENTS to include below.
    WE31...Extended the HRMD_A idoc to include the ZSEGMENTS defined below.
    WE82...Updated the output types and assignments to idoc.
    BD61...Activate Change Pointers
    BD50...Activated change pointer for HRMD_A.
    I change the address field in infotype 0006. 
    Run the BD21...idoc is generated with the changes to address, everything looks good.
    Do the same thing for the ethnic origin on infotype 77, no idoc is generated. 
    I turned on logging onto table PA0077.
    I am evaluating the change logs via SCU3, and I am seeing my changes on the field.
    What I have tried...
    I have tried creating a object in t-code SCDO (ZTEST)
    I have associated  ZTEST with table/field PA0077-RACKY.
    Tried running BD21...No iDoc generated.
    I have been researching for a few days and it feels that this should be able to be done through configuration and not custom coding.  Am I wrong to think that?
    Has anyone ever did anything like this before which they can point to documentation or even the appropriate search criteria on the SCN forums.
    Thanks in advance for your help!
    Jason

    Hi Jason,
    I believe you have to enter the fields that trigger the changing pointer in tcode BD52. In my case these are the fields for BOM:
    Regards,
    Custodio

  • ALE change pointer

    Hi all ,
    Can anyone suggest any link where i get step by step / complete procedure to create change documnet and change pointer to trigger IDOC for changed master data?
    thanks & regards
    Sheetal

    Hi,
    Please go through SAP Technical sites for details. You can check this [Link Also.|http://wiki.sdn.sap.com/wiki/display/ABAP/ALEChangePointers]
    [Check This also|http://articles.techrepublic.com.com/5100-10878_11-1048973.html]
    thanks,
    Abhijit
    Edited by: Abhijit Mandal on Feb 15, 2010 6:54 PM

  • Transaction  for using change pointer technique in ALE -IDOCS

    Hi,
    please let me know the following points.
    1: while using change pointer technique , any change in the sale order(any field ) will trigger IDOC or only specific field change. Or do we have to specify field on which we want to trigger IDOC?
    2:When IDOC gets genrated from change pointer , does it contain complete sales order or only change fields?
    3:Do we have Native format of IDOC in 4.6c ?? XML format??
    Please reply soon.

    Hi,
    For the changes to be carried over by change pointers, the steps followed are,
    If it's gonna be the vendor master for which change pointers needs to be activated,
    - goto SALE transaction ->Modelling and Implementing business processes ->Replication of Modified data -> Activate Change pointers - generally / for message types.... or as said in the earlier post, alternatively BD61/BD50.
    - Schedule a background job for program RBDMDIOC providing the message type(CREMAS) for which the change pointers needs to be processed.
    - Now for any changes made to the vendor via transaction XK02, automatically CREMAS IDocs would get generated with the IDoc carrying the changed fields in it. You would also be able to find the number master and communication IDocs generated from the joblog of the scheduled RBDMIDOC background job.
    ~ Bineah.

  • Query related to filter group on matnr created in ALE distribution model

    Hi All,
    I have query related to filter group on matnr created in ALE distribution model.
    I have created a filter group on matnr in ALE distribution model and put the value E*  ( purpose is that all the material number started with E should be triggered in case of any changes in the material).But it is not working.
    <b>Can anybody suggest the solution for this i.e how to capture E* value for the material master changes and should trigger idoc using change pointer using BD21.</b>
    Thanks & Regards
    Prabhat

    Unfortunately, you cannot filter using wildcards or exclusions.  You have to explicitly list each allowed value in its entirety.
    In my opinion, the simplest solution would be to copy function MASTERIDOC_CREATE_SMD_MATMAS, modify it to handle your custom filtering and update the message type entry in transaction BD60.

  • Activate change pointer for a new screen field in MM42/41

    Hi,
      I created a new screen field for Article master(MM41/42/43) under basic data. If there are changes made to this new field how will the system create a corresponding IDOC? does this have something to do with the change pointer thing?
    Thanks,
    Jeff

    Hi Jeffrey,
    first of all got transaction SALE :
    ALE
    -> Modeeling and Implementing
    -> Master Data Distribution
    -> Replication
    -> Activate Change Pointer generally
    Check if Changepointers are generally on.
    Then goto BD50 and activate change pointers fpr message type.
    Finally goto BD52 and check if your field is "watched".
    After that you can generate idocs from BD21.
    Hope it helps.

  • Message type US for ALE distribution

    I want to create an outbound IDOC using ALE distribution.
    I have to assign Partner type as 'US' - user. Can anyone give me some input. I got the error when trying to do the same
    " No partner profiles (message control) maintained                          
    Message no.                             B1127                                                    Diagnosis                                                     No IDOC partner profiles have been created for the message control for
         for application EF, condition key ZNBR and change message '' with     
         partner type 'LS' and partner role '  '.                              
    Procedure                                                     Please create the partner profiles for the logical system that should 
         contain the IDOC. You can either generate them from the ALE model or  
         create them manually.                                                 
    Step by step will be helpfull.
    Thanks

    Hi Preethi,
    You can use this program <b>RBDCUS15</b> to generate outbound partner profile.
    Also you use distribution model (t/code BD64) as well.
    Hope this will help.
    Regards,
    Ferry Lianto
    Please reward points if helpful.

  • ALE distribution of HR master data to CRM - subtype CELL and MAIL

    Hello,
    Overview/Introduction:
    we are using the ALE distribution of HR master data to CRM. The distribution has already been set up and it is running. We know that the infotype communication (0105) is especially distributing the subtypes 0010 (e-Mail) and 0020 (telephone number). This e-Mail address and the telephone number are stored in the business partner in the CRM system.
    For this infotype 0105 there are also the subtypes CELL (cell phone) and MAIL (e-Mail address). Unfortunately this cell phone number and the mail address (from subtype MAIL) are not stored at the business partner in CRM.
    Our request is on the one hand to store the data from subtype CELL into the field mobile number of the business partner. And on the other hand we want to store the e-mail address of subtype MAIL at the business partner instead of subtype 0010.
    For some reason it seems that these requests canu2019t be setup within SAP standard.
    So we found SAP note 758426 which suggests to use the BAdI HRALEX_INBOUND and the report RH_ENHANCE_BP_TEMPLATE.
    Problem:
    Now the problem is that the BAdI does not get called! The BAdI is active! We tried to set break points -> unfortunately did not stop! And we also implemented an endless loop in the BAdI -> even with this the system did not u2018stopu2019!?
    Any ideas?
    Thank you,
    Roman

    Hi,
    First you need to create a distribution model using transaction BD64 : Edit > Model View > create.
    Then you will need to maintain fields for description and technical name. In partner box you need to enter the source system (HR) and the target system (FI) in the second field. Then you need to assign a message type and filter settings if you need it. You need to create this distribution model in source system (HR).
    After, still in BD64, go to environment > change partner profile or transaction WE20
    Select your target system and enter the corresponding message type ( HRMD_A or HRMD_ABA depends on your scenario) with the correct customizing (receiver port, packet size, idoc type, syntax check and output mode).
    Then please do the same things in your source system using WE20 for your source system and define your inbound parameters (Process code HRMD, processing by function module : use trigger immediately if it is not a production system or else trigger by background program and this case you will need to run report RBDAPP01 to process Idocs).
    Once done, then go back to your model view in your source system (BD64) and go to Environment > generate partner profiles. Then please go to Edit > Model View > distribute
    After all these settings done, it should work.
    Please also check out documentation :
    http://help.sap.com/erp2005_ehp_04/helpdata/EN/82/933b90aa9e11d6b28800508b5d5211/frameset.htm
    Best Regards
    Christine

  • What is the use of change pointer technique in IDOC

    hi
    could anybody suggest me
    what is the use of change pointer technique and how to use it
    thank you
    kalyan.

    Change pointers are used for changes to the master data objects are flagged for distribution by SMD Tool.i.e.shared Master Data.
    You need change pointers to distribute changes with the ALE SMD tool. If you do not use this tool, you do not need to write change pointers.
    You can deactivate change pointers and activate them again with the transaction BD61
    The SMD tool is connected to the change document interface. If the master data changes are to be distributed, the application writes a change document. The contents of this are passed to the SMD tool. The tool writes change pointers, reads the application data and creates the master IDoc.
    The master IDoc is then passed to the ALE layer, which sends it to all interested systems.
    The change pointer tables (BDCP und BDCPS) should be as small as possible. Use as few change pointers as possible and delete change pointers which you no longer need.
    You can increase the rate of processing by using the Analyze Change Pointer and Reorganize Change Pointer functions.

Maybe you are looking for