Now, that wasn’t a shock but was a kind of surprise for me. Suddenly, I was asked to brush up my skills on Web Dynpro for ABAP. I had, in reality, worked for closed to just 100 hrs on Web Dynpro for Java (and that too for support purpose for a client of my previous employer). My ABAP skills are just a micro meter above average, but that driving force which acts as fuel inside me is still giving me sufficient energy to take up challenges like this. That thirst of programming removes entire pain from my body, brain & my fingers starts stroking & breaking the keys on keyboards.
As last time I wrote about, Got some work on Java Connector. That task was asked to be stopped ( I say it sweetly ) and to be migrated to SAP’s WD ABAP. Now, after successfully marching towards the goal, finally I got some appreciation about the work. I still find it difficult to work without a proper training. But, after developing more than 50 to 60 thousand lines of code in last 7 years using different languages ranging from VB, ASP, JSP, JS, PHP, ABAP (majorly), I feel confident about my work.
Hope, this thing sail successfully till the end. I am sure, the scope of my current task will increase to quite an extent in near future. So I have crossed my fingers. And by the way, for your information, there is 1 position open in my company (in Pune) on Web Dynpro for ABAP (expected experience about 3 years in WDA and an overall SAP experience of 5 years). If anyone interested, please contact me on vaibhav.sap@gmail.com. Please write your interest to me and I will reply you with the details about the opening.

Hi all,

Since long, I did not get a chance to write. I was a little confused about continuing the writing task for my blog or to stop this activity for good. But, now I think that I will fight with those negative thoughts as much as I can and do not let this writing habit move away from my brain.

In my office, I have got some work on Java Connectors now and I am supposed to return to my favorite job i.e. Programming. And to add some spice to the taste, I have got task to code using core Java. Its not first time happening to me, but it was same old feelings of mine coming alive. I was feeling little scary about Java. Being worked on Visual Basic development suite, i never liked the taste of  Java ( or any other non MS tool, for that matter).

Thanks to some of Java friends in office, I am not only surviving but able to connect Java pages with SAP. I have used Java Connector for this. I will soon publish the sample code about this. Also, you can meanwhile read about How to get PO details from SAP to VB using BAPI control.

Some time ago, I wrote about how to manually process the sap idoc which got a good response from you.

Sometimes, the IDOCs created by the system are very big in size and it takes long time to transfer them. In that case, better to check the size of the IDOC file which is created by the system. Because if it is a small file and taking lot of time to transfer then there may be some other network related problem.

Ok, whatever. This is the way to find the size of the IDOC file.

You have to create a file port destination (probably in your local system) and send your IDOC to it. This will save the IDOC to your local server / machine very quickly. Once the IDOC is created in your local server, you can check the size of the file.

This  was the question asked to me in a recent interview. Apart from the basic differences between SAP XI and Business Connector, I was supposed to answer in what situations they are preferred over the other.

According to me, the basic purpose of the SAP XI and BC is to achieve the integration between SAP and non SAP systems. SAP XI will play the central integration tool where as BC will provide you one is to one connections.

BC will always act as a translator between different systems. But SAP XI is more advanced using which you can implement complex logic before sending data to target systems.

I think there are more points to write, but I will write them later.

Once, the IDOC which I was trying to send, was not getting sent because some of other big programs were getting executed at the same time. So the SAP server was not able to allocate the required memory & processing resources (i guess).

I think, it was better to process the IDOC manually. The transaction required for manuall processing of the IDOC is - BD87.

In BD87, you have to select the node / message with the status 64 and press F8 button (i.e. Process Button on the toolbar). I hope this helps you.

This is not a usual scenario but sometimes we have to send same Purchase Order to 2 different vendors via EDI. We can manually create the output for those vendors but there is another way to automate the process. You can do this using transaction NACE.

In the output determination access sequence, there is a checkbox that tells whether a certain access is “Exclusive“. If it is unchecked, it means it will search in other condition tables even after it finds a match. This means that you can have two NEU outputs set up.

Another option is to create a new output type using transaction NACE. This means that the two outputs can be handled independent of each other.

I hope you guys must have read the article about how can we change the idoc content at receiver side.