Belajar dari Kecerdikan Para Desainer

November 5, 2012 Leave a comment

04 Nov 2012 | Dian | Ekonomi Bisnis

Titik-titik perjumpaan antara ilmu manajemen dan bidang-bidang lain boleh dibilang sudah jamak dimengerti. Di ranah manajemen sumber daya manusia, psikologi memainkan peran dominan. Dalam manajemen produksi, teknologi—termasuk teknologi informasi yang tergolong mutakhir—berperan tidak kecil.

Belakangan, upaya pencarian titik temu dengan bidang yang sebelumnya jarang dirambah mulai memperlihatkan hasilnya. Studi mengenai video games mendorong beberapa pakar manajemen untuk menemukan prinsip-prinsip permainan ini yang bisa diterapkan di dunia manajemen. Misalnya, untuk meningkatkan keterlibatan karyawan dalam aktivitas perusahaan. Gamification boleh dibilang wilayah baru yang tengah menarik minat banyak orang.

Akademisi dan pelaku bisnis juga menengok wilayah desain untuk mencari inspirasi dari bidang yang sangat menarik dan terus berkembang ini. Lahirlah apa yang disebut sebagai design thinking. Cara berpikir desainer dimanfaatkan di lapangan manajerial. Tapi bagaimana para manajer dapat belajar dari para desainer?

Garr Reynolds, guru besar manajemen di Universitas Kansai Gaidai, Jepang, menyebut empat prinsip yang dapat diserap oleh manajer dari desainer, yakni:

  1. Hadapi saja segala kendala. Para desainer bekerja di tengah berbagai kendala, seperti waktu, anggaran, lokasi, material. Dengan mengidentifikasi keterbatasan yang dipunyai, mereka kemudian menciptakan solusi, tapi bukan solusi yang sempurna, melainkan solusi terbaik yang mungkin diperoleh di tengah berbagai kendala itu.
  2. Ambillah risiko. Setiap keinginan untuk melakukan perubahan harus disertai dengan kesiapan untuk menghadapi risiko. Perubahan tidak akan terjadi tanpa kita mengambil kesempatan dan peluang, yang di dalamnya tersimpan pula risiko. Desainer umumnya terbiasa dengan pilihan yang mungkin keliru, tapi mereka tidak jera untuk bereksperimen dan mencoba pendekatan-pendekatan baru hingga menemukan pendekatan terbaik.
  3. Mempertanyakan segala sesuatu. Tentu saja, jawaban itu penting, tetapi yang pertama muncul pastilah pertanyaan. Desainer mengajukan banyak sekali pertanyaan yang akan memandu mereka untuk sampai kepada pertanyaan yang tepat. Nah, pertanyaan yang tepat akan membawa mereka kepada jawaban yang tepat.
  4. Ini bukan soal peralatan, melainkan perihal gagasan. Para desainer di berbagai bidang, apakah produk, interior, maupun busana, lebih memilih menggunakan pensil dan kertas untuk menuangkan gagasan mereka ke dalam sketsa. Mereka umumnya tidak mengandalkan peranti keras dan lunak untuk memulai pekerjaan mereka. Gagasan adalah bagian yang sangat penting dari pemecahan masalah, dan terkait dengan gagasan mereka bertumpu pada kertas dan pensil.

Prinsip-prinsip pokok dalam cara kerja desainer ini dapat ditransfer ke bidang manajemen. Konsep-konsep desain seperi hierarki, keseimbangan, kontras, ruang kosong dan harmoni tampaknya relevan untuk menyelesaikan pekerjaan para manajer. Dari dunia desain, para manajer dapat mengambil banyak inspirasi yang mengesankan. ***

sumber: http://blog.tempointeraktif.com/ekonomi-bisnis/belajar-dari-kecerdikan-para-desainer/

Filed under IT Architect

Indonesia PSC Accounting (Introduction: Fundamental Understanding)

August 31, 2012 Leave a comment

Untuk memahami PSC Accounting Indonesia, gambar dibawah ini bisa dijadikan awal pembelajaran kita. Berbagai versi istilah terus berkembang, namun prinsip dasar akuntansinya masih identik saat ini. Kedepan prinsip Akuntansi PSC ini tidak menutup kemungkinan mengalami perubahan mengikuti aturan yang ditetapkan oleh Pemerintah Indonesia.

Secara umum dari sudut pandang Akuntansi PSC, kegiatan bisnis di industri Minyak dan Gas di Indonesia dikelompokan menjadi 2, yaitu kegiatan yang bersifat Rutin dan kegiatan yang bersifat Tidak Rutin atau disebut sebagai Proyek. Pengelompokan ini untuk memudahkan Regulator (yaitu BPMIGAS) melakukan Perencanaan, Pengangaran, Pengendalian, Pelaporan dan Analisa atas seluruh kegiatan KPS di Indonesia.

Dari sudut pandang Budget, kegiatan Rutin dianggarkan dalam bentuk WP&B (Work Program & Budget). Sedangkan kegiatan Tidak Rutin / Proyek dianggarkan dalam format AFE (Authorization For Expenditure).  Anggaran WP&B dan AFE diajukan oleh KPS kepada BPMIGAS untuk dianalisa dan disetujui sebagai dasar rencana dan anggaran kegiatan KPS.

Dari sudut pandang Pelaporan, kegiatan Rutin memiliki 17 jenis laporan yang berbeda. Silakan dilihat dalam gambar kolom kiri. Dimulai dari Report Schedule 1 sampai dengan 17. Sedangkan kegiatan Tidak Rutin memiliki 13 jenis laporan, mulai dari Report Schedule 18 A sampai dengan 26.  Pelaporan pada kegiatan Tidak Rutin menjadi bagian dari Report Schedule WP&B juga, dijelaskan pada sesi Capex/Opex dibawah ini.

Sebagaimana istilah Akuntansi pada umumnya, Akuntansi PSC juga mengelompokan jenis biaya dalam 2 kategori CAPEX dan OPEX. Capex atau Capital Expenditure merupakan pengelompokan biaya yang pada akhirnya akan dikapitalisasi (Amount yang ada di akun biaya diposting menjadi Aset Tetap / Fixed Asset). Kapitalisasi ini dilakukan jika sudah memenuhi syarat-syarat tertentu, misalnya Proyek sudah selesai (complete) dan PIS (Place Into Service). Sedangkan Opex atau Operating Expenditure merupakan kelompok transaksi yang selamanya akan dilaporkan dalam akun biaya. Amount dalam kategori Opex ini tidak dikapitalisasi.

