Material Needed on Data Migration

Hi All,
               I am working on project as fresher.
               The major work is on Data Migration.                 
               Can I have get any material like Basic documents,
               Sample programs/Codes Concept explanation
               etc regarding Data Migration (BDC’s and LSMW)?
               If so can you send me that personal mail id so that
               it might be useful for me?
               My personal mail id's are
               1) [email protected]
               2) [email protected]
                Thanks in Advance.
                Points would be rewarded.
   With Regards
Jitendra Gujarathi

Hi
BDC:
Batch Data Communication (BDC) is the process of transferring data from one SAP System to another SAP system or from a non-SAP system to SAP System.
Features :
BDC is an automatic procedure.
This method is used to transfer large amount of data that is available in electronic medium.
BDC can be used primarily when installing the SAP system and when transferring data from a legacy system (external system).
BDC uses normal transaction codes to transfer data.
Types of BDC :
CLASSICAL BATCH INPUT (Session Method)
CALL TRANSACTION
BATCH INPUT METHOD:
This method is also called as ‘CLASSICAL METHOD’.
Features:
Asynchronous processing.
Synchronous Processing in database update.
Transfer data for more than one transaction.
Batch input processing log will be generated.
During processing, no transaction is started until the previous transaction has been written to the database.
CALL TRANSACTION METHOD :
This is another method to transfer data from the legacy system.
Features:
Synchronous processing. The system performs a database commit immediately before and after the CALL TRANSACTION USING statement.
Updating the database can be either synchronous or asynchronous. The program specifies the update type.
Transfer data for a single transaction.
Transfers data for a sequence of dialog screens.
No batch input processing log is generated.
For BDC:
http://myweb.dal.ca/hchinni/sap/bdc_home.htm
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/bdc&
http://www.sap-img.com/abap/learning-bdc-programming.htm
http://www.sapdevelopment.co.uk/bdc/bdchome.htm
http://www.sap-img.com/abap/difference-between-batch-input-and-call-transaction-in-bdc.htm
http://help.sap.com/saphelp_47x200/helpdata/en/69/c250684ba111d189750000e8322d00/frameset.htm
http://www.sapbrain.com/TUTORIALS/TECHNICAL/BDC_tutorial.html
Check these link:
http://www.sap-img.com/abap/difference-between-batch-input-and-call-transaction-in-bdc.htm
http://www.sap-img.com/abap/question-about-bdc-program.htm
http://www.itcserver.com/blog/2006/06/30/batch-input-vs-call-transaction/
http://www.planetsap.com/bdc_main_page.htm
call Transaction or session method ?
LSMW
1. Maintain Attributes:
Here you have to choose the second option and you can do the recording how this should work. Then assign the same to the Batch Input Recording name.
2. Maintain Source structure:
Create a structure name
3. Maintain Source field:
In this you have to create a structure same as that of the input file
eg: name
age
4. Maintain structure relations:
This will link the structure to the input file.
5. Maintain field mapping and conversion rules:
Here is the place where you can do coding, depending upon the code you have written or assignment you have done the values will get picked up from the file and get processed.
6. Maintain field mapping and conversion rules:
If you have any fixed values you can define here.
7. Specify files:
Specify the input file path and type.
8. Assign files:
This will assign ur file to the Input file
9. Read Data:
This will read ur data from teh file.
10. Dispaly Read Data:
You can see the uploaded data
11. Convert Data
This will convert the data to the corresponding format for processing
12. Display Converted data:
13. Create batch input session
Here this will create a batch input session for processing
14. Run Batch Input session:
By clicking on the session and process the same you can do teh needfu.
http://www.sapbrain.com/TOOLS/LSMW/SAP_LSMW_steps_introduction.html
http://esnips.com/doc/8e732760-5548-44cc-a0bb-5982c9424f17/lsmw_sp.ppt
http://esnips.com/doc/f55fef40-fb82-4e89-9000-88316699c323/Data-Transfer-Using-LSMW.zip
http://esnips.com/doc/1cd73c19-4263-42a4-9d6f-ac5487b0ebcb/LSMW-with-Idocs.ppt
http://esnips.com/doc/ef04c89f-f3a2-473c-beee-6db5bb3dbb0e/LSMW-with-BAPI.ppt
http://esnips.com/doc/7582d072-6663-4388-803b-4b2b94d7f85e/LSMW.pdf
for Long texts Upload
Please take a look at this..
http://help.sap.com/saphelp_erp2005/helpdata/en/e1/c6d30210e6cf4eac7b054a73f8fb1d/frameset.htm
<b>
Reward points for useful Answers</b>
Regards
Anji

