Data Load to the SAP System

<Moderator Message: Even as a newbie you should be able to search for this information on your own. We are not here to spoonfeed>
Hi All,
I am very new to SAP BI.
Could anybody please tell me the steps for loading data to SAP BI system?
I wanted to do it through RFC and also through flat file.
Thanks a lot in advance,
Amilie
Edited by: Siegfried Szameitat on Jul 16, 2009 2:15 PM

>
Amilie wrote:
> I am very new to SAP BI.
>
> Thanks a lot in advance,
> Amilie
Please read the Rules and Engagement of this forum.

Similar Messages

Spread the Data Loads in a SAP BW System

Gurus,
I want to spread the data loads in our BW system, as a BASIS person how do I identify the jobs if they are full loads or delta loads, our goal is to make the load on the system to be evenly distributed as we see too many data loads starting and running around the same time. Can you suggest a right approach to achieve our goal.
Thanks in advance
Siva

Hello Siva,
As already mentioned the solution is to include the different steps of the data flow, extraction , ODS activation , rollup etc
in process chains and schedule these chains to run at differet times so that they do not place too much load on the system.
If the problem is specific to data loads on the extraction step then I guess that maybe you see the resource problem on the
source system side, if you don't have the load distribtion switched on in the RFC connection to the source system it is
possible that you can specify that the source system extraxction jobs are executed on a particular application server,
please see the information in the 'Solution' part of the note 147104 and read it carefully.
Best Regards,
Des

How to check data sent by XI in the SAP system?

Hi All,
I have a File to Proxy scenario. I have generated and activated the proxy. The scenario got executed successfully.
Now, how can I check the data being sent by XI in the SAP system? Kindly help.
Thanks,
Karthik

Hi,
If u want to check in XI system as said by experts you can check in SXMB_MONI transcation(Check for chequred flag:Sucess).If not you need to see the error message and troubleshoot.
if the message is sucess in XI,then goto your R/3 system.
you can check SXMB_MONI in R/3 system.Tis is the message before going to proxy.
Then as experts have already pointed out you must be knowing which tables are getting updated.
check in those tables for the updated data.
otherwise you need to debug proxy,
Plz keep the thread updated.
thanks and regards
parvez

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

CX_RSR_X_MESSAGE Data load error in Quality system

Hi
We are on BI.7 and trying to load Technical content data for first time in Quality system .
We get the following error :
Runtime Errors UNCAUGHT_EXCEPTION
Except. CX_RSR_X_MESSAGE
for all the technical content data load.
The other data loads are working fine in the quality system.
We searched a lot on the forum and got various solutions like try out note 615389, 963760 etc.. But none of them are working fine for us.
Please suggest.
Thanks you for your help.
Gaurav

Hi
The error log is as follows -
Runtime Errors         UNCAUGHT_EXCEPTION
Exception              CX_RSR_X_MESSAGE
Date and Time          23.01.2009 10:06:08
Short text
     An exception occurred that was not caught.
What happened?
     The exception 'CX_RSR_X_MESSAGE' was raised, but it was not caught anywhere
      along
     the call hierarchy.
     Since exceptions represent error situations and this error was not
     adequately responded to, the running ABAP program 'SAPLRRMS' has to be
     terminated.
What can you do?
     Note down which actions and inputs caused the error.
     To process the problem further, contact you SAP system
     administrator.
     Using Transaction ST22 for ABAP Dump Analysis, you can look
     at and manage termination messages, and you can also
     keep them for a long time.
Error analysis
    An exception occurred which is explained in detail below.
    The exception, which is assigned to class 'CX_RSR_X_MESSAGE', was not caught
     and
    therefore caused a runtime error.
    The reason for the exception is:
    No text available for this exception
How to correct the error
    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:
    "UNCAUGHT_EXCEPTION" "CX_RSR_X_MESSAGE"
    "SAPLRRMS" or "LRRMSU13"
    "RRMS_X_MESSAGE"
    If you cannot solve the problem yourself and want to send an error
    notification to SAP, include the following information:
    1. The description of the current problem (short dump)
       To save the description, choose "System->List->Save->Local File
    (Unconverted)".
It gives a error in the last step of executing infopackage wherein the data is to be updated to the infocube.
I checked with Basis team. There is no tablespace problem as well.
Regards
Gaurav

Put these costs of delivery into the SAP system

Hello,
After a delivery is done we receive an invoice from the carrier. So far we are doing the correlation between the costs of the delivery and the delivery note itself manually on an excel sheet. What we would like to do is to put these costs into the SAP system and they should be able to be monitored afterwards ( per query for example ). Do you have any idea or recommondation how to do this?
Many Thanks
Jean

