Binding a Standard QC to a button in Custom object and passing parameter to Standard QC from Child node of Custom Object on selection.
This document covers how to pass parameters from Child node of Custom Object on selection to the Standard QC (here Ticket) binded to a button to open a Standard ticket QC screen from a custom business object child node.
Note: We dont have a Alternative Key in root level.
This document covers how to pass parameter from Custom object child node record to Standard QC. Thanks to Abhishek Raj for support.
Table of Contents:
Creating a button on Custom Object.
Creating a data field on Root level and binding the thing type to the field
Using the Standard QC Inport Name and Binding the button to Standard QC(here Ticket QC)
We had the below requirement for opening a Standard QC (Ticket) by passing values from Custom Object child node on selection. Currently to open Standard QC( here Ticket QC) , passing the value from Child node is not available as standard functionality because of the limitation to outport and inport in SAP Cloud for Customer.However, we got a workaround for the same.
For example: Users wish to create ticket from the custom object and the QC should have the look and feel of the Standard QC of the ticket .
Binding the button with the Standard QC of ticket and use the standard inport with its standard name.
Creating a button on Custom Object:
A button to be created for opening the standard QC screen of QuickCreate type.
Creating a data field on Root level and binding the thing type to the field:
Creating a data field at the root level and binf the Service ticket TT screen (COD_SRQ_AGENT_TT) with it.
CCTS type of the field should be identifier.
Creating Outport :
Use the terminology as in Standard QC of the Ticket and portTypePackage used as below:
Creating an Outport with reference to above as below:
Using the Standard QC Inport Name and Binding the button to Standard QC(here Ticket QC):
Below we are able to pass parameter(data) from custom Business Object child node to Standard Ticket QC without any Alternative key in the Custom Business Object at root level.
Also we are able to open the ticket standard QC from custom business object child node New Ticket button using the standard PortTypePackage ” CreateWithParent” maintaining the UI consistency throughout the solution.
Hope this is useful to community for making use of Standard Functionality in a Custom screen. Please note that this can be done using Standard Import provided by SAP in Standard screen and when we do not have a Alternative Key. Also we are making use of ABSL code for populating and retrieving other values after selection.
Great Document ... Very well explained.. @rajpriya6
Nice Document Raj Priya 🙂