Create new LSMW using Idoc for HR master Data

Hi Guys,
I was wondering id someone could help me. I have started developing an LSMW, of which I have already
created the Object. I have also created the Maintain attributes and I have supplied the Message Type, Basic Type and activated the IDOC inbound processing after providing the appropriate information.
The question I have is in the "Maintain source structure" do I need to create a structure for data records
and a structure for header?
Can I do a recording for transaction     -
"PA30" --->  update infotype 6
                                                       |
IDOC   -
> infotype 0,1,2,6
I have previously created HR LSMW using recording, but I have not used the IDOC facility and I'm not
sure of the differences.
Does anyone have any documentation.
Regards,
Frank

Dear Frank,
For Idoc method need to do setting first.
Creating  pratner profile,.....................etc.
then rest of the thing are same.
Best Regards,
Flavya

Similar Messages

  • How to use LSMW on CRM for bulk master data creation?

    Hello Experts,
    I need your help to able to use LSMW on CRM for bulk master data creation. Below is described my detailed requirement; -
    We have CRM 2007 integrated with SAP ISU (ECC6.0). As per business process all Business Master Data (BP details, Business Agreement details etc) and Technical Master Data (Connection Object, PoD etc.) is created in CRM and then it is replicated in ISU. We are going to start Assembly Test soon. Now we need to have all master data in place. Tool we want to use is LSMW.
    Now can you help me right from scratch on how to use LSMW for bulk master data creation in CRM?
    Please give me documents / links etc that is relevant.
    Regards,
    Rohit

    Hi,
    I have looked into your query.
    These are some information which might be useful to you.
    What is LSMW?
    Legacy System Migration Workbench or LSMW is SAP standard program that can be used to easily load / change master data or transactions in SAP without any programming at all. It can be used to upload data at cutover, such as: open orders, contracts, materials, vendors, stock on hand. It can also be used in a production system to make changes to existing data. Very limited authorization checks are available on the transaction, so the use of it must be very well controlled.
    One input file can be used to create all the views of the material master. For all the material types. Even if different views and fields are used for the different materials.
    Steps to take
    1. Create text file with data to be loaded
    2. Set up and run LSMW
    The following link will provide good information on LSMW Idoc method:
    [http://help.sap.com/saphelp_nw04/helpdata/en/ad/2d54a41d7011d2b42e006094b944c8/frameset.htm]
    I hope this helps.
    Regards,
    Venkat

  • Generate outbound idoc for Customer Master

    Hi Developers,
    I have requirement to generate outbound IDOC for Customer Master Data. I need to send customer master data through an Outbound IDOC. Can we generate an outbound DEBMAS06 idoc? Can someone help me finding a solution to this problem?
    Thanks in advance for helping.
    Regards,
    Gajendra

    Hi,
    If you have done all the required settings (logical system, partner profiles, distribution model), then either transaction BD10 / BD14 will help you generate the IDOC.
    If you want to send the idocs automatically, then you will to configure some program.
    Unlike transaction data, Master data IDOCS are not triggered immediately, you will have to do the required configuration in SPRO.
    Transaction SPRO
    SAP Customizing Implementation Guide -->
    SAP Web application Server --> Application Link Enabling --> Modeling and Implementing Business Processes -->
    Master Data distribution --> Replication of Modified Data --> Creating IDOCS from Change Pointers
    Take a look at this thread.
    Re: automatic Idoc outbound
    Regards,
    Ravi
    Note : Please mark the helpful answers
    Message was edited by: Ravikumar Allampallam

  • Working on LSMW using IDoc method for processing Open Sales Orders

    We are currently in middle of creation of a new instance of production for a different Business SBU. We are looking to utilise the LSMW tool using IDocs for uploading / transferring the open orders to the new box. If some one has worked on LSMW using IDocs, please get in touch and if you could share any documents on the process of utilising the LSMW tool using Idocs for any kind of conversions, it would be great. The following is a sample case.
    1. Each order will have multiple segments with different qualifiers under various segments.
    2. Multiple line items would be available under each order.
    Issues we are currently looking to solve :
    1. How do you manage to loop through the qualifiers during processing for the same segment.
    2. How do you prepare the tool to recognise the multiple line items of the same order.
    3. What kind of strategy needs to be used to create the input data file(s). Like, splitting the header and detail level information ?
    Note  : The volume of data we are looking at is somewhere around 40-60 thousand orders worldwide.
    Thanks in Advance.

    hI vikram check this link
    and reward points if helpful
    http://www.****************/Tutorials/LSMW/IDocMethod/IDocMethod1.htm
    http://www.jt77.com/system-dynamics/model-01395.html

  • Creating a BP in CRM through LSMW using IDOC

    I am trying to create a buss partner in crm through LSMW using IDOC:
    Message Type:  CRMXIF_PARTNER_SAVE_M
    Basic Type:       CRMXIF_PARTNER_SAVE_M02
    I get an error: "No update is defined for BP role 000000".
    I am also filling
    IDENTIFICATIONCATEGORY: CRM001
    IDENTIFICATIONNUMBER:     12345678
    However i get this error only if the external ID does not exist in table BUT0ID.
    otherwise if the external ID is present in table BUT0ID and the object task is "U"pdate, the BP is saved.
    Has anybody worked on BP creation using IDOCs? If yes please guide me.

    Hi,
    This Check Box is required for Archiving Business Partners from the System. You can have a full idea about the same from the link below [Archiving Business Partners|http://help.sap.com/saphelp_crm60/helpdata/en/52/cff837a9aae651e10000009b38f8cf/frameset.htm]
    Also have a look at the following [Introduction to Data Archiving (CA-ARC)|http://help.sap.com/saphelp_crm60/helpdata/en/8d/3e4c11462a11d189000000e8323d3a/frameset.htm]
    Hope this helps.
    Thanks,
    Samantak.

  • Requesting all to help me how to create lsmw using idoc method

    hi
    thanx for ur answer
    requesting every body in the forum to help me how to create lsmw using idoc method.
    regards,
    balaji

    Hi Balaji,
    LSMW using IDOC is similar to using flat file method. Here you are getting data from IDOC container and mapping data with Idoc segments insted of flatfile column.
    Hope this is what you are looking for. If helpful then don’t forget to reward me for that
    Darshan

  • HT204053 I have one apple ID that my entire family has been using.  How do I create new apple ID's for each of us and move the appropriate content to each new ID from the original apple ID now that we all have our own devices?

    I have been using one apple ID for 4 family members.  Up until now it hasn't been a problem but now that we all have our own devices how do I create new apple ID's for each of us and them move the approprioate things from the original apple ID account to the new ones for each of us?

    stuartx4 wrote:
    Thanks Csound1, wish I have seperated everything from the beginning but when your kids are little and start buying music etc it just didn't seem like an issue.
    That has a familiar ring to it

  • LSMW used only for master data upload?

    Hi
    Can you please let me know if LSMW is used only for master data upload or we can also use it for transaction data ?

    Hi Christino.
    I have come across a standard SDN thread which deals with the uploading master data, refer it:
    [SDN Reference for uploading master data using LSMW|how can we upload master data by using LSMW;
    [SDN reference for which uploading is preferred (Master data or Transaction data)|Which one is better for uploading data LSMW or ECATT ?;
    Good Luck & Regards.
    HARSH

  • I want IDOC for Vendor master updation ( XK01 &XK02 )

    Hi
    I want to do LSMW in IDOC method for this vendor updation.
    So I want IDOC for Vendor master updation ( XK01 & XK02 ).
    I want to do both create vendor and change also.
    Regards,
    Ravi
    Edited by: kandukuri ravi on Dec 1, 2008 2:56 PM

    Hi,
        For Vendor Master using IDoc's for LSMW,Use Message Type = CREMAS and Basic Type = CREMAS05.
    For Basic type 01,02,03...05 are versions which includes more fields in basic type so better use latest version.
    Hope it will help you.
    Regards,
    Sudhakar Reddy.A

  • Partner profile in lsmw using idocs

    Hii!
    I have a requirement where i need to convert article master in SAP Retail. I am using LSMW using IDOC. I have followed all the steps of configuration like created a partner profile, a message type(zmsg_type), processcode etc.
    However in LSMW Step: Start Idoc Generation , i get the foll. error:
    <b>Create a partner profile for message type zmsg_type.</b>
    Please help me with this.
    Thanks.

    Go to WE20 and then take your partner profile type from the left hand side and check you have assinged the message type in outbound or inbound parameter(in the right hand side).. if you have not then you will get this error.
    Award if usefule
    Prince

  • Urgent : LSMW using Idocs

    Hi Friends...kindly send me step by step procedure on how to do LSMW using Idocs only. I know how to do LSMW using all other methods other than Idocs. So
    Kindly send me procedure or any good document on LSMW using Idocs. Thanks in advance.

    Hi Satyesh T
    Go through the following Steps for LSMW Using IDoc
    Inbound Processing of LSMW Via IDOC's
    Step1) Create the Partner Profiles & Port for Inbound Process and Ctivate the Inbound Process for LSMW.
         a) Goto Tcode SALE
                    1) Create Logical System for Receiver Save & Come Back
                    2) assign Logical to Client for LSMW inbound Process
         b) Goto Tcode SM59
                    1) Create  RFC Destinations for ALE
         c) Goto Tcode WE21
                    1) Create a file port which can read the data from the specified path.
                    Here select "FILE" Node --> Click on Create Button(F5)
                    Give the following Information
                    Port : FILE
                    Desc : File Port for Inbound Processing of LSMW Via IDOC's
              Goto Outbound File Tab.
              Select Logical Directory Radio Button.
              Give LOCAL_TEMPORARY_FILES as Logical Path.
              If it is Physical Pthat : C:\TEMP\Filename.
    Goto Tcode LSMW
    ===============
    Give      Project          : ZPROJECT
         SubProject        : ZPROJECT
         Object            : ZPROJECT
    Click on Create  Button
    then goto Settings Mwnu
              Click on  IDoc Inbound Process.
    Here you need to Pass File Port : File
                       Partner Type : LS
                       Partner No.  : Port Name (Just Created from WE21 Tcode)
    Save And Click on ACTIVATE IDOC INBOUND PROCESS
    Save and Come Back.
    1) Click on Execute(F8)    1 Maintain Object Attributes    
    Select IDoc(Intermediate Document)
    Message Type : MATMAS
    Basic Type   : MATMAS05
    Save & Come Back
    Then Your Getting the following Steps need to Do
      2 Maintain Source Structures                   
      3 Maintain Source Fields                       
      4 Maintain Structure Relations                 
      5 Maintain Field Mapping and Conversion Rules  
      6 Maintain Fixed Values, Translations, User-Defi
      7 Specify Files                                
      8 Assign Files                                 
      9 Read Data                                    
    10 Display Read Data                            
    11 Convert Data                                 
    12 Display Converted Data                       
    13 Start IDoc Generation                        
    14 Start IDoc Processing                        
    15 Create IDoc Overview                         
    16 Start IDoc Follow-Up                         
    2) Select the 2nd Radio Button & Execute.
    Click on Create Button.
         Source Structure : ZE1MARAM
            Description      : XXXXXXXXXX
    Click on Continu Button
    Select Just Created "Source Structure : ZE1MARAM"
    Again Click on Create Button this is your Second Source Structure.
         Source Structure : ZE1MAKTM
            Description      : XXXXXXXXXX
    It Asks the Same Level or Lowerlavel of Source Structure : ZE1MARAM
    select Lower Level Radio Button.
    Click on Continue Button 
    Save & Come Back.
    3) Select the 3rd Radio Button and click on Execute Button
    Select the first Source Structure
       Click on Copy Button
    Select the Third Radio Button
       Click on Copy Button
         Give the Tab Name is E1MARAM
    Click on Continue Button.
    Save this
    Go bottom
    Select the 2nd Source Structure " ZE1MAKTM"
       Click on Copy Button
    Select the Third Radio Button
       Click on Copy Button
         Give the Tab Name is E1MAKTM
    Click on Continue Button.
    Save & Come Back.
    4) Select the 4TH Radio Button and click on Execute Button
    Select E1MARAM -->Click on Relationship Button
         Here A Small window comes  then Select ZE1MARAM
         Click on Continue Button.
    Select E1MAKTM -->Click on Relationship Button
         Here A Small window comes  then Select ZE1MAKTM
         Click on Continue Button.
    The Above two Structure are appears in Blue Color
    Save & Come Back.
    5) Select the 5TH Radio Button and click on Execute Button
    First Structure : EDI_DC40 this is Control Record of your IDoc.
    after this you will find a Structure "E1MARAM" this is in Orange Color Remember
    Select MSGFN Field and Click on Source Field
             a New window will comes here select the ZE1MARAM-->MSGFN field and double Click on it.
    Select MATNR Field and Click on Source Field
             a New window will comes here select the ZE1MARAM-->MATNR field and double Click on it.
    Select MTART Field and Click on Source Field
             a New window will comes here select the ZE1MARAM-->MTART field and double Click on it.
    Select MBRSH Field and Click on Source Field
             a New window will comes here select the ZE1MARAM-->MBRSH field and double Click on it.
    Select MATKL Field and Click on Source Field
             a New window will comes here select the ZE1MARAM-->MATKL field and double Click on it.
    Select MEINS Field and Click on Source Field
             a New window will comes here select the ZE1MARAM-->MEINS field and double Click on it.
    Select GEWEI Field and Click on Source Field
             a New window will comes here select the ZE1MARAM-->GEWEI field and double Click on it.
    Save This.
    Go Bottom.
    you will find a Structure "E1MAKTM" this is in Orange Color Remember
    Select MSGFN Field and Click on Source Field
             a New window will comes here select the ZE1MAKTM-->MSGFN field and double Click on it.
    Select SPRAS Field and Click on Source Field
             a New window will comes here select the ZE1MAKTM-->SPARS field and double Click on it.
    Select MAKTX Field and Click on Source Field
             a New window will comes here select the ZE1MAKTM-->MAKTX field and double Click on it.
    Save and Comeback.
    Create Your Flat Files Like he following Format. and save it in C:\TEMP folder Only
    1st File : MARA.TXT
    001     MAT001                                   COUP     C     15          KG                                                                                          01
    2nd File : MAKT.TXT
    001     EN     New Material For Inbound Processing of LSMW Via IDOC's
    6) Select the 6TH Radio Button and click on Execute Button
         We don't do any process here  Just Come Back.
    7) Select the 7TH Radio Button and click on Execute Button
         Click on Legacy data : Click on F5 Button.
                  Add Two Files 1) C:\TEMP\MARA.TXT     
                       2) C:\TEMP\MAKT.TXT
         Select Tablator Radio Button as Delimiter
         Save & Come Back.
    8) Select the 8TH Radio Button and click on Execute Button
         Select ZE1MARAM Structure and Click on Assignment Button
         Save this
         Select ZE1maktm Structure and Click on Assignment Button
         Save and Come Back.
    9) Select the 9TH Radio Button and click on Execute Button
         Click F8 Button.
         Check the Read Dada
    10) Select the 10TH Radio Button and click on Execute Button
         Click F8 Button.
         Check the Display Read Data.
    11) Select the 11TH Radio Button and click on Execute Button
         Click F8 Button.
         Check the Convert Data.
    12) Select the 12TH Radio Button and click on Execute Button
         Click F8 Button.
         Check the Display Convert Data.
    13) Select the 13TH Radio Button and click on Execute Button
         Click F8 Button.
    14) Select the 14TH Radio Button and click on Execute Button
         This is WE05 Tcode Screen Start IDoc Process.
    15) Select the 15TH Radio Button and click on Execute Button
         This is WE05 Tcode Screen Creating IDoc Here
    16) Select the 16TH Radio Button and click on Execute Button
         Select Posting Radio Button(that is 5th Button)
         then Click on F8 or Execute Button.
    After this your will check your Material exist in receving Side or Not.
    Thanks & Regards
    Sreeni

  • LSMW using IDocs/BAPIS

    Hi All,
    I am new to LSMW and want a simple tutorial for using LSMW using Idocs and BAPIs. I have found many useful tutorials for Direct Input and Batch Recording. If anyone can give me link or a tutorial for using lsmw with idocs and bapis it will be of great help.
    Thanks in advance.
    archish

    Hi,
       is step by step process .
    Step-by-Step Guide for using BAPI in LSMW
    Note! The screen prints in this article are from ECC 5.0. They may differ slightly in other versions.
    Introduction:
    This document details the usage of BAPI in LSMW. We have used the example of migration of the purchase order data into SAP.
    Pre-requisites:
    It is assumed that the reader of this article has the minimum knowledge required on the Business Object, BAPI, Message Types and IDoc Types.
    Step-by-Step Procedure:
    Details of the BAPI used in this scenario:
    Business Object: BUS2012
    Method: CreateFromData
    Details of Message Type and Basic IDoc Type:
    Message Type: PORDCR
    Basic IDoc Type: PORDCR02
    Let’s have a look at the BAPI first, before proceeding to the LSMW:
    1. Go to Transaction BAPI
    2. Click on Search Button
    3. Enter the value “BUS2012” and select “Obj.type(Technical Object Name”
    4. Press ENTER
    5. Following screen appears:
    6. On the left side of the screen, Expand the “PurchaseOrder”.
    7. Select “PurchaseOrder” and double-click on the same for details.
    Building LSMW using BAPI:
    1. Go to Transaction LSMW.
    2. Enter the Project, Subproject and Object information and click on CREATE.
    3. Enter the descriptions for Project, Subproject and Object as prompted.
    4. Now select Settings à IDoc Inbound Processing
    5. “IDoc Inbound Processing” screen appears. Enter the required details as shown below:
    6. Click on “Activate IDoc Inbound Processing”.
    7. Click on “Yes” when prompted for “Activate IDoc Inbound?”
    8. Hit on “Back” to return to the main screen.
    9. Click on Continue (F8). Following Screen appears:
    10. Select the Step 1 “Maintain Object Attributes” and select “Execute”.
    11. Select the radio button “Business Object Method” and enter the following details:
    Business Object: BUS2012
    Method: CreateFromData
    Hit ENTER
    12. Save and click on BACK button. Following information message is displayed.
    13. Now select step 2 “Maintain Source Structures” and click “Execute”.
    14. In this step, we need to maintain the source structure. In our example, lets consider the example of a file with 2 structures Head and Item data as shown below:
    Click on Create and name the source structure as HEADERDATA. Now select HEADERDATA and click on “Create” again to create the child structure. Following popup appears:
    Select “Lower Level” and click on Continue. Enter the Item data structure name.
    Click Save and hit BACK button to go to the main screen.
    15. Select step 3 “Maintain Source Fields” and hit execute.
    16. Enter the fields as shown below:
    17. Click SAVE and return to main screen.
    18. Select step 4 “Maintain Structure Relations” and click Execute.
    Select E1PORDCR and click on CREATE RelationShip. Following screen appears:
    Select HEADERDATA and hit ENTER
    Similarly do the same for the structure E1BPEKKOA, E1BPEKPOC and E1BPPEKET.
    Click Save and return to main screen.
    19. Select the step “Maintain Field Mapping and Conversion Rules” and click on execute. Maintain the Field Mapping as seen below:
    20. Select step 7 “Maintain Source Files” and provide the link for the test file created. (Create a test file with the same structure as defined earlier).
    Save and return to main screen.
    21. Select the step “Assign Files” and click on Execute.
    Assign the file provided to the source structure. Here the same file is provided for both the structures.
    Save and return to the main screen.
    22. Select the step “Read Data” and click on Execute.
    Click on Execute.
    Return to the main screen.
    23. Select the step “Display read data” and click on execute.
    Click on the structure name to get the field level values.
    24. Return to main screen and now select “Convert Data”.
    25. Return to the main screen and select “Display Converted data”.
    26. Return to main screen and select “Start IDoc generation”.
    27. Now select the step “Start IDoc Processing” on the main screen.
    28. Return to main screen and click on “Create IDoc overview”. Here the data record and status records of the IDoc could be viewed:
    Please Go through these Links ,
    BAPI with LSMW
    http://esnips.com/doc/ef04c89f-f3a2-473c-beee-6db5bb3dbb0e/LSMW-with-BAPI
    For document on using BAPI with LSMW, I suggest you to visit:
    http://www.****************/Tutorials/LSMW/BAPIinLSMW/BL1.htm
    http://myweb.dal.ca/hchinni/sap/lsmw_home.htm
    http://sapabap.iespana.es/sapabap/manuales/pdf/lsmw.pdf
    lsmw-idoc method:
    http://www.scmexpertonline.com/downloads/SCM_LSMW_StepsOnWeb.doc
    Regards

  • 'Create' Push button is not working in BDC and LSMW while uploading G/L master data

    Hello Experts:
    I am facing the following problem:
    While uploading G/L master data with the BDC program, 'create' push button is not working  even after executing following lines.
    PERFORM BDC_DYNPRO      USING 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
    PERFORM BDC_FIELD       USING 'BDC_OKCODE'
                                   '=ACC_CRE'.
    Create G/L account  screen is not coming in BDC. Please suggest me what to do.
    Thanks !!

    Re: 'Create' Push button is not working in BDC and LSMW while uploading G/L master data
    Re: 'Create' Push button is not working in BDC and LSMW while uploading G/L master data
    Hi Glen Anthony
    Thank you for the reply Glen Anthony please take a look at the following code.
    REPORT  ZFI_BDC_FS00
            NO STANDARD PAGE HEADING LINE-SIZE 255.
    *INCLUDE BDCRECX1.
    TYPES : BEGIN OF STR,
       BUKRS TYPE GLACCOUNT_SCREEN_KEY-BUKRS,        "Company Code
       SAKNR TYPE GLACCOUNT_SCREEN_KEY-SAKNR,        "G/L Account Number
       KTOKS TYPE GLACCOUNT_SCREEN_COA-KTOKS,        "G/L Account Group
       XPLACCT TYPE GLACCOUNT_SCREEN_COA-XPLACCT,    "P&L statement account
       XBILK TYPE GLACCOUNT_SCREEN_COA-XBILK,        "Indicator: Account is a balance sheet account?
       TXT20_ML TYPE GLACCOUNT_SCREEN_COA-TXT20_ML,  "G/L account short text
       TXT50_ML TYPE GLACCOUNT_SCREEN_COA-TXT50_ML,  "G/L account short text
       WAERS TYPE GLACCOUNT_SCREEN_CCODE-WAERS,      "Account currency
       XSALH TYPE GLACCOUNT_SCREEN_CCODE-XSALH,      "Indicator: Only Manage Balances in Local Currency
       MWSKZ TYPE GLACCOUNT_SCREEN_CCODE-MWSKZ,      "Tax Category in Account Master Record
       XMWNO TYPE GLACCOUNT_SCREEN_CCODE-XMWNO,      "Indicator: Tax code is not a required field
       MITKZ TYPE GLACCOUNT_SCREEN_CCODE-MITKZ,      "Account is reconciliation account
       XOPVW TYPE GLACCOUNT_SCREEN_CCODE-XOPVW,      "Indicator: Open item management?
       XKRES TYPE GLACCOUNT_SCREEN_CCODE-XKRES,      "Indicator: Can Line Items Be Displayed by Account?
       ZUAWA TYPE GLACCOUNT_SCREEN_CCODE-ZUAWA,      "Key for sorting according to assignment numbers
       FSTAG TYPE GLACCOUNT_SCREEN_CCODE-FSTAG,      "Field status group
       XINTB TYPE GLACCOUNT_SCREEN_CCODE-XINTB,      "Indicator: Is account only posted to automatically?
       END OF STR.
    DATA : ITAB TYPE TABLE OF STR WITH HEADER LINE,
            IT_BDCDATA TYPE TABLE OF BDCDATA WITH HEADER LINE,
            TXT(4096) TYPE C OCCURS 0,
            MSG TYPE STRING,
            COUNT(5) TYPE N.
    SELECTION-SCREEN : BEGIN OF BLOCK B1 WITH FRAME TITLE TEXT-001.
       PARAMETERS : MY_FILE TYPE RLGRAP-FILENAME.
    SELECTION-SCREEN : END OF BLOCK B1.
    AT SELECTION-SCREEN ON VALUE-REQUEST FOR MY_FILE.
    CALL FUNCTION 'F4_FILENAME'
      EXPORTING
        PROGRAM_NAME        = SYST-CPROG
        DYNPRO_NUMBER       = SYST-DYNNR
    *   FIELD_NAME          = ' '
      IMPORTING
        FILE_NAME           = MY_FILE
    CALL FUNCTION 'TEXT_CONVERT_XLS_TO_SAP'
       EXPORTING
    *   I_FIELD_SEPERATOR          =
    *   I_LINE_HEADER              =
         I_TAB_RAW_DATA             = TXT
         I_FILENAME                 = MY_FILE
       TABLES
         I_TAB_CONVERTED_DATA       = ITAB[]
      EXCEPTIONS
        CONVERSION_FAILED          = 1
        OTHERS                     = 2
    IF SY-SUBRC <> 0.
    * IMPLEMENT SUITABLE ERROR HANDLING HERE
    ENDIF.
    START-OF-SELECTION.
    COUNT = 0.
    LOOP AT ITAB.
    *PERFORM OPEN_GROUP.
    REFRESH  IT_BDCDATA.
    PERFORM BDC_DYNPRO      USING 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
    PERFORM BDC_FIELD       USING 'BDC_CURSOR'
                                   'GLACCOUNT_SCREEN_KEY-BUKRS'.
    PERFORM BDC_FIELD       USING 'BDC_OKCODE'
                                   '=ACC_CRE'.
    *PERFORM BDC_FIELD       USING 'BDC_CURSOR'
    *                              'GLACCOUNT_SCREEN_KEY-BUKRS'.
    PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_KEY-SAKNR'
                                   ITAB-SAKNR. "'5'.
    PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_KEY-BUKRS'
                                   ITAB-BUKRS. "'TATA'.
    PERFORM BDC_DYNPRO      USING 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
    PERFORM BDC_FIELD       USING 'BDC_OKCODE'
                                   '=2102_GROUP'.
    PERFORM BDC_FIELD       USING 'BDC_CURSOR'
                                   'GLACCOUNT_SCREEN_COA-KTOKS'.
    PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_COA-KTOKS'
                                   ITAB-KTOKS. "'GL'.
    PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_COA-XPLACCT'
                                   ITAB-XPLACCT. "'X'.
    PERFORM BDC_DYNPRO      USING 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
    PERFORM BDC_FIELD       USING 'BDC_OKCODE'
                                   '=2102_BS_PL'.
    PERFORM BDC_FIELD       USING 'BDC_CURSOR'
                                   'GLACCOUNT_SCREEN_COA-XBILK'.
    PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_COA-KTOKS'
                                   ITAB-KTOKS. "'GL'.
    PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_COA-XPLACCT'
                                   ITAB-XPLACCT. "''.
    PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_COA-XBILK'
                                   ITAB-XBILK. "'X'.
    PERFORM BDC_DYNPRO      USING 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
    PERFORM BDC_FIELD       USING 'BDC_OKCODE'
                                   '=TAB02'.
    PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_COA-KTOKS'
                                   ITAB-KTOKS. "'GL'.
    PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_COA-XBILK'
                                   ITAB-XBILK. "'X'.
    PERFORM BDC_FIELD       USING 'BDC_CURSOR'
                                   'GLACCOUNT_SCREEN_COA-TXT50_ML'.
    PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_COA-TXT20_ML'
                                   ITAB-TXT20_ML. "'G/L ACCOUNT'.
    PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_COA-TXT50_ML'
                                   ITAB-TXT50_ML. "'G/L ACCOUNT'.
    PERFORM BDC_DYNPRO      USING 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
    PERFORM BDC_FIELD       USING 'BDC_OKCODE'
                                   '=TAB03'.
    PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_CCODE-WAERS'
                                   ITAB-WAERS. "'INR'.
    PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_CCODE-XSALH'
                                   ITAB-XSALH. "'X'.
    PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_CCODE-MWSKZ'
                                   ITAB-MWSKZ. "'*'.
    PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_CCODE-XMWNO'
                                   ITAB-XMWNO. "'X'.
    PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_CCODE-MITKZ'
                                   ITAB-MITKZ. "''.
    PERFORM BDC_FIELD       USING 'BDC_CURSOR'
                                   'GLACCOUNT_SCREEN_CCODE-ZUAWA'.
    PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_CCODE-XOPVW'
                                   ITAB-XOPVW. "'X'.
    PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_CCODE-XKRES'
                                   ITAB-XKRES. "'X'.
    PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_CCODE-ZUAWA'
                                   ITAB-ZUAWA. "'1'.
    PERFORM BDC_DYNPRO      USING 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
    PERFORM BDC_FIELD       USING 'BDC_OKCODE'
                                   '=SAVE'.
    PERFORM BDC_FIELD       USING 'BDC_CURSOR'
                                   'GLACCOUNT_SCREEN_CCODE-XINTB'.
    PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_CCODE-FSTAG'
                                   ITAB-FSTAG. "'G019'.
    PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_CCODE-XINTB'
                                   ITAB-XINTB. "'X'.
    *PERFORM BDC_TRANSACTION USING 'FS00'.
    CALL TRANSACTION 'FS00' USING IT_BDCDATA MODE 'E' UPDATE 'S'.
    COUNT = COUNT + 1.
    *PERFORM CLOSE_GROUP.
    ENDLOOP.
    CONCATENATE COUNT ' RECORDS UPDATED SUCCESSFULLY' INTO MSG.
    MESSAGE MSG TYPE 'I'.
    FORM BDC_DYNPRO USING PROGRAM DYNPRO.
       CLEAR IT_BDCDATA.
       IT_BDCDATA-PROGRAM  = PROGRAM.
       IT_BDCDATA-DYNPRO   = DYNPRO.
       IT_BDCDATA-DYNBEGIN = 'X'.
       APPEND IT_BDCDATA.
    ENDFORM.
    *        INSERT FIELD                                                  *
    FORM BDC_FIELD USING FNAM FVAL.
    *  IF FVAL <> NODATA.
         CLEAR IT_BDCDATA.
         IT_BDCDATA-FNAM = FNAM.
         IT_BDCDATA-FVAL = FVAL.
         APPEND IT_BDCDATA.
    *  ENDIF.
    ENDFORM.

  • New SAP Tools for faster Master Data Upload?

    Hi All!
    I am interested in getting some detailed information on different tools that are used for faster master data upload. Please let me know about the tools apart from LSMW, BAPI, eCATT and BDC.
    We basically want to know the following things:
    1.Which are the tools available for this master data upload?
    for eg. SAP MDM, Info Shuttle, other available new age tools etc........
    2. Their performance / feature comparions?
    Please provide performance / feature comparison for different new age tools in detail.
    Thanking you in advance.
    Regards,

    Hi Amar,
    regarding SAP MDM you can read advantages and characteristics here: http://www.sap.com/platform/netweaver/components/mdm/index.epx
    Hope this help you,
    Vito

  • Idoc for plant master

    Hi Everyone,
    This is my first project on ALE/Idocs ... I need to send the Plant information using Idoc but I'm not getting any Idoc to send the information. So do I have to create a custom Idoc for this??? The feilds whhich I need to send are WERKS,NAME1 and ORT01.

    Hi this will help u.
    Data Creation in Idoc
    IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an
    asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.
    While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.
    IDoc is a intermediate document to exchange data between two SAP Systems.
    *IDocs are structured ASCII files (or a virtual equivalent).
    *Electronic Interchange Document
    *They are the file format used by SAP R/3 to exchange data with foreign systems.
    *Data Is transmitted in ASCII format, i.e. human readable form
    *IDocs exchange messages
    *IDocs are used like classical interface files
    IDOC types are templates for specific message types depending on what is the business document, you want to exchange.
    WE30 - you can create a IDOC type.
    An IDOC with data, will have to be triggered by the application that is trying to send out the data.
    FOr testing you can use WE19.
    How to create idoc?
    *WE30 - you can create a IDOC type
    For more information in details on the same along with the examples can be viewed on:
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm
    http://www.sappoint.com/presentation.html
    http://www.allsaplinks.com/idoc_search.html
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://www.erpgenie.com/sapedi/idoc_abap.htm
    To Create Idoc we need to follow these steps:
    Create Segment ( WE31)
    Create Idoc Type ( WE30 )
    Create Message Type ( WE81 )
    Assign Idoc Type to Message Type ( WE82 )
    Creating a Segment
    Go to transaction 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 it and go back
    Go to Edit -> Set Release
    Follow steps to create more number of segments
    Create IDOC Type
    Go to transaction code WE30
    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
    Create Message Type
    Go to transaction 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
    Go to transaction 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
    Check these out..
    Re: How to create IDOC
    Check below link. It will give the step by step procedure for IDOC creation.
    http://www.supinfo-projects.com/cn/2005/idocs_en/2/
    ALE/ IDOC
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sappoint.com/abap.html
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
    go trough these links.
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sappoint.com/abap.html
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data...
    1.IDOCs are stored in the database. In the SAP system, IDOCs are stored in database tables.
    2.IDOCs are independent of the sending and receiving systems.
    3.IDOCs are independent of the direction of data exchange.
    The two available process for IDOCs are
    Outbound Process
    Inbound Process
    AND There are basically two types of IDOCs.
    Basic IDOCs
    Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
    Extended IDOCs
    Extending the functionality by adding more segments to existing Basic IDOCs.
    To Create Idoc we need to follow these steps:
    Create Segment ( WE31)
    Create Idoc Type ( WE30)
    Create Message Type ( WE81)
    Assign Idoc Type to Message Type ( WE82)
    imp links
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    www.sappoint.com
    --here u can find the ppts and basic seetings for ALE
    http://sappoint.com/presentation.html
    www.sapgenie.com
    http://www.sapgenie.com/ale/index.htm
    WE30 - you can create a IDOC type.
    An IDOC with data, will have to be triggered by the application that is trying to send out the data.
    Try this..Hope this will help.
    >>>> SAP ALE & IDOC<<<<
    Steps to configuration(Basis) >>
    1. Create Logical System (LS) for each applicable ALE-enabled client
    2. Link client to Logical System on the respective servers
    3. Create background user, to be used by ALE(with authorizaton for ALE postings)
    4. Create RFC Destinations(SM59)
    5. Ports in Idoc processing(WE21)
    6. Generate partner profiles for sending system
    The functional configuration(Tcode: SALE)
    • Create a Customer Distribution Model (CDM);
    • Add appropriate message types and filters to the CDM;
    • Generate outbound partner profiles;
    • Distribute the CDM to the receiving systems; and
    • Generate inbound partner profiles on each of the clients.
    Steps to customize a new IDoc >>>
    1. Define IDoc Segment (WE31)
    2. Convert Segments into an IDoc type (WE30)
    3. Create a Message Type (WE81)
    4. Create valid Combination of Message & IDoc type(WE82)
    5. Define Processing Code(WE41 for OUT / WE42 for IN)
    6. Define Partner Profile(WE20)
    Important Transaction Codes:
    SALE - IMG ALE Configuration root
    WE20 - Manually maintain partner profiles
    BD64 - Maintain customer distribution model
    BD71 - Distribute customer distribution model
    SM59 - Create RFC Destinations
    BDM5 - Consistency check (Transaction scenarios)
    BD82 - Generate Partner Profiles
    BD61 - Activate Change Pointers - Globally
    BD50 - Activate Change Pointer for Msg Type
    BD52 - Activate change pointer per change.doc object
    BD59 - Allocation object type -> IDOC type
    BD56 - Maintain IDOC Segment Filters
    BD53 - Reduction of Message Types
    BD21 - Select Change Pointer
    BD87 - Status Monitor for ALE Messages
    BDM5 - Consistency check (Transaction scenarios)
    BD62 - Define rules
    BD79 - Maintain rules
    BD55 - Defining settings for IDoc conversion
    WEDI - ALE IDoc Administration
    WE21 - Ports in Idoc processing
    WE60 - IDoc documentation
    SARA - IDoc archiving (Object type IDOC)
    WE47 - IDoc status maintenance
    WE07 - IDoc statistics
    BALE - ALE Distribution Administration
    WE05 - IDoc overview
    BD87 - Inbound IDoc reprocessing
    BD88 - Outbound IDoc reprocessing
    BDM2 - IDoc Trace
    BDM7 - IDoc Audit Analysis
    BD21 - Create IDocs from change pointers
    SM58 - Schedule RFC Failures
    Basic config for Distributed data:
    BD64: Maintain a Distributed Model
    BD82: Generate Partner Profile
    BD64: Distribute the distribution Model
    Programs
    RBDMIDOC – Creating IDoc Type from Change Pointers
    RSEOUT00 – Process all selected IDocs (EDI)
    RBDAPP01 - Inbound Processing of IDocs Ready for Transfer
    RSARFCEX - Execute Calls Not Yet Executed
    RBDMOIND - Status Conversion with Successful tRFC Execution
    RBDMANIN - Start error handling for non-posted IDocs
    RBDSTATE - Send Audit Confirmations
    FOr testing you can use WE19.
    with regards,
    Hema Sundara.
    pls reward if it is helpful.

Maybe you are looking for