Confirmation Using Message Manager (with Error Recording)

You can inform the data pool or your data provider (vendor) about the processing status of the data you have received and any errors found in the data records by sending Catalogue Item Confirmation (CIC) messages. You can do this using the report RWGDS_MESSAGE_MANAGER (transaction WGDS_CONF_MSG_MNGR).

You can call up this report by using transaction SE38, or from the SAP Easy Access screen by choosing Start of the navigation path Logistics Next navigation step Retailing Master Data Material Data Price Catalog Inbound Processing Confirmation Sending Messages and Statuses End of the navigation path .

Prerequisites

You are using GDSN (Catalogue Item Notification, or CIN) messages to receive price catalogs, as well as the enhanced price catalog inbound processing (transactions Select and Edit Price Catalog - W_SYNC; Process Price Catalog (enhanced) - W_PRICAT_MAINTAIN), or your own BAdI implementation, for example, to send confirmations by e-mail. In the above transactions, you can set the processing status for each base unit of measure, and record errors for all dependent units of measure as needed.

For more information, see Selecting Price Catalogs for Editing and Editing Price Catalogs (Enhanced).

Note Note

If you want to create message proposals for data received in your system in the form of IDocs, you need a BAdI implementation.

End of the note.

Features

The report determines the message statuses for all selected trade items and uses these statuses to create message proposals for confirmations to be sent to the data pool. The message status is based on the processing status from the enhanced inbound processing and on the existence (or nonexistence) of errors. You can select single, multiple, or all message proposals created by the report, and then transfer the contents of the selected message proposals at once.

You can influence the results output by the report by using various selection options available on the selection screen. For example, you can choose to include the following in your selection:

Message proposals for trade items that match the specified trade item details
Message proposals for trade items with the specified status(es)
Sent and/or unsent message proposals
Message proposals that match your date selection

Each message proposal covers all units of measure contained in a top level trade item (for example, a Catalogue Item Notification). Each trade item (unit of measure of an article) is identified by a Global Trade Item Number (GTIN) and has a valid-from date. Accordingly, a GDSN message contains all trade items (units of measure) included in the top level trade item concerned (for example, a pallet).

Example Example

A pallet consists of 5 cartons, each of which, in turn, contains 4 smaller cartons with 10 pieces of article A each. A pallet can also include different articles. It is also possible for the same article (base unit of measure) to be included in multiple GDSN messages: For example, one message could refer to a pallet containing 10 cartons, each with 100 pieces of article B. A separate message could refer to a pallet containing 5 cartons, each with 150 pieces of article B.

For each base unit of measure, the enhanced inbound processing also displays all other packaging units involved. For article B In the above example, these would include the two sizes of cartons (the larger one and the smaller one) and the two pallets.

This means that article B is included in two different top level GTINs (each representing a pallet). The report creates a message proposal for each top level GTIN related to this article. In the above example, this would result in two message proposals.

CIN 456 (pallet)	CIN 789 (pallet)	CIN 101 (pallet)
Carton 2	Carton 3	Carton 4
Carton 1
Article A	Article B	Article B

End of the example.

Selection

Selection area Trade Item Status

In the selection area Trade Item Status, you can specify the trade item statuses of the trade items you want to include in the message proposals:

With Unsolved Errors: The report creates message proposals containing trade items for which unsolved errors exist.
Synchronized: The report creates message proposals containing trade items without errors that already have been, or have yet to be, created in the SAP ERP article master (processing status Checked or Forwarded in the enhanced inbound processing).
Rejected: The report creates message proposals for trade items that no longer need to be transferred from the data pool. The selection of these trade items is solely based on the processing status Excluded in the enhanced inbound processing and is not influenced by whether or not errors exist for the trade items.
Accepted: The report creates message proposals containing trade items without errors that have the processing status Open, In Processing, or Error in the enhanced inbound processing. The status Accepted is used to inform the data provider that the data supplied is technically readable. The processing status Error is set as a result of posting errors that have occurred in SAP ERP and is unrelated to the existence or nonexistence of errors in the data received from the data pool.

For information about the processing statuses in the enhanced inbound processing, see Enhanced Price Catalog Processing.

