Revenue: Gain and clearing acct

Hi,
I want to expose Gain from asset sale and clearing account revenue in Asset register (IT) - RAITAR01
When I execute ABAON transaction, the system use TTy (transaction type) 210-290 only on Acquisition account and Dep account for ordinary depreciation.
How to force using a transaction type into Gain from asset sale and clearing account revenue too? I need TTy to expose this value in the report with Asset History Sheet version, transaction OA79
Thanks
Regards

Hello Chinnu,
Error message F3029 is raised when the clearing account (T042I-VKONT)
is filled but the payment method in question is not defined as
"Bill/exchange".
I assume that the field is not changable at the moment. You may make
necessary changes (delete the entry or delete the specified account)
with the instructions below.
1. Go to Tcd: FBZP -> Push [Pmt methods in country]
2. Select the entry for the erroneous country(US?)/payment method
3. Change Payment method classification to 'Bill/ex' and save
Now you should be able to change "Set Up Bank Determination for Payment
Transactions" table.
Best Regards,
Gladys xing

Similar Messages

When is 'Clearing Balance Sheet' and 'Clearing Inc Stmt item' used?

Hi,
In what circumstances, clearing balance sheet item and clearing inc stmt items are used. Commonly, it's used for balance carry forward task, where system recognized the net profit for the year (in PL) and current ytd profit (in BS).
i was trying to post the following entry via manual posting and system generated additional 2 lines:
DR Sales 100
CR AR 100
DR Clearing BS item 100 < System auto generated additional one line
CR Clearing PL item 100 < System auto generated additional one line
(The above entry is enter at posting level 01)
I was trying to post another 2 balance sheet items via manual posting at posting level 30. There was no additional 2 lines created.
Please advise.
Regards, Renee

Rene,
In real life there are usually closing periods in enterprises, when accountant close their books. Closing partially means that all revenues/gains and expenses/costs are summed up, and net profit in income statement calculated. During this procedure accountants usually make closing entries. After that this calculated net profit is to be transferred to balance sheet, to the retained earnings of the current year item.
In SAP SEM-BCS there are no closing entries. Instead, the system monitors whether entries in P&L were made. The P&L hierarchy in BCS has the following structure:
- one main node under which all revenues and expenses are gathered
- clearing item located OUTSIDE the P&L main node (equals to net profit).
The amount on the clearing item equals the sum of all P&L items under main node, with the opposite sign. So, the sum of P&L items & clearing item is zero.
If the system detects postings to the items located under P&L main node, it recalculates the net profit and adjust the clearing item in P&L accordingly. Since net profit in P&L should correspond to the RE in B/S, the system adjust clearing item in B/S also. So, AT ANY MOMENT the B/S & P&L in the system correspond each other. The work of special/clearing items is like pseudoclosing.
That's the purpose of these clearing items. And as I said earlier they has nothing to do with balance carryforward.
Resume: in case of postings to P&L, the net profit changes and the system adjusts net profit in P&L & B/S (adds two additional entries).
There is NO NET PROFIT CHANGE (and additional entries) when postings made in the balance sheet ONLY (as in your case). -- (As you know, there is almost no possibility to make postings to clearing item in B/S).

Foreign exchange gain and loss

Short Text
Foreign Exch Gain / Loss to be booked to a diffr cost center
Long Text
The transaction booked with the following parameters
Step 1:-Transaction booked trough FB60
Foreign currency CHF @ 40/ruppee
Expenses debited (1000-cost center)
Vendor Credited
Step 2:-Transaction paid through F-53
Foreign currency CHF @ 50/ruppee paid
Vendor Debited (Clearing the open item)
Bank outgoing account Credited
Foriegn exchange gain and loss Debited
In ECC 6.00 Version:- The open item clearing inherits the CO objects
from step one except for "Foreign exchange agin and loss line item"
Note:
1) In above scnerio, if foreign exchange gain and loss booked to some
other cost center other than Step one:- Cost Center (Expenses booked).
2) If the foreign exchange gain and loss line item booked to same cost
center as specified in Step one:- Cost Center (Expenses booked).The
below error does not occur.
3) The requirement is to book different cost center for the Foreign
exchange gain and loss line item.
The following error occurs during FB05 transaction execution for
transfering the line item in Bank outgoing account to Bank Main account.
Error Details occur during FB05 transaction execution:-
Start----
Ex.rate diff.accts are incomplete for account 0002500062 currency CHF
Message no. F5063
Diagnosis
The accounts for posting exchange rate differences could not be
determined. For the specified G/L account and the specified
currency
key, the accounts are only specified incompletely. Either the
accounts
for the implemented exchange rate difference, the accounts for the
valuation differences or the balance sheet adjustment account are
missing.
System Response
The system cannot generate the exchange rate difference posting.
Procedure
By pressing ENTER, you achieve that the document is reset to a
status
without automatic posting. In another window, you can complete
default
settings for exchange rate differences and post the document
afterwards.
END----
Configuration already in place:-
1) Bank outgoing and main account "ONLY BALANCE IN LOCAL CURRENCY" is a
ticked
2) In OBA1 Foreign exchange gain and loss and valuation gain and loss
GL's are defined for respective Reconciliation account.
Regards,
Sathya

Hi,
Is your problem solved, I am also facing the same issue when transffering from Incoming/Outgoing to Main Bank Account. Exchange gain/loss is being calculated by the system.
Please share with me the solution to the above problem.
Thanks & Regards,
Jyoti

Define Clearing Accts for Payment Diff. with Altern.Currency

Dear SAP Gurus,
Please suggest difference between Define Clearing Accts for Payment Diff. with Altern.Currency & Define Accounts for Payment Differences with Altern. Currency.
I am not able to understand what the use of defining Accounts for Payment Differences with Altern. Currency in two activities.
Early reply would be appreciated.
Regards,
Prafful kansal

Hi,
For this Scenario payment clearing is based on the exchange rate currencies for that purpose we configure that 2 setup accounts.
Briefly: If Invoice is raised as per date feb 1st (1 us dollar = 45 rupees)and payment received on that 1 mar ( 1 us dollar=40 Rupees)for this the exchage rate values are may be different for that purpose.
For this scenarios it will be loss or gain.
Hope you will understand.
Regards,
Kanike

