Training historical records of legacy system

Hi all,
I'm migrating the training history records as a qualification. And the start/end date of given qualification is specified as duration of training.
Is it a good idea? If not, what infotype do you record training historical records from legacy system?
Thank you in advance.
ECTSAKC

Hi ECTSAKC,
I have to create course upload programme for the client. My plan is to upload through LSMW. Created an action in PP03. but when I am executing the transaction I am getting the error as "Infotype 1035 skipped due to lack of authorization". FOllowing is the sequence of actions in action:
ZE
Create Course
1
FW
E
1000
2
ZE
Create Course
40
FW
E
1021
2
ZE
Create Course
50
FW
E
1024
2
ZE
Create Course
60
FW
E
1026
2
ZE
Create Course
100
FW
E
1035
2
ZE
Create Course
123
FW
E
1001
A020
2
D
ZE
Create Course
170
FW
E
1001
A024
2
F
ZE
Create Course
210
FW
E
1001
A036
2
U
ZE
Create Course
250
FW
E
1001
A999
2
O
Pls help.
Thanks
Srinivas Ch

Similar Messages

Upload of historical data from legacy system

Dear forum
We are running standard SOP with transaction MC88 in ECC6.0.
We are doing forecasting on material/plant level, based on historical data (we create the sales plan from transaction MC88).
Now, the problem is that we are introducing new products into SOP, but there is no historical data in SAP for those materials.
Is there any way we can import historical data into SAP from legacy system, so that SOP would take this data into account when calculating the forecast?
Note: we do not want to build anything in flexible planning. Just want to check whether or not it is possible to import historical values from a legacy system, to use as historical data in SAP.
Thanks in advance
Lars

Thanks,
But that will not help us.
Any ohter suggestions out there?

Historically recording events - Training and event management

Hi,
What is meant by historically recording an event?
What is the difference if an event is followed up tcode PV15, and the small check box "Historically record business event" is checked or not checked?
I know it means that no changes can be made to the event once it has been followed up, but that happens even if hte checkbox is not ticked.
So what coule be the difference?
Thanks in advance!!
Regards,
Shreyasi

Hi ,
I am facing this issue in LSMW.
Is there a way to capture the below BDC code in the LSMW recording itself?
Tips,
PERFORM bdc_dynpro      USING 'SAPLRHSV' '1001'.
   PERFORM bdc_field       USING    'BDC_CURSOR'
                                                      'PLOG-PLVAR'.
   PERFORM bdc_field       USING    'BDC_OKCODE'
                                                      '=CONF'.
   PERFORM bdc_field       USING    'PLOG-PLVAR'
                                                      '01'.                               " Current plan

Reg:when i was uploading data from legacy system

Hi All,
it is any Include program
for tcode mpr1
when i was upload the data for forecast values from
legacy system to sap system .
only one record is geting updated
other records are not updateding
i have retun logic like this
code,,,,,,,,
TYPES: BEGIN OF TY_FILE,
        WERKS LIKE MAPR-WERKS,
        MATNR LIKE MAPR-MATNR,
        PRWRT LIKE PROW-PRWRT,
       END OF TY_FILE.
DATA: IT_FILE TYPE STANDARD TABLE OF TY_FILE,
      WA_FILE TYPE TY_FILE.
DATA : IT_MARA LIKE MARA OCCURS 0 WITH HEADER LINE,
       IT_MARC LIKE MARC OCCURS 0 WITH HEADER LINE.
DATA : LV_FILE TYPE STRING.
LV_FILE = I_MPR1USERPAR.
CALL METHOD CL_GUI_FRONTEND_SERVICES=>GUI_UPLOAD
EXPORTING
    FILENAME                = LV_FILE
    FILETYPE                = 'DAT'
    HAS_FIELD_SEPARATOR     = 'X'
CHANGING
    DATA_TAB                = IT_FILE
EXCEPTIONS
    FILE_OPEN_ERROR         = 1
    FILE_READ_ERROR         = 2
    NO_BATCH                = 3
    GUI_REFUSE_FILETRANSFER = 4
    INVALID_TYPE            = 5
    NO_AUTHORITY            = 6
    UNKNOWN_ERROR           = 7
    BAD_DATA_FORMAT         = 8
    HEADER_NOT_ALLOWED      = 9
    SEPARATOR_NOT_ALLOWED   = 10
    HEADER_TOO_LONG         = 11
    UNKNOWN_DP_ERROR        = 12
    ACCESS_DENIED           = 13
    DP_OUT_OF_MEMORY        = 14
    DISK_FULL               = 15
    DP_TIMEOUT              = 16
    NOT_SUPPORTED_BY_GUI    = 17
    ERROR_NO_GUI            = 18
    OTHERS                  = 19
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
             WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
LOOP AT T_ARTICLES.
    CLEAR : IT_MARA,IT_MARC.
    SELECT SINGLE * FROM MARA INTO IT_MARA WHERE MATNR = T_ARTICLES-MATNR.
    SELECT SINGLE * FROM MARC INTO IT_MARC WHERE MATNR = T_ARTICLES-MATNR
                                             AND WERKS = T_ARTICLES-WERKS.
ENDLOOP.
LOOP AT IT_FILE INTO WA_FILE .
CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
    EXPORTING
      INPUT = WA_FILE-MATNR
    IMPORTING
      OUTPUT = WA_FILE-MATNR.
T_FORECAST_VALUES-WERKS = WA_FILE-WERKS.
T_FORECAST_VALUES-MATNR = WA_FILE-MATNR.
T_FORECAST_VALUES-PERKZ = IT_MARC-PERKZ.
T_FORECAST_VALUES-ERTAG = T_ARTICLES-PRDAT_NEW.
T_FORECAST_VALUES-KOPRW = WA_FILE-PRWRT.
T_FORECAST_VALUES-MEINS = IT_MARA-MEINS.
APPEND T_FORECAST_VALUES.
CLEAR : T_FORECAST_VALUES.
ENDLOOP.
thanks
mars

