Issue No.: 1
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. At 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. Reverse the MIGO entry, make changes in the PO, then once again do the MIGO and MIRO transactions.
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. At 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. Reverse the MIGO entry, make changes in the PO, then once again do the MIGO and MIRO transactions.
Issue No.: 2
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.
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.
For 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 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.
|
Issue No.: 3
What is ranking order in an APP?
Ranking 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.
What is ranking order in an APP?
Ranking 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.
Issue No.: 4
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 F110, 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:
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 F110, 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:
- Paying company ode
- House bank
- Account ID
- Number of the check to be voided
- Void reason code
- New check number
4. Choose the path: Check → Reprint from the menu.
You must follow this process in a situation where you have issued checks, but the checks are lost in post.
You must follow this process in a situation where you have issued checks, but the checks are lost in post.
Issue No.: 5
While posting outgoing payments through T-code F-53, the client received the error message ‘The entry 1100 is missing in table T043G’ and the system did not allow the posting payment document.
The 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 OBA3 (menu path: Financial Accounting → Accounts Receivable and Accounts Payable → Business Transactions → Outgoing Payments → Manual Outgoing Payments → Define Tolerances (Vendors)) for your company code.
Issue No.: 6
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 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
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.
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.: 7
A client posted a new document using T-code FBR2. Using T-code F110, payment was also posted for this invoice. After 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?
A client posted a new document using T-code FBR2. Using T-code F110, payment was also posted for this invoice. After 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?
You 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. Reverse the vendor document and post a new document with the correct discount base date.
Issue No.: 8
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 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).
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 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).
The 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: IMG → Financial Account Global setting → Withholding tax → Extend withholding tax → Calculation → Withholding Tax Type → Define withholding tax type for payment posting.
2. Select 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
Issue No.: 9
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?
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 transaction code FCHU, which will update the payment document with check information. Follow these steps:
1. Go to transaction code FCHU.
2. Fill 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. Now, 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.
1. Go to transaction code FCHU.
2. Fill 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. Now, 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.
The 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.
Executing transaction code FCHU
Transaction 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 and pay through an APP or (2) create an advance payment document through transaction code F-48 and print a check through transaction code FBZ5. Here are the steps for both options:
Option 1:
1. Create a down payment request through transaction code F-47.
2. Run the payment program through transaction code F110
Option 2:
1. Use transaction code F-48 for advance payment to vendors.
2. Based on the posted document number, print a check using transaction code FBZ5
Transaction 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 and pay through an APP or (2) create an advance payment document through transaction code F-48 and print a check through transaction code FBZ5. Here are the steps for both options:
Option 1:
1. Create a down payment request through transaction code F-47.
2. Run the payment program through transaction code F110
Option 2:
1. Use transaction code F-48 for advance payment to vendors.
2. Based on the posted document number, print a check using transaction code FBZ5
1 SAP FICO ACCOUNTS PAYABLE Issue-10
Issue No.: 10
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.
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. While 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 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."
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."
2 SAP FICO ACCOUNTS PAYABLE Issue-11
Issue No.: 11
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 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. In transaction code F110, enter the payment run ID and payment run date.
3. Go to the Printout/data medium tab and place the mouse curser on variant field against print program.
4. From the system menu, choose Environment → Maintain Variants
Figure Using transaction code F110
5. SAP R/3 will show the Maintain variant: XXXX screen, at the bottom of which you will see the section shown in Figure
5. SAP R/3 will show the Maintain variant: XXXX screen, at the bottom of which you will see the section shown in Figure
Figure 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.
If 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. Save the variant and come back to the payment run screen. Click on to
generate the desired checks.
generated through this particular payment program.
If 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. Save the variant and come back to the payment run screen. Click on to
generate the desired checks.
3 SAP FICO ACCOUNTS PAYABLE Issue-12
Issue No.: 12
In 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?
In 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?
When 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.
4 SAP FICO ACCOUNTS PAYABLE Issue-13
Issue No.: 13
While posting a transaction through T-code F-58, the user sees this error message: "Changes for vendor XXXXXX not yet confirmed."
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.
5 SAP FICO ACCOUNTS PAYABLE Issue-14
Issue No.: 14
The user wants to make a check payment for petty expenses like stationery, travel, etc. Transaction code F-02 provides facility to capture 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 wants to make a check payment for petty expenses like stationery, travel, etc. Transaction code F-02 provides facility to capture 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
Figure Using transaction code F-53
2. After 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.
2. After 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.
6 SAP FICO ACCOUNTS PAYABLE Issue-15
Issue No.: 15
The 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.
The 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.
Executing transaction code FCHU
Transaction 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 and pay through an APP or (2) create an advance payment document through transaction code F-48 and print a check through transaction code FBZ5. Here are the steps for both options:
Option 1:
1. Create a down payment request through transaction code F-47.
2. Run the payment program through transaction code F110
Option 2:
1. Use transaction code F-48 for advance payment to vendors.
2. Based on the posted document number, print a check using transaction code FBZ5
Transaction 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 and pay through an APP or (2) create an advance payment document through transaction code F-48 and print a check through transaction code FBZ5. Here are the steps for both options:
Option 1:
1. Create a down payment request through transaction code F-47.
2. Run the payment program through transaction code F110
Option 2:
1. Use transaction code F-48 for advance payment to vendors.
2. Based on the posted document number, print a check using transaction code FBZ5
Issue No.: 16
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?
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 transaction code FCHU, which will update the payment document with check information. Follow these steps:
1. Go to transaction code FCHU.
2. Fill 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. Now, 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.
7 SAP FICO ACCOUNTS PAYABLE Issue-117
Issue No.: 17
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 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).
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 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).
The 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: IMG → Financial Account Global setting → Withholding tax → Extend withholding tax → Calculation → Withholding Tax Type → Define withholding tax type for payment posting.
2. Select 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
Issue No.: 18
A client posted a new document using T-code FBR2. Using T-code F110, payment was also posted for this invoice. After 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?
A client posted a new document using T-code FBR2. Using T-code F110, payment was also posted for this invoice. After 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?
You 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. Reverse the vendor document and post a new document with the correct discount base date.
9 SAP FICO ACCOUNTS PAYABLE Issue-19
Issue No.: 19
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 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
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.
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.
10 SAP FICO ACCOUNTS PAYABLE Issue-20
Issue No.: 20
While 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.
While 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.
The 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 OBA3 (menu path: Financial Accounting → Accounts Receivable and Accounts Payable → Business Transactions → Outgoing Payments → Manual Outgoing Payments → Define Tolerances (Vendors)) for your company code.
Issue No.: 21
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 F110, 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:
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 F110, 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:
- Paying company ode
- House bank
- Account ID
- Number of the check to be voided
- Void reason code
- New check number
4. Choose the path: Check → Reprint from the menu.
You must follow this process in a situation where you have issued checks, but the checks are lost in post.
You must follow this process in a situation where you have issued checks, but the checks are lost in post.
11 SAP FICO Issue-22
Issue No.: 22
What is ranking order in an APP?
Ranking 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.
What is ranking order in an APP?
Ranking 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.
12 SAP FICO Issue-23
Issue No.: 23
While 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.
While 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.
There 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.
You may use the following programs/reports to find out the reason for the missing documents:
- Program RFVBER00 provides a list of transactions that failed while updating the database.
- Program RFBNUM00 shows gaps in the FI number range.
13 SAP FICO Issue-24
Issue No.: 24
After 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?
The 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. You can reclassify a G/L account when its balance is zero. So clear all open items and bring your account balance to zero.
2. Through 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. Change 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 Enter 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).
After 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?
The 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. You can reclassify a G/L account when its balance is zero. So clear all open items and bring your account balance to zero.
2. Through 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. Change 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 Enter 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).
5. Once 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. If 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.
6. If 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.: 25
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?
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.
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?
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.
Payment Advice through Mail using BTE
Send new document with attachments via RFC
Functionality
This function module enables you to send a new document including any existing attachments. The document and the attachments are transferred in the same table. They are created when sent and can also be placed in the sender's outbox.
It is necessary to distinguish between the document and its folder entries. The document itself only exists in the database once. It is a template for the folder entries and can be addressed via its object ID. Any number of folder entries can belong to the document. The folder entries have the content and the attributes of the document as well as some additional attributes relating to the folder entry itself. (Send priority and expiry date of the entry, for example.) Folder entries are created when a document is resubmitted, referenced, or sent, as well as when a new document is created.
SO_DOCUMENT_SEND_API1
Program - RFFODTA1
Go to transaction code FIBF
Settings ==> Process Modules ==> ... of an SAP Application
Process: 00002040
Ctr: Blank
Appl.: FI-FI
Function Module: SAMPLE_PROCESS_00002040
You can copy the function module to "Z" function module and modify it accordingly. Then you can use your customized FM here.
This triggers an email of payment advice, provided if you have maintained Email Address in the Vendor Master "Address" Tab and the Standard Communication Method is "INT - Email"
You can see the email that is being triggered / delivered in transaction code SOST.
To deliver the emails settings in SCOT are being completed by Basis consultants and the gateways must have been opened. Except production environment, normally the gateways are closed in development or QA environment in order to avoid sending wrong payment advices outside.
User have requirement payment method field should n't editable once any document is posted.
Solution:
Path: SPRO