SAP PSCS_GET_ORDCSH Function Module for NOTRANSL: Datenextraktion Infosource: 'Zahlungen Aufträge'









PSCS_GET_ORDCSH is a standard pscs get ordcsh 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: Datenextraktion Infosource: 'Zahlungen Aufträge' 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 pscs get ordcsh FM, simply by entering the name PSCS_GET_ORDCSH into the relevant SAP transaction such as SE37 or SE38.

Function Group: PSCS
Program Name: SAPLPSCS
Main Program: SAPLPSCS
Appliation area: K
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function PSCS_GET_ORDCSH 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 'PSCS_GET_ORDCSH'"NOTRANSL: Datenextraktion Infosource: 'Zahlungen Aufträge'
EXPORTING
* I_ISOURCE = "
I_REQUNR = "
* I_MAXSIZE = 1000 "
* I_INITFLAG = "
* I_UPDMODE = "

TABLES
* I_T_SELECT = "
* I_T_FIELDS = "
* E_T_ICORDCSH = "Info Source: Orders, Payments

EXCEPTIONS
NO_MORE_DATA = 1 ERROR_PASSED_TO_MESS_HANDLER = 2
.



IMPORTING Parameters details for PSCS_GET_ORDCSH

I_ISOURCE -

Data type: SBIWA_S_INTERFACE-ISOURCE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_REQUNR -

Data type: SBIWA_S_INTERFACE-REQUNR
Optional: No
Call by Reference: No ( called with pass by value option)

I_MAXSIZE -

Data type: SBIWA_S_INTERFACE-MAXSIZE
Default: 1000
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_INITFLAG -

Data type: SBIWA_S_INTERFACE-INITFLAG
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_UPDMODE -

Data type: SBIWA_S_INTERFACE-UPDMODE
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for PSCS_GET_ORDCSH

I_T_SELECT -

Data type: SBIWA_T_SELECT
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_T_FIELDS -

Data type: SBIWA_T_FIELDS
Optional: Yes
Call by Reference: No ( called with pass by value option)

E_T_ICORDCSH - Info Source: Orders, Payments

Data type: ICORDCSH
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

NO_MORE_DATA -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

ERROR_PASSED_TO_MESS_HANDLER -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for PSCS_GET_ORDCSH 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_i_isource  TYPE SBIWA_S_INTERFACE-ISOURCE, "   
lt_i_t_select  TYPE STANDARD TABLE OF SBIWA_T_SELECT, "   
lv_no_more_data  TYPE SBIWA_T_SELECT, "   
lv_i_requnr  TYPE SBIWA_S_INTERFACE-REQUNR, "   
lt_i_t_fields  TYPE STANDARD TABLE OF SBIWA_T_FIELDS, "   
lv_error_passed_to_mess_handler  TYPE SBIWA_T_FIELDS, "   
lv_i_maxsize  TYPE SBIWA_S_INTERFACE-MAXSIZE, "   1000
lt_e_t_icordcsh  TYPE STANDARD TABLE OF ICORDCSH, "   
lv_i_initflag  TYPE SBIWA_S_INTERFACE-INITFLAG, "   
lv_i_updmode  TYPE SBIWA_S_INTERFACE-UPDMODE. "   

  CALL FUNCTION 'PSCS_GET_ORDCSH'  "NOTRANSL: Datenextraktion Infosource: 'Zahlungen Aufträge'
    EXPORTING
         I_ISOURCE = lv_i_isource
         I_REQUNR = lv_i_requnr
         I_MAXSIZE = lv_i_maxsize
         I_INITFLAG = lv_i_initflag
         I_UPDMODE = lv_i_updmode
    TABLES
         I_T_SELECT = lt_i_t_select
         I_T_FIELDS = lt_i_t_fields
         E_T_ICORDCSH = lt_e_t_icordcsh
    EXCEPTIONS
        NO_MORE_DATA = 1
        ERROR_PASSED_TO_MESS_HANDLER = 2
. " PSCS_GET_ORDCSH




ABAP code using 7.40 inline data declarations to call FM PSCS_GET_ORDCSH

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 ISOURCE FROM SBIWA_S_INTERFACE INTO @DATA(ld_i_isource).
 
 
 
"SELECT single REQUNR FROM SBIWA_S_INTERFACE INTO @DATA(ld_i_requnr).
 
 
 
"SELECT single MAXSIZE FROM SBIWA_S_INTERFACE INTO @DATA(ld_i_maxsize).
DATA(ld_i_maxsize) = 1000.
 
 
"SELECT single INITFLAG FROM SBIWA_S_INTERFACE INTO @DATA(ld_i_initflag).
 
"SELECT single UPDMODE FROM SBIWA_S_INTERFACE INTO @DATA(ld_i_updmode).
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!