For creating/uploading the master data from legacy system to SAP we either use below options
1. BDC (recording)
2. BAPI
3. ALE iDoc.
I would sugguest you to use BAPI and there's already this post which explains few details about the BAPI:
Problems with BAPI_PROJECT_MAINTAIN
Regards
Sreenivas

Upload MR results which already billed from Legacy System to SAP

Hello Experts,
We want to implement ISU-Water .
Before Implementing SAP, we want to Upload Last Year's MR results (From the Previous system..) ,to let SAP use these results as a basis for Estimation.
To have these Meter Readings in DB tables, I probably need to start scheduling 1 year before the actual start of Using SAP,then I will Create Meter Reading Orders and Upload the MR Results, but:
I don't want to Bill these MR results,because they already billed in legacy system.
How can I perform this ?
Thank you very much in advance,
Michael.

Hi,
Historical Profiles is just a profile type used to store past meter data. But to maintain this historical data u need to attach the profile to the installation using load profiles. There is a button on the left top (called load profiles) where you can attach this historical profile to the installation to maintain the historical profile to the installation (similar to updating a operand in installation facts for basic meters)
Use the following path to define a new profile type:
SAP Utilities --> Energy Data Management --> Basic Settings --> Profile Type --> Define Profilet Types
Create a Historical profile in transaction EEDM06 with profile type historical. and upload the historical meter reads to this profile using a program.
Let me know if you need any more information.
Thank you,
Binno Don Thomas

How to transfer data from legacy system to SAP

Hi Friends,
I would like to know the process and the steps followed to transfer data from my legacy system to SAP.
Suppose if i have all the data in the form of Excel sheet or doc type. How can i transfer this data into SAP.
Please explain the steps followed.
Appreciate your help
Anil

Hi ,
Conversion of legacy data into SAP can be uploaded using a standard SAP Tool called LSMW ( TCode:LSMW).
the below link gives a brief explanation of the LSMW tool
http://tutorialsap.com/abap/sap-lsmw-tutorial-with-steps-to-create.html
There are various methods to upload data within LSMW. If the number of records are very high like Article Master or Conditions for Retail the IDOC method must be used.
Standard IDocs
1. Article Master - ARTMAS
2. Conditions - COND_A
3. Source list - SRCLST
4. Customer Master or WRF3/WRF6 tables - DEBMAS
5. Vendor master- CREMAS
Etc. Use transaction code WE60 to see the structure of each of the idocs. New enhancements can be done for the idocs if the required field is not available.
Regards
Prabhu

Data to be fetched from legacy system to SAP and doc needs to bee posted

Hi Experts,
I have a requirement where my client is using some application in Legacy system(Fuel Software) which receives fuel(Petrol, Deasel, CNG) in system and issue the same to company owned vehicles and wants that sap should be integrated and document also needs to be posted in sap for all the receivings and isssuences against their vehicles.
Process Designed is:
1. Required Data file will be picked from legacy system with some date stamp and will be placed in sap directory.
2. There will be batch job which will check for new file based on date stamp.
3. Will pick record n will pass to Goods_mvt_create bapi and then will post the document.
4. We have created Vehicles as Internal orders in sap and whenever any issue will be there internal order no will be captured.
5. By this way we are receiving and issuing in sap.
Now my problem is i am stuck in designing step 1 and rest 2,3,4,5 steps have already been designed and working fine. Need your help in step 1. Else you may suggest some better way-out but again want to mention rest steps are already mapped
Thanks in advance..

Hi Ashutosh,
You can use functions:
FTP_CLIENT_TO_R3
FTP_COMMAND
FTP_COMMAND_LIST
FTP_CONNECT
FTP_COPY
FTP_DISCONNECT
FTP_R3_TO_CLIENT
FTP_R3_TO_SERVER
FTP_SERVER_TO_R3
FTP_START_REG_SERVER
FTP_START_SAPFTP
FTP_STOP_REG_SERVER
FTP_VERSION
which allow you to connect from SAP ERP to any FTP server (if the legacy has it). You can validate the sample program RSFTP007.
Regards,
Juan

Uploading data from Legacy System to SAP (In PS Module)

While Implementing Project system Module, Whether LSMW is applicable for uploading data from Legacy sytem. If not, then what is the method used for uploading the data from Legacy sytsem to SAP

For creating/uploading the master data from legacy system to SAP we either use below options
1. BDC (recording)
2. BAPI
3. ALE iDoc.
I would sugguest you to use BAPI and there's already this post which explains few details about the BAPI:
Problems with BAPI_PROJECT_MAINTAIN
Regards
Sreenivas

Loan upload from legacy system to SAP

Hi Experts,
I have a query regarding uploading Loan from legacy system to SAP.
We are implementing SAP HR for a client going live by 1st jun 2011. The scenario is the client has few employees who have taken loan for various reason, i have configured the same through SPRO....now my query is when i ask the client to provide me with loan data:
1. We are running payroll from 1st April 11, should i ask the client to give me the loan amount as the current standing loan amount
2. when i am uploading loan in 0045, should i put something in third tab payment
Thanks for your support.
Regards,
Jyoti

Hi,
This third tab basically create a record for info type 0078(Loan Payments). If you don't have any records in 3rd tab/0078, system will not start loan recovery in payroll.
Find the response for 2 scenarios-
Scenario 1 & Scenario 2:
maintain these fields in the table control of 3rd tab-
Date(GT_PAYM-ZAHLD) - 01.04.2011....Basically payments and repayments starts date also used for interest calculation
PmntTyp(GT_PAYM-ZAHLA) - 100(Loan payment (external)) ....Contains information on the direction and method of payment. Also control wage type generation in loan PCR and Functions
Amount(GT_PAYM-BETRG) - Balance Amount ....The total of payment or repayment amounts which you enter here, may not exceed the amount that you have entered in the Approved loan amount field on the Basic data tab page ....For your both of the scenariof, this amount will be same.
Regards.
Suman
Edited by: suman poddar on May 22, 2011 10:28 AM