Product Revenue Bookings and Backlog Dashboard does not display any data

Product Revenue Bookings and Backlog Dashboard does not display any data even though the load completed successfully.
They are able to see just the parameters.
Not sure if the upgrade of the database from 9.2.0.6 to 10.2.0.3 is a factor.
What can I check?
Is there some table to verify that the data exists for display in the Product Revenue Bookings and Backlog Dashboard?
Screenshot is at:
https://gtcr.oracle.com/gtcr-dir/gtcr_5637/6415786.993/Product_Revenue_Bookings_Backlog_Dashboard.doc
Support suggested to create a new request set and run the initial load with load all summaries option; but there was no change in the Product Revenue Bookings and Backlog Dashboard.
Any ideas?

hi
We have faced the similar problem after the upgrade to 10G
What we did was
Ran the initial load of time dimension, Item setup request set, and the request set of all the dash board in the clear and initial load mode..
we were able to get the data once the clear and load is completed successfully
Regards
Ramesh Kumar S

MIRO--CENVAT CLEARING ACCT NOT APPEARING.

Hi All,
In PO ,we are maintaining only JIPC ( cst ) for a tax code, But while GR we are capturing excise( cenavtable), now while doing MIRO cenvat clearing acct is not appearing when we simulate.
Is it prerequisit to maintain excise condition in PO so that cenvat clearing acct appears while doing MIRO?
Regards,
Manish

you need to maintain the excise conditions in the PO. What you can do is maintain the values eg. BED 16% and if you have different percentages or values of excise for different materials. Then the t.code FV11 allows you to maintain your condition on the basis of material, material plant and other combinations.
If this does not help then one more suggestion is to maintain a certain condition and percentage in the PO, and when you do the J1IEX capture you can manually go and change the values in the Excise Value tab. Try this and see what entries are passed after J1IEX posting. But this method would require manual intervention, i mean the value will ahve to be changed each time while capturing. and a mistake may cause problems.

F-04 CLEARING ACCT

Hi Experts!
Good day!
When i'm using F-04 to clear acct 11200012, the error message below:
Consolidated companies ' ' and A201 are different
Message no. F5080
Diagnosis
The number of the affiliated company must be clear for the selected document type for all line items. In this case at least two different companies or a company in connection with a business partner who does not belong to a company are stated.
Procedure
If you selected the correct accounts, you must enter the document with a document type that allows cross-company posting. Otherwise, please correct the entered account.
Hope you can help me with this...
Thanks so much

Dear
Maria.
Please check that the document type you are using you have selected option Inter-Company postgs.
Simply double click on document type in OBA7 and check - if not flag it and try again.
When you make the transactions between intecompany or affilated company make sure you have flaged this option in for respective option.
Problems can arise in payment transactions if a vendor or a customer has changed its status, for example from a non-affiliated to an affiliated company. In the case of simultaneous payment of old and new items, there is therefore more than one trading partner assigned in the document. Similar problems can occur in the case of payments using several accounts. To make these postings possible, the document type must allow for the payment document to include different trading partners.
I hope this will help you to solve your issue. If you have any doubts feel free to share.
Regards,
Pankaj A Bhalerao.

Issue on Gain and Loss account in F110 document

Hello SAP Guru,
I would like to ask your assistance regarding our accounting document. The document was produced on F110 transaction.
Now the problem is Valuation Balance sheet adjustment, realize gain and loss are in one document.
25 - Vendor - 727,843.35
50 - Clearing Account - 801,874.76-
40 - Valuation Balance sheet adj - 159,734.84
50 - Realize gain - 85,703.43-
40 - realize loss - 0
How this happened? Realize loss and gain in one document, and why valuation balance sheet adjustment was used? I thought it is only use for open items?
Thanks in advance!
Jhero

Hello SAP Guru,
I have other question, I have maintained KDB accounts in OBA1. How could I test it? I mean what transactions do you have to perform to use the accounts I maintained.
Eg.
1. Post document FB01 - using Foreign Currency - Vendor + GL
2. Chnage the FX rate - to have FX valuation
3. Run FAGL_FC_VAL
Something like above
Thanks!
Jhero

Why are my photos not as sharp and clear in online album

I've been struggling thru this make-an-album thing and will not given up. I have continued to work thru this first album to be posted on line. I'm almost there. I've sorted thru the templates and only found one that shows my photos large enough to see and appreciate but they seem to be degraded - not sharp and clear. And that template cuts off my captions to the photos. I just want a slideshow, full screen, full resolution and with all my captions. I thought that was what Photoshop Elements 8 and my Adobe acct allowed me to do.
I take a lot of pixs with a Pentax K20D at 14.5M. I have not been able to share any of my photos, as taken, thru my email because they are too big. Now it looks like PS8/Adobe dumbs they down.
I'm new to this....so what am I missing????
Rebecca

Get SmugMug photo sharing. For a few dollars a year your photos will look fantastic. It is much better value and has unlimited storage unlike Photoshop.com and the full screen slideshow with captions look even more impressive on widescreen monitors.
What's more, you can upload photos to your SmugMug albums directly from the PSE Organizer.
http://www.smugmug.com/

YE Ret Earning Roll and Clear Process produces out of balance.-MA to fix...

