SAP Note 26050 - FIPP:Posting not poss. (SAPMF05A,0700,batch input)

Symptom:

• When you use Transaction FBV1 to post parked documents in Transaction FBV0, the message is issued that no batch input data exist for screen SAPMF05A/0700 cannot be found.

• For cross-company-code transactions, the system displays the message that no batch input data exist for screen SAPMF05A/0701.

Furthermore, there are always queries to the effect that customers are missing automatically generated line items (for example, tax line items) in the document overview, or fields that are to be automatically filled are not filled for document parking in the document overview. This is because only the line items actually entered are visible in document parking with Transaction FBV1. The automatically generated line items or fields that are to be automatically filled are only filled when you post the parked document, and so only then become visible to the user.
(Technical background: An accounting document is created from the parked document via batch input.)

Other terms

FBV0, document parking, automatically generated line items, 00344, 700,
required field, AUTTAB O

Reason and Prerequisites

Required-entry fields are defined for accounts of automatic postings (for example, taxes, cash discount, non-deductible taxes) which cannot be filled when making preliminary postings, or the indicator 'Supplement for automatic postings ?' (SKB1-XNKON) has been set in the master record of one of the accounts.

Solution

1. If required-entry fields are defined, as described above, the field selection of these accounts must be reduced to 'optional' (see Transaction OBC4). If you urgently need a required field check nevetheless, this check can be carried out via a validation at callup point 2. This validation should not be performed under condition SY-TCODE = 'FBVB' (posting a parked document).

2. If the indicator 'Supplement for automatic postings ?' has been set, you can either remove the indicator or implement the modifications from Note 49893. This will only work if you generate a batch input session from the parked documents and then process it.

If it is still required to realize required field checks / supplementary account assignments for parked documents, proceed as follows:

1. Call up Transaction FBV0 and branch to the list.

2. Select the parked document in which the termination occurs, and create a batch input session via 'Edit -> Create batch input'. Then process the batch input session in the foreground.

This procedure can also be used for error analysis.
or: You create a substitution which tries to 'automatically' make an
an account assignment for the field to be filled.