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_”"
"If we pass by value..Inside the subroutine if you change the value it will not have effect (means it will not change the value) in the calling place..
If we pass by reference...Inside the subroutine if you change the value it will change in the calling place..Means it will share the same memory.."
If we pass by reference...Inside the subroutine if you change the value it will change in the calling place..Means it will share the same memory.."
Its applied on Table level but programmatically we can achieve it on row level as well.
Static methods cannot access instance variables and methods however instance methods can access static methods.
The first level of compression is a basic type which is Dictionary compression. Further, on the second level, there are advanced compression methods that we apply to the data compressed by dictionary compression. The methods under advanced compression type are prefix encoding, run-length encoding, cluster encoding, indirect encoding, and sparse encoding.
The UNNEST function converts one or many arrays into a table. The result table includes a row for each element of the specified array. The result of the UNNEST function needs to be assigned to a table variable
ARRAY_AGG ( )– Function can be used to convert a column of an Internal Table to an Array. its opposite to UNNEST
ARRAY_AGG ( )– Function can be used to convert a column of an Internal Table to an Array. its opposite to UNNEST
CE function is Calculation Engine function with below role:
CE functions are specially optimized for HANA and can perform better than a normal SQL statement.
CE functions are executed in calculation engine.
CE functions can also help structure the code in a simpler way
CE functions are specially optimized for HANA and can perform better than a normal SQL statement.
CE functions are executed in calculation engine.
CE functions can also help structure the code in a simpler way
"Join Engine:This engine is for processing the JOINS (all type of joins)/attribute views
OLAP Engine: This engine is used to process analytical view
Calculation Engine: used by Calculation View
It is the SQL optimizer, which sees the models and queries and decides which engine to call"
OLAP Engine: This engine is used to process analytical view
Calculation Engine: used by Calculation View
It is the SQL optimizer, which sees the models and queries and decides which engine to call"