xFlow Interface
Alternative payee
In SAP, a general alternative payee and a company-code-dependent alternative payee can be entered in the vendor master data. The general alternative payee applies to the vendor in all company codes. If both types of alternative payees are present, the company-code-dependent alternative payee has priority.
In the xFlow Interface Monitor, display of the bank account number now includes both the company-code-dependent alternative payee and that from the vendor master data.
The alternative payee in the data extraction step
If a partner bank type is entered in xFlow Interface, it is forwarded to the SAP document, where it is used to identify the bank account number.
If a partner bank type has not been entered in xFlow Interface, the bank account number from the SAP vendor entry will be identified in the SAP document.
For this, the alternative payee is now read from vendor master data.
If an alternative payee is maintained in the vendor master data, only partner bank types of this alternative payee are allowed in xFlow Interface. As a result of this change, behavior in xFlow Interface is now the same as that in the SAP document.
F4 help for the field "partner bank type"
In the header data of the validation screen, F4 help for the field Partner Bank Type now behaves as follows:
If neither a company-code-dependent alternative payee nor a general alternative payee is maintained, the bank account numbers of the vendor will be available for selection.
If a company-code-dependent alternative payee is maintained, its bank account numbers will be available for selection.
If a general alternative payee is maintained, its bank account numbers will be available for selection.
Terms of payment with key date
For certain terms of payment with key date (the fields T051-ZSTG1, T051-ZSTG2 are filled or the field T051-ZSTG3 is filled), the number of days for the cash discount period in SAP previously only changed when entering the 4-digit abbreviation. Now, making changes to the baseline date also changes it.
This modification made by SAP to payment details is now also included in the xFlow Invoice Monitor.
ISR procedure allowed
In /WMD/CL_FP_IV_UTIL → CHECK_ESR_ACTIVATION, the only check performed concerned whether the payment methods E, H or O were activated for ISR in a company code.
Now, all payment methods from the table T042Z are checked.
Starting an XI workflow from background processing
The procedure for starting a workflow from background processing in the program /WMD/FP_INVB has been revised. Now, with the proper customizing, it will be launched even if a notification has been returned from the INIT methods of the model classes.
Identifying the vendor
If no vendor numbers are transferred when the module /WMD/FP_IMPORT is invoked, an attempt is now made to identify the vendor based on the company code, the bank information, and the tax ID.
This data must be transferred as header data to the fields IBAN, STCEG, STCD1, BANKN, BANKL, and BANKS. Then the vendor is identified in the class /WMD/CL_FP_IV_TRANSFER_IF_DOC in the method VENDOR_FROM_BANK_OR_TAXID( ).
Additional queries
For later use in the xSuite Cloud, new queries have been added to the group /WMD/QUERY:
Query | Description |
|---|---|
MD_CCTR_365 | Cost centers |
MD_CC_365 | Company codes |
MD_CUST_365 | Customer master data |
MD_GLAC_365 | G/L accounts |
MD_PO_365 | PO dates |
MD_VENDOR_365 | Vendor master data |
Automatic tax calculation for mixed debit/credit indicators
If different debit/credit indicators appear in a single document, a check is no longer made for negative amounts when transmitting them to the SAP transaction. As a result, continued processing is no longer prevented. The amount is then calculated within the SAP transaction.