"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."
"A subset of Standard SQL that is fully integrated in ABAP is Open SQL statements. Their role is to help you by giving permission to access data irrespective of the database system, which the R/3 installation is using. The Data Manipulation Language (DML) part of the Standard SQL is present in the Open SQL. In other words, it gives you the permission to read (SELECT) and change (INSERT, UPDATE, DELETE) data. In the R/3 system, the tasks of the Data Definition Language (DDL) and Data Control Language (DCL) parts of the Standard SQL are performed by the ABAP dictionary and the authorization system."
If you wish to PopUp a Text Editor to your users this can be done by using the following function Module.
TERM_CONTROL_EDIT
This is useful in module pool programming when the user wants to enter some text either directly or via a text file from the presentation server. It can also be used to PopUp a screen for the users to enter some text in any of the business objects that needs to be exported to another business object or to an external system.
Please find the code below.
REPORT ZEX_MINITEXTEDITOR .
Parameters: P_title(10).
Data: Begin of int_text occurs 0, Text(100), End of int_text.
CALL FUNCTION 'TERM_CONTROL_EDIT' EXPORTING TITEL = P_title LANGU = 'E' TABLES TEXTLINES = int_text EXCEPTIONS USER_CANCELLED = 1 OTHERS = 2 . IF SY-SUBRC <> 0. * MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO * WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4. ENDIF.
In any company there are several systems apart from the ERP, SAP R/3 systems. For example a company could be using Siebel as the CRM package, Cognos as the BI solution and there could be a legacy system. Apart from the internal third party systems a company also need to interface with its partners (Customers and Vendors). This integration can be done in several ways depending upon the level of integration and the business objects that need to be integrated. One of the commonly used method is Electronic Data Interchange (EDI).
With the help of EDI business process can be integrated across companies, business documents such as Sales Orders, Purchase Orders, Invoices can be exchanged between partners. This is achieved by using Industry standards such as ANSI X12 (American National Standards Institute) and EDIFACT (Electronic Data Interchange For Administration, Commerce, and Transport).
EDI makes use of SAP's proprietary IDOC interface. This interface defines the format of the data that has to be interchanged between one SAP and another SAP system or between SAP and NON-SAP systems. EDI can be used with all the Modules of SAP eg. SD, MM, PP, FICO, PM, WM etc.
The Materials Management Module (MM) of SAP is completely integrated with other modules such as (SD, FICO, PP, WM, PM).
Procurement in SAP MM comprises of following.
Determination of Requirements
Source Determination
Vendor Selection
Purchase Order Processing
Purchase Order Follow-up
Goods Receiving and Inventory Management
Invoice Verification
Determination of Requirements: This phase comprises of identification of Material Requirements. This can be based on the user or MRP proper/Demand based approach to inventory control. Purchase Requisitions can be created manually (ME51N) Release (ME54) or can be generated using the System.
Source Determination: This Phase comprises of identification of potential sources of supply. This can be based on past orders, and existing agreements.
Vendor Selection: This Phase comprises of comparison of quotations received from Vendors. The system can check different quotations received from vendors.
Purchase Order Processing: In this phase information is acquired from the Requisition and the Quotation. Purchase Orders can be generated by the system or they can be created manually (ME21N).
Goods Receiving and Inventory Management: The goods receipts number can be obtained by entering the Purchase Order number.
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.
