Application Development Blog Posts
Learn and share on deeper, cross technology development topics such as integration and connectivity, automation, cloud extensibility, developing at scale, and security.
cancel
Showing results for 
Search instead for 
Did you mean: 
Jigang_Zhang张吉刚
Active Contributor
The error message F1(307) is quite straight forward. 'No target chart of accounts is defined for company code XXXX' which needs maintenance at table T001O (Cross-System Company Codes) by TCODE: OBV7. But the interesting things are: the user didn't encounter this issue and never maintain this entry before even at the production system. Why we need this entry which didn't require before?


With breakpoint help at the debugger, we can find it's related to sub-routine fi_document_idoc inside the function module 'FI_DOCUMENT_POST'. The key function here is 'FI_IDOC_UPDATE'. 


The standard program checks whether X_ACTIV_C2 (message type: FIDCC2) is active or not.


Inside this FM, it’ll check if an entry exists at table T001O(Cross-System Company Codes) for company code XXXX.


Then I go to WE20 and find out new created outbound message type using this message type: FIDCC2. Finally, we got the whole picture:

  1. An enhancement project created outbound for FI document posting using message type: FIDCC2;

  2. System check has been activated after FIDCC2 been activated;

  3. An entry at table T001O(Cross-System Company Codes) for company code XXXX becomes mandatory from optional.


 

Labels in this area