Similar Messages

  • RollOut: Data migration phase - material master

    Dear all,
    we are going to implement the SAP in one of our subsidiaries. The phase data migration of the material master is not that clear because I am not very experienced in such a project.
    Can anybody consult me concerning my intentions?
    I would like to subdivide the prozess data migration in the following separate steps:
    1. Analysis of the structure and the material master fields of the legacy system
    First I would require an example structure of the legacy system to get a first overview. This structure should be an excel sheet. Then I would discuss this structure with the staff of our subsidiary.
    2. Structure of our SAP system
    The structure of the SAP and all the necessary fields of the material master will be discussed with the staff of the subsidiary.
    3. Comparing of both structures
    Compare both structures and define which fields are missing and which fields have to be added
    4. Preparation of the migration tool (LSMW)
    I would be very grateful to get a reply or critic are recommendations.
    Did I forget anything?
    Thank you very much
    Conan

    I think you basically got what needs to be done.
    I usually let the module teams deliver the SAP fields that are necessary for their process.
    For the source data I contact the team that deals with the legacy system.
    Then we map fields and find the source fields that have to target, as well as mandatory target fields that have no source data.
    And I request this usually per material type, as each material type may have different requirements.
    Start with the process as early as possible, best with project begin already.
    I am currently doing a huge migration project (merging of several SAP systems) , started last December, and I still miss a lot of mappings.
    I made the exerience that I get mapping for the well kown entries of a field, however, there are many records that have different values, maybe values that should not be used anymore in the legacy system, but old records never go adjusted, hence I have them as error when loading.

  • Que on Material Master Data Migration

    Hi All
    We are trying to allocate parallel currency to an existing co code, and since SAP recommends not to add parallel currency to an existing co code, we have decided to go ahead with a new co code - thereby transferring all master and transaction data as part of data migration..
    However, my Qs is.. do we have to migrate the material master data aswell since when I make the material to plant assignment in customizing, it should then officially belong to the new co code too right?
    Please advise
    RS

    Hello Jürgen
    Thanks for your reply.
    I dont think you fully understand my scenario..
    we have an entity that wants to introduce a parallel currency to all their reporting.. therefore, addiding a parallel currency to an active company code is not possible and they are not keen to go with material ledger...
    therefore, we suggested a brand new co code as of 01.01.2012. So the current co code is not going to be active after 31.12.2011. We are creating a brand new co code and doing data migration for all the master data and transaction data.
    meaning, Vendor, Customer, GL, AP & AR item Data, GL item data and asset master and transaction data.
    In customizing, after creating the new company, we will make the assignments to plant purchasing/sales org etc.
    My Qs - do we also need to migrate the material master since it belongs to a Plant. Therefore, when we assign the co code to the Plant, it will automatically be available in the co code when creating a PO etc..
    this is my Qs
    thank you
    RS

  • Need help for HR data migration

    Hi Experts,
         I need a help that i want to do data migration for PA30 and PP01 transactions.so if any std bapi for upload the data or bdc programs you have means let me know for further process.if early it is good for me.
    Thanks,
    Deesanth

    You can use the standard batch program RPUSTD00.  Also you can use the function module HR_INFOTYPE_OPERATION.
    Hope this is helpful.
    Thanks,
    Pavan

  • Data Migration for Open Purchase Order

    Hi, All,
    Is there anyone know how to Count the volume for Open Purchase Order. What's the normal strategy for the Data Migration and Cut-over stage?
    My client want to know how many Open Purchase Order in the legacy system and then determine manual or automatic data migration. If manual, how to do? If automatic, how to do? Because all materials and vendors, plants are different number. How to track? How to find out to match between new and old?
    Thank you very much

    JC,
    Sounds a bit early to be making decisions about the realization phase.  It doesn't sound like you have finished the Blueprinting phase yet, much less the testing phase.
    Anyhow, in my experience I typically use LSMW (Legacy system migration workbench) to load MM master data (material masters), Inventory (WIP, RM, FG, etc) Purchasing Master data (Vendors, Purchase Info Records, Source Lists, Quota Arrangements), and Purchasing transactional documents (POs, PurReqs, Scheduling Agreements, etc).  Depending on the complexity and volume of data, it  may be necessary to write custom programs to load the data.  You will find this out during your requirements gathering.
    It is uncommon but possible to load all of these data manually.  I have never run across a client that wants to pay a consultant's hourly rate to sit at a terminal to peck away loading master data, so if the client intends to have his own users enter the data manually, the project manager should make provision that there will be qualified TRAINED client employees available for this data entry.  I did help with a portion of a conversion once manually; of Sales Credits, but there were only about 30 SD docs to load.   I did this the evening before go-live day, while I was waiting for some of my LSMW projects to complete in the background.
    A good opportunity to 'practice' your data loads is right after you have completed your development and customization, and you have gotten the approval from the client to proceed from the pilot build to the full test environment.  Once you have moved your workbench and customization into the client's test environment, but before integration testing, you can mass load all, or a substantial portion of your conversion data into the qual system.  You can treat it like a dry run for go-live, and fine tune your processes, as well as your LSMW projects.
    Yes, it is good practice to generate comparisons between legacy and SAP even if the client doesn't ask for it. For Purchase orders on the SAP side, you could use any of the standard SAP Purchasing reports, such as ME2W, ME2M, ME2C, ME2L, ME2N.  If these reports do not meet the requirements of the client, you could write a query to display the loaded data, or have an ABAPer write a custom report.
    You didn't ask, but you should also do comparisons of ALL loaded data - including master data.
    It sounds like you are implying that the client wants YOU to extract the legacy data.  For an SAP consultant, this is not very realistic (unless the legacy system is another SAP system).  Most of us do not understand the workings of the myriad legacy systems.  The client is usually expected to produce one or more legacy system technical experts for you to liase with.  You normally negotiate with the technical expert about every facet of of the data migration.  In addition, you will liase with business users, who will help you and the implementation team to logically validate that the final solution (turnkey SAP production system, fully loaded with data) will meet the client's business needs.
    Finally, you mentioned how do you track the mapping of master data between legacy and SAP.  There are many ways to do this.  I normally try to get the legacy person do the conversion on his end, eg, when he gives you the load file, you would like to have already translated the master data and inserted the SAP relevant values into the file.  If this is not possible, I usually use MS Access databases to maintain a master map, and I perform the mapping on a PC.  If your data package is small, you can probably get by using MS Excel or similar.
    Good Luck,
    DB49

  • Confuse on PR & PO data migration approach new to MM module

    Hi All,
    I'm pretty confuse with the PO data migration approach when it comes to PO is GR or partial GR or GR&IR. I'm hoping that someone can enlighten me. i understand that we typically don't migrate PO when it is GR & IR, FI team usually will bring over to the new system as an vendor open item in AP. How about the PR or PO which have gone through or half release strategy? What is the follow up process?  I have created a criteria table below. How Could someone point me in the right direction? Thanks in advance.
    PR
    Criteria
    Data migration required
    Notes
    Open and Released
    Y
    Open and not Released
    Y
    Flag for Deletion
    N
    Flag for Block
    Y
    PO
    Criteria
    Data migration required
    Notes
    Open and Released
    Y
    Open and not Released
    Y
    GR but no IR
    GR & IR
    N
    AP will bring over as open item
    Flag for Deletion
    N
    Flag for Block
    Y
    Partial
    Y
    For partial GR to recreate PO only with missing GR quantity
    Regards,
    John

    Hi John,
    The approach that i have followed recently is that we have considered PO as the base document and converted other documents based on the PO condition. This means you first need to see if the PO is to be converted or not. Then you can proceed to convert the related documents like PR, Agreement, Info record, Source list, etc.
    Also open qty for PO should be considered for Material and Service line items both.
    Once a GR/SES is created, it gets updated in the PO history table EKBE with its related transaction/event type.i.e. EKBE-VGABE = 1 for GR and 9 for SES. Quantity and value also gets updated in case of material and services. You can compare this consumed quantities with PO quantity.
    Please see below from SCN and let me know if you need more info on PR or PO conversion.
    Purchase Requisition Conversion Strategy
    Thanks,
    Akash

  • Data Migration From Peoplesoft , JDEdwards To SAP.

    Hi,
    This is kiran here we are doing data Migration work from Peoplesoft And JDEdwards to SAP.in SAP side it involves Master data tables Related to Customer, Vendor, Material. and Meta data tables related to SD, MM, FI. We as SAP Consultant identified Fields from above tables and marked them as Required, Not required, And Mandatory. The Peoplesoft and JDEdwards flocks come up with the same from their side. Then we want map the Fields. as I am new to data Migration any body suggest me what are the steps involves in data Migration How to do Data Mapping in Migration Thanks in advance.
    Thanks
    Kiran.B

    Hi Kiran,
    Good... Check out the following documentation and links
    Migrating from one ERP solution to another is a very complex undertaking. I don't think I would start with comparing data structures. It would be better to understand the business flows you have currently with any unique customizations and determine how these could be implemented in your target ERP. Once this is in place, you can determine the necessary data unload/reload to seed your target system.
    A real configuration of an ERP system will only happen when there is real data in the system. The mapping of legacy system data to a new ERP is a long difficult process, and choices must be made as to what data gets moved and what gets left behind. The only way to verify what you need to actually run in the new ERP environment is to migrate the data over to the ERP development and test environments and test it. The only way to get a smooth transition to a new ERP is to develop processes as automatic as possible to migrate the data from the old system to the new.
    Data loading is not a project that can be done after everything else is ready. Just defining the data in the legacy system is a huge horrible task. Actually mapping it to one of the ERP system schemas is a lesson in pain that must be experienced to be believed.
    The scope of a data migration project is usually a fairly large development process with a lot of proprietary code written to extract legacy data, transform and load the data into the ERP system. This process is usually called ETL (extract, transform, load.)
    How is data put into the ERP?
    There is usually a painfully slow data import facility with most ERP systems. Mashing data into the usually undocumented table schema is also an option, but must be carefully researched. Getting the data out of the legacy systems is usually left to the company buying the ERP. These export - import processes can be complex and slow, sometimes specialized ETL tools can help, sometimes it is easier to use what ever your programmers are familiar with, tools such as C, shell or perl.
    An interesting thing to note is that many bugs and quirks of the old systems will be found when the data is mapped and examined. I am always amazed at what data I find in a legacy system, usually the data has no relational integrity , note that it does not have much more integrity once it is placed in an ERP system so accurate and clean data going in helps to create a system that can work.
    The Business Analysts (BAs) that are good understand the importance of data migration and have an organized plan to migrate the data, allocate resources, give detailed data maps to the migrators (or help create the maps) and give space estimates to the DBAs. Bad BAs can totally fubar the ERP implementation. If the BAs and management cannot fathom that old data must be mapped to the new system, RUN AWAY. The project will fail.
    Check these links
    http://pdf.me.uk/informatica/AAHN/INFDI11.pdf
    http://researchcenter.line56.com/search/keyword/line56/Edwards%20Sap%20Migration%20Solutions/Edwards%20Sap%20Migration%20Solutions
    http://resources.crmbuyer.com/search/keyword/crmbuyer/Scm%20Data%20Migration%20On%20Peoplesoft%20Peoplesoft%20Data%20Migration/Scm%20Data%20Migration%20On%20Peoplesoft%20Peoplesoft%20Data%20Migration
    Good Luck and Thanks
    AK

  • Data Migration from R3 to new ECC System

    Hello,
    We are doing a fresh implementation for SAP MDM. Currently we have 3 SAP R/3 systems and 1 non-R3 system (BPCS system). One of the project goals is to do data migration from all these 4 systems into a new SAP ECC system and to MDM for Vendor Master, Customer Master and Material Master. My manager says that we need Business Objects tool to Migrate these data. But, my question is that is it not possible to achive this through XI/PI itself ? Can anyone let me know the entire process in XI/PI as to how do I receive the Idocs from R/3, convert into XML and then send it to the new ECC system in Idoc format ?
    Thks & Rgds,
    Hema

    Hi Gandhi,
    You have SAP MDM, BPC and R/3 systems in your landscape, when you are migrating data to new ECC system, what is the role of mdm, did you moving the same data to MDM to avoid duplicate/redundant data??is there any data migration from R/3 to MDM(any integration required)or MDM to R/3,
    You have to develop different interfaces to transfer data from MDM to ECC, BPC to ECC.definelty you required one middleware, the option definitely SAP PI. it offers very easy of integration between MDM and R/3 system, you can use MDM-PI adapter to connect to directly MDM syndicator file port from there you can pull the XML file and convert it in to IDoc format use Receiver IDoc adapter in PI, the same way we can integrate BPC system with R/3.
    Search in sdn, there are some scenarios integration of R/3 and MDM using PI, refer those links, if still you have any doubts let me know,
    Regards,
    Raj

  • Legacy Data Migration - question on conversion

    Hello All,
    We are trying to build a generic tool which could help the conversion process in data migration.
    For eg, If the material name in legacy starts with AB (AB6790), the same has to be referred in SAP as SQ6790.
    So its replacing initial few characters during the conversion process.
    Like this, I am expected to collect possible scenarios and
    develop a generic tool, which can cover some possible conversion conditions.
    Can you please help me with such scenarios, which you may have come across in project needs.
    Thank you.
    Meenakshi

    Rahul,
    I strongly suggest you do a search in the CRM General & Framework Forum on this topic.  If you are looking for specific objects to migrate there are several posts on the major data elements in crm (transactions, business partners, products).
    In general the technique is to use the LSMW combined with the XIF-IDOC adapter to convert data into the CRM system.
    My blog here will explain the general process:
    /people/stephen.johannes/blog/2005/08/18/external-data-loads-for-crm-40-using-xif-adapter
    Thank you,
    Stephen

  • Data migration ALE or idocs and bapis

    hi ,
    thank you guys for the support.
    i am into a data migration project.
    i need the initial setup for the idocs and bapis.
    i dont know anything about these so can u send me the process for the setup and the data migration process too with idocs and bapis.
    i didnt understand when they asked me if we can data migrate with a ALE, is that the same as using idocs and bapis or is it a different approach.
    u can send me at any inofrmation connected to my eamil addr.
    i would really appreciate that.
    thank you.

    Hi,
    Outbound:
    Step 1. Application document is created when transaction is saved.
    2. Message control is invoked.
    3. Messages are processed by system.
    4. Messages are Edited (if desired).
    5. Output (ALE / EDI) is checked
    6. Validate against Message control record from Partner Profile
    7. Application Document is saved.
    8. Entry NAST table is created for every selected output program
    along with Medium & Timing.
    9. Check for Process Immediately .
    If (yes)
    Determine Processing Program from TNAPR Table.
    ELSE
    Execute RSNASTED Program.
    10. Read Partner Profile to determine Process Code.
    11. Process Code points to the Function Module & Invoked.
    12. IDoc is generated.
    13. Check for ALE Request.
    if (Yes)
    Perform Filters, Conversions, Version Changes etc.
    Else.
    IDoc is stored in DATABASE.
    INBOUND:
    Step 1. EDI Subsystem creates an IDoc file from EDI Messages
    2. Subsystem calls Functional Module EDI_DATA_INCOMING from startRFC program.
    3. Data in Control Record is validate against the Partner Profile.
    4. IDoc is generated in Database and syntax check is carried out.
    5. IDoc file is deleted once file read.
    6. Event PROCESSSTATE REACHED is triggered in Idoc Object Workflow.
    7. Check for Process Immediately.
    If NO
    Execute RBDAPP01 Program
    Else
    Read Process Code from Partner Profile
    Process Code Points to Function Module
    Application Document Posted.
    further help:
    check url
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapgenie.com/ale/configuration.htm
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapdevelopment.co.uk/training
    And also u can get lots of inof from the below link.
    http://www.sapgenie.com/ale/why_ale.htm
    Just follow the procedure
    Sending System(Outbound ALE Process)
    Tcode SALE ? for
    a) Define Logical System
    b) Assign Client to Logical System
    Tcode SM59-RFC Destination
    Tcode BD64 ? Create Model View
    Tcode BD82 ? Generate partner Profiles & Create Ports
    Tcode BD64 ? Distribute the Model view
    Message Type MATMAS
    Tcode BD10 ? Send Material Data
    Tcode WE05 ? Idoc List for watching any Errors
    Receiving System(Inbound ALE )
    Tcode SALE ? for
    a) Define Logical System
    b) Assign Client to Logical System
    Tcode SM59-RFC Destination
    Tcode BD64 ? Check for Model view whether it has distributed or not
    Tcode BD82 -- Generate partner Profiles & Create Ports
    Tcode BD11 Getting Material Data
    Tcode WE05 ? Idoc List for inbound status codes
    ALE IDOC Steps
    Sending System(Outbound ALE Process)
    Tcode SALE ?3 for
    a) Define Logical System
    b) Assign Client to Logical System
    Tcode SM59-RFC Destination
    Tcode BD64 !V Create Model View
    Tcode BD82 !V Generate partner Profiles & Create Ports
    Tcode BD64 !V Distribute the Model view
    This is Receiving system Settings
    Receiving System(Inbound ALE )
    Tcode SALE ?3 for
    a) Define Logical System
    b) Assign Client to Logical System
    Tcode SM59-RFC Destination
    Tcode BD64 !V Check for Model view whether it has distributed or not
    Tcode BD82 -- Generate partner Profiles & Create Ports
    Tcode BD11 Getting Material Data
    Tcode WE05 !V Idoc List for inbound status codes
    Message Type MATMAS
    Tcode BD10 !V Send Material Data
    Tcode WE05 ( )
    The BAPIs Create() and CreateFromData() create an instance of an SAP business object type, for example, a purchase order. These BAPIs are class methods.
    Change( )
    The BAPI Change() changes an existing instance of an SAP business object type, for example, a purchase order. The BAPI Change () is an instance method.
    Delete( ) and Undelete( ) The BAPI Delete() deletes an instance of an SAP business object type from the database or sets a deletion flag.
    The BAPI Undelete() removes a deletion flag. These BAPIs are instance methods.
    Cancel ( ) Unlike the BAPI Delete(), the BAPI Cancel() cancels an instance of a business object type. The instance to be cancelled remains in the database and an additional instance is created and this is the one that is actually canceled. The Cancel() BAPI is an instance method.
    Add<subobject> ( ) and Remove<subobject> ( ) The BAPI Add<subobject> adds a subobject to an existing object inst! ance and the BAPI and Remove<subobject> removes a subobject from an object instance. These BAPIs are instance methods.
    BAPI-step by step
    http://www.sapgenie.com/abap/bapi/example.htm
    just refer to the link below
    http://www.sapmaterial.com/?gclid=CN322K28t4sCFQ-WbgodSGbK2g
    list of all bapis
    http://www.planetsap.com/LIST_ALL_BAPIs.htm
    for BAPI's
    http://www.sappoint.com/abap/bapiintro.pdf
    http://www.sappoint.com/abap/bapiprg.pdf
    http://www.sappoint.com/abap/bapiactx.pdf
    http://www.sappoint.com/abap/bapilst.pdf
    http://www.sappoint.com/abap/bapiexer.pdf
    http://service.sap.com/ale
    http://service.sap.com/bapi
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDAPII/CABFAAPIINTRO.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFABAPIREF/CABFABAPIPG.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCFESDE8/BCFESDE8.pdf
    http://www.planetsap.com/Bapi_main_page.htm
    http://www.topxml.com/sap/sap_idoc_xml.asp
    http://www.sapdevelopment.co.uk/
    http://www.sapdevelopment.co.uk/java/jco/bapi_jco.pdf
    Also refer to the following links..
    www.sap-img.com/bapi.htm
    www.sap-img.com/abap/bapi-conventions.htm
    www.planetsap.com/Bapi_main_page.htm
    www.sapgenie.com/abap/bapi/index.htm
    Checkout !!
    http://searchsap.techtarget.com/originalContent/0,289142,sid21_gci948835,00.html
    http://techrepublic.com.com/5100-6329-1051160.html#
    Example Code
    U need to give the step_nr, item_nr, cond_count and cond_type so the correct conditon will be updated. If no condition exists for the given parameters, a new condition will be created.
    U can find these parameters for a particular condition type in table KONV.
    *& Form saveTransactionJOCR
    text
    --> p1 text
    <-- p2 text
    FORM saveTransactionJOCR .
    data: salesdocument like BAPIVBELN-VBELN,
    order_header_inx like bapisdh1x,
    order_header_in like bapisdh1,
    return type standard table of bapiret2 with header line,
    conditions_in type standard table of bapicond with header line,
    conditions_inx type standard table of bapicondx with header line,
    logic_switch like BAPISDLS,
    step_nr like conditions_in-cond_st_no,
    item_nr like conditions_in-itm_number,
    cond_count like conditions_in-cond_count,
    cond_type like conditions_in-cond_type.
    salesdocument = wa_order_information-VBELN.
    LOGIC_SWITCH-COND_HANDL = 'X'.
    order_header_inx-updateflag = 'U'.
    conditions
    clear conditions_in[].
    clear conditions_inx[].
    clear: step_nr,
    item_nr,
    cond_count,
    cond_type.
    step_nr = '710'.
    item_nr = '000000'.
    cond_count = '01'.
    cond_type = 'ZCP2'.
    CONDITIONS_IN-ITM_NUMBER = item_nr.
    conditions_in-cond_st_no = step_nr.
    CONDITIONS_IN-COND_COUNT = cond_count.
    CONDITIONS_IN-COND_TYPE = cond_type.
    CONDITIONS_IN-COND_VALUE = 666.
    CONDITIONS_IN-CURRENCY = 'EUR'.
    append conditions_in.
    CONDITIONS_INX-ITM_NUMBER = item_nr.
    conditions_inx-cond_st_no = step_nr.
    CONDITIONS_INX-COND_COUNT = cond_count.
    CONDITIONS_INX-COND_TYPE = cond_type.
    CONDITIONS_INX-UPDATEFLAG = 'U'.
    CONDITIONS_INX-COND_VALUE = 'X'.
    CONDITIONS_INX-CURRENCY = 'X'.
    append conditions_inx.
    CALL FUNCTION 'BAPI_SALESORDER_CHANGE'
    EXPORTING
    SALESDOCUMENT = salesdocument
    ORDER_HEADER_IN = order_header_in
    ORDER_HEADER_INX = order_header_inx
    LOGIC_SWITCH = logic_switch
    TABLES
    RETURN = return
    CONDITIONS_IN = conditions_in
    CONDITIONS_INX = conditions_inx
    if return-type ne 'E'.
    commit work and wait.
    endif.
    ENDFORM. " saveTransactionJOCR
    Bdc to Bapi
    The steps to be followed are :
    1. Find out the relevant BAPI (BAPI_SALESORDER_CHANGE for VA02).
    for VA01 use BAPI_SALESORDER_CREATEFROMDAT2
    2. Create a Z program and call the BAPi (same as a Funtion module call).
    2. Now, if you see this BAPi, it has
    -> Importing structures.
    eg: SALESDOCUMENT: this will take the Sales order header data as input.
    -> Tables parameters:
    eg: ORDER_ITEM_IN: this will take the line item data as input.
    Note :
    Only specify fields that should be changed
    Select these fields by entering an X in the checkboxes
    Enter a U in the UPDATEFLAG field
    Always specify key fields when changing the data, including in the checkboxes
    The configuration is an exception here. If this needs to be changed, you need to complete it again fully.
    Maintain quantities and dates in the schedule line data
    Possible UPDATEFLAGS:
    U = change
    D = delete
    I = add
    Example
    1. Delete the whole order
    2. Delete order items
    3. Change the order
    4. Change the configuration
    Notes
    1. Minimum entry:
    You must enter the order number in the SALESDOCUMENT structure.
    You must always enter key fields for changes.
    You must always specify the update indicator in the ORDER_HEADER_INX.
    2. Commit control:
    The BAPI does not run a database Commit, which means that the application must trigger the Commit so that the changes are read to the database. To do this, use the BAPI_TRANSACTION_COMMIT BAPI.
    For further details... refer to the Function Module documentation for the BAPi.
    Bapi to VB(Visual Basic)
    Long back I had used the following flow structure to acheive the same.
    Report -> SM59 RFC destination -> COM4ABAP -> VB.exe
    my report uses the rfc destination to create a COM session with com4abap. com4abap calls the vb.exe and manages the flow of data between sap and vb exe.
    You need to have com4abap.exe
    If com4abap is installed you will find it in sapgui installatin directory , C:\Program Files\SAPpc\sapgui\RFCSDK\com4abap.
    else refer OSS note 419822 for installation of com4abap
    after making the settings in com4abap to point to the vb program and setting up rfc destination in sm59 to point to com4abap session , you can use the following function modules to call the vb code.
    for setting up com4abap and rfc destination please refer to the documentation for com4abap.
    Invoke NEW DCOM session
    call function 'BEGIN_COM_SESSION'
    exporting
    service_dest = service_dest "(this will be a RFC destination created in SM59)
    importing
    worker_dest = worker_dest
    exceptions
    connect_to_dcom_service_failed = 1
    connect_to_dcom_worker_failed = 2
    others = 3.
    call function 'create_com_instance' destination worker_dest
    exporting
    clsid = g_c_clsid
    typelib = g_c_typelib
    importing
    instid = g_f_oid
    exceptions
    communication_failure = 1 message g_f_msg
    system_failure = 2 message g_f_msg
    invalid_instance_id = 3
    others = 4.
    call function 'com_invoke' destination worker_dest
    exporting
    %instid = g_f_oid
    %method = 'UpdatePDF'
    sntemp = g_v_const_filent
    snsysid = sy-sysid
    snflag = 'N'
    tables
    rssaptable = g_t_pdfdetail1
    %return = g_t_pdfdetail1 "t_test
    exceptions
    communication_failure = 1 message g_f_msg
    system_failure = 2 message g_f_msg
    invalid_instance_id = 3
    others = 4.
    then close the com session , using
    FM delete_com_instance
    FM END_COM_SESSION
    Thanks and regards,
    Sarada

  • Data migration from ECC5.0 to ECC6.0

    Hi All,
    Is there a standard SAP utility to migrate the data from ECC5.0 to ECC6.0? Assumption is that all the standard fields and the transactions are same. Good example for this case is standard material master, Purchase order, purchase info record etc.
    Currently I am planning to extract the data from source system (using custom program or table download etc...) and upload the data into target system (using LSMW, eCATT, BDC etc...).
    Is there a standard way to load the data into target system without extraction and upload? Please let me know.
    Thanks
    Nagarajan

    ALE Customizing
    1)     IMG > Application Link Enabling (ALE) > Sending and Receiving  >  logical systems > Define Logical System:  name it XXXXXX
    2)     IMG > Application Link Enabling (ALE) > Sending and Receiving  >  Systems in Network > Asynchronous Processing > Assigning Ports > Define Port: name it XXXXXX   Description:  Files for Migration to YYY
    The port need to be defined beneath FILE
    The IDOC record types for SAP Release 4.x need to be selected
    A physical directory is needed.  One must be able to map this directory with the Windows explorer to copy the file to the network or local drive.
    Function module: EDI_PATH_CREATE_CLIENT_DOCNUM
    In order to prevent unprocessed files being overwritten, you use function modules which generate file or directory names dynamically, that is to say, at runtime.
    3)     IMG > Application Link Enabling (ALE) > Modelling and Implementing Business Processes > Cross-Application Settings > Global Organizational Units > Cross-System Company Codes
    a)     Cross-System Company Codes
    b) Assign Cross-System Company Code to Chart of Accounts
    c) Assign Company Code to Cross-System Company Code
    Cross-system company codes are used in the distribution in financial accounting. There is exactly one central system for each cross-system company code in the distributed environment. One company code has to be assigned to this cross-system company code on each system involved in the distribution.
    When sending an IDoc with company code-dependent data, the company code is replaced with the cross-system company code in all company code fields.
    4)     IMG > Application Link Enabling (ALE) > Modelling and Implementing Business Processes > Maintain Distribution Model and Distribute Views
    Here we need a distribution model
         Structure: model view (call it XXXXXX)
                   Sending system (AAAAAA)
                        Receiving system  (XXXXXX)
    5)     IMG > Application Link Enabling (ALE) > Modelling and Implementing Business Processes > Predefined ALE Business Processes > Logistics > Master Data Distribution > Proposal for distribution model: Customer and vendor masters
    (Beside of customers and vendors, we need to add the message type BOMMAT for material bill of materials and MATMAS for material master to to the distribution model, probably manually in step 4. Depending on further requests for automatic migration the one or other message type may need to be added later )
    6)     IMG > Application Link Enabling (ALE) > Modelling and Implementing Business Processes > Partner Profiles and Time of Processing > Maintain Partner Profile Manually
    Partner profile type/Partner type: LS  logical system
    Partner profile/Partner number: XXXXXX
    Details at Post Processing agent
    Typ: US user
    Agent: JJJJJ
    Lang: EN
    Outbound parameters
    Message type:     ADDR2MAS
                   ADR3MAS
                   ADRMAS
                   MATMAS
                   CREMAS
                   DEBMAS
    Details per message type like this:
    Receiver port: XXXXXXX Output mode: Collect Idocs and Do not start subsystem
    IDOC type:      for     ADDR2MAS   use      ADR2MAS02
                   ADR3MAS          ADR3MAS02
                   ADRMAS          ADRMAS02
                   MATMAS          MATMAS03
                   CREMAS          CREMAS03
                   DEBMAS          DEBMAS05
    Activate syntax check
    7)     Authorization needed to execute Transactions:
    BD12 Send Customers
    BD14 Send vendors
    BD10 Send material
    BD30 Send bill of material
    Depending on future migration requests for other objects we may need some more.

  • Data migration on purchasing info record

    Hi Gurus,
    Where can I find some detail information about how to use program RM06IBI0 via LSMW to carry out data migration on purchasing info record?
    Thanks in advance for your help!

    if you know how to use LSMW, then it does not really matter whether you prepare for loading info records or material masters or any other data.
    this forum has many many threads that have links to LSMW documentation. Search for it if you need explanation on LSMW.
    If you have specific questions to the info record load, then let me know

  • Data Migration examples

    can give some examples on data migration?...thanks.

    Hi Gow.
    Difference Between Batch Input and Call Transaction in BDC
    What is the difference between batch input and call transaction in BDC?
    Session method.
    1) synchronous processing.
    2) can tranfer large amount of data.
    3) processing is slower.
    4) error log is created
    5) data is not updated until session is processed.
    Call transaction.
    1) asynchronous processing
    2) can transfer small amount of data
    3) processing is faster.
    4) errors need to be handled explicitly
    5) data is updated automatically
    Batch Data Communication (BDC) is the oldest batch interfacing technique that SAP provided since the early versions of R/3.   BDC is not a typical integration tool, in the sense that, it can be only be used for uploading data into R/3 and so it is
    not bi-directional. 
    BDC works on the principle of simulating user input for transactional screen, via an ABAP program.
    Typically the input comes in the form of a flat file. The ABAP program reads this file and formats the input data screen by screen into an internal table (BDCDATA). The transaction is then started using this internal table as the input and executed in the background. 
    In ‘Call Transaction’, the transactions are triggered at the time of processing itself and so the ABAP program must do the error handling.  It can also be used for real-time interfaces and custom error handling & logging features. Whereas in
    Batch Input Sessions, the ABAP program creates a session with all the transactional data, and this session can be viewed, scheduled and processed (using Transaction SM35) at a later time. The latter technique has a built-in error processing mechanism too. 
    Batch Input (BI) programs still use the classical BDC approach but doesn’t require an ABAP program to be written to format the BDCDATA. The user has to format the data using predefined structures and store it in a flat file. The BI program then reads this and invokes the transaction mentioned in the header record of the file. 
    Direct Input (DI) programs work exactly similar to BI programs. But the only difference is, instead of processing screens they validate fields and directly load the data into tables using standard function modules. For this reason, DI programs are much faster (RMDATIND - Material Master DI program works at least 5 times faster) than the BDC counterpart and so ideally suited for loading large volume data. DI programs are not available for all application areas. 
    Differences between bdc session method and call transaction method.
    The most important aspects of the batch session interface are: - Asynchronous processing - Transfers data for multiple transactions - Synchronous database update During processing, no transaction is started until the previous transaction has been written to the database. - A batch input processing log is generated for each session - Sessions cannot be generated in parallel 
    The most important aspects of the CALL TRANSACTION USING interface are: - Synchronous processing - Transfers data for a single transaction - Synchronous and asynchronous database updating both possible The program specifies which kind of updating is desired. - Separate LUW for the transaction The system performs a database commit immediately before and after the CALL TRANSACTION USING statement.  - No batch input processing log is generated.
    Explain in detail with example what is batch input session?
    Batch Input Session:
    - It is a sequence of transactions, which is generated when user run a particular program. 
    - It contains the accounting documents that are to be created. The SAP system stores these transactions until you decide to process them online. 
    - It does not update transaction figures until the session has been processed.  Using this technique, you can transfer large amounts of data to the SAP system in a short time.
    Three processing modes of executing Batch Input Session :-
    (1) Run Visibly : You can correct faulty transactions online & work step-by-step through  the transactions not yet executed. 
    (2) Display Errors only : You can correct faulty transactions online.   Transactions not yet executed, but without error, run in the background.
    (3) Run in Background : Recommended by SAP.                                     
    <b>Kindly Reward Points If You Found The Reply Usefull<b>,
    Cheers,
    Chaitanya.

  • Data Migration into Sourcing

    Hi
    i am interested in learning how to migrate data into SAP Sourcing (7.0)
    i have experience of data migration into SAP via LSMW, BDC and Custom upload programs. 
    However i do not have the same experience with SAP Sourcing.
    Do SAP run a course for this?
    or can some point me the direction of Help material/blogs where these detail could be covered.
    i searched SDN and Google, but i am not finding the required information. 
    Thank you for your time.

    Hi Barry
    In e Sourcing also you can follow the same 3 environment scenario (Development, Quality and Production and additional cutover system if needed)  based on SAP project management methodology. This is very similar to the multiple client scenario you have in case of SAP ECC.Here the concept is called multitenancy wherein multiple instances of e sourcing can be deployed in a single installation each having seperate database cluster. I would suggest you to look up multitenancy on forum for reference.
    I dont think there are seperate tools for system rollbacks but database back up can always be taken.Databse rollback would allow you to restore the data to previous date. Apart from that server backup is always an option though used very sparingly. Database backup has served me well in all my deployments so far.
    PI for integration is a good option. Apart from that standard ECC integration package is provided with SAP with proper checks maintained to avoid any data corruption/ data loss issues.
    Hope this helps!
    Regards
    Mudit Saini
    Edited by: Mudit_UCB on Aug 19, 2011 10:43 AM

  • Informix 7.x to Oracle 9i Data migration

    Hi All,
    I'm in the process of migrating the data from Informix 7.X databse to Oracle 9i. I need to migrate data from selected columns and selected tables only from the informix schema.The data migration deals with Huge volumes[ Around 50GB ] of data.
    I need some help regarding
    1. I'm thinking to use Informix Unload Option for data unloading and SQL * loader for loading the data into the database. Is there any other better way.
    2. how to deal with the memory issues during migration process.
    Regards
    Gaurav

    Hi,
    Thanks a ton for the prompt response.
    I'm elploring the usage of Migration Workbench for the migration.But yet don't know the correct way to use it.
    I need some inputs and material to refer from this end.
    Apart from that Regarding memory :
    As I'm dealing with 50GB of data
    1) I want to foresee any problems which i might encounter during the migration process.
    2) Any oracle specific parameters I need to setup to rule out any memory related migration failures.
    3) How can i do the migration in the quickest way?
    Kindly do the needful.
    Regards
    Gaurav Jain

Maybe you are looking for