Refresh data in a system form

Hi all,
i have the following scenario:
i developed an addon to enable the user to modify the invoice billing address after the invoice has been created.
to achieve it i used a UDF with a text edit field.
everythings seems to works fine but i'd like to refresh the system invoice form (form 133 - item 6) with the new value submited in the UDF when i go back to the main form.
i already tried to use refresh and update form method without success.
can someone help me?
thanks in advance.
best regards
Andrea

something like
Dim oform As SAPbouiCOM.Form
            Dim docnum As String
            Dim edit As SAPbouiCOM.EditText
            oform = SBO_Application.Forms.ActiveForm
            edit = oform.Items.Item("8")
            docnum = edit.Value
            SBO_Application.Menus.Item("1281").Activate()
            edit.Value = docnum
            oform.Items.Item("1").Click(SAPbouiCOM.BoCellClickType.ct_Regular)

Similar Messages

Copy Data from a System Form to another (GetByKey)

Hi All,
I 'll try the following: "After the succesful add of a specific Credit Note I want to copy the Cardcode and the Cardname (of this Credit Note) to cardcode and cardname of a Delivery Note".
I tried the following code without success:
            If (pval.FormType = 179) And (pval.ItemUID = "1") And (pval.EventType = SAPbouiCOM.BoEventTypes.et_ITEM_PRESSED) And (pval.Before_Action = False) And (pval.ActionSuccess = True) Then
                Dim DocEntry As Integer
                Try
                    Dim oCredit As SAPbobsCOM.Documents
                    oCredit = oCompany.GetBusinessObject(SAPbobsCOM.BoObjectTypes.oDeliveryNotes)
                    Dim oDeliv As SAPbobsCOM.Documents
                    'Creation of Business Objects
                    oDeliv = oCompany.GetBusinessObject(SAPbobsCOM.BoObjectTypes.oDeliveryNotes)
                    oCredit.GetByKey(DocEntry)
                    oDeliv.CardCode = oCredit.CardCode
                    oDeliv.CardName = oCredit.CardName
                Catch ex As Exception
                    MessageBox.Show(ex.Message)
                End Try
Thanks in advance,
Vangelis

Hello,
There are a few errors in the code you've pasted:
oCredit = oCompany.GetBusinessObject(SAPbobsCOM.BoObjectTypes.oDeliveryNotes)
oDeliv = oCompany.GetBusinessObject(SAPbobsCOM.BoObjectTypes.oDeliveryNotes)
a) both the above lines are creating delivery notes.
b) where are you getting the docentry value from, get it from the form using UI-API
c) you can also get the cardcode / cardname value using UI-API, by referring to the fields on the form, rather than using oCredit object.
c) you are not calling add/update after writing delivery note
d) lets be clear that you cannot change cardcode / cardname in already created delivery note, and if you are adding a new delivery note you can not do it by just specifying cardcode / cardname
Rahul

How to Refresh System Form in Run Time

Dear All,
Please give me idea for Refresh System Document in Run Time using DI,basically I am using system columns for update for some scenarios.
So please give solution that how should refresh system form.
Thanks a lot.
Ashish Singh.

Hi,
Please post above discussion in SDK forum.
Thanks & Regards,
Nagarajan

Auto populate system Current date in Info path form textbox

Hi,
I want to display system current date in info path when user opens new form.I have placed a text box and added now function and in format selected do not display time option.
When i preview the form everything works as expected.the date is displaying like mm/dd/yyyy format without time :)
But after publishing the same form to share point list when i open the form from browser the text box is not showing current date
Instead it is showing yesterday's date :(
Can anyone help me to resolve the issue.
Regards,
Poovi

Hi Poovi,
According to your description, you want to enable the text box to show the current date when opening the form from browser. However, the date that your text box displayed
in the SharePoint site page is different from the
one in the InfoPath Designer.
In InfoPath, the date displayed is the same as the system date. However, the date displayed in the SharePoint site
page depends on the Regional
settings of a site other
than system date.
As a solution, you could set the time zone in Regional settings of a site if needed.
Here is a link about how to change the Regional settings of a site, you could use as a reference:
http://office.microsoft.com/en-sg/sharepoint-foundation-help/change-regional-settings-for-a-site-HA102894666.aspx
Best regards,
Patrick
Patrick Liang
TechNet Community Support

Is it possible to get System form Matrix Data in DI API?

HI,
   i would like to use DI API to get the System Form Matrix ( like Sale Order ) . Is it possible?
   i know that using UI API is most easier way. However, UI API cause extermemly slow perfomance.
   no matter i use Form.Freeze or not. Please Advise
Thanks
Gordon
Edited by: Gordon Ho on May 7, 2009 7:03 AM

Hi,
U can access the Sales Order rows using the DI only if its added to the system. U can use the DOCUMENT object and Document.Lines and access the row data. Please check the SDK help file for more information.
From SDK Help
Document_Lines is a child object of Documents object and represents the line entries of a document in the Marketing Documents and Receipts module and the Inventory and Production module.
Vasu Natari.

Opening a System-Form with selected Data

Hi,
i´m looking for a way to open a System-Form, e.g. Orders with
selected Data.
In the moment i do the following:
     application.ActivateMenuItem("2050"); // orders
     SAPbouiCOM.Form belegForm = application.Forms.ActiveForm;
     belegForm.Mode = SAPbouiCOM.BoFormMode.fm_FIND_MODE;
     SAPbouiCOM.EditText edDocNum = (SAPbouiCOM.EditText)belegForm.Items.Item("8").Specific;
     edDocNum.Value = "4711";
     belegForm.Items.Item("1").Click(SAPbouiCOM.BoCellClickType.ct_Regular);
This works, but the screen is blinking, because first the form ist opened and shown with
empty values and then filled.
Is there a way to activate the form and do the search-Operation and afterwards show it ?
I think ist must be possible, because when clicking on the link-Button near CardCode, the Contacts-Form
is opened in this way.
regards Matthias

Hi Ibai,
i have tested both: freeze and form.visible = false in
the form_load-Event. It doesn´t work here.
Also neither the call
   application.ActivateMenuItem("1281"); // find
nor the call
   oForm.Mode = SAPbouiCOM.BoFormMode.fm_FIND_MODE;
work in the form_load-Event.
After the form-Load-Event the et_FORM_ACTIVATE-Event is called.
Here the functions work, but here the screen is already visible.
regards Matthias

