SAP STATUS_DETERMINE Function Module for What Status Does the Contract Acquire When You Save?
STATUS_DETERMINE is a standard status determine SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for What Status Does the Contract Acquire When You Save? 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 status determine FM, simply by entering the name STATUS_DETERMINE into the relevant SAP transaction such as SE37 or SE38.
Function Group: FV14
Program Name: SAPLFV14
Main Program: SAPLFV14
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function STATUS_DETERMINE 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 'STATUS_DETERMINE'"What Status Does the Contract Acquire When You Save?.
EXPORTING
BUSINESS_TYPE = "Transaction Type
COMPANY_CODE = "
OLD_STATUS = "Alter Status des Vertrages
* PICKUP_POSSIBLE = 'X' "Pichup erlaubt oder nicht
* POPUP_TITLE = ' ' "Transaction Type
TRANSACTION_CODE = "Vorgang / Transaktion
* RELEASE_FLAG = "
* I_VDARL = "Loans
* I_FVD_LOAN_MD = "BAdI Interface IF_EX_FVD_LOAN_MASTERDATA
IMPORTING
TZC37 = "Gueltiger Eintrag aus TZC37
EXCEPTIONS
PICKUP_CANCELLED = 1 STATUS_IMPOSSIBLE = 2 STATUS_NOT_UNIQUE = 3 TZC37_NOT_VALID = 4 TZM37_NOT_VALID = 5 TZV37_NOT_VALID = 6
IMPORTING Parameters details for STATUS_DETERMINE
BUSINESS_TYPE - Transaction Type
Data type: TZC37-GSARTOptional: No
Call by Reference: No ( called with pass by value option)
COMPANY_CODE -
Data type: T001-BUKRSOptional: No
Call by Reference: No ( called with pass by value option)
OLD_STATUS - Alter Status des Vertrages
Data type: TZC37-STATUOptional: No
Call by Reference: No ( called with pass by value option)
PICKUP_POSSIBLE - Pichup erlaubt oder nicht
Data type:Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
POPUP_TITLE - Transaction Type
Data type:Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
TRANSACTION_CODE - Vorgang / Transaktion
Data type: TZV37-VCODEOptional: No
Call by Reference: No ( called with pass by value option)
RELEASE_FLAG -
Data type: VDARL-SFGKZOptional: Yes
Call by Reference: Yes
I_VDARL - Loans
Data type: VDARLOptional: Yes
Call by Reference: Yes
I_FVD_LOAN_MD - BAdI Interface IF_EX_FVD_LOAN_MASTERDATA
Data type: IF_EX_FVD_LOAN_MASTERDATAOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for STATUS_DETERMINE
TZC37 - Gueltiger Eintrag aus TZC37
Data type: TZC37Optional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
PICKUP_CANCELLED - Pickup wurde abgebrochen
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
STATUS_IMPOSSIBLE - Status ist nicht moeglich, da Ergebnismenge = 0
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
STATUS_NOT_UNIQUE - Status ist nicht eindeutig
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
TZC37_NOT_VALID - Eintrag in TZC37 fehlt
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
TZM37_NOT_VALID - Eintrag in TZM37 fehlt
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
TZV37_NOT_VALID - Eintrag in TZV37 fehlt
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for STATUS_DETERMINE 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: | ||||
| lv_tzc37 | TYPE TZC37, " | |||
| lv_business_type | TYPE TZC37-GSART, " | |||
| lv_pickup_cancelled | TYPE TZC37, " | |||
| lv_company_code | TYPE T001-BUKRS, " | |||
| lv_status_impossible | TYPE T001, " | |||
| lv_old_status | TYPE TZC37-STATU, " | |||
| lv_status_not_unique | TYPE TZC37, " | |||
| lv_pickup_possible | TYPE TZC37, " 'X' | |||
| lv_tzc37_not_valid | TYPE TZC37, " | |||
| lv_popup_title | TYPE TZC37, " SPACE | |||
| lv_tzm37_not_valid | TYPE TZC37, " | |||
| lv_tzv37_not_valid | TYPE TZC37, " | |||
| lv_transaction_code | TYPE TZV37-VCODE, " | |||
| lv_release_flag | TYPE VDARL-SFGKZ, " | |||
| lv_i_vdarl | TYPE VDARL, " | |||
| lv_i_fvd_loan_md | TYPE IF_EX_FVD_LOAN_MASTERDATA. " |
|   CALL FUNCTION 'STATUS_DETERMINE' "What Status Does the Contract Acquire When You Save? |
| EXPORTING | ||
| BUSINESS_TYPE | = lv_business_type | |
| COMPANY_CODE | = lv_company_code | |
| OLD_STATUS | = lv_old_status | |
| PICKUP_POSSIBLE | = lv_pickup_possible | |
| POPUP_TITLE | = lv_popup_title | |
| TRANSACTION_CODE | = lv_transaction_code | |
| RELEASE_FLAG | = lv_release_flag | |
| I_VDARL | = lv_i_vdarl | |
| I_FVD_LOAN_MD | = lv_i_fvd_loan_md | |
| IMPORTING | ||
| TZC37 | = lv_tzc37 | |
| EXCEPTIONS | ||
| PICKUP_CANCELLED = 1 | ||
| STATUS_IMPOSSIBLE = 2 | ||
| STATUS_NOT_UNIQUE = 3 | ||
| TZC37_NOT_VALID = 4 | ||
| TZM37_NOT_VALID = 5 | ||
| TZV37_NOT_VALID = 6 | ||
| . " STATUS_DETERMINE | ||
ABAP code using 7.40 inline data declarations to call FM STATUS_DETERMINE
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 GSART FROM TZC37 INTO @DATA(ld_business_type). | ||||
| "SELECT single BUKRS FROM T001 INTO @DATA(ld_company_code). | ||||
| "SELECT single STATU FROM TZC37 INTO @DATA(ld_old_status). | ||||
| DATA(ld_pickup_possible) | = 'X'. | |||
| DATA(ld_popup_title) | = ' '. | |||
| "SELECT single VCODE FROM TZV37 INTO @DATA(ld_transaction_code). | ||||
| "SELECT single SFGKZ FROM VDARL INTO @DATA(ld_release_flag). | ||||
Search for further information about these or an SAP related objects