Issue/Solution: Errors with IDOC message type PEXR002/REMADV

Message type PEXR2002/REMADV, can used to create remittance advice for customer using EDI 820 or other common formats. The following errors are common to appear in basic type PEXR2002 and message type REMADV as the mapping of IDOC fields to customer or company code is not very intuitive.

FD 16 - Company code could not be determined for intermediate document 
FD 17 - Customer/vendor could not be determined for intermediate document

To resolve the errors above, it's very important to understand how standard SAP function module to process Remittance Advice determines the relevant Customer or Company Code records.

Customer Determination
The Customer to whom remittance advice is to be posted is determined using segment with the following alternatives

1. Based on Partner Profile, as configured in WE19 if the partner is of type "KU" - customer
2. If partner type is not "KU", Segment E1EDKA1 is checked the following order of precedence where the partner function E1EDKA1-PARVW = "AG"

• Based on field LIFNR (Vendor) if Partner Function (PARVW) = "AG" (Sold to Party) against KNA1-KUNNR (Customer Account Number)

• Yes: Field LIFNR in the IDOC is validated against KUNNR in table KNA1

• Based on Our Number at Vendor/Customer (Name1) if the Partner Function (PARVW) = "AG" (Sold to Party) againt KNBK-KOINT , where KNBK-KOINT is Customer's Bank Account Holder Name as maintained in customer master Payment Transaction tab  

Company Code Determination 

1. Based on configuration in OBCA 

• Company Code Name assigned to the partner type and partner number is checked against the fields PARTN and NAME1 in segement E1EDKA1, where Partner Function (PARVW) = "BE"

2. Based on Details of the bank account in segment E1IDB02 where Partner function(PARVW)= "BB"

Some more details may be found in SAP Note 63485
https://service.sap.com/sap/support/notes/63485

Program to execute external operating system commands on SAP

SAP program RSBDCOS0 can be used to execute external operating system command, such as Unix/Linux Shell commands, from within SAP GUI.

For example, commands like change directory (cd), copy (cp), move (mv) can be executed from withing SAP GUI, to copy or move files on the SAP application server

T-codes CG3Y and CG3Z can also be used in to download files from SAP application server to desktop environment or to upload from desktop to SAP application server. However, these transactions may not work with upload of large files.

Mismatch in GL balance between FAGLB03 and FAGLL03

Issue:

General Ledger account balance displayed in transaction FAGLB03, may not match with balance for the same period shown on double clicking any cell in FAGLB03. or with transaction FAGLL03.

Causes:

There could be various reasons for mismatch between FAGLB03 and FAGLL03, Below are some of  the common reasons 

Reason One: Transaction Figures not updated 

Some documents were posted in entry view, but did not update the ledger totals  

Solution:

To identify and correct such documents, follow the steps below 

• Execute t-code FAGLF03 ( Program: TFC_COMPARE_VZ) to compare document and transaction figures in order to identify the documents in error
• If FAGLF03 identifies documents which are not posted to one or more ledgers, Execute t-code GLGCU1 (Program: RGURECGLFLEX) to update the transaction totals for the documents in error in the corresponding ledgers 

Reason Two: Incorrect negative postings 

Due to a program error, some debit line items may be displayed as credit line items in transaction FAGLL03 or some credit line items may be displayed as debit line items as shown in the screenshot below.This is usually for negative postings made due for reversals

Solution:
There could be various causes for this error,
Check the following SAP notes for resolution according to your system conditions

Note 1113114 - FAGLL03: Incorrect plus/minus signs for negative postings
Note 1163346 - FAGLL03: Incorrect plus/minus signs for negative postings(2)
Note 1170400 - Document splitting: Incorrect posting key in new G/L

Reason Three: Database Inconsistencies 

Inconsistencies in the database at various levels may cause the transaction totals and balance to differ.

Solution:

Several reports are provided by SAP to analyze database inconsistencies for relevant tables. 

Note 1155429 - Analysis:Posting keys/debit/credit indicators in FI-GL (new) 

The not above provides reports to detect and analyze database inconsistencies in new GL line items.

Electronic Bank Statement Processing in SAP

The following pages from SAP Help site, provide excellent details on the Electronic Bank Statement Processing  methodology in SAP.It also provided detail explanation of the terms used to setup the electronic bank reconciliation process using SAP

Follow the link below for details:  

SAP Help : Electronic Bank Statement Processing

Tool to compare SAP financial statement versions, Configuration and Table

Recently I needed to compare Financial Statement Versions, Configurations and Table data between two SAP systems or clients in order to ensure synchronization across multiple landscape 

While SAP offers great tools to compare ABAP programs and many configurations within the system and across multiple systems, comparing financial statement versions, table data could be tricky. Comparison in Excel may work well for comparing table data, but it becomes a time consuming activity if you need to compare each and every cell 

I stumbled upon a beautiful tool to compare two text files. SAP allows any Financial Statement Version (FSV), Configuration or Table to be downloaded to a ASCII text (.txt) file using menu option System > List > Save > Local File > Unconverted in case of FSVs or Configuration screens 

On screens where the Save Local option is not available a Print option may also be used to download data to an unconverted .txt file. Only precaution required is, files from both the SAP systems or clients you need to compare should be downloaded with exact same procedure.

After downloading the data into two files to be compared, just enter the location of the two data files in the  Exam Diff  tool and it would provide you with usual analysis of entries which are common in both the files, records which exist in one file but do not exist in other file or records which exist in both the files but are different in some way 

ExamDiff is a freeware visual file comparison tool which can be downloaded from PrestoSoft's website at the following location: ExamDiff Download Page  It's also available for download on CNET.