Page Comparison

Status

Description

03

Status 03 indicates, that the IDOCs have not been sent to the Message Broker component. This may happen because of the following reasons:

• outbound options not been configured as Transfer IDOC immediately in Partner Profile (transaction WE20) for logical system /PACG/ECM and the given IDOC type

  Image Modified

• qRFC Outbound Queue has stuck – the queue status can be checked and message processing can be brought back to the normal state in transaction SMQ1, as described in section Message queues.

• message broker is down – you may want to verify, if the respective Windows service is up and running as described in section Deleting Master Data in the Cloud
  
  

  INTRODUCTION

  When the master data are sent from SAP to the Cloud (e.g. Activity Codes based on SAP Inspection Catalog Codes), the IDocs are generated – every IDoc corresponds to one master data object. The IDoc contains the main segment (different one, depending on the object type). The segment contains a field playing the role of an identifier of the object. E.g. in case of Activity Code based on SAP Inspection Catalog Codes the IDoc with IDoc Type /PACG/ECM_ITYPE_SRERRCOD is issued for every Activity Code. The IDoc contains a segment /PACG/ECM_IS_SRERRCOD, the field ID identifies uniquely the object in the Cloud:
  

  Image Modified

  
  Every FSM Cloud Connector IDoc contains a segment /PACG/ECM_IS_CONTROL, playing a role of a control segment. The field TRANSACTION_TYPE informs the Cloud whether the object is to be created in the Cloud (or updated, if it exists) or deleted:

• 'C' – corresponds to the creation/update request,

• 'D' – corresponds to the deletion request.
  
  

  Image Modified

  
  If you want to delete the given object in the Cloud, you must create an IDoc with TRANSACTION_TYPE = 'D'.
  

  SENDING DELETION REQUESTS USING THE PROGRAMS SENDING THE OBJECTS

  Many programs sending master data from SAP to the cloud contain a checkbox "Delete flag", e.g.:
  

  Image Modified

  
  In that case the selected objects will be sent with TRANSACTION_TYPE = 'D' – they will be actually deleted in the Cloud. This approach can be useful if we have the master data object in SAP and we want to send it together with the information that it is to be deleted.
  

  USING TRANSACTION /PACG/ECM_SEND_DELRQ

  It can be the case however, that the object does not exist in the SAP any longer and we want to delete it in the Cloud as well. In that case resending this object with deletion flag is problematic. In that case the transaction /PACG/ECM_SEND_DELRQ can be used. Two ways of usage of this transaction are possible:

1. We know the identifiers of the objects; we want to delete the object in the Cloud for the given identifiers.

2. We do not know the identifiers of the objects, we rather would like to say "delete the objects which were created from SAP by the IDocs type X, created within last Y months".
   
   
   In that case the IDoc with IDoc Type /PACG/ECM_ITYPE_OPERATION, Message Type /PACG/ECM_OBJDELREQ is used. The IDoc is generic, its data contains the object type used in the Cloud (e.g. ACTIVITYCODE) and the identifier sent by SAP (e.g. G5ZKAMCAU2).
   

   Image Modified

   
   Tip: Open the XSLT Transformation and locate the node "idElement" to find out, what Cloud Message Type should be used:
   

   Image Modified

   Deleting the objects for the given identifiers

   You know, that you want to delete the Activity Codes with the identifiers X1 and X2. Execute the Transaction /PACG/ECM_SEND_DELRQ with the following Selection Screen:
   

   Image Modified

   
   You provide the identifiers in the field "Object key":
   

   Image Modified

   
   The following protocol is generated:
   

   Image Modified

   
   

   Deleting the objects based on the IDocs sent

   You don't know the identifiers of the objects which are to be deleted. Instead the objects which have been created by the outgoing IDocs should be retrieved from the database, their identifiers should be collected and then the deletion request should be sent. You execute the program providing the selection criteria for the IDocs search:
   

   Image Modified

   
   Enter the following fields:

• Basic type: the IDoc type of the IDoc:

Image Modified

• Segment type: The Segment name, in which the Identifier is passed:

Image Modified

• Field name: field holding the identifier of the object:

Image Modified

• Created on: date range, when the IDocs were created.
  
  It is good practice to execute the program with the parameter 'Write Identifiers on Screen" = X and "Test Mode" = X. In that case the outgoing IDocs will not be created and the identifiers determined by IDoc search will be written on the screen:
  

  Image Modified

  
  Once you have verified the identifiers, you can uncheck the "Test Mode" – the IDoc with deletion request will be sent to the Cloud:
  

  Image Modified

• Message Broker administration

• check if the web service of Message Broker is available from SAP. In order to do that, an FSM Cloud Connector menu should be opened (transaction code /n/pacg/ec while in SAP main menu) and Administration/Ping Message Broker option should be selected. Upon execution the program will either respond with a success message (connection works), network error message (network problem, service not available or listening on a different port than configured for the client proxy in SOAMANAGER transaction) or SOAP failure, which stands for a problem with web service/SOAP format

• check in Message Broker log file if it doesn't contain any error entries related with the messages received from SAP

18

Status 18 indicates, that the message has been sent to (and received by) Message Broker, but its reception has not been confirmed by the cloud. This may happen because of the following reasons:

• connection between Message Broker and Cloud has been broken, which could be an effect of network failure or of the Cloud being down

• problems in the Message Broker – please check Message Broker log and verify if there are no error entries related to the message processing

• message confirmation failed to be delivered – you may want to restart the Message Broker windows service and verify if this helps

41

Status 41 means, the message has been received by the cloud. If the data do not seem updated in the cloud, this could mean one of the following:

• the message was not correct and its parsing failed on the cloud, you may want to set Message Broker logs to DEBUG level, send the message again (e.g. by updating and saving the business object in SAP again) and check if the message contents are correct

• the message refers other objects, that are not present on the cloud (e.g. a service call refers an equipment, that has not been synchronized or has been deleted from the cloud), you may update references and send the message again (e.g. by updating and saving the business object in SAP again)

• there is a problem in the Cloud not related to the particular message, the case should be investigated by SAP