YE Ret Earning Roll and Clear Process produces out of balance.-MA to fix....
Hi,
Our co. has 13 segments.
xxxxx-xxx-xxxxx-xxxxx-xxxx-xxx-x-xxx-xx-xx-xxx-xxx-xxx
ENTITY OU PRIME SUB CC PRD R DC ST NW SP STAT FUT
As a result of our year end retained earnings roll and clear process, our stat segment (seg 12) is not balancing and rolling up to retained earnings. Our balancing segment is legal entity. Currently our countries have to perform manual entries to reclass all non 000 stat accounts back to it's original P&L account. Attempting to automate via Mass Allocation.
Currently, working the following formula. However, unable to move from 000 to applicable stat (130 for example)
A 03011-TTT-30100-TTTTT-TTT-TTT-T-TTT-TT-TT-TTT-TTT-TTT
C S C S S S S S S S S S S
B 03011-TTT-30100-TTTTT-TTT-TTT-T-TTT-TT-TT-TTT-TTT-TTT
C L C L L L L L L L L L L
C 03011-TTT-30100-TTTTT-TTT-TTT-T-TTT-TT-TT-TTT-TTT-TTT
C L C L L L L L L L L L L
T 03011-TTT-30100-TTTTT-TTT-TTT-T-TTT-TT-TT-TTT-TTT-TTT
C L C L L L L L L L L L L
0 03011-TTT-30100-TTTTT-TTT-TTT-T-TTT-TT-TT-TTT-TTT-TTT
C L C L L L L L L L L L L
Note that B and C are the same so that they basically would be a wash. I orignally had a constant (1) in both, however, it resulted in a rule violation.
What currently is happening is a total reclass. That is, all segment 12 values moving from 30100 xxxxx 000 stat to the same. Has anyone experienced this issue? Any ideas/suggestions would be appreciated.
Thanks,

Hi,
If I understand you correctly, you are trying to move balances from ONE account combination to another right?
So, let's say, my COA is structured as
B/S- Stat - Acct - whatever...
And account combination
10-000-6100-0000-000 has $100 erroneously in it and I want to MOVE the balance from STAT value 000 to 130.
This is how to do it:
Choose to Allocate Balances From FULL BALANCE.
Leave Full Cost Pool Allocation check box BLANK. If you check this, you cannot use numbers in B and C lines. (See General Ledger Users Guide).
Thus, this is what my formual should look like:
A 10-000-6110-0000-000
C C C C C
B 1
C 1
T 10-130-6110-0000-000
C C C C C
O 10-000-6110-0000-000 (same as A to empty it out)
C C C C C
I'm not sure why you're looping. Looping is used on Parent account when you want to divide up the cost pool proportionately, say across departments.

Can We Change Realized gain and loss account in system option Receivables

Hi All,
As part of our month end processes we are posting a manual journal each month to clear this GL account down to a nil balance.
Looking at the activity they all look to be automated AR postings on foreign currency transactions.
Is there any way we could get these to automatically post into account 01.2201.4901 instead of 01.9000.9757? This would save us having to do the manual journal and avoid the situation of missing any which we did last month.
Regards,
Raju.

Hi Raju,
option 1
You can change the Realized Gain and Loss Account from the System options form in Receivables, but this will be effective only for all new transactions that are going to get created and not for the existing one ...
Option 2
If you do not want to modify the system options, you can override the values at the accounting time frame by configuring an Accounting Derivation Rule for the Realized Gain and Loss Journal Line Type. Again this would take effect on new transactions only
Option 3
You can disable 01.2201.4901 and state its replacement is 01.9000.9757 in General Ledger module, so whenever system would use the replacement account for automatic processing ....
You have to keep running the Accounting analysis report in General ledger for the account string 01.9000.9757 every month to cross check whether you have passed all Manual Journal Vouchers to make the balance NIL ... i am not sure whether there is any other way of performing a cross checking and minimizing the time that is being consumed at present ....
Regards,
Ivruksha

Open and Cleared Items

Hi all
We are currently busy finalising our FI-CA BW Data Modeling exercise - and in process to complete Dataflow documentation.
We will make use of the standard open and cleared item extractors with enhancements on different levels. Some background on the requirements:
- We will have to extract document types, divisions, dates, clearing reasons, contract account, Business Partner etc.. information to meet the requirements.
- We will have to keep history for at least 26 months to produce the required management reports (very high number of data), and 'partition' the cubes on date level for both Cleared and Open Items.
- Most of the reports display 13 months worth of billing/ payment figures. I.e. the report for the end of October show billings vs. payments for October 2006, September, August, July, ... to October 2005.
- The requirement is that the report figures will not change from one month to the next (i.e. if I run the report for end of October - all figures from October 2006 to Oct 2005 will remain the same when I run the report for end of November). I.e. if reversals, transfers, returns etc. occur - these will be picked up in later months.
- For the above requirement, we are looking at extracting open (end of month) and cleared items (for the specific monthly interval) on a monthly basis, and appending the data in the cubes. We will then always base the June figure in the report on the June month extraction (LAUFD/ LAUFI fields) and we will pick up any movement in the next month/s - i.e. July.
Has anyone had these types of requirements before - to report on billings vs. payments, and report on history as described above. We would appreciate it if you could share your report requirements, and also design documents, especially the DataFlow documentation that we can look at as input to our design.

We had a requirement to retrieve "aging of receiveables" by customer. Basically, it goes thru each record and depending on the due date places the amounts in the following buckets (example). 0-30 day Overdue, 31-60 days Overdue, 61-90 days overdue, 30+ days overdue, 60+ days overdue) etc all the way to 6+ years overdue.
There are also cooresponding buckets for coming due analysis. For example, what is: 0-30 days coming due, 31-60 days coming due, 30+ days coming due, etc...
To do this, first I needed to be able be able to produce an open items statement at any given time in the past. Now, this seems impossible because of how the items go from open to cleared all the time. And an item that was open one month ago, may not be open anymore.
What I did was first remove any selections on item status. Then compare the posting date with teh key date in the past, if the posting date is less than or equal to the key date, keep the record.
Then compare the clearing date with the key date. First, keep all that are #. (This keeps all records still open from that posting date/key date)
Then, add another check for all items that were cleared after the key date (GT Key Date). This gives you the open items on that date.
Hope that makes sense. Let me know if you want clarification.
/smw

Custom purchase requsitionto vendor open and cleared payment report

