CreateRfcAttachment

Create an attachment for an existing RFC.

Request Syntax


{
   "Content": blob,
   "FileName": "string",
   "RfcId": "string"
}

For information about the parameters that are common to all actions, see Common Parameters.

The request accepts the following data in JSON format.

The content of the RFC attachment, which is binary data.

Type: Base64-encoded binary data object

Required: Yes

The file name of the RFC attachment.

Type: String

Required: Yes

The RFC identifier for an RFC attachment request.

Type: String

Required: Yes


{
   "AttachmentId": "string",
   "RfcId": "string"
}

If the action is successful, the service sends back an HTTP 200 response.

The following data is returned in JSON format by the service.

The attachment identifier in an RFC attachment response.

Type: String

The RFC identifier in an RFC attachment request.

Type: String

For information about the errors that are common to all actions, see Common Errors.

InternalServerError

An unspecified server error occurred.

HTTP Status Code: 500

InvalidArgumentException

A specified argument is not valid.

HTTP Status Code: 400

InvalidRfcStateException

The RFC is not in a state that allows the requested operation. Actual status code: 409

HTTP Status Code: 400

ResourceNotFoundException

A specified resource could not be located. Actual status code: 404

HTTP Status Code: 400

ServiceQuotaExceededException

You have exceeded your service quotas.

HTTP Status Code: 400