"In SAP for logging in to the system you need a user ID and a password. This user ID is created by the system administrator. The first time you login to the SAP system you need to change that password which has been assigned to you while creating the user ID. Every user ID will have certain roles assigned to it. The System Admin (Basis Administrator) is responsible for creating these roles after consulting the Functional team. Each user will typically have several roles assigned to their user ID. The user roles are predefined in the SAP system and each employee would have a combination of several roles which have been predefined in the SAP system. The roles are defined using the activity groups in the SAP system. A proper understating of the activity groups is necessary for creating and assigning Roles in the SAP system. Once a pre-defined user role is assigned to a user the system then automatically displays the appropriate User menu when the user logs on and provides the required authorization. An activity group can contain Transactions, Reports, Files, Web Links. Once the activity group has been assigned it defines the user specific menus. Once the user logs on to SAP a user specific menu is displayed this menu is controlled by the activity group that has been assigned to the user. To display a list of descriptions of the pre-defined user roles, select Tools---- Administration----User Maintenance--'Repository Infosys--' Activity Groups----' List of activity groups according to complex selection criterion---' Selection according to activity group name or call transaction S_BCE_68001418. The pre-defined user roles are delivered as templates and have names beginning with 'SAP_' and suffix _AG. Composite activity groups can be built with individual activity groups. A composite activity group does not contain any authorization."
"SAP has provided two different types of methods for BDC to do its work. Among these the first one is called the classical method. This method is also called as the session method. Through this method the data can be read by the BDC program from a sequential dataset file. This sequential dataset file is stored in batch-input sessions. In order to run the transaction in this session, What you need is to execute the session. For this follow these few steps. YOu an start and subsequently monitor the sessions firstly from System----> Service---->Batch input or have the sessions run in the background."
Enter the desired table name. Make sure that you follow the naming convention. Name should either start with 'Z' or 'Y'.
Delivery class needs to be entered as shown in the figure below.
Select A application table master and transaction data.
Check the table maintenance box. And click on the Fields Tab.
Enter the Filed names as shown in the figure below. Matnr with data element 'MATNR' For the 'ADDDESC' field please click on the Data element button as shown in the figure below.
Click on the technical settings button. For data class select APPL0
And For size category select 0
Select buffering not allowed for this table.
Make Material number as the Primary Key.
Activate the table.
Go back to transaction SE11 and select Utilities------> Table maintenance generator.
In the resulting screen for Authorization group select &NC&
Select the one step and standard recording routine
Now we need to create a Function group. For that we need to run transaction SE37.
Select Function group create.
Name the function group as ZMAT_ADD. Give an appropriate description.
Select Generate Objects from the drop down menu and select Create.
We need to activate the function group. To do so run transaction SE80. Select Function group and type the Function group name. Right click on the function group and click activate
Once this is done enter the scree number as 1 or select the available screen number by clicking the find screen number button.
Always specify your conditions in the Where-clause instead of checking
them yourself with check statements. The database system can then use an index
(if possible) and the network load is considerably less.
Always use Pretty Printer and Extended Program Check before releasing the code.
Do not leave unused code in the program. Comment the code thoroughly. Align the comments and the Code. Follow the SAP Standards and SAP Best Practices guidelines. It’s a good practice to take a dump of the code on your local drive.
