The document contains questions and answers regarding account assignments and postings in SAP. It addresses issues such as a missing table entry, posting restrictions by period, missing controlling area assignments, account determination errors, and resolving number range errors in specific transaction codes. The responses provide transaction code solutions or configuration steps to resolve the identified issues.
The document contains questions and answers regarding account assignments and postings in SAP. It addresses issues such as a missing table entry, posting restrictions by period, missing controlling area assignments, account determination errors, and resolving number range errors in specific transaction codes. The responses provide transaction code solutions or configuration steps to resolve the identified issues.
The document contains questions and answers regarding account assignments and postings in SAP. It addresses issues such as a missing table entry, posting restrictions by period, missing controlling area assignments, account determination errors, and resolving number range errors in specific transaction codes. The responses provide transaction code solutions or configuration steps to resolve the identified issues.
Q.2 Table T169P: entry 5180 does not exist( Invoice verification) (MIGO)
Ans: SM30 > T169P
Q.3 Posting only possible in periods 2019/01 and 2018/12 in company code (MIGO) Ans: MMPV, MMRV Q.4 No controlling area has been assigned to company code 5180n (MIGO) Ans: OKKP And OBY6 Q: 5 Account 100100 for trans./event key BSX is a K control account (OBYC) Ans: FSOO- Then Obyc BSX- 3000- AR/AP Only balance Post Automatic Q:6 Account determination for entry 5180 WRX ____ ___ 3000 not possible Ans: FSOO-then OBYC WRX- Only balance Post Automatic Q.7. For object RF_BELEG 5180, number range interval 50 does not exist FBN1 Ans: Go To FBN1.