Do you have any question about this error?
Stop googling SAP errors. Use our Free Essentials plan instead - no credit card needed. Start Now →
Message type: E = Error
Message class: 64 - Treasury Management: Securities
Message number: 659
Message text: Error when assigning a SEC posting document no. for &1 in company code &2
An error occurred when assigning a securities posting document number
for fiscal year &V1& in company code &V2&.
The posting transaction is cancelled.
Check in Customizing to see if interval '01' is defined for number
range object 'FVVW_PODOC' in company code &V2& for fiscal year &V1& and
that there are still numbers available:
<DS:TRAN.FW-7>Number Range Securities Posting Document</>
Error message extract from SAP system. Copyright SAP SE.
64659
- Error when assigning a SEC posting document no. for &1 in company code &2 ?The SAP error message 64659, which states "Error when assigning a SEC posting document no. for &1 in company code &2," typically occurs in the context of financial transactions, particularly when dealing with secondary cost elements or postings in the Controlling (CO) module.
Cause:
This error can arise due to several reasons, including:
Missing Configuration: The secondary cost element may not be properly configured in the system. This could include missing assignment to the relevant company code or controlling area.
Document Number Range Issues: The document number range for the secondary posting may not be defined or may have been exhausted.
Authorization Issues: The user may not have the necessary authorizations to perform the posting.
Data Inconsistencies: There may be inconsistencies in the data being posted, such as incorrect account assignments or missing mandatory fields.
Technical Issues: There could be underlying technical issues, such as problems with the database or application server.
Solution:
To resolve this error, you can take the following steps:
Check Configuration:
- Verify that the secondary cost element is correctly defined in the system.
- Ensure that it is assigned to the correct company code and controlling area.
Review Document Number Ranges:
- Go to the transaction code
SNRO
to check the number range object for secondary postings.- Ensure that the number range is defined and that there are available numbers.
Check Authorizations:
- Ensure that the user has the necessary authorizations to perform the posting. This can be checked in transaction
SU53
after the error occurs.Validate Data:
- Review the data being posted for any inconsistencies or missing information. Ensure that all required fields are filled out correctly.
Consult Logs:
- Check the application logs (transaction
SLG1
) for more detailed error messages that may provide additional context.Technical Support:
- If the issue persists, consider reaching out to your SAP Basis or technical support team to investigate any underlying technical issues.
Related Information:
KSB1
(Cost Centers: Actual Line Items), KOB1
(Order: Actual Line Items), and S_ALR_87013611
(Cost Centers: Actual/Plan/Variance).By following these steps, you should be able to identify and resolve the cause of the error message 64659 in SAP.
Get instant SAP help. Sign up for our Free Essentials Plan.
64658
Error when assigning a flow header number in company code &1
What causes this issue? An error occurred when assigning a flow header number in company code &V1&.System Response The posting transaction i...
64657
Acct determination: Bal.sht acct in acc.assign.ref. &1 empty in CoCd &2
What causes this issue? You have not entered the G/L account on which the position is to be managed in the FI general ledger in account assignment re...
64660
Internal error occurred during posting in &1 &2 &3 &4
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
64661
Inconsistency between FI general ledger and SEC subledger (see long text)
What causes this issue? FI documents were reversed, although entire reversal activity was terminated due to error messages (see log).System Response ...
Click on this link to search all SAP messages.