Interface req from SQL to SAP

Hi
i need to develop interface from SQL to SAP, can any one give me some input on this.
Thanks.

Hey,
I guess you have a stand-alone DB and you want to develop interface from this DB to the SAP system.
If I'm right, then SAP have product called XI (eXchange Infrastructure), that now is called PI (process integrator).
this product have an adapter to FlatFile, DB (JDBC), MQSerires (JMS) and etc...
you can develop an interface in the XI that will read information from the DB,
and execute RFC (remote function call) or IDOCs in the SAP.
SAP does not support executing delete/update/insert SQL on their tables,
they demands from you to use the standard APIs (RFC/IDOC).
you can use the PI/XI forms in the SDN for more information.

Similar Messages

How to send automatic EMail from SQL or SAP B1

hi experts as we are using SQL as DB i ned to send E-mails from sap system automatically but from SBO mailer or Scheduler is not working from my side now i was planning to send emails from SQL can any one help me how to send emails automatically from SAP business one or from SQL

Hi
In SQL under Management\Database Mail
You can configure account you use to send mails from SQL
Then you can prepare procedure that will send mail
for example
EXEC msdb.dbo.sp_send_dbmail
@profile_name = 'Hurtpol',
@recipients = '[email protected]',
@query = 'select isnull(syncherror,'''') collate polish_ci_as
from np.dbo.OITM
where U_SynchStatus=''Failed''',
--@body = @tresc,
@subject = 'synch error'
read about sp_send_dbmail

Data transfer from SQL to SAP r/3

Hi,
We have a scenario wherein we require to get data from two tables in SQL and send the data to r/3 and do some some calculation. finally save the data in tables.
Can you please help me out the best way to do so. Is it Flat file transfer or RFC. Please do provide examples, if any.
Thanks.

Hi Sai;
I suggest you 2 way for your status.
Native sql very useful and healty method. You can try this method.
Please check below links.
Best regards.
http://help.sap.com/saphelp_smehp1/helpdata/en/a9/9cbe7ecd9b464b8f31449df34c8d8c/content.htm
http://help.sap.com/saphelp_nw04/helpdata/EN/fc/eb3b8b358411d1829f0000e829fbfe/content.htm

Need to fetch documents from filenet to SAP ?

Hi,
Here is the scenario..,
The physical documents such as pdf, word documents etc.. are available in filenet/P8.
These documents need to get fetched & displayed in SAP.
For a prticular document id, all the related documents need to get displayed...
Is there any function module or class to do so?
Thanks.

> I need to fetch data from SAP system to SQL, I know to fetch it from SQL to SAP using DBConnect but don't know to do this stuff, can any one please help me out with this.
You can use the same way.
Markus

ANY INTERFACE FOR INTEGRATING MS-SQL TO SAP R/3?

Hi All.
Is there any fecility to interact data between MS-Sql to R/3 System .
I Mean to say If can retriving the data from MS-SQL to R/3 and display in browser.
interface between MS-SQL server to SAP
Thnaks in advance.
RAMA.

Thanks for u r reply,
here what i need is i want to interact with MS-SQL ,but ms SQL is different data base.
What I need is If I display the data to browser from getting Ms-sql to R/3 System that R/3 System Screen output will display on the browser.
How can get data from MS-SQL to R/3.
Thnks and regards
RAMA

1)    Is there North Bound Interface / API from SAP Solution Manager available for 3rd party integration?       i. The list of the modules that are being managed by SAP Solution Manager(s)      ii. The performance metrics of those modules/components at th

1)
Is there North Bound Interface / API from SAP Solution Manager available for 3rd party integration?
i. The list of the modules that are being managed by SAP Solution Manager(s)
ii. The performance metrics of those modules/components at the high level
iii. The information about Early Watch Alerts (or situations to watch for)
2)
Is there a full SNMP interface for getting the above information from SAP Solution Manager?
3)
Is that understanding that SAP has SNMP support for forwarding alerts to a 3rd party system, correct?
4)
Does SAP has both free and licensed? If yes then what are the advantages of licensed over the open/free version?

