MSDS for COPACK Materials

[ashish25bp]

Hi Experts

Need your suggestions on the following report shipping scenario for COPACK material.

We have two finished material (M1 & M2) maintained under one Main Copack material(CM).

Similarly we have two specifications (R1 & R2) assigned to Main Copack Specification (CS).

The setup of assignment is something like this

R1 and R2 will be assigned as 100 % under composition in CS

Main CO Pack specification will have a phrase maintained to identify as co pack specification.

Delivery will be created for Main Copack material CM

Our requirement is to generate and ship MSDS for material M1 & M2 (spec R1 & R2) instead of Material CM even though the Delivery is created for Material CM

Can you please advise how can this be achieved in report shipping so that we bundle two MSDS for martial M1 and M2 (Not for CM). How can SDB output will be generated for M1 & M2 material?

Is this feasible with standard SAP

Regards,

Ashish

[ashish25bp]

Thanks to all of you for your valuable inputs and suggestions. Each reply seems to be helpful for us and we are analyzing our approach based on that. We do not have clarity on the volume of material in this case as of now, as it is in a very initail stage where we are exploring feasibility for this requirement. The inputs provided here will be useful for us as we start built a logic. I will definately update this thread as a new learning and for curiosity, once we implement this requirment.

[satya11719]

Hello @Christoph Bergemann

I agree with your point and the thing is in reality no one even ask for the Components SDS when you are shipping the material it is rare case and i never heard of this before.

In this case it seems it is packaging material specification and they can use CG36VEN and upload the component SDS and assign to RGV and they cans send, in this case also SD_CALL is not possible cause we are not creating delivery for the components.

Long story in short : It is always depends on the business if they want to use permanent solution solution based on the frequency and order from the customers.

Thanks

Satya

[former_member3035]

@Christoph Bergemann Hello,

I want to check 1 think with you - What will happen if we add Specification Symbol in Coversheet?

Usually what I see and read - Most cases have Parameter Symbol for Material number and Address. If I use Specification symbol - It will fetch some VAT / Char information on cover sheet ? or it will not read any information from Specification?

Thanks

Idrees

[christoph_bergemann]

Dear Idress

the "Cover Sheet" is a very special document. The issue is: you do not have any "generation variant" assigned to coversheet generation process and any selection from spec. master data require the definition of a "usage" so that you can use this in Cover Sheet process

Any material data (ESTMJ) is any how "parameter" like and the only objects, which you could use in CoverSheet without a problem (if i remember correct), is to print:

Spec id

Substance nature

etc.

So anything from "spec" header as there is no "usage" related to this information; for me: this does not really add value... the customer is communicating with you in 99% of the cases by using "Material numbers" and not spec ids

C.B.

[former_member3035]

Hello ashish25bp and christoph.bergemann

Find the attached flow diagram. I believe finding the correct child material is possible. Below are some more inputs:

1] Need to think on numbering and nomenclature which are going to use in MSDS as it should not confuse the customer which child material belongs to which FERT (Usually customer know this but still we need be specific which description of MSDS and with the sequences)

2] If we follow the attached flow - I believe below will be the correct way to follow the sequences and on cover-sheet also it is suggest to have underline MSDS details.

Cover-sheet :

M1 - 1.1/1.2/1.3

M2 - 2.1/2.2/2.3

MSDS naming convention :

• M1_M1.1
• M1_M1.2
• M1_M1.3
• M2_M2.1
• M2_M2.2
• M2_M2.3

Need to have more closer look on how we can bundle all MSDS

and send in proper sequence

Thanks

Idrees

[christoph_bergemann]

Dear Idrees

regarding your sentence:

1] Need to think on numbering and nomenclature which are going to use in MSDS as it should not confuse the customer which child material belongs to which FERT (Usually customer know this but still we need be specific which description of MSDS and with the sequences)

This is not clear for me. I interpret this as:

The SDS/MSDS to disptach are linked on R1 and R2. In practical process. there is no chance to guarantee that the version number of e.g. FR SDS on R1 is the same as on R2.

Is this your story regarding numbering"?

