Using the Data Pool Service for Machine-to-Machine (M2M ...
Using the Data Pool Service for Machine-to-Machine (M2M ...
Using the Data Pool Service for Machine-to-Machine (M2M ...
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
Message flow via <strong>M2M</strong><br />
XML inbound data<br />
Note that any generated XML EAN/UCC Response Message or GDSN Exception Message is au<strong>to</strong>matically sent <strong>to</strong><br />
<strong>the</strong> sending <strong>M2M</strong> User.<br />
DPM processes each XML command message, i.e., CPC, CIS, CIC, CIP, RFCIN, and generates ei<strong>the</strong>r<br />
Deleted: RCI,<br />
• An EAN/UCC XML Response Message stating that <strong>the</strong> message was processed successfully.<br />
• A GDSN XML Exception message stating that <strong>the</strong> message has errors.<br />
DPM processes each XML business data message, i.e., CIN and CPN, and <strong>for</strong><br />
• Valid data, DPM generates<br />
• An EAN/UCC XML Response Message stating that <strong>the</strong> message was processed successfully<br />
• If on your Company Profile page, you selected a GDSN XML version as your Notification Format, you will also<br />
receive an EAN/UCC XML Response Message containing <strong>the</strong> <strong>Data</strong> Load Status Report (DLSR) in XML <strong>for</strong>mat.<br />
For a sample report, see <strong>the</strong> <strong>Data</strong> Load Status report <strong>to</strong>pic.<br />
• Invalid data, DPM generates<br />
• A GDSN XML Exception message stating that <strong>the</strong> message has errors. When this occurs, Your in-house system<br />
should process <strong>the</strong> GDSNException and generate an alert out of <strong>the</strong>ir systems<br />
• An internal GXS email notification, which is sent <strong>to</strong> <strong>the</strong> GXS support team email address. This is so that GXS is<br />
aware of <strong>the</strong> problem if you need technical support.<br />
• Corrupt data — if an XML data message parses correctly but still cannot be interpreted by DPM, an<br />
internal failure is flagged in <strong>the</strong> Communications Gateway. Gateway moni<strong>to</strong>ring detects this and GXS<br />
will proactively follow up on this failure with your Membership Organization (MO).<br />
DPM DDF inbound data<br />
DPM processes inbound data and generates <strong>the</strong> <strong>Data</strong> Load Status Report (DLSR) . Any invalid data, e.g.,<br />
non-numeric when numeric expected, is shown in this report.<br />
Corrupt data, e.g., record/field structure not apparent or empty, is interpreted by DPM as an indica<strong>to</strong>r that<br />
something is very wrong. A DLSR report is NOT generated, but <strong>the</strong> Supplier Load Processing Status will<br />
have a status of Rejected and a message stating <strong>Data</strong>base error and <strong>the</strong> catalogue is locked<br />
(VEND_CAT_BUSY=Y) until <strong>the</strong> corrupt data is fixed.<br />
Note that<br />
• Because DPM CSV/DDF goes straight in<strong>to</strong> <strong>the</strong> data load process (<strong>the</strong>re is no intermediate parsing),<br />
you must always access <strong>the</strong> <strong>Data</strong> Load Processing Status and <strong>Data</strong> Load Status reports <strong>to</strong> check on<br />
<strong>the</strong> success or failure of <strong>the</strong> data load. For a sample report, see <strong>the</strong> <strong>Data</strong> Load Status report <strong>to</strong>pic.<br />
• The DPM <strong>M2M</strong> interface was designed <strong>to</strong> meet <strong>the</strong> GDSN XML/AS2 messaging recommendation and<br />
<strong>the</strong>re<strong>for</strong>e a DPM CSV/DDF (CIN,CPN) inbound <strong>to</strong> DPM has no EAN/UCC Response or Exception sent<br />
back <strong>to</strong> you.<br />
<strong>M2M</strong> Guide <strong>for</strong> Suppliers 3