Dalam postingan kali ini kita tidak membahas tentang bagaimana jalannya seminar tapi our experience on journey to pekanbaru . Perjalanan mulai dari padang, bukit tinggi hingga sampai di pekanbaru hehehe…

Berangkat sore hari sekitar jam 15.00 dari kota padang sudah cukup sore buat kami dan alhamdulillah tidak ada kemacetan yang berarti diperjalanan, awalnya kami memilih rute dari pinggiran kota padang menyusur melewati solok, tapi kami mengubah haluan karena sesaat setelah melewati indarung keatas sedikit, terjadi kemacetan yang luar biasa, mumpung masih belum terjebak terlalu lama, kami memilih untuk memutar dan lewat bypass menuju padang panjang dan bukit tinggi, di bukit tinggi waktu sudah menunjukkan waktu sholat maghrib, kami berhenti sejenak untuk sholat maghrib, dan tidak lupa untuk foto2 narsis sebentar di jam gadang. Karena kata orang-orang, kalau ke sumatra barat belum mampir ke bukit tinggi dan berfoto di jam gadang belum dianggap pernah ke sumbar hehehe… ada2 saja, yalah… biar dianggap pernah kesini, maka kami foto2 narsis sebentar hehehehe…

Setelah puas foto2 di jam gadang, kami melanjutkan perjalanan ke pekan baru, karena perjalanan masih sangat panjang, sekitar 6 jam lagi dari kota bukit tinggi. Kami masih harus melewati jalan yang berbukit2 di tengah malam, melewati kelok sembilan yang terkenal dengan tikungan/kelok yang sangat tajam. Sayang sekali kami tidak bisa mengabadikan gambar dari kelok sembilan karena hari sudah sangat gelap sekali dan tidak mungkin bagi kami untuk berhenti ditengah jalan yang tikungannya sangat curam ini, takutnya nanti ada mobil dengan laju kencang yang tidak melihat keberadaan kami dan tertabrak, daripada mengambil resiko tersebut, kami putuskan untuk lanjut saja.

Tepat pukul 24.00 kami sampai di pekanbaru, dan yang pertama kami pikirkan adalah tidur , perjalanan panjang yang melelahkan walaupun saya hanya duduk dikursi penumpang apalagi yang gantian nyetir, machmud dan agung ^^, thank ya bro… hehehe… yah akhirnya tidur untuk mengumpulkan tenaga untuk seminar siang harinya.

Bangun pagi2, mas oki yang notabene adalah orang pekanbaru langsung dijemput istrinya yang mungkin sudah kangen berat ditinggal pergi terus *piiis kii… pulang lah dia bersama istrinya *mikir, mau apa mereka dirumah yah wkwkwkwkwk…

Sambil menunggu siang untuk presentasi, kami jalan2 dulu keliling kota pekanbaru tp sayangnya kali ini tanpa oki yang pulang kerumah dan agung yang sedang sibuk menyiapkan bahan presentasi nya yang masih belum selesai. dan wooow… sangat terkejut dengan kondisi kota pekanbaru sekarang, tata kota dan bangunannya sudah sangat maju, perkembangan pesat ini tidak lain didukung oleh banyaknya perusahaan2 asing dan investor yang menanamkan modal didaerah riau ini, pemerintah kotanya juga sangat responsif dalam melakukan pembangunan, beberapa bangunan yang menarik perhatian kami adalah gedung perpustakaan kota dan kantor gubernur, sangat indah, gedung perpustakaan daerah nya sangat menarik, berbentuk seperti buku, bisa dilihat di gambar dibawah ini.

Bentuk kantor gubernur Riau juga sangat unik, atap nya berbentuk seperti kapal, kalau saya melihat seperti itu, tapi design aslinya saya kurang tau itu menyerupai apa, tapi yang jelas sangat menarik, daerah2 lain harus meniru Riau dalam tata kota dan bangunannya.

Dan akhirnya seminar pun dimulai ^__^

Dan dalam perjalanan pulang dari Poltek Caltex ini waktu sudah menunjukkan waktu sholat maghrib, kami melewati masjid agung kota pekanbaru, kami sholat disitu sebentar dan foto2 disana, hehehe… tetep aja narsis nya , maklumlah, masjid dikota ini begitu megah dan indah.