Mugunthan
Yes we have applied 11i.AZ.H.2. I am getting several errors still that we trying to resolve
One of them is
===========>>>
Uploading snapshot to central instance failed, with 3 different messages
Error: An invalid status '-1' was passed to fnd_concurrent.set_completion_status. The valid statuses are: 'NORMAL', 'WARNING', 'ERROR'FND     at oracle.apps.az.r12.util.XmlTransmorpher.<init>(XmlTransmorpher.java:301)
     at oracle.apps.az.r12.extractor.cpserver.APIExtractor.insertGenericSelectionSet(APIExtractor.java:231)
please assist.
regards
girish

Cannot set required connection params for interface import from SAP system

Hello all
I'm trying to import some interfaces (RFC) from SAP system. For this I need to set the connection paramters pointing to the SAP system. Unfortunately it is not possible... all fields remain "greyed out" regardless what I'm trying.
JVM is 1.4.2_12
My user account has SAP_ALL so it shouldn't be an authorization problem...
Where to control this?
Any ideas?
BR
Renaud

Hi,
After you import the SWCV from SLD. while creating the NAmespace in IR select the radio button Import RFC/IDOC from SAP radio button.
And the save it.Now it shld be possible
Regards
Seshagiri

Error while retrieving data from sql using jdbc adapter

hi all,
i m working on one scenario where i m sending data using HTTP and receiver is jdbc adapter which is retrieving me data from sql server.
i have checked the structure both for req and res.
i m getting this error
<SAP:Error>
<SAP:Category>Application</SAP:Category>
<SAP:Code>MAPPING.EXCEPTION_DURING_EXECUTE</SAP:Code>
<SAP:P1>com/sap/xi/tf/_INF57285_DB_HR_RES_</SAP:P1>
<SAP:P2>com.sap.aii.utilxi.misc.api.BaseRuntimeException</SAP:P2>
<SAP:P3>RuntimeException in Message-Mapping transformatio~</SAP:P3>
<SAP:Stack>During the application mapping com/sap/xi/tf/_INF57285_DB_HR_RES_ a com.sap.aii.utilxi.misc.api.BaseRuntimeException was thrown: RuntimeException in Message-Mapping transformatio~</SAP:Stack>
</SAP:Error>
can somebody help me with this.
Thanks & Regards
Aruna

thnks bhavesh i think i made it that way
JDBC REQ
<ns:INF57285_DB_Request xmlns:ns="http://www.infosys.com/xi/training/hyd/57285">
<Employee>
    <EmpDetails action="SELECT">
      <table>EmpDetails</table>
      <access>
        <Name />
        <EmpId />
        <Band />
        <Salary />
      </access>
      <Key>
        <EmpId>57285</EmpId>
      </Key>
    </EmpDetails>
</Employee>
</ns:INF57285_DB_Request>
JDBC RES
<ns:INF57285_DB_Request_response xmlns:ns="http://www.infosys.com/xi/training/hyd/57285">
<Employee_response>
    <row>
      <Name>aruna</Name>
      <EmpId>57285</EmpId>
      <Band>A</Band>
      <Salary>4675776</Salary>
    </row>
</Employee_response>
</ns:INF57285_DB_Request_response>
my hr req is which i mapped with DB req
<ns:INF57285_HR_Req xmlns:ns="http://www.infosys.com/xi/training/hyd/57285">
<REQUEST>
    <EmpNo>57285</EmpNo>
</REQUEST>
</ns:INF57285_HR_Req>
my hr res is which i mapped with DB res
<ns:INF57285_HR_Res xmlns:ns="http://www.infosys.com/xi/training/hyd/57285">
<response>
    <row>
      <Name>aruna</Name>
      <Empld>57285</Empld>
      <Salary>4675776</Salary>
    </row>
</response>
</ns:INF57285_HR_Res>
and interestingly i am not getting any error in sxmb_moni
it's not showing any error
plz suggest me something wht to do ....
thnks & regards
Aruna

