What are SAP Note ?

Hi,
i am new to sap bw i would like to know what are SAP NOTes and where can i find those?

hi sai..
SAP notes are nothing but the standard solutions given by SAP for most frequently faced problems and querries.
Also if any corrective measures to be taken for the problems are explained in SAP notes.
They are avialable on service.sap.com
But you need login id for this.
The transaction code SNOTE is used to implement OSS Notes. With the SNOTE
transaction, it is no longer necessary to register ABAP objects such as report function
modules etc. manually. But data dictionary objects such as screens, tables need to
be modified manually by registering them in OSS system.
In order to use the transaction code SNOTE, the relevant transport which implement
this transaction in the system need to be transported. Please refer to the SNOTE
guide available at http://service.sap.com
for information you can refer http://www.sappoint.com/basis/snote.pdf
http://www.sap.info/index.php4?ACTION=noframe&url=http://www.sap.info/public/INT/int/index/PrintEdition-2558940029a53bfd4d-int/0/articleContainer-227444002b5ff8597d
go to URL https://websmp201.sap-ag.de/notes and enter the note number and display.
you need a service market place userid and password for this(check with basis team for user id and password)..
chk this blog...
/people/markus.meisl/blog/2006/11/03/the-most-important-sap-notes-for-sap-interactive-forms
hope this helps..

Similar Messages

What is sap note. where it will be used.

what is sap note. where it will be used. what are the advantages. when it will be used

http://www.sap-img.com/basis/manually-applying-the-oss-note.htm
http://www.sap-img.com/basis/oss-notes.htm

How can L identify what are the not null fields of a table in a stored procedure ?

How can L identify what are the not null fields of a table in a stored procedure ?

You could query the data dictionary:
SELECT column_name
FROM all_tab_columns
WHERE owner = '...'
AND table_name = '...'
AND nullable = 'N'

What are SAP products?

Dear all
i am new in SAP and research about SAP products in university .
so i want to know what are sap products exactly.
i heard many names as products of SAP AG but i don't know
the diffrences.for instance i read ABAP ,SAP GUI,NETWEAVER
SAP business one,my SAP business suite,what are the use of this products.what should someone do to establish a complete system of sap.deos it need to have database?
to explain more i know that ORACLE CORPORATION have 4 major products:
1. DATABASE Server
2. APPLICATION Server
3. Developer Suite
4. Application e-business suite 11i
so plz write for me what are SAP AG products and thier use

There are a lot of SAP products, I wouldn't name them all, but I will give the basics.
1) Web Application Server, ABAP and/or JAVA. This is the basis for SAP applications.
2) SAP R/3 or SAP ERP. These are the applications in which most companies have installed. These applications run the day to day business functions. They run on the ABAP side of the WAS. The frontend end that the user uses to interact with the system is the SAPgui.
3) There are many other systems which compliment your R/3 implementation such as CRM, SRM, APO, etc.
4) Enterprise Portal, is an application which runs on the Java side of the WAS, this is a web based frontend which integrates SAP applications and non-SAP applications into one central place where the user can access all kinds of data.
There are many other products in SAP, these are just the major ones.
SAP supports many databases, such as Oracle, SQL, DB2.
Regards,
Rich Heilman

What are the notes of the Smart Guitar?

When I open iOS GarageBand's Smart Guitar on Key C-Major, what are the notes I'm seeing? For instance, what are the notes when I tap the C chord string from 1 (bottom) to 6 (up)?
My actual goal is to record all string tap sounds, cut them into respective pieces in Audacity, then save them as e.g. "C.wav", for further use in another context. I like how GarageBand lays out the chords so my small (noncommercial) program aims to copy this, albeit I'm not a professional musician (as you can see from my question, I'm sure!).
Thanks!

1. Keeping track of the individual conversations taking place between applications on the source and destinations on the source and destination hosts. 2. Segmenting data and adding a header to identify and manage each segment. 3. Using the header information to reassemble the segments into applications data. 4. Passing the assembled data to the correct applications.

What are SAp Extension sets??

Hi all,
I'm doing a research about customizing in SAP and I've learnt about BC sets and their limitations. But...what are the Extension sets?? Are only predefined sets or can be created as the BC sets?? Are they similar to the BC sets??
Could anyone please give me some clue about them or provide me a link to this information??
Thanx all i advance.

