How To Fix FB063 - Company code & already contains accounts in specified interval

FB063 - Overview

• Message type: E = Error

• Message class: FB - Batch Programs

• Message number: 063

• Message text: Company code & already contains accounts in specified interval

What causes this issue?

You are attempting to extract G/L account master data from company code
&V2&. However, G/L accounts are already created in the G/L account
range specified in target company code &V1&.
&HINTS&
No check was made as to whether the same G/L account numbers exist in
both company codes.
The system checked the target company code &V1& in the current logical
system. If you want to import the extracted G/L account master data
into a different logical system, this check does not apply and you can
ignore this message.

System Response

If a G/L account already exists, it cannot be processed a second time
using the "Create" function. The system therefore would not allow you
to carry out this transaction; errors would occur during import of the
batch input session.

How to fix this error?

If there are no identical G/L account numbers in the relevant intervals
of company codes &V1& and &V2&, no action is required.
If identical G/L account numbers exist you can:
Remove these accounts from your selection,
Remove the entries for these accounts after the file has been created,
or
Change the entries for these accounts in the created file from the
function "Create" to the function "Change" (change the field code
"TCODE" from "FS01" to "FS02").

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message FB063 - Company code & already contains accounts in specified interval ?

  The SAP error message FB063 indicates that the specified company code already contains accounts in the specified interval. This typically occurs when you are trying to create or modify a financial document or transaction that involves a company code that has existing account entries for the specified period.
  
  Cause:
  
  Existing Transactions: The company code has already recorded transactions (e.g., postings, journal entries) for the date range you are trying to use.
  Period Locking: The financial period you are trying to post to may be locked or closed, preventing any new entries from being made.
  Incorrect Date Range: The date range specified in your transaction overlaps with existing postings.
  
  
  Solution:
  
  
  Check Existing Transactions: Review the existing transactions in the specified date range for the company code. You can do this by using transaction codes like FB03 (Display Document) or FBL1N (Vendor Line Item Display) to see if there are any postings.
  
  
  Adjust Date Range: If you are trying