Based on the Bank Statements, this application will enhance the Treasury Postings with additional information , collected differently depending on the System of origin, on the following documents :
in order to get details on the categories of payments ( i.e. Checks vs.Transfers) , on the processing methods ( auto vs. manual clearing) , on the life cycle of the payment, etc.
This application gathers data from 3 different SAP ECC systems (PI1,PF1 and WP1) which is then available in a Multiprovider on the BW system .
Name of project or main leader for the application + reporting coodinator
How many users? Which user category ? Is there critical period ? Which geographical perimeter? Describe in one sentence: around 50 users, worldwide or 200 users / European Site
Provide some history of the application : When was it created ? What was the initial project ? Who was the original requestor ? If possible provide link to the project information
List of application role + menu role and explanation if we have several applications role with specials rules.
| Role Code | Role Description | Explanation |
|---|---|---|
List of autorisation objects mandatory for the application.
| Authorization object | Explanation |
|---|---|
Bank Statements details are extracted from both Banks Staement tables (FEBKO/FEBEP) and enhanced by data from the generated accounting Document (tables BKPF) and the Clearing information (tables BSAD and BSAS) .
Reporting documentation drive folder:
The following document will give an overview of fields used together with field transformation rules and examples :
| https://docs.google.com/spreadsheets/d/1V8-2VM9OkEecXYgb1w6ilwHGillt4bhmossnLeDYpAw/edit#gid=551362417 |
https://drive.google.com/drive/folders/0B0qn89R0RGdqYkZZOFZyYXlXVkE
Flow Chart :
The data is extracted from systems PF1, WP1 and PI1 from a generic Datasource ZZFCM_AR_PAYMENTS based on a Function Module.
The function module Z_ZBW_READ_AR_PAYMENT_FLOW will read the Bank Statement tables FEBKO/FEBEP within the range of the Statement dates selected and will enhance the payments with Accounting Document information from table BKPF and with the Clearing information from tables BSAS and BSAD.
Dependencies with other application (BW, QV, Externals tools like PVelocity or Dynasis etc...
Detail of process chain, list + link between or special event done for the loading
The data is extracted into Structure ZZF_BW_AR_PAYMENT_FLOW :
| Source Field | Type | Length | Dec | Description |
| KUKEY | NUMC | 8 | 0 | Short key (surrogate) |
| ESNUM | NUMC | 5 | 0 | Memo record number (line item number in bank statement) |
| AZDAT | DATS | 8 | 0 | Statement Date |
| BUKRS | CHAR | 4 | 0 | Company Code |
| BUKRS_AFF | CHAR | 4 | 0 | Company Code |
| EDATE | DATS | 8 | 0 | Import date into bank data puffer |
| ETIME | TIMS | 6 | 0 | Import time into bank data buffer |
| ETIMST | DEC | 15 | 0 | UTC Time Stamp in Short Form (YYYYMMDDhhmmss) |
| KWAER | CUKY | 5 | 0 | Account Currency Key |
| KWBTR | CURR | 13 | 2 | Amount in account currency |
| HBKID | CHAR | 5 | 0 | Short Key for a House Bank |
| BANKS | CHAR | 3 | 0 | Bank country key |
| BELNR | CHAR | 10 | 0 | Accounting Document Number |
| GJAHR | NUMC | 4 | 0 | Fiscal Year |
| BUDAT_TI | DATS | 8 | 0 | Posting Date in the Document |
| CPUDT_TI | DATS | 8 | 0 | Day On Which Accounting Document Was Entered |
| CPUTM_TI | TIMS | 6 | 0 | Time of Entry |
| CPUTS_TI | DEC | 15 | 0 | UTC Time Stamp in Short Form (YYYYMMDDhhmmss) |
| USNAM_TI | CHAR | 12 | 0 | User name |
| HKONT_TI | CHAR | 10 | 0 | General Ledger Account |
| BLART_TI | CHAR | 2 | 0 | Document Type |
| TCODE_TI | CHAR | 20 | 0 | Transaction Code |
| AUGBL_TI | CHAR | 10 | 0 | Document Number of the Clearing Document |
| AUGDT_TI | DATS | 8 | 0 | Clearing Date |
| BLART_AUGBL_TI | CHAR | 2 | 0 | Document Type |
| TCODE_AUGBL_TI | CHAR | 20 | 0 | Transaction Code |
| NB_DOCS_TI | INT2 | 5 | 0 | 2 byte integer (signed) |
| NBBLN | CHAR | 10 | 0 | Subledger document number |
| BUDAT_DZ | DATS | 8 | 0 | Posting Date in the Document |
| BLART_DZ | CHAR | 2 | 0 | Document Type |
| KKBER_DZ | CHAR | 4 | 0 | Credit Control Area |
| KUNNR_DZ | CHAR | 10 | 0 | Customer Number |
| CPUDT_DZ | DATS | 8 | 0 | Day On Which Accounting Document Was Entered |
| CPUTM_DZ | TIMS | 6 | 0 | Time of Entry |
| CPUTS_DZ | DEC | 15 | 0 | UTC Time Stamp in Short Form (YYYYMMDDhhmmss) |
| USNAM_DZ | CHAR | 12 | 0 | User name |
| AUGBL_DZ | CHAR | 10 | 0 | Document Number of the Clearing Document |
| AUGDT_DZ | DATS | 8 | 0 | Clearing Date |
| TCODE_DZ | CHAR | 20 | 0 | Transaction Code |
| XREF1_DZ | CHAR | 12 | 0 | Business Partner Reference Key |
| BSCHL_DZ | CHAR | 2 | 0 | Posting Key |
| BUDAT_AUGBL_DZ | DATS | 8 | 0 | Posting Date in the Document |
| BLART_AUGBL_DZ | CHAR | 2 | 0 | Document Type |
| CPUDT_AUGBL_DZ | DATS | 8 | 0 | Day On Which Accounting Document Was Entered |
| CPUTM_AUGBL_DZ | TIMS | 6 | 0 | Time of Entry |
| CPUTS_AUGBL_DZ | DEC | 15 | 0 | UTC Time Stamp in Short Form (YYYYMMDDhhmmss) |
| USNAM_AUGBL_DZ | CHAR | 12 | 0 | User name |
| NB_INVOICES | INT2 | 5 | 0 | 2 byte integer (signed) |
| EPVOZ | CHAR | 1 | 0 | Debit/credit key for line items (for bank purposes) |
Data is then loaded in BW first layer DSO's DPFIAR09, DPFIAR20, DPFIAR21 respectively from systems PI1, PF1, WD1, and then loaded into 2nd layer DSO's DBFIAR13, DBFIAR23, DBFIAR24
Data is loaded daily from Process Chain PC_FI_ITC_02 , ITC: AR Payments
Detail of frequency : monthly; weekly or else
if possible, give some information on average process chain duration, amount of data loaded and total data volume example: daily process chain loaded in 30 min, weekly chain loaded in 1h15, with around 2k to 10k lines in DELTA mode for a total of 10M lines in cube. The purpose is to give a general overview of the volume of data managed y the application
| Key Figure | Estimation |
|---|---|
| ~ Average Process Chain Runtime | |
| ~ Average nb of rows loaded per load | |
| ~ Total nb of rows loaded (if full) | |
| ~ Average Runtime for 10k lines |
Give details if any historisation is done, example: keep only data greater than beginning of Y-3
Query end user documentation should be created in the public "Customer Support Wiki" space under the corresponding BW application page : BW - Application. Technical query query documentation, if necessary should be added as a sub-page of this documentation using the BW Technical Query Documentation template.
List the most important and complex queries only with a link to the documentation
Give detail on all complex functionalities: list most important and/or complex KPI, query jump, alerts
Indicate if there are broadcasts and give some details on the broadcast settings.
Give the list and explanation on the known, not-solved, bugs.
List recurring procedures
Detail planned major evolution if already known. Example: complete decommissioning of application is planned in 2017 / Extension to solvay perimeter planned in 2nd semester of 2016