Subsequent Shipping and Sending of PDF file thru Email

[Former Member]

Dear EHS Experts,

Can I have your expert advise on my question below please?

1. Is there any environment parameter available wherein it only deletes all rejected report request in CVD1 say 1 week after its request date? If there is, can you please specify the environment parameter?
2. I have tried activating the subsequent report shipping in SD_CALL so I just ticked the subsequent shipping in the shipping reason. I also set up the SUB_CALL. SAP delivers EHS_SAVE exit only for this “Reason”. FM has also been set up in Assign Check and Subsequent Shipping Functions.  To test it, I have created a new version of report template, released it and created a report. Eventually a new report was created with a new version (e.g.- from 1.0 to 1.1) and the same was also been released. I have executed the SD side transactions. When checking CVD1 it had a status of rejected. As per my understanding, it should not be rejected due to subsequent shipping functionality. The client is using SAP ECC 6.0. I suspect the missing config is in Assign Names for User Exits. Just to reiterate that only EHS_SAVE exit is available in SUB_CALL. I did some research and EHS_SUBSEQ should be set up but I couldn’t find this exit.  Are there other exits that I need to set up in Assign Names for User Exits? Is my understanding also correct that the button “Activate Subsequent Shipping” within Edit menu in CVD1 is only for manual activation of subsequent shipping and no need to select it if I have selected the said indicator in config of Specify Shipping Reasons?
3. I have tried using the email functionality in sending MSDS and I just got worried about the size of the file. Upon receipt of the email attaching the MSDS, its size was 2.5MB. The file name was RTF as it was the standard format assigned in WWI and I didn’t change anything. Is this normal using the said file? I want to reduce the file so can you please advise what specifically should I do?
4. Regarding sending a PDF file to the customer like in email, can you please guide me on this? Ive made some initial reading and looks like there’s a need to update the content of WWI.INI like shown below.

;command=printto

;target=c:\temp\target.ps

;printer=Convert

command=

target=

printer=

[Printers]

PS=

PCL=

;PDF=Acrobat Distiller

[PrintUserExits]

; Format=addin(.dot);macro(.main)

;PDF=c:\wwi\wwiMkPDF;wwiEConvertToPDF

I would really appreciate if you could send me a procedure or steps on how to execute  inside the system in relation to the my question. You may send it at jaguardrives@yahoo.com and I would be glad giving you the points.

Kind regards,

Mark

[christoph_bergemann · Accepted solution]

Dear Mark

regarding 1:

Check may be:

http://www.stechno.net/sap-notes.html?view=sapnote&id=174268

regarding 2.

A subsequent report distribution is only taking place if main version changes. So if you change "1.0" to "2.0". No support is provided (by standard) if you create a minor version (1.0 => 1.1).

regarding 3.)

The file size depends on type of SDS/MSDS. An european SDS/MSDS can be "big" (after REACh is now in place the SDS/MSDS might be very long (> 100 pages). An e.g. US SDS/MSDS might be "smaller". SAP is providing a functionality to take care regarding size of "raw report" etc. (there is a "zip" functionality in place).I assume a "similar" option might be possible in "final report creation" but from SAP point of view: it is only planned/realized  for "raw" report and not for final report generation,  but you generate (in any case) a "rar" (or zip) file which the receiver need to accept and this might not be the case for all receivers; there is no other option (to my knowlegde) possible to reduce size of document.

regarding 4.)

This topic has been discussed "very very" often here. Pleasse check e.g. http://scn.sap.com/docs/DOC-41109

I did not count the number of threads which discuss this; but there are many (pay attention: you ned to "do" something on WWI server side and in SDS distribution process as well; additional customizing steps are required (and there is a "risk" that you can not "reduce" size of document (like with rtf topic as discussed before.).

Hope this helps

C.B.

[Former Member · Accepted solution]

Dear C.B.,

Thank you for providing me the needed and helpful info. In point 2, I just tested it now and looks like there is a config missing and i suspect standard exit is something to do with it. I was able to generate a new main version. (e.g.-1.1 to 2.0). When checking CVD1 the report has a status of "rejected" because of the routine of 12 mos/365 days. I did attached the standard routine of subsequent shipping but still it didnt send successfully. Below is the standard config and modified:

1st test:

SUB_CALL has exit of EHS_SAVE

Test Result: second shipping was rejected though it has a new higher version

2nd test:

SUB_CALL has exit of EHS_SAVE, EHS_BUNDLE, EHS_CHECK, EHS_GEN and EHS_PACK_P

Test Result: second shipping was rejected though it has a new higher version

Can you guide me place whats the correct one? Please let me know also if i missed something in CVD1.

Thanks in advance for your guidance.

Kind regards,

Mark

[christoph_bergemann · Accepted solution]

Dear Mark

regarding subsequent shipment I would like to start from scratch. May be I misinterpreted your topic a little bit.

a.) you have prepared material <=> spec combination (and material is "active" regarding EHS)

b.) you have generated suitable report (genvar / language combination) on spec level

