Ansicht
Dokumentation

BAPI_CASHJOURNALDOC_CREATE - Save FI Cash Journal Documents

rdisp/max_wprun_time - Maximum work process run time   General Material Data  
This documentation is copyright by SAP AG.

Functionality

Using the BAPI BAPI_CASHJOURNALDOC_CREATE, you can ensure that during a run, a document in the FI cash journal is saved in the same way as when you enter it via the interface transaction FBCJ.

If the field TESTRUN is set, then the system only carries out the checks and not the actual save process with update to the database.

If you want to save a cash journal document, the program that calls the BAPI must run COMMIT WORK in order for the document to be updated.

A document can have several split items.

For each document, you can post either expenses or receipts; this means that in all line items, either the field ITEMS-P_PAYMENTS or ITEMS-P_RECEIPTS must be filled.

If the document has several line items or entries in the tax table, any net or tax base amounts that you enter are deleted.

The calling application must enter the item number (ITEMS-POSITION_NUMBER) for either all line items or none.

If the calling application specifies one-time account data, the item numbers (CPD_ITEMS-POSITION_NUMBER) must correspond to the relevant line items (ITEMS-POSITION_NUMBER). This item number must only be used in one one-time account item.

If extended withholding tax is active in the company code being used, you can only enter one line item for vendors and customers relevant for withholding tax, and no split documents.

The vendor must be filled for all withholding tax information items specified (table WTAX_ITEMS).

If withholding tax information is to be specified, the indicator for the withholding tax type (WTAX_ITEMS-WTAXTYPE) must have a value that is defined in the vendor master. This same indicator for the withholding tax type must only be specified in one line of the table WTAX_ITEMS. The external item number for withholding tax information is not taken into account.

In table TAX_ITEMS, the same tax code must only be specified in one line.

If there are entries in the table TAX_ITEMS, each tax code or jurisdiction code of this table must be specified in at least one line of the table ITEMS, or must be derivable from the Customizing for the business transaction.

If accounts and tax codes for interface transactions are designated as not ready for input in Customizing, the BAPI derives values that are transferred in table CJ_ITEMS again and overwrites them if necessary.

The system recognizes a check because the field HEADER-CHECK_NUMBER is filled when the BAPI is called.

A document cannot be saved in a cash journal using this BAPI if this cash journal is locked by another user or another BAPI calling application at the same time. When you run the BAPI, a lock is set for other users.

Using the table EXTENSIONIN, the application calling the BAPI can transfer additional field values and process them further in a BAdI that is called in the subroutine customer_function.

You cannot change saved documents or present checks.

Example

Notes

Further information

Parameters

CASH_JOURNAL_DOC_NO
CASH_JOURNAL_NUMBER
COMPANY_CODE
CPD_ITEMS
EXTENSION_IN
FISCAL_YEAR
HEADER
ITEMS
RETURN
TAX_ITEMS
TESTRUN
WTAX_ITEMS

Exceptions

Function Group

SAPLFCJ_BAPI

ABAP Short Reference   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

Length: 4148 Date: 20240523 Time: 113342     sap01-206 ( 78 ms )