Vendor due date analysis and vendor aging wise analysis

Could u please explain vendor due date analysis and vendor aging wise analysis. what is the differnce between and with t code y specify

Hi Venkatkumar,
Vendor due date analysis refers to the date on which the bill becomes due for payment based on the payment terms and base date. It gives a detailed report of all vendors whose bill have become due for payment on a particular date (Key Date).
Vendor agewise analysis refers to the grouping of amounts due to vendors for various periods, for e.g. 0-30 Days, 31-60 Days, 61-90 Days & so on.
T code for Vendor due date analysis is S_ALR_87012078 - Due Date Analysis for Open Items.
T code for Vendor agewise analysis S_ALR_87012084 - Open Items - Vendor Due Date Forecast
Thank You.
Regards,
Ameet

Similar Messages

Vendor Due Date analysis ( delete posts )

delete
Edited by: Edgar Almonte on Mar 13, 2008 1:58 PM

Hi Venkatkumar,
Vendor due date analysis refers to the date on which the bill becomes due for payment based on the payment terms and base date. It gives a detailed report of all vendors whose bill have become due for payment on a particular date (Key Date).
Vendor agewise analysis refers to the grouping of amounts due to vendors for various periods, for e.g. 0-30 Days, 31-60 Days, 61-90 Days & so on.
T code for Vendor due date analysis is S_ALR_87012078 - Due Date Analysis for Open Items.
T code for Vendor agewise analysis S_ALR_87012084 - Open Items - Vendor Due Date Forecast
Thank You.
Regards,
Ameet

Age-wise analysis

Dear Gurus,
How i will get in details of the age-wise analysis for the customers & Vendors? I am having the detail transaction codes but my user need that in a drilldown report.
Please help me.
Satya.

Hi
USE S_ALR_87012178 for your requirement.you need to create areport in report painter at GR01 to have adrill dwon reports.
sridhar

Requirement for Customer Overdue Age wise Analysis

Dear Experts,
I do have following requirement.
E.g.
Cust Nam | Credit Term | Total Outstanding | Withing Cr. Period | Total O/due | Overdue Analysis (1-30, 31-60,61-90,181>)
001 | 30 Days | 3140 | 743 | 2398 | 941 819 596 42
For each Customer had particular payment term which means that Customer has given some days before which he has to do payment then after payment is overdue.
Total Outstanding = Oust. Withing Credit Period + Overdue Outstanding
& overdue Analysis will give bifurcation of total overdue, from Customer Payment terms end.
I am developing this report from Cube 0FIAR_C03
Now I can easily get the values age wise without including any condition of payment Term.
My Problem is How to get age wise analysis dynamically as each customer has different payment terms.
Please help me out.
Regards,
Divyesh Khambhati

Any Answers..... ????

Age wise analysis reports of customers and vendors balances

Hellow Gurus,
can any one advise me regarding, Is there any T.Codes for Agewise analysis reports of customer and vendors other than
1.S_ALR_87012085.-Vendors
2.S_ALR_87012176-Customers
I have tried these two reports.
Reports are very lengthy and gives information of each Customer/Vendor in 15 lines which is not required.
Can you please advise me, how to get data in given template as follows:
Cust.Code| Name |Total OS| 0 - 30 | 31 -60|60- 90| 91 - 180| above 180
140333 | xyz | 3500 | 500 | | 3000 | |
140334 | abc | 9000 | 3000 | 1000 | 2000 | | 3000
Please treat it as urgent,
I will give points
Thanks&Regards,
Kumar.

Hi Kumar,
For customer balances use t code f.23
for vendor balances use t code f.42
and select from period to to period.
go to screen layout and select required fields
regards
prasad

Vendor due date analysis

Frnds
I need to generate the report which consists of Vendor number, vendor name and invoice no with total amount of invoice and due date of that invoices.
is it possible i cna get all the above required information in one report?
actuall i tried to check out that due date analysis report but didnt fullfill my requirement.
Please reply asap
Thanks

Hi Methew,
There was a similar post for transaction FBL5N, please refer below post:
Name field in FBL5N transaction
"You need to code BTE 00001650 to add extra data to your FBLxN reports.
We have added name for customer and vendor to our FBLxN reports. We even added to FBL3N since we use line item management on our reconciliation accounts. It provides an alternative view of your subledgers with the name of the customer and vendor to boot.
"
Hope this helps.
Pls assign points as way to say thanks

Due Date Indicator on vendor line item

Hi,
We have raised a credit memo via logistics invoice verification.
The baseline date is 21/10/2008 and the payment term is 31
days from month end. That makes the credit memo due in 40 days time. However on the vendor open item list (FBL1N) the due date indicator is set to "DUE". This should be set as "NOT DUE". The payment run (F110) is picking up this line item in the payment run, when infact it should not do so.
Please help.
Many Thanks
Pops Balram
Toyota SA

