Synchronising Two SAP Systems

Hi All,
        I have a generic doubt in synchronising two SAP systems. Say, I have systems A and B connected to 2 different servers respectively. Whenever I create a notification in system A, same should be created in system B, if any changes are made in system A on the same notification, that should also be reflected in system B and vice versa, same is the case for Purchase Requisitions, Purchase Orders and Maintenance orders.
        I tried with IDOC configuration but I am not sure how the standard IDOC message type gets populated, so I manually populated the segments and tested. That's working fine. But that is not what I want, everything should happen automatically.
       Please give a brief idea on how a standard IDOC gets populated and kindly advise me on what all possible solutions that I could try for.
Thanks in Advance,
Cheers,
Vivek.

Hi Madhu,
Thanks for the response.
I have already tried with ALE processing. But, the data is not getting populated in the standard idoc type. Instead it is getting populated in another idoc type as there is a configuration done already in NACE for that idoc type.
By going through some links from google, I have found that configuration in the NACE transaction should be done for the corresponding output types, with medium as "Distribution (ALE)". But this will not work out for notifications as there is no standard output type for notifications.
Cheers,
Vivek.

Similar Messages

Interfacing two SAP systems for data collection

hi,
A scenario. i have two sap systems, one is 4.7 and another is ECC. based on one value in 4.7 i want to collect data from ecc. this has to happen thru XI. so shud i write a function module in ecc which takes as parameter the input value and picks data from database and exports the same and enable this function module as RFC ?
so then from XI this function module can be called with the required input parameter ? can anyone give me the code/steps or how to do this ?
thks

Hello,
why do you want to use XI? I would create a RFC-enabled FM in the ECC system and a RFC destination (transaction SM59) in the 4.7 system (calling the ECC system). Then create a report in the 4.7 system, getting the value and calling the RFC in the ECC system via:
CALL FUNCTION <RFC function> DESTINATION <RFC-destination>
Best regards
Stephan

Two SAP systems in the same host "no files processing"

Hello!
I have two SAP Systems installed on the same host.
If I execute redo logs archiving from DB13 I get the error "no files processing", because of I already executed redo logs for the other SAP system on the same host.
How can I set up this issue?
Thank you very much
regards
Thank you very much
regards

Hello!
I have two SAP Systems installed on the same host.
If I execute redo logs archiving from DB13 I get the error "no files processing", because of I already executed redo logs for the other SAP system on the same host.
How can I set up this issue?
Thank you very much
regards
Thank you very much
regards

Two SAP systems, same smartform, different print outputs

We have two SAP systems, because of the different business areas that our company has.
We develop a smartform with a custom style which has Gill Sans MT as default font. The smartform is printed directly into PDF format.
On system A on all environments it works fine and we transported it to system B.
On system B the output on PDF format comes in bold, all the characters are bold. This happens on all environments. On preview we don't see bold font but the spacing between characters is larger than expected (for example, a date is printed in two lines of a cell).
I've checked the settings on SE73 and they are the same on both systems.
I've also created a second style were I've taken out all bold settings. On system A, the smartform' style was changed to this new one. The changes were transported to system B, and still it prints all bold.

Thanks for the replys. I think this is an answer to both.
Checked SPAD and differences are:
1. output device LOCL:
System A:
- Device Type: ZSAPWIN
- Host Spool Access Method: F
System B:
- Device Type: SAPWIN
- Host Spool Access Method: G
2. Device Type:
System A:
- has two custom formats (none used on this specific smartform)

RFC connection between two SAP systems (with SAP router)

Hi!
I would like to set up a RFC-connection from SAP Solution Manager to other SAP system.
The network connection between the servers is VPN.
How can I set up this RFC-connection, if my connection between two SAP systems looks as follows,
(I use the following SAP routers)?
my server --> customer
my server --> internal SAP Router server xy (10.101....) --> SAP Router customer 2 (10.1....) --> SAP System customer (134....)
Back-way
SAP Systeme customer --> SAP Router customer (134.1....) --> internal SAP router (212.6....) --> my server
How can I set up this RFC-connection, if my connection between two SAP systems looks as follows,
(I use the following SAP routers)?
something like:
/H/10.101..../S/sapdp99/H/10.1.4..../S/sapdp99/H/134...
Thank you very much!
regards
Thom

Same answer as in the other forum where you cross posted....

Two SAP system in one host and one oracle software

Hi SAP Gurus,
We want to install Two SAP system (PR1 & PP1) in one host(Prdb05) and one database (Oracle). I dont want to do MCOD.
I am very confuse about what changes i need to make before start the install of PP1. Actually i do not required to install oracle software again. am i correct ?
also i do not required to install oracle client again.am i correct ?
Will it take software automatically ?
In SAP note 350251 they asked me to run ./runinstaller !!! but when we
are not installing software again why we need to to execute that.
Will you please guide us for the same.