Dari sudut pandang Capex / Opex, kegiatan Proyek / AFE dibagi menjadi 7 kelompok, terbagi dalam 5 kelompok Capex dan 2 kelompok Opex. Kelompok Capex yaitu;

  1. Seismic & Survey bersumber dari Report Schedule 18 A, 18 B, dan 18 C. Untuk diketahui bahwa kelompok Seismic & Survey ini di-summary-kan dalam WP&B Report Schedule 4.
  2. Geological & Geophysical Study bersumber dari Report Schedule 18 D dan 18 E. Untuk diketahui bahwa kelompok G&G Study ini di-summary-kan dalam WP&B Report Schedule 4.
  3. Drilling bersumber dari Report Schedule 19 dan 20 yang terkait dengan biaya Drilling saja. Untuk diketahui bahwa kelompok Drilling ini di-summary-kan dalam WP&B Report Schedule 4 kelompok Tangible.
  4. Facilities bersumber dari Report Schedule 21, 22, 23, 24, dan 25. Untuk diketahui bahwa kelompok Facilities ini di-summary-kan dalam WP&B Report Schedule 8.
  5. Other Project Capex bersumber dari Report Schedule 26 yang biayanya dikapitalisasi. Untuk diketahui bahwa kelompok Other Project Capex ini di-summary-kan dalam WP&B Report Schedule 8 atau 11 tergantung jenis proyeknya, namun perlu diingat bahwa biaya ini dikapitalisasi. Detail akan dijelaskan pada sesi berikutnya.

Sedangkan kelompok Opex terdiri dari (1) Work Over yang bersumber dari Report Schedule 19 dan 20 yang terkait dengan biaya Work Over saja. Untuk diketahui bahwa kelompok Work Over ini di-summary-kan dalam WP&B Report Schedule 4 kelompok Intangible. (2) Other Project Opex yang bersumber dari Report Schedule 26 yang biayanya tidak dikapitalisasi. Untuk diketahui bahwa kelompok Other Project Opex ini di-summary-kan dalam WP&B Report Schedule 8 atau 11 tergantung jenis proyeknya, namun perlu diingat bahwa biaya ini tidak dikapitalisasi. Detail akan dijelaskan pada sesi berikutnya.

Source: Dari berbagai sumber online dan offline (dwiERP.com)

Filed under PSC Accounting Tagged with , , , , ,

SAP JVA Standard Program

April 10, 2012 Leave a comment

