SAP ISMAM_ORDER_BDS_STATUS_MAINT Function Module for IS-M/AM: Maintain Billing Dataset Status
ISMAM_ORDER_BDS_STATUS_MAINT is a standard ismam order bds status maint SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for IS-M/AM: Maintain Billing Dataset Status 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 ismam order bds status maint FM, simply by entering the name ISMAM_ORDER_BDS_STATUS_MAINT into the relevant SAP transaction such as SE37 or SE38.
Function Group: JHA12
Program Name: SAPLJHA12
Main Program: SAPLJHA12
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISMAM_ORDER_BDS_STATUS_MAINT 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 'ISMAM_ORDER_BDS_STATUS_MAINT'"IS-M/AM: Maintain Billing Dataset Status.
EXPORTING
PS_RJHAGAX = "
CHANGING
PS_RJHAGA = "IS-M/AM: Order-Publishing-Media Billing Dataset
IMPORTING Parameters details for ISMAM_ORDER_BDS_STATUS_MAINT
PS_RJHAGAX -
Data type: RJHAGAXOptional: No
Call by Reference: Yes
CHANGING Parameters details for ISMAM_ORDER_BDS_STATUS_MAINT
PS_RJHAGA - IS-M/AM: Order-Publishing-Media Billing Dataset
Data type: RJHAGAOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for ISMAM_ORDER_BDS_STATUS_MAINT 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_ps_rjhaga | TYPE RJHAGA, " | |||
| lv_ps_rjhagax | TYPE RJHAGAX. " |
|   CALL FUNCTION 'ISMAM_ORDER_BDS_STATUS_MAINT' "IS-M/AM: Maintain Billing Dataset Status |
| EXPORTING | ||
| PS_RJHAGAX | = lv_ps_rjhagax | |
| CHANGING | ||
| PS_RJHAGA | = lv_ps_rjhaga | |
| . " ISMAM_ORDER_BDS_STATUS_MAINT | ||
ABAP code using 7.40 inline data declarations to call FM ISMAM_ORDER_BDS_STATUS_MAINT
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.Search for further information about these or an SAP related objects