Yes its will change the Internal table content as well. Since Field symbol is like a pointer only so changing its value will make changes in the source Internal table as well.
We can go to Tcode VOFM and based on our scenario we can check and routine number and its description for the specific process like Pricing in Requirements,Data Transfer ,Copy Requirements. We can set breakpoint and run the tcode for the Business process and check which is the correct VOFM routine that needs to be implemented.
"There are several ways to find BTE:
1. Go to FIBF tcode give attribute type A and tick the checkbox ""Display Short text only"" and execute.
It will dispplay all the Events along with some description which will help to choose the needed one.
2.Search the source code of Tcode for for “OPEN_FI_PERFORM” or ” OUTBOUND_CALL_”"
1. Go to FIBF tcode give attribute type A and tick the checkbox ""Display Short text only"" and execute.
It will dispplay all the Events along with some description which will help to choose the needed one.
2.Search the source code of Tcode for for “OPEN_FI_PERFORM” or ” OUTBOUND_CALL_”"
Its applied on Table level but programmatically we can achieve it on row level as well.
Dynamic Text is a Text Type in Smart Form and the value can be directly passed through Interface of the form. The data should be in table type TFSTEXT
"Using Text Type we can add text in smartforms.
Types of Text Type:
1. Text Element
2. Text Module
3. Include Text
4. Dynamic Text"
Types of Text Type:
1. Text Element
2. Text Module
3. Include Text
4. Dynamic Text"
Buffering is available under Technical Settings in SE11.
Buffering has 3 options.
SAP buffering can be permitted for a database table as follows:
Buffering not allowed
SAP buffering is not performed for the table. Open SQL always accesses the current data of the data table directly. This setting also dictates that SAP buffering should also not be activated for this table in any other systems due to the way it is used.
Buffering allowed, but switched off
SAP buffering is not performed for the table when delivered. This setting dictates, however, that buffering is possible in principle and can be activated in other systems depending on how the table is used.
Buffering switched on
SAP buffering is performed for the table. If possible, Open SQL statements access the SAP buffer in the shared memory instead of accessing the table directly.
Buffering has 3 options.
SAP buffering can be permitted for a database table as follows:
Buffering not allowed
SAP buffering is not performed for the table. Open SQL always accesses the current data of the data table directly. This setting also dictates that SAP buffering should also not be activated for this table in any other systems due to the way it is used.
Buffering allowed, but switched off
SAP buffering is not performed for the table when delivered. This setting dictates, however, that buffering is possible in principle and can be activated in other systems depending on how the table is used.
Buffering switched on
SAP buffering is performed for the table. If possible, Open SQL statements access the SAP buffer in the shared memory instead of accessing the table directly.
BAPI and RFC enabled FM are similar however, since BAPI is registered in BOR, it can be accessed through external applications and languages like VBA Excel or other places. RFC enabled FM works for SAP to SAP type systems
We can do that by modifying TMG Screen just like in module pool and add text to table control
"CMOD: To create a project to implement customer exists
SMOD: To search the exits"
SMOD: To search the exits"