Modify data in another R/3 system ?

hi,
i want to modify database table in system 1 through a RFC called in system 2.
and the RFC works fine in system 1 when testing through F8, that is the table is modified correcttly according to the given data. but when called in system 2, the database table can not be modified anyway. And more, i can't debug the RFC no matter what i try, open both system debug option in system 2 and external debug option in system 1.
finally, i check the destination set for system 2 in system 1 by SM59, the security option said it's not a trusted system . I wander if it's this option prevent me from modifying the database table and external debug ?? and better with some suggestion .
thank you !

got it

Similar Messages

Reading data from another database

Hi Folks!
I need to read some data from another non-sap system database to validate something in R/3. Does this is possible. If it is possible how could this be achieved?
Thanks in advance for your help.
Regards,
Gilberto Li

There are a couple of ways to do this. One, you can create an executable on the other non-sap system that you can call from SAP as a system command. So let us say you write a unix script that takes a value as input and returns a flag as output. Within the script you will check that value against this non-sap database. In SAP, you will create a system command in SM69 and then execute it in your program via function module SXPG_COMMAND_EXECUTE.
Alternatively, you can use the RFC route but you need to setup RFC connection between the two systems.
You can also bring this validation table into SAP as a one time or periodically updated table and then do the validations within SAP.

Archive/Move files based on Modified Date range to another Library Using PowerShell while retaining Metadata

