cancel
Showing results for 
Search instead for 
Did you mean: 

TerminalBasicTemplate80mm.xsl / Printlayout

Private_Member_381693
Active Participant
0 Kudos

Hello

The print template TerminalBasicTemplate80mm.xsl deployed from the pepper plugins (PepperPluginNG-2.9.16 or PepperPlugin_17.1-2.9.16) do not print anything. There is a wrong reference in the select in row 11. It should be ".../com.sap.scco.plugin.pepper..." instead of ".../com.sap.plugin.pepper...".

After this change there is an output but the print-out is not really good readable. Due to the submitted datastructure (one string per line) all "columns" like Cardname, Count and Amount are all togehter.

Has anybody found a solution for a readable print-out?

Accepted Solutions (1)

Accepted Solutions (1)

0 Kudos

Hello kfrick,

The fix is contained in today's new patch of SAP Customer Checkout 2.0 FP09 PL13.

In order to avail of the fix please follow these steps:

  1. Upgrade your CCO to 2.0 FP09 PL13
  2. Go to C:\SapCustomerCheckout\cco\print_templates
  3. Remove or rename the file TerminalBasicTemplate80mm.xsl
  4. Go to C:\SapCustomerCheckout\tools
  5. Select either PepperPlugin_17.1-2.9.20.jar or PepperPluginNG-2.9.20.jar (depending which API you are using)
  6. Copy the file over to C:\SapCustomerCheckout\cco\POSPlugins\AP
  7. Remove or rename the older version of the PepperPlugin.jar

This should solve the issue you reported. Thanks for this valuable contribution!

Best regards,

Gunther

Answers (2)

Answers (2)

Private_Member_381693
Active Participant
0 Kudos

Hello Gunther Sandtner

Thank you for confirmation. For better readability I adjusted my template by changing the font, font-size and space handling. If anybody has the same problem you can find my adjustments below.

Best Regards

Klaus

<fo:block text-align="center" space-before="9pt" font-family="Consolas" font-size="7pt" white-space-collapse="false">
	<xsl:for-each select="$terminalReceipt/receiptLines/string">
		<fo:block>
			<xsl:value-of select="text()"/>
		</fo:block>
	</xsl:for-each>
</fo:block>
Arne_Timmermann
Contributor
0 Kudos

Can't confirm this. Print template works fine for us.Which CCO version are you using? Did you try to delete the template from the printtemplate folder and let it redeploy by a CCO restart?

Private_Member_381693
Active Participant
0 Kudos

Hello arti3000

Yes I´ve tried with redeploy with FP09 PL11, PepperPluginNG-2.9.16 and FOP. From my sight it should be impossible that a print-out is working, when the reference in the select leads to "com.sap.plugin.pepper...." instead of "com.sap.scco.plugin.pepper...." - at least for the versions I use.

Best Regards

Klaus

Arne_Timmermann
Contributor
0 Kudos

Hi kfrick , so far we are only using FP09 PL09 productive. I would highly recommend to open a high priority incident, if the issue is as clear as you describe the matter ist really urgent and important and should be fixed asap by CCO development.

Private_Member_381693
Active Participant
0 Kudos

Hi arti3000

Thanks for feedback. What Pepper Plugin do you use in productive and do you use FOP or JPOS?

0 Kudos

Hello kfrick,

It is exactly like you say. Only an empty page is being produced for the settlement report (Kassenschnitt) from the EFT when using FOP.

The required fix is also exactly like you found out:

Incorrect:

<xsl:variable name="terminalReceipt" select="//entry[string/text()='terminalReceipt']/com.sap.plugin.pepper.print.TerminalReceiptDTO"/>

Correct:

<xsl:variable name="terminalReceipt" select="//entry[string/text()='terminalReceipt']/com.sap.scco.plugin.pepper.print.TerminalReceiptDTO"/>

We will provide a permanent fix for that. I'll update once the fix is delivered.

Regarding your concern about the content and readability I'm afraid we only print 1:1 what is coming from the EFT terminal. There we do not influence anything.

@arti3000 Did you perhaps check on the sales receipts only? These will still work fine. Only during the day-end closing with EFT this error comes up.

Best regards,

Gunther

Arne_Timmermann
Contributor
0 Kudos

Hi gunther.sandtner2 and kfrick luckily we are only using jpos, so we were not affected!