2
Description of Critical Business Transaction Status: 20.02.2002 Number of transaction Short description 6 Branched customer/vendor postings The terms “request”, “invoice” and “credit memo” are treated as synonyms in the following description. In addition, original incoming and outgoing payments and payment transfers between subledger accounts (for example down payment clearing and so on) are understood under payments. 1 Description of Critical Business Transaction / Process Chain 1.1 Description / Origin Postings that cause clearing or partial payments/residual items for several invoices in several customers in one document. 1.1.1 Examples a) Several invoices are paid to several subledger accounts with a payment (for example, a civil servant responsible for budget execution transfers the payments received in an amount to the city cash desk account. This amount must be split between several customer accounts). b) When a payment advice is received, a payment document is posted which clears several receivables in one or more customer accounts (for example, a building company’s payment for several objects). c) Customer/vendor transfer postings with several senders and/or receivers. 1.2 Resulting Problems These postings cause large interlinked clearing bundles. This causes performance problems as the payment selector always interprets the whole document bundle. In addition, the payment status (pay flag) can only be set to completed when all documents of the bundle have been completed. This document/bundle must be processed again and again by RFFMS200 until the pay flag is set. If the balance zero carry forward is used, this can mean that more documents are carried forward than is necessary. This also makes the analysis of documents within the day-closing operations and account maintenance more difficult. 1.3 Avoiding Errors Ensure that this posting is not made. SAP checks whether this critical business transaction can be prevented by the system. 2 Description of Recommended Description Posting Scenario 2.1 Description Postings should only be made if an unambiguous assignment is possible Seite: 1 / 2

Kritisch6en

Embed Size (px)

DESCRIPTION

Kritisch6en

Citation preview

  • Description of Critical Business Transaction Status: 20.02.2002

    Number of transaction

    Short description

    6 Branched customer/vendor postings The terms request, invoice and credit memo are treated as synonyms in the following description. In addition, original incoming and outgoing payments and payment transfers between subledger accounts (for example down payment clearing and so on) are understood under payments.

    1 Description of Critical Business Transaction / Process Chain

    1.1 Description / Origin Postings that cause clearing or partial payments/residual items for several invoices in several customers in one document.

    1.1.1 Examples a) Several invoices are paid to several subledger accounts with a payment (for example, a

    civil servant responsible for budget execution transfers the payments received in an amount to the city cash desk account. This amount must be split between several customer accounts).

    b) When a payment advice is received, a payment document is posted which clears several receivables in one or more customer accounts (for example, a building companys payment for several objects).

    c) Customer/vendor transfer postings with several senders and/or receivers.

    1.2 Resulting Problems These postings cause large interlinked clearing bundles. This causes performance problems as the payment selector always interprets the whole document bundle. In addition, the payment status (pay flag) can only be set to completed when all documents of the bundle have been completed. This document/bundle must be processed again and again by RFFMS200 until the pay flag is set. If the balance zero carry forward is used, this can mean that more documents are carried forward than is necessary. This also makes the analysis of documents within the day-closing operations and account maintenance more difficult.

    1.3 Avoiding Errors Ensure that this posting is not made. SAP checks whether this critical business transaction can be prevented by the system.

    2 Description of Recommended Description Posting Scenario

    2.1 Description Postings should only be made if an unambiguous assignment is possible

    Seite: 1 / 2

  • Description of Critical Business Transaction Status: 20.02.2002

    2.1.1 Posting Example Instead of clearing several open items to several customers simultaneously with a payment, the payment amount should be split between the bank clearing account and distributed to the individual customers with several transfer posting documents. Only relevant for German local authorities: transaction FMPAYD (payment distribution) can be used with release 4.62 See posting example 6.doc

    3 Summary and Correction Options Problem transaction Correction option TCD / ABAP See a), b), c) Split document bundle

    with FI funds FB01, FB05, FMPAYD

    Seite: 2 / 2

    Description of Critical Business Transaction / Process ChainDescription / OriginExamples

    Resulting ProblemsAvoiding Errors

    Description of Recommended Description Posting ScenarioDescriptionPosting Example

    Summary and Correction Options