Trigger CREXTPRT during print file generation is missing sequence number

Hi All,

I have a requirement to do XtendM3 logic when MWS435PF/MWS485PF files are generated. Custom tables are updated and through CMS006, they are related back to the original print file.

Everything was going well until multiple sequence numbers were outputted for MWS485PF with the same job number. My custom table uses the job number as its only key, although it seems now I need the sequence number as a secondary key.

Following the KB article listed KB 2253585, you have access to the below parameters.

// Get input arguments from method
String printerFile = method.getArgument(0) as String; //PRTF
long jobNumber = method.getArgument(1) as long; //BJNO
String structure = method.getArgument(2) as String; //RPLY
int variant = method.getArgument(3) as int; // XMLT
int rpbk = method.getArgument(4) as int; // XML Section
HashMap<String, Object> fieldMap = method.getArgument(5) as HashMap;

In CMS007 (for MWS485PF), I have enabled the DOC_HEADER section for XtendM3, and adding a custom section below that. Therefore, I only have visibility of elements in the DOC_HEADER section and as far as i'm aware, I can't add the sequence number to this section and pass it into XtendM3.

What are everyone's thoughts on how to get the sequence number passed into CREXTPRT?

Thanks, Callum

Find more posts tagged with

Accepted answers

All comments

martin-jarrolf

Hi,

You can add the file name that contains the sequence number and use that as key.

It is done in CMS009 by adding a field with Element type: 1-Text element and Source of data: 62-File name.

/ Martin

CWRIGHT

Thanks Martin, unfortunately i'm having difficulty getting the custom field from CMS009. The Custom PIPISS field is pulling through, but not the ZZFILE, maybe because the field name is being passed into XtendM3, not the element name.

Here's an example of the log:

XtendM3-Post_Print_Generation: {PIPLRI=, MGIRCV=, OQRIDN=1000000755, OQDSHM=1800, OQROUT=S01, PISEEQ=50, OQWHLO=100, OQADVI=, &MOT2=, &MOT1=Standard Delivery, PISLTP=W2, &TEDL=CFR, OQCONA=POLE10, &DATE=2.0230216E7, OQDSDT=20230126, PIPISE=99, &MODL=S01, &COPY=1.0, MWWHNM= (Fac 100), OQCONN=0, PIPLSX=1, PIPICK=, PITEAM=, &DLT2=(... named port of destination), &DLT1=Cost and Freight, OQDLIX=1000831, PIPISS=40}

And my CMS009 config.

martin-jarrolf

Sorry, I was quite sure the file name was passed in the hashtable.

All I can recommend is to add additional fields that makes the key unique, like DLIX and PLSX.

Copyright © 2025 Infor. All rights reserved.