| Table of Contents | ||||
|---|---|---|---|---|
|
...
In section Field Definition you find a collection of all JSON keys that are used by the interface. As specified in the Jira configuration section for this template some of these are purpose bound and can therefore not be mapped freely.
Currently it is not possible to send data with JSON keys deviating from this list:
JSON field | Note |
|---|---|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| only available SAP inbound |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
|
...
Otherwise, if a predecessor is mapped, no custimizing customizing for the predecessor Id is required.
...
To map both category one JSON key has to be mapped for each category, e.g. IVCATEGORY and IVCUSTOM01. Both field fields have to be mapped with the object SUBJECT and the logical key receives the value of the technical ID of the catalog type for the category scheme, e.g. C or D.
...
The specified SOCM actions can also be called via PPF action.
This option has be the added benefit of freely choosing the execution time of the outbound update but requiring requires more effort to set up.
Open administration of ppf actions via transaction SPPFCADM and navigate to the action of the process type you want to synchronize.
...
Also, the field ‘Direction’ helps to Identify identify whether the synchronization was inbound or outbound.
...