How to Refresh System Form on Before Action using DI

Dear All,
Please give me idea for Refresh System Document in Run Time on Before Action using DI,basically I am using system columns for update for some scenarios.
So please give solution that how should refresh system form.
Thanks a lot.
Ashish Singh.

Hi,
See i already descrived you my case what i am exactly doing.
Now,
Document Name -Purchase Order
All The item is non excisable and i want to put value in Assable Column for calculation Tax but when i non excisable then you can not put value in Assable column.so when user will add purchase order then i updating Excisable columns with value of 'Y' for Assable value.now this case is running correctly.
But if any change will come of particular purchase order then user need to put value in any field and now i am supposing change field is remarks.
And Then user click on update filed button then system giving error that "there is excisable item with non-excisable tax code" and after this not allow to update.but i wrote code in item press before action for update excisable filed with value of 'N' for time being. but the case is sap not refresh doc when i changed any any value ,
so main concern is i want to reflect value with front end immediate.
Thanks
Ashish

UIX form will not refresh data within session

I have some UIX forms to view a table, they displays data fine but when the underling table data changes (from another user session or an update trigger from different table) the forms will not show refreshed data, unless I delete my browser session cookie. Is there a simple way to fix this, and cause data to be reloaded each time its displayed? I'm using JDeveloper 10.1.2
Thanks, Craig Smith
Message was edited by:
user503876
Message was edited by:
user503876

Dear Sir...
in the struts page flow diagram
1- create a data action
2- drag the execute method from the viewobject methods and drop it on the data action
3- draw a page forward from the data action to your data page
4- finally ad a refresh link in your page which links to your data action
now each time you click the refresh button on your page, the execution will go to the data action, where the execute method is executed (the data is refreshed) and then the control goes back to your page.
best regards

DBDataSources not up to date in system form

Hi guys,
I really need you help on a issue.
I'm trying to read all records in the matrix of the Sales Order (System Form)
Now i'm using the datasource (DBDataSource) of this form to get the values, because this is faster then getting the values from the matrix.
I run the following code on the before et_CLICK event on the Update Button. And i get this message:
Data Source - Bad Data Source Offset at SAPbouiCOM.DBDataSourceClass.GetValue(Objext Index, Int32 RecorNumber)
This issue seems to occure when i duplicate or add some lines and hit the Update Button. The amount of lines in the datasource is still the same as when i opened the Sales Order. But the number of records in the matrix is larger. So it seems that the datasource has not been updated when i added the lines.
Does anyone has a solution for this?
//Cache the document matrix
      SalesOrderCached salesOrderCached = new SalesOrderCached();
      ui.Matrix mtx = (ui.Matrix)form.Items.Item(SBO_FormTypes.Document.ItemMatrix.VALUE).Specific;
      ui.DBDataSource dataSource = form.DataSources.DBDataSources.Item("ORDR");
      ui.DBDataSource dataSourceLines = form.DataSources.DBDataSources.Item("RDR1");
      salesOrderCached.DocNum = dataSource.GetValue("DocNum", 0);
      salesOrderCached.CardCode = dataSource.GetValue("CardCode", 0);
      for (int i = 1; i < mtx.RowCount; i++)
        mtx.GetLineData(i);
        SalesOrderLineCached salesOrderLine = new SalesOrderLineCached();
        salesOrderLine.LineNum = i;
        salesOrderLine.ItemCode = dataSourceLines.GetValue("ItemCode", i -1).Trim();
        salesOrderLine.WarehouseCode = dataSourceLines.GetValue("WhsCode", i -1).Trim();
        salesOrderLine.LineTotal = Convert.ToDouble(dataSourceLines.GetValue("LineTotal", i -1).Trim(), NumberFormatInfo.InvariantInfo);
        salesOrderCached.SalesOrderLinesCached.Add(salesOrderLine);
      return salesOrderCached;

Unfortunately not.
the only thing I can think of trying is using the GetCellSpecific method of the matrix object. I have never used it but I see in the helpfile SAP say "This is the recommended way to get the contents of a cell."
Worth a try but highly unlikely to work would be to use matrix.FlushToDataSouce().... but I would bet it won't work unless it's a user defined item. A similar method would be "GetLineData()"
So I think it will be either GetCellSpecific to see if it improves performance or some sort of workaround
EDIT: Actually, maybe try SerializeAsXML. It will be extra development time but bound to be faster.

Taking the data from interactive forms and load the data into SAP system?

hi all,
I want to know how to take the data from interactive forms and load the data into sap system?
if u have any sample scenario, explain with that.
thanks in advance
Raja

Hello,
Check the program...
SAPBC480_DEMO.
Check the below threads
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/88e7ea34-0501-0010-95b0-ed14cfbeb85a
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/bfbcd790-0201-0010-679d-e36a3c6b89fa
Thanks
Seshu

Access Data for System Form in SAP B1

Hi,
I want to access Text data and Matrix data for Purchase order Form. Can u Plz provide solution / Code for this problem.
Thanks

Hi Makarand,
write these code inside ItemEvent,
oForm = SBO_Application.Forms.Item(FormUID)
oEditText = oForm.Items.Item("4").Specific 'Unique ID of Vendor Code
VendorCode = oEditText.Value
oMatrix = oForm.Items.Item("38").Specific 'Unique ID of Matrix
For i=1 To oMatrix.RowCount
oColumn = oMatrix.Columns.Item("1") 'Unique ID of ItemCode in matrix
oEditText = oColumn.Cells.Item(i).Specific
ItemCode = oEditText.String
Next
You will get item Unique ID from Debug information.
Hope this will help you
regards,
BBN

Can not refresh data int the report...

Application on C#.
Steps:
1. Get Report without data from the database
2. Change the dataconnections in report to the current user
3. refresh data on the report (FilePath = TempFilePath)
4. Resave report file with data
5. Automatically open CrystalReportsViewer2008 and load the report
Result
On developer machine is allright, but on the user machine data isn't refreshed. Therefore CrysrtalReportsViewer2008 can't open report. It say that check the SaveDatawithReport parameter.
In process I found that in temp directory on user pc, didn't creates some temprorary files which creates on developer PC. Why? Help me please.
Sorry for my English.

