Show TOC

 Replicate Advertisement Graphic as Bulk

 

To replicate the advertisement graphics.

Technical Data

Entity Type

Service Operation

Software Component Version

RTLDDF 200

Release State

Released

Technical Name

AdvertisementGraphicReplicationBulkRequest_In

Namespace

http://sap.com/xi/RTLDMF/Global2

Category

Third-party A2A

Direction

inbound

Mode

Asynchronous

Idempotency

Not applicable

Change/Update Behavior

Type 1

P2P Communication Enabled

True

Business Context and Use

The Replicate Advertisement Graphic as Bulk service operation can be used by any industry for creating printed materials, which are used to communicate information to consumers.

Features

The inbound operation creates, updates, and deletes the image data.

Product images are required during the promotional planning process. Images can be assigned to one or more products. In addition, they can be imported to represent a theme; for example, a cow to promote chocolate. In this case, the picture does not have a product identifier. The image contains the path to the Multipurpose Internet Mail Extension (MIME) repository where the actual image is stored.

The operation includes the following main node:

  • Message Header

    Since the AdvertisementGraphicBulkReplicationRequest_In operation is enabled for bulk-handling, it is possible to send out more than one instance on advertising graphic object instances. The message header is defined at the bulk operation level and at the business object instance level. Either one of them must be filled while posting the inbound message. The receiver system first reads the details defined in the instance level message header. If this level is not defined, the system copies the detail from the bulk message header.

Message Types

  • Advertisement Graphic Replication Bulk Request

Error Handling

The Replicate Advertisement Graphic as Bulk operation supports the Forward Error Handling (FEH) concept.

Notes on SAP Implementation

Enhancements

The /DMF/SE_PMR_ADGRPHCRPLCT Business Add-In (BAdI) is available for this inbound operation. The BAdI is used to enhance the inbound message, and it is defined as an external customer BAdI. A default implementation is not delivered.