The first answer is the general rule: the due date of a credit memo is the baseline date.
There are 2 exceptions: if you put the number of an invoice in the field BSEG-REBZG (Number of the Invoice the Transaction Belongs to), the due date of the credit memo is the due date of the invoice.
2nd exception: if you put the constant 'V' in this field REBZG (you can do it thru a substitution rule), the due date will be calculated the same way as for an invoice.
You can see this in the documentation of the data element REBZG:
A special rule applies to credit memos which have a "V" in this field.
The due date is determined in the same way as for an invoice. If the field is empty (containing neither a document number nor a "V") the due date is the baseline date for payment.

Due date on a Vendor Debit Line Item

Hi,
We have a debit line item in Vendor Open items. The Baseline date is 09.06.2010 with 30 days net payment terms, but the due date is showing as 09.06.2010 and not 09.07.2010.
Any idea?
SAPFICO

For a credit memo the due date is the baseline date. This is the default rule. If you want that the credit memo is taken in account with payment terms, you must either link it to an invoice by filling the field REBZG with the invoice number either put the constant 'V' in the same field (REBZG). With 'V' in REBZG, the credit memo is taken in F110 according to its payment term.
see documentation of data element REBZG.

Vendor Evaluation by Material and Material Group wise

Dear Folks,
Customer requirement is to see subcriterion level scores of Vendor
Evaluation according to material, Material group wise. But the
datasource provided by SAP is providing the data according to
Purchasing Organisation level and Vendor level (0MM_PUR_VE_01).Is it
Possible to break the scores according to material group and material
as TC in r/3: ME6B provides ranking based on Main Criterion level
scores. If possible, what is the logic?
Thanks in Advance

Hi Anil,
Thanks for ur reply.
But Customer requires vendor evaluation data through Automatic route.
0MM_PUR_VE_02 caters to semi-automatic data which needs to be configured in r/3, and customer doesn't want to do that. Is there any other solution.

Invoice-wie Due Date List for Vendors

Hi,
Please inform me, if there is an report for vendor informing exact the Due Date for each Invoice Drawn for that Vendor
Regards
Ashwin

Use Transaction Code FBL1N & EXECUTE, then you go for
change layout button,
select "Net due date" field & activate(means get the field from right side to left side).
System will give the due date each invoice wise.
chandra

Vendor Master Data - General and Company Code Data

Hi,
We are collecting vendor master data requirements. The requirements that I have are for Vendor General Data, Company Code Data (Accounting Info, Payment Transactions, Correspondence etc.) and Purchasing Org Data. Out of these 3 groups I can only see Vendor General Data that is mapped to CREMDM04 in SAP supplied syndication maps. I am wondering if someone could tell me how much effort is involved to first create the structure in MDM for Company Code data and Purchasing Data and then map these additional fields to CREMDM04 fields?
Why is it that Company Code data and Purchasing Data is not mapped in pre-delivered syndication maps?
Thanks in advance,
M

Thanks Shruti for your reply.
I agree with you. However, our client is really pushing for Company Code Data and Purchasing Org data along with Vendor General Data. Now, this is something that is new to me to do. I have never done this kind of customization before.
I would really appreciate if someone from SAP could give me their recommendation and also help me answer the following questions
1. Is this doable to map and syndicate Company Code data and Purchasing Org data along with Vendor General Data
2. Is it possible to then extract the tables that hold Company Code data and Purchasing Org data from ECC and bring it back in MDM to update MDM tables (that we are going to create for this data)?
3. What's the effort involved in this customization (Considering that we will be extending our repository structure, extend the syndication map, extract new tables from ECC for MDM, create import maps for these tables to import Company Code and Purchasing Org data into MDM)
Regards,
M

Change the Net Due Date of a vendor Document

Hi,
Can anyone please tell me if it is possible to change the net due date of an AP Local document (doc. type = RE) generated by MIRO?
I`ve tried to change the base line date (Bline date) but this field is unavailable to be changed in my company`s SAP.
There is any other way?
Thanks in advance!

Hi
You can change the payment terms
Also
To make any field as modifiable check the document change rules in OB32
Regards
Sach!n

Include Document Date & Doc Due Date in SAP B1 Aging Details Report

We are not able to view the actual document date and document due date from the Aging details report, it should be an essential information that should be show in the aging report. It make no sense that user still have to manually drill into each document to just read the document date/ due date for their aging analysis!!!
Try to imaging that how important this information to a business, for instance, to age the invoice which due for 1 - 30 days, the document date which due for 1 days is categorise into 1-30days aged, the documents due for 30days also categorise into 1-30days aged, however it bring the different meanings to user and user need these information to take the action decision! How useful for an aging report which could not equip user with these basic information to provide user with efficiency to make effective decision???
I think it is necessary to incorporate this level of details to the SAP B1 Aging Report.

Hi Theerawat,
You may check these threads first:
Document Date
Posting / Due / Document date trouble
Re: Posting Date
Re: Difference between posting & system date in Inventory Audit Report
Thanks,
Gordon

Where and how to enter plan data cost and profit center wise to get data in grr1

Hi Gurus,
Appreciate you can tell me where and how to enter plan amount cost center wise for cost elements and profit center wise for revenue elements????
So that we can get this data in grr1 report.....
Can we upload this planned data, if yes how??
Thank you

