Getting error in Exporting the data from legacy system to Tables

Hi,
I am trying to export the data. But am getting the below error.
Unknown system exception - java.security.PrivilegedActionException: javax.security.auth.login.LoginException: java.net.ConnectException: t3://abc.com:7001: Bootstrap to abc.jdadelivers.com/0:0:0:0:0:0:0:1:7001 failed. It is likely that the remote side declared peer gone on this JVM.
No records are exported.
Include column headers: Yes
Format : Seperated (,) , enclosing character (")
{code}
I tried with with different user but getting the same error. Please have a look and let us know the route cause of the issue.
Many thanks in advance.
Vas.

Export ? What kind of export is this ? I see a weblogic port... Can you provide more information ?

Similar Messages

How to upload the data from legacy system database to SAP data base

Hi.
We are doing analysis of Legacy system and which needs to be converted to SAP system i.e. SAP implementation.
I just want to know , how we migrate the existing whole data( from legacy system) into SAP system.
and which method is the best method to use data migration from legacy to SAP system if data legacy data amount is huge.
Please suggest me.
Thanks.

Hi
We can either use the BDC or BAPI or LSMW or Direct Input techiniques for the data transfers.
The combination of both Session and Call transaction can be used to achieve this that includes the error handling also. This invloves the screen interaction.
These days, BAPIs are used to overvome some upgrade problems. For easy upgradation, we cna go for BAPIs. Here ther is no screen intercation.
LSMW mainly used for master data transfers using some standrad programs.
As per your client or company desicions we can choose any of them.
Please refer to these links for more understanding -
BDC Vs LSMW -
BDC VS LSMW
BDC Vs BAPI -
BDC VS LSMW
Thanks & Regards,
Chandralekha.

Error MUT-02041 : While exporting the data from Java system.

Dear Friends,
When exporting data from Java system (source system) using SAPINST. We are getting
the below error in 4 of 5 (Archiving SDM Repository) stage.
Error :
MUT-02041 SDM call of createsdmkitjar ends with returncode 2
With this, I am unable to proceed further. Please help me on this to proceed further.
Thanks in advance,
regards,
Srinivas

Hi All,
I could find the below error log from sapinst.log file.
=============
Info: Exclude components as specified
in /usr/sap/IPD/DVD_JAVA/51033746_1/Installation_Master_6.20_6.40_05_08/IM_AIX_PPC64/SAPINST/COMMON/INSTALL/JMIG/EXCLUDE.XML
Info: Resulting JAR
file: /oracle/IPD/sapdata1/data_export/SDM/SDMKIT.JAR
Info: No temporal directory for packing is provided. SDM home directory
will be used.
Info: Pack directory exists already. Remove it first.
Info: Start packing the components of com.gsk in
packedOrigin_com.gsk.jar
Info: Create /usr/sap/IPD/JC02/SDM/program/pack/packedOrigin_com.gsk.jarInfo: The components of com.gsk were successfully packed in
packedOrigin_com.gsk.jar
Info: Start packing the components of local in packedOrigin_local.jar
Info: Create /usr/sap/IPD/JC02/SDM/program/pack/packedOrigin_local.jar
Info: Create /oracle/IPD/sapdata1/data_export/SDM/SDMKIT.JAR
Warning: Warning during command execution: No metadata files exist for
development
component 'revtrac_agu11'/'local'/'LOKAL'/'0.2009.08.11.10.56.14'/'0'.
Cannot pack this archive.
No metadata files exist for development
component 'revtrac_aug13eartest'/'local'/'LOKAL'/'0.2009.08.13.14.44.25'/'0'. Cannot pack this archive.
No metadata files exist for development
component 'Aug10_09'/'local'/'LOKAL'/'0.2009.08.10.14.39.29'/'0'.
Cannot pack this archive.
No metadata files exist for development
component 'Aug14'/'local'/'LOKAL'/'0.2009.08.14.10.46.38'/'0'. Cannot
pack this archive.
No metadata files exist for development
component 'Aug14two'/'local'/'LOKAL'/'0.2009.08.14.10.55.21'/'0'.
Cannot pack this archive.
No metadata files exist for development
component 'revtrac_aug11b'/'local'/'LOKAL'/'0.2009.08.13.14.36.43'/'0'.
Cannot pack this archive.
Missing archives may lead to errors after the packed SDM installation
has been extracted later.
Info: This SDM installation has been packed
to /oracle/IPD/sapdata1/data_export/SDM/SDMKIT.JAR
To unpack this installation again,
extract /oracle/IPD/sapdata1/data_export/SDM/SDMKIT.JAR and invoke the
SDM command install with parameter extractpackedinst=true
Executed, but finished with warning(s). Return code: 2
Error: Executed, but finished with warning(s). Return code: 2
ERROR 2010-10-21 15:54:48
MUT-02041 SDM call of createsdmkitjar ends with returncode 2
=============
Can you please check this and help me on this to proceed further.
thanks..
Srinivas

Error while retracting the data from BW system

Dear all,
while retracting the data from BW we are getting the below dump
"Inconsistent entry in table TKA07 (Plan Version Maintenance)",Request you to please help to solve the issue
Thanks,
Jyoti

Jyoti,
Could you please explain in detail, were you using any standard retractor or custom?
is it erroring out in ECC system or BI?

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.

Load the data from Legacy system into CRM

I'm new to CRM,I would like to know What is the procedure used to Load the data (ex: Business partners data ,Organization data,Sales data, etc.) from Legacy system into CRM system?
Can anyone explain me and send any documents,it would be very helpful.
I highly appreciate your help.
Thanks,
[email protected]

Hi Rani,
You can also use the ALE IDOC method to load data from legacy to CRM system if you have some middlware tool(E.g. XI) in between. We have implemented this in our project where we were getting flat files from legacy, XI was converting the same into IDOC and the IDOC was sent to CRM where we read the IDOC data, populate the standard BAPI's or function modules to create the data in CRM.
You need to define an IDOC TYPE similar to the data structure on the legacy system. Maintain the ALE settings. Write the function module to validate and create data in the CRM system.
E.G. To create business partner SAP has provided BAPI_BUPA_CREATE_FROM_DATA bapi.
<b>Reward points if it helps.</b>

Upload data from legacy system to SAP through ALE IDOC

Hello All,
I have a requirement where i need to upload the data from legacy system to SAP. So i am using ALE IDOC.
In my requirement i need to extend the Standard IDOC. I have extended the IDOC and even found the exit for the updation of the extended fields to SAP. My data would be be placed in the application server.
Can anybody tell me how to retrieve the data and update in the tables for the extended fields.
Could you please provide a sample program for retrieving data for IDOC.
Thanks

Hi,
You can find the sample code in the following link.
Re: calling idoc_input_creditor
Regards
Sajid

What are the major process to transfer the data from legacy to sap system.

What are the major process to transfer the data from legacy to sap system using BDC at Real Time only?

hi,
BATCH DATA COMMUNICATION
main methods are:
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
SYSTEM ? SERVICES ? BATCH INPUT ? EDIT
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
Tools ? Administration ? Jobs ? Define jobs
Or
System ? services ? Jobs
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.
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.
generally Batch Input usually are used to transfer large amount of data. For example you are implementing a new SAP project, and of course you will need some data transfer from legacy system to SAP system.
CALL TRANSACTION is used especially for integration actions between two SAP systems or between different modules. Users sometimes wish to do something like that click a button or an item then SAP would inserts or changes data automatically. Here CALL TRANSACTION should be considered.
2. Transfer data for multiple transactions usually the Batch Input method is used.
check these sites for step by step process:
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 ?
null

Error when updating the data from DSO to cube

Hi,
I am getting the error when uploading the data from the ods to cube.
The following is the error message.
Unable to determine period for date 20090101, fiscal year variant Z2: Error #
How can i solve this issue.
Regards
Annie

Hi ,
fiscal year variant, go into Customizing for Financial Accounting (FI) under Financial Accounting Global Settings >>>Fiscal Year >>>Maintain Fiscal Year Variant.
check this link ..
http://help.sap.com/saphelp_scm41/helpdata/en/50/0d89f2ad919c40b95b9ae7583c8c96/frameset.htm
http://help.sap.com/saphelp_scm41/helpdata/en/50/0d89f2ad919c40b95b9ae7583c8c96/content.htm
Regards,
shikha

*Journal Entries while uploading the vendor master data from legacy system*

hi SAP Folks,
can any one of you tell me the journal entries while uploading the vendor master data from legacy system to SAP system.
Eg: legacy system is having 10000 vendors list, 1 reconciliation account and $ 1000000. while uploading all these data from legacy system to SAP what are the journal entries we get.
thanks in advance.
Edited by: ravindranath manikonda on Nov 24, 2008 1:12 PM

Hi
you will be having only one entry logically
i.e. Opening Bal. clrng A/c Dr.
To Vendor A/c Cr.
regards

How can we export the data from OAF Page to Excel instead of .csv or .txt

Hello,
How can we export the data from OAF Page to Excel instead of .csv or .txt
When i click on the export button it is exporting to txt file, But i need to export the data into Excel by default
Please help me
Thanks in advance
Thanks,
Raju
We have changed the below profile option to get the data in excel by default
Profile Name Export MIME type
Profile Code FND_EXPORT_MIME_TYPE+
Existing Value: text/tab-separated-values+
Change as: Excel
Thank you,
Raju
Edited by: 1006649 on May 21, 2013 10:55 AM

We have changed the below profile option to get the data in excel by default
Profile Name Export MIME type
Profile Code FND_EXPORT_MIME_TYPE+
Existing Value: text/tab-separated-values+
Change as: Excel
Thank you,
Raju

No data Exists error while retrieving the data from a table

Hi Everyone!
I am getting "No Data Exists" error while retrieving the data from a table....where i need to check...if possible please give me example link.....please help me regarding this

Hi !
thanks for ur response...
I have written vo.executeQuery for the table...My page is running but i m not getting the data....I have to select two LOV's and when I click on Go button the data has to display in the table...After the selection of LOV's when I click on Go in the table "No data exists" message is appearing...the table has the data and the query is also executing...please give info where i did the mistake....

Error "Encountered an error while exporting the data. View the lof file (DPR-10126)

Hello,
I would like to have sugestions and help to solve a problem in IS 4.2.
I've created a view from two tables, joined together with the key from each one.
Then i've binded the rule with the view (mentioned above) created and calculated score for it.
The calculation is successful, however when i try to export all failed data i have the following error:
"Encountered an error while exporting the data. View the lof file (DPR-10126)"
When exporting failed data from calculations made directly to the datasources i do not encounter any problem, but when i try to export all data to CSV file (not only the 500 results limit) i have this kind of error.
However, when i visualize the data from the view created, it is also possible to export to csv file.
Resuming, the error occurs only when exporting all failed data from the view.
Can anyone help with this issue?
Thx
Best Regards,

Hello,
Your information is correct.
I've just confirmed it in the 4.2 SP3 Release Notes and they specifically refer to this issue.
A user who has 'View objects' rights for the project and a failed rule connection cannot export the failed data. This issue has been fixed in this release.
Thank you very much for your input.
Best Regards,

Problem while exporting the data from a report to an excel file.

Hi SAP guru's,
I have a problem while exporting the data from a report to an excel file.
The problem is that after exporting, the excel file seems to have some irrelevant characters....I am checking this using SOST transaction..
Required text (Russian):
Операции по счету
№ документа     Тип документа     № учетной записи     Дата документа     Валюта     Сумма, вкл. НДС     Срок оплаты     Описание документа
Current Text :
   ? 5 @ 0 F 8 8 ? > A G 5 B C
!   4 > : C       "" 8 ? 4 > : C      !   C G 5 B = > 9 7 0 ? 8 A 8        0 B 0 4 > : C         0 ; N B 0      ! C <       ! @ > : > ? ; 0 B K        ? 8 A 0 = 8 5 4 > : C
Can you help me making configuration settings if any?
Regards,
Avinash Raju

Hi Avinash
To download such characteres you need to adjust code page to be used during export. You can review SAP note 73606 to identify which code page is required for this language
Best regards

Error when loading the data from PSA to ODS......

Hi BW guru's,
i am facing one problem while loading the data from PSA to ODS.so please help me in this regard.
Please give a step by step guidelines for me...
the error while loading the data from PSA to ODS is "There are no PSA tables for these selection criteria","An error occurred when reading PSA data".
thanks in advance,
ashok.

hi ashok,
u can push data from psa to ods, for this goto the psa in rsa1>psa>goto that request>rightclick>select " schedule update Immediately ", then data will moved from psa to ods.
or
In ods > delete the failed request>goto the processing tab-->select 3rd option " psa and then subsequentially to data targets ", --> schedule the infopackage.
bye
sunil

Getting error in Exporting the data from legacy system to Tables

Similar Messages

Maybe you are looking for