In going through our SAP Treasury Management Workstation implementation project we’re building a list of important Treasury Management T-codes.  I’m putting these down so I don’t forget them, so this isn’t a how-to (maybe later  ):

FF.5 – Upload Electronic Bank Statements

Use FF.5 to upload electronic bank statements.  You can upload your Prior Day and Current Day statements here.

FF.6 – View Bank Statements

Use FF.6 to view bank statements.

FF6B – Memo Records: List

This allows you to view and to “Convert”  or archive off the memo records that are not set to automically archive off.

FF7A – Cash Management and Forecast

Use FF7A to run your Cash Position or Liquidity Forecast reports.  From within these, you can Create Memo records.  Click the Create “Single Record” button.

FF67 – Process Manual Bank Statements

Use FF67 to process Manual bank Statements.  Click the Overview button to show a list of your accounts, and you can drill in to see the statements.

FEBAN, FEBA_LOCKBOX, FEBA_BANK_STATEMENT – Bank Statement Post-Processing

Use FEBAN for Post-processing of bank statements (FEBA_LOCKBOX and FEBA_BANK_STATEMENT are t-codes specific to either Lockboxes or regular Bank Statements).  This allows you to make GL account or other corrections and post the transactions that didn’t go through on the initial upload.  On the initial selection screen, you can just skip the selections and it will show you a tree of your House Bank IDs and it will mark entries that didn’t post with the Red dot icon .

SE38 – program RFEBKA40 – Post Memo Records

This will post memo records of your current day statements (you upload them through FF.5) so that they will show up in your Cash Position and Liquidity Forecast reports.

SE38 – program REFBKA96 -  Delete Bank Statements

Use RFEBKA96 to delete Bank Statements!  Be very careful!  This only deletes the statements, not the GL postings (you’ll have to reverse those some other way like in FB03 or FB08). You don’t have to enter anything into the selection screen.  Once you’re in, click the Delselect All.  Then manually (check the checkbox) select the statement(s) you want to delete.

OT83 – Configuration t-code for BAI codes, Account Symbols, and Assigning Bank Accounts

There are several functions under OT83. Here you create Account symbols and assign them to GL accounts. The functions also include Creating Posting Rules and posting Keys and assigning External Transaction Codes (BAI codes).

FI12 (also see FBZP) – Configure House Banks and Bank Accounts

The primary t-code for creating House Banks and their Bank Accounts. Here, they are assigned to Company Codes, GL Accounts, currency, etc.

FBZP – Payment Program Customizing

FBZP provides access to configuring:

• Company Codes
• Paying Company Codes
• Payment Methods in Country
• Payment Methods in Company Codes
• Bank Determination
• House Banks

DMEE – Payment Medium Workbench (PMW)

One of the requirements for Outbound bank payments is that you provide data in their specified file formats. While US Banks use the Fedwire network for wire transactions, they tend to have their own file formats. The DMEE Engine or Payment Medium Workbench allows you to configure custom file formats for these types of transactions. The PMW is accessed through t-code DMEE.

FDFD – Cash Management Implementation Tool

FDFD is a tool to help implement Cash Management and Forecasting. The 5 areas it touches are:

1. Activate Company Code
2. Vendor/Customer data
3. Data Setup
4. Data Reconciliation
5. Data Correction

Take a look at the Application Help for further details.

TBB1 – Treasury: Post Flows

Generates financial accounting transaction from various financial instruments – FX, Money Market, Derivatives, Securities. This would be where a payment of a long term debt would get placed into your Payment Requests GL Account, which would get picked up in your F111 payment runs.

FIBLAPOP – Vendors – Payment Request

If you want to make a Fedwire payment to a vendor, you can use FIBLAPOP to create the Payment Request. You will need to have the Bank information set up on the Vendor Master. (Note: it is a good idea to have the bank info on the vendor master configured as sensitive fields for security and control purposes.) This generates a payment request similar to what FRFT does…see below.

FRFT – Rapid Entry with Repetitive Code

Create Fedwire payments with repetitive codes. You can optionally set up Repetitive Codes with your banks or use them internally with SAP. These identify the payment information for specific payees. You will be able to change the amounts and instructions at the time you create the payments. Having the Repetitive codes provides significant controls you have around the business partners that are eligible to receive wire payments.