Selection area Send Status

In the selection area Send Status, you can specify the send statuses of the trade items or messages you want to include in the message proposals:

Unsent Only: The report only creates message proposals that contain at least one trade item whose current status has not yet been sent to the data pool.
Sent Only: For each top level GTIN in the same catalog and with the same valid-from date, only the message most recently sent is taken into account. The report only creates message proposals whose message status matches that of the message most recently sent for the GTIN concerned. You can use this setting to resend a previously sent message as a new message (copy). If the message concerned contains errors, only the errors that have not yet been solved are transferred in the copy.
Sent and Unsent: This setting is a combination of the two options mentioned above. The report creates only one message proposal for each top level GTIN (catalog and valid-from date). This allows you to transfer the current message status for all top level GTINs, regardless of whether or not the information has been sent to the data pool before.

A closed envelope ( ) indicates that the information has been sent before, while an open envelope ( ) indicates that the information is new and has not been sent.

Selection area Trade Item Details

In the selection area Trade Item Details, you can specify various properties of the trade items you want to include in the message proposals: All selection criteria in this area are linked by an AND operation. The input field Created On refers to the time when the Catalogue Item Notification was received in SAP ERP. You can use the options for expanding the trade item selection to specify whether or not you want to include additional trade items in the message proposals, apart from those that match the trade item details entered:

Specified Items Only: No expansion of the trade item selection takes place.
All Items of the CIN: In addition to the trade items that match the specified trade item details, the report also selects all other trade items of the CINs identified on this basis.
All Items with Same Base Unit: In addition to the trade items that match the specified trade item details, the report also selects all other trade items of the CINs identified on this basis, as well as all other trade items of all CINs that also contain the trade items concerned.

Example Example

Example: In the selection area Trade Item Details, you select a carton. This carton is included in CIN 123, which contains a pallet, the carton, a two-pack, and the base unit of measure. The same base unit of measure is also included in CIN 789 and CIN 101.

With the setting Specified Items Only, the report does not expand the selection. To create the message proposal, the report has to identify the top level GTIN and the base GTIN, but ignores the two-pack.
With the setting All Items of the CIN, the report expands the selection by including all trade items of CIN 123.
With the setting All Items with Same Base Unit, the report performs the expansion described above and in addition includes all trade items of CIN 456 and CIN 101.

CIN 123 (pallet)	CIN 789 (pallet)	CIN 101 (pallet)
Carton 1	Carton 3	Carton 4
Two-pack
Article B	Article B	Article B

End of the example.

Selection area Error Creation Details

In the selection area Error Creation Details, you can specify the time period during which the errors you want to include in the message proposals were created, as well as the user(s) who created the errors.

The report ignores errors that were recorded outside the specified time period. This can result in positive confirmations (with the status Accepted or Synchronized) being sent, even though errors exist. Since the GDSN standard allows the status Accepted to be sent in any case, that is, even in the presence of errors, an additional check is required only for the status Synchronized. This check determines whether or not all trade items of the CIN are free of errors, while ignoring all other selection parameters. If any unsolved errors are found during this check, these errors are included in the selection results and, consequently, in the message proposals.

The report ignores errors that were recorded by users other than those specified here.

Selection area Parallel Processing Options

In the selection area Parallel Processing Options, you can specify how the message proposals are to be transferred, after the report has selected the relevant data based on the selection parameters described above, and determined the status of the message proposals. You can use parallel processing to transfer the message proposals by making appropriate entries in the fields Number of Parallel Jobs, Server Group, and Minimum Trade Items per Job.

Selection area Output Options

In the selection area Output Options, you can specify whether or not you want the processing statistics and/or the application log to be displayed. You can view the application log at any time, using the transaction Analyze Application Log - SLG1. For this purpose, choose the object WGDS_CONFIRMATION and the subobject OUTBOUND.

Standard Variants

Grouping and status determination