There is the code of my programm
function ParseReport is refreshed the data and change dataconnections for current user
using System;
using System.Collections.Generic;
using System.ComponentModel;
using System.Data;
using System.Data.SqlClient;
using System.Drawing;
using System.Text;
using System.Windows.Forms;
using System.IO;
using System.Diagnostics;
using CRApp;
using Microsoft.Win32;
namespace CRApp
     * u041Au043Bu0430u0441u0441 u0434u043Bu044F u0430u0432u0442u043Eu043Cu0430u0442u0438u0437u0438u0440u043Eu0432u0430u043Du043Du043Eu0433u043E u0432u0438u0437u0443u0430u043Bu044Cu043Du043Eu0433u043E u0434u043Eu0441u0442u0443u043Fu0430
     * u043A u0444u0430u0439u043Bu0430u043C u0448u0430u0431u043Bu043Eu043Du043Eu0432, u0441u0433u0435u043Du0435u0440u0438u0440u043Eu0432u0430u043Du043Du044Bu0445 u0432
     * u043Fu0440u043Eu0433u0440u0430u043Cu043Cu0435 Crystal Reports
    public partial class Export2CR_MForm : Form
        public Export2CR_MForm()
            InitializeComponent();
            Start();
        public void Start()
            LoginForm Login = new LoginForm();
            DialogResult Dres = Login.ShowDialog();
            if (Dres == DialogResult.OK)
                if (Login.GetConStr().ToString() != "")
                    GetReportNamesFromDataBase(Login.GetConStr());
                    SetConnectionString(Login.GetConStr());
                    this.CenterToScreen();
                    Visible = true;
                    Login.Close();
            else
                Login.Close();
                this.CenterToScreen();
                this.OnClosed(null);
             * u041Fu043Eu043Bu0443u0447u0430u0435u043C u043Fu0443u0442u044C u043A u0432u0440u0435u043Cu0435u043Du043Du044Bu043C u0444u0430u0439u043Bu0430u043C
            TempFilePath = Path.GetTempPath();
         * u041Au0440u0438u0441u0442u0430u043Bu043Eu0432u0441u043Au0438u0439 u0432u044Cu044Eu0432u0435u0440u043Eu043A
        CrystalDecisions.Windows.Forms.CrystalReportViewer viewer;
         * u041Fu0443u0442u044C u043A u0432u0440u0435u043Cu0435u043Du043Du043Eu0439 u043Fu0430u043Fu043Au0435
        private string TempFilePath;
         * u041Fu0430u0440u0430u043Cu0435u0442u0440 u0437u0430u043Fu0438u0441u0438 u0432 u0440u0435u0436u0438u043Cu0435, u0442u0430u0431u043Bu0438u0446u0435 (u0438u0442u0434...)
         * u041Du0443u0436u0435u043D u0434u043Bu044F u0442u043Eu0433u043E u0447u0442u043Eu0431u044B u0432u044Bu0431u0438u0440u0430u0442u044C
         * u043Eu043Fu0435u0440u0435u0434u043Bu0451u043Du043Du044Bu0439 u0434u0430u0442u0430u0441u0435u0442, u0441u043Eu043Eu0442u0432u0435u0442u0441u0442u0432u0443u044Eu0449u0438u0439 u0432u044Bu0431u0440u0430u043Du043Du043Eu0439 u0437u0430u043Fu0438u0441u0438
        private int ObjectIDOfTemplate;
         * u0423u0441u0442u0430u043Du043Eu0432u043Au0430 u0437u043Du0430u0447u0435u043Du0438u044F ObjectIDOfTemplate
        public void SetObjectIDOfTemplate(int /*
                                               * ObjectID u0442u043Eu0433u043E u0448u0430u0431u043Bu043Eu043Du0430,
                                               * u043Au043Eu0442u043Eu0440u044Bu0439 u043Du0430u0434u043E u043Fu043Eu043Bu0443u0447u0438u0442u044C
                                                  EnternalObjectID)
            ObjectIDOfTemplate = EnternalObjectID;
         * u041Fu043Eu043Bu0443u0447u0438u0442u044C ObjectID u0448u0430u0431u043Bu043Eu043Du0430
         * u0441 u043Au043Eu0442u043Eu0440u044Bu043C u0440u0430u0431u043Eu0442u0430u043Bu0438 u0434u043Bu044F
         * u0438u0441u043Fu043Eu043Bu044Cu0437u043Eu0432u0430u043Du0438u044F u0435u0433u043E u0432u043Du0435 u0431u0438u0431u043Bu0438u043Eu0442u0435u043Au0438
        public int GetObjectIDOfTemplate()
            return ObjectIDOfTemplate;
         * u041Fu0443u0442u044C u043A u0432u044Bu043Fu043Bu044Eu043Du0443u0442u043Eu043Cu0443 u0444u0430u0439u043Bu0443
        private string TemplateFilePath;
         * u0423u0441u0442u0430u043Du043Eu0432u0438u0442u044C u043Fu0443u0442u044C u043A
         * u0432u044Bu043Fu043Bu044Eu043Du0443u0442u043Eu043Cu0443 u0444u0430u0439u043Bu0443
        public void SetTemplateFilePath(string In)
            TemplateFilePath = In;
         * u041Fu043Eu043Bu0443u0447u0438u0442u044C u043Fu0443u0442u044C u043A
         * u0432u044Bu043Fu043Bu044Eu043Du0443u0442u043Eu043Cu0443 u0444u0430u0439u043Bu0443
        public string GetTemplateFilePath()
            return TemplateFilePath;
         * u0424u0443u043Du043Au0446u0438u044F u043Eu0442u043Au0440u044Bu0442u0438u044F u0444u0430u0439u043Bu0430,
         * u043Fu043Eu043Bu0443u0447u0435u043Du043Du043Eu0433u043E u0438u0437 u0431u0430u0437u044B u0438
         * u043Fu043Eu043Bu043Eu0436u0435u043Du043Du043Eu0433u043E u0432u043E u0432u0440u0435u043Cu0435u043Du043Du0443u044E u043Fu0430u043Fu043Au0443
        public int ParseReport(string FilePath)
            viewer = new CrystalDecisions.Windows.Forms.CrystalReportViewer();
            CrystalDecisions.CrystalReports.Engine.ReportDocument rd =
                new CrystalDecisions.CrystalReports.Engine.ReportDocument();
            try
                rd.Load(FilePath);
                try
                    for (int i = 0; i < rd.DataSourceConnections.Count; i++)
                        rd.DataSourceConnections<i>.SetConnection(
                            GetConnectionString().GetServerName(),
                            GetConnectionString().GetDatabaseName(),
                            GetConnectionString().GetUserName(),
                            GetConnectionString().GetPassword()
                        for (int j = 0; j < rd.Database.Tables.Count; j++)
                            DataTable dataSet = new DataTable();
                            SqlConnection C = new SqlConnection(GetConnectionString().ToString());
                            string ViewName = GetDataViewName(GetConnectionString(), ParseTableName(
                                            rd.Database.Tables[j].Name));
                            SqlCommand Q = new SqlCommand("select * from " + ViewName
                                , C);
                            Q.CommandType = CommandType.Text;
                            SqlDataAdapter adapter = new SqlDataAdapter();
                            adapter.SelectCommand = Q;
                            adapter.Fill(dataSet);
                            rd.Database.Tables[j].SetDataSource(dataSet);
                catch (Exception e)
                    MessageBox.Show(e.Message);
                try
                    SetTemplateFilePath(TempFilePath + "\\" + FileTreeView.SelectedNode.Text.ToString() + ".rpt");
                    rd.ReportOptions.EnableSaveDataWithReport = true;
                    viewer.ReportSource = rd;
                    viewer.RefreshReport();
                    rd.SaveAs(TemplateFilePath);
                    rd.Close();
                    return 0;
                catch (Exception e)
                    MessageBox.Show(e.Message);
                    return -1;
            catch (Exception ex)
                rd.ReportOptions.EnableUseDummyData = true;
                rd.ReportOptions.EnableSaveDataWithReport = true;
                viewer.RefreshReport();
                rd.SaveAs(TemplateFilePath);
                MessageBox.Show("Error: Could not read file from disk. Original error: " + ex.Message);
                return -1;
         * u0420u0430u0437u0431u0438u0435u043Du0438u0435 u0438u043Cu0435u043Du0438 u0442u0430u0431u043Bu0438u0446u044B
         * u0434u043Bu044F u043Fu043Eu043Bu0443u0447u0435u043Du0438u044F u043Du043Eu043Cu0435u0440u0430 u043Au043Bu0430u0441u0441u0430
        public string ParseTableName(string TableName)
//            MessageBox.Show(TableName);
            int x = 0;
            if (TableName.Contains("Class"))
                x = TableName.LastIndexOf("s");
                return TableName.Remove(0,x+1);
            if(TableName.Contains("Attr"))
                x = TableName.IndexOf("r");
//           MessageBox.Show(x.ToString());
//           MessageBox.Show(TableName.Remove(0, x+1));
            return TableName.Remove(0, x+1);
         * u0424u0443u043Du043Au0446u0438u044F u043Fu043Eu043Bu0443u0447u0435u043Du0438u044F u0444u0430u0439u043Bu0430 u0438u0437 u0431u0430u0437u044B
        public int ParseReportWithDataBase()
            try
                string ConnectionString = GetConnectionString().ToString();
                SqlConnection C = new SqlConnection(ConnectionString);
                C.Open();
                string SelectString = "select P119 from "+ GetDataViewName(GetConnectionString(),"24") +" where P115='";
                SelectString = SelectString+FileTreeView.SelectedNode.Text.ToString()+"'";
                SqlCommand Q = new SqlCommand(SelectString, C);
                Q.CommandType = CommandType.Text;
                SqlDataAdapter adapter = new SqlDataAdapter();
                adapter.SelectCommand = Q;
                DataTable table = new DataTable();
                adapter.Fill(table);
                byte[] b = (byte[])table.Rows[0].ItemArray.GetValue(0);
                FileStream fs = File.Create(TempFilePath+"\\"+FileTreeView.SelectedNode.Text.ToString()+".rpt");
                fs.Write(b, 0, b.Length);
                fs.Close();
                C.Close();
                return 0;
            catch (Exception ex)
                MessageBox.Show(ex.Message);
                return -1;
         * u0421u0442u0440u0443u043Au0442u0443u0440u0430, u043Eu043Fu0438u0441u044Bu0432u0430u044Eu0449u0430u044F u043Fu0430u0440u0430u043Cu0435u0442u0440u044B
         * u043Fu043Eu0434u043Au043Bu044Eu0447u0435u043Du0438u044F u043A u0431u0430u0437u0435 u0434u0430u043Du043Du044Bu0445,
         * u043Au0430u043A u0434u043Bu044F u0432u043Du0435u0448u043Du0435u0433u043E u0438u0441u043Fu043Eu043Bu044Cu0437u043Eu0432u0430u043Du0438u044F
         * u0442u0430u043A u0438 u0434u043Bu044F u0432u043Du0443u0442u0440u0435u043Du043Du0435u0433u043E
        public struct ConnectionString
             * u0418u043Cu044F u0441u0435u0440u0432u0435u0440u0430 u0431u0430u0437u044B u0434u0430u043Du043Du044Bu0445
            private string DataSource_Value;
             * u041Du0430u0437u0432u0430u043Du0438u0435 u0431u0430u0437u044B u0434u0430u043Du043Du044Bu0445
            private string InitialCatalog_Value;
             * u0418u043Cu044F u043Fu043Eu043Bu044Cu0437u043Eu0432u0430u0442u0435u043Bu044F
            private string UserID_Value;
             * u041Fu0430u0440u043Eu043Bu044C
            private string Password_Value;
             * u041Fu0435u0440u0435u0433u0440u0443u0436u0435u043Du043Du044Bu0439 u043Au043Eu043Du0441u0442u0440u0443u043Au0442u043Eu0440
             * u0434u043Bu044F u0440u0443u0447u043Du043Eu0439 u0438u043Du0438u0446u0438u0430u043Bu0438u0437u0430u0446u0438u0438
             * u0441u0442u0440u043Eu043Au0438 u043Fu043Eu0434u043Au043Bu044Eu0447u0435u043Du0438u044F,
             * u043Du0443u0436u0435u043D u0434u043Bu044F u0438u0441u043Fu043Eu043Bu044Cu0437u043Eu0432u0430u043Du0438u044F u0435u0433u043E
             * u0432 u043Eu0434u0440u0443u0433u0438u0445 u0444u043Eu0440u043Cu0430u0445
            public ConnectionString(string /*
                                            * u0418u043Cu044F u0441u0435u0440u0432u0435u0440u0430 u0431u0430u0437u044B u0434u0430u043Du043Du044Bu0445
                                              InDataSource_Value,
                                    string /*
                                            * u041Du0430u0437u0432u0430u043Du0438u0435 u0431u0430u0437u044B u0434u0430u043Du043Du044Bu0445
                                              InInitialCatalog_Value,
                                    string /*
                                            * u0418u043Cu044F u043Fu043Eu043Bu044Cu0437u043Eu0432u0430u0442u0435u043Bu044F
                                            */ InUserID_Value,
                                    string /*
                                            * u041Fu0430u0440u043Eu043Bu044C
                                            */ InPassword_Value)
                DataSource_Value = InDataSource_Value;
                InitialCatalog_Value = InInitialCatalog_Value;
                UserID_Value = InUserID_Value;
                Password_Value = InPassword_Value;
             * u041Fu043Eu043Bu0443u0447u0438u0442u044C u0438u043Cu044F u0441u0435u0440u0432u0435u0440u0430
             * u0431u0430u0437u044B u0434u0430u043Du043Du044Bu0445
            public string GetServerName()
                return DataSource_Value;
             * u041Fu043Eu043Bu0443u0447u0438u0442u044C u043Du0430u0437u0432u0430u043Du0438u0435
             * u0431u0430u0437u044B u0434u0430u043Du043Du044Bu0445
            public string GetDatabaseName()
                return InitialCatalog_Value;
             * u041Fu043Eu043Bu0443u0447u0438u0442u044C u0438u043Cu044F
             * u0442u0435u043Au0443u0449u0435u0433u043E u043Fu043Eu043Bu044Cu0437u043Eu0432u0430u0442u0435u043Bu044F
            public string GetUserName()
                return UserID_Value;
             * u041Fu043Eu043Bu0443u0447u0438u0442u044C u043Fu0430u0440u043Eu043Bu044C
             * u0442u0435u043Au0443u0449u0435u0433u043E u043Fu043Eu043Bu044Cu0437u043Eu0432u0430u0442u0435u043Bu044F
            public string GetPassword()
                return Password_Value;
             * u041Fu0435u0440u0435u0432u043Eu0434 u0441u0442u0440u0443u043Au0442u0443u0440u044B u0432 u0442u0435u043Au0441u0442u043Eu0432u044Bu0439 u0432u0438u0434
             * u0434u043Bu044F u0438u0441u043Fu043Eu043Bu044Cu0437u043Eu0432u0430u043Du0438u044F u043Fu0440u0438 u0441u043Eu0437u0434u0430u043Du0438u0438 u043Au043Eu043Du043Du0435u043Au0442u043Eu0440u0430
            public override string ToString()
                return "Data Source="+DataSource_Value+";Initial Catalog="+
                    InitialCatalog_Value+";User ID="+UserID_Value+";Password="+
                    Password_Value;
         * u0424u0443u043Du043Au0446u0438u044F u043Fu043Eu043Bu0443u0447u0435u043Du0438u044F u0441u0442u0440u043Eu043Au0438 u043Fu043Eu0434u043Au043Bu044Eu0447u0435u043Du0438u044F u043Fu043E u0443u043Cu043Eu043Bu0447u0430u043Du0438u044E
         * u043Du0443u0436u043Du0430 u0431u044Bu043Bu0430 u0434u043Bu044F u0442u0435u0441u0442u043Eu0432
        static private string GetDefaultConnectionString()
            return "Data Source=BSRV01;Initial Catalog=Prokat_Last;User ID=sa;Password=";
         * u0412u043Du0443u0442u0440u0435u043Du043Du044Fu044F u0441u0442u0440u043Eu043Au0430 u043Fu043Eu0434u043Au043Bu044Eu0447u0435u043Du0438u044F
         * u043Du0435 u0434u043Eu0441u0442u0443u043Fu043Du0430 u0434u043Bu044F u0432u044Bu0437u043Eu0432u0430 u043Du0430u043Fu0440u044Fu043Cu0443u044E
        private ConnectionString localConnectionString;
         * u0423u0441u0442u0430u043Du043Eu0432u0438u0442u044C u0441u0442u0440u043Eu043Au0443 u0432u043Du0443u0442u0440u0435u043Du043Du0435u0433u043E u043Fu043Eu0434u043Au043Bu044Eu0447u0435u043Du0438u044F
        public void SetConnectionString(ConnectionString CS)
            this.localConnectionString = CS;
         * u041Fu043Eu043Bu0443u0447u0438u0442u044C u0441u0442u0440u043Eu043Au0443 u0432u043Du0443u0442u0440u0435u043Du043Du0435u0433u043E u043Fu043Eu0434u043Au043Bu044Eu0447u0435u043Du0438u044F
        public ConnectionString GetConnectionString()
            return this.localConnectionString;
         * u0424u0443u043Du043Au0446u0438u044F u0443u0434u0430u043Bu0435u043Du0438u044F u0432u0440u0435u043Cu0435u043Du043Du043Eu0433u043E u0444u0430u0439u043Bu0430
         * u043Fu043Eu0441u043Bu0435 u0437u0430u0432u0435u0440u0448u0435u043Du0438u044F u0432u0441u0435u0445 u043Eu043Fu0435u0440u0430u0446u0438u0439 u0441 u0448u0430u0431u043Bu043Eu043Du043Eu043C
        private void MainForm_FormClosed(object sender, FormClosedEventArgs e)
            if (FileTreeView.Nodes.Count!=0)
                if (File.Exists(TemplateFilePath))
                    File.Delete(TemplateFilePath);
         * u041Eu0431u0440u0430u0431u043Eu0442u0447u0438u043A u0434u0432u043Eu0439u043Du043Eu0433u043E u043Au043Bu0438u043Au0430
         * u043Fu043E u0448u0430u0431u043Bu043Eu043Du0443 u0432 u0434u0435u0440u0435u0432u0435 u0444u0430u0439u043Bu043Eu0432
        public void FileTreeView_DoubleClick(object sender, EventArgs e)
            int Result = 0;
            try
                Result = ParseReportWithDataBase();
                if (Result == 0)
                    Result = ParseReport(TempFilePath + FileTreeView.SelectedNode.Text.ToString() + ".rpt");
                    if (Result == 0)
                        Process.Start(TemplateFilePath);
                else
                    MessageBox.Show("u0424u0430u0439u043B u043Du0435 u043Cu043Eu0436u0435u0442 u0431u044Bu0442u044C u043Eu0442u043Au0440u044Bu0442!");
            catch (Exception ex)
                MessageBox.Show(ex.Message);
         * u041Fu043Eu043Bu0443u0447u0435u043Du0438u0435 u0432u0441u0435u0445 u0444u0430u0439u043Bu043Eu0432 u0441 u0440u0430u0441u0448u0438u0440u0435u043Du0438u0435u043C .rpt
         * u0438u0437 u0431u0430u0437u044B u043A u043Au043Eu0442u043Eu0440u043Eu0439 u043Fu0440u0438u0441u043Eu0435u0434u0438u043Du0438u043Bu0438u0441u044C
        public void GetReportNamesFromDataBase(ConnectionString CS)
            try
                SqlConnection C = new SqlConnection(CS.ToString());
                SqlDataAdapter adapter = new SqlDataAdapter();
                DataTable table = new DataTable();
                table.Clear();
                string sqlcom = "Select P115 from " + GetDataViewName(CS,"24") + " where P116 like '%.rpt'";
                SqlCommand Q1 = new SqlCommand(sqlcom,C);
                Q1.CommandType = CommandType.Text;
                adapter.SelectCommand = Q1;
                adapter.Fill(table);
                FileTreeView.Nodes.Clear();
                for (int i = 0; i < table.Rows.Count; i++)
                        FileTreeView.Nodes.Add(table.Rows<i>.ItemArray.GetValue(
                            table.Rows<i>.ItemArray.Length-1).ToString());
