FBRA RESET & REVERSE - WHAT IS THE DIFFERENCE ?

Reseting will set back the open items but will not reverse the payment document. Later you can clear the payment doc with other invoice. 
For example for a customer there are two invoices with similar amount. 
you had adjusted the invoice 1 and later on customer tells you that he has paid for invoice two. In this case you have to reset the invoice 1 and no need to reverse the payment doc. but you can clear the invoice two with payment doc. 

In case of resettting & reversing let us say instead of posting to customer A account you had posted to customer B account because of name similarity. In this you have to do resetting and reversing so that open item will be put back and payment doc is reversed. 

Invoices not selected in F110




Often times users in SAP are puzzled by why a certain vendor's invoices are not selected by the payment run.
We will discuss one reason that is easy to identify and resolve.

When running a payment proposal SAP blocks the vendors whose invoices have been selected in another proposal. The savvy user will check the payment proposal log where he will be able to see vendors that are blocked by another proposal.

In this case I have run a proposal on the 18th but for some reason vendor 1000's invoices are not showing up. By pressing the proposal log button from within the payment run, Figure 1, the proposal log will be displayed, Figure 2. When examining the log, I will easily see that, that vendor 1000 is contained in a different proposal. At this point I have two options, either complete the other proposal or delete it to release the blocked invoices.


But what if you want to see all the vendors that are blocked by different proposals not just the ones that have been selected for payment in a specific proposal.

In this case you can query table REGUS: Accounts blocked by payment proposal

By querying the different rows in this table you will be able to obtain a listing of all the vendors that have been blocked in a proposal. Figure 3 displays the output of table REGUS.

By reviewing the contents of this table you will be able to see the “Run On” and Identification” fields required for finding the payment proposals that are blocking payment to your vendors.

Recurring Entries


  • Some business transactions are repeated regularly every period or quarter such as rent and insurance .SAP gives the Recurring Entry option to make this entry one time and run it every period and have the same financial effect.
  • The following data never change in the Recurring Entry :  Posting Key – Account – Line item Amounts.
  • You enter the recurring data in a Recurring Entry original document and then run the Recurring Entry Program
Enter Recurring Entry: FBD1
Accounting ⇒ Financial Accounting ⇒General Ledger⇒ Posting⇒ Reference Documents ⇒ Recurring Document (FBD1)
Update the document as below,
Image
Image
Image
After posting this entry you will get an message like : Doc:9100000000 was stored under 3300 company code,
Now we need to execute the Document Under F.14
Before execution F.14  just visit at FBD3 TCode with your recurring document number.
Image
Give Document Number & Company code then press Enter
Then click on  Goto menu then press Recurring Entry Data, then you will get Display recurring Doc Popup box, what ever date you mentioned under First and Last Run date, same Date we have to key under F.14 Settlement period
Execute Recurring Document :  (F.14)
Image
Click On Execute,
Then we ll get message “Session xxxxxx was Created”
Then Go to System menu ⇒ Select ⇒ Batch Input ⇒ Sessions
Then select the line item as below and Click on PROCESS
Image
After that we ll  get one more popup as shown below Click on Process
Image
  • Accounting documents are posted and recurring documents are updated with processing data (next run on and number of runs .)To display a posted document, use transaction code FBL1N.
ParticularsTransaction Code
Recurring Documents
Creation of Recurring DocumentFBD1
Change Recurring DocumentFBD2
Display of Recurring DocumentFBD3
Display changes in Recurring DocumentFBD4
Define Document Change RulesOB32
Delete Reference DocumentF.56
Execute Recurring EntryF.14
Evaluating Recurring entry DocumentsF.15
Running Batch Input SessionSM35

Block a Profit Center from Posting


Here is the step-by-step:
  1. Go to T-code KE52 and call up your profit center
  2. Go to the Indicators tab and put a check in the Lock indicator
  3. Save
    • Note that this will save your changes in an Inactive Status. You may be thinking that is a good thing and that you’re done…I was.  But you’re not.  If you go to FB50 or 9KE0 and try to post to that profit center, it will let you post away all day long.  One more step.
  4. Click the Match stick button to Activate your new state: activate_iconke52