MESSAGE MAPPING FROM SQL TO RFC(BAPI)

Hello Guys,
Im just new here in SAP XI version 7.0 . Can anyone teach me how to map objects using IR (design) between sender (data coming from sql 2005) and receiver (using Bapi_Salesorder_Createfromdat2)?
there are only specific fields i need to transfer the data like the followings :
do i need to map all fields from sender to receiver?tell me how..
*ORDER_HEADER_IN
-DOC_TYPE = ZTRV
-SALES_ORG =4000
-DISTR_CHAN =40
-DIVISION=41
-SALES_OFF=4101
-SALES_GRP=411
-PURCH_NO_C='TEST TPL1' (MUST BE UNIQUE)
-PMNTTRMS =Z015
-PURCH_DATE=09/04/2008
*ORDER_PARTNERS
-PARTN_ROLE= AG
-PARTN_NUMB=1100074
Thanks in advance
aVaDuDz

Hi,
Create :
1. Source & Target Data Types
2. Messge Type (for source & target data types)
3. Two Message Interface for using above message types
4. One Message mapping using source & target message Type
5. One Interface mapping.
In message mapping just map those field which you require. You can leave rest of the fileds un mapped at source which are not required to map.
Regards,
Sarvesh

Connection from DP to SAP PI 7.11 via SOAP/https failed

Hello Guys,
we have a problem with connection from DP to SAP PI via SOAP/https.
DP send a request and get a timeout. timeout is 2 or 3 minutes.
DP and SAP PI authentificated with certificates.
Our Problems:
DP get now failure code
in commnication channel monitoring in RWB from SAP PI I see no entry, no error
in java default trace I see no error.
What could be the Problem? What must we configure for https communication via SOAP Adapter?
Which Log get me some information?
Thanks and regards
Martin

Hi Neetesh,
I have check all, but it resolved not my problem.
I will describe my scenario again:
scenario:
syncronous request from system A over DataPower ->SAP PI to SAP system.
communication DataPower to PI: SOAP over https
DataPower located in other network zone.
port is activated in firewall.
called URL from DataPower:
https://<host>:5<instance number>01/XISOAPAdapter/MessageServlet?
channel=:<business system>:<interface>
Problem:
authentication looks like ok. No error in ICM Trace, in default java
trace login from DataPower IP-adress ok.
but no message is to see in the communication channel.
no message in the adapter engine, no message in the integration engine
DataPower get a timeout. (Timeout 2 minutes)
we find no error, but also no message
What could be the error? And where find I some information in SAP PI.
Thanks and regards
Martin

Migration from webmethods to SAP PI 7.1

Hi All,
I need some information on migrating webmethods to PI 7.1.
We have our interfaces currently working in webmethods which call webservices in SAP.Currently legacy systems call SAP webservices through webmethods which we would like to migrate to PI 7.1.
Could I get some information on how to proceed with this?
1.Could I get the overview
2.Can I import the same structure and mappings into SAP PI?
3.Do I need to recreate the mappings or use the same from webmethods ..if they are XSLT mappings?
4.Can I use the mapping transformation done in webmethods ?
Any thoughts would be of great help
Thanks,
C

