Build an SAP RFC Server using the SAP .Net Connector
This blog post describes step-by-step how to use the SAP .Net Connector and Microsoft C# to create an SAP RFC Server. This allows an SAP process to call your custom C# code, which can accept parameters and return values.
The SAP .Net Connector simplifies creating C# programs that can interoperate with an SAP host. The SAP .Net Connector is available from the SAP Service Marketplace. You must have access to the SAP Service Marketplace to be able to download the SAP .Net Connector. The SAP .Net Connector must be installed on your development machine before we begin.
RFC is a Remote Function Call. In this case, the SAP process is a ‘client’ that is making an RFC call to our custom ‘server’ code. Our code uses the SAP .Net Connector to register on an SAP Application Gateway.
The TLA system we have been creating exists solely to demonstrate certain programming techniques involving the SAP .Net Connector and C#. We will cover three separate parts of the solution: defining the function to SAP, creating a proxy object used to access SAP, and creating our C# code to perform the RFC function.
Read more
Come Join Us In Orlando at the SAP Insider Tradeshow
When: March 23-26Are you going to be there? DataXstream will. Come by and talk to the technical eXperts in SAP integration, virtualization, and upgrades and see what we can do to make your ERP system run better. Sign Up NowFill out the form below and when you come by our booth you will receive a free DataXstream coffee mug and flash drive filled with only the information that matters to you. |
 |
SAP Event Driven Batch Job
When creating SAP batch jobs to run a program, most of the scheduling can be accomplished by setting a periodic time for when the job is executed. For example, execute the job every 10min, 30min, or 1 hour. But what if you needed more control of when a batch job was executed?
Troubleshooting the Services Registry
Recently I set up the services registry for PI 7.1 EHP1 for a client of ours. Although it seemed like it would be a simple process, I ran into a 401 authorization issue and another issue where web services were not publishing to the services registry. Looking online there are a lot of people who ran into the same issues as I did, so I am providing, here, the steps to perform if your services registry isn’t working.
SAP WM/IM Consultant
Location: Northern Virginia, USA
Start Date: April 2010
Duration: 7-8 months
Description:
DataXstream is searching for a highly qualified, experienced and deliverables focused SAP Functional Consultant with expertise in inventory management (IM) and warehouse management (IM) for a project starting in April 2010. The position requires functional expertise with additional technical understanding and skills. This position requires you to work with the client and the implementation team to design, configure, test and deploy an SAP-based solution. The work will also identify and produce specifications for custom development objects.
The client expects to make informed decisions based on guidance from a proactive consultant who presents options for how to execute business processes and functions along with the pros and cons of those options.
The responsibilities of the position start after project inception and continue through go-live, user training and post go-live. If you meet or exceed these standards and would like to be a part of a highly skilled SAP consulting team please attach your resume and your completed application form below.
BD53 Doesn’t Play Well With Others
I recently posted a blog about how to implement field-level IDOC reduction for the HRMD_A message type. In short, the standard SAP transaction to reduce IDOC segments and fields (transaction BD53) can’t be used because the field-level reduction is ignored by SAP. My solution leveraged TVARV as a repository for the fields to clear. Read the whole solution here. A colleague of mine was very quick to point out that instead of using TVARV as the method for controlling which fields are cleared, I should have continued to leverage transaction BD53 for the IDOC reduction maintenance and changed my code to look up field level reductions in table TBD24.
What a great idea! Too bad I hate this suggestion… and it’s all SAP’s fault!!
The Software Component
In my last blog entitled What’s in a Namespace, I discussed the value of developing deliverable custom solutions in a reserved unique namespace. In this blog, I will discuss how a namespace is related to a software component. I will also discuss the typical product lifecycle, the software component version, and the convention which we use for establishing the software component version release increments.
DataXstream, an SAP Solution Partner, builds, packages, and distributes custom solutions for our clients. We develop all of our custom add-on products in our own reserved and unique namespace /XSTREAM/. But, we also need to reserve a separate unique namespace for each add-on product that we package and deliver using the SAP Add-on Assembly Kit. So, we have a single development namespace /XSTREAM/ and a separate “packaging and delivery” namespace for each add-on product. Why is that?
How To Implement Field-Level HRMD_A Reduction
I love ALE. It is super-powerful and, once you get the hang of it, is a snap to configure. Recently, I was setting up an HRMD_A interface for my client. Everything was going smoothly until I ran into a requirement to filter out the social security number (PERID), birthdate (GBDAT), and gender (GESCH) for privacy reasons. All of these fields are in segment E1P0002. Initially, I thought that this requirement was easy enough to accomplish. I just created a IDOC reduction in transaction BD53 and filtered out the three fields. I soon found out that while entire segments were getting reduced from the IDOC as configured, the individually reduced fields were still showing up in the IDOC. What’s going on?!? Read more
SAP Upgrades & Recycling Project Artifacts
In my previous post on SAP upgrades I discussed how to get started on your project and to determine whether you are doing (ahem!) just a technical upgrade or intend to venture into deploying additional standard functionality, too. In this post I’ll talk about how you can plan, anticipate and potentially accelerate some of the execution activities to verify the upgrade is working.
SAP SD Functional Consultant
Location: Northern Virginia, USA
Start Date: April 2010
Duration: 7-8 months
Description:
DataXstream is searching for a highly qualified, experienced and deliverables focused SAP Functional Consultant with expertise in SD for an upcoming project in April 2010. The position requires functional expertise with additional technical understanding and skills. This position requires you to work with the client and the implementation team to design, configure, test and deploy an SAP based solution. The work will also identify and produce specifications for custom development objects.
The client expects to make informed decisions based on guidance from a proactive consultant who presents options for how to execute business processes and functions along with the pros and cons of those options.
The responsibilities of the position start at project inception and continue through go-live, user training and post go-live. If you meet or exceed these standards and would like to be a part of a highly skilled SAP consulting team please attach your resume and your completed application form below.
