SAP Function Modules

CASH_FORECAST_DOC_SPLIT_POST SAP Function module







CASH_FORECAST_DOC_SPLIT_POST is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name CASH_FORECAST_DOC_SPLIT_POST into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: FDSPLIT
Released Date: Not Released
Processing type: Normal fucntion module
Normal function module settings


Pattern for FM CASH_FORECAST_DOC_SPLIT_POST - CASH FORECAST DOC SPLIT POST





CALL FUNCTION 'CASH_FORECAST_DOC_SPLIT_POST' "
  EXPORTING
    i_awtyp =                   " awtyp
    i_awref =                   " awref
    i_aworg =                   " aworg
    i_awsys =                   " awsys
*   i_x_in_update_task = 'X'    " t001-xfdis
*   i_x_docno_known = SPACE     " t001-xfdis
    .  "  CASH_FORECAST_DOC_SPLIT_POST

ABAP code example for Function Module CASH_FORECAST_DOC_SPLIT_POST





The ABAP code below is a full code listing to execute function module CASH_FORECAST_DOC_SPLIT_POST including all data declarations. The code uses 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 original method of declaring data variables up front. 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).


DATA(ld_i_awtyp) = 'Check type of data required'.
DATA(ld_i_awref) = 'Check type of data required'.
DATA(ld_i_aworg) = 'Check type of data required'.
DATA(ld_i_awsys) = '20210129'.

SELECT single XFDIS
FROM T001
INTO @DATA(ld_i_x_in_update_task).


SELECT single XFDIS
FROM T001
INTO @DATA(ld_i_x_docno_known).
. CALL FUNCTION 'CASH_FORECAST_DOC_SPLIT_POST' EXPORTING i_awtyp = ld_i_awtyp i_awref = ld_i_awref i_aworg = ld_i_aworg i_awsys = ld_i_awsys * i_x_in_update_task = ld_i_x_in_update_task * i_x_docno_known = ld_i_x_docno_known . " CASH_FORECAST_DOC_SPLIT_POST
IF SY-SUBRC EQ 0. "All OK ENDIF.







ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:
ld_i_awtyp  TYPE AWTYP ,
ld_i_awref  TYPE AWREF ,
ld_i_aworg  TYPE AWORG ,
ld_i_awsys  TYPE AWSYS ,
ld_i_x_in_update_task  TYPE T001-XFDIS ,
ld_i_x_docno_known  TYPE T001-XFDIS .

ld_i_awtyp = 'some text here'.
ld_i_awref = 'some text here'.
ld_i_aworg = 'some text here'.
ld_i_awsys = '20210129'.

SELECT single XFDIS
FROM T001
INTO ld_i_x_in_update_task.


SELECT single XFDIS
FROM T001
INTO ld_i_x_docno_known.

Contribute (Add Comments)

Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name CASH_FORECAST_DOC_SPLIT_POST or its description.