Program Name                      Report title
RGJV_BILLING_SUPPLEMENT           Supplent for billing report
RGJV_CC_RECLASS                   JV Cash Call Reclassification with Rollforward
RGJV_CC_RECLASS_ALV               JV Cash Call Reclass – ALV Routines
RGJV_CC_RECLASS_EVT               JV Cash Call Reclass – JV Event table updates
RGJV_CC_RECLASS_MSG               JV Cash Call Reclass – Message handling routines
RGJV_CC_RECLASS_PST               JV Cash Call Reclass – Posting routines
RGJV_CUTB_REVERSE                 Cutack document reversal
RGJV2230                          Correction of JVSO1 (differences between 22D and 30x)
RGJV2CO1                          Mrule handling in settlment rule maintenance
RGJVACDL                          JV CRP pricing data – Deleting of archived data
RGJVACIC                          JV CRP pricing data – Creating of archive index
RGJVACID                          Program for deleting indices of JV_PRICING archives
RGJVACWR                          JV CRP pricing data – create archive
RGJVADIR                          Update TADIR
RGJVAP00                          Access to Automatic Posting Transaction for Joint Venture Accounting.
RGJVAPCC                          Access to Automatic Posting Transaction (Cost Calculations)
RGJVATAX                          Advance Return for Tax on Sales/Purchases
RGJVATI1                          Include with Table UMS40 Structure for Converting Documents
RGJVBASS                          Selection Screen section of Bank Switching
RGJVBAST                          Global data declaration for Bank Switching
RGJVBASW                          JV Bank Account Switches
RGJVBAZZ                          User Exit for Customer defined Forms
RGJVBE01                          Billing data selection: Invoice / Statement
RGJVBE02                          Billing data selection: Expenditure detail / supplemental detail
RGJVBE02_SUS_COVP                 include RGJVBE02_SUS_COVP
RGJVBE02_SUS_P                    Include RGJVBE02_SUS_P
RGJVBE02_TOP                      Billing data selection: Expenditure detail / supplemental detail – Top
RGJVBILL                          Form routines called by Billing SAPscript
RGJVBILL_EC                       Form routines called by Billing SAPscript
RGJVBILL_EC2                      Form routines called by Billing SAPscript
RGJVBJ01                          Jade File Generation for Auditing
RGJVBJ02                          Jade File Generation for Auditing
RGJVBJS2                          include selection screens for JADE
RGJVBJT2                          include global variables for JADE
RGJVBR04                          Common parts for Hard copy billing and Supplemental billing
RGJVBR10                          Billing output: Hard copy billing
RGJVBR10_SUS_COVP                 include RGJVBR10_SUS_COVP
RGJVBR10_SUS_P                    Include RGJVBR10_SUS_P
RGJVBR15                          Billing output: Hard copy billing
RGJVBR15_SUS_COVP                 include RGJVBR15_SUS_COVP
RGJVBR15_SUS_P                    Include RGJVBR15_SUS_P
RGJVBR20                          Hardcopy billing configuration analysis report
RGJVBR22                          JV Billing Extract Reconciliation Report
RGJVBR22_SUS_COVP                 include RGJVBR22_SUS_COVP
RGJVBR22_SUS_P                    Include RGJVBR22_SUS_P
RGJVBR23                          Norwegian Billing
RGJVBRTH                          Billing threshold check
RGJVBRTHSCR                       Include RGJVBRTHSCR
RGJVBRTHTOP                       Include RGJVBRTHTOP
RGJVBTR0                          Vorgänge für Joint Venture anlegen
RGJVBUP1                          Update Billing Extracts for New and Changed Fields
RGJVBUP2                          Change report for jvbx
RGJVBUPD                          Change report for jvbx
RGJVBUPT                          declaration of global data
RGJVC001                          Program to delete duplicate entries in JVOO1 and JVTO1
RGJVCB01                          Cutback Fast Batch Input – Validations
RGJVCB03                          Cutback – General includes
RGJVCB04                          Common include for RGJVEA10 and RGJVCB15
RGJVCB10
RGJVCB10_CUTB_REVERSE
RGJVCB15
RGJVCB15_CUTB_REVERSE             Include RGJVCB15_CUTB_REVERSE
RGJVCBT0                          Cutback – Fast Batch Input Global Data
RGJVCC00                          JVA: Copy/delete configuration for company code
RGJVCCRC                          Cash Call Reclassification
RGJVCF00                          JVA GL-X Carry Forward Program – RGJVCF00 (JVA GL-X ledgers only)
RGJVCF00_SWITCH_PL_ACCOUNTS
RGJVCF00_UPDATE_T8JTPMF01         Include RGJVCF00_UPDATE_T8JTPMF01
RGJVCF01                          JVA GL-X Carry Forward Program – RGJVCF01 (Common part of program)
RGJVCF01_ALV                      JVA GL-X Carry Forward Program – RGJVCF01 (Common part of program)
RGJVCF02                          JVA GL-X Carry Forward Program – RGJVCF02 (all GL-X ledger possible)
RGJVCNET                          Convenience Netting
RGJVCORB                          Correction program for false JV documents created by CO
RGJVCPEG                          Current Period Equity Group Changes
RGJVCUPA                          Customizing Partner Address
RGJVCYP1                          Print of all Cycle Information for Joint Venture Accounting
RGJVEA01                          Equity adjustment – Validations
RGJVEA10                          Prior period equity adjustment
RGJVEAS0                          Selection screen for RGJVEA10
RGJVEAT0                          Global data for RGJVEA10
RGJVEC00                          Pre-Cutback Equity Change Management
RGJVEDI1                          Translator for test purpose only (Inbound EDI) Text Document
RGJVEDI2                          EDI Inbound Reports (Cost Objects/Account Mappings)
RGJVEDIA                          JV EDI Inbound: IDOC Status Report
RGJVEDIB                          JV EDI Inbound: Invoice and Operating Statement
RGJVEDIC                          JV EDI Inbound: Unusual Expenditure Report (819)
RGJVEDID                          JV EDI Inbound: Memo AFE Projects
RGJVEDIE                          JV EDI Inbound: Expenditure Comparison Report
RGJVEDIF                          JV EDI Inbound: Forms for reporting
RGJVEDIG                          810 to 819 Property IDoc Comparison Report
RGJVEDII                          JV EDI Inbound Process code configuration
RGJVEDIO                          JV EDI Billing
RGJVEDIR                          Reset EDI inbound partner for processing
RGJVEDIT                          JV EDI Inbound: Invoice, Operating Statement & Unusual Exp.
RGJVEDIX                          EDI Outbound Basic Configuration for new Client/Company/Billing-Struc.
RGJVEG00                          JV Equity Groups
RGJVEUR_BALANCE_REBUILD           Euro reconciliation program JV ledgers to FI documents
RGJVEUR_CORRECT_CO_DOCS           Euro reconciliation program JV ledgers to FI documents
RGJVEUR_SINGLE                    Euro reconciliation program JV ledgers to FI documents
RGJVEUR3                          Euro reconciliation program JV ledgers to FI documents
RGJVEUR4                          Euro reconciliation program JV ledgers to FI documents
RGJVEUR5                          Euro reconciliation program JV ledgers to FI documents
RGJVEUR6                          Euro reconciliation program JV ledgers to FI documents
RGJVEUR7                          Euro reconciliation program JV ledgers to FI documents
RGJVEUR8                          Euro reconciliation program JV ledgers to FI documents
RGJVEUR9                          Euro reconciliation program JV ledgers to FI documents
RGJVEURD                          Data Include JV Euro
RGJVEURI                          Euro reconciliation program JV ledgers to FI documents
RGJVEURT                          Euro reconciliation program JV ledgers to FI documents
RGJVEVNT                          Display event table
RGJVFARM10                        Farm in/out & Re-Determination
RGJVFARM10_CHECK                  Selection screen for RGJVEA10
RGJVFARM10_SEL                    Equity adjustment – Validations
RGJVFARM10_TOP                    Global data for RGJVEA10
RGJVFARM20                        Farm IN/Out: Cutback Correction for Inter-Company  Partner
RGJVFARM20_SEL                    Equity adjustment – Validations
RGJVFARM20_TOP                    Global data for RGJVEA10
RGJVFARMCC                        Farm IN/Out: Change for billing ledger
RGJVFARMCC_COMMON_FORMS           RGJVFARMCC_COMMON_FORMS
RGJVFARMCC_SEL                    Equity adjustment – Validations
RGJVFARMCC_TOP                    Global data for RGJVEA10
RGJVFARMCC1                       Prior period equity adjustment
RGJVFARMCC1_SEL                   Equity adjustment – Validations
RGJVFARMCC1_TOP                   Global data for RGJVEA10
RGJVFARMCC2                       Farm IN/Out: Cash Call correction
RGJVFARMCC2_SEL                   Equity adjustment – Validations
RGJVFARMCC2_TOP                   Global data for RGJVEA10
RGJVGCCL                          Cash Call Transaction Report
RGJVGJ4A                          Periodic updates for company code
RGJVGJ4A_MCC                      Periodic updates for multiple company codes in JVA
RGJVGLXT                          Display of GL/X configuration tables
RGJVGM01                          General Posting Routine Include – Posting Forms
RGJVGM10                          Excel Spreadsheet Download to FB01 Post Program
RGJVGMTP                          General Posting Include – Data Structure of Master Table
RGJVHBCH                          House Bank Switching
RGJVIMCOR003                      Find unnecessary JVJV documents
RGJVIMG1                          Test
RGJVINST                          JV Installation for a client
RGJVIS00                          JVA: Install standard reports
RGJVJOBC                          JV Job Load Balancer
RGJVLB00                          Load balancing for JV processes
RGJVLBOX_DATA_CREATION            Lockbox data creation based on JV ledger
RGJVMISSINGTABLE                  Missing table entries in 4.0b new install
RGJVOO2                           Correction program for JVOO2
RGJVPLRP                          Delete and repost JV plandata created by CO
RGJVPM01                          Modification for LCOIHI10 to add JV data to PM orders
RGJVPMRECON                       Reconcile Production month numbers iwith JV totals
RGJVPMSTART                       Initialize Production Month Data
RGJVPMTP                          Data for JV processing in PM orders
RGJVPNET                          Partner Netting
RGJVPS01                          Modification for SAPLCOKO to add JV data to networks
RGJVRDFN                          Read file from PC for update JVSO1
RGJVREC1                          Simulate the posting of an FI document
RGJVREC3                          Simulate the posting of an existing MM document
RGJVREC5                          Report to repost FB08 documents which are missing in JV
RGJVREC7                          Re-post a clearing document
RGJVREC8                          Detecting and reposting incorrect JV documents
RGJVREC8B                         Reverse and Rebook of MM invoice documents
RGJVREC9                          Reverse and rebook of MM documents
RGJVRECS                          Missing JV document list
RGJVREP1                          Reporting Summary Ledger
RGJVREP2                          Reporting Billing Ledger
RGJVREPO                          Joint Venture Information System
RGJVROLLUP                        Find the correct rollup and start the rollup processing
RGJVRU00                          Suspense projects and equity groups
RGJVRU00_SUS_COVP                 include RGJVRU00_SUS_COVP
RGJVRU00_SUS_P                    Include RGJVRU00_SUS_P
RGJVRU02                          Suspense projects and equity groups
RGJVRUT1                          Data definition for RGJVRU01
RGJVRXDT                          Transfer automatic postings to CO
RGJVSALV                          ALV routines for JV snigle item reports
RGJVSDAT                          JV single items – general data declarations
RGJVSFRM                          JV single items – common forms
RGJVSINI                          JV single items – initialisation routines
RGJVSO10                          List JV single items
RGJVSO10_OLD                      Summary ledger line items
RGJVSO20                          JV Billing items
RGJVSO20_OLD                      Billing ledger line items
RGJVSOD0                          Common data declarations
RGJVSOEV                          Common events
RGJVSONN                          Common subroutines for line item reports (JVSO1, JVSO2)
RGJVSPAI                          JV single items – selection screen PAI
RGJVSPBO                          JV single items – selection screen PBO
RGJVSSEL                          Free selection routines for JV line item reports
RGJVT1S1                          AC Common Code Shell
RGJVT2S2                          AC Module Pool Shell
RGJVTAX2                          Advance Return for Tax on Sales/Purchases
RGJVTAXR                          Advance Return for Tax on Sales/Purchases
RGJVTAXR_NEW                      Advance Return for Tax on Sales/Purchases
RGJVTO10                          Drill-down receiver report dispatcher
RGJVTO1I                          Customize drill-down reports for billing reporting
RGJVUCUR                          Funding Currency by Equity Group Update
RGJVUDOC                          Compare FI/CO/MM document and JV document
RGJVUXDT                          Unrealized exchange differences
RGJVVALI                          Form routines for validation of input fields
RGJVVBAT                          Create Table Entries for VBA Switching
RGJVW001                          Valuation of foreign currency PO’s assigned to an account
RGJVXEDA                          EDI Outbound XPRA for Application code conversion in configuration
RGJVXMODIF                        Maintain modifications
RGJVXPR2                          RGJVXPR1     Umsetzung von JVTO1/JVSO1

