SAP BAPI_FTR_DAN_GIVENOTICE Function Module for Give Notice on Deposit at Notice
BAPI_FTR_DAN_GIVENOTICE is a standard bapi ftr dan givenotice SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Give Notice on Deposit at Notice processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.
See here to view full function module documentation and code listing for bapi ftr dan givenotice FM, simply by entering the name BAPI_FTR_DAN_GIVENOTICE into the relevant SAP transaction such as SE37 or SE38.
Function Group: FTR_BAPI_DAN
Program Name: SAPLFTR_BAPI_DAN
Main Program: SAPLFTR_BAPI_DAN
Appliation area:
Release date: 21-Sep-2000
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BAPI_FTR_DAN_GIVENOTICE pattern details
In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.CALL FUNCTION 'BAPI_FTR_DAN_GIVENOTICE'"Give Notice on Deposit at Notice.
EXPORTING
ENDTERM = "Term End
COMPANYCODE = "Company Code
FINANCIALTRANSACTION = "Financial Transaction
* TESTRUN = ' ' "Switch to Simulation Mode for Write BAPIs
* NOTICE_DATE = "Contract conclusion date
* TRADER = "Traders
* EXTERNAL_REFERENCE = "External Reference
* CONTACT_PERSON = "Contact Person
* NOTICE_TIME = "Time of contract conclusion
IMPORTING
RETURNFINANCIALTRANSACTION = "Financial Transaction
RETURNCOMPANYCODE = "Company Code
TABLES
* RETURN = "Return Parameters
IMPORTING Parameters details for BAPI_FTR_DAN_GIVENOTICE
ENDTERM - Term End
Data type: BAPI_FTR_CHANGE_DAN-END_TERMOptional: No
Call by Reference: No ( called with pass by value option)
COMPANYCODE - Company Code
Data type: BAPI2042-COMPANY_CODEOptional: No
Call by Reference: No ( called with pass by value option)
FINANCIALTRANSACTION - Financial Transaction
Data type: BAPI2042-TRANSACTIONOptional: No
Call by Reference: No ( called with pass by value option)
TESTRUN - Switch to Simulation Mode for Write BAPIs
Data type: BAPI2042-TESTRUNDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
NOTICE_DATE - Contract conclusion date
Data type: BAPI_FTR_CHANGE-CONTRACT_DATEOptional: Yes
Call by Reference: No ( called with pass by value option)
TRADER - Traders
Data type: BAPI_FTR_CHANGE-TRADEROptional: Yes
Call by Reference: No ( called with pass by value option)
EXTERNAL_REFERENCE - External Reference
Data type: BAPI_FTR_CHANGE-EXTERNAL_REFERENCEOptional: Yes
Call by Reference: No ( called with pass by value option)
CONTACT_PERSON - Contact Person
Data type: BAPI_FTR_CHANGE-CONTACT_PERSONOptional: Yes
Call by Reference: No ( called with pass by value option)
NOTICE_TIME - Time of contract conclusion
Data type: BAPI_FTR_CHANGE-CONTRACT_TIMEOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BAPI_FTR_DAN_GIVENOTICE
RETURNFINANCIALTRANSACTION - Financial Transaction
Data type: BAPI2042-TRANSACTIONOptional: No
Call by Reference: No ( called with pass by value option)
RETURNCOMPANYCODE - Company Code
Data type: BAPI2042-COMPANY_CODEOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BAPI_FTR_DAN_GIVENOTICE
RETURN - Return Parameters
Data type: BAPIRET2Optional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for BAPI_FTR_DAN_GIVENOTICE Function Module
The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the newer method of declaring data variables on the fly. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8), which i why i have stuck to the origianl for this example.| DATA: | ||||
| lt_return | TYPE STANDARD TABLE OF BAPIRET2, " | |||
| lv_endterm | TYPE BAPI_FTR_CHANGE_DAN-END_TERM, " | |||
| lv_returnfinancialtransaction | TYPE BAPI2042-TRANSACTION, " | |||
| lv_companycode | TYPE BAPI2042-COMPANY_CODE, " | |||
| lv_returncompanycode | TYPE BAPI2042-COMPANY_CODE, " | |||
| lv_financialtransaction | TYPE BAPI2042-TRANSACTION, " | |||
| lv_testrun | TYPE BAPI2042-TESTRUN, " SPACE | |||
| lv_notice_date | TYPE BAPI_FTR_CHANGE-CONTRACT_DATE, " | |||
| lv_trader | TYPE BAPI_FTR_CHANGE-TRADER, " | |||
| lv_external_reference | TYPE BAPI_FTR_CHANGE-EXTERNAL_REFERENCE, " | |||
| lv_contact_person | TYPE BAPI_FTR_CHANGE-CONTACT_PERSON, " | |||
| lv_notice_time | TYPE BAPI_FTR_CHANGE-CONTRACT_TIME. " |
|   CALL FUNCTION 'BAPI_FTR_DAN_GIVENOTICE' "Give Notice on Deposit at Notice |
| EXPORTING | ||
| ENDTERM | = lv_endterm | |
| COMPANYCODE | = lv_companycode | |
| FINANCIALTRANSACTION | = lv_financialtransaction | |
| TESTRUN | = lv_testrun | |
| NOTICE_DATE | = lv_notice_date | |
| TRADER | = lv_trader | |
| EXTERNAL_REFERENCE | = lv_external_reference | |
| CONTACT_PERSON | = lv_contact_person | |
| NOTICE_TIME | = lv_notice_time | |
| IMPORTING | ||
| RETURNFINANCIALTRANSACTION | = lv_returnfinancialtransaction | |
| RETURNCOMPANYCODE | = lv_returncompanycode | |
| TABLES | ||
| RETURN | = lt_return | |
| . " BAPI_FTR_DAN_GIVENOTICE | ||
ABAP code using 7.40 inline data declarations to call FM BAPI_FTR_DAN_GIVENOTICE
The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.| "SELECT single END_TERM FROM BAPI_FTR_CHANGE_DAN INTO @DATA(ld_endterm). | ||||
| "SELECT single TRANSACTION FROM BAPI2042 INTO @DATA(ld_returnfinancialtransaction). | ||||
| "SELECT single COMPANY_CODE FROM BAPI2042 INTO @DATA(ld_companycode). | ||||
| "SELECT single COMPANY_CODE FROM BAPI2042 INTO @DATA(ld_returncompanycode). | ||||
| "SELECT single TRANSACTION FROM BAPI2042 INTO @DATA(ld_financialtransaction). | ||||
| "SELECT single TESTRUN FROM BAPI2042 INTO @DATA(ld_testrun). | ||||
| DATA(ld_testrun) | = ' '. | |||
| "SELECT single CONTRACT_DATE FROM BAPI_FTR_CHANGE INTO @DATA(ld_notice_date). | ||||
| "SELECT single TRADER FROM BAPI_FTR_CHANGE INTO @DATA(ld_trader). | ||||
| "SELECT single EXTERNAL_REFERENCE FROM BAPI_FTR_CHANGE INTO @DATA(ld_external_reference). | ||||
| "SELECT single CONTACT_PERSON FROM BAPI_FTR_CHANGE INTO @DATA(ld_contact_person). | ||||
| "SELECT single CONTRACT_TIME FROM BAPI_FTR_CHANGE INTO @DATA(ld_notice_time). | ||||
Search for further information about these or an SAP related objects