Migration of Business Partner data, from a legacy system, does not work

Hi All,
We use a non-SAP application where our customers sign a loyalty program. The database created is replicated to CRM 7.0. However, when we create the Target Group in the Web Client UI, the number of Business Partner in CRM is different from the number of BP registered in the legacy system.
Any comment can be helpfull.!
Regards
Marí

Maria,
Please explain the way the data has been replicated,,, ( Errors in few records - answer to the mystery)
Is there any segmentation basis used while creating the target group? ( Segmentation Basis - answer to the mystery)
What are the data sources used for segmentation? ( Different query settings - answer to the mystery)
Regards,
Piyush

Upload vendor master data from legacy system to internal table tcode xk01

through batch input program how to upload vendor master data from legacy system to internal table and then to SAP R/3 database(transaction XK01) by using recording method.

By learning the basics of BDC recording and the use of GUI_UPLOAD

GRC 10 - Risk Analysis in legacy system

Hi everybody,
I have a problem with legacy connectors in GRC 10. I implemented the note 1594963. So, I created the legacy files and storage it in GRC server.
When I run the user synch, the legacy connector only synch the first record.
Someone can help me? Someone did implement a risk analysis for legacy systems?
Regards,

Hi Claudio Ekel
Can you share some inputs on the Legacy Risk Analysis.
We have configured the Legacy Connector as per the note 1594963 ; Placed the files on the server & tried running Synchronization Jobs. But the data is not getting uploaded to GRC10 .
We made sure that text files are in UTF-8 format
Is it mandatory to load all the 11 files that are provided in the note 1594963? We have excluded the Profile related files
Can you share a sample of Legacy file formats that you have used for the sync.
Can you throw some light on what could be the possible issues for data not getting uplaoded to GRC10?
Regards,
Pavan Muthyala

Pull the data from legacy System into report and display with SAP data

Hi Friends,
My requirement is-
Create report by processing data from SAP tables and prepare output.And Before displaying the output, I have to pull the data from non-sap system which is readymade (It will come as flat file with similar fields as Report structure has) and finally display the records from both SAP and Legacy System by filtering duplicates.

Steps:-
Define the file path on selection screen:-
Selection screen data
    select-options   (s_)
      parameters     (p_)
      radio buttons (r_)
      checkboxes     (x_)
      pushbuttons    (b_)
SELECTION-SCREEN BEGIN OF BLOCK block1 WITH FRAME TITLE text-f01.
parameter:    p_file    type text_512 obligatory.
Start-of-selection.
data : l_fname type string. " File Name
l_fname = p_file .
call function 'GUI_UPLOAD'
    exporting
      filename                = l_fname
      filetype                = 'ASC'
      has_field_separator     = '#'
    tables
      data_tab                = lt_data
    exceptions
      file_open_error         = 1
      file_read_error         = 2
      no_batch                = 3
      gui_refuse_filetransfer = 4
      invalid_type            = 5
      no_authority            = 6
      unknown_error           = 7
      bad_data_format         = 8
      header_not_allowed      = 9
      separator_not_allowed   = 10
      header_too_long         = 11
      unknown_dp_error        = 12
      access_denied           = 13
      dp_out_of_memory        = 14
      disk_full               = 15
      dp_timeout              = 16
      others                  = 17.
if sy-subrc <> 0.
    message e000 with 'Unable to upload file from the PC'(t13).
endif.
lt_data is of same structure as the fields in the file.
For filtering duplicates:-
delete adjacent duplicates from lt_data.
Now display the records using either ALV or using write statements.
You can display the records in any of the way you want.

Uploading data from Legacy system

Hi
i am shorthly going to work on data migration project. I have never worked on a data migration project and want to know the answers for the following questions.
1] which technique i must first consider in data upload ( both master data and transaction data )
2] What steps are involved?
3] I know we can use LSMW, BAPI's , BDC , Direct Input , IDOC etc but want to know which one choose and when?
4] What care must be taken in each data migration
5] is there is std list of programs or a good document on when to choose what?
~SR

