Do you have any question about this error?
Message type: E = Error
Message class: FB - Batch Programs
Message number: 063
Message text: Company code & already contains accounts in specified interval
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.
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.
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.
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) orFBL1N
(Vendor Line Item Display) to see if there are any postings.Adjust Date Range: If you are trying to post a new transaction, ensure that the date range does not overlap with existing postings. Adjust the date range accordingly.
Open the Period: If the period is closed and you need to make adjustments, you may need to open the period for posting. This can be done by using transaction code
OB52
(Open and Close Posting Periods). Note that this should be done with caution and typically requires authorization.Consult with Finance Team: If you are unsure about the implications of opening a period or modifying transactions, consult with your finance team or SAP administrator for guidance.
Use Correct Transaction Codes: Ensure you are using the correct transaction codes and following the proper procedures for posting transactions in SAP.
Related Information:
Transaction Codes: Familiarize yourself with relevant transaction codes such as:
FB03
- Display DocumentFBL1N
- Vendor Line Item DisplayOB52
- Open and Close Posting PeriodsFBL3N
- G/L Account Line Item DisplayAuthorization: Ensure you have the necessary authorizations to view and modify postings and periods.
SAP Notes: Check SAP Notes for any specific patches or updates related to this error message, as there may be known issues or fixes provided by SAP.
Documentation: Refer to SAP documentation for detailed procedures on managing financial postings and periods.
By following these steps, you should be able to resolve the FB063 error and proceed with your financial transactions in SAP.
Get instant SAP help. Start your 7-day free trial now.
FB062
Company code & does not exist in this system
What causes this issue? You are trying to extract G/L account master data from company code &V2&. The target company code &V1& you sp...
FB061
Document & record &: & not transferred.
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FB064
There are no records for processing for job &
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FB065
The first record is not a session record (type 0)
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.