Filed under JVA, SAP Enterprise Tagged with , ,

Is it required to set OAYC (last deprec. posted) during FIAA cut over?

December 3, 2011 Leave a comment

The most common questions were asked during FIAA cut over strategy discussion is how to maintain parameters for data transfer? In term of date specification, there are two configuration should be prepared prior data upload testing.
1. Specify Transfer Date/Last Closed Fiscal Year.
2. Specify Last Period Posted in Prv.System (Transf.During FY), we can execute this from t-code OAYC.

In what conditions consultant have to maintain those two configuration nodes:
Assumption: the transfer date has been decided by company, it can be at the end of the year or at the middle of the year.
First configuration is always mandatory although fixed asset legacy data transfer on the middle of the year. Below two scenarios for example.
a. Company RU01 plan to transfer fixed asset legacy data on end of date year 2003 then take over date (V_T093C_08-DATUM) is “31.12.2003) as follow picture.
b. Other company which is RERF plan to transfer fixed asset legacy data on end of June year 2004 (middle of the year) and the take over date should be “30.06.2004″.

Now we see second configuration, below.
Period in which last depreciation was posted for company code RERF which will go live on middle of the year has open field in FYear (V_T093U_01-AFBLGJ) and Per (V_T093U_01-AFBLPE). Consultant should maintain those fields with correct value which is the last month of depreciation was posted in company’s legacy system. In this example is 2004 / 6 (period June year 2004). Compare with the first configuration for company RERF, those are linked and have consistence values.

Period in which last depreciation was posted for company code RU01 which will go live on early of the year has grey field in FYear (V_T093U_01-AFBLGJ) and Per (V_T093U_01-AFBLPE). It means consultant shouldn’t maintain value on those fields. SAP system is preventing inconsistency configuration also.

Fiscal year of last depreciation posting.
In this field, the system enters the fiscal year for which depreciation was last posted. If legacy data transfer is carried out during the course of the fiscal year, you must manually update this field. The field is not available for input if legacy data not transferred within the fiscal year, or if depreciation is not posted in this depreciation area.

Period in which last depreciation was posted.
In this field, the system enters the period, for which depreciation was last posted. If the legacy data transfer is carried out during the fiscal year, you must update this field manually. This field is not available for input if there is no legacy data transfer during the fiscal year, or if depreciation is not posted in this depreciation area.

So what’s the answer then?
It’s depending on the transfer date, if it’s transferred on end of the year then OAYC shouldn’t be maintained. SAP system also preventing those inconsistence configuration by make those fields are grey.
If it’s transferred in the middle of the year then OAYC should be maintained, FYear and Per fields should be open, if it is not, check first configuration or check note 515269.

Hope it will help you and thank you.

Filed under Finance Controlling, SAP Enterprise Tagged with , ,

SAP JVA Function Module

December 3, 2011 Leave a comment

