Is it possible to receive IDOCs from a non-SAP system?

Hi,
I'm facing a problem where I have to configure SAP MII (12.0) to receive IDOCs from a non-SAP client. Is it possible? I'm dealing with a system named Hydra (developed by MPDV) and I'd like to know what I should configure in Hydra systems in fields like: PROGID, GWHOST, GWSERV, SYSNR, CLIENT etc.
Anyone can help me?
Thanks a lot in advance

Unless Hydra emulates ECC sending IDOCS, then you just might want to use the WSMessageListener (http://help.sap.com/saphelp_xmii120/helpdata/en/45/6a86ac88130dece10000000a11466f/frameset.htm) and configure your message processing rules accordingly.

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

Using UWL from a non sap system

We are intgerating OTM (Oracle transportation management system) with SAP.
We need to have a single point where the users track all their norifications.
Is it possible to add notifications (task or error) into sap UWL from a non sap system.
If yes what are the main steps to do it?
Which set up must be done in SAP UWL to manage this?
Thanks in advance
Regards

Do some searches about "UWL custom connector" or "UWL custom connector API". You should find pretty good documentation about this subject.
Regards,
Karri

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

One issue regarding PPDS OP.confirmation from Legal Non-SAP system

Dear Experts
we met a BAPI function issue regarding PPDS Operation.confirmation from Legal Non-SAP system.
scenario is as following:
we want to build the interface between PPDS and non-SAP system, regarding OP. and order confirmation inbound processing.
now we input simulated inbound date and test using BAPI: BAPI_MOSRVAPS_CONFOPRMULTI
but we find a problem, even we set different value for fields ‘ duration’ in function. after call BAPI, It didn't reflect the 'net duration' or 'remaining duration', these fields not changed through check in Tcode:/SAPAPO/RRP3 for single operation.
In the meanwhile , but it works for fields 'confirmed Yield' and fields 'confirmed Scrap' for single operation.
my questions is that: if we need to synchronize the operation confirmation( including confirmed yield,confirmation scrap, duration)，do we use the correct BAPI for this or do we need an additional BAPI, please hints.
Thanks a lot! any feedback would be welcome!
Best Regards
Kevin

Hi Kevin,
Yes you use the right BAPI.
you have to use table OPERATION_CONFIRMATION.
You cannot just set the duration. You have to trigger time event confirmations.
The field duration according to the documentation currently not supported.
You need to use CONFIRMATION_TYPE
0100 Start of Setup
0150 End of setup
0200 Start of processing
0300 Partially complete
0350 Complete
Not sure if all confirmation types are supported by the BAPI.
You can also set start and end time but not sure either whether it is supported or not.
Regards,
Uli

BAPI calling from a non SAP system.

Dear Experts,
I would like to know how can I call a BAPI from a non SAP system, a breif idea/with example ( from any non SAP system ) and sample coding will be highly appreciated.
Thanks, Sudeep..

Hi,
there are couple of possibilities. For example you can export your BAPI as a web service and then use standard tools for web services. There are also libraries to allow RFC calls from different programming languages. You can see all possibilities such as SAP Java connector supported by SAP on https://service.sap.com/connectors. There are also additional libraries not supported by SAP such as SAPRFC extension module for PHP. As you can see there are so many ways how to call RFC enabled FM. You can find examples for each method here on SCN.
Cheers

IDoc adapter with Non SAP systems

SAP XI 3.0 help says:
You can use the IDoc adapter to connect SAP systems (as of release 3.1) and non-SAP systems with the Integration Server using native IDoc structures
What does this mean?
-Naveen.

Hi Naveen,
Let me give a use-case in one of our projects ....we have 2 middlewares in our landscape...webmethods and XI...and in one particular instance there was a need to send an FI IDoc from webmethods to XI and forward it to R/3....
In this case, the webmethods was treated like any other sap system for receiving IDoc into XI(with settings in IDX1)...
Hope this might clarify a little bit...
Thanks,
Renjith

Data elements for IDoc Segments to non-SAP system

Hi,
I need to create IDocs for transferring data to non-SAP system. When I create segmet fields should I create new data elements for all the fields with attributes specific to receiving system? Because there are many fields where the field attributes of SAP system do not match the corresponding fields of receiving non-SAP system.
Thanks in advance!!
Regards,
Sriram

Hi Sriram,
When I create segmet fields should I create new data elements for all the fields with attributes specific to receiving system
Is it custom segments .
Regards,
Madhu.

Query regarding accessing of Webdynpro application from a non-SAP system.

Hi,
I have developed a webdynpro application and I want the users from non-SAP systems to access it from their browser. User will not have to enter the username and password of the SAP system. How will I achieve this? Any suggestions?

Hi Anirban,
you can assign a user in the service of your web dynpro application.
Call transaction SICF and open the service to your web dynpro application.
Within the tab "logon data" you can enter a user/password.
You should not assign a dialoug user.
For productive environment, have a look at all the other options like SSL
and maybe you have to do some more configuration to make it secure!!!
Keep in mind, that all "internet" users are working now with the same SAP user/authorization.
Kind Regards,
Andreas

Issue with Chinese characters while sending IDOCs from PI to SAP system

Hi,
We are working on File to IDOC scenario where in some of the fields are having Chinese characters. In SAP system, we noticed that the Chinese characters are getting replaced with # where as in PI output payload we are able to see the correct Chinese characters. The systems involved are PI 7.4 and SAP ECC -6.0.

Like in dual stack where we have an option to choose unicode/ non-unicode, i don't see any option in single stack.
However not sure if it works but you can give a try..
I assume you have created the RFC destination in NWA.
Go to RFC destination ->Specific Data -> Advanced Settings - here we have an option to mention the code page.
You might want to mention the code page for chinese char and see if it helps..
Before doing this, do checkMark's suggestion.

Sending IDoc from Non-SAP system to XI

Dear all,
We have a non sap system which needs to send IDoc to XI, Please could you answer my following four questions
1. What should be the values for the following fields in the IDoc control record
e.g. RCVPRN = <logical system name of XI>
SNDPOR
SNDPRT
SNDPRN
RCVPRT
RCVPOR
2. How does XI decide which port(idx1) to be used when it receives an idoc
3. The third party system is a non sap one, so it does not have a client no, so I would assume, I need to use another SAP system as a meta data provider, in that case, how would i tell XI to use that port when it receives IDocs from the non-SAP system ?
4. In what step does XI use the logical system name of the Business system(in SLD)?
Thanks in advance
cheers
danus
Edited by: Chidambaram Danus on Jan 25, 2008 2:21 PM

Hi
there is bit wrong interpretation of the statement
If the sender system is a non-SAP system, the sender service is identified from the logical system name of the sender port.
If the sender system is nonSAP it indicates taht the data is coming to XI from non sap systems such as file, database, webservice etc. to XI and from XI it will pass to sap as IDOC inbound.
For this you need to create the logical system in SAP (receiver) and pass on that value to IDOC header.
You could maintain it in the Business service used for Sender system (nonSAP). here it will be available in the tabs ---> History.
note : IDOC is the concept of data container in SAP, you will not be able to have the IDOCs in non sap systems...
Thanks
Swarup
Edited by: Swarup Sawant on Jan 25, 2008 2:54 PM

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

Data load into SAP ECC from Non SAP system

Hi Experts,
I am very new to BODS and I have want to load historical data from non SAP source system into SAP R/3 tables like VBAK,VBAP using BODS, Can you please provide steps/documents or guidelines on how to achieve this.
Regards,
Monil

Hi
In order to load into SAP you have the following options
1. Use IDocs. There are several standard IDocs in ECC for specific objects (MATMAS for materials, DEBMAS for customers, etc., ) You can generate and send IDocs as messages to the SAP Target using BODS.
2. Use LSMW programs to load into SAP Target. These programs will require input files generated in specific layouts generated using BODS.
3. Direct Input - The direct input method is to write ABAP programs targetting on specific tables. This approach is very complex and hence a lot of thought process needs to be applied.
The OSS Notes supplied in previous messages are all excellent guidance to steer you in the right direction on the choice of load, etc.,
However, the data load into SAP needs to be object specific. So targetting merely the sales tables will not help as the sales document data held in VBAK and VBAP tables you mentioned are related to Articles. These tables will hold sales document data for already created articles. So if you want to specifically target these tables, then you may need to prepare an LSMW program for the purpose.
To answer your question on whether it is possible to load objects like Materials, customers, vendors etc using BODS, it is yes you can.
Below is a standard list of IDocs that you can use for this purpose to load into SAP ECC system from a non SAP system.
Customer Master - DEBMAS
Article Master - ARTMAS
Material Master - MATMAS
Vendor Master - CREMAS
Purchase Info Records (PIR) - INFREC
The list is endless.........
In order to achieve this, you will need to get the functional design consultants to provide ETL mapping for the legacy data to IDoc target schema and fields (better to ahve sa tech table names and fields too). You should then prepare the data after putting it through the standard check table validations for each object along with any business specific conversion rules and validations applied. Having prepared this data, you can either generate flat file output for load into SAP using LSMW programs or generate IDoc messages to the target SAPsystem.
If you are going to post IDocs directly into SAP target using BODS, you will need to create a partner profile for BODS to send IDocs and define the IDocs you need as inbound IDocs. There are few more setings like RFC connectivity, authorizations etc, in order for BODS to successfully send IDocs into the SAP Target.
Do let me know if you need more info on any specific queries or issues you may encounter.
kind regards
Raghu

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

Bank Reconciliation (India Specific) for information from Non SAP systems

Bank Reconcilaition to be performed in SAP ECC6 on data received from A Non SAP system
Following is the scenario:
1. Data is received in to SAP for Cheques deposited in to the Bank with a unique Key feild
2. A Bank Reconciliation process is Run on the Line Items received using the Cheque numbers and amounts
3. The honored Cheques need to be Cleared in SAP
4. SAP will require to generate a report listing the Dishonored Cheques and also populate the Key feild against the Dishonored Cheques in the Report
Kindly help as to how this can be acheived in SAP, as teh Automated BRS process is executed sequentialy for every line in the Bank statement received.
Thanks in Advance

Hi ,
Check this link
<a href="http://help.sap.com/saphelp_nw04/helpdata/en/58/54f9c1562d104c9465dabd816f3f24/frameset.htm">DB Connect</a>
<a href="http://help.sap.com/saphelp_nw04/helpdata/en/fe/65d03b3f34d172e10000000a11402f/frameset.htm">XML Connect</a>

Is it possible to receive IDOCs from a non-SAP system?

Similar Messages

Maybe you are looking for