SAP PFM_PAP_CREATE Function Module for Create PAP using RFC









PFM_PAP_CREATE is a standard pfm pap create SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Create PAP using RFC 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 pfm pap create FM, simply by entering the name PFM_PAP_CREATE into the relevant SAP transaction such as SE37 or SE38.

Function Group: PFM_PAP_RFC
Program Name: SAPLPFM_PAP_RFC
Main Program: SAPLPFM_PAP_RFC
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function PFM_PAP_CREATE 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 'PFM_PAP_CREATE'"Create PAP using RFC
  EXPORTING
   COMPANY_CODE =  "Company Code
   PAP_DATE =  "Posting Date in the Document
   PAYMENT_TYPE =  "Payment Type
*  HOUSE_BANK =  "Short Key for a House Bank
*  ACCOUNT_ID =  "ID for Account Details
   DOCUMENTS =  "Document List
*  DOCUMENT_TEXT =  "Document Text

 IMPORTING
   PAP_NUMBER =  "Payment authorization
   RETURN =  "Table with BAPI Return Information

EXCEPTIONS
   NO_RFC_AUTHORIZATION = 1
.



IMPORTING Parameters details for PFM_PAP_CREATE

COMPANY_CODE - Company Code

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

PAP_DATE - Posting Date in the Document

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

PAYMENT_TYPE - Payment Type

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

HOUSE_BANK - Short Key for a House Bank

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

ACCOUNT_ID - ID for Account Details

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

DOCUMENTS - Document List

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

DOCUMENT_TEXT - Document Text

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

EXPORTING Parameters details for PFM_PAP_CREATE

PAP_NUMBER - Payment authorization

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

RETURN - Table with BAPI Return Information

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

EXCEPTIONS details

NO_RFC_AUTHORIZATION - No Authorization

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for PFM_PAP_CREATE 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_pap_number  TYPE PFM_12DOCNO, "   
lv_company_code  TYPE BUKRS, "   
lv_no_rfc_authorization  TYPE BUKRS, "   
lv_return  TYPE BAPIRETTAB, "   
lv_pap_date  TYPE BUDAT, "   
lv_payment_type  TYPE PFM_PAYMENT_TYPE, "   
lv_house_bank  TYPE HBKID, "   
lv_account_id  TYPE HKTID, "   
lv_documents  TYPE FAGL_T_BELNR_LIST, "   
lv_document_text  TYPE PFM_DOC_TEXT. "   

  CALL FUNCTION 'PFM_PAP_CREATE'  "Create PAP using RFC
    EXPORTING
         COMPANY_CODE = lv_company_code
         PAP_DATE = lv_pap_date
         PAYMENT_TYPE = lv_payment_type
         HOUSE_BANK = lv_house_bank
         ACCOUNT_ID = lv_account_id
         DOCUMENTS = lv_documents
         DOCUMENT_TEXT = lv_document_text
    IMPORTING
         PAP_NUMBER = lv_pap_number
         RETURN = lv_return
    EXCEPTIONS
        NO_RFC_AUTHORIZATION = 1
. " PFM_PAP_CREATE




ABAP code using 7.40 inline data declarations to call FM PFM_PAP_CREATE

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



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!