Beruflich Dokumente
Kultur Dokumente
Peter Faust
SAP AG 1997
SAP AG 1997
(collection)
- flexible instrument for financing (presentation)
SAP AG 1997
SAP AG 1997
SAP AG 1997
SAP AG 1997
The above mentioned payment method might be indicated in BSEG-ZLSCH in the customer item.
In Table T074 the special g/l indicator has to be defined as a BoE(under properties) and the link in between the reconciliation account of the customer and the reconciliation account to be used for booking the BoE. There would be an entry: d w BoE receivable
SAP AG 1997
SAP AG 1997
SAP AG 1997
SAP AG 1997
Report RFWOBL00 first creates the new remaining risks and then cancels the old risks.
RFWOBL00 has two parameters: 'remaining risk due by' which resets the old remaining risk postings and the 'days from table which is only used for selecting the new risks. It's not used with the cancelling of the old risks.
The risk items taken away are those whose due date is before the external defined date (p_bisdt). The goal of this functioning is to ensure a posting of a risk item and not take it away immediately.
As an option, noted items can also be posted for the existing residual risk. These noted items are, however, only posted if the BOE presentations are actually posted.
SAP AG 1997
SAP AG 1997
Special g/l indicators. There should be a special g/l indicator for remaining risk which under properties must have others (not BoE !!!)
Correspondence Type SAP12 linked to report RFKORD60 and layout set F140_FAIL_PAY_01.
SAP AG 1997
RFFBWG10 uploads a file containing the failed payment transaction data from UNIX, DOS or OS/2 files and writes them into table TINSO for further processing using report RFBITB01. RFBIBL01 posts the cancellation of the remaining risk which has been posted with RFWOBL00. In the selection parameters it is necessary not to enter a special g/l indicator or to enter one defined for remaining risk. This report creates a batch-input which post the documents with CPU date and payment method blank.
SAP AG 1997
When calling the transaction FBZG report RFBITB01 is called and the before mentioned posting is performed. Afterwards, TINSO will show the status of the BoE:
1 2 3 New open position created = posted (when the user runs RFBITB01 on-line) New open position to be created = not posted but BI session created (when the user runs RFBITB01 in batch-mode) Wrong input (when the batch-input session is processed and the document contains errors
SAP AG 1997
SAP AG 1997
Italian - Specifics
The main Italian specif is the file format created by means of transaction FBWE. Called by the standard IT01 it corresponds to Riba and ist content is available in Internet: www.abi.it There is no specific layout-set for printing a BoE in Italy. Thus F110_D_WECHSEL is used as a reference by the customers willing to print it out. When uploading the failed BoE by calling ta.FBZG the file format to be choosen is IT_RIBA_14.
SAP AG 1997
Spanish- Specifics
The main Spanish specific is the file format created by means of transaction FBWE. Called by the standard ES01 it corresponds to CSB32. As of the demand from Spain a second format is provided from FBWE. This second format corresponds with CSB58 and it is provided as of release 45a. In earlier releases there is a workaround to get it (apply note 83224):
Call ta.FBWE there choose the BoE, assign them a Bank and create the presentation indicating a date and ID under file details. Call ta.se38 and run RFFOES_D choosing output type 1 so the UNIX file is created entering the date and ID filled in FBWE. Call ta.se38 and run RFWEDX00 to download the file to the PC.
SAP AG 1997
When uploading the failed BoE by calling ta.FBZG the file format to be choosen is :
ES_DOMI_90 Spain - unsuccessful bank collections. ES_RECH_15 Spain - incorrectly presented bills of exchange returned (acording to CSB Rule 32). ES_DEVO_15 Spain - bills of exchange not paid (acording to CSB Rule 32). ES_CSB58 Spain - failed payments for Norm CSB58 (only starting from release 45*).
SAP AG 1997