cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

What exit name to use to send data to customer checkout manager

former_member333938
Participant
0 Likes
459

Hello all,

I have a listenToExit for "BusinessOneServiceWrapper.beforePostInvoiceRequest" that I use to add GenericValues, but this exitName is only for business one and I need it for Customer Checkout Manager.

Does anyone know what exactly is the exitName I need?

Thanks in advance

Accepted Solutions (0)

Answers (2)

Answers (2)

JoergAldinger
Active Contributor
0 Likes

Hello rzieschang,

We managed to get the additional fields to the manager by putting them into the receipt object at an earlier stage (when pressing a button in the QS). They are then sent to CCOM automatically and we don't need to intercept the call at all.

We would expect those same additional fields to be returned to CCO from CCOM when pulling up the table or loading the centrally parked receipt from a different station, but the AdditionalFields collection seems to be empty at this stage. We haven't thoroughly tested that operation, though, so maybe we're just not seeing something yet. We will analyze that a little more and report back soon...

Thanks so far for this!

Best regards,

Joerg.

R_Zieschang
Active Contributor
0 Likes

Hi josehrmatos ,

do you want to edit the receipt data before it is send to the CCOm?

You could try to hook into with @PluginAt, class ReceiptSendToErpPosServiceImpl, method sendSalesReceiptToExternalSystem
The receipt is the first in the args array.

Hth

Robert

former_member333938
Participant
0 Likes

Hi rzieschang ,

I want to add several GenericValues to the receipt, currently I do it for the receipt that goes to SAP with the ExitName "beforePostInvoiceRequest".

Do you say it would be better to add the GenericValues in "ReceiptSendToErpPosServiceImpl"?

R_Zieschang
Active Contributor
0 Likes

Hi josehrmatos,

ok, if you already implemented this with a b1 connection, I think you know, what you are doing. 😉
And yes, the plugin exit you mentioned is only available with b1 integration, because the method, which calls the exit is only called in the b1 layer.
And yes you could try to use the method with the @PluginAt annotation, which I mentioned, but I am not quite sure, if this method is also called with b1 integration. So if you need your plugin to work with both integrations, I would suggest, to implement the exit as well as the @PluginAt.
If it's working, please let us know.

Regards

Robert

former_member333938
Participant
0 Likes

Robert I tried these blocks of code but it didn't work, I never get here.

@PluginAt(pluginClass=ReceiptSendToErpPosServiceImpl.class, method="sendSalesReceiptToExternalSystem", where=POSITION.BEFORE)
	public void sendSalesReceiptToExternalSystemBefore(Object proxy, Object[] args, StackTraceElement callStack) throws BreakExecutionException
	{
		Object recp = args[0];
		System.out.print("hi");
	}
	
	@PluginAt(pluginClass=ReceiptSendToErpPosServiceImpl.class, method="sendSalesReceiptToExternalSystem", where=POSITION.AFTER)
	public void sendSalesReceiptToExternalSystem(Object proxy, Object[] args, Object returnValue, StackTraceElement callStack) throws BreakExecutionException
	{
		Object recp = args[0];
		System.out.print("hi");
	}

R_Zieschang
Active Contributor
0 Likes

Hi josehrmatos,

retail or quick service ui?

Check in quick service ui and it should work. For retail ui I have to check.

Regards

Robert

former_member333938
Participant
0 Likes

rzieschang ,

i tested in quick service ui.

R_Zieschang
Active Contributor
0 Likes

Hi joerg.ceo , josehrmatos,

the method seems not to be triggered at all. But I tested with sendSalesReceiptToExternalSystem.

This method seems to be triggered whenever the receipt is sent to the backend.

Regards

Robert