I LOVE SAP

Blog for SAP BASIS Knowledge sharing

Background Job

Posted by Della on June 23, 2009

Job name   –> Program  –> Variant  –> Repeat interval

*** SAP_REORG_JOBS  –>  RSBTCDEL2  –> yes  –> daily

*** SAP_REORG_SPOOL –> RSPO0041/1041   –> yes  –> daily

*** SAP_REORG_BATCHINPUT  –> RSBDCREO  –> yes  –> daily

*** SAP_REORG_ABAPDUMPS  –>  RSSNAPDL  –> yes  –> daily

*** SAP_REORG_JOBSTATISTIC  –> RSBPSTDE   –> yes  –> monthly

***SAP_COLLECTOR_FOR_JOBSTATISTIC  –>  RSBPCOLL    –> no  –> daily

*** SAP_COLLECTOR_FOR_PERFMONITOR  –> RSCOLL00  –> no  –>  hourly

*** SAP_COLLECTOR_FOR_NONE_R3_STAT –>RSN3_STAT_COLLECTOR –> no  –>  hourly

***SAP_REORG_PRIPARAMS  –>  RSBTCPRIDEL   –> no  –>  monthly

***SAP_REORG_XMILOG  –> RSXMILOGREORG   –> yes –>  weekly

*** SAP_CCMS_MONI_BATCH_DP  –>  RSAL_BATCH_TOOL_DISPATCHING  –> no –> hourly

*** SAP_SPOOL_CONSISTENCY_CHECK  –> SPO1043  –> yes –> daily

*** SAP_REORG_ORPHANED_JOBLOGS  –> RSTS0024  –> yes  –> weekly

Posted in background job | Tagged: | Leave a Comment »

Backup Mode

Posted by Della on June 23, 2009

Here is a brief description about Full Backup, Incremental Backup, All Backup

backup_mode = full
This is a full database backup. It is also referred to as a level 0 backup. This backup contains all database files (for offline backup, as well as the online redo log files) and is used as the basis for your following incremental backups.

backup_mode = incr
This is an incremental database backup. It is also referred to as a level 1 backup. This backup contains only the Oracle blocks of all database files that have been changed since the last full backup (for offline backup, as well as the online redo log files).

Compare:
backup_mode = all
This is a whole database backup. This backup contains all database files (for offline backup as well as the online redo log files), yet it cannot serve as the basis for your following incremental backups. Therefore, the scope of the backup is the same as a full backup. The main difference to a full backup is that a full backup is additionally flagged as level 0 in the Oracle control file.

Full backups and whole backups are referred to as complete backups.
Partial (backup_mode = <Object_list>) and whole backups (backup_mode = all) are also referred to as normal backups because they cannot be part of an incremental backup strategy.

Normal and full backups can be performed with or without RMAN (see init<SID>.sap parameter tape_copy_cmd or disk_copy_cmd). Incremental backups are always performed with RMAN.

Posted in Backup | Tagged: , , | 1 Comment »

How to know to know Kernel Version

Posted by Della on June 23, 2009

Here is the step by step how to know the kernel version on your SAP System

click system - status

click system - status

click arrow button beside navigate button

click arrow button beside navigate button

see Kernel Information

see Kernel Information

Posted in Patches | Tagged: , , , | Leave a Comment »

/sapmnt/SID full –> again???

Posted by Della on June 8, 2009

On Friday (June, 5 2009) when I check file system on our CI server, I saw that our sapmnt/CAP almost full (againnn??), only 5% left 😦 … and then I check our background job for SAP_REORG_JOBS to check what program that running this job, because this job supposed to delete old jobs.

The ABAP program that runs SAP_REORG_JOBS is RSBTCDEL!
Then I try to create the new one (in sm36) with RSBTCDEL2 program, but the step in sm36 couldn;t continue until you fill the variant for this jobs.

Today I found the website about how to create variant for RSBTCDEL2. Here it is how to create variant

Posted in Log File | Tagged: , , , | Leave a Comment »

check 32/64 bit

Posted by Della on May 26, 2009

to check 32/64 bit, do the following
on /sapmnt//exe and then execute the following command:
file disp+work

