Export Content and Deleted PKs

A common use case might be to export content from many tables (for example, all tables related to Buy Shipments) that have been modified within a given date range. It might also be important to export the list of shipments that have been deleted within the same range. The following example shows an example of an export request message to achieve this (although for brevity, not all child tables for the SHIPMENT are shown).

Table content is exported according to the information specified in the "tables" structure.

Deleted PKs are exported according to the information specified in the "deletes" structure.

Use Case Description:

• Specify date range at the header level to be available to both request items
• Add a request item for SHIPMENT content
• Add a request item for deleted SHIPMENT PKs.

curl -u username:password -X POST -H "Content-Type: application/json" -d '
 {
    "schema": "PRIMARY",
    "contentType": "text/plain,
    "rangeAfter" : {
        "value": "2022-09-01T00:00:00Z"
    },
    "rangeBefore": {
        "value": "2022-09-30T23:59:59Z"
    },
    "targetSystem": {
        "targetURL": "https://objectstorage.us2.oraclecloud.com/...bucket-details.../o/",
        "appendName": true,
        "httpMethod": "PUT"
    },
    "tables" : {
        "items" : [
            {
                "tableName": "SHIPMENT"
            }
        ]
    }
    "deletes" : {
        "items" : [
            {
                "tableName": "SHIPMENT"
            }
        ]
    }
}'
https://servername.us2.oraclecloud.com/logisticsRestApi/data/v1/exportRequests

Note:

• The export status will report the same information for both types of items.
• The parts for deleted PKs will also be CSV format files but will only contain the primary key columns.
• The part names for deleted PKs will begin with "DELETE_".
• Part size control is identical for "tables" and "deletes" parts.
• Deleted PKs can't be exported for a business object.
• • Deleted PKs aren't captured for transactional tables.