SAP ABAP/PI Developer Position

DataXstream has a full-time opening for an ABAP/PI Developer in our Indianapolis, IN office.

Technical Qualifications

  • 7+ years of experience in ABAP/PI/XI Programming is required
  • Experience with EDI strategy and tools
  • Understanding of Object Oriented concepts
  • Experience with Data Dictionary, Function Modules (Remote Enabled), BAPIs, Web Services
  • Experience creating/modifying Adobe Forms
  • Proficiency with ALE/IDocs including error handling is desirable
  • Experience working with SAP ECC 6.0
  • Programming experience in various modules – MM, SD, FI
  • Work will primarily be remote, but could be potential for periodic travel to client sites

Additional Qualifications

  • US citizens and those authorized to work in the US are encouraged to apply. We are unable to sponsor H1b candidates at this time.
  • Sharp, energetic consultants with an understanding of business processes
  • Self-starter
  • Ability to work both individually and as part of a team
  1. (required)
  2. (required)
  3. (valid email required)
  4. (required)
  5. (required)
  6. (required)
  7. (required)
  8. (required)
  9. (required)
  10. Captcha
 

cforms contact form by delicious:days

 

SAP PI Dilemma: How to Get Production IDocs for Testing

Every SAP developer/consultant knows that to be able to test new programming logic and/or configuration efficiently and thoroughly, sufficient test data is required to ensure quality. I have worked on several SAP PI projects and have run into the issue of not having great test data (or, for that matter, any test data!) in my development/test environment. If you’re ever in a spot where you need to test IDocs from a different system, here is a step-by-step guide on how to get them without having to perform much setup.
[Read more...]

Quick Connect for SAP Business Network

The DataXstream Quick Connect for SAP Business Network, is a rapid deployment solution that delivers preconfigured SAP ECC and PI content for mapping and integration of standard SAP II OD canonical interfaces.

Customer Challenges

On average, organizations exchange electronic documents with over 500 different business partners via 10,000 unique interfaces. With analysts expecting this number to double by 2014, implementation of SAP II OD is a business necessity. But, using in-house or consultant-based integration scenarios leads to daunting challenges:

  • High implementation and operation costs
  • Lack of standard integration
  • Lack of real-time integration

Quick Connect Key Features

The DataXstream Quick Connect eliminates those challenges by providing:

  • A standardized deployment methodology which uses pre-packaged mapping and integration content, reducing implementation costs
  • A subscription-based content model, allowing fixed operational costs
  • Updates to integration content, assuring all interfaces are consistently current

Business Benefits

Choosing to integrate SAP II OD with Quick Connect means:

  • A reduction in implementation and labor costs
  • The ability to scale the company delivery strategy to align with program expansion
  • Speedy adoption of SAP II OD
  • Management and maintenance of integration content via Quick Connect

SAP IDOCs for Customer Number with different Sales Organizations to different External Partnerships

Have you ever implemented an outbound  EDI process from SAP for a single customer number where the customer has multiple EDI trading by Sales Organization or Division?  It can be done.  In order to accomplish this you will need to create separate output types for each Sales Organization/Division and then set up the Access Sequence/Output Determination in order to create the IDOC for each partnership.  You can then use the Message Variant and/or Message Function fields of the Partner Profile to differentiate between the two Sales Organizations/Divisions.  Finally, you would set up your EDI Mapping to look at the Partner Profile fields in order to route it to the correct partnership.  Let’s take a closer look at this process.

Let’s say that Customer 15 in your SAP system buys products from your company.  It sends inbound EDI Orders to you using three different partner IDs because they have 3 internal divisions and they want all transactions to be separate.  You want to keep all sales data for this customer under one customer number in your SAP system and just separate them by a different division.  You are required to send out EDI invoices to this customer, but they must go to the correct EDI Partner ID.  Let’s say you would normally use the Standard SAP Output Type RD00 and  Access Sequence 0003 (Sales Org, Distribution Channel, Division, Customer Number) for producing your INVOIC IDOCs. [Read more...]

SAP EDI EDPAR Table Walkthrough – How to Cross Reference SAP Customer Number to External Customer Number (Part 1)