dear all i develop report but i cant ableto show in that open amount and cleared amount of vender in that report so please see this report and feedback me for logic to show open and clear amount of vendor purchase orderwise or vendorwise
report zpo_purchase_history no standard page heading message-id 00.
TABLES : bsik, bsak, lfa1, lfb1, skb1, t001, bapifvdexp_vzzbepp.
type-pools:slis,ICON.
types :begin of ty_po,
        banfn type eban-banfn,
        "Purchase Requisition Number
        bnfpo type eban-bnfpo,
        "Item Number of Purchase Requisition
        ekgrp type eban-ekgrp,                 "Purchasing Group
        badat type eban-badat,
        "Requisition (Request) Date
        menge type eban-menge,
        KNTTP TYPE EBAN-KNTTP,
         PSTYP type eban-PSTYP,
        "Purchase Requisition Quantity
        meins type eban-meins,
        "Purchase Requisition Unit of Measure
        lifnr type ekko-lifnr,                 "Vendor Account Number
        bedat type ekko-bedat,                 "Purchasing Document Date
        ebeln type ekpo-ebeln,
        "Purchasing Document Number
        ebelp type ekpo-ebelp,
        "Item Number of Purchasing Document
        matkl type ekpo-matkl,                 "Material Group
        mtart type ekpo-mtart,                 "Material Type
        matnr type ekpo-matnr,                 "Material Number
        txz01 type ekpo-txz01,                 "Short Text
        menge1 type ekpo-menge,                "Purchase Order Quantity
        meins1 type ekpo-meins,
        "Purchase Order Unit of Measure
        balqty type ekpo-menge,                "Balance Quantity
        netpr type ekpo-netpr,
        "Net Price in Purchasing Document
        peinh type ekpo-peinh,                 "Price Unit
        mblnr type mseg-mblnr,
        "Number of Material Document
        zeile type mseg-zeile,                 "Item in Material Document
        menge2 type mseg-menge,                "GR Quantity
        meins2 type mseg-meins,                "GR Unit of Measure
        werks type mseg-werks,                 "Plant
        charg type mseg-charg,                 "Batch
        belnr type rbkp-belnr,
        "Document Number of an Invoice Document
        bldat type ekbe-bldat,                 "Document Date in Document
        belnr_b type rbkp-belnr,
        SHKZG type ekbe-SHKZG ,                "Debit/Credit Indicator
        DMBTR type   bsik-dmbtr,                "Amount in Local Currency
        DMBTR_C type   bsAk-dmbtr,                "Amount in Local Currency
        thick(10) type c,                      "Thickness
        width(10) type c,                      "Width
        length(10) type c,                     "Length
        grade(10) type c,                        "Grade
        BELNR_d type bseg-belnr,
        xblnr type bkpf-xblnr,
        awkey type bkpf-awkey,
        RMWWR type rbkp-RMWWR,
        WMWST1 type rbkp-WMWST1,
        end of ty_po.
types :begin of ty_ekko,
        ebeln type ekko-ebeln,
        lifnr type ekko-lifnr,
        bedat type ekko-bedat,
        end of ty_ekko.
types:begin of ty_ekpo,
        ebeln type ekpo-ebeln,
        ebelp type ekpo-ebelp,
        matnr type ekpo-matnr,
        txz01 type ekpo-txz01,
        menge type ekpo-menge,
        meins type ekpo-meins,
        netpr type ekpo-netpr,
        peinh type ekpo-peinh,
        banfn type ekpo-banfn,
        bnfpo type ekpo-bnfpo,
        mtart type ekpo-mtart,
        end of ty_ekpo.
types :begin of ty_eban,
        banfn type eban-banfn,
        bnfpo type eban-bnfpo,
        matnr type eban-matnr,
        menge type eban-menge,
        meins type eban-meins,
        end of ty_eban.
types : begin of ty_ekbe,
         ebeln type ekbe-ebeln,
         ebelp type ekbe-ebelp,
         belnr type ekbe-belnr,
         bldat type ekbe-bldat,
         gjahr type ekbe-gjahr,
         buzei type ekbe-buzei,
         matnr type ekbe-matnr,
         DMBTR type ekbe-dmbtr,
         shkzg type ekbe-shkzg,
         end of ty_ekbe.
types : begin of ty_mseg,
         mblnr type mseg-mblnr,
         mjahr type mseg-mjahr,
         zeile type mseg-zeile,
         menge type mseg-menge,
         meins type mseg-meins,
         ebeln type mseg-ebeln,
         ebelp type mseg-ebelp,
         matnr type mseg-matnr,
         werks type mseg-werks,
         charg type mseg-charg,
         end of ty_mseg.
types : begin of ty_rbkp,
         belnr type rbkp-belnr,
         gjahr type rbkp-gjahr,
         bldat type rbkp-bldat,
         lifnr type rbkp-lifnr,
         ZUONR type rbkp-ZUONR,
         RMWWR type rbkp-RMWWR,
         WMWST1 type rbkp-WMWST1,
         end of ty_rbkp.
types : begin of ty_bseg,
         bukrs type bseg-bukrs,
         belnr type bseg-belnr,
         gjahr type bseg-gjahr,
         buzei type bseg-buzei,
         valut type bseg-valut,
         wrbtr type bseg-wrbtr ,
         augbl type bseg-augbl,
         matnr type bseg-matnr,
         lifnr type bseg-lifnr,
         ebeln type bseg-ebeln,
         end of ty_bseg.
types : begin of ty_rseg,
         belnr type rseg-belnr,
         gjahr type rseg-gjahr,
         ebeln type rseg-ebeln,
         ebelp type rseg-ebelp,
         matnr type rseg-matnr,
         bukrs type rseg-bukrs,
         end of ty_rseg.
types : begin of ty_bsik,
         belnr type bsik-belnr,
          buzei type bsik-buzei,
         DMBTR type bsik-DMBTR,
         budat type bsik-budat,
         shkzg type bsik-shkzg,
         ebeln type bsik-ebeln,
         lifnr type bsik-lifnr,
         end of ty_bsik.
types : begin of ty_bsak,
         belnr type bsak-belnr,
   lifnr type bsak-lifnr,
    ebeln type bsak-ebeln,
         DMBTR_C type bsak-DMBTR,
ZUONR type bsak-ZUONR,
         end of ty_bsak.
types: begin of ty_bkpf,
         BELNR type bkpf-belnr,
         xblnr type bkpf-xblnr,
         awkey type bkpf-awkey,
       end of ty_bkpf.
