In exchange, FD11, is the source table for getting open things net qualities.
As to things, net worth is shown up from table BSID.
Unpaid debts are determined in view of Capability Module “DETERMINE_DUE_DATE” through passing information of “Record Date in Report” and “Money Rebate Days 1.”
For different subtleties, FD11 Exchange took from these tables:
KNB4 – Client Installment History
KNC1—Client ace (exchange figures)
KNC3 – Client ace (unique G/L exchange figures)
Comparing data with the Table
As of late, one of the Money clients made an information examination utilizing FI tcode FD11—Deals tab. They utilized the information from the charging table of a redid ABAP report, which separates data from table S708. The client questioned why the all-out deals sum was not quite the same as their FI tcode FD11.
After some reproduction of the altered report, it was observed that the report was separating information with both of the key fields:
S708 – Receipt Detail
S708-PKUNAG – Offered to party
S708-PKUNRE – Bill-to party
In the long run, it was found that the client code used in FD11 was really the accomplice field payer.
Therefore, the solution was to request that the logistics report be changed to include the field selection for payer.
VBRK – Billing Document: Header Data
VBRK-KUNRG – Payer
S708-KUNRG – Payer
FD11—Default Screen
Customer – Payer Field
YOU MAY BE INTERESTED IN
10 Real-World SAP ABAP Programming Examples (with Code!)
SAP ALE IDoc Configuration Steps: Streamlining Communication
