Day: March 1, 2018

Please find below list of related blogs, it is convenient to jump between them.

Cloud Print Manager – Install and Configure

Output Management – Customize Master Form for Logo Address Data

Output Management – Customize Content Form for Outgoing Check

Output Management – Customize Email Form for Payment Advice

This is a continuation of blog for customizing eMail Form Template for Payment Advice. The predelivered eMail templates are maintained in Fiori App Maintain Email Templates.

The Email template is edited online in ABAP UI and does not need the Adobe Livecycle Designer needed for Master Form Template and Content Form Template.

This procedure uses standard SAP delivered Payment Advice form and is chosen because it is convenient to send the payment advice form by email while checks can be printed physically. Instead of standard SAP delivered payment advice form if you want to customize the form then please use the previous blogs for customizing Master Form and Content Form and then define the Content form in the last step under Output Parameter Determination – Form Template TIP: Please note that you should download/modify/upload template in Q-System. After it is uploaded in Q-System, you can move forms across landscape using Q-System Fiori tile “Export Software Collection” and then import into P-System using Fiori tile “Import Software Collection”.

STEP 1: MAINTAIN EMAIL TEMPLATE

Select Fiori app from group – Output Management, Fiori tile – Maintain Email Form Templates. 

To easily select the template, please set filter as required – click on (1) Predelivered Templates, (2) Description as check, (3) Available Languages as English, (4) Available Countries as USA, Click on (5) Go and (6) RightArrow to open the Content Template.

Click on Copy

You will see the copied form in (1) Custom tab. Select the (2) Email Template and Click on (3) >

Select English Language click on (2) Change Details.

You can change the text and then click on Save.

STEP 2: SSCUI – DEFINE EMAIL SENDER DOMAIN

In Q-System select Fiori group – Implementation Cockpit – Fiori tile Manage Your Solution. You will require authorization to Role SAP_BR_BPC_EXPERT

Select Configure Your Solution,

Enter (1) “domain” and click on (2) Search, Select (3) Define Email Sender Domain and click on (4) >

Enter name of domain

Click on Save.

STEP 3: MAINTAIN BUSINESS PARTNER 

In Q-System select Fiori group – Business Partner Master – Fiori tile Maintain Business Partner. You will require authorization to Business Catalog SAP_CMD_BC_BP_MAINT_PC

For every business partner (1), click on start (2), Select BP (3), Switch Between Display and Changes (4), Company Code (5)

tab Vendor Correspondence (1), enter Clerk’s internal address (2)

Save the record.

STEP 4: CONFIGURE OUTPUT PARAMETER DETERMINATION

In Q System Select Fiori  group – Output Control, Fiori tile Output Parameter Determination. You will require authorization with business role SAP_BR_ADMINISTRATOR business catalog SAP_CA_BC_OC.

Select Show Rules for (1) Payment Advice Determination Step (2) Output Type, that Dispatch Time shows (4) “immediately”, if not (3) Edit

Check the Receiver is set for the 2 lines as below

Check that Determination Step Channel is set to EMAIL as below..
You may also send a printout to PRINT and this can be set to DEFAULT printer so it does not print to physical printer but is available in the tile Print Queue.

Select Show Rules for (1) Payment Advice Determination Step (2) Printer Settings set to DEFAULT printer. You may set this to print to physical printer as well and this will require Print Queue to be setup.

Select Show Rules for (1) Payment Advice Determination Step (2) Email Settings, select (4) Direct Input, Sender email address (5) noreply@mycompany.com, Click on OK (6) , to change, click on (3) Edit 
Click on (7) Activate. Answer Yes to question below:

Select Show Rules for Payment Advice Determination Step Form Template as FIN_FO_PAYM_ADVICE, ensure as (4) below , if not (3) Edit.  FIN_FO_PAYM_ADVICE is a predefined template, if you want custom template, please select accordingly

Select Show Rules for Payment Advice Determination Step Email Recipient, ensure nothing is defined as below

Select Show Rules for Payment Advice Determination Step Output Relevance, ensure as (4) below , if not (3) Edit 

STEP 5: TEST PAYMENT FORM

Please follow steps for Payment Proposal and Payment Run

Please find below the sample printout. The pdf attachment is standard or as customized in the blog for Master form and Content Form.

Hope this was useful.

Mahesh Sardesai
SAP Canada
S/4HANA Cloud Product Expert http://bit.ly/2F1rx1i #SAP #SAPCloud #AI

In this blog, we will have a small test about how to realize a deadlock in HANA.

Multi version concurrency control ensures consistent read operations. However, it does not prevent concurrent write operations on the same data and the associated inconsistencies (dirty write, lost updates). To prevent concurrent write operations on the same data record, the SAP HANA database uses exclusive write locks at row level. For each write access, a row-level write lock is obtained. Concurrent transactions which need to write the same record have to wait until the lock is released. Write locks are implicitly requested before an update or delete operation is executed.

A deadlock situation occurs, if two transactions both need to update two records R1 and R2, and one transaction is given the lock for R1 and the other one the lock for R2. The transaction manager detects the deadlock and aborts one of the transactions.

In the following test, I created two stored procedures P1 and P2. Both P1 and P2 need to update all entries in one table(10000 entries). P1 updates the table from the last entry to the first entry. While P2 updates the table from the first entry to the last entry. Both P1 and P2 will execute at the same time. And one of the procedure will get aborted with deadlock error.

 

 

Execute the Transaction P1

Then execute the Transaction P2 in another SQL console session immediately

Here the transaction P2 aborted with the error deadlock detected. Could not execute ‘CALL “TRANSACTION_P2”’ in 29.059 seconds . SAP DBTech JDBC: [133]: transaction rolled back by detected deadlock: “TRANSACTION_P2”: line 8 col 3 (at pos 189): [133] (range 3): transaction rolled back by detected deadlock: TrexUpdate failed on table ‘TEST1’ with error: transaction rolled back by detected deadlock: Deadlock detected while executing transaction (TRANSACTION_ID=21, UPDATE_TRANSACTION_ID=60740880), rc=4616

Deadlocks are situations where two or more transactions lock each other cross-wise so that no transaction will ever be able to proceed. Usually deadlocks are caused by the application design.

If SAP HANA recognizes a deadlock based on a transactional lock, one of the transaction will be terminated and the following error is issued: SQL error 133: transaction rolled back by detected deadlock

This behavior is different from other databases like Oracle where a deadlock will only terminate the current DML operation and not the whole transaction.

For more details, please refer to SAP note 1999998 – FAQ: SAP HANA Lock Analysis. http://bit.ly/2CR7dd2 #SAP #SAPCloud #AI

The OpenAPI Specification (formerly Swagger) let us “create the RESTful contract for your API, detailing all of its resources and operations in a human and machine-readable format for easy development, discovery, and integration.” So, using Swagger, we can specify how our API will look, which operations we can perform on it, the expected parameters or payloads, and the format of the responses of the operations.

By having a way to define the contracts, it gives us the ability to quickly design an API and, from this design, prototype it without creating any real backend. https://goo.gl/bKSDyt #DataIntegration #ML