Author: admin

SAP Cloud Platform Integration (SAP CPI) simplifies the custom-driven integration with SAP S/4HANA Cloud  by using a wide variety of SAP S/4HANA Cloud APIs. These APIs play the major role in exchanging data with other systems. Offering OData and SOAP protocol based APIs SAP S/4HANA Cloud is perfectly equipped to meet this requirement now and in the future. The central tool to explore all available SAP S/4HANA Cloud APIs is the SAP API Business Hub.

This blog series consists of two Blog posts. In this series the integration possibilities between SAP S/4HANA Cloud and the SAP CPI will be outlined by using a SOAP API of SAP S/4HANA Cloud to replicate business data to the SAP CPI. As SOAP APIs are best suited for a asynchronous exchange of have weight data and is mostly used in the Business-to-Business and Application-to-Application context this blog series uses SOAP APIs.

Deploy the integration flow on the SAP Cloud Platform Integration

The following steps describe how to deploy your integration flow (iFlow):

* Logon to the SAP CPI with the appropriate user roles assigned. The four appropriate user roles are as follows (for more details visit the SAP CPI help page):

* AuthGroup.Administrator
* AuthGroup.IntegrationDeveloper
* ESBMessaging.Send
* Auth.Group.BusinessExpert

* Switch to the Design menu option in the main menu on the left.
* Create a Package.
* Open the Package by clicking on it and create an Integration Flow in the ARTIFACTS tab.
* Connect the Sender with the Start event by drawing a message flow between them.
* Select SOAP as adapter type and SOAP 1.X.
* Open the message flow settings by clicking on it and open the Connection tab. Enter a desired Address for your endpoint on the SAP CPI.
* Finally deploy the iFlow on the SAP CPI.

Retrieve the endpoint of the iFlow

This step describes where to find the endpoint url of your recently deployed integration flow. Both information will be needed during the setup of the Communication Arrangement in the SAP S/4HANA Cloud system.

* Switch to the Monitor menu option in the main menu on the left.
* Navigate to the Manage Integration Content section.
* Select the iFlow in the Integration Content navigation pane.
* Copy the complete URL displayed in the Endpoints tab and save it for later. The URL consist of the host name and the specific path of the iFlow.
* Continue with the SAP S/4HANA Cloud setup which is described in this blog.

Setup the Certificate-to-User-Mapping

To enable the communication between the SAP S/4HANA Cloud system and the SAP CPI system you have to upload your authentication certificate of the SAP S/4HANA Cloud system into the SAP CPI. To do so:

* Switch to the Monitor menu option in the main menu on the left.
* Open the Certificate-to-User Mapping App in the Monitor Dashboard.
* Enter the SAP CPI user name and choose the certificate of the S/4HANA Cloud system downloaded during the setup of the Communication Arrangement.

Monitor replicated data

After replicating the data in the SAP S/4HANA Cloud system (described in this blog) the data was sent to the endpoint configured in the iFlow on the SAP CPI. Proceed as follows to Monitor the data replication:

* Open the Message Processing Monitor.
* Select the iFlow in the left navigation pane.

The detailed communication log of the data exchange between the S/4HANA Cloud system and the SAP CPI are shown in the message processing logs which can be found on the right side of the screen. http://bit.ly/2GmoeyA #SAP #SAPCloud #AI

Hi All,

As per the Italian Tax regime, the “Certificatione Unica” which is the income tax statement issued to employees by their companies is required.

This feature has been enabled in the Business ByDesign system version 1802 onwards and below are the steps to configure the same.

* Go to the Business configuration work center.
* Select the Implementation project view.
* Click on Edit Project scope.
* Go to the Step-4 Questions.
* Expand the Cash Flow Management and Select Tax Management.
* On the right hand side, you will see the questions related to the Withholding tax filing – Italy

Here you will find that you must select the questions :

* Do you use Withholding tax File for Italy CU Return AND also tick the question?
* Do you use the withholding tax form for Italy CU return?

Later in the

* Tax Management work center
* Navigate to the Tax Authorities view.
* Select the tax authority of country Italy and press Edit – Company Tax Arrangements.
* Navigate to the Tax Return Arrangements subtab.

Here you will find that Tax return type – 13-Withholding tax return is relevant and the Electronic submission required box will be enabled and has to be ticked for electronic submission.

 

In the same way for the Tax return type – 16-CU-Withholding tax is relevant and the Print form required must be ticked to print the form.

Note – This feature is available in Business ByDesign 1802 onwards only.

 

Regards

John Nelson Paul

 

  http://bit.ly/2GpphOe #SAP #SAPCloud #AI

SAPs Extended Computer Aided Test Tool (eCATT) offers in its language two interesting commands – TCD and SAPGUI – to executes some recorded activities. In this blog post I describe how the commands works, from the recorded XML file to the BCD respectively to the OLE interface of the SAP GUI Scripting.

TCD

You can with the TCD eCATT command record very easily activities and executes it as batch data communication.

Press the pattern button of the toolbar and choose UI Control with TCD (Record), define the TAC and the interface name. Now your TAC is open and you can do your activities. When you are done quit the TAC and you will get a request.

If you say yes your script looks e.g. like this and you can execute it.

But what happens in the background?

The eCATT line interpreter executes your script and calls the method EXECUTE_TCD, which calls the function CAT_TCD_CAL and this runs your activities as batch data communication CALL TRANSACTION command.

SAPGUI

Batch data communication offers not all possibilties. In this case you can use the SAPGUI command. It records your activities also easily and executes it via the SAP GUI Scripting interface.

Press also the pattern button and choose SAPGUI (record).

Define your transaction code and start the recording. Now an additional dialog pops up.

If you are ready with your activities press stop recording and your script looks like this.

Here we see now very good the difference between BDC and SAP GUI Scripting. But much more interesting is the background processing.

The eCATT line interpreter executes your script and calls the method EXEC_SETGUI. The REPLAY_SAPGUI method calls the SAPGUI_INTERNAL_REPLAY method which starts the transaction code. After the methods SAPGUI_REPLAY_PROCESSED_SCREEN and SAPGUI_REPLAY_USERCHANGES shares the methods SAPGUI_THROW_COMMAND and SAPGUI_THROW_GUI_ELEMENT. Both use last but not least the OLE commands GET and SET PROPERTY as well as CALL METHOD.

With this knowledge is it now very easy follow the process from the eCATT script to the final OLE command call.

The eCATT script files itself are stored as XML files, here an example section:

Last but not least a tiny hint to SAP note 2382576: eCATT uses only the SAPGUI entry from the running object table (ROT), so it is not possible to use it with NWBC or ADT.

Enjoy it.

Cheers
Stefan http://bit.ly/2Gq0lpA #SAP #SAPCloud #AI