Notice
Recent Posts
Recent Comments
| 일 | 월 | 화 | 수 | 목 | 금 | 토 |
|---|---|---|---|---|---|---|
| 1 | 2 | 3 | 4 | |||
| 5 | 6 | 7 | 8 | 9 | 10 | 11 |
| 12 | 13 | 14 | 15 | 16 | 17 | 18 |
| 19 | 20 | 21 | 22 | 23 | 24 | 25 |
| 26 | 27 | 28 | 29 | 30 | 31 |
Tags
- List box
- Smart Forms
- ABAP
- SAP
- sapa
- 머니플랜
- 오라클 함수
- ole
- FI 용어정리
- EUC-kr
- Java
- 가계부
- 유닉스
- Standard Function
- gimp
- 엑소버드
- badi
- Enhancement
- 동적 쿼리
- UTF-8
- alv 정형화
- selection screen
- 스마트폼
- 이명박
- function
- ALV
- 방화벽
- EXIT
- KOSA
- fi
Archives
- Today
- Total
Drunken Lion
Business Transactions 본문
Business Transactions
Many of the actions that can change an order are defined in the system as business transactions. These business transactions are represented by a four-character key and a short descriptive text. Typical examples of business transactions are:
RKP1 Planning costs
KZPP Planned overhead (periodic)
KZPI Actual overhead (periodic)
BFRE Release
RFBU G/L account postings
RKU1 Reposting costs
RKL Activity allocation
KOAO Actual settlement
LVMS Set deletion flag
When you carry out such an action, the system checks whether the corresponding business transaction is allowed for the given order in the current status.
'SAP > FI' 카테고리의 다른 글
| FZ003 : Company codes &/& do not appear in proposal & &; correct (0) | 2011.08.23 |
|---|---|
| [FI] Taxes (FI-AP/AR) (0) | 2011.08.18 |
| Note 48121 - User Exits in Validations/Substitutions (0) | 2010.10.14 |
| GR/IR clearing 오류 발생시 대처 (0) | 2010.05.04 |
| How to implement screen exit for a SAP standard transaction (0) | 2010.02.12 |
'SAP/FI' Related Articles
more
