cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

No account is specified in item 0000000001

Former Member
0 Likes
10,356

Hi,

When i am posting the invoice got the following error and i am not able to save the document

No account is specified in item 0000000001

Message no. F5670

Diagnosis

No account was specified for account type "S" in item "0000000001" of the FI/CO document.

System Response

The Financial Accounting program cannot process the document.

Procedure

A system error has probably occurred in the application you called up. Check the data transferred to item "0000000001" of the FI/CO document.

pl help me on this

Thanks& Regards

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Likes

Hi, Maintain account determination for reconciliation postings in transaction OBYB. Specify the posting keys for general G/L account postings. Example: Posting key 40: Debit posting Posting key 50: Credit posting. Then check the business transaction and maintain required settings in OBYB Trust this helps much! Cheers!

Answers (2)

Answers (2)

No account is specified in item 0000000001 while doing GR or MB1C (561)

Ans-go to T-code OBYC- click on BSX and put your chat of account INT and click on Posting Key maintain Debit 40 and Credit 50----- save it.

Arun1985
Explorer
0 Likes
its perfect
Former Member
0 Likes

Hi,

Go to T.Code OBA7 select GL Account in the document type which you are posting.

Cheers!

Samsunder

Former Member
0 Likes

Hi

for what purpose we need maintain T Code : OBYB could you pl give me reply on this

Regards

LVK

Edited by: LVK N on Dec 20, 2008 7:12 AM

Edited by: LVK N on Dec 20, 2008 7:12 AM

Former Member
0 Likes

Hi, Since the thread is not closed, I hope your problem has not been solved yet. If it has been solved, let us know how it was solved. Let me suggest one link. .**REMOVED BY MODERATION** Trust this helps much! Cheers!

Rajasp
Newcomer
0 Likes
Hi, Thank you for the suggestion. However, we've already enabled the GL account tick in the document type configuration, and the issue still persists. Could you please advise on any additional checks or steps we can take to resolve this?