MHKIM : 입력된 maturity date가 System Date보다 클 경우, Negotiable 로 안됨

Note : 357272.1 를 참조 부탁드립니다.
When you run "Update Matured Future Payment Status" you enter a Maturity Date
=> this date entered in parameter is a date used for selection (Not to generate accounting date).
From AP user guide (P.6 110) :
" Payables updates selected payments if the Maturity Date on the payment document is on or before
the date you enter here and on or before the system date. The default for this parameter is the system date."
즉, System Date보다 이전이거나 입력된 Maturity Date이전이어야 대상이 됩니다.
또 다른 자료(Bug 1716593)에서는 "Update Matured Future Payment Status" 프로그램에 대해서 아래와 같이 설명하고 있는데,
The program enforces this by preventing any future dated payment from
being updated to "Negotiable" if its maturity date is greater than the system
date.
입력된 maturity date가 System Date보다 클 경우, Negotiable로 update하는 것을 막고 있다고 합니다.
즉, 해당 maturity date 값에 어떤 날짜도 입력은 가능하지만,
정상적으로 사용하시기 위해서는 오늘날짜와 같거나 이전으로 입력을 하셔야 합니다.

Similar Messages

How to change money market maturity date in TR modul

Dear Friends,
I want to change the maturity date for money market transaction. Currently the due date is 29.09.2008 but I want to change it to 15.04.2008. When I change it using tcode TS02, an error massage
"End of term is before end of calculation period of posted flow."
How can I fix this problem? anyone can help?
Norliza

Hi,
I hope you are required to reverse all posted (fixed flows) flows dated prior to the new term end date.
thanks,

How to handle the maturity date of loan in FCR

In Jilin, we have a contract maturity date and FCR maturity date, the contract maturity date can be less than or equal to the FCR maturity date. If the contract maturity date is less than the FCR maturity date, EFS will be done for the loan account in EOD automatically.
Here is the question from Tongfang, is above functionality added into FCR 4.5 version? If yes, how can we get the contract maturity date and where is the date stored in ?

Adding further clarification and details
Definition of Term :
FCR Maturity Date: It is the maturity date derived by FCR as part of Host Disbursement (Schedule generation). As per FCR the maturity date will always fall on the "Repayment Day" of the loan account. Say for example the Loan term is 12 months and the repayment date is 21st of each month. And, if the schedule is generated on 2013-01-15 then the FCR Maturity date will be 2014-01-21.
Contracted Maturity Date : Is the Maturity date which is in the Loan agreement. This may be different from the FCR Maturity date which is derived based on the schedule frequency and Loan term. Say for example, the Contracted Maturity Date of above account is 2013-12-31. It is commonly termed as CMD.
Restriction : Contracted Maturity Date should be less than FCR Maturity date.
Workflow in Jilin:
1. Loan Account opening : Contracted Maturity Date is passed in Loan account opening Interface. The same is maintained as Loan Attributes (ln_acct_attributes) using the Loans Attributes maintenance API.
2. Later on the CMD can be Inquired or Modified using the "Loan Account Attributes Inquiry" & "Loan Account Attributes Modification" API respectively.
3. On the date of CMD (2013-12-31 in the example above), when EOD Category 13 is executed it will do the Auto EFS of above accounts. As part of Auto EFS it will charge (Raise Arrears) all the oustanding Principal and Unbilled Interest.
4. Also, during the life-cycle of the loan the CMD can be extended. It can be done using FCR screen LN-055 or "Loans Roll Over Instruction Maintenance" API. On the date on which this instruction is maintained, the Loan account will be re-scheduled in "Auto EFS Category". The FCR Maturity Date and Contrancted maturity dates will be updated as per the instruction.
Edited by: PankajKumar on May 8, 2013 2:19 AM

PAYMENT & MATURITY DATE

Hi
Is it possible that the Payment Date is ahead of Maturity Date?
Example.. I have payments/check that should mature yesterday, but i will just draw it today.. So the Payment Date is TODAY and the maturity date is YESTERDAY.
Is this possible? By the way, our checkdate in check printing is based on Maturity Date.
thanks,
emgee

Hi Emgee
I dont think this is possible. The maturity date cannot be earlier than the payment date.
In the case mentioned, you can have the payment date also as yesterday's date along with the maturity date.
Thanks
Vinit

R11.0.3: An Invoice with future dated apyment data flow