Do not mess with the Validity periods unless you’ve got a good reason to.  The real key here is setting the Lock indicator and making sure that is Active.  Think of it as Actively locking your profit center

F111 Payment Request Error – Inconsistent Tables


In testing out my Fedwire configuration, I ran into a situation where I needed to switch the clearing account from the normal bank clearing to a Wire Clearing account. I made this change to the Payment Method in transaction FBZP by changing the Bank Sub-Account to the Wire Clearing GL account. After I did this, I ran another test payment request through RVND (Free Form version) and got the error message: “Database tables T042I and T042Y are not consistent”.

Solution

If you run into this error, you can go into t-code F8BF ‘Change View “Account Determination for G/L Account Payments”: Overview’ and make this match up with the account you set in FBZP. You can see the values in the tables through SE16, but the t-codes you need are:
FBZP and F8BF.

F110 Problem – Company Codes #/# do not Appear in Proposal


In some cases, you may not get that error message, but your vendor isn’t showing up in the Proposal.
Here are several things that you can check to troubleshoot this problem:
  1. Make sure the Vendor (or the invoice) has the same Payment Method your using in your Proposal – use XK03 or FK03 to view the vendor
  2. In the Parameters, make sure you have specified the vendor or a range of vendors that includes yours
  3. Make sure there is no payment block on the vendor (including FK08 confirmations for sensitive fields)
  4. Make sure the vendor doesn’t have a Debit balance
  5. Make sure there isn’t a payment block on the invoices you want to pay
  6. Make sure that the invoices that aren’t blocked don’t have a Debit balance
  7. Make sure the Vendor is NOT in an EXISTING PROPOSAL
That last one got me while doing some Payment Method testing.  We checked everything we could think of, and it came down to #7.

Company Codes and the Chart of Accounts


Though you can have multiple Charts of Accounts in SAP, company codes are assigned to only one chart of accounts. This is done in configuration (SPRO) (T-code: OB62 – Assign Company Code -> Chart of Accounts).
T-Code for Chart of Accounts
  • T-code: F.10 – Chart of Accounts
    Report of accounts in a chart of accounts. Lots of ways to limit your results, but can’t limit by Company Code! You will definitely want to limit by chart of accounts.
  • T-code: OB62 – Assign Company Code -> Chart of Accounts
    SAP: OBY2
  • T-code: OBY2 – Copy Company Code: G/L Accounts
    When creating a new Company Code, just assigning it to a chart of accounts in OB62 doesn’t automatically create those accounts for the new company code. I.e. you won’t be able to post any entries until you’ve created the accounts for the company code. OBY2 lets you copy all of the accounts that were created for another company code to your new one.
  • GL Postings are assigned to only 1 company code
    You can do “cross-company code” postings (i.e. DR CoCde A and CR CoCde B), but SAP will automatically generate the off-setting entries within each company code so that their books stay in balance (debits = credits). There is config around Intra-company postings to determine where you want those offsets to go.
  • T-code: FS00 – Edit G/L Account Centrally
    This is usually the preferred t-code for manually creating GL Accounts since it allows you to create both the chart of accounts piece and the company code pieces.
  • In FS00, you may need to create an account for multiple company codes. This can be done by changing the CoCde and using the “Create with reference button” in FS00.
    SAP: FS00
  • T-code: FSS0 – Edit Accounts in Company Code
    FSS0 allows you to edit just the Company Code (CoCde) portion of the GL Account.
  • T-code: FSP0 – Edit Account in Chart of Accounts
    FSP0 allows you to edit just the Chart of Accounts portion of the GL Account.
  • T-code: CX16 - Consolidation Chart of Accounts – Hierarchy Display
    CX16 allows you to create/edit financial statement items (FS Items) and their hierarchy for the Consolidated Chart of Accounts used in the EC-CS consolidation system.
    SAP: CX16