Parameter | Reference | Type | Length | Default | Optional | Text |
---|---|---|---|---|---|---|
IV_CLEARED_ITEMS | XFELD | C | 1 | 'X' | X | Character Field Length 1 |
IV_ONLY_INVOICES | XFELD | C | 1 | X | Character Field Length 1 | |
IV_OPEN_ITEMS | XFELD | C | 1 | 'X' | X | Character Field Length 1 |
IV_ORGTYPE | EBPP_ORG1T_PAY | C | 2 | '01' | X | Type of Organization |
IV_PARTNERKEY | BUSPA_KEY | C | 12 | X | Reference to the Business Partner | |
IV_PARTNERTYPE | BUSPA_TYPE | C | 2 | '12' | X | Business Partner Category |
IV_PAYMENT_DATE_HIGH | DATUM | D | 8 | '99990920' | X | Date |
IV_PAYMENT_DATE_LOW | DATUM | D | 8 | '19700101' | X | Date |
IV_PAYMENT_ID | BELNR_D | C | 10 | X | Accounting Document Number | |
IV_PAYMENT_TYPE | EBPP_PAYTY | C | 3 | X | Electronic Bill Presentment and Payment: Type of Payment | |
IV_SALES_ORG | CHAR14 | C | 14 | X | Text field length 14 | |
IV_SELECT_FOR_PAYMENTS | XFELD | C | 1 | X | Character Field Length 1 |
Parameter | Reference | Type | Length | Text |
---|---|---|---|---|
E_RETURNCODE | SYST-SUBRC | I | 4 | Return Value of ABAP Statements |
RETURN | BAPIRET1 | u | 470 | Return Parameter |
Parameter | Reference | Length | Optional | Text |
---|---|---|---|---|
T_MESSAGES | BAPIRET2 | 548 | Biller Direct: Messages | |
T_MYPAYMENTS | WEC_EBPP_MYPAYMENTS | 1228 | Biller Direct: My Payments | |
T_PAYMENT_CREDIT_DATA | WECT_PAYMENT_DATA | 1245 | WEC Payment Data | |
T_PAYMENT_INVOICE_DATA | WECT_PAYMENT_DATA | 1245 | WEC Payment Data |
Exception | Text |
---|---|
ACCOUNT_LOCKED | Account is locked |
ACCOUNT_MISSING | Account is not defined |
Functionality Further information
Payments data resides in t_mypayments. It contains the reference id ofthe payment and invoice assignment, but does not contain Payment ID. Inthe UI we also need to display the Payment ID. So fetch the payment IDfirst and form the complete payment table that needs to be displayed inthe UI. Payment ID is fetched from the table t_payallocation using the referenceid in t_mypayments. Other data related to payment are already present int_mypayments. Using the fetched Payment ID and the Payment data int_mypayments, form another table say x_tab, which would contain thecomplete payment details to be displayed in UI. The logic is similar as when Payment ID is not provided. In this caseprovided Payment ID along with the reference id from the tablet_mypayments is being matched with the Payment ID and the reference Idin the table t_payallocation. The proper payment record is then created. Invoices and Credit Memos are fetched in the table t_items andt_invoices. This is in continuation with the answers of the above questions. Fromt_payallocation we will have invid and linct. Using invid and linct readthe data from t_invoices from where we will fetch belnr,gjahr, buzei andbukrs. Using belnr,gjahr,buzei and bukrs data is being read fromt_items. Invoices and CreditMemos are differentiated using shkzg fromt_item. Value H for the field shkzg implies credit memo and S impliesinvoices. Currently passing values via following import parameter does not effectthe results, since these parameters are not being used internally by thecalled program WEC_APAR_EBPP_GET_DATA. ,,IV_PAYMENT_TYPE ,,IV_SELECT_FOR_PAYMENTS ,,IV_ONLY_INVOICES However these import parameters can be used for future enhancements tothe results. |