c.) the material has been delivered (in europe) once in last 12 month and therefore one final report should be found in CVD1.

d.) now you generate a new major version; in this case the system does not need a SD order but the subsequent shipment is done independent from that.

In http://scn.sap.com/docs/DOC-41109

you will find a number of hints regarding the set up of SDS disitrubtion (with all the steps required etc.)

As SDS distribution is "flexible" (regarding customizing set up and assignment of function module) a number of reasons can be listed why you detect the effect.

So regarding your examples (If I understand them correct)

1st test:

SUB_CALL has exit of EHS_SAVE

Test Result: second shipping was rejected though it has a new higher version

The sub sequent call should be triggered by main new version (e.g.) and not by a SD call. Main new version must be (in europe) distributed. Different rules apply for e.g. US etc. (topic of: which gen var/language combination is the "right" one)

2nd test:

SUB_CALL has exit of EHS_SAVE, EHS_BUNDLE, EHS_CHECK, EHS_GEN and EHS_PACK_P

Test Result: second shipping was rejected though it has a new higher version

This is the same.

Regarding the first topic:

If in the past version e,.g. 1.0 has been shipped and now 1.1 is available I am not "complete" sure how SAP standard should react.  Most companies does have the trend to be more compliant as needed. Therefore: even if 1.1 is only a minor version this version might be shipped (normal call! not sub sequent call) in some cases.

Please read cross OSS note: 1096697 (e.g.: http://scn.sap.com/thread/1736108). This is a "must to read" OSS note regarding SDS distrbution.

C.B.

PS: check:

http://help.sap.com/erp2005_ehp_06/helpdata/en/a7/2877d10a6c11d28a220000e829fbbd/content.htm?framese...

e.g. chapter " Saving of Report Shipping Orders",  "Report Shipping Order Checking  "

[Former Member · Accepted solution]

Thanks C.B. It's getting clearer now how subsequent shipping is being triggered. However, i need more info about the missing config or set up why subsequent shipping is not being triggered. In standard, does subsequent shipping work as well? When EHS was activated, SUB_CALL was assigned to EHS_SAVE exit only and nothing else. I also checked the Schema part and all were set up correctly. What could be the possible missing error. Please enlighten me more.

[dhinsap]

Dear Mark,

the problem can lie with the function module I believe. If you have copied the function module for Europe or any other country, this will check for the R/3 System checks whether a released subsequent shipping order exists whose date of creation lies within the last twelve months. The target shipping date is irrelevant here. If the main version of the subsequent shipping order is also identical to the version of the new report shipping order, the new report shipping order is rejected.

If incase, u adopted the FM for European union, check this data

The check function CVEM_RDO_CHECK_EU accepts a new report shipping order only if no equivalent report shipping order has been received by shipping or subsequent shipping within the last twelve months.

The check runs through a total of three steps. In steps one and two, the R/3 System runs the check for report shipping orders whose target shipping date is less than 12 months ago. By using the target shipping date, the shipping lead time is also taken into account.

In the standard system the target shipping date is calculated by:

• Subtracting the lead time from the goods issue date for shipping from delivery

• Subtracting the lead time from the requested delivery date for shipping from orders

• Step 1:

In the first step, the R/3 System compares the same criteria as for the validity area USA (see above) but initially ignores the main version. If within the last twelve months a report shipping order is identical in all criteria to the new report shipping order and the subsequent shipping indicator is set, the new report shipping order is rejected. Reshipping a report is then not necessary as the customer automatically receives a new version of the report via subsequent shipping.

• Step 2:

If the subsequent shipping indicator is not set, the second step also compares the main versions. If the main versions match, the new report shipping order is rejected. If the customer issues a new purchase order every month, for example, and if the main version of the report that was originally sent is unchanged, a new report is not sent to the customer. Only if the customer renews the purchase order after a break of more than twelve months does he/she receive a report again, regardless of whether the main version has changed or not.

• Step 3:

If no previous report shipping order was found, in the third step the R/3 System checks whether a released subsequent shipping order exists whose date of creation lies within the last twelve months. The target shipping date is irrelevant here. If the main version of the subsequent shipping order is also identical to the version of the new report shipping order, the new report shipping order is rejected.

Debufg the FM for europe, u will find the solution.

Regards

Dhinesh

[christoph_bergemann]

Dear Mark

check may be: Oss note: 1713905. This is related to "incorrect" handling of subsequent shipments (dated may 2012).

C.B.