제품 : FIN_AP
작성날짜 : 2003-11-18
R11.0.3: An Invoice with future dated apyment data flow
===============================================
PURPOSE
Future Dated Payment Term을 사용하는 Invoice의 Data Flow에 대해 살펴보도록 한다.
Explanation
accounting rule = accrual
.allowed future dated payment
1. Create a standard invoice (invoice amount: 2100, item amount: 2100, payment term : future dated payment)
And transfer it to GL.
* ap_invoice_distributions_all
accounting_date = 2003-11-11
accrual_posted_flag = Y
posted_flag = Y
* ap_trial_balance
accounting_date = 2003-11-11
distribution_amount = 2100
* 해당 data gl_interface table로 넘어감.
2. Posting these transferred journals in gl module
* 해당 data가 gl_interface table에서 삭제 된 후
* gl_je_lines
accounted_dr = 2100 charge
accounted_cr = 2100 liability
3. Create a payment against this invoice with mature date = 12-nov-2003 and then transfer it to gl
* ap_invoice_payments_all
accounting_date = 2003-11-11
accrual_posted_flag = 'N'
posted_flag = 'N'
future_pay_posted_flag = 'Y'
* ap_payment_distributions_all
line_type_lookup_code = 'CASH'
* ap_trial_balance
accounting_date = 2003-11-11
payment_amount = 2100
* ap_checks_all
status_lookup_code = 'NEGOTIABLE'
4. Posting these payment journals in gl module
* 해당 data가 gl_interface table에서 삭제 된 후
* gl_je_lines
accounted__cr : 2100 future pay
accounted_dr : 2100 liability
5. Clear this payment and then transfer to gl
Future dated payment 이고 Cash Management 를 사용하면 Cash Management 에서
Bank Reconcilation을 해주시면 됩니다.
Cash Management 를 사용하지 않으실 때는
"automatic clearing for future dated payment" 를 수행하여서 clear 를 해주어야 합니다.
이번 test case에서는 cash managemnt를 사용하지 않고 automatic clearing for
future dated payment 를 수행하여 clear 해주었습니다.
* ap_checks_all
status_lookup_code = 'CLEARED BUT UNACCOUNTED'
Cash Management를 사용하지 않기 때문에 status가 위와 같이 나타납니다.
Cash Management를 사용하면 option에 따라 status가 cleared나 reconciled로 변경 됩니다.
6. Transfer these cleared payment to gl and posting in gl
* 이 때에는 ap_trial_balance table에는 아무런 영향도 주지 않습니다.
* ap_invoice_payments_all
accrual_posted_flag = 'Y'
posted_flag = 'Y'
* gl_je_lines
accounted_dr= 2100 future pay
accounted_cr = 2100 cash
Example
Reference Documents
N/A

Rohini,
Thanks for your answer; I was out for few days and hence the delay.
What I am looking for is the complete usage model of the following ODS.
1> 0BBP_SC     we have figured it out
2> 0BBP_SCA    we have figured it out
3> 0BBP_DOC    we have figured it out
4> 0bbp_inv    we need help
     Looks like this can be populated from R3 using the following
Data Source    Info Source                    ODS Object
2LIS_02_ITM    2LIS_02_ITM                 0BBP_INV
2LIS_02_HDR    2LIS_02_HDR                0BBP_INV
5> 0BBP_DS     we need help
6> 0bbp_po     we need help
    The same combination is also used to populate the 0BBP_PO as well. We suspect that 0BBP_DS will then be populated from both 0BBP_INV and 0BBP_PO. At least that what we though after activating the BC and reading the sap help on BC for SRM.
We are doing a proof of concept and want to know all the ODS with data. We want to build an end to end (Shopping cart, approval, Doc flow, PO data with value, Invoice data with Value) and struggling to understand the model surrounding this three ODS ( 0bbp_inv, 0bbp_ds, 0bbp_po). Any help in this area will be appreciated.
Thanks
Arun

Fetch data from same table

Hi All,
Oracle 10g
The data in cust_link_tab is of 2 systems. Internal and External.
I want to compare fields (date, ccy, type) of the below table on the basis of linking id.
currently i am using a query like this:
SELECT F.SOURCE,
case
     when fac.type = f.type then
     'Y'
     else 'N'
end fac_cusip
FROM cust_link_tab FAC, cust_link_tab F
WHERE
FAC.LINKING_ID = F.LINKING_ID
AND FAC.ROWID!=F.ROWID;
But if there is more than one linking_id. this won't work correctly.
SQL> DESC CUST_LINK_TAB;
Name Null? Type
FSRC_ID VARCHAR2(10)
SOURCE VARCHAR2(10)
DSRCL_ID VARCHAR2(10)
CCY VARCHAR2(3)
MATURITY_DATE DATE
GLOBAL_CMT NUMBER
LINKING_ID NUMBER
TYPE VARCHAR2(10)
SQL> select *from CUST_LINK_TAB;
FSRC_ID SOURCE DSRCL_ID CCY MATURITY_ GLOBAL_CMT LINKING_ID TYPE
111 INTERNAL 900 usd 1000 ER
45 EXTERNAL 600 usd 1000 TR
454 INTERNAL 700 usd 500 II
SQL>
Thanks.
Edited by: user545846 on May 9, 2009 10:17 PM

SQL> select *from CUST_LINK_TAB;
FSRC_ID SOURCE DSRCL_ID CCY MATURITY_ GLOBAL_CMT LINKING_ID TYPE
111 INTERNAL 900 USD 1000 ER
45 EXTERNAL 600 USD 1000 TR
454 INTERNAL 700 USD 500 II
32 INTERNAL 300 EUR 25 2885 PO
96 EXTERNAL 600 USD 434 2885 PO
Basically we need to compare the fields ccy, global_cmt,type for internal and external
source.
Linking id is used to link the data. we are expecting the fsrc_id,source,dsrcl_id and result whether 'Y' or 'N' which we can do using a decode or case statement.
source, fsrc_id and dsrcl_id are the primary keys (composite) for this table (cust_link_tab).
Apart from this we have the map table which keeps the fsrc_id, dsrcl_id, dsrcl_id of the
internal system and the corresponding external fsrc_id and dsrcl_id. The data is loaded using
the linking_id.
But this table does not maintain the details like ccy, maturity date, and type.
Please give your suggestions. thanks