Hi,
BC sets and Extension sets have nothing in common.
A BC set is a set of technical customisings as you said.
An extension set is a set of functional activities that you can activate with SPRO.
For exemple SAP R/3 4.70 has 2 releases of extension sets : 4.70 ext 1.10 and 4.70 ext 2.00.
Best Regards,
Olivier

Questions about 1003051 - TDMS 3.0 corrections - Composite SAP Note

Experts:
We, from a big SAP shop, want to set up TDMS for ERP, BI, HCM and CRM.
We have some questions about note 1003051:
1) Is this note about ERP (and HCM) only? If so, what are the notes for TDMS on BI and CRM?
2) Should we apply this note to all systems involved: sender, controller (SM7.0 in our case) and receiver?
3) We have enhp1...enhp4 in our ERP (and HCM), enhp1 on BI and perhaps enhp1 on CRM (not sure yet).
a) What is the impact of enhp on TDMS?
b) should we install TDMS before applying enhp OR the sequence does not matter?
Thanks for your help!

1) Is this note about ERP (and HCM) only? If so, what are the notes for TDMS on BI and CRM?
>This is a composite note, and contains information about various other notes related to TDMS. Refer to each note mentioned in this note individually to assess the same.
2) Should we apply this note to all systems involved: sender, controller (SM7.0 in our case) and receiver?
>Depends from note to note, Each note contains the necessary information about the system it has to be installed on.
3) We have enhp1...enhp4 in our ERP (and HCM), enhp1 on BI and perhaps enhp1 on CRM (not sure yet).
a) What is the impact of enhp on TDMS?
>TDMS in standard supports Basis 7.0 systems. However it generally works fine with 7.01 too.
b) should we install TDMS before applying enhp OR the sequence does not matter?
>As TDMS 3.0 is only available for systems with basis 4.6C to 7.0. So install TDMS first and then the EHP.
I hope these answers help.
Regards
Pankaj.

What is OSS notes

hi all,
can any one explain me what are oss notes? i need its explainination

See the below link
<a href="http://https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/fe8dbb80-0c01-0010-fe84-b76d0d07db34">http://https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/fe8dbb80-0c01-0010-fe84-b76d0d07db34</a>
In BW Goto T.Code SNOTE, here you can see all the notes which has been applied.. also u can apply a new note in this T.Code.
OSS Notes are corrections provided by SAP...You can find the here SAP Marketplace
Sometimes, R/3 have some bugs...Using OSS notes and transaction SNOTE you can get rid of those bugs -;)

WHAT ARE THE FORMS (SCRIPTS) WHICH ARE NOT PROVIDED BY STANDARD SAP?

WHAT ARE THE FORMS (SCRIPTS) WHICH ARE NOT PROVIDED BY STANDARD SAP?

Hi Pravin
For a beginner in CRM - Sales would be a right choice to understand how CRM behaves when integrated with backend R/3.
Still as far as CRM goes, most of the components are not exposed to their fullest potential and that is why its not outshining the competitors in market.

What are reasons to generate work schedules-not using SAP payroll or TM?

We have SAP ECC 6 HR and only pass a work schedule rule to our proprietory payroll system and have our own time and attendance system. The extent of our TM in SAP is just to have work schedules to attach to positions IT1011 and IT0007 on the employees. We are a very large 24/7 organization and have nearly 20,000 work schedules in use. It the past we have generated them out for 3 years and regenerate them as the come close to expiring.
My question is - what are some basic reasons for generating a work schedule? In our implementation I can't seem to find out why we need to continue doing it. We are able to attach an ungenerated work schedule to a position and a person.
Thanks in advance for any insight.

Generally the reasons why you would have a works schedule is for leave deduction, and possibly accruals, and also for automatic generation of overtime and shift penalties, public holidays. It could also further link into separate systems for payment purposes, or for attendance checks (i.e. EHS, rostering, training & event mgt, Sales & Distribution).
However, if your rostering/award interpretation is being handled in a separate system, and this information is being passed to a separate payroll system, then it would seem redundant to have work schedules in SAP.

What is the new sap note for Ptax slabs of FY 2011-12.

Dear Experts,
we are currently using ECC 6.0, release 604, patch level 0035 and support package SAPKE60435. professional tax slabs not updated in table V_T7INP4.
what is the new sap note for Ptax slabs of FY 2011-12.

