Segment E1EDL37 for shipping notification not filled

Segment E1EDL37 for shipping notification not filled

Currently we are using delvry03 to generate ASN (Automatic shipment notification). The shipment unit header (E1EDL37) has to be filled from my Z tables. Since this ASN is being generated at the time of Delivery creation. The segment E1EDL37 will not be filled up automatically. So I may need to fill the segment E1EDL37 with the help of provided customer exits. Since the segment E1EDL37 is not filled, we don't have any control over the segment e1edl37 to fill the data. Please provide me the help to resolve this issue.

    Requires Free Membership to View

    Login

    When you register, you will start receiving targeted emails from my award-winning team of editorial writers. Our goal is to keep you informed on the hottest topics and biggest challenges faced by SAP professionals today.

    Hannah Smalltree, Editorial Director

    By submitting your registration information to SearchSAP.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchSAP.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

I had a look at IDOC_OUTPUT_SHPMNT and see no reason why the segment should not have been added. It may be empty but the routine to create it should be called. The you can fill the data with customer exit '002'. The catch-all solution would be to build a wrapper function, e.g. Z_IDOC_OUTPUT_SHPMNT which in turn calls the original function IDOC_OUTPUT_SHPMNT. This will build your IDoc the traditional way. Then you can process the created IDoc data and manipulate your segments as desired.

This was first published in June 2003

Join the conversationComment

Share
Comments

    Results

    Contribute to the conversation

    All fields are required. Comments will appear at the bottom of the article.
    Back to top