Send data to other non SAP system

Hye techies,
I have a requirement, on click of submit in my bsp application, the data updated by the button event should also be updated in other non SAP system.
Please let me know what is required at my end, also please let me know what should the other communicating non SAP should have to consume the data.
Regards
Imran.

Hello,
you want to consume the data send by sap via .NET?
I think in this case it is better to send the data via RFC. You have to implement an interface in your .NET application which will consume the data sent by sap. On the SAP side you can define a function module as interface. The .Net and the SAP FM parameters must be the same. Now you define an RFC in SAP via SM59,for exception chosse "start on explicit host" and then entery the .Net/SQL server adress and your programm. in your abap code you call your fm...
CALL FUNCTION XYZ DESTIONATION 'XYZ'
. In your .Net progamm consume the data send by sap and write it in the db. I hope this explanation is ok for you. We solved problems like yours, with this way.
A direct change of your SQL Data via BSP, in my opinion, is NOT possible

Similar Messages

How to send IDocs from a non-SAP system to a SAP system

Hi everyone i am new to SAP R/3 System.
Currently i am required to send IDocs from a non-SAP system to a SAP R/3 System.
There is a guide on Cost-Effective and Quick Communication between SAP and 3rd Party Systems using IDOC HTTP XML Interface. But its from a SAP system to a non-SAP system and i am able to do that.
Is there any step by step guide where they teaches you how to send IDocs from a non-SAP system to SAP system via similar method?
Thank You!

Hi,
I hope this link may help you......
http://publib.boulder.ibm.com/infocenter/iisinfsv/v8r1/index.jsp?topic=/com.ibm.swg.im.iis.ds.entpak.sapr3.use.doc/topics/c_pack_r3_Introduction.html

Sending Order acknowledgment to Non SAP system

Hello All,
Need expert advice in one of the scenario i am facing.
The scenario is
Vendor sends the scheduling agreement order confirmation to SAP system through inbound IDOC with message type ORDRSP......IDOC is posted in SAP.Now there is another third party system which plans the material planning... now this order confirmation needs to be send to that non SAP third party system which has JDBC
client needs the order confirmation data (SA no.,,co code...Item number....committed qty...delivery date...material no... plant) in flat file format only
please suggest the possible ways to overcome.

Hi NR,
What I understand from above is -
1. Inbound IDoc getting posted in SAP
2. Confirmation needs to be send to Non-SAP system which uses JDBC/Database
3. They want only Flat Files.
To answer above questions/scenarios - you have 2 choices
1. Proxy to JDBC Approach Directly post confirmation data to third party database.
How to do this -
a. Open ports with third party. - Check Connectivity stuff.
b. get databases details and configure receiver JDBC Adapter in your side
2. Proxy to SecureFTP - By this approach you will place a CSV file to securedFTP decided by you and your third party from where third party job will pick that file and post it to their database.
Regards
Aashish Sinha

Is a third-party tool required for data extraction to non-SAP system?

Hi,
I want to extract data to non-SAP systems with the open hub service.
If I choose Database tables as open hub destinations, I would like to know if a third-party tool is mandatory and if it's possible to send data directly from database tables in BW to non-SAP systems.
Many thanks
Ella

you can choose a flat file on the application server and then transffer the file from the application server to other server where you want to use.
in case you want to use the table in the open hub service. any other software that can connect to oracle db / the databasee you have and can access the data from the table.
Regards,
Bwer
Assign points if helpful.

ALE: Sending IDOC inbound from non-SAP system

Hi
How does one need to setup the SAP system to accept data from an external non-SAP system. Should one setup some sort of conection to trigger an import to SAP?

Hi,
On the SAP side you need to create a partner profile in T.code: WE20 of type LS. And add the message type, idoc type in the inbound parameters section of it.
And you must also specify the partner number you created here, on the IDoc control record.
This link from SAP help, will provide some addition data.
<a href="http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6524507d11d18ee90000e8366fc2/frameset.htm">http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6524507d11d18ee90000e8366fc2/frameset.htm</a>
Hope this helps.
Regards,
Sumant.

IDOC's sending to XI from NON-SAP system

