| Parameter | Reference | Type | Length | Default | Optional | Text |
|---|---|---|---|---|---|---|
| I_FIDOCNUM | IBKK_GLSFI-FIDOC | N | 6 | General Ledger: Sequential Number of FI Document per Reconciliation Key | ||
| I_HEADER | IBKKGLACHE | u | 146 | BCA: Structure for BCA-Relevant FI Document Header | ||
| I_TEST | BKK_SIMULATION_RUN | C | 1 | Simulation Run Indicator |
| Parameter | Reference | Type | Length | Text |
|---|---|---|---|---|
| E_RETURN | SYST-SUBRC | I | 4 | Return Code: 0=ok, Warning; 1=Error |
| Parameter | Reference | Length | Optional | Text |
|---|---|---|---|---|
| T_LINES | IBKKGLACGL | 173 | BCA: Structure for BCA-Relevant Fields for Document Line Items | |
| T_MESG | IBKKMESG | 224 | Structure for Transfer of Error Messages |
|
This process is intended for enhancements of the IHC module and may atthis time not be used by other applications. With this event you can replace the standard general ledger transferwith another transfer. The data of an SAP FI document is transferred to the process, which isstructured according to the posting logic of BCA. As for a standard general ledger transfer, the messages are output atthe end of the report and further processing is governed by theseverity of any errors. (This means that in the case of terminationerrors, end-of-day processing is not continued). You can use this process if you want to transfer additional fields tothe general ledger that are not supported in the standard interface(BAPI : ACC_BILLING). If the simulation indicator is set, no "COMMIT" is set at the end of theapplication. Note in this case that no asynchronous orders aretriggered for transfer. Transfer per ALE is described in the example. Description Value range Description Description Description Description Description |