Incorrect net due date in FBL5N

Hi,
I have problem with incorrect net due date in FBL5N. I made payment term "120 day end of month". Configuration of payment below.
Maturity date whitch is invoice is correct. For example: Invoice was generated on 6th of February and the maturity date is 28th of June. Problem is that the net due date in FBL5N is incorect, it means net due date is 8th of June. This date isn't counted from end of the month.
Does anyone have any suggestions on a fix?
Thanks

SAP has standard functionality for credit note (without invoice reference) to populate net due date as base line date itself irrespective of payment terms. Hence net due date and base line date is appearing same in FBL5N.
For this, we have to put “V” in invoice reference field (BSEG – REBZG). By putting “V” SAP correctly populates net due date in FBL5N. We have done this manually for below mentioned customer and its working fine. It can be automated by writing user exit mentioned in the link.
http://scn.sap.com/thread/342202

Essbase Date Measures as DATE in OBIEE

Hi,
We have created an ASO Cube in Essbase 11.1.1 with a Date Measure member call "Maturity Date" in Measure dimension (Tagged as Accounts).
Once we create the Physical layer Administrator tool on OBIEE this member refers as a double data type. And also when we create a criteria on Answers and displays the result it is shown as a number.
But on excel (with essbase add-on) data shows as a date. (Ex: 2009-09-20)
Can anyone tell what has to be changed to display a Date Measures as Date type on OBIEE or suggest another alternate.
Thanks!
Nilaksha.

Hi Nilaksha,
I thought you might say that, I think this is because Essbase doesn't use data types as such, all data is stored as a value and characteristics of that data or how it is treated are more like meta data. This certainly rings true for the time dimensions I have seen. I think your best bet is to look at how you can format the numbers in the columns to make them appear in the format you require.
Regards
Ed

Change of due date field in F-36 t.code

Hi
I posted Bills of exchange transaction thru F-36 t.code. Due on will be the future maturity date of Bill. While entering user made mistake. Now i want to change the date. I tried with Fb02 but it is grayed.
Pls suggest me.
Thanks
Sneha

Hello,
Check the document change rules in OB32.
I believe you are referring the following field.
BKPF-XWVOF
If yes, then
OB32,
Give account type, transaction type, company code.
Tick field can be changed.
Save.
Regards,
Ravi

Adjusting Date Calendar

I would like to set up a date calendar so that the user can select a year rather than scrolling through the months to get to the next year.
The purpose of this is that the user can select a start date and a maturity date on different products ie. loans. We can then use the information (difference between dates) to determine payments, etc.
Has anyone any information on this?

When the calendar is displayed, click on the year and you'll get scroll "arrows" where you can quickly change the year.

I need to raise LC for import PO . Need to track the LC and its maturity da

Hello ,
I have this scenario where I need to raise LC for import PO . Need to track the LC and its maturity date .
How to do this. Please guide .
Regards
subbu

HI,
I had raised the same issue few days back i got the same reply.From SD side it can be mapped not
from MM side.Raise an OSS note to SAP,get their reply and give it to the client.This is the only way out
murugan

E72 - Honeymoon to Divorce.

