SAP ME4S_CONTRACT_TYPE_WITH_SCHED Function Module for NOTRANSL: Decide whether schedule lines on the contract
ME4S_CONTRACT_TYPE_WITH_SCHED is a standard me4s contract type with sched SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Decide whether schedule lines on the contract 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 me4s contract type with sched FM, simply by entering the name ME4S_CONTRACT_TYPE_WITH_SCHED into the relevant SAP transaction such as SE37 or SE38.
Function Group: ME4S
Program Name: SAPLME4S
Main Program:
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ME4S_CONTRACT_TYPE_WITH_SCHED 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 'ME4S_CONTRACT_TYPE_WITH_SCHED'"NOTRANSL: Decide whether schedule lines on the contract.
EXPORTING
KTYPE = "Purchasing Document Type
IMPORTING
RETURN = "ABAP System Field: Return Code of ABAP Statements
IMPORTING Parameters details for ME4S_CONTRACT_TYPE_WITH_SCHED
KTYPE - Purchasing Document Type
Data type: T161-BSARTOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for ME4S_CONTRACT_TYPE_WITH_SCHED
RETURN - ABAP System Field: Return Code of ABAP Statements
Data type: SY-SUBRCOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ME4S_CONTRACT_TYPE_WITH_SCHED 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_ktype | TYPE T161-BSART, " | |||
| lv_return | TYPE SY-SUBRC. " |
|   CALL FUNCTION 'ME4S_CONTRACT_TYPE_WITH_SCHED' "NOTRANSL: Decide whether schedule lines on the contract |
| EXPORTING | ||
| KTYPE | = lv_ktype | |
| IMPORTING | ||
| RETURN | = lv_return | |
| . " ME4S_CONTRACT_TYPE_WITH_SCHED | ||
ABAP code using 7.40 inline data declarations to call FM ME4S_CONTRACT_TYPE_WITH_SCHED
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 BSART FROM T161 INTO @DATA(ld_ktype). | ||||
| "SELECT single SUBRC FROM SY INTO @DATA(ld_return). | ||||
Search for further information about these or an SAP related objects