When creating IDOCs in SAP to send Invoices to customers via EDI you will likely have to send the customers their internal partner numbers on the EDI ANSI X12 810 Invoice Document.  In almost all cases this will not be the same as the SAP partner numbers.  So how can we set up a cross reference of SAP and external partner numbers?  Well, the answer is simple because SAP has set up a utility to handle this for you.  All you need to do is populate the EDPAR table in SAP using the VOE4 transaction.  Once this is completed the IDOC_OUTPUT_INVOIC function module will read the EDPAR table when the Invoice document output is processed and populate the LIFNR element of the E1EDKA1 or E1EDPA1 segments of the INVOIC IDOC with the external partner number.  Entries in EDPAR can be set up for multiple partners including the Sold-to, Ship-to, and Bill-To numbers so that external customer number cross-references can be passed on the IDOC if needed.

Let’s look at how this process works.  Let’s say we have created an invoice document in SAP.  In this case, the Sold-to, Ship-to, and Bill-to partners are all SAP customer number 15.  If we want to create an INVOIC02 IDOC on which the external customer numbers are populated for all three of these partners we would have to set up three EDPAR entries as displayed on the below screen shot.  The Customer field will contain the SAP partner number (Sold-to, Ship-to, Bill-to).  The Ext. Function field will contain the Partner Function (SP = Sold-to, SH = Ship-to, BP = Bill-to).  The External Partner field will contain the external partner number that the customer is expecting on the EDI file.  And the Int. no. field will contain the SAP partner number (Same as the Customer field).

[Read more...]

How To: SAP PI Data Type Enhancements

I have worked with SAP PI since it was called SAP XI (version 3.0).  SAP XI was pretty rough around the edges and was not what I would call an enterprise class integration tool.  Each successive SAP PI release and enhancement pack has steadily added functionality such that the latest version of SAP PI is finally starting to resemble a fully functional EAI platform.

One such example of additional functionality is the ability to enhance delivered integration content.

Recently, I had to make some modifications to an integration scenario where an SAP ERP system was sending data to an external custom solution.  The good news was the SAP ERP and PI objects were built and delivered by SAP!

SAP ERP Delivered Content

SAP ERP Delivered Content

The bad news was that the interface, as designed, did not meet the business’ need…

How to add fields to delivered content?

How to add fields to delivered content?

So, the $64,000 question is, how do we add fields to delivered SAP PI content?
[Read more...]

Simplify SAP PI Mapping Logic with FixValues Mapping

I was trying to think of something to write about this weekend, when I happened to stumble upon this gem:

After I stopped laughing, I started to cry, because I realized that this happens all the time in SAP PI–it just looks a little different…

[Read more...]

DataXstream to Host September ASUG Event in Virginia

 

SAP Learning Seminar

When: Fri. Sept. 24

7:30 AM – 5:00 PM

Where: Holiday Inn – Williamsburg, VA

Cost: Free

Register for the Event

Can’t make it to Las Vegas for TechEd this year?

Join us September 24 in Williamsburg, VA as we host an SAP Learning Seminar for the VA/NC ASUG chapter. ASUG, DataXstream, and event sponsors have scheduled a full day of  presentations by industry experts and local SAP users, panel discussions, and interactive breakout sessions and workshops; all intended to give you a great learning experience and stay abreast on everything current in SAP. DataXstream’s sessions include:

[Read more...]

SAP PI CTS+: Letting CTS+ Out of the Bag to Get Better Change Management

Anybody familiar with older versions of SAP XI/PI understand that transporting interface development and configuration changes is often a prickly situation.  Standard change management in PI relies on the manual packaging and processing of changes into files.  These files have many issues:

  • No documentation
  • A different means of transport than standard SAP transports (need some training people used to ABAP transports)
  • Manual audit accountability (what do you do if you lose an exported PI .tpz file)

To help resolve these issues, SAP released CTS+.  But, what is CTS+ and how can it help?

[Read more...]

What’s in a Naming Convention?

It doesn’t take long for a PI implementation to become a complete mess if standards are not put in place before development occurs.  Even among seasoned developers, opinions vary as to the best way to name and organize the IR (ESR) or ID (IB), depending on different backgrounds and previous project experience.  In the next few blogs I would like to touch upon some of the best practices that we utilize in our implementations at DataXstream, which we have arrived at though our project experiences and  discussion, both internally and with other middleware experts.
[Read more...]