第 128 页 / 共 337 页
2.1 QUESTIONS 113
c. You can assign more than one payment term to a customer/vendor master.
d. The document type determines the reversal document type.
103. State True or False for each of the following statements.
a. SAP R/3 always assigns document number in case of internal number range.
b. A purchase order creates an accounting document within SAP R/3.
c. You can see all linked documents in SAP R/3.
104. State True or False for each of the following statements.
a. An APP selects all vendors/customers to be paid.
b. An APP selects open items to be paid for defi ned customers/vendors.
c. An APP clears the open items, which are paid.
105. State True or False for each of the following statements.
a. You can block or remove any payment block in the payment proposal edit phase
of an APP.
b. You can remove a payment block from the vendor/customer master during the
APP edit phase.
c. Line items that can be paid are listed in the exception list.
106. An automatic payment run is identifi ed by run date and identifi cation.
(True/False)
107. As per best practice, the payment run date should be the current date.
(True/False)
第 129 页 / 共 337 页
114 CHAPTER 2 CERTIFICATION QUESTIONS AND ANSWERS
108. State True or False for each of the following statements.
a. A dunning program is meant for dunning of regular customers, not for a
one-time account.
b. You can assign more than one dunning program to a customer.
c. You can set the minimum limit for transactions to be dunned.
d. A dunning program posts dunning interest to G/L accounts.
109. A customer can have a maximum of nine dunning levels in a standard
SAP-delivered program. (True/False)
110. State True or False for each of the following statements.
a. You can calculate balance interest with interest type “P.”
b. You assign an interest ID to line items while posting a transaction.
111. State True or False for each of the following statements.
a. You can confi gure a fi nancial statement version up to 10 levels.
b . I n a G/L external number range, the G/L number can be more than
10 characters.
c. It is possible to reclassify a customer under a different group.
112. A doubtful receivable is a special G/L transaction. (True/False)
113. You can run foreign currency valuation only for customers or vendors,
not for G/Ls. (True/False)
第 130 页 / 共 337 页
2.1 QUESTIONS 115
114. State True or False for each of the following statements.
a. You can’t clear an open item by reversing it.
b. Profi t center accounting (PCA) is part of the FI module in mySAP ERP.
c. You can settle an IO to the G/L through external settlement.
115. State True or False for each of the following statements.
a. Depreciation posting happens through a batch input session in SAP R/3.
b. Depreciation posting happens through direct posting in mySAP ERP.
c. A transaction can be posted to G/L account, which doesn’t have company code
segment.
d. Even if a G/L account is blocked at a COA level, you can post it.
116. State True or False for each of the following statements.
a. You can select a reconciliation ledger while posting to a vendor.
b. Payment terms are company code dependent.
c. A down payment request clears open items in AP and AR.
d . W hen you are clearing a debit item with a credit item, the SAP system doesn’t
create a clearing document.
117. State True or False for each of the following statements.
a. The down payment due date is determined by the SAP solution.
b. The G/L master is a company code–dependent master.
c. You can have alphanumeric characters in an external number range.
d . A ll special G/L transactions are posted to the normal reconciliation account of
the vendor/customer.
118. State True or False for each of the following statements.
a. The company code is part of the line item information in an FI document.
b . Y ou can see document currency and company code currency during line item
display.
第 131 页 / 共 337 页
116 CHAPTER 2 CERTIFICATION QUESTIONS AND ANSWERS
119. R/3 stands for real-time three-tier architecture. (True/False)
120. The FI module in mySAP ERP consists of the GL, AP, AR, AA, and
PCA modules. (True/False)
121. A controlling area can be assigned to multiple operational concerns.
(True/False)
122. More than one purchase organization can be assigned to a company
code. (True/False)
123. Costing-based CO-PA shares tables with other CO modules. (True/
False)
124. The creation of company codes is an IMG activity. (True/False)
125. The selection variant helps to standardize selection criteria for repetitive
use. (True/False)
第 132 页 / 共 337 页
2.1 QUESTIONS 117
126. The credit control area provides integrated solutions for the SD and AR
components of SAP solutions. (True/False)
127. A company code can be assigned to an operating COA, country COA,
or group COA. (True/False)
128. The G/L account groups control number range and G/L master fi eld
status. (True/False)
129. The G/L account and primary cost element have a 1:1 relationship.
(True/False)
130. In addition to the standard hierarchy, you can have an alternative profi t
center hierarchy. (True/False)
131. Statistical order permits external settlement. (True/False)
132. The SD billing document generates an FI document. (True/False)
第 133 页 / 共 337 页
118 CHAPTER 2 CERTIFICATION QUESTIONS AND ANSWERS
133. A purchase order creates a commitment posting into CO if commitment
posting is active in the controlling area. (True/False)
134. An FI document has the following areas: header section, line item sec-
tion, and template areas. (True/False)
135. The FI document number range is assigned to document types. (True/
False)
136. Standard SAP delivered account types are A, D, K, M, and S. (True/
False)
137. Posting keys determine account types, debit and credit logic, and line
item fi eld status. (True/False)
138. In mySAP ERP, leading and nonleading ledgers will have the same fi scal
year variant. (True/False)
139. A normal fi scal year can have a maximum of 12 regular posting periods
and 4 special periods. (True/False)
第 134 页 / 共 337 页
2.1 QUESTIONS 119
140. Negative reversal posts a transaction with a negative sign on the same
side of the G/L account. (True/False)
141. The customer and vendor masters can only be created in the FI module.
(True/False)
142. The customer master is divided into four parts: (1) general data,
(2) company code data, (3) sales organization data, and (4) credit con-
trol area data. (True/False)
143. The employee tolerance limit determines the allowable line item toler-
ance limit for clearing open items. (True/False)
144. Posting keys determine the document types to be used while posting a
business transaction. (True/False)
145. The document type is company code dependent. (True/False)
146. Posting keys 01 and 11 are used for G/L posting. (True/False)
第 135 页 / 共 337 页
120 CHAPTER 2 CERTIFICATION QUESTIONS AND ANSWERS
147. The document date determines the posting period and fi scal year. (True/
False)
148. When you are creating the vendor master centrally, the system allows
you to create all segments of the vendor master. (True/False)
149. The house bank ID is always a numeric ID. (True/False)
150. When the controlling (CO) module is active, you can post an expense
without a cost object. (True/False)
151. In the standard system, the posting key 40 refers to G/L credit. (True/
False)
152. While posting to a one-time vendor, the user needs to enter vendor
information like vendor name, address, etc., at the line item level. (True/
False)
153. A parking document is always a balanced document, i.e., debits = credits.
(True/False)
第 136 页 / 共 337 页
2.1 QUESTIONS 121
154. A shortened fi scal year is always a year-dependent fi scal year. (True/
False)
155. In order to get the opening balance in a new fi scal year, you need to carry
forward GL, AR, and AP. (True/False)
156. A user can enter the currency transaction rate if the document currency
is different from the company code currency. (True/False)
157. The tax category dictates whether or not a tax code is required for a line
item. (True/False)
158. If you want to display a document line item based on the posting date,
then you should use short key “001.” (True/False)
159. All open item managed accounts should have the line item activated.
(True/False)
160. If line item management is activated, then you can drill down to the line
item level from the G/L balance. (True/False)
第 137 页 / 共 337 页
122 CHAPTER 2 CERTIFICATION QUESTIONS AND ANSWERS
161. In SAP R/3, you can post up to 999 line items in a document. (True/
False)
162. For AP, AR, and AA, you use reconciliation accounts, which are updated
through batch processing. (True/False)
163. Validation checks for conditions and updates the required fi elds. (True/
False)
164. For every G/L account, you should have a cost element. (True/False)
165. A company code should have one G/L account. (True/False)
166. For a reconciliation account, you should always set up an external num-
ber range. (True/False)
167. The fi eld status group is created at the company code level. (True/
False)
第 138 页 / 共 337 页
2.2 ANSWERS 123
168. Once you cross a posting period, the system closes the posting period
automatically. (True/False)
169. While posting to a vendor, you are selecting the vendor group and
vendor. (True/False)
170. A tax procedure is a client-level confi guration. (True/False)
171. A special G/L transaction always posts to an alternative reconciliation
account. (True/False)
2.2 ANSWERS
1. b 9. b
2. b 10. a, b
3. a-False, b-True 11. a
4. a-True, b-False 12. a, b, c
5. False 13. True
6. b 14. False
7. a-True, b-True, c-True, d-False 15. False
8. a 16. True
第 139 页 / 共 337 页
124 CHAPTER 2 CERTIFICATION QUESTIONS AND ANSWERS
17. False 49. Yes
18. False 50. No
19. False 51. No
20. False 52. Yes
21. False 53. True
22. False 54. a-True, b-True
23. False 55. a-True, b-False, c-False
24. a-False, b-True, c-False 56. a-False, b-False, c-False, d-False
25. False 57. a-True, b-True
26. a-False, b-True, c-False 58. a-True, b-False, c-False
27. True 59. 9 (Nine)
28. a-True, b-False 60. True
29. a-True, b-True, c-True 61. a-True, b-True, c-True
30. a-False, b-True 62. a-True, b-False, c-True, d-False
31. a-False, b-True 63. a-True (Up to 4.6C), b-False
32. a-False, b-True (After 4.6C)
33. a-False, b-True, c-False 64. a-True, b-False, c-True, d-False
34. c, d 65. False
35. a-False, b-False, c-True, d-False 66. True
36. a-False, b-True 67. True
37. a-False, b-False 68. False
38. a-False, b-True 69. True
39. b 70. True
40. a 71. False
41. a-True, b-True 72. True
42. a-False, b-True, c-False 73. True
43. a-False, b-False 74. True
44. a-True, b-False, c-False 75. True
45. a-True, b-False, c-False 76. a-True, b-False, c-True, d-True
46. a-False, b-True, c-True 77. a-True, b-True, c-False
47. False 78. True
48. False 79. True
第 140 页 / 共 337 页
2.2 ANSWERS 125
80. a-True, b-False, c-True, d-False 110. a-False, b- False
81. True 111. a-False, b-False, c-False
82. True 112. True
83. False 113. False
84. d 114. a-True, b-True, c-True
85. False 115. a-True, b-True, c-False, d-False
86. False 116. a-False, b-False, c-False,
87. True d-False
88. False 117. a-False, b-False, c-True,
d-False
89. True
118. a-False, b-True
90. True
119. True
91. False
120. True
92. False
93. False 121. False
94. True 122. True
95. True 123. False
96. a-True, b-False, c-False, 124. True
d-False 125. True
97. a-False, b-False, c-False, 126. True
d-False
127. False
98. a-True, b-True, c-True
128. True
99. a-True, b-True, c-True, d-False
129. True
100. a-True, b-True, c-True, d-False
130. True
101. a-True, b-False, c-True, d-False
131. False
102. a- Not always, b- False, c- False,
132. True
d-True
133. True
103. a-True, b-False, c-True
134. True
104. a-False , b-True, c-False
135. True
105. a-True, b-False, c- False
136. True
106. True
137. True
107. True
138. False
108. a-False, b-False, c-True, d-False
139. True
109. True
第 141 页 / 共 337 页
126 CHAPTER 2 CERTIFICATION QUESTIONS AND ANSWERS
140. True 156. True
141. False 157. True
142. False 158. True
143. False 159. True
144. False 160. True
145. False 161. True
146. False 162. True
147. False 163. False
148. True 164. False
149. False 165. False
150. False 166. False
151. False 167. False
152. True 168. False
153. True 169. False
154. True 170. True
155. True 171. True
第 142 页 / 共 337 页
3 I
SSUES AND
R
ESOLUTIONS
Chapter
A ticket is a generic name for claims made by the end user to technical support.
At the very least, the end user has to send an email with a description of the
issue, the transaction code, and the program or report name. There are some
applications available to manage these jobs, such as Quality Center from HP,
ClarifyCRM®, and ManageNow®, among others. The tickets usually have
a priority scale: T1 (meaning the issue must be handled the same day, T2,
T3, etc. The person in charge of each module for analysis and resolution
handles those tickets. If it involves configuration, when you have missing
e.g. cost center, currency or customized reports discrepancy or for third part
as ABAP developers for debug or include functionality. Depending on the
nature of the ticket and resolution, necessary code changes will be done in the
development server. Once the SAP team is satisfied with unit testing, changes
will be promoted to the quality environment for user testing acceptance. Once
changes are approved by the user, the SAP team deploys the changes in the
production environment.
This chapter presents issues that may arise while using SAP solutions and
discusses ways to resolve those issues.
3.1 SAP GENERAL
Issue No.: 1
The user is trying to create a vendor for a particular company code. In the initial
screen for the customer, the company code was set to the default and the user
is trying to create another company code.
F or rapid data entry, some important parameters such as company code and
controlling area are set as the default while setting the user profile. If the security
role allows, the user can reset or define his own parameters through transaction
127
第 143 页 / 共 337 页
128 CHAPTER 3 ISSUES AND RESOLUTIONS
code SU01. In transaction code SU01, you will find a Parameter tab; this is
where you make all default settings. Check the default value for parameter ID
BUK. If you don’t want any default values, remove them.
3.2 GENERAL LEDGER (G/L) ACCOUNTING
Issue No.: 2
T he user is not getting the drop-down list of G/L accounts that he defined through
FS00 while posting through transaction code FB50/F-02.
While entering a transaction, the user usually presses F4 to select a G/L account
from the chart of account (COA). The SAP R/3 system displays all available
accounts that are created for the desired company code and COA in question.
If the user is not getting the G/L account in the drop-down list, try one of the
following:
1. Check if the G/L accounts have been created in the company code you are
posting.
2. Make sure you have selected the correct company code in T-code FB50.
3 . T he drop-down has a personal list and a global list. If you are in the personal
list, switch to the global list.
Issue No.: 3
My client raised a PO at USD 13 for 50 qty. A goods receipt MIGO transaction
was done at that price. Now my client wants to do a MIRO transaction at USD
14 for 50 qty.
This situation can be handled in two different ways: (1) price difference or
(2) reversing MIGO and repost MIGO with correct price.
1 . A t the time of the MIRO transaction, you have an option to post a price
difference. In the MIRO transaction, enter the G/L account for price
difference and amount (i.e., $1).
2 . R everse the MIGO entry, make changes in the PO, then once again do the
MIGO and MIRO transactions.
Issue No.: 4
How can you add a new column in an open item clearing transaction with T-code
F-03? Right now you have a document number, document date, document type,
第 144 页 / 共 337 页
3.2 G/L ACCOUNTING 129
posting key, and amount. You need to add a posting key and amount in the
transaction fields in the screen.
1. Go to the Clearing G/L Account Process Open Item screen using T-code
F-03 from the menu bar.
2. Select Settings and C hange line layout .
3. Select the Create button.
4. Give the line layout a name and description, and press E nter .
5. Select the Insert after button to view the available fields.
6. Select the required field by double-clicking on that field. The required field
is automatically listed under your own layout.
7. Repeat the process for each field required to create your layout and save.
8 . G o back to the Clearing G/L Account Process Open Item screen, and select
the Editing option button under the line layout variant for the G/L account
clearing transaction.
9. Give your variant a name and save.
Issue No.: 5
The user wants to add a trading partner as selection criteria in the F-03 screen.
This does not come with the standard screen.
Y ou are using transaction code F-03 to clear open items for a particular
G/L account. While offsetting debit transactions with credits, depending
upon business requirements, the user will select one of the selection options
provided in that screen. The SAP R/3 system will pull all open items based on
the selection criteria. The standard SAP R/3 system comes with very limited
selection criteria; however, you can include a new selection field and change the
sequence of the selection criteria. To add a new selection field or change the
selection criteria sequence, you have to configure the SAP R/3 system through
transaction code O7F1.
Issue No.: 6
T here are a few G/L accounts where line item displays are not activated. The
client would like to see what entries are actually hitting these accounts.
T here are two possible solutions regarding this problem. SAP recommends the
first solution because only standard means are used. The second solution requires
the usage of a correction report and is therefore a consulting solution.
第 145 页 / 共 337 页
130 CHAPTER 3 ISSUES AND RESOLUTIONS
n Standard solution:
1 . C reate a new account and set the options according to your require-
ments. Be sure to set the line item display indicator (SKB1-XKRES).
2 . T ransfer the items from the old account to the new account. You can
only do this for accounts that you cannot automatically post to. As an
alternative, you can transfer the balance completely.
3. Lock the old account for postings.
n Consulting solution:
1 . M anipulate all documents that were posted in the past. You can use the
correction program RFSEPA01 (contained in the standard system as
of release 3.0D). Read the document carefully.
2 . F or releases prior to 3.0D, a corresponding correction program is
available on SAPSERV3.
W hile creating the G/L account, utmost care should be taken with the open
item management and line item management attributes of the G/L account.
Issue No.: 7
While creating G/L accounts, some of the G/L accounts were wrongly kept as
open item management. Now the user wants to remove open item m ana gement
functionality through transaction code FS02, but the system is giving the
following error message: “This account does not balance to zero.”
System Response:
You cannot switch the open item management specification on or off with this
transaction.
Procedure:
If you want to switch this function on retroactively for a certain account, you
should create a new account with the correct setting and use this to make a
transfer posting of existing items.
While creating the G/L master, you have to pay utmost attention to the setting
of G/L master attributes. The situation here is changing the attribute of G/L
accounts after posting the transaction. For this, you have two options:
n Standard solution:
1. Create a new G/L account.
2 . T ransfer the account balance from the old G/L account to the new G/L
account.
第 146 页 / 共 337 页
3.2 G/L ACCOUNTING 131
3. Switch off open item management for the old account and retransfer
the G/L balance from the new account to the old account.
W ithout making the account balance zero, you can’t switch an open item
attribute of a G/L account.
n Consulting solution:
As an alternative, the user could try program RFSEPA03, depending on his
SAP release. The user may have to copy the program to the “Z” program
and remove the piece of code that prevents its use. Before adopting this
procedure, make sure the user reads the program documentation and
related SAP advice.
FIGURE 3.1 RFSEPA03 correction report
Issue No.: 8
The client processed a bank statement and one of the line items in the bank
statement overview in transaction FEBA shows the status as “ Complete.”
However, the client used a wrong posting rule here. How can you change to
the correct posting rule and process the transaction again so that the status is
changed to “Posted”?
There are two ways to handle this situation:
n With a reverse bank reconciliation posting document.
n By deleting the bank statement from the SAP R/3 system. To delete
the bank statement, follow these steps:
1. In T-code SM38, enter RFEBKA95 and execute the program. It will
open the posted bank statement.
第 147 页 / 共 337 页
132 CHAPTER 3 ISSUES AND RESOLUTIONS
2. Deselect all and select the statement that is wrongly posted to delete it.
3. Repost the bank statement through T-code FF67.
Issue No.: 9
The user has posted the documents without a business area. Now he wants
to update them. You know that once a document is posted, the business
area cannot be changed in the document overview. How can you solve this
issue?
To update the business area, you have two options:
n With the help of ABAP, you can update the business area in the
posted document’s BSIS table.
n Or you could just reverse the original entry and repost the entry
with business all the necessary details.
It is advisable to use the second option.
Issue No.: 10
The user is posting monthly entries through T-code FBS1 and reversing them
on the first of the next month through T-code F-81. The user wants to automate
the reversal procedure.
SAP solutions do come with automatic reversal of accrual entries, but the user
has to execute transaction code F-81 for accrual reversal. Accrual entries are
made through transaction code FBS1. SAP R/3 includes functionality to enter
reversal dates while posting transactions. Once you are executing transaction
code F-81, SAP R/3 will provide a list of accrual entries to be reversed. Instead
of executing transaction code F-81 manually at an interval, you can create a
batch job with a suitable variant and schedule it.
Issue No.: 11
A company code was assigned to an alternative COA. While creating a new
G/L, the user keyed the alternative G/L in the G/L master. But while saving,
the following error occurred: “Alternative Account number already assigned
to account xxxxxx, cannot save.” What would be the reason and how can you
solve this?
第 148 页 / 共 337 页
3.2 G/L ACCOUNTING 133
The error is due to the assignment of the operating G/L account to the country
COA. You can’t assign multiple operating G/L accounts to one country COA
G/L account. The relation between the operating G/L and country COA G/L
is 1:1. When you are creating the G/L account with reference from some existing
account, the alternative COA is also copied here; however, the country COA
G/L is already assigned to an operating COA G/L account. This rule is not valid
for group COA G/L accounts.
Issue No.: 12
A fter a transaction was posted, the client learned that an account that was
classified as a balance sheet account should have been a P&L account. Now the
client wants to reclassify the G/L account. Is this possible?
T he reclassification of G/L accounts from a balance sheet account to a P&L
account or vice versa is possible. Here are the steps for such a conversion:
1 . Y ou can reclassify a G/L account when its balance is zero. So clear all open
items and bring your account balance to zero.
2 . T hrough T-code FS00, change the account type from a BS account to a P&L
account. In a standard SAP system, you will get an error message. Note the
message numbers.
→
3 . C hange the message control by following this menu path: SPRO Cross-
→ →
Application Components Bank Directory Change Message
Control (transaction code OBA5).
4. Enter FH in the Area box (note that this is just an example) and press E nter for
the next screen. In the New Entries: Overview of Added Entries screen, enter the
two message numbers from step 2 and set the message to W (for Warning).
FIGURE 3.2 Message control
第 149 页 / 共 337 页
134 CHAPTER 3 ISSUES AND RESOLUTIONS
5 . O nce you have completed step 4, reclassify your G/L account as mentioned
in step 2 This time, the system will issue a warning message and your account
will be reclassified once you save your changes.
6 . I f your books of accounts are closed for the previous year, run program
SAPF0110 to carry forward your balance to the new year.
The reclassification of G/L accounts is advisable at either the end or
beginning of the year.
Issue No.: 13
W hile analyzing accounts, the user found that certain document numbers are not
appearing or are missing. For example, number range 17 is assigned to document
type KA, which has the range 1700000000–1799999999 valid up to 9999. The
current status shows that the next available number is 1790000000. During
analysis, the user found that documents 1780000000–1780000010 are missing.
The user wants to know why document numbers are missing.
T here are several reasons for missing document numbers. Here are two scenarios
for this issue:
1. One possible reason could be that these documents were initially parked and
later deleted. In this case, those document numbers cannot be reused.
2. The documents probably don’t exist. SAP solutions will set aside numbers
for use when the system detects multiple document creation. If someone is
creating documents, the system will make available, for example, the next
10 numbers, “reserving them,” in essence. If the user only creates eight
documents, two document numbers will be missing.
Y ou may use the following programs/reports to find out the reason for the
missing documents:
n Program RFVBER00 provides a list of transactions that failed
while updating the database.
n Program RFBNUM00 shows gaps in the FI number range.
Issue No.: 14
What is ranking order in an APP?
第 150 页 / 共 337 页
3.3 AP 135
R anking order represents priority assignments to each house bank. This helps
the APP choose the house bank for payment in case there is more than one
bank account satisfying the payment program parameters.
3.3 ACCOUNTS PAYABLE (AP)
Issue No.: 15
The client printed 50 checks, of which 10 checks are spoiled or torn. Now the
client wants to reprint the checks using the same APP. Is this possible? Or do
you have to void those checks that are spoiled or torn?
There may be times when the payment run has successfully posted
payment documents and generated checks, but for some reason or other, the
checks are not valid. In this situation, you have to void all of the printed checks
and reprint them. To void and reprint, follow these steps:
1. Execute transaction code FCH7 . You may navigate to FCH7 through the
payment run.
2. Execute transaction code F 110 , enter the payment run ID and run date, then
→ → →
follow the menu path: Environment Check information Change
Reprint Check (t-codeFCH7).
3. Enter the following details:
n Paying company ode
n House bank
n Account ID
n Number of the check to be voided
n Void reason code
n New check number
→
4. Choose the path: Check Reprint from the menu.
Y ou must follow this process in a situation where you have issued checks,
but the checks are lost in post.
第 151 页 / 共 337 页
136 CHAPTER 3 ISSUES AND RESOLUTIONS
Issue No.: 16
W hile posting outgoing payments through T-code F-53, the client received the
error message ‘The entry 1210 is missing in table T043G’ and the system did
not allow the posting payment document.
T he SAP R/3 system returns this error when it doesn’t find vendor/customer
tolerance for your company code. In this example, you are processing an outgoing
payment for a company code for which the vendor tolerance group is not defined.
Create vendor tolerance through transaction code O BA3 (menu path: F inanc ial
→ →
Accounting A ccounts Receivable and Accounts Payable B usiness
→ → →
Transactions Outgoing Payments Manual Outgoing Payments
Define Tolerances (Vendors)) for your company code.
Issue No.: 17
A vendor has requested that charges for services and materials be paid through
separate bank accounts. For example, Vendor X supplies both services and
materials and maintains two bank accounts—one for services and another for
materials. The vendor requests that your client pay for services through bank
account XXXXX and materials through bank account YYYYY. Is this possible
when payments are made through an APP?
A vendor may have multiple bank accounts. The SAP system provides the
functionality to store and use information from multiple vendor bank accounts
in the Payment transactions screen of the vendor master general data via
transaction code FK03.
FIGURE 3.3 Vendor bank accounts
第 152 页 / 共 337 页
3.3 AP 137
You can use the BnkT (bank type) field in the vendor master to enter
text differentiators for identifying the vendor’s bank accounts. If you leave
the bank type field blank for a bank account in the vendor master, it serves
as the default bank if the bank type information is missing in the vendor
invoice.
In this situation, you maintain information on both banks through
the identifiers XXXXX and YYYYY. While entering the vendor invoice for
services, select bank identifier XXXXX and for materials, select YYYYY.
Now when you are paying through an APP, you will find you are remitting
payment to two different bank accounts for the vendor for different
services.
Issue No.: 18
A client posted a new document using T-code FBR2.Using T-code F110, payment
was also posted for this invoice.
A fter this transaction, it was found that the discount base was wrong and the
system had taken the value based on the reference document. How can you
reverse a payment posting and change the baseline date?
Y ou have posted a vendor invoice through transaction code FBR2.
This transaction code is used to post a new document with reference to an
existing document. While posting a new document through transaction code
FBR2, SAP R/3 will copy all of the fields from the reference document;
however, you can change whatever is needed. After having posted the vendor
invoice, you also processed payment for the said document. To correct the
baseline date, you have to correct the vendor document. Follow these steps
to resolve this:
1. Cancel the payment check via transaction code FCH8 (if the check is in your
possession). This transaction voids the check, resets the clearing process, and
reverses the payment document.
2 . R everse the vendor document and post a new document with the correct
discount base date.
Issue No.: 19
A user made an advance payment of INR 20000 through a special G/L transaction
and deducted withholding taxes, at 2% (Rs. 400.00). Later the user received an
第 153 页 / 共 337 页
138 CHAPTER 3 ISSUES AND RESOLUTIONS
invoice for Rs. 30000. Now the client wants to deduct withholding tax on the
balance amount, i.e., Rs. 10000, not on the entire amount. If the user uses T-code
F-43, it deducts the tax on the full invoice value of Rs. 30000, which is Rs. 600,
whereas the user wants the advance payment taken into account and wants to
pay Rs. 200 (Rs. 600–Rs. 400).
T he user needs to deduct the tax on the entire amount at the time of invoice
posting. While adjusting the advance payment against the invoice, the SAP R/3
system will reverse the tax you have deducted.
However, the user needs to make the following configuration in the payment
withholding type for this tax reversal to take place:
→ →
1. Follow the menu path: I MG Financial Account Global setting
→ → →
Withholding tax Extend withholding tax Calculation
→
Withholding Tax Type Define withholding tax type for payment
posting .
2 . S elect the withholding tax type. At the bottom is a Central invoice window,
in which the user will select the last radio button— Central inv. prop .
FIGURE 3.4 Configuring withholding tax
Issue No.: 20
The client needs to update a reference field in the header of a payment document
with the check number generated by the system. Is there any way to update the
payment document with the check number?
Normally, you follow this process when you have issued a check that is written
outside of the SAP solution. To maintain the check register, you have to update
the payment document with check numbers. You can achieve this through
第 154 页 / 共 337 页
3.3 AP 139
transaction code FCHU, which will update the payment document with check
information. Follow these steps:
1. Go to transaction code FCHU.
2 . F ill out the company code, house bank, and account ID areas and give the
check number and payment document number for which you want to update
the check number.
3 . N ow, in the Target field selection of the check number section, select the
field on which you want to update the check number.
4. Then execute.
FIGURE 3.5 Executing transaction code FCHU
Issue No.: 21
T he user wants to print a check for a vendor down payment. To use T-code F-58,
the system needs an open item. When the user makes an advance payment, there
will not be any open items in the vendor account.
T ransaction code F-58 is used to process payment for existing open items. This
transaction code can’t be used for processing advance payments. You have
two options to handle this situation: (1) create an advance payment request
第 155 页 / 共 337 页
140 CHAPTER 3 ISSUES AND RESOLUTIONS
and pay through an APP or (2) create an advance payment document through
transaction code F-48 and print a check through trans action code FBZ5. Here
are the steps for both options:
n Option 1:
1. Create a down payment request through transaction code F -47 .
2. Run the payment program through transaction code F 110 .
n Option 2:
1. Use transaction code F-48 for advance payment to vendors.
2. Based on the posted document number, print a check using transac-
tion code FBZ5 .
Issue No.: 22
T he user wants to make a check payment for petty expenses like stationery,
travel, etc. Transaction code F-02 provides facility to c apture check information.
Without check information, the user can’t do bank reconciliation. The user is
wondering if there is any workaround to deal with this situation.
The user can use transaction code F-53 with doc type GZ (General Payments).
In the Post Outgoing Payment: Header Data screen, the user has to provide
bank data and the check number in the assignment field. After entering this
information, the user can switch screens using F-02. To switch the screen, the
user must follow these steps:
→
1. From the system menu, choose Goto Document overview (as shown
in Figure 3.6).
FIGURE 3.6 Using transaction code F-53
2 . A fter selecting Document overview, the user will get a new screen, in
which he can enter expenses by entering the posting key and expenses G/L
accounts. For bank reconciliation, the user can choose internal algorithm
15 or 13 for the system to check the assignment field for check numbers.
第 156 页 / 共 337 页
3.3 AP 141
Issue No.: 23
While posting a transaction through T-code F-58, the user sees this error message:
“Changes for vendor XXXXXX not yet confirmed.”
In SAP R/3 configuration, you define certain fields as sensitive to have proper
control and tracking on master data changes. If the user changes these sensitive
field(s), someone other than the user who changed the master data has to confirm
these changes. Until such confirmation, the SAP R/3 system does not allow any
transactions with that trading partner. For example, you configure payment term as
a sensitive field. To accommodate business requirements, user XXXXX updates the
payment term with a new payment term ID. In order to carry out any transactions
with this business partner, the changes have to be approved by another user.
To confirm this change, the user has to use transaction code FK09.
Follow this procedure before executing transaction code F-58.
Issue No.: 24
I n transaction code F-33 (bills of exchange discounting), the user entered all data.
When this is executed, the user receives a message that A/C No. 400400 (Interest
account) requires an assignment to a CO object. What does this mean?
W hen a controlling area is active, the user has to assign a valid cost object while
posting expenses. In this case, bank interest is an expenses account, while posting
selects a valid cost object.
Issue No.: 25
The user has executed transaction code F110 to pay 50 vendors, but he only
has 20 checks left. Hence, when he ran the program, it printed the checks with
random numbers. Now the problem is he is unable to cancel the payments, as
there is no check number. How can he reprint or cancel the checks?
The check printing program generated more checks than there are available
check numbers. To handle this issue, follow these steps:
1. Before proceeding, ensure that you have maintained a new check lot through
transaction code FCHI. Be sure to correct your check lot before you do
anything.
2 . I n transaction code F110, enter the payment run ID and payment run date.
第 157 页 / 共 337 页
142 CHAPTER 3 ISSUES AND RESOLUTIONS
3. Go to the Printout/data medium tab and place the mouse curser on variant
field against print program.
→
4 . F rom the system menu, choose Environment Maintain Variants as
shown in Figure 3.7.
FIGURE 3.7 Using transaction code F110
5 . S AP R/3 will show the Maintain variant: XXXX screen, at the bottom of which
you will see the section shown in Figure 3.8.
FIGURE 3.8 Using transaction code F110
6. Select Void and reprint checks from payment run already printed .
This procedure will void all of the checks generated through this particular
payment program.
I f you want to void and regenerate a particular set of checks, enter the check
numbers you want to void along with a void reason code.
7 . S ave the variant and come back to the payment run screen. Click on
to generate the desired checks.
Issue No.: 26
The user defined multiple payments in the vendor master, i.e., “C” and “E.” As
per business requirements, if the business is paying $10,000 or less, the check
will be issued to the vendor. For a payment of more than $10,000, the business
will pay though wire transfer. As a FICO consultant, the user is looking to you
for guidance.
You can define multiple allowed payment methods for the vendor by assigning
the payment method in the vendor master.
第 158 页 / 共 337 页
3.4 AM 143
W hile configuring the payment program through transaction code FBZP,
you specify your allowable minimum and maximum dollar amounts for your
payment method in the Payment Methods in Company Code step.
FIGURE 3.9 Using transaction code FBZP
Follow these steps to resolve this issue:
1. Set the minimum to 0 and the maximum to 10000 for payment method “C.”
2. Set the minimum to 10001 and the maximum to any larger amount for
payment method “E.”
Issue No.: 27
It is not possible to post multiple customers in transaction code FB70. Can you
use F-21?
A fter starting with FB70 and making as many entries as you wish, if you need to
post to other customer accounts you can press F6, which switches you back to
the “old-style” data entry screen where you can post to as many other customer
accounts as you wish using the old “posting key” method.
3.4 ASSETS MANAGEMENT (AM)
Issue No.: 28
During data migration, the client forgot to transfer two assets whose book
values are zero. Now the client wants to bring those assets to the asset portfolio
for reporting purposes. The client needs both acquisition cost and accumulated
depreciation in FI, including information from the AM module. As the data
第 159 页 / 共 337 页
144 CHAPTER 3 ISSUES AND RESOLUTIONS
migration is already done and the company code in question is already in the Go-live
stage, how can you bring these two assets to FI—including the Asset module?
The solution for this ticket would be:
1 . S et the company code status to “1”Asset data transfer not yet
completed .
2. Update legacy data using T-code A S91 .
3 . E nter the acquisition cost and accumulated depreciation using T-code
OASV .
Issue No.: 29
T he user wants to transfer an asset from one asset class to another asset class.
A depreciation expense of the new asset class is assigned to another account
determination. The user wants to transfer APC, accumulated depreciation, and
depreciation expenses to G/L accounts that are assigned to the new asset class.
Transaction code ABUMN has fields for ACP and accumulated depreciation.
The user is wondering how depreciation expenses will be transferred from the
old accounts to the new account.
Through transaction code ABUMN, you can reclassify assets. In the
reclassification process, you can only transfer APC and accumulated costs to a
new asset class with immediate effect. Depreciation expenses will be transferred
to the new G/L when you run depreciation. However, during the depreciation
run, you can’t transfer previous depreciation expenses that were already charged
to the cost center. But you can transfer current-year depreciation to the new
depreciation expenses account. While entering the transaction in transaction
code ABUMN, enter in the value date field the date on which you want to
transfer your expenses to the new account.
Issue No.: 30
After the depreciation run, the user changed the capitalized date and the
depreciation start date in the asset master. After making changes in the asset
master, the user once again ran depreciation in “repeat run” mode. But changes
made to the asset master did not hit depreciation, and the difference value is
appearing as a planned value when checked in T-code AW01N.
I f you are making any changes in the asset master that affect depreciation that
is already posted, you must follow this procedure:
第 160 页 / 共 337 页
3.4 AM 145
1. Recalculate depreciation using T-code AFAR .
2. Repeat the depreciation run using T-code AFAB .
Issue No.: 31
While running the year-end closing process through transaction code AJAB, the
system gives the following errors:
“Asset is incomplete and has to be completed. Message no. AU083”
Diagnosis:
The asset 000000100001-0000 is marked as incomplete. The asset was created
by someone who did not have the ‘asset accountant’ asset view. When this is the
case, the system expects that certain required fields are not maintained.
Procedure:
You can add the necessary specifications using the master data change transaction
and the needed asset view.
T he system gives this type of error when the asset master was not properly
maintained. You can execute transaction code AUVA to get the list of incomplete
assets. After getting the list of incomplete assets, maintain the necessary data
for the asset master and rerun transaction code AFAB.
Issue No.: 32
The user wants to post a transaction in the year 2008 through transaction code
F-90. While posting the transaction, the system returns the following error:
“ You cannot post to asset in company code 9999 fiscal year 2008 M essage no.
AA347.”
Diagnosis:
“A fiscal year change has not yet been performed in Asset accounting for company
code 9999.”
Procedure:
Check the asset value date.
It looks like the user entered an asset acquisition in fiscal year 2008 for
company code 9999, for which the assets accounting (AA) fiscal year change
has not been carried out.