MDMXFW - MDC Extraction Framework

The following messages are stored in message class MDMXFW: MDC Extraction Framework.
 It is part of development package MDM_XFW in software component MDM-CLT. This development package consists of objects that can be grouped under "MDC Extraction Framework".
Message Nr ▲
Message Text
001Only one IDoc can be updated at a time
002Target system & is not recognized in source system
003Error processing IDoc of message type &
004Selection operator SIGN contains an incorrect value
005Call # &1 of the extractor
006Extractor checker: missing parameter &1
007Parameter &1 must be entered with a number greater than 0
008Maximum number of &1 calls of the extractor reached
009-> Request received
010-> Extraction started
011-> Data was sent
012-> No data was found
013-> Extraction was canceled
014-> Extraction was canceled by extractor checker
015-> Extraction completed
016Extractor &1 does not exist
017Data IDoc &1 sent; status &2
018No entry in distribution model for message type &1
019More than one entry in distribution model for message type &1
020Parameter i_distmode must be 'I' (IDOC) or 'P' (Proxy)
021Extraction object &1 does not exist
022PIC handling: The data IDocs for extraction object &1 were passed
023PIC handling: Error when passing the data IDocs for extraction object &1
025Selection operator OPTION contains an incorrect value
026Selection operator SIGN must be the same for all entries
027Logical message type &1 is not supported here
028Communication type &1 is not allowed
029Error & when starting the extraction controller
030No selections or transfer segments found
031Repair receipt (request &1) was sent.
032Receipt could not be sent (inconsistency)
033No data found for the request ID &1
034-> Repair data was sent
035Request ID is missing
036An error occurred when scheduling the batch job for extraction
037Rescheduling a request is not possible
038Request data for extraction object &1 was deleted
039Request data for extraction object &1 could not be deleted
040Request &1 was deleted
041Request &1 could not be found
042Action canceled
043You must specify the extraction object
044Request data for extraction object &1 could not be replaced
045No Entry in ALE Distribution Model for &1 &2
046Logical message type does not exist
047Target systems are not the same
050******************** Verification extractor
051No transfer statements with field entries possible
052Segment &1 is not supported
053Table &1 cannot be extracted
054No data found for selection criteria entered
055Incorrect mixed transfer statements
056Data cannot be transferred without header segment &1
057Segment &1 not supported for selection
058Field &1 of segment &2 not supported for selection
059Multiple requests not supported
060No transfer statements allowed
070Update error: Table &1 function &2 return code &3
071Job &1 with ID number &2 is still running
072No extraction required because of repair request &1
100*********** MDM Metadata
101Processing type &1 not supported
102MDM extraction object &1 exists in content version &2
103MDM extraction object &1 does not exist in content version &2
104MDM extraction object &1 was generated in content version &2
105MDM extraction object &1 was deleted in content version &2
106MDM extraction object &1 was saved in transport request
107You cannot change the field content
108Object version '&1' now allowed (only 'A' is allowed)
109Message type '&1' is not allowed
110Content version '&1' is not allowed (only '0001' is allowed)
111Error while saving the metadata
150*** PIC (Receipt-Extraction)
151The field group &1 cannot be used for the selection
152No selection possible for field &1 (only &2 allowed)
153Selection option '&1' is not valid (only &2 allowed)
154Exactly one selection is required for field &1.
Privacy Policy