I have written 10 best practices for implementing 3PL for your BYD project. I have grouped as "Programming" or "Testing" where these bset practices are to be used. (BTW, I meant to number the bullets but the blog bulletting is a bit unwieldy.)
The documentation for each message type needs to be read thoroughly by the development team. Attention must be paid to the TypeCode within
the message, since a message can be used for multiple purposes. Eg for an IDEC (inbound delivery confirmation) message, the codes are allowed:
1563 Customer Return
1564 Intracompany Confirmed Inbound Delivery
1566 Supplier Confirmed Inbound Delivery
to denote what the IDEC is for. Similarly each field has a range of valid codes, and the developer should not use any invalid values (such as 1567, etc).
<Item>
<ID>10</ID>
<ID>10</ID>
For example,
SGN-201209040002 – is a message from the Singapore warehouse. The use of the date with a sequence (0002) guarantees uniqueness for up to 9999 messages in 1 day.
If a ODEC ID is re-used, there will be an error. Attention must be paid to use the right format and unique sequencing.
For example, an ODER should be tested for normal shipping , return to manufacturer and other functional codes. In addition, the dimension of 1 item and multiple line items must be tested also.
Also, testing must be done for the negative case. In other words, testing should be done for invalid sales orders, invalid 3PL ODERs, invalid quantities to confirm the system handling.
For any nonworking message, the team should get the payload XML and diagnose the issue using multiple methods, including soapUI (see item 4)
I hope this tips help your 3PL implementation. I welcome your feedback and of course, your likes.
Tim.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
13 | |
7 | |
6 | |
4 | |
4 | |
3 | |
3 | |
3 | |
3 | |
2 |