Formal and Material Checks for Prenotes Prenotes undergo a series of formal checks when they are created, changed or deleted. In addition, material checks are made during the creation process.
Formal checks include the following:
Have you defined the specified prenote type in the Customizing for
Account Management (FS-AM)
?
Did you specify a
Valid
To
date when you created the prenote / did you define a corresponding value date condition in the account, and is the
Valid To
date after the posting date?
Does the specified account exist and is it active?
Is the creation type (dialog or BAPI) allowed for the prenote type according to the Customizing settings in
Account Management (FS-AM)
under
?
Is the amount of the prenote greater than zero? (The amount must be greater than zero, even for debit postings, because the posting has already been defined as a debit posting by the prenote for which the
Credit Memo
is deactivated in Customizing under
.)
Has the reference number been used for any prenotes that are active, assigned or in the release process?
When you change or delete a prenote, the system also checks whether the prenote was created using a PLM document in
Posting Lock Management
. If this is the case, the prenote must be processed only in
Posting Lock Management
.
The system differentiates between the following if formal checks are unsuccessful:
If you entered the prenote in the dialog, the system issues an error message and you need to correct the errors.
If you used the relevant BAPI to enter the prenote, the prenote is rejected.
The following check objectsare run for the material checks:
Own checks
Facility
Limit
Account posting
Account name
Overdraft protection
Access limit
Availability
Currency Swap
Payment form management
For more information about the checks, see the F1 help in the Implementation Guide (IMG) for
If the checks are successful, the prenote either receives the
Active
status or completes the corresponding release procedure (for example, the principle of dual control), depending on the Customizing settings for
Account Management (FS-AM)
that were made under
For more information, see
Release Object PRENOTE
.
If the checks find errors, the continuation of processing depends on the settings that you entered in the Customizing for
Account Management (FS-AM).
If you have entered settings under
for the relevant error type according to the prenote type, product and posting control group, and if these settings specify that the prenote is to be created despite errors, then the prenote is either assigned the
Active
status, or goes through the release procedure. The same applies if the prenote is placed in reallocation despite material errors, and the system generates an
account orderfor continued processing in the
Posting Control Office (FS-PCO-AM).
If, however, if you have not entered any settings for the error type according to the prenote type, product and posting control group, then you can force the creation in the dialog. If you use a BAPI to create prenotes, you can deactivate all the checks if required. If you do not force the creation, processing is terminated if you are working in the dialog, and the prenote rejected if you are using a BAPI.