the result will show you if its a 32bit or 64bit. Like below
disp+work: 64-bit XCOFF executable or object module not stripped

Posted in Others | Tagged: , , , | 2 Comments »

Oracle Log and Trace Files

Posted by Della on May 13, 2009

Oracle generates some log files and alerts that can make your file system full
When I googling about that, I found this usefull link Maintenance Log dan Trace File

Here is a short description about oracle logs and trace files:
1. Alert Log –> File name : Alert_SID.log –> Location : /oracle/SID/saptrace/background
consist of instance activity (startup, shutdown, switch logfile, parameter change, error, etc).

2. Trace File –> File name : *.trc
record system or user activity.
System Trace –> Location : /oracle/CAP/saptrace/background
User Trace –> Location : /oracle/CAP/saptrace/usertrace

3. Core dump file
Like core dump in OS, if there is a configuration error such as storage accessibility
Location : /oracle/SID/saptrace/background

4. Audit file –> file name : ora_OSID.aud
contain of connection history from user sysdba and user audit activity for AUDIT_TRAIL=OS

5. Network log –> file name : listener.log
Location : /oracle/SID/102_604/network/log

Posted in Log File | Tagged: , , , , , , | 1 Comment »

/sapmnt/ full

Posted by Della on May 7, 2009

Today when I check our QA File System, it shows that sapmnt/CAQ 96% used. Wooow… what should I do??

