CS1294708, ER 123122
https://mingle-portal.us2.prd3.inforcloudsuite.com/v2/CONCIERGE_PRD/32bfda04-ad8e-4943-9b7d-0f3d57e84aaf
Proposal: Best Practices Approach for LN Session Across Multiple Disciplines
I propose creating an LN session designed to support multiple disciplines, following a best practices approach.
EDI Team Responsibilities
The EDI team ensures successful data flow from AE to LN.
This includes:
- Orders have completed mapping in AE (including new BP and/or Ship-To addresses created).
- Messages are managed appropriately.
Important: The EDI team is not responsible for the contents of the message.
Customer Service (CS) Team Responsibilities
CS may need to address missing or incorrect content/criteria, such as:
- Part Cross Reference
- Price (e.g., Price List issues)
- Minimum Order Quantity (MOQ)
- Any other details managed by CS
Note: The “Blackhole of ION” is not an acceptable solution.
Session Features
- The session should automatically refresh and function as a Draft Orders Queue.
Proposed Business Process
- CS works through the queue and references the PDF from NG2 if needed.
- If a PO appears in the shared mailbox but not in the work queue, CS should contact the EDI team for investigation.
- This is likely due to a BOD error.
Rationale
This approach is a better first step before implementing AE Notifications.
It prevents overwhelming CS with notifications for steps B, C, D, and E when they already know that completing Step A means subsequent steps will also need to be completed.
Current LN sessions are not sufficient for migrating to AE/LN or onboarding a new trading partner:
tdsls2100m000 – Received Customer Orders Overviewtdsls2600m100 – Received Customer Orders