Like many of you here, I've had quite a few mobile phones through the years and it's always a source of great excitement when a brand new phone lands on your desk. The new OS to explore, the Apps, the form factor. The downside of playing around with so many phones through the years is that there is no perfect device, no form factor that's perfect in every situation and no OS that can retain your interest beyond a few months before it's time to convince yourself that you need to try a new 'thing' which will solve everything for you (and make you more productive).
As long as you know this up front and understand your interest is going to stray, you can get a fairly balanced view of what makes a great, as opposed to a good phone. Here are my thoughts on the E72.
As a background to my adventure, I recently had an iPhone and although it's far from perfect I was fed up with the lack of a physical keyboard. It's not that I failed to bang an email out but I found it tedious when I made a typo and then had to spend 10 seconds trying to edit the message by tap'n'hold to move cursor, delete (x10), tap'n'hold to continue typing etc. It just got 'old' so I started to look for a device with a keyboard - remembering with fondness the keyboard on the old E61, Treo680 and even the Blackberry 8700 (love those clicky keys!).
Last October I bought an E63 because it was 'cheap' and to see if I could get back into using S60 + keyboard after such a long period in iPhone land. To my surprise, the E63 whilst creaky and a little too 'red' for me, was good, it, I even took it to Hong Kong on a trip and left the laptop behind as an experiment (it worked.. but only just) although it obviously had some shortcomings. Toy like Email client, browser standards, ram, camera etc.overall it was a positive experience that made me want to explore further.
I had bought a Nexus One in January the day it was released and although it's a super phone, it still had no keyboard and the Droid keyboard is awful so having had a half decent experience of the E63, I decided the E72 was the next best thing and decided to snap one up.
The Honeymoon / First impressions.
First impressions of the E72 is that it's a 'handsome' phone - not a good looking phone or a kiddy toy but a good, solid, classy looking phone for business. The keyboard was as good as the E63, the form factor was obviously near identical other than the materials being of higher grade and obviously it's slimmer and easier in the pocket. First impressions were very good.
The screen was a step back from most new phones, especially the Nexus One's gorgeous High-res effort but it's certainly clear and as it needs to be judged as a utility, not a spec-sheet competition so it fitted the job of a phone with a keyboard. The screen was clear and bright and easy to use.
Software seemed to be not much of a step up from the E63, I was expecting a higher grade of Application to be included and to my surprise (not disappointment) there was little on the surface to distinguish the E72 from the E63. I disliked the new transition effects as they felt like Nokia had iPhone envy rather than functional enhancements.
Camera quality was very good for a phone although I don't like the viewer application with its spinning wheel of pictures - iPhone envy again? what's wrong with a 5x5 thumb view that would work well with the D-Pad? Once again, it works but it's not designed to optimise the experience of the form-factor.
The touch-pad, I quite liked it, although I rely on the D-Pad more as it's just too small a surface to be useful.
The Email client. At first it felt like a step back from the E63, the E72 client seemed 'bare' for some reason and I also wanted to make the font smaller so I could see more email headers on the screen at once (cant do it), I put all of this down to the email client being prosumer rather than consumer
Overall, first impressions were good with the caveat of some changes to what I was used to, no bad thing.
Married life / day to day:
Day to day, as a Phone, the E72 is fantastic. Calling people by typing their name is so much easier than 'flicking' through lists, call quality is absolutely top notch, signal strength and 3G connectivity is years ahead of my old iPhone/Nexus/Blackberry/Treo and really shows that Nokia know how to make connectivity work from a technical perspective, something that almost every other company from HTC to Apple trail considerably behind on.
Short-cuts to communication 'tasks' are as good as it gets. Series60 is a superb, intuitive and well polished hierarchy of menus to get your calls and messages answered, read and replied to in record time. I can't praise the work that's been done over the years any higher.
Setting up email was easy enough as standard manual entries although after a week or so I decided to setup mail through OviMail - this was painful.
I'm pretty experienced in these things and technically very able (I'm into heavy tech for a few decades) but this was a challenge for me. Passwords, logins, usernames etc.. it all becomes one mixed up frustrating jumble that I think would have any mere mortal turned off or turn to their I.T. department in haste. It took me a couple of days to get it set up properly and even then it felt like it was hanging by its fingernails. Blackberry by contrast feels military strength compared to OviMail and BB's are far from a walk in the park when it comes to ease of setup. Once I did get OviMail setup, it did work but I always had the feeling that it might break at any minute if I touched the wrong option. To its credit, it never actually did break, but it just left a bad taste that I never quite got rid of.
Nokia are obviously moving heavily into services such as cloud infrastructure with Ovi services, Music etc. This push into services is being implemented the same way as Microsoft did a while back where none of the teams talk to one another other, it's all through a technical specification sheet. The E72 software works as silo-applications with each requiring the same login information being entered independently rather than simply log into Ovi services once, per device, and everything else flows. This constant entering of information per application is what makes S60 feel dated, it's unforgivable for a product manager of an integrated device like the E72 to let this pass. It either shows weak leadership within the product team or it shows a lack of cohesion between the teams within Nokia - again, a failure in leadership although higher up the chain of command. Yes, it's a big company but to let this happen shows the company has too many toothpaste managers and not enough tech savy people that love their work.
A second level of confusion is the PC software that's bundled and are encouraged to install. Nokia's PC suite is solid, but why am I encouraged to install Ovi software and map loaders which seem to replicate the same job? It's not a problem with the device itself, but it significantly dilutes the user experience to bemused confusion. Obviously this is not the E72 but companies can no longer separate user-experience from device experience, especially when they're intertwined to the degree that they are these days.
Setting up through a Mac was a lot simpler as you dont get all the Nokia apps, you just use iSync after manually searching for a plugin online. You loose some features but you do that with Macs anyway (yes.. I use one every day so stay away mac fanboys).
The Calendar and contacts apps are adequate but feel dated and slow and could do with some new views and features.
No Internet Radio feature as was in the E63.. I needed to scour the web to add this manually for some odd reason.
OviStore is an average implementation with some average applications. As the E72 is a prosumer phone, not having games and apps, whilst good to pass time on a 747 are far from needed and using the stock built in applications was fair enough.
Music player is 'functional' and did its duty without a hitch.
One thing that worked particularly well was Skype. I do a lot of international calls and I think the Nokia implementation is the best around, hopefully they can make more of this feature as times goes by.
Ovi/Nokia Maps. Where do I start with this? It's absolutely wonderful. I went a few trips to California, installed the map data on the device for California and Nevada and it worked perfectly. I bought a little car stand for $10 in Fry's electronics which worked for the trip and this just blew me away. Even with it's small screen, this has made me give away my Tom-Tom which I took with me on trips and never turned on once. Full marks.
Battery life is incredible, for a device in this day and age to last 4 days on a single charge is simply stunning. I'll put up with the lack of a decent movie player any day if it means I get 4 days out of a single charge. Once again, Nokia should shout about how awesome this is to anyone that will listen. iPhone users get trained into worrying about battery life and turning things off where possible, not having to worry about battery life is an absolute blessing. Well done Nokia.
To give an example, I drove from San Francisco to San Diego which takes 9 hours. I had the GPS running giving me directions, I had the Phone wired into AUX in the Car playing some Audio books for the entire duration and the battery life still had a good 2 days before needing a charge. The E72 battery life will forever go down in Legend as an 'I remember when' story.
Not that this piece is about comparisons with other Phones, but coming from the UK it means heavy roaming charges if I use data. I took a similar business trip with a Nexus One and it was pretty much useless as their GPS mapping software is US only in features and, it can't work with offline maps and would have cost me a pretty penny to use on a roaming contract with all the Data it would download. The Nexus one is arrogantly setup to be of use to US consumers, overseas users get a half-glass feature set (no turn by turn / street-view etc..).
The Divorce:
There is a time in the daily life of using a Phone where the 'unique characteristics' of the Phone start to become tedious. This happens with all phones and gadgets, if it didn't we'd all still be using Videostar VHS recorders (does that give my age away?).
After travelling up and down California, replying to a hundred or so emails over the course of a week, I noticed that I had just sent a handful of emails without being connected to Wifi. After examining a little further I worked out to my horror that the email client does not connect over Wifi - ever. It fails to work with Profiles, connection orders or anything remotely standard on almost any other Nokia/other device. Profiles for the uneducated should remain an unknown, it's a black art from a previous era that has no place in a modern day smartphone. Devices should simply connect over Wifi if connected, otherwise prompt the user if it's roaming - simple as that, no 'profile' needed. This is how all smartphones work, even the senile Blackberry OS does this out the box.
I foolishly presumed that as the old mule E63 has worked over Wifi, the E72 being an 'evolved' device would also have this feature as standard. Nokia took it out.. what the $£%$£?
I can only imagine at this point in time, Nokia deliberately engineered this deficiency to keep carriers happy. The E63 being 'consumer' can be used over wifi with a standard phone tariff, the E72 being a 'prosumer' device needs the user to buy a more expensive Smartphone tariff. I can't for the life of me work out why Nokia would remove a standard feature that was in all of their older phones.
This little oversight of the Email client not connecting or alerting me that it was using a non-wifi connection actually cost me over 100 euros in data charges. This is simply not acceptable, no excuses, no patch-it at some point please. It's simply stupid. Yes, I've used Profimail etc.. but should I need to on a messaging device? I bought the phone for this feature, paying to replace it is simply counter-intuitive when so many other options exist without wrestling with work-arounds.
Other than creating a hole in my wallet, I also through sheer paranoia removed all my Email accounts from Ovi and set them up as 'pull' accounts where I manually check my email. I need to do this simply as I travel so much and the roaming feature sometimes works - it's back to the holding on by your fingernails thing with this device, it should work but you're not quite sure.
Running the much loved Maps application brings up a notice asking to connect to download data - even after saying NO, I still fail to have faith in the profiles working which removes the confidence you have in the device, It removed the feeling that you're in control and that really gets to you after a while. If Email has been engineered to ignore profiles, what else if going on under the surface, I should not have to read forums to gain confidence and if I was a typical consumer I wouldn't know where to start to find this out.
Other problems starting to appear are that the E72 is starting to crash a few times every week, the dreaded space-bar problem has appeared, I can't upgrade the firmware for some reason even though I'm a few revisions behind (I bought it unlocked from Nokia), the back cover feels like it's starting to work loose and has fallen off a few times and the transition effects needed to be turned off (only half of them disappear). All of these things are in the forums here to some degree. Sometimes they annoy, sometimes not, but overall when you're having a tough day they all get to you.
Summary:
There's a scene in the Film "Flash Gordon" where a poor chap puts his hand in a tree trunk as a drunken game to see if the creature that lurks will bite him, he puts his hand in, smiles then slowly starts to pull his hand out before getting bitten just before he pulls his hand to safety - for some odd reason the E72 reminds me of that this. You approach with trepidation, become comfortable with the device then you get bitten just when you think all is well and you're about to make off with the cash.
The E72 is the end of an era. You can tell by Nokia's responses to the problems on the E72 that their corporate focus is no longer on developing S60 but maintaining it with minimal effort.
Their focus is now on Maemo and 300 other pressing priorities, their software engineers are stretched way too thin working on OviCloud services, Maemo and a multitude of new devices and holes/low quality are starting to become standard. This is starting to reflect on devices like the E72 which should be a flagship device but instead is not much more evolved than an 'old' E63 at half the price - which incidentally has an email client from the same codebase that can download over wifi. In many ways, plastic aside, I thought the E63 was better, more stable (for me) especially for the price.
Nokia will obviously keep churning out yearly revisions to the S60 line (C6, E5 etc). But you know for a fact that they're pretty much the same devices with a cavalier attitude to improvements and the least engineering time to fix bugs/features as they can get away with. Arrogant yes, damage to the Nokia Brand by doing this? Absolutely. It will take me 5 years before I return to a new Nokia device after seeing the speed of progress and responses despite some great promise. Look how quickly Google turned around a Nexus One update with multi-touch after an outcry - it can be counted in days after launch, not 'devices' as seems to be the case here.
The E72 device feels great, I love the form factor, the Keyboard is not the absolute best as that remains with Blackberry but it's certainly one of the very best. The phone functions are second to none.
Ovi-Maps is just brilliant and the Battery life is as covered above is the stuff of legend.
In many ways the E72 is the device I'm least able to move on from as there is so much to like and so much potential, but the amateur email implementation and creeping software problems makes this device seriously handicapped for anyone that travels or cares about the significant roaming fees that this device is designed to incur which is a genuine shame.
Hopefully these things will get fixed in firmware upgrades, I'm sure some of them will but why should I wait? this is not the 1990's - this is mature technology and a (very) mature Operating system which should be solid as a rock.
I like many on this forum would like to see Nokia do well but they've simply not stepped upto the plate by fixing basic feature holes nor have they communicated to the community that they're listening and will fix any of the problems. Instead they've announced new devices to replace the handsets that still have serious flaws. This is not the actions of a company that listens but a company that simply churns like a machine on a pre-set course with nobody at the wheel.
Despite much to like about the E72, I for the single reason that Nokia seem to have no ears to hear and no fingers to type, am out until further notice.