Hi,
Data migration can be done by the follwoing methods:
LSMW : for master data migartion or small data migartion
BAPI : its just like a FM , thru which u can create master aswell as Transactional data.
u have to import some paremetre as well as tables if required, and Bapi will RETURN the message saying so and so material/delievry had cretaed.
BDC : in BDC we got 2 methods.
CAll transaction and session.
CAll transacton : using this u can uplaod transcational data as well as master data.
the updation can be synchronus or asynchronus updates.
Session: using this u can uplaod transcational data as well as master data.
The updation in session is synchronus, so its time taking process.
Most of the time we go for Call transcation In real situations.
Dircet input method: its out dated.no longer it is being used.
in all the above cases, data is alraedy existing in flat file and u r going to migrate the data in one shot but IDOC is used where the dynamical data migration is necessary.
suppose say ones the material is craeted in legacy sytem , that particulat matreial shud be migarted to R/3.this can be handled thru IDOC.
Idoc: master data as well as Trnascational data is migarted thru IDOC( matmas, orders).
Idoc uses ALE technology in migartion of idoc.
Revert back if any issues.
Check these links.
SAP Data Migration with LSMW
http://www.sap-img.com/sap-data-migration.htm
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
LSMW
No ABAP effort are required for the SAP data migration. However, effort are required to map the data into the structure according to the pre-determined format as specified by the pre-written ABAP upload program of the LSMW.
The Legacy System Migration Workbench (LSMW) is a tool recommended by SAP that you can use to transfer data once only or periodically from legacy systems into an R/3 System.
More and more medium-sized firms are implementing SAP solutions, and many of them have their legacy data in desktop programs. In this case, the data is exported in a format that can be read by PC spreadsheet systems. As a result, the data transfer is mere child's play: Simply enter the field names in the first line of the table, and the LSM Workbench's import routine automatically generates the input file for your conversion program.
The LSM Workbench lets you check the data for migration against the current settings of your customizing. The check is performed after the data migration, but before the update in your database.
So although it was designed for uploading of legacy data it is not restricted to this use.
We use it for mass changes, i.e. uploading new/replacement data and it is great, but there are limits on its functionality, depending on the complexity of the transaction you are trying to replicate.
The SAP transaction code is 'LSMW' for SAP version 4.6x.
For those with the older SAP version (4.7 and below), the data migration programs might not have been pre-loaded.
You can download the LSMW at no cost from SAPNet under Services, SAP Methodology and Tools, category Tools.
If you are an existing SAP customer with an OSS ID, you can access the SAP Service Marketplace to download the LSWM for your Basis teams to install to your SAP system: http://service.sap.com/lsmw
The LSM Workbench carries out the following tasks:
Reads the transfer data from one or more files (for example, spreadsheets, sequential files etc.)
Converts the data from the source format into the target format
Note that with background processing, the input file must not be located in the presentation server. Access to presentation server files is only possible when you are working onlineUpload Condition Pricing
LSMW STEPS
Data Cleansing
Data cleansing allows you to compare, include and merge redundant business partner master records (potential duplicates) in data cleansing cases. Following the data cleansing process you can remove data records from the system using archiving.
Integration
Before you can carry out data cleansing, you must determine the redundant data in your system and include it in data cleansing cases.
You have the following options for duplicate recognition and creation of data cleansing cases.
The Business Address Services (BAS) provide interfaces for integrating the relevant external software (search machines).
User-defined programs
Services of data providers, who check their data for possible duplicates.
In the options described above, the data cleansing cases are created via the system and put into the data cleansing worklist for further processing.
In individual cases you can find potential business partner duplicates in the hitlist of the business partner search and create a separate data cleansing case.
After connecting the non-SAP software (search engines), the system starts duplicate recognition (Delta Scan) with every change to or new entry of a business partner for this specific individual record. You should do a full scan through the complete dataset at the beginning of the consolidation process using the non-SAP software, this registers all potential duplicates in data cleansing cases and makes them available or further processing.
Within the application basis, the referencing objects, which are taken into account by the data cleansing, are limited to the sub-objects of the business partner. You have the possibility to make modification-free enhancements to the referencing objects.
Prerequisites
You must have determined the redundant data records in your system.
To use the interface of the Business Address Services, make the following Customizing settings: SAP Implementation Guide -> Basis -> Basis Services -> Address Management -> Activate Duplicate Check Index Pool
Make the following system settings in the IMG of the SAP Business Partner: Basic Settings -> Data Cleansing -> Maintain Number Range / Define Priorities / Activate Data Cleansing.
Activities
Register data cleansing cases via BAPIs or create them in the dialog for business partner maintenance from the worklist or the business partner search.
Process the created data cleansing cases in a separate process step afterwards.
BATCH DATA COMMUNICATION
About Data Transfer In R/3 System
When a company decides to implement the SAP R/3 to manage business-critical data, it usually does not start from a no-data situation. Normally, a SAP R/3 project comes into replace or complement existing application.
In the process of replacing current applications and transferring application data, two situations might occur:
The first is when application data to be replaced is transferred at once, and only once.
The second situation is to transfer data periodically from external systems to SAP and vice versa.
There is a period of time when information has to be transferred from existing application, to SAP R/3, and often this process will be repetitive.
The SAP system offers two primary methods for transferring data into SAP systems. From non-SAP systems or legacy system. These two methods are collectively called batch input or batch data communication.
1. SESSION METHOD
2. CALL TRANSACTION
3. DIRECT INPUT
Advantages offered by BATCH INPUT method:
1. Can process large data volumes in batch.
2. Can be planned and submitted in the background.
3. No manual interaction is required when data is transferred.
4. Data integrity is maintained as whatever data is transferred to the table is through transaction. Hence batch input data is submitted to all the checks and validations.
To implement one of the supported data transfers, you must often write the program that exports the data from your non-SAP system. This program, known as a data transfer program must map the data from the external system into the data structure required by the SAP batch input program.
The batch input program must build all of the input to execute the SAP transaction.
Two main steps are required:
To build an internal table containing every screen and every field to be filled in during the execution of an SAP transaction.
To pass the table to SAP for processing.
Prerequisite for Data Transfer Program
Writing a Data Transfer Program involves following prerequisites:
Analyzing data from local file
Analyzing transaction
Analyzing transaction involves following steps:
The transaction code, if you do not already know it.
Which fields require input i.e., mandatory.
Which fields can you allow to default to standard values.
The names, types, and lengths of the fields that are used by a transaction.
Screen number and Name of module pool program behind a particular transaction.
To analyze a transaction::
Start the transaction by menu or by entering the transaction code in the command box.
(You can determine the transaction name by choosing System Status.)
Step through the transaction, entering the data will be required for processing your batch input data.
On each screen, note the program name and screen (dynpro) number.
(dynpro = dyn + pro. Dyn = screen, pro = number)
Display these by choosing System Status. The relevant fields are Program (dynpro) and Dynpro number. If pop-up windows occur during execution, you can get the program name and screen number by pressing F1 on any field or button on the screen.
The technical info pop-up shows not only the field information but also the program and screen.
For each field, check box, and radio button on each screen, press F1 (help) and then choose Technical Info.
Note the following information:
- The field name for batch input, which youll find in its own box.
The length and data type of the field. You can display this information by double clicking on the Data Element field.
Find out the identification code for each function (button or menu) that you must execute to process the batch-input data (or to go to new screen).
Place the cursor on the button or menu entry while holding down the left mouse button. Then press F1.
In the pop-up window that follows, choose Technical info and note the code that is shown in the Function field.
You can also run any function that is assigned to a function key by way of the function key number. To display the list of available function keys, click on the right mouse button. Note the key number that is assigned to the functions you want to run.
Once you have program name, screen number, field name (screen field name), you can start writing.
DATA TRANSFER program.
Declaring internal table
First Integral Table similar to structure like local file.
Declaring internal table like BDCDATA
The data from internal table is not transferred directly to database table, it has to go through transaction. You need to pass data to particular screen and to particular screen-field. Data is passed to transaction in particular format, hence there is a need for batch input structure.
The batch input structure stores the data that is to be entered into SAP system and the actions that are necessary to process the data. The batch input structure is used by all of the batch input methods. You can use the same structure for all types of batch input, regardless of whether you are creating a session in the batch input queue or using CALL TRANSACTION.
This structure is BDCDATA, which can contain the batch input data for only a single run of a transaction. The typical processing loop in a program is as follows:
Create a BDCDATA structure
Write the structure out to a session or process it with CALL TRANSACTION USING; and then
Create a BDCDATA structure for the next transaction that is to be processed.
Within a BDCDATA structure, organize the data of screens in a transaction. Each screen that is processed in the course of a transaction must be identified with a BDCDATA record. This record uses the Program, Dynpro, and Dynbegin fields of the structure.
The screen identifier record is followed by a separate BDCDATA record for each value, to be entered into a field. These records use the FNAM and FVAL fields of the BDCDATA structure. Values to be entered in a field can be any of the following:
Data that is entered into screen fields.
Function codes that are entered into the command field. Such function codes execute functions in a transaction, such as Save or Enter.
The BDCDATA structure contains the following fields:
PROGRAM: Name of module pool program associated with the screen. Set this field only for the first record for the screen.
DYNPRO: Screen Number. Set this field only in the first record for the screen.
DYNBEGIN: Indicates the first record for the screen. Set this field to X, only for the first record for the screen. (Reset to (blank) for all other records.)
FNAM: Field Name. The FNAM field is not case-sensitive.
FVAL: Value for the field named in FNAM. The FVAL field is case-sensitive. Values assigned to this field are always padded on the right, if they are less than 132 characters. Values must be in character format.
Transferring data from local file to internal table
Data is uploaded to internal table by UPLOAD of WS_UPLOAD function.
Population of BDCDATA
For each record of internal table, you need to populate Internal table, which is similar to BDCDATA structure.
All these five initial steps are necessary for any type of BDC interface.
DATA TRANSFER program can call SESSION METHOD or CALL TRANSACTION. The initial steps for both the methods are same.
First step for both the methods is to upload the data to internal table. From Internal Table, the data is transferred to database table by two ways i.e., Session method and Call transaction.
SESSION METHOD
About Session method
In this method you transfer data from internal table to database table through sessions.
In this method, an ABAP/4 program reads the external data that is to be entered in the SAP System and stores the data in session. A session stores the actions that are required to enter your data using normal SAP transaction i.e., Data is transferred to session which in turn transfers data to database table.
Session is intermediate step between internal table and database table. Data along with its action is stored in session i.e., data for screen fields, to which screen it is passed, the program name behind it, and how the next screen is processed.
When the program has finished generating the session, you can run the session to execute the SAP transactions in it. You can either explicitly start and monitor a session or have the session run in the background processing system.
Unless session is processed, the data is not transferred to database table.
BDC_OPEN_GROUP
You create the session through program by BDC_OPEN_GROUP function.
Parameters to this function are:
User Name: User name
Group: Name of the session
Lock Date: The date on which you want to process the session.
Keep: This parameter is passed as X when you want to retain session after
processing it or to delete it after processing.
BDC_INSERT
This function creates the session & data is transferred to Session.
Parameters to this function are:
Tcode: Transaction Name
Dynprotab: BDC Data
BDC_CLOSE_GROUP
This function closes the BDC Group. No Parameters.
Some additional information for session processing
When the session is generated using the KEEP option within the BDC_OPEN_GROUP, the system always keeps the sessions in the queue, whether it has been processed successfully or not.
However, if the session is processed, you have to delete it manually. When session processing is completed successfully while KEEP option was not set, it will be removed automatically from the session queue. Log is not removed for that session.
If the batch-input session is terminated with errors, then it appears in the list of INCORRECT session and it can be processed again. To correct incorrect session, you can analyze the session. The Analysis function allows to determine which screen and value has produced the error. If you find small errors in data, you can correct them interactively, otherwise you need to modify batch input program, which has generated the session or many times even the data file.
CALL TRANSACTION
About CALL TRANSACTION
A technique similar to SESSION method, while batch input is a two-step procedure, Call Transaction does both steps online, one after the other. In this method, you call a transaction from your program by
Call transaction <tcode> using <BDCTAB>
Mode <A/N/E>
Update <S/A>
Messages into <MSGTAB>.
Parameter 1 is transaction code.
Parameter 2 is name of BDCTAB table.
Parameter 3 here you are specifying mode in which you execute transaction
A is all screen mode. All the screen of transaction are displayed.
N is no screen mode. No screen is displayed when you execute the transaction.
E is error screen. Only those screens are displayed wherein you have error record.
Parameter 4 here you are specifying update type by which database table is updated.
S is for Synchronous update in which if you change data of one table then all the related Tables gets updated. And sy-subrc is returned i.e., sy-subrc is returned for once and all.
A is for Asynchronous update. When you change data of one table, the sy-subrc is returned. And then updating of other affected tables takes place. So if system fails to update other tables, still sy-subrc returned is 0 (i.e., when first table gets updated).
Parameter 5 when you update database table, operation is either successful or unsuccessful or operation is successful with some warning. These messages are stored in internal table, which you specify along with MESSAGE statement. This internal table should be declared like BDCMSGCOLL, a structure available in ABAP/4. It contains the following fields:
1. Tcode: Transaction code
2. Dyname: Batch point module name
3. Dynumb: Batch input Dyn number
4. Msgtyp: Batch input message type (A/E/W/I/S)
5. Msgspra: Batch input Lang, id of message
6. Msgid: Message id
7. MsgvN: Message variables (N = 1 - 4)
For each entry, which is updated in database, table message is available in BDCMSGCOLL. As BDCMSGCOLL is structure, you need to declare a internal table which can contain multiple records (unlike structure).
Steps for CALL TRANSACTION method
1. Internal table for the data (structure similar to your local file)
2. BDCTAB like BDCDATA
3. UPLOAD or WS_UPLOAD function to upload the data from local file to itab. (Considering file is local file)
4. Loop at itab.
Populate BDCTAB table.
Call transaction <tcode> using <BDCTAB>
Mode <A/N/E>
Update <S/A>.
Refresh BDCTAB.
Endloop.
(To populate BDCTAB, You need to transfer each and every field)
The major differences between Session method and Call transaction are as follows:
SESSION METHOD CALL TRANSACTION
1. Data is not updated in database table unless Session is processed. Immediate updation in database table.
2. No sy-subrc is returned. Sy-subrc is returned.
3. Error log is created for error records. Errors need to be handled explicitly
4. Updation in database table is always synchronous Updation in database table can be synchronous Or Asynchronous.
Error Handling in CALL TRANSACTION
When Session Method updates the records in database table, error records are stored in the log file. In Call transaction there is no such log file available and error record is lost unless handled. Usually you need to give report of all the error records i.e., records which are not inserted or updated in the database table. This can be done by the following method:
Steps for the error handling in CALL TRANSACTION
1. Internal table for the data (structure similar to your local file)
2. BDCTAB like BDCDATA
3. Internal table BDCMSG like BDCMSGCOLL
4. Internal table similar to Ist internal table
(Third and fourth steps are for error handling)
5. UPLOAD or WS_UPLOAD function to upload the data from the local file to itab. (Considering file is local file)
6. Loop at itab.
Populate BDCTAB table.
Call transaction <tr.code> using <Bdctab>
Mode <A/N/E>
Update <S/A>
Messages <BDCMSG>.
Perform check.
Refresh BDCTAB.
Endloop.
7 Form check.
IF sy-subrc 0. (Call transaction returns the sy-subrc if updating is not successful).
Call function Format_message.
(This function is called to store the message given by system and to display it along with record)
Append itab2.
Display the record and message.
DIRECT INPUT
About Direct Input
In contrast to batch input, this technique does not create sessions, but stores the data directly. It does not simulate the online transaction. To enter the data into the corresponding database tables directly, the system calls a number of function modules that execute any necessary checks. In case of errors, the direct input technique provides a restart mechanism. However, to be able to activate the restart mechanism, direct input programs must be executed in the background only. Direct input checks the data thoroughly and then updates the database directly.
You can start a Direct Input program in two ways;
Start the program directly
This is the quickest way to see if the program works with your flat file. This option is possible with all direct input programs. If the program ends abnormally, you will not have any logs telling you what has or has not been posted. To minimize the chance of this happening, always use the check file option for the first run with your flat file. This allows you to detect format errors before transfer.
Starting the program via the DI administration transaction
This transaction restarts the processing, if the data transfer program aborts. Since DI document are immediately posted into the SAP D/B, the restart option prevents the duplicate document posting that occurs during a program restart (i.e., without adjusting your flat file).
Direct input is usually done for standard data like material master, FI accounting document, SD sales order and Classification for which SAP has provided standard programs.
First time you work with the Direct Input administration program, you will need to do some preparation before you can transfer data:
- Create variant
Define job
Start job
Restart job
Common batch input errors
- The batch input BDCDATA structure tries to assign values to fields which do not exist in the current transaction screen.
The screen in the BDCDATA structure does not match the right sequence, or an intermediate screen is missing.
On exceptional occasions, the logic flow of batch input session does not exactly match that of manual online processing. Testing the sessions online can discover by this.
The BDCDATA structure contains fields, which are longer than the actual definition.
Authorization problems.
RECORDING A BATCH INPUT
A B recording allows you to record a R/3 transaction and generate a program that contains all screens and field information in the required BDC-DATA format.
You can either use SHDB transaction for recording or
EDIT BATCH INPUT  SERVICES SYSTEM
And from here click recording.
Enter name for the recording.
(Dates are optional)
Click recording.
Enter transaction code.
Enter.
Click Save button.
You finally come to a screen where, you have all the information for each screen including BDC_OKCODE.
Click Get Transaction.
Return to BI.
Click overview.
Position the cursor on the just recorded entry and click generate program.
Enter program name.
Click enter
The program is generated for the particular transaction.
BACKGROUND PROCESSING
Need for Background processing
When a large volume of data is involved, usually all batch inputs are done in background.
The R/3 system includes functions that allow users to work non-interactively or offline. The background processing systems handle these functions.
Non-interactively means that instead of executing the ABAP/4 programs and waiting for an answer, user can submit those programs for execution at a more convenient planned time.
There are several reasons to submit programs for background execution.
The maximum time allowed for online execution should not exceed 300 seconds. User gets TIMEOUT error and an aborted transaction, if time for execution exceeds 300 seconds. To avoid these types of error, you can submit jobs for background processing.
You can use the system while your program is executing.
This does not mean that interactive or online work is not useful. Both type of processing have their own purposes. Online work is the most common one entering business data, displaying information, printing small reports, managing the system and so on. Background jobs are mainly used for the following tasks; to process large amount of data, to execute periodic jobs without human intervention, to run program at a more convenient, planned time other than during normal working hours i.e., Nights or weekends.
The transaction for background processing is SM36.
Or
Define jobs Jobs  Administration Tools
Or
System Jobsservices
Components of the background jobs
A job in Background processing is a series of steps that can be scheduled and step is a program for background processing.
Job name. Define the name of assigned to the job. It identifies the job. You can specify up to 32 characters for the name.
Job class. Indicates the type of background processing priority assigned to the job.
The job class determines the priority of a job. The background system admits three types of job classes: A B & C, which correspond to job priority.
Job steps. Parameters to be passed for this screen are as follows:
Program name.
Variant if it is report program
Start criteria for the job: Option available for this are as follows:
Immediate - allows you to start a job immediately.
Date/Time - allows you to start a job at a specific name.
After job - you can start a job after a particular job.
After event - allows you to start a job after a particular event.
At operation mode - allows you to start a job when the system switches to a particular operation mode.
Defining Background jobs
It is two step process: Firstly, you define the job and then release it.
When users define a job and save it, they are actually scheduling the report i.e., specifying the job components, the steps, the start time.
When users schedule program for background processing, they are instructing the system to execute an ABAP/4 report or an external program in the background. Scheduled jobs are not executed until they are released. When jobs are released, they are sent for execution to the background processing system at the specified start time. Both scheduling and releasing of jobs require authorizations.
HANDLING OF POP UP SCREEN IN BDC
Many times in transaction pop up screen appears and for this screen you dont pass any record but some indication to system telling it to proceed further. For example: The following screen
To handle such screen, system has provided a variable called BDC_CURSOR. You pass this variable to BDCDATA and process the screen.
Usually such screen appears in many transactions, in this case you are just passing information, that YES you want to save the information, that means YES should be clicked. So you are transferring this information to BDCDATA i.e., field name of YES which is usually SPOT_OPTION. Instead of BDC_OKCODE, you are passing BDC_CURSOR.
BDC_CURSOR is also used to place cursor on particular field.
AN EXAMPLE WITH SESSION METHOD
Following program demonstrates how data is passed from flat file to SAP transaction and further to database table by using SESSION method.
The transaction is TFBA (to change customer).
A simple transaction where you are entering customer number on first screen and on next screen data is displayed for the particular customer number. Field, which we are changing here, are name and city. When you click on save, the changed record gets saved.
Prerequisite to write this BDC interface as indicated earlier is:
1. To find screen number
2. To find screen field names, type of the field and length of the field.
3. To find BDC_OKCODE for each screen
4. Create flat file.
Flat file can be created in your hard disk as follows:
1 Vinod Krishna Hyderabad
2 Kavitha Secunderabad
3 Kishore Hyderabad
(Where 1st character field is Customer number, 2nd field is Customer name and 3rd field is City.)
To transfer this data to database table SCUSTOM following interface can be used.
REPORT DEMO1.
Following internal table is to upload flat file.
DATA: BEGIN OF ITAB OCCURS 0,
ID(10),
NAME(25),
CITY(25),
END OF ITAB.
*Following internal table BDCDATA is to pass date from internal table to session.
DATA: BDCTAB LIKE BDCDATA OCCURS 0 WITH HEADER LINE.
Variables
DATA: DATE1 LIKE SY-DATUM. DATE1 = SY-DATUM - 1. This is for Hold Date
To upload flat file to internal table.
CALL FUNCTION UPLOAD
EXPORTING
FILE NAME = C:FF.TXT
FILE TYPE = ASC
TABLES
DATA_TAB = ITAB
EXCEPTIONS
CONVERSION_ERROR = 1
INVALID_TABLE_WIDTH = 2
INVALID_TYPE = 3
NO_BATCH = 4
UNKNOWN_ERROR = 5
OTHERS = 6.
If sy-subrc = 0.
Calling Function to Create a Session
CALL FUNCTION BDC_OPEN_GROUP
EXPORTING
CLIENT = SY-MANDT
GROUP = POTHURI
HOLDDATE = DATE1
KEEP = X
USER = SY-UNAME
EXCEPTIONS
CLIENT_INVALID = 1
DESTINATION_INVALID = 2
GROUP_INVALID = 3
GROUP_IS_LOCKED = 4
HOLDDATE_INVALID = 5
INTERNAL_ERROR = 6
QUEUE_ERROR = 7
RUNNING = 8
SYSTEM_LOCK_ERROR = 9
USER_INVALID = 10
OTHERS = 11.
If sy-subrc = 0.
*-- MAIN Logic--
LOOP AT ITAB
PERFORM GENERATE_DATA. Populating BDCDATA Table
CALL FUNCTION BDC_INSERT
EXPORTING
TCODE = TFBA
TABLES
DYNPROTAB = BDCTAB
EXCEPTIONS
INTERNAL_ERROR = 1
NOT_OPEN = 2
QUEUE_ERROR = 3
TCODE_INVALID = 4
PRINTING_INVALID = 5
POSTING_INVALID = 6
OTHERS = 7.
REFRESH BDCTAB
ENDLOOP.
Calling function to close the session
CALL FUNCTION BDC_CLOSE_GROUP
EXCEPTIONS
NOT_OPEN = 1
QUEUE_ERROR = 2
OTHERS = 3.
Endif.
Endif.
*& Form GENERATE_DATA
Create BDC Data
FORM GENERATE_DATA
Passing information for 1st screen on BDCDATA
BDCTAB-PROGRAM = SAPMTFBA.
BDCTAX-DYNPRO = 100.
BDCTAP-DYNBEGIN = X.
APPEND BCDTAB.CLEAR BDCTAB.
Passing field information to BDCDATA
BDCTAB-FNAM = SCUSTOM-ID
BDCTAB-FVAL = ITAB-ID.
APPEND BDCTAB.CLEAR BDCTAB.
Passing BDC_OKCODE to BDCDATA
BDCTAB-FNAM = BDC_OKCODE.
BDCTAB-FVAL = /5.
APPEND BDCTAB.CLEAR BDCTAB.
Passing screen information for next screen to BDCDATA
BDCTAB-PROGRAM = SAPMTFBA.
BDCTAB-DYNPRO = 200.
BDCTAB-DYNBEGIN = X.
APPEND BDCTAB.CLEAR BDCTAB.
Passing screen information to BDCDATA
BDCTAB-FNAM = SCUSTOM-NAME.
BDCTAB-FVAL = ITAB-NAME.
APPEND BDCTAB.CLEAR BDCTAB.
Passing screen information to BDCDATA
BDCTAB-FNAM = SCUSTOM-CITY.
BDCTAB-FVAL = ITAB-CITY.
APPEND BDCTAB.CLEAR BDCTAB.
Passing BDC_OKCODE to BDCDATA
BDCTAB-FNAM = BDC_OKCODE.
BDCTAB-FVAL = SAVE.
APPEND BDCTAB.CLEAR BDCTAB.
ENDFORM. GENERATE_DATA
AN EXAMPLE WITH CALL TRANSACTION
Same steps to be repeated for CALL TRANSACTION
The only difference between the two types of interface is in Session method, you create session and store information about screen and data into session. When session is processed the data is transferred to database. While in CALL TRANSACTION, data is transferred directly to database table.
REPORT DEMO1.
Follow above Code till MAIN Logic. Even the Subroutine should be copied
LOOP AT ITAB
PERFORM GENERATE_DATA, Populating BDCDATA Table
Call transaction TFBA using BCDDATA Mode A Update S.
REFRESH BDCTAB
ENDLOOP.
check this link:
http://www.sap-img.com/abap/learning-bdc-programming.htm
http://www.sap-img.com/bdc.htm
www.sappoint.com/abap/bdcconcept.pdf
www.sap-img.com/abap/learning-bdc-programming.htm
www.sap-img.com/abap/question-about-bdc-program.htm
www.sapdevelopment.co.uk/bdc/bdchome.htm
www.planetsap.com/bdc_main_page.htm
Re: bdc mm01
http://www.sapbrain.com/TUTORIALS/TECHNICAL/BDC_tutorial.html
http://www.sap-img.com/abap/bdc-example-using-table-control-in-bdc.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/fa/097119543b11d1898e0000e8322d00/frameset.htm
http://myweb.dal.ca/hchinni/sap/bdc_home.htm
IDOC
What is IDOC ?
IDoc
Standard SAP format for electronic data interchange between systems (Intermediate Document). Different message types (such as delivery confirmations or purchase orders) normally represent different specific formats, the IDoc types. However, multiple message types with related content can be assigned to one IDoc type: For example, the IDoc type ORDERS01 transfers the logical message types ORDERS (purchase order) and ORDRSP (order confirmation).
Also check these link it will help you.
idoc information
http://help.sap.com/saphelp_nw2004s/helpdata/en/78/21785851ce11d189570000e829fbbd/frameset.htm
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/sapR3%28Idocs%29ToXI--Steps+Summarized&
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
ALE/ IDOC/ XML
Troubleshooting of ALE Process - /people/raja.thangamani/blog/2007/07/19/troubleshooting-of-ale-process
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://www.thespot4sap.com/Articles/SAP_XML_Business_Integration.asp
http://help.sap.com/saphelp_srm30/helpdata/en/72/0fe1385bed2815e10000000a114084/content.htm
IDOC Convertion
/people/kevin.wilson2/blog/2005/12/07/changing-fields-in-an-idoc-segment
Please check this online document for ALE and IDoc.
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEIO/BCMIDALEIO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDISC/CAEDISCAP_STC.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf
Also check this links for additional information.
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
serialization /people/alessandro.guarneri/blog/2006/11/26/content-based-serialization-dynamic-queue-name-in-xi
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters - IDoc to File
IDOc testing - /people/suraj.sr/blog/2005/12/29/generate-test-case-for-an-idoc-scenario
/people/ravikumar.allampallam/blog/2005/06/24/convert-any-flat-file-to-any-idoc-java-mapping - Any flat file to any Idoc
/people/pooja.pandey/blog/2005/07/27/idocs-multiple-types-collection-in-bpm - Collection of IDoc to Single File
/people/stefan.grube/blog/2006/09/18/collecting-idocs-without-using-bpm - collecting IDocs without BPM
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters - IDoc to File
Hope it will be useful to u....plz don't forget to reward points...!!!!
Regards
Vasu