data: it_po type standard table of ty_po,
       it_ekko type standard table of ty_ekko,
       it_ekpo type standard table of ty_ekpo,
       it_eban type standard table of ty_eban,
       it_ekbe type standard table of ty_ekbe,
       it_mseg type standard table of ty_mseg,
       it_rbkp type standard table of ty_rbkp,
       it_rseg type standard table of ty_rseg,
       it_bseg type standard table of ty_bseg,
       it_bsik type STANDARD TABLE OF ty_bsik with header line,
       it_bsak type STANDARD TABLE OF ty_bsak,
       it_bkpf type standard table of ty_bkpf,
       wa_po type ty_po,
       wa_ekko type ty_ekko,
       wa_ekpo type ty_ekpo,
       wa_eban type ty_eban,
       wa_mseg type ty_mseg,
       wa_rbkp type ty_rbkp,
       wa_rseg type ty_rseg,
       wa_bseg type ty_bseg,
       wa_ekbe type ty_ekbe,
       wa_bsik type ty_bsik,
       wa_bsak type ty_bsak,
       wa_bkpf type ty_bkpf.
data: it_fcat type slis_t_fieldcat_alv,
       it_lshead type slis_t_listheader,
       it_sort type slis_t_sortinfo_alv,
       wa_fcat type slis_fieldcat_alv,
       wa_lshead type slis_listheader,
       wa_layout type slis_layout_alv,
       wa_sort type slis_sortinfo_alv.
data :it_cl_data like table of clobjdat,
       wa_cl_data like clobjdat.
data: values(10) type n.
data: value1(4) type N.
data: c_matkl type ekpo-matkl,
       c_matnr type ekpo-matnr,
       c_ekgrp type eban-ekgrp,
       c_badat type eban-badat,
       c_index type sy-tabix,
       c_grmenge type mseg-erfmg,
       c_low(10) type c,
       c_high(10) type c,
       c_date type string,
       c_bukrs type ekko-bukrs,
       c_WERKS type eban-WERKS.
data: gd_date(10).
DATA: V_EVENTS TYPE SLIS_T_EVENT,
       WA_EVENT TYPE SLIS_ALV_EVENT.
*********Selection screen variables*********
selection-screen:begin of block b1 with frame title text-001.
select-options: s_bukrs for c_bukrs DEFAULT 'bmp1',
                 s_WERKS for c_WERKS,
                 s_matnr for c_matnr DEFAULT 'rm-01',
                 s_matkl for c_matkl ,
                 s_badat for c_badat ,"obligatory,
                 s_ekgrp for c_ekgrp.
parameters: ch_bal as checkbox.
selection-screen:end of block b1.
*initialization.
* PERFORM EVENT_CALL.
* PERFORM POPULATE_EVENT.
start-of-selection.
     PERFORM EVENT_CALL.
   PERFORM POPULATE_EVENT.
   perform getdata.
   perform setdata.
   perform fieldcat.
   perform display.
*&      Form GETDATA
form getdata .
   select a~BANFN
          a~bnfpo
          a~ekgrp
          a~badat
          a~KNTTP
          a~PSTYP
          b~ebeln
          b~ebelp
          b~matkl
          b~matnr
          b~bukrs
          into corresponding fields of table it_po
          from eban as a inner join ekpo as b
          on a~banfn = b~banfn and
             a~bnfpo = b~bnfpo AND
             A~KNTTP = B~KNTTP and
             a~PSTYP = b~PSTYP
          where a~badat in s_badat and
                 a~ekgrp in s_ekgrp and
                 a~WERKS in s_WERKS and
                 b~matnr in s_matnr and
                 b~matkl in s_matkl and
                 b~bukrs in s_bukrs and
                 b~loekz <> 'L' and
                 a~loekz <> 'X'.
   if it_po[] is not initial.
     select ebeln
            ebelp
            matnr
            txz01
            menge
            meins
            netpr
            peinh
            banfn
            bnfpo
            mtart
            from ekpo into table it_ekpo
            for all entries in it_po
            where ebeln = it_po-ebeln and
                  ebelp = it_po-ebelp and
                  loekz <> 'L'.
     select banfn
            bnfpo
            matnr
            menge
            meins
            from eban into table it_eban
            for all entries in it_po
            where banfn = it_po-banfn and
                  bnfpo = it_po-bnfpo and
                  loekz <> 'X'.
     if it_ekpo[] is not initial.
       select ebeln
              lifnr
              bedat
              from ekko into table it_ekko
              for all entries in it_ekpo
              where ebeln = it_ekpo-ebeln.
       select ebeln
              ebelp
              belnr
              bldat
              gjahr
              buzei
              matnr
              DMBTR
              shkzg
              from ekbe into table it_ekbe
              for all entries in it_ekpo
              where ebeln = it_ekpo-ebeln and
                    ebelp = it_ekpo-ebelp .
*if it_ekbe-shkzg = 'H'.
**ekbe-dmbtr = ekbe-dmbtr * -1.
**ekbe-menge = ekbe-menge * -1.
*endif.
* select belnr
*             gjahr
*             ebeln
*             ebelp
*     from bseg into table it_bseg
*             for all entries in it_ekpo
*             where ebeln = it_ekpo-ebeln and
*                   ebelp = it_ekpo-ebelp.
       select belnr
              gjahr
              ebeln
              ebelp
              matnr
              bukrs
              from rseg into table it_rseg
              for all entries in it_ekpo
              where ebeln = it_ekpo-ebeln and
                    ebelp = it_ekpo-ebelp.
     endif.
     if it_ekbe[] is not initial.
       select mblnr
              mjahr
              zeile
              menge
              meins
              ebeln
              ebelp
              matnr
              werks
              charg
              from mseg into table it_mseg
              for all entries in it_ekbe
              where mblnr = it_ekbe-belnr and
                    mjahr = it_ekbe-gjahr and
                    zeile = it_ekbe-buzei and
                    bwart = '101'.
     endif.
     if it_rseg[] is not initial.
       select belnr
              gjahr
              bldat
              lifnr
              ZUONR
              RMWWR
              WMWST1
              from rbkp into table it_rbkp
              for all entries in it_rseg
              where belnr = it_rseg-belnr.
     endif.
