SAP /FSCAA/BAPI_SO_CREATE_PREP Function Module for Prepare Standing Order for change
/FSCAA/BAPI_SO_CREATE_PREP is a standard /fscaa/bapi so create prep SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Prepare Standing Order for change 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 /fscaa/bapi so create prep FM, simply by entering the name /FSCAA/BAPI_SO_CREATE_PREP into the relevant SAP transaction such as SE37 or SE38.
Function Group: /FSCAA/SERVICES
Program Name: /FSCAA/SAPLSERVICES
Main Program: /FSCAA/SAPLSERVICES
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function /FSCAA/BAPI_SO_CREATE_PREP 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 '/FSCAA/BAPI_SO_CREATE_PREP'"Prepare Standing Order for change.
EXPORTING
* PI_TRANS_ID = "GUID im 'CHAR' Format in Großschreibung
PI_ACCOUNT_ID = "Account identification
IMPORTING
PE_TRANS_ID = "GUID im 'CHAR' Format in Großschreibung
PE_TAB_ALL_ATTRIBUTES = "Table of fieldattributes
PE_TAB_EXTENSION_ATTRIBUTES = "Table of fieldattributes
PE_STANDING_ORDER = "Standing Order
PE_PAYMENT_NOTES = "payment notes
PE_TAB_MESSAGES = "Returnparameter
PE_TAB_EXTENSIONS = "Table: Key value pairs for BAPI Extensions
PE_SUBRC = "Return value
IMPORTING Parameters details for /FSCAA/BAPI_SO_CREATE_PREP
PI_TRANS_ID - GUID im 'CHAR' Format in Großschreibung
Data type: GUID_32Optional: Yes
Call by Reference: No ( called with pass by value option)
PI_ACCOUNT_ID - Account identification
Data type: /FSCAA/ACCOUNT_IDOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for /FSCAA/BAPI_SO_CREATE_PREP
PE_TRANS_ID - GUID im 'CHAR' Format in Großschreibung
Data type: GUID_32Optional: No
Call by Reference: No ( called with pass by value option)
PE_TAB_ALL_ATTRIBUTES - Table of fieldattributes
Data type: /FSCAA/TAB_FIELD_ATTRIBUTESOptional: No
Call by Reference: No ( called with pass by value option)
PE_TAB_EXTENSION_ATTRIBUTES - Table of fieldattributes
Data type: /FSCAA/TAB_FIELD_ATTRIBUTESOptional: No
Call by Reference: No ( called with pass by value option)
PE_STANDING_ORDER - Standing Order
Data type: /FSCAA/STANDING_ORDEROptional: No
Call by Reference: No ( called with pass by value option)
PE_PAYMENT_NOTES - payment notes
Data type: STRINGOptional: No
Call by Reference: No ( called with pass by value option)
PE_TAB_MESSAGES - Returnparameter
Data type: BAPIRET2_TOptional: No
Call by Reference: No ( called with pass by value option)
PE_TAB_EXTENSIONS - Table: Key value pairs for BAPI Extensions
Data type: /FSCAA/TAB_EXTENSIONSOptional: No
Call by Reference: No ( called with pass by value option)
PE_SUBRC - Return value
Data type: SYSUBRCOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for /FSCAA/BAPI_SO_CREATE_PREP 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_pe_trans_id | TYPE GUID_32, " | |||
| lv_pi_trans_id | TYPE GUID_32, " | |||
| lv_pi_account_id | TYPE /FSCAA/ACCOUNT_ID, " | |||
| lv_pe_tab_all_attributes | TYPE /FSCAA/TAB_FIELD_ATTRIBUTES, " | |||
| lv_pe_tab_extension_attributes | TYPE /FSCAA/TAB_FIELD_ATTRIBUTES, " | |||
| lv_pe_standing_order | TYPE /FSCAA/STANDING_ORDER, " | |||
| lv_pe_payment_notes | TYPE STRING, " | |||
| lv_pe_tab_messages | TYPE BAPIRET2_T, " | |||
| lv_pe_tab_extensions | TYPE /FSCAA/TAB_EXTENSIONS, " | |||
| lv_pe_subrc | TYPE SYSUBRC. " |
|   CALL FUNCTION '/FSCAA/BAPI_SO_CREATE_PREP' "Prepare Standing Order for change |
| EXPORTING | ||
| PI_TRANS_ID | = lv_pi_trans_id | |
| PI_ACCOUNT_ID | = lv_pi_account_id | |
| IMPORTING | ||
| PE_TRANS_ID | = lv_pe_trans_id | |
| PE_TAB_ALL_ATTRIBUTES | = lv_pe_tab_all_attributes | |
| PE_TAB_EXTENSION_ATTRIBUTES | = lv_pe_tab_extension_attributes | |
| PE_STANDING_ORDER | = lv_pe_standing_order | |
| PE_PAYMENT_NOTES | = lv_pe_payment_notes | |
| PE_TAB_MESSAGES | = lv_pe_tab_messages | |
| PE_TAB_EXTENSIONS | = lv_pe_tab_extensions | |
| PE_SUBRC | = lv_pe_subrc | |
| . " /FSCAA/BAPI_SO_CREATE_PREP | ||
ABAP code using 7.40 inline data declarations to call FM /FSCAA/BAPI_SO_CREATE_PREP
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