Monday, September 1, 2014

Confession of a SAP Consultant

Consultant. Big word. The word web dictionary defines it as "someone who gives an advice" while meriam webster says "one who gives professional advice or services"

Who would ever imagined that I'll become a consultant? It's like a perfume. It's an ego booster. It's pleasant to the ear. But what does really it takes to become a consultant?

A SAP Consultant means you're waking up each day, convincing yourself that you need to wake up early because you will travel too far. It's like you're convincing yourself to be motivated and have a passionate heart as if it's your first day. EVERYDAY.

Being a SAP consultant means you have to be patient. Clients keep asking same questions at the same time. You'll get irritated sometime. As if they are not thinking any possible way out. And All answers are on hands. Be Patient. MAKE IT YOUR CHARACTER.

Being a SAP Consultant means you know the difference between white and black. When you have the darkest moment of being a consultant and nobody helps you, or nobody could help you, You should always look to the brighter side. There's always a brighter side. LOOK UP.

Being a SAP Consultant means you can say no. If the clients are too demanding and when they're asking too much, and and you know too much is too much. JUST SAY NO.

Being a SAP Consultant means to be personal. Drop the "Trabaho lang walang personalan" You should put your heart on what you do. Once you're heart is in it, you'll never run out of joy to do more. TAKE IT PERSONALLY.

Being a SAP consultant means you are not MS-I-KNOW-EVERYTHING. Learning is always a continuous process for you. You learn from every people you meet, From your officemates, from the client, from the system. And even from the least person you meet along. BE HUMBLE.

And lastly, Being a SAP Consultant doesn't mean "Its all about me" It's always about who deserves glory. It's about God who gives you a job. It's about him who gives an applause each time you uploaded a correct beginning balance when noone else did. It's about him who protects you not to be harmed when you're travelling alone. It's about him who celebrates when you closed a project. It's about him being who doesn't leave you afterall.

Being a SAP Consultant means, to bring back all the glory onto the LORD



This is a guest post from Mahj. Mahj is a SAP Consultant and the blogger behind http://pasthadpassed.com/

Friday, August 29, 2014

Posting Period Locked ; specify an alternative date Error



This error occurs when you uploaded a file with a closed posting period. To fix this error you can go to SAP Menu > Administration  > System Initialization > Posting Period and unlock the specific period you used. 



You can leave a comment if this post is helpful. 

Sunday, March 30, 2014

SAP - SAP Client upgrade take too long

We encountered a problem when upgrading the SAP Client application in our server. I've spent almost 8hrs waiting to upgrade the SAP Client application. The actual picture below :


I leave the server open for a day. But it surprise me that the upgrade process is still in upgrading process. I was worried that if I cancel or force stop this upgrade process, the SAP Client will corrupt. The last time we encounter the problem, we canceled the upgrade process and try to install again. But, when we installing it there's a missing file in the folder. So what we do is to re-install all the SAP related application in the server. I believed that was not necessary or advisable if you are in a production type of company.  There's a SAP note provided by SAP 1991617 - SAP Business One 9.0 client upgrade freezes.  Just log-in your S-user ID.

Thursday, March 6, 2014

SAP - Slow Login on SAP Client

This is the most frustrating error that I've encounter when troubleshooting our SAP Business One server. Imagine, when you are logging in to SAP Business One Client it takes 5-10mins before you actually login. But if, if you are trying to login on the SAP Server you may not encounter the slowness. So, after compiling some solution I've decided to create my own. This is Tips and some kind of Tricks. :) Would you mind to try it if ever you encouter? So lets begin.


Please check if their SAP Server is running on two NETWORK CARD.

  • Disable additional network cards in the Network Connections. Also, make sure there is no dial-up interface or VPN interface set up, and restart the server. Note that you can re-enable the additional network card after the restart. This will resolve the issue until the next restart.
  • Check if there is an additional IP address assigned for single network cards (Start-->Run-->cmd-->ipconfig). If there is more than one IP address displayed, ensure there is only one address assigned.
  • Install the license server on a machine with a single network card.
Disable all network cards, restart the license server, and then enable the network cards again.
  • Restart license server.
Disable the Firewall and the antivirus
Change registry entry, and add the IP address of the License Server computer. 
  • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ACE\TAO
  • For example: -ORBEndPoint iiop://10.59.39.60:30000  -ORBDottedDecimalAddresses 1
  • Use the IP address instead of the computer name for the License Server address wherever License Server address is needed, such as SAP Business One client, DI API, B1i, and so on.
Check SQL Server process in the Task Manager
  • If the SQL Server eating too much CPU usage between than 70-80% then you should adjust the memory consumptions in SQL Server settings. I remember this when we are on training for SQL Server Implementation and Maintenance.
  • Log on to SQL Server > right click the Server name > Properties > Memory
  • Change the Maximum server memory value, as you see the default value is set to 2147483647(mb) equivalent of 2097151(gb).
  • Change it to the total memory of the server then dived it by two, assumption 8192(mb)/2 = 4096(mb)
  • You can use this online tool for conversion (http://www.whatsabyte.com/P1/byteconverter.htm


Wednesday, March 5, 2014

SAP - Access Provider cannot be found. (DTW)

Most of the time, the DTW(Data Transfer Workbench) save a lot of time when importing Transactions, Master Data in SAP Business One instead of typing it manually. But what if upon importing your data an error occurs? Error not from the file, but the application it self. I've encountered this error most of the time so basically I know how can I fixed it. I'm pretty sure you'll encounter this, in the last step of importing an error message will show 
"Access Provider cannot be found. It may not be properly installed."


The symptoms might be the installation of your Microsoft Office has a problem. To fixed this error, you may go to Microsoft website or visit this link Microsoft Access Database Engine 2010. I preferred to install the 32bit version of Microsoft Access Database Engine and 32bit version of DTW.

Tuesday, March 4, 2014

SAP - Unhanded Exception on Depreciation Run

Recently our team encountered an "Unhanded Exception" in SAP Business One using Depreciation Run, after this message an error will appear again "Microsoft Visual C++ Runtime Library". We raised this issue to SAP Business One team and they recommend to upgrade our current version of the application. Unfortunately after we upgrade to the latest version, we still encounter this error.




As we analyze the error, I've check the Log file of the application that indicate in the error description in SAP Business One client go to "Help > Support Desk > Log Settings" from there you can check the default path of the error. "C:\Users\YourUser\Local Settings\Application Data\SAP\SAP Business One\Log\BusinessOne\" as I read the error log, I've noticed that there is also a problem in the SBO_SP_TransactionNotification stored procedure. As previously discussed in SAP - Conversion failed when converting the nvarchar. So we decided to disable again the SBO_SP_TransactionNotification and after that, it work perfectly. Mostly this error occur when SBO_SP_TransactionNotification is blocking some transactions.

SAP - Conversion failed when converting the nvarchar

This is probably my first post in this blog. :) So, yesterday one of my friend raised an error when adding a Marketing Documents, Item Master Data and Customer Master Data in SAP Business One.




[Microsoft][SQL Server Native Client 11.0](SQL Server)Conversion failed when converting the nvarchar value 'value' to data type int. (CINF)
The root cause of this error is on the SBO_SP_TransactionNotification this is a stored procedure from SAP Business One database where in you can create your own user define error which they can't proceed on Add/Updating based on your scenario. So, I've told him that to review this stored procedure. The solution is either disable all the query in the SBO_SP_TransactionNotification or debug the stored procedure.

To go to this stored procedure :
Log in to your SQL server
Expand Databases > Expand your Database > Programmability > Stored Procedures > Find SBO_SP_TransactionNotification