*if it_rseg[] is not initial.
*      SELECT bukrs
*              belnr
*              gjahr
*              buzei
*              valut
*              wrbtr
*              augbl
*              matnr
*              lifnr
*              ebeln
*        INTO TABLE it_bseg
*          FROM bseg
*          FOR ALL ENTRIES IN it_rseg
*          WHERE bukrs = it_rseg-bukrs and ebeln = it_rseg-ebeln and mwskz = ''.
*endif.
*loop at it_BKPF into wa_BKPF.
* values = wa_rbkp-belnr.
* value1 = wa_rbkp-gjahr.
   data: aekey_1 type string .
*CONCATENATE values value1 into aekey_1.
* if it_BSEG[] is not initial.
*MESSAGE aekey_1 type 'I'.
       SELECT single belnr xblnr awkey into wa_bkpf
         from bkpf
         where awkey = aekey_1.
SELECT SINGLe belnr
buzei
dmbtr
budat
   shkzg
   ebeln
   lifnr
   FROM bsik
INTO CORRESPONDING FIELDS OF wa_bsik
*FOR ALL ENTRIES IN it_bseg
WHERE
    bukrs in s_bukrs and
    lifnr = wa_rbkp-lifnr
and
*AND gjahr = it_bseg-gjahr
* AND
    belnr = wa_bkpf-belnr.
insert wa_bsik into table it_bsik.
CLEAR wa_bsik.
CLEAR it_bsik.
*endloop.
* and ebeln = it_bseg-ebeln .
*    select BELNR
**           SHKZG
**           DMBTR
*           from bkpf into table it_bkpf
*            for ALL ENTRIES IN it_rbkp
*            where belnr = it_rbkp-belnr.
*        ENDif.
IF IT_bseg[] IS NOT INITIAL.
       select belnr
         LIFNR
         ebeln
              DMBTR
          ZUONR
              from bsik into table it_bsik
              for all entries in it_bseg
              where belnr = it_bseg-belnr.
       select belnr
         LIFNR
         ebeln
              DMBTR
          ZUONR
              from bsak into table it_bsak
              for all entries in it_bseg
              where belnr = it_bseg-belnr.
ENDIF.
   else.
     message s002.
     leave list-processing.
   endif.
endform.                    " GETDATA
*&      Form SETDATA
form setdata .
   clear wa_po.
   loop at it_po into wa_po.
     c_index = sy-tabix.
********Calculate PR Quantity**********
     clear wa_eban.
     read table it_eban into wa_eban
                with key banfn = wa_po-banfn
                         bnfpo = wa_po-bnfpo.
     if sy-subrc eq 0.
       move:wa_eban-menge to wa_po-menge,
            wa_eban-meins to wa_po-meins.
     endif.
********Calculate PO Quantity**********
     clear wa_ekpo.
     read table it_ekpo into wa_ekpo
                with key banfn = wa_po-banfn
                         bnfpo = wa_po-bnfpo .
     if sy-subrc eq 0.
       move:wa_ekpo-txz01 to wa_po-txz01,
            wa_ekpo-netpr to wa_po-netpr,
            wa_ekpo-peinh to wa_po-peinh,
            wa_ekpo-mtart to wa_po-mtart,
            wa_ekpo-menge to wa_po-menge1,
            wa_ekpo-meins to wa_po-meins1.
     endif.
********Calculate Balance Quantity******
     clear wa_mseg.
     loop at it_mseg into wa_mseg
            where ebeln = wa_po-ebeln and
                  ebelp = wa_po-ebelp.
       c_grmenge = c_grmenge + wa_mseg-menge.
     endloop.
     move:wa_mseg-mblnr to wa_po-mblnr,
          c_grmenge to wa_po-menge2,
          wa_mseg-meins to wa_po-meins2,
          wa_mseg-werks to wa_po-werks,
          wa_mseg-charg to wa_po-charg.
     wa_po-balqty = wa_eban-menge - c_grmenge.
     clear : wa_rseg,wa_rbkp.
     read table it_rseg into wa_rseg with key
                    ebeln = wa_mseg-ebeln
                    ebelp = wa_mseg-ebelp.
     read table it_rbkp into wa_rbkp
                with key belnr = wa_rseg-belnr
                         gjahr = wa_rseg-gjahr.
     if sy-subrc eq 0.
       move : wa_rbkp-belnr to wa_po-belnr,
              wa_rbkp-bldat to wa_po-bldat,
              wa_rbkp-RMWWR to wa_po-RMWWR,
              WA_RBKP-WMWST1 TO WA_PO-WMWST1.
     endif.
       read table it_bseg into wa_bseg with key
                     ebeln = wa_rseg-ebeln
                     bukrs = wa_rseg-bukrs.
       if sy-subrc eq 0.
         move wa_bseg-belnr to wa_po-belnr_d.
       endif.
*    read table it_bkpf into wa_bkpf
*    with key belnr = wa_ekbe-belnr.
*    read table it_bseg into wa_bseg
*    with key belnr = wa_bkpf-belnr.
CLEAR wa_bsik.
clear it_bsik.
     read table it_bsik into wa_bsik
     with key belnr = wa_bkpf-belnr.
*    if wa_bsik-shkzg = 'H'.
*     wa_bsik-DMBTR = wa_bsik-DMBTR * 1.
*     endif.
       if sy-subrc eq 0.
         move : wa_bsik-belnr to wa_po-belnr,
                 wa_bsik-DMBTR to wa_po-DMBTR.
        endif.
*    clear wa_bsik.
*    read table it_bsik into wa_bsik
*               with key belnr = wa_bseg-belnr.
*    if sy-subrc eq 0.
*        move : wa_bsik-DMBTR to wa_po-DMBTR.
*    endif.
*clear wa_bsak.
*    read table it_bsak into wa_bsak
*               with key belnr = wa_bseg-belnr.
*    if sy-subrc eq 0.
*        move : wa_bsak-DMBTR_C to wa_po-DMBTR_C.
*    endif.
*clear : wa_rbkp.
*loop at it_bsik into wa_bsik.
*read table it_bsik into wa_bsik with key belnr = wa_rbkp-belnr.
*if sy-subrc eq 0.
* move : wa_bsik-DMBTR to wa_po-DMBTR.
*    endif.
*endloop.
*********Assign Vendor,PO Date*********
     clear wa_ekko.
     read table it_ekko into wa_ekko
                with key ebeln = wa_po-ebeln.
     if sy-subrc eq 0.
       move:wa_ekko-lifnr to wa_po-lifnr,
            wa_ekko-bedat to wa_po-bedat.
     endif.
