DataXstream OMS+ DataXstream OMS+
Simple Order Management for SAP
  • Home
  • About
    • About DataXstream
    • Our Partners
    • Our Clients
    • Careers
    • Privacy Policy
  • OMS+
    • Executive Summary
    • Unified Commerce
    • Feature Gallery
  • Xstream Connector
  • SAP Services
    • Services Overview
    • Project Management
    • Integration
    • Development
    • ISV Enablement
  • Blog
  • Contact
    • Technical Support
DataXstream OMS+ DataXstream OMS+
  • Home
  • About
    • About DataXstream
    • Our Partners
    • Our Clients
    • Careers
    • Privacy Policy
  • OMS+
    • Executive Summary
    • Unified Commerce
    • Feature Gallery
  • Xstream Connector
  • SAP Services
    • Services Overview
    • Project Management
    • Integration
    • Development
    • ISV Enablement
  • Blog
  • Contact
    • Technical Support
Feb 25

BD53 Doesn’t Play Well With Others

  • February 25, 2010
  • Craig Stasila
  • 1 Comment
  • SAP Consultants Blog, SAP Interface Blog, SAP Technical
  • ALE, Change Pointer, Craig Stasila, DataXstream, Integration, Interface, SAP

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!!

You see, SAP transaction BD53 just does not play well with others.  My full HRMD_A solution used a custom filter object (transactions BD95 and BD59) and a custom outbound IDOC formatting function module to convert change pointers into IDOCs (transaction BD60).  The dirty little secret of transaction BD53 is that every time you save and update the IDOC reduction in transaction BD53, SAP goes and screws up a bunch of configuration  displaying a message that says “Interface changed for message type <your_message_type>:  Settings reset”

Wait! What!?!

What does that message even mean?  Well, that message is telling you in very cryptic language that SAP has gone and reset the settings in BD59 and BD60 to the SAP standard! So, every time the field reductions were updated, kiss your custom filter assignments and custom IDOC processing function goodbye!

Why couldn’t the message say:

Hey Buddy! You know all that custom configuration you did to get your interface working just so? Well, its gone and you’re going to have to redo it all in the following transactions:
BD59
BD60
etc.

I guess SAP is just far too polite.

So, be very cautious when you pair IDOC reduction with custom filter assignments and custom IDOC formatting function modules and be aware that every time the IDOC reduction is updated, you will need to go back in to reconfigure transactions BD59 and BD60.

For more information, see SAP OSS Note 655321

  • Facebook
  • Twitter
  • Tumblr
  • Pinterest
  • Google+
  • LinkedIn
  • E-Mail
Avatar

About The Author

Former Partner and Senior Consultant at DataXstream, Craig Stasila played a key role in developing DataXstream. For current information regarding Craig Stasila please see his Linkedin profile.

Related Posts

  • SAP ABAP/PI Developer PositionJanuary 26, 2015
  • SAP IDOCs for Customer Number with different Sales Organizations to different External PartnershipsFebruary 7, 2012
  • SAP EDI EDPAR Table Walkthrough – How to Cross Reference External Customer Number to SAP Customer Number (Part 2)February 1, 2012
  • SAP EDI EDPAR Table Walkthrough – How to Cross Reference SAP Customer Number to External Customer Number (Part 1)January 26, 2012

1 Comment

  1. How To Implement Field-Level HRMD_A Reduction : SAP Integration Experts – DataXstream
    February 25, 2010 at 11:13 am · Reply

    […] my full HRMD_A solution uses custom filter objects and a custom IDOC formatting function module.  And BD53 does not play well with these customizations. About Craig: Craig Stasila is a senior partner consultant with DataXstream, LLC. He has over […]

Leave a reply Cancel reply

Your email address will not be published. Required fields are marked *

Looking for something in particular?

Categories

New Series: ABAP Tricks

Check out our newest blog series - ABAP Tricks and learn something new!

ABAP Tricks Series

Other articles you may be interested in…

Building an SAP .Net Connector Proxy

How To Configure UNIX Security To Allow SAP To Share A File System With Another UNIX Application

DataXstream to Exhibit at SAP® TechEd® 2016

SAP Integration Optimization

Are You Properly Managing Your SAP Change Pointer Tables Part 1 – The 50,000 Foot View

Popular Topics

.Net Connector 2009 ABAP ABAP development Accounts Receivable ALE ASUG Basis Basis/Netweaver Cforia Chris Caparon consulting Craig Stasila DataXstream IDOC Integration Interface Mike Salvo NCo NetWeaver OMS+ order management PI point of sale POS Project Management Retail sales SAP SAP .Net Connector SAP Integration SAP Order Management SAPPHIRE SAP PI SAP Retail SAP testing Solution Manager TechEd Tim Cooper Timothy Yates upgrades virtualization Wholesale XI XI/PI

Contact Us

434 McLaws Circle Phone: 757-345-3437 Fax: 757-645-2384 Web: www.dataxstream.com

Search

© 1998-2019 DATAXSTREAM, LLC