Fsr Rfc
This document was uploaded by user and they confirmed that they have the permission to share it. If you are author or own the copyright of this book, please report to us by using this DMCA report form. Report DMCA
Overview
Download & View Fsr Rfc as PDF for free.
More details
- Words: 499
- Pages: 3
RFC
1
RFC (Derivation, Validation and TLR engine) The RFC functions are implemented in the SAP environment. These RFC functions are called by the ETL Layer during various phases, by passing the required input parameters. The usage of RFC in the Derivation, Validation and Target Load Ready (TLR) phases is explained here. SAP RFC Derivation Engine The SAP RFC derivation engine covers the following engines. 1. B4.5.2_APAC_ALL (Used for Regional Off-Balance Sheet Derivation) 2. B4.5.4_APAC_DW_ACC The input parameters specified for a particular RFC function are sent to the corresponding RFC function call. The output from RFC is send back from SAP to our server. For example the Y_YFF_GLV4_GET_WORKDAY function is used to calculate the next business day. The input parameters that are being passed to this function are:
Input to RFC I_DATE I_DIRECTION I_DAYS I_CALENDAR1
Corresponding data from T_GW_TMP_PROCESSED_DATA table PSTNGDTE Null Null 'PH'
The output parameter derived from RFC function is listed below:
Output from RFC E_DATE
Return value to T_GW_TMP_PROCESSED_DATA table YYYYMMDD format
SAP RFC/FSI Validation Engine The SAP RFC validation engine covers the following components. 1. B3.4.1_APAC_ALL 2. B3.6.4.1.1 The SAP RFC and FSI validations are done in the SAP environment, through the RFC calls from ETL layer. If any errors are detected in the data present in SAP, then the
RFC
2
error report is sent back. Else no message is returned from the SAP through this RFC, indicating that the data available in SAP is correct. The details about the error are recorded in the error tables. 1. T_GW_ERR_RECORD_DEFAULT 2. T_GW_ERR_RECORD_HDR 3. T_GW_ERR_RECORD_ASN 4. T_GW_ERR_MSG_PARAMETERS Query: Clarification is required for the following rule. (RULE_NO - 3173) RULE_TEXT These validations would be handled through an RFC Process. FSI value will be derived based on GCoA and its possible GDS combinations. Once the GDS values are derived ETL need to check against this C3REDA table and ensure that a valid FSI value is possible to be derived. 1. What is the GCoA that is being referred to? 2. How do we get all possible GDS combinations? SAP R/3 & BW TLR Engine The SAP R/3 and BW TLR engine covers the following components. 1. 2. 3. 4. 5. 6.
B9.2_APAC_ALL_UPLOAD B9.4_APAC_ALL_UPLOAD B9.6_APAC_FLA_UPLOAD B9.7_APAC_NFI_UPLOAD B9.8_APAC_ALL_UPLOAD B9.9_APAC_ALL_UPLOAD
Output files are created by the TLR engines. These target files are renamed with a unique name using shell scripts, and uploaded to the SAP server. The status of the TLR engines is send to the SAP server by the RFC function that is being called in the TLR UPLOAD Components. History of the files that have already uploaded is also kept track by the shell scripts, which helps in further uploading process. Files are transferred through secured file transfer protocol. The process status is updated in the T_GW_PRC_FILES and T_GW_PRC_STAGE tables.
Queries:
RFC
3
1. How will the errors encountered during transferring of the files through SFTP command notified? 2. How do we know which RFC function is to be called at a specified point? Has it been specified anywhere.
1
RFC (Derivation, Validation and TLR engine) The RFC functions are implemented in the SAP environment. These RFC functions are called by the ETL Layer during various phases, by passing the required input parameters. The usage of RFC in the Derivation, Validation and Target Load Ready (TLR) phases is explained here. SAP RFC Derivation Engine The SAP RFC derivation engine covers the following engines. 1. B4.5.2_APAC_ALL (Used for Regional Off-Balance Sheet Derivation) 2. B4.5.4_APAC_DW_ACC The input parameters specified for a particular RFC function are sent to the corresponding RFC function call. The output from RFC is send back from SAP to our server. For example the Y_YFF_GLV4_GET_WORKDAY function is used to calculate the next business day. The input parameters that are being passed to this function are:
Input to RFC I_DATE I_DIRECTION I_DAYS I_CALENDAR1
Corresponding data from T_GW_TMP_PROCESSED_DATA table PSTNGDTE Null Null 'PH'
The output parameter derived from RFC function is listed below:
Output from RFC E_DATE
Return value to T_GW_TMP_PROCESSED_DATA table YYYYMMDD format
SAP RFC/FSI Validation Engine The SAP RFC validation engine covers the following components. 1. B3.4.1_APAC_ALL 2. B3.6.4.1.1 The SAP RFC and FSI validations are done in the SAP environment, through the RFC calls from ETL layer. If any errors are detected in the data present in SAP, then the
RFC
2
error report is sent back. Else no message is returned from the SAP through this RFC, indicating that the data available in SAP is correct. The details about the error are recorded in the error tables. 1. T_GW_ERR_RECORD_DEFAULT 2. T_GW_ERR_RECORD_HDR 3. T_GW_ERR_RECORD_ASN 4. T_GW_ERR_MSG_PARAMETERS Query: Clarification is required for the following rule. (RULE_NO - 3173) RULE_TEXT These validations would be handled through an RFC Process. FSI value will be derived based on GCoA and its possible GDS combinations. Once the GDS values are derived ETL need to check against this C3REDA table and ensure that a valid FSI value is possible to be derived. 1. What is the GCoA that is being referred to? 2. How do we get all possible GDS combinations? SAP R/3 & BW TLR Engine The SAP R/3 and BW TLR engine covers the following components. 1. 2. 3. 4. 5. 6.
B9.2_APAC_ALL_UPLOAD B9.4_APAC_ALL_UPLOAD B9.6_APAC_FLA_UPLOAD B9.7_APAC_NFI_UPLOAD B9.8_APAC_ALL_UPLOAD B9.9_APAC_ALL_UPLOAD
Output files are created by the TLR engines. These target files are renamed with a unique name using shell scripts, and uploaded to the SAP server. The status of the TLR engines is send to the SAP server by the RFC function that is being called in the TLR UPLOAD Components. History of the files that have already uploaded is also kept track by the shell scripts, which helps in further uploading process. Files are transferred through secured file transfer protocol. The process status is updated in the T_GW_PRC_FILES and T_GW_PRC_STAGE tables.
Queries:
RFC
3
1. How will the errors encountered during transferring of the files through SFTP command notified? 2. How do we know which RFC function is to be called at a specified point? Has it been specified anywhere.
