Develop a data extract program

Develop a data extract program to get the class and characteristics for a material.
Edited by: suresh babu on Oct 7, 2010 7:13 AM
Moderator message: 3.2.1...Thread locked. This post makes no sense whatsoever.
Edited by: Neil Gardiner on Oct 7, 2010 4:16 PM

Which LiveCycle product are you thinking of? I don't think LiveCycle
Reader Extensions can help you as it does not enable database
functionality in Reader.
Aandi Inston

Similar Messages

  • 'Error 8 occurred when starting the data extraction program'

    Hello Experts,
    I am trying to pull master data (Full upload) for a attribute. I am getting an error on BW side i.e. 'The error occurred in Service API .'
    So I checked in Source system and found that the an IDOC processing failure has occurred. The failure shows 'Error 8 occurred when starting the data extraction program'.
    But when I check the extractor through RSA3, it looks fine.
    Can someone inform what might be the reason of the failure for IDOC processing and how can this be avoided in future. Because the same problem kept occurring later as well.
    Thanks
    Regards,
    KP

    Hi,
    Chk the idocs from SM58 of source system are processing fine into ur target system(BI system)...?
    Chk thru Sm58 and give all * and target destination as ur BI system and execute and chk any entries pending there?
    rgds,
    Edited by: Krishna Rao on May 6, 2009 3:22 PM

  • Problem during data extraction program (tran - RSA3) in SC system

    Hi Experts,
    We are extracting data from one of the data source (9ALS_SBC) through trans RSA3. We are using active version 000 for the same.
    but, the transaction is showing error below:
    Error when generating program
    Message no. /SAPAPO/TSM141
    Diagnosis
    Generated programs are programs that are generated based on individual data objects, such as planning object structures, planniung areas and InfoCubes. These programs are then executed in the transaction. An error occurred during the generation of such a program.
    There are two possible causes:
    The template has been corrupted.
    The object that the template uses to generate the program contains inconsistencies, for instnace an InfopCube has not been activated.
    could someone tell me how to solve this error?
    i hv corrected all the inconsistencies but still it is showing same error!
    thanks in advance for this help!
    with best rgds/
    Jay

    Dear Jay,
    the error can have several reasons, it depends on your business scenario and system settings.
    I send you some possible reasons and solutions:
    1.
    The problem can be that the technical datasource name has changed inside the planning area. The planning area has other extract structure assigned as the datasource.
    This could have happened due to a planning area or datasource transport.
    The best way to repair this is to create a dummy-datasource for the planning area with transaction /N/SAPAPO/SDP_EXTR. This will update the relevant tables with the new datasource structure.
    Please check if the other datasources will work correctly as well. If not you may create similar dummy-datasources for the other aggregates as well.
    Please do not forget to delete the dummy-datasources as well in  /N/SAPAPO/SDP_EXTR.
    2.
    You can try to re-generate the data source at transaction /SAPAPO/SDP_EXTR and recheck the issue.                   
    3.
    Run /sapapo/ts_pstru_gen via transaction se38.         
    In the selection, enter the Planning Object Structure used and select  'Planning area extractor' and set the flags on the 2 bottom checkboxes 'Reset generation time stamp' and 'Generate'. 
    4.
    Maybe the extract structure which is assigned to planning area doesn't exist in your system. This could  happend at the time of transport.             
    Please refer to following content from note 549184:                                                                               
    =======================================================================
    Q4: Why could I have extraction problem after transport of DataSource? 
    A4: DataSources for DP/SNP planning areas depend directly on the                                                                               
    structure of the planning areas. That's why the planning area MUST                                                                               
    ALWAYS be transported with or before the DataSource.                   
    ========================================================================
    To solve this inconsistency please try the below:                      
    -Please reactivate the datasoure on Planning Area.                     
    And activate all active transfer structures for a source system with  RS_TRANSTRU_ACTIVATE_ALL programme on se38 transaction.                
    I hope these proposals could solve the error.
    Regards,
    Tibor

  • Need data extract and load program

    hi
    where i can find all the standard data extract programs and standard load programs. Pls thisis urgent.
    thankyou

    Thankyou
    can i get a list of the extract programs and dataload programs? SAP provides programs for extracting data for material master, customer, vendor, purchase order , sales order ? It also provides std programs for data load rite? where can i find the list. i need to prepare a document with the list.
    Heng

  • How to add new fields to a data extract

    The following data extract program generates an output file which is displayed using a publisher template as a check format report.
    Oracle Payments Funds Disbursement Payment Instruction Extract 1.0
    How would I add new fields to the generated file? In other words what is the procedure to add new fields to the data extract?
    Thanks

    Do anyone pls advise how to customize the payment extraction program? We also have the similar requirement to extract extra fields to format a payment file.

  • Error 8 when starting the extraction program (BI7.x)

    I am receiving the following message when loading from the ODS to the data targets:
    Error 8 when starting the extraction program
    Message no. R3019
    Diagnosis
    Error 8 occurred when starting the data extraction program.
    System response
    The data extraction is terminated.
    Procedure
    Check for relevant OSS Notes, or create a problem message of your own.
    I have searched the forums and OSS, and can't find anything that matches my situation exactly.  I was originally getting an error message that the infosource (80FIA_DS11) didn't exist in the source system.  I restored the BIP client and all transfer structures were reactivated.  Now when I try to load, I get this error 8.  Has anyone experienced this issue?
    Thanks,
    Pam

    Josko,
    I am also using BI 7.x and had the problem loading from DSO to Infocube.  What are the entries in table ROIDCPRMS?  What is the host name displayed when you run transaction SM51 in the BI system?
    Pam

  • Error  8 when startingthe  extraction program

    Error                                                   8 when startingthe extraction program
    Hi Friends,can anyone tell what the error is:
    Message no. R3019
    Diagnosis
    Error                                                   8 occurred whenstarting the data extraction program.
    System response
    The data extraction is terminated.
    Procedure
    Check for relevant OSS Notes, or create a problem message of your own.

    It may be due to non background user trying to run the job in background.
    You might want to change the user type for the user id used to run th eextraction.
    you may use su01, and change the user type in tab 'logon data', set the type to 'system' or 'background'. ask basis help if you have no authorization to do so.

  • Logical Data Extract from SAP/Oracle

    Hi,
    We have been asked by our client to develop a data extraction tool for SAP/Oracle. For example, we would need to extract user/employee information.
    What is the best way to go about this? Ideally we would like to allow the user to connect to the DB and select the the data that we would like through a UI. The problem is that they will not know the schema and obviously too many tables to navigate through.
    Are there any legal concerns here?
    Regards,
    Justin

    Justin Todd wrote:
    Hi,
    >
    > We have been asked by our client to develop a data extraction tool for SAP/Oracle. For example, we would need to extract user/employee information.
    >
    > What is the best way to go about this? Ideally we would like to allow the user to connect to the DB and select the the data that we would like through a UI. The problem is that they will not know the schema and obviously too many tables to navigate through.
    >
    > Are there any legal concerns here?
    >
    > Regards,
    > Justin
    Hi Justin,
    Use BAPI functions, instead of directly accessing tables on the database.
    Best regards,
    Orkun Gedik

  • Simple data extraction reports by SAPu2019s SQL

    Hi,
    Can you please let me know how can I develop simple data extraction report using SAP's sql.
    Regards,
    Koushik

    HI,
    I have to do a PoC on Data Quality checks. In which there will be few reporting tables. One will be daily agreegate, one weely agreegate etc. Now I have to show those the data in form of reports. and Option is also required to drill down and drill up for those reports.
    Please let me know if I am able to clarify my question or not.
    Regards,
    Koushik

  • Extract program to extract data from SAP into multiple worksheets of excel

    Hi , I am currently facing an issue.
    Extracting the data during data extraction, conversion into an excel and also into multiple worksheets withing a excel file.
    What is the function which can help me. Also how do you give refernce to multiple worksheets to be created withing a excel file (which is the destination)
    Any sample program extracting data from SAP tables into a excel with multiple worksheet will be of immense help
    Please respond. Appreciate it.
    Rgds
    Madhu

    Hi Madhu,
    Here is the program for creating the excel file and creating the multiple worksheets.
    *& Report  ZEXCEL_UPLOAD2
    REPORT  ZEXCEL_UPLOAD2.
    INCLUDE ole2incl.
    DATA: application TYPE ole2_object,
           workbook TYPE ole2_object,
           sheet TYPE ole2_object,
           cells TYPE ole2_object.
    CONSTANTS: row_max TYPE i VALUE 256.
    DATA index TYPE i.
    DATA: BEGIN OF itab1 OCCURS 0, first_name(10), END OF itab1.
    DATA: BEGIN OF itab2 OCCURS 0, last_name(10), END OF itab2.
    DATA: BEGIN OF itab3 OCCURS 0, formula(50), END OF itab3.
    *START-OF-SELECTION
    START-OF-SELECTION.
      APPEND: 'Peter' TO itab1, 'Ivanov' TO itab2,
                                  '=Sheet1!A1 & " " & Sheet2!A1' TO itab3,
                'John' TO itab1, 'Smith' TO itab2,
                                  '=Sheet1!A2 & " " & Sheet2!A2' TO itab3.
      CREATE OBJECT application 'excel.application'.
      SET PROPERTY OF application 'visible' = 0.
      CALL METHOD OF application 'Workbooks' = workbook.
      CALL METHOD OF workbook 'Add'.
    Create first Excel Sheet
      CALL METHOD OF application 'Worksheets' = sheet
                                   EXPORTING #1 = 1.
      CALL METHOD OF sheet 'Activate'.
      SET PROPERTY OF sheet 'Name' = 'Sheet1'.
      LOOP AT itab1.
        index = row_max * ( sy-tabix - 1 ) + 1. " 1 - column name
        CALL METHOD OF sheet 'Cells' = cells EXPORTING #1 = index.
        SET PROPERTY OF cells 'Value' = itab1-first_name.
      ENDLOOP.
    Create second Excel sheet
      CALL METHOD OF application 'Worksheets' = sheet
                                   EXPORTING #1 = 2.
      SET PROPERTY OF sheet 'Name' = 'Sheet2'.
      CALL METHOD OF sheet 'Activate'.
      LOOP AT itab2.
        index = row_max * ( sy-tabix - 1 ) + 1. " 1 - column name
        CALL METHOD OF sheet 'Cells' = cells EXPORTING #1 = index.
        SET PROPERTY OF cells 'Value' = itab2-last_name.
      ENDLOOP.
    Create third Excel sheet
      CALL METHOD OF application 'Worksheets' = sheet
                                   EXPORTING #1 = 3.
      SET PROPERTY OF sheet 'Name' = 'Sheet3'.
      CALL METHOD OF sheet 'Activate'.
      LOOP AT itab3.
        index = row_max * ( sy-tabix - 1 ) + 1. " 1 - column name
        CALL METHOD OF sheet 'Cells' = cells EXPORTING #1 = index.
        SET PROPERTY OF cells 'Formula' = itab3-formula.
        SET PROPERTY OF cells 'Value' = itab3-formula.
      ENDLOOP.
    Save excel speadsheet to particular filename
      CALL METHOD OF sheet 'SaveAs'
                      EXPORTING #1 = 'c:\temp\exceldoc1.xls'     "filename
                                #2 = 1.                          "fileFormat
    Closes excel window, data is lost if not saved
    SET PROPERTY OF application 'visible' = 0.
    **Quick guide to some of the OLE statements for OLE processing in this program as well as a few other ones.
    Save Excel speadsheet to particular filename
    CALL METHOD OF sheet 'SaveAs'
                    EXPORTING #1 = 'C:\Users\dprasad\Desktop\excel_sheet.xls'     "filename
                              #2 = 1.                          "fileFormat
    Save Excel document
    CALL METHOD OF sheet 'SAVE'.
    Quits out of Excel document
    CALL METHOD OF sheet 'QUIT'.
    Closes visible Excel window, data is lost if not saved
    SET PROPERTY OF application 'visible' = 0.

  • Standard SAP program name for the data extraction

    Please tell me the stadard SAP program  for the data extraction for Material, Vendor and Customer.

    you might want to explore tx. SXDA.

  • Use of Catalog data Extract concurrent programs

    Hi All,
    1. What is the use of Catalog Data Extract - Classifications, Catalog Data Extract - Items Concurrent Programs in Purchasing?
    2. To load the items from inventory to iprocurement whether the above two concurrents are must?
    Kindly help me in giving a clear idea about it.
    Thanks in advance.
    Regards,
    Simbu...

    Hi Simbu,
    The mentioned program works only in 11i, as R12 follows different mechanism.
    Yes, to load the items and categories to iProcurement mentioned programs are must in 11i.
    Need to make sure, item got a list price in the purchasing tab and purchasing category is published to iProcurement.
    You should run Catalog Data Extract - Classifications prior to running Catalog Data Extract - Items program.
    Thanks,
    PS.

  • Flat file issue in extract program

    Hi All
    I have developed an extract program, which downloads the data from SAP and dump it in a flat file, in desired format.
    Flat file contains various rows.
    In one row, i want to keep 80 charecter length blank at the end.
    Ex:
    HDR2345 c 20060125 0r42z1005.5USD
    Now after "USD", i want to keep 80 char length as Blank spaces.
    If i code it as  v_record+33(80) = ' '.. it won't work out...
    Please suggest me...
    Regards
    Pavan

    Hi Pavan,
    Please try this code.
    DATA: L_SPACE TYPE X VALUE '20'.
    MOVE L_SPACE TO V_RECORD+33(80)
    OR
    MOVE L_SPACE TO V_RECORD+79(80).
    This should work.
    Regards,
    Ferry Lianto

  • Need help for writing extract program

    hi
    i need help for writing extract program to retriew data from legacy system.
    i already developed bdc programs for me31k and me21.
    my requirement is to write extract program s for those t.codes.
    to retriew data from legacy system and stored in flat file.

    i need help with a java program. it is a program that allows the user to enter a student's GPA, number of extracurricular activities, and number of service activities. The user can not enter a gpa above 4.0 or below 0. The user can not enter a negative number for the number of both activities. If the student meets the following criteria: 1) GPA of 3.8 or above and at least one extracurricular activity and one service activity, 2) GPA below 3.8 but at least 3.4 and a total of at least three extracurricular and service activities, 3) GPA below 3.4 but at least 3.0 and at least two extracurricular activities and three service activities, the message "Scholarship candidate" should display. If the student does not meet the criteria above, then the message"not a candidate" should display. Can you help me, please?
    You haven't posted ANY 'java program' for us to help with.
    The forum is NOT a coding service. It is to help you with YOUR code.
    Post the code you have written and SHOW us (don't just tell us) how you compile it and execute it and the results you get. Then we can help you with any problems you are are having.
    If you need help understanding just what the program should be doing you need to ask your instructor to clarify the assignment.

  • Extraction program for EH&S (EH&S to XI scenario)

    Dear Experts,
    I am from the XI background and am new to EH&S. I would like to know whether there exists an extraction program to extract substance data from EH&S(ECC) and send it to XI. If yes then what is it? The EH&S team here doesn't know of any kind. They have only used Change pointers to extract data from one client to the another.
    Please help.
    Thanks,
    Merrilly

    Hello,
    How to set up ALE for substances is described in the IMG / Customizing for EH&S.
    For EH&S 2.7B on R/3 4.6C this is located under:
    Environment, Health & Safety -> Product Safety -> Interfaces -> EH&S Application Link Enabling (ALE) -> ALE for Specification Management.
    All necessary information should be found in 'Set up Distribution of Specification Data':
                                                                                    Set Up Distribution of Specification Data                                                                               
    In this IMG activity you set up the distribution of data on                   
         specifications (see also Information About the Concept in EH&S                
         Application Link Enabling (ALE)).                                                                               
    Requirements                                                                               
    1.  Setting the Active Code Page                                              
             To transfer the data using ALE, you must ensure that the active code      
             pages are the same in the receiving system and sending system as          
             follows:                                                                               
    -   You must select a code page for transfer (for example, SAP(ISO)       
                 code page 1100) that you set up on all SAP Systems that belong        
                 to your ALE distribution model.                                                                               
    -   In Customizing for Product Safety in the IMG activity Specify         
                 Environment Parameters using the environment parameter                
                 ALE_TRANSFER_LANGUAGE, you must specify a language of the             
                 previously selected code page as the transfer language in the         
                 sending system. This language controls which code page is active      
                 in the sending system during data transfer.                                                                               
    -   The RFC destinations of the target systems must be defined with       
                 the logon language that corresponds to the specified code page.                                                                               
    -   If data is to be transferred to different SAP(ISO) code pages,        
                 the operating systems of the sending and receiving systems must       
                 use the same character sets (ASCII or EBCDIC):                                                                               
    Sending system      Receiving system        Transfer possible             
             AS400               AS400                   Yes                           
             UNIX                UNIX                    Yes                           
             NT                  NT                      Yes                           
             NT                  UNIX                    Yes                           
             UNIX                NT                      Yes                           
             AS400               NT                      No                            
             AS400               UNIX                    No                            
             NT                  AS400                   No                            
             UNIX                AS400                   No                                                                               
    For more information, see:                                                                               
    -   The IMG activity Specify Environment Parameters                                                                               
    -   The IMG activity Set Up EH&S Native Language Support                                                                               
    -   The Product Safety documentation in the section EH&S Native           
                 Language Support                                                                               
    2.  Settings in Customizing for Distribution (ALE)                            
             You have made the necessary settings in Customizing for Distribution      
             (ALE).                                                                    
             Also maintain, for example, the sections                                                                               
    -   Basic Settings                                                                               
    -   Communication                                                                               
    3.  Settings in the Product Safety Component                                  
             Make sure that you have fulfilled the following prerequisites:                                                                               
    a)  Maintain the environment variables for serialization                    
                 Serialization collects the IDocs and makes sure that they are           
                 processed in the correct order. For more information, see               
                 section Serialized Distribution in Customizing for Distribution         
                 (ALE).                                                                               
    You specify the serialization number for the sending logical            
                 system in the IMG activity Specify Environment Parameters using         
                 the environment parameter ALE_SERIAL_ID. You specify one unique         
                 channel per logical system.                                                                               
    b)  Specify specifications to be distributed                                
                 If you want to distribute specification data manually, choose           
                 the specification directly from the hit list in specification           
                 management.                                                             
                 For automatic distribution, the specifications must appear in a         
                 set of hits that is assigned to the distribution method. If a           
                 set of hits has not been assigned, all of the specifications are        
                 distributed, providing that you have not defined filters.               
                 Apart from standard filters (see below), you can use the                
                 following customer exits to define further restrictions and             
                 filters:                                                                
                 - Specify Additional Table and Parameter Filter (1)                     
                 - Specify Additional Table and Parameter Filter (2)                                                                               
    c)  Ensure unique identification of specifications                          
                 The specification object must have a unique specification key.          
                 In the standard system, identification is supported by the              
                 specification key.                                                      
                 You can use the customer exit Develop Enhancement for                   
                 Identification to enhance the identification, for example, to           
                 link with one or more identifiers.                                                                               
    d)  Check authorizations                                                    
                 For manual distribution and automatic scheduling, you must have         
                 the read authorization for all the specification data to be             
                 distributed.                                                            
                 You also need the appropriate authorizations for inbound                
                 processing in the target system.                                                                               
    Activities                                                                               
    1.  Maintain the Distribution Model in Distribution (ALE) Customizing           
             In Customizing for Distribution, call the IMG activity Maintain             
             Distribution Model.                                                         
             For more information, see the documentation for the IMG activity.           
             To guarantee communication between systems during distribution, you         
             must make the following entries in the IMG activity Maintain                
             Distribution Model by choosing Add method:                                                                               
    Field             Entry                                                      
            Sender/client:    <Key for EH&S system>                                      
            Receiver/server:  <Key for target system>, for example,                      
                              Sales and Distribution system (SD), on which EH&S          
                              is installed.                                              
            Object name/interface:   Substance (substance(specification),                
         BUS1077)                                                                               
    Method:           SavRepMul (save replicated specifications)                                                                               
    Note:                                                                               
    Message type SUBMAS is supported.                                                                               
    You can set the following filters:                                                                               
    -   Reducing specifications by determining recipients:                               
                 You can reduce the specifications to be distributed by defining                  
                 the following filters:                                                           
                 - Specification type                                                             
                 - Authorization group                                                            
                 - Substance nature                                                               
                 - Set of hits (external key of group object)                                     
                 You can enter several values for a filter field. Individual                      
                 values are linked with OR, whereas the filter groups are linked                  
                 with AND.                                                                               
    If no filters are entered, all specifications are distributed.                                                                               
    -   Reducing specifications using 'IDENTHEADER' filtering                            
                 You define the identification category and identification type                   
                 whose specifications are to be distributed.                                                                               
    -   Reducing data using 'PROPHEADER' filtering                                       
                 You specify the value assignment types for which specification                   
                 data is to be distributed.                                                                               
    -   In Distribution (ALE) Customizing, you can use the IMG activity                  
                 Set Up Segment Filtering to exclude further tables from                          
                 distribution, for example:                                                       
                 - Material assignment                                                            
                 - Regulatory list assignment                                                     
                 - Reference specification assignment                                             
                 - Usage                                                                               
    - Assessment                                                                               
    Then in Distribution (ALE) Customizing, you maintain the IMG                         
             activity Generate Partner Profiles.                                                                               
    2.  Maintain Settings in the Sending and Recipient Systems                               
             The following tables must be maintained in the same way in the                       
             sending and recipient systems:                                                                               
    -   Value assignment type TCG01 and description TCG02 (system                        
                 tables)                                                                               
    -   Table of names for the DDIC objects TCG03 (system table)                                                                               
    -   Table of names for the child DDIC objects TCG04 (system table)                                                                               
    -   Specify Value Assignment Types                                                   
                 Value assignment type TCG11 and description TCG12                                
                 Value assignment type - specification type assignment TCG13                                                                               
    -   Identification category TCG21 and description TCG22 (system                      
                 tables)                                                                               
    -   Check Identification Types                                                       
                 Identification type TCG23 and description TCG24                                                                               
    -   Check Identification Listing                                                     
                 Identification listings TCG26 and description TCG27                              
                 Definition of identification listings TCG28                                                                               
    -   Assign Characteristic-Specific Identification                                    
                 Overriding identification list definitions TCG29                                                                               
    -   Specify Specification Types                                                      
                 Specification type TCG31 and description TCG32                                                                               
    -   Specify Authorization Groups                                                     
                 Authorization object TCG36 and description TCG37                                                                               
    -   Specify Types for User-Defined Texts                                  
                Value assignment text type TCG41 and description TCG42                                                                               
    -   Create Sources                                                        
                Source TCG46                                                                               
    -   Specify Source Types                                                  
                Source type TCG47 and description TCG48                                                                               
    -   Set Up Property Trees                                                 
                Property tree TCG51 and description TCG52                             
                Property tree - value assignment type assignment TCG53                                                                               
    -   Specify Data Origin                                                   
                Data origin TCG56                                                                               
    -   Specify Phrase Libraries and Phrase Groups                            
                Phrase library TCG61 and description TCG62                            
                Phrase group TCG63 and description TCG64                                                                               
    -   Specify Language Selection                                            
                Phrase language (languages supported in phrase library) TCG65                                                                               
    -   Value assignment type class characteristic TCG66                      
                System table, filled using master data matchup                                                                               
    -   Check Value Assignments                                               
                Value assignment assessment TCG71 and description TCG72                                                                               
    -   Specify Component Types for Compositions                              
                Component type TCG76 and description                                                                               
    -   Specify Regulatory Lists                                              
                Regulatory list TCG81 and description TCG82                                                                               
    -   Specify Ratings                                                       
                Value assignment rating TCG86 and description TCG87                                                                               
    -   Specify Validity Areas                                                
                Validity area TCG91 and description TCG92                                                                               
    -   Specify Usage Profiles                                                
                Usage profile TCG96 and description TCG97                             
                Usage profile - rating - validity area assignment TCG98                                                                               
    -   Specify Exchange Profiles                                             
                Exchange profile TCGC3 and description TCGC4                                                                               
    -   Specify Environment Parameters                                        
                General environment parameters TCGENV                                                                               
    -   Protect Characteristics Within Namespace                              
                Namespaces for characteristics TCGK1                                                                               
    -   Manage User Exits                                                     
                User exit parameters from user exit management TCGUEEN                
                User exits from user exit management with function module             
                assignment TCGUEFU                                                    
                Language-dependent user exit names from user exit management          
                TCGUENA                                                               
                User exit categories from user exit management TCGUETY                                                                               
    3.  Check Master Data to Be Distributed                                                                               
    For the ALE process, the following master data must be distributed      
             to all the relevant systems:                                                                               
    -   Phrases                                                                               
    -   Phrase sets (for systems, in which data is created)                                                                               
    -   Classes and characteristics                                                                               
    -   Materials (all material data that is required for                   
                 material-specification assignment)                                                                               
    -   Change numbers                                                      
             Note:                                                                               
    Classes and characteristics are distributed via export and          
                 import. The help texts and phrase sets are also transferred to      
                 other systems along with the classes and characteristics.           
                 Classes and characteristics can also be distributed using ALE.      
             Note:                                                                   
             The required data providers must have been created manually in the      
             Product Safety component under Tools -> Edit addresses -> Data          
             provider before data is distributed in the recipient system. The        
             data providers must be unique with regard to the following three        
             fields:                                                                 
             - Name (NAME1)                                                          
             - City  (CITY1)                                                         
             - Country (COUNTRY)                                                     
             During distribution, the data providers of the specification to be      
             sent are read and also distributed. When writing to the recipient       
             system, the SAP System determines the corresponding address number      
             for the data provider in the recipient system by comparing the three    
             fields Name, City and Country for the address numbers that were         
             sent, and then transfers this address number that was determined to     
             the Data provider field (OWNID).                                                                               
    You can determine the address number of the data provider in            
             Customizing for Product Safety in the IMG activity Specify              
             Authorization Groups.                                                   
             To do this, call the input help for the Data prov. field in the IMG     
             activity. You will find the value you require in the Addr. no.          
             field.                                                                  
             The address number is not displayed in address management in the        
             Product Safety component.                                                                               
    4.  Check Control Data to Be Distributed                                    
             See above: "Maintain Settings in the Sending and Recipient Systems"                                                                               
    5.  Check Consistency                                                       
             A consistency check can be performed for the settings in the            
             distribution model and the partner profiles.                            
             To do this, in Distribution (ALE) Customizing, call the IMG activity    
             Check Partner Profiles and Model Settings.                              
             The distribution model must have been distributed and the partner       
             profiles must have been maintained in all relevant systems.                                                                               
    6.  Error Handling                                                          
             As soon as an error occurs when an IDoc is processed, the whole IDoc    
             is not updated. You can use a workflow to correct errors. IDocs can     
             be modified manually (you can change the identifier, for example)       
             and updated retrospectively.                                                                               
    General Procedure                                                                               
    1.  In a customer reference model you define which data is to be                  
             distributed to which system. You use sets of hits to define the               
             specifications that are to be distributed and specify filters with            
             regard to specifications or specification data as required.                                                                               
    2.  The first time you distribute specifications to the target systems,           
             you do it manually, using the method REPLICATE according to the               
             distribution model. Serialization must be switched off.                                                                               
    3.  You activate serialization and switch on delta distribution as                
             follows:                                                                               
    Activating Serialization                                                                               
    a)  In Customizing for Product Safety, in the IMG activity Specify            
                 Environment Parameters specify the channel for the parameter              
                 ALE_SERIAL_ID through which the ALE data is to be distributed.                                                                               
    b)  In Customizing for Distribution (ALE) choose Set Up Data                  
                 Distribution -> Serialized Distribution -> Serialized                     
                 Distribution Using Object Types -> Activate Inbound Object Types          
                 and specify the inbound object types for which serialization is           
                 to be performed.                                                                               
    c)  Schedule a job (RBDAPP01) that posts the IDocs that arrive in             
                 series in the recipient system.                                                                               
    Switching On Delta Distribution                                                                               
    a)  Activating change pointers for a message type                             
                 Changes to master data objects are logged in the form of change           
                 pointers during master data distribution. To activate the                 
                 writing of change pointers, in Customizing for Distribution               
                 (ALE) choose Set Up Data Distribution -> Master Data                      
                 Distribution -> Activating Change Pointers -> Activate Change             
                 Pointers for Message Types and set the Active indicator for the           
                 message type for which you want to realize delta distribution.                                                                               
    b)  Activating change pointers for each field                                 
                 From the SAP R/3 screen, choose Tools -> Business Framework ->            
                 ALE -> Development -> Master data -> Activate change pointer for          
                 each field and enter the message type for which you want to               
                 determine fields, for which the SAP System writes change                  
                 pointers. All relevant data fields are delivered. If necessary,           
                 adjust the table to your requirements.                                                                               
    c)  Activating change pointers generally                                      
                 To generally activate master data distribution using change               
                 pointers, in Customizing for Distribution (ALE), choose Set Up            
                 Data Distribution -> Master Data Distribution -> Activating               
                 Change Pointers -> Activate Change Pointers (generally) and set           
                 the active indicator.                                                                               
    d)  Scheduling delta distribution as a job                                    
                 You can perform delta distribution manually or schedule it as a           
                 job.                                                                               
    To perform delta distribution manually, from the SAP R/3 screen           
                 choose Tools -> Business Framework -> ALE -> Administration ->            
                 Periodic processing -> Process change pointers and enter the              
                 message type you require and choose Execute.                              
                 To schedule delta distribution as a job, in Customizing for               
                 Distribution (ALE) choose Scheduling Periodic Processing ->               
                 Scheduling Generation of IDocs from Change Pointers -> Define                                                                               
    Variants and create a variant. Then in the IMG activity Schedule       
                 Jobs create a job (RBDMIDOC) for the variant. You can set the          
                 time at which distribution is performed, for example,                  
                 immediately after a change or periodically.                                                                               
    The following applies when transferring data:                                                                               
    o   If a specification is not found in the target system, it is created        
             with the specification key that is transferred.                                                                               
    o   If a specification is available in the target system, its data is          
             updated.                                                                               
    o   When complete specification data is being sent, the specification is       
             locked and no changes can be made to it. If this lock cannot be set,       
             the specification cannot be processed. The IDoc is given the status        
             with error and a work item is created.                                                                               
    Note:                                                                               
    In manual distribution, change pointers are not taken into account.        
             In other words, the entire data record is distributed and delta            
             distribution is not performed.                                                                               
    Note on Executing the Report Program RC1PHDEL:                                 
             You must NOT schedule the report program RC1PHDEL (physical deletion       
             of data) to run in the source system or manually run it between            
             initial distribution and delta distribution, because the keys of           
             logically deleted data records can no longer be read and distributed       
             by delta distribution after the report program has been executed.          
             Before initial distribution you can execute the report in the source       
             system.                                                                    
             In the target system you can execute the report program independent        
             of distribution, as long as the target system does not serve as the        
             source system for further distribution.                                    
             If you want to execute the report program after the first delta            
             distribution, you must first make sure that all change pointers            
             created have been fully processed by the delta distribution and, if        
             possible, that all IDocs (intermediate documents) created were also        
             successfully posted in the target system. Otherwise, there is no           
             guarantee that the source and target systems will be consistent.                                                                               
    Example                                                                    
             The report program RC1PHDEL was executed in the source system so           
             that the deletions of an identifier of the identification category         
             NUM and the identification type CAS and a phrase item were not             
             distributed.                                                               
             Then an identifier of the identification category NUM and                  
             identification type CAS with the identical value that was previously       
             deleted and a phrase item for the same phrase in the previously            
             deleted language are created. The following errors occur in the            
             subsequent delta distribution:                                                                               
    -   The identifier cannot be created because the NUM-CAS value             
                 already exists. The IDoc cannot therefore be posted.                   
                 Notes:                                                                               
    If you attempt to create duplicate identifiers in the dialog,          
                 the same error messages will be displayed as when posting using        
                 ALE.                                                                               
    If the NUM-CAS identifier was not identical to the previously          
                 deleted identifier, the IDoc would be posted successfully and          
                 the identifier would be created in addition.                                                                               
    -   The phrase item cannot be created, because only one phrase item        
                 is permitted for a phrase in each language. The old phrase item                                                                               
    must be deleted first before the IDoc can be posted.                                                                               
    The next section describes the solution for similar error cases. You    
             should, however, try to avoid the need for this procedure by not        
             executing the report program.                                                                               
    e)  In the target system in the dialog, delete the EH&S objects         
                 (specifications, phrases, reports), for which you have already      
                 run delta distribution. These objects are internally marked with    
                 a deletion indicator.                                               
                 Caution:                                                            
                 When you distribute reports, the report bodies are distributed.     
                 To delete these, you simply need to delete all report reference     
                 specifications. Deleting report bodies is not necessary and also    
                 not possible. If you cannot delete objects (such as                 
                 specifications or phrases) owing to their where-used-list, it is    
                 sufficient to delete the 'deleted' detail data in the target        
                 system that has not been distributed. This may require more         
                 processing effort than if you delete all the objects using the      
                 hit list and distribute all the data again in full.                                                                               
    f)  In the target system, set the Set missing deletion indicators       
                 and Delete physically indicators in the RC1PHDEL report program     
                 and execute the report program in the target system.                
                 This triggers the following actions:                                
                 - The deletion indicator is set in the tables that depend on the    
                 header data to be deleted.                                          
                 - All data with deletion indicators is deleted physically.          
                 - The corresponding entries in the table ESTALE (conversion         
                 table for ALE) are deleted physically.                                                                               
    g)  Deactivate the active serialization and the writing of change       
                 pointers and start initial distribution of all objects again.                                                                               
    h)  You can now activate the writing of change pointers and             
                 serialization again and use delta distribution as usual.            
             Note:                                                                   
             If you still have IDocs in the source system or target system that      
             were created before the deletion in your target system, but were not    
             distributed or posted, ignore these IDocs and do not post them. You     
             can do this by changing the channel before repeating the initial        
             distribution by using the environment parameter ALE_SERIAL_ID (for      
             more information on the environment parameter, see the IMG activity     
             Set Up Distribution of Specification Data).                             
    Return ->                                                                       
         Application                                                                               
    Hope this helps
    Mark

Maybe you are looking for