I need to send one IDOC from a NON-SAP sytem to XI. In my scenario I've configured a receiver IDOC adapter with the suitables RFC destination and Port for the SAP R/3 receiver system. We achieve this sending by using the following URL: "http://:/sap/xi/engine?type=entry" but we don´t get any message in XI. We don´t know if we are doing it properly.
Could you help me?
Thank you in advance.
Juan Pablo.

Hi Juan,
Did you try the HTTP client tool that Michal gaves you?
Attention: the URL address that this tool or any other client who wants send messages via XI with http is: http://<our-server>:<http-port>/sap/xi/engine?type=entry and not -> http://<our-server>:<our-port>/sap/xi
This URL must be set on the pipeline of XI Business System (role-> Integration Server) as well on integration server configuration.
If you have http port and adapter_plain service (sifc) running it should be working!!!
Open your browser and put the Integration Engine URL http://<our-server>:<http-port>/sap/xi/engine?type=entry
If its running you should be see this soap message:
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP:Header />
- <SOAP:Body>
- <SOAP:Fault xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<faultcode>SOAP:Client</faultcode>
<faultstring>Empty HTTP request received</faultstring>
<faultactor>http://sap.com/xi/XI/Message/30</faultactor>
- <detail>
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIProtocol</SAP:Category>
<SAP:Code area="MESSAGE">EMPTY_HTTP_REQUEST_RECEIVED</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Empty HTTP query received. No message processing possible</SAP:Stack>
</SAP:Error>
</detail>
</SOAP:Fault>
</SOAP:Body>
</SOAP:Envelope>[/code]
Cheers,
Ricardo.
Message was edited by: Ricardo Quintino
Message was edited by: Ricardo Quintino

Can I use export my SAP created master data in a non-SAP system?

Hello,
I am about to start a large integration solution with my SAP customer and they are concerned about licensing. What they want to do is export their GL, cost centre and WBS master data to an external system via integration (probably custom ABAP, or home built BAPI/RFC). The external system then uses the accounting data to determine where to post FI or MM documents back into SAP via custom ABAP, BAPI or maybe IDOC).
Is this OK? Are there any licensing issues with master data used externally and posted back in via custom ABAP or standard BAPIs/IDOCs?
Thank you in advance,
Geoff

Hello Geoff,
Yes, even indirect access to SAP transactions or data needs to be licensed properly with SAP. Your customer should contact their SAP account rep to discuss the exact use case. Indirect access via certain types of certified integrations may qualify for Platform User License pricing, but there is no generic answer, and it is best for the customer to discuss their specific case directly.

Encrypt data send from a non-SAP system to ECC.

Hi,
We are tryign to encrypt the credit card details send from web (non-sap system) via a xml file to ECC.
From Basis side, I have exported the public key from the ECC for the web server to encrypt the CC details while sending via xml.
The external web consultants encrypted the cc detail with the public key and send it via xml but that was not able to decrypt at the ECC side.
The developers were using the FM 'CCARD_DEVELOPE'at ECC to decrypt the data in the xml file. It was saying SSF error: No data transfered.
Meanwhile SAP CryptoLib is installed and credit card encryption/decryption is working fine for CC details entered via GUI interface.
Is there anything I am missing out here to encrypt CC details send from a Non-SAP system to ECC.? Do we need to load the SAP cryptolib in the non-SAP system to ecrypt this data at the senders end. Or is there a alternate solution for this ?
We are in ECC6.0/RHEL/Oracle10204.
Appreciate your help.
Thanks

Hi Nelis,
Thanks for your reply.
This note does not get any information regarding encrypting data from a non-SAP system to SAp system.
I am looking setup/information for encrypting data from a non-SAP system to SAP system.
Thanks

HOW TO SEND THE REPORTS AND THROUGH XI TO NON -SAP SYSTEM

Hi Experts,
I want to know how to send the reports and smartform through xi to another system. All the post blogs are just explaning only about the FILE-TO-FILE, FILE-TO-IDOCS scenarios only.