Hi,
I am trying to archive files from a SharePoint 2010 document library by moving them to another library that's a dedicated archive/folder/library. The files to be moved are selected based on their modified date column value that should range between any time
in the past to January 1st 2012.
Also, to be able to retain the tags and cloumn values after the move. Open in explorer does not bring along the user added tags.
I tried to edit this script
$WebURL = "http://mysite.com/";
$ListDisplayName = "Crawl Test Library";
$ArchiveFolderName = "Crawl Test Library Archive";
function moveItems ()
trap
#make sure we dispose of these in the event of an error to avoid memory leaks:
write-host "Error - disposing of objects...";
$Web.Dispose();
$Site.Dispose();
[Microsoft.SharePoint.SPSite] $Site = New-Object Microsoft.SharePoint.SPSite($WebURL);
[Microsoft.SharePoint.SPWeb] $Web = $Site.OpenWeb();
[Microsoft.SharePoint.SPList] $List = $Web.Lists[$ListDisplayName];
$FolderToMoveTo = $List.RootFolder.Url + "/" + $FolderName;
$ItemMoveCount=0;
$Query = New-Object Microsoft.SharePoint.SPQuery;
$Query.Folder = $list.RootFolder;
$camlQuery = "<Where><Leq><FieldRef Name='Modified' /><Value Type='DateTime'>2012-01-01T00:00:00Z</Value></Leq></Where>"
$Query.Query = $camlQuery
$Query.RowLimit = 2200; #limit query because of large folder
$List.GetItems($Query) |
Where {$_.ContentType.Name -ne "Folder"} |
foreach-object {
#Line below will simply output to console and demonstrates another .NET call
[System.String]::format("Moving Item {0} with ID {1}...",$_.Name, $_.ID.ToString());
$Web.GetFile($_.Url).MoveTo([System.String]::format("{0}/{1}",$FolderToMoveTo,$_.Name));
write-host "Success...";
$ItemMoveCount++;
write-host "==============================================================================";
write-host "Complete! -> Moved " $ItemMoveCount " Items to directory " $FolderName;
write-host "==============================================================================";
#dispose:
$Web.Dispose();
$Site.Dispose();
#garbage collection
[GC]::Collect()
to do that but it doesn't seem to work. I am no guru in powershell yet so any help is appreciated.
Thanks.

This solution gets the job done. Much thanks to
Ian Hayse
NB...The Modified and Created dates are gonna reflect runtime dates now
$web = Get-SPWeb "http://sharepointed.com/"
$list = $web.Lists["Shared Documents"]
$spQuery = New-Object Microsoft.SharePoint.SPQuery
$spQuery.ViewAttributes = "Scope='Recursive'";
$spQuery.RowLimit = 2000
$caml = '<Where><Lt><FieldRef Name="Created" /><Value IncludeTimeValue="TRUE" Type="DateTime">2014-01-01T04:06:45Z</Value></Lt></Where> '
$spQuery.Query = $caml
do
$listItems = $list.GetItems($spQuery)
$spQuery.ListItemCollectionPosition = $listItems.ListItemCollectionPosition
$listTotal = $listItems.Count
for ($x=$listTotal-1;$x -ge 0; $x--)
try
$listItems[$x].CopyTo("http://sharepoint/Docs/Documents/"+ $listItems[$x].name)
Write-Host("DELETED: " + $listItems[$x].name)
$listItems[$x].Recycle()
catch
Write-Host $_.Exception.ToString()
while ($spQuery.ListItemCollectionPosition -ne $null)

Another user or another operation modified data

I have a problem in updating document numbering setup in AP invoice
Another user or another operation modified data; to continue, open the window again '' (NNM1) (ODBC -2039) [Message 131-183]
SAP 8.81. PL07
I disabled also all Add-ons , but still the problem continue,
Thanks

hi,
when setting document numbering series it is recommended that you should have an exclusive access in the database. to achieve this you need to lock all users except your username. in the way no other user can log on in the system. also you need to use a superuser account.
regards,
Fidel

Load file on db with file system last modified date info

Hi,
i have e procedure for load a file on my DB table.
How to write on my table the last modified date read for file system?
Thanks in advance
Marc

Try this example to use dbms_pipe for executing the OS commands to get the last modified date of a file.
calling shell script from sql procedure

Another user or another operation modified data,to continue open windows

Saludos Estimados:
tengo la siguiente situación, tengo un cliente que gestiona sus cuentas a nivel articulo, estamos actualizando sus cuentas ya que algunas apuntaron mal, pero cuando lo hacemos por DTW manda el siguiente error
another user or another operation modified data,to continue, open windows again (OBDC-2039) Application-defined or object-defined error65171

esta es la nota de SAP que nos sugirio y se soluciono.
When you update the warehouse info via DTW, you need to set the LineNum value in ItemWarehouseInfo that corresonds to the warehouse in Item Master Data.
That means the LineNum value match warehouse list number minus 1.
In your case it seems you just used 0,1,2,3,4 but it does not necessarily match the order of the warehouses.
So for example if you have 4 warehouses in the database
1 Test
2 Ware
3 House
4 DTW
then when you update properties of the warehouse the LineNum is 0 for warehouse Test, 1 for warehouse Ware and so on (please refer to note 1328706).
Should you have any further questions related to this issue please do not hesitate to contact us.
Kindly confirm the message at your earliest convenience after successfully testing it.

I am trying to organize thousands of images in aperture. The dates on the old scanned images is all 2008, when I started importing them. When I change the date in aperture some of them hold the modified date and some revert to 2008. Any ideas?

I am trying to organize thousands of old images in aperture. Aperture dates them all in 2008, when I started this project. When I change the date in aperture some of them hold the modified date and some revert to 2008. Any ideas?

I just tried a test library, re-imported fresh images from a hard drive, and the date changes still revert.
So neither your external drive nor your Aperture library are to blame.
What do you mean test in a different user acct? Would it be a good idea to uninstall and re-download aperture 3?
Appreciate all your help.
I meant the trouble shooting procedure described here: Isolating an issue by using another user account
To test, if some settings in your user account are faulty or preferences files corrupted, it helps to create a new user account from the "Users&Groups" System preferences. With a brand new user account you can see, if something in your current account is causing this.
Should you see, that Aperture is not even working from a new and clean account, I'd reinstall Aperture, and if need be the Operating system. Are you using any plug-ins?

Standalone GWCheck purges by Modified date -- leaves mail

Hello all.
System in question is still GW 8.0.2/3.
I have a problem where running the standalone GWCheck Expire/Reduce job leaves mail older than the specified date in mailboxes, particularly in the Sent Items. After a call with Novell support, they say that it's working as designed, according to TID:
http://www.novell.com/support/kb/doc.php?id=7000929
The TID says the standalone GWCheck purges via the modified date, and if someone moves an item into a folder or any number of operations against the item, it sets the modified date to that moment. We're wanting to do a 365-day purge date, so that'd keep the mail around for another year. Not what we want.
Does anyone know a switch to change this behavior, to go off Created Date?
Does the scheduled tasks in the POA itself operate differently? That'd work against the entire PO (minus exclusions) but is it an option?
After years in Groupwise, I was astonished to learn the standalone tool goes by modified date, and that many common operations change the modified date on an item.
Thanks in Advance,
~Howard H.
Austin TX

Hi!
You can do a test by scheduling a task of clearing and deleting emails from a certain date, in the post office.
In the post office:
GroupWise Utilities -> Client Options -> Enviroment -> Cleanup
Mail and Phone: Auto-Delete After: (n) days that you want
Appointment, Task and Note: (n) days that you want
Empty Trash: (n) days that you want
In the next maintenance task, all the emails and tasks on the post office should be removed from the date that you want.
I hope this can help to solve you problem.

Automatically (programming) Extracting last modified date

Hi
I have the url addresses of sesveral documents stored in SharePoint. Those addresses are stored in a column within Excel. There is one address per line (row).
I would like to extract for each file its last modified date. Ideally in an automatiic mode.
All files are not in the same "folder".
How could I achieve that?
Many thanks in advance

Hi,
you can write a query to get all the files from the doc library and use SPFile.Properties to get the last modified date
http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.spfile.properties.aspx
your code will be like the below (Taken from above link)
SPSite oSiteCollection = SPContext.Current.Site;
using(SPWeb oWebsite = oSiteCollection.AllWebs["Site_Name"])
SPFolder oFolder = oWebsite.Folders["Shared Documents"];
SPFileCollection collFiles = folder.Files;
foreach (SPFile oFile in collFiles)
System.Collections.Hashtable collHashes = file.Properties;
System.Collections.ICollection collKeys = hash.Keys;
foreach (object oKey in collKeys)
Response.Write(SPEncode.HtmlEncode(oKey.ToString())
+ " :: " +
SPEncode.HtmlEncode(hash[oKey.ToString()].ToString())
+ "<BR>");
another option would be to use SPFile.TimeLastModified
http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.spfile.timelastmodified.aspx
http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.spfile_properties.aspx
Hope this helps!
Ram - SharePoint Architect
Blog - SharePointDeveloper.in
Please vote or mark your question answered, if my reply helps you

Unable to extract data from an AS/400 system.

Hello experts.
We are trying to extract data from an AS/400 system but not having any success until now.
I´ll write down you the stepts that we have followed until now:
1.- Create a DB Connect between both systems
2.- Create a Source System from AS400 in the workbench under DB Connect Directory
3.- Generate datasources from tebles specified in the schema of the connection
break point -
At this point, we had a problem with some tables with at least one fieldname containing character "Ñ".
After asking some possible solutions to SAP, the told us this is not supported, as the system can´t have any object with character "Ñ", so the transfer structure was unable to activate with this fields in the datasource.
--- end of brek point --
4.- After those issues, we´ve decided to implement, in another schema, views from those tables which had the fieldnames with that character "Ñ", changing them to an "N".
5.- We´ve created another source system with that schema, and user than can see that schema.
6.- To be able to see those views, in transaction RSDBC, we had to deactivate the two checkboxes in the first window ( Choose tables and Choose views) .
7.- Right afeter, we could generate correctly the datasources from this logical tables.
8.- We have designed the hole dataflow for this datasources and everithing went rigth.
9.- But wen we tried to execute the infopackage to extract data from those logic tables, we cannot get any registers. Acctualy the charge remains yellow after the job have finished.
Please, I would appreciate any help you could give us on this problem.
Thank you very much
Regards
Joaquin

I´d like ti add something to this thread, and maybe clarify a littel bit the question.
The only way that the BW system recognizes those logical tables, through transaction RSDBC is checking out the two boxes on this transaction, "Select Tables" and "Select Views".
I don´t know haw these logical tables have been created, bus does this mean that the are not neither tables or views as BW understand them.
Please, if someone knows anythin about this, answer to this thread.
Thank you very much.
Joaquin Sobrido

How can I modify data from a Transparent Table without ABAP code.

Hi,All
How can I modify data from a Transparent Table (like TCURR), and important thing is I want do all that with no ABAP code here. It is like that we always do that in a Oracle database use TOAD or PLSQL third party tools, with no script code here.
I had fond that there is a way can do that:
1, type 'se11',and Display Database table 'TCURR', click Contents, then click Execute to display all data
2, type '/h' and let debugging on
3, select one of this data then click 'Display',enter in debugging system.
4, then make a breakpoint in the code. But... display a dialog let I type a 'ABAP Cmnds', I want to know what can be type in for that?
and, My system is ECC6.
thank you all
Edited by: xuehui li on Aug 20, 2008 6:30 PM

Hello,
Your approach (with Vijay's suggestion) MAY work. However, depending on how tight security is at the company that you are working at you may or may not be able to acutaly change the value of the SHOW field to EDIT. This will be especially true if you are working in a Production environment. Vijay's other comment is true as well. This is not a recommended approach to change data (especially data with a financial impact like TCURR) in a production environment. The auditors will not be impressed.
Explore the option of a maintenace view or look at tcode TBDM to upload a file which includes daily rates from providers like Reuters or try tcode s_bce_68000174 which is a maintenance view on TCURR.
Regards
Greg Kern

Is it possible to migrate data from a 4.6C system to an ECC 6.0 system?

Hello all,
We have an ECC6.0/Oracle 11g system which runs Finance, Purchasing and Payroll/HR for our own organisation.
We also have another 4.6C/Oracle9 system where we run only Payroll for another organisation.
This is a separate landscape (Dev / Test / Prod / DR) which runs on its own hardware.
Clearly, this 4.6C system has to be upgraded in the next 12 months or so before it is out of maintenance.
However, we are exploring whether it would be possible to migrate the data from the 4.6C system to our existing ECC6.0 system instead of upgrading the 4.6C system.
In this way, we can decommission the 4.6C hardware and simplify our landscape.
Has anyone undertaken a similar exercise who would be willing to share their experiences?
Or does anyone have any opinions as to whether this would even be possible?
Our initial thinking is that we would probably have to write our own conversion programs and/or possibly use LSMW but it's early days so any feedback is welcome.
Regards...John

Hi,
However, we are exploring whether it would be possible to migrate the data from the 4.6C system to our existing ECC6.0 system instead of upgrading the 4.6C system.
You can make of ALE/IDOCs technology to transfer the required data from 4.6C system to ECC 6.0 system. Here you will need to perform necessary mapping of the fields and perform required technical configuration. Later write ABAP codes to fetch and transfer data .
Hope this answers your query.
Regards,
Deepak Kori

OIM 11g - How to get modified data on a reconciliation event

Hi,
We're running OIM 11.1.1.5.2 with Ad (9.1.1) , exchange ( 9.1.1.7), dbum (9.1.0.4) and dbat (9.1.0.5) connectors.
When we run reconciliation we can get the recon data on the event management tab of the advanced administration console, but, update succeded events show all fields mapped on the reconciliation with the new values only. For example, for AD, if an account on the target resource has its "TelephoneNumber" field updated, we can see the event, but, we cannot identify what was changed on that event was the telephone number, as the event shows all fields on the Ad account...
Our requirement is to inform th customer as soon as the reconciliation has ocurred for each particular updated account, in a manner that is fast and easy to understand.
We have the audit on OIM on Resource Form (XL.UserProfileAuditDataCollection) and we can see the upa tables being populated.
Now, the question is, what is the recommended or most used way to process the information on upa tables? Is there any ootb report that maybe we're missing that shows this info? Are there api's documented to work with audit data (i just couldn't find them)?
Having in consideration our requirement, I'm thinking on creating a new task for each process form to be triggered by "Reconciliation Update Succeeded" that executes a pl/sql to find events on upa tables related to the user and resource, then parse the generated xml and send an email with old and new values, but I want to be sure there's no ootb or simpler way to do it.
Thanks.

Thanks Kevin,
I think that we found an easier way though. By setting the system property XL.EnableExceptionReports to TRUE, the tables UPA_FORMS y UPA_FORMFIELDS get populated automatically.
This tables contain information of the fields that were modified an the reason (i.e. 'Reconciliation', 'API').
I have created a database job that executes a stored procedure that searches for new records on upa_ud_formfields and gets the resource name, resource key, field name, old and new values and then sends an email with all modified data to the corresponding administrators for each resource. I use an auxiliary table on a different schema to keep track of records already read on previous runnings of the job.
It takes sometime to get the info because we depend first on the running of the recon scheduled job, then the "issue audit message task" job, and finally our own job, but it works.

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

Unable to open the physical file "D:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\abc.mdf". Operating system error 2: "2(The system cannot find the file specified.)".

hi,
am running the below command for moving sql serevr mdf and ldf files from one drive to another : c drive to d drive:
but am getting the below error
SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\abc.mdf". Operating system error 2: "2(The system cannot find the file specified.)".
use master
DECLARE @DBName nvarchar(50)
SET @DBName = 'CMP_143'
DECLARE @RC int
EXEC @RC = sp_detach_db @DBName
DECLARE @NewPath nvarchar(1000)
--SET @NewPath = 'E:\Data\Microsoft SQL Server\Data\';
SET @NewPath = 'D:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\';
DECLARE @OldPath nvarchar(1000)
SET @OldPath = 'C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\';
DECLARE @DBFileName nvarchar(100)
SET @DBFileName = @DBName + '.mdf';
DECLARE @LogFileName nvarchar(100)
SET @LogFileName = @DBName + '_log.ldf';
DECLARE @SRCData nvarchar(1000)
SET @SRCData = @OldPath + @DBFileName;
DECLARE @SRCLog nvarchar(1000)
SET @SRCLog = @OldPath + @LogFileName;
DECLARE @DESTData nvarchar(1000)
SET @DESTData = @NewPath + @DBFileName;
DECLARE @DESTLog nvarchar(1000)
SET @DESTLog = @NewPath + @LogFileName;
DECLARE @FILEPATH nvarchar(1000);
DECLARE @LOGPATH nvarchar(1000);
SET @FILEPATH = N'xcopy /Y "' + @SRCData + N'" "' + @NewPath + '"';
SET @LOGPATH = N'xcopy /Y "' + @SRCLog + N'" "' + @NewPath + '"';
exec xp_cmdshell @FILEPATH;
exec xp_cmdshell @LOGPATH;
EXEC @RC = sp_attach_db @DBName, @DESTData, @DESTLog
go
can anyone pls help how to set the db offline. currently i stopped the sql server services from services.msc and started the sql server agent.
should i stop both services for moving from one drive to another?
note: I tried teh below solution but this didint work:
ALTER DATABASE <DBName> SET OFFLINE WITH ROLLBACK IMMEDIATE
Update:
now am getting the message :
Msg 15010, Level 16, State 1, Procedure sp_detach_db, Line 40
The database 'CMP_143' does not exist. Supply a valid database name. To see available databases, use sys.databases.
(3 row(s) affected)
(3 row(s) affected)
Msg 5120, Level 16, State 101, Line 1
Unable to open the physical file "D:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\CMP_143.mdf". Operating system error 2: "2(The system cannot find the file specified.)".

First you should have checked the database mdf/ldf name and location by using the command
Use CMP_143
Go
Sp_helpfile
Looks like your database CMP_143 was successfully detached but mdf/ldf location or name was different that is why it did not get copied to target location.
Database is already detached that’s why db offline failed
Msg 15010, Level 16, State 1, Procedure sp_detach_db, Line 40
The database 'CMP_143' does not exist. Supply a valid database name. To see available databases, use sys.databases.
EXEC @RC = sp_attach_db @DBName, @DESTData, @DESTLog
Attached step is failing as there is no mdf file
Msg 5120, Level 16, State 101, Line 1
Unable to open the physical file "D:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\CMP_143.mdf". Operating system error 2: "2(The system cannot find the file specified.)"
Solution:
Search for the physical files(mdf/ldf) in the OS and copy to target location and the re-run sp_attach_db with right location and name of mdf/ldf.

Modify data in another R/3 system ?

Similar Messages

Maybe you are looking for