Gentlemen,
Thank you for your kind words and replies to my experiences with the E72. Since writing the original post my Firmware has been updated not once, but twice no less.
As I bought the device 'vanilla' style from Nokia online, I have no idea why I was unable to use PCSuite to upgrade my firmware despite my E72 being clearly a few revisions behind, I also tried upgrading from the device itself and it gave me a firm but fair 'No'; one day after hammering the server for a few minutes with constant requests, Nokia's servers finally rolled over and let me download an upgraded firmware directly onto the device. I can only presume it was a load-balance issue with their servers although open to being educated otherwise, I have no idea why PCsuite/Ovi Suite failed to upgrade the E72 despite downloading the new firmware every time I checked for an upgrade. Not to worry, these things happen.
The new firmware (031.023) has some new features with a few new icons added and many bugs fixed. If I were to relate it to my original 'Honeymoon to Divorce' post, it's a bit like the Wife has put on some heels and lipstick and has lost a bit of weight in an attempt to win my affections (sorry female readers, I know it's unforgivably sexist).
In that spirit, and considering the Nexus One that I moved back to using is a poor quality phone (remember that function?) I thought I'd give the E72 another spin to see if it fixed my original problems. I reset the device, cleared the SD card and set the device up from what should be a clean and sparkly install.
You'll all be glad to hear I wont go into another vast post as most of my thoughts still stand, however:
Email:
The new email revision does fix some of the Wifi connection issues I was having. I'm glad to say it's faster and does indeed work over Wifi although it seems very slow when updating itself. Other phones seem to download a full header+message infinitely quicker that the E72. As I've been using the new firmware for a week solid, I'm increasingly annoyed that I need to download the HTML versions of email manually which takes terra-years; I believe the E71 email client can be configured to download HTML versions automatically as can my old E63 so why not the E72? Did someone 'merge' the old email source-code into Nokia messaging when they made the E72 client?
A new bug has appeared that seems to lock into a constantly 'downloading' logo loop - where it never completes the email download. I need to click 'cancel' manually then the email appears as if by magic. There are other niggles that have seemingly crept in such as when using the E72 without a SIM card, the email client will work for a few hours then simply stop connecting manually or automatically, needing a reset to come to life again. **Geek alert on** As an old games programmer, this looks to me like a memory leak problem that could be easily found (or a thread that's gone haywire) - especially considering good debug tools have been around since it's Psion Series 5 roots. **Geek alert off**.
I'm sure your mileage - or bugs - will be different from my own depending on your own unique circumstances but it's another of those two steps forward, one step back things which Nokia seem to do with the E-series.
What's frustrating is the phone part of the E72 is world-class which when coupled with a bottom of class email client it defeats the reason to have a QWERTY in the first place. I'd trade the Phone stability for a best of breed email client on this device in a heartbeat. I've not tested the Gmail client as RistotheGreat did (above) so this may solve the email conundrum for some.
Memory:
As Beowulfpt above originally questioned, Ram is becoming as scarce as the Yeti. Before the firmware update I had plenty of spare RAM, after the firmware update I get low-RAM notifications every few days and I'm running the exact same email accounts without running ANY 3rd party software whatsoever.
Stability:
Overall crashes of the device are now far and few. It seems to be a step forward. Well done Nokia.
Other:
It's worth mentioning (thanks DeadKenny) that you can now sign in once to Ovi services and it's supposed to work across the Ovi suite of apps. I've not checked this personally as I'm using the device without adding extra apps at present but there was a note in the firmware note when upgrading.
Internet Radio has now been added back to the Radio client - no need to go hunting for external versions of this anymore. This, as before, works pretty well.
To close, it's interesting to read others frustrations (above) with this device, there are many good things about E72 and I can live with compromises in a device if it does other things well. In the case of the E72 it's a great phone but it's an incredibly poorly implemented email client, too poor if you ask me. If Nokia added a half stable email client with HTML (as they had many years back in other similar devices) then I'd put up with the tedious old-school 'profiles' and an old-school approach to connectivity and other such compromises. As it stands I can't in all honesty make this my main device when it's fails to offer a usable email client that I can use without frustration on a daily basis despite the new lipstick.
As Nokia are so close to making this device 'ok', should I go back to the Nexus and put up with the lack of a keyboard and poor phone functionality, but excellent mail client - waiting for one more Firmware revision from Nokia? How long did you good E71 owners need to wait until Nokia fixed the problems for you? I really want to like this device despite my sheer frustration at it's implementation.
Note: Despite the E72 still sitting on my desk and not on Ebay, my original post conclusions about Nokia's tardiness in selling half-finished devices still stands. I'd find it incredibly difficult to justify buying a new Nokia device for a number of years. This is a real shame when they have so many voiceless employees within their organisation that if given half a management-vote could turn this cheap strategy around.

Is it possobile to get a discounted vwesion of leopard for recent Mac buyer

I bought my Macbook just under a month ago now ad was told in an apple store tha t might be possible to get the new OS cheaper because of how recently i had accquired my mac
anyone if this posible ? and if so where would i get it from??
thanks alot
Martyn

Frank: FWIW, my advice is to buy your new iMac now, while you can still get one that comes with Tiger preinstalled. Then you'll have a solid, mature operating system and won't be stuck with the first version of Leopard, which is bound to have bugs. The Leopard Up-to-Date program (linked above in this thread) will let you buy Leopard installer discs for only $10, and then you can wait for the second or third incremental update to be released and squash most of the early bugs before you install Leopard and immediately apply the updates.

Insertion problem .... plzzzzzzzzzzz help

I have a jsp page code below mentioned...
This jsp page retrieved values from a html files, which is shown as bold.
my problem is that i cannot insert the values in database.plzz help me...
<html>
<head>
<title></title>
</head>
<body>
<%@ page import =" java.sql.Date.*" %>
<%@ page import =" java.text.SimpleDateFormat.*" %>
<%@ page import =" java.util.Date.*" %>
<%@ page import =" java.text.*" %>
<%@ page import="javax.servlet.*" %>
<%@ page import="javax.servlet.http.*" %>
<%@ page language="java" import="java.sql.*" %>
<%
 String Security_No, Category_code,Face_Value, Purchase_Value,Interest_Paid,Interest_Received,Brokrage,Total_Value,Voucher_No,Voucher_Date,Voucher_Amt,D_Date1,D_Date2,Ledger_No,Maturity_Date,sql1 ;
 java.util.Date voudate_temp=null;
 java.util.Date duedate1_temp=null;
 java.util.Date duedate2_temp=null;
 java.util.Date matdate_temp=null;
 ResultSet results;
 PreparedStatement sql;
try {
 Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
 Connection conn=DriverManager.getConnection("jdbc:odbc:pf","scott","ttlscott");
 System.out.println("got connection");
 try
 SimpleDateFormat format = new SimpleDateFormat("dd/MM/yyyy");
 format.setLenient(false);
 int sec_no, catg_code,face_val,pur_val,int_paid,int_recd,brkr,tot_val,vou_amt;
 String vou_no, lf_no;
 java.sql.Date vou_date, due_date1, due_date2,mat_date;
 boolean doneheading = false;
 Statement s=con.createStatement();
 Security_No = request.getParameter("secno");
 Category_code = request.getParameter("catcode");
 Face_Value = request.getParameter("facevalue");
 Purchase_Value = request.getParameter("purvalue");
 Interest_Paid = request.getParameter("intpaid");
 Interest_Received = request.getParameter("intrecvd");
 Brokrage = request.getParameter("brokrage");
 Total_Value = request.getParameter("tvalue");
 Voucher_No = request.getParameter("vouno");
 Voucher_Date = request.getParameter("voudate");
 Voucher_Amt = request.getParameter("vouamt");
 D_Date1 = request.getParameter("due1");
 D_Date2 = request.getParameter("due2");
 Ledger_No = request.getParameter("lfno");
 Maturity_Date = request.getParameter("maturity");
 sql1 = "insert into sec_mast values (" + "'" + Security_No + "', '" Category_code "' , '" + Face_Value + "', '" + Purchase_Value + "', '" + Interest_Paid + "', '" + Interest_Received + "', '" + Brokrage + "', '" + Total_Value + "', '" + Voucher_No + "', #"+ Voucher_Date+ "# , '" + Voucher_Amt + "', #" + D_Date1 + "#, #" + D_Date2 + "#, '" + Ledger_No + "', #" + Maturity_Date + "#)" ;
 s.executeUpdate(sql1);
 sql = con.prepareStatement("SELECT * FROM sec_mast WHERE sec_no = '" + Security_No + "' ");
 results = sql.executeQuery();
 while(results.next())
 if(! doneheading)
 doneheading = true;
sec_no = results.getInt("sec_no");
catg_code= results.getInt("catg_code");
face_val = results.getInt("face_val");
pur_val = results.getInt("pur_val");
int_paid= results.getInt("int_paid");
int_recd = results.getInt("int_recd");
 brkr = results.getInt("brkr");
tot_val= results.getInt("tot_val");
 vou_no = results.getString("vou_no");
 voudate_temp = results.getDate("vou_date");
vou_amt = results.getInt("vou_amt");
 duedate1_temp = results.getDate("due_date1");
duedate2_temp= results.getDate("due_date2");
lf_no= results.getString("lf_no");
 matdate_temp = results.getDate("mat_date");
java.text.SimpleDateFormat sdf = new java.text.SimpleDateFormat("MM/dd/yyyy");
 sdf.setTimeZone(TimeZone.getDefault());
 vou_date = sdf.format(voudate_temp);
 java.text.SimpleDateFormat sdf = new java.text.SimpleDateFormat("MM/dd/yyyy");
 sdf.setTimeZone(TimeZone.getDefault());
 due_date1 = sdf.format(duedate1_temp);
 java.text.SimpleDateFormat sdf = new java.text.SimpleDateFormat("MM/dd/yyyy");
 sdf.setTimeZone(TimeZone.getDefault());
 due_date2 = sdf.format(duedate2_temp);
 java.text.SimpleDateFormat sdf = new java.text.SimpleDateFormat("MM/dd/yyyy");
 sdf.setTimeZone(TimeZone.getDefault());
 mat_date = sdf.format(matdate_temp);
out.println("<BODY bgColor=blanchedalmond text=#008000 topMargin=0>");
out.println(" <BIG>SECURITY INFORMATION</BIG>");
out.println("");
out.println("<TABLE align=center border=1 cellPadding=1 cellSpacing=1 width=\"75%\">");
out.println("<TR>");
 out.println("<TD>Secuirty No.</TD>");
out.println("<TD>Category Code</TD>");
out.println("<TD>Face Value</TD>");
out.println("<TD>Purchase Value</TD>");
 out.println("<TD>Interest Paid</TD>");
 out.println("<TD>Interest Recieved</TD>");
out.println("<TD>Brokrage Value</TD>");
out.println("<TD>Total Value</TD>");
out.println("<TD>Voucher No.</TD>");
out.println("<TD>VOucher Date</TD>");
 out.println("<TD>VOucher Amount</TD>");
out.println("<TD>Due Date 1</TD>");
 out.println("<TD>Due Date 2</TD>");
out.println("<TD>L F No.</TD>");
 out.println("<TD>Maturity Date</TD>");
 out.println("<tr><td>" + sec_no);
 out.println("<td>" + catg_code);
 out.println("<td>" + face_val);
 out.println("<tr><td>" + pur_val);
 out.println("<td>" + int_paid);
 out.println("<td>" + int_recd);
 out.println("<tr><td>" + brkr);
 out.println("<td>" + tot_val);
 out.println("<td>" + vou_no);
 out.println("<tr><td>" + vou_date);
 out.println("<td>" + vou_amt);
 out.println("<td>" + due_date1);
 out.println("<tr><td>" + due_date2);
 out.println("<td>" + lf_no);
 out.println("<td>" + mat_date);
 if(doneheading)
 out.println("</table>");
 else
 out.println("<BODY bgColor=blanchedalmond text=#FF0000 topMargin=0>");
 out.println("");
out.println("");
 out.println("No matches for " + Security_No);
 }catch(ParseException e) {
out.println("do date format error action. ");
 catch (SQLException s)
 out.println("<BODY bgColor=blanchedalmond text=#FF0000 topMargin=50>");
 out.println("");
out.println("");
 out.println("Duplicate Entry.Try another Security Code No. ");
 catch(ParseException e) {
 out.println("do date format error action. ");
 catch (ClassNotFoundException err)
 out.println("Class loading error");
%>
</body>
</html>

you should try posting it in the jsp forum.what error/exceptions are you getting if any?

Left outer join query

Hi Experts,
 I am facing a problem with left outer join query. Am using one standard table and ztable for this join. My problem is values are not extracted from the Ztable.
Query:
 SELECT b~lifnr b~belnr b~gjahr b~xblnr b~shkzg b~blart b~zfbdt b~budat b~wrbtr
 b~wskto b~zlspr s~EXTRACT_STATUS s~maturity_date FROM bsik AS b
 LEFT OUTER JOIN zprm_rvne_sapdoc AS s
 ON s~belnr EQ b~belnr
 AND s~gjahr EQ b~gjahr
 INTO CORRESPONDING FIELDS OF TABLE it_join
 WHERE b~zlsch = p_zlsch
 AND b~xblnr IN so_invno
 ORDER BY b~lifnr b~xblnr.
I have all entries of BSIK table in Ztable with extract status as Y but this query is not fetching extract status and maturity date of ztable so it is blank in the internal table.
Need solution.
Regards
Sridevi S

Hi,
see the sample wiki for writing the Left outer join
http://wiki.sdn.sap.com/wiki/display/Snippets/EmployeeInfotype0000to9999ChangeHistory
Specifying Two or More Database Tables as a Left Outer Join
The left outer join, on the other hand, reads lines from the left-hand database table or join even if there is no corresponding line in the right-hand table.
SELECT...
FROM <tab> LEFT [OUTER] JOIN <dbtab> [AS <alias>] ON <cond>
 <options>
<tab> and <dbtab> are subject to the same rules and conditions as in an inner join. The OUTER addition is optional. The tables are linked in the same way as the inner join with the one exception that all lines selected from <tab> are included in the final selection. If <dbtab> does not contain any lines that meet the condition <cond>, the system includes a single line in the selection whose columns from <dbtab> are filled with null values.
In the left outer join, more restrictions apply to the condition <cond> than in the inner join. In addition to the above restrictions:
EQ or = is the only permitted relational operator.
There must be at least one comparison between columns from <tab> and <dbtab>.
The WHERE clause may not contain any comparisons with columns from <dbtab>. All comparisons using columns from <dbtab> must appear in the condition <cond>.
If we have two tables named stud1,stud2 with the following data
Stud1: id Name stud2: id Name
1 xxx 1 aaa
2 yyy 2 bbb
3 zzz 4 ccc
4 www 6 ddd
When we use Left Outer Join we get the output as:
1 aaa
2 bbb
3 <Null>
4 ccc
When we use Right Outer Join we get the output as:
1 aaa
2 bbb
4 ccc
<Null> ddd
When we use Full Outer Join we get the output as:
1 aaa
2 bbb
3 <Null>
4 ccc
<Null> ddd
Prabhudas

MHKIM : 입력된 maturity date가 System Date보다 클 경우, Negotiable 로 안됨

Similar Messages

Maybe you are looking for