Question Re: CCO Extension points for cash-in/cash-out transactions in CRM and CX Q&A

CCO Extension points for cash-in/cash-out transactions

JoergAldinger — Wed, 20 Nov 2019 05:51:19 GMT

Hello all,

I am looking for the right extension point to intercept and modify the cash-in, cash-out (including day-end-closing) transactions. I have tried both the POSTInvoice_Payment and POSTPay_Payments extension points (they seem pretty much identical to me?), and while the former works fine for the incoming payment of invoices, I can't seem to be able to hook into the cash-in/out transactions using either.

Unfortunately none of the documentation I have found lists and explains all of the extension points. Most of these documents are quite old already. These are the documents I have consulted so far.

Thanks in advance,

Joerg.

Re: CCO Extension points for cash-in/cash-out transactions

JoergAldinger — Thu, 21 Nov 2019 16:21:10 GMT

Could anyone from the CCO team help on this?

Thanks,

Joerg.

Re: CCO Extension points for cash-in/cash-out transactions

Klaus_Frick — Fri, 22 Nov 2019 14:48:47 GMT

Hi Joerg

For cash-in/cash-out it should be Scenario sap.POS.POSTPay. I just did a cash-in on CCO and then followed the message log in B1if. Hope this helps?

Re: CCO Extension points for cash-in/cash-out transactions

JoergAldinger — Fri, 22 Nov 2019 14:51:53 GMT

Hi Klaus,

It does to some point. It confirms that this is where it should work. Now at least I can try to find out why it doesn't. For some reason my B1iF installation doesn't let me switch to proper debug mode with message logging. But that doesn't have anything to do with CCO...

Regards,

Joerg.

Re: CCO Extension points for cash-in/cash-out transactions

Klaus_Frick — Fri, 22 Nov 2019 15:42:08 GMT

Hi Joerg

I found that in regular message log in Monitoring. For step debugging you have activated the detailed Logging in Maintenance -> Cfg Dev Env?

Regards

Klaus

Re: CCO Extension points for cash-in/cash-out transactions

JoergAldinger — Fri, 22 Nov 2019 17:24:55 GMT

Yes, I have. Strangely however it does not seem to have the desired effect:

As you can see, the B1i stays "blue" even though it's supposed to be configured as "development environment" with the orange bar on top instead of the blue. It's the latest version (B1 9.3 PL11), so I'm not sure of there's something broke there. (And yes, I did restart all services after setting it as a development environment.)

Any idea?

Regards,

Joerg.

Re: CCO Extension points for cash-in/cash-out transactions

Klaus_Frick — Sat, 23 Nov 2019 08:51:15 GMT

With this configuration you have Read-Only Mode in Step Design sap.CustomerCheckout? Then just change development prefix from ceodo to sap.

Regards

Klaus

Re: CCO Extension points for cash-in/cash-out transactions

former_member280904 — Mon, 25 Nov 2019 07:50:32 GMT

Hi Joerg, hi Klaus,

as Klaus said, the step that is called in B1if for cash-in and -out-postings to B1 is sap.POS.PostPay. Hence, the extension point to choose in case of cash-ins and cash-outs is sap.POS.PostPay_Payments.

In case of day end closings, the scenario step sap.POS.POSTSummary is called for postings to the SAP Customer Checkout Monitor. Please use here the extension point sap.POS.POSTSummary_PostProcessing.

To see the message flow for development purposes, follow the steps as explained by Klaus.

Best regards,

Armin

Re: CCO Extension points for cash-in/cash-out transactions

JoergAldinger — Mon, 25 Nov 2019 16:37:10 GMT

Thank you for getting back to me, Armin and Klaus!

Let me quickly mention what I am trying to do. Since we're setting up CCO in a B1 foreign currency, I have identified two problems in how payments are posted in this scenario:

The exchange rate from CCO is sent to B1 in the payment header. This causes a wrong transaction conversion, but is fixed if I strip the "DocRate" tag completely from the header, so that B1 takes care of the exchange rate determination.
The CashFlowAssignment value needs to be sent in the correct child tag according to the local or foreign currency (AmountFC/AmountLC), if the amount is in the wrong tag you will get a "unbalanced cash flow" error. (Apparently, rather than having the value "in the wrong tag" as I was assuming, apparently the value needs to be converted appropriately to local currency.)

Besides these two fixes, do you see any other problems with this specific scenario? Is that something you could support natively in the future?

Thanks and best regards,

Joerg.

Re: CCO Extension points for cash-in/cash-out transactions

JoergAldinger — Tue, 26 Nov 2019 00:52:04 GMT

Hello Armin, Klaus:

I think I have progressed a little on the scenario, since I can now properly debug the messages. However, I am unsure on how to construct the information so B1 properly understands it. The following is a Cash-In transaction that should credit the account 111-110-02 (master petty cash) and debit the account 111-120-22 (POS petty cash). It is a foreign currency operation for B1 so I am inserting the exchange rate from B1, and also setting the CashSum to (FC * $rate).

Currently, both accounts are set as "cash flow relevant", but I have tried unmarking one just for testing and the result was the same (the other account cannot be unmarked anymore).

However, I am still getting the "unbalanced cash flow assignment" for this operation:

See final payment below, where the foreign currency value is 104 USD, with an exchange rate of 52.75:

Please let me know what I'm missing in the output so I can correct it as soon as possible.

Thanks!

Joerg.

Re: CCO Extension points for cash-in/cash-out transactions

Klaus_Frick — Thu, 28 Nov 2019 10:15:02 GMT

Hello Joerg

I would try to book this case manually in SBO and then save the booking with DI afterwards to XML. Then you might find the difference more easily....

Best Regards

Klaus

Re: CCO Extension points for cash-in/cash-out transactions

JoergAldinger — Thu, 28 Nov 2019 13:06:50 GMT

Hello Klaus!

Thank you, I had already thought of that. What I did to find the issue is to validate the XML structure using DI Server/B1WS, since that's a little faster/easier to modify. Then I went back to the scenarios and noticed that the problem was caused by an XML "merge" further down the line (after the extension step).

So in the end this issue resulted to be a bug in the B1iF scenarios delivered by CCO. The team was so kind to release a new version today, see version 4.0.4 of the scenarios in SAP note https://launchpad.support.sap.com/#/notes/2163033

Best regards!

Joerg.