Hi..
If you use classic PCA, refer to Plan Data Transfer - Profit Center Accounting (EC-PCA) - SAP Library.
If you use new gl pca, refer to Transferring Plan Data from Controlling - General Ledger Accounting (FI-GL) (New) - SAP Library

Urgent due date calculation in vendor ageing(plz solve)

hi everybody there
i have to calculate the due on date
which is calculated as
dueon = BLINE Date (BSIK-ZFBDT) + No of Days(BSIK-ZBD1T)
for this i am using fm
RP_CALC_DATE_IN_INTERVAL
but it is not working .
could u suggest that what is going wrong with this
fm.
i am calling this fm in following code but it is not working , it is going to dump.
could any one suggest me how to use the above fm in my following code so that i will be able to calculate due on date based on above formula.
my code is as follows
*& Report Z_VENDOR AGEING *
*& in this repoet I am calculating the vendor ageing
 which is depending on formula
 AGEING = Current Date(or any date entered by user) Bline Date(BSIK-ZFBDT) *
REPORT z_vendor NO STANDARD PAGE HEADING
 LINE-SIZE 200
 LINE-COUNT 65(3).
TABLES : bsik.
DATA : BEGIN OF t_out OCCURS 0,
 bukrs LIKE bsik-bukrs,
 saknr LIKE bsik-saknr,
 bldat LIKE bsik-bldat,
 wrbtr LIKE bsik-wrbtr,
 lifnr LIKE bsik-lifnr,
 zfbdt like bsik-zfbdt,
 zbd1t like bsik-zbd1t,
 ageing type i,
 END OF t_out.
parameters : p_date1 type d.
SELECT-OPTIONS : s_bukrs FOR bsik-bukrs,
 s_saknr FOR bsik-saknr,
 s_lifnr FOR bsik-lifnr.
SELECT bukrs saknr bldat wrbtr lifnr zfbdt
 FROM bsik
 INTO TABLE t_out
 WHERE saknr IN s_saknr
 AND bukrs IN s_bukrs
 AND lifnr IN s_lifnr.
Loop at t_out.
CALL FUNCTION 'DAYS_BETWEEN_TWO_DATES'
EXPORTING
 i_datum_bis = p_date1
 i_datum_von = t_out-zfbdt
I_KZ_EXCL_VON = '0'
I_KZ_INCL_BIS = '0'
I_KZ_ULT_BIS = ' '
I_KZ_ULT_VON = ' '
I_STGMETH = '0'
I_SZBMETH = '1'
IMPORTING
 E_TAGE = t_out-ageing
EXCEPTIONS
DAYS_METHOD_NOT_DEFINED = 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.
Modify t_out.
Clear t_out.
Endloop.
LOOP AT t_out.
WRITE : / t_out-saknr,
 t_out-lifnr,
 t_out-wrbtr,
 t_out-zfbdt,
 t_out-ageing.
ENDLOOP.

hi sanjeev,
chnage ur code.
note the bolded part.
TABLES : bsik.
DATA : BEGIN OF t_out OCCURS 0,
bukrs LIKE bsik-bukrs,
saknr LIKE bsik-saknr,
bldat LIKE bsik-bldat,
wrbtr LIKE bsik-wrbtr,
lifnr LIKE bsik-lifnr,
zfbdt LIKE bsik-zfbdt,
zbd1t LIKE bsik-zbd1t,
ageing TYPE i,
END OF t_out.
PARAMETERS : p_date1 TYPE d.
SELECT-OPTIONS : s_bukrs FOR bsik-bukrs,
s_saknr FOR bsik-saknr,
s_lifnr FOR bsik-lifnr.
SELECT bukrs saknr bldat wrbtr lifnr zfbdt zbd1t
FROM bsik
INTO corresponding fields of table t_out
WHERE saknr IN s_saknr
AND bukrs IN s_bukrs
AND lifnr IN s_lifnr.
if sy-subrc <> 0.
message 'no data' type 'S'.
endif.
LOOP AT t_out.
 CALL FUNCTION 'DAYS_BETWEEN_TWO_DATES'
 EXPORTING
 i_datum_bis = p_date1
 i_datum_von = t_out-zfbdt
I_KZ_EXCL_VON = '0'
I_KZ_INCL_BIS = '0'
I_KZ_ULT_BIS = ' '
I_KZ_ULT_VON = ' '
I_STGMETH = '0'
I_SZBMETH = '1'
 IMPORTING
 e_tage = t_out-ageing
 EXCEPTIONS
 days_method_not_defined = 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.

data : dueon like t_out-zfbdt.
dueon = t_out-zfbdt + t_out-zbd1t.
write dueon.
 MODIFY t_out.
 CLEAR t_out.
ENDLOOP.
rgds
anver.
if hlped mark points
LOOP AT t_out.
 WRITE : / t_out-saknr,
 t_out-lifnr,
 t_out-wrbtr,
 t_out-zfbdt,
 t_out-ageing.

Vendor due date analysis and vendor aging wise analysis

Similar Messages

Maybe you are looking for