+
+|
+
+Name
+
+ |
+
+
+Service Plan
+
+ |
+
+
+Description
+
+ |
+
+
+|
+
+free
+
+ |
+
+
+Free
+
+ |
+
+
+Allows you to create small proof-of-concept development projects. Also can be used for the piloting of a remote ABAP test cockpit scenario against on-premise systems in the Custom Code Migration app. The instance will be stopped each night automatically and needs to be started again via the Landscape Portal. Only community support is available for free tier service plans and these are not subject to SLAs.
+
+ |
+
+
+|
+
+standard
+
+ |
+
+
+Standard
+
+ |
+
+
+Allows you to create projects for development, test, and productive ABAP systems. The minimum system size is 2 HANA Compute Units and 1 ABAP Compute Unit.
+
+It is mandatory to assign a combination of three entitlement service plans: ABAP Compute Unit, HANA Compute Unit, and either the Free, Standard, or SaaS OEM plan.
+
+ |
+
+
+|
+
+abap\_compute\_unit
+
+ |
+
+
+Standard
+
+ |
+
+
+Allows you to configure runtime memory, which refers to volatile memory used during the execution of applications. This memory provides fast read and write access but loses all data when the system is restarted or shut down. The metric measures the amount of runtime memory used in 16 GB blocks on an hourly basis.
+
+It is mandatory to assign a combination of three entitlement service plans: ABAP Compute Unit, HANA Compute Unit, and either the Free, Standard, or SaaS OEM plan.
+
+ |
+
+
+|
+
+hana\_compute\_unit
+
+ |
+
+
+Standard
+
+ |
+
+
+Allows you to configure persistent memory, which refers to storage that retains data even after the system is restarted or shut down. The metric measures the amount of persistent storage used in 16 GB blocks on an hourly basis.
+
+It is mandatory to assign a combination of three entitlement service plans: ABAP Compute Unit, HANA Compute Unit, and either the Free, Standard, or SaaS OEM plan.
+
+ |
+
+
+|
+
+saas\_oem
+
+ |
+
+
+SaaS OEM
+
+ |
+
+
+Allows you to create projects for ABAP systems to run multitenancy SaaS applications. The minimum system size is 2 HANA Compute Units and 1 ABAP Compute Unit.
+
+It is mandatory to assign a combination of three entitlement service plans: ABAP Compute Unit, HANA Compute Unit, and either the Free, Standard, or SaaS OEM plan.
+
+ |
+
+
+|
+
+16\_abap\_64\_db \(Deprecated\)
+
+ |
+
+
+16 GB Runtime and 64 GB Persistence \(Deprecated\)
+
+ |
+
+
+This ABAP runtime service plan provides a 16 GB ABAP runtime with a 64 GB database. No additional sizing is possible.
+
+This service plan is deprecated. Please change the service plan to “standard”.
+
+ |
+
+
+
+
+
+
|
-[SAP Web IDE](https://help.sap.com/viewer/product/SAP_Web_IDE/CF/en-US)
-
- |
-
-
-With SAP Web IDE Full-Stack, you can easily develop, test, build, deploy, and extend role-based, consumer-grade apps for business users. Create applications rapidly and deliver an outstanding user experience. You can extend or build SAP Fiori apps, create SaaS solutions, extend SAP S/4HANA cloud services, develop hybrid mobile apps, and build IoT apps for SAP Leonardo, using the UI development toolkit for HTML5, the SAP HANA toolset, and Java programming language and technologies.
-
- |
-
-
+
+|
+
+Method
+
+ |
+
+
+Parameter
+
+ |
+
+
+Description
+
+ |
+
+
+|
+
+`Get_Content_List`
+
+This method is used to get the list of context elements for BRFplus function.
+
+ |
+
+
+Importing: `IV_FUNCTION_ID`
+
+ |
+
+
+ID of the function to be processed.
+
+ |
+
+
+|
+
+Importing: `V_TIMESTAMP`:
+
+ |
+
+
+The timestamp parameter specifies the data retrieval or function evaluation time. Without a timestamp, the function returns the context list at the current date and time.
+
+ |
+
+
+|
+
+Importing: `IV_TRACE_GENERATION`
+
+ |
+
+
+This Boolean indicates that the trace should be generated with a lean trace or not.
+
+ |
+
+
+|
+
+Exporting: `ET_CONTEXT_LIST`
+
+ |
+
+
+The exporting parameter is a table containing the function's context list, which includes the id, name, and data object type of each context.
+
+ |
+
+
+|
+
+`GET_CONTEXT_VALUE`
+
+This method is used to get the value of the context object of a BRFplus function in a referenced object.
+
+ |
+
+
+Importing: `IV_FUNCTION_ID`
+
+ |
+
+
+ID of the function to be processed.
+
+ |
+
+
+|
+
+Importing:`IV_DATA_OBJECT`
+
+ |
+
+
+A character-like parameter that specifies the name or ID of the data object involved in the function call.
+
+ |
+
+
+|
+
+Importing: `IV_TIMESTAMP`
+
+ |
+
+
+The timestamp parameter specifies the point in time for data retrieval or function evaluation. If no timestamp is provided, the function returns the context value at the current date and time.
+
+ |
+
+
+|
+
+Importing: `IV_TRACE_GENERATION`
+
+ |
+
+
+This Boolean indicates that the trace should be generated with a lean trace or not.
+
+ |
+
+
+|
+
+Exporting: `EV_DATA`
+
+ |
+
+
+This parameter exports the data object's actual value after function execution. Its type "ANY" indicates flexibility to handle any data type, expanding the function's return possibilities.
+
+ |
+
+
+|
+
+Exporting: `ER_DATA`
+
+ |
+
+
+This exporting parameter references the data object, enabling its manipulation or examination beyond the function call.
+
+ |
+
+
+|
+
+`GET_DATA_OBJECT_REFERENCE`
+
+This method is used to get the data reference of a context object in BRFplus function.
+
+ |
+
+
+Importing: `IV_FUNCTION_ID`
+
+ |
+
+
+ID of the function to be processed.
+
+ |
+
+
+|
+
+Importing: `IV_DATA_OBJECT`:
+
+ |
+
+
+Importing: IV\_DATA\_OBJECT: A character-like parameter that specifies the name or ID of the data object involved in the function call.
+
+ |
+
+
+|
+
+Importing: `IV_DATA_OBJECT`
+
+ |
+
+
+A character-like parameter that specifies the name or ID of the data object involved in the function call.
+
+ |
+
+
+|
+
+Importing: `IV_TIMESTAMP`
+
+ |
+
+
+Importing: IV\_TIMESTAMP: The timestamp parameter specifies a specific point in time for data retrieval or function evaluation. If no timestamp is provided, all function context in a referenced object at the current date and time is returned.
+
+ |
+
+
+|
+
+Importing: `IV_TRACE_GENERATION`
+
+ |
+
+
+Importing: IV\_TRACE\_GENERATION: This Boolean indicates that the trace should be generated with a lean trace or not.
+
+ |
+
+
+|
+
+Exporting:
+
+`EV_DATA_OBJECT_NAME`
+
+ |
+
+
+This parameter exports the technical name of the data object involved in the operation, providing metadata such as its name or identifier.
+
+ |
+
+
+|
+
+Exporting `ER_DATA`
+
+ |
+
+
+This exporting parameter provides a reference to the data object. It does not contain an actual value but rather a pointer to the data object.
+
+ |
+
+
+|
+
+`MOVE_DATA_TO_DATA_OBJECT`
+
+This method is used to pass data from external source to BRFplus function’s context.
+
+ |
+
+
+Importing: `IR_DATA`
+
+ |
+
+
+This is a reference to any ABAP data object. It allows the method to directly interact with ABAP data objects provided by the calling program, offering a flexible interface for data processing.
+
+ |
+
+
+|
+
+Importing: `IV_FUNCTION_ID`
+
+ |
+
+
+ID of the function to be processed.
+
+ |
+
+
+|
+
+Importing: `IV_DATA_OBJECT`:
+
+ |
+
+
+A character-like parameter that specifies the name or ID of the data object involved in the function call.
+
+ |
+
+
+|
+
+Importing: `IV_TIMESTAMP`
+
+ |
+
+
+The timestamp parameter is used to define a specific point in time for the data retrieval or function evaluation. If no time stamp is provided, then it takes current date and time.
+
+ |
+
+
+|
+
+Importing: `IV_TRACE_GENERATION`
+
+ |
+
+
+This Boolean indicates that the trace should be generated with a lean trace or not.
+
+ |
+
+
+|
+
+Importing: `IV_HAS_DDIC_BINDING`
+
+ |
+
+
+Indicates whether the data passed to the method confirms to a DDIC \(Data Dictionary\) structure as defined in BRF+.
+
+ |
+
+
+|
+
+Exporting: `ER_DATA`
+
+ |
+
+
+This exporting parameter exports a reference to a BRFplus data object. This allows the method to return a data object that can be further manipulated or evaluated outside the method.
+
+ |
+
+
+|
+
+`PROCESS `
+
+With this method, a BRFplus function can be processed. You can specify a timestamp for the function to be processed so you can simulate the system behavior as it would have been at that point. Also, you can decide whether the trace for the function execution shall be saved in database for later reference or not.
+
+ |
+
+
+Importing: `IV_FUNCTION_ID`
+
+ |
+
+
+ID of the function to be processed.
+
+ |
+
+
+|
+
+Importing: `IV_TIMESTAMP`
+
+ |
+
+
+The timestamp parameter is used to define a specific point in time for the data retrieval or function evaluation. If no time stamp is provided, the result of the function at the current date and time is returned.
+
+ |
+
+
+|
+
+Importing: `IV_TRACE_MODE`
+
+ |
+
+
+Indicates the modes of trace. By default, mode is ‘L’ \(Lean Trace\).
+
+ |
+
+
+|
+
+Importing: `: IV_SAVE_TRACE`
+
+ |
+
+
+Indicates whether the trace generated for current processing of the Function should be saved in database.
+
+ |
+
+
+|
+
+Importing:`IT_ID_VALUE`
+
+ |
+
+
+Table of ID/value pairs \(ID/reference to value for each context element\). From a performance perspective, this is the most efficient way of triggering the processing of BRFplus. Also, using this parameter requires that you know the IDs of the context elements that you want to pass.
+
+ |
+
+
+|
+
+Exporting: `EA_RESULT`
+
+ |
+
+
+Exporting: EA\_RESULT:
+
+A variable of a type that is compatible with the result data object of the BRFplus function. You can get an ABAP data object of this type \(a reference\) by calling method`CL_FDT_FUNCTION_PROCESS_API ->IF_FDT_FUNCTION_PROCESS_API~GET_DATA_OBJECT_REFERENCE`.
+
+ |
+
+
+
diff --git a/docs/30-development/application-router-configuration-c19f165.md b/docs/30-development/application-router-configuration-c19f165.md
index 46a59f94..3d72f94e 100644
--- a/docs/30-development/application-router-configuration-c19f165.md
+++ b/docs/30-development/application-router-configuration-c19f165.md
@@ -240,17 +240,39 @@ In addition, the relevant destination configurations in the *