SAP Function Modules
ISH_CALL_RULE_SERVICES_BILLING SAP Function module
ISH_CALL_RULE_SERVICES_BILLING 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 ISH_CALL_RULE_SERVICES_BILLING into the relevant SAP transaction such as SE37 or SE80.
Associated Function Group:
NBTG
Released Date:
Not Released
Processing type: Normal fucntion module
Pattern for FM ISH_CALL_RULE_SERVICES_BILLING - ISH CALL RULE SERVICES BILLING
CALL FUNCTION 'ISH_CALL_RULE_SERVICES_BILLING' "
EXPORTING
einri = " tn01-einri Institution
* event = SPACE " tn02e-event
infal = " nfal Case
inpat = " npat Patient
* messages_collect = 'X' " npdok-xfeld Save or save and display services
* messages_show = ' ' " npdok-xfeld Rule type
rgart = " tnt3-rgart Rule type
* stichtag = SY-DATUM " sy-datum Check Date
* aktion = ' ' " tnrs2-aktion
IMPORTING
errors = " No. messages with type E
warnings = " No. message with type W
TABLES
* ernlsr = " rnlsr Table containing services which caused E messages
inlei = " nlei Table with services to be checked
ivnbew = " vnbew Movements
* ernlrf = " rnlrf
EXCEPTIONS
ERROR = 1 " Internal error
. " ISH_CALL_RULE_SERVICES_BILLING
ABAP code example for Function Module ISH_CALL_RULE_SERVICES_BILLING
The ABAP code below is a full code listing to execute function module ISH_CALL_RULE_SERVICES_BILLING 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).
| ld_errors | TYPE STRING , |
| ld_warnings | TYPE STRING , |
| it_ernlsr | TYPE STANDARD TABLE OF RNLSR,"TABLES PARAM |
| wa_ernlsr | LIKE LINE OF it_ernlsr , |
| it_inlei | TYPE STANDARD TABLE OF NLEI,"TABLES PARAM |
| wa_inlei | LIKE LINE OF it_inlei , |
| it_ivnbew | TYPE STANDARD TABLE OF VNBEW,"TABLES PARAM |
| wa_ivnbew | LIKE LINE OF it_ivnbew , |
| it_ernlrf | TYPE STANDARD TABLE OF RNLRF,"TABLES PARAM |
| wa_ernlrf | LIKE LINE OF it_ernlrf . |
SELECT single EINRI
FROM TN01
INTO @DATA(ld_einri).
SELECT single EVENT
FROM TN02E
INTO @DATA(ld_event).
DATA(ld_infal) = 'Check type of data required'.
DATA(ld_inpat) = 'Check type of data required'.
DATA(ld_messages_collect) = some text here
DATA(ld_messages_show) = some text here
SELECT single RGART
FROM TNT3
INTO @DATA(ld_rgart).
DATA(ld_stichtag) = '20210129'.
SELECT single AKTION
FROM TNRS2
INTO @DATA(ld_aktion).
"populate fields of struture and append to itab
append wa_ernlsr to it_ernlsr.
"populate fields of struture and append to itab
append wa_inlei to it_inlei.
"populate fields of struture and append to itab
append wa_ivnbew to it_ivnbew.
"populate fields of struture and append to itab
append wa_ernlrf to it_ernlrf. . CALL FUNCTION 'ISH_CALL_RULE_SERVICES_BILLING' EXPORTING einri = ld_einri * event = ld_event infal = ld_infal inpat = ld_inpat * messages_collect = ld_messages_collect * messages_show = ld_messages_show rgart = ld_rgart * stichtag = ld_stichtag * aktion = ld_aktion IMPORTING errors = ld_errors warnings = ld_warnings TABLES * ernlsr = it_ernlsr inlei = it_inlei ivnbew = it_ivnbew * ernlrf = it_ernlrf EXCEPTIONS ERROR = 1 . " ISH_CALL_RULE_SERVICES_BILLING
IF SY-SUBRC EQ 0. "All OK ELSEIF SY-SUBRC EQ 1. "Exception "Add code for exception here 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_errors | TYPE STRING , |
| ld_einri | TYPE TN01-EINRI , |
| it_ernlsr | TYPE STANDARD TABLE OF RNLSR , |
| wa_ernlsr | LIKE LINE OF it_ernlsr, |
| ld_warnings | TYPE STRING , |
| ld_event | TYPE TN02E-EVENT , |
| it_inlei | TYPE STANDARD TABLE OF NLEI , |
| wa_inlei | LIKE LINE OF it_inlei, |
| ld_infal | TYPE NFAL , |
| it_ivnbew | TYPE STANDARD TABLE OF VNBEW , |
| wa_ivnbew | LIKE LINE OF it_ivnbew, |
| ld_inpat | TYPE NPAT , |
| it_ernlrf | TYPE STANDARD TABLE OF RNLRF , |
| wa_ernlrf | LIKE LINE OF it_ernlrf, |
| ld_messages_collect | TYPE NPDOK-XFELD , |
| ld_messages_show | TYPE NPDOK-XFELD , |
| ld_rgart | TYPE TNT3-RGART , |
| ld_stichtag | TYPE SY-DATUM , |
| ld_aktion | TYPE TNRS2-AKTION . |
SELECT single EINRI
FROM TN01
INTO ld_einri.
"populate fields of struture and append to itab
append wa_ernlsr to it_ernlsr.
SELECT single EVENT
FROM TN02E
INTO ld_event.
"populate fields of struture and append to itab
append wa_inlei to it_inlei.
ld_infal = '20210129'.
"populate fields of struture and append to itab
append wa_ivnbew to it_ivnbew.
ld_inpat = '20210129'.
"populate fields of struture and append to itab
append wa_ernlrf to it_ernlrf.
ld_messages_collect = some text here
ld_messages_show = some text here
SELECT single RGART
FROM TNT3
INTO ld_rgart.
ld_stichtag = '20210129'.
SELECT single AKTION
FROM TNRS2
INTO ld_aktion.
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 ISH_CALL_RULE_SERVICES_BILLING or its description.