However, for completeness checking purposes, the Open Payables Lists are often obtained through a separate system. *This field is not needed for AP Detail, rather it can be used to determine whether this entry should be in the Open Payables Lists.
#Sap debit credit indicator manual#
Instead, you need to configure the Manual Entry codes in the Settings. Note that this column does not show up in column mapping. This field indicates whether each entry is to be considered as manual. *SAP does not provide a field that explicitly defines a manual entry. While not used in analytics, if supplied, User ID is a sortable / filterable column in our reports If this is the case, you can adjust your extraction scripts to do that calculation. Alternatively, you can provide a formula along with the appropriate raw columns and mapping table for MindBridge Data Services to preprocess your data. *Depending on the SAP implementation, Net Due Date may not be available in which case further business logic may be necessary to arrive at Due Date from BSEG.ZFBDT, BSEG.ZTERM and other fields.
This is currently not supported in MindBridge.ĭepending on the data, can use either or a concatenation of both. Note that invoice and payments may have a many to many relationship in SAP. Depending on the SAP implementation, there may be yet other ways of doing this. Depending on your SAP implementation, this may be stored in REBZG of the payment document or, in reverse, stored in AUGBL of the invoice document. *These values need to link back to the Entry ID of the related invoice entry. Number of the Invoice the Transaction Belongs to Depending on your SAP configuration, you may also need to include some combination of the other primary keys, MANDT, BUKRS, and GJAHR in order to preserve uniqueness.ĭay On Which Accounting Document Was EnteredīSEG.SAKNR may also be available, but is not always filled in The Vendor ID field needs to match across all files. *For SAP data sets, Vendor ID is strongly suggested. Note: This column is not mapped in the Open Payables Lists. See below for detailed information on Entry Type. *There is no specific SAP field that corresponds to Entry Type. If BSEG.SHKZG is "H (ie: Credit)", use BSEG.DMBTR, otherwise leave as 0 or blank If supplying line entry amounts via the Debit / Credit columns, leave the Amount column blank If BSEG.SHKZG is "S (ie: Debit)", use BSEG.DMBTR, otherwise leave as 0 or blank If supplying line entry amounts via the Amount column, leave Debit / Credit columns blank
If BSEG.SHKZG is "H (ie: Credit)", use 0 - BSEG.DMBTR If BSEG.SHKZG is "S (ie: Debit)", use BSEG.DMBTR May also need to concatenate NAME2, NAME3, and NAME4, depending on the SAP implementation. If needed, concatenation of the component raw SAP columns can be done via the MindBridge column mapping UI. The Entry ID field needs to match across all files. Depending on your SAP configuration, you may also need to include some combination of the other primary keys, MANDT, BUKRS, and GJAHR in order to preserve uniqueness. Values need to uniquely define transactions.
0 kommentar(er)