*clear wa_ekko.
*read table it_ekko into wa_ekko
*with key lifnr = wa_po-lifnr.
*if sy-subrc eq 0.
* move: wa_bsik-DMBTR to wa_po-DMBTR.
* endif.
*    call function 'ZSD_BATCH_CLASSIFICATION_DATA'
*      exporting
**        ch_charg                   = wa_po-charg
*        ch_matnr                   = wa_po-matnr
*        ch_werks                   = wa_po-werks
*      tables
*        cl_data                    = it_cl_data
**       I_SEL_CHARACTERISTIC       =
     loop at it_cl_data into wa_cl_data.
       if wa_cl_data-ausp1 ne '?'.
         if wa_cl_data-atnam eq 'THICKNESS'.
           move wa_cl_data-ausp1 to wa_po-thick.
         elseif wa_cl_data-atnam eq 'LENGTH'.
           move wa_cl_data-ausp1 to wa_po-length.
         elseif wa_cl_data-atnam eq 'WIDTH'.
           move wa_cl_data-ausp1 to wa_po-width.
         elseif wa_cl_data-atnam eq 'GRADE'.
           move wa_cl_data-ausp1 to wa_po-grade.
         endif.
       endif.
     endloop.
     modify it_po from wa_po index c_index.
     clear :c_grmenge,wa_po,wa_ekpo,wa_mseg,c_index.
   endloop.
endform.                    " SETDATA
*&      Form FIELDCAT
*       text
* --> p1        text
* <-- p2        text
form fieldcat .
   perform buildfields using '1' 'BANFN' 'IT_PO' 'PR Number' '' ''.
* perform buildfields using '2' 'BNFPO' 'IT_PO' 'PR Item Number' '' ''.
   perform buildfields using '2' 'KNTTP' 'IT_PO' 'A/c Assignment Cat' '' ''.
   perform buildfields using '2' 'PSTYP' 'IT_PO' 'Item Cat' '' ''.
   perform buildfields using '3' 'EKGRP' 'IT_PO' 'Purchase Group' '' ''.
   perform buildfields using '4' 'BADAT' 'IT_PO' 'Request Date' '' ''.
   perform buildfields using '5' 'MENGE' 'IT_PO' 'PR Quantity' 'X' ''.
   perform buildfields using '6' 'MEINS' 'IT_PO' 'PR Unit' '' ''.
   perform buildfields using '7' 'LIFNR' 'IT_PO' 'Vendor Number' '' ''.
   perform buildfields using '8' 'EBELN' 'IT_PO' 'Purchasing Doc No' '' '' .
   perform buildfields using '9' 'BEDAT' 'IT_PO' 'PO Date' '' ''.
   perform buildfields using '10' 'MTART' 'IT_PO' 'Material Type' '' ''.
   perform buildfields using '11' 'MATKL' 'IT_PO' 'Material Group' '' ''.
   perform buildfields using '12' 'MATNR' 'IT_PO' 'Material Number' '' ''.
   perform buildfields using '13' 'TXZ01' 'IT_PO' 'Material Desc' '' ''.
   perform buildfields using '18' 'MENGE1' 'IT_PO' 'PO Quantity' 'X' ''.
   perform buildfields using '19' 'MEINS' 'IT_PO' 'PO Unit' '' ''.
   perform buildfields using '20' 'NETPR' 'IT_PO' 'Net Price' '' ''.
   perform buildfields using '21' 'PEINH' 'IT_PO' 'Price Unit' '' ''.
   perform buildfields using '22' 'MBLNR' 'IT_PO' 'GR Number' '' ''.
   perform buildfields using '23' 'MENGE2' 'IT_PO' 'GR Quantity' 'X' ''.
   perform buildfields using '24' 'MEINS2' 'IT_PO' 'GR Unit' '' ''.
   perform buildfields using '25' 'BELNR' 'IT_PO' 'Invoice doc. number' '' ''.
   perform buildfields using '26' 'BLDAT' 'IT_PO' 'Invoice Date' '' ''.
* perform buildfields using '26' 'BELNR_D' 'IT_POP' 'A/C Doc. No.' '' ''.
* perform buildfields using '26' 'AUGBL' 'IT_PO' 'Clearing Doc No.' '' ''.
   perform buildfields using '26' 'DMBTR' 'IT_PO' 'OPEN AMOUNT' '' ''.
perform buildfields using '26' 'DMBTR' 'IT_PO' 'clear AMOUNT' '' ''.
* perform buildfields using '26' 'DMBTR_C' 'IT_PO' 'Clear balance' '' ''.
   if ch_bal = 'X'.
     perform buildfields using '27' 'BALQTY' 'IT_PO' 'Balance Quantity'
     'X' ''.
   endif.
   perform buildfields using '26' 'WMWST1' 'IT_PO' 'TOTAL TAX ADDED' 'X' ''.
   perform buildfields using '26' 'RMWWR' 'IT_PO' 'TOTAL AMOUNT IN INVOICE' 'X' ''.
endform.                    " FIELDCAT
*&      Form BUILDFIELDS
*       text
*      -->P_0449   text
*      -->P_0450   text
*      -->P_0451   text
*      -->P_0452   text
form buildfields using    value(p_col_pos) like sy-cucol
                            value(p_fldname) type slis_fieldname
                            value(p_tabname) type slis_tabname
                            value(p_reptext) like dd03p-reptext
                            value(p_do_sum) type char1
                            value(hotspot) type char1.
   wa_fcat-col_pos = p_col_pos.
   wa_fcat-fieldname = p_fldname.
   wa_fcat-tabname = p_tabname.
   wa_fcat-reptext_ddic = p_reptext.
   wa_fcat-do_sum = p_do_sum.
   wa_fcat-hotspot = hotspot.
   append wa_fcat to it_fcat.
   clear wa_fcat.