Listing data from ECC to legacy system??

Hello Experts,
This is my first post and hopefully in the correct forum:
We have a requirement of sending listing data (whether articles is listed or delisted) from ECC to a legacy system. We have analyzed the option os using LIKOND01, Assortment 01or WBBDLD03. We opted for LIKOND01 since it is lighter as compared to WBBDLD03. We tried to find the documents related to both of these IDocs in help.sap etc, but could not find any information accept the header and detail records. We just wanted to know how we can trigger this LIKOND01 IDoc and whether our approach will satisfy our needs.
Any information in this regard will be appreciated.
Thanks in advance!!
Rakesh
Edited by: rakeshjain_hit on Dec 25, 2010 1:10 PM
Edited by: rakeshjain_hit on Dec 29, 2010 1:17 PM

Hello Venu,
Thanks for your reply.
LIKOND01.
We will activate the necessary change pointers and other configurations.
What we want to know that once the change pointers are activated the LIOKOND01 IDoc will be created as soon as the listing is done in ECC and entry created in WLK1 or we have to use some t-code. Can this be done?
WBBDLD03
We also tried to create the WBBDLD IDoc after creating a listing in ECC using transaction WDBU or WDBM, but could not.
Please provide your input. I have also checked BD50 (whether it is Active) and BD52 also.
Also i tried Automatic creation of Idoc of basic type WBBDLD, however i checked the FM MASTERIDOC_CREATE_WBBDLD, and when excecuting RBDMIDOC program with the messg type WBBDLD, i am getting a ABAP DUMP.
Thanks in advance!!
Rakesh
Edited by: rakeshjain_hit on Jan 7, 2011 10:31 AM

Training historical records of legacy system

Similar Messages

Maybe you are looking for