Hi,
XI is the middleware that to be used to transfer the data between various systems and even you could design the Business Processes with it.
In R/3 the smartforms, are generally converted to PDF and then have to send it across to Non SAP systems. Similarly you can convert the smartforms to pdf format and keep it on application server. XI will pick up that pdf and will send it to Non SAP system either as mail or as an attachments.
ABAP reports are normally used to re-present the data. If you need to transfer this data across the Non SAP systems then you have the IDOCs to be generated, RFC or ABAP Proxy to integrate this data with Non SAP system.
XI is not restricted only upto file to file or file to IDOC scenarios. It have enormous capabilities to involve various Business Processes as well integrate various SAP or Non SAP systems.
If need anymore specific details, please let us know.
Thanks
Swarup

How to send a IDOC-XML to a non-sap system

Hai Frnds,
Can you give me a hint , if i would like to Convert a IDOC into xml and need to send it to a Non-sap system.And can i use change pointers here...
i have have similar one but it stores in the Front End system only....
waiting for ur replies...

Hi Mr. Jeevan,
And can i use change pointers here..>>>.
i think it wont be useful.. as change pointer only replicates master datas in the target system.
Actually u can use CHANGE POINTER in such cases where When ever changes occur in the field values then idoc triggers automatically and send changed information via ALE to other system.
for example:
u r setting up ALE for material master.
suppose u change material description in one side then change pointers triggers idoc and generate idoc with changed description and send to other end.
main use of change pointers is to track changes and send to other end if there is any changes.
i will suiggest u to follow this....
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e07dcaa0-a92b-2a10-3a96-b3d942bd1539
also see
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
regards
biplab

Distributing customizing(control) data from SAP ECC to a non SAP System

Dear Experts,
I am currently working on an interface for distribution of different data to a non SAP System. One of these is customizing data (Company code, purchasing org. plant etc). The system expects a file and we shall implemet the following scenario: IDOC>XI>File
Questions:
1. Is it possible to use CONDAT Idoc to transfer customizing data to a non SAP System or is this only used for synchronisation of data between SAP Systems?
2.In case CONDAT cannot be used would you recommend creating a custom table, message type etc. for this case?
Please advise.
Thank you so much

Hi Narasimha,
We can do this with the help of PI. Please find the below link.
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/404ee507-3fbc-2e10-00bc-be90ab28d036?QuickLink=index&overridelayout=true&52239687237174
Its from SAP PI to any other system.
Check this link too.. Proxy with Attachments.
Regards,
Siva

Extraction of InfoCube data from BW system to non SAP system

Hello All,
Is the extraction of InfoCube data from BW system to non SAP system availbale only for BW 3.5 release ? If yes, how can we extract the InfoCube data to a non SAP system with SAP BW 3.1 ?
Hope to get some help.
Best Regards,
Loveline.

Hi Gianfranco,
Thanks for replying.
Yes I know that open hub service is the appropriate technique to extract data from the infocube.
But if we look at SAP Netweaver documentation : Prior to SAP NetWeaver '04(since the SAP BW release I am working is 3.1); We find that we have the option to extract to a DB table or flat file.
Now if we look at SAP Netweaver documentation : SAP NetWeaver '04; In addition to the above we have the option to extract to a non SAP system.
My requirment is to extract data from InfoCube to a non SAP system. The SAP BW release I am using is 3.1
Best Regards,
Loveline.

Http communication with non-sap system

Hi ,
We have a requirement to send OM related data to a non-sap system using HTTP post in XML format and receive the response from that external system. We are on ECC 6.0 and we cannot use XI at this time.
What would be the correct approach to do this? I read that we could use ICM for HTTP communication am I on the right track?
Thanks

Hi ,
We have similar type of requirement, if you have the solution then let me know .
Thanks in adv
Vishnu

Non-XI HTTP Communication with non-sap system

Hi ,
We have a requirement to send OM related data to a non-sap system using HTTP post in XML format and receive the response from that external system. We are on ECC 6.0 and we cannot use XI at this time.
What would be the correct approach to do this? I read that we could use ICM for HTTP communication am I on the right track?
Thanks

What setup do we need for this ?
We are on ECC 6.0. I am trying to run the program, I am getting http_communication_failure = 1 in the receive function.
I am not sure if I am missing any authorizations/setup.
Thanks for your help.
VV

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

Send data to other non SAP system

Similar Messages

Maybe you are looking for