//                        MessageBox.Show(table.Rows<i>.ItemArray.GetValue(0).ToString());
                C.Close();
            catch (Exception ex)
                MessageBox.Show(ex.Message);
         * u041Fu043Eu043Bu0443u0447u0438u0442u044C u0438u043Cu044F DataView
         * u0434u043Bu044F u0442u0435u043Au0443u0449u0435u0433u043E u043Fu043Eu043Bu044Cu0437u043Eu0432u0430u0442u0435u043Bu044F
        private string GetDataViewName(ConnectionString CS,string ClassID)
            string ViewName = "";
            SqlConnection C = new SqlConnection(CS.ToString());
            C.Open();
            SqlCommand Q = new SqlCommand("[dbo].[_SysGetClassesInfoNew1]"/*P115 from dbo.Attr24 where P116='.rpt'*/, C);
            Q.CommandType = CommandType.Text;
            SqlDataAdapter adapter = new SqlDataAdapter();
            adapter.SelectCommand = Q;
            DataTable table = new DataTable();
            adapter.Fill(table);
            for (int i = 0; i < table.Rows.Count; i++)
                if (table.Rows<i>.ItemArray.GetValue(0).ToString() == ClassID)
                    ViewName = table.Rows<i>.ItemArray.GetValue(13).ToString();
                    // MessageBox.Show(ViewName);
            C.Close();
            return ViewName;
         * u041Eu0431u0440u0430u0431u043Eu0442u0447u0438u043A u043Au043Bu0438u043Au0430 u043Du0430 u0432u044Bu043Fu0430u0434u0430u044Eu0449u0435u043C
         * u043Cu0435u043Du044E u0432 u043Fu0443u043Du043Au0442u0435 "Delete"
        private void deleteToolStripMenuItem_Click(object sender, EventArgs e)
            FileTreeView.SelectedNode.Remove();

