substring(//DemandAssignmentRequest/DemandAssignmentRequest/TicketItem/ItemAssignment/AssignmentUUID,6,8)
This blog is created to throw some lights on SAP CPI concepts, which experienced in my journey. Trying to explore more about HCI/Cloud platform integration/SCPI and sharing the contents to help you. Thanks for all Users your support. Please give your comments below ...
Wednesday, 11 November 2020
Monday, 2 November 2020
XPATH or Router namespace based field handling in SAP CPI/SCPI
In Content Modifier, XPATH namespace based field handling in SAP CPI/SCPI
Input Field: <n1:LX_TKT_EXTERNALID>38683</n1:LX_TKT_EXTERNALID>
If we are using direct namespace like below will not work:
//DemandReplicationRequest/DemandHeaderInfo/RefTicketInfo/ns1:LX_TKT_EXTERNALID
Correct XPATH: //DemandReplicationRequest/DemandHeaderInfo/RefTicketInfo/*:LX_TKT_EXTERNALID
Field node not exist condition check : (Router)
Router condition: count(//PromisedDateTime) != 0
Count expression in router to field the field/node exist
In router, we tent to find the node / field exist in the incoming xml , based on the we will route the path.
Expression Type: XML
Condition: count(//PromisedDateTime) = 0