Hi , This is what you have to do .
Couple of questions before i answer anything
1) Is your first SAP system installed ?
2) is this High Available system
What Oliver suggested is a valid option on Windows , but not on Unix .
In Unix you might face problems for user,groups because the user for ORACLE_HOME should ideally be ora<SID>, and if you have 2 SID and one ORACLE_HOME , which user will you give ?
So , it is better that you have 2 seperate oracle software installed , 2 seperate ORACLE_HOME , 2 seperate filesystems for oracle software .
Hope you understood , what i am trying to say .
Thanks
Prasannna

Single billing from two SAP systems to common customer

Our company was recently purchased by another. We have common customers. The business would like us to provide single billing to these customer out of the two SAP systems until we can complete the global merge into a single SAP system. Is there a way to accomplish this?
Best regards.

if we want to the combined billing for a customer. there are some restrictions: those are difference between the header data, billing date, payer, country is different we cann't bill in sigle invoice.
regards
rp s

Is it possible to install two SAP system with same SID but different instance numbers on one host?

Is it possible to install two SAP system with same system ID (SID) but different instance numbers on one host?
If yes, then how?
If no, then why?
Thanks in advance.
Regards,
Sarim

Is it possible to install two SAP system with same system ID (SID) but different instance numbers on one host?
Yes, it is possible. If one is CI (PAS) and the second one is an AS (AAS). In this case there will be only one database.
If you are talking about two separate SAP systems with separate databases (Eg: A BI and an ECC) with the same SID then the problem will be with the database (Eg: Oracle)
The database will be installed under /oracle/SID/112_64 (ORACLE_HOME) unless one database is running on 10 G and in that case the ORACLE_HOME will be /oracle/SID/102_64
The next issue will be with the SAP file systems like /sapmnt/SID
The most important problem will be with the switch to the sidadm and orasid users and the conflicts there. If there is a need to stop one of the SAP systems and if you do a switch to sidadm and issue a stopsap command which system will be stopped ?
These are few of the many problems I can think of.
So if we are talking about two separate systems with their own databases I would rule out the possibility of having two systems with the same SID.
Regards
RB

DB Copy (MSSQL) between two SAP systems with different level and Components

Hi,
we have a SAP system release mysap 2004 SR1 and for "the upgrade project to SAP ECC 6.0 " we installed a new mysap 2004 in a new hardware (sap03) where we have also solution manager running. The new installed Mysap 2004 SR1 is alos running fine in the new hardware.
Now we would like to do DB copy from the old system (sap02) to the the new system sap03 and then we will do the upgrade to SAP ECC 6.0.
After I compared the two systems I have following questions:
1) there are 4 Software Components which are not in the new system (sap03). This are:
PI
FIN_BLERP
BP_INSTRASS
Is this necesary for the DB copy or we do not need this to be able to do the DB copy?
2) The Software Components Level is not the same. Should we have the same level to do the DB Copy?
Thanks in advance
Best regards
HanseAtik

Hi Juan, hi Clas,
just to be clear and to not stuck on the the way:
The systems are as follow:
1) the source system:
                     - Windows Server 2003,
                     - MSSQL Server 2005 with 32 bit.
                     - Mysap 2004 SR1
2) Target system:
                   - Windows Server 2003
                   - MSSQL Server 2005, with 64 bit.
                   - Mysap 2004 SR1 (with less Support package level and no PI, FIN_Basis, BP_BLERP and BP_INTASS coponents)
I hope this will work. could you post the link the DB Copy guide we are talking about?
By this way we will be sure that we are talking about the same DB Copy. Otherwise any mistake in this step will cost more work and time.
Thanks in advance
Best regards
HanseAtik

Calling Web Services between two SAP systems.

Hi Experts,
I am trying to trigger a web service created in one of the SAP system from a different R/3 system through WDA.
Kindly help me out on what are the configurations to be done like linking two systems (do i require this?) etc..
I have successfully obtained the WSDL file, but could not use it in my second system. It says , it encountered an error. I wonder if i am required to do any configurations.
All suggestions are welcome.
Thanks and Regards,
Anto.

Hi Antony,
By Proxy Object, I meant Class to consume WebService in your second system.
Lemme summarize, what you have done and lemme know where I am wrong.
System A.
You exposed an RFC enabled Func Module or BAPI as a webservice.
After this you have checked it using WSADMIN, and you have tested this as well.
And finally you saved the WSDL file of this Web Service.
System B.
you create a Proxy Object as specified in the link I provided.
you create the RFC destination n did the Logical Port Configuration as per that link.
Now you can use this proxy class any where , in any abap code.
you can use this in WDA as well.
But before doing so, I would suggest to write a test report as suggested in the link and test if your webservice is working fine.
Now please tell me where did you do the things differently.
Regards
Pushkar

Two SAP Systems in MSCS Oracle