Uploading data from Legacy system

Hi
i am shorthly going to work on data migration project. I have never worked on a data migration project and want to know the answers for the following questions.
1] which technique i must first consider in data upload ( both master data and transaction data )
2] What steps are involved?
3] I know we can use LSMW, BAPI's , BDC , Direct Input , IDOC etc but want to know which one choose and when?
4] What care must be taken in each data migration
5] is there is std list of programs or a good document on when to choose what?
~SR

Hi,
Data migration can be done by the follwoing methods:
LSMW : for master data migartion or small data migartion
BAPI : its just like a FM , thru which u can create master aswell as Transactional data.
u have to import some paremetre as well as tables if required, and Bapi will RETURN the message saying so and so material/delievry had cretaed.
BDC : in BDC we got 2 methods.
CAll transaction and session.
CAll transacton : using this u can uplaod transcational data as well as master data.
the updation can be synchronus or asynchronus updates.
Session: using this u can uplaod transcational data as well as master data.
The updation in session is synchronus, so its time taking process.
Most of the time we go for Call transcation In real situations.
Dircet input method: its out dated.no longer it is being used.
in all the above cases, data is alraedy existing in flat file and u r going to migrate the data in one shot but IDOC is used where the dynamical data migration is necessary.
suppose say ones the material is craeted in legacy sytem , that particulat matreial shud be migarted to R/3.this can be handled thru IDOC.
Idoc: master data as well as Trnascational data is migarted thru IDOC( matmas, orders).
Idoc uses ALE technology in migartion of idoc.
Revert back if any issues.
Check these links.
SAP Data Migration with LSMW
http://www.sap-img.com/sap-data-migration.htm
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
LSMW
No ABAP effort are required for the SAP data migration. However, effort are required to map the data into the structure according to the pre-determined format as specified by the pre-written ABAP upload program of the LSMW.
The Legacy System Migration Workbench (LSMW) is a tool recommended by SAP that you can use to transfer data once only or periodically from legacy systems into an R/3 System.
More and more medium-sized firms are implementing SAP solutions, and many of them have their legacy data in desktop programs. In this case, the data is exported in a format that can be read by PC spreadsheet systems. As a result, the data transfer is mere child's play: Simply enter the field names in the first line of the table, and the LSM Workbench's import routine automatically generates the input file for your conversion program.
The LSM Workbench lets you check the data for migration against the current settings of your customizing. The check is performed after the data migration, but before the update in your database.
So although it was designed for uploading of legacy data it is not restricted to this use.
We use it for mass changes, i.e. uploading new/replacement data and it is great, but there are limits on its functionality, depending on the complexity of the transaction you are trying to replicate.
The SAP transaction code is 'LSMW' for SAP version 4.6x.
For those with the older SAP version (4.7 and below), the data migration programs might not have been pre-loaded.
You can download the LSMW at no cost from SAPNet under Services, SAP Methodology and Tools, category Tools.
If you are an existing SAP customer with an OSS ID, you can access the SAP Service Marketplace to download the LSWM for your Basis teams to install to your SAP system: http://service.sap.com/lsmw
The LSM Workbench carries out the following tasks:
Reads the transfer data from one or more files (for example, spreadsheets, sequential files etc.)
Converts the data from the source format into the target format
Note that with background processing, the input file must not be located in the presentation server. Access to presentation server files is only possible when you are working onlineUpload Condition Pricing
LSMW STEPS
Data Cleansing
Data cleansing allows you to compare, include and merge redundant business partner master records (potential duplicates) in data cleansing cases. Following the data cleansing process you can remove data records from the system using archiving.
Integration
Before you can carry out data cleansing, you must determine the redundant data in your system and include it in data cleansing cases.
You have the following options for duplicate recognition and creation of data cleansing cases.
The Business Address Services (BAS) provide interfaces for integrating the relevant external software (search machines).
User-defined programs
Services of data providers, who check their data for possible duplicates.
In the options described above, the data cleansing cases are created via the system and put into the data cleansing worklist for further processing.
In individual cases you can find potential business partner duplicates in the hitlist of the business partner search and create a separate data cleansing case.
After connecting the non-SAP software (search engines), the system starts duplicate recognition (Delta Scan) with every change to or new entry of a business partner for this specific individual record. You should do a full scan through the complete dataset at the beginning of the consolidation process using the non-SAP software, this registers all potential duplicates in data cleansing cases and makes them available or further processing.
Within the application basis, the referencing objects, which are taken into account by the data cleansing, are limited to the sub-objects of the business partner. You have the possibility to make modification-free enhancements to the referencing objects.
Prerequisites
You must have determined the redundant data records in your system.
To use the interface of the Business Address Services, make the following Customizing settings: SAP Implementation Guide -> Basis -> Basis Services -> Address Management -> Activate Duplicate Check Index Pool
Make the following system settings in the IMG of the SAP Business Partner: Basic Settings -> Data Cleansing -> Maintain Number Range / Define Priorities / Activate Data Cleansing.
Activities
Register data cleansing cases via BAPIs or create them in the dialog for business partner maintenance from the worklist or the business partner search.
Process the created data cleansing cases in a separate process step afterwards.
BATCH DATA COMMUNICATION
About Data Transfer In R/3 System
When a company decides to implement the SAP R/3 to manage business-critical data, it usually does not start from a no-data situation. Normally, a SAP R/3 project comes into replace or complement existing application.
In the process of replacing current applications and transferring application data, two situations might occur:
The first is when application data to be replaced is transferred at once, and only once.
The second situation is to transfer data periodically from external systems to SAP and vice versa.
There is a period of time when information has to be transferred from existing application, to SAP R/3, and often this process will be repetitive.
The SAP system offers two primary methods for transferring data into SAP systems. From non-SAP systems or legacy system. These two methods are collectively called batch input or batch data communication.
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
EDIT BATCH INPUT  SERVICES SYSTEM
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
Define jobs Jobs  Administration Tools
Or
System Jobsservices
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.
AN EXAMPLE WITH SESSION METHOD
Following program demonstrates how data is passed from flat file to SAP transaction and further to database table by using SESSION method.
The transaction is TFBA (to change customer).
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.
Flat file can be created in your hard disk as follows:
1 Vinod Krishna Hyderabad
2 Kavitha Secunderabad
3 Kishore Hyderabad
(Where 1st character field is Customer number, 2nd field is Customer name and 3rd field is City.)
To transfer this data to database table SCUSTOM following interface can be used.
REPORT DEMO1.
Following internal table is to upload flat file.
DATA: BEGIN OF ITAB OCCURS 0,
ID(10),
NAME(25),
CITY(25),
END OF ITAB.
*Following internal table BDCDATA is to pass date from internal table to session.
DATA: BDCTAB LIKE BDCDATA OCCURS 0 WITH HEADER LINE.
Variables
DATA: DATE1 LIKE SY-DATUM. DATE1 = SY-DATUM - 1. This is for Hold Date
To upload flat file to internal table.
CALL FUNCTION UPLOAD
EXPORTING
FILE NAME = C:FF.TXT
FILE TYPE = ASC
TABLES
DATA_TAB = ITAB
EXCEPTIONS
CONVERSION_ERROR = 1
INVALID_TABLE_WIDTH = 2
INVALID_TYPE = 3
NO_BATCH = 4
UNKNOWN_ERROR = 5
OTHERS = 6.
If sy-subrc = 0.
Calling Function to Create a Session
CALL FUNCTION BDC_OPEN_GROUP
EXPORTING
CLIENT = SY-MANDT
GROUP = POTHURI
HOLDDATE = DATE1
KEEP = X
USER = SY-UNAME
EXCEPTIONS
CLIENT_INVALID = 1
DESTINATION_INVALID = 2
GROUP_INVALID = 3
GROUP_IS_LOCKED = 4
HOLDDATE_INVALID = 5
INTERNAL_ERROR = 6
QUEUE_ERROR = 7
RUNNING = 8
SYSTEM_LOCK_ERROR = 9
USER_INVALID = 10
OTHERS = 11.
If sy-subrc = 0.
*-- MAIN Logic--
LOOP AT ITAB
PERFORM GENERATE_DATA. Populating BDCDATA Table
CALL FUNCTION BDC_INSERT
EXPORTING
TCODE = TFBA
TABLES
DYNPROTAB = BDCTAB
EXCEPTIONS
INTERNAL_ERROR = 1
NOT_OPEN = 2
QUEUE_ERROR = 3
TCODE_INVALID = 4
PRINTING_INVALID = 5
POSTING_INVALID = 6
OTHERS = 7.
REFRESH BDCTAB
ENDLOOP.
Calling function to close the session
CALL FUNCTION BDC_CLOSE_GROUP
EXCEPTIONS
NOT_OPEN = 1
QUEUE_ERROR = 2
OTHERS = 3.
Endif.
Endif.
*& Form GENERATE_DATA
Create BDC Data
FORM GENERATE_DATA
Passing information for 1st screen on BDCDATA
BDCTAB-PROGRAM = SAPMTFBA.
BDCTAX-DYNPRO = 100.
BDCTAP-DYNBEGIN = X.
APPEND BCDTAB.CLEAR BDCTAB.
Passing field information to BDCDATA
BDCTAB-FNAM = SCUSTOM-ID
BDCTAB-FVAL = ITAB-ID.
APPEND BDCTAB.CLEAR BDCTAB.
Passing BDC_OKCODE to BDCDATA
BDCTAB-FNAM = BDC_OKCODE.
BDCTAB-FVAL = /5.
APPEND BDCTAB.CLEAR BDCTAB.
Passing screen information for next screen to BDCDATA
BDCTAB-PROGRAM = SAPMTFBA.
BDCTAB-DYNPRO = 200.
BDCTAB-DYNBEGIN = X.
APPEND BDCTAB.CLEAR BDCTAB.
Passing screen information to BDCDATA
BDCTAB-FNAM = SCUSTOM-NAME.
BDCTAB-FVAL = ITAB-NAME.
APPEND BDCTAB.CLEAR BDCTAB.
Passing screen information to BDCDATA
BDCTAB-FNAM = SCUSTOM-CITY.
BDCTAB-FVAL = ITAB-CITY.
APPEND BDCTAB.CLEAR BDCTAB.
Passing BDC_OKCODE to BDCDATA
BDCTAB-FNAM = BDC_OKCODE.
BDCTAB-FVAL = SAVE.
APPEND BDCTAB.CLEAR BDCTAB.
ENDFORM. GENERATE_DATA
AN EXAMPLE WITH CALL TRANSACTION
Same steps to be repeated for CALL TRANSACTION
The only difference between the two types of interface is in Session method, you create session and store information about screen and data into session. When session is processed the data is transferred to database. While in CALL TRANSACTION, data is transferred directly to database table.
REPORT DEMO1.
Follow above Code till MAIN Logic. Even the Subroutine should be copied
LOOP AT ITAB
PERFORM GENERATE_DATA, Populating BDCDATA Table
Call transaction TFBA using BCDDATA Mode A Update S.
REFRESH BDCTAB
ENDLOOP.
check this link:
http://www.sap-img.com/abap/learning-bdc-programming.htm
http://www.sap-img.com/bdc.htm
www.sappoint.com/abap/bdcconcept.pdf
www.sap-img.com/abap/learning-bdc-programming.htm
www.sap-img.com/abap/question-about-bdc-program.htm
www.sapdevelopment.co.uk/bdc/bdchome.htm
www.planetsap.com/bdc_main_page.htm
Re: bdc mm01
http://www.sapbrain.com/TUTORIALS/TECHNICAL/BDC_tutorial.html
http://www.sap-img.com/abap/bdc-example-using-table-control-in-bdc.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/fa/097119543b11d1898e0000e8322d00/frameset.htm
http://myweb.dal.ca/hchinni/sap/bdc_home.htm
IDOC
What is IDOC ?
IDoc
Standard SAP format for electronic data interchange between systems (Intermediate Document). Different message types (such as delivery confirmations or purchase orders) normally represent different specific formats, the IDoc types. However, multiple message types with related content can be assigned to one IDoc type: For example, the IDoc type ORDERS01 transfers the logical message types ORDERS (purchase order) and ORDRSP (order confirmation).
Also check these link it will help you.
idoc information
http://help.sap.com/saphelp_nw2004s/helpdata/en/78/21785851ce11d189570000e829fbbd/frameset.htm
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/sapR3%28Idocs%29ToXI--Steps+Summarized&
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
ALE/ IDOC/ XML
Troubleshooting of ALE Process - /people/raja.thangamani/blog/2007/07/19/troubleshooting-of-ale-process
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://www.thespot4sap.com/Articles/SAP_XML_Business_Integration.asp
http://help.sap.com/saphelp_srm30/helpdata/en/72/0fe1385bed2815e10000000a114084/content.htm
IDOC Convertion
/people/kevin.wilson2/blog/2005/12/07/changing-fields-in-an-idoc-segment
Please check this online document for ALE and IDoc.
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEIO/BCMIDALEIO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDISC/CAEDISCAP_STC.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf
Also check this links for additional information.
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
serialization /people/alessandro.guarneri/blog/2006/11/26/content-based-serialization-dynamic-queue-name-in-xi
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters - IDoc to File
IDOc testing - /people/suraj.sr/blog/2005/12/29/generate-test-case-for-an-idoc-scenario
/people/ravikumar.allampallam/blog/2005/06/24/convert-any-flat-file-to-any-idoc-java-mapping - Any flat file to any Idoc
/people/pooja.pandey/blog/2005/07/27/idocs-multiple-types-collection-in-bpm - Collection of IDoc to Single File
/people/stefan.grube/blog/2006/09/18/collecting-idocs-without-using-bpm - collecting IDocs without BPM
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters - IDoc to File
Hope it will be useful to u....plz don't forget to reward points...!!!!
Regards
Vasu