endform.                    " BUILDFIELDS
*&      Form DISPLAY
form display .
   clear wa_layout.
   wa_layout-zebra = 'X'.
   wa_layout-colwidth_optimize = 'X'.
* wa_layout-box_fieldname     = 'SEL'.
* wa_layout-edit = 'X'.
   perform build_sort using 'BANFN' '1' 'X'.
   call function 'REUSE_ALV_GRID_DISPLAY'
    exporting
*   I_INTERFACE_CHECK                 = ' '
*   I_BYPASSING_BUFFER                = ' '
*   I_BUFFER_ACTIVE                   = ' '
      i_callback_program               = sy-cprog
*   I_CALLBACK_PF_STATUS_SET          = ' '
    I_CALLBACK_USER_COMMAND           = 'USER_COMMAND '
      i_callback_top_of_page           = 'TOP_OF_PAGE'
*   I_CALLBACK_HTML_TOP_OF_PAGE       = ' '
*   I_CALLBACK_HTML_END_OF_LIST       = ' '
*   I_STRUCTURE_NAME                  =
    i_background_id                   = 'ALV_BACKGROUND'
*   I_GRID_TITLE                      =
*   I_GRID_SETTINGS                   =
      is_layout                        = wa_layout
      it_fieldcat                      = it_fcat
*   IT_EXCLUDING                      =
*   IT_SPECIAL_GROUPS                 =
     it_sort                           = it_sort
*   IT_FILTER                         =
*   IS_SEL_HIDE                       =
*   I_DEFAULT                         = 'X'
    I_SAVE                            = 'A'
*   IS_VARIANT                        =
*   IT_EVENTS                         =
*   IT_EVENT_EXIT                     =
*   IS_PRINT                          =
*   IS_REPREP_ID                      =
*   I_SCREEN_START_COLUMN             = 0
*   I_SCREEN_START_LINE               = 0
*   I_SCREEN_END_COLUMN               = 0
*   I_SCREEN_END_LINE                 = 0
*   I_HTML_HEIGHT_TOP                 = 0
*   I_HTML_HEIGHT_END                 = 0
*   IT_ALV_GRAPHICS                   =
*   IT_HYPERLINK                      =
*   IT_ADD_FIELDCAT                   =
*   IT_EXCEPT_QINFO                   =
*   IR_SALV_FULLSCREEN_ADAPTER        =
* IMPORTING
*   E_EXIT_CAUSED_BY_CALLER           =
*   ES_EXIT_CAUSED_BY_USER            =
     tables
       t_outtab                          = it_po[]
exceptions
    program_error                     = 1
    others                            = 2
   if sy-subrc <> 0.
     message id sy-msgid type sy-msgty number sy-msgno
             with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
   endif.
endform.                    " DISPLAY
*&      Form top_of_page
*       text
form top_of_page.                                           "#EC *
**********Create report header*********
   refresh it_lshead.
   clear wa_lshead.
**********To display date in header*********
* write: s_badat-low to c_low dd/mm/yyyy,s_badat-high to c_high
* dd/mm/yyyy.
* if s_badat-high is initial.
*    concatenate 'Dated on' c_low into c_date separated by space.
* else.
*    concatenate 'Dated between' c_low 'and' c_high into c_date separated
*    by space.
* endif.
   wa_lshead-typ = 'H'.
   wa_lshead-info = 'PR To Payment History'.
* 'Pending Indents History -

We had a requirement to retrieve "aging of receiveables" by customer. Basically, it goes thru each record and depending on the due date places the amounts in the following buckets (example). 0-30 day Overdue, 31-60 days Overdue, 61-90 days overdue, 30+ days overdue, 60+ days overdue) etc all the way to 6+ years overdue.
There are also cooresponding buckets for coming due analysis. For example, what is: 0-30 days coming due, 31-60 days coming due, 30+ days coming due, etc...
To do this, first I needed to be able be able to produce an open items statement at any given time in the past. Now, this seems impossible because of how the items go from open to cleared all the time. And an item that was open one month ago, may not be open anymore.
What I did was first remove any selections on item status. Then compare the posting date with teh key date in the past, if the posting date is less than or equal to the key date, keep the record.
Then compare the clearing date with the key date. First, keep all that are #. (This keeps all records still open from that posting date/key date)
Then, add another check for all items that were cleared after the key date (GT Key Date). This gives you the open items on that date.
Hope that makes sense. Let me know if you want clarification.
/smw

From which table ,i ll get both the invoice and cleared amount ???

Hi Friends,
i am making a report for my sales client where finance part is also required.
the requirement is : the sales people want know the status of the invoice generated at their end.the report shud be like if they enter the invoice no,fiscal year and coustomer they will be able to see the status of the invoice.how much pmt has received for that particular invoice,wheather it is open or fully cleared?
From which table i can get both invoice no. and the payment/pmts rerceived against that invoce/invoices.
plz guide.
Regards,
Biswa

Hi,
SAP Standard Report itself covers all the requirements mentioned. With FBL5N, we get to know how much has been invoiced, paid and cleared and how much advance has been paid by customer etc., in one screen. Apart from this we have also all signs which show, which all invoices are due, overdue and its easy to analyse as well.
Was this requirement given by client after seeing this standard report?
Hope this info is helpful.
Regards,
Venkat

FBL5N Review Open and Cleared Invoices per Customer

WHen one of our users goes into FBL5N to review open and cleared invoices he adds the WBS and the Profit Center. When the report runs it is blank. I looked at the invoice itself and the WBS and Profit center is on the invoice but I don't know why it doesn't show up on the report. Can anyone tell me why this happens? Do I need to make any kind of adjustment before running the report?
Thanks

I looked at the VF03 and there is a WBS and Profit Center on the Invoice. If this report shows Open and Cleared invoices then it should bring what is on the invoice in the report but doesn't.
I had someone email me this response"
Hi linda,
For your info, The reason why profit center and WBS element blank in report FBL5N is, this report purposely used to display subledger account.When me made a posting, balance sheet account is not require
cost object.Only PNL account require cost object.
Regards,
Abdul
I would like to know what other report in SAP shows open and cleared invoices with the Profit Center and WBS?

Revenue: Gain and clearing acct

Similar Messages

Maybe you are looking for