Scribd
Upload
301 views10 pages

SAP Button Down Payment Clearing in MIRO

SAP Button Down Payment Clearing in MIRO

Uploaded by

Kelly
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
301 views10 pages

SAP Button Down Payment Clearing in MIRO

SAP Button Down Payment Clearing in MIRO

Uploaded by

Kelly
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 10

Button Down Payment Clearing in MIRO

Down Payment Clearing push button not showing in MIRO

Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

Twitter @mistersharesap

1|Page
IF NO PURCHASE DOCUMENT FIELD

GO TO
Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

Twitter @mistersharesap

3|Page
Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

Twitter @mistersharesap

5|Page
Define Field Status Variants

Short text

Field status variants use field status groups to specify which fields are ready for input, which fields must be filled, or
which fields are suppressed when entering postings. Note that additional account assignments (that is, for cost
centers or orders) are possible only if data can be entered in the corresponding fields. The groups defined here can
be assigned in the company code part of the general ledger account master record.

Use

In this activity, you can define and edit field status variants and groups. You group several field status groups in one
field status variant. You assign the field status variants to a company code in the activity Assign Company Code to
Field Status Variants. This allows you to work with the same field status groups in any number of company codes.

You can also define and process field status groups. You must define a field status group in the company-code-
specific area of each G/L account. The field status group determines which fields are ready for input, which are
required entry fields, and which are hidden during document entry. Bear in mind that additional account assignments
(for example, cost centers or orders) are only possible if the corresponding fields are ready for input.

Standard Settings

In the standard SAP system, the field status variant 0001 is entered for company code 0001. Field status groups are
already defined for this field status variant.

Note
Some fields cannot be defined with a field status. This includes, for example, fields from the document header. Some
fields from the document header can, however, be defined as required or optional fields in the document type.

The field status group you enter in the reconciliation accounts affects the corresponding customer or vendor accounts
when posting. You cannot enter a field status group in customer and vendor accounts. Field status groups are
determined for customer and vendor accounts from their respective reconciliation accounts, via the G/L account
number in their master records.

In addition to the field status group, other factors influence the field status. These include:

• The field status, which is defined for the posting key.

The status "optional entry field" was assigned to posting keys 40 and 50 in the standard system. These are
the standard posting keys for G/L account postings. The status "optional entry field" does not have any
influence on the field status.

• Specifications for document type.

There you can, for example, specify that a reference number and a document header must always be
entered.

Recommendation

Determine the field status using the field status groups in the G/L accounts. You then have an account-specific screen
layout. No differentiation via posting keys is possible since there are only two posting keys for postings to G/L
accounts.

It acts differently with the reconciliation accounts. For these special G/L accounts, you do not define the field status
differently using the master record. For this, you use the debit and credit postings keys.

Activities

1. Create new field status variants using Edit -> New entries. You can also use the copy function to create
new field status variants. To do this, select Edit -> Copy as. When copying field status variants, the
accompanying field status groups are also copied.

2. Look at the standard field status groups.

3. Find out which fields on the entry screens for the G/L Accounts in your company:

o Are to be ready for input

o Are required to have an entry

o Are to be hidden

You do not make this specification for each individual account, but for groups of accounts. In this case, use
the standard field status groups as a reference.
4. If necessary, change the standard field status groups, or define your own for each field status variant.

Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

Twitter @mistersharesap

7|Page
5. If there are any field status variants you no longer need, you can delete them by choosing Edit-> Delete.
The accompanying field status groups will also be deleted.
Mickaël QUESNOT https://www.linkedin.com/in/mickaelquesnot/

Twitter @mistersharesap

9|Page
RESULT

You might also like