Hello Jean,
Designing a Z table is very easy, you would first figure out all the important fields you would want to maintain in SAP.
Then you would be giving those fields to your ABAPer, who first creates the table with all the important fields you need.
Once that is done you could again take the help of ABAPer to develop a program which when run would load the flat file from the carrier system and update this fields.You can automate this Program by creating a JOB.
Once the table is defined you could have this custom fields to be populated in Sales Order (example you could use Additional data A or B tab in Sales Order header or in Delivery Header and place your custom made fields in it.)
So that once the job is run it would populate the tables and also you would have this data in sales documents.
Once you have the data in SAP its very easy for you to run the query.
HOpe this helps.
Thanks
Murtuza

Customized delta data source for deleting data record in the source system.

Hello Gurus,
there is a customized delta data source, how to implement delta function for deleting data record in the source system?
I mean if there is record deleted in the source sytem, how to notify SAP BW system for this deleting change by this customized delta
data source?
Many thanks.

Hi,
when ever record deleted we need to write the code to insert the record in Z table load this records into BW in a cube with similar structure.while loading into this cube multiply the Keyfigure by -1.
add this cube in the Multi Provider.The union of the records in the orginal cube and the cube having deleted records will result in zero vale and will not be displayed in report .
Regards,

Inventory to the SAP System

My friend is trying to load the Inventory to the SAP System..
Can any one forward me the Documentation like pre checks and all i got to
do before i do the uploads..
Thanks

check this link which shows details about Inventory Management.
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/MMIM/MMIM.pdf
http://www.sap-img.com/sap-mm.htm
http://www.sap-img.com/shop/sap-mm-inventory-management-overview.htm
http://www50.sap.com/businessmaps/9B0FD9FD8D0D4E598EB224501FFC3801.htm
http://help.sap.com/saphelp_47x200/helpdata/en/4d/2ba31643ad11d189410000e829fbbd/frameset.htm
Reward points if useful.

Unable to Logon to the SAP System after Installing SAPNW2004sSneakPreviewAB

Hi
 I Installed SAPNW2004sSneakPreviewABAP.
 If i am trying to run the NSP Server it first Starting (Showing Blue Color ) and after few seconds it is becoming Yellow in Color. When i cross checked in Process list it is showing one of the process in yellow color i.e.
disp+work.EXE whose description is Dispatcher
and Status is showing as "Running but Dialog Queue standstill"
May be because of this i am unable to log on the SAP System.
One more thing i got a licence key from SAP but when i am trying to intall licence key using saplicence -install this is also not working it is showing following error message.
SAPLICENSE (Release 700) ERROR ***
 ERROR: Can not set DbSl trace function
 DETAILS: DbSlControl(DBSL_CMD_IMP_FUNS_SET) failed with return code 20
 RC-INFO: error loading dynamic db-library - check environment for:
 dbms_type = <db-type> (e.g. ora)
 DIR_LIBRARY = <path to db-dll> (e.g. /usr/sap/SID/SYS/exe/run)
Could you please help in this

Please refer to this post as this is a duplicate.
Problem after installing SAPNW2004sSneakPreviewABAP
Please close this post. Thanks.
Regards,
Rich Heilman

Creating tables on SQL studio and viewing the table in the SAP system

i have just created a table using the SQL studio and wants to use it view it in the SAP system using the SAP logon. till now i have not found a way to create it therefore any help is much appreciated.

Hmm... you want to see tables via SAPLogon ??
Ok, let's assume you really want to access tables via ABAP instead.
For that you've two options:
1. Create the table in the ABAP dictonary (SE11) exactly like you created it in the database and activate the table.
After that you can access the table via SE16 or any ABAP as you like.
2. You don't create the table in the ABAP dictonary and use native SQL to access the data.
Neither of these options is meant to be the way to do it.
The correct way would be to design the whole table in the ABAP dictionary and create the table on the database from that.
regards,
Lars

Getting the No of Users logged in the SAP system

Hi Experts ,
I have the requirement of finding the No of Users ( User Ids) logged into the SAP system.
Is there any database table or FM to retrieve this information.
Regards,
Abhishek Kokate

Hi Abhishek,
Check out transparent table : USR41 (User master: Additional data) This may be the table you want to use.
Or
You can use SUBMIT command with the above stated report (RSM04000_ALV) - export the output( ALV data) to memory and then retrieve to use it as you want (as an internal table).
example :
DATA BEGIN OF itab_list OCCURS 0.
        INCLUDE STRUCTURE abaplist.
DATA END OF itab_list
SUBMIT RSM04000_ALV
via selection-screen
    EXPORTING LIST TO MEMORY
      AND RETURN.
* To read from the memory
CALL FUNCTION 'LIST_FROM_MEMORY'
TABLES
    listobject = itab_list
EXCEPTIONS
    not_found = 4
    OTHERS     = 8.
Hope this is help full to you !!
Salil.

Output device DKRDSP029 is locked in the SAP system - RFC error