JVA_BTE_00503305 Event: Pflege Konditionen: Feldprüfung
JVA_BTE_ANLA_REPORT Venture Data selection for asset reporting
JVA_CURRENCIES Give JVA currency assignments
JVA_LAST_DATE_OF_MONTH Get last date of month
JVA_POPUP_TO_DISPLAY_TEXT Dialogfenster, um beliebigen Text anzuzeigen.
JVA_READ_EGROUP JVA Venture Data for E&P
JVA_READ_INTERCOCD_CC JVA Venture Data for E&P
JVA_READ_JVCC Read JVA Company Codes
JVA_READ_PARTNER JVA Partner Data for E&P
JVA_READ_VENTURE JVA Venture Data for E&P
JV_ADJUST_TAX_LINES Adjust tax lines for tax report
JV_ADVANCED_TAX_CALCULATION Advanced Tax Report – Calculation
JV_ADVANCED_TAX_REPORT Advanced Tax Report – Calculation
JV_ALLOC_MRULE_CHK Check routine for Mrule
JV_ALLOC_MRULE_F4H f4 help for Mrule in allocation
JV_ALLOC_MRULE_PAI Joint venture allocation manipulation rule – PAI
JV_ALLOC_MRULE_PBO Joint venture allocation manipulation rule – PBO
JV_ALLOC_REF_DATE_PAI Joint venture allocation reference date – PAI
JV_ALLOC_REF_DATE_PBO Joint venture allocation reference date – PBO
JV_AM_ANEA_PER_JVTO1 Find all ANEA records for a given JVTO1 entry
JV_AM_ANEPS_ANEAS_PER_JVTO1 Find all ANEA records for a given JVTO1 entry
JV_AM_COBL Derive Venture Information from Asset for COBL
JV_AM_CUTBACK_DEPR_GENERATE Generate Value Screens for Asset Cutback on retired depreciation
JV_AM_CUTBACK_GET_JVTO1_RECS Get collected JVTO1 records for Asset Cutback
JV_AM_CUTBACK_POSTINGS Create Asset Postings from Cutback
JV_AM_DETERMINE_SCREEN Determine if coding block is called from detail screen (0002)
JV_AM_DOCUMENT_CREATE Bereitet Belegerstellung vor und ruft Baustein für Belegerstellung
JV_AM_DOCUMENT_REVERSAL Fill venture information into ACCIT from asset information
JV_AM_POSTING_BY_RECID Update ANEPs by recovery indicator / table t8jhr
JV_AM_POSTRULES_GET Get Cutback posting rules for Asset Cutback Postings
JV_AM_RECOGNIZE_SCREEN Recognize if Coding block was called in detail screen before
JV_AM_SUBNUMBER_SELECT Selection of subnumbers according to vintage years
JV_AM_VENTURE_INFORMATION Fill venture information into ACCIT from asset information
JV_AND_FI_CURRENCIES Currencies used in JV and FI
JV_ANEP_PER_RECID Reset ANEPI according to recovery indicator
JV_AUTHORITY_CHECK_CUSTOMIZE Check authority for JVA customizing
JV_AUTHORITY_CHECK_JOA Check authority for Joint Operating Agreement master data
JV_AUTHORITY_CHECK_PROCESS Check authority for JVA process
JV_AUTHORITY_CHECK_REP Check authority for reporting
JV_AUTHORITY_CHECK_VNT Check authority for Venture master
JV_AUTHORITY_CUS_GROUP_GET Get JVA customizing group for authority
JV_BI_FOR_GJCU Creation of Batch Input for transaction GJCU (Cutback ledgers GB01)
JV_CASH_CALL_POPUP_CONFIRM_MSG Dialog box to confirm processing step; with diagnosis text
JV_CHECK_FIELDS Check JV fields of cost objects
JV_CLEAR_EQUITY_GROUP_DATES Clears and Refreshes internal table IT8JG for JV_GET_EQUITY_GROUP_DATES
JV_CLEAR_JVAP Clear table T_JVAP and T_JVAH
JV_COBL_CHECK Check Partner exists for this Venture/Equity group
JV_COBL_DOCUMENT_CHECK JV_COBL_DOCUMENT_CHECK
JV_COBL_RECEIVE_FOR_TAX Receive coding block for tax only postings
JV_COBL_SEND_PAI_FOR_TAX Send coding block to function group in PAI
JV_COBL_SEND_PBO_FOR_TAX Send coding block for tax only (in dynpro 312)
JV_COLLECT_MESSAGE Joint Venture Error Message Handling – Collection of Messages
JV_CO_CHECK JV-CO integration
JV_CO_PLAN_CHECK Plan data from CO
JV_CO_POST JC CO Interface posting
JV_CO_POST_PLAN JC CO Interface posting plan data
JV_CRP_MIGO_BADI_HANDLE directly called (PAI) by MIGO BADI for CRP pricing
JV_CUTBACK_EXIT_TEMPLATE Joint Venture Cutback User Exit Template
JV_DATA_CHECK Joint Venture-Felder prüfen
JV_DATA_CHECK_MM_JV JV interface module for checking JV data in MM
JV_DATA_CHECK_TS Allgemeiner Rückladebaustein für (RW-)Archive (keine Archivneuerstellung!)
JV_DATA_GET_MM_JV JV interface module for automatic JV data derivation in MM
JV_DATA_MAINTAIN_IN_POPUP Maintenance of JV data on application objects
JV_DATA_MAINTENANCE_MM_JV Joint venture data maintenance on logistic objects – JV plugin
JV_DATA_SET_IN_COBL Derive Recovery indicator in COBL for fixed asset postings
JV_DATA_SUBSCREEN_PAI Maintenance of JV data on application objects
JV_DATA_SUBSCREEN_PBO Maintenance of JV data on application objects
JV_DELETE_ERROR_LOG Delete documents from the error log
JV_DIRECT_INPUT Direct Input Postings for Joint Venture
JV_DISPLAY_ACTIVE_COMPCODE Display the active company codes (for PF4)
JV_DISPLAY_ACTIVE_LEDGER JVA display active JVA ledger
JV_DOCUMENT_DELETE Call the JV interface at Callup point DELETE
JV_DOCUMENT_HEADER JVA Integration Manager – processing for FI-Headers
JV_DOCUMENT_POST JVA Integration Manager – processing for entire FI-Document before Posting
JV_DOCUMENT_PREREV Prepare reversal of JV document
JV_DOCUMENT_REVERSE_REAL Real Reversal of JV Documents
JV_DUNNING_INTERFACE_00001760 Mahnselektion 1760: Applikationskennzeichen für Immo im Mahnkonto setzen
JV_DUNNING_INTERFACE_00001761 Mahnselektion 1761: Applikationskennzeichen für Immo im Mahnbestand setzen
JV_EC_EXIT Exit for E&C for call in JV IM
JV_EDIT_DATA_FOR_NETWORK Edit Jv data in network
JV_EDIT_DATA_FOR_PM Edit Jv data in PM order
JV_EDI_CHECK_INV_EXTRACT JV EDI Billing – Check the Invoice Extract for data
JV_EDI_COMPANY_LEVEL_TABS Joint Venture – LOAD THE JIB DESCRIPTION TABLES BY COMPANY
JV_EDI_COMPANY_TABLES JV EDI Billing – Load the Company specific tables
JV_EDI_CONTROL_819_GEN JV EDI Billing – Control calls to 819 generation modules
JV_EDI_CONTROL_REPORTING JV EDI Billing – Control Reporting at end of processing
JV_EDI_CONTROL_TOTALS JV EDI Billing – Generate Control totals for reporting
JV_EDI_GLOBAL_TABLES JV EDI Billing – Load the Global tables
JV_EDI_INBOUND_DOCUMENT_POST JV EDI Inbound:
JV_EDI_INBOUND_DOC_PROJECT JV EDI Inbound: IDOC & FB01 Document numbers cross-reference
JV_EDI_INTERNATIONAL Joint Venture EDI for International Companies
JV_EDI_JVCABI_INVOICE JV EDI Billing – Invoice for Canadian processing
JV_EDI_JVCABI_OP_STMT JV EDI Billing – Operating Exp. Statement for Canadian processing
JV_EDI_JVINBI_INVOICE JV EDI Billing – Invoice for International processing
JV_EDI_JVUSBI_INVOICE JV EDI Billing – Invoice for US processing
JV_EDI_JVUSBI_OP_STMT JV EDI Billing – Operating Exp. Statement for US processing
JV_EDI_MEMO_AFE_CHANGE_DATE T8JDP UPDATE
JV_EDI_MODIFY_819_TABLE Modify 819 table for 819 only processing
JV_EDI_NORTH_AMERICA Joint Venture EDI for North American Companies
JV_EDI_PARTNER_LEVEL_TABS Joint Venture – EDI Partner Level Processing
JV_EDI_PARTNER_TABLES JV EDI Billing – Load the Partner specific tables
JV_EDI_VENTURE_LEVEL_TABS Joint Venture EDI International – Venture Level Processing.
JV_EDI_VENTURE_TABLES JV EDI Billing – Load the Venture specific tables
JV_FARM_PROCESS_CHECK Check the process definition
JV_FARM_PROCESS_STATUS_SET Check the process definition
JV_FB01_DIRECT_INPUT Direct input for FBO1 postings
JV_FILL_JVKOMK IS-Oil /Joint Venture/ Material tansfer pricing
JV_FILL_JVKOMP IS-Oil /Joint Venture/ Material transfer pricing
JV_FI_CLEARING JVA Integration Manager – Processing for items to be cleared
JV_FI_DOCUMENT_CLOSE JVA Integration Manager – processing for entire FI-document
JV_FI_DOCUMENT_PROJECT JVA Integration Manager – processing for entire FI-document
JV_FI_RESET_CLEARING Belegaufteilung: Ausgleichsrücknahmeinformation in Funktionsgr. übernehmen
JV_GB01_DIRECT_INPUT JV GB01 Direct Input
JV_GB01_DOCUMENT_POST JVA Integration Manager – processing for entire FI-Document before Posting
JV_GET_BILLING_EXTRACT Get billing extract for JVA
JV_GET_BILLING_HISTORY Get billing history
JV_GET_BILLING_THRESHOLD Get billing threshold
JV_GET_CC_ATTRIBUTES Joint Venture Cost center attribute function module
JV_GET_CURRENT_BILLING_AMOUNT Get current amount to be billed in JVA
JV_GET_DOCUMENTS_FOR_HOLD Get documents for holding into the next period
JV_GET_DOCUMENTS_FOR_RELEASE Get documents for holding into the next period
JV_GET_DOCUMENT_DATE Document Date Retrieval Function Module
JV_GET_EQUITY_GROUP_DATES Get the document date for a specific Venture/Equity Group
JV_GET_JV_DATA_FROM_WBS JV Master Data from WBS element
JV_GET_OLD_BILLING_AMOUNT Get billing amount held from previous periods
JV_GET_ORD_ATTRIBUTES Joint Venture : Order Attributes
JV_GET_PROPERTY_NAME Get property name for venture/equity type level
JV_GET_PRPS_PER_VENTURE get all prps records per venture
JV_GET_VENTURES_FOR_JOA Retrieve all venture belonging to a JOA
JV_GET_WBS_ATTRIBUTES Joint Venture – Get Project Attributes
JV_HELP_EXIT_T8J0M User exit for billing format search help
JV_HELP_EXIT_T8J0R User exit for billing format search help
JV_HELP_EXIT_T8JV Search help exit for T8JV
JV_HELP_EXIT_T8JVC01 User exit for billing format search help
JV_HELP_EXIT_T8PSCSRC User exit for billing format search help
JV_IDOC_INPUT_INVOICE_CA Joint Venture: EDI Inbound, IDOC invoice
JV_IDOC_INPUT_INVOICE_US Joint Venture: EDI Inbound, IDOC invoice
JV_INITIALISE_MESSAGE JV Error Message Handling Initialisation
JV_INSERT Insert internal table into DB table
JV_INSERT_ERROR_LOG Write the information for reposting a document into the error log
JV_INSERT_T8JVBA Insert records in t8jvba
JV_INTERCOMP_MAPPING_CHECK Reconciliation of  intercompany settings
JV_JVSO1_TO_JVAP Create JVAP from JVSO1
JV_JVTO1_AND_PM Read producton month detail with JVTO1
JV_LEDGER_GIVE Joint Venture Utilities
JV_LOCKBOX Function for lockbox
JV_MCC_CHECK Multiple company code selection – checks
JV_MD_CREATE_CHANGE_DOCUMENT Create masterdata change document
JV_MD_DATABASE_UPDATE updates all masterdata JOA’s
JV_MD_GET_NEW_NUMBER gg
JV_MD_JOA_VALIDATE Validate JOA information
JV_MD_READTABLES read tables for JOA maintenance tables
JV_MD_UPDATE_EQUITY_GROUP update equity group
JV_MD_UPDATE_EQUITY_GROUP_X update equity group change document tables
JV_MD_UPDATE_JOA update change history
JV_MD_UPDATE_PARTNER Update partner
JV_MD_UPDATE_PARTNER_X update partner after update table xt8j9c
JV_MD_UPDATE_PENCAT Joint Venture Penalty Category Maintenance
JV_MD_UPDATE_PENCAT_X updates the after pencat table
JV_MD_VALIDATE_EQUITY_GROUP Validate equity group
JV_MD_VALIDATE_PARTNER validate partner
JV_MD_VALIDATE_PENCAT Joint Venture Penalty Category Maintenance
JV_MESSAGE_SHOW Joint Venture Write Message – Writes Error Messages Generated by JV prgs.
JV_MM_CRP_VALUES_ADD Transfer CRP Values to Integration Manager
JV_MM_CRP_VALUES_RECID Add Recovery indicator to CRP table
JV_MM_DOCUMENT_CLOSE JVA Integration Manager – processing for entire FI-document
JV_MM_DOCUMENT_PROJECT JVA Integration Manager – processing for entire MM-document
JV_MM_INVOICE_CLOSE JVA Integration Manager – processing for entire FI-document
JV_OWNERSHIP Get JV Ownership for a specific object
JV_PM_ACTIVE Check if Procution month processing is active
JV_POSTING_DATE_FROM_PERIOD Set posting date depending on the posting period
JV_POST_GROSS_VALUES Function posts to gross ledger
JV_PREPARE_FI_POSTING_TO_HOLD Prepare FI postings to hold data
JV_PREPARE_JVAP_FROM_JVSO1 Preparation of JVAP amounts from JVSO1 (all ledgers, all currencies)
JV_PREPARE_SELECT_OPTIONS Prepare select options for billing threshold determination
JV_PREPARE_THRESH_UPDATE_HOLD Prepare  update of threshold table to hold data
JV_PREPARE_THRESH_UPDATE_REL Prepare  update of threshold table to release data
JV_PRICING_POST AM/MM Transfers – Update CRP Pricing
JV_PRINT_DUNNING_NOTICE FI Mahnen – Ausdruck eines Mahnbriefs (Open FI Interface)
JV_PRINT_DUNNING_WITH_SUBTOTAL FI Mahnen – Ausdruck eines Mahnbriefs
JV_PRODPER_PRESET Preset production period from document date
JV_READ_VENTURE_DETAIL Read venture detail data
JV_RECID_AFABE_GET Get table of recovery indicator
JV_RECID_AM Derive JV recovery indicator for AM posting
JV_RECID_DERIVE JV Exit routine for RI derivation in SAPLKAIP
JV_RECID_DERIVE_INTERNAL JV recovery indicator derivation for CO internal transactions
JV_REFRESH_JVAH_JVAP Refresh table JVAH and JVAP for cutback test run
JV_RETURN_T_JVAP Return table T_JVAP from JV-IM
JV_RI_IN_PERIOD_CHECK Allocation Exit Module Line Item Check
JV_RI_MANIPULATE Manipulate RI on sender and receiver records based on Mrule
JV_RI_REVERSE_IN_PERIOD_CHECK Allocation Exit Module Line Item Check
JV_RI_TO_HRKFT_CONVERT Manipulate RI on sender and receiver records based on Mrule
JV_SETTLEMENT_PLAN_RI_GET_JV Get RI for plan settlement
JV_SETTLE_MRULE_MANIPULATE_JV Joint venture MRULE Pflege in settlement customizing – JV part
JV_SET_DUE_ON_DATE Set the baseline date or the due date for residuals/partial payments in AR
JV_SET_JVDATA_FOR_PART_RES Set venture, equity group, BI, billing month and POM for Partials/Residual
JV_SET_LEDGER_CURR Set Currencies for all ledgers in JVSO1
JV_SET_LEDGER_CURR_TABLE Ledger Currency table population
JV_SET_T_JVAP Prepare table T_JVAP
JV_SET_VENTURE_FOR_RESIDUAL Set Venture Information to new open items from Residual/Partial Payment
JV_SHOW_CARRYING_PARTNERS Display the allowed values for the help processor
JV_STATUS_RESET_MESSAGE Joint Venture Error Message Handling – Collection of Messages
JV_T8JTPM_POST Update production month data
JV_UPDATE_T8J9A Joint Venture update t8j9a
JV_UPDATE_T8JU update changes to tables t8ju and t8jut
JV_UPDATE_THRESHOLD_FOR_HOLD Update threshold table to hold data
JV_UPDATE_THRESHOLD_FOR_REL Update threshold table to release data
JV_USER_EXIT_003 User Exit 3 as preinstallation on 4.6C
JV_VALUES_FOR_CARRYING_PARTNER Display of the possible entries per table field
JV_VENTURE_ACTIVE_CHECK Check if a venture is active
JV_VENTURE_FROM_ASSET Find Venture information from Asset number
JV_WRITE_MESSAGE Joint Venture Write Message – Writes Error Messages Generated by JV prgs.
JV_WRITE_MSG_TO_SPOOL Joint Venture Write Message – Writes Error Messages Generated by JV prgs.