> I need some information on migrating webmethods to PI 7.1.
> We have our interfaces currently working in webmethods which call webservices in SAP.Currently legacy systems call SAP webservices through webmethods which we would like to migrate to PI 7.1.
>
> Could I get some information on how to proceed with this?
>
2 years back i worked on one migration project from WebMethods to SAP PI 7.1
> 1.Could I get the overview
> 2.Can I import the same structure and mappings into SAP PI?
> 3.Do I need to recreate the mappings or use the same from webmethods ..if they are XSLT mappings?
> 4.Can I use the mapping transformation done in webmethods ?
>
> Any thoughts would be of great help
1)Only XSLT Mapping program can be reused in PI7.1,most of the times without change, sometimes it required change when you have java functions in XSLT Mapping.
Adjust your XSLT mapping programs compatible to without using XML TOOL kit option in Operation mapping.
2) To understand the web methods flow , you should have some basic /medium level of knowledge , then you can easily understand the mapping logic implemented in Web Methods.
3) When you developing interface use Web methods for only mapping logic, donu2019t try to implement the same design what developed in Web Methods. Think PI prospective. The way web methods execute interface is differ compare to PI (execution process).
4)If any java services existing in current web method interfaces, you canu2019t use the same as java mapping program in PI,in web methods we can perform state full operation from java services in web methods. But in PI it is strictly avoided performing state full operation like retrieving the data/sending data to Data base using Java map.
5) If your client forcing you to use XSLT mappings then only use, else implement the same logic using GUI mapping in PI.
6) Connecting to SAP systems and non SAP system use Adapters in PI,it is very easy . Follow standard way of communication using PI ,donu2019t try to copy from Web METHODS.
Thanks and Regards,
Raja Sekhar

Creating a Crystal Report from a non-SAP data base

I have the following scenario
server1\myDataBase
server1\SAP\sapDataBases
in sapDataBases I have about 30 company databases. I am trying to create a report, that gets informatino from a table/view/SP from server1\myDataBase, when I try to PREVIEW or SAVE such report on SAP Business One, I always get errors as
I understand that this eerror means taht I can't invoke the data from out of SAP; it needs to be inside SAP (at least the SP, incoking some other data bases and stuff..)
Some bodies have told me that it is beacuase I can only create a report from a table/view/sp that resides in the running/currently SAP company database. Is this right?
Also, If this is the case, this means that If I have an SP taht I use for a crystal report, and 30 companies, I have to create such SP in the 30 companies?
This is my software details:
SQL Server 2012
SAP Business One 9 PL 11
SAP BusinessObjects Crystal Reports 2013 Support Pack 2 version 14.1.2.1121
What I want to do is to create a non-SAP data base to create all the SPs/Views for reports, to centralize it, and the just create one reporte and do the 30-imports in each company database, without the need of creating such sps/views in each company-database. Is this possible?
Thanks

Moved to Integration Kit forum.
The people in this forum will know more about the data structure than the CR Design forum which typically doesn't know much about the SAP Data sources Structure.
Don

Error when calling a XI-webservice from SQL-Server 2005

Hi all,
we have published a webservice with XI 7.0 (using the SOAP-Adapter) and try to call it from a stored procedure within SQL-Server 2005. Upon execution we receive the error
"<SAP:Code area="MESSAGE">EMPTY_HTTP_REQUEST_RECEIVED</SAP:Code>" and
"<SAP:Stack>Empty HTTP query received; message processing not possible </SAP:Stack>".
We are using the dll MSXML2.ServerXMLHTTP. The webservice is available and can be reached from other tools like SOAP-UI when using the same endpoint-URL. It is also possible to call the service from Visual-Basic using the same code.
Does anyone has any clue about what's causing this error?
Thanks in advance!

It is clear that, PI service is working absolutely fine and the problem is calling it in your SP. I do not think you are calling a web service but actually sending a HTTP request to the server. An HTTP request and a SOAP call are different in terms of protocol. You would need to explore more on how to call web services from SQL SPs.. and the right place to search would be MS SQL Server Forums..!!
VJ

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

How can we post data from CRM to SAP using ABAP proxies???

Hi ,
Can anyone hep me to create interface for the following scenario How can we post data from CRM to SAP using ABAP proxies???, can I find any document ???????
Thanks in advance
Andy

Andy,
Please look at these weblogs.
/people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy
/people/ravikumar.allampallam/blog/2005/03/03/creating-purchase-order-idoc-through-xi
/people/siva.maranani/blog/2005/04/03/abap-server-proxies
/people/vijaya.kumari2/blog/2006/01/26/how-do-you-activate-abap-proxies
These should give a good idea about implementing Proxies.
Regards,
Ravi

Interface req from SQL to SAP

Similar Messages

Maybe you are looking for