As I remember, we have faced the same problem before but I forgot what do we do to resolve the problem (I just remember that I’ve deleted some old jobs located under /sapmnt/CAQ/global
Then I start googling with the keyword /sapmnt/ full and then my eyes catch this link http://madhutekur.wordpress.com/2008/08/17/housekeeping-on-sapmntglobal

so I read what the recommendation for my problem.
And he suggest to running report RSBTCDEL2 in se38. Here is the complete sentences “The global directory contains the job logs. Old job logs can be deleted by running report RSBTCDEL2 in se38”

suddenly I remember that my friend used to do that also 😀

so I run that report and violaaa.. my file system now decreased until 49% 😀

Posted in Log File | Tagged: , , , , , , , , , , | Leave a Comment »

MM Training – Day 1

Posted by Della on November 11, 2008

Mulai kemaren (10 Nov) sampe 14 Nov nanti gua ikutan training MM di CA.

Berikut ini gua summarize apa yang gua dapet di hari pertama

Note : kemaren, kebanyakan sih bahas bisnis prosesnya yang ada di CA dan dari bahas dan diskusi dengan trainernya keliatannya untuk production akan sangat bagus kalo modul PP di jalankan. Karena dengan dipakainya modul PP maka production bisa di manage dengan lebih baik lagi, dari mulai ketersediaan barang, pemesanan barang, pemilihan vendor dsb.

Berikut adalah sedikit tentang Procurement Cycle:

Procurement Cycle dimulai dari

Reqr. Determination –> Determination of source supply –> Vendor Selection –> Order Processing –> PO Monitoring –> Goods Receipt –> Invoice Verification -> Payment Processing

Kemaren kita nyoba input :

1. PO (Create Order) –> tcode = ME21N

Logistic-Materials Management-Purchasing-Purchase Order-Create-Vendor/Supplying Plant Known


Create Order (ME21N)

Create Order (ME21N)

Yang di isi cuma Vendor, Material, Qty, Plant, Storage Location, Net Price (kalo belum ada).

Delivery Date bisa terisi otomatis jika PI Delivery Timenya sudah di maintain

Setelah isi data2 yang di perlukan simpan PO tersebut, system akan otomatis mengcreate PO Number

Untuk bisa melihat PO yang pernah kita buat, klik Document Overview On, lalu klik gambar gambar1

lalu pilih My Purchase Order

* Kalau mau create order berdasarkan PR yang pernah kita buat, klik Doc. Overview On, klik Variant-My PR -> lalu drag to basket

Untuk tau status PR (apakah sudah di PO atau belum) bisa melalui tcode ME53N lalu klik Tab Status

2. Goods Receipts –> tcode = MIGO

Logistic-Materials Management-Inventory Management-Goods Movement-MIGO

migo

Di MIGO cuma jangan lupa kasih flag Item OK di bagian bawah, lalu save

3. Invoice Verification –> tcode = MIRO

miro

Beberapa tcode penting :

Untuk melihat dokumen2 yang pernah di buat (PO, GR, Invoice Verification) bisa di lakukan dengan tcode :

ME2N –> Purchasing Document per Document Number atau

ME2L –> Purchasing Document per Vendor

ME2N

ME2N

Ada field Selection Parameter, untuk menyeleksi dokumen yang mau di print, misalnya hanya mau menampilkan dokumen-dokumen yang belum di Invoice (baru sampai GR), maka pilih RECHNUNG di selection parameter

selection_parameter

Outputnya adalah sbb:

ME2N - Output

ME2N - Output

Atau kalau mau liat status PO yang kita buat sudah sampai mana (GR or Invoice) bisa melalui tcode ME23N, klik Item(dibawah) lalu klik Tab Purchase Order History

ME23N - Display PO History

ME23N - Display PO History

Untuk melihat status PR sudah sampai mana (sudah di PO, RFQ dll) bisa dilakukan melalui tcode ME53N, lalu klik tab Status

ME53N - Display PR Status

ME53N - Display PR Status

INPUT MASTER DATA

1. Input Vendor

ada 2 tcode :

a. MK01 –> tidak ada accounting data –> Logistic-Purchasing-Master Data-Vendor-Purchase-Create

b. XK01 –> lengkap dengan accounting data –> Logistic-Purchasing-Master Data-Vendor-Central-Create

(wah, ini windows inputnya banyak benerrrrr… mm… liat halaman 60 aja dah di handbooknya :p)

2. Material Master Record –> MM01

MM01 - Material Master Record

MM01 - Material Master Record

di Material Master ini banyak banget yang bisa di maintain, bisa di liat di windows Select View.

Tapi ga semua harus di maintain, disesuaikan saja dengan bisnis proses perusahaan dan modul yang digunakan.

When creating a new material master record, you must choose a material type and an industry sector to which the material is to be assigned.

Materials with the same properties are assigned to the same material type. Examples of material types are raw materials, semifinished products, and finished products.

Among other things, the material type controls:
• The type of number assignment (internal or external)
• The permissible number range intervals
• Which screens appear and in which order
• Which user-department-specific data is suggested for entry (in views)
• Which procurement type is allowed for a material (that is, whether the material is produced in-house, procured externally, or both)

Along with the plant, the material type determines:

1. a material’s inventory management requirement (whether quantity changes are continuously
recorded in the material master record and/or value changes in the stock
accounts of financial accounting).

2. which accounts are posted when a receipt of a material into (or an issue from) the warehouse is
booked.

The data stored in the material master record is required for many purposes, including the following:
• Purchasing data is required for ordering purposes
• Inventory management data is needed to post goods movements and carry out physical inventories
• Accounting data is required for material valuation
• Materials planning data is needed for material requirements planning

Berikut adalah contoh pengisian MRP untuk Material Master

Material Master - MRP View

Material Master - MRP View

MRP Type ada banyak, tapi kalau PP modul belum di jalankan dan atau jika material ini adalah consumption based, maka biasanya di gunakan type V1-Manual reorder point with external reqs dan VB-Manual reorder point planning

Kemudian isi field Reorder Pointnya, jika stock dari material tersebut sudah mencapai reorder point, maka jika di jalankan MRP di MD01, MD02 or MD03, maka otomatis akan create PR dengan quantity sebanyak lot size (lihat penjelasan di bawah ini mengenai lot size)

MM01 - Lot Size Data

MM01 - Lot Size Data

Lot Size juga banyak tipenya, beberapa penjelasannya adalah sbb:

FX-Fixed Order Quantity

–> PR akan mengenerate qty sebanyak angka yang di masukkan pada field Fixed Lot Size

HB-Replenish to maximum stock level

–> PR akan mengenerate qty sebanyak angka yang di masukkan pada field Maximum Stock Level

Untuk melakukan perubahan secara berbarengan dapat dilakukan dengan tcode MM17

MM17 - Mass Material Maintenance

MM17 - Mass Material Maintenance

Posted in Functional Module | Tagged: , , , , , , , , , , , , , , , , , , | 7 Comments »