zkEDI Workflow Execution
A walkthrough of the sample batch script
Overview
The ABAP program ZPROUBC_SHUTTLEIDOC_EXMPL can be used to demonstrate triggering the we created earlier PRVD Baseline workflow
Prerequisites
Have an idoc of the type you just deployed for workflow modeler. For newly created dev/sandbox systems, the INTERNAL_ORDER01 idoc type should be available to you if you
Locate an appropriate iDoc from transaction code WE05
Copy an idoc number for use later.
In your SAP system, open the the program ZPRVD_SHUTTLEIDOC_EXMPL the program pictured below shall appear
Authentication
If they are not already set from parameter IDs - you may enter your PRVD organization ID, subject account ID, workgroup ID. You can also leave these parameters blank and the program will use the newest-created subject account for your SAP user ID.
Enter the iDoc number you copied earlier.
Execute by selecting the green checkmark. Additional debugging instructions shall follow
We'll highlight a few key areas you can debug to better understand PRVD Baseline messaging in ABAP
Authentication
Using the refresh token JWT stored in the ZPRVDTENANTS table for the given user subject account id, an API call is made to retrieve an access token from the PRVD Ident microservice through the API and iDoc helper classes.
PRVD Organization ID, Subject Account ID, and Workgroup ID are selected either from the batch program front-end or from user defaults.
Protocol Messaging
Assuming a successful authentication, the program proceeds to marshall the selected idocs for baselining
The selected iDoc data is transformed to JSON format and included to the REST payload.
The call to the PRVD Baseline API is then triggered
ZK-proof generation for the iDoc
The PRVD Baseline API creates the initial zero-knowledge proof of the data off-chain
Once your ZK-proof is created - you can check out the created zero knowledge proof in the workflow console in Shuttle.
You may notice your iDoc number or purchase order number are absent from the workflow console; this is to preserve the privacy of your data as it enters into the blockchain. The PRVD Baseline API itself does not retain this information for similar privacy reasons
Data directly linking the zk-proof to the idoc is only maintained in SAP. An entry is also created in the ZBPIOBJECTS table linking your idoc, underlying business document, and the ZK-proof together. This table entry will provide an easy to use data link in SAP of the generated ZK proof, the idoc, and the underlying business document in SAP.
Last updated