Hi,
One user of the system has got the following error when he is loading his "Change Office and communication" iView in the portal. This is the SAP standard DK used iView!
No one else has this error in the system as far as we know and the DKRDSP029 is a printer. I had no idea that a printer was connected to this information but apparently there is.
Does anyone has any input to what the problem actually is?
Thanks :-)...
Start of the stacktrace:
com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException: Output device DKRDSP029 is locked in the SAP system , error key: RFC_ERROR_SYSTEM_FAILURE
at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:101)
at com.sap.xss.hr.cod.FcCodBusinessLogicComp.callRFCGetDetails(FcCodBusinessLogicComp.java:472)
at com.sap.xss.hr.cod.FcCodBusinessLogicComp.onInit(FcCodBusinessLogicComp.java:228)
at com.sap.xss.hr.cod.wdp.InternalFcCodBusinessLogicComp.onInit(InternalFcCodBusinessLogicComp.java:512)
at com.sap.xss.hr.cod.FcCodBusinessLogicCompInterface.onInit(FcCodBusinessLogicCompInterface.java:115)
at com.sap.xss.hr.cod.wdp.InternalFcCodBusinessLogicCompInterface.onInit(InternalFcCodBusinessLogicCompInterface.java:147)
at com.sap.xss.hr.cod.wdp.InternalFcCodBusinessLogicCompInterface$External.onInit(InternalFcCodBusinessLogicCompInterface.java:227)
at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:922)
at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:891)

Please check if this user has any default output device configured in the corresponding backend system. (from SU01)
If the printer/output device configured for this user is DKRDSP029, there might be a problem with the printer setup.
You can try and change the printer to a different one if required.
Thanks,
Shanti

Cannot find Master Data folder in the SAP Netweaver

Hello,
I need to create Open Catalog Interface (OCI) punch out system for our web shop. In order to test it I need SRM server that can call our web shop. I have downloaded this SRM software and installed it in my local computer:
ABAP_Trial_7_02_SP11_Win_64_bit_Version_with_Gateway_2_0_SP04
But I cannot see the Master Data folder inside the SAP Easy Access. Does that mean SAP SRM server has not been installed on my computer? If yes, how can I install it? Can i have it for free or I should pay for it?
Best regards,
Kevin

I'm having the same problem. As far as I know the only version of ODAC that I have installed is 11.2.0.3. What version did you ultimately install?
What I have:
- Visual Studio 2010 Ultimate
- .Net framework 4
- Entity Framework 4
- 64 Bit ODAC 11.2.0.3
Any help is greatly appreciated!
Austen
Edited by: AHowell1337 on Jan 2, 2013 7:25 AM

ZGPGL - Copying Accounts and Cost Centers to the SAP system

Hi all,
When I try to copy accounts and cost centers from my excel mapping document to the SAP system I can only copy about 20 of them at a time. I have about 30,000 accounts and am wondering if there is a quicker way to do this.
Thanks,
Deki

Write a catt script to create the GL account and cost center master data. they are relativley easy to learn and create. They work great for this. I have used them several times for that purpose.
pls assign points to say thanks.

Error message 'Please log on to the SAP system' when selecting 'shop'

In SRM when we click on 'shop' or 'Goods Receipt' we get the error 'ITS System Information 'Please log on to the SAP System' where it prompts user to log on again. However when user logs on it opens up the same screen again saying please log on to the sap system.
This only happens when we shop using the External ITS (wgate), EBP works fine using the Internal ITS.
Please can someone help.
Kindest Regards
Paul

Hi
Please try this ->
Look using SRM transaction SITSPMON and RZ20, RZ21.
Also Please check SAP OSS Note 517860
-> For ITS, You need to maintain the RFC connection in the connection type "T" i.e TCP/IP. Maintain in the Table - TWPURLSVR.
Ensure that you have maintained correct entries in the TWPURLSVR table using SM30 transaction for the ITS Web path (http or https address path). Note you are passing port - 8001 in the address here. Incase you face problems, Please ask you BASIS person to help you out.
-> Please ask you BASIS person to help you out for maintaining ITS settings. (Ensure IACOR service is running properly - ITS server is running), through the transaction SMICM
-> What all logs appear in SLG1 and SM21 transactions after publishing all the Internet services.
-> If you are using ITS 6.2,you need to do the IACOR settings for SRM on the ITS server.Also in SE80 mainatin the Site for SRM system.After this ,you can publish all the ITS services usig the report,W3_PUBLISH SERVICES.
Related links ->
Integrated ITS :Login Problem
Re: ITS_CANT_LOAD_INCLUDE in BBPstart service
Re: ITS_DEST_NOT_FOUND
Re: ITS Configuration
Re: ITS Template not found
Do let me know.
Regards
- Atul

Data Load to the SAP System

Similar Messages

Maybe you are looking for