Sending Date parameter from the form to Report

Dear Friend
Hi everybody, I am sending the date parameter to my report through a form ,and my date format in the form and in the report as follow : DD/MM/YYYY but when I enter the date as 18/1/2004 the system pass this value as follow : 18-JAN-04 but I want the system to pass my date format as 18/1/2004 not as 18-JAN-04 ,how can I do that
Best regards
Jamil

Ino,
thanks for your answer.
You're all rigth abouth the index issue. So I've written my SQL like you say in your post. But i get an error : "ORA-... Non-character found where character expected... " or something like that. I've checked nls_date_format in my client machine and the server (DB 8.1.7.4), and also the regional settings in both machines, and all are set to 'DD-MON-YY'. What can be wrong?
Thanks again for your time.
Jaime.

Problem with AddRow() in custom matrix on System Form

Hello all,
I'm trying to add 1 row to a custom matrix on a system form (Sales Quotation).
However I always get a RPC_E_SERVERFAULT exception when calling pMatrix.AddRow() and SBO crashes...
My code is simple:
        [B1Listener(BoEventTypes.et_CLICK, false)]
        public virtual void OnAfterClick(ItemEvent pVal)
            Form pForm = B1Connections.theAppl.Forms.Item(pVal.FormUID);
            // Add matrix line
            Matrix pMatrix = (Matrix) pForm.Items.Item("MATRIX").Specific;
            pMatrix.AddRow();
            // Set matrix line data
The matrix shows ok in the system form, inside a new folder.
What is the problem with my code?
Is there any way to add rows to a custom matrix in a system form?
This code runs ok if executed in a custom form...
Thanks!
Manuel Dias

hi.
R u facing any problem ...
actually add row and del row both are same.
in normal customization form and system form matrx...
Any problem are u facing...

Refresh data in a system form

Similar Messages

Maybe you are looking for