Skip to Content
avatar image
Former Member

SDS Report shipping

Dear Experts,

We have requirement wherein whenever output type for report shipping is triggered, it has to send SDS along with label. Will it be possible through standard system ?

Also if not possible through standard, how can re-start the shipping in case of status error found(shipping reason) technically for the label which is added along with SDS.

Thank you

RJ

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

8 Answers

  • Best Answer
    Mar 28, 2017 at 06:12 AM

    Hello Jeevitha,

    I happen to do some analysis on the label distribution functionality and understand that it is possible to ship labels via CVD1 by means of a business process ETI_DIST similar to MSDS_DIST. The standard system has default customization available you can try the scenario. Now coming to merging two business scenarios together you need to develop custom Business Scenario which merges both MSDS_DIST and ETI_DIST distribution using some kind of triggering point like Shipping Reasons type of analysis. I recommend keep them separated and trigger the other label distribution specific to selected scenarios. You need to change the standard FM to identify the combination scenarios of MSDS / Labels combinations for which it should be triggered otherwise system will expect for all the cases.

    It is trickly but possible.

    Thanks

    Jayakumar

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Mar 29, 2017 at 12:15 PM

    Hi Guys,

    Sorry for the delay in my response.

    We had completed this last week by customizing the standard functional module ( *BUNDLE & *PACKAGE)

    This requirement of shipping ETI_DIST is only specific to some specification of REAL_SUB (based on authorization group) where MSDS_DIST is for all specifications of REAL_SUB. Considering the two FM, it will send ETI_DIST only if it has specific specifications along with MSDS_DIST

    Thanks for all your response :)

    Best Regards

    Jeevitha Ravi

    Add comment
    10|10000 characters needed characters exceeded

  • Mar 28, 2017 at 06:35 AM
    -1

    Dear Jeevitha

    even considering the quite positive feedback of Jayakumar: still for me the overall "business process" is not clear. The two processes (from my point of view) of MSDS dispatch and label printing is 99% not related to each other. The "main" issue i have is: the logic must be complete different (and how then to combine ??)

    1.) for MSDS (EU) and MSDS (NAFTA) you have some rules to use so that CVD1 process is possible. The "dispatch" of MSDS"can here (from my point of view) not be synchronized (if we talk about SD_CALL mainly) as the legal needs are totally different in comparison to Label process

    2.) The "possible" combination might be by using MAN:CALL process. But why combine MSDS/Label? Not knowing the details: you can not bundle (normally) two completly different processes in CVD1 (as they are completely seperate). So you can not have one "bundle" with MSDS/LAbel combined. This will be in 99% of the cases two bundles (which is much better). So the dispatch of MSDS and label can not be synchronized (and still i d not understand the business reason why you would like to synchronize)

    3) The "need" to trigger a label dispatch are not clear to me. The GLM process is designed completely different in comparison to MSDS process (e.g. you have scenarios like: "Make to stock" etc.). So here as well the Label and MSDS process are not in "sync"

    The use of CVD1 for label can therefore only start using CG54. And here are my "highest" doubts (considering the many GLM parameters you must normally specify to print a label)). In GLM process the complete" label tree" determination is managed. why "reprogramming" that in CVD1?? (and you must do that to determine the "correct" labels to be distributed)

    So from my point of view. The ETI_DIST process can may be used for "very primitive" labels (and even here I have doubts) which are not the "business critical part" in daily business and there is not "benefit" for using such option.

    Nether seen an ETI_DIST process established in one company.

    C.B.

    PS: please check the options of GLM plus. Here the "difference" to MSDS disptach are "greater/bigger" but the process is then more flexible

    Add comment
    10|10000 characters needed characters exceeded

  • Mar 20, 2017 at 11:18 AM

    Dear Jeevitha

    the SDS and the Label process are complete different processes You can not combine them.

    The Label Process is much more specifc and need much more data. So it can not be combined with SDS siphment

    Check this blog as a starter: https://blogs.sap.com/2014/07/24/what-is-a-label-and-how-support-sap-ehs-management-labeling/

    For SDS distribution: may be check https://blogs.sap.com/2016/04/10/ehs-classic-report-distribution/

    C.B.

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Mar 20, 2017 at 04:20 PM

    Dear Christoph,

    Thanks for your reply. yes i agree it is different for label.

    but in our case it is created as report category and the report which has this report category should be sent along with SDS for only specific substance.

    I can see standard setting ETI_DIST for label shipping, we can use this meet the above requirement or is it not possible with the standard system.

    Thank you,

    RJ

    Add comment
    10|10000 characters needed characters exceeded

    • Hello Jeevitha,

      Most companies do not send labels along with SDS. Therefore there is not a lot of knowledge for this topic available.

      I would suggest you try it out:
      If you're labels are of report type MSDS - and you set up the needed customizing accordingly it should work!

      However Christoph remarks are valid: Some data you "normally" print on labels like:

      • Batch Numbers
      • Expiration date
      • Manufgacturing date
      • etc.

      will not work (without changing the standard). Or in other words - if your label only has data that is on the MSDS it should work.


      Hope this helps

      Mark

  • Mar 21, 2017 at 08:27 AM

    DearJeevitha

    the "ETI_DIST" process is only discussed once. I was not able to find this discussion any more.

    99% of the labels can not be distributed using CVD1 (from my point of view) as there is complete different process for Label handling involved/designed in EHS and tehrefore CVD1 is in most cases not "suitable" to handle labels.

    But 1% of labels might be "designed" to be used in "ETI_DIST". Never seen a further discussion on "ETI_DIST" and we are not using this process. There is no OSS etc. NOte available in which "ETI_DIST" is discussed.

    In 99% of the cases the "Label" is not distributed using CVD1.

    C.B.

    PS: what kinf of label process do you think about?

    Add comment
    10|10000 characters needed characters exceeded

  • Mar 28, 2017 at 09:19 AM

    Hello Jeevitha,

    Could you elaborate the business scenario in which shipping the label along with the SDS might is required?

    An example might help.

    Regards,

    Gaurish

    Add comment
    10|10000 characters needed characters exceeded

  • Mar 29, 2017 at 03:04 PM

    Dear Jeevitha

    I can not follow your argumentation and explanations

    in context of:

    "This requirement of shipping ETI_DIST is only specific to some specification type where MSDS_DIST is for all specification type"

    The last part is "not really true". MSDS_DIST is used in 99% of the cases for REAL_SUB only.. Nether seen a different use.

    In context of:

    "This requirement of shipping ETI_DIST is only specific to some specification type

    as well i can not follow. 99% of labels of daily business are "REAL_SUB" related. What is the purpose of a "different" spec type? And what type of label do you think about here?

    In context of "along with MSDS_DIST where flagged environmentally relevant"

    you "misinterpret" the design of report shipment partially. You could/Can use MSDS_DIST as well on "spec" level. The "environmetal flag" exists only on material level

    Still i have no clue/idea what you have now used as set up. I assume " you use a "MAN_CALL"??

    Like Gaurish explained. It is not very "probable" to combine MSDS with label. I have nether seen such requirement

    So i am really interested to understand what type of label you are thinking about and why this label should be dispatched with MSDS

    C.B.

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Dear CB

      This requirement is for all shipping reason not to only MAN_CALL. i have updated the same comment with more clarity.

      Thanks

      RJ