Hi,
The Profession Tax tables T7INP3 & T7INP4 are customizing tables in which the entries are to be modified. SAP provides the initial entries and, if there is any change in slab rates, then you would need to update these slabs manually.
Please delimit the slab code in table T7INP3 and then create a new slab code entry from the date of delimition for the new rates in table T7INP4.
Regards,
Nishtha

What are the latest updates in the SAP GUI patches?

Hi All,
Can anyone let me know what are the major updates in the SAP GUI 730.
Any note that says this..The release note with each patch is too grainy and i cannot consolidate what are the major updates.
We are currently on patch level 1 and SAP GUI have patch 8 released?
Can someone kindly assist in identifying the major updates in SAP GUI 730?
Thanks,
Deep Desai

Hi,
You can see in the info section what are the new notes added in that patch.
Please see the below screenshot for your reference.
Regards
Sudhir Sadhu

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

What are the must have SAP componets req to publish MDM 7.1.03.86 on web

Can anyone explain to me what are the SAP components required for MDM 7.1.03.86 allowing me create a webpage front end to MDM 7.1 and create and publish my own screens?
Like many I am very new to the world of SAP.
There are many others in my own company with a vast knowledge of what are all the pieces needed to run almost anything
In SAP. One of the exceptions to this rule is SAP Master Data Management (MDM).
We run:
- SAP MDM version 7.1.03.86
- A Windows 2003 server
- Oracle 10.X.
- 7.1 Import Manager
- 7.1 Import Server
- 7.1 Data Manager
- 7.1 Syndication Server
- I see reference to the 7.1 MDM Publishers but I donu2019t see the API in the way I have software loaded right now.
I would like to get to the point where I can create a web portal front end to the MDM product.
My problem is I canu2019t get anyone to give me a an answer as to what are the other pieced of software I would need to get
In an end to end solution. Starting with barebones and working up to the works!
Here is what I would like to be able to do:
- Publish in a SAP Portal screens to the web. (SAP NetWeaver CE Portal, PI Portal ????)
- Write code in Java, SQL, VB and more, save and test them. (SAP NetWeaver WebDynpro for Java ???)
- create a web screen in the portal and publish to a Portal or URL. (SDK kit or Developer's kit Like: SAP NetWeaver
Developer Studio ???)
- It looks to me like the "SAP NetWeaver BPM" product is "Nice" to have but not required.
This is soo confusing, PLEASE help!
Thank You
Steve T

Hi Steve
Adding to Anu's response:
The prebuilt packages (worksets) cannot be used on a CE portal - only on a NW Enterprise Portal.
iView templates are also provided which allows you to put together your own pages and worksets. Again, these require the Enterprise Portal.
You don't have to use an SAP portal. You can use any webserver combined with Java code
(that makes use of the MDM Java API) to access the data (check out http://catalog.bd.com/ for a sample of this). Of course, this requires a lot more effort on your side.
"SAP NetWeaver BPM" amounts to NetWeaver CE. It is required if you want to make use of the WebDynpro components in new MDM releases.
Since you mentioned the MDM Publisher, if you want to simply publish "read only" data to a web front-end, you may be able to make use of the MDM Publisher together with Adboe InDesign.
Java code can make use of the MDM Java API. Windows development tools can make use of the MDM COM and MDM .NET APIs.
HTH,
Mark

What are the different ways to upload file data to SAP? Please help

Hi Experts,
I have to transfer huge file data (few lakhs records) to SAP business transaction. What are the different ways to do the same? I have heard of BDC and LSMW. But are there any more options?
Which option is best suited for huge file data?
Is LSMW an old technology and SAP will not support it any more?
Kindly answer my queries at the earliest.
I will be greatful to you if you can help me.
Thanks
Gopal

for uplodig data to non sap we have 2 methodes
i) if u know bapi u will use lasm
2) bdc
but u mentioned so many records isthere
best thing is u will uplode all record sto al11 using XI interface
then u have to write bdc / lsmw program
beter to go for lsmw before that u will find bapi
if u will unable to find bapi
u have to create bapi and use it in lasmw
ofter that u have schedule the lsmw program as a bockground
then u have to create a job for it
and release from sm 37
then u have to moniter through bd87
if u want to go through i will help u.
if it is usefull to u pls give points
Saimedha

What are SAP Note ?

Similar Messages

Maybe you are looking for