It would generally be advisable to keep field status optional in Posting Key and control fields using Field status Group. However, there might be scenarios where you would want to use Posting key (example you may want different field status based on debit and credit, in which case you would need to control field status using Posting key).

It should also be ensured that Field Statuses specified in Posting Key and Fields status group are compatible to each other. For example, assigning suppress and required for the same field will result in error.

Document type configuration controls

• Number range assigned.
• Reverse document type – This document type will get posted when you reverse the document.
• You can also control authorization by document type.
• Account types allowed for the document type – Asset, Customer, Vendor, Material, G/L.
• If document can only be used in batch input – Rarely used.
• Net document type – Used for vendor invoices to deduct cash automatically.
• Cust/Vend Check – If checked, only one customer or vendor can be used per document.
• Negative Postings Permitted – This check would allow to enter negative amount. This is particularly useful if you want to correct a document. You can do that by entering negative amount for wrong line item. This saves time by having not to post reversal document and corrected document.
• Inter-company postgs – If cross company postings are allowed.
• Enter Trading Partner – Allows manual entry of trading partner.
• Weather Reference Number and Document header text are required..
• You can also specify exchange rate type to be used with document type.

You get profit center balancing error, if you do not maintain necessary account determination in Config. To fix the error look for depreciation area with the issue and check if the account determination Cost object has been maintained in ACSET. Maintain the values and issue should be fixed.

Every P&L posting must be assigned to a Cost Object. Examples of Cost Object includes Cost Center, Internal Order, WBS element, Sales Order, Production order. Cost Object is the key concept in SAP Controlling.

Transfer Variant Controls

• The transfer method used (Net, Gross or New Value)
• The transaction types used for Acquisition in new Company code and Retirement in old Company Code.
• These controlling parameters can be assigned based on relationship of Company codes involved in the transfers (Dependent or Independent) and Cross-System Depreciation area. You can also mention ‘*’ to apply controls to all areas. Company codes are considered legally dependent if they have same Company id and legally independent if they different Company ids.

Other than these, Transfer Variant also controls what fields transfer to new company code.

To resolve the issue, you have everything in Error message except G/L account that needs to be assigned to Tax code. Go to Tcode OB40, Provide Chart of Account (ZZZZ), Transaction (XXX) and assign G/L to the tax code (YY).

Gross Methods – Transfers Acquisition Cost and Accumulated Depreciation to Receiving asset

Net Method – Transfers Net Book Value to Receiving asset as Acquisition Value. Accumulated Depreciation is not transferred.

New Value Method – If New Value method is assigned, system asks for a manual value to be entered while transferring.

You can maintain these setting for different transaction types or you can mention ‘*’ to include all transactions.

If you do not maintain these setting you will get error requesting Cost Center during depreciation run or APC postings. If you are using New G/L, you might get Profit Center balancing or Segment balancing error.

SAP delivers standard Transaction types. If new transaction types are required, makes sure to include X, Y or Z somewhere in the transaction type to ensure these don’t get overwritten by SAP upgrades.

Transaction type controls

• Type of transaction – Credit or Debit ie Acquisition or Retirement
• Whether asset gets capitalize when you post to it.
• Document type used for posting
• The posting is done as Gross or Net method
• Transaction type is used for Intercompany posting or not (Set Post to Affiliate Company)
• If the transaction type should not be used manually
• If the posting year should be set.
• Consolidation transaction type – used for legal Consolidation as detailed level of transaction type postings are not needed for Consolidation module.
• Asset history group can also be assigned.

You can also limit posting to only certain Depreciation areas. A pop up window will show restricted Depreciation areas while posting. If you do not maintain this setting, Posting will be done to all the Depreciation areas and SAP will suppress the popup window.