CM_EHFND_PC_SRQ - Messages for Product Compliance Regulatory Service Request

The following messages are stored in message class CM_EHFND_PC_SRQ: Messages for Product Compliance Regulatory Service Request.
 It is part of development package EHFND_SDSA_SERVICE_INTEGRATION in software component EHS-SUS-FND. This development package consists of objects that can be grouped under "Integration of SDS Authoring Service".
Message Nr ▲
Message Text
000Status update is triggered and will be processed in the background.
001Error while requesting a status update.
002Error while reading the product request list from the service provider.
003No communication arrangement found.
004Error while initializing the HTTP client.
005Error while initializing the web API client.
006Error in communication with the service provider.
007All product requests are up to date.
008Error while creating tasks for product request of instance &1.
009Error while updating the product request database table for instance &1.
010Product request &1 is ready. Subsequent tasks are triggered.
011Updating product request database table for instance &1.
012Reading product requests that are changed after &1.
013Issues in communication setting. Please check customizing settings.
014This service request has an unknown status.
015Inserting a new service request entry into the database failed.
016Updating an existing service request in the database failed.
020The substance request &1 is ready. Subsequent tasks are triggered.
021Task for req. &1 to submit a new publ. subst. (&2; &3; &4) is triggered.
022You successfully activated the refreshment of the product list.
023You successfully activated the refreshment of the public substance list.
024You activated fetching dangerous goods info for the compliance view &1.
025You fetched safety data sheet info for the compliance view &1.
026You triggered the request &1 to submit new product (&2; &3; &4).
027Task for req. &1 for a new private substance (&2; &3; &4) is triggered.
028You successfully activated the refreshment of the private substance list.
050<<-- Dangerous Goods Tasks -->>
051Service request ID: &1; Compliance View ID: &2
052Processing of task "Get DG Info" has started.
053Processing of task "Get DG Info" is finished.
054This service request does not exist.
055This service request is not in status "Ready".
056The business feature for dangerous goods is not active.
057No regulation assigned that matches the &1, edition &2. Data is ignored.
058A service request with ID &1 ("&2") with edition "&3" does not exist.
059Reading basic classification for product request with ID &1.
060Error in writing product request data to the compliance assessments.
061Reading basic classification for the product request failed.
062Released assessment found at later regulation &2 (&3). Data is ignored.
063Cannot find compliance assessments for the compliance view.
064
065Compliance Requirement: &1
066Compliance Requirement Edition: &1
067Dangerous Goods Data of Product Request:
068Number Type: &1
069Number: &1
070Basic Descriptions:
071Language: &1
072Description: &1
073Reading compliance assessments from the database:
074BCO ID: &1
075Compliance Pattern: &1
076Internal Name of CCI: &1
077Calling API to create assessments with the following data:
078Root Node:
079Basic Classification Details:
080Basic Classification Description:
081Internal ID of the Compliance View: &1
082Transport Permission: &1
083Classified as dangerous good: &1
084Language &1 is not supported by compliance requirement &2.
085Provide a name or at least a CAS number or an EC number.
086The request of a new public substance failed.
087The request of a new public substance is triggered.
088Version &1 found for Compliance Requirement &2 Edition &3.
089We couldn't find any substance for the listed substance &1.
090The listed substance &1 can be mapped to several substances.
091The qualifying word prefix &1 is not supported by regulation &2.
092The qualifying word suffix &1 is not supported by regulation &2.
093Marine pollutant &1 is not supported by regulation &2.
094Reportable quantity &1 is not supported by regulation &2.
095Printing of reportable quantities is not supported by regulation &1.
096Inhalation Hazard Zone &1 is not supported by regulation &2.
097Marine pollutant is not supported by regulation &1.
098Environmentally hazardous is not supported by regulation &1.
099<<-- Safety Data Sheet Tasks -->>
100Processing of task "Get SDS Info" has started.
101Processing of task "Get SDS Info" is finished.
102Business feature for safety data sheet management is not active.
103Reading safety data sheets (SDS)results for product request with ID &1.
104Reading safety data sheets results for product request with ID &1 failed.
105The safety data sheet service request with ID &1 failed.
106You need a safety data sheet service request &1 with internal number &2.
107Safety data sheet data of product request:
108Generation date: &1; major version: &2; subversion: &3
109Mime type: &1
110ID of the compliance view: &1
111Safety data sheets results:
112Country/Region: &1
113Safety data sheet documents:
114HTTP error &1: &2
115The service provider returned no safety data sheet results.
116No active version can be determined for requirement &1.
117Inserting your data into the database failed.
118The request of a new private substance failed.
119The request of a new private substance is triggered.
120Please provide a valid substance.
121The physical-chemical properties you entered are invalid or released.
122The safety-related properties are invalid or have already been released.
123An error occured while the system was reading the product data.
124A mandatory value is missing in product data.
149<<-- Finalize Tasks -->>
150Task "Finalize Product Request" created.
151Processing of task "Finalize Product Request" has started.
152Processing of task "Finalize Product Request" is finished.
153Error while creating task "Finalize Product Request".
154Preceding tasks "&1" and "&2" have been successfully finished.
155Preceding task "&1" is still in progress.
156Preceding tasks "&1" and "&2" are still in progress.
157Update of status of request with ID &1 to "&2" is requested.
158Status of request with ID &1 has been updated to "&2".
207All public substance requests are up to date.
208Error while creating tasks for a substance request for instance &1.
209Error while updating database table for pub. substance requ. instance &1.
210The substance request &1 is ready. Subsequent tasks are triggered.
211Updating public substance request database table for instance &1.
212Reading public substance requests that have been changed after &1.
213Updating private substance request database table for instance &1.
214Reading private substance requests that have been changed after &1.
215Error while updating database table for pri. substance requ. instance &1.
216All private substance requests are up to date.
220<<-- Submit New Substance Tasks -->>
221New public substance request for &1, CAS number: &2, EC number: &3
222Setting external status of request to "In Progress"
223Setting internal status of request to "In Progress"
224Sending public substance request &1 for substance &2 to external service.
225New private substance request for &1, CAS number: &2, EC number: &3
226Sending private substance req. &1 for substance &2 to external service.
230<<-- Receive New Substance Tasks --->>
231Error while creating a new public substance.
232Unknown substance type is received.
233The substance request contains no listed substances.
234Listed substance &1 contained in the substance request is unknown.
235The substance request contains more than one root listed substance.
236The substance request contains no root listed substance.
237Error in modifying substance &1 by the API (&2, &3).
238Error in reading public substance &1 by the API.
239Error in modifying substance &1 text for language &2 by the API.
240Error in modifying substance &1 condition for listed substance &2 by API.
241No changes found for substance &1 in the substance request.
242Error while updating an existing substance.
243Substance request &1 is ready.
244Task for receiving a new substance (&1; &2; &3; &4) was triggered.
245Task for receiving an updated substance (&1; &2; &3; &4) was triggered.
246Error while creating tasks for the substance request of instance &1.
247Start receiving of request &1 for a new substance.
248Substance request was received. Creating of public substance &1 started.
249Setting external status of request to "Completed".
250Setting internal status of request to "Completed".
251Processing of the public substance request was finished successfully.
252Receiving of request &1 for updated substance has started.
253Substance request was received. Updating of public substance &1 started.
254Listed substance &1 is determined as root for the substance.
255&1 conditions determined for the substance.
256&1 company-specific names determined for the substance.
257Language &1 (&2) is not active in the system. Name '&3' will be skipped.
258Error in reading private substance &1 by the API.
259Processing of the private substance request was finished successfully.
260Product Request (&1)
261Substance Request (&1)
262New substance request for CAS number &1, EC number &2
263New substance request for CAS number &1
264New substance request for EC number &1
265Skipped Public Substance Request with initial key for substance &1
266The segregation group &1 is not supported by regulation &2.
267Segregation groups are not supported by Regulation &1.
268Error while deleting technical names for substance &1.
269Error while creating technical names for substance &1.
270An error occured while you created technical names.
271Dangerous good class: &1
272Packaging group: &1
273List item variant: &1
274Technical name &1 (substance): &2
275Marine pollutant &1 (substance): &2
276Reportable quantity &1 (substance): &2
277Qualifying word prefix: &1
278Qualifying word suffix: &1
279Inhalation hazard zone: &1
280Segregation groups:
281Segregation group: &1
282An error occured while the system wrote the service request data.
283Skipped Private Substance Request with initial key for substance &1
301No arrangement found for communication scenario &1, service &2.
302Cannot create HTTP client for RFC destination &1. Exception code: &2.
303No RFC destination is provided for service &1.
304Cannot receive client proxy for service &1.
305Error in communication with the web API.
306Insufficient data provided for submitting a new public substance.
307An error occured while reading expanded product request with ID &1.
308An error occured during converting UUID &1 to outbound format.
309The request for a new product failed.
310The request for a new product was triggered.
311Processing of the product request was finished successfully.
321New product request for &1, physical-chemical &2, composition &3
324Sending product request &1 for product &2 to external service.
350HTTP request header - &1: &2
409Request with ID &1 already exists in service. Try to update the status.
500PCAL_LOG: &1&2&3
501CX_CP_REMOTE occured &1 &2
502CX_GATEWAY occured &1 &2 &3
503Support ID found: &1
504Detailed logging is active.
Privacy Policy