" The functions Hold data and Set data is used when you want to create a group of objects that contain the same data. The function Hold data can be used to create data that can be changed, for example if you wish to create multiple objects with slight variation in the field values (Sales order or Purchase order) then the function Hold data can be used. If you wish to create multiple objects with exactly the same data without changing any of the filed values then SET data can be used. To hold data on the screen you need to first enter the data in the field and then choose User Profile from the Systems Menu. Now choose Hold data. The data that you hold on the screen can be changed. In case if you wish to hold data on the screen without changing it then select SET data. This way the data will be held but you will not be able to change the contents of the individual fields. You can delete the Data that is held. To do this select User profile from the Systems menu and select the option Delete data. Once the delete Data option is selected no data will be displayed the next time you visit the screen. You may want to work in more than one screen, and would like to store data in each screen, to do this you can press Ctrl+S or click on the save icon while moving between screens. You can also Cancel the data that you have just entered on the screen. To do this press the cancel button. Please note that when using HOLD data and SET data options, the required/Mandatory fields on the screen cannot be ignored. The correct values should be entered in these fields before proceeding to the next screen. Using the menus and functions you can go to the other screens within your task, as well as in related tasks. Check the Goto Extras and Environment menus in the Menu bar to find out the other screens available within your task and related tasks. Depending upon the task the contents also change. "
"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 display Material data related to Material General Data, Material Plant Data and Material Valuation Data then you can use the following BAPI. This BAPI displays the above mentioned data for a Material.
BAPI/Function Module to display Material Data / Display Material Data BAPI/Function Module
BAPI_MATERIAL_GET_DETAIL
This BAPI has 4 input parameters
Material (Mandatory) Plant Valuation Area Valuation Type
Please find the code below.
REPORT ZEX_GETMATDET .
Parameters: p_matnr like BAPIMATDET-MATERIAL, p_werks like BAPIMATALL-PLANT, p_valara like BAPIMATALL-VAL_AREA, p_valtyp like BAPIMATALL-VAL_TYPE.
Data: st_matgendata like BAPIMATDOA, st_matplantdat like BAPIMATDOC, st_matvaldat like BAPIMATDOBEW, d_return like BAPIRETURN.
You may be knowing the SAP transaction, and would like to trace the path to this transaction in the SAP menu. To do this SAP has provided a way. There is a transaction called SEARCH_SAP_MENU.
With the help of this transaction you can easily search the path to a particular transaction. For example if you wish to search the path to the transaction XD01 (Create Customer Centrally) then you can execute the transaction SEARCH_SAP_MENU and hit enter. You will see the following. You can then choose the one that has the shortest path.
Finding SAP Transaction in the Menu SEARCH_SAP_MENU
If you wish to extract the bank details of a particular vendor then you can use the following BAPI.
BAPI/Function Module for vendor bank details extraction
BAPI_VENDOR_GETDETAIL
Please find below the code to extract vendor Bank Details.
REPORT ZEX_CUSTOMERBANK .
Parameters: p_kunnr like BAPICUSTOMER_ID-CUSTOMER, p_bukrs like BAPICUSTOMER_ID-COMP_CODE.
Data: ty_knbk type knbk, ty_custadd type BAPICUSTOMER_04, ty_custgendet type BAPICUSTOMER_KNA1, ty_custcompdet type BAPICUSTOMER_05, d_ret like BAPIRET1.
Data: wa_custadd like ty_custadd, wa_custgendet like ty_custgendet, wa_custcompdet like ty_custcompdet.
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.