Hi,
I would like to install two systems in MSCS Oracle with two nodes. In the first node I'll install a PI, and in the other one SAP Portal. My question is :
How many Oracle Database Engine should I install ? Or I should install one Oracle Database Engine with two oracle instance ?
Thank's in advanced
Francesc

Hi Thomas,
Would appreciate if you clarify following on Windows Server 2003 - Oracle 10g.
1 oracle-homes with 2 database
The 2 databases are not completly idependent because they share 1 oracle-home. if you want to update oracle you need to update both databases at the same time.
What are the points which needs to be taken care before using this option. During installation it prompts for Listener name and port - so should we use the same as used in first SAP instance.
2 oracle-homes with 2 database
The database are completly idependent. You can update both db's separately
Is there any pre and post installation steps before installation of second instance. In this case, listener would also be independent. And owner of SAP instance can start its own SAP instance.
Thanks
Davinder

Synch of two sap systems separated geographically

Hi Experts,
I wanted your advice on the above..
A user logs into SAP GUI from a remote machine but is unable to reach the server...
What are the possible ways to ensure the business is not affected by this???
Can we have a local instance of sap runnin on the client machine and then synchronise the client and server machines when the network is back online???
are there any othe rways we can accomplish this??
Pls share your thoughts
Regards,
Teja

A user logs into SAP GUI from a remote machine but is unable to reach the server...
What about other applications (non sap)?
Regards,
Nick Loy

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

Call a remote RFC from one sap system to to other sap system

Hi experts,
I'd like to know how to connect two sap systems via RFC. The two systems are in the same network and I'd like to know how to set up the SM59 in order to create the destination to the RFC.
Any help in configuring the SM59 to stablish the communication?
thanks a lot.

You can do that from t-code SM59 or SALE
This step is to create the Logical system for the remote system.
A logical system allows SAP internal functions to interface with external systems, either an SAP system or a non-SAP system. We also need to have a logical system name for the SAP system,.
SALE is the transaction.
Expand the Sending and receiving Systems and then the Logical systems click on define logical system.
You will receive the informational message, The table is cross-client. Click the green check icon to continue.
Now click on the New Entries.
The Screen appears like this here you will be giving the LS name and the description of that.
After u click on the save button a window will be displayed like the bellow asking for the Request ID. Here we can create our own or we can use the existing one.
After that we see the message blow as DATA SAVED.
Now the step is to Link the LS to the client.
Click on the Assign Client to LS .
The Screen as below will be appearing.
Double click on the client on which u r going to work and there specify the SAP LS(IDS47800) and you also need to specify the City and Std Currency and the client role as Test for the drop down box.
Register the RFC server module with the
SAP gateway
The RFC (Remote Function Call) destination is a logical name used to define the
Characteristics of a communication link to a remote system (in our case, LS for the remote system) on which a function needs to be executed. In ALE, the RFC specifies information required to log on to the remote SAP system to which an IDoc is being sent.
To register the RFC Sever Module as the RFC destination:
SAP transaction code: SM59 Type /nsm59 on the SAP input window and press the
Enter key.
Expand the TCP/IP connections directory.
Give some name to the RFC Destination (ALESERVER), Connection type as T. and fill the Description field.
In technical settings give the program name as you desired.
Click on save
regards,
srinivas
*reward for useful answers*
Message was edited by:
XI_Novice
Message was edited by:
XI_Novice

Send IDOC from SAP system to IX but can't see any message in SXI_MONITOR

Hi all,
I have built up an XI system and configured an IDOC to IDOC scenario between two SAP Systems. After completed all configuration necessary:
1. Configuration on Source Side (SAP System that send IDOC) and on Target Side (SAP System that receive IDOC) is OK.
2. SLD is OK: Technical System and Business System are correct for these two SAP System.
3. Integration Repository: all designed Object is OK.
4. Integration Directory: all configuration is OK. "Test Configuration" Function is OK.
5. Runtime WorkBench: is OK. "Test Message" Function of "Integration Server" is OK.
In general, it is all OK.
But when i send an IDOC from SAP System Sour Side (Outbound IDOC from Source Side is OK), on the XI server i can't see any message in Tcode SXI_MONITOR. In this case, my XI server didn't receive any IDOC Message from this Source Side, and so that my XI server can't process and exchange any IDOC sent from Source Side.
Anyone can please help me to explain this problem: why my XI server can't receive any IDOC message from SAP System Source Side when all configuration is OK? Do anyone see the same case as this case?
Thanks a lot for all in advance,
Best regards,
Vinh vo

Hi,
Possible checks
At R/3 side
1) Check in SMQ1 and SM58
At XI Side
1) Check in SMQ2 and IDX5
Check this
http://help.sap.com/saphelp_nw04/helpdata/en/6a/e6194119d8f323e10000000a155106/frameset.htm
Regards
Seshagiri

Synchronising Two SAP Systems

Similar Messages

Maybe you are looking for