Skip to Content
Former Member
May 13, 2013 at 07:26 AM

SDS Version numbering in CG36 and Test scenario for subsequent shipping


Dear Experts,

I have couple of questions regarding SDS upload and SDS Subsequent shipping,

1) Document versions in CG36 for Inbound SDS:

In this case, the SDSs are Inbound pdf documents, and the mass upload transaction CG36 is used to upload them to the Report Management.

I'd like to maintain the difference between major change and minor change in the versions of the SDSs when using CG36.

However, unlike with CG36VEN where the version number is given manually during the upload,

transaction CG36 inserts an equal version change for all inbound documents, ignoring the version number (=VER) stated in the Key file.

So to me it seems that in CG36, the version number stated in the Key file is ignored by the system standard. Is there some change i could do in the configuration to make the version number stated in the Key file become picked up as an actual version number for the document?

2) SDS subsequent shipping. F.ex shipping after one year from the first shipment to the customer:

How have you tested this scenario during the implementation, in a situation where the test environment does not contain sales orders dating back one year? F.ex. have you temporarily changed the period between first and subsequent shipping into two weeks or two days etc.?

Where in the configuration can you change this time period?

Many thanks in advance!