When you execute the report, it generates message proposals for messages of the type Catalogue Item Confirmation (CIC) as defined by the GDSN standard. All trade item information belonging to a particular top level trade item is grouped together in a single message. In the lower screen area, the report lists the trade items included in the message proposals concerned. Since message proposals with the message statuses Accepted, Synchronized, or Rejected do not include any trade items with unsolved errors, the list of trade items for these message proposals does not contain any error information. For message proposals with the message status Review – which the report assigns to message proposals that include at least one trade item with one or more errors – the error information is also included in the list of trade items. If a trade item has multiple errors, these are displayed in as many rows with the same trade item ID.

When selecting trade items, the report always checks the validity dates. For trade items that are currently valid, it also selects errors recorded for past validity dates. For trade items whose validity dates are in the future, it selects only errors recorded for the validity dates concerned.

You can use the BAdI method WGDS_CC_2012_CONFIRMATION group_and_stat_determ_of_prop of enhancement spot WGDS_CC_2012_BADI to implement customer-specific grouping and status determination.

Data transfer

The grouped message proposals of the message type CIC are mapped to an internal structure and passed on to the proxy. The data is then re-converted to the external GS1 format by SAP NetWeaver Process Integration.

When the data has been transferred successfully, this is recorded in the database by means of appropriate messages. In addition, the Sent indicator is set for the errors whose data has been transferred.If any errors occur while transferring the data, the system issues an error message.

You can use the BAdI method WGDS_CC_2012_CONFIRMATION sending_of_conf_proposals of enhancement spot WGDS_CC_2012_BADI to implement customer-specific adaptations, for example, to send confirmation messages by e-mail.

Selection when using transaction W_PRICAT_MAINTAIN or W_SYNC

When you execute the report using the function Send Errors and Statuses in the enhanced price catalog inbound processing (transaction W_PRICAT_MAINTAIN), you cannot specify selection criteria on the report's selection screen. In this case, the report only performs the grouping, status determination, and send functions. The selection parameters of the selection areas Trade Item Status and Send Status are read from the Customizing activity Maintain Default Settings for Message Manager.

Determining the top level trade item is possible only for trade items received in the CIN format. When you select trade items that did not arrive in a CIN message, these trade items are included in the grouping process only, but are ignored by the status determination and send functions. The trade items are grouped by vendor, catalog, and base trade item. The Message Type and Message Status fields of the message header are empty in this case. The message details display includes all errors, and a single row for each trade item that does not have any errors. Status determination and sending for these message proposals must be implemented using a BAdI.

Output

The report outputs message proposals, with the message headers displayed in the upper part of the screen, and the item and error details displayed in the lower part for one message proposal at a time. You can display the item and error details of a specific message proposal by double-clicking the message header.

Row/Column	Function/Content
Content Sent Status (Message Content Already Sent)	Indicates that the message status and message details contained in the message proposal have already been transferred. Fields with this icon can also be used as hotspots. Clicking the icon displays an overview of all existing messages for the top level GTIN in the lower screen area.
Content Sent Status (Message Content Not or Only Partly Sent)	Indicates that all or some information (message status or message details) contained in the message proposal has not yet been transferred.
(Items/Errors for This Message Proposal Are Listed Below)	Identifies the message proposal whose item and error information are displayed in the lower part of the screen.
Message Status	Indicates the status of a confirmation message in accordance with the statuses defined in the GDSN standard by GS1.
Confirmation Message ID	Uniquely identifies a confirmation item.
Message ID	Indicates the ID of the related XI message and serves as a hotspot. Clicking this field displays the contents of the message sent.

Note Note

A closed envelope indicates that the message proposal has already been transferred. The current message proposal may or may not be identical to a message that has already been sent.

A current message proposal with a closed envelope can differ from a previously sent message for the following reasons:

A previously existing error has since been solved (the current message proposal only contains unsolved errors).
Even if the content of a message proposal has already been sent (as indicated by a closed envelope), you can transfer it using this report.

End of the note.

Sending confirmation messages

In the results list output by the report, all message proposals listed are selected by default. If you want to send all message proposals created by the report, you can simply choose Send (Send).

If you do not want to send all message proposals contained in the results list, you can deselect or select individual rows as needed before choosing Send (Send).

When the report is executed in the background, all message proposals created are automatically transferred.