Filed under JVA, SAP Enterprise Tagged with , ,

Configuration of Electronic Bank Statement (EBS) for MT940

December 3, 2011 Leave a comment

This article explains how to configure EBS (Electronic Bank Statement) in SAP for MT940 bank statement format.

The SAP MT940 format consists of a sequence of fields defined as follows:

Define MT 940 transaction code.

Following table shows MT 940 transaction codes which have been defined by bank officer and business user previously. Some more transaction code could be applied in SAP EBS configuration. It is better to include Debit / Credit identification during definition.

Define bank transactions.

Before configure EBS, we have to know several of daily bank transactions. This information usually is coming from business user who take care bank reconciliation. For example:

1.    Bank Incoming

2.    Bank Outgoing

3.    Bank Charges

4.    Bank Interest

For each bank transaction should follow with which GL account for posting.

Make Global Settings for Electronic Bank Statement

IMG → Financial Accounting → Bank Accounting → Business Transactions → Payment Transactions → Electronic Bank Statement → Make Global Settings for Electronic Bank Statement

Enter Chart of Accounts press enter

Configuration steps are follow:

1. Create account symbols.

Specify G/L accounts (such as bank, cash receipt, outgoing checks) to which postings are to be made from account statement.

You create account symbols instead of G/L account numbers. These are required for the posting rules in step 2