Creates payment requests based on the entries in the a Payment Request GL account that you would specify in your Parameter definition.

F111 – Automatic Payment Transaction for Payment Requests

Creates payments based on the entries in the a Payment Request GL account that you would specify in your Parameter definition. You would first create a Payment Request through t-code FRFT (using Repetitive codes) or RVND (free form payment requests), but due to controls issues, FRFT and repetitive codes are recommended.

s_p99_41000099 – Payment List

The Payment List report (s_p99_41000099) will show the details for an F110 Check or ACH Payment run. Enter the run date and the Identification and it shows the vendors and invoices that make up the proposal list for the specified proposal run.

FCHN – Check Register

FCHN will display the checks for a Payment Run.

Note: to view the checks online (as they would look in the print out), you can (if you have rights to view them) go to System > Own Spool Requests, and then look for the spool files that say something like “Accounts Payable Checks…”. You may not have access to this in Production (but you might). Also, this only lets you see spool requests you created.

FCKR – Cashed Checks

FCKR (program RFEBCK00) allows you to upload file containing Cashed Checks. These files may be called Check Encashment files or Check Reconciliation files. You can post these to the GL to clear your outstanding checks account. You can also generate a test file using program RFEBCKT0, but I’ve had trouble getting it to upload  .

S_P99_41000099 – Payment List

Shows all payments, not just checks like FCHN does.

Bonus – Tables for payment methods on vendor: LFB1

• SE16 and table LFB1 – gives you vendor data with Payment Methods
• Table LFA1 – gives you vendor name and address information

1a. Looking at MM and SD interaction first, take the scenario of a
third party order process.

This process uses a PO (which is sent to your vendor)

Also invoice verification is used further along the process to check
that the invoice you send to your customer is the same material
and quantity as that which the vendor sends to you
(but obviously shipped directly to your customer).

1b. Billing is an SD function.

But SAP needs to know, when processing a customer’s payment,
to which GL account the payment has to be processed.

For instance payment of a UK based material would be placed in
a different GL account to that of a non-UK based material.

Furthermore, a UK based customer may have a different GL
account to that of an Export customer.

This is configured in Account Determination.

2. ABAPers are there to essential do some bespoke development.
Your integration, or interaction, with them would be when specifying
the tables, fields, input fields, a simple process explanation, data
mapping (if doing an interface from one system to another) etc.

The link between SD and MM :-

1. When you create sales order in SD, all the details of the items are copied from Material master of MM.

2. MRP and availibility check related data is also taken from MM
although you control this data in SD also.

3. While you create inbound/outbound delivery with reference to a
sales order,the shipping point determination takes place with the
help of the loading group, plant data, shipping conditions etc.
This also refers to Material Master.

4. The material which you are entering in a sales order must be
extended to the sales area of your sales order/customer
otherwise you cannot transact with this material.There are many such links between SD and MM.

The link between SD and FI :-

1. Whenever you create a delivery with reference to a sales order,
goods movement takes place in the bacgground.
eg. In case of standard sales order, you create an outbound
goods delivery to the customer.

Here movement 601 takes place.
This movement is configured in MM. Also, this movement hits
some G/L account in FI.
Every such movement of good s hits some G/L account.

2. The accounts posting in FI is done with reference to the billing
documents (invoice, debit note, credit note etc) created in SD. Thus this is a link between SD and FI

3. Tax determination: In case of a tax determination also, there is a direct link between SD and MM

SD Integration points with other modules
SD module is highly integrated with the other modules in SAP.

Sales Order – Integration Points Module

•Availability Check – MM
•Credit Check – FI
•Costing – CO/ MM
•Tax Determination – FI
•Transfer of Requirements – PP/ MM

Delivery & Goods Issue –Integration Points Module

•Availability Check – MM
•Credit Check – FI
•Reduces stock – MM
•Reduces Inventory $– FI/ CO
•Requirement Eliminated – PP/ MM

Billing – Integration Points Module
•Debit A/R – FI/ CO
•Credit Revenue – FI/ CO
•Updates G/ L – FI/ CO

(Tax, discounts, surcharges, etc.)
•Milestone Billing – PS

Return Delivery & Credit Memo – Integration Points Module

•Increases Inventory – MM
•Updates G/ L – FI
•Credit Memo – FI
•Adjustment to A/R – FI
•Reduces Revenue – FI