FPA Specific Replacements

Redwood Finance Automation Default parameters - ${F:<?>}

The replacements F retrieves its value from the FPA default parameter table /JCS/FPA_DEFPARM. The replacement parameter is the parameter name used in the table.

The replacement depends on the parameters BUKRS, KOKRS to provide the right context to retrieve the information.

Redwood Finance Automation table FCA_FPA_DefaultParameters

SAP Table/JCS/FPA_DEFPARM

Sync robotFCA_FPA_DefaultParameters_Synchronize

The logic to retrieve a parameter value for parameter NAME_PART1_PART2 is described below.

1. Retrieval of NAME_PART1_PART2.
2. Find the value with given organizational data. The values of the fields KOKRS and BUKRS from the Task context are compared with the fields CA and CC in the parameter table.
3. If no value was found, find the value with given KOKRS.
4. Find the value without any organizational parameters set.
5. If no value was found continue with retrieval of NAME_PART1_PART2_1 the same way described above.
6. If a value was found, continue with NAME_PART1_PART2_2 etc. according to the algorithm above. The result is the concatenated value of all found values.
7. If no value was found continue with retrieval of NAME_PART1 1 the same way described above.
8. If no value was found, continue with the parent entry of NAME_PART1, which is NAME, the same way as described above.

Example

${F:BATCH_USER}

Default Parameter system dependent- ${D:<?>}

With this replacement, you can access the Default Parameter table which can be used to define standard settings which are target system specific.

The replacement depends on the parameters SAP_SYSTEMS, CLIENT, BUKRS, KOKRS, WERKS to provide the right context to retrieve the information.

Redwood Finance Automation table FCA_SAP_DefaultParametersBySystem

SAP table/JCS/FI_DEFPARM

Sync robotFCA_SAP_DefaultParametersBySystem_Synchronize

The logic to retrieve a parameter value for parameter NAME_PART1_PART2 is described below.

1. Retrieval of NAME_PART1_PART2.
2. Find the value with given organizational data. The values of the fields KOKRS, BUKRS and WERKS from the Task context are compared with the fields CA, CC and Plnt in the parameter table.
3. If no value was found, find the value with given KOKRS and BUKRS.
4. If no value was found, find the value with given KOKRS.
5. Find the value without any organizational parameters set.
6. If no value was found continue with retrieval of NAME_PART1_PART2_1 the same way described above.
7. If a value was found, continue with NAME_PART1_PART2_2 etc. according to the algorithm above. The result is the concatenated value of all found values.
8. If no value was found continue with retrieval of NAME_PART1 1 the same way described above.
9. If no value was found, continue with the parent entry of NAME_PART1, which is NAME, the same way described above.

Example

${D:DL_AFAB}

Cross System Variable Parameter

Retrieves the value from the cross System variable table FCA_Variables and if there is no value for the specified parameter, it will retrieve the value from the FCA_FPA_DefaultParameters table instead.

Syntax

${PV:<parameter>}}

Example

${PV:Counter}

See Also

Usage of Replacements

financeTopic