Examples: Bank Account; Outgoing checks; Incoming checks; Outgoing Transfers; Incoming transfers; Bank charges etc.

Enter a description in the text field

2. Assign accounts to account symbols.

Double click on Assign accounts to accounts symbol and click on new entries.

We have not assigned charges accounts, because we should ascertain from the business, to which GL account the charges are to be posted. This step has to be performed again for charges. Bank charges account is hard coded because this account is commonly debited for charges debited by all house banks.

3. Create keys for posting rules.

Double click on Create keys for posting rules field and click on NEW ENTRIES

1. Define an ID for each posting rule.

2. Enter a description in the text field.

Update the information as follows.

Click on save

 4. Define posting rules.

Double click on Define posting rules and click on New Entries

In this activity you create posting specifications for each posting rule. You use the posting specifications to specify how a certain business transaction (such as a check issued) is to be posted.

Posting specifications consist of one or two posting records Debit and Credit

5. Create Transaction type.

Double click on Create transaction type. Here we create the names and descriptions of the various transaction types we require. House banks that use identical lists of business transaction codes (external transactions) can be assigned to the same transaction type later.

Click on NEW ENTRIES and enter the required transaction types

Create the names and descriptions of the various transaction types you require.  In the present business scenario we go for MT940 and we require creating this transaction type here.

6. Assign external transaction type to posting rules.

Double click on Assign external transaction types to posting rules and click on new entries.

Here we assign the external transaction type of banks to our posting rules.

Bank Transaction Type (samples)

Banks generally have their own codes for various transactions. For example Mashreq bank is issuing statements with the following transaction codes

We need to have clarity from business on which transaction type should post with clearing or post only.

NCHK denotes check transaction and prefixed with D for debit (out going) and C for credit (incoming). Hence we need to create two variations while mapping these transaction types to our posting rules (one for Debit and the other for Credit).

From the point of view of business use, the external business transactions listed above use identical posting procedures and must therefore be assigned to the same posting rule.  The same posting rules can also be used for different bank details, even if different business transaction codes are used (if different file formats are used, for example).

Note:  Update the algorithm for bank transaction type which needs to be posted with clearing in EBS transaction.

7. Assign Bank Accounts to Transaction types.

Double click on assign bank accounts to transaction types and click on new entries.

Here we assign each of the bank accounts to a transaction type. You can specify a work list of G/L accounts. This enables you to search several bank sub accounts for open items that the system could not clear during posting of the account statement when you post process the account statement.

If you select the field No Automatic Clearing, an open item remains, even if the amount of the open item agrees with that in the account statement.

We assign our banks to a transaction type and, if required, to a currency class. The banks are identified by means of the bank key and the external account number.

Note: This transaction type MT940 shall be added to the bank accounts

8. Search string definition

When importing an electronic bank statement, the system identifies the business transactions and uses the settings you have already made to determine how each should be recorded. In most cases, the system uses the document number entered in the “note to payee” lines of the bank statement to determine the appropriate clearing transaction. For example, a cash receipt clears customer open items.

The information in the note to payee may be incomplete – for example, the first characters in the document number may be cut off or new characters may be added. The interpretation algorithm then reaches the limits and cannot find the appropriate document numbers. This means the document cannot be cleared and you must post- process the transactions manually.

