SAP Function Modules

comments icon Comments

JV_GET_DOCUMENTS_FOR_RELEASE SAP Function module - Get documents for holding into the next period







JV_GET_DOCUMENTS_FOR_RELEASE 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 JV_GET_DOCUMENTS_FOR_RELEASE into the relevant SAP transaction such as SE37 or SE80.

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


Pattern for FM JV_GET_DOCUMENTS_FOR_RELEASE - JV GET DOCUMENTS FOR RELEASE 





CALL FUNCTION 'JV_GET_DOCUMENTS_FOR_RELEASE' "Get documents for holding into the next period
  EXPORTING
    bukrs =                     " bukrs         Company code
    fper =                      " monat         Fiscal period
    fyear =                     " gjahr         Fiscal year
    bill_level =                " jv_invlvl     Joint Venture Invoice Level
  IMPORTING
    error_jvto2 =               " gjvbt_jvto2struc
    jvso2_process =             " gjvbt_jvso2
    jvso2_done =                " gjvbt_jvso2
    jvso2_outside =             " gjvbt_jvso2
  CHANGING
    thresholdlist =             " gjvbt_threshold
    .  "  JV_GET_DOCUMENTS_FOR_RELEASE

ABAP code example for Function Module JV_GET_DOCUMENTS_FOR_RELEASE





The ABAP code below is a full code listing to execute function module JV_GET_DOCUMENTS_FOR_RELEASE 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_error_jvto2    TYPE GJVBT_JVTO2STRUC
,
ld_jvso2_process    TYPE GJVBT_JVSO2
,
ld_jvso2_done    TYPE GJVBT_JVSO2
,
ld_jvso2_outside    TYPE GJVBT_JVSO2
.




DATA(ld_thresholdlist) = 'Check type of data required'.

DATA(ld_bukrs) = 'Check type of data required'.

DATA(ld_fper) = 'Check type of data required'.

DATA(ld_fyear) = 'Check type of data required'.

DATA(ld_bill_level) = 'Check type of data required'.
.

CALL FUNCTION 'JV_GET_DOCUMENTS_FOR_RELEASE'
  EXPORTING
    bukrs =                      ld_bukrs
    fper =                       ld_fper
    fyear =                      ld_fyear
    bill_level =                 ld_bill_level
  IMPORTING
    error_jvto2 =                ld_error_jvto2
    jvso2_process =              ld_jvso2_process
    jvso2_done =                 ld_jvso2_done
    jvso2_outside =              ld_jvso2_outside
  CHANGING
    thresholdlist =              ld_thresholdlist
    .  "  JV_GET_DOCUMENTS_FOR_RELEASE

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_thresholdlist  TYPE GJVBT_THRESHOLD ,
ld_error_jvto2  TYPE GJVBT_JVTO2STRUC ,
ld_bukrs  TYPE BUKRS ,
ld_jvso2_process  TYPE GJVBT_JVSO2 ,
ld_fper  TYPE MONAT ,
ld_jvso2_done  TYPE GJVBT_JVSO2 ,
ld_fyear  TYPE GJAHR ,
ld_jvso2_outside  TYPE GJVBT_JVSO2 ,
ld_bill_level  TYPE JV_INVLVL .




ld_thresholdlist = 'Check type of data required'.
ld_bukrs = 'Check type of data required'.
ld_fper = 'Check type of data required'.
ld_fyear = 'Check type of data required'.
ld_bill_level = 'Check type of data required'.

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 JV_GET_DOCUMENTS_FOR_RELEASE or its description.


   
 

JV_GET_DOCUMENTS_FOR_RELEASE - Get documents for holding into the next period
JV_GET_DOCUMENTS_FOR_HOLD - Get documents for holding into the next period
JV_GET_CURRENT_BILLING_AMOUNT - Get current amount to be billed in JVA
JV_GET_COST_OBJECTS_FOR_JV - Popup with all cost objects where a JV is assigned to
JV_GET_CC_ATTRIBUTES - Joint Venture Cost center attribute function module
JV_GET_BILLING_THRESHOLD - Get billing threshold