SAP Note 487722 - Using EXTENSION1 for accounting BAPIs

Component : Accounting Interface -

Solution : https://service.sap.com/sap/support/notes/487722 (SAP Service marketplace login required)

Summary :
When implementing specific accounting BAPIs such as BAPI_ACC_DOCUMENT_POST, it's found that certain required fields are missing in the transfer structure. These interfaces, deemed stable, cannot be altered in the current release. Users are advised to utilize the EXTENSION1 enhancement structure and implement the CMOD exit ACBAPI01 to append these fields. For non-standard, company-specific transactions, leveraging this user-exit without contacting SAP is recommended. Additionally, adjusting accounting documents via BTE with RWBAPI01 at the same BAPI is achievable by configuring through transaction FIBF, ensuring custom accounting processes are supported.

Key words :
bapi_acc_document_post         bapi_acc_document_checkbapi_acc_gl_posting_post       bapi_acc_gl_posting_checkbapi_acc_billing_post          bapi_acc_billing_checkbapi_acc_invoice_receipt_post  bapi_acc_invoice_receipt_checkbapi_acc_goods_movement_post   bapi_acc_goods_movement_checkmessage types, line item text  t_accit-sgtxt = extension+3, modify t_accit index sy-tabix, determine line itemread table t_accit, implementing cmod/smod exit acbapi01, cmod/smod exit acbapi01, it_extension type standard table, settings -> process function modules >, cmod exit acbapi01, key posnr = extension

Related Notes :

646449Differences with tax lines in reconciliation reports
556311BAPI in the extended withholding tax
306504Collective note: BAPIs for the AC interface