What do you have in mind if you use the term "nomenclature"here?

The trick is really (as you try to explain according to my understanding): Cutomer is asking for material CM but in reality will get M1 and M2 (somehow: this is my "two component glue example); one on top challenge here is: how to handle "labels"

https://www.worldbuild365.com/media/products/07a530ba8f55225ccc91afac5b1c00c3/7ca545cef53a160d92334c... shows such an example: So yo have two physical materials which are packed together; the customer will by the "package" (this would be CM) but it contains M1 and M2

You picture descrbes high level the process design; and as i have explained. one on top challenge is the "bundling" part in SDS shiphment

Very nive picture of process flow !

C.B.

[christoph_bergemann]

Dear Ashish

referring to your sentence:

"We have two finished material (M1 & M2) maintained under one Main Copack material(CM)." and suggestion by Idrees:

SAP allows to generate several types of "BOMs". One BOM type is related to the "Sales order"; the other more on the "production" part; you need to think about: which BOM is the "best" one; both can be used as the starting point for SDS dispatch.

The idea of Idrees will work if you are willing to extend the interface SAP SD => EHS for SDS dispatch (more or less: in the interface you generate then "two" requests for SDS dispatch and not one). So from my point of view: a SD_CALL process can be set up. The "MAN_CALL" approach is not really feasible as somebody need to check if there is some relevant sales order/delivery happening; this is time consuming; but it is a workaround if you are not willing to invest a lot of money.

There might by only somthing you have to consider on the top:

The customer is getting material number "CM" (you sell CM to him). THis relation should be transparent in the SDS shipment. Normally you have a "Cover Sheet" attached to the SDS dispatch. If you extend then the idea of Idrees; then you must/should enhance the "Cover Sheet" part as well. Keep in mind the problem of "media". You can have a "print" or an "eMAil" dispatch; and you need to think about this situation:

E.g. Customer is sitting in "FR". On R1 and R2 now an SDS should be available, But what should happen if this is not the case? And only e.g.one SDS is there?

You have two options: you need to extend SDS shipment approach either customer will get only one SDS (if the other does not exists) or you extend the process in such a way that the process should "wait" until both SDS are there to be then dispatched in one "bundle" to the customer

Over all: It seems to be that you are talking about materials like "two component glues"; and this topic is discussed quite often here. You will find threads in context of "SVT" and "DG"

C.B.

[former_member3035]

Hello Ashish Pradhan

You can achieve by developing a logic, Below are some overview how we can achieve child level report shipping:

1] SD: Find list of material in Sales order having BOM

2] PP: SO header have plant info maintained - with this plant number - Find the BOM which is active and valid for this BOM

3] Filter these material - excluding FERT Material so that only you left with child level material

4] Find the Spec - where these child level material are used

5] Find the release report against these spec - latest version

here need to keep the nomenclature of report in order to which child material report belongs to which FET item. Also need to send in a set of sequence - first will be first line item sales order FERT Item child level report. Then start second line item of sales order child material report.

I will prepare a process flow how we can achieve this and send you shortly.

Thanks

Idrees

[satya11719]

Hello Ashish Pradhan

It is the rare scenario , But the question how frequently you will send this SDS , I can suggest you to use MAN_CALL.

Cause you will create delivery for CM for M1 & M2.

R1 and R2 will be assigned as 100 % under composition as REAL_SUB ? and for this you need assign material right ?

your requirement will not fit into standard structure model and Standard way of SD_CALL is not possible as well , if feasible go for MAN_CALL.

Let me know if this helps.

Thanks

Satya

[christoph_bergemann]

Dear Satya

your approach will in reality only work if somebody is doing an permanent analysis of relevant deliveries and then decide: is the MAN_CALL needed or not. Even if we talk may be only of 100 materials with similar data situation: this is a process which can be used a " work around" and last chance and if you are not willing to invest IT money. But money for people is as well expensive. So yes. it is possible. But i would no tuse this option

C.B.

PS: i forgot to mention: you have in any case a issue with "subsequent" SDS shipment (but this depends on business philosophy and is not critical)