In addition to the search for clearing information, you can use the the search string to fill other fields (such as the cost center or posting rule, depending on the content of the note to payee.

It is the “Target Field” which determined which field is filled in each case. The target field in the bank data store indicates to where the result of the search is written. The target field must always be the note to payee when you are searching for clearing information (document number, reference document number. (Unlike other fields, it is not necessary to repeatedly change the note to payee field – the information in it is temporarily “enriched” while the interpretation algorithm is running.) The explanations and examples that follow all refer to the search for clearing information (meaning that the note to payee is the target field), but they can also be applied to most other fields (such as “Cost Center”; see the section on “Other Target Fields”).

To increase the number of hits in the document number search, you can use this step to define strings for the search. The system uses this string to conduct the search before the interpretation algorithm comes into effect.

Note: Please check length of cheque number for each company code which use EBS functionality. It may different with 7 digits length as configured above.

9. Assign Search String to Interpretation Algorithm

•Go back and double click in the tree Note-to-payee search string

•Choose New entries.

•Enter the company code, house bank, account, interpretation algorithm, and a name for the string.

•If you leave all or one of the fields Company code, House bank, or Account , the system uses the specified search string to search in all company codes, house banks, and/or accounts.

•If you want to use the string in the document number search, select Active and “Note to Payee” as the target field.

Enter a mapping basis if required. Select the ID indicator if required.

10. User exit

This exit will remove original note to payee of bank file with “TRANSACTION TYPE” and “CHEQUE NUMBER” as new note to payee.

Example:

Original MT940 file recognize “NONREF” as note to payee value for both line

:20:0000000000511286

:25:0493134965

:28C:175/1

:60F:C100608AED341400,35

:61:100103C499601,350NCHK0000431268      //NONREF

:61:100103D158201,000NCHK0000008760      //NONREF

:62F:C100608AED682800,70

After run this exit, new note to payee become “NCHK0000431268” for first line and “NCHK0000008760” for second line.

11. Default Cost Center for Bank Charges

Maintain OKB9 per company code.

Hope you get it clear, for further discussion please send a comment or email me.

Filed under Finance Controlling, SAP Enterprise Tagged with , , , , , , , ,

Understanding MT 940 bank statement format [EBS-1]

July 31, 2010 Leave a comment

The MT940 (MT = Message Type) electronic account statement is an international standard that was developed by S.W.I.F.T. in Brussels for the paperless transmission of account information. This standard is used by banks all over the world. In particular, MT940 is used to provide bank information to clients’ cash management, treasury systems and accounting applications.

  • Structure

Each message is divided into four blocks. Blocks 1, 2 and 3 relate to header information, and Block 4 contains the text of the message or Bank Account Statement. Each block is subdivided into a number of fields and each field contains particular information, for example, date, time, LT address, Session Number, ISN, or a tag number followed by the appropriate variable content. All fields within blocks 1 and 2 are of fixed length and are continuous. Block 3 is optional and may be used for user-to-user messages. No field separators are used. The content of Block 4 differs depending on bank in terms of which optional fields are used.

Block structure

Block Name Example of Content
1. BASIC HEADER BLOCK {1:F01NDEASESSAXXX0833510237}
2. APPLICATION HEADER BLOCK {2:O9400325050701NDEANOKKBXXX12706189060507010325N}
3: USER HEADER BLOCK {3:108:34}
4. TEXT BLOCK / Account Statement {4:<CrLf>
:20:VR06314330391601<CrLf>
:25:60030631433<CrLf>
:28C:123/1<CrLf>
:60F:D100405USD6000000,00<CrLf>
:61F:100320C9860,030NCHK0000033322      //NONREF<CrLf>
:61F:100331D9860,030NINT1700000348      //NONREF<CrLf>
:62F:D100405USD6000000,00<CrLf>
  • Account statement format

Now we focus on block number 4, which are contain of bank transactions captured in bank account statement. The message type consists of a sequence of fields or Taq Type. Each tag type gives important message to the customers system. It contains to bank account number, date of transaction, statement number, opening and closing balance and reference bank transactions information. Detail of taq type, meaning, and example of information defined as follows:

Tag Type Meaning SIF Field Description SWIFT content / format SWIFT status Information Reported
20 Transaction Reference Number :20: Statement Date 16x Mandatory Always = YYYYMMDD Eg. 20041231
25 Account Specification :25: Account Identification Bank ID/account number 35x Mandatory Eg. LT527300010002245349LTL
28C Statement Number/Sequence Number :28C: Statement and/or sequence number 5n[/5n] Mandatory From the statement date; YYYY-1980 and Julian date, therefore 15th July 2004 reads as 20196 – (where 20 refers to the year and 196 = Julian date 15/07) “/01″ eg 20196/01
60F Opening Balance :60F: Opening Balance 1!a6!n3!a15d Mandatory D for Debit or C for Credit

Date (YYMMDD)

Currency Code

Opening Balance with a comma as the decimal point
61 Statement Line (one per transaction) :61: Statement line field 6!n[4!n]2a[1!a]15d1!a3!c16x[//16x]

[34x]

 Optional A statement line field is produced for each transaction.

This field is sub-divided as follows:

• Date – YYMMDD

• Date – MMDD

• Debit/Credit mark – ‘D’ Debit, ‘C’ Credit, ‘RD’ Reverse Debit, ‘RC’ Reverse Credit

• Funds code – ‘X’

• Transaction amount

• Transaction type identification code: ‘NCHK’ for cheques, ‘F’ plus TLA for other transaction types

• Account owner reference

  • Cheque number for cheques, or transaction type for other transaction types

• Originating bank’s own reference ‘//’

• Supplementary details: Not applicable
86 Information to Account Holder :86: Information to account holder 6*65x Optional For Credit transactions:

Payer: /<Payer’s account number> <Payer’s name> /ID/<Payer’s register No> Payer bank : <Payer’s bank code (SWIFT code)> Details: <Payment details>

ForDebit transactions:

Beneficiary: /<Beneficiary’s account number> <Beneficiary’s name> /ID/<Beneficiary’s register No> Beneficiary bank : <Beneficiary’s bank code (SWIFT code)> Details: <Payment details>

Default business code – 999/

Posting text to follow – 00

Transaction details – CHEQUE or transaction code eg.

:86:999/00CHEQUE or

:86:999/00STOJSMITH
62F Closing Balance :62F Closing Balance 1!a6!n3!a15d Mandatory D (Debit) or C (Credit)

Date – YYMMDD

Currency code

Amount, with a comma marking the decimal point
  • Define MT 940 transaction code.

Each bank transaction is identified by transaction code in MT 940 block number 4 and tag type 61. Each bank has different meaning to utilize each MT 940 transaction code. Client / business user should get the information and knowledge from the bank how to define each transaction code related with its bank transactions that written in MT 940 bank statement format. Following table shows some MT 940 transaction codes have been defined by bank officer and business user. Some other transaction codes may been used in other case.

Code Description
NBOE Bill of exchange
NCHG Charges and other expenses
NCHK Cheques
NCOL Collections
NCOM Commissions
NDCR Documentary credit
NDIV Dividends-Warrants
NECK Eurocheques
NEQA Equivalent amount
NFEX Foreign exchange
NINT Interest
NLDP Loan deposit
NMSC Miscellaneous
NRTI Returned item
NSEC Securities
NSTO Standing order
NTCK Travelers Cheques
NTRF Transfer
NMAR Securities Related Item – Margin payments/Receipts
NBOE Bill of exchange
NCLR Cash letters/Cheques remittance
NVDA Value date adjustment
NCMI Bank collection

We have learnt structure of MT 940 bank statement, bank account statement format, and MT 940 transaction codes.

Filed under SAP Enterprise, Finance Controlling Tagged with , ,

← Older posts

Follow

Get every new post delivered to your Inbox.