| Status | |
|---|---|
| Owner | VIDWANS-ext, Sauradh |
| Stakeholders |
Purpose
The purpose of this document is to define the conversion approach to create Facilities Transactions in S/4 HANA.
Facilities are borrowing arrangements with either one or multiple banks. If we have a long term borrowing facility with one bank its called as Bi-Lateral Facility. Under this facility you, can define the fund requirements and the Bank will ear mark these funds to be drawn at a certain interval. If this facility is with multiple banks its called as Syndicate Facility. In a Syndicate there is normally a Lead Banker who will arrange the lending commitment from other lenders and will also have a Lead Banker charges.
These instruments are created under a certain Product Type (Instrument Number) and a Transaction Type (Kind of action i.e. buying or selling) against a counterparty (BP Number) in a Company Code.
Conversion Scope
The scope of this document covers the approach for converting active Facilities from Legacy Source System (Quantum) into S/4HANA.
The relevancy criteria is not applicable for this object as the relevant data will be provided by business in a DCT (Data Collection Template).
List of source systems and approximate number of records
| Source | Scope | Source Approx No. of Records | Target System | Target Approx No. of Records |
|---|---|---|---|---|
Quantum | Live Commercial Paper Contracts | 100 <TBC> | S4HANA | 100 <TBC> |
Additional Information
Multi-language Requirement
Document Management
Legal Requirement
Special Requirements
As the conversion involves a source system which is non-SAP, the below area needs special handling:
- Extraction of CP data from source system i.e. Quantum is to be done manually
- Cleansing by business team in the source system (Quantum) to ensure that only active and in use records for CP’s are provided in DCT
- The extracted records to be converted into a DCT and stored in the Syniti for Transformation
- Below Configuration Check Tables needs to be referenced in Syniti to validate the data in the DCT:
- Counterparty to Business Partner - BUT100
- Company Code - T001
- Product Type - TZPA
- Transaction Type - AT10
- Trader - TZDEA
- Portfolio Code - TWPOB
- General Valuation Class - TRGC_COM_VALCL
- Interest Calculation Method - Custom Check Table with Value Fields given in the below CNV
- Amount and date format from source system to align with S4HANA
- As the target structure in S4HANA involves dependency on various Configuration and BP Master Data objects (CNV 3040), all this data needs to be loaded before Transactions Data loads.
Custom Check Tables for Interest Calculation Method, Frequency and Update Rule are as under:
Interest Calculation Method:
Interest Calculation Method | Text |
1 | 360E/360 |
B | 360E/365 |
L | 360/360 (German) |
F | 360/360 (ISDA) |
H | 360/365 (ISDA) |
7 | 360/360 |
2 | act/360 |
E | act/364 |
3 | act/365 |
R | act/365.25 |
4 | act/366 |
M | act/365P |
5 | act/actP (ICMA) |
6 | act/actY (ISDA) |
G | act/actE (AFB) |
Q | act/actEP (AFB) |
N | act/365L |
S | act/365Y |
A | actW/252 |
D | 365/360 |
C | 365/365 |
I | 360E/actY |
8 | 30.42E/360 |
9 | *365.25/360 |
P | 01-01-2026 |
J | m+act/360 |
K | m+30/360 |
0 | Not Specified |
T | act/act[M] |
U | actW/actW[M] |
Update Rule:
| Rule Number | Text |
| 0 | Pro Rata Temporis |
| 1 | Include Fully |
| 2 | Do Not Include |
Frequency:
1 | At End of Term |
5 | On First Day of Month |
2 | On Last Day of Month |
3 | Monthly |
4 | Daily |
0 | Manual Input |
Target Design
For a Transaction Load DCT, since there are no standard LTMC objects that we can use for loading this data, we will be using BAPI’s for this purpose. In a BAPI there are multiple fields, off which all are not necessary to be utilized as part of DCT.
In this section, we will see the full list of fields that are part of the DCT. This section will also explain field by field mapping of the DCT structure and where the data will come from for each field.
The technical design of the target for this conversion approach.
| Table Name | Field | Field Description | Data Type | Length | Requirement |
|---|---|---|---|---|---|
| VTBFHA | BUKRS | COMPANY_CODE | CHAR | 4 | This is a Required Field |
| VTBFHA | SGSART | PRODUCT_TYPE | CHAR | 3 | This is a Required Field |
| VTBFHA | SFHAART | TRANSACTION_TYPE | CHAR | 3 | This is a Required Field |
| VTBFHA | KONTRH | PARTNER | CHAR | 10 | This is a Required Field |
| VTBFHA | DBLFZ | CONTRACT_DATE | DATS | 8 | This is a Required Field |
| VTBFHAZU | RDEALER | TRADER | CHAR | 12 | This is Optional Field |
| VTBFHA | RPORTB | PORTFOLIO | CHAR | 10 | This is Optional Field |
| VTBFHA | ZUOND | ASSIGNMENT | CHAR | 18 | This is Optional Field |
| VTBFHAZU | NORDEXT | EXTERNAL_REFERENCE | CHAR | 16 | This is Optional Field |
| VTBFHA | REFER | INTERNAL_REFERENCE | CHAR | 16 | This is Optional Field |
| VTBFHA | MERKM | CHARACTERISTICS | CHAR | 25 | This is a Required Field |
| VTBFHA | TPM_COM_VAL_CLASS | VALUATION_CLASS | NUMC | 4 | This is a Required Field |
| VTBFHA | DBLFZ | Term Start | DATS | 8 | This is a Required Field |
| VTBFHA | DELFZ | Term End | DATS | 8 | This is a Required Field |
| NA | NA | Calculation Period: Start Inclusive vs. End Inclusive | CHAR | 1 | This is a Required Field |
| VTBFHA | WGSCHFT | Transaction Currency | CUKY | 5 | This is a Required Field |
| VTB_ASGN_LIMIT | LIMIT_DATE | FTR Assignment Management: Limit Date | DATS | 8 | This is a Required Field |
| VTB_ASGN_LIMIT | LIMIT_CHG_AMOUNT | FTR Assignment Management: Drawing Amount | CURR | 17 | This is a Required Field |
| VTB_ASGN_LIMIT | LIMIT_CURRENCY | FTR Assignment Management: Limit Currency | CUKY | 5 | This is a Required Field |
| VTB_ASGN_LIMIT | LIMIT_POS_AMOUNT | FTR Assignment Management: Drawing Amount (BAPI) | DEC | 23 | This is a Required Field |
| VTBFINKO | SRHYTHM | Frequency | NUMC | 3 | This is Optional Field |
| VTBFINKO | AMMRHY OR ATTRHY (Pick any field that has a value. If the Frequency Indicator is set to Months, then AMMRHY will have a value. If Frequency Indicator is set to Days then ATTRHY will have a value. | Unit for Frequency | NUMC | 1 | This is Optional Field |
| VTBFHAPO | PKOND | Percentage rate for condition items | DEC | 10 | This is Optional Field |
| NA | NA | Calculation method for first period of condition item | NUMC | 1 | This is Optional Field |
| NA | NA | Calculation method for last period of condition item | NUMC | 1 | This is Optional Field |
| NA | NA | Interest Calculation Method | CHAR | 1 | This is Optional Field |
| VTBFHAPO | SKALIDWT | Interest Calendar | CHAR | 2 | This is Optional Field |
| NA | NA | Update for Calculation/Due Date for Interest | NUMC | 2 | This is Optional Field |
| VTBFHAPO | DVALUT | Calculation Date | DATS | 8 | This is Optional Field |
| NA | NA | Inclusive Indicator for Calculation Date | CHAR | 1 | This is Optional Field |
| NA | NA | Month-End Indicator for Calculation Date | CHAR | 1 | This is Optional Field |
| VTBFINKO | SVWERK | Working Day Shift for Calculation Day | NUMC | 1 | This is Optional Field |
| VTBFINKO | DFAELL | Due date | DATS | 8 | This is Optional Field |
| NA | NA | Month-End Indicator for Due Date | CHAR | 1 | This is Optional Field |
| VTBFINKO | SFWERK | Working Day Shift for Due Date | NUMC | 1 | This is Optional Field |
| NA | NA | Shift Due Date Back to End of Term | CHAR | 1 | This is Optional Field |
There are 5 main tables in consideration here.
- VTBFHA
- VTBFHAPO
- VTBFINKO
- VTB_ASGN_LIMIT
- VTBFHAZU
The reference between the tables is a combination of Company Code and Transaction Number. This is the Primary Key to join these tables.
In Addition to this, the field "Characteristics" will have the Legacy Quantum Deal Number. This will form a linkage between Deals loaded in the system vs Quantum deals.
In the above table we saw fields in the DCT. Now we will check the fields in the BAPI and the data logic how it will correspond to the DCT.
Data Cleansing
For the Object 9113 – Treasury Facilities no specific data cleansing is applicable due to below reasons/assumptions:
- The Source System is Quantum and therefore it will be a manual extract of relevant data in a DCT form
Data- Pre Load Validation Report
However, for the purpose of the object 9113 – Treasury Facilities, below validations reports should be available in Syniti so that the data as provided in DCT is validated before generating the pre-load file.
| ID | Criticality | Error Message/Report Description | Rule | Output |
|---|---|---|---|---|
| 1 | High | Company Code is valid | Check if BUKRS is valid as per Company Codes created in the system in Table T001 | Invalid Company Code |
| 1 | High | PRODUCT_TYPE | Check if VVSART is valid as per Product Types created in the system in Table TZPA. Value for Facility Product Type is “CPF” or "BLT". If this is not, then the validation should fail. | Invalid Product Type |
| 1 | High | TRANSACTION_TYPE | Check if SFHAART is valid as per Transaction Types created in the system in Table AT10 | Invalid Transaction Type |
| 1 | High | PARTNER | Check if KUNNR is valid as per Business Partners created in the system under CNV 3040 Business Partner Counterparty | Invalid Partner |
| 1 | High | CONTRACT_DATE | Check if DVTRAB is valid in YYYYMMDD Format and is < or = Load Date | Contract Date greater than Load Date |
| 1 | High | VALUATION_CLASS | Check if TPM_COM_VAL_CLASS is valid as per Company Codes created in the system in Table TRGC_COM_VALCL | Invalid Valuation Class |
| 1 | High | TERM START | Check if DBLFZ is valid in YYYYMMDD Format and is < or = Contract Date | Term Start greater than or equal to Contract Date |
| 1 | High | TERM END | Check if DELFZ is valid in YYYYMMDD Format and is < Start Date | Term End greater than Term Start |
Apart from the above, a custom report is required to be created for this. The report needs to have row reference for each Interest Rate Instrument loaded under this CNY and display the standard BAPI return messages successful as well as failed. This will make sure all the deposits successfully pass all checks. An additional check is needed if
- All dates loaded are correctly transformed into the deals created
- Payment Details are not going blank and if yes, the BAPI will return a warning for the same. If this warning appears, it will signify the BP Master Maintenance has been missed. Such records must fail and the maintenance needs to be done at the BP Master.
Conversion Process
The generic high-level process steps for the conversion are as below:
- Extraction:
- Extract from the source systems: Apply the selection parameters and data relevancy as mentioned in this specification, from the relevant tables
- DCT: The DCT to be prepared if the data to be transformed and is part of the load file is not available in the Source system
- Transform
- Transform fields by applying the fields and value mapping in the Syniti
- Generate and validate Pre-load files
- Load
- Load the validated Pre-load file using SAP's LTMC or the custom upload program as applicable.
However, with respect to object 9113- Treasury Facilities DCT will be used for transformation and generation of the pre-load file.
Data Privacy and Sensitivity
Not ApplicableExtraction
Extract data from a source into . There are 2 possibilities:
- The data exists. connects to the source and loads the data into . There are 3 methods:
- Perform full data extraction from relevant tables in the source system(s).
- Perform extraction through the application layer.
- Only if ; cannot connect to the source, data is loaded to the repository from the provided source system extract/report.
- The data does not exist (or cannot be converted from its current state). The data is manually collected by the business directly in . This is to be conducted using DCT (Data Collection Template) in
The agreed Relevancy criteria is applied to the extracted records to identify the records that are applicable for the Target loads
Extraction Run Sheet
| Req # | Requirement Description | Team Responsible |
|---|---|---|
01 | Extract from relevant tables/reports from Quantum all relevant information required to populate the DCT for Interest Rate Instruments for relevant Company Codes. This extraction is dependent on the extraction, validation and load of Master Data Object CNV 3040 BP Master. It is also dependent on completion of configuration for items like Company Code, Product Type, Transaction Type, Portfolio Codes, General Valuation Class. | Business |
Selection Screen
Not applicable as the extraction is manual activity to be performed by business in Quantum system.
Data Collection Template (DCT)
Target Ready Data Collection Template will be created for data with exception of some fields which require transformation as mentioned in the transformation rule.Target Ready Data Collection Template will be created for 9113 - TRM Facilities with exception of some fields which require transformation as mentioned in the transformation rule.
9113 - TRM Facilities DCT Rules
| Field Name | Field Description | Rule |
|---|---|---|
| BUKRS | COMPANY_CODE | This is a Required field. This data will be captured by business. It is the Company Code under which a Stock is to be created. In DCT, S4HANA number to be populated based upon the list of Company Codes. This list needs to be provided to the Business Team who will be downloading data from Quantum System. Default Value "1010" |
| SGSART | PRODUCT_TYPE | This is a Required field. This data will be captured by business. It is the Product Type under which a Stock is to be created. In DCT, S4HANA number is defaulted to “EAP”. Drop Down Value "CPF" and "BLT" |
| SFHAART | TRANSACTION_TYPE | This is a Required field. This data will be captured by business. It is the Transaction Type under which a Stock is to be created. In DCT, S4HANA number is defaulted to “100”. Default Value "OBT" |
| KONTRH | PARTNER | This is a Required field. This data will be captured by business for Counterparties. A validation is needed to check the BP number captured in the DCT is valid one and is present as per CNV 3040 - Business Partner Counterparty. Transformation Rule is to be applied to get the BP Number from BP Text. |
| DBLFZ | CONTRACT_DATE | This is a Required field. Date format is YYYYMMDD. Contract Date will always be LESS Than the Load Date. This check needs to be implemented. Example: 99991231 |
| RDEALER | TRADER | This is a Optional field. This data will be captured by business. It is the Trader who concludes the Stock. In DCT, S4HANA Trader Code needs to be populated based upon the list of configured Traders. This list needs to be provided to the Business Team who will be downloading data from Quantum System. Validation check needs to be done with check table TZDEA |
| RPORTB | PORTFOLIO | This is a Optional field. This data will be captured by business. It is the Portfolio Code to bucket all Stock under for reporting purposes.In DCT, S4HANA Portfolio Codes needs to be populated based upon the list of Portfolio's configured in the system. This list needs to be provided to the Business Team who will be downloading data from Quantum System. Validation check needs to be done with check table TWPOB |
| ZUOND | ASSIGNMENT | This is a Optional field. This is a freely maintainable field to capture additional data for the deal. No validations needed for this field. |
| NORDEXT | EXTERNAL_REFERENCE | This is a Optional field. This is a freely maintainable field to capture additional data for the deal. No validations needed for this field. |
| REFER | INTERNAL_REFERENCE | This is a Optional field. This is a freely maintainable field to capture additional data for the deal. No validations needed for this field. |
| MERKM | CHARACTERISTICS | This is a Required field. This field will be populated with the Legacy Quantum Deal Number |
| TPM_COM_VAL_CLASS | VALUATION_CLASS | This is a Required field. This data will be captured by business. It is the Valuation Class under which a Stock is to be accounted for. In DCT, S4HANA GVC number needs to be populated based upon the list of GVC's configured in the system. This list needs to be provided to the Business Team who will be downloading data from Quantum System. |
| DBLFZ | Term Start | This is a Required Field Date format is YYYYMMDD. Start Term Date will always be LESS Than or Equal to Load Date. This check needs to be implemented as part of Preload Validation. Example: If load date is 20260401 and date in DCT is 20260501, then the Validation Check should fail this record. |
| DELFZ | Term End | This is a Required Field Date format is YYYYMMDD. End Term will always be Greater Than the Load Date. This check needs to be implemented. Example: If load date is 20260401 and date in DCT is 20250401, then the Validation Check should fail this record. |
| NA | Calculation Period: Start Inclusive vs. End Inclusive | This is a Optional Field This field defines if the Start Date is to be made inclusive in the calculation of Interest |
| WGSCHFT | Transaction Currency | This is a Required Field This data will be captured by business. It is the Currency of the Fixed Deposit. Currency Codes are ISO standards hence it will be same in all Treasury systems. Still a Validation check is needed in Syniti to check if a valid Currency Code is used in the DCT. Drop Down value from table "TCURC" |
| LIMIT_DATE | FTR Assignment Management: Limit Date | This is a Required field This field defines from when the Facility Limit is applicable from. |
| LIMIT_CHG_AMOUNT | FTR Assignment Management: Drawing Amount | This is a Required field This field defines what is value of the facility. |
| LIMIT_CURRENCY | FTR Assignment Management: Limit Currency | This is a Required field This field defines what is the currency of the facility |
| LIMIT_POS_AMOUNT | FTR Assignment Management: Drawing Amount (BAPI) | This is a Required field This field defines what amount of the facility is available to be drawn. |
| SRHYTHM | Frequency | This is a Optional field This field defines the Frequency on which Interest is to be paid There is a domain value range for this field which needs to be given to business which they extract and prepare this DCT. For Eg. Monthly or Quarterly. Drop Down Value as per the "Frequency Category" table provided Above. |
| AMMRHY OR ATTRHY (Pick any field that has a value. If the Frequency Indicator is set to Months, then AMMRHY will have a value. If Frequency Indicator is set to Days then ATTRHY will have a value. | Unit for Frequency | This is a Optional field This field defines the number of days or months when Interest needs to be paid |
| PKOND | Percentage rate for condition items | This is a Optional Field This field defines the Interest Rate if applicable to the deal. |
| NA | Calculation method for first period of condition item | This is a Optional field This field defines what is the calculation method of first period of Interest. Drop Down Value from the table "Update Rule" |
| NA | Calculation method for last period of condition item | This is a Optional field This field defines what is the calculation method of Last period of Interest. Drop Down Value from the table "Update Rule" |
| NA | Interest Calculation Method | This is a Optional field This is the Interest Calculation Method for Day Counting of Interest and needs to be provided by business. There is a domain value range for this field which needs to be given to business which they extract and prepare this DCT. For Eg. ACT/360 in SAP means 2. Drop Down Value as per the "Interest Calculation Methods" table provided Above. |
| SKALIDWT | Interest Calendar | This is a Optional field This defines Calendar to be considered to check if the Payment date is a holiday. Calendars are another configuration item and a list needs to be provided to business to populate the DCT. A Pre Validation check is needed if the calendar is valid in the DCT. Drop Down Values from table "TFACD - IDENT" |
| NA | Update for Calculation/Due Date for Interest | This is a Optional field This field defines the update rule for Calculation Date and Due Date. Drop Down Values from table "Update Rules" |
| DVALUT | Calculation Date | This is a Optional field Date format is YYYYMMDD. Calculation Date will always be GREATER Than or Equal to Load Date. This check needs to be implemented as part of Preload Validation. Example: If load date is 20260401 and date in DCT is 20260501, then the Validation Check should fail this record. |
| NA | Inclusive Indicator for Calculation Date | This is a Optional field This field defines if calculation period is to be shiftred to Start Inclusive or End Enclusive Drop Down Value is "X" |
| NA | Month-End Indicator for Calculation Date | This is a Optional field This field defines if Calculation Date is to be shifted to nearest Month End Drop Down Value is "X" |
| SVWERK | Working Day Shift for Calculation Day | This is a Optional field This field defines the how the Working Day needs to be calculated, for eg. If the interest payment date is a holiday then it should shift it to the Next working date. Default Value "1" |
| DFAELL | Due date | This is a Optional field This field defines if calculation Date is to be shiftred to Start Inclusive or End Enclusive Drop Down Value is "X" |
| NA | Month-End Indicator for Due Date | This is a Optional field This field defines if calculation period is to be shiftred to Start Inclusive or End Enclusive Drop Down Value is "X" |
| SFWERK | Working Day Shift for Due Date | This is a Optional field This field defines the how the Working Day needs to be calculated, for eg. If the interest payment date is a holiday then it should shift it to the Next working date. Default Value "1" |
| NA | Shift Due Date Back to End of Term | This is a Optional field This field defines if the due date is to be shifted to the end date of the deal. Drop Down Value for this is "X" |
Extraction Dependencies
For object 9113 - TRM Facilities dependencies are applicable as under
| Item # | Step Description | Team Responsible |
|---|---|---|
0001 | TRM Business Partner | Data Team/Functional Treasury Team |
0002 | Treasury Configuration | Functional Treasury Team |
Transformation
The Target fields are mapped to the applicable Legacy field that will be its source, this is a 3-way activity involving the Business, Functional team and Data team. This identifies the transformation activity required to allow to make the data Target ready:
- Perform value mapping and data transformation rules.
- Legacy values are mapped to the to-be values (this could include a default value)
- Values are transformed according to the rules defined in
- Prepare target-ready data in the structure and format that is required for loading via prescribed Load Tool. This step also produces the load data ready for business to perform Pre-load Data Validation
Transformation Run Sheet
Item # | Step Description | Team Responsible |
1 | Ensure all the fields that require value mapping, as stipulated Mapping tables, have the latest signed-off mapping files imported into Syniti | Data team |
2 | Ensure that signed off value mappings have been maintained in the Syniti | Syniti team |
3 | Confirm the value mappings as maintained in the Syniti | Data team |
4 | Ensure that Signed off CONSTRUCT from business has been received and maintained in Syniti | Syniti/Data team |
5 | Execute transformation for the object | Syniti team |
6 | Monitor the transformation progress and ensure performance and completion is within allowed timeframe | Syniti/Data team |
7. | Generate Pre-Load reports. | Syniti team |
8. | Generate data load count. | Syniti team |
9. | Log errors as defects, if any and address resolutions. Close defects. | Syniti/Data team |
10. | Re-transform and re-validate the Pre-load reports if necessary. | Syniti/Data team |
11. | Validate the transformed file as part of pre-load validation, raise data defects or provide the pre-load sign-off. | Business |
12. | Analyse and resolve any pre-load defects logged by business. | Syniti/Data team |
13. | Repeat steps 5 to 11 if necessary | Syniti/Data team |
14. | Proceed to pre-load validations | Data team |
Transformation Rules
| Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|
| NA | NA | NA | CONSTRUCT | S4HANA | VTBFHA | BUKRS | COMPANY_CODE | From DCT Field BUKRS |
| NA | NA | NA | CONSTRUCT | S4HANA | VTBFHA | SGSART | PRODUCT_TYPE | From DCT Field SGSART |
| NA | NA | NA | CONSTRUCT | S4HANA | VTBFHA | SFHAART | TRANSACTION_TYPE | From DCT Field SFHAART |
| NA | NA | NA | CONSTRUCT | S4HANA | VTBFHA | KONTRH | PARTNER | From DCT Field KONTRH Step 1 - Concatenate BUT000 - Name_ORG1, Name_ORG2, Name_ORG3 & Name_ORG4. Step 2 - Compare the BP Name in the DCT with the concatenated filed name. Step 3 - Find the BP Number for the match BUT000 - PARTNER Step 4 - Pass the BP Number fetched in BUT000 in table BUT100 to check if Role "TR0151" Step 5 - If the condition matches, then replace the BP Number in the DCT field VTBFHA - KONTRH |
| NA | NA | NA | CONSTRUCT | S4HANA | VTBFHA | DBLFZ | CONTRACT_DATE | From DCT Field DBLFZ |
| NA | NA | NA | CONSTRUCT | S4HANA | VTBFHAZU | RDEALER | TRADER | From DCT Field RDEALER |
| NA | NA | NA | CONSTRUCT | S4HANA | VTBFHA | RPORTB | PORTFOLIO | From DCT Field RPORTB |
| NA | NA | NA | CONSTRUCT | S4HANA | VTBFHA | ZUOND | ASSIGNMENT | From DCT Field ZUOND |
| NA | NA | NA | CONSTRUCT | S4HANA | VTBFHAZU | NORDEXT | EXTERNAL_REFERENCE | From DCT Field NORDEXT |
| NA | NA | NA | CONSTRUCT | S4HANA | VTBFHA | REFER | INTERNAL_REFERENCE | From DCT Field REFER |
| NA | NA | NA | CONSTRUCT | S4HANA | VTBFHA | MERKM | CHARACTERISTICS | From DCT Field MERKM |
| NA | NA | NA | CONSTRUCT | S4HANA | VTBFHA | TPM_COM_VAL_CLASS | VALUATION_CLASS | From DCT Field TPM_COM_VAL_CLASS |
| NA | NA | NA | CONSTRUCT | S4HANA | VTBFHA | DBLFZ | Term Start | From DCT Field DBLFZ |
| NA | NA | NA | CONSTRUCT | S4HANA | VTBFHA | DELFZ | Term End | From DCT Field DELFZ |
| NA | NA | NA | CONSTRUCT | S4HANA | NA | NA | Calculation Period: Start Inclusive vs. End Inclusive | From DCT Field Calculation Period: Start Inclusive vs. End Inclusive |
| NA | NA | NA | CONSTRUCT | S4HANA | VTBFHA | WGSCHFT | Transaction Currency | From DCT Field WGSCHFT |
| NA | NA | NA | CONSTRUCT | S4HANA | VTB_ASGN_LIMIT | LIMIT_DATE | FTR Assignment Management: Limit Date | From DCT Field LIMIT_DATE |
| NA | NA | NA | CONSTRUCT | S4HANA | VTB_ASGN_LIMIT | LIMIT_CHG_AMOUNT | FTR Assignment Management: Drawing Amount | From DCT Field LIMIT_CHG_AMOUNT |
| NA | NA | NA | CONSTRUCT | S4HANA | VTB_ASGN_LIMIT | LIMIT_CURRENCY | FTR Assignment Management: Limit Currency | From DCT Field LIMIT_CURRENCY |
| NA | NA | NA | CONSTRUCT | S4HANA | VTB_ASGN_LIMIT | LIMIT_POS_AMOUNT | FTR Assignment Management: Drawing Amount (BAPI) | From DCT Field LIMIT_POS_AMOUNT |
| NA | NA | NA | CONSTRUCT | S4HANA | VTBFINKO | SRHYTHM | Frequency | From DCT Field SRHYTHM |
| NA | NA | NA | CONSTRUCT | S4HANA | VTBFINKO | AMMRHY OR ATTRHY | Unit for Frequency | From DCT Field AMMRHY OR ATTRHY |
| NA | NA | NA | CONSTRUCT | S4HANA | VTBFHAPO | PKOND | Percentage rate for condition items | From DCT Field PKOND |
| NA | NA | NA | CONSTRUCT | S4HANA | NA | NA | Calculation method for first period of condition item | From DCT Field Calculation method for first period of condition item |
| NA | NA | NA | CONSTRUCT | S4HANA | NA | NA | Calculation method for last period of condition item | From DCT Field Calculation method for last period of condition item |
| NA | NA | NA | CONSTRUCT | S4HANA | NA | NA | Interest Calculation Method | From DCT Field Interest Calculation Method |
| NA | NA | NA | CONSTRUCT | S4HANA | VTBFHAPO | SKALIDWT | Interest Calendar | From DCT Field SKALIDWT |
| NA | NA | NA | CONSTRUCT | S4HANA | NA | NA | Update for Calculation/Due Date for Interest | From DCT Field Update for Calculation/Due Date for Interest |
| NA | NA | NA | CONSTRUCT | S4HANA | VTBFHAPO | DVALUT | Calculation Date | From DCT Field DVALUT |
| NA | NA | NA | CONSTRUCT | S4HANA | NA | NA | Inclusive Indicator for Calculation Date | From DCT Field Inclusive Indicator for Calculation Date |
| NA | NA | NA | CONSTRUCT | S4HANA | NA | NA | Month-End Indicator for Calculation Date | From DCT Field Month-End Indicator for Calculation Date |
| NA | NA | NA | CONSTRUCT | S4HANA | VTBFINKO | SVWERK | Working Day Shift for Calculation Day | From DCT Field SVWERK |
| NA | NA | NA | CONSTRUCT | S4HANA | VTBFINKO | DFAELL | Due date | From DCT Field DFAELL |
| NA | NA | NA | CONSTRUCT | S4HANA | NA | NA | Month-End Indicator for Due Date | From DCT Field Month-End Indicator for Due Date |
| NA | NA | NA | CONSTRUCT | S4HANA | VTBFINKO | SFWERK | Working Day Shift for Due Date | From DCT Field SFWERK |
| NA | NA | NA | CONSTRUCT | S4HANA | NA | NA | Shift Due Date Back to End of Term | From DCT Field Shift Due Date Back to End of Term |
Transformation Mapping
| Mapping Table Name | Mapping Table Description |
|---|---|
Transformation Dependencies
List the steps that need to occur before transformation can commence| Item # | Step Description | Team Responsible |
|---|---|---|
Pre-Load Validation
Project Team
Completeness
| Task | Action |
|---|---|
Accuracy
| Task | Action |
|---|---|
Business
Completeness
| Task | Action |
|---|---|
Accuracy
| Task | Action |
|---|---|
Load
The load process includes:
- Execute the automated data load into target system using load tool or product the load file if the load must be done manually
- Once the data is loaded to the target system, it will be extracted and prepared for Post Load Data Validation
Load Run Sheet
| Item # | Step Description | Team Responsible |
|---|---|---|
Load Phase and Dependencies
Configuration
| Item # | Configuration Item |
|---|---|
Conversion Objects
| Object # | Preceding Object Conversion Approach |
|---|---|
| list the exact title of the conversion object of only the immediate predecessor – this will then confirm the DDD (Data Dependency Diagram) | |
Error Handling
| Error Type | Error Description | Action Taken |
|---|---|---|
Post-Load Validation
Project Team
Completeness
| Task | Action |
|---|---|
Accuracy
| Task | Action |
|---|---|
Business
Completeness
| Task | Action |
|---|---|
Accuracy
| Task | Action |
|---|---|
Key Assumptions
- Master Data Standard is up to date as on the date of documenting this conversion approach and data load.
- is in scope based on data design and any exception requested by business.