Tlr

Target Load Ready Engine: In this engine, ETL generates the required target files by retrieving the data from T_GW_TMP_PROCESSED_DATA table and calls a RFC function to post the output data to SAP. Please refer the below mappings of TLR Engine. While processing it loads the file upload information into T_GW_PRC_FILES. These are the mappings which generates the target files. m_B9.2_APAC_ALL m_B9.4_APAC_ALL m_B9.6_APAC_FLA m_B9.7_APAC_NFI m_B9.8_APAC_ALL m_B9.9_APAC_ALL m_B9.6.4.3.1 These are the mappings which call a RFC function to post the output data to SAP and load the file upload information into T_GW_PRC_FILES table. As of now these mappings are out of scope. Still KT session has to be taken. m_B9.2_APAC_ALL_UPLOAD m_B9.4_APAC_ALL_UPLOAD

Questions: 1. The checksum value is hard coded to ‘12345’ in most of the mappings. Please check and confirm. We tried to get specification for checksum calculation from Joseph and SAP team, but no one was able to provide it. Finally SAP team confirmed that we can use some fixed value, so we are writing 12345 there. 2. The BW structure is different from mapping to the structure provided by you (Matthias). I have considered the “Primary key Master Data” sheet structure for the same. Please check and confirm. We have a lot of different structure documents. The expected structure should be the implemented. But we have to discuss this with SAP and Bussines to get a confirmation. At the moment we have at least 3 different structure-documents (TAXONOMY, TLR-Description in Excel file, Description in FSR TDD BW-ETL Integration ver 0.2.doc).

3. Can you please provide us the footer, header and control file structures? Document “FSR TDD BW-ETL Integration ver 0.2.doc” in the folder “Y:\APAC\Build\ETL 1.0\BW Specific\TDD” should provide this information. This document has to be revised, because it is not up to date. 4. The off BS Master Data (B9.9_APAC_ALL) is different from mapping to the structure provided by you (Matthias). a) LDS_Interest_Rate and LDS_Geographic_Location columns are commented in the code which is present in the xls sheet target structure. The according Rules in the Taxonomy were removed. So the structure and the Taxonomy are not in sync. The taxonomy is our golden source so we deleted the field from the TLR. This version of TLR is already tested. b) COUNTERPARTY_INDICATOR, SECURITY_ID and SOURCE_SYSTEM_ACCOUT_ID are included mapping code which is not present in the xls sheet target structure. Only the Source_system_ACCOUNT_ID is not includet in latest Document. But this is still to clarify in the taxonomy clean-up process. 5. The RFP structure is also different. Please check and confirm. This should also be checked in the clean-up process. The Rules and the structure file is not up to date.